Best Practice for IBM SmartCloud Application Performance Management UI integration with JazzSM and Transaction Tracking
1. Background Introduction
The following abbreviations are used in this article:
APMUI - IBM SmartCloud Application Performance Management UI
OSLC - Open Services for Lifecycle Collaboration
SCR - Service Component Repository
TTAPP3 - an application with MQ, DB2, IHS, and WAS resources
QMA - an MQ queue manager in APPL1
TT - ITCAM for Transactions Tracking Agents
TO - Transaction Reporting Agent, one agent of TT.
In APMUI7.7, a new component SCR is introduced. SCR applies OSLC standard and works
as a repository for resources from different providers to be registered and reconciled into a
single resource model and consumed by APMUI. Currently the possible providers include ITM
(through JazzSM), TADDM (through JazzSM) and Transaction Tracking.
This article describes how APMUI integrates with JazzSM and Transaction Tracking to realize
the reconciliation in SCR among the registration records for the same application/resource
from different providers, thus this application/resource can be displayed on APMUI as a single
one, and changes made on the same application/resource that are detected by different providers can be updated on APMUI.
2.Highlight of the best practice
As a user, I would like to see application 'TTAPP3' and the performance data for the resources under it, for example, MQ queue manager 'QMA' , on APMUI. If changes are made to
application 'TTAPP3' , I would like to see the update notification on APMUI in a timely manner.
Integration ENV topology:
The integration of APMUI with JazzSM and Transaction Tracking topology is similar to the
following one:
figure 1 An overall view of integration
①APMUI is configured to use ITM Data Provider.
②MQ agent discovers 'QMA'.
③KAS agent registers 'QMA' to JazzSM.
④TADDM discovers 'QMA' into data store.
⑤User creates an application 'TTTAPP3' using 'qmgr1' in TADDM.
⑥TADDM OSLC agent registers both 'TTAPP3' and 'QMA' to JazzSM.
⑦TT Agent - TO discovers 'TTAPP3' and all resources under it, including 'QMA'
⑧TT Agent - TO posts 'TTAPP3' and all resources under it to SCR, including 'QMA'
⑨JazzSM register 'TTAPP3' and 'QMA' to SCR.
⑩'TTAPP3' and 'QMA' from JazzSM and TT are reconciled in SCR and ready for use.
Before going on, please note that following product versions are used in this best practice :





