Follow these steps to manually configure a DB2® database for the Context Menu Service (CMS)
and Data Integration Service (DIS).
Before you begin
You must install the DB2 database
software on the database server.
About this task
You can optionally specify that the CMS and DIS configuration
be completed automatically during the TADDM installation process.
Follow these steps if you did not use this option and need to manually
configure the database after installation.
Procedure
To prepare a DB2 database
for CMS and DIS:
- Optional: If you want to use a new DB2 instance for the TADDM database,
use the db2icrt command to create the DB2 instance.
Typically, the primary DB2 database user ID is the instance
owner (db2inst1 on Linux and UNIX systems, or db2admin on Windows systems). This database
user ID is created during the DB2 installation.
If you want to use the existing DB2 instance
for the TADDM database, skip this step.
Refer to the DB2 documentation for more information
about the db2icrt command.
- From the product DVD, copy the support/cmsdis/cmsdis.zip file
to the system where the DB2 database
is installed.
- Use one of the following procedures to run the make_db2_cms_dis script
on the system where the DB2 database
is installed:
- For Linux and UNIX systems:
- Log in as the DB2 database
instance owner. Use the db2inst1 ID.
- Extract the contents of the cmsdis.zip file.
- Navigate to the cmsdis directory.
- At a command prompt, run the following command:
make_db2_cms_dis.sh -d db_name db_user db_password
where: - db_name
- The database name. The database name for CMS and DIS must be different
from the TADDM database name.
- db_user
- The database instance user ID.
- db_password
- The password for the database instance user ID.
- For Windows systems:
- Open the DB2CMD command prompt.
- Extract the contents of the cmsdis.zip file.
- Navigate to the cmsdis directory.
- At a command prompt, run the following command:
make_db2_cms_dis.bat -d db_name db_user db_password
where:- db_name
- The database name. The database name for CMS and DIS must be different
from the TADDM database name.
- db_user
- The database instance user ID.
- db_password
- The password for the database instance user ID.
Check the standard output for any errors resulting
from the make_db2_cms_dis script.
- Set the following configuration parameters in the $COLLATION_HOME/etc/collation.properties file:
com.ibm.cdb.DisCmsIntegration.enabled=true
com.ibm.cdb.DisCmsIntegration.dbUser=db2_instance_userid
com.ibm.cdb.DisCmsIntegration.dbPassword=db2_instance_password
com.ibm.cdb.DisCmsIntegration.dbUrl=jdbc:db2://db2_hostname:db2_port/db2_name
com.ibm.cdb.DisCmsIntegration.dbDriver=com.ibm.db2.jcc.DB2Driver
where:
- db2_instance_userid
- The user ID of the DB2 instance
owner.
- db2_instance_password
- The password for the DB2 instance
owner user ID.
- db2_hostname
- The host name of the DB2 server.
- db2_port
- The DB2 port on the server.
- db2_name
- The DB2 instance name.