Offline Mediation Controller Post-Installation Tasks

Post-Installation Tasks

After installing Offline Mediation Controller, perform the following post-installation tasks:

Set the JAVA_HOME environment variable. For more information, see "Setting the JAVA_HOME Environment Variable".
Add the Offline Mediation Controller service to the system startup scripts. For more information, see "Adding Offline Mediation Controller Service to System Startup".
(Optional) Create certificates to use secure communication between Offline Mediation Controller components. For more information, see "Enabling Secure Communication Using Certificates".
Install the JDBC library. For more information, see "Installing the JDBC Library".

Setting the JAVA_HOME Environment Variable

You must set the JAVA_HOME environment variable to the latest version of JRE certified with Offline Mediation Controller before running any Offline Mediation Controller components. For more information, see "Additional Offline Mediation Controller Software Requirements" in Offline Mediation Controller Compatibility Matrix.

To set the JAVA_HOME environment variable on the Linux system on which Offline Mediation Controller is installed:

Stop all Offline Mediation Controller components and all Java processes.

For more information, see "Starting and Stopping Offline Mediation Controller" in Offline Mediation Controller System Administrator's Guide.
Copy the JDK_home/lib/tools.jar file to the JRE_home/lib directory.

where:
- JDK_home is the directory in which the latest version of JDK certified with Offline Mediation Controller is installed.
- JRE_home is the directory in which the latest version of JRE certified with Offline Mediation Controller is installed.
Set the JAVA_HOME environment variable to the latest version of JRE certified with Offline Mediation Controller.

For example, in C shell, do the following:
1. Open the .cshrc file in a text editor.
2. Add or modify the following entries:
```
setenv JAVA_HOME JRE_home
setenv PATH ${JAVA_HOME}:${PATH}
```
3. Save and close the file.
4. Update the environment by running the following command:
```
source .cshrc
```

To set the JAVA_HOME environment variable on the Windows system on which Administration Client is installed:

Close Administration Client.
Copy the JDK_home\lib\tools.jar file to the JRE_home\lib directory.
Open the OMC_home\bin\UDCEnvironment.bat file in a text editor, where OMC_home is the directory in which Offline Mediation Controller is installed.
Search for the following entry:
```
set JAVA_HOME=%UDC_HOME%\jre
```

Change this entry to:

set JAVA_HOME=JRE_home

For example:

set JAVA_HOME= C:\Program Files\Java\jre7

Save and close the file.

Adding Offline Mediation Controller Service to System Startup

After installing Offline Mediation Controller, run the configure script to add the Offline Mediation Controller service to the system startup scripts in the /etc/init.d/ directory.

To add the Offline Mediation Controller service to the system startup scripts:

Log on as root to the system on which Offline Mediation Controller is installed.
Set the JAVA_HOME environment variable to the latest version of JRE certified with Offline Mediation Controller. For more information, see "Additional Offline Mediation Controller Software Requirements" in Offline Mediation Controller Compatibility Matrix.

For example, in C shell, do the following:
1. Open the .cshrc file in a text editor.
2. Add or modify the following entries:
```
setenv JAVA_HOME JRE_home
setenv PATH ${JAVA_HOME}:${PATH}
```
3. Save and close the file.
4. Update the environment by running the following command:
```
source .cshrc
```
Go to the OMC_home/bin directory, where OMC_home is the directory in which Offline Mediation Controller is installed.
Run the following command:
```
./configure OMC_home
```
The configurations required to run Offline Mediation Controller are performed.
Start all Offline Mediation Controller components.

Enabling Secure Communication Using Certificates

To enable secure communication between the Offline Mediation Controller components, create trusted certification authority (CA) certificates for Administration Server and Node Manager. For more information, see the discussion about secure communication using secure sockets layer (SSL) in Offline Mediation Controller System Administrator's Guide.

Note:

You must create the CA certificates after installing and before starting the Offline Mediation Controller components.

Creating the Administration Server's Certificate

Administration Server has its own certificate in a secure keystore. This certificate has a private and a public key pair. Administration Server shares the certificate containing only the public key with all its known Administration Clients. Administration Client adds the server's certificate to its truststore, indicating that Administration Server is added to the trusted list.

To create the Administration Server's certificate:

Log on to the system on which Offline Mediation Controller is installed.
Go to the OMC_home/bin directory.
Run the following command:
```
./createAdminSvrCert
```
The Enter keystore password prompt appears.
Enter the keystore password.

The Re-enter new password prompt appears.
Re-enter the keystore password.
You are prompted to enter the following information:
- First and last name
- Organizational unit
- Organization
- City or locality
- State or province
- Two-letter country code
The information confirmation prompt appears.
Enter y, which confirms the information.

The Enter key password for <adminServer> prompt appears.
Leave the key password blank and press Enter. The keystore password is used for the key password. Note the key password because this is required to access the keystore entry containing the key.

The key pair for Administration Server is created, and the Enter keystore password prompt appears.
Enter the keystore password.

The certificate is created and stored in the OMC_home/config/adminserver/adminServer.cer file.

The Enter keystore password prompt appears.
Enter the Administration Client's keystore (truststore) password.

The Re-enter new password prompt appears.
Re-enter the Administration Client's keystore password.

The Trust this certificate prompt appears.
Enter y, which trusts the certificate.

Note:

If you enter n, you must manually import the Administration Server's public certificate into the Administration Client's truststore. For more information, see "Manually Importing Administration Server's Public Certificate into Administration Client's Truststore".

The Administrator Server certificate is created and added to keystore, and the public certificate is imported to the Administration Client's truststore.

