Category Archives: SmartCloud Control Desk

Error starting Integration Composer

SmartCloud Control Desk comes bundled with IBM Tivoli Integration Composer. In case of SCCD version 7.5.3 , after installing ITIC it cannot be started.

If we run startFusion.sh , it stops with java.lang.ClassNotFoundException

Examining the script we see it calls init.sh, which has a property called FSNBUILD. This is the version number of SCCD – referring to the IntegrationComposer####.jar (located in the workarea directory)

In ver. 7.5.3, we have workarea/IntegrationComposer7530.jar file and in init.sh FSNBUILD=7510. Changing FSNBUILD to 7530 in init.sh script solves the problem.

Relocating SCCD database

Leave a reply

When we install SmartCloud Control Desk in a Unix/Linux box using middleware installer, it only asks for db instance user. (If we accept the default value, it’s ctginst1)

The installer then creates the user, and places the db in it’s home directory.

In lots of cases there is a dedicated filesystem to hold business critical data, ( and usually it’s not /home) so we have to move database to that location.

db2relocatedb is the tool to use. First, copy/move /home/ctginst1/ctginst1 directory to the new location (for eg.: /data/ctginst1 ), then create a config file for db2relocatedb. ( Keep in mind that we have to move tablespace containers as well )

so the command is:

db2relocatedb -f relocate.cfg

relocate.cfg is :

DB_NAME=maxdb75
DB_PATH=/home/ctginst1,/data/ctginst1
INSTANCE=ctginst1
STORAGE_PATH=/home//ctginst1/,/data/ctginst1/

(don’t forget, the instance should be stopped ! )

Integrating TADDM and Control Desk using Integration Composer

2 Replies

In this example we will use the Integration Composer to get CMDB data out from TADDM and populate that data into Control Desk’s CMDB. We are basically setting up data translation between TADDM and Control Desk’s CMDB.

We will have the following steps:

Create data source for TADDM CIType ( Configuration Item )
Create data source for TADDM Actual CI ( Configuration Item )
Create target data source for Control Desk CIType ( Configuration Item )
Create target data source for Control Desk Actual CI ( Configuration Item )
Create mappings between TADDM CIType and Control Desk CIType
Create mapping between TADDM Actual CI and TADDM Actual CI
Run executeMapping.sh on the CIType mapping to populate the Control Desk CIType database
Activate CIs Types on Control Desk
Run executeMapping.sh on the Actual CI mapping to populate the Control Desk Actual CI database

Before we start the procedure we will copy the taddm api files to the ./lib directory in the Integration Composer root directory.

scp platform-model.jar root@huctrldsk001-p1:/app/IBM/Integration_Composer/lib/
Password:
platform-model.jar 100% 16MB 16.2MB/s 00:00
scp taddm-api-client.jar root@huctrldsk001-p1:/app/IBM/Integration_Composer/lib/
Password:
taddm-api-client.jar
100% 117MB 39.1MB/s 00:03

Make sure that the JAVA_PATH variable is set correctly in the init.sh file. We used the java version that comes with the Control Desk installation.

# ===============
# SPECIFY THE JDK
# ===============
JAVA_HOME=/app/IBM/SMP/sdk/

Start the Integration Composer using the startFusion.sh command from ./bin directory of your Integration composer installation root.

HUCTRLDSK001-P1:/app/IBM/Integration_Composer/bin # ./startFusion.sh
09 Feb 2015 11:13:01:274 [INFO] IBM Tivoli Integration Composer 7.5.3.0 Build 201411111713 logger started. (This should only happen once.)
09 Feb 2015 11:13:01:276 [INFO] Java version: JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr10-20111207_96808 (JIT enabled, AOT enabled)
J9VM – 20111207_096808
JIT – r9_20111107_21307ifx1
GC – 20110519_AA
09 Feb 2015 11:13:01:276 [INFO] Java vendor: IBM Corporation
09 Feb 2015 11:13:01:345 [INFO] Mediator created. (This should only happen once.)

Create data source for TADDM CIType ( Configuration Item )

Click Define New Data Source on the Integration Composer Console.

Select TADDM75CIType from the data schemes, then click Next.

Specify the data source name then click Next.

Define your TADDM server connection details. Specify the hostname or ip address, TADDM port, username and password. Please note that TADDM Version 7.2.1 or earlier uses 9530 for host port. TADDM Version 7.2.2 or later uses 9433 port for host port.

Test the connection then click OK if the connection is successful. Please note that the User Name is case sensitive.

Click Finish to save the Data Source.

Create data source for TADDM Actual CI ( Configuration Item )

Click Define New Data Source on the Integration Composer Console.

Select TADDM75ActualCI from the data schemes, then click Next.

Specify the data source name then click Next.

Test the connection then click OK if the connection is successful. Please note that the User Name is case sensitive.

Click Finish to save the Data Source.

Create target data source for Control Desk CIType ( Configuration Item )

Click Define New Data Source on the Integration Composer Console.

Select CCMDB75CIType from the data schemes, then click Next.

Specify the data source name then click Next.

Specify your DB2 server connection details.

Test the database connection, then click OK once the connection is successful.

Click Finish to save the data source.

Create target data source for Control Desk Actual CI ( Configuration Item )

Click Define New Data Source on the Integration Composer Console.

Select CCMDB75ActualCI from the data schemes, then click Next.

Specify the data source name then click Next.

Specify your DB2 server connection details.

Test the database connection, then click OK once the connection is successful.

Click Finish to save the data source.

Create mappings between TADDM CIType and Control Desk CIType

Click Create New Mapping on the Integration Composer Console.

Select TADDM75CIType as Source then select CCMDB75CIType as Target. Name the mapping to TADDM-2-TUSC-CI-Types then click OK.

Click specify the Password then click Finish at the TADDM75CIType data source selection.

Click specify the Password then click Finish at the CCMDB75CIType data source selection.

Select Import from the upper Select Action menu.

Select TADDMToCIType75.fsn from the list then click Open.

Select Save from the upper Select Action menu.

Select Close from the upper Select Action menu then click Yes to close the mapping window.

Create mapping between TADDM Actual CI and TADDM Actual CI

Click Create New Mapping on the Integration Composer Console.

Select TADDM75ActualCI as Source then select CCMDB75ActualCI as Target. Name the mapping to TADDM-2-TUSC-Actual-CIs then click OK.

Click specify the Password then click Finish at the TADDM75ActualCI data source selection.

Click specify the Password then click Finish at the CCMDB75ActualCI data source selection.

Select Import from the upper Select Action menu.

Select TADDMtoActualCI75.fsn then click Open.

Select Save from the upper Select Action menu.

Select Close from the upper Select Action menu then click Yes to close the mapping window.

Run executeMapping.sh on the CIType mapping to populate the Control Desk CIType database

executeMapping.sh is located in ./bin directory of your Integration Composer root directory. Run the command with the following syntax:

./executeMapping.sh TADDM-2-TUSC-CI-Types maximo yourpassword administrator yourpassword maximo yourpassword

If the procedure completes successfully you should be seeing this:

09 Feb 2015 13:25:41:640 [INFO]
========================================================
Mapping execution completed
Mapping: TADDM-2-TUSC-CI-Types
Execution time: 00:46:28
Classifications created: 88
Records created: 109947
Records updated: 41808
Records deleted: 1583
Errors: 0

NRS GUIDs created: 0
NRS errors: 0
NRS records updated on Alternate Keys: 0
NRS records found as duplicate: 0
NRS records deleted because of duplicate: 0
NRS warnings due to duplicate data: 0
========================================================

Done
Mapping completed successfully.
Integration Composer has finished.

Activate CIs Types on Control Desk

It is important to point out here that you should only activate a very small number of CI Types at first then try to expand the list later on. We only enabled the Linux system specific Configuration Item Types such as:

SYS.LINUX.LINUXUNITARYCOMPUTERSYSTEM
SYS.UNITARYCOMPUTERSYSTEM
SYS.COMPUTERSYSTEM
SYS.LINUX.LINUX

You can Activate a CI by selecting it then clicking on the Change Status option in the left menu.

Run executeMapping.sh on the Actual CI mapping to populate the Control Desk Actual CI database

Prior to import the Actual Configuration items su over to ctginst1 and run the following command against your db2 database:

