Process Automation

On CCMDB 7.2.1 it is possible to configure Context Menu Service to launch CI and Actual CI data from TADDM 7.2.1.

During CCMDB 7.2.1 installation in the panel "Data Integration Services and Context Menu Service Deployment Option", choose the 1st option: Deploy data integration and context menu services into the same database that you created for the product

On CCMDB 7.2.1, confirm that the hostname of TADDM server is configured on System Properties.

Install CMS Integration PSI Package: cci_cms_lic_7.2.1.0.zip. This package comes with CCMDB 7.2.1 product.

Installation instructions (MXServer must be stopped):

1 - Launch the PSI Installer: \ibm\SMP\bin\solutionInstallerGUI.bat

2 - Click Next on the "Introduction" Panel

3 - Click the Choose button to select the PSI installable package

4 - Select cci_cms_lic_7.2.1.0.zip from \ibm\SMP\pmp

5- Click the Open button and Next. Package should pass the validation process

6 - Click Next

Or install it using command line: solutionInstaller -action install -pkgpath c:\ibm\SMP\pmp\cci_cms_lic_7.2.1.0.zip -dbpwd dbpwd -dbuser dbuser -wasuser wasuser -waspwd waspwd -wasrxauser wasrxauser -wasrxapwd wasrxapwd

If you have any CCMDB fixpack installed, also install the cms package that comes with the fixpack. For instance, if you have CCMDB 7.2.1.3 installed, you need to install cci_cms_lic_7.2.1.3.zip package. Note: On CCMDB 7.2.1.1 you will need to apply CCMDB 7.2.1.1 IF001 to have this package installed.

On CCMDB environment you should have CITypes and Actual CIs imported from TADDM. Using DW, create promotion scope and promote CIs.

From TADDM 7.2.1 machine, register CMS (this will not impact the TADDM):

Go to \ibm\taddm\dist\etc and edit collation.properties file

- If the CCMDB database is installed on DB2, edit the parameters:

#===============================

# DIS/CMS Integration properties

#===============================

com.ibm.cdb.DisCmsIntegration.enabled=true

# User name

com.ibm.cdb.DisCmsIntegration.dbUser=maximodbuser

# User password

com.ibm.cdb.DisCmsIntegration.dbPassword=password

# JDBC URL of db to use

com.ibm.cdb.DisCmsIntegration.dbUrl=jdbc:db2://hostname:portnumber/dbname

# JDBC driver. Jar file containing it needs to be present in collation deploy dir

com.ibm.cdb.DisCmsIntegration.dbDriver=com.ibm.db2.jcc.DB2Driver

- If the CCMDB database is installed on Oracle, edit the parameters like:

#===============================

# DIS/CMS Integration properties

#===============================

com.ibm.cdb.DisCmsIntegration.enabled=true

# User name

com.ibm.cdb.DisCmsIntegration.dbUser=maximodbuser

# User password

com.ibm.cdb.DisCmsIntegration.dbPassword=dbpassword

# JDBC URL of db to use

com.ibm.cdb.DisCmsIntegration.dbUrl=jdbc:oracle:thin:@hostname:portnumber:dbname

# JDBC driver. Jar file containing it needs to be present in collation deploy dir

com.ibm.cdb.DisCmsIntegration.dbDriver=oracle.jdbc.driver.OracleDriver

Open a command prompt on TADDM machine, go to \ibm\taddm\dist\bin, and execute the command: run_cms_dis_registration.bat re-register-all

Note: If you are registering the CMS in the CCMDB with Oracle, make sure that the file oracle-jdbc-9.2.jar is at \ibm\taddm\dist\lib\jdbc. If not, find this oracle-jdbc-9.2.jar in your TADDM machine, and copy it to this directory.

Now there will be two new options on Select Action menu on CI and Actual CI applications that will launch data from TADDM:

- View Change History Report

- View Details Panel

On Actual CI application, select one top level Actual CI, and go to Select Action menu:

 

 

 

 

 

 

 

 

On CI application, select one top level CI, and go to Select Action menu: