(r18) IBMQuickDeployerChangeDefaultDB2ParametersOld < Deployment

Engineering Lifecycle Management Wiki - Deployment

Community information and contribution guidelines

~~EditAttach~~Printable

TWiki > Deployment Web > RwattsSandbox > DeploymentInstallingUpgradingAndMigrating > IBMQuickDeployer > IBMQuickDeployerSetupAndRun > IBMQuickDeployerChangeDefaultDB2ParametersOld

Revision 18 - 2016-12-10 - 19:35:45 - Main.ktessier

<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%">
---+!! IBM Quick Deployer change default DB2 database parameters <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/uc.png" alt="uc.png" width="50" height="50" align="right"> 
%DKGRAY%
%INCLUDE{"IBMQuickDeployerInsertAuthorBuildBasis"}%
%ENDCOLOR%</div></sticky>

<!-- Page contents top of page on right hand side in box -->
<sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;">
%TOC{title="Page contents"}%
</div></sticky>

<sticky><div style="margin:15px;"></sticky>
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. <br/><br/>
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.  
   <br/><br/><img src="%ATTACHURLPATH%/change-db-parameters.png" alt="run process"><br/><br/>
   1. In the Process field, select *Change Default DB2 Parameters*.
   <br/><br/><img src="%ATTACHURLPATH%/change-db2-parameters.png" alt="change parameters"><br/><br/>
   1. 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.
   <br/><br/><img src="%ATTACHURLPATH%/CDDP2.png" alt="choose version"><br/><br/>
   1. Modify the process property default values to match your database.
   <br/><br/> The DB2 databases are created using this command *db2 CREATE DATABASE ${app}DBName $create{app}DBOption* which is populated using these property values:
   <br/><br/>  eg db2 CREATE DATABASE *$jtsDBName $createjtsDBOption*
   <br/><br/> The properties are as follows
      * *createjtsDBOption* : command options for creating the jts database
      <br/> _Default_ : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 16384"
      * *jtsDBName* : name of the jts database
      <br/> _Default_ : jtsDB
      * *createdwDBOption* : command options for creating the datawarehouse database
      <br/> _Default_ : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 16384"
      * *dwDBName* : name of the datawarehouse database
      <br/> _Default_ : dwDB
      * *createccmDBOption* : command options for creating the ccm database
      <br/> _Default_ : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 16384"
      * *ccmDBName* : name of the ccm database
      <br/> _Default_ : ccmDB
      * *createqmDBOption* : command options for creating the qm database
      <br/> _Default_ : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 16384"
      * *qmDBName* : name of the qm database
      <br/> _Default_ : qmDB
      * *creatermDBOption* : command options for creating the rm database
      <br/> _Default_ : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 16384"
      * *rmDBName* : name of the rm database
      <br/> _Default_ : rmDB
      * *creategcDBOption* : command options for creating the gc database
      <br/> _Default_ : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 16384"
      * *gcDBName* : name of the gc database
      <br/> _Default_ : gcDB
      * *createdccDBOption* : command options for creating the dcc database
      <br/> _Default_ : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 16384"
      * *dccDBName* : name of the dcc database
      <br/> _Default_ : dccDB
      * *createrelmDBOption* : command options for creating the relm database
      <br/> _Default_ : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 16384"
      * *relmDBName* : name of the relm database
      <br/> _Default_ : relmDB
      * *createlqeDBOption* : command options for creating the lqe database
      <br/> _Default_ : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 32768"
      * *lqeDBName* : name of the lqe database
      <br/> _Default_ : lqeDB
      * *createldxDBOption* : command options for creating the ldx database
      <br/> _Default_ : "ON '/db2fs' DBPATH ON '/db2fs' USING CODESET UTF-8 TERRITORY EN PAGESIZE 32768"
      * *ldxDBName* : name of the ldx database
      <br/> _Default_ : ldxDB
      * *DB2InstancePort* : database connection port
      <br/> _Default_ : 50001
      <br/><br/>
   1. Click on *Submit* and wait for the process to run to completion
   <br/><br/><img src="%ATTACHURLPATH%/CDDP3.png" alt="wait for completion"><br/><br/>

%INCLUDE{"IBMQuickDeployerInsertMiscellaneous"}%

<sticky></div></sticky>

Deployment.IBMQuickDeployerChangeDefaultDBParameters moved from Deployment.IBMQuickDeployerChangeDefaultDbParameters on 2015-10-02 - 14:33 by Main.tomp

Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.