/app/ibm/db2/V9.7/bin/db2jdbcbind -url jdbc:db2://huctrldsk001-p1.ipm.local:50005/maxdb75 -user maximo -password yourpassword -size 15
Binder performing action “add” to “jdbc:db2://huctrldsk001-p1.ipm.local:50005/maxdb75” under collection “NULLID”:
Package “SYSSTAT”: Already exists (No need to bind).
Package “SYSSH100”: Already exists (No need to bind).
Package “SYSSH200”: Already exists (No need to bind).
Package “SYSSH300”: Already exists (No need to bind).
Package “SYSSH400”: Already exists (No need to bind).
Package “SYSSN100”: Already exists (No need to bind).
Package “SYSSN200”: Already exists (No need to bind).
Package “SYSSN300”: Already exists (No need to bind).
Package “SYSSN400”: Already exists (No need to bind).
Package “SYSSH101”: Already exists (No need to bind).
Package “SYSSH201”: Already exists (No need to bind).
Package “SYSSH301”: Already exists (No need to bind).
Package “SYSSH401”: Already exists (No need to bind).
Package “SYSSN101”: Already exists (No need to bind).
Package “SYSSN201”: Already exists (No need to bind).
Package “SYSSN301”: Already exists (No need to bind).
Package “SYSSN401”: Already exists (No need to bind).
Package “SYSSH102”: Already exists (No need to bind).
Package “SYSSH202”: Already exists (No need to bind).
Package “SYSSH302”: Already exists (No need to bind).
Package “SYSSH402”: Already exists (No need to bind).
Package “SYSSN102”: Already exists (No need to bind).
Package “SYSSN202”: Already exists (No need to bind).
Package “SYSSN302”: Already exists (No need to bind).
Package “SYSSN402”: Already exists (No need to bind).
Package “SYSLH100”: Already exists (No need to bind).
Package “SYSLH200”: Already exists (No need to bind).
Package “SYSLH300”: Already exists (No need to bind).
Package “SYSLH400”: Already exists (No need to bind).
Package “SYSLN100”: Already exists (No need to bind).
Package “SYSLN200”: Already exists (No need to bind).
Package “SYSLN300”: Already exists (No need to bind).
Package “SYSLN400”: Already exists (No need to bind).
Package “SYSLH101”: Already exists (No need to bind).
Package “SYSLH201”: Already exists (No need to bind).
Package “SYSLH301”: Already exists (No need to bind).
Package “SYSLH401”: Already exists (No need to bind).
Package “SYSLN101”: Already exists (No need to bind).
Package “SYSLN201”: Already exists (No need to bind).
Package “SYSLN301”: Already exists (No need to bind).
Package “SYSLN401”: Already exists (No need to bind).
Package “SYSLH102”: Already exists (No need to bind).
Package “SYSLH202”: Already exists (No need to bind).
Package “SYSLH302”: Already exists (No need to bind).
Package “SYSLH402”: Already exists (No need to bind).
Package “SYSLN102”: Already exists (No need to bind).
Package “SYSLN202”: Already exists (No need to bind).
Package “SYSLN302”: Already exists (No need to bind).
Package “SYSLN402”: Already exists (No need to bind).
Package “SYSLH103”: Bind succeeded.
Package “SYSLH203”: Bind succeeded.
Package “SYSLH303”: Bind succeeded.
Package “SYSLH403”: Bind succeeded.
Package “SYSLN103”: Bind succeeded.
Package “SYSLN203”: Bind succeeded.
Package “SYSLN303”: Bind succeeded.
Package “SYSLN403”: Bind succeeded.
Package “SYSLH104”: Bind succeeded.
Package “SYSLH204”: Bind succeeded.
Package “SYSLH304”: Bind succeeded.
Package “SYSLH404”: Bind succeeded.
Package “SYSLN104”: Bind succeeded.
Package “SYSLN204”: Bind succeeded.
Package “SYSLN304”: Bind succeeded.
Package “SYSLN404”: Bind succeeded.
Package “SYSLH105”: Bind succeeded.
Package “SYSLH205”: Bind succeeded.
Package “SYSLH305”: Bind succeeded.
Package “SYSLH405”: Bind succeeded.
Package “SYSLN105”: Bind succeeded.
Package “SYSLN205”: Bind succeeded.
Package “SYSLN305”: Bind succeeded.
Package “SYSLN405”: Bind succeeded.
Package “SYSLH106”: Bind succeeded.
Package “SYSLH206”: Bind succeeded.
Package “SYSLH306”: Bind succeeded.
Package “SYSLH406”: Bind succeeded.
Package “SYSLN106”: Bind succeeded.
Package “SYSLN206”: Bind succeeded.
Package “SYSLN306”: Bind succeeded.
Package “SYSLN406”: Bind succeeded.
Package “SYSLH107”: Bind succeeded.
Package “SYSLH207”: Bind succeeded.
Package “SYSLH307”: Bind succeeded.
Package “SYSLH407”: Bind succeeded.
Package “SYSLN107”: Bind succeeded.
Package “SYSLN207”: Bind succeeded.
Package “SYSLN307”: Bind succeeded.
Package “SYSLN407”: Bind succeeded.
Package “SYSLH108”: Bind succeeded.
Package “SYSLH208”: Bind succeeded.
Package “SYSLH308”: Bind succeeded.
Package “SYSLH408”: Bind succeeded.
Package “SYSLN108”: Bind succeeded.
Package “SYSLN208”: Bind succeeded.
Package “SYSLN308”: Bind succeeded.
Package “SYSLN408”: Bind succeeded.
Package “SYSLH109”: Bind succeeded.
Package “SYSLH209”: Bind succeeded.
Package “SYSLH309”: Bind succeeded.
Package “SYSLH409”: Bind succeeded.
Package “SYSLN109”: Bind succeeded.
Package “SYSLN209”: Bind succeeded.
Package “SYSLN309”: Bind succeeded.
Package “SYSLN409”: Bind succeeded.
Package “SYSLH10A”: Bind succeeded.
Package “SYSLH20A”: Bind succeeded.
Package “SYSLH30A”: Bind succeeded.
Package “SYSLH40A”: Bind succeeded.
Package “SYSLN10A”: Bind succeeded.
Package “SYSLN20A”: Bind succeeded.
Package “SYSLN30A”: Bind succeeded.
Package “SYSLN40A”: Bind succeeded.
Package “SYSLH10B”: Bind succeeded.
Package “SYSLH20B”: Bind succeeded.
Package “SYSLH30B”: Bind succeeded.
Package “SYSLH40B”: Bind succeeded.
Package “SYSLN10B”: Bind succeeded.
Package “SYSLN20B”: Bind succeeded.
Package “SYSLN30B”: Bind succeeded.
Package “SYSLN40B”: Bind succeeded.
Package “SYSLH10C”: Bind succeeded.
Package “SYSLH20C”: Bind succeeded.
Package “SYSLH30C”: Bind succeeded.
Package “SYSLH40C”: Bind succeeded.
Package “SYSLN10C”: Bind succeeded.
Package “SYSLN20C”: Bind succeeded.
Package “SYSLN30C”: Bind succeeded.
Package “SYSLN40C”: Bind succeeded.
Package “SYSLH10D”: Bind succeeded.
Package “SYSLH20D”: Bind succeeded.
Package “SYSLH30D”: Bind succeeded.
Package “SYSLH40D”: Bind succeeded.
Package “SYSLN10D”: Bind succeeded.
Package “SYSLN20D”: Bind succeeded.
Package “SYSLN30D”: Bind succeeded.
Package “SYSLN40D”: Bind succeeded.
Package “SYSLH10E”: Bind succeeded.
Package “SYSLH20E”: Bind succeeded.
Package “SYSLH30E”: Bind succeeded.
Package “SYSLH40E”: Bind succeeded.
Package “SYSLN10E”: Bind succeeded.
Package “SYSLN20E”: Bind succeeded.
Package “SYSLN30E”: Bind succeeded.
Package “SYSLN40E”: Bind succeeded.
DB2Binder finished.

Once that is done run the executeMapping.sh against the Actual CI mapping like this:

