IBM Quick Deployer change default DB2 database parameters

Authors: ThomasPiccoli, KennethThomson, JenniferLiu, KenTessier, ClareCarty
Build basis: CLM 6.0, CLM 6.0.x, CE 6.0.x

The values contained in the default database parameters are used to configure the connections between the installed CLM applications and their individual databases. If you are going to use the Quick Deployer installed DB2 database then there is no need to change them prior to running the UCD application Install Applications process. However, you should have your database administrator review the configuration to make sure it conforms to internal security and reliability policies.

If you are going to use an existing DB2 database instance then you need to ensure that the default database parameters are updated to match the configuration used by your database instance. To do this follow the instructions in this topic.

Change default database parameters

1. Open application Rational_QD_60x, click Environments, then click the Request Process icon for the target environment.
   
   
   
   
2. In the Process field, select Change Default DB2 Parameters.
   
   
   
   
3. If you fixed the component versions on the process you will not be prompted to choose versions. If offered to choose the component versions, then select Latest Available.
   
   
   
   
4. Modify the process property default values to match your database.
   
   The DB2 databases are created using this command db2 CREATE DATABASE ${app}DBName $create{app}DBOption which is populated using these property values:
   
   eg db2 CREATE DATABASE $jtsDBName $createjtsDBOption
   
   The properties are as follows
   • createjtsDBOption : command options for creating the jts database
     Default : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 16384"
   • jtsDBName : name of the jts database
     Default : jtsDB
   • createdwDBOption : command options for creating the datawarehouse database
     Default : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 16384"
   • dwDBName : name of the datawarehouse database
     Default : dwDB
   • createccmDBOption : command options for creating the ccm database
     Default : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 16384"
   • ccmDBName : name of the ccm database
     Default : ccmDB
   • createqmDBOption : command options for creating the qm database
     Default : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 16384"
   • qmDBName : name of the qm database
     Default : qmDB
   • creatermDBOption : command options for creating the rm database
     Default : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 16384"
   • rmDBName : name of the rm database
     Default : rmDB
   • creategcDBOption : command options for creating the gc database
     Default : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 16384"
   • gcDBName : name of the gc database
     Default : gcDB
   • createdccDBOption : command options for creating the dcc database
     Default : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 16384"
   • dccDBName : name of the dcc database
     Default : dccDB
   • createrelmDBOption : command options for creating the relm database
     Default : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 16384"
   • relmDBName : name of the relm database
     Default : relmDB
   • createlqeDBOption : command options for creating the lqe database
     Default : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 32768"
   • lqeDBName : name of the lqe database
     Default : lqeDB
   • createldxDBOption : command options for creating the ldx database
     Default : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 32768"
   • ldxDBName : name of the ldx database
     Default : ldxDB
   • DB2InstancePort : database connection port
     Default : 50001
     
     
5. Click on Submit and wait for the process to run to completion
   
   
   
   

Miscellaneous

Notes:

• Throughout the IBM Quick Deployer wiki the screen captures are for reference only.
  In some cases if the functionality they display has not changed in the latest release they will be from a previous release

Related topics:

• Quick Deployer
• Quick Deployer setup and run

External links:

• Collaborative Lifecycle Management
• Continuous Engineering
• UrbanCode Deploy

Additional contributors: MichelleCrane, NathanBak, ChristianLopez