If the databases of the Libary Server and Resource Manager are installed in different DB2 instances, but on the same server host, you should catalog the Library Server database within the instance of the Resource Manager, to enable the Resource Manager to access the Library Server database. The Resource Manager needs to access the Libary Server database to validate any security tokens, the Library Server creates when people import or retreive any documents from the Resource Manager.
In the next procedure, the following texts need to be updated to your own situation:
- instance_name_resource_manager -> Name of the instance of the Resource Manager.
- hostname -> The short hostname of your server.
- resource_manager_database -> The name of the Resource Manager database.
- resource_manager_instance_owner -> The owner/userid of the Resource Manager instance.
- library_server_database -> The name of the Library Server database.
- instance_name_library_server -> Name of the instance of the Library Server.
- library_server_instance_owner -> The owner/userid of the Library Server instance.
- Log in as the database instance owner of the Resource Manager.
- Open or create the sqllib/profile.env file and add the following lines, to enable TCP/IP communication and the automatic restart:
DB2ENVLIST='EXTSHM'
DB2COMM='tcpip'
DB2AUTOSTART='TRUE' - Open or create the sqllib/userprofile file and add the following lines:
ICMROOT=/usr/lpp/icm
ICMDLL=/home/db2fenc1
ICMCOMP=/usr/vacpp/bin
CMCOMMON=/usr/lpp/cmb/cmgmt
EXTSHM=ON
PATH=$PATH:$ICMROOT/bin/DB2
LIBPATH=$ICMROOT/lib:$ICMROOT/inso:$LIBPATH
export ICMROOT ICMDLL ICMCOMP CMCOMMON EXTSHM PATH LIBPATH - Log off.
- Log in as the database instance owner of the Library Server.
- Open or create the sqllib/profile.env file and add the following lines, to enable TCP/IP communication and the automatic restart:
DB2ENVLIST='LIBPATH IMCROOT ICMDLL ICMCOMP EXTSHM CMCOMMON'
DB2COMM='tcpip'
DB2AUTOSTART='TRUE' - Open or create the sqllib/userprofile file and add the following lines:
ICMROOT=/usr/lpp/icm
ICMDLL=/home/db2fenc1
ICMCOMP=/usr/vacpp/bin
CMCOMMON=/usr/lpp/cmb/cmgmt
EXTSHM=ON
PATH=$PATH:$ICMROOT/bin/DB
LIBPATH=$ICMROOT/lib:$ICMROOT/inso:$LIBPATH
export ICMROOT ICMDLL ICMCOMP CMCOMMON EXTSHM PATH LIBPATH - Catalog the Resource Manager database instance:
db2 catalog local node instance_name instance instance_name system
ostype aix - Refresh the database directory cache:
db2 terminate
- Catalog the Resource Manager database in the system database directory:
db2 catalog db resource_manager_database at node instance_name_resource_manager
- Refresh the database directory cache:
db2 terminate
- Try to connect to the Resource Manager database:
db2 connect to resource_manager_database user resource_manager_instance_owner
- Disconnect the connection:
db2 terminate
- Log off.
Perform te following steps on the Resource Manager machine with the Resource Manager instance owner:
- Log in as the Resource Manager instance owner.
- Catalog the Resource Manager database instance:
db2 catalog local node instance_name_resource_manager instance instance_name_resource_manager system
ostype aix - Catalog the Library Server database in the system database directory:
db2 catalog db library_server_database at node instance_name_library_server
- Refresh the database directory cache:
db2 terminate
- Try to connect to the Library Server database:
db2 connect to library_server-database user library_serveR_instance_owner
- Disconnect the connection:
db2 terminate
- Log off.
- Log in as the Library Server instance owner.
db2 catalog tcpip node CMCDB2 remote hostname server db2c_library_server_instance
- Log off.
- Log in as the Resource Manager instance owner.
db2 catalog tcpip node CMCDB2 remote hostname server db2c_resource_manager_instance
- Log off.
- Log in as root and modify /etc/services:
db2c_library_server_instance 50000/tcp
db2c_resource_manager_instance 50001/tcp
db2 list database directoryThen connect to both databases.
If you found this useful, here's more on the same topic(s) in our blog:
- Starting and stopping Content Manager On Demand
- Image quality in the eClient
- ICM process check
- IBM Content Manager links
- Cataloging a Content Manager database on a Windows client
UNIX Health Check delivers software to scan Linux and AIX systems for potential issues. Run our software on your system, and receive a report in just a few minutes. UNIX Health Check is an automated check list. It will report on perfomance, capacity, stability and security issues. It will alert on configurations that can be improved per best practices, or items that should be improved per audit guidelines. A report will be generated in the format you wish, and the report includes the issues discovered and information on how to solve the issues as well.
Interested in learning more?
Interested in learning more?