HUCTRLDSK001-P1:/app/IBM/Integration_Composer/bin # ./executeMapping.sh TADDM-2-TUSC-Actual-CIs maximo yourpassword administrator yourpassword maximo yourpassword
Integration Composer will now start.
IBM Tivoli Integration Composer 7.5.3.0 Build 201411111713
09 Feb 2015 13:35:55:371 [INFO] IBM Tivoli Integration Composer 7.5.3.0 Build 201411111713
Mapping: TADDM-2-TUSC-Actual-CIs
Creating data source Fusion… done
IBM Tivoli Integration Composer database version: V7507-40
Retrieving mapping definition TADDM-2-TUSC-Actual-CIs…        done
Creating source data source TADDM75ActualCI… done
Connecting to source data source TADDM75ActualCI…
09 Feb 2015 13:35:56:371 [INFO] ResourceManager : Loading resource file /app/IBM/Integration_Composer/data/properties/jdbcinfo.properties : 39 resource(s) loaded.
09 Feb 2015 13:35:56:992 [INFO] Collation version: 2.2, build: null, home: /app/IBM/Integration_Composer
09 Feb 2015 13:35:57:001 [INFO] TADDMActualCI._loadResources: TADDM global depth value set at 3
09 Feb 2015 13:35:57:001 [INFO] TADDMActualCI._loadResources: TADDM deleted GUIDs will not be logged; Actual CI deletion is disabled.
09 Feb 2015 13:35:57:002 [INFO] TADDMActualCI._loadResources: Authorized space filtering enabled.
09 Feb 2015 13:35:57:125 [INFO] AppServer Exclusions Filtering will be turned off. TADDM version is 7.3 or greater.
09 Feb 2015 13:35:57:125 [INFO] TADDMActualCI._loadResources: Relationships marked for deletion will only be deleted if ITIC processed both the target and source during this run.
09 Feb 2015 13:35:57:126 [INFO] …TADDMActualCI._loadResources: 10 threads will be used to gather TADDM data.
… … A maximum of 50 objects will be queued at one time.
Connecting to source data source TADDM75ActualCI…     done
Creating target data source CCMDB75ActualCI… done
Connecting to target data source CCMDB75ActualCI…
Connecting to target data source CCMDB75ActualCI…     done
Retrieving mapping expressions…       done
Retrieving mapping deciding classes… done
retrieving mapping expressions 44
finished mapping expressions 1
finished mapping expressions 2
finished mapping expressions 3
finished mapping expressions 4
finished mapping expressions 5
finished mapping expressions 6
finished mapping expressions 7
finished mapping expressions 8
finished mapping expressions 9
finished mapping expressions 10
finished mapping expressions 11
finished mapping expressions 12
finished mapping expressions 13
finished mapping expressions 14
finished mapping expressions 15
finished mapping expressions 16
finished mapping expressions 17
finished mapping expressions 18
finished mapping expressions 19
finished mapping expressions 20
finished mapping expressions 21
finished mapping expressions 22
finished mapping expressions 23
finished mapping expressions 24
finished mapping expressions 25
finished mapping expressions 26
finished mapping expressions 27
finished mapping expressions 28
finished mapping expressions 29
finished mapping expressions 30
finished mapping expressions 31
finished mapping expressions 32
finished mapping expressions 33
finished mapping expressions 34
finished mapping expressions 35
finished mapping expressions 36
finished mapping expressions 37
finished mapping expressions 38
finished mapping expressions 39
finished mapping expressions 40
finished mapping expressions 41
finished mapping expressions 42
finished mapping expressions 43
finished mapping expressions 44
done mapping expressions
translating mappings 6
finished mappings 1
finished mappings 2
finished mappings 3
finished mappings 4
finished mappings 5
finished mappings 6
done mappings
retrieving deciding classes 6
finished deciding classes 1
finished deciding classes 2
finished deciding classes 3
finished deciding classes 4
finished deciding classes 5
finished deciding classes 6
done deciding classes
generating source code 1
finished source code 1
done source code
generating target code 6
finished target code 1
finished target code 2
finished target code 3
finished target code 4
finished target code 5
finished target code 6
done target code
retrieving file names to compile 6
finished file name 1
finished file name 2
finished file name 3
finished file name 4
finished file name 5
finished file name 6
done file names
Compiling 11 files 11
finished compiling 1
finished compiling 2
finished compiling 3
finished compiling 4
finished compiling 5
finished compiling 6
finished compiling 7
finished compiling 8
finished compiling 9
finished compiling 10
finished compiling 11
done
REMOVELISTENER
09 Feb 2015 13:35:57:806 [INFO]
========================================================
Start mapping execution
Mapping: TADDM-2-TUSC-Actual-CIs
========================================================

