IBM Content Manager, Version 8.5 Platform: Oracle

Configuring the tnsnames.ora file for a dedicated Content Manager EE Oracle listener

View the tnsnames_ecm.ora template file to create a new tnsnames entry that is exclusive to Content Manager EE. If you plan to install the library server and resource manager on separate machines, then create one tsnames entry on the library server and one tsnames entry on the resource manager.

Requirement: See your new listener entry to complete this task.

Complete the following steps to create a new tnsnames entry that is exclusive to Content Manager EE:

Copy the templates from the Content Manager EE directory AdvSetup/Oracle to ORACLE_HOME/assistants/dbca/templates.
In the ORACLE_HOME/assistants/dbca/templates directory, view tnsnames_ecm.ora in a text editor.
Recommendation: View these listener templates in read-only mode so that you can see them again if you need to re-create the tnsnames.ora file.
Append all uncommented lines in the tnsnames template to the tnsnames.ora file, located in your ORACLE_HOME/network/admin or TNS_ADMIN directory, that you intend to use with the Content Manager EE repositories. These lines specify that the new listener spawn extproc processes for the library server.
Using the comments for guidance, replace the %<name>% text strings with your own values. The values that you specify here must be consistent with the values that you chose for listener.ora.
Attention: The extproc KEY and SID must exactly match the values (Key, SID_NAME respectively) that you set in listener.ora.
Tips to remember:
- Oracle treats all values as case-sensitive, even on Windows platforms.
- Do not use any environment variables. Paths must be fully qualified.
- For 64-bit Oracle installations on Linux, AIX®, or Solaris, verify that ORACLE_HOME/lib32 precedes ORACLE_HOME/lib. Otherwise, the library server configuration will fail because it runs as a 32-bit application.
Define an alias for the new listener in the tnsnames.ora file. Complete the following line to the tnsnames.ora file, where %FULL_HOSTNAME% represents your fully qualified host name and %LISTENER_PORT% represents the Oracle listener port that you defined in the listener.ora file.
```
LISTENER_ECM =
   (ADDRESS=(PROTOCOL=TCP)(HOST=%FULL_HOSTNAME%)(PORT=%LISTENER_PORT%))
```
For every Content Manager EE repository that will use the new listener, make sure that the port in your tnsnames entry matches the port of this new listener. For example, if you previously had a tnsnames entry for a library server with an entry named ICMNLSDB and the new listener will use port 1522, then make sure that the PORT name-value pair uses the value 1522.
Important: Whenever you change the Oracle listener port for a Content Manager EE repository, then you must change the corresponding port information in the configuration files for that repository. Otherwise, the Content Manager EE configuration and administration will fail. For example, if you change the listener port for the Content Manager EE resource manager, then you must change the corresponding information in the following places:
- The WebSphere® Application Server port for the resource manager
- The resource manager server definition properties in the system administration client
- The Oracle tnsnames entry port value for the corresponding resource manager instance.
Save your changes to the tnsnames.ora file and exit.

The following lines show what the modified tnsnames.ora for a library server must look like:

LISTENER_ECM =
   (ADDRESS = (PROTOCOL = TCP)(HOST = myhost.mydomain.com)(PORT = 1522))

EXTPROC_CONNECTION_DATA =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = IPC)(KEY = ICMLSEXTPROC))
    )
    (CONNECT_DATA =
      (SID = ICMLSExtProc)

The following lines show what the modified tnsnames.ora file for a resource manager must look like:

LISTENER_ECM =
   (ADDRESS = (PROTOCOL = TCP)(HOST = myhost.mydomain.com)(PORT = 1522))

Feedback