Manually Importing Administration Server's Public Certificate into Administration Client's Truststore

To manually import the Administration Server's public certificate into the Administration Client's truststore:

Log on to the system on which Offline Mediation Controller is installed.

Run the following command:

OMC_home/jre/bin/keytool -import -v -trustcacerts -alias adminServer -file OMC_home/config/adminserver/adminServer.cer -keystore OMC_home/config/GUI/adminClientTruststore.jks

The Enter keystore password prompt appears.

Enter the Administration Client's keystore (truststore) password.

The Trust this certificate prompt appears.
Enter y, which trusts the certificate.

The Administration Server's public certificate is imported to the Administration Server's truststore.

Encoding the Administration Server's Keystore Password

When secure communication is enabled, you must manually encode the Administration Server's keystore password and store the encoded password in a configuration file. Offline Mediation Controller uses the configuration file to run the Administration Server daemon.

To encode the Administration Server's keystore password:

Log on to the system on which Offline Mediation Controller is installed.
Go to the OMC_home/bin directory and run the following command:
```
./encode keystore_password
```
where keystore_password is the Administration Server's keystore password.

The command window displays keystore_password in encoded form. For example:
```
72,-46,62,71,41,-115,14,-68,-34,-4,-105,-113,-125,1,-18,-70
```
Copy the encoded password.
Open the OMC_home/config/adminserver/ASkeystore.cfg file in a text editor.
Find the following entry:
```
KEYSTORE_PASSWORD= value
```
If the file does not have this entry, add it.
Replace value with the copied encoded password.
Save and close the file.

Creating the Node Manager's Certificate

Node Manager has its own certificate in a secure keystore. This certificate has a private and a public key pair. Node Manager shares the certificate containing only the public key with Administration Server. Administration Server adds the Node Manager's certificate to its truststore.

To create the Node Manager's certificate:

Log on to the system on which Offline Mediation Controller is installed.
Go to the OMC_home/bin directory.
Run the following command:
```
./createNodeMgrCert
```
The Enter keystore password prompt appears.
Enter the keystore password.

The Re-enter new password prompt appears.
Re-enter the keystore password.

You are prompted to enter the following information:
- First and last name
- Organizational unit
- Organization
- City or locality
- State or province
- Two-letter country code
The information confirmation prompt appears.
Enter y, which confirms the information.

The Enter key password for <nodeManager> prompt appears.
Leave the key password blank and press Enter. The keystore password is used for the key password. Note the key password because this is required to access the keystore entry containing the key.

The key pair for Node Manager is created, and the Enter keystore password prompt appears.
Enter the keystore password.

The certificate is created and stored in the OMC_home/config/nodemgr/nodeManager.cer file.

The Enter keystore password prompt appears.
Enter the Administration Server's keystore (truststore) password.

The Re-enter new password prompt appears.
Re-enter the Administration Server's keystore password.

The Trust this certificate prompt appears.
Enter y, which trusts the certificate.

Note:

If you enter n, you must manually import the Node Manager's certificate into the Administration Server's truststore. For more information, see "Manually Importing Node Manager's Public Certificate into Administration Server's Truststore".

The Node Manager's certificate is created and added to keystore, and the public certificate is imported to the Administration Server's truststore.

Manually Importing Node Manager's Public Certificate into Administration Server's Truststore

To manually import the Node Manager's public certificate into the Administration Server's truststore:

Log on to the system on which Offline Mediation Controller is installed.

Run the following command:

OMC_home/jre/bin/keytool -import -v -trustcacerts -alias nodeManager -file OMC_home/config/nodemgr/nodeManager.cer -keystore OMC_home/config/adminserver/adminServerTuststore.jks

The Enter keystore password prompt appears.

Enter the Administration Server's keystore (truststore) password.

The Trust this certificate prompt appears.
Enter y, which trusts the certificate.

The Node Manager's public certificate is imported to the Administration Server's truststore.

Encoding the Node Manager's Keystore Password

When secure communication is enabled, you must encode the Node Manager's keystore password and store the encoded password in a configuration file. Offline Mediation Controller uses the configuration file to run the Node Manager daemon.

To encode the Node Manager's keystore password:

Log on to the system on which Offline Mediation Controller is installed.
Go to the OMC_home/bin directory and run the following command:
```
./encode keystore_password
```
where keystore_password is the Node Manager's keystore password.

The command window displays keystore_password in encoded form. For example:
```
72,-46,62,71,41,-115,14,-68,-34,-4,-105,-113,-125,1,-18,-70
```
Copy the encoded password.
Open the OMC_home/config/nodemgr/NMkeystore.cfg file in a text editor.
Find the following entry:
```
KEYSTORE_PASSWORD= value
```
If the file does not have this entry, add it.
Replace value with the copied encoded password.
Save and close the file.

Installing the JDBC Library

Before using the cartridges that require JDBC, install the JDBC library for the installed Java version and the database into which you want to insert data.

To install the JDBC library:

Stop all Offline Mediation Controller components.
Go to the Oracle JDBC Drivers website:

https://www.oracle.com/database/technologies/appdev/jdbc.html
From the list of JDBC drivers, click the link for the database into which you want to insert data.

The JDBC Driver Downloads page appears.
Download the ojdbcversion.jar file to the OMC_home/3rdparty_jars directory, where version is the latest version of Java certified with Offline Mediation Controller.
Start all the Offline Mediation Controller components. For more information, see the discussion about starting and stopping Offline Mediation Controller in Offline Mediation Controller System Administrator's Guide.