09 Feb 2015 13:36:06:589 [INFO] TADDMActualCI.getClassificationDepthSetting():Classification SYS.LINUX.LINUX will be processed at depth level 1 because it is an active non-top-level classification
09 Feb 2015 13:36:07:059 [WARN]
09 Feb 2015 13:36:07:060 [WARN] The following top level classifications are in a promotion scope, but not activated. CIs with these classifications will only be imported from TADDM if they are related to other active, top-level CIs.
09 Feb 2015 13:36:07:060 [WARN]   SYS.BUSINESSSYSTEM
09 Feb 2015 13:36:07:060 [WARN]   APP.APPLICATION
09 Feb 2015 13:36:07:060 [WARN]   APP.SOFTWAREIMAGE
09 Feb 2015 13:36:07:060 [INFO]
09 Feb 2015 13:36:07:061 [INFO] Querying TADDM for CIs of the classifications that are active…
09 Feb 2015 13:36:07:061 [INFO]
09 Feb 2015 13:36:07:061 [INFO] All TADDM Guids for the active Classifications will be imported.
09 Feb 2015 13:36:07:140 [INFO] Retrieved 0 Authorized CIs for filtering.
09 Feb 2015 13:36:07:187 [INFO] TADDM contains 4 guids for the SYS.LINUX.LINUX classification.
09 Feb 2015 13:36:07:188 [INFO] The number of new and updated SYS.LINUX.LINUX GUIDs to process is 4. These will be processed at depth level 1.
09 Feb 2015 13:36:07:234 [INFO] TADDM contains 4 guids for the SYS.COMPUTERSYSTEM classification.
09 Feb 2015 13:36:07:234 [INFO] The number of new and updated SYS.COMPUTERSYSTEM GUIDs to process is 4. These will be processed at depth level 3.
09 Feb 2015 13:36:07:234 [INFO]   The following classifications will be processed as subclasses of SYS.COMPUTERSYSTEM at depth level 3.
09 Feb 2015 13:36:07:235 [INFO]     SYS.LINUX.LINUXUNITARYCOMPUTERSYSTEM
09 Feb 2015 13:36:07:235 [INFO]     SYS.UNITARYCOMPUTERSYSTEM
09 Feb 2015 13:36:07:235 [INFO]
09 Feb 2015 13:36:07:236 [INFO] The total number of active Guids to process is: 8
Actual CI: 3EA8E707D644308A8A3CFB967DB7F726
09 Feb 2015 13:36:11:389 [INFO] NRS initialized.
09 Feb 2015 13:36:11:409 [INFO] MaxSequenceProvider created. (This should only happen once.)
Actual CI: 021E523A62B73A9E9A9017CFCE0DECEA
Actual CI: 9EBC5B2280883ECFA71F03DDB8CA4366
Actual CI: 151EAA4AD64A3E73938800BE3164BEE6
Actual CI: 5867ECDB40603FEDA8ADFAAA9C257300
Actual CI: 021E523A62B73A9E9A9017CFCE0DECEA
Actual CI: E92F23A3DD3836E59EDEFC5438B76168
Actual CI: FBFD45DA10C93EDB8D74D00551F511C1
Actual CI: F437063E046032F59F60A050018F01EC
Actual CI: C084A1E967653AF4940E2A7152C02149
Actual CI: 550246C3B0F83308960EF8330500B680
Actual CI: 28E856A815043FA6887ABB2C5A0E73B7
Actual CI: 803AB968A0783313AC883835A0EDDDA2
Actual CI: 4CA413D13A5E3383A3724EA072F803D8
Actual CI: E4B9E460B82E3DACB7D2912F6A9CCE87
Actual CI: 0B2FBE6FCA4B35B8B93BC244883BEDC4
Actual CI: C824EFE2CA163D5EA95EF79BAB769732
Actual CI: 3EA8E707D644308A8A3CFB967DB7F726
Actual CI: 26BBEF79820B300D9366E5FA7B95D807
Actual CI: 530DB97F996832C291088B4A66055CBB
Actual CI: 72D9B0CD2E733F63A4C75C76104251EF
Actual CI: DEDE63ECA1AE37A1A1A5AE1E28E63857
Actual CI: 56BADF3D751D302694E18DD6AF7990F9
Actual CI: E8BE04B2F9953B798B935F64672BDAB9
Actual CI: 1838453074AA304B8C9EB270B3209CDB
Actual CI: EDA8200495A731AFB48A55228ED51570
Actual CI: 29432FD455E03F43920AED7D29798258
Actual CI: 055E03B89E34320882ABD781A69F9809
Actual CI: 5D9F1A0574333C6EBE33DECA4E09BEC3
Actual CI: 151EAA4AD64A3E73938800BE3164BEE6
Actual CI: 9BEF9EC3D9C3333AB8E3D2BE42433035
Actual CI: DD025C72A0B5391BBC14E0F5458D5093
Actual CI: 78AD41482B143ABA8D6397BC899D1ECD
Actual CI: 28DD04BB28D73BDD8013954A03C1D4F3
Actual CI: 933D9FC7AD373FEFA2A2609AFD2E033C
Actual CI: B310D4FB341B3ECB8B8E3DE61B9769BB
Actual CI: 892B43543AB635249544B74FB2D50238
Actual CI: 9F6B77BB3AF132729EBDB479E926B2A0
Actual CI: BFCE3FB197A435E9B9C39320A6BCB734
Actual CI: 6D738D4A858E3F739EE5019BF6DAE542
09 Feb 2015 13:36:13:913 [INFO] Processed Status — TopLevel CIs: 8/8 All CIs this Interval: 52 Total CIs: 52
Actual CI: 3605D85E1356342789A8C75555D1753C
Actual CI: 9EBC5B2280883ECFA71F03DDB8CA4366
Actual CI: E89365947C4A3B028E09856A0ECBD001
Actual CI: 29811E1696A23E6DBEFFCACCD48F9CFF
Actual CI: 8332EE5EB64031688E2A8FF94CF8F8FD
Actual CI: 550F4F2A50F6386D9F5C62D8D8078F8B
Actual CI: 992CB812486E3F6994890C610520DB2A
Actual CI: CDC438AE661B3E558BF1C9E3F674D7D5
Actual CI: 7CB0F3129F7538888C6112812FC63919
Actual CI: DF646C6330F4326AA08E66F311BD8748
Actual CI: 97658F61EAB23405BAA76164A00C7342
Actual CI: 352BBACA06E63002AA30DC0D24F106E2
09 Feb 2015 13:36:14:113 [INFO]
========================================================
Mapping execution completed
Mapping: TADDM-2-TUSC-Actual-CIs
Execution time: 00:00:16
Actual CIs created: 8
Records created: 404
Records updated: 0
Records deleted: 0
Errors: 0

NRS GUIDs created: 12
NRS errors: 0
NRS records updated on Alternate Keys: 0
NRS records found as duplicate: 0
NRS records deleted because of duplicate: 0
NRS warnings due to duplicate data: 0
========================================================

Done
Mapping completed successfully.
Integration Composer has finished.

As you can see 8 Actual Configuration items were created using data coming from TADDM. Log in to your Control Desk Console and navigate to: IT Infrastructure -> Actual Configuration Items

The Actual Configuration items window now loads, however it is empty. Click on the blue double arrow icon on the top of the screen to reload data from the database.

If everything went fine you should be seeing TADDM records showing up here.