APMUI 7.7
JazzSM1.2
TADDM 7.2.2
ITM63 FP2
Transaction Tracking 7.4 IFix 1
Messaging MQ Agent v71FP1
3. Detailed steps of the best practice :
3.1 Prerequisite:
Before going on to the next section, JazzSM, ITM(KLZ, MQ,TT,KAS agent and agent support
) and TADDM need to be setup and configured as shown in figure 1 in section 2. If you don't
have TADDM in your solution, just ignore the TADDM-related steps. Also, it's assumed that
TT agent 7.4 IF1 AMCE is configured to collect data for TTAPP3 before going on.
To simplify the best practice and focus on the APMUI side configuration, the basic configuration of the TADDM, KAS agent, MQ Agent and TT agents will not be discussed here.
3.2 Preparation
Ensure that required products are installed and configured on the following machines.
Role
ITM
TO Agent
MQ agent/WMQ
TADDM
JazzSM
APMUI
host name
tivp7bl04/9.181.25.199
v525400197c2c
v525400d6ca22
tivvm195
tivvm194
tivvm182
3.2.1. APMUI :
During the APMUI installation, ensure that APMUI is enabled for JazzSM connection.
After APMUI installation is completed, configure an ITM data provider and make sure its status is 'available'.
3.2.2 JazzSM :
Make sure JazzSM server and FRS is active by querying FRS for all applications :
http://tivvm194.cn.ibm.com:16310/oslc/rr/collection?oslc.where=rdf%3Atype%3D%3Chttp%3
A%2F%2Fopen-services.net%2Fns%2Fcrtv%23Application%3E&oslc.select=*&oslc.pageSiz
e=500&oslc.paging=true
Return result should include total count of applications, in the following example, it is 43.
3.2.3 ITM :
1) Preparation for JazzSM registration:
- Enable OSLC for MQ on TEMS with OSLC template for MQ.
- Configure and start MQ agent to monitor queue manager 'QMA' on v525400d6ca22.
- Configure and start LZ agent on v525400d6ca22.
- Configure and start KAS agent to connect to TEMS and JazzSM.
Ensure 'QMA' softwareServer is found on KAS provider via the link below:
2) Configure the TO agent to monitor application 'TTAPP3'.
3.2.4 TADDM :
1) Discover queue manager 'QMA' on v525400d6ca22 into TADDM.
2) Create an application 'TTAPP3' in TADDM, and add 'QMA' to it.
3) Configure the TADDM update registering interval to JazzSM:
The default update interval is 3 hours, change it to a smaller value (for example, 15 minutes)
to get TADDM updates more quickly on JazzSM and APMUI.
Modify the collation.properties file under TADDM home:
vi /opt/IBM/taddm/dist/etc/collation.properties
Modify the value from 3.0 (3 hours) to a value that fulfills your requirements. In this best
practice, 0.25 (15 minutes) is used:
com.ibm.cdb.topobuilder.groupinterval.integration=0.25
As TADDM owner, restart TADDM server.
[taddmusr@tivvm195 bin]$ pwd
/opt/IBM/taddm/dist/bin
[taddmusr@tivvm195 bin]$ ./control stop
[taddmusr@tivvm195 bin]$ ./control start
3.3 The integration scenario:
3.3.1 User create an apo on APMUI by reading TT discovered application 'TTAPP3'
1) Posting TT discovered 'TTAPP3' to SCR:
On v525400197c2c where the TO agent is running:
[root@v525400197c2c bin]# pwd
/opt/IBM/ITM/li6263/to/bin
[root@v525400197c2c bin]# vi itcamfttdla_config.properties
Modifying the file with correct information for the SCR server and save it:
SCR_SERVER_ADDRESS=tivvm182.cn.ibm.com
SCR_SERVER_PORT=17310
SCR_USERNAME=apmadmin
SCR_PASSWORD=YXBtcGFzcw==
Remove the last time posting info:
[root@v525400197c2c bin]# rm lastPersist.properties
Run run-rdf.sh to post the TO discovered rdf for 'TTAPP3' to SCR.
* ensure XMLtoolkit, SCRderby and SCR is active at SCR machine, or else the TO data
posting will fail.
2) APMUI read the 'TTAPP3' from SCR and save it as a new application named
'TTAPP3-new'
On APMUI, open the 'Add Application' panel and click 'read', the 'TTAPP3' is available in the
Application list, with Transaction Tracking as its source.
Choose the 'TTAPP3' and save it as a new application 'TTAPP3-new'.
In the saved application 'TTAPP3-new', QMA shows up as a TO group widget.
3.3.2 The 'QMA' from ITM and TADDM reconciled in JazzSM
As instructed in section 3.2.3 and 3.2.4, the 'QMA' from ITM and TADDM should already be
updated into JazzSM and reconciled into a single resource.
Use a serial of queries to check the existence of the reconciled resource record for 'QMA' in
JazzSM.
1) Find out the ComputerSystem resource records for 'v525400dd6ca22':
http://tivvm194.cn.ibm.com:16310/oslc/rr/collection?oslc.where=crtv:shortHostname=%22v5
25400d6ca22%22&oslc.select=*&oslc.pageSize=500&oslc.paging=true
The returned computerSystem resource record ID is
http://tivvm194.cn.ibm.com:16310/oslc/resources/1384802640026
2)Find out all the resources running on this computerSystem, using the resource record ID for
'v525400d6ca22'
http://tivvm194.cn.ibm.com:16310/oslc/rr/collection?oslc.where=crtv:runsOn=%3Chttp://tivvm
194.cn.ibm.com:16310/oslc/resources/1384802640026%3E&oslc.select=*&oslc.pageSize=5
00&oslc.paging=true
3)Four queue managers are returned as a result of the query, the first one is 'QMA', which is
what we are looking for. There are 2 provider records from TADDM (sourceRecord containing
'/cdm/oslc/configuration' and '/cdm/oslc/changehistory') and 1 from KAS (sourceRecord containing '/kas_srv/') in this single resource record for 'QMA', which prove this is a reconciled
resource record.
3.3.3 The 'TTAPP3' from TADDM is registered in JazzSM
3.3.4 Configure SCR connection with JazzSM.
Configure SCR connection with JazzSM using the connManager.sh command.
Restart all APMUI servers to apply the configuration:
In the same directory as connManager.sh, find server.sh command and run ./server.sh
stop/start to restart all APMUI servers.
3.3.5 Check 'TTAPP3' and 'QMA' reconciled in SCR.
1) Query for application 'TTAPP3' in SCR.
http://tivvm182.cn.ibm.com:17310/SCRCLUSTER_SCR_oslc/oslc/rr/collection?oslc.where=c
rtv:name=%22TTAPP3%22&oslc.select=*&oslc.pageSize=1000&oslc.paging=true
2) The application resource record for 'TTAPP3' is found as below. There are 3 providerRecord in the Application and you need to pay attention to 2 of them:
one is from TT (sourceRecord containing '/tt/v525400197c2c:TO') and one is from
TADDM(sourceRecord containing '/cdm/oslc/configuration'), which means registration record
from the 2 providers has reconciled into this single resource record for application 'TTAPP3'.
3) Query for all 'QMA' in SCR and find the resource record for 'QMA' on v525400d6ca22 as
below.
There are 3 providerRecord sections from TO, TADDM and KAS(ITM) found in the resource
record, which means registration records from the 3 providers has reconciled into this single
resource record for queue manager 'QMA' on v525400d6ca22.
3.3.6 Check 'TTAPP3' and 'QMA' on APMUI after reconciliation taking effect.
1) Log in to APMUI. A blue icon is displayed on 'TTAPP3-new' with a number of updates.
Accept the updates for the new component on QMA and save the application.
As shown in the screenshot below, 'TTAPP3-new' is read from 'TTAPP3', thus any updates
on 'TTAPP3' will be reflected on 'TTAPP3-new' on APMUI.
2) As shown in screenshot below, now the QMA TO group widget has been replaced by a
resource group widget with performance data after you accept the update on QMA. As a result of the reconciliation, QMA resource now can link to ITM performance data from SCR and
get the result returned on APMUI.
3.3.7 An example for changes update on 'TTAPP3' on APMUI
1) From TADDM, add and delete some resources in 'TTAPP3'.
The following screenshot shows the 'TTAPP3' content before you make changes to it.
The following screenshot shows the 'TTAPP3' content after you make changes to it.
2) Configure TADDM to quickly synchronize changes to JazzSM:
Refer to section 3.2.4
3) Configure APMUI to quickly detect application updates:
On APMUI machine :
Modify the OSLC_APP_DELTA_SYNC_INTERVAL to a preferred value. Here we set the
minimum value to 120 seconds.
After editing and saving the apmui.cfg file, run the following command to make the configuration changes take effect:
4) Check updates on APMUI for the changes made in TADDM.
Check on APMUI, an update icon appears on application 'TTAPP3-new', check details of the
updates and 3 updates are waiting to be accepted:
- 'New Components' update for 'QMA' running on v525400e0238c
- 'New Components' update for computer system v525400e0238c
- 'Deleted Components' update for 'brkqm1' running on v525400d6ca22
These are the changes on 'TTAPP3' in TADDM, and now they are reflected on APMUI.
5) Accept these changes and save the application. Now the changes from TADDM are reflected on APMUI.
4. Consideration for performance:
Optimize JazzSM for better performance when it has a relatively big workload, for example,
short APMUI App sync up interval and TADDM update sync up interval is configured when
there are a large number of resources.
Please refer to JazzSM technotes below for detail information:
http://www-01.ibm.com/support/docview.wss?uid=swg21656954
Additional Information
APMUI online documentation:
http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apm.doc_7.7/apmui77_
ug.pdf
SMC best practice: Grouping Applications in Transaction Tracking for APMUI
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Comp
osite%20Application%20Manager/page/Grouping%20Applications%20in%20Transaction%2
0Tracking%20for%20APMUI
SMC best practice: APMUI and Integrating with Transaction Tracking - Quick Start Guide
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Comp
osite%20Application%20Manager/page/APMUI%20and%20Integrating%20with%20Transacti
on%20Tracking%20-%20Quick%20Start%20Guide
About the author
If you have any questions about this document, you can contact us :
Wang Lu
Email : [email protected]
Xiao Lu
Email : [email protected]
Zhou Huai Nan Email : [email protected]