IBM Tivoli Composite Application Manager Family Version 6.1 - Installation, Configuration and Basic...

7/31/2019 IBM Tivoli Composite Application Manager Family Version 6.1 - Installation, Configuration and Basic Usage - SG247151

http://slidepdf.com/reader/full/ibm-tivoli-composite-application-manager-family-version-61-installation 1/503

ibm.com /redbooks

Draft Document for Review March 1, 2007 5:22 pm SG24-7151-01

IBM Tivoli CompositeApplication Manager V6.1FamilyInstallation, Configuration and Basic Usage

Budi Darmawan

Lee Hwa Yong

Michael Stahl

Sören Eickhoff

Managing response time and

transaction

Monitoring J2EE application

servers

Collecting Web Services

information

Front cover

http://www.redbooks.ibm.com/






IBM Tivoli Composite Application Manager V6.1Family Installation, Configuration and Basic Usage

February 2007

International Technical Support Organization

Draft Document for Review March 1, 2007 5:22 pm 7151edno.fm

SG24-7151-01



7151edno.fm Draft Document for Review March 1, 2007 5:22 pm

© Copyright International Business Machines Corporation 2007. All rights reserved.

Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADPSchedule Contract with IBM Corp.

Second Edition (February 2007)

This edition applies to Version 6, Release 1 of IBM Tivoli Composite Application Managerproducts: IBM Tivoli Composite Application Manager for CICS Transactions, 5698-A69 IBM Tivoli Composite Application Manager for IMS Transactions, 5698-A70 IBM Tivoli Composite Application Manager for WebSphere (z/OS), 5698-A71 IBM Tivoli Composite Application Manager for WebSphere, 5724-L62 IBM Tivoli Composite Application Manager for J2EE, 5724-N95 IBM Tivoli Composite Application Manager for Response Time Tracking (z/OS), 5698-A75

IBM Tivoli Composite Application Manager for Response Time Tracking, 5724-L99 IBM Tivoli Composite Application Manager for J2EE Operations, 5724-Q21 IBM Tivoli Composite Application Manager for SOA (z/OS), 5698-A77 IBM Tivoli Composite Application Manager for SOA (Distributed), 5724-M07 IBM Tivoli Composite Application Manager for Internet Service Monitoring, 5724-Q22

This document created or updated on March 1, 2007.

Note: Before using this information and the product it supports, read the information in“Notices” on page xxv.

Note: This book is based on a pre-GA version of a product and may not apply when the

product becomes generally available. We recommend that you consult the productdocumentation or follow-on versions of this redbook for more current information.



© Copyright IBM Corp. 2007. All rights reserved. iii

Draft Document for Review March 1, 2007 5:22 pm 7151TOC.fm

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxviiThe team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxviiBecome a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxixComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxiFebruary 2007, Second Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi

Chapter 1. IBM Tivoli Composite Application Manager V6.1 overview . . . 1

1.1 Application management background and issues. . . . . . . . . . . . . . . . . . . . 21.2 IBM Tivoli Composite Application Manager. . . . . . . . . . . . . . . . . . . . . . . . . 3

1.2.1 ITCAM for WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2.2 ITCAM for J2EE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.2.3 ITCAM for Response Time Tracking. . . . . . . . . . . . . . . . . . . . . . . . . . 61.2.4 ITCAM for J2EE Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2.5 ITCAM for Internet Service Monitoring . . . . . . . . . . . . . . . . . . . . . . . . 71.2.6 ITCAM for SOA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2.7 ITCAM for CICS Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.2.8 ITCAM for IMS Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2.9 OMEGAMON XE for Messaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.3 Project environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3.1 Machine environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.3.2 Application environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.4 Document organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2. ITCAM for WebSphere and ITCAM for J2EE concepts and

installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.1 Monitoring J2EE application servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2 Architecture and interconnection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.2.1 The managing server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.2.2 J2EE and WebSphere data collector . . . . . . . . . . . . . . . . . . . . . . . . 18



7151TOC.fm Draft Document for Review March 1, 2007 5:22 pm

iv IBM Tivoli Composite Application Manager V6.1 Family Installation, Configuration and Basic Usage

2.2.3 Tivoli Enterprise Management Agent . . . . . . . . . . . . . . . . . . . . . . . . 202.2.4 Monitoring resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.2.5 Logging and troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.3 Implementation overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.3.1 Sizing consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.3.2 Security considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.3.3 Implementation configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.3.4 Managing server installation options. . . . . . . . . . . . . . . . . . . . . . . . . 29

2.4 Installation process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.4.1 ITCAM for WebSphere and ITCAM for J2EE managing server . . . . 302.4.2 ITCAM for WebSphere data collector . . . . . . . . . . . . . . . . . . . . . . . . 352.4.3 J2EE data collector installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412.4.4 Apache HTTP Server set up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

2.5 Integration with Tivoli Enterprise Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . 442.5.1 Prepare the IBM Tivoli Monitoring V6.1 infrastructure . . . . . . . . . . . 462.5.2 Tivoli Enterprise Management Agent installation . . . . . . . . . . . . . . . 482.5.3 Tivoli Enterprise Management Agent configuration . . . . . . . . . . . . . 51

2.6 Initial configuration and operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522.6.1 Data collector configuration steps. . . . . . . . . . . . . . . . . . . . . . . . . . . 522.6.2 Operator definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Chapter 3. ITCAM for WebSphere and ITCAM for J2EE usage . . . . . . . . . 61

3.1 Usage scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623.2 Enterprise monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633.3 Server activity analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.4 Transaction reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

3.4.1 TOP reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.4.2 Problem investigation using report . . . . . . . . . . . . . . . . . . . . . . . . . . 723.4.3 Method based reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

3.5 Composite transaction analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

3.5.1 Transaction report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803.5.2 In-flight request search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853.6 Using Tivoli Enterprise Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

3.6.1 WebSphere summary workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . 893.6.2 Garbage collection workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903.6.3 Web applications workspace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

3.7 Historical information and reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933.8 JBoss application server data collector . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Chapter 4. ITCAM for Response Time Tracking concepts and installation .1094.1 Product architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

4.1.1 The management server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111



Contents v


4.1.2 Store-and-forward agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134.1.3 Management agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144.1.4 Tivoli Enterprise Monitoring Agent . . . . . . . . . . . . . . . . . . . . . . . . . 1174.1.5 ARM concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

4.2 Management methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204.2.1 Management resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214.2.2 Reporting group and agent group . . . . . . . . . . . . . . . . . . . . . . . . . . 1214.2.3 Management implementation overview. . . . . . . . . . . . . . . . . . . . . . 123

4.3 Implementation process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1234.3.1 Management server installation options . . . . . . . . . . . . . . . . . . . . . 1254.3.2 Management agent deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

4.4 Installation of ITCAM for Response Time Tracking. . . . . . . . . . . . . . . . . 1294.4.1 Management server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

4.4.2 Store and forward agent installation . . . . . . . . . . . . . . . . . . . . . . . . 1404.4.3 Distributed management agent installation . . . . . . . . . . . . . . . . . . . 1444.4.4 Installing ITCAM for Response Time Tracking fix pack 1 . . . . . . . . 1484.4.5 Integration with Tivoli Enterprise Monitoring Server . . . . . . . . . . . . 151

4.5 Monitoring components deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1594.5.1 Monitoring components in general . . . . . . . . . . . . . . . . . . . . . . . . . 1604.5.2 Installing Rational Robot and Generic Windows. . . . . . . . . . . . . . . 1624.5.3 Deploying Client Application Tracker . . . . . . . . . . . . . . . . . . . . . . . 1664.5.4 Deploying J2EE component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1674.5.5 Deploying JBoss and Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

4.5.6 Deploying Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1724.5.7 Deploying Synthetic Transaction Investigator . . . . . . . . . . . . . . . . . 1734.5.8 Deploying Web Response Monitor . . . . . . . . . . . . . . . . . . . . . . . . . 1744.5.9 Deploying Generic Playback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1774.5.10 Deploying ARM Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

4.6 Initial configuration and usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

4.6.1 Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

4.6.2 Reporting groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1834.6.3 Agent groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1844.6.4 User role assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Chapter 5. ITCAM for Response Time Tracking usage . . . . . . . . . . . . . . 1935.1 Usage scenarios overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1945.2 J2EE monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

5.2.1 J2EE discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1955.2.2 J2EE listening monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

5.2.3 J2EE report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1995.3 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

5.3.1 QoS discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2035.3.2 QoS listening monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204




vi IBM Tivoli Composite Application Manager V6.1 Family Installation, Configuration and Basic Usage

5.3.3 QoS report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2055.4 Synthetic Transaction Investigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

5.4.1 Recording Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2065.4.2 Generating robotic monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

5.4.3 STI report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2125.5 Web Response Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2185.5.1 Web Response Monitor discovery . . . . . . . . . . . . . . . . . . . . . . . . . 2185.5.2 Web Response Monitor listening monitor . . . . . . . . . . . . . . . . . . . . 2215.5.3 Web Response Monitor report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

5.6 Rational Robot and Generic Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 2235.6.1 Creating Robot script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2235.6.2 Generic Windows robotic monitor and report . . . . . . . . . . . . . . . . . 226

5.7 JBoss and Tomcat monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

5.8 Application Response Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2305.8.1 Instrumenting the sample application . . . . . . . . . . . . . . . . . . . . . . . 2305.8.2 ARM discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2345.8.3 ARM listening monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2355.8.4 ARM report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

5.9 Client Application Tracker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2375.9.1 Client Application Tracker discovery . . . . . . . . . . . . . . . . . . . . . . . . 2395.9.2 Client Application Tracker listening monitor . . . . . . . . . . . . . . . . . . 2415.9.3 Client Application Tracker report. . . . . . . . . . . . . . . . . . . . . . . . . . . 242

5.10 Generic Playback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

5.10.1 Using the command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2435.10.2 Using uploaded file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

5.11 Working with Tivoli Enterprise Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Chapter 6. ITCAM for J2EE Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . 2536.1 ITCAM for J2EE Operations architecture . . . . . . . . . . . . . . . . . . . . . . . . 2546.2 ITCAM for J2EE Operations installation . . . . . . . . . . . . . . . . . . . . . . . . . 254

6.2.1 Installing the code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

6.2.2 Activating WebSphere support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2556.2.3 Preparing Tivoli Enterprise Portal . . . . . . . . . . . . . . . . . . . . . . . . . . 256

6.3 ITCAM for J2EE Operations usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2566.3.1 Setting up historical collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2576.3.2 Setting up target systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2576.3.3 Workspace samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Chapter 7. ITCAM for Internet Service Monitoring . . . . . . . . . . . . . . . . . . 265

7.1 Internet service monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2667.2 ITCAM for Internet Service Monitoring architecture . . . . . . . . . . . . . . . . 2667.3 Installing ITCAM for Internet Service Monitoring. . . . . . . . . . . . . . . . . . . 268

7.3.1 Installing Netcool license server . . . . . . . . . . . . . . . . . . . . . . . . . . . 268



Contents vii


7.3.2 Installing Internet Service Monitors. . . . . . . . . . . . . . . . . . . . . . . . . 2707.3.3 Problem determination and log files . . . . . . . . . . . . . . . . . . . . . . . . 275

7.4 Configuration and usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2777.4.1 Define profiles and profile elements . . . . . . . . . . . . . . . . . . . . . . . . 2777.4.2 Status reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Chapter 8. ITCAM for SOA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2858.1 ITCAM for SOA overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

8.1.1 Product features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2868.1.2 Product components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2888.1.3 ITCAM for SOA management resources . . . . . . . . . . . . . . . . . . . . 292

8.2 ITCAM for SOA installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2968.2.1 Planning the implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

8.2.2 ITCAM for SOA application support installation . . . . . . . . . . . . . . . 2998.2.3 ITCAM for SOA monitoring agent installation . . . . . . . . . . . . . . . . . 3068.2.4 Enabling the monitoring agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3098.2.5 Configuring warehouse proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3108.2.6 Installing IBM Web Services Navigator. . . . . . . . . . . . . . . . . . . . . . 315

8.3 ITCAM for SOA usage scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3178.3.1 Monitoring Web services calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3178.3.2 Filtering Web services calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3218.3.3 Using workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

8.3.4 Using IBM Web Services Navigator . . . . . . . . . . . . . . . . . . . . . . . . 325

Chapter 9. Implementation of ITCAM products on z/OS . . . . . . . . . . . . . 3439.1 Implementation overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3449.2 The CYN1 subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

9.2.1 CYN1 subsystem definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3469.2.2 Assigning RACF user ID for CYN1PROC. . . . . . . . . . . . . . . . . . . . 3469.2.3 Started task creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3479.2.4 Authorizing SCYNAUTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

9.2.5 SMF customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3479.3 ITCAM for WebSphere data collector . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

9.3.1 Modifying WebSphere started tasks . . . . . . . . . . . . . . . . . . . . . . . . 3499.3.2 Defining the data collector to WebSphere Application Server . . . . 3499.3.3 Problem determination and log files . . . . . . . . . . . . . . . . . . . . . . . . 355

9.4 ITCAM for Response Time Tracking agent . . . . . . . . . . . . . . . . . . . . . . . 3589.4.1 Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3599.4.2 Problem determination and log files . . . . . . . . . . . . . . . . . . . . . . . . 362

9.4.3 J2EE monitoring component on z/OS. . . . . . . . . . . . . . . . . . . . . . . 3639.5 ITCAM for CICS Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3709.5.1 Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3709.5.2 Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371




viii IBM Tivoli Composite Application Manager V6.1 Family Installation, Configuration and Basic Usage

9.5.3 Problem determination and log files . . . . . . . . . . . . . . . . . . . . . . . . 3739.6 ITCAM for IMS Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

9.6.1 Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3749.6.2 Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3759.6.3 Problem determination and log files . . . . . . . . . . . . . . . . . . . . . . . . 377

9.7 ITCAM for SOA management agent for z/OS . . . . . . . . . . . . . . . . . . . . . 3779.7.1 Considerations for the z/OS environment . . . . . . . . . . . . . . . . . . . . 3789.7.2 ITCAM for SOA management agent for z/OS. . . . . . . . . . . . . . . . . 3799.7.3 Enabling CICS data collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389

Chapter 10. Integration scenarios with ITCAM products. . . . . . . . . . . . . 39110.1 ITCAM family integration scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . 39210.2 Deep dive and in-context launch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

10.2.1 Configuring Launch in Context . . . . . . . . . . . . . . . . . . . . . . . . . . . 39310.2.2 Using Launch in Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39510.3 Tivoli Enterprise Portal workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

10.3.1 Designing the workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39710.3.2 Building the navigation tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39810.3.3 Defining the workspace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40310.3.4 Defining Trader main view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40710.3.5 Defining bandung and laredo workspaces . . . . . . . . . . . . . . . . . . 407

10.4 Workflows and situations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421

10.4.1 Situation basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42210.4.2 Workflow basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42210.4.3 Trader workflow design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42410.4.4 Defining workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431

Appendix A. Trader application description . . . . . . . . . . . . . . . . . . . . . . . 437Managed application environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438Back-end systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

IMS implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

CICS implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439DB2 implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440

J2EE back-end system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440Front-end J2EE Web application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441Java desktop application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444

Appendix B. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447Locating the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448

System requirements for downloading the Web material . . . . . . . . . . . . . 448How to use the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453



Contents ix


Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458

Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459




x IBM Tivoli Composite Application Manager V6.1 Family Installation, Configuration and Basic Usage



© Copyright IBM Corp. 2007. All rights reserved. xi

Draft Document for Review March 1, 2007 5:22 pm 7151LOF.fm

Figures

1-1 Composite application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2 IBM Tivoli product portfolio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1-3 Project environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101-4 ITSOTrader application environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112-1 ITCAM for WebSphere and ITCAM for J2EE architecture . . . . . . . . . . . . 162-2 Kernel components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182-3 J2EE data collector structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202-4 Split-server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272-5 ITCAM for WebSphere and ITCAM for J2EE implementation . . . . . . . . . 282-6 Installation startup screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322-7 Defining the installation Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332-8 Inserting the administrative user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

2-9 Create response file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352-10 WebSphere data collector installation first steps . . . . . . . . . . . . . . . . . . 372-11 Configure the data collector for the managing server . . . . . . . . . . . . . . . 382-12 WebSphere configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402-13 JBOSS J2EE data collector configuration. . . . . . . . . . . . . . . . . . . . . . . . 422-14 JBoss server startup script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432-15 Apache Server Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

2-16 ITCAM for WebSphere integration with Tivoli Enterprise Monitoring Agent45

2-17 Tivoli Enterprise Monitoring Agent Welcome window . . . . . . . . . . . . . . . 472-18 Tivoli Enterprise Monitoring Agent components . . . . . . . . . . . . . . . . . . . 482-19 Data collector configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532-20 Default monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542-21 Monitoring on demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

2-22 Create user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562-23 Server Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

2-24 Creating operator oper1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593-1 Enterprise overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633-2 Modify server group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653-3 Group Overview display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Note to Author: This is an optional file and is not required for publication. If this file is

not essential to your readers, delete it from your book. Open .book → select the file→ Edit→ Delete File from Book



7151LOF.fm Draft Document for Review March 1, 2007 5:22 pm

xii IBM Tivoli Composite Application Manager V6.1 Family Installation, Configuration and Basic Usage

3-4 Server overview display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673-5 Server Activity Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683-6 Recent Requests tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693-7 Tool icons to launch Server Activity Display . . . . . . . . . . . . . . . . . . . . . . . 703-8 Top Reports - Top Requests Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

3-9 Top Reports - top CPU intensive requests . . . . . . . . . . . . . . . . . . . . . . . . 733-10 Report filtering options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743-11 Response time of requests by hour . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753-12 Decomposition Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763-13 Sorted detail CSMI report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773-14 Flow View for the transaction in question . . . . . . . . . . . . . . . . . . . . . . . . 783-15 Method detail report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793-16 Decomposition report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

3-17 Flow view TraderCICSServices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823-18 CSMI transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833-19 Flow view CICS transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843-20 In-flight request list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853-21 Incomplete TraderCICSService . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863-22 Incomplete CICS transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873-23 WebSphere App Server workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893-24 Garbage collection normal view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903-25 Garbage collection poor performance. . . . . . . . . . . . . . . . . . . . . . . . . . . 91

3-26 Garbage collection high heap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923-27 TEP Web application view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933-28 Tivoli Enterprise Monitoring Server historical processing . . . . . . . . . . . . 953-29 ITCAM for WebSphere - History collection configuration . . . . . . . . . . . . 963-30 Historical information with TEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973-31 Enterprise overview showing active JBoss . . . . . . . . . . . . . . . . . . . . . . . 993-32 JBOSS configured for ITCAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

3-33 Request detail of recent requests of sample application. . . . . . . . . . . . 100

3-34 Create application trap - step 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013-35 Create application trap - step 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013-36 Create application trap - step 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023-37 Create application trap - step 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033-38 Activate application trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043-39 Trap and Alert management - active trap list . . . . . . . . . . . . . . . . . . . . 1053-40 Alerts and events management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

3-41 Trap method trace - summary view. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063-42 Trap method trace - drill down view . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

3-43 Trap method trace - flow view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1084-1 ITCAM for Response Time Tracking components . . . . . . . . . . . . . . . . . 1104-2 Stand-alone management server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114-3 Clustered management server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112



Figures xiii


4-4 Store-and-forward agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134-5 Multiple store-and-forward agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134-6 Management agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144-7 QoS processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1154-8 Mainframe management agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

4-9 Tivoli Enterprise Monitoring Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174-10 Arm concepts: simple application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1184-11 ARM concepts: complex application . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194-12 STI agent groups for multiple applications . . . . . . . . . . . . . . . . . . . . . . 1224-13 ITCAM for Response Time Tracking configuration . . . . . . . . . . . . . . . . 1294-14 LaunchPad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1314-15 Installation path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324-16 WebSphere Application Server installation . . . . . . . . . . . . . . . . . . . . . . 132

4-17 Port and SSL usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334-18 Global security enable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1344-19 WebSphere Application Server parameters . . . . . . . . . . . . . . . . . . . . . 1344-20 Installation DB2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1354-21 DB2 admin user account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1354-22 DB2 fence user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1364-23 db2 instance user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1364-24 Installation image location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1374-25 Product installation directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

4-26 Management server console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1384-27 Installation path for store-and-forward agent . . . . . . . . . . . . . . . . . . . . 1414-28 Store-and-forward agent attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1424-29 Additional store-and-forward agent properties . . . . . . . . . . . . . . . . . . . 1434-30 WebSphere Edge Component CD image . . . . . . . . . . . . . . . . . . . . . . . 1444-31 Component permission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1454-32 Management agent option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

4-33 User account for management agent . . . . . . . . . . . . . . . . . . . . . . . . . . 147

4-34 Launching for ITCAM for WebSphere Data Collector installation . . . . . 1474-35 The fix pack installation wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1484-36 Complete agent updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1504-37 Tivoli Enterprise Monitoring Agent welcome window . . . . . . . . . . . . . . 1534-38 Tivoli Enterprise Monitoring Agent components . . . . . . . . . . . . . . . . . . 1544-39 Monitoring components assignments . . . . . . . . . . . . . . . . . . . . . . . . . . 1624-40 Select option for importing a Rational license file . . . . . . . . . . . . . . . . . 163

4-41 Import ibm_robot.upd file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1634-42 Confirm import file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

4-43 Choose agent for deploying Generic Windows. . . . . . . . . . . . . . . . . . . 1654-44 Deployment information for Generic Windows . . . . . . . . . . . . . . . . . . . 1654-45 Complete the Generic Windows deployment . . . . . . . . . . . . . . . . . . . . 1664-46 Deploy Client Application Tracker component . . . . . . . . . . . . . . . . . . . 167




xiv IBM Tivoli Composite Application Manager V6.1 Family Installation, Configuration and Basic Usage

4-47 Choose J2EE deployment method . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1684-48 J2EE discovery criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1694-49 Deploy J2EE monitoring component. . . . . . . . . . . . . . . . . . . . . . . . . . . 1704-50 Required informations to deploy JBoss. . . . . . . . . . . . . . . . . . . . . . . . . 1714-51 Required informations to deploy Tomcat . . . . . . . . . . . . . . . . . . . . . . . 171

4-52 Required informations to deploy Quality of Service . . . . . . . . . . . . . . . 1734-53 Select agent to deploy STI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1744-54 Installation Network Monitor Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1754-55 Installing the Web Response Monitor on the Quality of Service . . . . . . 1764-56 Required informations to deploy Web Response Monitor. . . . . . . . . . . 1774-57 Deploying Generic Playback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1784-58 Deploying ARM Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1794-59 Default schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

4-60 Configure discovery and listening schedule . . . . . . . . . . . . . . . . . . . . . 1824-61 Configure robotic monitor schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . 1834-62 Reporting groups list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1844-63 Default agent group list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1864-64 Configure agent group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1874-65 New user assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1884-66 Role definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1894-67 Task access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1904-68 Role definitions list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

5-1 Application monitoring flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1945-2 J2EE servlet discovery settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1965-3 J2EE web services discovery settings . . . . . . . . . . . . . . . . . . . . . . . . . . 1975-4 Discovered J2EE transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1985-5 getCompanies Web Services listening monitor settings . . . . . . . . . . . . . 1995-6 J2EE transaction node overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2005-7 Break down in srv178 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

5-8 Web Services Web application modules. . . . . . . . . . . . . . . . . . . . . . . . . 201

5-9 J2C break down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2025-10 CICS transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2025-11 QoS discovery settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2035-12 Discovered QoS transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2045-13 QoS listening monitor settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2055-14 Transaction Topology by the QoS listening monitor . . . . . . . . . . . . . . . 2065-15 STI Recorder installation configuration for connecting server. . . . . . . . 207

5-16 STI recording display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2085-17 Edit robotic script display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

5-18 STI robotic monitor settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2105-19 STI thresholds settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2115-20 Example QoS threshold in transaction topology . . . . . . . . . . . . . . . . . . 2125-21 STI robotic monitor report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

f f 7151LOF f



Figures xv


5-22 Component events display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2145-23 Transaction topology by the STI robotic monitor. . . . . . . . . . . . . . . . . . 2155-24 Break down STI transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2165-25 Drill down with ITCAM for WebSphere/J2EE in monitoring component 2175-26 Example Page Analyzer Viewer report . . . . . . . . . . . . . . . . . . . . . . . . . 218

5-27 Create the Web Response Monitor discovery. . . . . . . . . . . . . . . . . . . . 2195-28 The Web Response Monitor discovery settings . . . . . . . . . . . . . . . . . . 2205-29 Discovered web transactions by the Web Response Monitor. . . . . . . . 2215-30 The Web Response Monitor listening monitor settings. . . . . . . . . . . . . 2225-31 Transaction topoloty by the Web Response Monitor listening monitor . 2235-32 Starting record GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2245-33 Created transaction script by the Rational Robot . . . . . . . . . . . . . . . . . 2255-34 Uploading the recorded transaction by Rational Robot. . . . . . . . . . . . . 226

5-35 Generic Windows - GUI robotic monitor settings . . . . . . . . . . . . . . . . . 2275-36 Sample transaction topology report for the GenWin robotic monitor . . 2285-37 J2EE transaction topology of JBoss . . . . . . . . . . . . . . . . . . . . . . . . . . . 2295-38 J2EE transaction topology of Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . 2295-39 Sample Java application for ARM monitor . . . . . . . . . . . . . . . . . . . . . . 2305-40 ARM discovery settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2345-41 Discovered the ARM instrumentation application by the ARM discovery2355-42 ARM listening monitor settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2365-43 Sample application transaction topology. . . . . . . . . . . . . . . . . . . . . . . . 237

5-44 Behavior modules directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2385-45 Restart the management agent using services. . . . . . . . . . . . . . . . . . . 2395-46 Execute IBM PCOMM emulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2405-47 Discovered the IBM PCOMM application by the ARM discovery . . . . . 2415-48 Client Application Tracker listening monitor settings for CAT PCOM . . 2425-49 Transaction topology by the Client Application Tracker monitoring

component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

5-50 Generic Playback robotic monitor settings . . . . . . . . . . . . . . . . . . . . . . 244

5-51 The Generic Playback report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2455-52 Creating robotic script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2465-53 Generic Playback robotic monitor settings with robotic script. . . . . . . . 2475-54 Response Time Tracking portal workspace. . . . . . . . . . . . . . . . . . . . . . 2485-55 Response Time Tracking Agent Policy Groups . . . . . . . . . . . . . . . . . . 2495-56 Policy status display for policy group . . . . . . . . . . . . . . . . . . . . . . . . . . 2505-57 STI_QoS_TraderWeb robotic monitor status display . . . . . . . . . . . . . . 251

5-58 Display the agent availability historical data in Tivoli Enterprise Portal. 2526-1 ITCAM for J2EE Operations concepts . . . . . . . . . . . . . . . . . . . . . . . . . . 254

6-2 ITCAM for J2EE Operations console menu . . . . . . . . . . . . . . . . . . . . . . 2556-3 Monitoring ITCAM for J2EE Operations . . . . . . . . . . . . . . . . . . . . . . . . . 2586-4 ITCAM for J2EE Operations workspace . . . . . . . . . . . . . . . . . . . . . . . . . 2596-5 ITCAM for J2EE Operations workspaces . . . . . . . . . . . . . . . . . . . . . . . . 259

7151LOF fm D ft D t f R i M h 1 2007 5 22




xvi IBM Tivoli Composite Application Manager V6.1 Family Installation, Configuration and Basic Usage

6-6 JVM runtime workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2606-7 System workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2616-8 Web application summary workspace. . . . . . . . . . . . . . . . . . . . . . . . . . . 2626-9 Transactions workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2637-1 ITCAM for Internet Service Monitoring architecture . . . . . . . . . . . . . . . . 267

7-2 Installation review of Netcool/License server . . . . . . . . . . . . . . . . . . . . . 2697-3 Command nc_print_license. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2707-4 Netcool/Internet Service Monitor welcome dialog. . . . . . . . . . . . . . . . . . 2717-5 Object server default configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2727-6 Configure ISMServer user ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2737-7 Configure ISMServer settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2747-8 Installation review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2757-9 ITCAM for Internet Service Monitoring login page . . . . . . . . . . . . . . . . . 278

7-10 Netcool/Internet Service Monitor - View profiles . . . . . . . . . . . . . . . . . . 2787-11 Profile page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2797-12 Selecting the type of protocol to monitor. . . . . . . . . . . . . . . . . . . . . . . . 2797-13 Editing an HTTP-element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2807-14 Profile element pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2817-15 Service Level Agreement report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2827-16 View current status report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2837-17 Fine grained timings statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2848-1 ITCAM for SOA structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

8-2 Web Services Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2908-3 Navigator in the workspace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2938-4 Installation drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3008-5 Installation features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3018-6 Application support component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3028-7 Installation action list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3038-8 Configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

8-9 TEMA hub configuration.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3058-10 TEMA configuration part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

8-11 TEMA configuration part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3068-12 Manage Tivoli Monitoring Services window . . . . . . . . . . . . . . . . . . . . . 3118-13 Warehouse proxy configuration - TEMS settings . . . . . . . . . . . . . . . . . 3128-14 Warehouse proxy configuration - database settings . . . . . . . . . . . . . . . 3138-15 Configuring historical collection for ITCAM for SOA . . . . . . . . . . . . . . . 3148-16 IBM Web Services Navigator installation . . . . . . . . . . . . . . . . . . . . . . . 315

8-17 Initial help window for IBM Web Services Navigator. . . . . . . . . . . . . . . 3168-18 Empty IBM Web Services Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

8-19 Primary workspace for ITCAM for SOA . . . . . . . . . . . . . . . . . . . . . . . . 3188-20 Primary workspace for ITCAM for SOA . . . . . . . . . . . . . . . . . . . . . . . . 3198-21 Primary workspace for ITCAM for SOA . . . . . . . . . . . . . . . . . . . . . . . . 3208-22 Primary workspace for ITCAM for SOA . . . . . . . . . . . . . . . . . . . . . . . . 321

Draft Document for Review March 1 2007 5:22 pm 7151LOF fm



Figures xvii


8-23 Invoking action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3228-24 Action parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3228-25 Rejected Web services call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3238-26 Rejected Web services call faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3248-27 Removing filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

8-28 Workflow for ITCAM for SOA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3258-29 Creating new connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3268-30 New connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3278-31 WAREHOUS database information . . . . . . . . . . . . . . . . . . . . . . . . . . . 3288-32 Defining a new project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3298-33 Importing ITCAM for SOA data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3308-34 Import dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3318-35 Service topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

8-36 Monitor control action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3338-37 Monitor list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3348-38 Log files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3358-39 Creating a project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3368-40 Importing log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3378-41 Service topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3388-42 Operation summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3388-43 Flow patterns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3398-44 Message content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

8-45 Flow patterns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3419-1 z/OS overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3449-2 J2EE data collector runtime configuration directory . . . . . . . . . . . . . . . . 3549-3 ITCAM for WebSphere unconfigured data collectors . . . . . . . . . . . . . . . 3549-4 Custom Properties for Servant address space JVM . . . . . . . . . . . . . . . . 3569-5 Custom Services list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3579-6 Probe service setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

9-7 All agents installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3629-8 Deploy J2EE Agent on z/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

9-9 Agent Deployment - Choose J2EE Deployment Method . . . . . . . . . . . . 3659-10 Agent Deployment - J2EE Discovery Criteria . . . . . . . . . . . . . . . . . . . . 3659-11 J2EE component directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3669-12 JVM initialization error with tmtp management agent . . . . . . . . . . . . . . 3669-13 Example of jvmpiagents.properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3689-14 Indicator for existence of an unsupported JVMPI agent . . . . . . . . . . . . 369

9-15 CICS data collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3719-16 IMS data collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374

9-17 Configuration tool processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3809-18 Configuration tool page - main menu . . . . . . . . . . . . . . . . . . . . . . . . . . 3819-19 Configuration tool page - product selection. . . . . . . . . . . . . . . . . . . . . . 3819-20 Configuration tool page - creation of full RTE . . . . . . . . . . . . . . . . . . . . 382

7151LOF fm Draft Document for Review March 1 2007 5:22 pm




xviii IBM Tivoli Composite Application Manager V6.1 Family Installation, Configuration and Basic Usage

9-21 Configuration tool page - defining an RTE . . . . . . . . . . . . . . . . . . . . . . 3829-22 Configuration tool page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3839-23 Configuration tool page - ITCAM for SOA steps . . . . . . . . . . . . . . . . . . 3849-24 Configuration tool page - configuration parameter . . . . . . . . . . . . . . . . 3859-25 Configuration tool page - agent address space . . . . . . . . . . . . . . . . . . 385

9-26 Configuration tool page - CMS values . . . . . . . . . . . . . . . . . . . . . . . . . 3869-27 Configuration tool page - IP.PIPE configuration . . . . . . . . . . . . . . . . . . 3879-28 Configuration tool page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38810-1 Launch in Context configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . 39310-2 Launch in context configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39410-3 Launch in context pop-up menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39510-4 Launch in context WebSphere window. . . . . . . . . . . . . . . . . . . . . . . . . 39610-5 TEP Physical view example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398

10-6 Navigator view edit window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39910-7 Create new logical view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39910-8 Bandung1 navigator managed systems . . . . . . . . . . . . . . . . . . . . . . . . 40010-9 Laredo1 navigator managed systems. . . . . . . . . . . . . . . . . . . . . . . . . . 40110-10 Final navigator dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40210-11 Workspace not defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40310-12 Trader workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40410-13 Laredo workspace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40510-14 Bandung workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406

10-15 Portlet components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40710-16 Workspace areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40810-17 Query assignment confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40910-18 Empty portlet property page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41010-19 Query editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41110-20 Portlet filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41210-21 Heading text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

10-22 Circular gauge setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41410-23 Linear gauge settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415

10-24 Bar chart settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41510-25 Legend customization for bar chart. . . . . . . . . . . . . . . . . . . . . . . . . . . 41610-26 Name for new query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41610-27 Query specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41710-28 Laredo policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41710-29 Getting policy group ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418

10-30 Query name and category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41910-31 Query attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420

10-32 Setting condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42110-33 Trader workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42410-34 Situation editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42710-35 New situation dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428




Figures xix


10-36 Selecting attribute group and attributes . . . . . . . . . . . . . . . . . . . . . . . 42810-37 ITCAM for Response Time Tracking condition . . . . . . . . . . . . . . . . . . 42910-38 ITCAM for SOA condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42910-39 ITCAM for WebSphere condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43010-40 ITCAM for WebSphere for JDBC call condition . . . . . . . . . . . . . . . . . 430

10-41 Workflow editor initial window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43110-42 New empty Trader workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43210-43 Workflow with only IMS components . . . . . . . . . . . . . . . . . . . . . . . . . 43310-44 Completed workflow - recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43410-45 Completed workflow - failure for database . . . . . . . . . . . . . . . . . . . . . 43410-46 Completed workflow - failure for CICS . . . . . . . . . . . . . . . . . . . . . . . . 43510-47 Completed workflow - failure for front end . . . . . . . . . . . . . . . . . . . . . 43510-48 Completed workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436

A-1 Application environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438A-2 Entity diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439A-3 Login page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441A-4 List Company page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442A-5 Quotes window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443A-6 Login dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444A-7 Company listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444A-8 Quote window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445B-1 Application environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448




p

xx IBM Tivoli Composite Application Manager V6.1 Family Installation, Configuration and Basic Usage

Draft Document for Review March 1, 2007 5:22 pm 7151LOT.fm



© Copyright IBM Corp. 2007. All rights reserved. xxi

Tables

4-1 Terminoloy changes in this release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1244-2 Determing points for the monitoring components deployment . . . . . . . . 127

4-3 ITCAM for Response Time Tracking monitoring components . . . . . . . . 1604-4 Defatul roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1897-1 Netcool/Internet Service Monitor installation options and settings . . . . . 2728-1 ITCAM for SOA situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29510-1 Workflow components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42210-2 New situations list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42510-3 Condition for problem source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433



7151LOT.fm Draft Document for Review March 1, 2007 5:22 pm



xxii IBM Tivoli Composite Application Manager V6.1 Family Installation, Configuration and Basic Usage

Draft Document for Review March 1, 2007 5:22 pm 7151LOE.fm



© Copyright IBM Corp. 2007. All rights reserved. xxiii

Examples

2-1 Excerpt of cynlogging.properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242-2 Memory size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2-3 Port usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272-4 Modification to httpd.conf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432-5 Listing of the Tivoli Enterprise Monitoring Agent installation. . . . . . . . . . . 492-6 Configuration of Tivoli Enterprise Monitoring Agent . . . . . . . . . . . . . . . . . 514-1 Installation DB2 fix pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1394-2 Running install.sh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1554-3 Running itmcmd config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1584-4 Running itmcmd agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1595-1 Import ARM instrumentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

5-2 ARM instrumentation variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2305-3 Initializing ARM environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2315-4 Starting ARM transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2325-5 Stopping ARM transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2325-6 Complex part of the sample application . . . . . . . . . . . . . . . . . . . . . . . . . 2325-7 Modify tn3270.rul file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2387-1 The bridge.props . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2767-2 bridge.props with Object Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2767-3 Starting databridge manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

8-1 Linux installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3078-2 Configuration of agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3088-3 Running log assembler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3359-1 Defining IEFU83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3479-2 Defining SMF exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3489-3 Adding HEAP parameter for servant address space . . . . . . . . . . . . . . . 349

9-4 Running setupwas.sh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3509-5 The setupEnv.sh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

9-6 Our zos.properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3609-7 Configuring the management agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3609-8 Creating links for ARM libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3619-9 Check the Java virtual machine setting. . . . . . . . . . . . . . . . . . . . . . . . . . 367



7151LOE.fm Draft Document for Review March 1, 2007 5:22 pm



xxiv IBM Tivoli Composite Application Manager V6.1 Family Installation, Configuration and Basic Usage

9-10 Running setupcics.sh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3719-11 Running setupims.sh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3759-12 TCP/IP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3789-13 CICS handler definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389

Draft Document for Review March 1, 2007 5:22 pm 7151spec.fm



© Copyright IBM Corp. 2007. All rights reserved. xxv

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consultyour local IBM representative for information on the products and services currently available in your area.Any reference to an IBM product, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead. However, it is the user'sresponsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document.The furnishing of this document does not give you any license to these patents. You can send licenseinquiries, in writing, to:

IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where suchprovisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimerof express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically madeto the information herein; these changes will be incorporated in new editions of the publication. IBM maymake improvements and/or changes in the product(s) and/or the program(s) described in this publication at

any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in anymanner serve as an endorsement of those Web sites. The materials at those Web sites are not part of thematerials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements or other publicly available sources. IBM has not tested those products and cannot confirmthe accuracy of performance, compatibility or any other claims related to non-IBM products. Questions onthe capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate themas completely as possible, the examples include the names of individuals, companies, brands, and products.All of these names are fictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs inany form without payment to IBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operating platform for which thesample programs are written. These examples have not been thoroughly tested under all conditions. IBM,therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

7151spec.fm Draft Document for Review March 1, 2007 5:22 pm



xxvi IBM Tivoli Composite Application Manager V6.1 Family Installation, Configuration and Basic Usage

Trademarks

The following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both:

Redbooks (logo) ™ibm.com® z/OS® AIX® Candle® CICS® Database 2™DataPower® DB2 Universal Database™DB2®

ETE™ETEWatch® IBM® IMS™Lotus Notes® Lotus® Monitoring On Demand® MVS™Netcool/Internet Service

Monitors®

Netcool® Notes® OMEGAMON® Rational® Redbooks™RACF® Tivoli Enterprise™Tivoli® WebSphere®

The following terms are trademarks of other companies:

SAP NetWeaver, SAP, and SAP logos are trademarks or registered trademarks of SAP AG in Germany andin several other countries.

Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or itsaffiliates.

ITIL is a registered trademark, and a registered community trademark of the Office of GovernmentCommerce, and is registered in the U.S. Patent and Trademark Office.

ALERTS, and ALPHABLOX logo are registered trademarks of Alphablox Corporation in the United States,other countries, or both.

EJB, Java, Java Web Server, JDBC, JMX, JRE, JVM, J2EE, Solaris, Sun, Sun Java, and all Java-basedtrademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Internet Explorer, Microsoft, Outlook, Windows, and the Windows logo are trademarks of MicrosoftCorporation in the United States, other countries, or both.

Intel, Pentium, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarksof Intel Corporation or its subsidiaries in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.

Draft Document for Review March 1, 2007 5:22 pm 7151pref.fm



© Copyright IBM Corp. 2007. All rights reserved. xxvii

Preface

This IBM® Redbook describes the IBM Tivoli® Composite Application Managerfamily of products. The Composite Application Manager currently consists of:

ITCAM for WebSphere ITCAM for Response Time Tracking ITCAM for SOA ITCAM for Internet Service Monitoring ITCAM for J2EE ITCAM for J2EE Operations ITCAM for CICS Transactions ITCAM for IMS Transactions

The aim of the Composite Application Manager is to simplify and enhancedistributed application management. Application components can reside onmultiple servers, across different platforms and J2EE™ environments, eventhrough mainframes. The complexity of understanding and solvingapplication-related problems, typically around performance issues, requires acohesive set of tools to be able to provide an end-to-end view of the application.

The discussion that we provide in this book mainly consists of basic installationand configuration of the products. The discussion is aimed at augmenting theinformation provided in the product manuals. Readers should consult theappropriate product manual before starting to implement these products.

Usage scenarios are provided in this book as a demonstration of using theseproducts in our sample environment. We use a single application environmentthat can be managed by all of the products.

The team that wrote this redbook

This redbook was produced by a team of specialists from around the worldworking at the International Technical Support Organization, PoughkeepsieCenter.

7151pref.fm Draft Document for Review March 1, 2007 5:22 pm



xxviii IBM Tivoli Composite Application Manager V6.1 Family Installation, Configuration and Basic

Figure 1 Left to right: Sören Eickhoff, Michael Stahl, Budi Darmawan and Lee Hwa Yong

Budi Darmawan is a Project Leader at the International Technical SupportOrganization, Austin Center. He writes extensively and teaches IBM classesworldwide on all areas of systems management; primarily application

management, business service management and workload scheduling. Before joining the ITSO 8 years ago, Budi worked in IBM Indonesia as lead implementorand solution architect. His current interests are J2EE and SOA applicationmanagement, z/OS® integration and business system management.

Lee Hwa Yong is a Field Technical Sales Specialist from IBM Korea.

Michael Stahl is a IT-Specialist working at DATEV eG, Germany. His backgroundin IT extends for 14 years, covering software development, systems management

and automation on diverse platforms. Michael’s areas of expertise include weband application server administration, z/OS system programming, performanceand availability management.

Sören Eickhoff is an IT-Specialist in the IBM Software Group in Germany. Hisresponsibility spans the ITCAM product family as well as license and contractmanagement on z/OS. He holds a diploma in information management and anBachelor of Arts.

Thanks to the following people for their contributions to this project:

Bob Haimowitz, Richard M Conway, EditorInternational Technical Support Organization, Poughkeepsie Center

Draft Document for Review March 1, 2007 5:22 pm 7151pref.fm



Preface xxix

Rebecca Poole, Adrian Mitu, Erik Klein, Michael BaconIBM Software Group

Danilo Rezende Araujo, Christian Minarovits, Kimberly Nguyen-TheunissenOriginal authors of the IBM Tivoli Composite Application Manager V6.0 Family

redbook.

Become a published author

Join us for a two- to six-week residency program! Help write an IBM Redbookdealing with specific products or solutions, while getting hands-on experiencewith leading-edge technologies. You'll have the opportunity to team with IBMtechnical professionals, Business Partners, and Clients.

Your efforts will help increase product acceptance and customer satisfaction. Asa bonus, you'll develop a network of contacts in IBM development labs, andincrease your productivity and marketability.

Find out more about the residency program, browse the residency index, andapply online at:

ibm.com/redbooks/residencies.html

Comments welcome

Your comments are important to us!

We want our Redbooks™ to be as helpful as possible. Send us your commentsabout this or other Redbooks in one of the following ways:

Use the online Contact us review redbook form found at:

ibm.com/redbooks

Send your comments in an email to:

[email protected]

Mail your comments to:

IBM Corporation, International Technical Support OrganizationDept. HYTD Mail Station P0992455 South Road

Poughkeepsie, NY 12601-5400

7151pref.fm Draft Document for Review March 1, 2007 5:22 pm

http://www.redbooks.ibm.com/residencies.html




http://www.redbooks.ibm.com/contacts.html

http://www.redbooks.ibm.com/contacts.html







xxx IBM Tivoli Composite Application Manager V6.1 Family Installation, Configuration and Basic Usage

Draft Document for Review March 1, 2007 5:22 pm 7151chang.fm



© Copyright IBM Corp. 2007. All rights reserved. xxxi

Summary of changes

This section describes the technical changes made in this edition of the book andin previous editions. This edition may also include minor corrections and editorialchanges that are not identified.

Summary of Changesfor SG24-7151-01for IBM Tivoli Composite Application Manager V6.1 Family Installation,Configuration and Basic Usageas created or updated on March 1, 2007.

February 2007, Second Edition

This revision reflects the addition, deletion, or modification of new and changedinformation described below.

New information

Inclusion of IBM Tivoli Composite Application Manager for J2EE, IBM TivoliComposite Application Manager for Internet Service Monitor and IBM TivoliComposite Application Manager for J2EE Operations.

Stream lined chapter structure, instead of explaining each product in differentpart, each chapter now covers different products.

Changed information The redbook now covers Version 6.1 of the IBM Tivoli Composite Application

Manager family

Various changes in screen shots and product capabilities related to newversion.

7151chang.fm Draft Document for Review March 1, 2007 5:22 pm



xxxii IBM Tivoli Composite Application Manager V6.1 Family Installation, Configuration and Basic

Draft Document for Review March 1, 2007 5:22 pm 7151ch01-introduction.fm



© Copyright IBM Corp. 2007. All rights reserved. 1

Chapter 1. IBM Tivoli CompositeApplication Manager V6.1overview

This chapter introduces the IBM Tivoli Composite Application Manager productfamily. These products are aimed to manage applications instead of the moretraditional resource management. Application management requires themanagement to understand the application behavior instead of looking for justthe resources that the application uses. The discussion is divided into:

1.1, “Application management background and issues” on page 2

1.2, “IBM Tivoli Composite Application Manager” on page 3

1.3, “Project environment” on page 9

1.4, “Document organization” on page 11

1

7151ch01-introduction.fm Draft Document for Review March 1, 2007 5:22 pm

1 1 Application management background and issues



2 IBM Tivoli Composite Application Manager V6.1 Family Installation, Configuration and Basic Usage

1.1 Application management background and issues

Nowadays, businesses requires computer based application. Businessprocesses are highly dependent on the application that it uses, without theapplications, the business processes can no longer function. The traditionalpaper based manual processes has been completely replaced by computerbased application.

As the applications health is now almost synonymous with the business processhealth, managing the application to optimize its health is critical for the overallbusiness survival. Application health can be viewed as a multi-facets problems.The health can consists of the following:

Availability: the application must be available to be used

Performance: the application must perform in a reasonable time Integrity: the application must handle the information entered correctly Reliability: the application must be able to recover the data that it has

Fromt the above list, integrity and reliability are typically handled inside theapplication and uses several redundant storage and commit mechanism toachieve that. Sometimes off-line backup process is added to manage datareliability.

On the other hand, the availability and performance of the application isdependent on many of the component that supports the application. This iscritical for a major application that consists of multiple different interconnectedcomponents.

A typical e-business distributed application can have the components spreadsover several clustered application server that are interconnected using severaldifferent mechanism. These distributed interconnected applications are referredcollectively as composite applications. A sample complex application can beseen in Figure 1-1 on page 2.

Figure 1-1 Composite application

Web

Services

MQ CTG

IMS4J

Web

Services

IIOP

IIOP

WebSphere

Application

Server

Tomcat

WebSphere

Application

Server

IMS

CICS

DB2

DB2

WebSphere

Application

Server

WebSphere

Application

Server


Managing a composite application as shown in Figure 1-1 requires a



Chapter 1. IBM Tivoli Composite Application Manager V6.1 overview 3

g g p pp g qmanagement of both the underlying resources and the understanding on how thecomponents interact with another. Understanding the application is performingpoorly from the end user view does not necessarily means that theuser-interaction application server that has a problem, a back-end server may be

suffering some lack of resources.

The composite application management aims to be able to understand theserelationship and present the root-cause of the application problem. This includesdecomposing the application and understanding the individual componentsresource needs to be able to pin-point resource problem on an applicationcontext.

The IBM Tivoli Composite Application Manager family is aimed to address thecomposite application management issues above. It allows different componentsto be addressed and transactions to be decomposed to get to the root-cause ofthe problem.

1.2 IBM Tivoli Composite Application Manager

IBM Tivoli Composite Application Manager is a family of product that is part ofthe application management building block of the IBM Tivoli portfolio. The system

management portfolio of IBM Tivoli consists of a set of systems managementsuite to manage your entire IT infrastructure.

The IBM Tivoli product suite is in-line with the Information TechnologyInfrastructure Library (ITIL®) specification. With the launch of IBM Tivoli ServiceManagement suite of product the overall IBM Tivoli Portfolio can conceptuallyshown similar to Figure 1-2 on page 3.

Figure 1-2 IBM Tivoli product portfolio

IBM Service Management

Best Practices

Process Management

Service Management

Platform

Operational

Management

IT CRM &

Business

Management

Service

Delivery &

Support

Service

Deployment

Information

Management

Business

Resilience

Business

Application

Management

Server, Network &

Device Management

Storage

Management

Security

Management

Change and Configuration Management Database


Within Figure 1-2, the application management product resides in the




g pp g pavailability management discipline. For more information on other Tivoli productsuite, visit the Tivoli homepage at

http://www.ibm.com/tivoli

The application management product suite consists of the following products: IBM Tivoli Composite Application Manager for WebSphere® IBM Tivoli Composite Application Manager for J2EE IBM Tivoli Composite Application Manager for Response Time Tracking IBM Tivoli Composite Application Manager for J2EE Operations IBM Tivoli Composite Application Manager for Internet Service Monitor IBM Tivoli Composite Application Manager for SOA IBM Tivoli Composite Application Manager for CICS® Transactions IBM Tivoli Composite Application Manager for IMS™ Transactions OMEGAMON® XE for Messaging

We will discuss the individual products in the subsequent sections.

1.2.1 ITCAM for WebSphere

The IBM Tivoli Composite Application Manager for WebSphere (ITCAM forWebSphere) is an evolution from WebSphere Studio Application Monitor and

OMEGAMON XE for WebSphere Application Server.

ITCAM for WebSphere allows you to analyze the health of WebSphereApplication Server and the transactions that are invoked in it. It is able to tracethe transaction execution to the detailed method level information and connectstransactions that spawns from one application server and invoke services fromother application servers, including mainframe applications in IMS or CICS.

ITCAM for WebSphere provides a flexible level of monitoring, from annon-intrusive production ready monitor, to a detailed deep-dive tracing forproblems on locking or even memory leaks. ITCAM for WebSphere provides aseparate interactive Web console and also allows monitoring data to bedisplayed on Tivoli Enterprise™ Portal.

The current ITCAM for WebSphere Version 6.1 provides additional functions,such as:

Integration with IBM Tivoli Service Manager by providing Web Servicesinterface to get health status

Improved memory leak and locking analysis pages

Problem determination enhancements


Advanced visualization, aggregation, persistence, and correlation of






performance metrics in Tivoli Enterprise Portal

Additional WebSphere server platform support, including WebSphere PortalServer and WebSphere Process Server

Enhanced composite transaction tracing and decomposition

Web session browser to help diagnose session-related problems

For more information, see ITCAM for WebSphere page at:

http://www.ibm.com/software/tivoli/products/composite-application-mgr-websphere/

1.2.2 ITCAM for J2EE

IBM Tivoli Composite Application Manager for J2EE (ITCAM for J2EE) is acomplementary solution for monitoring and managing applications on anon-WebSphere Application Server based J2EE container. This include supportfor WebSphere Application Client J2EE container and non-IBM application

servers, such as: SAP® NetWeaver Oracle® 9i/10i Application Server JBoss Application Server Apache Tomcat BEA WebLogic Server WebSphere Application Server CE

ITCAM for J2EE uses the same interface and technology as ITCAM for

WebSphere. It handles application server specific interface as additional metricsthat are collected from the application servers.

Additional supports are available to monitor Web Servers using Tivoli EnterpriseManagement Agent for Web Servers supporting:

Apache Web Server Sun™ Java™ System Web Server Microsoft Internet Information Server

ITCAM for J2EE allows you to:

View all in-flight J2EE transactions, including composite transactions.

Note: The ITCAM Basic for WebSphere is a restricted version of ITCAM forWebSphere that is bundled with the purchase of some WebSphere Application

Server product.


Evaluate common performance bottlenecks and contributing factors with ant t d bl fi d t h l d t t t i d l t




automated problem finder to help detect, categorize and analyze root causeseasily.

Analyze problematic transactions both historically and in real time, drill downinto the details and share the information with other stakeholders using

built-in, interactive reporting tools that preserve some problem context.

Correlate and profile transactions across multiple subsystems to determinethe precise location and root causes of application failures.

Set traps and alerts to detect and fix potentially troublesome situations beforethey affect end users.

Analyze resource consumption patterns, perform trends or historical analysis,and plan for future growth.

More information of ITCAM for J2EE can be read from:

http://www.ibm.com/software/tivoli/products/composite-application-mgr-itcam-j2ee/

1.2.3 ITCAM for Response Time Tracking

IBM Tivoli Composite Application Manager for Response Time Tracking (ITCAMfor Response Time Tracking) is an evolution from IBM Tivoli Monitoring for

Transaction Performance, Candle® End-to-end Watch, and Web ResponseMonitor.

ITCAM for Response Time Tracking allows monitoring and analysis of applicationtransaction response time. It can provides statistic of response time using ainstrumentation and robotic means. ITCAM for Response Time Tracking allowsanalysis and break down of response time into individual components to quicklypinpoint a response time problem.

ITCAM for Response Time Tracking can decompose transactions from roboticmeans simulating end users, tracking its execution in J2EE application servers allthe way to IMS or CICS back-end. The response time information is presented onthe Web management console or Tivoli Enterprise Portal.

ITCAM for Response Time Tracking allows:

Proactively recognizes, isolates and resolves transaction performanceproblems using robotic and real-time techniques

Enables you to drill down each of the transaction's steps across multiplesystems and measure each transaction component's contribution to overallresponse time


Delivers application topology information to the CCMDB and monitoringstatus to the Availability Process Manager




status to the Availability Process Manager

Integrates Web Response Monitor for real end-user response-time analysis

Provides custom reporting using TEP or direct SQL queries of databaseviews, and organizes reports by application, customer, and location

Enables you to easily reuse Mercury LoadRunner scripts

Offers new tracking support for Business processes written in BPEL runningin WebSphere Process Server; portals in WebSphere Portal Server; J2EEapplications on JBoss and Tomcat; and 64-bit applications, including 64-biteditions of WebSphere Application Server

More information of ITCAM for Response Time Tracking can be found at:

http://www.ibm.com/software/tivoli/products/composite-application-mgr-rtt/

1.2.4 ITCAM for J2EE Operations

IBM Tivoli Composite Application Manager for J2EE Operations (ITCAM for J2EEOperations) is based on Netcool WebSphere or WebLogic Application ServiceMonitor (ASM).

ITCAM for J2EE Operations provides a low overhead monitoring for keyperformance and response time metrics of WebSphere Application Server orBEA WebLogic server using Simple Network Management Protocol (SNMP).The performance metrics can be viewed using the Netcool System ServiceMonitors or from Universal Agent SNMP feature for Tivoli Enterprise Portal.

More information of ITCAM for J2EE Operations can be read from:

http://www.ibm.com/software/tivoli/products/composite-application-mgr-j2ee/

1.2.5 ITCAM for Internet Service Monitoring

IBM Tivoli Composite Application Manager for Internet Service Monitor (ITCAMfor Internet Service Monitoring) is based on Netcool Internet Service Monitor. Itallows monitoring of TCP/IP based services and transaction using a roboticprobe to check whether the service is available or not.

ITCAM for Internet Service Monitoring provides a Web based administrationconsole. It also plugs-in seamlessly to Netcool System Service Monitors.

More information on ITCAM for Internet Service Monitoring can be read from:


http://www.ibm.com/software/tivoli/products/composite-application-mgr-ism/




sm/

1.2.6 ITCAM for SOA

IBM Tivoli Composite Application Manager for SOA (ITCAM for SOA) is a productbased on OMEGAMON platform structure. It monitors, manages and controlsWeb Services and SOAs deployed using a wide range of IBM and third-partysystems.

ITCAM for SOA helps you to:

Proactively recognize and quickly isolate Web service performance problems

Verify that Web services are available and performing to specification

Alert you when Web service performance is degraded

Perform automated service mediation, for example, to reject or re-routecertain requests during periods of heavy load

Report results against committed service levels

Visualize service flows, end-to-end, as they cross the enterprise

Pinpoint source of service bottlenecks

Understand the impact of service problems on business processes

ITCAM for SOA includes the Web Services Navigator, a plug-in to IBM Rational® and other Eclipse-based tools, which provides deep understanding of serviceflows, patterns and relationships to developers and architects using operationaldata from Tivoli Data Warehouse.

ITCAM for SOA is a core component of the IBM SOA Foundation, an integratedand open set of software, best practices, patterns and skills resources to get youstarted with service-oriented architectures.

ITCAM for SOA Version 6.1 supports WebSphere Application Server, BEAWebLogic, Microsoft® Internet Information Server, CICS Transaction Server,WebSphere CE, SAP NetWeaver® and JBoss Application Server.

More information on ITCAM for SOA can be read from:

http://www-306.ibm.com/software/tivoli/products/composite-application-mgr-soa/


1.2.7 ITCAM for CICS Transactions




IBM Tivoli Composite Application Manager for CICS Transaction is the datacollector for ITCAM for Response Time Tracking and ITCAM for WebSphere fortransaction that invokes CICS transaction in the back end. It provides CICSresponse time information and other performance metrics. This is not astandalone product. It has to run with either ITCAM for Response Time Trackingor ITCAM for WebSphere.

1.2.8 ITCAM for IMS Transactions

IBM Tivoli Composite Application Manager for IMS Transaction is the datacollector for ITCAM for Response Time Tracking and ITCAM for WebSphere fortransaction that invokes IMS transaction in the back end. It provides IMS

response time information and other performance metrics. This is not astandalone product. It has to run with either ITCAM for Response Time Trackingor ITCAM for WebSphere.

1.2.9 OMEGAMON XE for Messaging

OMEGAMON XE for Messaging, formerly OMEGAMON XE for WebSphereBusiness Integration is a powerful messaging middleware performance andconfiguration management tool. It allows monitoring and management ofWebSphere MQ based middleware environments.

For more information on OMEGAMON XE for Messaging, refer to:

http://www.ibm.com/software/tivoli/products/omegamon-xe-messaging-dist-sys/

and

http://www.ibm.com/software/tivoli/products/omegamon-xe-messaging-zos/

This product is not discussed in this redbook. Refer to <bart’s book>,SG24-7xxx.

1.3 Project environment

This ITCAM family project is performed in ITSO Austin center. The products areinstalled and used to manage a set of server with a single distributed applicationthat is called ITSOTrader.


1.3.1 Machine environment




The machines that we used in this projects are illustrated in Figure 1-3 onpage 10.

Figure 1-3 Project environment

The project are run mainly using Linux® based servers running RedHatEnterprise Linux V3. The z/OS backend is running on another ITSO lab inPoughkeepsie. As the usage is not necessarily related to the Operating Systemplatform that is used, we decided to limit our environment for least number ofOperating System to be maintained.

Management servers

Managed environment

peoria

RHEL V3

ITCAM for WebSphere

Managing Server

khartoum

RHEL V3

ITCAM for RTT

Management Server

lima

Windows 2003

ITM V6.1

TEMS/TEPS

srv179

RHEL V3

ITCAM for ISM

wtsc67

z/OSsrv176

RHEL V3

srv177

RHEL V3

srv178

RHEL V3


1.3.2 Application environment




The application, ITSOTrader, is a distributed application with the componentsillustrated in Figure 1-4 on page 11.

Figure 1-4 ITSOTrader application environment

The application consists of the following components:

Front end presentation called TraderWebClient that provides client sideaccess. It uses Web Services calls to perform its functions.

Service application that provides the business logic for the application,running in another WebSphere server. This application acts as a Web

Services provider to get the requests. There are three service applicationsthat are available, TraderIMSServices, TraderCICSServices andTraderDB2Services. Each having different data store in the backend.

IMS server on z/OS is accessed using IMS Connect interface.

CICS Transaction Server on z/OS is accessed using CICS TransactionGateway.

DB2® database is accessed using direct JDBC™ calls.

1.4 Document organization

This redbook is organized by products. We discuss individual products in theirown chapters. We specifically pull out the discussion for z/OS-basedimplementation on a separate chapter as most of the reader who wouldimplement the z/OS platform would be systems programmers that would notwant to search through all the pages. The last chapter would address the issue of

integration of these different products.

The chapter structure is:

TraderClientWeb

TraderDBServices

TraderIMSServices

TraderCICSServices

DB2

IMS

CICS

Web Services

Web Services

Web Services

JDBC

IMS Connect

CICS Transaction

Gateway


Chapter 1, “IBM Tivoli Composite Application Manager V6.1 overview” onpage 1




Chapter 2, “ITCAM for WebSphere and ITCAM for J2EE concepts andinstallation” on page 13

Chapter 3, “ITCAM for WebSphere and ITCAM for J2EE usage” on page 61

Chapter 4, “ITCAM for Response Time Tracking concepts and installation” onpage 109

Chapter 5, “ITCAM for Response Time Tracking usage” on page 193

Chapter 6, “ITCAM for J2EE Operations” on page 253

Chapter 7, “ITCAM for Internet Service Monitoring” on page 265

Chapter 8, “ITCAM for SOA” on page 285

Chapter 9, “Implementation of ITCAM products on z/OS” on page 343 Chapter 10, “Integration scenarios with ITCAM products” on page 391

Draft Document for Review March 1, 2007 5:22 pm 7151chWAS-J2EE-intro.fm

2




Chapter 2. ITCAM for WebSphere andITCAM for J2EE conceptsand installation

This chapter describes ITCAM for WebSphere and ITCAM for J2EE. Thediscussion includes:

2.1, “Monitoring J2EE application servers” on page 14

2.2, “Architecture and interconnection” on page 15

2.3, “Implementation overview” on page 24

2.4, “Installation process” on page 30 2.5, “Integration with Tivoli Enterprise Portal” on page 44

2.6, “Initial configuration and operation” on page 52

2

7151chWAS-J2EE-intro.fm Draft Document for Review March 1, 2007 5:22 pm

2.1 Monitoring J2EE application servers




The IBM Tivoli application management solution for J2EE application serverscomes in the form of ITCAM for WebSphere and ITCAM for J2EE. These twoproducts shares the same managing server. ITCAM for WebSphere and ITCAM

for J2EE observes and reports on the health of J2EE-based applications. Theytrack the progress of applications as they traverse through J2EE applicationservers, middleware adapters and transports, and database calls, and on toback-end systems such as CICS or IMS to extract business data or to invokemainframe business processes.

The tracking of applications produces request traces, where the events in arequest’s life are recorded and stored in a monitoring repository database.ITCAM for WebSphere and ITCAM for J2EE captures the CPU and the elapsed

internal times when events are called and when they are exited, measuring as fardown as the CPU times consumed and the elapsed internal times charged toindividual methods in J2EE classes. The methods or events taking the most timeare marked as an application’s parts that deserve attention for runtimeimprovement studies and code optimizations.

ITCAM for WebSphere manages and monitors WebSphere-based applicationservers, while ITCAM for J2EE manages and monitors the following J2EEcontainers:

JBoss Tomcat SAP Netweaver BEA Web Logic Server Oracle AppServer Apache Web Server Sun Java System Webserver Microsoft IIS WebSphere Application Server CE

ITCAM for WebSphere and ITCAM for J2EE does not need modification of anyJ2EE or mainframe application code. The data collectors are using the followingprincipal data sources: Java Virtual Machine Tool Interface (JVMTI) interfacesand primitives. ITCAM for WebSphere also uses WebSphere PerformanceManagement Interface (PMI) and z/OS System Measurement Facility (SMF) 120records. The monitoring data is collected and analyzed to offer a wealth ofinformation about the health of J2EE applications and their servers.

Many system-level performance metrics are collected and reported about J2EEapplication servers. The status of the servers and their resources (particularly atvital checkpoints such as CPU utilization), memory usage, and the status of


internal components such as database connection pools, JVM™ thread pools,EJB™ usage, and request processing statistics can be very important in locatingreal time problems with J2EE applications ITCAM for WebSphere and ITCAM



Chapter 2. ITCAM for WebSphere and ITCAM for J2EE concepts and installation 15

real-time problems with J2EE applications. ITCAM for WebSphere and ITCAMfor J2EE brings attention to these critical indicators with real-time, graphicaldisplays of their values and their trends over spans of time.

2.2 Architecture and interconnection

ITCAM for WebSphere and ITCAM for J2EE is a distributed performancemonitoring application for application servers. Its components are connectedthrough TCP/IP communication. The central component of ITCAM forWebSphere and ITCAM for J2EE, the managing server , is its heart and brain. Itcollects and displays various performance information from application servers.

The application servers run the data collector , which is a collecting agent thatruns in the application server and sends monitoring information to the managingserver. These data collectors operate independently of each other. Figure 2-1 shows the overall architecture of ITCAM for WebSphere and ITCAM for J2EE.





Figure 2-1 ITCAM for WebSphere and ITCAM for J2EE architecture

The Application Monitor comprises two main parts: the managing server and thedata collectors. A data collector agent runs on each monitored application server,whether J2EE, CICS, or IMS, and communicates essential operational data tothe managing server. Unique sampling algorithms maintain low CPU and

network overhead while providing application-specific performance information.The managing server comprises several Java-based components that providethe environment to collect and present management data.

2.2.1 The managing server

ITCAM for WebSphere and ITCAM for J2EE use one common managing serverthat controls and coordinates data collectors for J2EE, CICS, and IMS serversthat run applications. The difference between ITCAM for J2EE and ITCAM for

WebSphere are on the platform support for the data collectors. These datacollectors can run independently.

Browser interfaceITCAM for WebSphere

ITCAM for J2EE

Managing Server

Tivoli Enterprise

Management Server

and

Tivoli Enterprise

Portal Server

I

Web Servers

Application servers with

Data collectors

Tivoli Enter prise

Monitoring Agent

T i v o l i

E n t e

r p r i s

e

M o n i t

o r i n g

A g e

n t


The managing server uses the following software:

Managing server database (DB2 UDB or Oracle on Sun Solaris™) forl ti l d t it




relational data repository

WebSphere Application Server to run the visualization engine Web consoleapplication

An optional Web server, such as IBM HTTP Server

The managing server overseer components, which are a set of Java-basedprocesses.

The overseer components are the controlling logic for the managing server. Theyare:

Kernels control the managing server. There are always two copies of thekernels running on an ITCAM for WebSphere and ITCAM for J2EE managingserver for redundancy and failover. The kernels register components as they

join the managing server, periodically renew connections and registrationswith components and data collectors, and collect server and componentavailability information.

Publishing servers receive application and system event data from the datacollectors, gather and compute request-level information about performancemetrics such as response times, and implement the trap monitoring and alertsfeatures.

Archive agents receive monitoring data from the publish servers, and storethe monitoring data in ITCAM for WebSphere’s and ITCAM for J2EE’srepository.

The global publishing server collects information from the publish servers,and correlates all parts and pieces of multi-server requests, such as requestsfrom J2EE servers to execute CICS or IMS programs.

The message dispatcher is a conduit for messages from ITCAM forWebSphere and ITCAM for J2EE using e-mail and SNMP facilities.

The visualization engine is a Web-based GUI with access to graphics, ITCAMfor WebSphere and ITCAM for J2EE performance reports, real-time views ofdifferent slices of monitoring data, and ITCAM for WebSphere and ITCAM forJ2EE internal commands and event-driven functions. The visualization engineruns on a WebSphere Application Server.


Figure 2-2 shows the conceptual relationship between the components.




Figure 2-2 Kernel components

At the managing server, monitoring data is prepared for real-time displays withinthe monitoring console and is inserted into the OCTIGATE data repository. Theseare very resource-intensive operations; moving them the managing server

isolates them from other the application servers, thus reducing ITCAM forWebSphere’s and ITCAM for J2EE’s footprints in the monitored systems. Thisdesign also helps keep the data collectors’s processing overhead at levels lowenough for 24x7 production system monitoring.

Data from the data collectors is collected by the publishing server then stored inthe OCTIGATE database by the archive agent. The Visualization Engine readsthe database to present data through the Web console, and snapshot informationsuch as lock analysis and in-flight transactions are retrieved directly from the

data collectors.

2.2.2 J2EE and WebSphere data collector

The data collectors run inside the application servers. They use native systemservices, and they are tailored for the particular environments where theyexecute. The data collectors for z/OS systems are written to take advantage ofservices on z/OS, such as MVS™ Cross-Memory Services and address spacefencing, which are not available on distributed systems.

Kernel (KL)Provide services on:

- Lookup

- Registration

- Recovery

- Configuration

Publish Server (PS)

Archive Agent (AA)

Global Publish

Server (SAM)

Message Dispatcher

(MD)

Visualization EngineProvide services on:

-Administration

-Availability

-Problem Determination

-Performance Management

OCTIGATEdatabase

P u b l i s h t r a f f i c

S

n a p s h o t t r a f f i c


Data collectors are configured as a multi-threaded process. They consists of thefollowing agents:

Command agent




Command agent

The command agent collects requests from other components for informationabout EJB invocations, database connection pools, thread pools, stack

traces, memory analyses, and heap dumps.

Event agent

The event agent provides data to the publish servers according to pollingfrequencies. This data includes system initialization data, applicationrequest-level data, and application method-level data.

Secondary collector

The optional secondary collector provides support for displaying data into

Tivoli Enterprise Portal for collecting WebSphere Application Server and otherJ2EE application server performance metrics. This component communicateswith Tivoli Enterprise Monitoring Agent using a TCP/IP port.

Collectively, these agents and other data collector routines unleash the probes,package the monitoring data into Java formats for the managing server, anddeliver the data to the managing server.

The data collectors send the probes into the application servers to analyze the

applications’ performance. The probes collect monitoring data and feed it totransport routines that in turn route the data to the managing server. Themanaging server processes it for display in the Web console and for storage inthe OCTIGATE repository. This relieves the processing burden of ITCAM forWebSphere and ITCAM for J2EE from the application servers as much aspossible. The data collectors and probes are not designed to analyze or interpretdata, but to collect it and route it as quickly as possible to the managing serverwhere the analysis is performed.

The data sources that are employed by ITCAM for WebSphere and ITCAM forJ2EE are:

JVMTI garbage collection data, method trace, stack trace, CPU time, andheap dump

JMX™ system resources

SMF system resources (z/OS only)

PMI system resources (WebSphere only)

OS services SCC, platform CPU, and its environment Byte Code Modification (BCM) instrumentation of some classes


The data collector in the J2EE server runs as a custom service called am indistributed and “-” for z/OS. Figure 2-3 shows the conceptual data collectorstructure of the distributed WebSphere data colledtor.




Figure 2-3 J2EE data collector structure

2.2.3 Tivoli Enterprise Management Agent

ITCAM for WebSphere and ITCAM for J2EE’s Tivoli Enterprise Monitoring Agentcan forward monitoring information to Tivoli Enterprise Monitoring Server formonitoring using Tivoli Enterprise Portal. There is an additional component isversion 6.1; which is Tivoli Enterprise Monitoring Agent for Web Servers. Webservers monitoring no longer using the managing server’s polling agent, but it isusing an Tivoli Enterprise Monitoring Agent for Web Servers instead.

The existing Tivoli Enterprise Monitoring Agent for WebSphere and J2EE are

providing application server performance information, while the new TivoliEnterprise Monitoring Agent for Web Servers displays Web servers performanceinformation.

2.2.4 Monitoring resources

You may encounter certain terminology that is used in the operation of ITCAM forWebSphere and ITCAM for J2EE:

Monitoring on demandMonitoring level for the amount of instrumentation performed by

WebSphere

Custom Service

amPublish databcm

JVMTI PMIJMX

Tivoli Enterprise

Management Agent

K Y N

To TEMS


the data collector and the percentage of information that isstored.

Server configuration




g

Assigning a data collector with a profile. A server profiledetermines the classes to include or exclude for monitoring.

Server group A logical grouping of servers that enables aggregation of statusor is used for report generation grouping.

Report Interactive display that enables navigation of collectedinformation in the database to analyze previous performance ofapplication. Reports can also be generated into a PDF file.

Monitoring levelsThe monitors for ITCAM for WebSphere and ITCAM for J2EE run on a

pre-defined monitoring level. These levels can be changed dynamically withoutthe need to restart the monitored systems. The levels are:

Level 1 Production-level monitoring that provides basic response timeand transaction information

Level 2 More detailed information that includes method call details andmemory usage. In version 6.1, there is a new method profilingoption for this level to allow collection of aggregate methodcalling statistic with much lower overhead than Level 3

monitoring.Level 3 Detailed tracing information that shows all method entries and

exits with significant amounts of information collected.

Data collector configurationThe data collector configuration is stored in the $DC_HOME/runtime subdirectory. It is governed by several configuration files, among them are:

custom/toolkit_custom.properties

This file stores custom settings for bytecode instrumentationproperties.

cynlogging.properties

Message logging and tracing level for the data collectorcomponents. The level is typically set to INFO. Other possiblelevels are DEBUG_MIN, DEBUG_MID, and DEBUG_MAX.

jiti.properties Just in time instrumentation property for Java classinstrumentation profile.

<wasver>.<node>.<srv>.datacollector.policy

Java security permission of the data collector.


<wasver>.<node>.<srv>.datacollector.propertiesMonitoring properties, levels, and time-out parameters. This fileis extracted to generate an instance-based configuration filecalled <node> <server>(<profile>) datacollector properties




called <node>.<server>(<profile>).datacollector.properties.

<wasver>.<node>.<srv>.kwjdc.properties

Property file for Tivoli Enterprise Monitoring Agent connector.<wasver>.<node>.<srv>.toolkit.*

Instrumentation properties with ITCAM toolkit.

<node>.<srv>.cyaneaGpsCounter.txtCounter that identifies a sequence number for matching acomposite transaction.

Managing server utilities

Several utilities for the managing server are useful for maintaining the operationof ITCAM for WebSphere/J2EE.

The following utilities are for the managing server components:

klctl.sh With this command you can start, stop and ping the kernelmanually. You can also change the debugging level andcheck the data base connection.

am-check.sh This verifies whether all settings are correct. This test can

be run manually. am-start.sh executes this checkimplicitly.

amctl.sh This script can start, stop, ping, get status and set logginglevels for all components.

am-start.sh Starts the managing server components.

am-stop.sh Stops the managing server components.

add-ps.sh Adding a separate publish server instance

add-aa.sh Adding a separate archive agent instance

Some programs are aimed on managing the OCTIGATE database in themanagement server, such as initializing or maintaining the database. Those are:

Database creation tools: db2configuration.sh

Database schema creation, when the database is already created:db2createschema.sh

Database setting definition for existing database: db2settings.sh

Database migration script: migration*.sh

Updating the database statistics: run-stat-cmds.sh.


Trimming data: aa_deletedata.sh and datatrim.sh

Other programs that are provided in the managing server include:

th ti t Thi i d t if th ’ t d




authenticate This program is used to verify the user’s account andpassword to the operating system for the Web console.

rotate-apache-logs.sh Rotates Apache logs by issuing the apachectl command.

setenv.sh Sets configuration parameters for the managing servercomponents, including memory sizes and databaseaccess.

dcctl.sh Controls the logging level in data collectors.

2.2.5 Logging and troubleshooting

The ITCAM for WebSphere logs are located either in the Tivoli common logdirectory with the identifier of CYN or in the logs subdirectory of the installationpath. In general, the logging level can be modified, either from the properties fileto include am.debug=yes or using the control commands, dcctl.sh or amctl.sh.

The managing server logs are:

$AM_HOME/logs

– am_stderr.log– am_stdout.log

/var/ibm/tivoli/common/CYN/logs

– msg-<component>.log– trace-<component>.log– audit-ms.log

The distributed data collector logs are in $commondir\CYN\logs: some logs mayreside in <admin>.<server> path, such as:

msg-dc.log trace-dc.log msg-dc-native.log trace-dc-native.log

The z/OS data collector logs are in /var/ibm/tivoli/common/CYN/logs

trace-zprobe.log trace-imsprobe-native.log msg-zprobe-native.log msg-zprobe.log


The cynlogging.properties file controls the logging level of the components. Werecommend that you activate only the appropriate detailed logging level for aspecific component. An example is to modify part of the logging for the CICSinstrumentation to DEBUG MAX as shown in Example 2-1




instrumentation to DEBUG MAX as shown in Example 2 1.

Example 2-1 Excerpt of cynlogging.properties

. . .

#-----------------------------------------------# COMPONENT SPECIFIC LOGGERS#-----------------------------------------------

. . .#-----------------------------------------------# CICS Data Collector

#-----------------------------------------------

# MESSAGE LOGGERCYN.msg.cicsdc.level=INFOCYN.msg.cicsdc.logging=true

# TRACE LOGGERCYN.trc.cicsdc.level=DEBUG_MAXCYN.trc.cicsdc.logging=true

. . .

2.3 Implementation overview

The overall implementation process for ITCAM for WebSphere and ITCAM forJ2EE can be described in the following procedure:

1. Plan for the configuration. Primary concerns for this planning process are theexpected load and sizing of the managing server. The managing server is thecenterpiece of ITCAM for WebSphere and ITCAM for J2EE, soimplementation must consider its performance and capacity implications.Another important planning factor is the security and communication structurebetween the managing server and data collectors. Implementation planning isdiscussed in this section.

2. Managing server installation is discussed in 2.4, “Installation process” on

page 30. This includes database setup and tuning.3. Install data collectors. Different data collectors require different installation

mechanisms. The available data collectors are for ITCAM for WebSphere,


ITCAM for J2EE, ITCAM for IMS Transactions and ITCAM for CICSTransactions. The distributed based data collectors are discussed in thischapter, while the z/OS based data collector is discussed in Chapter 9,“Implementation of ITCAM products on z/OS” on page 343




p p p g

4. (Optional) For feeding information into Tivoli Enterprise Monitoring Server

with Tivoli Enterprise Portal, you must install the Tivoli EnterpriseManagement Agent for ITCAM for WebSphere or ITCAM for J2EE on eachdata collector system. See 2.5, “Integration with Tivoli Enterprise Portal” onpage 44.

5. Certain administrative tasks must be performed before monitoring can takeplace. These are discussed in 2.6, “Initial configuration and operation” onpage 52:

– Assign the data collector configuration.– Modify the monitoring level.– Define server groups.– Create operators.

The planning consideration includes:

2.3.1, “Sizing consideration” on page 25 2.3.2, “Security considerations” on page 27 2.3.3, “Implementation configuration” on page 28 2.3.4, “Managing server installation options” on page 29

2.3.1 Sizing consideration

As discussed in 2.2.1, “The managing server” on page 16, the managing serverconsists of multiple processes that each run in its own Java Virtual Machine. Thisarchitecture, while providing redundancy and scalability, also requires a largeamount of memory. ITCAM for WebSphere and ITCAM for J2EE managingserver needs at least 4 GB of memory. The memory and processingrequirements largely depend on:

The number of data collectors connected to the publish server and kernel

The amount of transaction information sent to the publish server

Monitoring levels of transactions by the data collectors, which translate to thedata size sent to the publish server

The monitoring sampling rate, which determines the numbers of records thatare passed from the publish server to the archive agent

The amount of correlation for composite transactions that the Global Publish

Server must process

The number of users connected to the Visualization Engine


The number of users who actually perform problem determination, whichtranslates to direct connection to the data collectors from the visualizationengine.




Database sizing for the managing server can be estimated using the worksheetin this Web page:

http://www-1.ibm.com/support/docview.wss?rs=2344&context=SS3PGL&dc=DB520&q1=database&uid=swg21250907&loc=en_US&cs=utf-8&lang=en

JVM sizes are determined from the setenv.sh in the bin directory of the managingserver. Example 2-2 shows the default memory sizes.

Example 2-2 Memory size

HEAP_MIN_SIZE_PS=256HEAP_MAX_SIZE_PS=512HEAP_MIN_SIZE_ARCHIVE_AGENT=256HEAP_MAX_SIZE_ARCHIVE_AGENT=512HEAP_MIN_SIZE_EMAIL=32HEAP_MAX_SIZE_EMAIL=64HEAP_MIN_SIZE_MESSAGE_DISPATCHER=32HEAP_MAX_SIZE_MESSAGE_DISPATCHER=64HEAP_MIN_SIZE_KERNEL=128HEAP_MAX_SIZE_KERNEL=256HEAP_MIN_SIZE_AVM=32

HEAP_MAX_SIZE_AVM=64HEAP_MIN_SIZE_SAM=64HEAP_MAX_SIZE_SAM=128HEAP_MIN_SIZE_POLLING_AGENT=64HEAP_MAX_SIZE_POLLING_AGENT=64

As shown in Figure 2-4, the majority of memory is used by the publish server andarchive agent. Publish servers and archive agents process transactioninformation from the data collectors. Visualization engine memory can beenforced from the WebSphere Application Server administration console.

To optimize performance and provide additional reliability, the managing servercan be divided among several machines. While the provided installation wizard

allows only a single-machine installation for the managing server components,customization can be performed to split the managing server.

Note: For proof of concepts and demonstration systems without anyproduction load, you can decrease the memory footprint for publish serversand archive agents. You may also want to suppress starting and stopping

processes that you do not need in the am-start.sh and am-stop.sh.


Note: The wizard allows you to have only the database installed on a remoteDB2 server. We do not cover split-server installation in this book.




Figure 2-4 shows a sample split-server installation.

Figure 2-4 Split-server installation

2.3.2 Security considerations

Communication security between the ITCAM for WebSphere managing serverand the data collectors requires the use of certificates and SSL encryption. Astransaction information carries a large amount of information, including

potentially sensitive information, this is a must for an enterprise. We do notdiscuss SSL implementation in this book, but we recommend performing this withyour own certificates, instead of using the pre-supplied certificate that comeswith the product. This ensures the confidentiality of communication.

Another important security consideration is the use of the TCP/IP port. ITCAM forWebSphere and ITCAM for J2EE uses a range of ports in the data collector tocommunicate with the publish server and kernel in the managing server. Whencommunicating through a firewall, you may want to use a port consolidator proxy.

Example 2-3 shows default port usage.

Example 2-3 Port usage

PORT_KERNEL_CODEBASE01=9122PORT_KERNEL_CODEBASE02=9123PORT_KERNEL_RFS01=9120PORT_KERNEL_RMI01=9118PORT_ARCHIVE_AGENT1=9129PORT_ARCHIVE_AGENT2=9130

PORT_MESSAGE_DISPATCHER=9106PORT_PS=9103PORT_PS2=9104

kernel1 kernel2publish1 publish2

archive1 archive2message

dispatcher global publish

server


PORT_PA=9111PORT_SAM=9126

2 3 3 I l t ti fi ti




2.3.3 Implementation configuration

Figure 2-5 on page 28 shows the overall environment of the implementation thatwe performed on our system to manage the Trader application. The managingserver is installed in a single machine in peoria, and the data collectors areconnected directly to the managing server.

Figure 2-5 ITCAM for WebSphere and ITCAM for J2EE implementation

peoriaManaging Server

srv178datacollector

WebSphere xLinux

srv177datacollector

WebSphere xLinux

srv180datacollector Jboss

xLinux

WebSphere z/OS

datacollector

srv176

datacollector

WebSphere xLinux

wtsc67

IMS

datacollector

CICS

datacollector

wtsc67

wtsc67


2.3.4 Managing server installation options

The installation procedure for the managing server can be performed using theembedded installation, the separate installation of WebSphere, DB2 and themanaging server or the silent installation




managing server or the silent installation.

The embedded installation installs WebSphere Application Server and DB2 withthe ITCAM for WebSphere managing server. This embedded installationsimplifies the installation process and does not require WebSphere and DB2skill.The embedded installation is divided into two options the typical installationand the custom installation.

Using the typical installation the wizard will choose the following default valuesfor the installation:

The installation paths for the DB2, WebSphere and managing server

installations:

– Product directory for DB2 /opt/IBM/db2 orC:\Program Files\IBM\itcam\WebSphere\MS\DB2

– Product directory for WebSphere /opt/IBM/itcam/WebSphere orC:\Program Files\IBM\itcam\WebSphere\MS\WAS61

– Product director for managing server /opt/IBM/itcam/WebSphere/MS orC:\Program Files\IBM\itcam\WebSphere\MS

The DB2 users needed for the installation:db2admin The DB2 administration userdb2inst1 The DB2 instance userdb2fenc1 The DB2 fence user.

The installation procedure will also create an database called OCTIGATE tostore the performance information collected by the managing server. Thedefault port number for DB2 will be 50000.

When you decide to use any other values then the default ones for theinstallation, you can use the custom installation. This option enables you tocustomize the following values:

For DB2 you can choose the following settings:

– The user names

– The port for the data base

For WebSphere you can choose the following settings:

– The installation path– The user you want to use for the installation and the user you want to use

to access the user interface


For the managing server you can choose the following settings:

– You can define the ports for the different components of the managingserver.

Th thi d t i t ll th i ld b t i t ll ti f




The third way to install the managing server would be an separate installation ofWebSphere, DB2 and the managing server. You can also use an existingdatabase on the local system or an remote DB2 or Oracel database.Using anexisting database it is recommended to use a supported version. In ourinstallation we used DB2 version 8.2 fix pack 1. You also have to use WebSphereversion 6.1. When you do a separate installation of the database or using anexisting database, the installation wizard can still do the configuration of thedatabase tables. You can also use the scrips that are supplied on the installationcd to do the database configuration.

Another way to install the managing server would be the silent script which also

comes with the installation cd in the folder /silent.Choosing the silent installation,you have to define all installation options and values in the script before startingthe installation.

In this book, we install the managing server using the embedded installation withthe typical settings.

2.4 Installation processThis section discusses the installation for ITCAM for WebSphere and ITCAM forJ2EE. The sub-sections are:

2.4.1, “ITCAM for WebSphere and ITCAM for J2EE managing server” onpage 30

2.4.2, “ITCAM for WebSphere data collector” on page 35 2.4.3, “J2EE data collector installation” on page 41 2.4.4, “Apache HTTP Server set up” on page 43

2.4.1 ITCAM for WebSphere and ITCAM for J2EE managing server

We chose Red Hat Enterprise Linux 3.0 as our managing server platform.Typically, using a Linux-based system decreases the memory requirement for thebase operating systems compared to Windows-based systems.

The installation of the ITCAM for WebSphere managing server can be outlinedas follows:

1. Create the necessary user ID for the managing server installation. This useris used as an administrative user for WebSphere and ITCAM’s managing


server. The user will be able to access the WebSphere administrator’sconsole and the user interface of the managing server. For an UNIX® environment this user should have root privileges. For an Windowsenvironment the user must be member of the Administrator’s group.




2. Copy the installation images of DB2, WebSphere to a local directory beforestarting the installation. The embedded installation method would requireaccess to these installation images. The DB2 and WebSphere software levelmust match exactly the requirement for the embedded installation process.

3. Use the ITCAM for WebSphere managing server for Linux CD-ROM to startthe installation wizard. The installation wizard in UNIX or Linux-based systemrequires X-Windows server application, such as the native desktops orWindows based X-Windows server application.

4. Installation is started using the launchpad command from the installationmedia. Use the appropriate launchpad executable for your platform. We areusing launchpad.sh for the Linux system and select Install ITCAM and clickon the Start the installation process for ITCAM for WebSphere and J2EEManaging Server Version 6.1 link as shown in the Figure 2-6 on page 32

Note: For a Windows-based managing server, you need to install MicrosoftServices for UNIX (SFU) utility. This can be downloaded from:

http://www.microsoft.com/windows/sfu/default.asp







Figure 2-6 Installation startup screen

5. If you are installing from CD-ROM, the wizard will copy the installation files tothe temp directory. If you are installing from a installation image on theharddrive, the wizard will use the existing installation media.

6. The wizard will check the prerequisite for the Installation and will show you theresults as shown in Figure 2-6

7. The next step enables us to select the type of installation: typical or custom.We decide to keep the default settings for the installation therefore weselected typical.


8. In the next step we define the installation path of the managing server asshown in Figure 2-6.




Figure 2-7 Defining the installation Path

9. We typed in the managing server administrative user that we defined at thebeginning of the installation, as shown in Figure 2-7.

10.As we copied the DB2 and WebSphere installation images to a local directory

before we started the installation, we selected those images as shown inFigure 2-8 on page 34.





Figure 2-8 Inserting the administrative user

11.As you can see in Figure 2-9 on page 35 you have the possibility to install themanaging server and you can choose also to create an response file. Theresponse file will save your settings so you can use them again for a silentinstallation of the managing server. It is also possible to just create theresponsfile if you don’t want to install the managing server at this time, butyou like to keep your settings.




C:\Program Files\ibm\tivoli\common). This file system must be large enoughto contain the various message files and trace log files.

To install the data collector make sure that the WebSphere Application Serverwere you want to install the data collector into is running.




The following sample installation flow is from a Linux system with WebSphere

Application Server V6.0.2 network deployment environment. We highlight someof the important dialogs:

1. Installation is started using the launchpad command from the data collectorinstallation media. Use the appropriate launchpad executable for yourplatform. We were using launchpad.sh for the Linux System and select InstallITCAM→ start the installation process... as shown in the Figure 2-10 onpage 37.

2. The next step is to fill in the path were you want the data collector to be

installed as shown in Figure 2-10 on page 37. You can also choose wetheryou want to create an response file for a silent installation or not as discussedin 2.4, “Installation process” on page 30 step 10.





Figure 2-10 WebSphere data collector installation first steps

3. After the wizard copied the data collector files into the specified directory wechoose to configure the data collector this will start the configuration of theWebSphere data collector in a another window.

4. You can see in Figure 2-11 on page 38 that we choose to do both theconfiguration for the integration into the Tivoli Enterprise Portal. Be aware thatyou need to install another agent called Tivoli Enterprise Monitoring Agent tointegrate the WebSphere data collector into the Tivoli Enterprise Portal. Theinstallation of the Tivoli Enterprise Monitoring Agent agent is disused in 2.5,

“Integration with Tivoli Enterprise Portal” on page 44.To configure the datacollector for the ITCAM for WebSphere and ITCAM for J2EE application


monitoring interface you need to install the managing server as described in2.4, “Installation process” on page 30.

5. In the next window we configure the data collector to find the managing serverby inserting the hostname and the Codebase port that can be defined at themanaging server installation. The default port is 9122.




6. You can also see in Figure 2-11 on page 38 that we insert the installationdirectory of our managing server.

Figure 2-11 Configure the data collector for the managing server

7. We enter the hostname of the Tivoli Monitor Enterprise Agent and the portwhere the agent is lessening on. In our case we typed in the local IP address

and the default port: 63335.


8. If there is a firewall between the data collector and the managing server youneed to enable the firewall option and specify the RMI port numbers.

9. The next step is to select the type of WebSphere Server you want to monitor.We select WebSphere Application Server in our installation.

10.The wizard will detect the running WebSphere Application Server and ask you




g p pp y

to select the server you would like to monitor.11.As shown in Figure 2-12 on page 40 we specify the home directory of the

WebSphere Application Server. We also insert the WebSphere version andthe Java home directory.

12.On the second window in Figure 2-12 on page 40 we specify the hostname ofthe Network Deployment Server we are using. If you don’t use a DeploymentServer just use the hostname of the local WebSphere Server.

13.In the last window in Figure 2-12 on page 40 we select the server that we

want to monitor.





Figure 2-12 WebSphere configuration

14.In the next step you have the possibility to generate a responsfile for silentinstallations.

After the installation you should see the data collector registered in the managing

server. You can see the data collectore from the following menu from thevisualization engine:


Unconfigured data collectors from Administration→ ServerManagement→ Data Collector Configuration→ Unconfigured Data

Collectors.

Data collector controller process (PPEController) from Administration→ Managing Server→ Self Diagnostic.




For further configuration see 2.6, “Initial configuration and operation” on page 52.

2.4.3 J2EE data collector installation

In general the Installation of the ITCAM for J2EE data collector is similar to theinstallation of the ITCAM for WebSphere data collector. There are somedifferences depending on the J2EE platform on which you install the datacollector. We demonstrate the installation of the ITCAM for J2EE data collectore

on a JBoss application server in this chapter. We also describe some differencesbetween WebSphere data collector and the JBoss data collector installation. Thelist of all web and application servers supported by the ITCAM for J2EE datacollector is shown in 2.3, “Implementation overview” on page 24.

Similar to the WebSphere data collector, the J2EE data collector implementationis performed in two stages. The file copying stage and the application serverconfiguration stage. The file copying dialog is very similar to the ITCAM forWebSphere data collector that we describe in 2.4.2, “ITCAM for WebSphere datacollector” on page 35 in the step 1to step 8 on page 39.

1. After you finished the first tage, you would start configuring the J2EEapplication server. The configuration values specific for JBoss applicationserver is shown in Figure 2-13 on page 42.





Figure 2-13 JBOSS J2EE data collector configuration

2. The next step is to select the JBoss server startup script as shown inFigure 2-14 on page 43.





Figure 2-14 JBoss server startup script

3. We select the server that we want to monitor in our case it is the defaultserver.

4. In the last step you have the possibility to generate a response file for a silentinstallation.

2.4.4 Apache HTTP Server set upTo be able to monitor Apache Web Server using the ITCAM for Web Serversfeature on ITCAM for WebSphere, you must activate the status monitor. Theactivation of the status monitor is performed by modifying the httpd.conf with theExtendedStatus option and you need to add the server-status page in theLocation directive. See Example 2-4.

Example 2-4 Modification to httpd.conf

. . .ExtendedStatus On

. . .


<Location /server-status>SetHandler server-status<Location>

Note: The runtime environment in our sample configuration use Apache HTTPServer 2.0.59 on Red Hat Enterprise Linux AS version 3 (Taroon Update 7).




As a test, we displayed the server status page as shown in Figure 2-15.

Figure 2-15 Apache Server Status

2.5 Integration with Tivoli Enterprise Portal

ITCAM for WebSphere and ITCAM for J2EE can be integrated into the IBM TivoliMonitoring V6.1 infrastructure. This enables you to exploit IBM Tivoli MonitoringV6.1 functionality such as Tivoli Data Warehouse V2.1, correlation of WebSphereand other J2EE application server information with data from other IBM TivoliMonitoring V6.1 agents, and presentation with Tivoli Enterprise Portal.

p ( p )

The default configuration is used.


The Tivoli Enterprise Monitoring Agent retrieves performance data about theWebSphere and other J2EE application servers for the following information:

Response time data for application server requests from the ITCAM forWebSphere and J2EE data collector

Resource data from the WebSphere and J2EE Performance Monitoring




Infrastructure WebSphere application server and other J2EE server log messages

Garbage collector activity recorded in the Java Virtual Machine’s verbosegarbage collector trace

The Tivoli Enterprise Monitoring Agent retrieves performance data from thesecondary collector of the data collector and ships them to the Tivoli EnterpriseMonitoring Server, which processes the data for storage and display in the IBMTivoli Monitoring infrastructure. Figure 2-16 on page 45 shows the inter

connectivity structure.

Figure 2-16 ITCAM for WebSphere integration with Tivoli Enterprise Monitoring Agent

Tivoli Enterprise

Management Server

Tivoli Enterprise

Management Server

Tomcat

Tivoli EnterpriseManagement Agent

J2EE data

collector

WebSphere Portal

Tivoli Enterprise

Management Agent

WebSphere

data collector

WebSphere AS

Tivoli Enterprise

Management Agent

WebSphere

data collector


In this redbook we discuss the integration of data collectors into the IBM TivoliMonitoring V6.1 infra structure. Notice the following regarding ITCAM forWebSphere and ITCAM for J2EE agents:

There are separate installation image for the Tivoli Enterprise MonitoringAgent and application support file.




The agent code for ITCAM for WebSphere is YN, while ITCAM for J2EE is YJ.The agent code is used for using the command line to configure the agent.Configuring ITCAM for WebSphere is launched using the command:itmcmd.sh config -A yj while configuring ITCAM for J2EE is using thecommand: itmcmd.sh config -A yn.

This section assumes that you already have the IBM Tivoli Monitoring V6.1infrastructure installed. The implementation has three steps:

2.5.1, “Prepare the IBM Tivoli Monitoring V6.1 infrastructure” on page 46

2.5.2, “Tivoli Enterprise Management Agent installation” on page 48 2.5.3, “Tivoli Enterprise Management Agent configuration” on page 51

2.5.1 Prepare the IBM Tivoli Monitoring V6.1 infrastructure

In order to integrate ITCAM for WebSphere information into IBM Tivoli MonitoringV6.1 infrastructure, you must set the infrastructure to support this type of agent.

Tivoli Enterprise Monitoring Server: Generates agent-specific information in

Tivoli Enterprise Monitoring Server such as product situations and agenttables.

Tivoli Enterprise Portal Server: Adds workspaces and presentation files forthe agents to the Tivoli Enterprise Portal Server.

Tivoli Enterprise Portal: Updates Tivoli Enterprise Portal clients withproduct-specific information such as help files.

This section covers these steps from a process point of view and guides youthrough the installation process. For the installation and customization, we follow

the instructions in IBM Tivoli Composite Application Manager for WebSphere Installing and Configuring the Tivoli Enterprise Monitoring Agent, SC32-1801.

Important: Be sure that you understand on what machine these activitieshave to run; check with your IBM Tivoli Monitoring V6.1 administrator andconsult the appropriate IBM Tivoli Monitoring V6.1 documentation.


1. Start the installation by clicking Setup in the Windows directory of the ITCAMfor WebSphere Tivoli Enterprise Monitoring Agent CD-ROM or by runninginstall.sh in your Linux or UNIX environment.

Figure 2-17 shows the Welcome window for the installation of ITCAM forWebSphere. Click Next.




Figure 2-17 Tivoli Enterprise Monitoring Agent Welcome window

2. Check the Prerequisites window.

3. Accept the license agreement.

4. Choose the installation path.

5. Check the User Data Encryption Key.

6. Select features to install; depending on where you are running this installationwizard, you may install different components on different machines. In ourenvironment, we have both Tivoli Enterprise Monitoring Server and TivoliEnterprise Portal Server on a single machine, so we checked (Figure 2-18):

– Tivoli Enterprise Monitoring Server– Tivoli Enterprise Portal Server

– Tivoli Enterprise Portal Server


Note: You may have to install this on your Tivoli Enterprise MonitoringServer machine, Tivoli Enterprise Portal Server machine, and individualTivoli Enterprise Portal desktop clients. You only have to install thecomponent that is available in each machine.




Figure 2-18 Tivoli Enterprise Monitoring Agent components

7. Follow the installation wizard and configure the components. Most of thecomponents will already be preconfigured because they are installed on anexisting IBM Tivoli Monitoring server.

The communication to Tivoli Enterprise Monitoring Server and Tivoli EnterprisePortal Server in our environment uses IP:PIPE, which is a TCP connection.

2.5.2 Tivoli Enterprise Management Agent installation

We install the Tivoli Enterprise Monitoring Agent on the same machine that weinstalled the ITCAM for WebSphere or ITCAM for J2EE data collector on. This isrecommended as the Tivoli Enterprise Portal displays the agent by machine,having the Tivoli Enterprise Monitoring Agent on the same machine as the actualapplication server reduces the confusion that may arise.


The installation of the Tivoli Enterprise Monitoring Agent on Linux platform iscommand line based.

The installation is started using the install.sh script from the installationCD-ROM directory. Enter the name of the IBM Tivoli Monitoring directory.Example 2-5 lists the responses of our installation.




Example 2-5 Listing of the Tivoli Enterprise Monitoring Agent installation

Enter the name of the IBM Tivoli Monitoring directory[ default = /opt/IBM/ITM ]:/opt/IBM/ITM

“/opt/IBM/ITM" does not existTry to create it [ y or n; "y" is default ]? y

Select one of the following:1) Install products to the local host.2) Install products to depot for remote deployment (requires TEMS).3) Exit install.

Please enter a valid number: 1

Initializing ...Software Licensing Agreement1. Czech2. English...

Please enter the number that corresponds to the languageyou prefer. 2

Software Licensing Agreement...

1Preparing to install the IBM Global Security Kit (GSkit)

Preparing packages for installation...gsk7bas-7.0-3.18Will enable automatic agent initiation after reboot.

Enter a 32-character encryption key, or just press Enter to use thedefault

Default = IBMTivoliMonitoringEncryptionKey....+....1....+....2....+....3..

GSkit encryption key has been set.Key File directory: /opt/IBM/ITM/keyfiles

Note: It is recommended to start the agent with the same user ID used to startWebSphere, because the Agent should be able to start and stop WebSpherewith the default startServer and stopServer script.


Product packages are available in /code/TEMA-YN/unixProduct packages are available for the following operating systems andcomponent support categories:

1) Linux AMD64 R2.6 (64 bit)2) Linux Intel R2.4 (32 bit)

...

Type the number for the OS or component support category you want or" " i l i




Type the number for the OS or component support category you want, ortype "q" to quit selection[ number "2" or "Linux Intel R2.4 (32 bit)" is default ]: 2Is the operating system or component support correct [ y or n; "y" isdefault ]? y The following products are available for installation:

1) IBM Tivoli Composite Application Manager for WebSphereV06.10.00.00

2) Tivoli Enterprise Services User Interface V06.10.03.003) all of the aboveType the numbers for the products you want to install, or type "q" toquit selection. If you enter more than one number, separate the numbersby a comma or a space.Type your selections here: 1 The following products will be installed:

IBM Tivoli Composite Application Manager for WebSphere V06.10.00.00

Are your selections correct [ y or n; "y" is default ]? y... installing "IBM Tivoli Composite Application Manager for WebSphereV06.10.00.00 for Linux Intel R2.4 (32 bit)"; please wait.

=> installed "IBM Tivoli Composite Application Manager for WebSphereV06.10.00.00 for Linux Intel R2.4 (32 bit)."... Initializing database for IBM Tivoli Composite Application Managerfor WebSphere V06.10.00.00 for Linux Intel R2.4 (32 bit).... IBM Tivoli Composite Application Manager for WebSphere

V06.10.00.00 for Linux Intel R2.4 (32 bit) initialized.

Do you want to install additional products or product support packages[ y or n; "n" is default ]? n

... postprocessing; please wait.

... finished postprocessing.Installation step complete.

As a reminder, you should install product support on each of your TEM

servers for any agents you have just installed. This is done via the"[ITM home]/bin/itmcmd support" command on your TEM servers.


You may now configure any locally installed IBM Tivoli Monitoringproduct via the "/opt/IBM/ITM/bin/itmcmd config" command.

2.5.3 Tivoli Enterprise Management Agent configuration

After finishing the installation we have to configure the agent by running the/itmcmd sh config -A yn command form the bin directory of the installation




./itmcmd.sh config -A yn command form the bin directory of the installationpath where yn is the 2-character product code for ITCAM for WebSphere. Theconfiguration listing is shown in Example 2-6.

Example 2-6 Configuration of Tivoli Enterprise Monitoring Agent

# ./itmcmd config -A ynAgent configuration started...Edit 'Basic' settings? (default is: Yes):Yes

Request Data MonitoringType number of item from the below list1. Disable2. Level13. Level2(default is: LEVEL1): 3

Request Data Monitoring MethodType number of item from the below list1. Fixed Interval

2. On Demand(default is: FIXEDINTERVAL):1Resource Data Monitoring

Type number of item from the below list1. Disable2. Enable(default is: ENABLE):2

Resource Data Monitoring MethodType number of item from the below list

1. Fixed Interval2. On Demand(default is: ONDEMAND):2

Garbage Collection MonitoringType number of item from the below list1. Disable2. Enable(default is: ENABLE):2

Edit 'Agent (Advanced)' settings? (default is: Yes):n

Edit 'Collection (Advanced)' settings? (default is: Yes):n


Will this agent connect to a TEMS? [YES or NO] (Default is: YES): yTEMS Host Name (Default is: srv178): limaNetwork Protocol [ip, sna, ip.pipe or ip.spipe] (Default is:ip.pipe):ip.pipe

Now choose the next protocol from one of these:- ip

- snaip spipe




snaip.spipe- none

Network Protocol 2 (Default is: none):noneIP.PIPE Port Number (Default is: 1918):1918Enter name of KDC_PARTITION (Default is: null): Configure connection for a secondary TEMS? [YES or NO] (Default is: NO):NO

Enter Optional Primary Network Name or "none" (Default is: none): noneAgent configuration completed...

After finishing the configuration, we start Tivoli Enterprise Monitoring Agent usingthe ./itmcmd agent start yn command.

2.6 Initial configuration and operation

In this section, we discuss the following topics:

2.6.1, “Data collector configuration steps” on page 52 2.6.2, “Operator definition” on page 58

2.6.1 Data collector configuration steps

When a data collector connects to the managing server, it does not startmonitoring immediately. It only starts the controller communication to themanaging server. The managing server would then start the probe based on theconfiguration that it know. You must perform these tasks:

Assign a configuration for the data collector. See “Data collector

configuration” on page 53. Define the monitoring level and sampling rate for the data collector. See

“Monitoring level and sampling rate” on page 53.

Note: Be sure that you configured the data collector to work with the TivoliEnterprise Monitoring Agent. You can also check the kwjdc.properties file inthe data collector runtime directory.


Assign the data collector to a server group. See “Server group consideration”on page 54.

Data collector configurationA configuration is a profile that provides a specific monitoring definition for thedata collector. Select ADMINISTRATION→ Server Management→ Data

Collector Configuration→ Unconfigured Data Collector. Assign thei t d f lt fil h i Fi 2 19 U ll th d f lt fil

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-




g g gappropriate default profile as shown in Figure 2-19. Usually these default profilesare adequate for your monitoring needs. Additional customization can beperformed using the configuration files on the data collector.

Figure 2-19 Data collector configuration

Monitoring level and sampling rateThe default monitoring level and sampling rate is provided underADMINISTRATION→ Managing Server→ System Properties (Figure 2-20).





Figure 2-20 Default monitoring

Select ADMINISTRATION→ Monitoring On Demand® to specify the overalldefault and provide a specific level for each servers. See Figure 2-21 onpage 54.For further information about those settings see 2.3.1, “Sizingconsideration” on page 25.

Figure 2-21 Monitoring on demand

Server group considerationThe idea of server groups is to consolidate information from several servers andincrease efficiency in handling ITCAM for WebSphere and ITCAM for J2EE.Examples where server groups help are the Enterprise Overview page andreport generations.

The Enterprise Overview enables users to understand the behavior of theirapplication servers at a glance, by graphically displaying throughput and


response time of server groups. In this case, grouping of servers helps tomaintain overview character of this workspace in multi-server environments.

Using server groups for report generation enables you to run reports againsta combined group of servers in contrast to having the report run against everysingle server.

Another option server grouping gives you is more granular authorization, asyou can grant access to servers at group level.




Server grouping is also helpful if you want to change the monitoring level ofseveral servers manually at the time.

ITCAM for WebSphere and ITCAM for J2EE offers to group the servers andaggregate information from all servers in various ways. Examples of servergrouping could be grouping by cell or node, operating system, physical location,or responsibility. For instance, you group the servers according to the group of

people responsible for managing those servers and grant access to theappropriate group of servers only to the various teams.

Figure 2-22 on page 56 shows an example of user distrTr with limited access toservers, in this case authorized only for servers being in the TraderIMSdistrgroup.




Note: Using “shared” servers in server groups might cause misinterpretationsin the Enterprise Overview. Transactions are not distinguished at componentlevel. For example, every server group containing the same “shared” CICSserver, sees all transactions from this CICS server. The number of requestsand response time aggregated in the Enterprise View include alsotransactions triggered by servers that are not part of the group.




Figure 2-23 on page 57 shows an example with servers grouped from anapplication perspective. Note the patterns for the Trader_IMS_distr andTrader_IMS_distr groups although there have not been any IMS activities duringthis period of time. The explanation is that we run both CICS and IMStransactions on the same WebSphere Application Server.

Figure 2-23 Server Group


To find the most helpful server grouping, you might consider:

The number of servers you want to monitor: Does grouping make sense?

Organization and processes in your environment: Who is responsible for whatservers, who needs to have access to what server information?

The way you use reporting: What reports do you use, how many of your

reports are manual reports, and how many scheduled reports are there?

If h “ h d” i t d ib d i thi ti




If you have a “shared” server environment as described in this section(depending on your requirement of accuracy in the Enterprise Overview),grouping servers from an application point of view might be an option.

2.6.2 Operator definition

You must define the operators to use ITCAM for WebSphere and ITCAM for

J2EE. To define the operators, you must perform these steps:

1. Define the user ID to the operating system where you install the ITCAM forWebSphere and ITCAM for J2EE managing server.

– Use Computer Management on a Windows system.

– Use smit for an AIX® system.

– Use the adduser command on a Linux system.

– Otherwise, use the appropriate tools for your server platform.

Our managing server is a Linux box, so we define additional user oper1 usingthe command adduser oper1, then we assign a password for oper1 using thepasswd oper1 command. You need to log on to the system to change thepassword, as the password from the passwd command is expired immediately.


2. Define the operator in ITCAM for WebSphere and ITCAM for J2EE using theWeb console. Select ADMINISTRATION→ Account Management→ User

Profiles and create the oper1 user as shown in Figure 2-24.




Figure 2-24 Creating operator oper1

In Figure 2-24, the operator name in ITCAM for WebSphere and ITCAM for J2EEand the operating system logon do not have to be the same. You can have manyITCAM for WebSphere and ITCAM for J2EE operators defined to the sameoperating system user. This may be confusing for maintenance purposes, so werecommend using a unique operating system user for each ITCAM forWebSphere and ITCAM for J2EE operator. However, the ITCAM for WebSphereand ITCAM for J2EE operator should be the same as the operating system logonto avoid confusion.





Draft Document for Review March 1, 2007 5:22 pm 7151chWAS-J2EE-Usage.fm

3




Chapter 3. ITCAM for WebSphere andITCAM for J2EE usage

This chapter demonstrates the use of ITCAM for WebSphere in our environment.

The discussion includes: 3.1, “Usage scenarios” on page 62

3.2, “Enterprise monitoring” on page 63

3.3, “Server activity analysis” on page 68

3.4, “Transaction reporting” on page 70

3.5, “Composite transaction analysis” on page 80

3.6, “Using Tivoli Enterprise Portal” on page 88

3.7, “Historical information and reporting” on page 93

7151chWAS-J2EE-Usage.fm Draft Document for Review March 1, 2007 5:22 pm

3.1 Usage scenarios

ITCAM for WebSphere and ITCAM for J2EE are solutions that primarily aimed atsecond-line support to perform diagnosis of J2EE-based applications andservices. This chapter discusses some usage scenarios for ITCAM forWebSphere and ITCAM for J2EE within our environment and explores the new

functions of ITCAM for WebSphere and ITCAM for J2EE. The scenarios hereconsist of:




Working with the ITCAM for WebSphere and J2EE Web console to monitorthe environment: This is discussed in 3.2, “Enterprise monitoring” on page 63.Server groups influence the presentation on the enterprise overview andoperator assignment, affecting the display.

Monitoring J2EE Application Server activity is discussed in 3.3, “Serveractivity analysis” on page 68. Here we explore some examples of J2EE

Application Server activity. Transaction analysis and reporting is discussed in 3.4, “Transaction reporting”

on page 70. Trend reports and top reports are the two most common reportsused for analysis. Trend reports show how transactions behave, and topreports show potential bottlenecks in the system.

Analyzing composite applications is discussed in 3.5, “Composite transactionanalysis” on page 80 shows the result of having IMS and CICS transaction aspart of the J2EE-based application.

Working with Tivoli Enterprise Portal information is discussed in 3.6, “UsingTivoli Enterprise Portal” on page 88.

Historical data collection with Tivoli Data Warehouse V2.1 is discussed in 3.7,“Historical information and reporting” on page 93

For additional scenarios and usage, refer to ITCAM for WebSphere Usage

Guide , SCxx-xxxx which includes in-depth discussions about memory analysis,locking analysis, and other advanced analysis scenarios.

It is important to consider how the product will be used in your environment andwho will use it. The solution produces reports that can be relevant to OperationalManagers and Service or Application managers. Identifying the roles andresponsibilities are important considerations because this affects customizationof ITCAM for WebSphere and J2EE, especially around such things as servergroups.


3.2 Enterprise monitoring

When you initially log on ITCAM for WebSphere and J2EE managing server, yousee the availability display. This display shows all data collectors that you haveaccess to with the following level of detail:

Enterprise Shows the overview of all server groups that you have

access.Group Shows all servers within a particular server groupServer Shows the overview page of an application server



Chapter 3. ITCAM for WebSphere and ITCAM for J2EE usage 63

Server Shows the overview page of an application serverAlerts and Events Shows all alerts and events appeared in your environmentProblem Center Views problems in your environment

Figure 3-1 shows our enterprise overview.

Figure 3-1 Enterprise overview


The enterprise overview shows the transaction volume and response time foreach server group. The transaction volume is the total of all transaction volumesfor each server in the server group, and the response time shows the averageresponse time across all servers in the group. This level of display hides the factthat each application server may have a different workload profile. This groupdisplay is beneficial only if you have an application server cluster with loadbalancer where each application server is identical with a similar load profile.

Our enterprise overview in Figure 3-1 on page 63 shows that we have four serverTh d l A il bl S h h f th




groups. The second column, Available Servers, shows how many of the serversin this group are available out of a maximum. So in the Server Group JBOSS,there is a maximum of one server defined and it is available.

Figure 3-1 on page 63 shows the yellow and red horizontal lines that indicatewarning and critical response time thresholds. These settings are defined in theserver group level that can be modified from ADMINISTRATION→ Server

Management→ Server Groups. Figure 3-2 shows an example forDistributedWebSphere.





Figure 3-2 Modify server group

There, threshold is defined as deviation from a baseline performance. You canuse an average from a rolling period of the past few days, a reference period, or ahard-coded response time threshold. In Figure 3-2, we use a fixed baseline of1000 ms.

Be aware that neither the yellow nor red markers actually drive the issue ofalerts; they are only a visual indicator on this display. If alerts are needed, you

can use the ITCAM for WebSphere trap-and-alert facility.


The Enterprise overview shown in Figure 3-1 on page 63 revealed that theresponse time graph for the TraderCICSdistr group is consistently higher thanboth markers and suggests that either the marker needs adjusting or a genuineperformance problem exists. As we intend to investigate using the Server Groupview, click the relevant server group, such as DistributedWebSphere, and thegroup display is shown in Figure 3-3.




Figure 3-3 Group Overview display

This page shows the overview of each server in the server group, includingtransaction volume and average response time for each application server. Thispage also shows whether the data collector in the application server is online.

The DistributedWebSphere server group is very simple; it consists of twodifferent types of server. It can be considered as a Line of Business type view.Server groups defined as containing different server types tend to be useful forreporting and to diagnose bottlenecks in one of the servers.

In our example, the actual throughputs through both srv176 and SCSCBUD1 arequite low. Therefore, the high response time is not caused by high volume oftransactions.

A finer level of granularity is available by selecting a server from this group. The

server summary display is similar to Figure 3-4.





Figure 3-4 Server overview display

The detailed server view is most likely to be used by second-line support teamsto diagnose application issues and narrow down possibilities to the root cause.

Note: These availability pages automatically refresh every 60 seconds. Theydo not time out the user. This may be an issue in some environments that are

particularly security conscious.


3.3 Server activity analysis

When we start work or zoom in to a server for more detailed analysis, typicallywe start with the Server Overview as shown in Figure 3-4 on page 67. You mayalso want a snapshot of the activity of the server using the Server Activity Displayfrom PROBLEM DETERMINATION→ Server Activity Display.

In loading the page in Figure 3-5, the visualization engine requests a snapshot ofinformation directly from the data collector. This may be a costly operation.




Figure 3-5 Server Activity Display

In our sample display, we capture an active transaction under the ActiveRequests tab. This panel is useful for support personnel to identify long-running

requests, usually indicated by a high resident and idle time, or perhaps indicatelooping code if the Accumulated CPU is high.

Select the Recent Requests tab to view a snapshot of requests from the datacollector shown in Figure 3-6. By default this is limited to 100 entries. In some liveenvironments this would be very recent data and may not give a large enoughtime frame to diagnose properly.





Figure 3-6 Recent Requests tab

If more data is needed, transaction history can be retrieved using the Requestand transaction report from the menu of PERFORMANCE ANALYSIS→ Create Application Reports→ Request/Transaction . See some reports in3.4, “Transaction reporting” on page 70.


The Server Activity Display that was shown in Figure 3-5 on page 68 can also beinvoked by clicking the tool icon shown in Figure 3-7. Several other functions arealso available for diagnosing problems.




Figure 3-7 Tool icons to launch Server Activity Display

3.4 Transaction reporting

In 3.3, “Server activity analysis” on page 68, views were analyzed in real time

from snapshot data directly from the data collector. This section discussesreporting from stored data. This stored data is transaction information that ispassed from the publish server to the archive agent. The transaction shown hereis subject to filtering based on the sampling rate specified on the applicationserver data collector setting. ITCAM for WebSphere and ITCAM for J2EEreporting is based on data stored in the OCTIGATE database.

3.4.1 TOP reports

We looked at the reports provided by ITCAM for WebSphere and ITCAM forJ2EE from the perspective of how to identify application bottlenecks quickly and


to get a better understanding of the application flow. Begin with TOP reports toidentify the top players in your environment. In the development phase, thesereports might be run at regular intervals to understand application behavior andpinpoint possible bottlenecks.

The Top Reports delivered with ITCAM for WebSphere and ITCAM for J2EE andthe required monitor level are:

Requests Used Most called requests with the number of calls (L1)

Methods Used Most called methods including the number ofcalls (L3)




calls (L3)

Slowest Requests Slowest requests and their average responsetime (L1)

Slowest Methods Slowest methods and their average responsetime (L3)

CPU-Intensive Requests Requests sorted by total CPU time (L1)

CPU-Intensive Methods Methods sorted by total CPU time (L3)

SQL-Intensive Requests Requests sorted by number of SQL calls (L2)

SQL-Intensive Methods Methods sorted by number of SQL calls (L3)

Tables Used The database tables called most often and thenumber of calls (L1)

SQL Used Top five SQL call types and number of calls (L2)

A customer example of how TOP Request Reports can help is the appearance ofthe authentication method with an unexpectedly high number of requests. Basedon this report, the customer saw redundant calls in the authentication processand lowered resource usage by redesigning the application.


Figure 3-8 shows an example of a TOP Requests Used report from our labenvironment. Actually this report looked as we expected it to, so we did not diginto more details in this case.




Figure 3-8 Top Reports - Top Requests Used

3.4.2 Problem investigation using report

Here is an example of how we used application reports to check the behavior ofour test application. We started with TOP reports for an overview and followedsuspicious data down to method level by using Request/Transaction reports.

Note: The vast majority of the reports we used to narrow down this problemare based on L1 information. The only time L3 information is required is in theFlow View used to identify the method.


In Figure 3-9, helps you figure out the requests with the slowest response timeand helps you to start further diagnosis in case of unexpected results.




Figure 3-9 Top Reports - top CPU intensive requests

Figure 3-9 shows CSMI as the top request in terms of CPU usage. We can startinvestigating the reason of the high response time by drilling down deeper intothe details of the request.


We used PERFORMANCE ANALYSIS→ Create Application Reports→ Request/Transaction and select the TraderCICSdistr group to get more detailsof the CSMI request. We are able to filter our search by a cearten request. In ourcase we will have a look at all request in the specified server group therefor weleave this field blanc. We also select the metric response time(ms) to see therequest with the highest response times.




Figure 3-10 Report filtering options


Figure 3-11 shows the resulting report. The graphic in the report immediatelyinforms you that the requests with the worst responsiveness appeared between10 am and 2 pm of that day. In this time frame we had requests withresponsiveness higher than 60 s. We are now able to click on the bar showingthe bad performer to investigate that specific time frame deeper.




Figure 3-11 Response time of requests by hour


Selecting the request between 10 am and 11 am the report shows a pie chartwith all the requests in this time frame on the selected server group. We can seethe CSMI CICS application with responsiveness as high as 60462 ms. We canalso see the TraderCICSServices application with even higher response times. Inour case we will have a look at the CSMI application. The TraderCICSServicesapplication will be investigated in the next chapter Appendix 3.5, “Compositetransaction analysis” on page 80.




Figure 3-12 Decomposition Report


Click an application for a detail report. We check the CSMI application an thereport shows all the CSMI transactions in the selected hour. We can also see ansymbol on the left of the requests that tells as that the request is a compositerequest (as discussed in the next chapter). The report also tells us the exact timeand date the request was executed and the response time of the request. We willknow have a closer look at one of those requests by selecting the name next tothe composite request symbol.




Figure 3-13 Sorted detail CSMI report


As shown in Figure 3-14, the report shows the flow view of the selectedtransaction. We can see the highlighted CICS EXEC command DELAY that hasan elapsed time of 60s. That is the reason of the overall high response time ofthe CICS transaction. In this case we programed the CICS transaction to sleepfor 60s to show you the possibility of a deep dive analyses of specifiedtransaction.

Note: For detailed information about method calls in the Flow View, you mustbe at L3 monitoring level.




Figure 3-14 Flow View for the transaction in question


3.4.3 Method based reporting

IT is possible to dig even deeper into transactions by displaying every methodcalled by the transaction. To do this we have to configure this option on the datacollector side by editing the toolkit_custom.properties in the<DC_HOME>\runtime\<Server>\ directory.

In Figure 3-15 you will see an report with method details.




Figure 3-15 Method detail report




Figure 3-16 Decomposition report




includes the response time of the CSMI transaktion.In the Figure 3-18 onpage 83 you will see the nesting summary of the CSMI transaction.




Figure 3-18 CSMI transaction

Figure 3-19 shows the CICS transaction in the flow view. You can see theincoming WebSphere based transaction shown as the first arrow. The secondarrow shows the exit form CICS back to WebSpehere.





Figure 3-19 Flow view CICS transaction


3.5.2 In-flight request search

From the in-flight Request Search, the current requests view shows incompleteand running requests on the application server. Most of the time thesetransactions are quite quick, and we cannot actually capture what is happeninginside the transaction.

However, for some slow transactions, we can collect additional information fromthe in-flight request search shown in Figure 3-20.




Figure 3-20 In-flight request list


Figure 3-21 shows the incomplete TraderCICSService in the srv178 server.




Figure 3-21 Incomplete TraderCICSService


In Figure 3-21 on page 86, you can see that the transaction is calling CSMItransaction in CICS. Following the link takes you to the CICS transaction, asshown in Figure 3-22.




Figure 3-22 Incomplete CICS transaction

As we were running in a test environment, we actually injected a delay timer inthe program so we could capture the thread.


3.6 Using Tivoli Enterprise Portal

The Tivoli Enterprise Portal provides a portalized consolidated view of datacollected by ITCAM for WebSphere and J2EE and data collected by other IBMTivoli agents. It also provides mechanisms to tailor views of the data according touser needs.

Tivoli Enterprise Portal can be used by anyone who needs to monitor andanalyze many servers or technology types from a common user interface.Usually this is most beneficial to operational areas supporting many systems orapplication support for complex applications.

The default application monitoring from ITCAM for WebSphere and J2EE is




The default application monitoring from ITCAM for WebSphere and J2EE isshown in the physical navigator tree. This section outlines the features of thephysical views of ITCAM for WebSphere information. It is likely that operationsare more likely to use these views because it is easier to associate aspects of the

application with physical hardware.

Note that most of the information that you can view in the Tivoli Enterprise Portalshould be similar to the information that you collect from ITCAM for WebSphereand J2EE Web console under AVAILABILITY → System Resources.

In the following example we will show the integration into the Tivoli Enterpriseportal from the ITCAM for WebSphere perspective.




processing and the usage of Tivoli Data Warehouse 2.1. Integrating ITCAM forWebSphere with Tivoli Data Warehouse 2.1 means that you make theinformation collected about your J2EE environment available for othermanagement tools such as IBM Tivoli Service Level Advisor or your standardcapacity planning software.

The Tivoli Data Warehouse option is a complement of the available historicalprocessing with the standard reporting function of ITCAM for WebSphere.

Tivoli Enterprise Monitoring Server history is independent of ITCAM forWebSphere data storage. Although you use Tivoli Enterprise Monitoring Serverhistory based on your requirements, there is always a minimum level of historycollection recommended in ITCAM for WebSphere.




ITCAM for WebSphere historical data is used for shorter periods of time toshow transaction behavior. It is not recommended to keep the data for longperiod of time without pruning for performance reason.

Tivoli Data Warehouse solution with Tivoli Enterprise Monitoring Server is anoffline reporting database. Some support of summarization exists there,hence allowing data to be kept for longer period of time to show trends. Theinformation may not be as detailed as the transaction information in ITCAMfor WebSphere database.

In Tivoli Enterprise Monitoring Server we distinguish between to two types ofhistorical information

Short-Term History This refers to historical information stored in flat files forthe specific agent in a 24-hour interval. Short-term historyinformation is generated by accumulating real-time dataand writing it off to history files at predefined intervals.

Long-Term History Long-term history data is stored in Tivoli Data Warehouse2.1. Tivoli Enterprise Monitoring Server allows offloadingshort-term history information to Tivoli Data Warehouse2.1 at definable intervals. The offload is handled by theso-called Data Warehouse Proxy.


Both types of historical information can be displayed in the Tivoli EnterprisePortal, enabling you to combine historical information with real-time data, asshown in Figure 3-28. Reporting against Tivoli Data Warehouse 2.1 can be doneby using the standard reporting tools in your installation.

Tivoli Data Warehouse 2.1Tivoli Enterprise Management Server

Real-time data

(Memory, refresh

every x minutes)

Short TermHistorical data

(Binary file: 24 hours

life time)

Long Term

Historical data




Figure 3-28 Tivoli Enterprise Monitoring Server historical processing

Tivoli Data Warehouse 2.1 supports the DB2 UDB, Microsoft SQL Server, andOracle databases. The Warehouse Proxy Agent is the interface between TivoliEnterprise Monitoring Server and Tivoli Data Warehouse 2.1, and it is used totransfer short-term history data into the database system used by Tivoli DataWarehouse 2.1. Note that granular data that is available in short-term history filesis transferred. All data management within Tivoli Data Warehouse is done by theSummarization and Pruning Agent. Data can be aggregated at various levels(yearly, quarterly, monthly, weekly, or hourly), and obsolete data can be pruned atregular intervals. An example is summarizing and averaging hourly CPU usagedata at a daily or weekly level. For more information about Tivoli Data Warehouse2.1 and Tivoli Enterprise Monitoring Server historical processing capabilities, seeGetting Started with IBM Tivoli Monitoring V6.1, SG24-7143.

Tivoli Enterprise Monitoring Server history information is defined and activated atagent level. Figure 3-29 on page 96 shows the standard Historical CollectionConfiguration for Tivoli Enterprise Monitoring Agent for ITCAM for WebSphere .History is activated out of the box for the attribute groups:

Application_Server Garbage_Collection_Analysis

Request_Times_and_Rates Thread_Pools

Attribute groups

Attribute groups

Attribute groups





Figure 3-29 ITCAM for WebSphere - History collection configuration

Note: Historical data collection can be defined to happen at Tivoli EnterpriseMonitoring Server of Tivoli Enterprise Monitoring Agent level. You may changethis setting depending on your environment.


Figure 3-30 shows an example of how to use historical data in Tivoli EnterprisePortal. This shows the WebSphere App Server workspace coming with the TivoliEnterprise Monitoring Agent for ITCAM for WebSphere. It uses historicalinformation for an overview of the activities in a particular WebSphere ApplicationServer. In this case we use short-term history information to display heap usage,average response time, request rate, and CPU usage over the past hour.




Figure 3-30 Historical information with TEP

The graph also il lustrates the advantages of combining ITCAM for WebSpherewith other Tivoli Enterprise Monitoring Server agents. From looking at thisworkspace we learn that the WebSphere Application Server heap size does notappear to be optimal for this Windows® machine. The Tivoli EnterpriseMonitoring Server Windows agent, which is also installed on this machine,generates an alert (note the small red icon with a cross in the Windows Memoryfield in the navigation tree) indicating that Windows is running out of memory. Inthis special case, Windows is already complaining about memory constraints, butWebSphere Application Server still has not reached it defined memory limits.(See the heap usage graph in Figure 3-30).


3.8 JBoss application server data collector

ITCAM for J2EE data collector supports several J2EE application server toperform diagnosis of web applications and services. The functionality andmanagement of J2EE data collector is similar to the WebSphere ApplicationServer data collector in ITCAM for WebSphere.

This chapter discusses a usage scenarios for JBoss application server datacollector within our environment and explores the new functions of ITCAM forJ2EE. We manage the software traps set on your system on the Trap and AlertManagement page. Trap and Alert Management influence the presentation onthe enterprise overview and operator assignment, affecting the display. Trapsand Alerts show how transactions behave, and the method trace is helpful forfurther analysis




further analysis.

The steps documented in this section take place after installation and

configuration of JBoss application server. We assume that you are familiar withthe functionality of JBoss application server and finished installation processingfor those components successfully.

We configured and customized the JBoss application server and the ITCAM forJ2EE data collector for JBoss based on instructions in the corresponding chapter2.4.3, “J2EE data collector installation” on page 41.

This scenario shows how to create, modify and activate a trap for serverresources and application, in order to get a component method trace for furtheranalysis. Managing the software traps in menu Trap and Alert Management inITCAM for J2EE is described on the basis of a sample web application.

Ensure the J2EE data collector for JBoss is running and appears in theenterprise overview page in ITCAM for J2EE, as shown in Figure 3-31,“Enterprise overview showing active JBoss” on page 99.

Note: The runtime environment in our sample configuration use JBossapplication server Version 4.0.4 GA on Red Hat Enterprise Linux AS version 3(Taroon Update 7). The default configuration including a default profile ofapplication server is used.


Figure 3-31 Enterprise overview showing active JBoss

Additional in Figure 3-32 on page 99 the complete configuration and setting for




Additional in Figure 3 32 on page 99 the complete configuration and setting forITCAM for J2EE is shown in the JBoss Web Console for review.

Figure 3-32 JBOSS configured for ITCAM

The simulation of the scenario is described as follows:

One web application runs nicely with an average cpu time below 1 ms. Thesituation changes and randomly a high cpu time consumption attractsattention in the reports. To analyze the reason, ITCAM for J2EE provides thetrap and alert management to force a snapshot for this web application atruntime.

In our environment we deployed a long running sample application, to havethe possibility to make a snapshot of active threads. The Figure 3-33 on


page 100 demonstrates the view of this long running thread in the ITCAM forJ2EE console in menu Server Activity Display→ Recent Requests.




Figure 3-33 Request detail of recent requests of sample application

Perform the following steps to create a trap event for the appropriate webapplication.

1. Select in the main menu in ITCAM for J2EE the function for Trap and Alert

Management, using PROBLEM DETERMINATION→

Trap & AlertManagement. The Trap and Alert Management page appears, to manage thesoftware traps set on your system. The overview page show the current activetraps and trap profiles, which can be activated, modified, duplicated, ordeleted.

2. To create a new trap profile, use the Create Trap selection from the menu.The first step page for the setting is displayed in Figure 3-34 on page 101. Onthis page, select the trap type and the target type of resource. In our case,referring to Figure 3-34, we select:

Trap Type Application TrapTarget Type CPU Time

Click Next for further definition steps.


Figure 3-34 Create application trap - step 1




g pp p p

3. To define the trap, the setting of value threshold and the content must be

provided. The content is divided by request or by method. The settingmatches the request and will trigger the trap. The threshold is a level set thatwill cause an alert when the system count exceeds the defined threshold. Asshown in Figure 3-35 on page 101, we define the values of the sample webapplication:

Threshold(ms) 2By Request ITCAMTest

Click Next to set trap alerts.





5. Finally enter a trap profile name and description. Click Save & Activate tofinish the configuration process and activate the trap immediately. Otherwiseclick Save to store the trap profile in the trap profile list. Figure 3-37 onpage 103 shows the last configuration step. In our case we activate the trapimmediately with option Save & Activate. Therefor the activation process andconfiguration page appears.





6. To activate the trap profile a few settings, like server selection, alertsuppression and deactivation, are needed. Select an entire group of serversor select only a specific server, where the trap needs to be activated. Choosethe setting of the time period of alert suppression. To the end, the deactivation

of the trap is specified either by time period or number of occurrences. We setup following settings, as shown in Figure 3-38 on page 104:

Server filter JBOSSServer srv180.default(L3)Alert suppression 15min (Trap default)Deactivation 5 (Number of occurrences)





Figure 3-38 Activate application trap

After finishing the trap activation process, you see the new trap profile namedITSO JBOSS TRAP EXAMPLE1 in the active traps list in the trap and alertmanagement page, as illustrated in Figure 3-39 on page 105.


Fi T d Al i li




Figure 3-39 Trap and Alert management - active trap list

Triggering now the active trap by requesting the designated web application.During the request the trap executes automatically a component method traceand store the trace in the data base. In ALERTS AND EVENTS managementpage the processed trap with profile name, server occurrence and time stamp islisted, like in Figure 3-40 on page 105. This figure shows the new predefined trapprofile in our environment, that occurred and executed in the JBoss applicationserver.

Figure 3-40 Alerts and events management

The analyzing process for the component method trace starts atop the Trap &

Alert Management page. The data can be retrieved using the trap action history


from the menu of PROBLEM DETERMINATION→ Trap & AlertManagement→ Trap Action History. The Trap Action History provides a recordof traps that met the set conditions. Choose the appropriate action and click onMethod Trace. The TRAP METHOD TRACE page is displayed in Figure 3-41 onpage 106.




Figure 3-41 Trap method trace - summary view

Analyze the composition of methods in the request, the nested summary allowsyou to quickly access the likely causes of problems within a request, separatedby J2EE API calls. The trap method trace provides for problem determinationfollowing views:

• Drill down View

• Flow View

• Search specific characteristic view

Refer to our sample web application, the drill down view supports a navigationthrough completed method traces one level at a time, as shown in Figure 3-42 onpage 107. Data as execution order, event type, event data, resident time andCPU time is provided for each entry.





Figure 3-42 Trap method trace - drill down view

The Flow View presents method events in their order of execution, and lets youidentify slow or expensive methods using the Threshold High lighter, and exportthe method trace to a file or email. Depth is ordered by servlet entry and servletexit and indicates the elapsed time and cpu time. In Figure 3-43 on page 108 theflow view of our method trace is displayed.





Figure 3-43 Trap method trace - flow view

Draft Document for Review March 1, 2007 5:22 pm 7151ch-RTT-install.fm

4




Chapter 4.

ITCAM for Response TimeTracking concepts andinstallation

This chapter describes the implementation of ITCAM for Response TimeTracking in our environment. It includes:

4.1, “Product architecture” on page 110

4.2, “Management methodology” on page 120

4.3, “Implementation process” on page 123

4.4, “Installation of ITCAM for Response Time Tracking” on page 129

4.5, “Monitoring components deployment” on page 159

4.6, “Initial configuration and usage” on page 179

7151ch-RTT-install.fm Draft Document for Review March 1, 2007 5:22 pm

4.1 Product architecture

ITCAM for Response Time Tracking V6.1 is an evolution from IBM TivoliMonitoring for Transaction Performance V5.3. It inherits the major componentsand functions of IBM Tivoli Monitoring for Transaction Performance V5.3.

Figure 4-1 shows ITCAM for Response Time Tracking components.

RTT

Management

server

RTT

Store and

forward agentL

LL

L

RTT

Store and

forward agent

RTT

management

agent




Figure 4-1 ITCAM for Response Time Tracking components

Basically, ITCAM for Response Time Tracking is controlled from the managementserver. The management server provides a centralized repository of policy,configuration, and data for the ITCAM for Response Time Tracking environment.

The rest of ITCAM for Response Time Tracking are the management agents. Themanagement agents perform performance and response-time data collection onbehalf of the management server. The agent can perform response timecollection from an application server or perform robotic simulation of a

transaction for measuring response time. The management agent functions as asingle agent that can have different monitoring components deployed on them toperform different functions.

The management server and management agent typically operate in anunrestricted port environment. When there is a firewall between them, theyrestrict the port usage to communicate. The firewall requirement typicallyrequests that they use a single communication port to talk back and forth. This iswhere the store-and-forward agent comes in. It bundles the management

communication between management server and management agent to use asingle port to pass through the firewall. The store-and-forward agent can be

RTT

management

agent

RTT

management

agent

RTT

management

agent

RTT

management

agent

F I R E

W A L

F I R E

W A L

Tivoli

Enterprise

Management

Agent


cascaded, so in this sense there can be a chain of store-and-forward agents topass through multiple layers of firewalls.

A special management agent resides on z/OS machines. The managementagent on z/OS machines has the transaction server component activated toreceive performance information from CICS and IMS data collector.

In ITCAM for Response Time Tracking V6.1, information from the management

server can be forwarded to Tivoli Enterprise Monitoring Server for display in theTivoli Enterprise Portal. This is achieved using the Tivoli Enterprise MonitoringAgent for ITCAM for Response Time Tracking.

We discuss the components of ITCAM for Response Time Tracking in thefollowing sections:

4.1.1, “The management server” on page 111 4 1 2 “Store-and-forward agent” on page 113



Chapter 4. ITCAM for Response Time Tracking concepts and installation 111

4.1.2, Store and forward agent on page 113 4.1.3, “Management agents” on page 114 4.1.4, “Tivoli Enterprise Monitoring Agent” on page 117 4.1.5, “ARM concepts” on page 118

4.1.1 The management server

ITCAM for Response Time Tracking management server consists of a J2EEenterprise application that accesses a DB2 repository using JDBC. Themanagement server runs on WebSphere Application Server. The application

server can be installed on a stand-alone WebSphere Application Server or on aclustered environment. Figure 4-2 shows a stand-alone management server.

Figure 4-2 Stand-alone management server

Management server

DB2

WebSphere Application Server


Figure 4-3 shows the clustered management server. It consists of WebSphereEdge Server for load balancing, the management server on several clusteredWebSphere Application Server Node Deployment systems, and the databaseinstalled on a separate database server.

WebSphere Node

Deployment Cluster

DB2

WebSphere

Application Server

WebSphere Edge

Server




Figure 4-3 Clustered management server

A clustered management server benefits include:

Separating the servers reduces the processing burden of a single machine.

Allows fail-over for failure in WebSphere Application Server, so the othermanagement server in the cluster can take over the work.

Some disadvantages are:

Overhead of communication between machines.

More difficult setup; refer to IBM Tivoli Composite Application Manager for

Response Time Tracking V6.0: Installing a Management Server in a WebSphere Cluster Environment , SC32-1804, for installation instructions.

Overall, regardless of the management server types, the management serverprovides the following functions:

Managing management agents and their deployed components.Management agents must sign in to the management server and retrieve allrequired policies when it is started initially.

Storing policies for management agent operation, including discoverypolicies, listening policies, and playback policies. These policies are

maintained using the Web interface or the new command line interface.

WebSphere Application Server


Managing a schedule repository; note that the schedule application will beperformed by the management agent.

Performing data collection from various management agents and storingthem in its repository.

Maintaining users and roles for accessing the Web interface.

Serving the Web interface.

4.1.2 Store-and-forward agent

The store-and-forward agent acts as an intermediary between managementserver and management agent. Figure 4-4 shows its overall processing.

Store and Forward

1976




Figure 4-4 Store-and-forward agent

This agent consolidates communication from and to management agents anduses a single port to communicate to the upstream component. Thestore-and-forward agent can be cascaded. It uses IBM WebSphere Caching

Proxy, which is part of the WebSphere Edge Server 2.0. The caching proxyenables optimization of connection with the management server.

The default port, to which the management agent must connect, is 9446 for SSLor 80 for non-SSL.

You can have multiple store-and-forward agents chained to get to themanagement server through multiple layers of firewalls. Figure 4-5 shows thisconcept.

Figure 4-5 Multiple store-and-forward agents

RTT

Managementserver

RTT

Managementagent

Store and Forward

agent

Caching

Proxy

80

1976

9081

Management

Server

Management

agent

Store and

forward

agent80

Store and

forward

agent

80


4.1.3 Management agents

The management agent runs in a Java Virtual Machine on the managed server. Ittypically performs the following functions:

Starting and stopping the management components Collecting monitoring and schedule information from the management server Informing the management components about what to perform

Caching response time data in the temporary directory Uploading response time data as requested by the management server,either at regular collection time or on demand.

The management agent behavior is based on the Application ResponseMeasurement (ARM) specification. More discussion on ARM is provided in 4.1.5,“ARM concepts” on page 118. The management component monitors measureresponse time and reports them using the ARM specification to the ARM agentprocess (tapmagent executable). The ARM agent process stores response time




p ( p g ) g p pinformation on physical disk. The management agent will upload the responsetime information to the management server at the regular interval.

There is a slight difference between distributed management agent architectureand the z/OS-based management agent.

Distributed management agentConceptually the processing of the management agent can be illustrated asshown in Figure 4-6.

Figure 4-6 Management agent

ARM agent

Management

agent

J2EE

monitoring

component

Client

Application

Tracker

Generic

WindowSTI client

QoS Apache

reverse

proxy

Web

Response

Monitor


The existing management components are:

A generic window component that allows investigation of a Windows-basedapplication to use with Rational Robot application. This enables the robot tointeract with a native Windows application, a Java application, or abrowser-based application. This can be deployed only on a Windows system.

Synthetic Transaction Investigator (STI): Simulates user interaction with a Webbrowser. STI transactions are recorded in advance using the STI recorder

application. The STI component can be deployed only on a Windows system.

Quality of Service (QoS): QoS runs in an Apache Web server proxy thattracks the response time for an end user. It inserts a small Java script forHTML code to reply back to QoS and indicates the overall end-user responsetime. Figure 4-7 on page 115 outlines QoS processing.

QoS

Apache reverse proxyBack-end Web server

End user with Web

browser




Figure 4-7 QoS processing

J2EE instrumentation component: Runs as JVMPI instrumentation for a

J2EE-compliant Web application server such as WebSphere ApplicationServer or BEA WebLogic. It monitors certain WebSphere classes to collectinformation about servlets and Web services calls. It also collectsresponse-time information for JDBC connections and J2C accesses.

ARM agent: The ARM agent is implemented as the executable tapmagent, asit was historically called Tivoli Application Performance Manager.

Web Response Monitor (WRM): measures the performance of Web-basedapplications, provides response time and other performance data and tracks

navigation paths and usage behavior.

Overall

response time

Apache reverse proxy

Back end

processing

time

Page

render

time

Round trip

time

browser


Mainframe management agentFor z/OS-based systems, ITCAM for CICS Transactions and ITCAM for IMSTransactions data collectors can send transaction start and transaction endevents to the management agent running on the same z/OS system as the CICSand IMS started task. These start and stop events for CICS and IMS transactionare translated into ARM start and ARM stop calls by a component called theTransaction Server. This allows IMS and CICS transactions to be shown as partof the distributed transaction or as a stand-alone transaction running on z/OS.Figure 4-8 on page 116 shows the z/OS based management agent structure.

ARM agent

Management

agent

Transaction Server

ITCAM for

CICS

Transactions

ITCAM for

IMS

Transactions




Figure 4-8 Mainframe management agent

The components of the management agent in z/OS are:

Management agent The management agent is responsible for communicationwith the ITCAM for Response Time Tracking managementserver and collecting ARM-related activities on behalf of

CICS and IMS. The ARM engine or tapmagent is part ofthe management agent; it enables you to integrate anyother ARM-instrumented application with ITCAM forResponse Time Tracking.

CICS data collector The CICS data collector monitors transaction responsetimes within CICS regions. It gives you information abouthow long it took to run the transaction in the monitoredCICS region. If your CICS transaction flows throughseveral CICS regions, installing CICS data collectors in

Note: The transaction server component is activated by default in all platformsthat we installed. Only z/OS management agent can use this feature. You cansee which components are started from configuration file tmtp_sc.xml.

J2EE

monitoring

component


every region involved enables you to track the completetransaction flow.

IMS data collector The IMS data collector monitors transaction responsetimes within IMS regions. This means you get informationabout how long it took to execute the single transaction inthe monitored IMS region. If your IMS transaction spansmultiple IMS regions, you can monitor the complete

transaction flow by installing the IMS data collectors in theregions that are involved.

The IMS data collectors and CICS data collectors report to the transaction serverportion of the ITCAM for Response Time Tracking management agent on thez/OS machine on which they execute.

4.1.4 Tivoli Enterprise Monitoring Agent




The agent for Tivoli Enterprise Monitoring Server for ITCAM for Response TimeTracking is provided as a separate installable feature. Figure 4-9 shows theconnectivity of the Tivoli Enterprise Monitoring Agent for ITCAM for ResponseTime Tracking.

Figure 4-9 Tivoli Enterprise Monitoring Agent

The ITCAM for Response Time Tracking agent is assigned the code KT2. TheTivoli Enterprise Management Agent components must be installed in the TivoliEnterprise Monitoring Server, Tivoli Enterprise Portal Server, and TivoliEnterprise Portal.

ITCAM for Response Time Tracking provides a workspace that is dynamicallylinked based on the policy groups that are available on the management server.

ITCAM for RTT

Management server

DB2

WebSphere

Application Server

Tivoli Enterprise

Management Agent

Tivoli Enterprise

Management Server

Tivoli Enterprise

Management Server




Figure 4-11 shows a more complex ARM calling sequence in which a distributedapplication calls across several modules. Each module should provide its owninstrumentation to call ARM APIs.

m a i n P r o g

s u b 1

s u b 1 1

a r m S t a r t ()

a r m S t a r t ()

a r m S t a r t ( )

a r m S t o p ( )

a r m S t o p ( )

c a l l

c a l l




Figure 4-11 ARM concepts: complex application

Distributed application programs can be viewed as multiple components ofprograms that are called independently. The overall response time of theapplication is broken down into response time components that may not resideon a single machine, thus complicating performance analysis. The objective ofARM is to enable response time tracking and analysis for these components andidentify them in a big picture.

In Figure 4-11 on page 119, ARM acts in its basic function as a digital stopwatch.It records the start and end of transactions using the armStart() and armStop()calls. As the program makes a call to its subprogram—which can use Webservices, Remote Procedure Call, or any other means—it also passes acorrelator, which enables the ARM server to identify the relationship of theresponse time components. The same correlator is passed from the calling

m a i n P r o g

s u b 2

s u b 2 2

s u b 2 1

a r m S t o p ( )

a r m S t a r t () a r m S t a r t ( )

a r m S t a r t ( )

a r m S t o p ( )

a r m S t o p ( )

a r m S t o p ( )

c a l l

c a l lc a l l


program to all of its subprograms. The calling sequence is of no importance toARM.

To use ARM, the application program must:

1. Initialize the ARM environment.2. (Optional) Collect ARM correlator.3. Indicate the start of the transaction.4. (Optional) Pass ARM correlator to subtransaction.5. Indicate the end of the transaction.6. Clean up ARM resources.

The ARM start and stop API calls actually send a small packet of data to theARM agent that is specified in the initialization logic. This data is then interpretedand response time is calculated. The correlator is used to show transactionhierarchy so that response time components can be analyzed.

The ARM API provides an implementation specification for both the C language




p p p g g

and Java-based programs. In this book, we discuss only Java implementation ofARM API using ITCAM for Response Time Tracking. Instrumenting applicationwith ARM calls enables ITCAM for Response Time Tracking to display customapplication topology other than the default instrumentation structure. Thisenables the application programmer to show better structuring of the applicationresponse time.

The Java implementation of ARM API is defined in a set of interfaces. TheseJava interfaces are provided from the software Open Group. Specific vendor

implementation should only implement these interfaces to provide the functionneeded for response time measurement.

ITCAM for Response Time Tracking implementation or ARM for Javaimplementation uses Java Native Interface (JNI) calls that are made on thespecific platform. For ARM Version 4, the required JAR file to load is calledarmjni4.jar and it needs also the corresponding shared native library to beavailable.

4.2 Management methodology

For ITCAM for Response Time Tracking, several management resources andcertain terminology will be used. We discuss them in this section. The discussionhere includes:

4.2.1, “Management resources” on page 121 4.2.2, “Reporting group and agent group” on page 121

4.2.3, “Management implementation overview” on page 123


4.2.1 Management resources

The management resources for ITCAM for Response Time Tracking are:

Reporting group A grouping for monitors that share certain properties.

Agent group A grouping for management agents that enables policiesto be applied to all its members.

Schedule Time rules on which policies should be active.

Discovery Activity to find transaction or other server processing.

Listening monitor Activity to collect server based response time informationfrom applications.

Robotic monitor Activity to send automated transactions, either usingClient Application Tracker, STI or Rational Robot.

Out of these resources, the important concepts that must be discussed are policygroup and agent group.




g p g g p

4.2.2 Reporting group and agent group

This section discusses the groups that are used in ITCAM for Response TimeTracking, the reporting group and agent group.


Agent groupAn agent group assists monitor deployment. The agent group determines onwhich machines the monitor executes. Figure 4-12 shows an example of agentgroup consideration.

` ``

Trading

eBanking




Figure 4-12 STI agent groups for multiple applications

Figure 4-12 shows three management agents for monitoring two applicationsfrom geographically separate sites. In this scenario, we want to execute monitorfor the Trading application on both Agent1 and Agent2. However, the eBankingapplication is available only in Europe, and the agent monitor for eBanking isdeployed to Agent2 and Agent3. This case requires the Trader clients andeBanking clients agent group. You may also need to have an agent group basedon the location, so that USA clients and Europe clients can deploy local monitor.

You can create the agent group before creating any monitors using

Configuration→ Agent Groups. Alternatively, you can create the agent groupwhen you create the monitor; however, some implementations may want torestrict this function to allow only the system administrator to add agent groups.

Reporting group Reporting group differs from agent group in that it does not directly affect theexecution of monitors. A reporting group can be used to control access to certainfunctions, using new role definition. Roles can be defined to allow read or updateaccess for monitors inside the reporting group.

USA Europe

eBanking clients

Trader clients Agent1 Agent3 Agent2




We discuss which monitors to use and whether or not before the monitoringcomponents deployment. It is important to have good understanding of themanagement agent deployment. The Table 4-2 helps you determine whichmonitoring components to use for deployment.

Table 4-2 Determing points for the monitoring components deployment

Note: Before deploying any monitoring component, a management agentinstallation is required on the target box.

If you want to... Monitoring

components

Monitor user transactions on an IBM HTTP server. For example,use this if you want the following measurements: The time it takes the Web server to process and respond to

the HTTP request

The time it takes to display Web page on a browser

Web ResponseMonitor




The time it takes to display Web page on a browser The time it takes to complete the entire page request

(round-trip time). It includes the previous two times andnetwork and data transfer time

Monitor the internals of the infrastructure server, such asWebSphere Application Server, WebSphere Portal products,WebLogic, Tomcat, or JBoss so that you can do the following: View detailed reports so you can perform root-cause

analysis

Identify the exact cause of slowdowns and bottlenecks Monitor Business Process Execution Language (BPEL)

processes running on a WebSphere Process Server

For WebLogic andWebSphere, useJ2EE Servlet. ForTomcat and JBoss,use the Tomcat and

JBoss monitors.

Monitor response time data for Web services invocations. J2EE WebServices

Monitor the performance of ARM-instrumented applications,such as Siebel® and it has no XML file.

ARM Application

Monitor user response times for Lotus® Notes®, Microsoft

Outlook®, SAP, 3270 emulators, or applications running in aCitrix environment.

Client Application

Tracker

Run a custom application, script, or command and see results.For example: Testing server availability with FTP, telnet, or ping Querying a database with a custom SQL command Running a custom shell script

Generic Playback


We decided to deploy the management agent on:

All WebSphere Application Servers that host the Trader applications

CICS and IMS servers

Tomcat and JBoss Application Servers

Generic Windows(it runs Rational Robot), Arm Application, Web Response

Monitor Quality of Service Client Application Tracker Generic Playback and

Perform transaction decomposition by one of the followingmethods: Viewing detailed reports so you can perform root-cause

analysis Identifying the exact cause of slowdowns and bottlenecks. Monitoring back-end service, page render, and round-trip

times.

SyntheticTransactionInvestigator withboth Quality ofService and J2EEthresholds

If you want to... Monitoring

components




Monitor, Quality of Service, Client Application Tracker, Generic Playback andSynthetic Transaction Investigator servers

Our overall configuration for ITCAM for Response Time Tracking is shown inFigure 4-13.


khartoum

TEMA

ITCAMRTT

database

ITCAM for RTTManagement Server

lima

win2003

ITM 6.1 server

tivaxv

win2000Pro

Client Application Tracker

srv179

RHEL

Generic Windows

ARM Application

perth

RHEL

Tomcat

JBoss

srv176

RHEL

J2EE

wtsc65

z/OS

J2EE, IMS, CICS




Figure 4-13 ITCAM for Response Time Tracking configuration

4.4 Installation of ITCAM for Response Time Tracking

The installation discussion is divided into the following:

4.4.1, “Management server installation” on page 130

4.4.2, “Store and forward agent installation” on page 140 4.4.3, “Distributed management agent installation” on page 144

Management agents

srv181

Win2003

STI

laredo

win2003

QoS

Generic Windows

Web Response Monitor

srv177

RHEL

J2EE

srv178

RHEL

J2EE

Note: The z/OS based management agent implementation is discussedseparately in <>.




– User account information for WebSphere Application Server process– Administrative console port– WebSphere Application Server installation directory

DB2 database parameter:

– DB2 installation image path– DB2 administration server, fenced and instance owner user accounts– DB2 installation directory

The installation of ITCAM for Response Time Tracking management server usestwo CD-ROMs; the first CD is platform specific and the second is platformneutral. The wizard copies files from both CD-ROMs files onto the disk. If youcopy these CD-ROM images to disk manually, you must copy both CD-ROMs’content into the same path; otherwise, the installation wizard will fail.

The installation wizard is launched from the first disk using the launchpad command or by invoking the appropriate setup_MS executable. This is the way theinstallation goes:

1 Run launchpad sh where the installation files are located LaunchPad can




1. Run launchpad.sh where the installation files are located. LaunchPad canprovide installation prerequisites, installation guide, product support, productupdate and install ITCAM.

Figure 4-14 LaunchPad


2. We use the installation directory /opt/IBM/itcam/RTT/MS as the defaultlocation.

Fi 4 1 I ll i h




Figure 4-15 Installation path

3. The typical installation wizard can install an embedded WebSphereApplication Server as shown in Figure 4-16.

Figure 4-16 WebSphere Application Server installation


4. The management server using several ports. We use SSL for managementserver communication instead of non-SSL. It use port for the managementserver console with 9445. The non-SSL connection from management agentsor CLI will go through port 9081. The SSL port is 9446 as shown inFigure 4-17.




Figure 4-17 Port and SSL usage

Note: To enable SSL for management server communication, it also need toenable WebSphere Application Server global security. The typical installation

does not support to enable WebSphere Application Server global security ininstallation process. And we enable global security through WebSphereApplication Server after ITCAM for Response Time Tracking installation. SeeFigure 4-18.


Figure 4-18 Global security enable

5. The next installation is for WebSphere Application Server. It requiresinformation configuring WebSphere Application Server as shown in

Figure 4-19.




Figure 4-19 WebSphere Application Server parameters

6. The installation connect to database installation. We select Install DB2 in

database options as shown in Figure 4-20.





Figure 4-20 Installation DB2

7. DB2 installation requires database user account information.

– Figure 4-21 shows DB2 administration server user account input window.

Figure 4-21 DB2 admin user account

– Figure 4-22 shows DB2 fenced user account input window.


Figure 4-22 DB2 fence user account

– Figure 4-23 shows DB2 instance owner user account input window.




Figure 4-23 db2 instance user account

8. Fill in the installation path for embedded product installation. The wizardrequests the installation image path of WebSphere Application Server andDB2. WebSphere Application Server must be Version 6.0 with Refresh pack2; while DB2 must be on version 8.2 Modification level WR21342.





Figure 4-24 Installation image location

9. The installation window shows acceptance embedded product installationdirectories and ITCAM for Response Time Tracking management server

installation directory.

Figure 4-25 Product installation directory


10.The wizard starts an embedded WebSphere Application Server and DB2installation. It then installs ITCAM for Response Time Tracking managementserver, creates the database and configures the management serverapplication.

11.After the typical installation, we can access the management server usingInternet Explorer® as shown in Figure 4-26.

https://<management server hostname>:9445/tmtpUI/




Figure 4-26 Management server console


Note: If you change password of db2inst1 account after ITCAM for ResponseTime Tracking installation, you get the following error message in logonwindow.

BWMVZ2175E The server could not find the table USERSETTINGS in thedatabase

You must change the password for JDBC provider in WebSphere Application

Server.1. In the WebSphere Application Server admin console go to Resources→

JDBC Providers→ DB2 Universal JDBC Driver Provider - TMTP→ Data Sources.

2. Correct the password that is used to access the DB2 database for all ofTMTP related datasources. In the data sources window click TMTPDataSource in turn go to J2EE Connector Architecture(J2C)

authentication data entries→ db2Alias and change the password for

db2inst1 user account.3. Save the changes and restart WebSphere Application Server.




Installation of DB2 fix pack 8 is recommended for DB2 stability. However, ITCAMfor Response Time Tracking management server pre requisite database versionis DB2 8.2. You can download DB2 fix packs from the site:

http://www-306.ibm.com/software/data/db2/udb/support/downloadv8.html

When applying DB2 fix packs on Linux servers, refer to Example 4-1 steps fordb2 update completion. It stops the DB2 instances, installs the fix pack, updatesthe instances and restarts the DB2 instances.

Example 4-1 Installation DB2 fix pack

# su - db2inst1 -C db2 force application all# su - db2inst1 -C db2stop# su - dasusr1 -C db2admin stop# ./installFixPak

# /opt/IBM/db2/V8.1/instance/db2iupdt db2inst1# /opt/IBM/db2/V8.1/instance/dasupdt dasusr1# su - db2inst1 -C db2start# su - dasusr1 -C db2admin start


4.4.2 Store and forward agent installation

Note to Author: I tried to install SnF on laredo which was installed QoS, WRM andGenric Windows. All of monitoring components and agent removed and tried to installSnF, but MS connection error occurred.Error Message in trace-install.log:[2006-11-03T10:25:46.922-06:00] - MID - laredo - AWT-EventQueue-0 -

com.ibm.tivoli.transperf.install.tp.ismp.wizard.panel.endpoint.StoreForwardAgentPanel.testMSConnection() - java.lang.reflect.InvocationTargetException

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)....Caused by: javax.net.ssl.SSLHandshakeException: unknown certificate

at com.ibm.jsse.bs.a(Unknown Source)at com.ibm.jsse.bs.startHandshake(Unknown Source)at com.ibm.net.ssl.www.protocol.https.b.o(Unknown Source)

....I searched the CAST site, it may be some corruption in keyfiles due to

6.1-ITCAMRTT-FP0001 installation. If the FP0001 GA release, please proceed SnFinstallation at that time.




Store and forward agents are needed when firewalls separate managementagents from the management server. Installing the store-and-forward agentrequires the IBM WebSphere Caching Proxy 6.0. This is part of the WebSphere6.0 Edge Components. We found that the following tips help when installing thestore-and-forward agent:

Specify Install from CD so that the installation files are copied to a temporarydirectory on the local disk.

It is best to install WebSphere Caching Proxy separately to avoid restarting inthe middle of installation.

Do not install from disk because the installation directory will be wiped out.

The store-and-forward agent installation is performed as follows:

1. We install the store-and-forward agent into C:\IBM\itcam\RTT\SnF(Figure 4-27).


Figure 4-27 Installation path for store-and-forward agent




3. Further attributes for the store-and-forward agent indicate the managementserver address and the authentication user. We use the primary ITCAM forResponse Time Tracking user that we defined when installing themanagement server (Figure 4-29). Here we also define the managementagent endpoint filter. The filter is a regular expression filter for themanagement agent IP addresses.




Figure 4-29 Additional store-and-forward agent properties


4. The wizard requests a certificate that may have to be used and the user IDthat is used to start the agent.

If WebSphere Caching Proxy is not installed, the wizard requests the path ofthe WebSphere Edge Components V6 CD as shown in Figure 4-30.




Figure 4-30 WebSphere Edge Component CD image

4.4.3 Distributed management agent installation

In this section, we describe the main steps of the management agent installation.Installation considerations:

For a Windows system:

– Ensure access to the following user rights:• Act as part of the operating system• Create a token object• Log on as a service• Replace a process level token• Shut down the system

– Configure Windows component permissions using the dcomcnfg command. Figure 4-31 shows the dialogs for Windows 2003. This is


required for the management agents running Robotic monitoringcomponents.




Figure 4-31 Component permission

For UNIX or Linux systems: Ensure that you have X-Windows access. If youare running from a command line session, make sure you have access to an

X-server and export your DISPLAY environment variable accordingly.

To install the management agents:

1. We install all management agents for our environment as shown inFigure 4-13 on page 129. The installation is platform dependent. In generalthese are the options that we use:

– Path that has no spaces in Windows, such as C:\IBM\itcam\RTT\MA andthe default path using in Linux, such as /opt/IBM/itcam/RTT/MA. This is

useful for command line processing with ITCAM for Response TimeTracking.

– MS host name field must be the proper hostname for your managementserver our server is khartoum.itsc.austin.ibm.com

– User and password for the management server, for Linux installation, wecan use the root user as shown in Figure 4-32

– For the non secure installation, uncheck the Enable SSL radio box asshown in Figure 4-32





Figure 4-32 Management agent option

– Use an existing user account in Windows, which is Administrator andspecify user account in Linux, which is root as shown in Figure 4-33.


Figure 4-33 User account for management agent




2. The installation wizard progresses ITCAM for Response Time Trackingmanagement agent installation. After the installation work, you can seeFigure 4-34 for launching ITCAM for WebSphere Data Collector automatically.If you select Yes, Install, it starts with ITCAM for WebSphere Data Collectorinstallation.

Figure 4-34 Launching for ITCAM for WebSphere Data Collector installation


3. Verify ITCAM for Response Time Tracking management agent installation bylooking at the Status field on System Administration→ Agents.

4.4.4 Installing ITCAM for Response Time Tracking fix pack 1

In this section, we describe coexistence method ITCAM for J2EE data collectorand J2EE monitoring component of ITCAM for Response Time Tracking on thesame WebSphere Application Server. It has been the defect that the toolkit’s

setting is overriding by ITCAM for Response Time Tracking installation. It is fixedby 6.1.0.0-TIV-RTT-FP0001 for ITCAM for Response Time Tracking V6.1. Youcan download the product fix pack from this site:

http://www3.software.ibm.com/ibmdl/pub/software/tivoli_support/patches/

The following procedure is for installing the fix pack on the Management Server:

1. Extract the 6.1.0.0-TIV-RTT-FP0001 tar file.

2. Run the 6.1.0.0-TIV-RTT-FP0001_lin.bin and show installation wizard as

shown in Figure 7-43. To continue click Next.




Figure 4-35 The fix pack installation wizard


3. Read the information and click Next.

4. Check the management server location and click Next.

5. Confirm the WebSphere Application Server value and click Next.

6. Check the installation options and click Next, it starts with the fix packinstallation on the management server.

7. After installing the fix pack, you can check error in installation_log.txt file.

Note: If you meet installation error a similar the following messages ininstallation_log.txt file, it caused by the SOAP timeout is too small.

wsadmin.sh -javaoption -Xms128m -javaoption -Xmx256m -conntype SOAP-port 8880 -user root -password its0g00d -f/opt/IBM/itcam/RTT/MS/ear/updateEAR.jacl Failed status code: 105

Setup.product.install, com.tivoli.ismp.ExecCommandProductAction,err, An error occurred while updating the EAR Binaries for

WebSphere. For more information refer to the$(absoluteInstallLocation)/6.1.0.0-TIV-RTT-FP0001/installation_log.txt file.




The following procedure is for installing the fix pack on the Management Agent

1. To deploy the fix pack on the management agent, select SystemAdministration→ Agent Updates. Choose 6.1.0.0-TIV-RTT-FP00001 fromthe Available Updates pull-down menu. Select agent on which to upgrade inthe table. Select Install Update from the pull-down menu and click Go. Thisstarts the fix pack installation on the management agent.

2. After installing the fix pack on the management agent, to verify themanagement agents level, look at the Agent Update Status field andComponent Update Status on System Administration→ Agents Updates as shown in Figure 4-36. Both should say Up-to-date.

The solution is to change the default timeout of 180 from soap.client.props filein <WAS_HOME>/profiles/<profileName>/properties/ and modify:com.ibm.SOAP.requestTimeout = 600

And restart the WebSphere Application Server.

Note: If you meet upgrade failure with Agent Updates, you can remove themonitoring components and redeploy the monitoring components afterwards.





Figure 4-36 Complete agent updates

The following procedure is for installing the fix pack on the z/OS ManagementAgent. Get the z/OS package and put it on a temporary location in the UNIXSystem Services part of the z/OS machine.

1. Stop the management agent.

/etc/tmtp/MA/config/stop_tmtpd.sh

2. Extract the parts.tar file to the base management agent directory. Specify the“o” option of the tar command to preserve the owner ID on your system. Forexample:

cd /usr/lpp/tmtp/V6R0M0/MAtar xvfo parts.tar

3. The package contains the files used to deploy the J2EE component:

MA/lib/j2eeinst.jar.EJBsMA/lib/j2eeinst.jar.noEJBs


Verify that the j2eeinst.jar file in the MA/app/instrument directory correspondsto the desired behavior when deploying the J2EE component to thismanagement agent.

For performance reason, the MA/lib/j2eeinst.jar.noEJBs file should be usedas the file to be copied over the MA/app/instrument location.

If your monitoring rquirements need the enablement of EJB edges, you cancopy the j2eeinst.jar.EJBs file to the MA/app/instrument location.

4. Start the management agent.#/etc/tmtp/MA/config/start_tmtpd.sh

4.4.5 Integration with Tivoli Enterprise Monitoring Server

ITCAM for Response Time Tracking can be integrated into the IBM TivoliMonitoring V6.1 infrastructure, enabling you to exploit full IBM Tivoli MonitoringV6.1 functionality such as Tivoli Data Warehouse V2.1, correlate response timeinformation with data from other IBM Tivoli Monitoring V6.1 agents, and have thisinformation presented in Tivoli Enterprise Portal.

The integration into IBM Tivoli Monitoring V6.1 infrastructure uses Tivoli




Enterprise Monitoring Agent for ITCAM for Response Time Tracking. The TivoliEnterprise Monitoring Agent task is for retrieving information from ITCAM forResponse Time Tracking management server and forwarding response timeinformation to Tivoli Enterprise Monitoring Server.

Tivoli Enterprise Monitoring Agent is shipped as part of ITCAM for Response

Time Tracking. It connects to the ITCAM for Response Time Trackingmanagement server and collects information at customizable intervals. Thisenables you to install it on any box with a TCP/IP connection to the ITCAM forResponse Time Tracking management server. It is much easier to have themanagement server itself host the Tivoli Enterprise Monitoring Agent as theTivoli Enterprise Monitoring Agent host name is shown in Tivoli Enterprise Portalas the source of the monitor.

The installation process basically has two steps, which are:

“IBM Tivoli Monitoring V6.1 preparation” on page 152 “Tivoli Enterprise Monitoring Agent implementation” on page 154

Note: You must have an existing IBM Tivoli Monitoring V6.1 infrastructure setup. ITCAM for Response Time Tracking does not contain any IBM TivoliMonitoring V6.1 infrastructure components like Tivoli Enterprise MonitoringServer or Tivoli Enterprise Portal Server. For additional information about theIBM Tivoli Monitoring product, see the IBM Tivoli Monitoring documentation.


IBM Tivoli Monitoring V6.1 preparationIn order to integrate ITCAM for Response Time Tracking information into the IBMTivoli Monitoring V6.1 infrastructure, you must install application support files sothe infrastructure can support this type of agent:

Tivoli Enterprise Monitoring Server: Generates agent-specific information inTivoli Enterprise Monitoring Server, such as product situations and agenttables.

Tivoli Enterprise Portal Server: Adds workspaces and presentation files forthe agents to the Tivoli Enterprise Portal Server.

Tivoli Enterprise Portal: Updates Tivoli Enterprise Portal clients withproduct-specific information such as help files.

This section covers these steps from a process point of view and guides youthrough the installation process. For installation and customization, we follow theinstructions in ITCAM for Response Time Tracking Installation and Configuration Guide, GC32-1907.

Note: Before you begin installing the Tivoli Enterprise Monitoring Agent, youmust have installed at least IBM Tivoli Monitoring V6.1, Fix Pack 001 or higher.For your reference we use IBM Tivoli Monitoring V6 1 Fix Pack 003

http://-/?-

http://-/?-

http://-/?-

http://-/?-




1. Start the installation by clicking Setup in the Windows directory of the ITCAMfor WebSphere Tivoli Enterprise Monitoring Agent CD-ROM or by runninginstall.sh in your Linux or UNIX environment.

Figure 4-37 shows the welcome window for the installation of ITCAM forResponse Time Tracking. Click Next.

For your reference, we use IBM Tivoli Monitoring V6.1, Fix Pack 003.





Figure 4-37 Tivoli Enterprise Monitoring Agent welcome window

2. Click Accept to accept the license agreement.

3. Select the following features on the Select Features window to install.

Depending on where you are running this installation wizard, you may installdifferent components on different machines. In our environment, we have bothTivoli Enterprise Monitoring Server and Tivoli Enterprise Portal Server in asingle machine so we checked as shown in Figure 4-38:

– Tivoli Enterprise Monitoring Server– Tivoli Enterprise Portal Server– Tivoli Enterprise Portal Desktop Client

Note: You may have to install this on your Tivoli Enterprise Monitoring

Server machine, Tivoli Enterprise Portal Server machine, and individualTivoli Enterprise Portal desktop clients. You only have to install thecomponent that is available in each machine.





Figure 4-38 Tivoli Enterprise Monitoring Agent components

4. Select the agents to configure for remote deployment. If your requirementsenable to deploy for remote agent, you can check the component installationand click Next.

5. Follow the wizard to install and configure the components. Most componentsare already pre-configured, as we install to an existing IBM Tivoli Monitoringenvironment. The important option is to specify the communication to TivoliEnterprise Monitoring Server and Tivoli Enterprise Portal Server. We areusing IP:PIPE, which is a TCP connection.

Tivoli Enterprise Monitoring Agent implementationStart the setup from the ITCAM for Response Time Tracking Tivoli EnterpriseMonitoring Agent on the ITCAM for Response Time Tracking managementserver. The windows installation uses the same wizard as in , “IBM TivoliMonitoring V6.1 preparation” on page 152.

The differences will be noted the following on windows:

Install only the Tivoli Enterprise Monitoring Agent component.


When the installation is finished, configure the agent communication to TivoliEnterprise Monitoring Server. The communication is using IP:PIPE, and youmust specify the Tivoli Enterprise Monitoring Server host name.

Enter ITCAM for Response Time Tracking MS information.

We configured the ITCAM for Response Time Tracking management server onour RedHat Linux Enterprise Server. The installation process is started using theinstall.sh script as shown in Example 4-2.

Example 4-2 Running install.sh

[root@khartoum rtt]# ./install.shEnter the name of the IBM Tivoli Monitoring directory

[ default = /opt/IBM/ITM ]:/opt/IBM/ITM

ITM home directory "/opt/IBM/ITM" already exists.OK to use it [ y or n; "y" is default ]? y

Note: The ITCAM for Response Time Tracking Management Server port isdefined in the server.properties file, which was in

/opt/IBM/itcam/RTT/MS/config in our lab environment.

http://-/?-

http://-/?-

http://-/?-

http://-/?-




Select one of the following: 1) Install products to the local host.2) Install products to depot for remote deployment (requires TEMS).3) Exit install.

Please enter a valid number: 1

Software Licensing Agreement1. Czech2. English3. French

. . .

Please enter the number that corresponds to the languageyou prefer.

2

Software Licensing Agreement. . .. . .

Enter "1" to accept the agreement, "2" to decline it or


"99" to go back to the previous screen.

1Preparing to install the IBM Global Security Kit (GSkit)Preparing packages for installation...gsk7bas-7.0-3.18Will enable automatic agent initiation after reboot.

Enter a 32-character encryption key, or just press Enter to use the

defaultDefault = IBMTivoliMonitoringEncryptionKey

....+....1....+....2....+....3..[Enter]GSkit encryption key has been set.Key File directory: /opt/IBM/ITM/keyfilesProduct packages are available for the following operating systems andcomponent support categories:

1) Linux Intel R2.4 (32 bit)2) Linux Intel R2.4 (64 bit)3) Linux Intel R2.4 GCC 2.9.5 (32 bit)4) Linux Intel R2.4 GCC 2.9.5 (64 bit)




4) Linux Intel R2.4 GCC 2.9.5 (64 bit)5) Linux Intel R2.6 (32 bit)6) Linux Intel R2.6 (64 bit)7) Linux Intel R2.6 GCC 2.9.5 (32 bit)8) Linux Intel R2.6 GCC 2.9.5 (64 bit)9) Linux S390 R2.4 (32 bit)

10) Linux S390 R2.4 (64 bit)11) Linux S390 R2.6 (32 bit)12) Linux S390 R2.6 (64 bit)13) Linux S390 R2.6 GCC 2.9.5 (64 bit)14) Tivoli Enterprise Portal Browser Client support15) Tivoli Enterprise Portal Desktop Client support16) Tivoli Enterprise Portal Server support17) Tivoli Enterprise Monitoring Server support

Type the number for the OS or component support category you want, ortype "q"to quit selection[ number "1" or "Linux Intel R2.4 (32 bit)" is default ]:You selected number "1" or "Linux Intel R2.4 (32 bit)"

Is the operating system or component support correct [ y or n; "y" isdefault]? y


The following products are available for installation:

1) IBM Tivoli Composite Application Manager for Response Time TrackingV06.10.00.002) Tivoli Enterprise Services User Interface V06.10.01.003) all of the above

Type the numbers for the products you want to install, or type "q" to

quit selection.If you enter more than one number, separate the numbers by a comma ora space.

Type your selections here: 1The following products will be installed:

IBM Tivoli Composite Application Manager for Response Time TrackingV06.10.00 .00

Are your selections correct [ y or n; "y" is default ]? y... installing "IBM Tivoli Composite Application Manager for ResponseTime




Trac king V06.10.00.00 for Linux Intel R2.4 (32 bit)"; please wait.

=> installed "IBM Tivoli Composite Application Manager for ResponseTimeTracki ng V06.10.00.00 for Linux Intel R2.4 (32 bit)."... Initializing database for IBM Tivoli Composite Application ManagerforResp onse Time Tracking V06.10.00.00 for Linux Intel R2.4 (32 bit).... IBM Tivoli Composite Application Manager for Response Time

TrackingV06.10 .00.00 for Linux Intel R2.4 (32 bit) initialized.

Do you want to install additional products or product support packages[ y orn; "n" is default ]? n


... finished postprocessing.

Installation step complete.

As a reminder, you should install product support on each of your TEM


servers for any agents you have just installed. This is done via the"[ITM home]/bin/itmcmd support" command on your TEM servers.

You may now configure any locally installed IBM Tivoli Monitoringproduct viathe "/opt/IBM/ITM/bin/itmcmd config" command.

To connect Tivoli Enterprise Monitoring Server and Agent need configuration.

Configuration can be performed using itmcmd command. See Example 4-3Example 4-3 Running itmcmd config

root@khartoum bin]# ./itmcmd config -A t2Edit 'ITCAM for Response Time Tracking Management Server Identity'settings? (default is: Yes): YesResponse Time Tracking Management Server Host (default is: ): khartoumResponse Time Tracking Management Server Port (default is: ): 9445Response Time Tracking User Login ID (default is: ): root

Response Time Tracking Login Password (default is: ): ********Is Response Time Tracking Management Server SSL Enabled?

Type number of item from the below list1. Yes2 N




2. No(default is: ): 1

Response Time Tracking Keystore File (default is: ):[Enter]Response Time Tracking Keystore Password (default is: ):[Enter]Edit 'Response Time Tracking Agent Configuration Options' settings?

(default is: Yes): YesMaximum Timespan for Transaction Reporting in hours (default is: 8): 8Maximum Timespan for Instance Selection in hours (default is: 1): 1Maximum number of log messages (default is: 100): 100Agent Messsage expiration (default is: 7): 7Edit 'Response Time Tracking Managing Server Database ConfigurationOptions' set tings? (default is: Yes): YesSelect the Database type for Managing Server Database

Type number of item from the below list

1. DB22. ORACLE(default is: ): 1

Fully qualified hostname of the Managing Server Database Machine(default is: ): khartoum.itsc.austin.ibm.comSpecify Database Port: default for DB2 is 50000 and for Oracle is 1521(default is: 50000): 50000Database Name or SID Name (default is: ): TMTPRTT MS Schema User Login Name (default is: ): db2inst1


RTT MS Schema User Login Password (default is: ): ****Will this agent connect to a TEMS? [YES or NO] (Default is: YES): YESTEMS Host Name (Default is: khartoum): limaNetwork Protocol [ip, sna, ip.pipe or ip.spipe] (Default is: ip.pipe):

Now choose the next protocol from one of these:- ip- sna- ip.spipe

- noneNetwork Protocol 2 (Default is: none): noneIP.PIPE Port Number (Default is: 1918): 1918Enter name of KDC_PARTITION (Default is: null):[Enter]

Configure connection for a secondary TEMS? [YES or NO] (Default is:NO): NOEnter Optional Primary Network Name or "none" (Default is: none): noneAgent configuration completed...

Starting Tivoli Enterprise Monitoring Agent can be performed using itmcmd command. See Example 4-4




Example 4-4 Running itmcmd agent

[root@khartoum bin]# ./itmcmd agent start t2Starting agent...Agent Started...

4.5 Monitoring components deployment

This section describes the deployment of the monitoring components. After themanagement server and agents are set, you can deploy monitoring componentsto the installed management agents. This section provides the main steps of thedeployment process of monitoring components.

The deployment considerations include:

4.5.1, “Monitoring components in general” on page 160 4.5.2, “Installing Rational Robot and Generic Windows” on page 162 4.5.3, “Deploying Client Application Tracker” on page 166 4.5.4, “Deploying J2EE component” on page 167 4.5.5, “Deploying JBoss and Tomcat” on page 170 4.5.6, “Deploying Quality of Service” on page 172 4.5.7, “Deploying Synthetic Transaction Investigator” on page 173


4.5.8, “Deploying Web Response Monitor” on page 174 4.5.9, “Deploying Generic Playback” on page 177 4.5.10, “Deploying ARM Application” on page 178 4.4.4, “Installing ITCAM for Response Time Tracking fix pack 1” on page 148

4.5.1 Monitoring components in general

ITCAM for Response Time Tracking has twelve monitoring components as

shown in Table 4-3.Table 4-3 ITCAM for Response Time Tracking monitoring components

Component Usage

ARM Applicaition Used to monitor the performance of ARM 2.0 or 4.0-instrumented applicationsfrom ISVs (such as Siebel) or custom in-house applications. The ARMcomponent can also detect and monitor custom metrics that are recorded fromthese ARM instrumented applications.

Client ApplicationTracker Used to measure the round trip response time of transaction originating at theclient desktop. It can monitor Lotus Notes, Microsoft Outlook, SAP GUI, IBMPersonal Communication 3270, Exceed, or Extra with this monitoringcomponent.

Generic Playback Used to enable you to schedule regular playback of any command on a




Generic Playback Used to enable you to schedule regular playback of any command on amanagement agent. It can upload and run any set of custom scripts or caninvoke commands that already exist on the agent.

Generic Windows VU - Used to enable you to monitor your Web application by recording a scriptand playing it back as a robotic user.GUI - Used to monitor your Microsoft Windows or Java application by recordinga script and playing it back as a robotic user.This agent runs Rational Robot.

J2EE Used to monitor J2EE application servers, such as WebSphere ApplicationServer and BEA WebLogic. A single management agent can monitor multipleJ2EE Application Servers on the managment agent’s host.

JBoss Used to monitor JBoss application servers.

Mercury RoadRunner Used to enable you to playback and monitor your Web applications byrecording a Mercury LoadRunner script and playing it back as a robotic useron a management agent. HTTP(S) transactions generated by MercuryLoadRunner are automatically correlated with backend monitored systems

Quality of Service Used to collect performance data for HTTP transactions for one or more Webservers, which includes the entire round-trip time of the transaction, theback-end service time, and the page display time.


Some considerations regarding agent components:

The components can be used independently or in conjunction with anothercomponent. For example, using Generic Windows component to play back arecorded transaction that targets a URL monitored by the Web Response

Monitor component and is routed to a Web Application Server monitored by aJ2EE endpoint provides the performance data available for that specificinstance of the transaction.

You can spread out the playback agents to collect measurements from

Rational PerformanceTester

Used to schedule regular playback of recorded scripts on a managementagent, similar to robot function.

Synthetic TransactionInvestigator

Used to simulate end-user experience while doing Internet transactionsthrough a Web browser and trace a transaction that you can decompose usingQuality of Service and J2EE performance measurements.

Tomcat Used to monitor apache Tomcat server

Web Response Monitor Used to measure the performance of Web-based applications, providesresponse time and other performance data, tracks navigation paths and usagebehavior.

Component Usage




different sites of the enterprise to get an overall response time measurement.

Figure 4-39 shows our final monitoring component assignment.





Figure 4-39 Monitoring components assignments

4.5.2 Installing Rational Robot and Generic Windows

The Generic Windows (GenWin) component uses Rational Robot to gauge howusers experience Windows-based applications, Web-based applications, andcustom applications. The Rational Robot software must be installed on themanagement agents that you want to play back Generic Windows scripts. Youmust install Rational Robot before you can deploy the Generic Windowsmonitoring component.

Installing Rational Robot can be performed as follows:

1. The robot2003.zip can download from management server Downloads→ Generic Windows Recorder

2. Extract the file on the local machine and run the Robot2003_SR5.exe.

3. Accept the default setting by clicking Next until “License Key AdministratorWizard”. Select Import a Rational License File as shown in Figure 4-40 andclick Next.


Figure 4-40 Select option for importing a Rational license file

4. Click Browse and navigate to the directory where you extractedrobot2003.zip and select the ibm_robot.upd file as shown in Figure 4-41.




Figure 4-41 Import ibm_robot.upd file

5. Click Import again for confim import


Figure 4-42 Confirm import file

6. After install the Rational robot, you need restart the computer.

7. After installing the robot, you must configure DCOM security permissions forthe Administrator using DCOMCNFG utility. The default access and launch

permission of DCOM do not give the Rational Robot Player accountpermission to launch Microsoft Internet Explorer. Permission must be given tothe ITCAM for Response Time Tracking user and the user that runs RationalRobot recording. Refer to 4.4.3, “Distributed management agent installation”on page 144 and ITCAM for Response Time Tracking Installation and

C fi ti G id GC32 1907




Configuration Guide , GC32-1907.

For deploying Generic Windows components:

1. To deploy the Generic Windows component, access System

Administration→ Monitoring Components, select the Generic Windows component, and select agent on which to deploy Generic Windows in theagent table as shown in Figure 4-43.

Tip: Even after this procedure you may get the following messages:

Setup failed to launch installation engine: Access is denied

or

Error installing ikernel.exe, access is denied

If these messages occur, follow the procedure described on:

http://support.microsoft.com/default.aspx?scid=kb;en-us;295278


Figure 4-43 Choose agent for deploying Generic Windows

2. Enter the following fields to deploy the Generic Windows component.Figure 4-44 shows the deployment setting. The userID, password and project






Figure 4 44 shows the deployment setting. The userID, password and projectname fields will be used for running Robot scripts.

Figure 4-44 Deployment information for Generic Windows


3. After deploying the Generic Windows, the agent will reboot. Verify the GenericWindows deployment by looking at the Status field on System

Administration→ Agents as shown in Figure 4-45.

Figure 4-45 Complete the Generic Windows deployment

4.5.3 Deploying Client Application Tracker

The Client Application Tracker measures the round trip response time of

transactions originating at the client desktop. An agent sits invisibly at the clientdesktop and clocks transactions by setting a software stopwatch when thetransaction begins. The monitoring component provides the ability to monitor thefollowing versions of applications out-of-the box. Additional component (orbehavior modules) can be downloaded.




Lotus Notes, version 5 and 6 Microsoft Outlook 2000 and 2003 SAP, version 6.2 and 6.4 IBM PCOMM, Hummingbird Exceed, and Attachmate Extra 3270 emulators

The following procedure deploy the Client Application Tracker component:

1. To deploy the Client Application Tracker, select System Administration→ Monitoring Components. Select Client Application Tracker in theMonitoring Components Table, and choose Deploy Monitoring Component from the pull-down menu. Click Go (Figure 4-46).


Figure 4-46 Deploy Client Application Tracker component




2. Select agent on which to depoy Client Application Tracker in the agent tableand click Next.

3. After deploying the Client Application Tracker, the agent will reboot. Verify theClient Application Tracker deployment by looking at the Status filed onSystem Administration→ Agents

4.5.4 Deploying J2EE component

The J2EE monitoring component provides a high-level view of transactions bycollecting ARM data generated by J2EE applications. ITCAM for Response TimeTracking uses Java byte code instrumentation. You can monitor the following

application servers with this components: WebSphere Application Servers BEA WebLogic WebSphere Portal products Business Process Execution Language (BPEL) processes running on a

WebSphere Process Server

The following procedure deploy the J2EE monitoring component:


1. To deploy the J2EE monitoring component, select System Administration→ Monitoring Components. Select J2EE in the Monitoring Components Table,and choose Deploy Monitoring Component from the pull-down menu. ClickGo. Choose J2EE deployment method as shown in Figure 4-47 and clickNext.




Figure 4-47 Choose J2EE deployment method

2. Select agent on which to depoy J2EE in the agent table and click Next. Enterthe following fields to discovery J2EE in the agent and click Next. Figure 4-48 shows the J2EE discovery settings.


Figure 4-48 J2EE discovery criteria




3. After discovery the J2EE, select to deploy J2EE component in the table asshown in Figure 4-49 and click Finish. It starts to deploy J2EE component onthe J2EE Application Server.


Figure 4-49 Deploy J2EE monitoring component




4. After deploying the J2EE, the J2EE Applicaiton Server needs to restart. It canbe restarted in deploying the J2EE component for selecting restart option inFigure 4-49. Verify the J2EE deployment by looking at the Status filed on

System Administration→

Agents

4.5.5 Deploying JBoss and Tomcat

The JBoss and Tomcat monitoring components enables to monitor JBossapplication server and apache Tomcat server. It provides a high-level view oftransactions by collecting ARM data generated by J2EE applications. You canmonitor the following types of applications with these components:

JBoss Application Server Apache Tomcat

The following procedure deploy the monitoring component.

1. To deploy the JBoss and Tomcat monitoring components, select SystemAdministration→ Monitoring Components. Select JBoss or Tomcat inthe Monitoring Components Table, and choose Deploy MonitoringComponent from the pull-down menu. Click Go. Select agent on which todepoy JBoss or Tomcat component in the agent table and click Next.


2. It needs the following information for the deployment monitoring components. JBoss : JBoss Application Home, Java Home and JBoss JMX Port(Optional)

as shown in Figure 4-50.

Tomcat : Apache Tomcat Home and Java Home as shown in Figure 4-51.




Figure 4-50 Required informations to deploy JBoss

Figure 4-51 Required informations to deploy Tomcat

3. Select agent on which to depoy JBoss or Tomcat in the agent table and clickNext.


4. After deploying the JBoss or Tomcat, restart of application server needed.Verify the JBoss or Tomcat deployment by looking at the Status filed onSystem Administration→ Agents

4.5.6 Deploying Quality of Service

The Quality of Service monitoring component collects performance data forHTTP transactions for one or more Web servers, including the entire round-triptime of the transaction, the back-end service time, and the page render time. It isa reverse proxy. A forward proxy serves as a gateway for a client’s browser,

sending HTTP requests on the client’s behalf to the Internet and protects theinternal network by masking the client’s IP address and using its own. TheQuality of Service component includes origin server, proxy server and digitalcertificates.

1. To deploy the Quality of Service monitoring components, select SystemAdministration Monitoring Components S l t Q alit of Ser ice i

Note: JBoss and Tomcat J2EE component deployment change the followingfiles:

<JBoss Application Home>/bin/run.sh <Apache Tomcat Home>/bin/startup.sh

The original file is backed up with .orig extension.




Administration→ Monitoring Components. Select Quality of Service inthe Monitoring Components Table, and choose Deploy MonitoringComponent from the pull-down menu. Click Go. Select agent on which to

depoy Quality of Service component in the agent table and click Next.2. To deploy the Quality of Service monitoring component, the related

information enter the fields as shown in Figure 4-52.




Figure 4-53 Select agent to deploy STI

2. After deploying the STI, the agent will reboot. Verify the STI deployment bylooking at the Status filed on System Administration→ Agents

4.5.8 Deploying Web Response Monitor

The Web Response Monitor monitoring component measures the performance




The Web Response Monitor monitoring component measures the performanceof Web-based applications. It provides response time and other performancedata, and tracks navigation paths and usage behavior for Web pages andembedded objects in Web pages, such as graphics files.

1. Before deploying the Web Response Monitor component, install the NetworkMonitor driver.

a. Open Network Connections.

b. In Network Connections, click Local Area Connection.

c. Select File→ Properties.

d. In the Local Area Connection Properties dialog box, click Install.

e. In the Select Network Component Type dialog box, click Protocol, andthen click Add.

f. In the Select Network Protocol dialog box, click Network Monitor Driver,and then click OK.

g. After installing the Network monitor driver shown as in Figure 4-54.


Figure 4-54 Installation Network Monitor Driver

2. To deploy the Web Response Monitor monitoring components, select System

Administration→ Monitoring Components. Select Web ResponseMonitor in the Monitoring Components Table, and choose Deploy

Monitoring Component from the pull-down menu. Click Go. Select agent onwhich to depoy Web Response Monitor component in the agent table as

shown in Figure 4-55 and click Next..

Note: The Web Response Monitor component runs on a management agenton the Web server machine. You can to deploy on the following Web servermachine.

IBM HTTP S




IBM HTTP Server Microsoft Internet Information Server (IIS) Sun Java Web Server™

We deploy the Web Response Monitor component runs on the Quality ofService component as shown in Figure 7-39. It is a reverse proxy runs withinIBM HTTP Server, Version 1.3.26.1.


Figure 4-55 Installing the Web Response Monitor on the Quality of Service




3. To deploy the Web Response Monitor monitoring component, the followinginformation enter the fields as shown in Figure 4-56 and click Finish.


Figure 4-56 Required informations to deploy Web Response Monitor

4. After deploying the Web Response Monitor, to verify the Web Response




Monitor deployment by looking at the Status filed on SystemAdministration→ Agents

4.5.9 Deploying Generic Playback

The Generic Playback runs on a regular schedule any command on amanagement agent and collect timing information for the command executing.

1. To deploy the Generic Playback monitoring components, select SystemAdministration→ Monitoring Components. Select Generic Playback inthe Monitoring Components Table. Choose Deploy Monitoring Component from the pull-down menu as shown in Figure 4-57 and click Go . Select agent

on which to depoy Generic Playback component in the agent table and clickNext. To deploy component click Finish.


Figure 4-57 Deploying Generic Playback




2. After deploying the Generic Playback to verify the Generic Playback

deployment by looking at the Status field on System Administrations→ Agents.

4.5.10 Deploying ARM Application

The ARM Application component monitors the performance of ARMinstrumented applications. The applications can be from ISVs or customin-house applications. Some commercial applications already contain ARMinstrumentation. For example, WebSphere Application Server, Apache Web

server, IBM HTTP server, DB2 Universal Database™, Siebel, Baan ERP andSAS.

1. To deploy the ARM Application monitoring components, select System

Administration→Monitoring Components. Select Arm Application in theMonitoring Components Table. Choose Deploy Monitoring Component from the pull-down menu and click Go . Select agent on which to depoy ArmApplication component in the agent table and click Next.. Enter to enableARM application informations as shown in Figure 4-58 and click Finish.





Figure 4-58 Deploying ARM Application

2. After deploying the ARM Application to verify the ARM Applicationdeployment by looking at the Status field on System Administrations→ Agents.

4.6 Initial configuration and usage

When all the setup has been performed, most of initial configuration tasks areperformed. The tasks are:

Defining schedules as describes in 4.6.1, “Schedules” on page 180 Defining reporting group as explained in 4.6.2, “Reporting groups” on

page 183 Defining agent group as shown in 4.6.3, “Agent groups” on page 184 Defining user role assignment as discussed in 4.6.4, “User role assignment”

on page 187


4.6.1 SchedulesThe schedules use to define when discovery, listening, and robotic monitors run.ITCAM for Response Time Tracking uses two types of schedules:

Discovery and listening monitor schedules have start times and stop times, soyou can specify when the monitor runs. A discovery and listening schedulecan run continuously.

Robotic monitor schedules for robotic transactions also have start and stoptimes. You specify how many times the monitor runs between the start andstop times.

The ITCAM for Response Time Tracking V6.1 has default schedules for:

Default Listening Schedule: It runs now and forever

Default Playback Schedule : It runs every 15 minutes forever




Figure 4-59 Default schedules

Schedules should be designed to generate the most meaningful data andminimize disruption to the running environment. Schedules also may beinfluenced by the Service Level Agreement monitoring requirement.


We are running in a test environment, we have no real scheduling concern suchas peak time, prime time, and other transaction volume fluctuation. We define thefollowing schedules:

Discovery and listening schedules:

Workdays Runs 24 hours Monday through Friday.Workhours Runs 9 a.m.to 6 p.m.Monday through Friday.Weekend Runs 24 hours Saturday through Sunday.Discovery Runs every day 8 a.m to 9 p.m.

Playback schedules, we wanted to capture transaction and response timetrends so we would leave the schedule running all the time except forscheduled maintenance. In our environment, we define continuous scheduleswith intervals, depending on the need of the application:

– Every_30_min

– Every_1_hour

Schedules are created by accessing Configuration→ Schedules. Figure 4-60

shows the dialog for defining discovery and listening monitor schedules.




Figure 4-60 Configure discovery and listening schedule

A robotic monitor schedule is defined using the dialog shown in Figure 4-61.





Figure 4-61 Configure robotic monitor schedule

4.6.2 Reporting groups

The reporting groups are used to group reports for monitors by function or

business use, such as by site or applicaiton. It allows you to groups monitors byone of three types: Application, Customer, or Location. For example, if you havea Service Level Agreement for a customer called BookSeller, you might create areporting group called MonitorBookSeller that is of type Customer. Then you canknow whether you are meeting the requirements for BookSeller. Every monitormust belongs to at least one reporting group and cat belong to multiple reportinggroups. In our environment, we have the Trader application, which is explained in


Appendix A, “Trader application description” on page 437. For our monitoring ofthe application, we define these reporting groups by application:

TraderWeb We define that all report must belong to this group for anoverall view of the enterprise. This policy group alsomakes a global operator easier to define.

Trader_DB2_appl Report the J2EE transaction calls monitor.

Trader_CICS_appl Monitors the Web application for Trader.

To define the reporting group, select Configuration→ Reporting Groups. Todefine a new reporting group by clicking Create New. A reporting group has thename, description field and select type in drop-down list. Figure 4-62 shows ourcompleted reporting groups list.




Figure 4-62 Reporting groups list

4.6.3 Agent groups

The agent group is a group of management agents that run the same monitor ormonitoring components. An agent group can be used for authorization purposes.Each management agent is associated with one or more listening and playback


components. If a transaction spans multiple management agents and you want toperform thresholding on subtransactions, you must include all the managementagents in the same group. For example, if you create an STI monitor and knowthat the played-back transaction runs through a Web server monitored by Qualityof Service, include the agent that is running Quality of Service. Otherwise, youcannot establish thresholds for the part of the played-back transaction that runsthrough the Web server. You can obtain performance data, but thresholding is notenabled.

The ITCAM for Response Time Tracking provides the default agent groups whenyou deploy a new monitoring components type automatically as shown inFigure 4-63.




Figure 4-64 Configure agent group

4.6.4 User role assignment

This section provides information about how to assign users to preassigned rolesor create granular, restricted profiles for different users so they can only see andwork on the resources that matter to them. If you provide service to competinggroups, this ensures they cannot see each other’s data. User's can have multipleroles. Each role has the following characteristics:

Associated operations, each of which can have view or modify permission.

A set of reporting groups restricting the scope of the operations orunrestricted reporting groups.


A set of agent groups restricting the scope of the operations or unrestrictedagent groups.

The default role of admin can perform all the procedures. There must always beat least one user in the system that is assigned the admin role.

ITCAM for Response Time Tracking operators are assigned roles from the Webinterface. These roles are not WebSphere roles, although users are stillauthenticated using WebSphere security and authentication mechanisms thatcan be based on OS users or LDAP users. The users are defined from the menu

System Administration→ User-Role Assignments. New users can becreated by clicking Add User. Figure 4-65 shows the new user assignmentdialog.




Figure 4-65 New user assignments

The default existing roles are as shown in Table 4-4.


Table 4-4 Defatul roles

Additional roles may be created to segregate users based on policy groups.Roles are defined using System Administration→ Role Definitions as shownin Figure 4-66.

Role Default permissions for this role

admin Allows the user to perform all possible actions on every resource. If youwant to define custom roles, you must be assigned to this role.

agent Can install or view management agents. This role cannot createmonitors, schedules, etc.

operator Can view all reports and events.

tap Has view capability for the DATA_QUERY permission; unrestrictedresources. This role is provided to facilitate the authorization set up forthe IBM Tivoli Enterprise Management Agent user. The tap role canonly retrieve data for the reporting groups and agent groups for whichthe user has been granted access.

user Has view capability for all tasks with no restrictions.




Figure 4-66 Role definitions




User access: Defines which users can be assigned to this role.

Role access: Defines which roles can manage this role.

Figure 4-68 shows our role definitions list included the new role.




Figure 4-68 Role definitions list



Draft Document for Review March 1, 2007 5:22 pm 7151ch-RTT-usage.fm

Chapter 5. ITCAM for Response Time

Tracking usage

This chapter describes the basic usage for ITCAM for Response Time Trackingmonitoring components and contains it as applied to our sample environment. Itincludes the following topics:

5 1 “U i i ” 194

5




5.1, “Usage scenarios overview” on page 194

5.2, “J2EE monitoring” on page 195

5.3, “Quality of Service” on page 202

5.4, “Synthetic Transaction Investigator” on page 206

5.5, “Web Response Monitor” on page 218

5.6, “Rational Robot and Generic Windows” on page 223

5.7, “JBoss and Tomcat monitoring” on page 228

5.8, “Application Response Measurement” on page 230 5.9, “Client Application Tracker” on page 237

5.10, “Generic Playback” on page 243

5.11, “Working with Tivoli Enterprise Portal” on page 247

7151ch-RTT-usage.fm Draft Document for Review March 1, 2007 5:22 pm

5.1 Usage scenarios overviewWe configured a distributed monitoring components that we want to manage itsresponse time with ITCAM for Response Time Tracking. It can be monitoredusing several components, such as:

To collect existing response time from the J2EE application server by J2EEmonitoring component. It is collected by the J2EE instrumentation onWebSphere Application Server. For CICS, this instrumentation information byITCAM for CICS transaction. See 5.2, “J2EE monitoring” on page 195.

To collect web-based transaction response time using the Quality of Servicemonitoring component that resides between the Web application and a Webbrowser. See 5.3, “Quality of Service” on page 202.

To perfrom the sample application from an end-user site on scheduledintervals. These sample Trader application can be run using SyntheticTransaction Investigator (STI). See 5.4, “Synthetic Transaction Investigator”on page 206.

The monitoring flow is described in Figure 5-1.

Note: As a general usage tip, the ITCAM for Response Time Tracking usesthe string .* wildcard, not just the * character.




Figure 5-1 Application monitoring flow

Note: A discovery will not discover transactions when a listening monitor isalready in effect. Disable the discovery when the transactions have beendiscovered. A discovery or listening monitor will be effective if the transactionhas been tagged with ARM correlator from its upstream.


To monitoring the response time, we create the TraderWeb_CICS reportinggroups. This reporting group is inlcuded in these monitors:

J2EE listening monitor: for J2EE servlets and web services transactionmonitoring on WebSphere Application Server

Quality of Service listening monitor: for the Web transaction going through theproxy

STI robotic monitor: for the sample transaction monitored from STI monitoringcomponent

For additional monitoring components usage, we also perfom monitoring for thefollowing:

Web application response time with Web Response Time, see 5.5, “WebResponse Monitor” on page 218.

Using the Rational Robot transaction response time with Generic Windows,see 5.6, “Rational Robot and Generic Windows” on page 223.

JBoss and Tomcat on J2EE application transaction response time with JBoss

and Tomcat, see 5.7, “JBoss and Tomcat monitoring” on page 228. ARM instrumented application transaction response time with Application

Response Measurement, see 5.8, “Application Response Measurement” onpage 230.

Lotus Notes client response time with Client Application Tracker using ETE™Watch, see 5.9, “Client Application Tracker” on page 237.

Command execution response time with Generic Playback, see 5.10,“Generic Playback” on page 243



Chapter 5. ITCAM for Response Time Tracking usage 195

Generic Playback on page 243.

The usage of Tivoli Enterprise Portal with ITCAM for Response Time Trackingis described in 5.11, “Working with Tivoli Enterprise Portal” on page 247.

5.2 J2EE monitoring

For getting the J2EE transaction response time component path, we configureJ2EE monitoring component. It provides to get into the detailed on the J2EE

based instrumentation. The J2EE monitor can be shown as a Web Services callsor Servlets access. The Web based Trader application uses Servlets inTraderClientWeb application, while the Java based Trader application performdirect Web Services calls.

5.2.1 J2EE discovery

We create the J2EE discovery for both Servlets and Web Services calls.


1. To configure the J2EE servlets discovery, select Configuration→

Discovery. Choose J2EE Servlet from the pull-down menu and click CreateNew. The Servlet discovery settings are shown in Figure 5-2.

Figure 5-2 J2EE servlet discovery settings




2. We also create discovery for Web Services that are called from Java basedapplication. The Web Services discovery settings are shown in Figure 5-3.





Figure 5-3 J2EE web services discovery settings

3. Once some transaction has been captured, you can get the discoveredtransaction. The sample discoverd the J2EE transactions are shown inFigure 5-4.




Figure 5-6 J2EE transaction node overview

From the transaction nodes, we can expand and analyze its behavior for eachnode. For the J2EE servlet in srv178, the transaction is broken down as shown inFigure 5-7.




Figure 5-9 J2C break down

The transaction that is invoked on the z/OS side shows as Figure 5-10. For morethe detailed CICS configuration, <refer to the part V for z/OS>.




Figure 5-10 CICS transaction

5.3 Quality of Service

To identify the Web transaction performance on Web Server, you can configure aQoS for access gateway. It will collect end-user response time including theentire round-trip time of the transaction, the back-end service time, and the page


render time. The QoS monitoring component configuration can be performed two

steps are similar to the J2EE monitoring component.

5.3.1 QoS discovery

To monitor with the QoS, we create the discovery to find the transaction runningon the QoS.

1. To configure the QoS discovery, select Configuration→ Discovery. ChooseQuality of Service from the pull-down menu and click Create New. The QoS

discovery settings are shown in Figure 5-11.




Figure 5-11 QoS discovery settings

If you don’t know exactly which part of the transaction you would like tomonitor just input .* on the URI title field and 100% sample rate to discover alltransactions running through the QoS server. Mind that this can degrade yourserver performance depending on how much transactions you have runningon the server.

2. The QoS discovered transactions are shown in Figure 5-12.


Figure 5-12 Discovered QoS transactions

5.3.2 QoS listening monitor




From the discovered QoS transactions in Figure 5-12, we can define the QoSlistening monitor. We create the QoS listening monitor for TraderCICSWeb.

To create the QoS listening monitor, select the discovered web transaction, andchoose Create Listening Monitor From from the pull-down menu. Click Go, andconfigure QoS settings for the QoS listening monitor as shown in Figure 5-13.





Figure 5-13 QoS listening monitor settings

You can listen to multiple transactions from different sources once the all requestfrom IP address and All pages with URI fields accept regular expressions as

parameters.

5.3.3 QoS report

Once the QoS listening monitor is running you can see its topology fromReports→ Dashboard. Figure 5-14 shows the QoS composite transactiontopology.


Figure 5-14 Transaction Topology by the QoS listening monitor

5.4 Synthetic Transaction Investigator

The Synthetic Transaction Investigator (STI) provides you to gather availabilityand performance of a scenario based Web-browser transaction in end userperspective. To monitor using STI, there are two sides:

The STI recorder: It is a standalone transaction recording tools that run on aWindows-based system using Microsoft Internet Explorer.

The Robotic monitor: It runs the recorded transaction.

5.4.1 Recording Transaction

This section describes the procedure on records STI transactions for our Traderapplication. The STI recorder can download from the management serverconsole.




1. Download the STI recorder from Downloads→ STI Recorder and install.During the install, you have to enter the hostname of the ITCAM for ResponseTime Tracking management server and the relevant port as shown in

Figure 5-15.

Note: The STI recorder cannot install on running the ITCAM for ResponseTime Tracking management agent. You must be install on a Windows machinewithout any management agent.




4. The transaction recording is complete, click Save and logon the management

server for uploading the STI robotic script. The uploaded STI robotic scriptcan modify at need using Configuration→ Robotic Scripts. Select theRobotic Script in the Robotic Scripts Table. Choose Edit from the pull-downmenu and click Go. Figure 5-17 shows Robotic Script edit display. Mind thatthe Robotic Script can not edit which is used by currently running monitor.




Figure 5-17 Edit robotic script display

5.4.2 Generating robotic monitor

After the STI robotic script created and uploaded, create STI robotic monitor.

1. To monitor with the STI, select Configuration→

Robotic Monitors. ChooseSynthetic Transaction Investigator from the pull-down menu, then clickCreate New. Figure 5-18 shows the STI settings.




Figure 5-19 STI thresholds settings

The thresholds in QoS, J2EE and ARM settings are not available at this time.It can be defined only the transaction topology view contains those elements

as shown in Figure 5-20.





Figure 5-20 Example QoS threshold in transaction topology

3. Defining schedule, agent group and reporting groups for the STI roboticmonitor. All of settings can make a new using Create New button. In our




monitor. All of settings can make a new using C ea e e button. In ourexample, we define the STI robotic monitor named TraderWeb_CICS.

5.4.3 STI report

This section describes the STI reports and shows identify problem node in theSTI transaction topology.

Note: If you are using Generic Windows GUI to play back browser interactionswith Microsoft Internet Explorer, do not run STI play backs on the samemachine with the same or overlapping schedules. This might cause a conflictwith desktop interactions.

Also, Client Application Tracker agent do not run on the same machine as STI.We recommend to run STI as standalone.




Figure 5-24 Break down STI transaction




In the production environment, where your performace thresholds are directlydriven from business requirements. If the J2EE component occurrs alert, you cansee what component causes the problem. If you have a ITCAM for WebSphere orITCAM for J2EE monitoring environment, you can dril l down into ITCAM forWebSphere for more detail analyzing in application level as shown inFigure 5-25.


Figure 5-25 Drill down with ITCAM for WebSphere /J2EE in monitoring component

We also enabled Page Analyzer Viewer in STI robotic monitor settings, and wecan see report using Reports→ General Reports→ Page Analyzer Viewer asshown in Figure 5-26.




Figure 5-28 The Web Response Monitor discovery settings

3. After the discovery monitor configuration, we generated the Traderapplication. Once some transaction captured, you can get the discovered

transactions as shown in Figure 5-29.





Figure 5-29 Discovered web transactions by the Web Response Monitor

5.5.2 Web Response Monitor listening monitor

From the discovered web transactions in Figure 5-29, we can define listeningmonitor.




1. To create the Web Response Monitor listening monitor, select URL thediscovered web transaction and choose Create Listening Monitor From from the pull-down menu. Click Go, and configure WRM settings for thelistening monitor as shown in Figure 5-30.




Figure 5-32 Starting record GUI

3. We record the Trader application transaction using Microsoft InternetExplorer, and click stop button. You can the script will be available to edit asshown in Figure 5-33.

Attention: We have used the GUI Robot only for Microsoft InternetExplorer, if you have the required the other application using the RationalRobot refer to ITCAM for Response Time Tracking Administrator’s Guide,SC32 1905




SC32-1905.


Figure 5-33 Created transaction script by the Rational Robot

4. To use the Rational Robot script on the management server, you need toupload the recorded transaction. For uploading, choose Configuration→ Robotic Scripts on the management server console. Select Generic

Windows - GUI from the pull-down menu and click Create New. You can useto upload both Java Web Start Upload and Manual Script Upload. We use the

manual script upload as shown in Figure 5-34.





Figure 5-34 Uploading the recorded transaction by Rational Robot

5.6.2 Generic Windows robotic monitor and reportAfter the Rational Robot script created and uploaded, it can be used by therobotic monitor for the transaction monitoring.




robotic monitor for the transaction monitoring.

1. To monitor with the Generic Windows, select Configuration→ Robotic

Monitors. Choose Generic Windows - GUI from the pull-down menu, thenclick Create New. Figure 5-35 shows the Generic Windows - GUI settings.


Figure 5-35 Generic Windows - GUI robotic monitor settings

2. We created the Generic Windows Robotic Monitors using the default playbackschedule. After the robotic monitor running, you can see the report using

Reports→ Dashboard as shown in Figure 5-36.




Figure 5-37 J2EE transaction topology of JBoss

Figure 5-38 shows the transaction topology report from running Tomcat sample

J2EE application.




Figure 5-38 J2EE transaction topology of Tomcat


5.8 Application Response Measurement

The Application Response Measurement (ARM) monitors the performance ofARM 2.0 or 4.0-instrumented application. This section describes the ARMinstrumentation using the sample Java application.

5.8.1 Instrumenting the sample application

We used the sample Java application to monitor using ARM. The sampleapplication is simple, click “Simple” or “Complex” button and then returns theelapsed time as shown in Figure 5-39.

Figure 5-39 Sample Java application for ARM monitor

1. For our instrumentation, we only need to importorg.opengroup.arm40.transaction package as shown in Example 5-1.

Example 5-1 Import ARM instrumentation

import org.opengroup.arm40.transaction.*;

2. Declaring ARM instrumentation variables as shown in Example 5-2.

Example 5-2 ARM instrumentation variables

bli l ARMA M i d JA l i l A i Li {




public class ARMAppsMain extends JApplet implements ActionListener {private static final long serialVersionUID = 1;private Random r;private static boolean armOn;public static ArmTransactionFactory armTranFactory = null;static {

try {String tranFactoryName =

"com.ibm.tivoli.transperf.arm4.transaction.Arm40TransactionFactory";Class tranFactoryClass =

Class.forName(tranFactoryName,true,ClassLoader.getSystemClassLoader());armTranFactory =

(ArmTransactionFactory)tranFactoryClass.newInstance();


armOn = true;System.out.println("ARM interface activated");

} catch ( Exception ex ) {ex.printStackTrace();armOn = false;

}}private ArmApplicationDefinition armAppDef;private ArmTransactionDefinition armTranDefs;private ArmTransactionDefinition armTranDefc;

private ArmTransactionDefinition armTranDefc1;private ArmTransactionDefinition armTranDefc2;private ArmApplication armClient;private ArmTransaction armTran;private ArmCorrelator corr;private JTextArea ta;

3. Initializing the ARM environment when the Servlet is initialized as shown inExample 5-3.

Example 5-3 Initializing ARM environment

public ARMAppsMain() {r = new Random();if (armOn) {

armAppDef =armTranFactory.newArmApplicationDefinition("TI6M11",null,null);

System.out.println("ARM appl TI6M11 defined");armTranDefs =

armTranFactory.newArmTransactionDefinition(armAppDef,"SimpleTran",null,null);

armTranDefc =armTranFactory.newArmTransactionDefinition(armAppDef,"ComplexTran",null




armTranFactory.newArmTransactionDefinition(armAppDef, ComplexTran ,null,null);

armTranDefc1 =armTranFactory.newArmTransactionDefinition(armAppDef,"ComplexSub1",null,null);

armTranDefc2 =

armTranFactory.newArmTransactionDefinition(armAppDef,"ComplexSub2",null,null);

System.out.println("ARM transactions defined");}

4. Instrumenting the start of transaction as shown in Example 5-4. ThearmStatus variable will be used to contain the transaction status, we initialize


it with a STATUS_GOOD indicator. The ta.append can only be retrieved afterthe transaction is started using the start() method.

Example 5-4 Starting ARM transaction

int armStatus = ArmConstants.STATUS_GOOD;if (armOn) {

armClient =armTranFactory.newArmApplication(armAppDef,"ITSO","Austin",null);

armTran =armTranFactory.newArmTransaction(armClient,armTranDefs);

armTran.start();ta.append("-+-");}

5. Stopping the ARM transaction as shown in Example 5-5.

Example 5-5 Stopping ARM transaction

if (armOn) {armTran.stop(armStatus);

armClient.end();ta.append("==");

}

The complex part of the sample Java application is call the sub transaction asshown in Example 5-6.

Example 5-6 Complex part of the sample application

long i = r.nextInt(300)+100;ta.append("Main-"+i+"-");try {

Thread.sleep(i);} catch (I te tedE ce tio e) {




} catch (InterruptedException e) {}sub1();sub2();if (armOn) {

armTran.stop(armStatus);armClient.end();ta.append(">>==");

}ta.append("\n");

}}


public void sub1() {int armStatus = ArmConstants.STATUS_GOOD;if (armOn) {

armClient =armTranFactory.newArmApplication(armAppDef,"ITSO","Austin",null);

armTran =armTranFactory.newArmTransaction(armClient,armTranDefc1);

armTran.start(corr);ta.append("-+-<<");

}

long i = r.nextInt(1000)+300;ta.append("Sub1-"+i+"-");try {

Thread.sleep(i);} catch (InterruptedException e) {}if (armOn) {

armTran.stop(armStatus);

armClient.end();ta.append(">>==");}

}

public void sub2() {int armStatus = ArmConstants.STATUS_GOOD;if (armOn) {

armClient =

armTranFactory.newArmApplication(armAppDef,"ITSO","Austin",null);armTran =armTranFactory.newArmTransaction(armClient,armTranDefc2);

armTran.start(corr);t d(" ")




ta.append("-+-<<");}

long i = r.nextInt(1000)+300;ta.append("Sub2-"+i+"-");

try {Thread.sleep(i);} catch (InterruptedException e) {}if (armOn) {

armTran.stop(armStatus);armClient.end();ta.append(">>==");


}}

5.8.2 ARM discovery

To define each transaction monitor, you can do one of these actions:

Incorporate the ARM-instrumented applications into the monitoringenvironment by uploading an XML file for the application.

Use ARM discovery to identify ARM applications if you do not know whichapplications you want to monitor.

The easiest way to create a listening policy is to define a discovery to find thetransaction.

1. To configure the ARM discovery, select Configuration→ Discovery. ChooseARM Application from the pull-down menu and click Create New. Enter theARM settings to discovery the transaction in the sample application as shownin Figure 5-40 and click Next.




Figure 5-40 ARM discovery settings


2. After the ARM discovery monitor configuration, we run the sampleapplication. Once some transaction captured, you can get the discoveredARM application as shown in Figure 5-41.

Figure 5-41 Discovered the ARM instrumentation application by the ARM discovery

5.8.3 ARM listening monitor

From the discovered ARM transactions in Figure 5-41, we can define listening




g gmonitor.

To create the ARM listening monitor, select application the discovered ARMinstrumentation application and choose Create Listening Monitor From fromthe pull-down menu. Click Go and configure ARM 4.0 settings for the listening

monitor as shown in Figure 5-42.





Figure 5-42 ARM listening monitor settings

5.8.4 ARM report

Once the listening monitor is running, you can see the response time andtopology information using Reports→ Dashboard. Figure 5-43 shows thetransaction topology for the sample application.


Figure 5-43 Sample application transaction topology

5.9 Client Application Tracker

The Client Application Tracker monitor the round trip response time of transactionoriginating at the client desktop. Client Application Tracker is an evolution fromCandle ETE Watch product.




The Client Application Tracker provides the capability to monitor Lotus Notes,Microsoft Outlook, SAP, IBM PCOMM and so on. For more informations, refer toITCAM for Response Time Tracking Administrator’s Guide, SC32-1905

We monitor the IBM PCOMM which is a new object monitoring application in thisrelease. For monitoring the IBM PCOMM, you need the following process inadvance:

Note: You should not use Client Application Tracker agent on the samemachine as STI.


Check the behavior modules file is named pcom_5x.dat inMA_install_directory/app/CAT/Mgmt/Collector/TC directory as shown inFigure 5-44.

Figure 5-44 Behavior modules directory

Edit rule file tn3270.rul which identifies strings of characters that appear inyour application and identifies applications and transactions. The tn3270.rul file is in MA_install_directory/app/CAT/Mgmt/Collector directory. We add

the line for the default rule for unidentified transactions as shown inExample 5-7. For details on creating this custom rule file, see the chapterabout 3270 applications in the CandleNet ETEWatch® User's Guide, GC32-9178.




Example 5-7 Modify tn3270.rul file

<...>## Default rule for unidentified transactions#tranid: return("Unknown");

To compile the modified tn3270.rul rule file, execute tdl tn3270.rul command from MA_install_directory/app/CAT/Mgmt/Collector.


Restart the management agent using Start→ Settings→ Control Panel→ Administrative Tools→ Services. Execute restart for IBM Tivoli Monitoringfor Transaction Performance service as shown in Figure 5-45.

Figure 5-45 Restart the management agent using services

5.9.1 Client Application Tracker discovery

To monitor the IBM PCOMM application, create the discovery using ARMApplication for the behavior modules.

1. To configure the ARM discovery, refer to 5.8.2, “ARM discovery” on page 234.

2. We executed the IBM PCOMM emulator to create transaction as shown inFigure 5-46.





Figure 5-46 Execute IBM PCOMM emulator

Note: You can check that Client Application Tracker runs using the log files. If

the product runs, the file size grows when you execute the application. The logfiles are:

MA_install_directory/app/CAT/Mgmt/Log/KeeAgent.logMA_install_directory/app/CAT/Mgmt/Log/KeeHook.log




3. After the IBM PCOMM emulator execute, you can get the discoveredapplication as shown in Figure 5-47.


Figure 5-47 Discovered the IBM PCOMM application by the ARM discovery

5.9.2 Client Application Tracker listening monitor

From the discovered CAT PCOM application in Figure 5-47, we can define listeningmonitor

To create the Client Application Tracker listening monitor, select application thedi d CAT PCOM li ti d h C t Li t i M it F




discovered CAT PCOM application and choose Create Listening Monitor From from the pull-down menu. Click Go and configure ARM 4.0 settings for thelistening monitor as shown in Figure 5-48.





Figure 5-48 Client Application Tracker listening monitor settings for CAT PCOM

5.9.3 Client Application Tracker report

Once the listening monitor is running, you can see the separate response timesand transaction topology using Reports→ Dashboard. Figure 5-49 shows thetransaction topology of the IBM PCOMM application.


Figure 5-49 Transaction topology by the Client Application Tracker monitoring component

5.10 Generic Playback

The Generic Playback is a new monitoring component in this release. It runs anycommand on a management agent and collects timing information for thecommnad execution. The Generic Playback is used to automate running script

based on robotic schedule. For example, it can be used to test server availabilitywith FTP, telent or ping, to query a database with a custom SQL command and torun a custom shell script.

5 10 1 U i th d




5.10.1 Using the command

The following are the steps to use a command based generic playback monitor:

1. To use the Geneirc Playback, you create a Generic Playback robotic monitor.

We create the robotic monitor for server availability with ping command.Select Configuration→ Robotic Monitors and choose Generic Playback from the pull-down menu. Click Create New. Figure 5-50 shows the GenericPlayback robotic monitor setting dialog.


Figure 5-50 Generic Playback robotic monitor settings

2. Continue to set the Generic Playback and Name enter, click Finish.

Note: If you put the command on a management agent instead of uploadingfiles, it needs to know the full path to the command when creating the playbackmonitor as shown in Figure 5-50




3. After the robotic monitor is running for a while, you can see report fromReports→ Dashboard. Figure 5-51 is our output from the Generic Playbackrobotic monitor, it shows ping command execution performance result with ina certain period of time.


Figure 5-51 The Generic Playback report

5.10.2 Using uploaded file

The following are the steps to use an uploaded file for generic playback monitor:

1 T l di fil th R b ti S i t S l t




1. To use uploading file, you can use the Robotic Scripts. SelectConfiguration→ Robotic Scripts, Choose Generic Playback from thepull-down menu, then click Create New. Figure 5-52 shows the GenericPlayback robotic monitor settings dialog. Click Browse...→Open the file and

click Add. It will upload the file to the management server.


Figure 5-52 Creating robotic script

2. To monitor with the uploading file, select Configuration→ Robotic

Monitors. Choose Generic Playback from the pull-down menu, then clickCreate New. Figure 5-53 shows the Generic Playback robotic monitorsettings dialog.





Figure 5-53 Generic Playback robotic monitor settings with robotic script

The Generic Playback can work by wrapping a recording in ARM start and stopcalls so that the software can measure the total time the command or recordingtook. For information on how to do this, see ITCAM for Response Time Tracking

Administrator’s Guide, SC32-1905.

5.11 Working with Tivoli Enterprise Portal




This section describes Tivoli Enterprise Portal information from ITCAM forResponse Time Tracking. The Tivoli Enterprise Management Agent is installedon ITCAM for Response Time Tracking management server which is khartoum.

The Tivoli Enterprise Portal Client runs either as a desktop or Web-basedapplication. To use Tivoli Enterprise Portal Client as a desktop, it needsinstallation on your desktop. To access Tivoli Enterprise Portal Client as abrowser mode, type the URL in the browser and enter to access user id andpassword. The default user id is sysadmin . The URL is:

http://lima:1920//cnp/client


We customized the logical view for the ITCAM for Reponse Time Tracking.Figure 5-54 shows the agent status and message.

Figure 5-54 Response Time Tracking portal workspace.

Select the Response Time Tracking Agent Policy Groups, it will bring the primaryinterface for ITCAM for Response Time Tracking as shown in Figure 5-55. The




p g gpolicy groups summary shows the reporting groups in ITCAM for Response TimeTracking defined. To view the detailed reporting groups information, click the icon

by the TraderWeb reporting group.


Figure 5-55 Response Time Tracking Agent Policy Groups

It links to the reporting group TraderWeb under monitors summary as shown inFigure 5-56. You can see the monitors status of the reporting group TraderWeb.To check each of monitor status, click the icon by the policy name.





Figure 5-56 Policy status display for policy group

In Figure 5-57, Tivoli Enterprise Portal shows STI_QoS_TraderWeb, STI roboticmonitors status. For more detailed status, click the icon , it links to therelated workspace.





Figure 5-57 STI_QoS_TraderWeb robotic monitor status display

The Tivoli Enterpirse Portal provides historical data by configuration and startinghistorical data collection. For more information about historical data collectionsetting, refer to IBM Tivoli Monitoring documentation. Figure 5-58 shows anexample of the agent availability historical data over the last 8 hours.





Figure 5-58 Display the agent availability historical data in Tivoli Enterprise Portal




Draft Document for Review March 1, 2007 5:22 pm 7151chJ2EEoperation.fm

Chapter 6. ITCAM for J2EE Operations

In this chapter we describe ITCAM for J2EE Operations. We explore theconcepts of the products, explains the installation and demonstrate some basicuses of the ITCAM for J2EE Operations.

This chapter contains the following sections:

6.1, “ITCAM for J2EE Operations architecture” on page 254

6.2, “ITCAM for J2EE Operations installation” on page 254

6.3, “ITCAM for J2EE Operations usage” on page 256

6




7151chJ2EEoperation.fm Draft Document for Review March 1, 2007 5:22 pm

6.1 ITCAM for J2EE Operations architecture

ITCAM for J2EE Operations provides a simple out-of-the-box solution forcollecting and analyzing WebSphere and WebLogic application servers health.ITCAM for J2EE Operations collects performance metric from the applicationservers and stores them in SNMP interface. This data can then be retrievedusing Netcool/OMNIbus Object Server or displayed using Tivoli EnterprisePortal.

Figure 6-1 shows the conceptual diagram of ITCAM for J2EE Operations.

Figure 6-1 ITCAM for J2EE Operations concepts

ITCAM for J2EE Operations is a rebranding of Netcool/SSM solution in which theSSM agent is installed on the application server machine and monitors theapplication server. There is no modification needed on the application side.

This redbook focuses on the capability of ITCAM for J2EE Operations to be able

to display the monitoring data from Tivoli Enterprise Portal. The interface isacquired as an add-on to the Tivoli Enterprise Portal. A universal agent SNMPinterface must then be defined to retrieve data from ITCAM for J2EE Operationsagent. The add-on also includes some workspace definitions that allow theseinformation to be displayed.

WebSphere

Application

Server

PerfServlet.

ear

ITCAM for J2EE

OperationsSSMAgent

SNMP

IBM Tivoli

Monitoring 6.1

Univeral Agent

Tivoli Enterprise

Monitoring Server

Tivoli Enterprise

Portal Server




6.2 ITCAM for J2EE Operations installation

Installation consists of the following steps:

6.2.1, “Installing the code” on page 255 6.2.2, “Activating WebSphere support” on page 255 6.2.3, “Preparing Tivoli Enterprise Portal” on page 256


6.2.1 Installing the code

The installation of ITCAM for J2EE Operations in Linux is performed using aconsole based interface. After accepting the license agreement, the installationsetting is shown in a text menu shown in Figure 6-2.

Figure 6-2 ITCAM for J2EE Operations console menu

When you press enter, installation commenced and the product is installed onthe specified directory. In our case it is /opt/netcool/ssm.

The agent can be started using the executable nco_m_ssmagent in /opt/netcool/ssm/bin. You can interact with the agent using the administrativeconsole executable nco_m_ssmcons.

6.2.2 Activating WebSphere support



Chapter 6. ITCAM for J2EE Operations 255

For WebSphere Application Server monitoring, you must setup the WebSphereenvironment using the script ws_setup.sh. The script takes the following

arguments:Binary directory The path in which wsadmin executable residesUsername Optional user name for accessing wsadminPassword Optional password for accessing wsadmin


The setup will activate PMI monitoring and install PerfServlet.ear enterpriseapplication. The PerfServlet will serve as the data collector for ITCAM for J2EE

Operations.

Restart the application server when done.

6.2.3 Preparing Tivoli Enterprise Portal

Tivoli Enterprise Portal module for ITCAM for J2EE Operations is available fromthe Open Process Automation Library (OPAL) Web-page:

http://catalog.lotus.com/topal?NavCode=1TW10TM2ZThe zip file should then be exploded in the machine with both Universal Agentand Tivoli Enterprise Portal Server installed. It includes the detailed installationinstruction.

1. Copy the setup executable to the appropriate ITCAM for J2EE Operationsagent machine such as ssm32-itmj2ee01.0.0-<platform>.* and run theexecutable.

2. Modify the Universal Agent configuration file to use SNMP data provider.

– For Windows, edit %CANDLE_HOME%\TMAITM6\KUMENV file and addsnmp to the KUMA_STARTUP_DP line.

– For UNIX, configure Universal Agent using the Tivoli Monitoring Servicesmanagement and check the SNMP Data Provider under the AgentParameter tab.

3. You can then issue the itmconfig command to import the data definition(*.mdl) and the workspace definitions (*.sql).

4. Restart Universal Agent, Tivoli Enterprise Portal Server and Tivoli EnterprisePortal desktop.

6.3 ITCAM for J2EE Operations usage




We look at the usage from the Tivoli Enterprise Portal point of view. We divide thediscussion into:

6.3.1, “Setting up historical collection” on page 257 6.3.2, “Setting up target systems” on page 257 6.3.3, “Workspace samples” on page 258


6.3.1 Setting up historical collection

Most of the chart in ITCAM for J2EE Operations workspaces includes statisticsover time. This information are not available as the Universal Agent would onlyretrieve data in real time. The charts are constructed from historical data. Thisindicates that data must be collected into the historical database.

Follow the following to setup historical collection for ITCAM for J2EE Operationsfor WebSphere data:

1. Log in to the Tivoli Enterprise Portal

2. From the menu, choose Edit→

History Configuration….3. Select WAS_WEBSPHERE from the product drop down menu (for other

ITCAM for J2EE Operations feature, you can use APC_APACHE orWBL_WEBLOGIC).

4. Select all attribute groups and define the appropriate parameters for yourenvironment. Click Configure Groups.

5. Select all attribute groups again and click Start Collection.

6.3.2 Setting up target systems

As the data are all collected from a single Universal Agent, you have to tell theUniversal Agent the actual target systems that you want to monitors. This isperformed from Tivoli Enterprise Portal. The following steps configure collectionfor our WebSphere Application Server agent in srv177:

1. In the tree view, navigate to the machine running the Universal Agent in theEnterprise tree.

2. Use the WAS_WEBSPHERE workspace to monitor WebSphere ApplicationServers. Right click and select Take Action…→ Select….

3. Select Monitor start from the Name drop down menu and for theparameters, enter the TCP/IP address of the computer running ITCAM forJ2EE Operations agent in the AgentData field, supply the poll period in theInterval field and click OK. See Figure 6-3 on page 258.





Figure 6-3 Monitoring ITCAM for J2EE Operations

4. Select the system corresponding to the application you wish to monitor in theDestination Systems list and click OK again.

6.3.3 Workspace samplesThe resulting workspace for monitoring in our environment is shown inFigure 6-4. The tree points to the Universal Agent host, srv177.





Figure 6-4 ITCAM for J2EE Operations workspace

The WAS_WEBSPHERE system is then consists of serveral workspaces thatreflects the available monitoring for ITCAM for J2EE Operations, thoseworkspaces are shown in Figure 6-5 on page 259.




Figure 6-5 ITCAM for J2EE Operations workspaces

Lets look at some of these workspaces.


JVM runtime workspace, see Figure 6-6.

Figure 6-6 JVM runtime workspace

System workspace, see Figure 6-7 on page 261.





Figure 6-7 System workspace

Web application summary workspace, see Figure 6-8 on page 262.





Figure 6-8 Web application summary workspace

Transactions workspace, see Figure 6-9 on page 263.





Figure 6-9 Transactions workspace




Draft Document for Review March 1, 2007 5:22 pm 7151ch-netcool-ism.fm

Chapter 7. ITCAM for Internet ServiceMonitoring

This chapter contains the implementation and monitoring usage of ITCAM forInternet Service Monitoring in our environment. The discussion includes:

7.1, “Internet service monitoring” on page 266

7.2, “ITCAM for Internet Service Monitoring architecture” on page 266

7.3, “Installing ITCAM for Internet Service Monitoring” on page 268

7.4, “Configuration and usage” on page 277

7




7151ch-netcool-ism.fm Draft Document for Review March 1, 2007 5:22 pm

7.1 Internet service monitoring

The ITCAM for Internet Service Monitoring is the new name for Netcool/InternetService Monitors. It allows monitoring for Internet application availability andresponse monitoring. It provides lightweight service availability testing for morethan 20 TCP/IP based protocols. This infrastructure integrates with otherNetcool® based solution for systems monitoring and network management.

Some overview of Netcool solution for network and event management can beread from the <Steve’s book>, SG24-7xxx.

ITCAM for Internet Service Monitoring probes Internet application using standardinterface to collect data from:

Host systems Applications Internet applications

7.2 ITCAM for Internet Service Monitoring architecture

ITCAM for Internet Service Monitoring consists of a set of interrelatedcomponents, each of which performs a monitoring, configuration, dataprocessing, and reporting function. The main components of ITCAM for InternetService Monitoring are the monitors, which regularly poll or test Internet servicesto check their status. The test results generate data for evaluation, reporting andalert generation. This data can be used for Service Level Monitoring. Figure 7-1on page 267 shows the components of ITCAM for Internet Service Monitoring.





Figure 7-1 ITCAM for Internet Service Monitoring architecture

Based on Figure 7-1, the main components are:

Monitors

The monitors test specific Internet services and forward test results to theDatabridge. They emulate the actions of a real user of the service. Forexample, the HTTP monitor periodically attempts to access a Web page byemulating requests that a Web browser would usually send when a user visitsthe Web page. It generates an event recording the result of the test, which is

sent to the Databridge. The key functions of monitors are their pollingfunctions. The monitors actively poll or test services at regular intervals byinjecting transactions or queries into the target service, and generatingperformance evaluation data.

ISMServer

ISMServer provides configuration, management and reporting functions. Ituses monitoring profiles for configuring and scheduling the testing performed

ITCAM for ISM

Databridge ISM server

Monitors

Web administration

and reporting

NetCool SM

Reporter

NetCool

ObjectServer

profile

NetCool licenseserver



Chapter 7. ITCAM for Internet Service Monitoring 267

by monitors. The profiles include criteria for evaluating SLAs and service

availability based on the results of each monitor’s service tests. TheISMServer provides a Web-based interface for accessing the ISMServerconfiguration, management and reporting functions. All reports and statuspages are provided in the Web browser based interface.

Databridge


The databridge is the communications bridge between the monitors with theISMServer and any other components that requires data from the monitors. It

also interfaces with the ObjectServer and Netcool/SM Reporter. It receivesthe results of service tests performed by the monitors, converts this data intodifferent formats for processing by ISMServer, an ObjectServer, orNetcool/SM Reporter. The formats are:

– XML data logs, which ISMServer uses to compile SLA views andperformance graphs

– Alerts are sent to ObjectServers– Service Monitor Data Records (SMDRs), which Netcool/SM Reporter uses

to generate reports

Netcool license server is a standalone server component that provideslicensing functionality for the Netcool portfolio of products. This component isbased on the premise that license administration and maintenance can besimplified by centralizing license data on one or more designated licenseservers, with licenses being drawn from a server as necessary. This is arequired component for running any Netcool software.

Netcool SM Reporter: a comprehensive reporting solution for Netcoolproduct.

Netcool Object Server an interface to store overall monitoring informatino forNetcool products.

7.3 Installing ITCAM for Internet Service Monitoring

In our environment, we decided to only run the minimal ITCAM for InternetService Monitoring component. This includes installing the license server and the

main ITCAM for Internet Service Monitoring component in a single machine. Wedid not implement the Object Server nor the SM Reporter. The installation isdiscussed in the following sections:

7.3.1, “Installing Netcool license server” on page 268 7.3.2, “Installing Internet Service Monitors” on page 270 7.3.3, “Problem determination and log files” on page 275




7.3.1 Installing Netcool license server

Netcool/License server must be installed and configured before running anyNetcool product in your environment. You must also ensure that you have therequired license files containing license feature codes for the Netcool productsand related components that you are authorized to use.


The license server can be a single stand alone system or installed as aredundant server to accomodate fault tolerance. We implemented the single

license server scenario which is the simpler configuration, recommended forsmaller implementation.

The steps involved in installing Netcool/License server are:

1. Download the tar and lic file. Extract the tar file into a temporary directory.

2. To start the installer, execute the following command from the temporarydirectory to which you extracted the archive:

./INSTALL [-errorlevel (debug|info|warning}]

Use the optional -errorlevel parameter to set the level of detail in theinstallation log file for information or troubleshooting purposes.

3. The installer prompts you for the location of the NCHOME variable, if notdefined. Accept the proposed location by pressing Enter, or provide a newlocation and press Enter. We use the default NCHOME variable of

/opt/netcool.

4. The installation window show information about the Licence Agreement andthe setup type of installation. We select the Default option.

5. The Netcool/License server installer provides a summary of the operations itwill perform during the installation process. Review the installation settings, asshown in Figure 7-2 on page 269, and click Install to complete theinstallation.




Figure 7-2 Installation review of Netcool/License server


6. The Netcool/License server files are stored in the location $NCHOME/license,in our case it is /opt/netcool/license. Save the license file (.lic) in the

$NCHOME/license/etc directory of the system running the Netcool/Licenseserver. Use a unique file name.

7. Start the license server by entering following command:

$NCHOME/license/bin/nc_start_license &

When the license server is started, it reads all license files in$NCHOME/license/etc and then waits for incoming license requests. Thelicense server writes information to license.log in directory$NCHOME/license/log.

8. Verify the installed license file. Enter following command:

$NCHOME/license/bin/nc_print_license

This command lists all served licenses of the Netcool/License server. The

Figure 7-3 on page 270 shows a excerpt of our configuration.

Figure 7-3 Command nc_print_license

Note: When checking for the license server process using the UNIX ps command, the license server daemon is identified as lmgrd.

ncadmin@srv179:/opt/netcool/license/bin #./nc_print_licenselmstat - Copyright (c) 1989-2003 by Macrovision Corporation. All rightsreserved.Flexible License Manager status on Fri 11/3/2006 15:49License server status: 27000@srv179License file(s) on srv179: /opt/netcool/license/etc/license.lic:srv179: license server UP (MASTER) v9.2Vendor daemon status (on srv179):

netcool: UP v9.2Feature usage info:Users of ncism_dhcp: (Total of 9999 licenses issued; Total of 0 licenses in use)Users of ncism_dns: (Total of 9999 licenses issued; Total of 0 licenses in use)Users of ncism_ftp: (Total of 9999 licenses issued; Total of 0 licenses in use)Users of ncism_http: (Total of 9999 licenses issued; Total of 0 licenses in use).....




7.3.2 Installing Internet Service Monitors

This section discusses installation of the ITCAM for Internet Service Monitoring.We are using ITCAM for Internet Service Monitoring V2.4 on Red Hat EnterpriseLinux V3. The installation of the ITCAM for Internet Service Monitoring can beoutlined as follows:


1. Create the necessary user ID for ITCAM for Internet Service Monitoring.ITCAM for Internet Service Monitoring requires a user ID as the installation

owner and the default monitor process. We use:ncadmin Owner of ITCAM for Internet Service Monitoring files

and directoriesnetcool Default group for user ID ncadmin

Use the appropriate operating system facility to create the group and user. Inour environment, we use the groupadd and adduser commands. Thesecommands create the group and user as follows:

groupadd netcool

useradd -c Netcool_Admin_ITSO -d /home/ncadmin -g netcool -n -pxxxxxx -s /bin/sh -u 10500 ncadmin

2. Start the installer, the installer can be invoked in a Graphical interface or usinga console mode. The default is the GUI installer, the console mode can beinvoked using the -console option. The installer is invoked using the INSTALLcommand from the archive directory.

3. The installer prompts you for the location of the NCHOME variable, if notdefined. Accept the proposed location by pressing Enter, or provide a new

location and press Enter. Our location of variable NCHOME is defined withthe value of /opt/netcool. As we install this in the same machine as our licenseserver, the NCHOME variable should already been configured.

4. The installation process appears, like in Figure 7-4. After agreement to theterms of license, we select the default setup type.




Figure 7-4 Netcool/Internet Service Monitor welcome dialog


5. Enter the required settings and configuration options. The installer presents aseries of dialogs and menus that provide options and settings for configuring

the Netcool/Internet Service Monitor installation. In our environment we donot have an Object Server. We use the default settings for Object Server, asshown in Figure 7-5 on page 272.

Figure 7-5 Object server default configuration

The description for options and settings are provided in Table 7-1 onpage 272.

Table 7-1 Netcool/Internet Service Monitor installation options and settings

Option or setting name Description

ISMServer Distribution Port The port on which ISMServer distributes profiles.

ISMServer Port The port that ISMServer uses to serve thebrowser-based interface.

ObjectServer Host The DNS name or IP address of the ObjectServer towhich the Databridge forwards events.

ObjectServer Name The name of the ObjectServer to which the Databridge




ObjectServer Name The name of the ObjectServer to which the Databridge

and ISMServer send events and SLA data.

ObjectServer Por t The ObjectServer port to which the Databridgeforwards events.




Figure 7-7 Configure ISMServer settings

8. The ITCAM for Internet Service Monitoringinstaller provides a summary of the

operations it will perform during the installation process. Review theinstallation settings, as shown in Figure 7-8 on page 275, and click Install tocomplete the installation.





Figure 7-8 Installation review

9. Start the ITCAM for Internet Service Monitoring with following shell script:

$NCHOME/ism/bin/ism_startup.sh

This script starts the Databridge, the Netcool/Internet Service Monitormonitors and ISMServer. In our environment the value of variable NCHOMEis /opt/netcool.

The Web console interface is discussed in “Configuration and usage” on




The Web console interface is discussed in “Configuration and usage” on

page 277. The default username and password are ism and netcool.

7.3.3 Problem determination and log files

This section provides some tips for problem determination and log file locationsthat we encounter during our work:


The ISMServer, monitors and databridge provide their log files in the directory$NCHOME/log/ism. In our case the directory is /opt/netcool/log/ism:

– bridge.log– ismserver_startup.log– ismserver.log

For problems in Databridge from executing the ism_startup.sh shell script.This includes the ISMServer seems not to be running, or the monitorscollecting no information data. In this case, check the property file$NCHOME/etc/ism/bridge.props for the Databridge. Check the setting forvariable Module0SharedLib and Module0PropFile. The content is shown inExample 7-1 on page 276.

Example 7-1 The bridge.props

Manager: ‘Internet Service Monitors’MaxLogFileSize: 1048576MessageLevel: ‘warn’MessageLog: ‘/opt/netcool/log/ism/bridge.log’Module0SharedLib:’libSMModuleDatalog’Module0PropFile:’’

Module1SharedLib:’NONE’Module1PropFile:’’Module2SharedLib:’NONE’Module2PropFile:’’

In case of running a configured Object Server, the setting for variableModule0SharedLib and Module0PropFile in property file would be as shownin Example 7-2 on page 276

Example 7-2 bridge.props with Object Server

Manager: ‘Internet Service Monitors’MaxLogFileSize: 1048576MessageLevel: ‘warn’MessageLog: ‘/opt/netcool/log/ism/bridge.log’Module0SharedLib:’libSMModuleObjectServer’Module0PropFile:’/opt/netcool/etc/ism/props/objectserver.props’Module1SharedLib:’NONE’Module1PropFile:’’




p

Module2SharedLib:’NONE’Module2PropFile:’’

You can also try to start the databridge manually using the user ID for theISMServer. Therefore be sure to set the appropriate runtime definitions for the


variables LD_LIBRARY_PATH, LIBPATH and NCHOME. Using followingcommands or a self-made script, see Example 7-3 on page 277.

Example 7-3 Starting databridge manually

export NCHOME=/opt/netcool

LIBPATH=$NCHOME/platform/linux2x86/lib:$LIBPATHexport LIBPATH=$NCHOME/ism/platform/linux2x86/lib:$LIBPATH

LD_LIBRARY_PATH=$NCHOME/platform/linux2x86/lib:$LD_LIBRARY_PATHexport LD_LIBRARY_PATH=$NCHOME/ism/platform/linux2x86/lib:$LD_LIBRARY_P

ATH#### start the databridge##$NCHOME/ism/platform/linux2x86/bin/nco_m_bridge

7.4 Configuration and usage

This section illustrates the usage of ITCAM for Internet Service Monitoringusinbg the Web-based interface. The discussion includes:

7.4.1, “Define profiles and profile elements” on page 277 7.4.2, “Status reports” on page 281

7.4.1 Define profiles and profile elements

The usage scenario performs a sample configuration for monitoring andreporting a Web application using HTTP protocol. We have a distributedapplication and we want to manage its response time with ITCAM for InternetService Monitoring.

1. To access ISMServer, open a Web browser and enter the URL of the ISMserver with the port defined in Figure 7-7 on page 274. In our case we areusing the default port of 9500. Our URL is:

http://srv179.itsc.austin.ibm.com:9500/




Figure 7-9 on page 278 show the login page.


Figure 7-9 ITCAM for Internet Service Monitoring login page

2. The default username and password are ism and netcool. After successfullyLogin, the Profiles page is displayed, with an empty list.

3. Define the first profile for the environment to be monitored, by using Create anew profile. We create a new profile named netc1, as shown in Figure 7-10.

Figure 7-10 Netcool/Internet Service Monitor - View profiles




4. Choose Select profile for opening a specific profile. See Figure 7-11 onpage 279. Click Add new element in the profile elements page.




Retest Poll Interval: 1Action: GETServer Authentication:NONEDescription: HTTP srv177Active: activated

Save the configuration by click Submit changes.




Figure 7-13 Editing an HTTP-element

6. The configuration is activated immediately and the monitor starts for pollingthe Web application. ITCAM for Internet Service Monitoring displays thestatus of each profile element using color-coded indicators. Over time, as thestatus of the service changes, the color of the service indicator changes so


that you can see how the service is performing in relation to the Service Level.This performance is shown as both the current status and the Service Levelcompliance over the last hour.

The results of our monitoring environment appears in profile element pages inFigure 7-14 on page 281.

Figure 7-14 Profile element pages

7.4.2 Status reports

Using ITCAM for Internet Service Monitoring, status reports that provideinformation on the performance of monitored services can be viewed. Reportsprovide color-coded Service Level status indicators, detailed service levelgraphs, and performance graphs.

On Profile pages and Profile Element pages, ITCAM for Internet ServiceMonitoring provides indicators that show the SLA status of a service. The CurrentStatus indicator shows the SLA status of the most recent poll of the service andthe Last Hour SLA Status indicator shows the status over the last hourly interval.On Profile pages, the indicators show the status of each monitor group in theprofile. On Profile Elements pages, they show the status of each profile element.

1. Select the Last Hour SLA Status button in profile element pages. The reportfor measurement of the Service Level Agreement statistics appears. In case




of our sample, shown in Figure 7-15 on page 282, we stopped and started theWebSphere Application Server srv176 to demonstrate the availability of theWeb application. The graph of the 3 Hour view shows the appropriatepercentage of downtime and uptime.


Figure 7-15 Service Level Agreement report

2. Beginning from the profile element pages click Current Status to view theresponse time report. According to our sample Web application in application

server srv176 in Figure 7-15 the averaged and aggregated response timesare shown in Figure 7-16 on page 283. The report of 1 Hour view shows thedowntime and the total response time in milliseconds. The distinctive oneincreased bar after downtime demonstrates the initialization step of the Webapplication for the first HTTP request.





Figure 7-16 View current status report

3. ITCAM for Internet Service Monitoring provides various reports, that show theSLA status of a service. Choose the value to graph Fine Grained Timings,as displayed in Figure 7-17 on page 284. The graph provides detailedinformation about the measurement of a service contains response time,download time, lookup time and connect time. This could be helpful using the

service status to identify problem areas quickly and act to resolve them beforethey become critical.





Figure 7-17 Fine grained timings statistics




Draft Document for Review March 1, 2007 5:22 pm 7151chSOA.fm

Chapter 8. ITCAM for SOA

This chapter discribes ITCAM for SOA V6.1 concept, installation and usage: 8.1, “ITCAM for SOA overview” on page 286

8.2, “ITCAM for SOA installation” on page 296

8.3, “ITCAM for SOA usage scenarios” on page 317

8




7151chSOA.fm Draft Document for Review March 1, 2007 5:22 pm

8.1 ITCAM for SOA overview

This section describes ITCAM for SOA V6.1. The discussion includes: 8.1.1, “Product features” on page 286

8.1.2, “Product components” on page 288

8.1.3, “ITCAM for SOA management resources” on page 292

8.1.1 Product features

ITCAM for SOA manages service-oriented architecture (SOA). It can monitor,manage, and control the Web services layer of IT architectures while drillingdown to the application or resource layer to identify the source of bottlenecks orfailures and to pinpoint services that take the most time or use the mostresources. ITCAM for SOA:

Provides service monitoring views in Tivoli Enterprise Portal. ITCAM for SOAworkspaces consist of some data collector based workspaces:

Performance Summary

Shows the response time information for Web servicescalls as viewed from the client or the server.

Message Summary Shows the message statistics, including the volumeand size of message information.

Fault Summary Shows failure analysis for Web services calls.

Other workspaces for each agent are:

Service Management Agent Environment

Provides a summary of the Web services metrics for all

data collectors.

Service Management Agent

Shows the agent configuration summary, datacollectors, monitoring profiles and filters.

Mediation ConfigurationConfiguration entries for mediation on SCA.

Message arrival Workspace that shows the message arrival rate and

events based on the message arrival critical situation




events based on the message arrival critical situation. Leverages Tivoli Enterprise Portal situations to check thresholds. ITCAM for

SOA provides some predefined situations that you need to tailor. Thepredefined situations concern:

– Number of messages received by a service within a time window


– Size of the messages

Provides basic mediation support with the ability to filter or reject Web

services call messages from a particular client or service. It can log requestand response messages for analysis.

Offers heterogeneous platform coverage:

– Support for IBM WebSphere Application Server, CICS Transaction Server,Microsoft .NET, JBoss, BEA WebLogic and other SOA clients and servers

– Target IBM Enterprise Service Bus platforms: WebSphere ApplicationServer 5.x and 6.x, WebSphere Business Integration Server Foundation5.1.1

Displays a list of services and operations monitored in environment.

Leverages Tivoli Enterprise Portal workflow and policy editor forthreshold-triggered action sequences.

Offers the ability to include Services-layer views in Tivoli Enterprise Portal.

The context-rich views and inter-workspace linkages in the Tivoli EnterprisePortal enables users to drill down to IT resources to identify of Web servicebottlenecks and failures. By providing built-in and extensible alerts, situations,

and workflows, users can create powerful automated mediation scenarios via theTivoli Enterprise Portal.

The service metrics, aler ts, and automation workflows provided by ITCAM forSOA and other Tivoli products can be displayed in the Tivoli Enterprise Portalwith the cross-workspace linkages to provide a rich and multi-layered source ofinformation that can help to reduce the time and skills required for problemroot-cause analysis and resolution.

ITCAM for SOA includes the Web Services Navigator, a plug-in to IBM RationalApplication Development and other Eclipse-based tools. It provides deepunderstanding of the service flow, patterns, and relationships to developers andarchitects. The Web Services Navigator uses data from IBM Tivoli MonitoringV6.1’s Tivoli Data Warehouse or from the ITCAM for SOA log files using the LogAssembler tool.

In version 6.1 ITCAM for SOA contains a new component for mediation servicemanagement based on Service Component Architecture (SCA). It allows you to

modify some of the mediation service settings on the fly. Mediation is a facilitythat sits between Web Services requester and Web Services provider that allows



Chapter 8. ITCAM for SOA 287

modify some of the mediation service settings on the fly. Mediation is a facilitythat sits between Web Services requester and Web Services provider that allowsmanipulation of Web Services messages, includes format translation, filteringand enrichment.


8.1.2 Product components

ITCAM for SOA manages Web services. Web services can be viewed as a

remote processing facility that is defined through the use of Web ServicesDefinition Language (WSDL). Usual access uses Simple Object Access Protocol(SOAP) over HTTP. Internally, Web services are implemented using Java API forXML-based Remote Procedure Call (JAX-RPC). ITCAM for SOA installs itself asthe JAX-RPC handler to capture and manage Web services calls.

ITCAM for SOA consists of these logical components:

Web services data collector, which acts as the JAX-RPC handler andintercepts Web services calls to collect statistical information and write to alog file.

Tivoli Enterprise Monitoring Agent collects information from all of the datacollectors on a machine and forwards them to Tivoli Enterprise MonitoringServer. The data collectors and Tivoli Enterprise Monitoring Agent arediscussed in “Monitoring agent data collector” on page 289.

An Eclipsed-based viewer that processes log files that are generated by theWeb services data collector. It generates visual representations of variouscharacteristics of monitored Web services. See “IBM Web ServicesNavigator” on page 290.

Mediation SCA tools that allows partial monitoring of Service ComponentArchitecture within WebSphere Enterprise Service Bus. See “Managing SCAmediation” on page 292.





Monitoring agent data collectorITCAM for SOA works with several application server environments:

IBM WebSphere Application Server V5.1.0.5 with PQ89492, V6.0 and V6.1 IBM WebSphere Business Integration V5.1.1.1 IBM WebSphere Process Server v6.0.1 IBM WebSphere Enterprise Service Bus v6.0.1 IBM CICS(R) Transaction Server v3.1 and later BEA WebLogic Server v8.1.4 Microsoft(R) .NET v1.1 with Service Pack 1 and v2.0 JBoss v4.03 WebSphere Community Edition v1.0 and its Service Packs

SAP NetWeaver v6.40 with Service Pack 9 or later service packs IBM WebSphere DataPower®(R) SOA Appliance Firmware v3.5.0.5 or later

Figure 8-1 shows the ITCAM for SOA data collection conceptual architecture.

Figure 8-1 ITCAM for SOA structure

The monitoring agent data collector is implemented as a JAX-RPC handler orservice extension that is installed into the application servers that are hosting themonitored Web services. The handler is given control when either of the followingevents occurs:

A client application invokes a Web service, which is referred to as a

client-side interception.

ITCAM for SOA

Monitoring agent

Application Server

Web Services

handler or

extension

Data

collector

Data collector

adapter

IRA

Intellignent

Resource Model

log

configuration

Tivoli Enterprise

Management Server

Tivoli Enterprise Portal

Server




p

The Web service request is received by the hosting application server, whichis referred to as a server-side interception.

The monitoring agent records and collects monitored information into one ormore local log files. The information is then transferred to Tivoli Enterprise


Monitoring Server and can be archived into a historical database for laterretrieval with IBM Web Services Navigator.

ITCAM for SOA 6.1 focuses on the Simple Object Access Protocol (SOAP)engine of IBM WebSphere Application Server, WebSphere Service IntegrationBus, the Microsoft .NET Framework, and BEA WebLogic.

The Web services data collector supports both J2EE application client andserver container environments because JAX-RPC handlers are supported onlyby these environments. The Web services must be compliant with JSR-109specifications.

To ensure proper operation of the JAX-RPC handler, verify that the clientapplications are written according to the conventions that can be found at thefollowing location:

http://www.jcp.org/aboutJava/communityprocess/final/jsr109/

IBM Web Services NavigatorIBM Web Services Navigator is an Eclipsed-based tool used to visualize Webservices in an SOA environment. It provides a graphical display of:

Web services transaction flows Service topology Flow patterns

Web Services Navigator concepts can be illustrated as shown in Figure 8-2.

Web Services

Navigator

Log Assembler

TEMA

TDWwarehouse

Data

collector

Metric

log

Data

collector

Metric

log

Data

collector

Metric

log

Combined






Figure 8-2 Web Services Navigator

Data

collector

Metric

log

Combined

metric log


The Web Services Navigator is a log-browsing tool intended for offline analysis ofSOA Web services. Four primary views that are provided:

Statistic tables:– Message statistics

Per-message statistics including requestor, provider, send/receive time,and message size.

– Invocation statistics

Response time, network delay, message size, and more for each Webservice invocation.

– Transaction statisticsProvides statistics for aggregated transactions, including elapsed time,number of faults, number of machines this transaction involves, andnumber of invocations comprising this transaction.

– Pattern invocation statistics

Provides statistics for discovered patterns, including operation names,number of occurrences, response times, and message sizes.

Service topology view

A graphical representation of the monitored Web services that displays

aggregated information and information about the relationships between Webservices.

Transaction flows view

Transaction flow view displays Universal Markup Language (UML) stylesequence diagrams. Transaction flow shows a chronological view of eachtransaction, the flow between the various Web services over time, and thetopology and statistics for each transaction. The view can be zoomed to seethe details of individual transactions.

Flow pattern view

Note: To see actual message content from the ITCAM for SOA metric log:

1. Set a monitor control higher than “none” for any or all of the Webservices being monitored.

2. Include the subsequent xxxx.content.log when running log assembler.




Flow pattern view is a visual representation of the aggregated pattern oftransactions represented in the log file. The view also represents each patternas a distinct sequence of Web service calls and displays the frequency ofeach pattern.


Managing SCA mediationWebSphere Process Server and WebSphere Enterprise Service Bus introduce anew way to model services in an SOA, called the Service ComponentArchitecture (SCA). SCA is designed to separate business logic from itsimplementation, so that you can focus on assembling an integrated applicationwithout knowing implementation details.

There is a special type of SCA component, called a mediation. In aservice-oriented architecture (SOA), where services are loosely coupled ratherthan being connected directly to each other, mediations can be inserted betweenthe services, where they can intercept and process messages that are beingpassed between the services. Mediations can process these messages and take

appropriate actions, such as reroute, log, or transform a message, or create anotification or an event.

ITCAM for SOA provides the ability to dynamically enable and disable thedeployed mediation functions. This facility is available for application in theWebSphere Enterprise Service Bus or WebSphere Process Server runtimeenvironment. The invocation is provided in a new workspace in Tivoli EnterprisePortal called Mediation Configuration workspace, implementation as actions:

ConfigureMediation_610 DeletePrimitiveProperty_610

8.1.3 ITCAM for SOA management resources

The management resources for ITCAM for SOA that we discuss here are:

“Workspaces” on page 292 “Attributes” on page 294 “Situations” on page 294 “Actions” on page 295

WorkspacesITCAM for SOA delivers a set of predefined workspaces, which you can selectfrom Tivoli Enterprise Portal navigator view. Each workspace has its own set ofviews that display Web services data and metrics in various levels of details.Figure 8-3 shows the workspace navigator area.





Figure 8-3 Navigator in the workspace

These workspaces are available:

Service Management Agent workspace displays the current configurationdetails for the monitoring agent data collectors that are configured in differentapplication server instances. This workspace contains the following views:

– Data Collector Global Configuration– Data Collector Monitor Control Configuration– Data Collector Filter Control Configuration

Mediation Configuration workspace that contains the SCA mediationconfiguration. This workspace can be used to launch the SCA mediationactions.

Message Arrival Summary workspace provides a summary of the number ofmessages that arrive at the data collector for each combination of servicename, operation name, and remote IP address that has been configured as asituation. This workspace contains the following views:

– Message Arrival Details– Message Arrival by Service– Message Arrival by Operation

Services Management Agent Environment workspace represents the agentmonitoring applications for all of the application servers on that system. TheServices Management Agent Environment workspace provides a set of viewsthat summarize the performance, message activity, and fault occurrencesassociated with the Web services traffic through this monitoring agent This




associated with the Web services traffic through this monitoring agent. Thisworkspace contains the following views:

– Average Response Time by Operation– Number of Messages by Operation


– Average Message Size by Operation

Performance Summary workspace provides the inventory of currently activeand monitored services, as well as the response time of the services. Thisworkspace contains the following views:

– Average Response Time by Operation– Services Inventory

Messages Summary workspace provides details about the number and sizeof messages received for services, and service/operation combinations. Thisworkspace contains the following views:

– Number of Messages by Service - Operation - Type

– Average size of Messages by Service - Operation - Type Faults Summary workspace provides a general faults summary. This

workspace contains the following views:

– Faults Summary by Operation– Fault Details

AttributesAttributes are measurements that are collected by the IBM Tivoli Monitoring V6.1

family of products. ITCAM for SOA stores specific measurement or attributesrelevant to its needs and function.

Refer to IBM Tivoli Composite Application Manager for SOA Installation and User's Guide , GC32-9492. An appendix lists the attribute groups or tablesprovided with the ITCAM for SOA product. The tables that are available for longterm historical data collection are indicated in the description of the table, andshow the historical reference information that identifies each attribute within eachtable. Each table identifies the actual column name, attribute name, and a

description of the data provided. These attributes are used in ITCAM for SOAsituations.

SituationsIn IBM Tivoli Monitoring V6.1 context, situation is a condition where a set ofattributes are tested against a threshold within any filtering rules (if necessary).The situation evaluates these conditions at predefined intervals and invokes thenecessary automated responses and notification methods when needed.

ITCAM for SOA provides a set of predefined situations that are designed to helpmonitor critical activities and serve as templates for creating customized




monitor critical activities and serve as templates for creating customizedsituations for your own use. Predefined situations are started automatically whenthe product is installed. After they have been configured, the situation alertsprovided with ITCAM for SOA trigger event notification.


Table 8-1 lists the predefined situations that are provided with ITCAM for SOA.

Table 8-1 ITCAM for SOA situations

ActionsIn ITCAM for SOA V6.1 there are different sets of actions for different context.Although the available action types are the same, there are now 4 actions thatare available for each types:

The existing 6.0 actions are still kept for compatibility and coexistence with

ITCAM for SOA V6.0 agents and data collectors New generic ITCAM for SOA actions are labelled with suffix _610 thatcontains new parameters and functionality to be used with the new ITCAM for

Situation name Description

Fault Monitors the messages in the Web services flow to determinewhether a Web services fault has occurred.

Message ArrivalCritical

Alerts you to excessive amounts of Web services traffic (thenumber of messages received from one or more remote clientsexceeds a threshold that you specify).

Message Arrival

Clearing

Clears a previously triggered Message Arrival Critical situation.

This situation can also be used to alert for message falls below aspecified threshold (lack of activity alert).

Message Size Monitors the length, in bytes, of each message during the Webservices flow. If the length of the message is more than thethreshold value, then this situation is triggered.

Response TimeCritical

Monitors elapsed round-trip response time, in milliseconds, forthe completion of a Web services request.

Response Time

Warning

Monitors elapsed round-trip response time, in milliseconds, for

the completion of a Web services request.

Note: Each implementation should provide its own set of thresholds, as theproduct’s default will not fit your environment. You must tune your monitoringthresholds.

The default situations are based on individual service calls stored in theServices_Metric table. Analyzing on summarized information in theServices_Inventory table can reduce some of the monitoring overhead.




contains new parameters and functionality to be used with the new ITCAM forSOA V6.1 data collectors.


When invoked from the workspaces with Service Metric or Service Inventorydata, these data is inserted automatically as the arguments for the actions.The action name is prefixed with SM_* or SI_* respectively.

The available take action methods for ITCAM for SOA are:

AddFltrCntrl Creates new filter control settings to reject messagesAddMntrCntrl Creates new monitor control settings, these monitor affect

the data logging for use with IBM Web Service Navigator.DelFltrCntrl Deletes existing filter control settingsDelMntrCntrl Deletes existing monitor control settingsDisableDC Disables data collection and the ability to reject messagesEnableDC Enables data collection and the ability to reject messagesupdateLogging Defines the level of logging informationUpdMntrCntrl Updates existing message logging levels for monitor controlupdateTracing Enables or disables tracing

These actions can be invoked manually or triggered by a situation. Action canalso be triggered by workflows, which are predefined automations that you canbuild on the IBM Tivoli Monitoring platform.

8.2 ITCAM for SOA installation

This is the overall implementation procedure for ITCAM for SOA:

1. Plan for the configuration. It is important to have a good understanding of themanaged environment and the capability of the product. We discuss someplanning considerations in “Planning the implementation” below.

2. ITCAM for SOA is installed and operates within the management

infrastructure of the Tivoli Enterprise Monitoring Server services platform.Installation of IBM Tivoli Monitoring V6.1 must be performed before any otherITCAM for SOA component. Tivoli Monitoring installation information can befound in the IBM Tivoli Monitoring Installation and Setup Guide, GC32-9407.

3. Install the application support component for ITCAM for SOA on your TivoliEnterprise Monitoring Server, Tivoli Enterprise Portal Server, and TivoliEnterprise Portal systems (8.2.2, “ITCAM for SOA application supportinstallation” on page 299).

4. Install and configure the monitoring agents of ITCAM for SOA, see 8.2.3,“ITCAM for SOA monitoring agent installation” on page 306 and 8.2.4,“Enabling the monitoring agent” on page 309




Enabling the monitoring agent on page 309.

5. Metrics collected by the ITCAM for SOA data collector (DC) can be stored inthe Tivoli Data Warehouse. The Data Warehouse Proxy must be configuredon the Tivoli Enterprise Monitoring Server in order to enable historical data


collection for ITCAM for SOA. We discuss this in 8.2.5, “Configuringwarehouse proxy” on page 310 and 8.2.6, “Installing IBM Web ServicesNavigator” on page 315.

8.2.1 Planning the implementation

Planning considerations include:

, “IBM Tivoli Monitoring services” on page 297 , “ITCAM for SOA application support” on page 297 , “ITCAM for SOA monitoring agent” on page 298 , “IBM Web Service Navigator” on page 299

IBM Tivoli Monitoring servicesIBM Tivoli Monitoring services include the Tivoli Enterprise Monitoring Server,

and Tivoli Enterprise Portal Server must be already installed and configured inyour environment. Refer to IBM Tivoli Monitoring Installation and Setup Guide,GC32-9407, to understand the available options for deploying the variouscomponents on one or more systems in your enterprise.

Familiarize yourself with the Tivoli Enterprise Monitoring Server managementinfrastructure installed in your enterprise environment, including its variousfacilities to manage the system such as workflows and situations. Use the TivoliEnterprise Portal Server and Tivoli Enterprise Portal to understand workspacesand views for operators and their implication in the overall monitoring.

ITCAM for SOA application supportTo view the ITCAM for SOA monitored agents through the Tivoli Enterprise

Portal, you must install application support for the agent on the Tivoli EnterpriseMonitoring Server, Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal.

Note: This chapter intends to give an overview of ITCAM for SOA maincomponents and installation process. Refer to the IBM Tivoli Composite Application Manager for SOA Installation and User’s Guide , GC32-9492 formore detailed information.

Note: This chapter does not list steps to install, set up, or implement TivoliMonitoring Services. See Getting Started with IBM Tivoli Monitoring V6.1,SG24-7143.




g p pThe Tivoli Enterprise Monitoring Server and Tivoli Enterprise Portal Serverservices will be restarted during the ITCAM for SOA application supportinstallation process.


The application support files include:

Data structure definition for Tivoli Enterprise Monitoring Server attributes andattribute groups (tables). ITCAM for SOA contains two tables:Services_Metrics and Services_Inventory.

Situation definitions that allow proactive monitoring to be performed in theIBM Tivoli Monitoring environment.

Presentation information to be installed in the Tivoli Enterprise Portal Server,including help resources and workspace definitions.

Additional resources such as sample workflow and historical collectioninformation.

ITCAM for SOA monitoring agentIn a typical distributed environment, the Tivoli Enterprise Monitoring Server isinstalled on one system, Tivoli Enterprise Portal Server is installed on anothersystem, and Tivoli Enterprise Monitoring Agent is installed on additional multipleapplication server systems where Web services traffic is to be monitored.

You must install ITCAM for SOA agents on each system that has one or moreapplication server environments that run Web services, such as IBM WebSphere

Application Server, Microsoft .NET, and BEA WebLogic. Review the IBM Tivoli Composite Application Manager for SOA Release Notes , GI11-4096 thatcontains the most current information.

When you install ITCAM for SOA on the application server, select to install theagent support component. This includes the data collector component thatintercepts request and response messages for the Web services that you want tomonitor. You must configure the appropriate data collector after installing theagent component.

The IBM Tivoli Monitoring environment requires installation and configuration tobe performed on both distr ibuted and z/OS-managed systems where some of theplatform components are installed and run.

For more information about installing ITCAM for SOA on a supported z/OSoperating system, refer to Configuring IBM Tivoli Composite Application Manager for SOA z/OS , SN32-9493.

When the ITCAM for SOA monitoring agent is installed and the application serveris enabled, the data collector is the monitoring component of the ITCAM for SOA.It is implemented as a SOAP message handler and used to monitor Web




p gservices that flow across an interception point.


The interception point is a JAX-RPC handler in IBM WebSphere ApplicationServer and BEA WebLogic server environments and service extensions in theMicrosoft .NET environment.

IBM Web Service NavigatorIBM Web Services Navigator has these features in the Eclipse environment:

An import wizard to import Web services log files or retrieve data from ITCAMfor SOA historical data into the IBM Web Services Navigator.

Web Services Profiling perspectives with a set of views of Web servicestransactions.

A separate Log Assembler tool that can be used to manually combine locallystored metric and content log files from the multiple application servers inyour Web services environment into a single log file that can be imported tothe IBM Web Services Navigator for viewing.

8.2.2 ITCAM for SOA application support installation

This section provides installation procedures for application support for theITCAM for SOA monitoring agent on the Tivoli Enterprise Monitoring Server.

The installation for ITCAM for SOA application support is on the CD, whichprovides multiple-platform support (Windows, AIX, and Solaris binaries). Thewizard will copy the CD-ROM’s files into the disk. If you install this from disk, copythe CD content into the same path; otherwise the installation wizard will fail.

1. Navigate to the \KD4\ITM_ASI directory on the ITCAM for SOA product CD.The installer is provided to support IBM Tivoli Monitoring V6.1 installation.Select the appropriate operating system platform. For Windows, we invokesetup.exe.

2. The wizard can discover the IBM Tivoli Monitoring or Candle platforminstallation. It checks for the appropriate GSKit and Java environment. Wechoose the installation drive C: as shown in Figure 8-4.

Note: Another component for managing SCA mediation is not tested in theproject.





Figure 8-4 Installation drive





3. Because the Tivoli Enterprise Monitoring Server, Tivoli Enterprise PortalServer, and Tivoli Enterprise Portal are installed on one system, all of thecomponents are selected to install to the local machine. See Figure 8-5.

Figure 8-5 Installation features

Note: If you select any of the application support components that are alreadyinstalled, a warning window is displayed. You have the choice of overwriting

the existing installation files or unchecking the desired component to avoidoverwriting the files.





4. The ITCAM for SOA also support packaging of the agent for remotedeployment. See Figure 8-6.

Figure 8-6 Application support component





5. The installation summary provides a brief list of actions it will perform afterNext is clicked (Figure 8-7).

Figure 8-7 Installation action list





6. Select which components you want to configure as shown in Figure 8-8.

Figure 8-8 Configuration options

7. The next step is to enter the hostname of the machine where the TEP serveris installed, in our case we enter Lima.

8. Enter the information for the Tivoli Enterprise Management Hub or RemoteServer as shown in Figure 8-9 on page 305.





Figure 8-9 TEMA hub configuration.

9. The next step is to select if the TEMS is located on the same system. In ourinstallation that is the case.




Figure 8-10 TEMA configuration part 1


10.We enter the default configuration for the TEMS connection as shown inFigure 8-10 on page 305 and Figure 8-11.

Figure 8-11 TEMA configuration part 2

8.2.3 ITCAM for SOA monitoring agent installation

Monitoring agent installation differs by environment. This section gives anoverview of management agent installation. ITCAM for SOA monitoring agentinstallation includes the data collector, which is installed into each applicationserver environment where Web services traffic is to be monitored.

1. To launch the ITCAM for SOA monitoring agent Welcome window:

Note: If you are installing ITCAM for SOA monitoring agent on an applicationserver where the Tivoli Enterprise Portal is running, close the Tivoli EnterprisePortal client or browser.

If you are installing ITCAM for SOA monitoring agent on an application serverwhere the Tivoli Enterprise Monitoring Server and Tivoli Enterprise PortalServer are installed and running, open the Manage Tivoli EnterpriseMonitoring Services utility and stop these services. If these Tivoli Monitoringservices are running on other application servers in your enterprise, you donot have to stop them.




– For Windows installation, navigate to the /WINDOWS directory and selectsetup.exe from the ITCAM for SOA product CD.


– For UNIX installation, open a command session and navigate to the rootdirectory of the ITCAM for SOA CD. Issue this command: ./install.sh

2. We demonstrate the installation on a Linux machine in Example 8-1.

Example 8-1 Linux installation

# ./install.sh

INSTALLEnter the name of the IBM Tivoli Monitoring directory[ default = /opt/IBM/ITM ]:/opt/IBM/ITMSelect one of the following:1) Install products to the local host.2) Install products to depot for remote deployment (requires TEMS).3) Exit install.Please enter a valid number: 1Initializing ...Software Licensing Agreement

1. Czech2. English

. . .Please enter the number that corresponds to the language you prefer. 2Software Licensing Agreement

. . .Enter "1" to accept the agreement, "2" to decline it or"99" to go back to the previous screen. 1Product packages are available in /code/SOA61-linux/unix

The following products are currently installed in "/opt/IBM/ITM:". . .

The following prerequisites should be installed now:IBM Tivoli Monitoring Shared Libraries V610R437 @ Linux Intel R2.4 (32 bit)Tivoli Enterprise Services User Interface V610R291 @ Linux Intel R2.4 (32 bit)Do you want to install these prerequisites [ y or n; "y" is default ]? y... installing package "axli6243"; please wait.=> installed package "axli6243."... installing package "uili6243"; please wait.=> installed package "uili6243."Product packages are available for the following operating systems andcomponent support categories:1) Linux AMD64 R2.6 (64 bit)) l ( b )

Note: It is recommended to start the agent with the same user ID used to startWebSphere, because the Agent should be able to start and stop WebSpherewith the default startServer and stopServer script.




2) Linux Intel R2.4 (32 bit)…[ number "2" or "Linux Intel R2.4 (32 bit)" is default ]:2


You selected number "2" or "Linux Intel R2.4 (32 bit)"Is the operating system or component support correct [ y or n; "y" is default]? y

The following products are available for installation:1) ITCAM for SOA V06.10.00.002) Tivoli Enterprise Services User Interface V06.10.04.003) all of the aboveType the numbers for the products you want to install, or type "q" to quitselection.If you enter more than one number, separate the numbers by a comma ora space.Type your selections here: 1The following products will be installed:

ITCAM for SOA V06.10.00.00Are your selections correct [ y or n; "y" is default ]?y... installing "ITCAM for SOA V06.10.00.00 for Linux Intel R2.4 (32 bit)";please wait.=> installed "ITCAM for SOA V06.10.00.00 for Linux Intel R2.4 (32 bit)."... Initializing database for ITCAM for SOA V06.10.00.00 for Linux Intel R2.4(32 bit).

Do you want to install additional products or product support packages [ y orn; "n" is default ]?n


... finished postprocessing.Installation step complete. As a reminder, you should install product support on each of your TEM serversfor any agents you have just installed. This is done via the "[ITMhome]/bin/itmcmd support" command on your TEM servers.You may now configure any locally installed IBM Tivoli Monitoring product viathe "/opt/IBM/ITM/bin/itmcmd config" command.

3. After finishing the installation we have to configure the agent by running the./itmcmd.sh config -A d4 command form the /bin directory of yourinstallation where d4 is the 2-character product code for ITCAM for SOA. Forfurther steps see the script in Example 8-2.

Example 8-2 Configuration of agent

# ./itmcmd config -A d4Agent configuration started...

Will this agent connect to a TEMS? [YES or NO] (Default is: YES):YESTEMS Host Name (Default is: srv178): lima




Network Protocol [ip, sna, ip.pipe or ip.spipe] (Default is: ip.pipe):Now choose the next protocol from one of these:


- ip- sna- ip.spipe

- noneNetwork Protocol 2 (Default is: none):noneIP.PIPE Port Number (Default is: 1918):1918Enter name of KDC_PARTITION (Default is: null):null Configure connection for a secondary TEMS? [YES or NO] (Default is:NO):NOEnter Optional Primary Network Name or "none" (Default is: none):noneAgent configuration completed...

8.2.4 Enabling the monitoring agent

This section describes how to enable the ITCAM for SOA monitoring agent datacollector handler in the appropriate application server systems, depending on theapplication server environment you have installed on this application server.

After ITCAM for SOA monitoring agent is installed on the application server. The

data collector directory structure is created in the Tivoli Enterprise MonitoringAgent base directory as follows:

For Windows %TEMA_HOME%\TMAITM6\KD4For UNIX $TEMA_HOME/<OS_INTERP>/d4/KD4For z/OS <TEMA_HOME>

These directories contain all files required to run the data collectors.

Note: You do not have to start the ITCAM for SOA monitoring agent until themonitoring agent is enabled for the application server. If you start themonitoring agent prior to enabling the application server, the agent will startbut will have to be stopped and restarted after enabling the application server.

Tivoli Enterprise Monitoring Server will not collect data from ITCAM for SOAmonitoring agent if you enabled the application server after initially starting theITCAM for SOA service.

Note: An install script called KD4configDC is used to configure the datacollector for all application server platform. However, each platform requires itsown additional parameters and steps that must be performed to enablemonitoring of Web services.




g


Depending on your operating system platform, issue KD4configDC.sh orKD4configDC.bat. The arguments for this command vary depending on theapplication server environment. Refer to the IBM Tivoli Composite Application

Manager for SOA Installation and User’s Guide , GC32-9492, for more detailedinformation about the KD4configDC options.

We only enable the data collection in our WebSphere Application Serverenvironment. For IBM WebSphere Application Server, run this command at acommand prompt:

KD4configDC -enable -env 1 <WAS_HOME>

This command enables IBM WebSphere Application Server to use the KD4 datacollector as a JAX-RPC handler. The kd4dcagent.jar file is installed into the%WAS_HOME%/lib/ext directory.

After the ITCAM for SOA monitoring agent data collector has been configured,stop and restart IBM WebSphere Application Server.

8.2.5 Configuring warehouse proxy

You can configure the warehouse proxy to start retrieving data into Tivoli DataWarehouse from the Manage Tivoli Services windows:

1. As shown in Figure 8-12, right-click Warehouse Proxy→ Reconfigure.

Note: If you have set the WAS_HOME environment variable, the configuration

program can be invoked without any argument. The WAS_HOME environmentvariable is typically set using the setupCmdLine program from WebSphere.





Figure 8-12 Manage Tivoli Monitoring Services window





2. The first part of the configuration is specifying the Tivoli Enterprise MonitoringServer. Figure 8-13 shows the dialogs.

Figure 8-13 Warehouse proxy configuration - TEMS settings





3. The database setting is also collected as shown in Figure 8-14. We use theWAREHOUS database in our DB2 UDB.

Figure 8-14 Warehouse proxy configuration - database settings





Now the warehouse proxy has been configured and started. You can configuredata collection for the IBM Tivoli Monitoring agents. To enable ITCAM for SOAcollection, click the historical data configuration button in Tivoli Enterprise

Portal, and in the dialog shown in Figure 8-15, specify that the ITCAM for SOAinformation is to be collected.

Figure 8-15 Configuring historical collection for ITCAM for SOA

ITCAM for SOA collects a large amount of data. You may want to limit thecollection to a particular shorter time. The data from ITCAM for SOA in the metrictable will be used by IBM Web Services Navigator.




table will be used by IBM Web Services Navigator.


8.2.6 Installing IBM Web Services Navigator

IBM Web Services Navigator runs in the Eclipse environment. ITCAM for SOArelease 6.1 is packaged with its own Eclipse V3.0.2 environment. You can installIBM Web Services Navigator into IBM Rational Application Developer V6.1 andIBM Rational Software Architect V6.1, which are built on the Eclipse platform.Refer to IBM Tivoli Composite Application Manager for SOA Tools version 6.1.0 ,GC32-9494.

IBM Web Services Navigator can be installed with a new Eclipse environment orto an existing Eclipse environment as an Eclipse plug-in. Currently IBM WebServices Navigator is supported only on Windows and Linux based operatingsystems. Figure 8-16 shows the installation path and option that we use.

Figure 8-16 IBM Web Services Navigator installation

When the installation is completed, you can launch IBM Web Services Navigatorfrom Programs → IBM Tivoli Composite Application Manager for SOA6.1.0→ IBM Web Services Navigator, or by executing runNavigator.

IBM Web Services Navigator uses a perspective in Eclipse called Web ServicesProfiling perspective. For more information about Eclipse and perspective usagein Eclipse, refer to http://www.eclipse.org.

The initial page when starting IBM Web Services Navigator is the task assistantpage to guide you through the use of the navigator (Figure 8-17).





Figure 8-17 Initial help window for IBM Web Services Navigator





You can exit from this help window using the restore tool and resize the helpwindow. Figure 8-18 shows an empty Eclipse workspace with the Web ServicesProfiling perspective.

Figure 8-18 Empty IBM Web Services Navigator

8.3 ITCAM for SOA usage scenarios

Metrics are gathered from the monitored Web services messages. Use of ITCAMfor SOA is discussed in the following sections:

8.3.1, “Monitoring Web services calls” on page 317 8.3.2, “Filtering Web services calls” on page 321 8.3.3, “Using workflow” on page 325 8.3.4, “Using IBM Web Services Navigator” on page 325

8.3.1 Monitoring Web services calls

The workspace of ITCAM for SOA (Figure 8-19 shows the default) in the TivoliEnterprise Portal is arranged to show Web services calls by servers. The Webservices calls are typically identified by the following attributes:

Frequency Response time Message length




Message length


Figure 8-19 Primary workspace for ITCAM for SOA

The workspace in Figure 8-19 on page 318 displays the primary metrics that arecollected by ITCAM for SOA. It shows all active Web services calls in theduration. In our Trader application, we have three Web modules, each oneaccessing DB2, CICS, and IMS. Each Web module serves four Web servicescalls: getCompanies, getQuote, buy, and sell.





In the performance summary display shown in Figure 8-20, the detailedinformation of the Web services call performance are shown in a table, along witha response time summary chart.


The message summary page in Figure 8-21 shows the message statistics. Thisis typically useful to assess the network capacity requirement for the Webservices, as it shows both the length and the number of messages for the server.






From a different branch, the message arrival rate is shown in Figure 8-22. Thisshows the activity of the server in general.






8.3.2 Filtering Web services calls

Web services calls can be rejected by ITCAM for SOA. This is provided as part ofthe default take action method in the IBM Tivoli Monitoring V6.1 environment.

See , “Actions” on page 295 for descriptions of the take action methods.

These actions can be invoked manually or triggered by a situation. This sectiondemonstrates invoking the take action method manually to reject a certain Webservices call.





It makes sense to invoke the filtering action from the Message Arrival table orfrom the Message Summary table when you see a lot of unexpected messagesflowing through. You can invoke the action using the context menu, as shown inFigure 8-23.

Figure 8-23 Invoking action

We invoke the addFltrCntrl action. This action requires a set of parameters as

shown in Figure 8-24. Depending on where you initiate the take action you canget pre-filled data for these arguments.

Figure 8-24 Action parameter





After the action has been completed, you can see the effective setting in theService Management Agent workspace as shown in Figure 8-25.

Figure 8-25 Rejected Web services call

The rejected Web services calls would show up as fault in the fault summary list.Figure 8-26 on page 324 shows the fault list.





Figure 8-26 Rejected Web services call faults

You can remove the filter using the DelFltrCntrl action as shown in Figure 8-27.This is invoked from the filter list table in Figure 8-25 on page 323 directly, that’swhy the arguments are automatically filled.

Figure 8-27 Removing filter





8.3.3 Using workflow

ITCAM for SOA provides a sample workflow for your customization. Figure 8-28 shows the workflow that is provided for ITCAM for SOA. (By default, this workflow

is not started.)

Figure 8-28 Workflow for ITCAM for SOA

The sample workflow uses MessageArrivalCritical and MessageArrivalClearingsituations. This workflow is automatically started. When the Message Arrivalapproaches a critical threshold, a call filtering is performed for the source IPaddress. The workflow restores the access when the message arrival rate dropsbelow the threshold.

This workflow is useful for detecting a Denial of Service (DoS) attack to Webservices systems.

8.3.4 Using IBM Web Services NavigatorThis section demonstrates the IBM Web Services Navigator to explore our Webservices environment. Web services information can be retrieved from the Tivoli





Data Warehouse V2.1 database or from a merged log using the Log Assemblertool. We will illustrate both processes.

Using the warehouse dataBefore you can work with the historical data from ITCAM for SOA, you mustconfigure a connection from IBM Web Services Navigator to Tivoli DataWarehouse V2.1 database. We are using DB2 UDB database as the warehouse.The configuration for historical data collection should have been performed asdiscussed in 8.2.5, “Configuring warehouse proxy” on page 310.

1. Create a new connection by right-clicking in the Database Explorer view andselecting New Connection as shown in Figure 8-29.

Figure 8-29 Creating new connection





2. The new connection dialog appears. The Choose a DB2 Alias option enablesyou to select from the local database alias. This is typically not a viable optionas the warehouse would typically not reside on the same machine as the IBMWeb Services Navigator. We select Choose Database Manager and JDBC

driver and call the connection WAREHOUS as shown in Figure 8-30.

Figure 8-30 New connection





3. The new connection property dialog (Figure 8-31) includes the databaseinformation and user access information for the Tivoli Data Warehouse. ClickTest Connection to ensure that you can connect to the warehouse database.

Figure 8-31 WAREHOUS database information





Once we connect the warehouse database, we can start working with the IBMWeb Services Navigator. Follow this procedure:

1. Create a new project by selecting File→ New→ Project. The new project

type should be Simple (Figure 8-32).

Figure 8-32 Defining a new project





2. Within the project, you can import the ITCAM for SOA data using the menuFile→ Import and choosing ITCAM for SOA data as shown in Figure 8-33.

Figure 8-33 Importing ITCAM for SOA data





3. The data import wizard asks about the target workspace and time range tocollect (Figure 8-34). The time range that you specify here must be convertedto UTC. You can then specify the database connection. We use an existingconnection that we have defined.

Figure 8-34 Import dialogs

Note: The tables that must exist in the warehouse for the IBM Web ServicesNavigator can be viewed with the db2 list table command if you areconnected as the warehouse user to the warehouse database.

Services_Inventory ITMUSER T 2005-11-23-16.28.03.687001Services_Message_Metric ITMUSER T 2005-11-23-18.28.04.640001

Also, depending on the transaction volume and mix that you have, you maywant to restrict data collection to a smaller time frame to make the result more

readable. If you put an invalid value in the date range, the Next button isdisabled and not returned to enabled unless you cancel and restart the import.





4. Figure 8-35 shows the Service Topology view of our environment.

Service topology shows the Web services providers and transactions in ourenvironment. It also shows the mix of clients that call each service. Our

environment has a dedicated client, laredo, that issues all Web services calls.Laredo is the front-end WebSphere Application Server that the end userconnects to, and it issues all of the Web services calls.

Figure 8-35 Service topology

Note: Other views of the Web Services Navigator will be discussed in the nextsection “Using the log assembler tool” on page 333.





Using the log assembler toolWith the log assembler tool, you can specify the nature of transactions that youwant to analyze. The data collection is performed using the monitor controlaction. The monitor control action are:

AddMntrCntrl adding new control UpdMntrCntrl updating existing control DelMntrCntrl deleting existing control

By default, each data collector has a global definition of no monitor controllogging for all Web services call. Individual control can be specified by:

Service port namespace Service port Operation namespace Operation

We decided to add monitor control for individual service port for our Webservices, those are TraderDBServices, TraderIMSServices andTraderCICSServices. Figure 8-36 on page 333 shows the action invocation forTraderIMSServices.

Figure 8-36 Monitor control action

The resulting control can be seen in the Service Management Agent workspace.Figure 8-37 on page 334 shows the monitor list.

Note: Two important items:

The ports here are not TCP/IP ports, these are port definition in wsdl file. The global definition with all arguments are wildcards existed, you must

use UpdMntrCntrl to change this.





Figure 8-37 Monitor list

This monitor control specification would generate the metric log and content logfiles in the $ITMhome\TMAITM6\KD4\logs.

The content log would be stored for each data collector, each content log filecan goes up to 500 MB in size. The file name of the content log is in theformat of:

KD4.<env>..<cell>.<node>.<server>.content.log

There would be multiple metric log files. The metric logs are stored in eitherthe KD4.DCA.CACHE or KD4.DCA.CACHE\archive sub directory of the logsdirectory. These files has the name of:

KD4.<env>..<cell>.<node>.<server>.metric.log.<timestamp>

You must select the appropriate content logs and metric logs and collects them tothe machine on which you install the Web Services Navigator. The log assemblertool is installed with the Web Services Navigator. The log assembler wouldprocess and merge each metric log, while retrieving the message content fromthe content log file. The result would then be a single merged metric log file frommultiple servers, each with their own message contents attached.

The easiest way to process these logs is using a batch file as the file names arelong and you have to invoke the command multiple times. In our tests that weinvoke 108 Web services calls within 3 minutes on 2 application servers, thisgave us 28 metric log files and 2 content log files. Our log files are shown inFigure 8-38 on page 335.





Figure 8-38 Log files

We use the batch file in Example 8-3 to process these log files.

Example 8-3 Running log assembler SET TOOLPATH="C:\IBM\ITCAM for SOA 6.1.0\Tools"SET LOGAJAR=com.ibm.websightView.LogAssembler.jarcd \soalogs

for %%i in (*.ClientSvc.metric.log.*) do %toolpath%\_jvm\jre\bin\java-cp %toolpath%\lib\%logajar%;%toolpath%\lib\jlog.jar -jar%toolpath%\lib\%logajar% 0 a soa.Merged.log C:\soalogs\%%iC:\soalogs\KD4.1..PERTHCell01.PERTHNode01.ClientSvc.content.log

for %%i in (*.ServerSvc.metric.log.*) do %toolpath%\_jvm\jre\bin\java-cp %toolpath%\lib\%logajar%;%toolpath%\lib\jlog.jar -jar%toolpath%\lib\%logajar% 0 a soa.Merged.log C:\soalogs\%%iC:\soalogs\KD4.1..PERTHCell01.PERTHNode01.ServerSvc.content.log





Note that from Example 8-3 on page 335:

The log assembler must be invoked separately for each servers, the metriclog for ClientSvc must be processed with the content log for ClientSvc, you

cannot combine the processing. The log assembler uses 2 jar files, the LogAssembler.jar and jlog.jar.

The arguments of the command are:

logging level 0, 1 or 2; non zero values generates a lot of outputprocessing o or a; represent overwrite or append to the log filestarget log file name This is the merged log file namemetric log file name The metric log that you want to be processedcontent log files The content log files for a single server

We now ready to import the log file into Web Services Navigator.

1. First, we need an empty project (or an existing one) to store the imported logfile definitions. We perform File→ New→ Project, we create a simpleproject. See Figure 8-39.

Figure 8-39 Creating a project





2. We then import the log file. Use File→ Import menu and select from the filesystem the merged log from the log assembler tool. Figure 8-40 shows theimport process.

Figure 8-40 Importing log files

In Figure 8-40, note that we experimeted with the log files. We have individual

server log files and the merged log files. The individual server log files doesnot generate a full picture of the Web Services calls. The next discussionwould only cover the merged log file.

3. We have the service topology view of the merge log shown in Figure 8-41 onpage 338.





Figure 8-41 Service topology

In Figure 8-41, the figure shows the calling pattern of the Web Services. Thegreen boxes indicate the service name and the operations are listed within it.The arrows indicate service calls with numbers showing the number ofinvocation. You can also summarize the calls based on services name insteadof the operation by collapsing the boxes as shown in Figure 8-42 onpage 338.

Figure 8-42 Operation summary





4. Figure 8-43 shows the transaction flows. It shows the timeline of WebServices calling sequences. The busy chart shows all 108 Web Services callsthat we made.

Figure 8-43 Flow patterns

Hovering the cursor over any of those lines would gave the call details of theWeb Service. Selecting the service would shown in yellow highlighting anddisplays the detail in the bottom pane. See Figure 8-44 on page 340.





Figure 8-44 Message content

5. The flow pattern would summarize the transaction flows in Figure 8-43 onpage 339 and collapse any similar invocation pattern. A pattern can beidentified by the requestor, provider, service name and operation name. Theflow pattern is shown in Figure 8-45.





Figure 8-45 Flow patterns




© C i h IBM C All i h d 343

Draft Document for Review March 1, 2007 5:22 pm 7151ch15-zos-implementation.fm

Chapter 9. Implementation of ITCAMproducts on z/OS

This chapter describes the implementation of IBM Tivoli Composite ApplicationManager specifics for z/OS. We specifically feel that z/OS implementation tasksare typically performed separately from the distributed components, thereforethis chapter is aimed directly for z/OS implementer. The discussion includes:

9.1, “Implementation overview” on page 344

9.2, “The CYN1 subsystem” on page 345

9.3, “ITCAM for WebSphere data collector” on page 348

9.4, “ITCAM for Response Time Tracking agent” on page 358

9.5, “ITCAM for CICS Transactions” on page 370

9.6, “ITCAM for IMS Transactions” on page 373

9.7, “ITCAM for SOA management agent for z/OS” on page 377

9




7151ch15-zos-implementation.fm Draft Document for Review March 1, 2007 5:22 pm

344 IBM Ti oli Composite Application Manager V6 1 Famil Installation Config ration and Basic Usage

9.1 Implementation overview

This chapter contains the overall implementation procedure for all IBM Tivoli

Composite Application Manager family products for z/OS.

This section provides an overview of the components of ITCAM products that areinstalled in z/OS. Figure 9-1 on page 344 shows the complete configuration ofagents and components in each subsystem and started task.

Figure 9-1 z/OS overview

From Figure 9-1, the interaction agents is as follows:

The CYN1 subsystem runs to collect information related to WorkloadManager (WLM) and System Measurement Facility (SMF). ITCAM forWebSphere, ITCAM for CICS Transactions and ITCAM for IMS Transactionsdata collectors retrieves information from the CYN1 subsystem. The

z/OS operating system

WebSphere Application

Server

IMSCICS

WAS DCor

RTT J2EE

CICS

DC

IMSDC

RTTMA

KD4

CYN1

Tivoli

Enterprise

Monitoring

Server

ITCAM for

WebSphere

Managing

Server

ITCAM for

RTT

Management

Server




Chapter 9 Implementation of ITCAM products on z/OS 345


implementation process is discussed in 9.2, “The CYN1 subsystem” onpage 345.

The WebSphere data collector from ITCAM for WebSphere providesappropriate mechanism to collect WebSphere Application Server on z/OStransaction performance. The WebSphere Application Server data collector isdiscussed in 9.3, “ITCAM for WebSphere data collector” on page 348.

ITCAM for Response Time Tracking provides a management agent for z/OS.This management agent primarily resides in UNIX System Services. Theagent consists of the ARM agent and the management agent process, similarto the distributed implementation. WebSphere monitoring is acquired from theJ2EE monitoring component. Installation and configuration are provided in“ITCAM for Response Time Tracking agent” on page 358.

ITCAM for CICS Transactions and ITCAM for IMS Transactions provides datacollector mechanism for both ITCAM for Response Time Tracking and ITCAMfor WebSphere. They communicate directly to ITCAM for WebSpheremanaging server, while for ITCAM for Response Time Tracking they feed themanagement agent for performance data. Discussion of ITCAM for CICSTransactions and ITCAM for IMS Transactions are provided in 9.5, “ITCAM forCICS Transactions” on page 370 and 9.6, “ITCAM for IMS Transactions” onpage 373.

ITCAM for SOA data collector, KD4, resides in WebSphere Application ServerJAX-RPC handler. It collects Web Services performance and statisticsinformation. This is discussed in 9.7, “ITCAM for SOA management agent forz/OS” on page 377.

9.2 The CYN1 subsystem

The CYN1 subsystem can be used for ITCAM for WebSphere, ITCAM for CICSTransactions and ITCAM for IMS Transactions on z/OS. It provides the interfaceto SMF and z/OS-related information, such as CPU and memory usage.TheCYN1 subsystem uses address space storage to store SMF informationcollected from the various WebSphere for z/OS Application Server instancesrunning in the same LPAR. SMF statistics comprise server and container data,bean data, bean method data, web application data, and servlet data. Thesedata are collected from SMF records 120 and reside in the CYN1 address spaceaccording to a hierarchical structure with the server instance as the top level.Memory for such a structure is pre-allocated by the CYN1 address space when itcomes up according to a pre-defined parameter template, which specifies themaximum number of server instances, the sizes of the bean section, beanmethod section, web application section, and servlet section pools.



Chapter 9. Implementation of ITCAM products on z/OS 345


346 IBM Tivoli Composite Application Manager V6 1 Family Installation Configuration and Basic Usage

ITCAM for CICS Transactions, ITCAM for IMS Transactions, and ITCAM forWebSphere data collector on z/OS use for each runtime instance a uniquecomposite identification token for tracking transaction correlation. The CYN1subsystem is useful to collect additional information related to Workload

Manager (WLM) and System Measurement Facility (SMF). Therefore the CYN1subsystem should be implemented for z/OS systems running a data collector, asit provides a composite application token for the z/OS application.

To define the CYN1 subsystem on z/OS, you must perform several tasks:

9.2.1, “CYN1 subsystem definition” on page 346 9.2.2, “Assigning RACF user ID for CYN1PROC” on page 346 9.2.3, “Started task creation” on page 347 9.2.4, “Authorizing SCYNAUTH” on page 347 9.2.5, “SMF customization” on page 347

9.2.1 CYN1 subsystem definition

Subsystem definition is performed by updating the SYS1.PARMLIB(IEFSSNxx).You must include the following statement:

SUBSYS SUBNAME(CYN1)

The update in IEFSSNxx takes effect with the next IPL of the system and will bepermanent. You can dynamically add a subsystem using this console command:

SETSSI ADD,SUBNAME=CYN1

9.2.2 Assigning RACF user ID for CYN1PROC

Installations have a significant number of options they can choose to enablestarted tasks and authorize them with RACF. A started task should have anRACF association with a user ID or a group in the started task table ICHRIN03 or

using the STARTED class. To associate the CYN1 subsystem procedure(CYN1PROC) to the appropriate user ID STC, you can issue the following RACFcommand:

RDEF STARTED (CYN1*.*) STDATA(USER(STCRACF))

As the STARTED class is typically cached using the RACLIST option, you mayhave to refresh the cached started task information using the command:

SETROPTS REFRESH RACLIST(STARTED)

The user ID associated with the started tasks must have RACF access to theITCAM for WebSphere libraries.






9.2.3 Started task creation

Copy the member CYN1PROC from the library dataset SCYNPROC into thesystem procedure library, typically SYS1.PROCLIB. You can apply this member

to any dataset listed in the PROC00 DD statement of the JES2 started task.

9.2.4 Authorizing SCYNAUTH

The SCYNAUTH data set must be APF authorized and concatenated to thesystem link list. A link list is a cached system search area for executable moduleson z/OS.

To authorize a library, you can update either the IEAAPFxx or PROGxx data set

according to your installation requirement. You can also dynamically assign adata set to be APF authorized using the console command similar to this:

SETPROG APF,ADD,DSN=ITCAM.V6R1.SCYNAUTH,VOL=ITCAM1

To add SCYNAUTH to the link list, you can update the LNKLSTxx or PROGxxand include the data set. You can also issue the following commands todynamically add the data sets to the link list concatenation:

SETPROG LNKLST,DEFINE,NAME=ITCAMLST,COPYFROM=CURRENTSETPROG LNKLST,ADD,NAME=ITCAMLST,DSN=ITCAM.V6R1.SCYNAUTH

SETPROG LNKLST,ACTIVATE,NAME=ITCAMLST

9.2.5 SMF customization

The SMF exit IEFU83 of ITCAM for WebSphere must be installed as a systemexit module. This can be placed in the PROGxx member using the definitionshown in Example 9-1.

Example 9-1 Defining IEFU83

EXIT ADD EXITNAME(SYS.IEFU83)MODNAME(CYN1FU83)DSNAME(ITCAM.V6R1.SCYNAUTH)FIRST

EXIT ADD EXITNAME(SYSSTC.IEFU83)MODNAME(CYN1FU83)DSNAME(ITCAM.V6R1.SCYNAUTH)FIRST

These can also be performed dynamically using console commands:

SETPROG EXIT,ADD,EX=SYS.IEFU83,MOD=CYN1FU83,DSN=ITCAM.V6R1.SCYNAUTH,FIRSTSETPROG EXIT,ADD,EX=SYSSTC.IEFU83,MOD=CYN1FU83,DSN=ITCAM.V6R1.SCYNAUTH,FIRST



C ap e 9 p e e a o o C p oduc s o /OS 3



The IEFU83 exit must be then associated with SMF record 120 and record it.This is performed from the SYS1.PARMLIB(SMFPRMxx). Example 9-2 shows anexample of an entry to enable an IEFU83 exit and recording of SMF type 120.

Example 9-2 Defining SMF exit

SYS(TYPE(120), EXITS(IEFU83))SUBSYS(STC,EXITS(IEFU83))

9.3 ITCAM for WebSphere data collector

This section describes installation and configuration of ITCAM for WebSpheredata collector for WebSphere Application Server on z/OS. The stepsdocumented in this section take place after SMP/E installation. We assume thatyou finished SMP/E processing for those components successfully.

The installation for ITCAM for WebSphere on z/OS is performed using SMP/Ewith FMID HAAD610. The following UNIX System Services file systems shouldbe available:

/usr/lpp/itcam (main product file system, SMP/E maintained) /etc/ibm/tivoli/cfg/ (configuration files) /var/itcam61 (runtime configuration directory) /var/ibm/tivoli/common/CYN (Tivoli common log files)

We configured and customized ITCAM for WebSphere data collector onWebSphere Application Server on z/OS based on instructions in the IBM Tivoli Composite Application Manager for WebSphere Installation and Customization

Guide , GC32-9506.

An overview of the implementation tasks includes:

1. Define CYN1 subsystem to z/OS, which is an optional task described in 9.2,“The CYN1 subsystem” on page 345.

2. Generate the runtime environment in UNIX System Services (USS). Youneed to modify some files here to further tailor the data collector execution.See 9.3.1, “Modifying WebSphere started tasks” on page 349.

Note: The SMF exit definition shown in Example 9-2 on page 348 is theminimum definition. Your installation most likely will have much more of theSMF record type being captured and more exits being defined. Consult SMFdocumentation for details about how to update the SMF parameter.



p pp g y g g



3. Modify WebSphere Application Server parameters using the Administrationconsole in case of failures. See 9.3.2, “Defining the data collector toWebSphere Application Server” on page 349.

4. Finally if you have some problem, see 9.3.3, “Problem determination and log

files” on page 355.

9.3.1 Modifying WebSphere started tasks

WebSphere Application Server on z/OS consists of multiple address spacesincluding:

WebSphere daemon address space WebSphere manager address space

Control address space Servant address space

Each application server environment typically consists of a control addressspace and a dynamic number of servant address spaces that can be started ondemand as needed. ITCAM for WebSphere is implemented in each applicationserver environment. It requires modification to the servant address space byadding the statement HEAP(,,,FREE) in the started task as shown for ourenvironment in Example 9-3.

Example 9-3 Adding HEAP parameter for servant address space

//BBO5ASR PROC ENV = ADCDPL.P390.SERVER1,Z=BBO5ASRZ// SET ROOT=’/wasitconfig/itcell/itnodea’//BBOSR EXEC PGM=BBOSR,REGION=0M,TIME=NOLIMIT,//PARM=’TRAP(ON,NOSPIE),HEAP(,,,FREE),ENVAR("_EDC_UMASK_DFLT=007")/"//BBOENV DD PATH=’&ROOT/&ENV/was.env’// INCLUDE MEMBER=&Z

9.3.2 Defining the data collector to WebSphere Application Server

The data collector is installed as a WebSphere Application Server customservice. It will be started in the Java Virtual Machine (JVM).

You may have multiple distinct server instances under a common node, or youmay have multiple cells in a single z/OS image, or you may share the binary forall the images in the SYSPLEX. In version 6.1, all runtime configuration areplaced in a user-maintained directory, such as /var/itcam61. Multiple applicationserver instances would create different sub-directories in this path.

All ITCAM 6.1 data collectors can share the same configuration home.





Run the createcfg.sh script in the data collector base home directory /usr/lpp/itcam/WebSphere/DC/bin. The script creates a runtime configurationdirectory, separating your typical SMP/E-maintained libraries. You only needto run this script once. Our runtime environment is created in directory

/var/itcam61/websphere/DC/runtime. Generate runtime environments in UNIX System Services. ITCAM for

WebSphere generates a runtime directory based on the WebSphereApplication Server Name. This can be performed using the setupwas.shcommand. Example 9-4 shows our setup. This script is provided in the datacollector base home directory /usr/lpp/itcam/WebSphere/DC/bin. Theconfiguration program automatically updates datacollector.properties andenvironment files.

The script integrate optional the support for WebSphere MQ and IMS. Ifrequested, the appropriate resource adapters must be installed already in theWebSphere Application Server environment. In our test case, we don’t usethem.

Example 9-4 Running setupwas.sh

TIVO01:/usr/lpp/itcam/WebSphere/DC/bin: >./setupwas.sh

ITCAM 6.1 for WebSphere Application Server

Data Collector Configuration

Enter the path of the WAS user install root [/u/WAS510]:/SC67/wasitconfig/itcell/itnodea/AppServer/binSearching for wsadmin.sh. Please wait...Found wsadmin.sh in the following locations:

1) /SC67/wasitconfig/itcell/itnodea/AppServer/bin/wsadmin.sh

Using wsadmin: /SC67/wasitconfig/itcell/itnodea/AppServer/bin/wsadmin.shChecking Websphere Application Server version...

The history xml file does not exist.Found WAS Version 6.1.0.2 NDSearching for Application ServersThis may take some time. Please wait...WASX7209I: Connected to process ’dmgr’ on node itdmnode using SOAP connector;The type of process is: Deployment Manager

WASX7303I: The following options are passed to the scripting environment andare available as arguments that are stored in the argv variable:’[/tmp/am_setupwas67961453.a]’

Found the following servers:

1)itsr01a(cells/itcell/nodes/itnodea/servers/itsr01a|server.xml#Server_1161372225374)





ITCAM configuration /usr/lpp/itcam/WebSphere/DC/runtime/was61.itnodea.itsr01aalready exists. Overwrite? (y|n):

y+----------------------------------------------------------------++Which data collection agents(s) would you like to configure?+Select all that apply.+----------------------------------------------------------------+

+----------------------------------------------------------------+|Data collection for ITCAM for WebSphere and J2EE's Tivoli Enterprise|Portal Interface requires a separate installation of ITCAM|for WebSphere's Tivoli Enterprise Monitoring Agents+----------------------------------------------------------------+Configure data collection for ITCAM for WebSphere and J2EE's

Tivoli Enterprise Portal Interface?(y|n): yEnter the IP address of the TEMA agent[127.0.0.1]:127.0.0.1Enter the port number of the TEMA agent[63335]:63335+----------------------------------------------------------------+|Data collection for ITCAM for WebSphere and J2EE's Application Monitor|Interface requires a separate installation of ITCAM for|WebSphere's Managing Server.

+----------------------------------------------------------------+Configure data collection for ITCAM for WebSphere and J2EE Application MonitorInterface? (y|n):

y Enter the IP address of the ITCAM Managing Server:peoria.itsc.austin.ibm.comEnter ITCAM Managing Server install directory: [/opt/IBM/itcam/WebSphere/MS]:/opt/IBM/itcam/WebSphere/MSEnter the MS Codebase Port [9122]:9122

Do you wish to configure data collection for IMS Connect for Java? (y|n):nDo you wish to configure data collection for WebSphere MQ JMS Provider? (y|n):n Setup will create an ITCAM runtime with the following parameters:

1) WAS server name: itsr01a2) ITCAM for Tivoli Enterprise Portal Interface: Yes

TEMA Host : 127.0.0.1TEMA Port : 63335Monitor GC :

3) ITCAM for Tivoli Application Monitor Interface: YesITCAM MS host : peoria.itsc.austin.ibm.comITCAM MS home : /opt/IBM/itcam/WebSphere/MSCodebase port :9122





Collect SMF data: No4) IMS Connect for Java support :No5) WebSphere MQ :No

Enter item number to modify, 'y' to accept, or 'n' to cancel: yITCAM configuration for itsr01a created in/usr/lpp/itcam/WebSphere/DC/runtime/was61.itnodea.itsr01aCreating plugin directory/SC67/wasitconfig/itcell/itnodea/AppServer/plugins/itcam_6.1.0Creating plugin directory/SC67/wasitconfig/itcell/itnodea/AppServer/plugins/itcamsib_6.1.0Creating plugin directory/SC67/wasitconfig/itcell/itnodea/AppServer/plugins/itcammqjms_6.1.0

Reinitializing plugins...Configure WebSphere Application Server itsr01a? (y|n): yConfiguring Application Server. This may take some time. please wait...

WASX7209I: Connected to process ’dmgr’ on node itdmnode using SOAP connector;The type of process is: DeploymentManagerWASX7303I: The following options are passed to the scripting environment andare available as arguments that are stored in the argv variable:’[/usr/lpp/itcam/WebSphere/DC/runtime/was61.itnodea.itsr01a/input.txt]’

server.platform=z/OSserver.id=itsr01a(cells/itcell/nodes/itnodea/servers/itsr01a|server.xml#Server_1161372225374)

. . .

Server major version is 61.INFO: Configuring for z/OSINFO: Configuring AdminService

. . .

INFO: Start setting attributes foritsr01a(cells/itcell/nodes/itnodea/servers/itsr01a|server.xml#Server_1161372225374)INFO: Configuring JVM Args and SystemPropertiesModify JVM command line arguments

. . .

INFO: Configuring Environment VariablesCreate/Modify java process environments





create new environmentLIBPATH=/usr/lpp/itcam/WebSphere/DC/runtime/was61.itnodea.itsr01a/lib:${ITCAM61HOME}/toolkit/libcreate new environment NLSPATH=${ITCAM61HOME}/toolkit/msg/%L/%N.catcreate new environment JITC_COMPILEOPT=NALLINFO: Configuring CustomServiceignore externalConfigURL=amConfigure custom service (am)INFO: Configuring PmiServicemodify PMI service to {enable true} {statisticSet extended}

. . .

INFO: Configuring variable protocol_iiop_propagate_unknown_service_ctxs

create new variable protocol_iiop_propagate_unknown_service_ctxsINFO: Configuring variable AM_HOMEcreate new variable AM_HOMEINFO: Configuring variable MS_AM_HOMEcreate new variable MS_AM_HOMEINFO: Configuring variable ITCAM61HOMEcreate new variable ITCAM61HOMEINFO: Dsabling SMF data collectionINFO: Configuring Control Region system propertiesCreate/Modify JVM system properties

newProperty={name protocol_http_timeout_output_recovery} {value SESSION}create new property protocol_http_timeout_output_recoveryWAS_PROPS_DIR=/wasitconfig/itcell/itdmnode/DeploymentManager/profiles/default/propertiesSynchronizing with node itnodeaSynchronization completed successfully on itnodeaSuccessfully configured data collector for serveritsr01a(cells/itcell/nodes/itnodea/servers/itsr01a|server.xml#Server_1161372225374)

The setupwas.sh defines a separate directory structure beneath the runtimeconfiguration path. Our servant application server is called itsr01a; therefore, theruntime environment is created under

/var/itcam61/websphere/DC/runtime/was61.itnodea.itsr01a, as shown inFigure 9-2.





Figure 9-2 J2EE data collector runtime configuration directory

When the setup and configuration is done, you must restart the applicationserver servant started tasks. The data collector is then show up in theUnconfigured data collectors from the ITCAM for WebSphere Web console asdisplayed in Figure 9-3.

Figure 9-3 ITCAM for WebSphere unconfigured data collectors

TIVO01:/SC67/var/itcam61/websphere/DC/runtime/was61.itnodea.itsr01a: >ls -ltotal 2208drwxr-xr-x 2 ASSR1 WSSR1 Oct 23 custom-rw-r--r-- 1 ASSR1 WSSR1 Oct 23 cyn-cclog.properties-rwxr-xr-x 1 ASSR1 WSSR1 Oct 23 cynlogging.properties-rw-r--r-- 1 ASSR1 WSSR1 Oct 23 datacollector.policy-rw-r--r-- 1 ASSR1 WSSR1 Oct 23 datacollector.policy.asc-rw-r----- 1 ASSR1 WSSR1 Oct 24 datacollector.properties-rw-r--r-- 1 ASSR1 WSSR1 Oct 23 input.properties-rw-r--r-- 1 ASSR1 WSSR1 Oct 23 input.txt-rw-rw---- 1 ASSR1 WSSR1 Nov 1 itnodea.itsr01a.0.gls.properties-rw-rw---- 1 ASSR1 WSSR1 Nov 1 itnodea.itsr01a.0.parser.xml-rw-r----- 1 ASSR1 WSSR1 Oct 24 itnodea.itsr01a.cyaneaGpsCounter.txt

-rw-r----- 1 ASSR1 WSSR1 Oct 23 jiti.propertiesdrwxr-xr-x 2 ASSR1 WSSR1 Oct 23 libdrwxr-xr-x 2 ASSR1 WSSR1 Oct 23 logs-rw-r----- 1 ASSR1 WSSR1 Nov 1 was61.itnodea.itsr01a.classinfo.data-rw-r----- 1 ASSR1 WSSR1 Oct 24was61.itnodea.itsr01a.datacollector.properties-rw-rw---- 1 ASSR1 WSSR1 Nov 1 was61.itnodea.itsr01a.id-rw-r----- 1 ASSR1 WSSR1 Oct 24 was61.itnodea.itsr01a.kwjdc.properties-rw-r----- 1 ASSR1 WSSR1 Nov 1 was61.itnodea.itsr01a.requestaggregator.xml-rw-r----- 1 ASSR1 WSSR1 Nov 1 was61.itnodea.itsr01a.toolkit.properties

-rw-r----- 1 ASSR1 WSSR1 Nov 1 was61.itnodea.itsr01a.toolkit.xml





Further configuration and usage would be similar to non-z/OS WebSphereapplication server as discussed in Chapter 2, “ITCAM for WebSphere andITCAM for J2EE concepts and installation” on page 13 and Chapter 3, “ITCAMfor WebSphere and ITCAM for J2EE usage” on page 61.


Apart from the main runtime directory, ITCAM for WebSphere uses the Tivolicommon directory to store its logs. You must allocate a generous amount ofspace for this common directory as it potentially grows quite large for problemdetermination. We create a separate Hierarchical File System (HFS) under

/var/ibm with the primary allocation size of 500 MB and 100 MB secondary. ThisTivoli common directory is used to store logs and First Failure Data Collector

(FFDC) information.

For problem determination, there are several location to check:

The datacollector.properties for the application server itsr01a provides thenecessary configuration data for the connection to the management server.For problem determination check the settings in datacollector.properties.Remember that there is a datacollector.properties prefixed by the WebSphereinstance name.

Since most of the WebSphere Application Server configuration are performedautomatically using the setupwas.sh, some verification from theadministration console can be performed to ensure all updates are in theWebSphere environment. These updates include:

– Definition of WebSphere Application Server’s JVM parameters– Definition of the custom service itself

WebSphere Application Server JVM parameters.

JVM parameters must be defined for the Servant region. From the Administrationconsole menu, select Servers→ Application Servers and select the server onwhich you are installing the data collector.

Server Infrastructure: Java and Process Management→ Process

Definition: Servant.

Additional Properties: Java Virtual Machine.

Boot Classpath ${ITCAM61HOME}/toolkit/lib/bcm-bootstrap.jar:$%ITCAM61HOME}/itcamdc/lib/ppe.probe-bootstrap.j

ar

Generic JVM arguments

-Djlog.propertyFileDir.CYN=${ITCAM61HOME}/toolkit /etc





-Dcom.ibm.tivoli.jiti.config=${ITCAM61HOME}/toolkit/etc/config.properties

Initial Heap size 256

Maximum Heap size at least 512

Custom properties for the Servant process

For the custom service are some customer properties required, seeFigure 9-4.

Figure 9-4 Custom Properties for Servant address space JVM





java.security.policy: /usr/lpp/itcam/WebSphere/DC/runtime/was61.itnodea.itsr01a/datacollector.policy

am.home: /usr/lpp/itcam/WebSphere/DC/itcamdc

com.ibm.tivoli.jiti.injector.ProbeInjectorManagerChain.primaryInjectorFi

le: j /usr/lpp/itcam/WebSphere/DC/runtime/was61.itnodea.itsr01a/jiti.properties

Environment entries for the Servant address space:

LIBPATH

/var/itcam61/WebSphere/DC/runtime/was61.itnodea.itsr01a/lib:${ITCAM61HOME}/toolkit/lib

Message catalog for the Servant process:

NLSPATH

/usr/lib/nls/msg/%L/%N:${ITCAM61HOME}/toolkit/msg/%L/%N.cat

Probe services definitionFrom the Administration console menu, select Servers→ Application Servers

and choose the server on which you are installing the data collector. In theServer Infrastructure→ Administration, select Custom Services. One entryfor the ITCAM for WebSphere data collector must be exist. Otherwise, click New to create a new custom service. The new service will have the display name ofam, as shown in Figure 9-5.

Figure 9-5 Custom Services list

The setting of values for the custom service are provided as follows:

Enable service at server startupactivated

Classname com.cynea.ws6.ITCAMNotifierCustomService





Display Name am

Description Probe Service

Classpath ${ITCAM61HOME}/itcamdc/lib/ppe.probe-bootstrap.jar

The configuration example is shown in Figure 9-6.

Figure 9-6 Probe service setting

Save the setting by clicking the Save link and Save to master configuration with the Synchronize with node option checked.

9.4 ITCAM for Response Time Tracking agentThis section describes how to install and configure ITCAM for Response TimeTracking agents on z/OS, which can communicate with ITCAM for CICSTransactions data collector and ITCAM for IMS Transactions data collector. Wewill discuss some specific implementation issues with those components.





9.4.1 Implementation

The installation for ITCAM for Response Time Tracking on z/OS is performedusing SMP/E with FMID HWTP610 and HWTP61A. The following file systems

should be available: /usr/lpp/tmtp (main product file system, SMP/E maintained) /etc/tmtp (configuration files) /var/tmtp (data files) /var/ibm/tivoli/common/BWM (Tivoli common log files)

We configured the components based on the instructions in the correspondingmanuals, including IBM Tivoli Composite Application Manager for Response

Time Tracking Installation and Configuration Guide , GC32-1907. The general

configuration tasks are: RACF authorizations

– Define user TMTPAGNT and group TMTPGRP with the necessarypermissions:

• Allow access to UNIX system services.• Specify the JVM maximum address space size on user TMTPAGNT

OMVS segment, use the RACF ASSIZEMAX configuration parameter.Minimum value of 268435456 bytes is required.

• Allow access to the group for WebSphere servant address space.• Connect the WebSphere servant user to the TMTPGRP.• Allow access to the group for WebSphere runtime configuration files in

UNIX system services.• Allow access to the Tivoli configuration files /var/ibm/tivoli/common/cfg.• Assign STARTED profile to start and stop the agent.

– Prepare certificate configuration for SSL communication. In z/OS,certificates are managed from RACF.

Generating runtime environments in USS

– Ensure that /var/tmtp and /etc/tmtp are owned by TMTPAGNT andTMTPGRP with access mode of 750 or more.

– Copy prepConfig.sh and setupEnv.sh from /usr/lpp/tmtp/V6R1M0/MA/config1 to a temporary directory, and modifysetupEnv.sh to provide BASEDIR, the management agent installationdirectory, and the JAVA_HOME path, shown in Example 9-5.

Example 9-5 The setupEnv.sh #!/bin/shBASEDIR=/usr/lpp/tmtp/V6R1M0/MAexport BASEDIRJAVAHOME=/usr/lpp/java/J5.0





export JAVAHOME

# Do not change thisINTERP=zosexport INTERP

– Run prepConfig.sh to generate runtime files. This creates a new set offiles in /etc/tmtp/MA/config.

– Update zos.properties from /etc/tmtp/MA/config to include themanagement server parameters. Our zos.properties is shown inExample 9-6.

Example 9-6 Our zos.properties

## ITMTP MA for z/OS Configurable Parameters#zos.msHostName=khartoum.itsc.austin.ibm.comzos.msUserName=itcrttadmzos.msUserPassword=XXXXXXXzos.sslEnabled=falsezos.msProtocol=httpzos.msPort=9081

zos.maPort=1976zos.offline=falsezos.proxyProtocol=noproxyzos.proxyHostName=zos.proxyPortNumber=zos.epKeyStore=/etc/tmtp/MA/config/agent.jkszos.epKeyPass=changeit# uncomment to set this to full local hostname# it is discovered automatically if not setzos.maHostName=wtsc67.itso.ibm.com

Configure the Management Agent, from /etc/tmtp/MA/config:

– Run configMa.sh install as shown in Example 9-7.

Example 9-7 Configuring the management agent

TIVO01:/SC67/etc/tmtp/MA/config # ./configMa.sh installRetrieving document at '/usr/lpp/tmtp/V6R1M0/MA/wsdl//EndpointAdmin.wsdl'.Retrieving document at '/usr/lpp/tmtp/V6R1M0/MA/wsdl//AgentStatus.wsdl'.

Retrieving document at '/usr/lpp/tmtp/V6R1M0/MA/wsdl//PolicyManager.wsdl'.Retrieving document at '/usr/lpp/tmtp/V6R1M0/MA/wsdl//EventService.wsdl'.Retrieving document at '/usr/lpp/tmtp/V6R1M0/MA/wsdl//TransferController.wsdl'.Retrieving document at '/usr/lpp/tmtp/V6R1M0/MA/wsdl//BDH.wsdl'.Retrieving document at '/usr/lpp/tmtp/V6R1M0/MA/wsdl//ManagementServer.wsdl'.





Retrieving document at '/usr/lpp/tmtp/V6R1M0/MA/wsdl//EndpointGroup.wsdl'.Retrieving document at '/usr/lpp/tmtp/V6R1M0/MA/wsdl//Upgrade.wsdl'.Retrieving document at '/usr/lpp/tmtp/V6R1M0/MA/wsdl//RCA.wsdl'.Configured the management agent successfully.If you have a IBM Tivoli Composite Application Manager Data Collector

installed,datacollector.propertiesneeds to be updated for Am.tt.enable key. This key can either be editedmanuallyorthis configuration script can do it for you.Would you like this script to update the key (y/n) ?

y

– Run createArmLinks.sh as shown in Example 9-8.Example 9-8 Creating links for ARM libraries

TIVO01:/SC67/etc/tmtp/MA/config # ./createArmLinks.shThis script will create links for the ARM shared libraries in /usr/libdirectory.Do you want to continue ? [y/n]

yA link was found for the common ARM library used by both ITCAMfRTT and eWLM,/usr/lib/libarm4_31.so. If eWLM is installed on the system, do not replace it,

choose to replace otherwise. Replace ? [y/n] yDone. Links were created successfully in /usr/lib directory.

– Start the management agent by running start_tmtpd.sh.

Our completed agent installation is shown in the ITCAM for Response TimeTracking agent list as shown in Figure 9-7.





Figure 9-7 All agents installed


The tmtp management agent writes information to: Initial startup of the JVM and failure to start the JVM will be shown here:

– /etc/tmtp/MA/config/ma-stdout.log– /etc/tmtp/MA/config/ma-stderr.log

Message and trace files in the Tivoli common directory, typically under /var/ibm/tivoli/common/BWM/logs:

– msg-ma.log– msg-instr.log– trace-ma.log– trace-instr.log– trace-tapmagent.log– SystemErr.log– SystemOut.log– wsadmin.traceout– wsadmin.valout

Check the setting for variables BASEDIR, JAVAHOME in setupEnv.sh in the

configuration directory /etc/tmtp/MA/config/. Check the setting for variables zos.msHostName, zos.msUserName,

zos.msUserPassword, zos.msProtocol and zos.msPort in zos.properties inthe configuration directory /etc/tmtp/MA/config/.





Check the NETACCESS profiles in RACF to grant access for the tmtp agentlistener port.

Export the variable DEBUG_TMTP to any value to debug events on the scriptstart_tmtpd.sh.

9.4.3 J2EE monitoring component on z/OS

The J2EE monitoring component is used by ITCAM for Response Time Trackingto collect response time information from a WebSphere Application Serverenvironment. The configuration is done by deploying it using ITCAM forResponse Time Tracking Web console.

To deploy the J2EE component, select System Administration→ MonitoringComponents. Select J2EE in the Monitoring Components Table, and chooseDeploy Monitoring Component from the pull-down menu. Click Go

(Figure 9-8).

Important: Backup the configuration directory of the WebSphere ApplicationServer on which you are deploying the ITCAM for Response Time TrackingJ2EE agent. Deployment defines the JVM arguments needed for ITCAM forResponse Time Tracking J2EE arguments, which might affect some settingsfor your other JVMPI agents, such as ITCAM for WebSphere data collector.





Figure 9-8 Deploy J2EE Agent on z/OS

The deployment process can discover and deploy automatically the J2EE server,or you can specify it manually. See Figure 9-9 to choose the deployment method.We use the discover and deploy method.





.

Figure 9-9 Agent Deployment - Choose J2EE Deployment Method

You select the management agent which maintain the J2EE server and supplythe Application Server path, Profile Name (for WebSphere Application ServerV6.x), and the SOAP port of the server. See Figure 9-10 to specify the discoverycriteria.

Figure 9-10 Agent Deployment - J2EE Discovery Criteria

Note: The SOAP port can be found in JESMSGLOG of the WebSphereControl region by searching for SOAP.





The J2EE deployment process enables you to pre-discover your instances or justdeploy your monitoring component. The deployment generates a runtimeenvironment for every selected server instance. The deployment process createsseveral directories under /var/tmtp/MA/app/instrument/6101 as shown inFigure 9-11. Subsequent agent deployment creates a separate directory in

/var/tmtp/MA/app/instrument/6101/appServers/ server_name .

Figure 9-11 J2EE component directories

Our configuration parameters for the itsr01a WebSphere Application Serverprocess can be found in the

/var/tmtp/MA/app/instrument/6101/appServers/itsr01a_213/config directory.

Problem executing wsadmin scriptsIn this case, check the message and trace logfile trace-ma.log in

/var/ibm/tivoli/common/BWM/logs.

Figure 9-12 JVM initialization error with tmtp management agent

For the J2EE deployment process is not enough address space of the executingtask user for the tmtp management agent defined, as shown in.Figure 9-12. Inother cases the process is not be able to communicate with the WebSphere

Deployment Server in cause of improper setting of scripting language. Ensure the maximum JVM address space size of user TMTPAGNT. Inspect

the configuration with following arguments, as shown in Example 9-9:

TIVO01:/SC67/var/tmtp/MA/app/instrument/6101: >ls -ltotal 88-rw-rw-r-- 1 TMTPAGNT TMTPGRP 100 Oct 31 12:44 TMTPJ2EEJ050300.sysdrwxrwxr-x 3 TMTPAGNT TMTPGRP 8192 Oct 31 12:44 appServersdrwxrwxr-x 2 TMTPAGNT TMTPGRP 8192 Oct 31 14:57 bindrwxrwxr-x 3 TMTPAGNT TMTPGRP 8192 Oct 31 12:44 cli

drwxrwxr-x 3 TMTPAGNT TMTPGRP 8192 Oct 31 12:44 icdrwxrwxr-x 5 TMTPAGNT TMTPGRP 8192 Oct 31 12:44 lib

Note: If you remove the last J2EE agent from the system, all runtimedirectories under /var/tmtp/MA/app/instrument/6101 will be removed.

STDERR from jacl script, /SC67/var/ibm/tivoli/common/BWM/logs/discoverServers.jacl:

STDERR:Error: unable to allocate 268435456 bytes for GC in j9vmem_reserve _memory.JVMJ9VM015W Initialization error for library j9gc23(2): Failed to instantiate heap.256M requestedCould not create the Java virtual machine.





Example 9-9 Check the Java virtual machine setting

TMTPAGNT:/SC67/etc/tmtp/MA/config: >/usr/lpp/java/J5.0/bin/java -version -Xmx256mjava version’1.5.0’Java(TM) 2 Runtime Environment, Standard Edition (build pmz31devifx-20060524 (SR2))IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 z/OS s390-31 j9vmmz3123-20060505a (JIT

enabled)J9VM - 20060501_06428_bHdSMrJIT - 20060428_1800_r8GC - 20060501_AA)JCL - 20060524a

Check the setting for variable com.ibm.ws.scripting.defaultLang inwsadmin.properties in properties directory of the appropriate WebSphereApplication Server profile name. The value of jacl is required.

Coexistence with other JVMPI AgentsITCAM for Response Time Tracking J2EE Data Collector uses JVMPI to gatherinformation. It can coexist with other products using this interface. Tivolimaintains a list of tested products for coexistence with the ITCAM for ResponseTime Tracking J2EE component. During deployment, a jvmpiagents.propertiesfile is created containing the list of tested products. All products defined assupported are fully deployed, meaning that the runtime files are generated andthe JVM arguments are defined.

The deployment process checks whether other JVMPI agents are defined in thegeneric JVM arguments and compares them with the allowed entries in

jvmpiagents.properties. This includes instrumentation for ITCAM for WebSphere.Figure 9-13 on page 368 shows an excerpt of our jvmpiagents.properties from

/var/tmtp/MA/app/instrument/6101/lib.





Figure 9-13 Example of jvmpiagents.properties

## Supported JVMPI Profiler Agents#

# Cyanea WSAM 2.1.4/3.1supported.wsam31=-Xruncyanea## Cyanea WSAM 3.2/ITCAMfJ2EE 6.0+supported.wsam32=-Xrunam### Cyanea ITCAMfWAS 6.0 (OS400 only)supported.itcamfwas.os400.v5=-Xrunam5supported.itcamfwas.os400.v6=-Xrunam6#

# Rational Performance Analyst 6.1supported.rpa=-XrunpiAgent## ITM/WebSphere Performance Monitorsupported.wpm=-XrunpmiJvmpiProfiler## CAM Toolkit supported.camtoolkit=-Xrunam_*## Unsupported JVMPI Profiler Agents## Borland OptimizeItunsupported.BorlandOptimizeIt1=-Xrunoiiunsupported.BorlandOptimizeIt2=-Xrunpriunsupported.BorlandOptimizeIt3=-Xruncciunsupported.BorlandOptimizeIt4=-Xruntdi

Note: If the phrase Installed - Restart of the application server needed shows up under Component Status after server restart (as shown inFigure 9-14), it might indicate that an unsupported JVMPI agent was found.





Figure 9-14 Indicator for existence of an unsupported JVMPI agent

In this case, check the log file msg-ma.log in the Tivoli logs directory (in our lab,in /var/ibm/tivoli/common/BWM/logs). Message BWMN0052E in msg-ma.loginforms you that an unsupported JVMPI agent was found for the J2EE server inquestion.

We added the line shown in bold in Figure 9-13 on page 368 to facilitate ITCAMfor WebSphere data collector co-existence. To resolve the message inFigure 9-14, we run enableprobes (from the

/var/tmtp/MA/app/instrument/6101/bin directory) with the following arguments:

./enableprobes.sh -serverHome /wasitconfig/itcell/itnodea -serverNameitsr01a -profileName default -enable -netdeploy

ITCAM for Response Time Tracking writes information to SYSOUT and

SYSPRINT of the J2EE server. Product logs and trace information can be foundin the common Tivoli log directory, for example /var/ibm/tivoli/common/BWM/logs.

Problem finding librariesWebSphere Application Server could not find some requested libraries. Theselibraries must be allocated in the LIBPATH. For example:

libarmjni.so /usr/lpp/tmtp/V6R1M0/MA/bin/zos/USRLIB

libvirt.so /var/tmtp/MA/app/instrument/6101/lib/os390





File not found: cynlogging.propertiesLogging configuration file not found in created runtime environment:

/var/tmtp/MA/app/instrument/6101/appServers/itsr01a_213/config/cynlogging.properties. You can copy this file from the ITCAM for WebSphere data collector.

WebSphere Application Server cannot write to common logITCAM for Response Time Tracking uses Tivoli common path to write loginformation. This path is typically /var/ibm/tivoli/common/BWM/logs. TheWebSphere Application Server user ID needs access to this directory to createits log files. You can either change the owner of the path or connect theWebSphere Application Server user ID to the ITCAM for Response TimeTracking user.

9.5 ITCAM for CICS Transactions

The ITCAM for CICS Transactions is a data collector installed on CICS systemsto provide data for ITCAM for Response Time Tracking or ITCAM forWebSphere. ITCAM for CICS Transactions does not provide an in-depthapplication analysis or CICS system analysis.

ITCAM for CICS Transactions is not a standalone product; it needs ITCAM for

Response Time Tracking, ITCAM for WebSphere, or both. We discuss theITCAM for CICS Transactions integration in their respective chapters.

The discussion here is based on IBM Tivoli Composite Application Manager IMS

Transactions Product Guide , SC32-9511, and IBM Tivoli Composite Application Manager CICS Transactions Product Guide , SC32-9510.

9.5.1 Concepts

The CICS data collector uses standard CICS calls that run in CICS to monitortransactions. It also installs CICS Global user exit (GLUE) and task-related userexit (TRUE). The global user exit gets control for every EXEC CICS execution,and the task-related user exit gets control for task invocation and completion.

The command agent installs itself as a CICS transaction SAMC that must berunning for the extent of the data collector. The event agent runs in a JVM inCICS to bridge the communication from CICS data collector to the managingserver. Figure 9-15 shows the CICS data collector concept.





Figure 9-15 CICS data collector


The configuration of the CICS data collector is according to IBM Tivoli Composite

Application Manager CICS Transactions Product Guide , SC32-9510.Configuration tasks for ITCAM for CICS Transactions include:

1. (Optional) Define the CYN1 subsystem; see 9.2, “The CYN1 subsystem” on

page 345.

2. Assign the ITCAM for CICS Transactions library as APF authorized. (Thelibrary is SCYNAUT2.) APF authorization can be given using either IEAAPFxxor PROGxx member from SYS1.PARMLIB or using the SETPROG commandsimilar to:

SETPROG APF,ADD,DSN=ITCAM.V6R1.SCYNAUT2,VOL=ITCAM1

3. Update the CICS startup JCL to include the library SCYNAUT2 in theSTEPLIB and DFHRPL concatenation.

4. The JVM Support for the CICS Region is recommended.

5. Generate runtime environments in UNIX System Services. ITCAM for CICSTransactions comes with a default template directory in

/usr/lpp/itcam/cics/CICS1. This template directory must be replicated to aruntime directory based on the CICS application ID. This can be performedusing the setupcics.sh command (Example 9-10). The configuration programautomatically updates datacollector.properties and datacollector.env files.

Example 9-10 Running setupcics.sh

TIVO01:/usr/lpp/itcam # ./cics/CICS1/bin/setupcics.sh+---------------------------------------------------------+| (C) Copyright IBM Corp. 2005,2006 All Rights Reserved. |

CICS

SAMC

transaction

libam_cics_zos.soJNI module

Data collector JVM Publish data

GLUEGlobal User Exit

TRUETransaction User Exit





| ITCAM for CICS Transactions Data Collector V6.1.0 || Runtime configuration. |+---------------------------------------------------------+Enter Java home directory [/usr/lpp/java/J1.4]:/usr/lpp/java/J1.4

Enter ITCAM runtime directory name [/u/itcam]:/var/itcam61Enter the CICS region name (APPLID) to monitor [cics]:SCSCBUD1Do you want to enable ITCAM for WebSphere support [y or n]: yEnter the IP address of the ITCAM Managing Server:peoria.itsc.austin.ibm.comEnter ITCAM Managing Server install directory [/opt/IBM/itcam/WebSphere/MS]:/opt/IBM/itcam/WebSphere/MS

Do you want to enable ITCAM for RTT Support [y or n]: yWhat is the RTT port number [32323]:32323Enter the name of the TMTP MA install directory [/etc/tmtp]:/etc/tmtp/MADo you want to enable RTT MQ Monitoring Support [y or n]: nSetup will create an ITCAM runtime with the following parameters:

1) JAVA runtime: /usr/lpp/java/J1.42) ITCAM CICS runtime: /var/itcam61/cics/SCSCBUD13) CICS APPLID: SCSCBUD14) ITCAM enabled: yes

ITCAM MS host: peoria.itsc.austin.ibm.comITCAM MS home: /opt/IBM/itcam/WebSphere/MS

5) RTT enabled: yesRTT MA port: 32323RTT MA dir: /etc/tmtp/MA

6) RTT MQ enabled: no

Create ITCAM configuration for CICS SCSCBUD1?Enter item number to modify, 'y' to accept, or 'n' to cancel: yITCAM configuration for SCSCBUD1 created in /var/itcam61/cics/SCSCBUD1

6. Update the CICS PLT definitions. ITCAM for CICS Transactions supplies asample PLT definition in SCYNSAM2(CYN$PTCY) for assembling. If youalready have a PLT definition, you can copy the DFHPLT definition fromCYN$PTCY to your PLT definition to include CYNCINI1, DFHDELIM, and

CYNCINI2. For the example we use the data set memberCICSLOAD(DFHPLTCY).

7. Update CICS SYSIN to include the following parameter:

PLTPI=CY





INITPARM=(CYNCINI1=’/var/itcam61/’)INITPARM=(CYNCSQLP=DB2.DBRMLIB)

8. Update CICS definitions using SCYNSAM2(CYN$INST) job. This job createsa new group called CYNCICS. This CYNCICS must be added to a group list

that will be auto-started when CICS is started.9. Restart your CICS region.


The CICS data collector writes information to:

DD name SYSOUT: initial startup of the JVM; failure to start the JVM will beshown here.

DD name SYS00001: provide common system output for the data collectorJava process.

Message and trace files in the Tivoli common directory, typically under /var/ibm/tivoli/common/CYN/logs:

msg-<applid>-cicsprobe.logtrace-<applid>-cicsprobe.logmsg-<applid>-cicsprobe-native.logtrace-<applid>-cicsprobe-native.log

Check the setting for variables am.classpath, java.home, am.path, andam.libpath in datacollector.env in your appropriate CICS runtime directory,e.g. /var/itcam61/cics/<applid>/.

9.6 ITCAM for IMS Transactions

ITCAM for IMS Transactions is a data collector installed on IMS systems to

provide data for ITCAM for Response Time Tracking or ITCAM for WebSphere.ITCAM for IMS Transactions does not provide an in-depth application analysis orIMS system analysis.

ITCAM for IMS Transactions provides the following information:

IMS transaction response time IMS processor and memory usage

ITCAM for IMS Transactions is not a standalone product; it needs ITCAM for

Response Time Tracking, ITCAM for WebSphere, or both. We discuss moreabout ITCAM for IMS Transactions integration in the ITCAM for Response TimeTracking and ITCAM for WebSphere chapters.





The discussion here is based on IBM Tivoli Composite Application Manager IMS Transactions Product Guide , SC32-9511, and IBM Tivoli Composite Application

Manager CICS Transactions Product Guide , SC32-9510.

9.6.1 ConceptsThe IMS data collector installs itself as a standard IMS exit that taps transactioninformation. There are two IMS exits that are used:

DFSYIOE0: the OTMA message exit DFSMSCE0: terminal message exit

These exits then turn the processing to the data collector JVM using Java NativeInterface (JNI) routines. The data collector forwards the information to the

managing server. Figure 9-16 illustrates this process.

Figure 9-16 IMS data collector

The MSC edit routine takes control when a message is passed around. It cancollect the timestamp when:

A transaction message is inserted from terminal (TR start) A transaction message is returned to terminal (TR end) A program gets the message from IO PCB (PR start) A program inserts a message to IO PCB (PR end)

IMSControl region

DFSYIOE0OTMA edit routine

DFSMSCE0TM/MSC edit routine

OTMA message

libam_imsvv _zos.soJNI module

Data collector JVM

OTMA message

TM/MSC message TM/MSC message

Publish data






Configuration of ITCAM for IMS Transactions data collector is performedaccording to the instructions in IBM Tivoli Composite Application Manager IMS Transactions Product Guide , SC32-9511. The configuration tasks are:

1. (Optional) Set up CYN1 subsystem as discussed in 9.2, “The CYN1subsystem” on page 345.

2. Assign the ITCAM for IMS Transactions library as APF authorized. The libraryis SCYNAUT3. APF authorization can be given using either IEAAPFxx orPROGxx member from SYS1.PARMLIB or using the SETPROG commandsimilar to:

SETPROG APF,ADD,DSN=ITCAM.V6R1.SCYNAUT3,VOL=ITCAM1

3. Update the IMS control region startup JCL to accommodate:– Add SCYNAUT3 to STEPLIB concatenation

– Set the IMS region size to 0 or any appropriate number. The data collectoris a Java process; hence it requires additional vir tual memory.

– Add a new DD called CYNIMSIN; the content is an 80-byte record with thepath of the IMS data collector product. You can refer to theSCYNSAMP(CYN$PATH). From the runtime environment in Example 9-11on page 375, this must refer to /var/itcam61.

4. Depending on your IMS version, link edit the appropriate IMS exit to use. Youcan use the CYNILINK job from SCYNSAM3. The default exit is link-edited forIMS V7.1. IMS is also supported for IMS V8.1 and IMS V9.1.

5. Generate runtime environments in UNIX System Services. ITCAM for IMSTransactions comes with a default template directory in

/usr/lpp/itcam/ims/IMS1. This template directory must be replicated to aruntime directory, such as /var/itcam61/ims/<applid>, that represents the IMSdata collector in the specific application ID. This can be performed using

setupims.sh. See Example 9-11 on page 375.

Example 9-11 Running setupims.sh

TIVO01:/usr/lpp/itcam # ./ims/IMS1/bin/setupims.sh+-------------------------------------------------------------+| (C) Copyright IBM Corp. 2005,2006 All Rights Reserved. || ITCAM for IMS Transactions Data Collector V6.1.0 || Runtime configuration. |+-------------------------------------------------------------+

Enter Java home directory [/usr/lpp/java/J1.4]:/usr/lpp/java/J1.4Enter ITCAM runtime directory name [/u/itcam]:/var/itcam61Enter the IMS region ID to monitor [IMS]:





IMSJEnter version of IMS [71, 81, 91]:91Enter IMS network name [network1]:

wtsc67.itso.ibm.com

Do you want to enable ITCAM for WebSphere support [y or n]: yEnter the IP address of the ITCAM Managing Server:peoria.itsc.austin.ibm.comEnter ITCAM Managing Server install directory [/opt/IBM/itcam/WebSphere/MS]:/opt/IBM/itcam/WebSphere/MSDo you want to enable ITCAM for RTT Support [y or n]:

yWhat is the RTT port number [32323]:32323

Enter the name of the TMTP MA install directory [/etc/tmtp]:/etc/tmtp/MADo you want to enable RTT MQ Monitoring Support [y or n]:nSetup will create an ITCAM runtime with the following parameters:

1) JAVA runtime: /usr/lpp/java/J1.42) ITCAM IMS runtime: /var/itcam61/ims/IMSJ3) IMS Region Information

IMS APPLID: IMSJ

IMS network name: wtsc67.itso.ibm.com4) ITCAM enabled: yes

ITCAM MS host: peoria.itsc.austin.ibm.comITCAM MS home: /opt/IBM/itcam/WebSphere/MS

5) RTT enabled: yesRTT MA port: 32323RTT MA dir: /etc/tmtp/MA

6) RTT MQ enabled: no

Create ITCAM configuration for IMS IMSJ?Enter item number to modify, 'y' to accept, or 'n' to cancel: y ITCAM configuration for IMSJ created in /var/itcam61/ims/IMSJ

The setupims.sh updates the datacollector.properties and datacollector.envfiles for the IMSJ subsystem that we have.

6. APF authorize data collector native modules:

extattr +a /usr/lpp/itcam/ims/IMS1/bin/imsprobeextattr +a /usr/lpp/itcam/ims/scripts/imsprobe

extattr +a /usr/lpp/itcam/ims/IMS1/lib/libam_ims*_zos.soYou can check the extended attribute using the command ls -lE.





7. Restart the IMS region.


The CICS data collector writes information to:

DD name SYSOUT: initial startup of the JVM; failure to start the JVM will beshown here.

DD name SYS00001: provides common system output for the data collectorJava process.

Message and trace files in the Tivoli common directory, typically under /var/ibm/tivoli/common/CYN/logs:

msg-<applid>-imsprobe.logtrace-<applid>-imsprobe.logmsg-<applid>-imsprobe-native.logtrace-<applid>-imsprobe-native.log

Check the setting for variables am.classpath, java.home, am.path, andam.libpath in datacollector.env in your appropriate IMS runtime directory, e.g.

/var/itcam61/ims/<applid>/.

Check the right IMS version for variable probe.library.name in<instance-id>.datacollector.properties.

If you do not see any transaction-related data in the ITCAM for WebSphereconsole, check whether you are running the link job CYNILINK from SCYNSAM3for the right IMS version.

9.7 ITCAM for SOA management agent for z/OS

This is the overall implementation procedure for ITCAM for SOA managementagent for z/OS:

9.7.1, “Considerations for the z/OS environment” on page 378 9.7.2, “ITCAM for SOA management agent for z/OS” on page 379 9.7.3, “Enabling CICS data collector” on page 389

Note: There is one libam_ims*_zos.so for each IMS version that issupported. You only have to authorize the module for the IMS version thatyou are implementing.





9.7.1 Considerations for the z/OS environment

As you plan for the deployment of the ITCAM for SOA monitoring into your z/OSenvironment, consider the following additional deployment and configurationoptions:

Identify which z/OS systems to monitor with the ITCAM for SOA monitoringagent and other monitoring agents. ITCAM for SOA uses OMEGAMONmonitoring agent architecture, so you may need to consider the OMEGAMONenvironment. See IBM Tivoli OMEGAMON V3.1 Deep Dive on z/OS ,SG24-7155.

ITCAM for SOA monitoring agent can be run within the same address spaceas the Tivoli Enterprise Monitoring Server on z/OS.

By default, the data collector does not have write privileges to write to its logfile. You must grant write privileges for the $ITCAMSOA_HOME/KD4 directoryto the user ID that runs your IBM WebSphere Application Server, such asASSR1 in WSCFG1 group.

Ensure that the TCP/IP has been configured correctly in the z/OSenvironment that the ITCAM for SOA monitoring agent is running. TCP/IPmust have the connection services running with a minimum life time of 0. This

can be verified using the D TCPIP,NETSTAT,CONFIG console command. Theoutput should be similar to Example 9-12.

Example 9-12 TCP/IP configuration

. . .NETWORK MONITOR CONFIGURATION INFORMATION:PKTTRCSRV: NO TCPCNNSRV: YES MINLIFTIM: 0 SMFSRV: YES

Otherwise, modify TCP/IP with the obey command. Run V TCPIP,,OBEY,data

set from the system console with the input data set containing the line:

NETMON SMFS TCPCONNS MINLIFET 0

Note: Before installing ITCAM for SOA monitoring agent, review the spacerequirements and considerations for an SMP/E installed environment tomake sure that your z/OS system has sufficient DASD storage available.

Be aware that the DASD space estimates assume that these productswere installed in a separate CSI environment. When multiple products areinstalled into a shared CSI environment, DASD requirements for eachproduct should be less. Refer to Configuring IBM Tivoli Composite

Application Manager on z/OS , SC32-9493, for additional information.

f f 7151 h15 i l t ti f





9.7.2 ITCAM for SOA management agent for z/OS

ITCAM for SOA supplies a complete System Modification Program/Extended(SMP/E) distribution for installing on z/OS systems. The ITCAM for SOA producttape includes all of the z/OS components required for installation, which are:

Configuration Tool V3.1.0 Tivoli Enterprise Monitoring Server on z/OS ITCAM for SOA V6.0 Monitoring Agent

This is an outline of the installation procedure for ITCAM for SOA on z/OS:

1. We perform the standard SMP/E installation. This can be run by using batch jobs or by using dialogs under Interactive System ProductivityActivity/Program Development Facility (ISPF/PDF). The SMP/E processing

can be read from the IBM Tivoli Composite Application Manager for SOAProgram Directory , GI11-4087. The installed FMIDs are:

– HKCI310: Configuration tool V 3.1

– HKDS360: Tivoli Enterprise Monitoring Server version 360

– HKD4600: ITCAM for SOA agent V6

– HKLV190: CT engine

2. When ITCAM for SOA has been installed in the ACCEPT stage, we can startthe installation configuration tool. The configuration tool is executed from acopy of KCIINST target library that we call INSTLIB. The high-level qualifier

that we use is ITCAMSOA. Note that this configuration tool can be executedby only one TSO user at a time.

Note: If you have an existing OMEGAMON XE V3.1.0 monitoring agentproduct, you do not have to install the Configuration Tool again. If you havean earlier version of the Candle Installation and Configuration AssistanceTool (CICAT) in the same CSI on your z/OS system, it will be overwrittenautomatically by IBM Configuration Tool V3.1.0 during SMP/E installation.

7151ch15 zos implementation fm D ft D t f R i M h 1 2007 5 22





We show the configuration screen for installing ITCAM for SOA agent andconnecting it to a Tivoli Enterprise Monitoring Server running on a distributedworkstation. We do not configure Tivoli Enterprise Monitoring Server on z/OS.We also create a full runtime environment (RTE) instead of splitting theenvironment for a sysplex environment. See IBM Tivoli OMEGAMON V3.1.0

Deep Dive on z/OS , SG24-7155, for more information about RTE. Figure 9-17 shows the overall configuration process for a new installation.

Figure 9-17 Configuration tool processing

The ITCAM for SOA configuration tool dialog uses Candle terminology.Changes in this book and IBM Tivoli Monitoring V6.1 documentation include:

– Candle Management Server is called Tivoli Enterprise Monitoring Server.

– CandleNet Portal Server is called Tivoli Enterprise Portal Server.

– CandleNet Portal is called Tivoli Enterprise Portal.

Specify configuration parameters

Create configuration parameters

Specify Agent address pace parameters

Create runtime members

Configure persistent datastore

Setting up configuration tool

Configuring product

Creating RTE

Define RTE

Build RTE libraries

Configure RTE

Load RTE

Draft Document for Review March 1 2007 5:22 pm 7151ch15-zos-implementation fm





3. On the Configuration Tool initial page shown in Figure 9-18, select option 1 toset up your configuration tool.

Figure 9-18 Configuration tool page - main menu

4. The setup involves defining the JOB card and high-level qualifiers, andallocates work libraries.

Select option 2 to configure a product.

5. ITCAM for SOA should be available as shown in Figure 9-19.

Figure 9-19 Configuration tool page - product selection

---------------------------------- MAIN MENU ----------------------------------

OPTION ===>

Enter the number to select an option:

1 Set up work environment

2 Install products or maintenance

3 Configure products

I Installation information <=== RevisedS Services and utilities

Installation and Configuration Assistance Tool Version 310.01(C) Copyright IBM Corp. 1992-2004

Licensed Material - Program Property of IBM

F1=Help F3=Back

---------------------------- PRODUCT SELECTION MENU ---------------------------COMMAND ===>

Actions: S Select product

S IBM Tivoli Composite Application Manager for SOA V6.0.0F1=Help F3=Back F5=Refresh F7=Up F8=Down

7151ch15-zos-implementation fm Draft Document for Review March 1 2007 5:22 pm



7151ch15 zos implementation.fm Draft Document for Review March 1, 2007 5:22 pm


6. When we configure the product, we are defining the RTE. We only define afull RTE, instead of a split SHARING and BASE RTEs. The split RTE is usefulespecially if you are running on multiple systems in a sysplex environment.The definition is shown in Figure 9-20.

Figure 9-20 Configuration tool page - creation of full RTE

7. As shown in the process overview in Figure 9-21 on page 382, we need toadd (Figure 9-14), build, configure, and load the RTE. We do not create aCMS, as we use our Tivoli Enterprise Monitoring Server in our distributedserver.

Figure 9-21 Configuration tool page - defining an RTE

------------------------- RUNTIME ENVIRONMENTS (RTEs) -------------------------COMMAND ===>

Actions: A Add RTE, B Build libraries, C Configure,L Load all product libraries after SMP/E,D Delete, U Update, V View values, Z Utilities

Action Name Type Sharing Descriptiona SOA FULL ITCAM for SOA full RTE

F1=Help F3=Back (No RTEs defined, use Action A to Add)

----------------------- ADD RUNTIME ENVIRONMENT (1 of 2) ----------------------COMMAND ===>

RTE: SOA Type: FULL Desc: ITCAM for SOA full RTE

Libraries High-level Qualifier Volser Unit Storclas Mgmtclas PDSENon-VSAM ITCAMSOA TAROM2 3390 NVSAM ITCAMSOA TAROM2Mid-level qualifier ==> SOA

JCL suffix ==> SOASTC prefix ==> CANSSYSOUT class ==> X Diagnostic SYSOUT class ==> XLoad optimization ==> N (Y, N)

Will this RTE have a Candle Management Server ==> N (Y, N)If Y, CMS name ==> SOA:CMS (Case sensitive)

Copy configuration values from RTE ==> (Optional)

Enter=Next F1=Help F3=Back





Draft Document for Review March 1, 2007 5:22 pm 7151ch15 zos implementation.fm

8. Pressing Enter gets you to the second RTE definition screen in Figure 9-22.

Figure 9-22 Configuration tool page

----------------------- ADD RUNTIME ENVIRONMENT (2 of 2) ----------------------COMMAND ===>

Use OS/390 system variables? ==> N (Y, N)RTE name specification ==> &SYSNAMERTE base alias specification ==> n/aApplid prefix specification ==> K&SYSCLONE.Use VTAM model applids? ==> N (Y, N)

Security system ==> NONE (RACF, ACF2, TSS, NAM, None)ACF2 macro library ==>

VTAM communications values:Applid prefix ==> CTD Network ID ==> USIBMSCLogmode table ==> KDSMTAB1 LU6.2 logmode ==> CANCTDCS

If you require TCP/IP communications for this RTE, complete these values:Hostname ==> WTSC58.ITSO.IBM.COMAddress ==> 9.3.4.129Started task ==> TCPIPPort number ==> 1918Interlink subsystem ==> (if applicable)





p p


9. In the configuration page for the RTE (Figure 9-23), we configure only theITCAM for SOA agent. We do not configure Tivoli Enterprise MonitoringServer because we will connect to Tivoli Enterprise Monitoring Server on adistributed system.

Figure 9-23 Configuration tool page - ITCAM for SOA steps

---CONFIGURE IBM TIVOLI COMPOSITE APPLICATION MANAGER FOR SOA RTE: SOA --------OPTION ===>

Last selectedPerform the appropriate configuration steps in order: Date Time

If you have defined a TEMS in this RTE that this Agentwill communicate with, select option 1.1 Register with local TEMS

2 Specify configuration parameters3 Create configuration parameters

4 Specify Agent address space parameters5 Create runtime members6 Configure persistent datastore

7 Create HFS directories and copy files on USS8 Complete the configuration

F1=Help F3=Back





10.The configuration parameter requires a UNIX System Services path. We usethe path /usr/lpp/Candle as shown in Figure 9-24.

Figure 9-24 Configuration tool page - configuration parameter

11.The ITCAM for SOA agent will start in its own address space. Figure 9-25 shows the address space configuration.

Figure 9-25 Configuration tool page - agent address space

----------------------- SPECIFY CONFIGURATION PARAMETERS ----------------------

OPTION ===>

HFS CandleHome directory (case sensitive):/usr/lpp/Candle_______________________________________________________________________________________________________________________________________________________________________________

USS CLIST library (Required) ==> SYS1.SBPXEXECHFS migration directory (case sensitive):


-------------------- SPECIFY AGENT ADDRESS SPACE PARAMETERS -------------------COMMAND ===>

The following information is needed to define the Agent address space:

Agent started task ==> CANSD4

Connect to CMS in this RTE ==> N (Y, N)Name of Primary CMS ==> BEIJING

Specify communication protocols in priority sequence:Protocol 1 ==> IPPIPE (SNA, IP, IPPIPE)Protocol 2 (optional) ==> (SNA, IP, IPPIPE)Protocol 3 (optional) ==> (SNA, IP, IPPIPE)

Enter=Next F1=Help F3=Back F5=Advanced F10=CMS List





12.The connection to Tivoli Enterprise Monitoring Server is configured as shownin Figure 9-26.

Figure 9-26 Configuration tool page - CMS values

--------------------- SPECIFY AGENT PRIMARY CMS VALUES ------------------------

COMMAND ===>

CMS name (case sensitive) ==> BEIJING

Complete this section if the primary CMS requires SNA support:LU6.2 logmode ==>Logmode table name ==>Local location broker applid ==>Network ID ==>

Complete this section if the primary CMS requires TCP support:Hostname ==> BEIJING.ITSC.AUSTIN.IBM.COMAddress ==> 9.3.5.35Network interface card (NIC) ==>

IP port number ==>

IP.PIPE port number ==> 1918Address translation ==> N (Y, N)

Partition name ==>






13.Figure 9-27 shows the communication parameter for the ITCAM for SOAagent.

Figure 9-27 Configuration tool page - IP.PIPE configuration

14.The persistent data store is used to store short-term historical data for theITCAM for SOA agent. We use mostly the default value for going through theconfiguration menu.

------------------ SPECIFY AGENT IP.PIPE CONFIGURATION VALUES -----------------

COMMAND ===>

Specify the TCP communication values for this Agent:Hostname ==> WTSC58.ITSO.IBM.COMAddress ==> 9.3.4.129Started task ==> TCPIP

If applicable

Network interface card (NIC) ==>Interlink subsystem ==>IUCV interface in use? ==> N (Y, N)

Specify Agent IP.PIPE configuration:Address translation ==> N (Y, N)

Partition name ==>






15.The last step is to load and populate the runtime environment. You have theoption to populate the UNIX System Services directory with this step or deferit to be executed manually from RKANSAM(KD4USSJB). See Figure 9-28.

Figure 9-28 Configuration tool page

16.Copy start-up JCLs to the system procedure library, such as SYS1.PROCLIB.These JCLs reside in the RKANSAM data set:

CANSD4 ITCAM for SOA agent

KDSPROC1 Persistent data store maintenanceKDSPROC2 Persistent data store backup and initialization

17.Authorize the RKANMOD and RKANMODL from your RTE. You can use theSETPROG console command to perform this. Our setup uses the followingcommands:

SETPROG APF,ADD,DSN=ITCAMSOA.SOA.RKANMOD,VOL=TAROM2SETPROG APF,ADD,DSN=ITCAMSOA.SOA.RKANMODL,VOL=TAROM2

Activating the ITCAM for SOA to the WebSphere Application Server environmentin z/OS is similar to the distributed environment. See 8.2.4, “Enabling themonitoring agent” on page 309.

------------------------- LOAD JOB - INCLUDE USS STEPS ------------------------COMMAND ===>

The IBM Tivoli Composite Application Manager for SOA component isconfigured in this RTE. In order to include information for this RTE onz/OS UNIX System Services (USS), you must meet the following conditions:- the job to create directories and copy files to HFS must be submitted

on a machine that has access to the USS directories.- the job to create directories and copy files to HFS must be submitted

by a TSO userid that has write access to the HFS directories specified

in the Specify configuration parameters panel from the IBM TivoliComposite Application Manager for SOA menu.

If the above conditions are met, then IBM recommends that you specify Y belowto ensure that all maintenance is synchronized. If not, then specify N andthe configuration job will create a KD4USSJB job for later submission. Submitthe hilev.RKANSAMU(KD4USSJB) job from an appropriate machine with a TSOuserid that satisfies these conditions.

Do you want to include the USS steps in the configuration job? ==> Y (Y, N) Y

Enter=Next F1=Help





9.7.3 Enabling CICS data collector

ITCAM for SOA V6.1 has a new feature to collect Web Services information fromCICS Transaction Server. This feature allows Web Services information to becollected similar to the WebSphere Application Server collection.

There are several configuration steps that must be performed:

The CICS Started Task usedID must have read write access to the agentdirectory in UNIX System Services. Our setup is /usr/lpp/Candle.

The CICS started task should have access to TKANMOD dataset in theDFHRPL concatenation.

Data collector programs and transactions must be defined using the CICSSystem Definition program. A sample JCL is provided in the

TKANSAM(KD4CSD). Some of these transactions may need to be secured,those are KD4, KD4O and KD4C.

Updating CICS program load table (PLT) to include KD4INIT module to beloaded and unloaded with startup and shutdown of CICS.

The Web Services through CICS is handled using the CICS pipelines. Thesepipelines are configured using an XML definition. The pipeline that you wantto monitor must be handled by the KD4HAND program. This program isbasically the Web Services interceptor. KD4HAND can be defined similarly

for the requestor pipeline and provider pipeline. Example 9-13 shows thehandler definition excerpt.

Example 9-13 CICS handler definition

<service_handler_list><handler>

<program>KD4HAND</program><handler_parameter_list><soap_1.1/><handler_parameter_list>

</handler>

</service_handler_list>





Draft Document for Review March 1, 2007 5:22 pm 7151chITMTEP.fm




Chapter 10. Integration scenarios withITCAM products

This chapter describes the features and capabilities of the IBM Tivoli CompositeApplication Manager family of products. The discussion includes:

10.1, “ITCAM family integration scenarios” on page 392

10.2, “Deep dive and in-context launch” on page 392

10.3, “Tivoli Enterprise Portal workspace” on page 396

10.4, “Workflows and situations” on page 421

10

7151chITMTEP.fm Draft Document for Review March 1, 2007 5:22 pm




10.1 ITCAM family integration scenarios

As the products develop, cross-product integration is needed to see the biggerpicture and have a better understanding of the environment. We discuss severalintegration topics here:

10.2, “Deep dive and in-context launch” on page 392, which is the apparentfirst level of integration from ITCAM for Response Time Tracking to ITCAM forWebSphere.

10.3, “Tivoli Enterprise Portal workspace” on page 396 discusses a samplesession in which we customize Tivoli Enterprise Portal workspace to monitorour Trader application servers with information from ITCAM for ResponseTime Tracking, ITCAM for SOA, and ITCAM for WebSphere.

10.4, “Workflows and situations” on page 421 provides an overview of asample workflow that can be used to raise a situation based on the analysisfrom multiple situations that are customized from various ITCAM products.

10.2 Deep dive and in-context launch

ITCAM for Response Time Tracking topology view allows deep dive to launch incontext ITCAM for WebSphere. This feature enables operational and support

areas to view the application at a high level using ITCAM for Response TimeTracking and, where needed, quickly link to the relevant detailed data in the sameuser interface. Using the ITCAM for Response Time Tracking topology view, youcan quickly launch ITCAM for WebSphere by right-clicking a J2EE object in thetopology. This discussion includes:

10.2.1, “Configuring Launch in Context” on page 393 10.2.2, “Using Launch in Context” on page 395




Chapter 10. Integration scenarios with ITCAM products 393

10.2.1 Configuring Launch in Context

This functionality must be preconfigured before use, by using the ITCAM forResponse Time Tracking management browser. From the Web interface,navigate to System Administration→ System Properties and choose Launch

in Context from the pull-down menu as shown in Figure 10-1. Click ShowProperties.

Figure 10-1 Launch in Context configuration menu





This opens a window similar to Figure 10-2.

Provide the ITCAM for Response Time Tracking server host and ITCAM forWebSphere managing server host details as we have done for our exampleenvironment and click Apply.

Figure 10-2 Launch in context configuration


10 2 2 U i L h i C t t




10.2.2 Using Launch in Context

The benefit of performing this integration involves the reduction in diagnosis orresolution time of problems because all relevant information is quick to hand.This is highlighted in our example application in Figure 10-3. On a relevant object

in the topology view, right-click and select ITCAM for WebSphere from thepop-up menu.

Figure 10-3 Launch in context pop-up menu


The browser for ITCAM for WebSphere should open and a valid user name and




The browser for ITCAM for WebSphere should open and a valid user name andpassword may be needed. Figure 10-4 shows an example.

Figure 10-4 Launch in context WebSphere window

We had selected to launch in context from the J2EE object on laredo in thetopology view. As you see, it has directly placed the view into context showingdetail of laredo.

10.3 Tivoli Enterprise Portal workspace

The Tivoli Enterprise Portal (TEP) is the common user interface for real-timeinformation and historical data collected by the Tivoli Enterprise Monitoring

Server. Products from the various Tivoli families integrate with it to provide aflexible, customizable repository and linked information. This section shows anexample Tivoli Enterprise Portal customization for workspaces that can be usedto monitor our Trader application.


The discussion includes:




The discussion includes:

10.3.1, “Designing the workspaces” on page 397 10.3.2, “Building the navigation tree” on page 398 10.3.3, “Defining the workspace” on page 403 10.3.4, “Defining Trader main view” on page 407 10.3.5, “Defining bandung and laredo workspaces” on page 407

10.3.1 Designing the workspaces

As discussed in Chapter 1, “IBM Tivoli Composite Application Manager V6.1overview” on page 1, the application configuration of Trader application goesthrough two levels of WebSphere Application Servers. This enables us toconfigure the structure of our navigation tree to show the application servers.

We assume that Tivoli Enterprise Portal is operational and all data collectionfrom ITCAM for Response Time Tracking, ITCAM for SOA, and ITCAM forWebSphere are running. Refer to IBM Tivoli Monitoring User's Guide ,SC32-9409, for further details about defining queries and workspaces. We use abasic workspace that does not includes links.

You may need to be familiar with the information provided for each product. Wediscuss them in the following topics:

ITCAM for Response Time Tracking: 5.11, “Working with Tivoli EnterprisePortal” on page 247

ITCAM for WebSphere: 3.6, “Using Tivoli Enterprise Portal” on page 88

ITCAM for SOA: 8.3, “ITCAM for SOA usage scenarios” on page 317

As we are using an IBM Tivoli Monitoring platform, we have the ability to createnew workspaces with combined content of several monitoring sources. This issimilar in OMEGAMON Dashboard Edition (DE).

We create a new navigation tree and workspaces for the Trader application andthe two servers that it uses. Important performance considerations forworkspaces include:

The queries in the workspace retrieve data from the agents through TivoliEnterprise Monitoring Server. They use some processing power on the agent.

You can share queries for several portlets in the workspace to save someprocessing.

Limit the rows and columns of data that you retrieve from the query as muchas possible from the query definition, not the filter definition of the portlet.


10 3 2 Building the navigation tree




10.3.2 Building the navigation tree

As management agents are configured, they are automatically added to thePhysical View workspaces in the navigator panel. As you would expect in ourenvironment, it shows the various physical servers that we have worked with sofar (Figure 10-5).

Figure 10-5 TEP Physical view example


We develop a new navigation tree called Trader for a user who must monitor the




p gTrader application only. We can do this using a Logical view in a new navigator.We perform these procedures:

1. Click the Edit Navigator View icon to open the Navigator Edit dialogshown in Figure 10-6.

Figure 10-6 Navigator view edit window

2. Click the Create New Navigator View icon and enter a name anddescription as we have done in Figure 10-7. Click OK.

Figure 10-7 Create new logical view

3. In the new Trader navigator item, we create two more navigator items.Right-click and select Create Child Item. They represent the WebSphereApplication Servers that we use: bandung1 and laredo1.


4. The managed systems represent the monitoring agents that provide the




g y p g g pinformation display for the appropriate navigation tree. Select this carefully asthis represents available data for your portlets. Figure 10-8 shows theproperty of the bandung1 navigator view.

Figure 10-8 Bandung1 navigator managed systems


5. Figure 10-9 shows the display for the laredo navigator item.




Figure 10-9 Laredo1 navigator managed systems

6. In Figure 10-8 on page 400 and Figure 10-9, you can see that we use anindividual agent for ITCAM for SOA and ITCAM for WebSphere, but forITCAM for Response Time Tracking we use a shared object from themanagement server.

D4 Represents ITCAM for SOA agent data.

ITCAMSOA Represents ITCAM for SOA agent status.

KYNA Represents ITCAM for WebSphere agent status.

KYNS Represents ITCAM for WebSphere agent data.

T2 Represents ITCAM for Response Time Tracking agentdata and status.


7. You can also add views from the physical view into this new navigator view. Tod d d l t h i l i bj t (Wh l t d b d




drag and drop, select a physical view object. (When selected, a box surroundsit.) Drop directly onto the Trader object on the left, ensuring that it has thesurrounding outline box. We do not perform this step. Figure 10-10 shows thefinal navigator tree for our example.

Now that the navigator tree is defined, we can close the navigator edit dialogby clicking Close.

Figure 10-10 Final navigator dialog


10.3.3 Defining the workspace




The initial workspace for the new navigator item is an empty workspace with anotepad and a browser pointing to a generic page showing Workspace notdefined as shown in Figure 10-11.

Figure 10-11 Workspace not defined

We have to define these workspaces for the navigator objects.

The main trader workspace should be the initial display window for eachoperator and must consume the least amount of overhead. Keeping that inmind, we use the alert view for the individual objects as the initial display forthe Trader workspace.

Alerts are generated by background collectors called situations. This has theoverhead for transporting the alert to and from the Tivoli Enterprise PortalServer only. When an operator sees an alert, drilling down to the appropriate


application server exposes information used in analyzing the problem.Figure 10 12 shows the completed trader workspace




Figure 10-12 shows the completed trader workspace.

Figure 10-12 Trader workspace


The laredo workspace contains the information for laredo. The finalworkspace contains:




workspace contains:

– WebSphere Application Server statistics from ITCAM for WebSphere:CPU usage, memory usage, transaction rate, transaction response time.

– Response time information from ITCAM for Response Time Tracking thatshows the performance of the Trader servlets that run on theTraderClientWeb application.

– Web services client information from ITCAM for SOA: message rate andresponse time.

Figure 10-13 shows the completed laredo workspace.

Figure 10-13 Laredo workspace


The final bandung workspace contains this information for bandung:

WebSphere Application Server statistics from ITCAM for WebSphere




– WebSphere Application Server statistics from ITCAM for WebSphere:CPU usage, memory usage, transaction rate, transaction response time.

– Response time information from ITCAM for Response Time Tracking thatshows the performance of the Trader servlets that run on theTrader*Services applications. This is typically called directly from the Javaapplication as requests from laredo have been correlated to the callingservlets. Also, we monitor requests from Trader*Web applications.

– Web services client information from ITCAM for SOA: message rate andresponse time.

Figure 10-14 shows the completed bandung workspace.

Figure 10-14 Bandung workspace


The workspace is defined by dissecting the workspace area using the splitvertical button or split horizontal button. For each area, we then




p ,populate it with the appropriate type of portlet that we wanted to fit in.Figure 10-15 indicates the available components.

Figure 10-15 Portlet components

We describe the building of some of the workspace por tlets in the followingsections.

10.3.4 Defining Trader main view

The main view of the Trader workspace is similar to the Enterprise workspace inthe physical view. It contains the Situation Event Console and Message Log. Thisdisplay is adequate if you have already tuned your system and have theappropriate situations defined with the appropriate thresholds. When most of thedefinitions are valid, you should not get any false alarms or silent problems.

Both the message log and Situation Event Console are inserted into the area by

clicking the appropriate icon then clicking on the area you want to assign them.There is no real customization for these types of por tlets.

10.3.5 Defining bandung and laredo workspaces

The bandung and laredo workspaces shown in Figure 10-13 on page 405 andFigure 10-14 on page 406 are similar, so we discuss them together.

Data portlets are built from queries. However, the more query that we submit in a

single page, the more overhead it introduces to the system. In designing theportlets, we take into consideration the number of queries that we use and thepossibilities of using an IBM-supplied query.

Tivoli Enterprise Console

Table

Pie chart

Bar chart

Plot chart

Circular gauge

Linear gauge

Notepad

Message log

Situation event console

Universal message console

Graphic view

Take action

3270 terminal

Browser


Figure 10-16 shows our workspace with the areas identified.




Figure 10-16 Workspace areas

We used these queries for our bandung and laredo workspaces:

ITCAM for WebSphere information

From the WebSphere Application Server queries, we use the followingqueries:

– Application_Server attribute group, with the existing Application Serverquery. This query provides CPU usage percentage and memory usage

information (total, used, and free memory). The CPU usage is shown as acircular gauge, and the total memory and memory used in a bar chart.

– Request_Times_and_Rates attribute group, with the existing RequestTime and Rates query that provides average response time and requestrate information. These are displayed as linear gauges.

ITCAM for Response Time Tracking information

From the Response Time Tracking queries, we cannot use the availablequeries because the original workspaces are mostly accessed through links.

(See 5.11, “Working with Tivoli Enterprise Portal” on page 247.) Links collectinformation from previous stages to present information. We create newqueries, one for bandung and one for laredo, to present the information from

ITCAM for WebSphere

ITCAM for SOA

ITCAM for Response

Time Tracking


the ITCAM_TT_Policy_Status attribute group. We copy the Response TimeAgent Policy Status query to our own query. See “Creating a new query” on

http://-/?-

http://-/?-

http://-/?-

http://-/?-




page 416.

ITCAM for SOA information

From the Service Management Agent Environment, under theServices_Inventory attribute group, we can retrieve Web services information.We want to show the response time and invocation rate of Web services. Wecan either use two existing queries for the same attribute group, which meansthat data collection will be performed twice, or create a new query that selectsthe information that we need. We decided to create our own query to collectthe information that we use.

With this design, the workspace for bandung and laredo uses only four queries toretrieve information. One goes to ITCAM for Response Time Tracking agent, and

three go to the application server machine for execution by the ITCAM for SOAagent and ITCAM for WebSphere agent.

Setting a query portletThis is the procedure for setting a query portlet:

1. Select the appropriate portlet type from the toolbar and click on theworkspace area that you want to customize.

2. A prompt asks whether to assign a query (Figure 10-17). Click Yes.

Figure 10-17 Query assignment confirmation


3. The portlet setting page appears as shown in Figure 10-18. Click on Click here to assign a query.

http://-/?-

http://-/?-




Figure 10-18 Empty portlet property page


4. When you reach the Query Editor page, select the query that you want toassign. Or you can create a new query, as discussed in “Creating a newquery” on page 416 Figure 10 19 shows the example query for Request

http://-/?-

http://-/?-

http://-/?-

http://-/?-




query on page 416. Figure 10-19 shows the example query for RequestTimes and Rates. Click OK to select the query.

Figure 10-19 Query editor window


5. Back on the portlet property page, select the Filter tab, which enables you toselect the columns (attributes) that you want to be displayed on the portlet.Some portlets support multiple columns such as table bar and plot charts

http://-/?-

http://-/?-




Some portlets support multiple columns, such as table, bar, and plot charts,but gauges support only a single column. Select the column by checking it asshown in Figure 10-20. If your query is valid and there is an appropriateprovider for data, you will see a snapshot of data for the query for yourreference.

Figure 10-20 Portlet filter


6. You can customize the appearance of the portlet using the Style tab. First,change the heading text, which is provided on the initial page as shown inFigure 10-21.




Figure 10 21.

Figure 10-21 Heading text


7. Customize chart-specific attributes, such as:

– For circular gauge, customize the shape and value range of the data asshown in Figure 10 22




shown in Figure 10-22.

Figure 10-22 Circular gauge setting


– For linear gauge, customize the orientation and range of data as shown inFigure 10-23.




Figure 10-23 Linear gauge settings

– For bar chart, customize the orientation and axis labels as shown inFigure 10-24.

Figure 10-24 Bar chart settings


You can also change the legend text and position as shown inFigure 10-25.




Figure 10-25 Legend customization for bar chart

8. Click OK to save the portlet property and select File→ Save Workspace tosave the workspace.

Creating a new queryAs discussed in 10.3.5, “Defining bandung and laredo workspaces” on page 407,

we create a new query to optimize the workspace and provide data for ourportlet.

From the query editor, you can either create a completely new query or copyan exiting query . You must assign a name for the new query as shown inFigure 10-26.

Figure 10-26 Name for new query

The query specification defines both the selected attributes and the row selectionconditions. Some conditions are mandatory, and typically they are selected froma variable. A variable is specified by enclosing with $ signs. You can substitutethese variables with a fixed value. Conditions specified in the same row representan AND operation, and conditions specified on different rows represent an ORoperation. See sample specification in Figure 10-27 on page 417.





Figure 10-27 Query specification

The query for ITCAM for Response Time Tracking that we create copies from theexisting query shown in Figure 10-27. We modify the query because thePCYGRPID and PCYGRPNAME variables will not be available from a simpleworkspace. They can only be retrieved from a linked workspace. For laredo, weretrieve all Policies response time information for the policy inside theTrader_Web_appl policy group as shown in Figure 10-28.

Figure 10-28 Laredo policies


The policy group ID number can be retrieved from the ITCAM for Response TimeTracking dashboard report by hovering the cursor over the policy group to see thestatus bar as shown in Figure 10-29.




Figure 10-29 Getting policy group ID


The ITCAM for SOA query that we create selects only specific columns fromscratch from the Services_Inventory attribute group. Use the following procedure:

1. Create a new query from the Create Query button. Assign the name and




category of the query as shown in Figure 10-30.

Figure 10-30 Query name and category


2. Select the attributes that you want to collect as shown in Figure 10-31.




Figure 10-31 Query attributes


3. The query appears in the query editor window, where we provide theselection conditions. For the Services_Inventory attribute group, specify atleast Origin Node to be $NODE$. The condition that we use is shown inFigure 10-32.




g

Figure 10-32 Setting condition

4. You can further select the attributes to be included in the query by checking orunchecking the attributes. For attributes that you unchecked in a previoussession, you can add them by clicking the Add attributes button.

10.4 Workflows and situations

A situation is an automatic monitoring of the system that can be raised based ona certain condition. A situation runs in the background based on a predefined

interval. It is useful for getting basic health information from a Tivoli EnterpriseMonitoring Agent.

Workflow is also called policy; the terms are used interchangeably on the TivoliEnterprise Portal. Workflows enable some level of automation for IBM TivoliMonitoring V6.1.

This section discusses the creation of custom situations and incorporates theminto a workflow for monitoring our Trader application environment. As the

situation will be used in a workflow, these situations will not be auto-started. Onlythe workflow has to be auto-started, and this will start the situation.


The discussion in this section includes:

10.4.1, “Situation basics” on page 422 10.4.2, “Workflow basics” on page 422 10 4 3 “Trader workflow design” on page 424




10.4.3, Trader workflow design on page 424

10.4.1 Situation basics

A situation is a conditional expression that is evaluated at certain intervals. Thesituation can evaluate to true; this is considered as a situation change event.

Situation evaluates the attributes in an agent from an attribute group. As anattribute group is considered a table and attributes are its columns, the situationdefinition contains the following components:

The name of the situation The category of the situation The attribute group that will be evaluated The row selection condition from the attribute group

The selection condition can contain multiple expressions:

Filtering for certain types of data, such as servlet name, policy name, or otherattributes

Checking data value for a selected row. This checking can be considered athreshold for the data in the table. Some checking uses an aggregationfunction such as count, maximum, or minimum; this type of checking isperformed at the Tivoli Enterprise Monitoring Server.

10.4.2 Workflow basics

Workflows can automate and correlate several situations. A situation canevaluate attributes from only a single attribute group. Correlation from severalsituations is possible using workflow. This allows a more intelligent approach to

event analysis.

Table 10-1 shows workflow components.

Table 10-1 Workflow components

Component icon Description

Fire the situation collection when the policy executes. This doesnot create an additional collection of the situation.


Schedules the situation for collection. In IBM Tivoli MonitoringV6.1, the situations are removed from the synchronization

f

Component icon Description




Workflow can also be a huge source of overhead in situation processing. Thiscan be more than double the overhead of collecting data for situations becausethey duplicate the collection for the situation to drive alerts to the Tivoli Enterprise

Portal Server and may not be eligible for situation synchronization.

When three situations that are eligible for synchronization in one synchronizeddata collection are added to a workflow, the situation will not be collected in a

mechanism but if the original situation is collecting, this will notgenerate an additional collection.

Perform a predefined action for the situation or write a messageto the message log.

Suspend the execution of the workflow for a certain time range.

Start or stop a workflow. This can be used to trigger anotherworkflow to start (for example, to change workflow from workdaysto weekend workflow).

This can be used to start or stop a new situation to be executed.The new situation may be used to indicate a time-dependentthreshold.

Decision point that communicates a message to a group of users.When this is executed, someone has to answer the prompt todetermine whether the workflow will continue. This is availableonly for Candle Management Workstation users.

This is an extension component to wait for a situation to becomefalse.

Sending an SNMP event.


single synchronized collection. In IBM Tivoli Monitoring V6.1, these collectionswill be performed once for all instances of a situation.

In a workflow, the Evaluate a Situation Now activity does not actually start thesituation it just performs a one time sampling of data; however Wait Until A




situation, it just performs a one-time sampling of data; however, Wait Until ASituation is True activity does.

10.4.3 Trader workflow design

The workflow that is built for the Trader application is constructed based on thediagram in Figure 10-33. For a problem in response time, we want to pinpoint thesource of the problem, whether the front end, middle tier, or back end. Thisproblem comes from the fact that the front end uses the same servlet to accessdifferent back-end systems.

Figure 10-33 Trader workflow

To accomplish this workflow, we need to define 21 new situations for our sampleand a workflow. The rounded rectangles represent conditional situations; we

need two situations for each condition true and false. The raised rectanglesrepresent new events; each represents one new situation. Table 10-2 onpage 425 lists the new situations.

Trader Servlet response

time unacceptable

Web Services response

time for TraderIMSServices

Web Services response

time for TraderDBServices

Web Services responsetime for

TraderCICSServices

IMS request threshold

DB request threshold

CICS request threshold

Trader_IMS_Backend_Slow

Trader_IMS_WAS_Slow

Trader_CICS_Backend_Slow

Trader_CICS_WAS_Slow

Trader_DB_Backend_Slow

Trader_DB_WAS_Slow

TRUE TRUE

T

TRUE

TRUE

T

TRUE

TRUE

T

F

F

F

Trader_FrontEnd_SlowFALSE


Table 10-2 New situations list

Name Category Attribute group Condition

TraderServlet_slow Response TimeTracking

ITCAM_TT_PolicyStatus

Policy Group Name ==Trader Web appl




Tracking _Status Trader_Web_applPolicy Name == SCAN(Servlet)

Average Response Time >= 5

TraderIMS_WS_slow

ServiceManagementAgent Environment

Service_Inventory Service Name == TraderIMSServicesAverage Elapsed Message RoundTrip Time >=4000

TraderCICS_WS_slow


Service_Inventory Service Name ==TraderCICSServicesAverage Elapsed Message RoundTrip Time >=4000

TraderDB_WS_slow


Service_Inventory Service Name == TraderDBServicesAverage Elapsed Message RoundTrip Time >=4000

TraderIMS_req_pct WebSphere AppServer

Request_Analysis Request Detail =STR(2,TraderIMSServices)JCA Time (%) >= 70.0

TraderCICS_req_pct

WebSphere AppServer

Request_Analysis Request Detail =STR(2,TraderCICSServices)

JCA Time (%) >= 70.0

TraderDB_req_pct WebSphere AppServer

Request_Analysis Request Detail =STR(2,TraderDBServices)SQL Connect Time (%) >= 30.0SQL Query Time (%) >= 30.0SQL Update Time (%) >= 30.0

TraderServlet_recover

Response TimeTracking

ITCAM_TT_Policy_Status

Policy Group Name ==Trader_Web_appl

Policy Name == SCAN(Servlet)Average Response Time < 5

TraderIMS_WS_recover


Service_Inventory Service Name == TraderIMSServicesAverage Elapsed Message RoundTrip Time <4000

TraderCICS_WS_recover


Service_Inventory Service Name ==TraderCICSServicesAverage Elapsed Message RoundTrip Time <4000


TraderDB_WS_recover


Service_Inventory Service Name == TraderDBServicesAverage Elapsed Message RoundTrip Time <4000

Name Category Attribute group Condition




Agent Environment Trip Time <4000

TraderIMS_req_pct_recover WebSphere AppServer Request_Analysis Request Detail =STR(2,TraderIMSServices)JCA Time (%) < 70.0

TraderCICS_req_pct_recover

WebSphere AppServer

Request_Analysis Request Detail =STR(2,TraderCICSServices)JCA Time (%) < 70.0

TraderDB_req_pct_recover

WebSphere AppServer

Request_Analysis Request Detail =STR(2,TraderDBServices)SQL Connect Time (%) < 30.0

SQL Query Time (%) < 30.0SQL Update Time (%) < 30.0

TraderIMS_backend_slow

Universal Agent Universal_Time Hour>=0

TraderIMS_WAS_slow


TraderCICS_backe

nd_slow


TraderCICS_WAS_slow


TraderDB_backend_slow


TraderDB_WAS_slow


TraderWAS_frontend_slow



Defining situationsSituations are defined using the situation editor that is invoked using thebutton. From the situation editor main window shown in Figure 10-34, we createa new situation by right-clicking the appropriate category and selecting Create

New




New.

Figure 10-34 Situation editor


When the Create Situation dialog opens as shown in Figure 10-35, enter thename and description of the situation. Click OK.




Figure 10-35 New situation dialog

The next dialog enables you to select the attribute group and attributes that youwant to use for the situation. Just select the attributes that you want to evaluate.This dialog is shown in Figure 10-36.

Figure 10-36 Selecting attribute group and attributes


When the attributes have been selected, click OK to see the situation formuladefinition. You must specify your condition here and select the distribution list onthe next tab. The distribution list represents the Tivoli Enterprise MonitoringAgent that the situation will run on.

Figure 10 37 shows the ITCAM for Response Time Tracking situation




Figure 10-37 shows the ITCAM for Response Time Tracking situationcondition. Trader_Web_appl is the policy group where we collect the servletresponse time listening policies. The target is Primary:KHARTOUM:T2 node.

Figure 10-37 ITCAM for Response Time Tracking condition

Figure 10-38 shows the ITCAM for SOA situation condition. This exampleshows the TraderIMSServices as the filter with threshold of 4 seconds (4000milliseconds). The distribution is to D4:2b251f23:bandung-bandung1, whichis the ITCAM for SOA agent.

Figure 10-38 ITCAM for SOA condition


Figure 10-39 shows the ITCAM for WebSphere situation condition. We use asubstring to locate the TraderIMSServices and have the JCA percentagegreater than 70%. Distribution target isbandung1_AppSrv01_:BANDUNG:KYNS.




Figure 10-39 ITCAM for WebSphere condition

Figure 10-40 shows the ITCAM for WebSphere situation condition for a SQLrequest with TraderDBServices.

Figure 10-40 ITCAM for WebSphere for JDBC call condition

The Universal Message situation that we provide just to get an event uses analways true condition with an hour for the evaluation time. We use hour >= 0as the condition.


10.4.4 Defining workflow

Now that we have defined all of the new situations, we are ready to define theworkflow. You invoke the workflow editor using the workflow editor button .Figure 10-41 shows the initial workflow editor window.




Figure 10-41 Workflow editor initial window


Click the create new workflow button and specify the workflow name. Youwill be presented with the edit display as shown in Figure 10-42. If you shouldneed to get out and come back to the workflow editor, you can click the editworkflow button to start editing your workflow.




Figure 10-42 New empty Trader workflow

As indicated in Figure 10-33 on page 424, the workflow checks existing

situations that we define. First, we analyze the definition for the IMS application.Figure 10-43 on page 433 shows the workflow with only IMS components.





Figure 10-43 Workflow with only IMS components

As shown in Figure 10-43, we want to start and stop TraderIMS_WAS_slow,TraderIMS_backend_slow, or TraderWAS_frontend_slow, depending on thecondition. The primary indication is the TraderServlet situations: When theservlet response time exceeds the threshold, it starts the trigger of events. WhenTraderServlet response time drops below the threshold as indicated byTraderServlet_recover situation, all generated situations are stopped.

The decision about which component is slow—whether it is the front end, backend WebSphere Application Server, or the back end server—is based onTable 10-3.

Table 10-3 Condition for problem source

Problem source Servlet is slow Web services is

slow

JCA call

percentage high

Front end Yes No -

WebSphere ApplicationServer back end

Yes Yes No

Back end server Yes Yes Yes


We then added the components for the CICS and DB services. Figure 10-44 shows the recovery part for stopping the situations.




Figure 10-44 Completed workflow - recovery

Starting the situation is much more complex. We show the completed piecesseparately. Figure 10-45 shows the database portion. The external links are fromTraderServlet_slow situation.

Figure 10-45 Completed workflow - failure for database


Figure 10-46 shows the CICS portion; again the external links are fromTraderServlet_slow situation.




Figure 10-46 Completed workflow - failure for CICS

For the front-end failure, the CICS and DB Web services recover situations areused as shown in Figure 10-47.

Figure 10-47 Completed workflow - failure for front end


Figure 10-48 shows the overall workflow. This has been rearranged forreadability and display.




Figure 10-48 Completed workflow

Draft Document for Review March 1, 2007 5:22 pm 7151ax01.fm

A




Appendix A. Trader applicationdescription

This appendix discusses the sample Trader application set that we used to

perform the tests and scenarios in this book. The discussion in this appendixincludes:

“Managed application environment” on page 438

“Back-end systems” on page 439

“J2EE back-end system” on page 440

“Front-end J2EE Web application” on page 441

“Java desktop application” on page 444

7151ax01.fm Draft Document for Review March 1, 2007 5:22 pm

Managed application environment

The application environment is managed by all IBM Tivoli Composite ApplicationManagers. This application is based on the Trader application from ITSO, whichdepicts a fictional, simplified stock-trading application. The application hasseveral flavors with different back-end server systems. We put out front-end




systems that access these applications using Web services calls. Figure A-1 shows the overall application environment.

Figure A-1 Application environment

As shown in Figure A-1, the application consists of:

Front end application: J2EE Web application or Java desktop application.These modules perform Web services calls to the back-end J2EE application.

J2EE back-end systems that accept Web services calls and translate theminto native protocol (either JDBC, IMS Connect, or CICS Transaction Gatewaycalls).

Back-end transaction engine that provides the business logic and data

repository for the transactions.

The following sections discuss each of these components. All source code isprovided in the additional materials. See Appendix B, “Additional material” onpage 447 for information about downloading these files.

Web browser TraderClient.ear

TraderJavaClient.jar

TraderDBSvc.ear TRADER

DB2 database

TraderIMSSvc.ear TraderIMS

TraderCICSSvc.ear TraderCICS

W e b S e r v i c e s


Back-end systems

The back-end systems consists of two entities: the company and the customer.The company has the quotes definitions, and the customer database has thecustomer’s name and its stock ownership. Figure A-2 shows the conceptual datastructure.



Appendix A. Trader application description 439

Figure A-2 Entity diagram

The back-end system is implemented in the following platforms:

IMS: Implemented in a single IMS transaction called TRADERBL. CICS: Implemented in a single CICS transaction called TRADERBL. DB2: Implemented as two tables, the customer and company tables.

IMS implementation

A single transaction called TRADERBL represents the IMS implementation. Thistransaction, which is written in COBOL, reads the message that contains theappropriate command and arguments. The TRADERBL transaction accessestwo databases: company and customer.

CICS implementation

The CICS implementation consists of two programs:

TRADERPL: The presentation logic for a 3270 interface that can be invokedusing the TRAD transaction.

List company GetQuote Buy/Sell Stock

COMPANYCompany Name

Stock price

Price history 7 days

Commission

CUSTOMERCustomer Name

Company name

Stock owned


TRADERBL: The business logic for the Trader application that will be invokedfrom either the TRAD transaction or from a distributed CSMI transaction. Thistransaction uses two databases: CUSTFILE and COMPFILE.

DB2 implementation




The DB2 implementation is represented in two tables, the CUSTOMER table andthe COMPANY table.

J2EE back-end system

The Trader server J2EE applications are constructed of the following modules(the asterisk can be substituted with IMS, DB, and CICS respectively):

TraderLib: Common trading functions implementation Trader*Command: Utility project that serves as the interface implementation

to the back-end system

Trader*EJB*: Enterprise JavaBean implementation of the Trader resources

Trader*Web: Web browser interface to the Trader application; used for theoriginal trader application and for testing the Trader application connectivity

Trader*Services: Web services implementation of the Trader function

The Trader*Services module consists of a single Java class calledTrader*Services, which provides the ListCompany, GetQuotes, Sell, and Buymethods. The Java class is then externalized as Web services from WebSphereStudio Application Development Integrated Edition 5.1.1 by selecting: WebServices→ Generate WSDL files.

The client stub can be generated from the context of the generated wsdl file byselecting Web Services→ Generate Client.


Front-end J2EE Web application

The front-end Web application is developed using the Web services client wizardfrom WebSphere Studio Application Development from the Trader*Servicesprojects. The application consists of:

Initial login page in login.html (Figure A-3).




g g g g

Figure A-3 Login page

Note: The DB2, IMS, and CICS radio check boxes shown in Figure A-3 arenot normally available to an end user. They are included on our sampleapplication purely to highlight the possible back-end system. Similarly, atypical application would not select a target host, but this is shown here as partof our lab environment.


ListCompanyServlet (Figure A-4): Invokes the back-end ListCompany Webservices.




Figure A-4 List Company page


GetQuotesServlet (Figure A-5): Invokes the back-end GetQuote Webservices.




Figure A-5 Quotes window

BuySellServlet: Invokes either the Buy or Sell Web services.

LogoutServlet: Clears up the session bean.


Java desktop application

The desktop application is also developed from the Web services client wizardfrom WebSphere Studio Application Development. It is made of the followingJava classes:

TraderClientLogin.java: JDialog extension that provides the initial parameter

(Fi A 6)




(Figure A-6).

Figure A-6 Login dialog

TraderClientMain.java: Main JApplet that provides the list of companies(Figure A-7).

Figure A-7 Company listing


TraderClientQuote.java: Company quote window that allows invocation ofbuying or selling stock (Figure A-8).




Figure A-8 Quote window





Draft Document for Review March 1, 2007 5:22 pm 7151addm.fm

B




Appendix B. Additional material

This redbook refers to additional material that can be downloaded from theInternet as described below.

Locating the Web material

The Web material associated with this redbook is available in softcopy on theInternet from the IBM Redbooks Web server. Point your Web browser to:

ftp://www.redbooks.ibm.com/redbooks/SG247151

Alternatively, you can go to the IBM Redbooks Web site at:

ibm.com/redbooks

Select the Additional materials and open the directory that corresponds withthe redbook form number, SG247151.

7151addm.fm Draft Document for Review March 1, 2007 5:22 pm

Using the Web material

The additional Web material that accompanies this book includes the followingfiles:

File name Description

TradersWksp.zip Workspace of the original application

TradersARMWksp.zip Workspace of the instrumented application

ftp://www.redbooks.ibm.com/redbooks/





ftp://www.redbooks.ibm.com/redbooks/




ade s sp p Workspace of the instrumented applicationTradersEARs.zip Zipped application archives and Java archives

System requirements for downloading the Web material

Figure B-1 shows the system requirements.

Figure B-1 Application environment

The following system configuration is recommended for the developmentenvironment:

Hard disk space: 5 GB free space

Operating system: As required by WebSphere Studio ApplicationDevelopment Integrated Edition 5.1.1

Processor: Pentium® IV

Memory: 1 GB of RAM

Software: WebSphere Studio Application Development IntegratedEdition 5.1.1

`

WebSphere AppServer

`

WebSphere AppServer

DB2

`

Development machine

WSADIE 5.1.1

`

Application Client

Web browser

WebSphere AppClient

zSeries

CICS, IMS

CICS TG,

IMSConnect


The configuration is meant to be run on two WebSphere Application Serverenvironments with access to the back-end DB2, CICS, and IMS applications. Thefollowing system configuration is recommended for running the WebSphereApplication Server application environment:


Operating System: As required by WebSphere Application Server

Processor: As required by WebSphere Application Server



Appendix B. Additional material 449

Processor: As required by WebSphere Application Server

Memory: 1 GB of RAM

Software: WebSphere Application Server Version 5.1 or aboveDB2 Enterprise Server Edition V8.2

The back-end system runs z/OS Version 1.5 or later with the following softwarerunning:

IMS Transaction Manager V8.1 CICS Transaction Server V2.3 IMS Connect V2.3 CICS Transaction Gateway V5.1

The following system configuration is recommended for the front-end Java client:


Operating System: Windows 2000 SP4, Windows XP SP1 or Windows 2003

Processor: Pentium class

Memory: 512 MB of RAM

Software: WebSphere Application Server Application Client Version5.1 or above

The following system configuration is recommended for the Web browsersystem:

Operating System: Windows 2000 SP4, Windows XP SP1, or Windows 2003

Processor: Pentium class

Memory: 512 MB of RAM

Software: Microsoft Internet Explorer V6 or Mozilla Firefox V1

How to use the Web material

To work with the development environment, follow this procedure:

1. Install the WebSphere Studio Application Development Integrated Edition5.1.1 on your workstation.


2. Create a subdirectory and unzip the contents of either TradersWksp.zip orTradersARMWksp.zip into this folder.

3. Open WebSphere Studio Application Development Integrated Edition 5.1.1and specify the workspace directory of the subdirectory that you created instep 2.

4. Import the projects from the directory by selecting File→ Import, and specifyImport existing project into workspace. Import the following directories:




p g p j p p g

ECIConnectorIMSConnectorTraderLibTrader_DBTraderCICSCommandTraderCICSEJBTraderCICSEJB2

TraderCICSServicesTraderCICSWebTraderCICSEARTraderDBClientWebTraderDBEARTraderDBServicesTraderDBWebTraderDBClientEARTraderIMSCommand

TraderIMSEJBTraderIMSEJB2TraderIMSServicesTraderIMSWebTraderIMSEARTraderClientWebTraderClientEARTraderJavaClient

5. Rebuild all projects using Project→ Rebuild All. You should see severalwarning messages.

6. Export the projects into a staging directory using File→ Export, and selectEAR file to export the following projects:

TraderWebClientTraderIMSServicesTraderCICSServicesTraderDBServicesTraderIMSWeb

TraderCICSWebTraderDB


7. WebExport Java application into a staging directory using File→ Export, andselect Java archive file to export the TraderJavaClient project. Make sure toinclude itso.j2ee.trader.client.TraderClientMain as the main class.

To work with the sample application environment, follow this procedure:

1. Use the staging directory, either from the files in the development

environment or from the TradersEAR.zip file.2 F th d W bS h f th f ll i t k



Appendix B. Additional material 451

2. From the second WebSphere server, perform the following tasks:

a. Install the IMS connector: imsico.rar.

b. Install the CICS connector.

c. Install DB2 database JDBC connectivity.

d. Install TraderIMSSvc.ear or TraderIMSArmSvc.ear.

e. Install TraderCICSSvc.ear or TraderCICSArmSvc.ear.

f. Install TraderDBSvc.ear or TraderDBArmSvc.ear.

g. Restart the application server.

3. From the first WebSphere server, perform the following tasks:

a. Install the TraderClient.ear or TraderClientArm.ear.

b. Restart the application server.

4. At the back-end z/OS system, perform the following tasks:

a. Set up the TraderIMS application.

b. Set up IMS Connect.

c. Set up the TraderCICS application.

d. Set up the CICS Transaction Gateway.

5. For the Java application front-end setup:

a. Install the WebSphere Application Server Application Client.

b. Run TraderJavaClient.jar.





Draft Document for Review March 1, 2007 5:22 pm 7151abrv.fm

AIX Advanced InteractiveExecutive

APF Authorized Program Facility

Abbreviations and acronyms

ISM Internet Service Monitoring

ITCAM IBM Tivoli CompositeApplication Monitor




API Application ProgrammingInterface

ARM Application ResponseMeasurement

ASM Application Service Monitor

BCM Byte Code Modification

CAT Client Application TrackerCD-ROM Compact Disk - Read-Only

Memory

CICS Customer Information ControlSystem

CLI Command Line Interface

CPU Central Processing Unit

DASD Direct Access Storage Device

DB2 Database 2™

EJB Enterprise Java Bean

ETE End to end

FFDC First Failure Data Capture

FMID Function ModificationIdentifier

GLUE Global User Exit

GUI Graphical User InterfaceHFS Hierarchical File System

HTML Hypertext Markup Language

HTTP Hypertext Transfer Protocol

HTTPS HTTP Secure

IBM International BusinessMachine Corp.

IMS Information Management

SystemIPL Initial Program Load

ITIL Information TechnologyInfrastructure Library

ITM IBM Tivoli Monitoring

ITSO International TechnicalSupport Organization

J2C Java 2 Connector

J2EE Java 2 Enterprise EditionJAR Java archive

JAX-RPC Java API for XML-basedRemote Procedure Call

JCL Job Control Language

JDBC Java Database Connectivity

JES2 Job Entry Subsystem 2

JMX Java Management Extension

JNI Java Native Interface

JRE™ Java Runtime Environment

JVM Java Virtual Machine

JVMPI Java Virtual Machine ProfilerInterface

JVMTI Java Virtual Machine ToolInterface

LDAP Lightweight Directory AccessProtocol

MSC Multi-system Coupling

MVS Mulitple Virtual Storage

OTMA Open Transaction ManagerAccess

PCB Program Control Block

PDF Portable Document Format

PLT Program List Table

7151abrv.fm Draft Document for Review March 1, 2007 5:22 pm

PMI Performance ManagementInterface

RACF® Resource Access ControlFacility

RMI Remote Method Invocation

RTE Runtime Environment

SCA Service ComponentA hit t

WRM Web Response Monitor

WSDL Web Services DefinitionLanguage

XML Extensible Markup Language




Architecture

SMF System Measurement Facility

SMP/E System ModificationProgram/Extended

SNMP Simple Network ManagementProtocol

SOA service-oriented architecture

SOAP Simple Object AccessProtocol

SQL Structured Query Language

SSH Secure Shell

SSL Secure Socket Layer

SSM System Service Monitor

STI Synthetic Transaction

InvestigatorSYSPLEX System Complex

TCP/IP Transmission Control Protocol

TEMA Tivoli Enterprise ManagementAgent

TEMS Tivoli Enterprise MonitoringServer

TEP Tivoli Enterprise Portal

TEPS Tivoli Enterprise Portal Server

TRUE Transaction User Exit

TSO Time Sharing Option

UDB Universal Database

UML Universal Markup Language

URI Universal Resource Identifier

URL Universal Resource Locator

USS UNIX System ServicesWLM Workload Manager

Draft Document for Review March 1, 2007 5:22 pm 7151bibl.fm

Related publications

The publications listed in this section are considered particularly suitable for a

more detailed discussion of the topics covered in this redbook.




IBM Redbooks

For information about ordering these publications, see “How to get IBMRedbooks” on page 458. Note that some of the documents referenced here maybe available in softcopy only.

End-to-End e-business Transaction Performance with IBM TMTP 5.1,SG24-6912

Getting Started with IBM Tivoli Monitoring V6.1 , SG24-7143

IBM Tivoli OMEGAMON V3.1.0 Deep Dive on z/OS , SG24-7155

Implementing OMEGAMON XE for Messaging V6.0 , SG24-7357

Installing WebSphere Studio Application Monitor V3.1, SG24-6491

WebSphere Studio Application Monitor V3.2 Advanced Usage Guide ,SG24-6764

Large-Scale Implementation of IBM Tivoli Composite Application Manager ,REDP-4162

Solution Deployment Guide for IBM Tivoli Composite Application Manager for WebSphere , SG24-7293

Deployment Guide Series: IBM Tivoli Composite Application Manager for

WebSphere V6.0 , SG24-7252

Other publications

These publications are also relevant as further information sources:

IBM Tivoli Composite Application Manager for Response Time Trackingpublications

– IBM Tivoli Composite Application Manager for Response Time Tracking V6.1 Program Directory for z/OS , GI11-4099

– IBM Tivoli Composite Application Manger for Response Time Tracking

V6.1 Installation and Configuration Guide , GC32-9482

7151bibl.fm Draft Document for Review March 1, 2007 5:22 pm

– IBM Tivoli Composite Application Manager for Response Time Tracking V6.1 Administrators Guide , SC32-9483

– IBM Tivoli Composite Application Manager for Response Time Tracking

V6.1 Checking Performance and Availability , SC32-9484


V6.1 Command Reference Guide , SC32-9485

– IBM Tivoli Composite Application Manager for Response Time Tracking V6 1 Prerequisites SC32 9486



456 IBM Tivoli Composite Application Manager V6.1 Family Installation, Configuration and Basic

V6.1 Prerequisites , SC32-9486


V6.1: Installing a Management Server in a WebSphere Cluster Environment , SC32-1804

– IBM Tivoli Composite Application Manager for Response Time Tracking V6.1 Problem Determination Guide , SC32-9513

IBM Tivoli Composite Application Manager for CICS and IMS transactionpublications

– IBM Tivoli Composite Application Manager for CICS Transactions V6.1Product Guide , SC32-9510

– IBM Tivoli Composite Application Manager for IMS Transactions V6.1Product Guide , SC32-9511

IBM Tivoli Composite Application Manager for WebSphere publications

– IBM Tivoli Composite Application Manager for WebSphere Installation and Customization Guide , GC32-9506

– IBM Tivoli Composite Application Manager for WebSphere User’s Guide ,SC32-9507

– IBM Tivoli Composite Application Manager for WebSphere Operator’s

Guide , SC32-9508

– IBM Tivoli Composite Application Manager for WebSphere Problem

Determination Guide , SC32-9509

– IBM Tivoli Composite Application Manager for WebSphere: Tivoli Enterprise Monitoring Agent Problem Determination Guide , SC32-1800

– IBM Tivoli Composite Application Manager for WebSphere: Installing and

Configuring the Tivoli Enterprise Monitoring Agent , SC32-1801

IBM Tivoli Composite Application Manager for SOA publications

– IBM Tivoli Composite Application Manager for SOA Program Directory ,GI11-4087

– IBM Tivoli Composite Application Manager for SOA Release Notes ,GI11-4096

Draft Document for Review March 1, 2007 5:22 pm 7151bibl.fm

– IBM Tivoli Composite Application Manager for SOA Installation and User's Guide , GC32-9492

– Configuring IBM Tivoli Composite Application Manager for SOA on z/OS ,SC32-9493

– Installing and Troubleshooting IBM Web Services Navigator , GC32-9494

IBM Tivoli Monitoring publications– Introducing IBM Tivoli Monitoring , GI11-4071



Related publications 457

– IBM Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring ,GC32-9462

– IBM Tivoli Monitoring Installation and Setup Guide , GC32-9407

– IBM Tivoli Monitoring User's Guide , SC32-9409

– IBM Tivoli Monitoring Administrator's Guide , SC32-9408

– Configuring IBM Tivoli Enterprise Monitoring Server on z/OS , SC32-9463

– IBM Tivoli Monitoring Problem Determination Guide , GC32-9458

– Exploring IBM Tivoli Monitoring , SC32-1803

– IBM Tivoli Universal Agent User's Guide , SC32-9459

– IBM Tivoli Universal Agent API and Command Programming Reference Guide , SC32-9461

Online resources

These Web sites are also relevant as further information sources:

Product prerequisites information

http://publib.boulder.ibm.com/tividd/td/ITCAMRTT/prereq61/en_US/HTML/Version61.htmlhttp://publib.boulder.ibm.com/tividd/td/ITCAMWAS/prereq61/en_US/HTML/itcam6

.html Product Web pages

http://www-306.ibm.com/software/tivoli/products/composite-application-mgr-rtt/http://www-306.ibm.com/software/tivoli/products/composite-application-mgr-websphere/http://www-306.ibm.com/software/tivoli/products/composite-application-mgr-soa/

Open group Web site for Application Response time Managementhttp://www.opengroup.org/arm

7151bibl.fm Draft Document for Review March 1, 2007 5:22 pm

Microsoft link for InstallShield error


Microsoft Windows Services for UNIX


Java specification for JAX-RPC


BEA WebLogic interceptor information

http://publib.boulder.ibm.com/tividd/td/ITCAMRTT/prereq61/en_US/HTML/Version61.html


http://publib.boulder.ibm.com/tividd/td/ITCAMWAS/prereq61/en_US/HTML/itcam6.html


http://www-306.ibm.com/software/tivoli/products/composite-application-mgr-rtt/


http://www-306.ibm.com/software/tivoli/products/composite-application-mgr-websphere/




http://www.opengroup.org/arm

http://www.opengroup.org/arm








http://www.jcp.org/aboutJava/communityprocess/final/jsr109

http://www.jcp.org/aboutJava/communityprocess/final/jsr109





458 IBM Tivoli Composite Application Manager V6.1 Family Installation, Configuration and Basic

BEA WebLogic interceptor information

http://e-docs.bea.com/wls/docs81/webserv/interceptors.html

Eclipse Web site

http://www.eclipse.org

How to get IBM RedbooksYou can search for, view, or download Redbooks, Redpapers, Hints and Tips,draft publications and Additional materials, as well as order hardcopy Redbooksor CD-ROMs, at this Web site:

ibm.com/redbooks

Help from IBMIBM Support and downloads

ibm.com/support

IBM Global Services

ibm.com/services

Draft Document for Review March 1, 2007 5:22 pm 7151IX.fm

Index

Symbols$NCHOME/ism/bin/ism_startup.sh command 275./install.sh 307

availability management 4

Bback-end system 439b h t 415


http://www.eclipse.org/



http://www.ibm.com/support/


http://www.ibm.com/services/


http://www.eclipse.org/











Aaction method 296add-aa.sh 22AddFltrCntrl 296AddMntrCntrl 296add-ps.sh 22adduser command 58

agent 401agent communication 155Agent group 121agent group 121–122alerts 403am.home 357am_stderr.log 23am_stdout.log 23am-check.sh 22amctl.sh 22

am-start.sh 22am-stop.sh 22apachectl 23apachectl command 23APF 347application environment 438Application Response Measurement, see ARMapplication server 14Application Service Monitor, see ASMapplication support installation 299Application_Server 408applications health 2archive agent 17, 26ARM 114, 118, 230

correlator 119specification 118

armjni4.jar 120ASM 7ASSR1 378

attribute 294, 318attribute group 294authenticate 23

bar chart 415base RTE 382BCM 19BPEL 167Business Process Execution Language, see BPELByte Code Modification

See BCM

CCandle Installation and Configuration AssistanceTool

See CICATCANSD4 388CICAT 379CICS 16, 370

Global user exit 370task-related user exit 370

TRADERBL 440TRADERPL 439transaction SAMC 370

CICS data collector 116CICS SYSIN 372circular gauge 414client-side interception 289commands

$NCHOME/ism/bin/ism_startup.sh 275./install.sh 307adduser 58am-start.sh 22apachectl 23configMa.sh 360createArmLinks.sh 361createcfg.sh 350dcctl.sh 23DCOMCNFG 164dcomcnfg 144–145

enableprobes 369extattr 376groupadd 271

7151IX.fm Draft Document for Review March 1, 2007 5:22 pm

install.sh 47, 49, 152ism_startup.sh 276itmcmd.sh 46itmconfig 256KD4configDC 310KD4configDC.sh 310launchpad 31, 131

launchpad.sh 131ls 376nco_m_ssmagent 255

CYN$PTCY 372CYN1 subsystem 346

definition 346CYN1FU83 347CYN1PROC 346CYNIMSIN 375cynlogging.properties 21, 370

DDashboard Edition (DE) 397




NETMON 378obey 378passwd 58prepConfig.sh 359–360RDEF 346runNavigator 315runNavigator.bat 315

setenv.sh 26SETPROG 347, 371, 375, 388SETROPTS 346SETSSI 346setup.exe 306setup_DC_w32 31, 36setup_MS 131setupcics.sh 350, 371setupEnv.sh 359setupims.sh 375–376

setupwas.sh 353smit 58start_tmtpd.sh 361tapmagent 115tar 150tdl 238telnet 35ws_setup.sh 255wsadmin 255

commands prepConfig.sh 359composite applications 2configMa.sh 360configMa.sh command 360correlator 119createArmLinks.sh 361createArmLinks.sh command 361createcfg.sh command 350cross-memory services 18cross-products integration 392

CSMI 440CT engine 379cyaneaGpsCounter.txt 22

Dashboard Edition (DE) 397data collector 15, 296

CICS 16, 370IMS 16J2EE 16

data collector, see DCdatabase connection pools 15datacollector.env 350, 371datacollector.policy 21datacollector.properties 22, 350, 371DB2 UDB 17db2admin 29db2fenc1 29db2inst1 29DC 296dcctl.sh 23dcctl.sh command 23

DCOMCNFG command 164dcomcnfg command 144–145deep dive 392DelFltrCntrl 296DelMntrCntrl 296Denial of Service (DoS) 325DFHPLTCY 372DFSMSCE0 374DFSYIOE0 374digital stop-watch 119

DisableDC 296Discovery 121discovery 121discovery and listening schedule 181discovery policy 125DISPLAY environment variable 145

EEclipse environment 315Eclipse perspective 315EJB 15EJB usage 15


empty workspace 403EnableDC 296enableprobes command 369enableprobes.sh 369Enterprise Java Bean

See EJBextattr command 376

FFaults Summary workspace 294

IBM Tivoli Monitoring services 297ICHRIN03 346IEFSSN 346IEFU83 347implementation

ITCAM for SOA 296ITCAM for WebSphere 24

import wizard 299IMS 16TRADERBL 439



Index 461

Faults Summary workspace 294FFDC 355file systems 130First Failure Data Collector

See FFDCFirst Failure Data Collector, see FFDCflow pattern view

Web Services Navigatorflow pattern view 291

FMID 379full RTE 382

Gglobal publishing server 17Global user exit

See GLUEGlobal user exit, see GLUE

GLUE 370gpsCounter.txt 22groupadd command 271

HHFS 355Hierarchical File System

See HFSHierarchical File System, see HFS

historical collection configuration 95HKCI310 379HKD4600 379HKDS360 379HKLV190 379HWTP600 348, 359HWTP60A 348, 359

IIBM HTTP Server 17IBM supplied query 407IBM Tivoli Monitoring 151

IMS data collector 117in-context launch 392in-flight request search 85Information Technology Infrastructure Library, seeITILInitial Heap size 356initial program load

See IPLinstall.sh 152install.sh command 49installation option 29IO PCB 374IP

PIPE 154IPL 346ism_startup.sh command 276ISPF/PDF 379

IT infrastructure 3ITCAM for CICS Transactions

datacollector.env 350, 371datacollector.properties 350, 371

ITCAM for Response Time Trackingagent group 121agent group definition 184components 110deep dive 392distributed management agent installation 144file systems 130implementation overview 123implementation procedure 123in-context launch 392installation 131management agent 114, 126management agent on z/OS 358management resources 120management server 111

management server installation 130management server installation options 125monitoring component 126, 159


policy group 121schedule 180store-and-forward agent 113store-and-forward agent installation 140terminology 120Tivoli Enterprise Monitoring Agent 117, 151

ITCAM for SOA 289

action 296, 321application support 297application support installation 299tt ib t 294

TOP reports 71trap-and-alert facility 65usage 62

ITCAM_TT_Policy_Status 409ITIL 3itmcmd.sh command 46itmconfig command 256

JJ2EE 16




attribute 294components 288data collector 288enabling 309features 286filters 321implementation 296

metrics 318monitoring agent 298monitoring agent installation 306planning 297sample workflow 325server-side interception 289situation 294Tivoli Enterprise Monitoring Agent 288usage 317viewer 288

workspace 286, 292z/OS consideration 378

ITCAM for WebSpherearchive agent 26composite transaction 80data collector 18database 18historical collection 95historical information 93implementation process 24in-flight request 85installation 30installation option 29JVM size 26managing server 16memory size 25monitoring level 21publish server 26scenario 62

server activity 68sizing 25Tivoli Enterprise Portal 88

J2EE application server 14Java API for XML-based Remote Procedure Call

See JAX-RPCJava API for XML-based Remote Procedure Call,see JAX-RPCJava Native Interface

See JNIJava Virtual Machine

See JVMJava Virtual Machine Tool Interface, see JVMTIJava Virtual Machine, see JVM

java.security.policy 357JAX-RPC 288JAX-RPC handler 289

jiti.properties 21JNI 120, 374

JVM 114, 349, 374JVM size 26JVM thread pools 15JVMPI 367

jvmpiagents.properties 367JVMTI 14

KKCIINST 379KD4configDC command 310

KD4configDC.sh 310KD4configDC.sh command 310KD4USSJB 388KDSPROC1 388KDSPROC2 388kernel parameters 130kernels 17kwjdc.properties 22

LLaunch in Context 393


configuration 393launchpad command 31, 131launchpad.sh command 131libarmjni.so 369LIBPATH 357libvirt.so 369linear gauge 415

Listening monitor 121listening monitor 121listening policy 125LNKLST 347

MessageArrivalCritical 325Messages Summary workspace 294metrics 318MINLIFTIM 378monitoring agent installation 306monitoring component 126

deployment 159

Monitoring on demand 20monitoring on demand 20msg--cicsprobe.log 373msg cicsprobe log 373



Index 463

LNKLST 347Log Assembler tool 299Long Term History 94ls command 376

Mmanaged systems 401

management agent 116ARM agent 115difference 114distributed installation 144generic window component 115ITCAM for Response Time Tracking 114J2EE instrumentation 115mainframe 116Quality of Service 115

z/OS installation 358management resourcesITCAM for Response Time Tracking 120

management server 111clustered 112installation options 125

management server installation 130managing server 15–16

archive agent 17, 26global publishing server 17

installation 30kernels 17message dispatcher 17publish server 26publishing servers 17

Maximum Heap size 356Mediation Configuration 286Message arrival 286Message Arrival Summary workspace 293message dispatcher 17

Message Log 407MessageArrivalClearing 325

msg-cicsprobe.log 373msg--cicsprobe-native.log 373msg-cicsprobe-native.log 373msg-dc.log 23msg-dc-native.log 23msg--imsprobe.log 377msg-imsprobe.log 377

msg--imsprobe-native.log 377msg-imsprobe-native.log 377msg-ma.log 369msg-zprobe.log 23msg-zprobe-native.log 23

Nnavigation tree 397

building 399

nco_m_ssmagent command 255netcool 271NETMON command 378NLSPATH 357

Oobey command 378OCTIGATE database 18OMEGAMON DE 397OPAL 256

open group 118Open Process Automation Library, see OPALOpen Transaction Manager Access

See OTMAOracle 17OTMA 374

Ppasswd command 58

PCYGRPID 417PCYGRPNAME 417


performance consideration 397Performance Management Interface, see PMIPerformance Monitoring Infrastructure 45Performance Summary workspace 294persistent data store 387playback schedule 181PLT 372

PMI 14policy 421policy group ID 418portlets 400

SSAMC 370SCA 287, 292Schedule 121SCYNAUT3 375SCYNAUTH 347SCYNPROC 347

SCYNSAM3 375secure shellSee SSH

Secure Socket Layer see SSL




portlets 400PR end 374PR start 374prepConfig.sh 359–360primary workspace 317PROG 347publishing servers 17, 26

Qquery 407query portlet 409

RRACF 346

STARTED class 346Rational Application Developer 315

Rational Software Architect 315RDEF command 346Redbooks Web site 458

Contact us xxixReport 21report 21Reporting group 122reporting group 121Request_Times_and_Rates 408RKANMOD 388

RKANMODL 388RKANSAM 388Robotic monitor 121robotic monitor 121role definition 189root-cause 3rotate-apache-logs.sh 23RTE 379runNavigator command 315runNavigator.bat 315runtime environment

See RTE

Secure Socket Layer, see SSLserver activity display 68Server configuration 21server configuration 21Server group 21server group 21server-side interception 289

Service Component Architecture, see SCAservice extension 289Service Management Agent 286Service Management Agent Environment 286Service Management Agent workspace 293service topology view 291service-oriented architecture

See SOAservice-oriented architecture, see SOAServices Management Agent Environment 293

Services_Inventory 409Services_Inventory table 295Services_Message_Metric 331Services_Metric table 295setenv.sh 23, 26SETPROG command 347, 371, 375, 388SETROPTS command 346SETSSI command 346setup.exe 306setup_DC_w32 command 31, 36setup_MS command 131setupcics.sh 350, 371setupEnv.sh 359setupims.sh 375–376setupwas.sh command 353sharing RTE 382Short-Term History 94Simple Network Management Protocol

See SNMP

Simple Network Management Protocol, see SNMPSimple Object Access ProtocolSee SOAP


Simple Object Access Protocol, see SOAPsituation 294, 421Situation Event Console 407SMF exit 347smit command 58SMP/E 379SNMP 7, 17

SOA 286SOAP 288, 290SSH 35SSL 130

TR start 374trace--cicsprobe.log 373trace-cicsprobe.log 373trace--cicsprobe-native.log 373trace-cicsprobe-native.log 373trace-dc.log 23trace-dc-native.log 23

trace--imsprobe.log 377trace-imsprobe.log 377trace--imsprobe-native.log 377trace-imsprobe-native.log 23, 377



Index 465

SSL 130start_tmtpd.sh 361start_tmtpd.sh command 361STARTED class 346STI 115, 173store-and-forward agent 113

installation 140

Sun Solaris 17Synthetic Transaction Investigator

See STISynthetic Transaction Investigator, see STISystem Modification Program/Extended

See SMP/E

Ttapmagent 115–116tar command 150task-related user exit

See TRUEtask-related user exit, see TRUETCPCNNSRV 378tdl command 238telnet command 35terminology

ITCAM for Response Time Tracking 120Tivoli Data Warehouse 151

Tivoli Enterprise Monitoring Agent 151Tivoli Enterprise Monitoring Server 152warehouse proxy 310

Tivoli Enterprise Portal 88, 152, 396navigation tree 397policy 421query 407situation 421workflow 421

Tivoli Enterprise Portal Server 152

TOP reports 71TR end 374

trace imsprobe native.log 23, 377trace-zprobe.log 23TRAD 439Trader 437

application environment 438BuySellServlet 443company database 439

customer database 439GetQuotesServlet 443ListCompanyServlet 442login.html 441LogoutServlet 443TraderClientLogin 444TraderClientMain 444TraderClientQuote 445

TRADERBL 439–440TRADERPL 439

transaction flows view 291trap-and-alert facility 65TRUE 370

UUML 291Universal Markup Language (UML) 291Universal Markup Language, see UMLUNIX System Services (USS) 348, 388

updateLogging 296updateTracing 296UpdMntrCntrl 296

WWAREHOUS database 313warehouse proxy 310Web Response Monitor, see WRMWeb services call 317, 438Web Services Definition Language

See WSDLWeb Services Definition Language, see WSDL


Web Services Navigator 288, 290import wizard 299installation 315service topology view 291transaction flows view 291usage 325

Web Services Profiling 299

WebSphere Application Server Node Deployment112WebSphere Caching Proxy 113, 140WebSphere Edge Server 112




p gWebSphere Studio Application Development Inte-grated Edition 440Windows user rights 144WLM 344, 346workflow 421workflow design 424

Workload ManagerSee WLM

Workload Manager, see WLMworkspace 286, 407

performance consideration 397WRM 115, 218ws_setup.sh command 255wsadmin command 255WSCFG1 378WSDL 288

XX-Windows 145

Zzos.properties 360

T o d e t er mi n e t h e s pi n ewi d

t h of a b o ok

s m o o t h wh i c h h a s aP P I of 5 2 6 .Di v i d e

t h e b o ok an d h i d e t h e o t h e

r s : S p e ci al

b o ok b y o p eni n g t h e b o ok

f i l ewi t h t h

Dr af t D o c um en t f or R ev

i ew

M ar c h



k , y o u d i v i d e t h e p a p er P P I i n t o t h en um b er of p a g

e s i n t h e b o ok .A n ex am pl ei s a2 5 0 p a g e b o ok u s i n gP l ai nf i el d o p a q u e 5 0 #

e d 2 5 0 b y 5 2 6 wh i c h e q u al s a s pi n ewi d t h of .4 7 5 2

" .I n t h i s c a s e , y o uw o ul d u s e

t h e. 5 ” s pi n e.N ow

s el e c t t h e S

pi n ewi d t h f or

> C on d i t i on al T ex t > S h ow / Hi d e > S pi n e S i z e ( - - >Hi d e: ) > S e t .M ov e t h e c h an g e d C on d i t i on al t ex t s e t t i n g s t o al l f i l e s i n y o ur

h e s pi n e.f m s t i l l o

p en an d F i l e >I m p or t >F or m a

t s t h e C on d i t i on al T ex t S e t t i n g s ( ONL Y ! ) t o t h e b o ok f i l e s .

h1 ,2 0 0 7 5 : 2 2 pm

7 1 5 1 s pi n e

.f m

4 6 7

( 0 .1 ” s pi n e )

0 .1 ” <-> 0 .1 6 9 ”

5 3 <-> 8 9 p a g e s

( 0 .2 ” s pi n e )

0 .1 7 ” <-> 0 .4 7 3 ”

9 0 <->2 4 9 p a g e s

( 0 . 5 ” s pi n e )

0 .4 7 5 ” <-> 0 . 8 7 5 ”

2

5 0 <->4 5 9 p a g e s

( 1 . 0 ” s pi n e )

0 . 8 7 5 ” <->1 .4 9 8 ”

4

6 0 <->7 8 8 p a g e s

( 1 . 5 ” s pi n e )

1 . 5 ” <->1 . 9 9 8 ”

7 8 9 <->1 0 5 1 p a g e s

I B M T i v o l i C o m p o s i t e A p p l i c a t i o n M a n a g e r V

6 .1 F a mi l y

I B M T i v o

l i C o m p o s i t e A p p l i c a t i o n M a n a

g e r V 6 .1

F a mi l y I n

s t a l l a t i o n , C o n

f i g u r a t i o n a n d B a s i c U s a g e

I B M

T i v o l i C o

m p o s i t e

A p p

l i c a t i o n M a n a g e r

V 6 .1

F a m

i l y I n s t a l l a t i o n ,

I B M T i v o l i C

o m p o s i t e A p p l i c a t i o n M a n a g e r V 6 .1 F a

mi l y I n s t a l l a t i o n ,

T o d e t er mi n e t h e s pi n ewi d

t h of a b o ok

s m o o t h wh i c h h a s aP P I of 5 2 6 .Di v i d e

t h e b o ok an d h i d e t h e o t h e

r s : S p e ci al >

b o ok b y o p eni n g t h e b o ok

f i l ewi t h t h

Dr af t D o c um en t f or R ev

i ew

M ar c h A A



( 2 . 0 ” s pi n e )

2 . 0 ” <->2 .4 9 8 ”

1 0

5 2 <->1 3 1 4 p a g e s

( 2 . 5 ” s pi n e )

2 . 5 ” <->nnn.n”

1 3 1 5 <->nnnn p a g e s

k , y o u d i v i d e t h e p a p er P P I i n t o t h en um b er of p a g e s i n t h e b o ok .A n ex am pl ei s a

2 5 0 p a g e b o ok u s i n gP l ai nf i el d o p a q u e 5 0 #

e d 2 5 0 b y 5 2 6 wh i c h e q u al s a s pi n ewi d t h of .4 7 5 2

" .I n t h i s c a s e , y o uw o ul d u s e

t h e. 5 ” s pi n e.N ow

s el e c t t h e S

pi n ewi d t h f or

> C on d i t i on al T ex t > S h ow / Hi d e > S pi n e S i z e ( - - >Hi d e: ) > S e t .M ov e t h e c h an g e d C on d i t i on al t ex t s e t t i n g s t o al l f i l e s i n y o ur

h e s pi n e.f m s t i l l o

p en an d F i l e >I m p or t >F or m

a t s t h e C on d i t i on al T ex t S

e t t i n g s ( ONL Y ! ) t o t h e b o ok

f i l e s .

1 ,2 0 0 7 5 : 2 2 pm

7 1 5 1 s pi n e

.f m

4 6 8

IB M

T i v o l i C o m p o s i t e

A p p l i c a t i o

n M a n a g e r

V 6 .1 F a mi

l y I n s t a

l l a t i o n ,

IB M

T i v o l i C o m p o s i t e

A p p l i c a t i o

n M a n a g e r

V 6 .1 F a mi

l y I n s t a

l l a t i o n ,



® Draft Document for Review March 1, 2007 5:22 pm

IBM Tivoli CompositeApplication Manager V6.1FamilyInstallation Configuration and Basic Usage

Back cover



SG24-7151-01 ISBN

INTERNATIONALTECHNICALSUPPORTORGANIZATION

BUILDING TECHNICALINFORMATION BASED ONPRACTICAL EXPERIENCE

IBM Redbooks are developed bythe IBM International TechnicalSupport Organization. Expertsfrom IBM, Customers andPartners from around the worldcreate timely technicalinformation based on realisticscenarios. Specificrecommendations are providedto help you implement IT

solutions more effectively inyour environment.

For more information:ibm.com /redbooks

Installation, Configuration and Basic Usage

Managing response

time and transaction

Monitoring J2EE

application servers

Collecting Web

Services information

This IBM® Redbook describes the IBM Tivoli® Composite Application

Manager family of products. The Composite Application Manager

currently consists of:

- ITCAM for WebSphere and ITCAM for J2EE

- ITCAM for Response Time Tracking

- ITCAM for SOA

- ITCAM for Internet Service Monitoring

- ITCAM for J2EE Operations

- ITCAM for CICS Transactions and ITCAM for IMS Transactions

The aim of the Composite Application Manager is to simplify and

enhance distributed application management. Application

components can reside on multiple servers, across differentplatforms and J2EE™ environments, even through mainframes. The

complexity of understanding and solving application-related

problems, typically around performance issues, requires a cohesive

set of tools to be able to provide an end-to-end view of the

application.

The discussion that we provide in this book mainly consists of basic

installation and configuration of the products. The discussion is aimed

at augmenting the information provided in the product manuals.

Readers should consult the appropriate product manual beforestarting to implement these products.

Usage scenarios are provided in this book as a demonstration of

using these products in our sample environment. We use a single

application environment that can be managed by all of the products.







IBM Tivoli Composite Application Manager Family Version 6.1 - Installation, Configuration and Basic...

Documents

Transcript of IBM Tivoli Composite Application Manager Family Version 6.1 - Installation, Configuration and Basic...