Installing and Configuring IBM Control Desk Service Provider Edition V7.5.3

Leave a reply

This article will help you install and configure IBM Control Desk Service Provider Edition V7.5.3. As usual we will use SLES 11 SP3 as an installation OS. We used 6 gigabyte of RAM, 2 CPU cores and 50 gigabytes of disk space in this scenario.

We downloaded the following packages from Passport Advantage:

IBM SmartCloud Control Desk V7.5.1 TDI Integrations Multiplatform Multilingual (CI9CWML )
IBM Control Desk Service Provider Edition V7.5.3 for Linux Multilingual (CN2HNML )
Tivoli Middleware Installer Images V7.5.0.2, 1 of 3 for Linux x86-64 Multilingual (CI913ML )
Tivoli Middleware Installer Images V7.5.0.2, 2 of 3 for Linux x86-64 Multilingual (CI5JBML )
Tivoli Middleware Installer Images V7.5.0, 3 of 3 for Linux x86-64 Multilingual (CZX5JML )
IBM DB2 Server V10.5 for Linux on AMD64 and Intel EM64T systems (x64) Multilingual (CIK9IML )
IBM DB2 ESE Restricted Use, Quick Start and Activation V10.5 for Linux, UNIX and Windows Multilingual (CIK0LML )

We will use the Middleware installer to install & configure the middleware for us. Once all products installed we will gradually upgrade and distribute the middleware components across multiple servers. The middleware installer will install the following software and versions:

DB2 9.7
WepSphere Application Server Network Deployment 7.0.0.17
IBM Tivoli Directory Server 6.3
IBM HTTP Server 7.0.0.17

Before the installation we perform the following steps:

Set environment variable for mwi_launchpadroot. This will set the installation location of the installer. Our setting was like this:

export mwi_launchpadroot=/Downloads/TIVOLI-IMAGES/CONTROLDESK753/

Raise the OS open file limit to 8192 by adding the following 2 files:

root hard nofile 8192
root soft nofile 8192
to
/etc/security/limits.conf

Once the file is modified and saved reboot the system for the settings to take effect. Please note that you must have root access to perform this installation.

Installing the Middleware

The middleware installation is started with the setupLinux64.sh command from ./Install/MWI directory if the Control Desk installation media. Alternatively you can use the launchpad application to execute this installation script.

HUCTRLDSK001-P1:/Downloads/TIVOLI-IMAGES/CONTROLDESK753/Install/MWI # ./setupLinux64.sh
————————————————————-
Preparing the IBM Tivoli Middleware Installer. Please wait…
————————————————————-
Operating System: Linux
Linux distribution: suse
Host HUCTRLDSK001-P1 not found: 3(NXDOMAIN)
Hostname HUCTRLDSK001-P1 is a fully qualified domain name.OK.
The library libstdc++.so.5(64-bit) is installed.OK.
Env variable mwi_launchpadroot is set.OK.
Copying the installation files to a temporary location…

Once the installation dialog pops up select the installation language and click OK.

Click Next at the Welcome window accept the license agreement then select the location of the installation plan and click Next.

Click Next at the Autonomic Deployment Engine installation window.

Select everything in the next window then click Next.

The installer is now generating an installation plan based on what was picked. Once ready the plan and installation order is displayed. Review the plan then click Next.

Make sure that you give the fully qualified domain name at the following window then click Next.

Define the master password in the next window. We used this option as we want all middleware passwords to be the same. You can unselect this option and type different passwords for different software components as you progress with the installation. Click Next to get to the following installation step.

Select the installation location of DB2 9.7 then click Next.

Leave the default configuration values for the DB2 instance then click Next.

Leave the default configuration values for the DB2 fenced user then click Next.

Leave the default configuration values for the DB2 admin group user then click Next.

Leave the default configuration values for the IBM Tivoli Directory Server installation, then click Next. It is important to point out here that the install location of the IBM Tivoli Directory Server can not be changed.

Leave the default configuration values for the IBM Tivoli Directory Server configuration, then click Next.

Leave the default configuration values for the IBM Tivoli Directory Server database configuration, then click Next.

Leave the default configuration values for the WebSphere Application Server Security, then click Next.

Leave the default configuration values for the WepSphere Application Server Network Deployment installation, then click Next.

Leave the default configuration values for the Deployment Manager profile name and the Application Server Profile Name then click Next.

Leave the default configuration values for the WepSphere Application Server Network Deployment configuration, then click Next.

Leave the default configuration values for the IBM HTTP Server Installation, then click Next.

Leave the default configuration values for the IBM WebSphere application server plugin for the IBM HTTP Server, then click Next.

Select Specify the directory to location where the Middleware installation images are, then click Next.

We copied everything into the root installation directory under the linux64 directory. Select your image location then click Next.

Specify the temporary directory for the installation, then click Next.

Select the Deploy Plan option then click Next.

Review the installation plan then click Deploy to kick off the installation.

The installation will take about 125 minutes in our environment. It is time to take a break now.

If everything goes as expected you should see this:

Installing Control Desk

Once the Middleware is installed we are ready to install the IBM Control Desk Service Provider Edition. Before you start the installation it is important to know that all configuration values will be validated once the Next button is clicked so there should be know unexpected surprises once the physical installation process starts. You will see the Validating inputs dialog a lot during configuration specification.

The installation process does take a very long time. Let the installer finish its procedure. It is not uncommon the the installation is running for more than 8 hours. If you have to stop the installation procedure for some reason, you can resume the installation using taskrunner utility. The utility is located in your control desk installation directory under scripts. Run the following command to continue a halted installation:

./scripts/taskRunner.sh CONTINUE

We start the installation using the command line installer instead of the launchpad. The installer is located in ./Install/ISM directory.

