Installing RME - Installing Content Manager Records Enabler

You can install Content Manager Records Enabler on AIX® or Windows®.

The following table describes the authority that is required to install Content Manager Records Enabler on AIX or Windows.

Operating system	Authority required
AIX	Root user or nonroot user with the following permissions: Member of the ibmcmgrp group Read, write, and execute permission on the temp directory. Read and write permissions on the `IBMCMROOT` directory (for example, the /opt/IBM/db2cmv8 directory). Ownership and read, write, and execute permissions on the following directories: $IBMCMROOT/rme $IBMCMROOT/log/rme $IBMCMROOT/config/rme /home/ibmcmadm/log/ /home/ibmcmadm/log/rme /tmp/IBMCM /tmp/RME Ownership and read and write permissions on the following directories: $IBMCMROOT/lib $IBMCMROOT/bin $IBMCMROOT/log $IBMCMROOT/cmgmt $IBMCMROOT/firststeps $IBMCMROOT/config/base $IBMCMROOT/config/bin /home/ibmcmadm Full permission on the WebSphere® Application Server profile. For Oracle databases, read permission on the Oracle JDBC driver. For example, the nonroot user belongs to the Oracle installation group. Ensure that the umask of your profile is set to 022. Otherwise, the installation might have permission problems and fail.
Windows	Administrator authority

Operating system

Authority required

AIX

Root user or nonroot user with the following permissions:

Member of the ibmcmgrp group
Read, write, and execute permission on the temp directory.
Read and write permissions on the IBMCMROOT directory (for example, the /opt/IBM/db2cmv8 directory).
Ownership and read, write, and execute permissions on the following directories:
- $IBMCMROOT/rme
- $IBMCMROOT/log/rme
- $IBMCMROOT/config/rme
- /home/ibmcmadm/log/
- /home/ibmcmadm/log/rme
- /tmp/IBMCM
- /tmp/RME
Ownership and read and write permissions on the following directories:
- $IBMCMROOT/lib
- $IBMCMROOT/bin
- $IBMCMROOT/log
- $IBMCMROOT/cmgmt
- $IBMCMROOT/firststeps
- $IBMCMROOT/config/base
- $IBMCMROOT/config/bin
- /home/ibmcmadm
Full permission on the WebSphere® Application Server profile.
For Oracle databases, read permission on the Oracle JDBC driver. For example, the nonroot user belongs to the Oracle installation group.

Ensure that the umask of your profile is set to 022. Otherwise, the installation might have permission problems and fail.

Windows

Administrator authority

Ensure that you install Content Manager Records Enabler on the same machine on which you installed IBM® DB2® Information Integrator for Content.

Prerequisites: Verifying environment variables; Gathering information that is required for the installation; Creating the Content Manager Records Enabler connection ID

To install Content Manager Records Enabler:

Disable the DB2 Content Manager deferred DDL execution feature.
Specific operations that are performed by the Content Manager Records Enabler installation and the records enablement of an item type in the Content Manager Records Enabler administration client will not work properly if the deferred DDL execution feature is enabled in DB2 Content Manager.

After you complete the installation, you can re-enable the deferred DDL execution feature in DB2 Content Manager.
Start WebSphere Application Server server1 by running the appropriate command for your operating system.

Operating system Command

AIX startServer.sh server1

Windows startserver server1

If WebSphere Application Server is not running, the Content Manager Records Enabler installation ends.
If you download the compressed package, extract the correct file to a temporary directory.

Operating system File name

AIX RMEInstall_aix-850.000.tar.gz

Windows RMEInstall_win-850.000.zip
For AIX, if you install Content Manager Records Enabler by using an X window session, enter the following command to export the display: export DISPLAY=hostname:0.0,, where hostname is the host name or IP address of the computer on which to view the installation panels.
From a command prompt, start the launchpad.

Operating system Command

AIX rme_launchpad.sh

Windows rme_launchpad.bat

If you installed DB2 Content Manager in a nonstandard location, the Java™ support found by the installation program might have problems communicating with IBM Records Manager. If you have problems, you can run the installation program directly by specifying the DB2 Content Manager JRE as follows:
For AIX

setup-cmre-8.5.00.exe -is:javahome $IBMCMROOT/java/jre

For Windows

setup-cmre-8.5.00.exe -is:javahome %IBMCMROOT%\java\jre
Follow the instructions in the installation windows. The installation program requires that the Content Manager Records Enabler server is installed into a separate WebSphere Application Server that is created during the installation. Do not specify a server name that was already created in the WebSphere Application Server installation.

Operating system	Command
AIX	`startServer.sh server1`
Windows	`startserver server1`

Operating system	File name
AIX	RMEInstall_aix-850.000.tar.gz
Windows	RMEInstall_win-850.000.zip

Operating system	Command
AIX	`rme_launchpad.sh`
Windows	`rme_launchpad.bat`

Content Manager Records Enabler is installed in the DB2 Information Integrator for Content directory. The IBMCMROOT environment variable points to the DB2 Information Integrator for Content directory. Do not change this value.