HUCTRLDSK001-P1:/Downloads/TIVOLI-IMAGES/CONTROLDESK753/Install/ISM # ./install_linux64.sh
Entering ./install_linux64.sh at Thu Feb 5 21:36:06 CET 2015.
Preparing to install…
Extracting the JRE from the installer archive…
Unpacking the JRE…
Extracting the installation resources from the installer archive…
Configuring the installer for this system’s environment…

Launching installer…

Select the installation language then click OK.

Click Next at the Introduction window, specify the installation location, then click Next.

Click Next after the install location verification, and the pre-installation process starts.

Check the Package Summary then click Next to continue the installation process.

Accept the License Agreement then select Custom Deployment in the following window then click Next.

Select the Import the Middleware configuration information and fill in the fields with your Host name, Workspace location and root account details. This is actually very handy as it will pick up all the Middleware configuration parameters apart from the passwords so most of the following installation parameters will be pre-filled. Click Next to continue the installation.

Select DB2 as the database type then click Next.

Type the DB2 user password, then click Next.

Select Automate database creation and configuration as the database is not yet created and we would like the installer to do this for us. Click Next to continue the installation. Specify an administrative account such as root so the installer can perform the required database operations. Click Next to continue the installation.

Specify the required database passwords, then click Next.

Leave the DB2 table space values on default, then click Next.

Select IBM WebSphere Application Server and select the Automate WebSphere configuration option, then click Next.

Specify the wasadmin password then click Next.

Specify root and its password for the remote access user, then click Next.

Leave the WebSphere Application Server Configuration parameters on default and click Next.

Since we have the LDAP server pre-installed and configured select the first option at the Security panel then click Next.

Specify passwords for the default maximo users. Please note that the password must contain at least one numeric and one special character. Click Next to continue the installation process.

Leave the LDAP schema settings on default, then click Next.

Leave the JMS settings on default and click Next.

If you have TADDM already installed you can specify the TADDM connection settings here. Since we have TADDM already rolled out we specify the required values.

We do not specify an SMTP server for now. Click Next to continue the installation process.

We use the maxdb75 database for everything so we picked the Deploy data integration and context menu services to the same database option. Click Next to continue the installation.

After selecting the product languages, the installation gets to its final stage, you have various options here to do the installation later or perform actions manually. if you do not pick any of the options the setup program will perform the installation…

… once you reviewed your input summary and …

.. the pre-installation summary. Click Install to start the installation process.

The installation have 15 stages ( tasks ) and as I pointed out before it will take a very long time. Stage 6 ( Task 6 ) when the Database configuration is happening is a notoriously long process for example. Therefore it is good to use a utility that checks the real time load on your server for example top or htop if you like more visualized results. This way you can see if the installer is actually doing its job.

Upon successful completion you should see the following screenshot.

Open your browser and type the following URL to get to the maximo console:

http://yoursccdhost/maximo

The admin user is maxadmin and use the password you have specified at installation time. If you are not able to log in right after the installation, you will need to restart the server and start up the components one by one. This usually solves the initial login issues for me.

This is how you start your IBM Control Desk server components:

HUCTRLDSK001-P1:~ # su – idsccmdb -c db2start
02/06/2015 13:48:13 0 0 SQL1063N DB2START processing was successful.
SQL1063N DB2START processing was successful.
HUCTRLDSK001-P1:~ # /opt/ibm/ldap/V6.3/sbin/ibmslapd -I idsccmdb
GLPSRV041I Server starting.
GLPCTL113I Largest core file size creation limit for the process (in bytes): ‘1024’(Soft limit) and ‘-1′(Hard limit).
GLPCTL119I Maximum Data Segment(Kbytes) soft ulimit for the process is -1 and the prescribed minimum is 262144.
GLPCTL119I Maximum File Size(512 bytes block) soft ulimit for the process is -1 and the prescribed minimum is 2097152.
GLPCTL122I Maximum Open Files soft ulimit for the process is 8192 and the prescribed minimum is 500.
GLPCTL121I Maximum Stack Size(Kbytes) soft ulimit for the process was 8192 and it is modified to the prescribed minimum 10240.
GLPCTL122I Maximum Virtual Memory(Kbytes) soft ulimit for the process is 6360560 and the prescribed minimum is 1048576.
GLPCOM024I The extended Operation plugin is successfully loaded from libevent.so.
GLPCOM024I The extended Operation plugin is successfully loaded from libtranext.so.
GLPCOM024I The extended Operation plugin is successfully loaded from libldaprepl.so.
GLPSRV155I The DIGEST-MD5 SASL Bind mechanism is enabled in the configuration file.
GLPCOM021I The preoperation plugin is successfully loaded from libDigest.so.
GLPCOM024I The extended Operation plugin is successfully loaded from libevent.so.
GLPCOM024I The extended Operation plugin is successfully loaded from libtranext.so.
GLPCOM023I The postoperation plugin is successfully loaded from libpsearch.so.
GLPCOM024I The extended Operation plugin is successfully loaded from libpsearch.so.
GLPCOM025I The audit plugin is successfully loaded from libldapaudit.so.
GLPCOM024I The extended Operation plugin is successfully loaded from libevent.so.
GLPCOM023I The postoperation plugin is successfully loaded from libpsearch.so.
GLPCOM024I The extended Operation plugin is successfully loaded from libpsearch.so.
GLPCOM022I The database plugin is successfully loaded from libback-config.so.
GLPCOM024I The extended Operation plugin is successfully loaded from libevent.so.
GLPCOM024I The extended Operation plugin is successfully loaded from libtranext.so.
GLPCOM023I The postoperation plugin is successfully loaded from libpsearch.so.
GLPCOM024I The extended Operation plugin is successfully loaded from libpsearch.so.
GLPCOM022I The database plugin is successfully loaded from libback-rdbm.so.
GLPCOM010I Replication plugin is successfully loaded from libldaprepl.so.
GLPSRV189I Virtual list view support is enabled.
GLPCOM021I The preoperation plugin is successfully loaded from libpta.so.
GLPSRV194I The Record Deleted Entries feature is disabled. Deleted entries are immediately removed from the database.
GLPSRV207I Group conflict resolution during replication is disabled.
GLPSRV200I Initializing primary database and its connections.
GLPRDB126I The directory server will not use DB2 selectivity.
GLPCOM024I The extended Operation plugin is successfully loaded from libloga.so.
GLPCOM024I The extended Operation plugin is successfully loaded from libidsfget.so.
GLPSRV180I Pass-through authentication is disabled.
GLPCOM003I Non-SSL port initialized to 389.
HUCTRLDSK001-P1:~ # su – ctginst1 -c db2start
02/06/2015 13:48:33 0 0 SQL1063N DB2START processing was successful.
SQL1063N DB2START processing was successful.
HUCTRLDSK001-P1:~ # /app/IBM/WebSphere/AppServer/profiles/ctgDmgr01/bin/startManager.sh
ADMU0116I: Tool information is being logged in file
/app/IBM/WebSphere/AppServer/profiles/ctgDmgr01/logs/dmgr/startServer.log
ADMU0128I: Starting tool with the ctgDmgr01 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server dmgr open for e-business; process id is 5078
HUCTRLDSK001-P1:~ # /app/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/bin/startNode.sh
ADMU0116I: Tool information is being logged in file
/app/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/logs/nodeagent/startServer.log
ADMU0128I: Starting tool with the ctgAppSrv01 profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server nodeagent open for e-business; process id is 5273
HUCTRLDSK001-P1:~ # /app/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/bin/startServer.sh MXServer
ADMU0116I: Tool information is being logged in file
/app/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/logs/MXServer/startServer.log
ADMU0128I: Starting tool with the ctgAppSrv01 profile
ADMU3100I: Reading configuration for server: MXServer
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server MXServer open for e-business; process id is 5436
HUCTRLDSK001-P1:~ # /app/IBM/HTTPServer/bin/apachectl start

We have a post with more detailed information about the components start up here.

IBM Control Desk Service Provider Edition Configuration & installation articles:

Installing the IBM Tivoli Integration Composer
Integrating TADDM and Control Desk using Integration Composer

Change DB2 database port/user/password for maxdb75 – Control Desk 7.5.1

Leave a reply

We had a requirement today to change the default port ( 50005 ) of the DB2 server on the Control Desk box. Control desk stores this configuration data in the maximo.properties file which is normally located in ./SMP/maximo/applications/maximo/properties/ directory. This file is encrypted as it also stores the userid and password for maxdb75 database. The following steps have to be performed to change the port or any other setting properly:

– Copy original properties file ( maximo.properties_orig ) from ./SMP/etc/ to ./SMP/maximo/applications/maximo/properties/
– Rename maximo.properties to maximo.properties.old
– Rename maximo.properties_orig to maximo.properties
– Edit maximo.properties file. We changed the default port to 60000. Don’t forget to update the password field to the current password.

mxe.encrypted=true
mxe.db.url=jdbc:db2://ussccd1-p1.ipm.local:60000/maxdb75
mxe.db.driver=com.ibm.db2.jcc.DB2Driver
mxe.rmi.port=0
mxe.db.schemaowner=maximo
mxe.db.password=CHANGETHISVALUE
mxe.db.user=maximo
mxe.registry.port=13400
mxe.name=MXServer

– Encrypt the configuration file using the encryptproperties.sh usually location in ./SMP/maximo/tools/maximo

Once this procedure is done you will have to repackage the configuration file in properties.jar located in ./WebSphere/AppServer/profiles/ctgAppSrv01/installedApps/ctgCell01/MAXIMO.ear

– Copy the configuration.jar file to a temporary location
– unpack the configuration.jar file using the jar utility. There will be several version of this on your server so just look for it and use whichever is convenient.
– Run the following command /yourjarlocation/jar -xvf properties.jar
– Copy the maximo.properties file to the temporary directory and overwrite the extracted version
– Pack the jar file back to /yourjarlocation/jar -cvf properties.jar
– Copy the new properties.jar file to it’s original location: ./WebSphere/AppServer/profiles/ctgAppSrv01/installedApps/ctgCell01/MAXIMO.ear

Now restart the WebSphere application server and your changes should be done.

If you happen to use Integration Composer you also have to change the database settings on the Control Desk Console in the following menu:

System Configuration -> Platform Configuration -> System Properties

Also change the port in the fusion.properties file which is located in the Integration Composer root directory under ./data/properties:

mxe.db.url=jdbc:db2://localhost:60000/maxdb75

Starting SmartCloud Control Desk one box system

Leave a reply

If we install a Smart Cloud Control Desk 7.5.1.1 one box system, and want to restart the server we have to follow the below list to get the whole system up and running again. (Please adapt the commands to your system)

1. Start directory server database
su – idsccmdb -c db2start

2. Start directory server
/opt/ibm/ldap/V6.3/sbin/ibmslapd -I idsccmdb

3. Start Maximo database
su – ctginst1 -c db2start

4. Start Websphere Deployment Manager
/app/IBM/WebSphere/AppServer/profiles/ctgDmgr01/bin/startManager.sh

5. Start Websphere Node agent
/app/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/bin/startNode.sh

6. Start Websphere Application Server
/app/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/bin/startServer.sh MXServer

7. If not starting automatically, start the web server
/app/IBM/HTTPServer/bin/apachectl start