Home

End-to-End e-business Transaction Management

1. 000 0c cece 474 Abbreviations and acronyms 0 00 e eee ee 475 Related publications 0 0 e eee ee 479 IBM REdDOOKS 24 eh ecard pa hare ead Gade Se Oe eee awh Ges eee aes 479 OthEPreSOUrceS ora cne aed tad aaalo duh aah waite oda oe Y meee ea ees 480 Referenced Web sites 000 ccc eee tees 481 How to get IBM Redbooks 0 0 tees 482 IBM Redbooks collections 000 0c eee eee eee 482 Help trom IBM n io aeres ainean ee ee eee ee E eae 482 MJEK ac5 cnc ass RTE RSPR ee OS hae een Saal 483 Contents vii viii End to End e business Transaction Management Made Easy Figures A OMONAGTAoOND 4 P a a a a a a k UN O PPDa On 2 4 2 5 2 6 2 7 2 8 2 9 2 10 2 11 2 12 3 1 3 2 3 3 3 4 3 7 Transaction breakdown 00 0000 eee 4 Growing infrastructure complexity 0000 cece eee eens 12 Layers of Service 1 1 eee 14 The ITIL Service Management disciplines 5 17 Key relationships between Service Management disciplines 20 A typical e business application infrastructure 21 e business solution specific service layers 0 005 24 Logical view of an e business solution 0000200000s 25 Typical Tivoli managed e business application infrastructure 27 The On Demand Operating Environment 00005 28 IBM Automation Blueprint
2. 0 00 e eee ee eee 261 Multiple QoS systems measuring multiple sites 265 Work with discovery policies 0 c eee ee 267 Configure QoS discovery policy 0000 eee e eee 268 Choose schedule for QoS 0000 cee ee 269 Selecting Agent Group for QoS discovery policy deployment 270 Assign name to new QoS discovery policy 2 05 271 View discovered transactions to define QoS listening policy 272 View discovered transaction of trade application 273 Configure QoS set data filter write data 2 0 000 eae 274 Configure QoS automatic threshold 00 cee eee eee 275 Configure QoS automatic threshold for Back End Service Time 276 Configure QoS and assign name 000 00 e eee 277 Deploy J2EE and Work of agents 2 0000 eee eee ee 279 J2EE deployment and configuration for WAS 5 0 1 280 J2EE deployment and work with agents 222005 282 J2EE Work with Discovery Policies 00e eee eee 283 Configure J2EE discovery policy 000 e cece eee 284 Work with Schedules for discovery policies 5 285 Assign Agent Groups to J2EE discovery policy 286 ASSIGN name JZEE oe deci eee Mate we tir lad Wm BE a aa 287 Create a listening policy for J2EE 2 00 0c eee eee 289 End to End e business Transaction Management Made Easy 8 4
3. Message EJBs Topic Figure 8 1 Trade3 architecture The Trade3 application models an electronic stock brokerage providing Web and Web Services based online securities trading Trade3 provides a real world e business application and JMS data access mix of transactional EJBs MDBs servlets JSPs JDBC adjustable to emulate various work environments Figure 8 1 shows high level Trade application components and a model view controller topology Trade3 implements new and significant features of the EJB 2 0 component specification Some of these include CRM EJB QL Local Remote I Fs Container Managed Relationships CRM provides one to one one to many and many to many object to relational data managed by the EJB container and defined by an abstract persistence schema This provides an extended real world data model with foreign key relationships cascaded updates deletes and so on Standardized portable query language for EJB finder and select methods with container managed persistence Optimized local interfaces providing pass by reference objects and reduced security overhead WebSphere End to End e business Transaction Management Made Easy EJB Data Read Ahead Access Intent Extended EJB QL provides significant features to optimize the performance of EJB 2 0 workloads These features are listed here and leveraged by the Trade3 performance workload Performance of these feat
4. tivlabO7 J2EE WebLogic 7 0 1 petstore petstoreServer STI w a Overall Transaction 12 508 E E Session EJB 1 594 F3 Work with Playback Policies Choose Create Edit etc B fax Local intranet A Figure 8 67 Correlation of STI and J2EE view for Pet Store application With respect to the thresholds defined for the QoS and J2EE listening policies in this scenario we see from Figure 8 68 on page 320 the aggregate topology view that threshold violations have been identified and reported Most_violated in the report Chapter 8 Measuring e business transaction response times 319 E IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer A j 3 O x File Edit View Favorites Tools Help EJ Back gt gt A A Qsearch Favortes meda D S a a Address ja http tivdce4 9082 tmtpUI jsp console WcFrameManager jsp z Go Links Tivoli Monitoring for Transaction Performance tivlabO1 J2EE WebLogic 7 0 1 petstore petstoreServer Filter Session EJB ee E E EA y o Nir STI 27 E amp hid Z238 SignOnFilter Soviet l rampini 9 088 ete 0 184 procesaE venti i i Events View Response Times Vie Web Health Console so m H USA Qos jimum Maximum Java Applet Window al l gt E Applet started fex Local intranet Figure 8 68 J2EE dofilter methods create
5. Extract Certificate A personal certificate has its associated private key in the database Figure 4 6 Creating a new self signed certificate Note At this point you have the following options You can purchase a certificate from a Certificate Authority you can use a pre existing certificate or you can create a self signed certificate We chose the last option In Figure 4 7 on page 96 we define the following Key Label prodms Common name ibmtiv4 itsc austin ibm com which is the fully qualified host name of the machine where the Management Server will be installed Organization IBM Country or Region US We leave the rest of the options on the default setting Chapter 4 TMTP WTP Version 5 2 installation and deployment 95 E4 Create New Self Signed Certificate bmtiv4 itsc austin ib m com ets Pee e Figure 4 7 New self signed certificate options Inthe next step shown in Figure 4 8 on page 97 we modify the password of the new self signed certificate by selecting Key Database File gt Change Password and then pressing the OK button as in Figure 4 9 on page 97 96 End to End e business Transaction Management Made Easy E4 IBM Key Management install keyfiles prodms jks Create View Help i New Open New Provider Close E Save As Key database information se file iles prodms jks
6. Eg Work with Agents Edit delete etc ya intranet Figure 8 3 Deployment of STI components After couple of minutes the Management Agent will be rebooted and the Management Agent will show that STI is installed 8 4 2 STI Recorder installation Follow the procedure below the install the STI Recorder on a Windows based system 1 Log in to a TMTP Version 5 2 UI console through your browser by specifying the following URL http hostname 9082 tmtpUI 2 Select Downloads Download STI Recorder 3 Click on the setup_sti_recorder exe download link From the file download dialog select Save and specify a location on your hard drive in which to store the file named setup_sti_recorder exe 242 End to End e business Transaction Management Made Easy 5 When the download is complete locate the setup_sti_recorder exe file on your hard drive and double click on the file to begin installation The welcome dialog shown in Figure 8 4 will appear Installer i 5 x Synthetic Transaction Investigator Recorder Setup InstallShield Cancel Figure 8 4 STI Recorder setup welcome dialog 6 Click Next to start the installation This will make the Software License Agreement dialog shown in Figure 8 5 appear la x greement wey see international Program License Agreement lease read the following license agreement carefully Part 1 General Terms BY DOWNLOADING IN
7. Internet To start the Pet Store application from the Windows Desktop select Start gt Programs BEA Weblogic Platform 7 0 Weblogic Server 7 0 Server Tour and Examples Lunch Pet Store 8 8 2 Deploying TMTP components in a Weblogic environment The deployment of the IBM Tivoli Monitoring for Transaction Performance Version 5 2 Management Agents and monitoring components is similar to the procedures already described for deployment and configuration in a WebSphere Application Server environment Please refer to the following sections for the specific tasks 310 gt 4 1 4 Installation of the Management Agents on page 130 gt 8 4 STI recording and playback on page 241 gt 8 5 Quality of Service on page 257 gt 8 6 The J2EE component on page 278 End to End e business Transaction Management Made Easy Table 8 3 provides the details of the Pet Store environment needed to configure and deploy the needed TMTP components and Figure 8 59 shows the details of defining deploying the Management Agent on a Weblogic 7 0 application server Table 8 3 Pet Store J2EE configuration parameters reg etautvaue c bea weblogic700 samples server config petstore Path and file name c bea weblogic700 samples server config petstore startP etStore cmd E IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer aan File Edit Yiew Favorites Tools Help Ea Back gt
8. JE iCase and ed Change Ma cms oe Figure 9 20 Rational Robot Project 4 Click Next If you do create a password for the Rational project supply the password on the Security page see Figure 9 21 on page 341 If you do not create a password then leave the fields blank on this page 340 End to End e business Transaction Management Made Easy New Project Security Each Rational Project may be associated with a password This password is required to connect to configure or delete the project Password Confirm lt Back Cancel Help Figure 9 21 Configuring project password 5 Click Next on the Summary page and select Configure Project Now see Figure 9 22 on page 342 The Configure Project dialog box appears see Figure 9 23 on page 343 Chapter 9 Rational Robot and GenWin 341 ji sn LX new Rational Project will be created If you want to review or change any settings click Back If you are satisfied with the settings click Finish Current Settings A new project with a name of testscripts will be created in the directory C RationalT ests The project will not be UCM enabled The project will not be password protected lt Back Cancel Help Figure 9 22 Finalize project 342 End to End e business Transaction Management Made Easy Configure Project Requirements Assets Associated RequisitePro Project eee sra T
9. Password Encryption a x Password mypassword Cancel Filename Jec encryptedpassword tat Figure B 19 Entering the password for use in Rational Scripts Once this script has run the file you specified above will contain an encrypted version of your password The password may be retrieved within your Rational Script as shown in Example B 2 Example B 2 Retrieving the password Sub Main Dim Result As Integer Dim bf As Object Dim strPasswd As String Dim fchar Dim x As Integer Create the Encryption Engine and store a key Set bf CreateObject EncryptionAlgorithms BlowFish bf key ibm Open file and read encrypted password Open C encryptedpassword txt For Input Access Read As 1 Redim fchar Lof 1 End to End e business Transaction Management Made Easy For x 1 to Lof 1 2 fchar x Input 1 1 strPasswd strPasswd amp fchar x Next x Decrypt strPasswd bf DecryptString strPasswd rational SQAConsoleWrite Decrypt amp strPasswd End Sub The resulting unencrypted password has been retrieved from the encrypted file in our case we used the encryptedpassword txt file and placed into the variable strPasswd and the variable may be used in place of the password where required A complete example of how this may be used in a Rational Script is shown in Example B 3 Example B 3 Using the retrieved password Sub Main Initially Recorded 10 1 2003 11 18 08 AM Scr
10. a m General Reports gt Transaction With Subtransactions Cp SE Change settings Policy trade_2_stockcheck_tivlab01 Management Agent tivlab01 gt S Transaction Step_3_http ibmtiv9 itsc austinibm com32 trade app bDc d 0 3 78 Backend Service Time_3 Step_3_http ibmtiv9 itsc austin ibm com 82 trade app 2 85 E _ 2 19 8 a 0 95 o0 E 10 01 10 02 10 02 10 02 10 02 21 00 03 00 09 00 15 00 21 00 Time Year Month Day Hour Minute Start Time 2003 z poah Ae 21 o Stop Time 2003 10 7 2 7 21 j 0 7 la gt Apply Alt a S Figure 8 48 Back End service Time for Trade subtransaction 3 The Back End Service Time details for subtransaction 3 shows that the actual processing time was roughly one fourth of the overall time spent When drilling further down into the Back End Service Time for subtransaction 3 we find as shown in Figure 8 49 on page 300 that the servlet processing this request is com ibm websphere samples trade web OrdersAlertFilter doFilter Chapter 8 Measuring e business transaction response times 299 IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer 5 x Address http ftivdces tse austin ibm Na ip eco Tivoli Monitoring for Transaction Performance it View Favorites Tools Help gt Transaction With Subtransactions wRe Change settings Policy trade_2_stockcheck_tivlab01 Management Agent i
11. A Qsearch Favorites meda lt 4 Ey S aa Tivoli Monitoring for Transaction Performance User Name root Configuration Configure J2EE Listener Work with Discovery Poli Work with Listening Polic ES URI Filter Work with Playback Poli http VWV VpetstoreV Work with Schedules 3 User Name Work with Agent Groups ae x Work with Transaction Ri ate Work with Realms C gent Group Advanced Settings Reports il b System Administration Date Fitar gt Downloads Sample Rate 20 Percent Number of Samples 5 Write on Disk Aggregate Data Only 5 Instances collected after failure C Aggregate and Instance lt Back Alt b Next Alt n gt Finish At Cancel Alt c gt Work with Agent Groups Edit delete etc a Internet vile Figure 6 10 Configuring the Sample Rate and Failure Instances collected This approach is recommended instead of manually changing the policy to collect Aggregate and Instance records Collecting both Aggregate and full instance records has the potential to produce significant amounts of data that may not necessarily be required at normal operating levels If you allow the Management Agent to dynamically switch to instance data collection when a violation occurs then your instance records will only contain situations that resulted in the violation With the higher J2EE Trace Detail Level more transaction context information will be collected Ther
12. Key database content Stash Paf wo rd Exi it Y Receive prodms Delete View Edit Export Import gt New Self Signed Extract Certificate The requested action has successfully completed Figure 4 8 Password change of the new self signed certificate 4 Change Password xi New Password Confirm New Password Password Strength Clear Cancel Figure 4 9 Modifying self signed certificate passwords Once the password is changed we are ready to create the JKS file for the Management Server The next step is to create the same JKS files for the Management Agent and for the Store and Forward agent We use the same steps as above except for some different parameters as explained in Table 4 2 on page 98 Chapter 4 TMTP WTP Version 5 2 installation and deployment 97 Table 4 2 JKS file creation differences prodagent jks prodagent 8 Generating KDB and STH files Once the JKS files are generated we need to generate a KDB file and its STH password file for the correct secure installation of the WebSphere Caching proxy on the Store and Forward agents The WebSphere Caching proxy gets installed automatically with the Store and Forward agent We will generate these files prodsnf kdb CMS Key Database file prodsnf sth The Password file for the CMS Key Database file W
13. Figure B 7 Finalize project Appendix B Using Rational Robot in the Tivoli Management Agent environment 447 Configure Project Requirements Assets Associated RequisitePro Project j Test Assets Associated Test Datastore Create Select Change Requests Associated ClearQuest Database pe Models Associated Rose Models Add Fassa Close Help Figure B 8 Configuring Rational Project A Rational Test datastore is a collection of related test assets including test scripts suites datapools logs reports test plans and build information You can create a new Test datastore or associate an existing Test datastore For testing of Rational Robot the user must set up the Test datastore To create a new test datastore 1 On the Configure Project dialog box click Create in the Test Assets area The Create Test Datastore tool appears Figure B 9 on page 449 448 End to End e business Transaction Management Made Easy Create Test Datastore New Test Datastore Path CAR ationalT est T estD atastore Browse Initialization Options Initialize Assets from the following Test Datastore Initialize Test Users and Groups from the Rational Project Test Sept o Advanced Database Setup Cancel Help Figure B 9 Specifying project datastore 2 Inthe Create Test Datastore dialog box a In the New Test Datastore Path field use a UNC path name
14. b System Administration Hare Start Time Stop Time Rut gt Downloads petstore_j2ee_dis Start as soon as possible Run forever trade_dis_sch Star as soon as possible Run forever Page 1 lt Back Alt b Next Alt n gt Finish Alt Cancel Alt c Ea Work with Discovery Policies Choose Create Edit etc ir Internet Figure 8 38 Work with Schedules for discovery policies Click Next to select the target agents to which this policy will be distributed from the Agent Groups dialog 5 Select the Agent Group s you wish to distribute the discovery policy to and click Next to get to the final step in discovery policy creation name assignment and deployment In the example shown in Figure 8 39 on page 286 the group selected is named trade_j2ee_grp Chapter 8 Measuring e business transaction response times 285 Tivoli Monitoring for Transaction Performance Configuration Work with Agent Groups Work with Discovery F Create Discovery Policy Create New Alt w Work with Agent Grou Agent Groups Work with Transaction Work with Realms Assign Name Please make a selection z b Reports b System Administratia Name gt Downloads ibmtiv9 itsc austin ibm com 82 Go Alt g STI QoS petstore_j2ee_grp petstore_gqos_grp gos_gtp sti_grp tivlabO1 itsc austin ibm com 80 trade_j2ee_grp lt Back Alt b Next
15. gt TEDW allows for correlation of information from many Tivoli applications TEDW can also be used to derive added value by correlating data from many Tivoli applications It allows reports to be written which correlate cross application data 376 End to End e business Transaction Management Made Easy gt TEDW uses open proven interfaces for extracting storing and sharing the data TEDW can extract data from any application Tivoli and non Tivoli and store it in a common central database TEDW also provides transparent access for third party Business Intelligence Bl solutions using the CWM standard such as IBM DB2 OLAP Crystal Decisions Cognos BusinessObjects Brio Technology and Microsoft OLAP Server CWM stands for Common Warehouse Metadata an industry standard specification for metadata interchange defined by the Object Management Group see http www omg org TEDW provides a Web based reporting front end called the Reporting Interface but the open architecture provided by the TEDW allows other BI front ends to be used to access the data in the central warehouse The value here is flexibility Customers can use the reporting application of their choice they are not limited to any specific one gt TEDW provides a robust security mechanism TEDW provides a robust security mechanism by allowing data marts to be built with data from subsets of managed resources by providing database level authorization to access tho
16. 00 00000 421 Part 4 Appendixes c 3 3 42640 ovata oeda Gir Meee ied ehad Poa Gee bee 427 Appendix A Patterns for e business 00 0200055 429 Introduction to Patterns for e business 0 00 cee eee 430 The Patterns for e business layered asset model 0 00 431 How to use the Patterns for e business 0000 e ee eee 433 Appendix B Using Rational Robot in the Tivoli Management Agent environment 00 000 ee 439 Rational Robot 0 0 0 0 ccc tees 440 Tivoli Monitoring for Transaction Performance TMTP 440 TREARM APIA miia girata cate MN A cath A BAM AN a 441 MItAMNStAll s se cess sete eet maiar tes tated tie Ae gee tad Ge deg oad aie amd 443 Working with Java Applets 0 0 0 eee 449 Running the Java Enabler 00 00 eee 450 Using the ARM API in Robot scripts 0 0000 e ee eee 450 Rational Robot command line options 00 a eee 462 Obfuscating embedded passwords in Rational Scripts 464 Rational Robot screen locking solution 0 0 cee eee eee 468 vi End to End e business Transaction Management Made Easy Appendix C Additional material 000 20 0 eu 473 Locating the Web material 0 0 0 cee eee ae 473 Using the Web material 0 0 00 c eee eee 473 System requirements for downloading the Web material 474 How to use the Web material
17. 360 End to End e business Transaction Management Made Easy Microsoft Windows 2000 CD Xx Install Add On Components Customize your Windows 2000 experience with a variety of optional components Figure 9 33 Terminal Server Add On Component As the Terminal Server session will be back on the local machine there is no reason to install the Terminal Server Licensing feature Due to this fact you should also select the Remote Administration mode option during Terminal Server install After the Terminal Server component is installed you will need to reboot your machine 2 Install the Terminal Server client on the local machine The Terminal Server install provides a facility to create client installation diskettes This same source can be used to install the Terminal Server client locally Figure 9 34 on page 362 by running the setup exe the path to this setup exe is by default c winnt system32 clients tsclient win32 disks disk1 Chapter 9 Rational Robot and GenWin 361 362 N C WINNT system32 clients tsclient win32 disks diski Eile Edit view Favorites Tools Help se Back gt v Qseach ares A A K A Ea EUS ja C WINNT system32 clients tsclient win32 disks disk1 z Go Folders x Name Size EB appmomt a acmsetup exe 345KB A CD catRoot QP acmsetup hip 15KB H i hO cea e commonss dil 57KB A BA certsry 247KB A BAA dents 2KB T EH tsclient 259KB A net
18. A A Gsearch fyravortes meda CH D S Gi a Address http tmtp linux ibm com 9082 tmtpUL jsp console WcFrameManager jsp v Go Links Tivoli Monitoring for Transaction Performance User Name root clients Deploy Components and or Monitoring Component eports eC System Administration Management Agent Name tivlab07 Work with Agents R Choose Component or Monitoring Component Configure System Event Details Component Management Configure J2EE Monitoring Component Go Configure User Settings Work with Event Responses View System Events Application Server Type View Log Files WebLogic v View Management Server Details b Downloads Application Server Name Application Server Home petstoreServer c bea weblogic700 Domain Java Home pestore c bea jdk131_03 A script starts this server Domain Path Path and file name c bealweblogic700 sampl letstore startPetStore crd I Node Manager starts this server aft Manage your listening data interet Z Figure 8 59 Weblogic Management Agent configuration Chapter 8 Measuring e business transaction response times 311 8 8 3 J2EE discovery and listening policies for Weblogic Pet Store 312 After successful installation of the Management Agent onto the Weblogic application server the next steps are creating the agent groups schedules and discovery and listening policies For details on how to create discovery and listening policies please r
19. Figure 2 5 Inspector view By examining the instance drop down list Figure 2 6 the administrator can see all of the instances captured for the hour Year Month Day Hour Time 2003 8 z 25 gt is D Data Type Aggregate C Instance Time 2003 08 25 16 27 14 Duration 6 03 Seconds e 2003 08 25 16 2 4 Duration 6 03 Second Time 2003 08 25 16 27 30 Duration 6 016 Seconds 4 Time 2003 08 25 16 41 19 Duration 5 02 Seconds Time 2003 08 25 16 41 33 Duration 5 025 Seconds Time 2003 08 25 16 41 45 Duration 5 014 Seconds Time 2003 08 25 16 41 58 Duration 5 009 Seconds Time 2003 08 25 16 42 07 Duration 0 082 Seconds Time 2003 08 25 16 42 12 Duration 5 014 Seconds Time 2003 08 25 16 42 25 Duration 5 024 Seconds _ 1 Time 2003 08 25 16 44 18 Duration5 019 Seconds _ ftical Fatal Time 2003 08 25 16 44 27 Duration 0 075 Seconds derer graphlayy Internet Figure 2 6 Instance drop down 46 End to End e business Transaction Management Made Easy Figure 2 6 on page 46 shows nine instances with asterisks indicating that they violated thresholds and two others with low performance figures indicating they did not violate The administrator can now select the first instance that violated they are in order of occurrence and click the Apply button to obtain an instance topology Figure 2 7 T https orcrist tiviab austin ibm com 9445 tmtpuI jsp console
20. 350 End to End e business Transaction Management Made Easy measure transaction performance with TMTP Timers are inserted using the Start Timer button in the GUI Insert Toolbar but you will also need to add ARM API calls to the script to capture transaction performance Timers can still be valuable to use if you want to have an idea of how long a transaction takes on the fly in this case you can insert timers together with ARM API calls Use comments in the script for maintenance It is a good idea to record comments in the script during execution in particular where you pressed particular code sequences or typed down information that was relevant only in that particular step For example suppose you are testing a Web based interface that pulls information from a database Since the information retrieved can change over time while the interface of the application does not when you add a Verification Point on a graph that is dynamically generated add a comment to remind you that the portion of script may need further coding 9 1 5 Add ARM API calls for TMTP in the script ARM API calls need to be included in the script by manually editing the code the instructions you add will load the ARM function library define ARM return codes for use in the script will initialize the simulation so that ARM will consider the API calls coming from it and define the start and stop points for each transaction You can create any number of transacti
21. 6 1 1 Checking MBeans The following procedure shows how to enable the HTTP Adapter for the MBean server on the Management Agent This HTTP adapter is useful for troubleshooting purposes however it creates a security hole so it should not be left enabled in a production environment The TMTP installation disables this access by default The MBean server configuration file is named tmtp sc xml and is located in the MA_HOME config directory SMA_HOME is the Management Agent home directory by default this is C Program Files IBM Tivoli MA on a Windows machine To enable the HTTP adaptor you will need to add the section shown in Example 6 1 on page 183 to the tmtp sc xml file and then restart the Tivoli transperf service daemon 182 End to End e business Transaction Management Made Easy Example 6 1 MbeanServer HTTP enable lt mbean class com ibm tivoli transperf core services sm HTTPAdapterService name TMTP type HTTPAdapter gt lt attribute name Port type int value 6969 gt lt mbean gt To access the MBean HTTP adapter point your Web browser to http hostname 6969 From the HTTP Adapter you can control the MBean server as well as see any attributes of the MBean server Using this interface is of course not supported however if you are interested in delving deeper into how TMTP works or troubleshooting some aspects of TMTP it is useful to know how to set this access up Figure 6 3 shows what will be displayed
22. Business Intelligence and Reporting Tools Cognos TEDW Control Business Crystal Center Objects Reports TT Figure 10 3 ITMTP Enterprise Transaction Performance data flow The TMTP upload component is responsible for moving data from the Management Agent to the database The TMTP ETL1 is then used to collect data from the TMTP database for any module and transform and load these to the staging area tables and dynamic data tables in the central data warehouse TWH_CDH Before going into details of how to install and configure the Tivoli Enterprise Data Warehouse Enablement Packs to extract and store data from the IBM Tivoli Monitoring for Transaction Performance components the environment used for TEDW in the ITSO lab is presented This can be used as a starting point for setting up the data gathering process We assume no preexisting components will be used and describe the steps of a brand new installation 382 End to End e business Transaction Management Made Easy As shown in Figure 10 4 our Tivoli Enterprise Data Warehouse environment is a small distributed environment composed of three machines 1 A Tivoli Enterprise Data Warehouse server machine hosting the central Warehouse and the Warehouse Data Mart databases 2 A Tivoli Enterprise Data Warehouse Control Center machine hosting the Warehouse meta data database and handling all the ETLs executions 3 A Tivoli Enterprise Data Warehouse Report
23. Bw E Step_1_hitp Araw google corn E Step_2_nttovArww google comsesrch hiser Step 3 Np vAYww google com search ni or STi google search 06 19 08 20 08 20 08 20 06 20 20 00 02 00 08 00 14 00 20 00 Time Year Month Day Hour Minute Start Time 20 7 a MJE 7 ff E 7 oo Stop Time i x a x fa 7 20 7 oo 7 Apply Alt a Figure 7 7 Transactions with Subtransactions report Up to five subtransactions can be viewed for the selected transaction By default the five subtransactions with the highest average time will be displayed The legend depicting each subtransaction can be used via clicking to enable or disable the display of a particular subtransaction to show how its performance is affecting the transaction performance This is the only general report where subtransactions are plotted over time the only other place to get this information is from the Topology Node view Chapter 7 Real time reporting 221 Slowest Transactions Table This report list the worst performing transactions either for the entire Management Server or a specific application The table shows the recent hourly aggregate data available for each root The report allows you to choose the number of transactions to display ranging between 5 and 100 Links are provided to the relevant topology or STI bar chart similar to the ones in the Big Board General Topology Presents the same information that is available through the Big Board s
24. C Program Files Rational Rational Test rtrobo exe ARM_example user Admin project C TEMP rationaltest ScriptTest rsp play build Build 1 nolog close Details of the command line options can be found in the Robot Help topic but are also included at the end of this document Set the Start in directory to the installation location typically this is Program Files Rational Rational Test see Figure B 16 on page 460 Appendix B Using Rational Robot in the Tivoli Management Agent environment 459 Rational Robot FA TION 1 utspla exe ts_rbt C PROGRA 1 RationaliRATION 1 FSTEWAR2 Administrator Figure B 16 Enable scheduled task Select the Schedule tab and click on the Advanced button see Figure B 17 on page 461 460 End to End e business Transaction Management Made Easy Rational Robot Task Schedule Settings Security Bx At 3 00 AM every day starting 3411 2003 24 Schedule Task Start time Advanced 8 00 AM Schedule Task Daily Every 1 day s Show multiple schedules Figure B 17 Viewing schedule frequency You can schedule the task to run every 15 minutes and set a date on which it will stop running see Figure B 18 on page 462 Appendix B Using Rational Robot in the Tivoli Management Agent environment 461 Advanced Schedule Options E 21 xi Start Date Tuesday March 11 2003 Iv End Date Tuesday August 26 2003 gt JV Repea
25. Figure 8 27 View discovered transactions to define QoS listening policy Now perform the following 1 Select QoS and the desired type of policie s QoS or J2EE from the drop down list at the top of the dialog 2 Select the appropriate discovery policies In our example only trade_qos_dis was selected 3 Select View Discovered Transactions from the drop down list just above the list of discovery profiles and press Go This will display a list of discovered transactions in the View Discovered Transactions as shown in Figure 8 28 on page 273 End to End e business Transaction Management Made Easy Tivoli Monitoring for Transaction Performance User Name administrator My Work Configuration Work with Discovery Policies View Discovered Transactions Work with Listening Policies Work with Playback Policies Work with Schedules Work with Agent Groups Work with Transaction Recordings Work with Realms Please make a selection gt Reports Create Component Policy From 2iu Average Time b System Administration http ibmtiv9 itsc austin ibm com 82 trade 0 015 b Downloads TE ee http ibmtiv itsc austin ibm com 82 trade leftMenu html oon Go Alt g http ibrntiv9 itsc austin ibm com 82 trade topBanner html loor j a http ibmtiv9 itsc austin ibm com 82 trade contentHome html 0 01 http ibrntiv itsc austin ibrn com 82 trade style css 0 0090 Page 1 All Times ar
26. IBM Redbooks collections Redbooks are also available on CD ROM Click the CD ROMs button on the Redbooks Web site for information about all CD ROMs offered as well as updates and formats Help from IBM 482 IBM Support and downloads ibm com support IBM Global Services ibm com services End to End e business Transaction Management Made Easy Index Numerics 3270 33 80 application 82 transactions 35 A administrator account 124 133 agent 26 aggregate 34 data 60 66 214 topology 218 aggregation data 376 aggregation level 414 aggregation period 61 aggregation type 414 alerts 60 analysis 379 historical 376 multi dimensional 417 OLAP 379 trend 417 application 3270 82 architecture 6 design 32 J2EE 5 management 5 6 patterns 436 performance 7 resource 26 system 13 tier 21 transaction 5 usefulness 32 applications source 378 architecture J2EE 7 ARM 33 67 257 API 351 441 correlation 68 engine 64 65 67 184 Copyright IBM Corp 2003 All rights reserved records 188 authentication 76 79 automated report 407 automatic baselining 213 responses 168 automatic thresholding 240 availability 59 154 graph 222 violation 219 222 Web transaction 35 Availability Management 18 avgWaitTime 163 B back end application tier 436 BAROC files 168 baselining automatic 213 BI See Busienss Intelligence bidirectional interface 74 Big Board 212 296 filtering 215 refresh rate 215 view 44 b
27. In the On Demand Operating Environment IBM Tivoli Monitoring for Transaction Performance plays an important role in the automation area By providing functions to determine how well the users of the business transactions the J2EE based ones in particular are served IBM Tivoli Monitoring for Transaction Performance supports the process of provisioning adequate capacity to meet Service Level Objectives and helps automate problem determination and resolution For more information on the IBM On Demand Operation Environment please refer to the Redpaper e business On Demand Operating Environment REDP3673 As part of the On Demand Blueprint IBM provides specific Blueprints for each of the three major properties The IBM Automation Blueprint depicted in Figure 1 11 on page 30 defines the various components needed to provide automation services for the On Demand Operation Environment Chapter 1 Transaction management imperatives 29 30 Business Services Management Policy based Orchestration Availability Security Optimization Provisioning Figure 1 11 IBM Automation Blueprint The IBM Automation Blueprint defines groups of common services and infrastructure that provide consistency across management applications as well as enabling integration Within the Tivoli product family there are specific solutions that target the same five primary disciplines of systems management Availability Security Optimization
28. Note Under normal circumstances specify a Low configuration Only when you want to diagnose a performance problem should you increase the configuration to Medium or High If you specified a Custom configuration you can adjust the level of monitoring for type specific context information Click one of the following radio buttons beside each of the J2EE subtransactions in the Trace Detail Level list Off Specifies that no monitoring is to occur on the subtransaction 1 Specifies that a low level of monitoring is to occur on the subtransaction 2 Specifies that a medium level of monitoring is to occur on the subtransaction 3 Specifies that a high level of monitoring is to occur on the subtransaction Define settings for intelligent event generation To enable intelligent event generation perform the following actions in the Filter Threshold Events by Time Percentage Failed fields i Select the check box next to Enable Intelligent Event Generation While you are not required to enable intelligent event generation do so in most cases Without intelligent event generation an overwhelming number of events can be generated For example a transaction might go above and fall below a threshold hundreds of times during a single monitoring period and without intelligent event generation each of these occurrences generates a separate event with associated notification Intelligent event generation merges multiple threshold violati
29. Senior technical executives can use Application patterns to make critical decisions related to the structure and architecture of the proposed solution Application patterns help refine Business patterns so that they can be implemented as computer based solutions Technical executives can use these patterns to identify and describe the high level logical components that are needed to implement the key functions identified in a Business pattern Each Application pattern would describe the structure tiers of the application placement of the data and the integration loosely or tightly coupled of the systems involved Finally solution architects and systems designers can develop a technical architecture by using Runtime patterns to realize the Application patterns Runtime patterns describe the logical architecture that is required to implement an Application pattern Solution architects can match Runtime patterns to existing environment and business needs The Runtime pattern they implement establishes the components needed to support the chosen Application pattern It defines the logical middleware nodes their roles and the interfaces among these nodes in order to meet business requirements The Runtime pattern documents what must be in place to complete the application but does not specify product brands Determination of actual products is made in the product mapping phase of the patterns In summary Patterns for e business captures e busi
30. Servlet JSP performance either at the application server or Web application or servlet level which occurs when the servlet response time exceeds the predefined monitoring threshold During the initial deployment on any Resource Model of IBM Tivoli Monitoring for Web Infrastructure we recommend using the default values shown in Table 5 2 The following definitions will help you understand the table Number of Occurrences Specifies the number of consecutive times the problem occurs before the software generates an indication Number of Holes Determines how many cycles that do not produce an indication can occur between cycles that do produce an indication Table 5 2 Resource Model indicator defaults Cycle Threshold Occurrences time Holes WebSphereAS Administration Server Status WebSphereAS Application Server Status WebSphereAS DB Pools Connection pool timeouts are too high E DB Pool avgWaitTime is too high 250ms fi ne pepe a high WebSphereAS EJB EJB performance data gathered at EJB level EJB performance data gathered at application server EJB container and level 164 End to End e business Transaction Management Made Easy Cycle Threshold Occurrences time Holes EJB exceptions data gathered at EJB 50 level EJB exceptions data gathered at 50 application server EJB container and level WebSphereAS HTTP Sessions p LiveSessions is too high 1000 WebSphereAS JVM Runtime W
31. Wait state Apply wait state to verification point Retr y every 2 seconds Timeout after 20 seconds m Expected result Pass Fail Cancel Help Figure 9 27 Verification Point Name Dialog In case the object you will use as a Verification Point takes some time to be displayed or to get to the desired state check the Apply wait state to Verification Point check box and select the retry and time out time in seconds Also select the desired state in simulations you generally always expect the result to be of Pass type Click on OK when you complete all the settings and the Object Finder dialog is displayed as in Figure 9 28 on page 349 348 End to End e business Transaction Management Made Easy Select Object Drag the Object Finder tool over an object and then release the left mouse button to select the object To select from a list of all objects on the Desktop click Browse Object Finder tool d Selected object RecMethod T Automatically close dialog box after object selection OK Cancel Help Figure 9 28 Object Finder Dialog Select the icon of the Object Finder tool and drag it on the object whose properties you want to investigate A flyover appearing on each object will tell you how it is identified for example a Java label will show a tool tip showing a Java label when the Object Finder tool is on it When the mouse is released the properties for the object yo
32. arm_update arm_stop arm_end This is used to define an application to the response time agent This is used to define a transaction to the response time agent A transaction is always a child of an application This call is used to start the response time clock for the transaction This call is optional It can be used to send a heartbeat to the response time agent while the transaction is running You might want to code this call in a long running transaction to receive confirmations that it is still running This call is used to stop the response time clock when a transaction completes This call ends collection on the application It is effectively the opposite of the arm_getid and arm_init calls The benefit of using ARM is that you can place the calls that start and stop the response time clock in exactly the parts of the script that you want to measure This is done by defining individual applications and transactions within the script and placing the ARM API calls at transaction start and transaction end End to End e business Transaction Management Made Easy Initial install This is fairly straightforward just run the setup executable and follow the typical install path You will need to import the license key either at the beginning of the install or once the install has completed using the Rational License Key Administrator which should appear automatically At the end of the install you will be
33. 1 command on the install directory after unpacking the installation files for the Management Server Example 4 2 YWxrwxrwx YWxrwxrwx YWxrwxrwx YWxrwxrwx drwxrwsrwx YWxrwxrwx drwxrwsrwx drwxrwsrwx drwxrwxrwx YWxrwxrwx YWxrwxrwx YWxrwxrwx YWxrwxrwx Ywxrwxrwx YWxrwxrwx YWxrwxrwx YWxrwxrwx Ywxrwxrwx YWxrwxrwx YWxrwxrwx Ywxrwxrwx Ywxrwxrwx YWxrwxrwx YWxrwxrwx drwxrwsrwx YWxrwxrwx drwxrwsrwx drwxrwsrwx Management Server installation_root nuucp 24 23 13 root 12 493 493 root lpd 11 10 12 16 15 16 15 19 18 16 15 15 16 11 root 11 root root SN OR DR RR RRP RP RP RP RP PrP RP rR rPrRPNNNF OP FP Fe mail 24 23 13 sys 12 493 493 system printq mqbrkr audit 12 16 15 16 15 19 18 16 15 15 16 mqbrkr sys mqbrkr sys sys 885 Sep 08 09 57 1332 Sep 08 09 57 957 Sep 08 09 57 10431 Sep 08 09 57 512 Sep 12 11 19 233 Sep 08 09 57 512 Sep 19 09 26 512 Sep 08 09 57 512 Sep 11 10 08 12 Sep 08 09 57 3792 Sep 08 09 57 16384 Sep 08 09 57 24 Sep 08 09 58 20824338 Sep 08 09 58 setup 24 Sep 08 09 58 19277890 Sep 08 09 58 setup 24 Sep 08 09 58 18960067 Sep 08 09 58 setup 24 Sep 08 09 58 24 Sep 08 09 58 5632 Sep 08 09 58 512 Sep 11 11 21 24665 Sep 08 09 58 512 Sep 12 11 12 512 Sep 18 18 10 End to End e business Transaction Management Made Easy MS opt MS_db2_embedded_unix opt MS_db2_embedded_w32 opt MsPrereqs xml db2 dm
34. 62 End to End e business Transaction Management Made Easy The Management Server components are JMX MBeans running on the MBeanServer provided by WebSphere Version 5 0 1 Communications between the Management Agents and the Management Server is via SOAP over HTTP or HTTPS using a customized version of the Apache Axis 1 0 SOAP implementation see Figure 3 4 The services provided by the Management Server to the Management Agents are implemented as Web Services and invoked by the Management Agent using the Web Services Invocation Framework WSIF All downcalls from the Management Server to the Management Agent are remote MBean method invocations Session Axis Engine Web Beans servlet Services MBeans Figure 3 4 Requests from Management Agent to Management Server via SOAP Note The Management Sever application is a J2EE 1 3 1 application that is deployed as a standard EAR file named tmtp52 ear Some of the more important modules in the EAR file are gt Report and User Interface Web Module ru_tmtp war gt Web Service Web Module tmtp war gt Policy Manager EJB Module pm_ejb jar gt User Interface Business Logic EJB Module uiSessionModule jar gt Core Business Logic EJB Module sessionModule jar gt Object Model EJB Module entityModule jar ARM data is uploaded to the Management Server from Management Agents at regularly scheduled intervals the upload interval By defa
35. Cross system amp domain root cause analysis Out of box best practices Ease of use Superior value with a fully integrated solution Monitor Systems and Applications Discover collect metrics probe e g user experience gt Quality perform local analysis filter concentrate determine root cause take automated action Processes roles and metrics Rapid problem response Figure 1 12 Tivoli s availability product structure The lowest level consists of the monitoring products and technologies such as IBM Tivoli Monitoring and its resource models At this layer Tivoli applications monitor the hardware and software and provide automated corrective actions whenever possible At the next level is event correlation and automation As problems occur that cannot be resolved at the monitoring level event notifications are generated and sent to a correlation engine such as Tivoli Enterprise Console The correlation engine at this point can analyze problem notifications events coming from multiple components and either automate corrective actions or provide the necessary information to operators who can initiate corrective actions Both tiers provide input to the Business Information Services category of the Blueprint From a business point of view it is important to know that a component or related set of components has failed as reported by the monitors in the first layer Likewise in the secon
36. IBM Tivoli Monitoring for products allow an IT department to provide management of the entire business system in a consistent way from a central site using an integrated set of tools This chapter contains multiple references to additional product documentation and other sources such as Redbooks which you are encouraged to refer to for further details Please see Related publications on page 479 for a complete list of the referenced documents Note At the time of the writing of this redbook the publicly available version of IBM Tivoli Monitoring for Web Infrastructure does not support WebSphere Version 5 0 1 This support was being tested within IBM and was due to be released shortly after our planned publishing date 5 1 1 Keeping Web and application servers online The IBM Tivoli Monitoring for Web Infrastructure provides an enterprise management solution for both the Web and application server environments The Proactive Analysis Components PAC that make up this product provide solutions that are integrated with other Tivoli management products A comprehensive and fully integrated management solution can be rapidly deployed and provide a very attractive return on investment The IBM Tivoli Monitoring for Web Infrastructure currently focuses primarily on the performance and availability aspect of managing a Web infrastructure The four proactive analysis components of the IBM Tivoli Monitoring for Web Infrastructure prod
37. In our example we logged into the trade application at http ibmtiv9 itsc austin ibm com trade app and started the Portfolio and Quotes Trade transactions Creating J2EE listening policies J2EE listening policies enable you to collect performance data for incoming transactions that run on one or more J2EE application servers This will help you achieve the following gt Measure transaction and subtransaction response times from J2EE applications in a real time or simulated environment gt Perform detailed analysis of transaction performance data Chapter 8 Measuring e business transaction response times 287 288 gt Identify root causes of performance problems A J2EE listening policy instructs J2EE listeners that are deployed on Management Agents to collect performance data for transactions that run on one or more J2EE application servers The Management Agents associated with a J2EE listening policy are installed on the J2EE application servers that you want to monitor Running a J2EE listening policy produces information about transaction performance times and helps you identify problem areas in applications that are hosted by the J2EE application servers in your environment A J2EE monitored transaction calls subtransactions that are part of the transaction There are six J2EE subtransaction types that you can monitor Servlets Session beans Entity beans JMS JDBC RMI vvvvvy When you create a J2EE listening p
38. Install Rational Robot to C Program Files Rational Ghange Rational Software Figure 9 9 Destination folder for Rational Robot Click on Next the install folder cannot be changed at this stage The Custom Setup panel is displayed Leave the defaults and click on Next the Ready to Install panel is displayed see Figure 9 10 on page 332 Chapter 9 Rational Robot and GenWin 331 ip Rational Robot Setup Wizard Ready to Install the Program R at i ona T The wizard is ready to begin installation the software development company Click Install to begin the installation Tf you want to review or change any of your installation settings click Back Click Cancel to exit the wizard Rational Softwa Figure 9 10 Ready to install Rational Robot You can now click on Next to complete the setup After a while the Setup Complete dialog is displayed see Figure 9 11 fe Rational Robot Setup Wizard xj Rational Setup Complete the software development company The Setup Wizard has successfully installed Rational Robot Click Finish to exit the wizard You must upgrade all Rational products on this system to release level 2003 06 00 436 000 or higher Products may not function correctly until this is done eloper Network Rational Software Figure 9 11 Rational Robot setup complete Deselect the check boxes if you want and click on Finish Installing the Rational Robot
39. ZI x at gt Year Month Day Hour zl Opening http tivdce4 9082 tmtpUt images topology jdbc 32 9 Ei tocalintranet 7 Figure 8 72 Real time Round Trip Time and Back End Service Time by QoS Chapter 8 Measuring e business transaction response times 323 324 End to End e business Transaction Management Made Easy Rational Robot and GenWin This chapter demonstrates how to use the Rational Robot to record e business transactions how to instrument those transactions in order to generate relevant e business transaction performance data and how to use TMTP s GenWin facility to manage playback of your transactions Copyright IBM Corp 2003 All rights reserved 325 9 1 Introducing Rational Robot Rational Robot is a collection of applications that can be used to perform a set of operations on a graphical interface or to operate directly at the network protocol layer using an intuitive and easy to use interface Rational Robot has been around a while and is reliable and complete in the features it offers the range of supported application types is considerable and the behavior between application types is almost identical It provides a robust programming interface that allows you to add strict controls to the program flow and includes technologies that allows the simulation to complete even if portions of the graphical interface of the application under stress changes during development Each record step is shown g
40. frankfurt itsc austin iom com Note The User Name user password fields are still referring to the root user on the Management Server since this user ID needs to have access to the WebSphere Application Server Chapter 4 TMTP WTP Version 5 2 installation and deployment 129 4 1 4 Installation of the Management Agents We will cover the installation of the Management Agents in this section As we have the mentioned we have three zones and each Management Agent will log on to the Management Server using its zone s Store and Forward agent or if the Management Agent is located in the intranet zone it will log on directly to the Management Server We first install the Management Agent for the intranet zone The following pre checks are required 1 Check if the Management Server and Store and Forward agents fully qualified host names are DNS resolvable 2 The Management Agent s platform will be Windows 2000 Advanced Server with Service Pack 4 The required disk space for all platforms is 50 MB not including logs 3 The installation wizard will install the following components Management Agent 4 We start the installation wizard by executing the following program setup_MA_w32 exe You should get the window shown in Figure 4 45 im Install Management Agent A loj x Follow the instructions in this installation program to install the following product component on your computer IBM Tivoli Monitoring for Transa
41. http tivdce4 9082 tmtpUI jsp console WwcFrameManager jsp x fed Go Bak gt A Gsearch SjFavorites Meda S 3 Si a Tivoli Monitoring for Transaction Performance User Name administrator Assign Name Name trade_qos_lis_pol Description Sent to Agents at next interval Send to Agents now lt Back Alt b Next Alt n gt re Cancel Alt c Work with Playback Policies Choose Create Edit etc ml Local intranet Figure 8 32 Configure QoS and assign name vile From the Assign Name dialog shown in Figure 8 32 select your preferred distribution time and click Finish Chapter 8 Measuring e business transaction response times 277 8 6 The J2EE component The Java 2 Platform Enterprise Edition J2EE component of TMTP Version 5 2 is a component in IBM Tivoli Monitoring for Transaction Performance Version 5 2 that provides transaction decomposition capabilities for Java based e business applications Performance and availability information will be captured from methods of J2EE classes includes Servlets Enterprise Java Beans Entity EJBs and Session EJBs JMS JDBC methods RMI IIOP operations vvvy The TMTP J2EE component supports WebSphere Application Server Enterprise Edition Versions 4 0 3 and later which are valid for the J2EE monitoring component Version 7 0 1 is the only supported version of BEA WebLogic More details about J2EE are av
42. prodagent jks proddmz jks prodagent arm proddmz arm Figure 4 15 Trust files and certificates Figure 4 16 on page 103 shows which JKS or KDB file needs to have which self signed certificate prodms jks prodagent jks proddmz jks prodsnf kdb Needs to have all the certificates Needs to have the certificate from the Management Server and its default certificate This file will be used for the Management Agents connecting directly to the Management Server Needs to have the certificates from the Management Server and from the prodsnf kdb file This file is used for the Store and Forward agent and for its Management Agents in the same zone Needs to have the certificate from the Management Server and from the Store and Forward agent s JKS files This file is used by the WebSphere Caching proxy End to End e business Transaction Management Made Easy Management Server ____ Sae N ponyaid gent prodms jks proddmz jks prodms arm proddmz arm prodagent arm prodms arm proddmz arm prodsnf arm prodsnf arm prodsnf kdb prodsnf arm proddmz arm prodms arm Management Agent Management Agent direct MS connection SnF connection prodagent jks proddmz jks prodagent arm proddmz arm prodms arm prodms arm prodsnf arm Figure 4 16 The imported certificates To ex
43. quantify Used with play Plays back the script referenced in scriptname under Rational Quantify coverage Used with play Plays back the script referenced in scriptname under Rational PureCoverage build build Name of the build associated with the script logfolder foldername The name of the log folder where the test log is located The log folder is associated with the build log logname The name of the log nolog Does not log any output while playing back the script C Some items to be aware of gt Use a space between each keyword and between each variable gt Ifa variable contains spaces enclose the variable in quotation marks gt Specifying log information on the command line overrides log data specified in the Log tab of the GUI Playback Options dialog box Appendix B Using Rational Robot in the Tivoli Management Agent environment 463 gt If you intend to run Robot unattended in batch mode be sure to specify the following options to get past the Rational Test Login dialog box user userid password password project full path and full projectname Also when running Robot unattended in batch mode you should specify the following options log logname build build logfolder foldername An example of these options is as follows rtrobo exe VBMenus user admin project C Sample Files Projects Default rsp play build Build1 logfolder Default log MyLog close In this example the use
44. setup 179 transaction 77 staging area tables 382 standardization 12 star schema 381 408 416 stash file 122 statistcis performance 70 status interpreted 217 production 404 server 162 STH files 98 STI 229 230 241 graph 213 limitations 231 placing 80 Recorder 242 recording 248 subtransaction 219 STI transaction breakdown 220 store and forward agent 77 Store and Forward Management Agent 82 subscribers 166 subtransaction 212 performance 221 selection 247 STI 219 times 212 Summary 224 summary report 413 surveillance 15 60 153 synchronization time 71 Synthetic Transaction Investigator 229 230 Synthetic Transaction Investigator Management Agent 82 system event 62 system management 5 28 infrastructure 26 T table dimension 381 fact 381 414 helper 381 table space temporary user 386 tables dynamic data 382 staging area 382 target warehouse 394 target ETL 379 task discovery 160 TEC adapter 167 events 440 TEDW installation 387 installation user 386 Report Interface 407 security 377 user access 394 TEDW Central Data Warehouse 380 TEDW Control Center 380 TEDW Control Center server 388 TEDW report interface 381 TEDW repository 376 TEDW server 379 Terminal Server 360 468 Test datastore 343 thread pool 163 threshold 167 253 threshold setting 45 64 threshold violation 68 thresholding 213 automatic 240 thresholds 61 219 Thresholds View 217 tier application 21 time interval report 416 ti
45. such as IBM Tivoli Monitoring for Databases to monitor the following TMTP DB2 parameters gt DB2 Instance Status gt DB2 Locks and Deadlocks gt DB2 Disk space usage gt To stop and start the WebSphere Application Server type the following commands stopServer sh serverl user root password password startServer sh serverl user root password password The WebSphere application server logs can be found under the following directories WebSphere_installation_folder logs WebSphere_installation_folder logs servername Important Prior to starting WebSphere on a UNIX platform you will need to source the DB2 environment This can be done by sourcing the db2profile script from the home directory of the relevant instance user id For us the command for this was home db2inst1 sq11ib db2profile If this is not done you will receive JDBC errors when trying to access the TMTP User Interface via a Web Browser see Figure 6 1 on page 179 178 End to End e business Transaction Management Made Easy Z IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer S lol x Fie Edit View Favorites Tools Help Address a http 9 3 4 230 9082 tmtpUT isp consale gt Go Bak gt A Qsearch yFavorites media B G Si a rror 500 nested exception is javax resource spi ResourceAllocationException DSRAOO80E An exception was received by the Data Store Adapter See original exc
46. 0 0 0 c ee eee 30 Tivoli s availability product structure 0 00 eee 31 e business transactionS 0 2 0 0 ee ae 34 Typical e business transactions are complex 00 38 Application topology discovered by TMTP 000 42 Big Board View 0 ccc eee 44 Topology view indicating problem 000002e eee eees 45 Inspector ViOW 0 et eee eee 46 Instance drop down 1 te eee 46 Instance topology e h ce eee 47 Inspector viewing Metrics 1 0 0 ee ee 48 Overall Transactions Over Time 0 00 cece eee eee 49 Transactions with Subtransactions 000 e eee eee 50 Page Analyzer Viewer 0 000 eee eee eee 50 Launching the Web Health Console from the Topology view 51 TMTP Version 5 2 architecture 000 00 cee eee 56 Enterprise Transaction Performance architecture 60 Management Server architecture 0 0 0 c ees 62 Requests from Management Agent to Management Server via SOAP 63 Management Agent JMX architecture 0002 0000ee 64 ARM Engine communication with Monitoring Engine 66 Transaction performance visualization 0000 69 Tivoli Just in Time Instrumentation overview 0 00 75 SnF Agent communication flows 00 000 eee eee eee 78 Putting it all together 0 0 ee eee 81 Customer production environment 00000 e eee
47. 28 Add metrics window 9 With Filter By you select only those records that match the values given in this file In the resulting SQL statement each chosen filter will result in a where clause The Group By function works as follows if you choose one attribute in the Group By field then all records with the same value for this attribute are taken together and aggregated according to the type chosen in the previous dialog The result is one aggregated measurement for each distinct value of the chosen attribute Each entry in the Group By column will result in a group by clause in the SQL statement The aggregation type will show up in the select part line 1 where Total is translated to sum 10 We chose no filter in our example The possible choices of the filters are automatically populated from all values in the star schemas If more than 27 distinct values exist you cannot filter on these attributes see Figure 10 29 on page 416 Chapter 10 Historical reporting 415 Sy Add Metrics x aes J2EE Server Name p Eare JOBE Cell Name references J2EE Domain Kwit Reports J2EE Node Jreate a Report J2EE Vendor J2EE Version Jreate a Report Probe Host Name danage Reports and Report Output Probe Name dlanage User Groups Center Name ERAN Customer Name Transaction Host Name TP Address Transaction Description Transaction Name URL Protocol Transaction Website Transaction Website Path Transaction Website Query BWM D_TX_ND
48. 379 OLAP tools 406 On Demand Blueprint 28 Automation 28 Integration 28 Virtualization 28 oslevel 88 overall transactions over time report 220 overview xxi 55 topology 51 owner instance 395 P Page Analyzer viewer 50 Page Analyzer Viewer 213 223 Comments 224 events 224 Host Socket Close 224 Idle Times 224 Local Socket Close 224 Properties 224 Sizes 224 Summary 224 pages visited 223 page specific information 223 parent based correlation 69 path transaction 212 pattern e business 22 Patterns for e business 429 PAV report 213 performance 157 338 EJB 163 hourly 220 measure 350 statistics 70 subtransaction 221 subtransactions 221 trace 70 violation 44 45 208 performance data collection 157 Pet Store application 307 308 playback 35 326 337 347 365 440 monitoring tools 227 schedule 248 Playback Policy create 369 Playback policy create 251 playback Policy 222 playback policy 252 PMR 189 190 policies 32 policy details 214 discovery 228 listening 222 management 64 monitoring 213 playback 222 region 158 161 policy based correlation 69 Port 488 End to End e business Transaction Management Made Easy default 156 number 123 132 predefined action 168 rules 168 presentation layer 24 tier 436 proactive monitoring 27 154 probe 35 59 74 problem cause 212 identification 35 resolution 154 Problem Management 19 process ETL 394 processes ETL 380 404 product mappings 437 produc
49. 5 The server decrypts the session key with its private key 6 Henceforth the client and server use the session key to encrypt all messages TMTP uses the Java Secure Sockets Extensions JSSE API to create SSL sockets within Java applications and includes IBM s GSKIT to manage certificates Chapter 4 TMTP WTP Version 5 2 installation and deployment on page 85 includes information on how to configure the environment to use SSL Store and Forward Agent The Store and Forward Management Service is a new component in the TMTP infrastructure The service resides on a TMTP Management Agent The new service was created in order to allow the TMTP Version 5 2 Management Server to be moved from the DMZ into the Enterprise The agent enables a point to point connection between the TMTP Management Agents in the DMZ with the TMTP Management Server in the Enterprise The functions provided by the Store and Forward agent hereafter referred to as the SnF agent are gt Behaves as a pipe between the TMTP Management Server and TMTP Management Agents gt Maintains a single open and optionally persistent connection to the Management Server in order to forward agent requests gt Minimizes access from the DMZ through the firewall one port for a SnF agent gt Acts as part of the TMTP framework that is the JMX environment User Interface Policy and so on Configuration of the SnF agent including how to configure SnF to relay across m
50. 9 7 Rational Robot product warnings Check if any message is relevant to you If you already have Rational products installed you could be required to upgrade those products to the latest version Click on Next the License Agreement panel will be displayed see Figure 9 8 on page 331 330 End to End e business Transaction Management Made Easy ip Rational Robot Setup Wizard License Agreement Please read the Rational and third party licenses prior to R ati n al the software development company acceptance Rational Product License Agreement Rev 15 April 2003 IMPORTANT READ THIS LICENSE AGREEMENT HEREAFTER AGREEMENT BEFORE CLICKING ON THE ACCEPT BUTTON ENTERING YES IN RESPONSE TO THE ELECTRONIC LICENSE ACCEPTANCE INQUIRY INSTALLING OR ELECTRONICALLY DOWNLOADING ANY OF THE ABOVE ACTIONS INDICATE ACCEPTANCE OF AND LEGALLY BINDS YOU YOUR COMPANY AND ITS xl EMDIOYFFS MITCENSER ANN DATTARAL COFTWADE CAODDAODATTON AND View Click View to display the third party terms you are accepting 1 accept the terms in the license agreement Rational Software Figure 9 8 Rational Robot License Agreement Select I accept the terms in the license agreement radio button and then click on Next the Destination Folder panel is displayed see Figure 9 9 xi Destination Folder z Click Next to install to this folder or click Change to install to a Ratio nal an different folder P a
51. A 21 oo gt i Apply Ait a zl Figure 8 65 Pet Store transaction and subtransaction response time by STI From the Page Analyzer Viewer report shown in Figure 8 66 on page 318 we can see that the enter_order_information_screen subtransaction takes longer 2 4 seconds to present the output to the end user By using Page Analyzer Viewer we can find out for STI transactions which subtransactions take a long time and what type of function is involved Among the functions that can be identified are gt DNS resolution Chapter 8 Measuring e business transaction response times 317 Connection Connection idle Socket connection SSL connection Server response error YYYY Y t IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer na z Bj x File Edit view Favorites Tools Help Back gt A A Qsearch Favorites Emedia B SI a 4 m _ gt HI Total Request Time Autoproxy A httovitiviabO1 itsc austin ibm com petstore main screen 0 71664 C Blank 4 hitp tivlab01 itsc austin ism comipetstore signon_welcom 0 52624 Host Name Resolution _ Blank Item L httovitiviabO1 itsc austin ibm com petstore j_signon_chec i 2 Cached Unknown hitpuitiviabOt it tin ib Vpetstore j_si heck 1 04871 E Cached Unki Z httpyitiviabO1 itsc austin ibm corn petstorefproduct screen 0 84899 Connec
52. Administration C http AivlabO01 itsc austin ibm com 7001 admin ApplRequestProcessor 32 241 0 103 60 53 gt Downloads C http AtivlabO1 itsc austin ibm com 7001 admin AdminRequestProcessor 0 187 0 187 0 187 0 074 0 072 0 078 C http tivlab01 itsc austin ibr cor 7001 petstore items screen 0 067 0 067 0 067 e http itiviabO1 itsc austin ibm com 7001 petstore product screen 0 062 0 062 0 062 C http Aivlab01 itsc austin ibm com 7001 petstore _signon_check 0 049 0 049 0 049 C http Aivlab01 itsc austin ibm com 7001 petstore main screen 0 038 0 037 0 039 C http tivlabO1 itsc austin ibm com 7001 petstore signoff do 0 032 0 032 0 032 c ivlab01 itsc austin ibm com 7001 petstore images banner_logo gif 0 023 0 0 0 105 6 http Aivlab01 itsc austin ibm com 7001 petstore signon_welcome screen 0 023 0 023 0 023 http tivlabO1 7001 petstore images built_bea_web gif 0 014 0 0030 0 027 C http tivlab01 itsc austin ibrn com 7001 petstore images us_flag gif 0 012 0 0 0 099 C http tivlabO1 itsc austin ibra com 7001 petstore index jsp 0 0050 0 0050 0 0050 C http tivlabO1 7001 petstore images banner_logo gif 0 0040 0 0 0 016 C http tivlab01 7001 petstore index jsp 0 0030 0 0030 0 0030 Page 1 2 All 21 i olla gt Figure 8 60 Creating listening policy for Pet Store J2EE Application The average response time reported by the discovery policy is 0 062 seconds see Figure 8 61 on page 314 C
53. Agents lt gt Communication between the Management Server and the WebSphere aching Proxy reverse proxy Figure 3 9 SnF Agent communication flows Ports used Because of the Store and Forward agent the number of ports used to communicate from the Management Agent to the Management Servers can be limited to one and communications via this port is secured using SSL Additionally each of the ports that are used by TMTP for communication between the various components can be configured The default port usage and configuration of non default ports is discussed in Chapter 4 TMTP WTP Version 5 2 installation and deployment on page 85 78 End to End e business Transaction Management Made Easy TMTP users and roles TMTP uses WebSphere Application Server 5 0 security This means that TMTP authentication can be performed using the operating system that is standard operating system user accounts LDAP or a custom registry Also the TMTP Application defines over 20 roles which can be assigned to TMTP users in order to limit their access to the various functions which TMTP offers Users are mapped to TMTP roles utilizing standard WebSphere Application Server 5 0 functionality The process of mapping users to roles within WebSphere is described in Chapter 4 TMTP WTP Version 5 2 installation and deployment on page 85 Also as TMTP uses WebSphere Security it is possible to configure TMTP for Single Sign On the details of how t
54. Available Star Schemas 7 IBM Console Welcome Select Name lt nofilte gt lt no filter gt Preferences r Work with Reports E BWM Hourly Transaction Node Star Schema y Transaction Node Star Schema RER SE O BWM Daily Transaction Node Star Schema ly Transaction Node Star Schema Create a Report O BWM Weekly Transaction Node Star Schema Weekly Transaction Node Star Schema Manage Reports and Report SY BWM Monthly Transaction Node Star Schema Monthly Transaction Node Star Schema Output Total 4 Retumed 4 Displayed 4 Selected 1 Page 1 of 1 Manage User Groups n EA Available Metrics gt Select Name Description Units Sno filter gt lt no filter gt lt no filter gt Sno filter gt Number of Executions total Number of Times a transaction was executed QTY Response Time avg The amount of time it took a process to respond Sec Response Time min The amount of time it took a process to respond Sec O Response Time max The amount of time it took a process to respond Sec O Service Time avg The backend service response time Sec O Service Time min The backend service response time Sec R O Service Time max The backend service response time Sec O Number Threshold Exceeded total The number of transaction thresholds that exceeded QTY Page Render Time avg The page render response time Sec Page Render Time min The page render response time Sec 4 AddMetrics E O Welcome Z Create a Report Figure 10
55. C Source file 12 12 2002 5 26 Pr a O WINDOWS 4 CustomerManager cs 2KB C Source File 12 12 2002 5 26 PY E Local Disk D MIS y gt 1 objects selected 3 My Computer Figure B 3 Rational Robot Project Directory To create a Rational project perform the following steps 1 Start the Rational Administrator by selecting Start Programs Rational Robot Rational Administrator 2 Start the New Project Wizard by selecting File New Project on the Administrator menu A window similar to Figure B 4 on page 444 should appear Appendix B Using Rational Robot in the Tivoli Management Agent environment 443 444 ES Rational Administrator Jog File Edit Yiew Tools Help BeoerKvecs GCEFrsSX 4E 4B iv tit Rational Administrator Name Location fy Projects Test_Script iflotsamit WFlotsa Test_Script For Help press F1 Figure B 4 Rational Robot Project 3 On the wizard s first page Figure B 5 on page 445 a Supply a name for your project for example testscripts The dialog box prevents you from typing illegal characters b In the Project Location field specify a UNC path to the root of the project referring to the directory name you created in above It does not really have to be a shared network directory with a UNC path End to End e business Transaction Management Made Easy G 5 New Project General Please specify the name of the new project an empty di
56. CURRENT_CDW Tnvoking User Management Policy a BWM D_TX_ND PARENT_CDW_ID BWM D_TX_ND ROOT_CDW_ID ke g ji Transaction Node Name e Previous Finish Reset Cancel X 4 Figure 10 29 Add Filter windows 11 Click Finish to set up your metrics and click on the Time pad 12 In the Time dialog you have to choose the time interval for the report In summary reports all measurements of the chosen time interval will be aggregated for all groups 13 In the Schedule pad you can select the Run button to execute the report when the data mart is built A record inserted into the RPI SSUpdated table in the TWH_MD database tells the report execution engine when a star schema has been updated and the report execution engine runs all scheduled reports that have been created from that star schema 14 When all settings are done click OK to create the report You should see a message window displaying Report created successful ly 15 To see the report in the report list click Refresh and expand root in the Reports panel and click Reports as demonstrated in Figure 10 30 on page 417 End to End e business Transaction Management Made Easy Z IBM Console Microsoft Internet Explorer a E My Work Report Ouiput D Administer Users and Roles trade2 1065998784640 Y IBM Console Welcome Preferences 900000 7 Work with Reports Create a Report 4 Create a Report 700000 Manage Reports and Report Output 600000 Man
57. Console port will not be applicable The following ports are important for observing the already installed products DB2 8 1 DB2_dbtmtp 60000 tcp DB2_dbtmitp_1 60001 tcp DB2_dbtmtp_2 60002 tcp DB2_dbtmtp_END 60003 tcp db2c_dbtmip 50000 tcp WebSphere 5 0 1 Admin Console port 9090 SOAP connector port8880 92 End to End e business Transaction Management Made Easy 7 Generating JKS files In order to secure our environment using Secure Socket Layer SSL communication we have to generate our own JKS files We will use the WebSphere s ikeyman utility We need to create three JKS files a prodms jks This will be used by the Management Server b proddmz jks This will be used by the Store and Forward agent and for those Management Agents that will connect to the Management Server through a Store and Forward agent c prodagent jks This will be used by those Management Agents that have direct connections to the Management Server We type the following command to start the ikeyman utility on AIX usr WebSphere AppServer bin ikeyman sh This command will take us to the ikeyman dialog shown in Figure 4 3 E3 IBM Key Management E i fa xj Key Database File Create View Help new A Ca aaa Key database information 4 New Provider Key database content A personal certificate has its associated private key in the database Figure 4 3 ikeyman utility We select
58. Dialog Box Click on OK and Rational Robot will minimize while the Recording toolbar is displayed I m 4 The Recording toolbar contains the following buttons Pause the recording Stop the recording Open the Rational Robot main window and Display the GUI Insert toolbar The first three are self explanatory the last is needed to easily add features to the script being recorded using the GUI Insert toolbar Figure 9 26 io jo O E euog w a B 0 A t g g ner Figure 9 26 GUI Insert 346 End to End e business Transaction Management Made Easy From this toolbar you can add Verification Points start the browser on a Web page for recording and so on Add Verification Points to the script During the GUI simulation flow it is a good idea to insert Verification Points which are points in the program flow that save information on GUI objects for comparing with the expected state When you create a Verification Point you select a Verification Method case sensitivity sub string numeric equivalence numeric range or blank field and an Identification Method by content location title and so on with Verification Points you can also insert timers and timeouts in the program flow Verification is especially needed to ensure that if the application has delays in the execution Rational Robot will wait for the Verification Point to pass before continuing the execution Verification Points can be created on Window Re
59. ETL programs from the management application databases and further processed for historical analysis and evaluation It is Tivoli s strategy to provide ETLs for most Tivoli components so the TEDW databases can be populated with meaningful systems management data IBM Tivoli Monitoring for Transaction Performance is but one of many products to leverage and use TEDW 10 1 1 Tivoli Enterprise Data Warehouse overview Having access to historical data regarding the performance and availability of IT resources is very useful in various ways such as gt TEDW collects historical data from many applications into one central place TEDW collects the underlying data about the network devices connections desktops servers applications software problems and activities that manage the infrastructure This allows for the construction of an end to end view of the enterprise and viewing of the related resource data independent of the specific applications used to monitor and control the resources gt TEDW adds value to raw data TEDW performs data aggregation based on user specified periods such as daily or weekly and allows for restricting the amount of data stored in the central data TEDW repository The data is also cleaned and consolidated in order to allow the data model of the central repository to share common dimensions For example TEDW ensures that the time host name and IP address are the same dimensions across all the applications
60. End e business Transaction Management Made Easy To stop and start the Management Agent you have to restart the following service Tivoli TransPerf Service Tip Stopping the Management Agent will generally stop all of the associated behavior services however in the case of the QoS we found that stopping the Management Agent would sometimes not stop the QoS service If the QoS service does not stop you will have to stop it manually To redirect a Management Agent to another Store and Forward agent or directly to the Management Server these steps need to be followed Open the MA_installation_folder config endpoint properties file Change the endpoint msurl https servername 443 option to the new Store and Forward or Management Server host name Restart the Management Agent service Important The Management Agent can not be redirected to a different Management Server without reinstallation To redirect a Store and Forward agent from one Store and Forward agent or to the Management Server directly follow these steps Open the SnF_installation_folder config snf properties file Edit the proxy proxy htips ibmtiv4 itsc austin ibm com 9446 tmtp option for the new Store and Forward or Management Server host name Restart the Store and Forward agent service The following parameters are listed in the endpoint properties file however changing them here will not affect the Management Age
61. Enterprise module also provides unique recording and playback functions for transaction simulation of 3270 and SAP Chapter 1 Transaction management imperatives 35 applications and a generic recording playback solution to be used only on Windows based systems 36 End to End e business Transaction Management Made Easy IBM Tivoli Monitoring for Transaction Performance in brief This chapter provides a high level overview of the functionality incorporated in IBM Tivoli Monitoring for Transaction Performance Version 5 2 We also introduce some of the reporting capabilities provided by TMTP Copyright IBM Corp 2003 All rights reserved 37 2 1 Typical e business transactions are complex Figure 2 1 depicts a typical e business application Typically it will involve multiple firewalls and an application that will have many components distributed across many different servers Web Application Customer account written in J2EE data held on legacy Customers and hosted on system Web Application Servers T RDBMS Edge Server Ps Middleware A m y Web 4 k BPS Servers App Legacy Servers Systems Figure 2 1 Typical e business transactions are complex As you can tell from Figure 2 1 there are also multiple machines doing the same piece of work as is indicated by the duplication of the Web servers application servers and databases This level o
62. However one disadvantage of this setup is that the QoS system introduces a potential bottleneck and a single point of failure Another disadvantage is that there is no distinction in the metrics measured for the different servers as the base for the distinguishing where the metrics come from is the QoS and not the back end Web servers To set up a single QoS Agent to measure multiple back end servers please understand that because the QoS acts as a front end for the back end Web server the browsers connect to the QoS rather than to the Web server If the QoS is to act as a front end for different servers it must have a separate identity for each server it serves as a front end for To define separate identities a virtual host has to be defined in the QoS HTTP server for each back end server These virtual servers may be either address or name based Address based The QoS has multiple IP addresses and multiple network interfaces each with its own host name Name based The QoS has multiple host names pointing to the same IP address Both ways imply that the DNS server must be aware that the QoS has multiple identities Definitions of virtual servers are after initial deployment of the Quality of Service component performed by manually editing the HTTP configuration file on the QoS system Example 8 2 shows an HTTP configuration file http conf fora QoS system named tivlab01 9 3 5 14 which the alias of tiviab02 9 3 5 14 which is co
63. IBM Tivoli Monitoring for Transaction Performance Version Figure 10 11 TEDW installation Installation running 11 Once the installation is finished the Installation summary dialog appears as shown in Figure 10 12 If the installation was not successful check the TWHApp log file for any errors This log file is located in the lt TWH_inst_dir gt apps AMX where lt TWH_inst_dir gt is the TEDW installation directory amp Tivoli Enterprise Data Warehouse Installation Installation Summary IBM Tivoli Monitoring for Transaction Performance Version 5 2 0 Warehouse Enablement Pack Version 5 1 0 5 CDYVIACOOO Installation of the application packages completed successfully Tivoli InstallShield Finish Figure 10 12 Installation summary window Chapter 10 Historical reporting 391 Existing TMTP warehouse pack installation Use the following installation steps to install an existing IBM Tivoli Monitoring for Transaction Performance Web Transaction Performance Version 5 1 0 warehouse pack Version 1 1 0 1 2 3 Back up the TWH_CDW database before you perform the upgrade Go to the lt TWH_DIR gt install bin directory Run the command sh tedw_wpack_patchadm sh to generate a configuration template file The default file name for the configuration file is lt USER_HOME gt LOCALS 1 Temp twh_app_patcher cfg Skip this step if this file already exists Edit the configuration file to set the parameter
64. MA_INSTRUMENT lib config properties Dcom ibm tivoli transperf logging baseDir MA_INSTRUMENT appServe rs 130 Dcom ibm tivoli jiti logging Logginglmpl com ibm tivoli transperf instr controller TMT PConsoleLoggingImpl Dcom ibm tivoli_jiti logging FileLogginglmpl logFileName MA_INSTRUMENT BWM logsi jiti log Dcom ibm tivoli jiti logging NativeFileLogginglmpl logFileName MA_INSTRUMENT BWM logs native log Dcom ibm tivoli jiti probe directory E MA app instrument appServers lib Dcom ibm tivolijiti registry Registry serializedFileName MA_INSTRUMENT lib registry ser Djlog propertyFileDir MA_INSTRUMENT_APPSERVER_CONFIG Dws ext dirs E MA app instrument appServers lib 8 Click the OK button 9 Click the Save Configuration link at the top of the page 10 Click the Save button on the new page that appears 11 In order to remove TMTP files that have been installed under the WebSphere Application Server directory all application servers running on this node must be shutdown Stop each application server with the stopServer command 12 After each application server has been stopped remove the following nine files from the directory lt WAS_HOME gt AppServer lib ext where lt WAS_HOMEs is the home directory where WebSphere Application Server is installed armjni jar copyright jar core_util jar ejflt jar eppam jar jffde jar jfltjar jlog jar probes jar 13 Remove the file lt WAS_HOME gt AppServe
65. Monitoring for Transaction Performance and discusses the transaction monitoring needs of an e business in particular the need for monitoring J2EE based applications The target audience for this section is decision makers and others that need a general understanding of the capabilities of IBM Tivoli Monitoring for Transaction Performance and the challenges from a business perspective that the product helps address This section is organized as follows gt Chapter 1 Transaction management imperatives on page 3 Copyright IBM Corp 2003 All rights reserved xxi gt Chapter 2 IBM Tivoli Monitoring for Transaction Performance in brief on page 37 gt Chapter 3 IBM TMTP architecture on page 55 Part 2 Installation and deployment on page 83 is targeted towards persons that are interested in implementing issues regarding IBM Tivoli Monitoring for Transaction Performance In this section we will describe best practices for installing and deploying the Web Transaction Performance components of IBM Tivoli Monitoring for Transaction Performance Version 5 2 and we provide information on how to ensure the operation of the tool This section includes gt Chapter 4 TMTP WTP Version 5 2 installation and deployment on page 85 gt Chapter 5 Interfaces to other management tools on page 153 gt Chapter 6 Keeping the transaction monitoring environment fit on page 177 Part 3 Using TMTP to measure
66. Organization of IBM Denmark as a Distributed Systems Management Specialist where he was xxii End to End e business Transaction Management Made Easy involved in numerous projects designing and implementing systems management solutions for major customers of IBM Denmark Sanver Ceylan is an Associate Project Leader at the International Technical Support Organization Austin Center Before working with the ITSO Sanver worked in the Software Organization of IBM Turkey as an Advisory IT Specialist where he was involved in numerous pre sales projects for major customers of IBM Turkey Sanver holds a Bachelors degree in Engineering Physics and a Masters degree in Computer Science Mahfujur Bhuiyan is a Systems Specialist and Certified Tivoli Enterprise Consultant at TeliaSonea IT Service Sweden Mahfujur has over eight years of experience in Information Technology with a focus on systems and network management and distributed environment and was involved in several projects in designing and implementing Tivoli environments for TeliaSonena s external and internal customers He holds a Bachelors degree in Mechanical Engineering and a Masters degree in Environmental Engineering from the Royal Institute of Technology KTH Sweden Valerio Graziani is a Staff Engineer at the IBM Tivoli Laboratory in Italy with nine years of experience in software development and verification He currently leads the System Verification Test on IBM Tivoli Monitori
67. S thinkAndy set MA_INSTRUMENT MA app instrument if SSERVER_NAME thinkAndy set JITI_OPTIONS Xbootclasspath a MA_INSTRUMENT 1ib jiti jar MA_INSTRUMENT 1ib bootic jar MA_INSTRUMENT ic config MA_INSTRUMENT appServers 169 config Xrunjitipi MA_INSTRUMENT 1ib jiti properties Dcom ibm tivoli jiti config MA_INSTRUMENT 1ib config properties Dcom ibm tivoli transperf logging baseDir MA_INSTRUMENT appServers 169 Dcom ibm tivoli jiti logging ILoggingImpl com ibm tivoli transperf instr contr oller TMTPConsoleLoggingImp1 Dcom ibm tivoli jiti logging FileLoggingImp logFileName MA_INSTRUMENT BWM 1 ogs jiti log Dcom ibm tivoli jiti logging NativeFileLoggingImp1 logFileName MA_INSTRUMENT BWM logs native log Dcom ibm tivoli jiti registry Registry serializedFileName MA_INSTRUMENT 1ib WLRegistry ser Djlog propertyFileDir MA_INSTRUMENT appServers 169 config if SSERVER_NAME thinkAndy set JAVA_OPTIONS JITI_OPTIONS JAVA_OPTIONS if SSERVER_NAME thinkAndy set CLASSPATH CLASSPATH C beaHome701 weblogic700 server 1lib ext probes jar C be Chapter 6 Keeping the transaction monitoring environment fit 201 aHome701 weblogic700 server 1lib ext ejflt jar C beaHome701 weblogic700 server lib ext jflt jar C beaHome701 weblogic700 server lib ext jffdc jar C beaHome7 01 weblogic700 server lib ext jlog jar C beaHome701 weblogic700 server lib ext copyright jar C beaHome701 weblogic700 server
68. Self Signed Certificate menu We name the new certificate prodsnf and the organization IBM The procedure for the KDB file creation is finished after pressing the OK button see Figure 4 14 on page 101 100 End to End e business Transaction Management Made Easy 4 Create New Self Signed Certificate xi Please provide the following Key Label Version Key Size Cammon Name Organization prodsnf X509V3 v 1024 v ib mtiv4 itsc austin ib m com BM Organization Unit optional Locality optional State Province optional Zipcode optional Country or region US v validity Period 365 Days Reset Cancel Help oK K Figure 4 14 Create new self signed certificate 9 Exchanging certificates The next step is to exchange the certificates between the JKS and KDB files In Figure 4 15 on page 102 the arm files represent the self signed certificates We have created a self signed certificate for each JKS and KDB file The next task is to import these certificates into the relevant JKD or KDB files Chapter 4 TMTP WTP Version 5 2 installation and deployment 101 Management Server lt 4 SOA A eel Agent prodms jks proddmz jks prodms arm proddmz arm prodsnf kdb prodsnf arm Management Agent Management Agent direct MS connection SnF connection
69. Transaction which most likely is the one you recorded and registered in the previous step described in 8 4 3 Transaction recording and registration on page 245 Define the Playback Settings that applies to your transaction Your choices on this dialog will affect the operation and data gathering performed during playback Some key factors to be aware of are e You may choose to click the Enable Page Analyzer Viewer for a playback When enabled data related to the time used to retrieve and render subdocuments of a Web page are gathered during the playback e By enabling Abort On Violation you decide whether or not you want STI to abort a playback iteration if a subtransaction fails Normally STI aborts a playback if one of the subtransactions fails For example a playback is aborted when a requested Web page cannot be opened If Abort On Violation is not enabled STI continues with the playback and attempts to complete the transaction after a violation occurs Note If a threshold violation occurs a Page Analyzer Viewer record is automatically uploaded even if the Enable Page Analyzer Viewer option is not selected This ensures that you receive sufficient information about problems that occur Configure STI settings You can specify four different types of thresholds e Performance e HTTP Response Code e Desired Content not found e Undesired contents found It is possible to create multi level performance thresholds
70. Transaction Performance provides functions to monitor e business transaction performance in a variety of situations Focusing on e business transactions it should come as no surprise that the product provides functions for transaction performance measurement for various Web based transaction types originating from external systems systems situated somewhere on the Internet and not managed by the organization that provide the e business transactions or applications that are the target of the performance measurement These transactions are referred to in the following pages as Web transactions and they are implemented by the Web Transaction Performance module of IBM Tivoli Monitoring for Transaction Performance In addition a set of functions specifically designed to monitor the performance metrics of transactions invoked from within the corporate network known as enterprise transactions are provided by the product s Enterprise Transaction Performance module The main function of Enterprise Transaction Performance is to monitor transaction performance of applications that have transaction performance probes ARM calls included In addition Enterprise Transaction Performance provides functions to monitor online transactions with mainframe sessions 3270 and SAP systems non Web based response times for transactions with mail and database servers and Web based transactions with HTTP servers as shown in Figure 1 13 on page 34 It should be no
71. Transaction Performance with IBM TMTP 5 1 SG24 6912 ETP provides four ways of measuring transaction performance ARMed application Predefined Enterprise Probes Client Capture browser based Record and Playback vvvy However the base technology used in probes Client Capture and Record and Playback is that of ARM Enterprise Transaction Performance provides the means to capture and manage transaction performance data generated by ARM calls It also provides a set of ARMed tools to facilitate data gathering and provide transaction performance data from applications that are not ARMed themselves End to End e business Transaction Management Made Easy Applications that are ARMed issue calls to the Application Response Measurement API to notify the ARM receiver in this case implemented by Tivoli about the specifics of the transactions within the application The probes are predefined ARMed programs provided by Tivoli that may be used to verify the availability of and the response time to load Web sites mail servers Lotus Notes Servers and more The specific object to be targeted by a probe is provided as run time parameters to the probe itself Client Capture acts like a probe When activated it scans the input buffer of the browser of a monitored system typically an end user s workstation for specific patterns defined at the profile level and records the response time of all page loads which matches the patterns specifi
72. WebSphere Application Server or Weblogic Provides transaction and subtransaction data that may be used for performance topology and problem analysis Generic Windows Provides similar functionality as STI however the Rational Robot implementation allows for recording and playback of any Windows based application not specific to the Microsoft Internet Explorer browser but does not provide the same detailed level of data regarding times for building the end user browser based dialogs These four components may be used alone or in conjunction Using STI or Generic Windows to play back a pre recorded transaction that targets a URI owned by the QoS endpoint and is routed to a Web Server monitored by a J2EE endpoint will basically provide all the performance data available for that specific instance of the transaction The following sections provide more details that will help decide which measurement tools to use in specific circumstances Chapter 8 Measuring e business transaction response times 229 Synthetic Transaction Investigator TMTP STI can be used as a synthetic transaction playback and investigator tool for any Web server such as Apache IBM HTTP server Sun One formerly known as iPlanet and Microsoft Internet Information Server and with J2EE applications hosted by WebSphere Application Server and BEA Weblogic application servers Synthetic Transaction Investigator is simple to use It is easy to record synthetic tran
73. and fully integrated management solution can be deployed rapidly and provide a very attractive return on investment Chapter 1 Transaction management imperatives 27 1 4 Tivoli product structure Let us take a look at how Tivoli solutions provide comprehensive systems management for the e business enterprise and how the IBM Tivoli Monitoring for Transaction Performance product fits into the overall architecture In the hectic on demand environments e businesses find themselves in today responsiveness focus resilience and variability flexibility are key to conducting business successfully Most business processes rely heavily on IT systems so it is fair to say that the IT systems have to possess the same set of attributes in order to be able to keep up with the speed of business To provide an open framework for the on demand IT infrastructure IBM has published the On Demand Blueprint which defines an On Demand Operating Environment with three major properties Figure 1 10 Integration Efficient and flexible combination of resources people processes and information to optimize resources across and beyond the enterprise Automation The capability to dynamically deploy monitor manage and protect an IT infrastructure to meet business needs with little or no human intervention Virtualization Present computer resources in ways that allows users and applications to easily get value out of them rather than presenting them in ways
74. app action portfolio trade_2_stockcheck_tiviab01 Configure System E Component Manage Configure User Sett Work with Event Re View System Event Seconds a amp N a View Log Files View Management b Downloads 00 10 01 10 02 10 02 10 02 10 02 21 00 03 00 09 00 15 00 21 00 Time Year Month Day Hour Minute Start Time 2003 7j 10 yj 1 7 21 00 Stop Time 2003 10 2 ae 21 gt foo x a Ay tes Figure 8 47 Trade transaction and subtransaction response time by STI From the Transaction with Subtransaction report for the trace_2_stock check we see that the total User Experience Time to complete the order is 6 34 sec This is measured by STI We can drill down into the Trade application and see every subtransaction response time maximum of five subtransactions and understand how much time is used by every piece of the Trade business transaction Click on any subtransaction in the report and it will drill down into the Back End Service Time for the selected subtransaction If this is repeated TMTP will display the response times reported by the J2EE application components for the actual subtransaction As an example Figure 8 50 on page 301 shows the Back End Service Time for the step_3 app subtransaction 298 End to End e business Transaction Management Made Easy Tivoli Monitoring for Transaction Performance User Name administrator
75. are only generated and displayed in the Component Event view accessed by selecting View Component Events from the Reports menu in the Navigation area IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer E O x Fie Edt View Favorites Tools Help Address a http itivdce4 9082 tmtput jsp console wcFrameManager jsp z Eo Ea my w Tivoli Monitoring for Transaction Performance User Name Administrator Peon i Configure Generic Windows Thresholds Work with AAE LE Work with Performance hd Create Alt e Configure Generic Windows Thresholds se Agent Group MASHER Assign Name Era i Violation Response Level Violation Response Recovery Resp Work with Threshold Configure I Performance Above 5 0 Seconds Warning ChangeBufferSize Harmless Componer M Transaction Status Becomes equal Failure Waring ChangeBufferSize Harmless Configure p 1 Work with rE Show Enabled Thresholds C Show Disabled Thresholds gt Downloads lt Back Alt b Next Alt n gt Finish At Cancel Alt c plm F Figure 9 43 Configure Generic Windows Thresholds Note If you are unsure what thresholds to set you may take advantage of TMTP s automatic baseline and thresholding mechanism This is explained in 8 3 Deployment configuration and ARM data collection on page 239 5 Configure the schedule you wish
76. bin ijitipi dll file if it exists Some OS platforms use jitipi dll and some OS platforms use ijitipi dll Note The ijitipi dll file may not exist in lt WL7_HOME gt server bin depending on the version of J2EE Instrumentation If it does not exist in this directory it is in the Management Agent s directory and can be left in the Management Agent s directory without any harm 6 6 TMTP Version 5 2 best practices This section describes our recommendations on how to implement and configure TMTP Version 5 2 to maximize effectiveness and performance in your production environment Please note that although the following recommendations are general and suitable to most typical production environments you may need to customize configurations for your environment and particular requirements Overview of recommendations gt Use the following default J2EE Monitoring settings for long term monitoring during normal operation in the production environment Only record aggregate records Discovery Policies for J2EE and QoS transactions should be run and then disabled once listening policies have been created off the discovered transactions Note The Discovery Policies may be re enabled at a future date if further transaction discovery is required Use a 20 sampling rate Set low tracing detail gt Define the URI filters as narrow as possible to match the transaction patterns you are interested in monitoring This will optimize
77. cee eee 160 Discover WebSphere Resources 00000 00 eee eens 161 WebSphere managed application object icons 162 Example for an IBM Tivoli Monitoring Profile 167 Web Health Console using WebSphere Application Server 171 Configure User Setting for ITM Web Health Console 174 WebSphere started without sourcing the DB2 environment 179 Management Server ping output 00000 e eee eee 180 MBean Server HTTP Adapter 0 000 c eee eee eee eee 183 Duplicate row atthe TWH_CDW 0 00 c eee eee eee 192 Rational Project exists error message 0 eee eee eee 196 WebSphere 4 Admin Console 0000 0c eee eee eens 197 Removing the JVM Generic Arguments 0 000 0005 199 WebLogic class path and argument settings 202 Configuring the J2EE Trace Level 0000e eee cence 206 Configuring the Sample Rate and Failure Instances collected 207 The Big Board cd etacteaiat E aoe dhdtataeh deeds Gatcty aydeeds 214 Topology Report 0 00 cece E ERIN E eee 216 Node context reports 0 2 6 ee eee 217 Topology Line Chart 00000 cece tte eee 218 STL REPOMS i sie sede dotoaes pata a a a dead a E Etcte eke 219 General TepOmns res tarin eta nee ot L E whee eae 220 Transactions with Subtransactions report 00000 221 Figures Xi xii 7 9 8 1 8 2 8 3 8 4 8
78. command after deploying a new application gt You can view a transaction path in Topology gt Itis easy to discover the root cause of a performance problem gt You can discover new transactions you were not aware of in your environment gt You can dynamically configure tracing details gt You can run monitoring at a low trace level during normal operation gt You can increase to a high tracing level after a problem is detected 3 4 Security features TMTP Version 5 2 includes features to allow your transaction monitoring infrastructure to be secure The key features that support secure implementations are shown in the following sections SSL communications between components SSL is a security protocol that provides for authentication integrity and confidentiality Each of the components of TMTP Version 5 2 WTP can optionally be configured to utilize SSL for communications 76 End to End e business Transaction Management Made Easy A sample HTTP based SSL transaction using server side certificates follows 1 The client requests a secure session with the server 2 The server provides a certificate its public key and a list of its ciphers to the client 3 The client uses the certificate to authenticate the server that is to verify that the server is who they claim to be 4 The client picks the strongest cipher that they have in common and uses the server s public key to encrypt a newly generated session key
79. credit card and insurance company online apps Appendix A Patterns for e business 435 Composite patterns Trading Exchange fee ee Allows buyers and sellers to trade goods and services ona public site gt Buyer s side Interaction between buyer s procurement system and commerce functions of e Marketplace Seller s side Interaction between the procurement functions of the e Marketplace and its suppliers Sell Side Hub Supplier The seller owns the e Marketplace and uses it as a vehicle to sell goods and services on the Web www carmax com car purchase Buy Side Hub Purchaser The buyer of the goods owns the e Marketplace and uses it as a vehicle to leverage the buying or procurement budget in soliciting the best deals for goods and services from prospective sellers across the Web www wre org WorldWide Retail Exchange The makeup of these patterns is variable in that there will be basic patterns present for each type but the Composite can easily be extended to meet additional criteria For more information about Composite patterns refer to Patterns for e business A Strategy for Reuse by Adams et al Selecting Patterns and product mapping After the appropriate Business pattern is identified the next step is to define the high level logical components that make up the solution and how these components interact This is known as the Application pattern A Business pattern will us
80. dictated by the implementation geographical location or physical packaging Aitomation On Demand Operating Environment Figure 1 10 The On Demand Operating Environment 28 End to End e business Transaction Management Made Easy The key motivators for taking steps to align the IT infrastructure with the ideas of the On Demand Operating Environment are Align the IT processes with business priorities Allow your business to dictate how IT operates and eliminate constraints that prohibits the effectiveness of your business Enable business flexibility and responsiveness Speed is the one of the critical determinants of competitive success IT processes that are too slow to keep up with the business climate cripples corporate goals and objectives Rapid response and nimbleness mean that IT becomes an enabler of business advantage versus a hindrance Reduce cost By increasing the automation in your environment immediate benefits can be realized from lower administrative costs and less reliance on human operators Improved asset utilization Use resources more intelligently Deploy resources on an as needed just in time basis versus a costly and inefficient just in case basis Address new business opportunities Automation removes lack of speed and human error from the cost equation New opportunities to serve customers or offer better services will not be hampered by the inability to mobilize resources in time
81. display recently collected data in a variety of formats and from a variety of perspectives gt Integrate with the Tivoli Enterprise Date Warehouse where you can store collected data for use in historical analysis and long term planning gt Receive prompt automated notification of performance problems With IBM Tivoli Monitoring for Transaction Performance you can effectively measure how users experience your Web site and applications under different conditions and at different times Most important you can quickly isolate the source of performance problems as they occur so that you can correct those problems before they produce expensive outages and lost revenue 2 2 1 TMTP 5 2 components IBM Tivoli Monitoring for Transaction Performance provides the following major components that you can use to investigate and monitor transactions in your environment Discovery component The discovery component enables you to identify incoming Web transactions that need to be monitored 40 End to End e business Transaction Management Made Easy Two listening components Listening components collect performance data for actual user transactions that are executed against the Web servers and Web application servers in your environment For example you can use a listening component to gauge the time it takes for customers to access an online product catalog and order a specific item Listening components also called listeners are the Quality of
82. display the return of each of the ARM API calls The returns should be arm_init positive integer arm_getid positive integer arm_start positive integer arm_stop 0 zero arm_end 0 zero In production you will want to comment out these MsgBox statements Here is the script file that we ended up with Version 1 1 Some declarations modified Declare ARM API functions arm_update is not declared since TMTP doesn t use it Declare Function arm_init Lib libarm32 ByVal appl_name As String ByVal appl_userid As String ByVal flags As Long ByVal data As String ByVal data_size As Long As Long Declare Function arm_getid Lib libarm32 ByVal appl_id As Long ByVal tran_name As String ByVal tran_detail As String ByVal flags As Long ByVal data As String ByVal data_size As Long As Long 452 End to End e business Transaction Management Made Easy Declare Function arm_start Lib libarm32 ByVal tran_id As Long ByVal flags As Long ByVal data As String ByVal data_size As Long As Long Declare Function arm_stop Lib libarm32 ByVal start_handle As Long ByVal tran_status As Long ByVal flags As Long ByVal data As String ByVal data_size As Long As Long Declare Function arm_end Lib libarm32 ByVal appl_id As Long ByVal flags As Long ByVal data As String ByVal data_size As Long As Long Sub Main Dim Result As Integer Initially Recorded 1 31 2003 4 12 02 PM Script Name testl Declare variables to hold returns fr
83. ees 87 WebSphere information screen 0 0 cee eee 92 koyman utility 43 08 owas EN had Shas Pode ees EES 93 Copyright IBM Corp 2003 All rights reserved ix x 4 39 4 40 4 41 4 42 4 43 4 44 4 45 4 46 Creation of custom JKS file 0 ee 94 Set password for the JKS file 2 0 0 0 0c eee 94 Creating a new self signed certificate 00 00 00s 95 New self signed certificate options 000 eee eee ee 96 Password change of the new self signed certificate 97 Modifying self signed certificate passwords 2055 97 GSkKit new KDB file creation 0 00 0 cece eee ee 99 CMS key database file creation 0 000 99 Password setup for the prodsnf kKdb 00 cee eee eee 100 New Self Signed Certificate menu 20000 eee 100 Create new self signed certificate 0 000 eee eae 101 Trust files and certificates 0 0 02 eee 102 The imported certificates 0 0 0 eee ee 103 Extract Certificate ne pcan asan d joe vob Sta ee hatisk ad 104 Extracting certificate from the msprod jks file 104 Add a new self signed certificate 0 0 0 eee eee eee 105 Adding a new self signed certificate 0 0 00a 105 Label for the certificate 2 ee 106 The imported self signed certificate 0 c ee eee 106 Welcome screen on the Management Server installation wiza
84. existing administrative user account If the user is not already a member of the Administrators group the user will be added OR Create a dedicated administrative user account The default name is TMTPAgent You have the option to change this name to a unique string Specify an existing user account Create a new dedicated user account User Administrator Password F Verify Password Ez InstallShield Back Next gt j Cancel Figure 4 49 Local user account specification 8 We press Next on the installation summary window Figure 4 50 on page 135 134 End to End e business Transaction Management Made Easy Install Management Agent A ol x 3 IBM Tivoli Monitoring for Transaction Performance Management Agent A will be installed in the following location C Program FilesiBMiTivoliiMaA for a total size 49 1MB InstallShield Cancel Figure 4 50 Installation summary window Press the Finish button in the window shown in Figure 4 51 on page 136 to finish the installation Chapter 4 TMTP WTP Version 5 2 installation and deployment 135 Install Management Agent ig 5 x The InstallShield Wizard has successfully installed IBM Tivoli Monitoring for Transaction Performance Management Agent Choose Finish to exit the wizard installShield Figure 4 51 The finished installation 9 All Management Agents must be installed with the same parameters in the intra
85. file size support DB2 defaults to this but double check in etc security olimits The instance owner should have fsize 1 208 End to End e business Transaction Management Made Easy Part 3 Using TMTP to measure transaction performance This part discusses the use of TMTP to measure both actual real time end user as well as simulated transaction response times Copyright IBM Corp 2003 All rights reserved 209 210 The information is divided into the following main sections Chapter 7 Real time reporting on page 211 This chapter introduces the reader to the various reporting options available to users of TMTP both real time and historical Chapter 8 Measuring e business transaction response times on page 225 This chapter focuses on how to set up and deploy TMTP to capture real time experiences as experienced by the end users Real time end user measurement by Quality of Service and J2EE are introduced and the use of subtransaction analysis and back end service time from Quality of Service are demonstrated along with the use of correlation of the information to identify the root cause of e business transaction problems Chapter 9 Rational Robot and GenWin on page 325 This chapter demonstrates how to use the Rational Robot to record e business transactions how to instrument those transactions in order to generate relevant e business transaction performance data and how to use TMTP s GenWi
86. for J2EE trade_qos_lis Listening policy for QoS trace_2_stock check STI Playback policy 8 7 2 Looking at subtransactions Now to get a snapshot of the overall performance we open the Transactions with Subtransactions report for the trace_2_stock check policy The overall and subtransaction times are depicted in Figure 8 47 on page 298 Chapter 8 Measuring e business transaction response times 297 4 IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer Fle Edit View Favorites Tools Help Address x http itivdce4 9082 tmtpU jsp console wcFrameManager jsp Tivoli Monitoring for Transaction Performance Configuration General Reports gt Transaction With Subtransactions Work with Discover Work with Listening Change settings ya m RA Policy trade_2_stockcheck tivlabO Muh ned Management Agent tivlab01 Work with Agent Gi Work with Transact Transaction trade_2_stockcheck_tivlab0 Work with Realms Q 0 vReports SS Zs endl View Big Board View General Repo 8 58 N E Step_3_httpvibmtiva itsc austin ibm com 82 tradelapp View Component E vSystem Administra E Step_1_http ipmtiv9 itsc austin ibm com 82 trade Work with Agents 6 45 F E _ Step_4_http ibmtiv9 itsc austin ibm com 82 trade app action quotes amp symbols s 0 S E Step_6_http ipmtiv9 itsc austin ibm com 82 trade app action logout Step_5_http ibmtiv9 itsc austin ibm com 82 trade
87. from TMTP TMTP Version 5 2 General Reports such as Overall Transaction Over Time Availability and Transaction with Subtransaction can be used for viewing a transaction report over a short period of time but are not recommended for reporting over longer periods To see a general report of every Trade or Pet Store listening policy and playback policy navigate to the General Reports and select the specific type of your interest Change the settings to view data related to the specific policy and time period of your choice An example of a Transaction With Subtransaction report is shown in Figure 10 22 on page 406 Chapter 10 Historical reporting 405 Et Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer ae z _ 5 xj File Edt View Favortes Toos Help p l Heak gt O A A Asearch Favorites Bristory E4 SH Address http tivdce4 9082 tmtpUI jsp console WwcFrameManager jsp Go Tivoli Monitoring for Transaction Performance User Name administrator General Reports gt Transaction With Subtransactions 3 Change settings Policy petstore_2_order_tivlab01 Management Agent tivlab01 Transaction petstore_2_order_tivlab01 Dao poue Step_1_http tiviab01 itsc austin ibm com petstore main screen E Step_8_http tiviab01 itsc austin ibm com petstore order do give Step_3_http tiviabO1 itsc austin ibm com petstore _signon_c
88. get level 3 logging These two keys ENGINE INTERNALS IPCAppToEngSize 500 IPCEngToAppSize 500 define the size of internal buffers used for communications between ARM instrumented applications and the ARM engine The IPCAppToEngSize key defines the number of elements used for ARM instrumented applications to communicate to the ARM engine Likewise the IPCEngToAppSize key defines the number of elements used for communications from the ARM engine back to the ARM instrumented applications In this example 500 elements are assigned to each of these buffers The larger these buffers are the more memory is taken up by the ARM engine If the application being monitored is a single threaded application and only one application is being monitored then these numbers can be decreased This is not normally the case Most applications are multithreaded and need a large number of entries here If the number of entries is set too low applications making many calls to the ARM engine will be blocked by the ARM engine until an unused entry is found that will slow the ARM instrumented application In general changes to these two entries should only be necessary on a UNIX Management Agent and the values for the two entries should be kept the same If the ARM engine will not start and the log file shows errors in IPC attempt to lower these values Chapter 6 Keeping the transaction monitoring environment fit 185 Some other interesting key value
89. hosting IBM WebSphere Application Server that you want to manage with IBM Tivoli Monitoring for WebSphere Application Server gt IBM Tivoli Monitoring for WebSphere Application Server supports only one installation of WebSphere Application Server on each host system gt If security is enabled for IBM WebSphere Application Server you should create a security properties file for the wscp client so that it can be authenticated by the server You can copy the existing sas client props file in the WAS_HOME Properties directory 6WAS_HOME is the directory where you have installed your WebSphere Application Server to sas wscp props and edit the following lines com ibm CORBA loginSource properties com ibm CORBA 1 oginUserid lt userid gt com ibm CORBA 1oginPassword lt password gt where lt userid gt is the IBM WebSphere Application Server user ID and lt password gt is the password for the user gt If you are using a non default port for IBM WebSphere Application Server you need to change the configuration of the endpoint in order to communicate with the IBM WebSphere Application Server object You can do this by changing the port setting in the sas wscp props file You can create the file in the same way as mentioned above and then add the following line wscp hostPort lt port_number gt where lt port_number gt is the same value specified for property com ibm ejs sm adminServer bootstrapPort in 156 End to End e bus
90. monitoring overhead during normal operation in the production environment The narrow URI filters also help the effectiveness of analysis of TMTP reports as you can selectively investigate transaction data of interest gt It is suggested to avoid using regular expressions that contain wildcard in the middle of URI filter if possible gt Only turn up the tracing details when a performance or availability violation is detected for the J2EE application server to allow for quick debugging of the 204 End to End e business Transaction Management Made Easy situation It is recommended for high traffic Web sites to set the Sample Rate lower than 20 when a tracing detail higher than the Low level is used Setting the maximum number of sample per minute instead of the sample rate is also recommended to better regulate monitoring overhead during a high traffic period gt Ina production environment we recommend collecting Aggregate Data Only TMTP will automatically collect a certain number of Instance records when a failure is detected It is not recommended to collect Aggregate and Instance records during normal operation in a production environment as it may generate overwhelming data gt Ina large scale environment with more than 100 Management Agents uploading ARM data to the Management Server database the scheduled data persistence may take more than a few minutes As disk access may be a bottleneck for persisting or retri
91. more detail The Management Server The Management Server is shared by all IBM Tivoli Monitoring for Transaction Performance components and serves as the control center of your IBM Tivoli Monitoring for Transaction Performance installation The Management Server collects information from and provides services to the Management Agents deployed in your environment Management Server components are Java Management Extensions JMX MBeans Deployed as a standard WebSphere Version 5 0 1 EAR file the Management Server provides the following functions gt User interface You can access the user interface provided by the Management Server through a Web browser running Internet Explorer 6 or higher From the user interface you create and schedule the policies that instruct monitoring components to collect performance data You also use the user interface to establish acceptable performance metrics or thresholds define notifications for threshold violations and recoveries view reports view system events manage schedules and perform other management tasks Chapter 3 IBM TMTP architecture 61 gt Real time reports Accessed through the user interface real time reports graphically display the performance data collected by the monitoring and playback components deployed in your environment The reports enable you to quickly assess the performance and availability of your Web sites and Microsoft Windows applications gt Event system The M
92. more information through the JVMPI for example the profiler agent can turn on off a specific event notification based on the needs of the profiler front end As shown by Figure 3 8 on page 75 JITI starts when the application classes are loaded by the JVM for example the WebSphere Application Server The Injector alters the Java methods and constructors specified in the registry by injecting special byte codes in the in memory application class files These byte codes include invocations to hook methods that contain the logic to manage End to End e business Transaction Management Made Easy the execution of the probes When a hook is executed it gets the list of probes currently enabled for its location from the registry and executes them original application catalog EJB catalog EJB order Enable disable EJB probes Management order aplication EJB servlet Load Tivoli Just in Time Instrumentation Execute probes G Get enabled locations probes managed application Figure 3 8 Tivoli Just in Time Instrumentation overview TMTP Version 5 2 bundles JITI probes for Servlets also includes Filters JSPs Entity Beans Session Beans JMS JDBC RMI IIOP vvvvvy JITI combined with the other mechanisms included with TMTP Version 5 2 allow you to reconstruct and follow the path of the entire J2EE transaction through the enter
93. of every transaction subtransaction select General Reports Transaction with Subtransaction and use Change Settings to specify the particular policy for which you want see the details To see the STI playback policy topology view select Topology from the General Reports Now use Change setting on the STI playback policy you want to see details for and drill down to the created view to see STI QoS and J2EE transaction correlation using ARM For a discussion of transaction drill down using ARM and correlation please see 7 4 Topology Report overview on page 215 There are four additional options from a topology node Each of the following can be accessed using the context menu right click of any object in the topology report Events View View all the events for the policy and Management Agent Response Time View View the node s performance over time Web Health Console Launch the ITM Web Health Console for this Management Agent Thresholds View Configure a threshold for this node 8 7 1 Reporting on Trade If we consider an end user who uses a trade application for buying and selling stock the application probably uses several processes to buy and sell such as gt gt gt Browse to Trade Web site Log in to trade application Quote trade Buying selling Log out from the application 296 End to End e business Transaction Management Made Easy 2 0 x Z IBM Tivoli Monitoring for Transaction Pe
94. or improve the cooperation between QA and operations to make sure that the testing phase is a true preparation of the deployment phase and that many integration and performance problems are tackled beforehand 1 3 e business applications complex layers of services A modern e business solution is much more complex than the standard terminal processing oriented systems of the 1970s and 1980s as illustrated in Figure 1 2 on page 12 However despite major revisions especially during the turn of the last century legacy systems are still the bread and butter of many enterprises and the e business solutions in these environments are designed to front end these mainframe oriented application complexes Chapter 1 Transaction management imperatives 11 Central Site Internet Enterprise Network I Browser I m e business Browser e business with Legacy Systems m wt AL Browser Business Systems E 1 i L Applications Client Server n 1 Personal ami 1 Computer GUI Front End f l Personal Computer i Business Systems I Front End elude faa le i rocessing I I 1 Dumb Terminal Figure 1 2 Growing infrastructure complexity The complex infrastructure needed to facilitate e business solutions has been dictated mostly by requirements for standardization of client run time environments in order to allow any standard browser to access the e busin
95. orders you might need an option to cancel or back out of the playback user s business transaction records from the database 8 1 1 Naming standards for TMTP policies Before creating any policies a standard for naming discovery and listening policies should be developed This will make it easier and more convenient for users to recognize different policies according to customer name business application scope of monitored transactions and type of policy Developing and adhering to a naming standard will especially help in distinguishing different policies and creating different type of real time and historical reports from Tivoli Enterprise Date Warehouse One suggestion that may be used to name TMTP policies is lt customer gt _ lt application gt _ lt type of monitoring gt _ lt type of policy gt Using a customer name of telia and application name of trade the following examples would clearly convey the scope and type of different policies telia_trade_qos_lis telia_trade_qos_ dis telia_trade_j2ee_dis telia_trade_j2ee_lis telia_trade_sti_forever The discovery component of IBM Tivoli Monitoring for Transaction Performance enables you to identify incoming Web transactions that need monitoring When you use the discovery process you create a discovery policy in which you define the scope of the Web environment you want to investigate monitor for incoming transactions The discovery policy then samples transaction activity and p
96. page of the TMTP Version 5 2 console and use the left side navigation pane to select Configuration Work with Discovery Policies The Work with Discovery Policies dialog shown in Figure 8 27 on page 272 will be displayed Chapter 8 Measuring e business transaction response times 271 272 3 IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer Back gt i A Al Qsearch Favorites PMedia K Ehy 48 B e g File Edit View Favorites Tools Help address http tivdce4 itsc austin ibm com 9082 tmtpUI jsp console WcFrameManager isp ha Po Ea Tivoli Monitoring for Transaction Performance User Name administrator My Work Configuration Work with Discovery Policies Work with Listening Policies Work with Playback Policies Work with Schedules QoS a Create New Alt w Work with Agent Groups Work with Transaction Recordings Please make a selection o Alt Work with Realms Please make a selection b Reports create From Alt m ent Grou Schedule Status Sea Amnat Lm pi pelete re_j2ee_grp petstore_j2ee_dis In scheduled window ownloads H Disable I pdEdit re_qos_grp petstore_j2ee_dis In scheduled window m trie agen menean j2ee_grp itrade_dis_sch In scheduled window W trade_gos_dis QOS qos_grp itrade_dis_sch In scheduled window e ee Show Enabled Policies 2 C Show Disabled Policies ee ee aft
97. pairs include TransactionIDCacheSize 100000 This is the number of transactions that are allowed to be active at any specific point in time Once this limit is reached the least recently run transaction mapping is removed from memory and a arm_getid call must proceed any future start calls for that transaction ID mapping TransactionIDCacheRemoveCount 10 This is the number of transactions we flush from the cache when the above limit is reached PolicyCacheSize 100000 This is the number of transaction IDs to policy mappings kept in memory at any one time This saves TMTP from having to perform regular expression matches for every policy each time it sees a transaction Making this larger than TransactionIDCacheSize really does not have any value but setting it equal is a good idea This cache has to be flushed completely every time a management policy is added to the agent PolicyCacheRemoveCount 10 When the above cache size limit is reached this many entries are removed EdgeCacheSize 100000 This is the number of unique edges TMTP has seen that are kept in memory to avoid sending duplicate new edge notifications to the Management Server This cache can be lowered or raised freely depending on your memory consumption desired Lowering it can potentially cause more network agent and Management Server load but less memory requirements on the agent EdgeCacheRemoveCount 10 This is the number of edge entries to remove when the above l
98. perform preventive maintenance by filling up the tank 1 3 1 Managing the e business applications Specialized functions require specialized management and general functions require general management Therefore it is obvious that the management of the operating system hardware layer and networking layer may be may be general since they are used by most of the components of the e business infrastructure On the other hand a management tool for Web application servers might not be very well suited for managing the database server Up till now the term managing has been widely used but not yet explained Control over and management of the computer system and its vital components are critical to the continuing operation of the system and therefore the timely availability of the services and functions provided by the system This includes controlling both physical and logical access to the system to prevent unauthorized modifications to the core components and monitoring the availability of the systems as a whole as well as the performance and capacity usage of the individual resources such as disk space networking equipment memory and processor usage Of course these control and monitoring activities have to be performed cost effectively so the cost of controlling any resource does not become higher than the cost of the resource itself It does not make much business sense to spend 1000 to manage a 200 hard disk unless the data
99. performance measurements in a controlled environment This technique is used to provide baselining and to verify compliance with Service Level Objectives for pre recorded transactions For real time transactions J2EE monitoring is primarily used for monitoring a limited number of critical subtransactions and may be activated on the fly to help in problem determination and identification of bottle necks Details of the inner workings of the J2EE endpoint are provided in 3 3 2 J2EE instrumentation on page 72 and are depicted in Figure 3 8 on page 75 Note J2EE is the only IBM Tivoli Monitoring for Transaction Performance Version 5 2 monitoring component that is capable of monitoring the subtransaction response times within WebSphere Application Server and BEA Weblogic application servers Generic Windows The Generic Windows recording and playback component in TMTP Version 5 2 is based on technology from Rational which was acquired by IBM in 2003 Rational Robot s Generic Windows component is specially designed to measure performance and availability of Windows based applications Like STI Generic Windows GenWin performs analysis on synthetic transactions Like STI GenWin can record and playback Web browser based applications but in addition GenWin can record and playback any application that can run ona Windows platform provided the application performs some kind of screen interaction For playing back a GenWin recorded transac
100. point of contact for users of the service It registers incidents allocates severity and coordinates the efforts of support teams to ensure timely and accurate problem resolution Escalation times are noted in the SLA and are agreed on between the customer and the IT department The Help Desk also provides statistics to Service Level Management to demonstrate the service levels achieved Problem Management Problem Management implements and uses procedures to perform problem diagnosis and identify solutions that correct problems It also registers solutions in the configuration repository Escalation times should be agreed upon internally with Service Level Management during the SLA negotiation It also provides problem resolution statistics to support Service Level Management Change Management Change Management plans and ensures that the impact of a change to any component of a service is well known and that the implications regarding service level achievements are minimized This includes changes to the SLA documents and the Service Catalog as well as organizational changes and changes to hardware and software components Software Control and Distribution It is the responsibility of Software Control and Distribution to manage the master software repository and deploy software components of services It also deploys changes at the request of Change Management and provides management reports regarding deployment The key relationship
101. reported by the trade_2_stock check_tivlab01 played back STI transaction are fairly consistent in the seven second range Response Time vs Date 10 4 2003 10 2 2008 10 3 2003 10 1 2003 10 2 2003 10 3 2003 10 4 2003 105 2008 106 2008 Date Figure 10 34 trade_2_stock check_tivlab01 playback policy end user experience J2EE Response Time by date The J2EE Response Time by date report in Figure 10 35 on page 423 shows that special attention needs to be devoted to tuning the J2EE environment to make the response times from the J2EE backed transactions monitored by the trade_j2ee_lis listening policy more consistent 422 End to End e business Transaction Management Made Easy Response Time vs Date For E 1041 2008 E 106 200 E 107 2008 E 108 200 10 1 2003 10 6 2003 10 7 2003 10 2003 Response time based on Average case Figure 10 35 trade_j2ee_lis listening policy response time report The JDBC Response Time by date shown in Figure 10 36 on page 424 shows that after a problematic start on 10 1 the tuning activities of the database has had the desired effect Chapter 10 Historical reporting 423 JDBC Response Time by date Response Time vs Date For E 1014 2008 E 102 200 o 103 200 E 10200 E 105 200 E 106 200 10 4 2003 10 2 2003 10 3 2003 10 4 2003 10 5 2003 10 6 2003 Date Response time based on Average case Figure 10 36 Response time JDBC process Trade application
102. reporting may be set up to only handle transaction performance measurements from machines that have specific network addresses for example thus limiting the scope of the monitoring to well known machines However the transactions executed and the sequence is still random and unplanned The monitoring infrastructure used to capture performance metrics of the average transaction may also be used to measure transaction performance for specific pre planned transactions initiated from well known systems accessing End to End e business Transaction Management Made Easy the e business applications through the Internet or intranet To facilitate this kind of controlled measurements certain programs must be installed on the systems initiating the transactions and they will have to be controlled by the organization that wants the measurements From a transaction monitoring point of view there are no differences between monitoring average or controlled transactions the same data may be gathered to the same level of granularity The big difference is that the monitoring organization knows that the transaction is being executed as well as the specifics of the initiating systems The main functions provided by IBM Tivoli Monitoring for Transaction Performance Web Transaction Performance are gt For both unknown and well known systems Real time transaction performance monitoring Transaction breakdown Automatic problem identification a
103. run aul Figure B 10 Scheduler A wizard will guide you through the addition of a new scheduled task Select Rational Robot as the program you want to run Figure B 11 on page 455 454 End to End e business Transaction Management Made Easy Scheduled Task Wizard Click the program you want Windows to run To see more programs click Application BB Rational Sitecheck Rational Administrator 8 5 0 1003 ER Rational ERP gui 2 00 0011 ER Rational ERP vu 2 00 0011 QE Rational License Key Admini 2002 0500 0 E Rational ManualTest 8 5 0 1003 i inal Robot 8 5 0 1003 2001 4 04 00 a Browse Cancel Figure B 11 Scheduling wizard Name the task and set it to repeat daily Figure B 12 on page 456 You can set how often it repeats during the day later Appendix B Using Rational Robot in the Tivoli Management Agent environment 455 456 Scheduled Task Wizard o x Type a name for this task The task name can be the same name as the program name Rational Robot Perform this One time only C When my computer starts When log on Figure B 12 Scheduler frequency Set up the start time and date Figure B 13 on page 457 End to End e business Transaction Management Made Easy Scheduled Task Wizard gt Select the time and day you want this task to start Start time amam Perform this task Every Day Weekdays
104. scheduled distribution Click Finish to save the definition of the Quality of Service discovery profile see Figure 8 26 on page 271 270 End to End e business Transaction Management Made Easy Z IBM Tivoli Monitoring for Transaction Performan soft Internet Explorer Fie Edi Favorites Tools Tivoli Monitoring for Transaction Performance User Name administrator My Work Configuration Assign Name Work with Discovery Policies Work with Listening Policies dex Name Work with Playback Policies ninfe papa trade_qos_dis Work with Schedules sched Work with Agent Groups Ch 5 Description Work with Transaction Recordings P S QoS discovery for Trace reared Reams Sent to Agents at next interval b System Administration C Send to Agents now gt Downloads lt Back Alt b Next Alt n gt Finish Alt Cancel Alt c Figure 8 26 Assign name to new QoS discovery policy Create a listening policy for QoS The newly created discovery profile may be used as the starting point for creating the QoS listening policy the one that actually collects and reports on transaction performance data This will allow you to select transactions that have been discovered as the basis for the listening policy Listening policies may also be created directly without the use of previously discovered transactions To create a listening policy by using the data gathered by the discovery policy start by going to the home
105. started by the user by clicking on the Compile button to ensure that the script is formally correct or the compile stage can be left to Rational Robot that takes care of it whenever a change is done to the source Scripts are recorded with the rec extension their compiled form is sbx Include files have the sbh extension and are automatically compiled by Rational Robot so the user does not have to worry about them in any case Debugging scripts Rational Robot includes a fully functional debugging environment you can use to ensure that your script flow is correct and that all edge cases are covered during the execution Starting the debugging process also compiles the script in case it has just been recorded or if the source has been changed To start debugging open an existing script or record a new script and click on the Debug menu The menu is displayed as shown in Figure 9 30 Go Fa Go Until Cursor F6 Animate ause Stop Fil Set or Clear Breakpoint F9 Clear All Breakpoints Step Over Fit Step Into F8 Step Out F7 Figure 9 30 Debug menu Before starting to debug you will probably need to set breakpoints in the script to run a portion of script that is already working To use breakpoints move the cursor in the script up to where the breakpoint to be set and select Set or Clear Breakpoint to set or clear a breakpoint at that point in the script You can also simply press F9 to set or clear breakpoints on the current
106. strumenti bbe otic arC UMARO pinstrumeanticlconng C WAtapplnstrumentapoSevers t 20 config CONArapplinstrumentiiniiti jar C MMAlappinsium erMiblbootic jar CVMAa poi netrumenbicleonfig C UMAlappinstrumertappServersit 29tconfig 129 Apply Reset Help D MAOIIZOTPM DYNADONIE Sentet cache file ctmacache sn not found caching is disabled comm semet dynacache Cachewanager Detaits D f SRVE0 S9 Loading Web Module Default Application comibm sentet engine Serdetengine o SRVE Loading Wab Module Examples Applicaton com ibm santet engine Servistengine Clear Bb SRVEO1 711 Transport htio is Estening on port 9 081 comm cametengine htipt 1 HtipTransoor gt Figure 6 6 WebSphere 4 Admin Console 2 On the right panel select the tab labeled JVM Settings Under the System Properties table remove each of the following eight properties jlog propertyFileDir com ibm tivoli transperf logging baseDir com ibm tivolijiti probe directory com ibm tivoli jiti contfig com ibm tivoli jiti logging FileLogginglmpl logFileName com ibm tivoli jiti registry Registry serializedFileName com ibm tivoli jiti logging llogginglmpl com ibm tivoli jiti logging NativeFileLogginglmpl logFileName 3 Click the Advanced JMV Settings button which opens the Advanced JVM Settings window In the Command line arguments text box remove the entry Xrunijitipi lt MA gt app instrument lib jiti properties In the Boot classpath appen
107. the Key Database File New option once the ikeyman utility starts We select JKS from the Key Database Type since this is supported by the TMTP We name it prodms jks and set the location to install keyfiles to save the file as shown in Figure 4 4 on page 94 Chapter 4 TMTP WTP Version 5 2 installation and deployment 93 94 Key database type JKS v File Name prodms jks Browse Location install keyfiles OK Figure 4 4 Creation of custom JKS file At the next screen Figure 4 5 we provide the password for the JKS file We have to use this password during the installation of the TMTP product 4 Password Prompt xi Password Confirm Password Password Strength ok crar Cancer Figure 4 5 Set password for the JKS file We choose to create a new self signed certificate We select the New Self Signed Certificate from the Create menu see Figure 4 6 on page 95 End to End e business Transaction Management Made Easy E3 IBM Key Management install keyfiles prodms jks a Fl ol x Key Database File View Help BAF R New Certificate Request DB Type JKS database file File Name install keyfiles prodms jks lt lt Token Labe Key database content Personal Certificates v Receive Delete View Edit Import Recreate Request New Self Signed
108. the default refresh rate of five minutes or change it according to your needs gt Configure the Time Zone performing the following steps a Select a time zone from the Time Zone drop down list b Place a check mark in the box to enable automatic adjustment for Daylight Savings Time c Provide the following information regarding the environment of the Web Health Console e Type the following information about the Tivoli managed node also referred to as the TME that is monitoring server endpoints TME Host name The fully qualified host name or the IP address of the Tivoli managed node Additional Information The host that you specify for the Tivoli managed node might be the same computer that hosts the Tivoli management region server This sharing of the host computer might exist in smaller Tivoli environments for example when Tivoli is monitoring fewer than 10 endpoints When the Tivoli environment monitors hundreds of endpoints the host for the Tivoli managed node is likely to be different from the host for the Tivoli management region server Note Do not include the protocol in the host name For example type myserver ibm tivoli com not http myserver ibm tivoli com TME Username Name of a valid user account on the host computer TME Password Password of the user account on the host computer Chapter 5 Interfaces to other management tools 173 e Type the following information about the Integrated Solutions Conso
109. the edge application for this transaction and generate a correlator which is included in the HTTP request as it is passed on the server that hosts the called application The reverse proxy implementation provides a single entry point to several Web servers much like a normal proxy works as an Internet gateway for multiple workstations on a corporate network as depicted in Figure 8 17 on page 258 Without the reverse proxy the IP addresses of all the Web servers has to be known by the requestors With the reverse proxy the requestors only need to know the IP address of the reverse proxy Chapter 8 Measuring e business transaction response times 257 origin server requesters virtual server Servers B reverse proxy Figure 8 17 Proxies in an Internet environment This technology is primarily implemented to circumvent some of the shortcomings of the TCP IP addressing schema by removing the need for all servers and workstations to be addressable known to all other systems on the Internet which also may be regarded as an additional security feature When working with the Quality of Service monitoring component you should be familiar with the following terms Origin server The Web server that you want to monitor Proxy server A virtual server impleme
110. to other management tools 153 5 1 Managing and monitoring your Web infrastructure 154 5 1 1 Keeping Web and application servers online 154 5 1 2 ITM for Web Infrastructure installation 04 155 5 1 3 Creating managed application objects 2 158 5 1 4 WebSphere monitoring 00 0c eee eee 162 5 1 5 Eventhandling userai a eee 168 5 1 6 Surveillance Web Health Console 20000 0005 170 5 2 Configuration of TEC to work with TMTP 0200ee eee 171 5 2 1 Configuration of ITM Health Console to work with TMTP 173 5 2 2 Setting SNMP 00 00 ccc eee 175 5 2 3 Setting SMTP 00 E a E tee 176 Chapter 6 Keeping the transaction monitoring environment fit 177 6 1 Basic maintenance for the TMTP WTP environment 178 6 1 1 Checking MBeans 000 cece eee 182 6 2 Configuring the ARM Agent 00 0 c cece eee eee 184 6 3 J2EE monitoring maintenance 0 0 0 cee ee eee 188 6 4 TMTP TDW maintenance tips 0 00 eee 191 6 5 Uninstalling the TMTP Management Server 0 2005 193 6 5 1 The right way to uninstall on UNIX 0 0 0 00 000 e eee eee 193 6 5 2 The wrong way to uninstall on UNIX 0020 0 eee 195 6 5 3 Removing GenWin from a Management Agent 195 6 5 4 Removing the J2EE component manua
111. to their high visibility and importance to the bottom line business results their level of distribution and the special security issues that characterize the Internet 20 End to End e business Transaction Management Made Easy 1 3 2 Architecting e business application infrastructures In a typical e business environment the application infrastructure consists of three separate tiers and the communication between these is restricted as Figure 1 6 shows ee 7 Firewall aa Authentication Demilitarized Access control Zone Intrusion detection Firewall Application hosting serving Web and application servers Application Load balancing Tier Distributed resource servers MQ database and so on Gateways to back end or external resources MQ database etc Firewall Back end and legacy recources databases transactions etc Back end Infrastructural resource servers MQ database and so on Gateways to external resources Firewall Internal Internal Company intranet Customer Customer pany i Segment Segment Resource sharing Figure 1 6 A typical e business application infrastructure The tiers are typically Demilitarized Zone The tier accessible by all external users of the applications This tier functions as the gatekeeper to the entire system and functions such as access control and intrusion detection are enforced here The only other p
112. to use to playback the Rational Robot script see Figure 9 44 on page 372 You may use schedules you have previously created or create a new one Chapter 9 Rational Robot and GenWin 371 IBM Tivoli Monitoring for Transaction Performan rosoft Internet Explorer z ioj xj Fle Edt View Favortes Tools Hep address ice4 9082 tmtpUIjsp console WcFrameManager jsp es EA Tivoli Monitoring for Transaction Performance Configuratii i ios ran Create Playback Policy Work with Schedules Work with AA ete Create New Alt w Work with Work with Work with Schedule Table aren 8 Prose ate a sector zoo Name Stat Time Stop Time Run the policy Between the hows off Monday Tues petstore_sti_sch Start as soon as possible Run forever Every 5 Minutes irade_sti sch Start as soon as possible Run forever Every 5 Minutes Page 1 N lt Back Alt b Next Alt n gt Finish Alt Cancel Alt c Figure 9 44 Choosing a schedule Note The Rational Robot has a practical limit to the number of transactions that can be played back in a given period During our experiments we found each invocation of the Robot at the Management Agent took 30 seconds to initialize prior to playing the recording This meant that it was only possible to play back two transactions a minute There are several ways in which this shortcoming could be overc
113. transaction performance on page 209 is aimed at the audience that will use IBM Tivoli Monitoring for Transaction Performance functions on a daily basis Here we provide detailed information and best practices on how to configure monitoring policies and deploy monitors to gather transaction performance data We also provide extensive information on how to create meaningful reports from the data gathered by IBM Tivoli Monitoring for Transaction Performance This part includes gt Chapter 7 Real time reporting on page 211 gt Chapter 8 Measuring e business transaction response times on page 225 gt Chapter 9 Rational Robot and GenWin on page 325 v Chapter 10 Historical reporting on page 375 It is our hope that this redbook will help you enhance your e business management solutions to benefit your organization and better support future Web based initiatives The team that wrote this redbook This redbook was produced by a team of specialists from around the world working at the International Technical Support Organization Austin Center Morten Moeller is an IBM Certified IT Specialist working as a Project Leader at the International Technical Support Organization Austin Center He applies his extensive field experience as an IBM Certified IT Specialist to his work at the ITSO where he writes extensively on all areas of Systems Management Before joining the ITSO Morten worked in the Professional Services
114. until the next time the ARM engine is started Note The ARM agent tapmagent exe is started by the Management Agent that is to start and stop the ARM agent you will need to stop and start the Tivoli Management Agent On Windows based platforms this is achieved by stopping and starting the Tivoli TransPerf Service jmxservice exe On UNIX platforms the Management Agent is stopped and started using the stop_tmtpd sh and start_tmtpd sh scripts The contents of the file are organized in stanzas denoted by a character followed by the section name and ending with a character Within each section are a number of key value pairs Some of the more interesting keys are described below The entry ENGINE LOG LogLevel 1 defines the level of logging that the ARM engine will use The valid values for this key are shown in Table 6 1 on page 185 184 End to End e business Transaction Management Made Easy Table 6 1 ARM engine log levels as Minimum logging Error conditions and some performance logging Medium logging All of 1 and more High logging All of 2 and much more The logging from the Management Agent ARM engine is by default sent to one of the following files Windows C Program Files ibm tivoliicommon BWM logs tapmagent log UNIX usr ibm tivoliicommon BWM logs tapmagent log If you are experiencing problems with the ARM agent you can set this key to 3 and stop and start the Management Agent to
115. used in our case are shown in Figure 10 16 on page 398 Chapter 10 Historical reporting 397 398 i Properties TRANSACTION x ByvM_TMTP_DATA_SOURCE TRANSACTION Source Table Columns Warehouse Primary Key Warehouse Foreign Keys Table schema DB2 z Table name TRANSACTION Table space S a Indextablespace H Description BT Data Warehouse Center options Business name Cancel Help Figure 10 16 TableSchema and TableName for TMTP Warehouse sources These steps should be performed for all the tables referenced by the two IBM Tivoli Monitoring for Transaction Performance Warehouse sources BWM_TMTP_DATA_SOURCE Upon completion the list of tables displayed in the right pane of the Data Warehouse Center window should look similar to the one shown in Figure 10 17 where all the schema information is filled out and no table names include the creator information t Properties TRANSACTION ee xi BYiM_TMTP_DATA_SOURCE TRANSACTION Source Table Columns Warehouse Primary Key Warehouse Foreign Keys Table schema pezns Table name TRANSACTION Table space S Indextablespace Description nn O Data Warehouse Center options Business name a j Figure 10 17 Warehouse source table names changed End to End e business Transaction Management Made Easy Data Warehouse Center ol x Warehouse Selected Edit View Tools Help PA 3 agaaga aa sa AMY_TWH_CDW_So
116. using the Tivoli Data Warehouse is covered in Chapter 10 Historical reporting on page 375 Additionally several of the chapters include scenarios that show how to use the reporting capabilities of the TMTP product in order to identify e business transaction problems This is important as the dynamic nature and 50 End to End e business Transaction Management Made Easy drill down capabilities of reports such as the Topology overview are very powerful problem solving and troubleshooting tools 2 4 Integration points Existing IBM Tivoli Customers are aware of the value that can be obtained by integrating IBM Tivoli products into a complete Performance and Availability monitoring Infrastructure with the goals of autonomic and on demand computing TMTP supports these goals by including the following integration points gt IBM Tivoli Monitoring ITM ITM provides monitoring for system level resources to detect bottlenecks and potential problems and automatically recover from critical situations This saves system administrators from manually scanning through extensive performance data before problems can be resolved ITM incorporates industry best practices in order to provide immediate value to the enterprise TMTP provides integration with ITM through the ability to launch the ITM Web Health Console in the context of a poorly performing transaction component Figure 2 12 This is a powerful feature as it allows you to drill down to
117. value extreme 413 variable 106 Verification Point 345 347 adding 347 violation availability 219 222 percent 294 severity 216 virtual host 265 virtual server 261 visited pages 223 VU script 345 VuGen 59 W warehouse cetral database 380 source 394 source database 380 target 394 warehouse modules 378 wcrtprf 166 492 End to End e business Transaction Management Made Easy wertprfmgr 166 wdmdistrib 156 167 wdmeditprf 166 Web application tier 436 Detailer 223 transaction 33 Web Health Console 51 60 170 217 306 Web page activity 224 Web page requests 224 Web transaction 4 33 availability 35 Weblogic 201 application server 307 WebSphere server start and stop 116 stop and start 150 WriteNewEdge 190 wscp 156 wsub 166 wwebshpere 161 Index 493 494 End to End e business Transaction Management Made Easy Redbooks End to End e business Transaction Management Made Easy 1 0 spine 0 875 lt gt 1 498 460 lt gt 788 pages End to End e business Transaction 1 C Management Made Easy Redbooks Seamless transaction decomposition and correlation Automatic problem identification and baselining Policy based transaction discovery This IBM Redbook will help you install tailor and configure the new IBM Tivoli Monitoring for Transaction Performance Version 5 2 which will assist you in determining the business performance of your e business transactions in term
118. we have to ensure the availability of the WebSphere Application Server and the IBM HTTP Server IBM WebSphere Application Server These are the prerequisites you need on the WebSphere Application Server system gt IBM WebSphere Application Server Version 4 0 2 or higher gt An operational Tivoli Endpoint gt WebSphere Administration Server must be installed on the same system as the Tivoli endpoint gt Java Runtime Environment Version 1 3 0 or higher gt Monitoring at the IBM WebSphere Application Server must be enabled Chapter 5 Interfaces to other management tools 155 Java Runtime Environment IBM Tivoli Monitoring for Web Infrastructure requires that the endpoints have Java Runtime Environment JRE Version 1 3 0 or higher installed If a Java Runtime Environment currently is not installed on the endpoint one can be installed from the IBM Tivoli Monitoring product CD You can install JRE either manually or by running the wdmdistrib J command or by using the Tivoli Software Installation Service SIS If you have just installed Java Runtime Environment or if you have an existing Java Runtime Environment you need to link it to the IBM Tivoli Monitoring using the DMLinkJre task from the IBM Tivoli Monitoring Tasks TaskLibrary Note For IBM WebSphere Application Server you must use the IBM WebSphere Application Servers JRE Monitoring at the IBM WebSphere Application Server The following details apply to any systems
119. when to fill up the fuel tank or adjust the tire pressure The vehicle owner also decides when to take the vehicle in for a tune up when to add chrome bumpers and alloy wheels to make the vehicle look better and when to sell it The user of an e business site has none of those choices As owners of the e business solution we decide when to rework the user interface to make it look better when to add resources to increase performance and ultimately when to retire and replace the solution This gives us a few advantages over the car manufacturer as we can modify the product seamlessly by adding or removing components as needed in order to align the performance with the requirements and adjust the functionality of the product as competition toughens or we engage in new alliances No matter whether the e business solution is the front end of a legacy system or a new application developed using modern state of the art development tools it may be characterized by three specific layers of services that work together to provide the unique functionality necessary to allow the applications to be used in an Internet environment as shown in Figure 1 7 on page 24 Chapter 1 Transaction management imperatives 23 Solution Server f Presentation Networking Services Transformation Internet Protocol Client Operating Services Server Operating Services Environment
120. with the Management Server Management Agents communicate with the Management Server using Web services and the secure socket layer SSL Every 15 minutes all Management Agents poll the Management Server for any new policy information known as the polling interval gt Store and Forward Store and Forward can be implemented on one or more Management Agents in your environment typically only one to handle firewall situations Store and Forward performs the following firewall related tasks in your environment Enables point to point connections between Management Agents and the Management Server Enables Management Agents to interact with Store and Forward as if Store and Forward were a Management Server Routes requests and responses to the correct target Supports SSL communications Supports one way communications through the firewall All applications such as STI QoS and J2EE are registered as MBeans as are all services used by the Management Agent and Server for example Scheduler Monitoring engine Bulk Data Transfer and the Policy Manager service The Application Response Measurement Engine When you install and configure a Management Agent in your environment the Application Response Measurement ARM Engine is automatically installed as part of the Management Agent The engine and ARM API comply with the ARM 2 0 specification The ARM specification was developed in order to meet the challenge of tracki
121. 0 eee eee 332 9 11 Rational Robot setup complete 0 332 9 12 Rational Robot license key administrator wizard 333 Figures xiii xiv 10 2 10 3 10 4 10 5 10 6 10 7 10 8 10 9 Import Rational Robot license 0 ee 334 Import Rational Robot license cont 0 00 eee 334 Rational Robot license imported successfully 334 Rational Robot license key now usable 200 05 335 Configuring the Rational Robot Java Enabler 336 Select appropriate JVM 0 0000 c eee 337 Select extensionS 00 00 ee 338 Rational Robot Project 0 0 e cee ee ee 340 Configuring project password 000 eee eee eee 341 Finalize project e E e a A eee 342 Configuring Rational Project 00 000 e eee eee 343 Specifying project datastore ansaa eee 344 Record GUI Dialog Box 1 0 0 cee 346 GUlInsert sass ates ada hee Re ote We ate aes UR Seen eid a See 346 Verification Point Name Dialog 0000 c eee eee 348 Object Finder Dialog 0000 c cece 349 Object Properties Verification Point panel 350 Debug Menu sy oc esas es a e Deed ae Miao et edo arate ees 354 GUI Playback Options s srin usri rset saap aai E oE UE E eee 355 Entering the password for use in Rational Scripts 358 Terminal Server Add On Component 0000e eae 361 Setup for Te
122. 082 tmtpUL jsp console WcFrameManager jsp z C60 Links a Tivoli Monitoring for Transaction Performance User Name administrator b Configuration vReports View Big Board View General Reg View Component vSystem Administ All Times are in Seconds Aer oooga 2d tivla b01 ibmtiv9 STI o View Log Files L kau view Managemey Overall Transaction 90S b Downloads 6 342 o mm J2EE WebSphere 5 0 ibmtiv9 ibmtiv9 server1 URL 3 068 25 E Opening http tivdce4 9082 tmtpUL images topology filter_32 gif I l fez Local intranet a Figure 8 50 STI topology relationship with QoS and J2EE The total real end user response time is 0 623 seconds and if we decompose the topology further we see six specific back end response times one for each of the different Trade subtransactions processes From the Inspector View shown in Figure 8 51 on page 302 we can see the total end user time all subtransaction steps Back End Service Time and J2EE application time from serviets EJBs and JSPs Chapter 8 Measuring e business transaction response times 301 QoS Back End Service Time STI transaction lolx Start Time Status St ivoli Monitoring for Transaction Performance Maxim Name atus Fail 6 828 jtrade_2_stockcheck_tivlabO1 2003 10 0 0 985 Step_1_http ipmtiv9 itsc austin ibm com 82 trade 2003 10 0 Harmless
123. 10A software End to End e business Transaction Management Made Easy Seamless transaction decomposition and correlation Automatic problem identification and baselining Policy based transaction discovery Morten Moeller Sanver Ceylan Mahfujur Bhuiyan Valerio Graziani Scott Henley Zoltan Veress ibm com redbooks Red b ooks International Technical Support Organization End to End e business Transaction Management Made Easy December 2003 SG24 6080 00 Note Before using this information and the product it supports read the information in Notices on page xix First Edition December 2003 This edition applies to Version 5 Release 2 of IBM Tivoli Monitoring for Transaction Performance product number 5724 C02 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 product documentation or follow on versions of this redbook for more current information Copyright International Business Machines Corporation 2003 All rights reserved Note to U S Government Users Restricted Rights Use duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp Contents FIQUIES siagan ee Pi hehe ee ee ee Ae een Pelee be ix FADES 3 2 0 0 epi techies waite Ae ae edd Een waite day xvii NOUCES oe csc ke ee ha one de Pend epee Meee Dre ee nn dpe xix Trademarks 20008 ee tee ede pele ke ac
124. 1KB C ce wins SKB 5 E wins2 7KB 5 EHO disks 1KB I ski 80KB A disk2 Maes Plier 1KB C C com 2KB L O config 1KB T a dhcp diicache i drivers a DTCLog i O export i H E GroupPolicy Oia poi inetsrv 4 a gt f gt Type Application Size 79 6 KB 79 6 KB My Computer A Figure 9 34 Setup for Terminal Server client 3 Once you have installed the client you may start a client session from the appropriate menu option You will be presented with the dialog shown in Figure 9 35 on page 363 From this dialog you should select the local machine as the server you wish to connect to End to End e business Transaction Management Made Easy fa Terminal Services Client S x Server dahouse z Screen area Available servers M Expand by default WORKGROUP J Enable data compression I Cache bitmaps to disk Cancel Help About Figure 9 35 Terminal Client connection dialog Note It is useful to set the resolution to one lower than that used by the workstation you are connecting from This allows the full Terminal Client session to be seen from the workstation screen 4 Once you have connected you will be presented with a standard Windows 2000 logon screen for the local machine within your client session Log on as normal 5 Now you can run your Rational Robot scripts using whichever method you would normally do this with the exception of via GenWin You may now lock the host scr
125. 2 2 Registering your Rational Robot Transaction Once the Generic Windows component has been deployed you can register your Rational Robot transaction scripts with TMTP as follows 1 Select the Work with Transaction Recordings option from the Configuration menu of the Navigation pane The window shown in Figure 9 39 should appear 4 IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer File Edt View Favorites Tools Help Address s http tivdce 9082 tmtplyjsp console WcFrameManager jsp z eo El Tivoli Monitoring for Transaction Performance User Name Administrator i Configuration Work with Discovery Policies Work with Transaction Recordings Work with Listening Policies Work with Playback Policies Create New At w M Work with Schedules Work with Agent Groups Work with Transaction Recordings a Work with Realms b Reports Type b System Administration b Downloads E AN petstore_2_order Aes SRL CANE Peeping Mode te ANA ST Mintle Oo trade_2_stock check sT Page 1 _ a af Figure 9 39 Work with Transaction Recordings 2 Select Create Generic Windows Transaction Recording from the Create New drop down box and then push the Create New button 3 In the Create Generic Windows Transaction window Figure 9 40 on page 369 which you are now presented with you need to provide the Rational Robot Script files This can be done using the Browse button Tip I
126. 2 Creating listening policies and selecting application transactions 290 8 43 Configure J2EE listener 0 00 291 8 44 Configure J2EE parameter and threshold for performance 292 8 45 Assign a name for the J2EE listener 200055 295 8 46 Event Graph Topology view for Trade application 297 8 47 Trade transaction and subtransaction response time by STI 298 8 48 Back End service Time for Trade subtransaction3 299 8 49 Time used by servlet to perform Trade back end process 300 8 50 STI topology relationship with QoS and J2EE 301 8 51 QoS Inspector View from topology correlation with STI and J2EE 302 8 52 Response time view of QoS Back end service 1 time 303 8 53 Response time view of Trade application relative to threshold 304 8 54 Trade EJB response time view get market summary 305 8 55 Topology view of J2EE and trade JDBC components 306 8 56 Topology view of J2EE details Trade EJB get market summary 307 8 57 Pet Store application welcome page 0 e eee eee eee 309 8 58 Weblogic 7 0 1 Admin Console 00000 cece eee 310 8 59 Weblogic Management Agent configuration 04 311 8 60 Creating listening policy for Pet Store J2EE Application 313 8 61 Choose Pet Store transaction for Listening policy 314 8 62 Automatic threshold
127. 4 4 55 4 56 4 57 4 58 4 59 4 60 4 61 4 62 4 63 4 64 4 65 5 1 5 2 5 4 5 5 5 7 6 1 6 2 6 3 6 5 6 6 6 7 6 8 6 9 6 10 7 2 7 3 7 4 7 5 7 7 Installation location definition 0 0 0 0 00 0 e eee eee 132 Management Agent connection window 0 e ae 133 Local user account specification 0 00 0 134 Installation summary window 0 000 e eee eee eee 135 The finished installation 0 0 0 cee eee 136 Management Server Welcome screen 20 00 e005 138 Management Server License Agreement panel 139 Installation location WindoW 0 eee 140 SSL enablement window 0000 c cece 141 WebSphere Configuration window 20000 eee eee eee 142 Database options Window 00 cee eee es 143 DB2 administrative user account specification 144 User specification for fenced operations in DB2 145 User specification for the DB2 instance 0000 146 Management Server installation progress window 147 DB2 silent installation window 0 0000 c ee eee ee 148 WebSphere Application Server silent installation 149 Configuration of the Management Server 00 0005 150 The finished Management Server installation 151 Create WSAdministrationServer 00 0c eee eee 159 Create WSApplicationServer 000
128. 5 8 6 8 7 8 8 8 9 8 10 8 11 8 12 8 13 8 14 8 15 8 16 8 17 8 18 8 19 8 20 8 21 8 22 8 23 8 31 8 34 8 35 8 36 8 37 8 38 8 39 8 40 8 41 Availability graph 6 eee 222 Page Analyzer Viewer 0 0 0 cece eee 223 Trade3 architecture 0 0 cee eee 236 WAS 5 0 Admin console Install of Trade3 application 238 Deployment of STI components 0 0000 cece ee ees 242 STI Recorder setup welcome dialog 0000 cece eaee 243 STI Software License Agreement dialog 00 243 Installation of STI Recorder with SSL disable 244 installation of STI Recorder with SSL enabled 244 STI Recorder is recording the Trade application 246 Creating STI transaction for trade 1 0 0 cee eee 247 Application steps run by trade_2_stock check playback policy 248 Creating a new playback schedule 000 e eee eee 249 Specify new playback schedule properties 000 250 Create new Playback Policy 000 cece eee eee eee 251 Configure STI Playback 0 00 c eects 252 Assign name to STI Playback Policy 000000e0 eee 255 Specifying realm settingS 0 00 cece eee eee 256 Proxies in an Internet environment 0000 e eee eee 258 Work with agents QoS auauua aa aaea 259 Deploy QoS components 0 00 c eects 260 Work with Agents QoS installed
129. 7 Schedule user pret ei Ari Ee a a aE a ATK oA E EA 458 Select schedule advanced properties 20 00000ee 459 Enable scheduled task 0 00 cee eee ee 460 Viewing schedule frequency 000 e eee ee eee 461 Advanced scheduling options 0 0 0 eee ee eee 462 Entering the password for use in Rational Scripts 466 Terminal Server Add On Component 000000 eee 469 Setup for Terminal Server client 0 0000 eee eee 470 Terminal Client Connection Dialog 000000 eee eee 471 End to End e business Transaction Management Made Easy Tables 4 1 File system creation 0 0 0 0 cece ee 89 4 2 JKS file creation differences 0 0 0 eee 98 4 3 Internet Zone SnF different parameters 2 0005 129 4 4 Changed option of the Management Agent installation zone 136 5 1 Minimum monitoring levels WebSphere Application Server 157 5 2 Resource Model indicator defaults 02 000 e eee eae 164 6 1 ARM engine log levels 0 00 ee 185 7 1 Big Board Icons 1 0 0 a E eee 214 8 1 Choosing monitoring components 0600e eee ee eee 234 8 2 J2EE components configuration properties 00 281 8 3 Pet Store J2EE configuration parameters 20000 311 10 1 Measurement codes 0 eee 387 10 2 Source database names used by the TMTPETLs 393 10 3 Warehou
130. 9445 ee co Number IBY iy lf EF InstallShield lt Back Next Cancel Figure 8 7 installation of STI Recorder with SSL enabled 9 Whether or not SSL has been enabled select the port to be used to communicate with the Management Server If in doubt contact your local TMTP system administrator Click Next and Next and then Finish to complete the installation of the STI Recorder 10 Once installed the STI Recorder can be started from the Start Menu Start Programs Tivoli Synthetic Transaction Investigator Recorder 244 End to End e business Transaction Management Made Easy and the setup_sti_recorder exe file downloaded in step 4 on page 242 may be deleted Tip If you want to connect your STI Recorder to a different TMTP Version 5 2 Management Server edit the endpoint file in the c install dir STI Recorder lib properties directory and change value of the dbmgmitsrvurl property to the host name of the new Management Server 8 4 3 Transaction recording and registration There are several steps involved in recording and playing back a STI transaction 1 Record the desired e business transaction using the STI Recorder and save it to a Management Server From your Windows Desktop select Start gt Programs Tivoli gt Synthetic Transaction Investigator Recorder to start the STI Recorder locally 3 Type the application address in Location and set the Completion Time to a value that wil
131. AS sTo0Su2EF reliability E E gunsnroses idlab austin ibm cam ST1 2008 09 19 12 56 42 1 702 equal Failure 0 0 001 0 A SN DoS JEE reliability E E BIOHAZARD sT 2006 09 12 18 44 52 2 234 equal Failure 0 0 001 0 ity E cinderella tivlab austin ibrn cam STI 2008 09 12 18 27 35 1 61 equal Failure O 0 0017 EN QoS J2EE reliability q AS plantabywebsphere playback E E metal man E 2003 09 16 17 21 560 equal Failure 0 40 001 70 SN DSE reliability E m metalman ST 2008 09 16 17 26 31 0 equal Failure HE feanor anainet Hit Count Servlet connects to WAS DE2PAC E 4 feanor J2EE 2008 040 19 68 40 0 011 0 072 0 004 0 08 E BioBot onimledis E imladris Qos 2008 09 10 16 64 34 11 318 6 219 1 537 16 1 E Wwelcome jsp onimladris imladris aos 2008 09 10 16 64 26 1 865 0 418 0 418 0 44 E sessiont xm fal BIOHAZARD ST 2003 0910 01 08 3910 999 10 43 0 407 0 453 session xm m kisa dirlab austin ibrn cam sm 2008 05 10 00 52 29 0 953 0 8 0 358 0 51 sessiont xm fal cinderella tilab austin ibm cam ST 2003 040 01 06 54 1 187 0 415 0 39 0 469 Poge 1 2 3 All GH Refresh Rate Minutes E fi Iteri ng Filter Starts With a Event Transaction Apply Atta ee ee ees Harmless B Unknown amp Mi Fatal Figure 7 1 The Big Board Event data updates the values for duration time and transactions as thresholds are breached Those values are sh
132. Advisor product Chapter 10 Historical reporting on page 375 describes historical reporting for TMTP with the Tivoli Data Warehouse in some depth Tivoli Business Systems Manager TBSM IBM Tivoli Business Systems Manager simplifies management of mission critical e business systems by providing the ability to manage real time problems in the context of an enterprise s business priorities Business systems typically span Web client server and or host environments are comprised of many interconnected application components and rely on diverse middleware databases and supporting platforms Tivoli Business Systems Manager provides customers a single point of management and control for real time operations for end to end business systems management Tivoli Business Systems Manager enables you to graphically monitor and control interconnected business components and operating system resources from one single console and give a business context to management decisions It helps users manage business systems by understanding and managing the dependencies between business systems components and their underlying infrastructure TMTP can be integrated with TBSM using either the Tivoli Enterprise Console or via SNMP Tivoli Service Level Adviser TSLA TSLA automatically analyzes service level agreements and evaluates compliance while using predictive analysis to help avoid service level violations It provides graphical business level reports vi
133. Alt n gt Finish At Cancel Alt c sla Work with Playback Policies Choose Create Edit etc Figure 8 39 Assign Agent Groups to J2EE discovery policy 6 Assign a name to the new J2EE discovery policy and determine when to deploy the policy In the example shown in Figure 8 40 on page 287 the name assigned is trade_j2ee_dis and it has been decided to deploy the policy at the next regular interval Click Finish to complete the J2EE discovery policy creation 286 End to End e business Transaction Management Made Easy Z IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer 3 E jol xi File Edit View Favorites Tools Help e Address i http tivdce4 9082 tmtpUI jsp console WcFrameManager jsp z co eBak gt gt A search Gjravorites meda lt 4 D S Si a Tivoli Monitoring for Transaction Performance User Name administrator Create Discovery Policy Assign Name J2EE Listener Name f trade_j2ee_dis E Description Dicovery policy Sent to Agents at next interval Send to Agents now lt Back Alt b Next Alt n gt SEES Cancel Alt c m ES Work with Discovery Policies Choose Create Edit etc oa Local intranet y Figure 8 40 Assign name J2EE In order to trigger the discovery policy and to have transactions discovered you need to direct your browser to the application and start a few transactions
134. Applications Bl Resources Classpath FT ects te stares path n whch the aA lava vitual machine looks for classes curt 1 Environment T System Administration E Troubleshooting Boot Classpath Verbose class loading Verbose garbage colection Verbose JN Initial Heap Sze Maximum Heap Size Run HProt poter mets setting T Protprtie spat Prot Arguments e Tlspecities conmend ine protter arguments to pass tothe Jaya virtual machine thet starts the application You can epectyargunerts when Her rot profiler support is enabled Hlspecites whether to use the JVM debug output is rotto en Jode support Debug Mode T Debug arguments Djava compier NONE Xdebug Knc Generic JVM arguments Pittotciesspethie SIMA NSTRUMG Daa mand Ine arguments for the JVM Executable JAR fie name ll Species a ha path re executattejer fie E Websphere Status i lt Previous Next gt October 9 2003 1 14 13 PM CDT C3 E IEE Local intranet 7A E bene Figure 6 7 Removing the JVM Generic Arguments 7 Remove all of the following entries from this field Xbootclasspath a MA_INSTRUMENT Wlib jiti jar MA_INSTRUMENT lib bootic jar MA_INSTRUMENT ic config MA_INSTRUMENT_APPSERVER_CONFIG Xrunijitipi MA_INSTRUMENT ib jiti properties Chapter 6 Keeping the transaction monitoring environment fit 199 Dcom ibm tivoli jiti config
135. Apply appropriate values for filtering your data You can apply filters that will help you collect transaction data from requests that originate from specific systems IP addresses or groups thereof The filtering may be defined as a regular expression In addition you should specify how much data you want to capture per minute and whether or not instance data should be stored along with the aggregated values In case a threshold which you will specify in the following dialog is violated TMTP Version 5 2 will automatically collect instance data for a number of invocations of the same transaction You can customize this number to provide the level of detail needed in your particular circumstances Click Next to go on to defining thresholds for the listening policy 6 The Configure QoS Settings dialog shown in Figure 8 30 on page 275 is used to define global values for threshold and event processing in QoS 274 End to End e business Transaction Management Made Easy 4 File Edit View Favorites Tools Help Address http ftivdces itsc austin ibm com 9082 tmtpUL isp console WcFrameManager isp 7 Go gt r Tivoli Monitoring for Transaction Perf User Name administrator Configure QoS Settings Configuration Work with Discovery Policies e stene Performance gt Create Alt e Work with Listening Policies Work with Playback Policies Work with Schedules e n Configure QoS Thresholds Work wi
136. B Tables and Views Security Data source name TMTP_DB_SRC ad System name localhost User ID db2inst1 Password pe Verify password I Customize ODBC connect string Cancel Help Figure 10 14 BWB_TMTP_DATA_SOURCE user ID information Set the user ID and password of Data Source for every BWM Warehouse Source and Target ETL Modifying the schema information In order for the ETLs to successfully access the data within the sources defined an extra step is needed to make sure that the table names referenced by the ETLs match those found in the source databases For all the tables used in the IBM Tivoli Monitoring for Transaction Performance Warehouse source BWM_TMTP_DATA_SOURCE it should be verified that the schema information is filled out and that the table names do not contain creator information This is unfortunately the default situation immediately after installation as shown in Figure 10 15 on page 397 where you should note that the table names all include the creator information the part before the period and the schema field has been left blank To provide TEDW with the correct schema and table information follow the following procedure for every table in each of the IBM Tivoli Monitoring for Transaction Performance ETL sources 1 On the TEDW Control Center server using Data Warehouse Center window expand Warehouse Sources 2 Select the appropriate source for example BWM_TMTP_DATA_SOURCE and exp
137. C Every 1 days Start date 3 11 2003 Figure B 13 Schedule start time The task will need to run with the authority of some user ID on the machine so enter the relevant user ID and password Figure B 14 on page 458 Appendix B Using Rational Robot in the Tivoli Management Agent environment 457 Scheduled Task Wizard o xi Enter the name and password of a user The task will run as if t were started by that user Enter the user name FSTENAR Z Administrator Enter the password Preece Confirm password ea Figure B 14 Schedule user Check the box in the window shown in Figure B 15 on page 459 in order to get to the advanced scheduling options 458 End to End e business Transaction Management Made Easy Scheduled Task Wizard You have successfully scheduled the following task x Rational Robot VYindow s will perform this task At 3 00 AM every day starting 3411 2003 pisencensenscnscsscessessssncassnsssnsssenscenssssensenssssenessnsnsensonssescenseaseasenscnensssscessnsceseeses Vv Open advanced properties for this task when click Finish i Resesssesssssnnsessensenssnsssansesenssnsnsssssnssnessnssssanssnnsnssnssssssssensssnssssnssenseesnesnesnsssesenses Click Finish to add this task to your Windows schedule Cancel Figure B 15 Select schedule advanced properties Edit the contents of the Run option to use the Robot command line interface For example
138. D 0 0 10 05 10 05 10 06 10 06 10 06 16 00 22 00 04 00 10 00 16 00 Time Figure 2 10 Transactions with Subtransactions Page Analyzer Viewer The Page Analyzer Viewer Report window Figure 2 11 allows you to view the performance of Web screens that are visited during a synthetic transaction The Page Analyzer Viewer Report window gives details about the timing size identity and source of each item that makes up a page You can use this information to evaluate Web page design regarding efficiency organization and delivery Time Time Stamp 4 httpvAwtsc61 itso ibm com 61 00 TradenVeb Logon html hitp wtsc61 itso ib 0 164935 1494 Oct 10 2003 8 55 19 PM Oct 10 2003 8 55 19 PM http wtsc61 itso ib 0 179730 4950 Oct 10 2003 8 55 22 pm 0 154935 Seconds 1494 Bytes 1 Items httpviwtsc61 itso ib 0 094029 912 Oct 10 2003 8 55 26 PM m http wtsc61 itso ib 0 161531 4950 Oct 10 2003 8 55 31 PM httpvwtse61 jtso ib 0 093416 905 Oct 10 2003 8 55 34 PM httpvwtse61 jtso ib 0 214667 4950 Oct 10 2003 8 55 37 PM http wtsc61 itso ib 0 104295 1494 Oct 10 2003 9 55 41 PM gt Chart Details Legend Us httpwtsc61 jitso ibm com 61 00 TradenWeb Logon html Figure 2 11 Page Analyzer Viewer A more detailed introduction to the reporting capabilities of TMTP is included in Chapter 7 Real time reporting on page 211 Historical reporting
139. DW installation Installation running 020 00 0 391 10 12 Installation summary window 000 c cee ee 391 10 13 TMTP ETL Source and Target 0000 e eee eee eee 395 10 14 BWB_TMTP_DATA_SOURCE user ID information 396 10 15 Warehouse source table properties 00 c eee eee 397 10 16 TableSchema and TableName for TMTP Warehouse sources 398 10 17 Warehouse source table names changed 5 398 10 18 Warehouse source table names immediately after installation 399 10 19 Scheduling source ETL process 00 0c cece eee 402 10 20 Scheduling soure ETL process periodically 403 10 21 Source ETL scheduled processes to Production status 405 10 22 Pet Store STI transaction response time report for eight days 406 10 23 Response time by Application 0 0 0 cee eee 409 10 24 Response time by hostname 0 eee eee 410 10 25 Execution Load by Application daily 00 0000 411 10 26 Performance Execution load by User 000 00s 412 10 27 Performance Transaction availability Daily 413 10 28 Add metrics Window 0 cet 415 10 29 Add Filter windows 0 eee 416 10 30 Weekly performance load execution by user for trade application 417 10 31 Create links for report generation in Crystal Reports 419 10 32 Choose fields for report g
140. EE could be instrumented incorrectly Verify in the UI that the J2EE component says RUNNING Possible solution If there is no arm_start but the UI says RUNNING you may have encountered a defect and should open a PMR with IBM Tivoli Support If arm_start exists then search the file for WriteNewEdge If this exists then ARM has successfully matched a J2EE edge with an existing policy Possible problem If arm_start exists but WriteNewEdge does not exist then there could be a problem with your listening policy or your have not run an instrumented application At this point also check to see if ARM_IGNORE_ID exists If it does then the edge URI for the listening policy is not matching the edge that J2EE is sending Possible solution Verify that you have run an application that would match your policy Verify that the listening policy is on the Management Agent and that the URI pattern matches what the URI you are clicking on for the application on the Management Agent s appserver If this is still a problem then you may have to open a PMR with IBM Tivoli Support 190 End to End e business Transaction Management Made Easy 6 4 TMTP TDW maintenance tips This section provides information about maintaining and troubleshooting the Tivoli Data Warehouse Backing up and restoring The dbrest bat script in the misc tools directory is an example script that shows you how to restore the three databases on an NT or 2000 Microsoft W
141. End to End e business Transaction Management Made Easy Additional material This redbook refers to additional material that can be downloaded from the Internet as described below Locating the Web material The Web material associated with this redbook is available in softcopy on the Internet from the IBM Redbooks Web server Point your Web browser to ftp www redbooks ibm com redbooks SG246080 Alternatively you can go to the IBM Redbooks Web site at ibm com redbooks Select the Additional materials and open the directory that corresponds with the redbook form number SG246080 Using the Web material The additional Web material that accompanies this redbook includes the following files File name Description SG246080 zip Zipped SQL statements and report samples Copyright IBM Corp 2003 All rights reserved 473 System requirements for downloading the Web material The following system configuration is recommended Hard disk space 1 MB Operating System Windows UNIX Processor 700 or higher Memory 256 MB or more How to use the Web material 474 Create a subdirectory folder on your workstation and unzip the contents of the Web material zip file into this folder The files in the zip archive are trade_petstore_method avg rpt A sample Crystal Report file showing how to report on aggregated average data collected from TWH_CDW trade_petstore_method max rpt A sample Crystal Report file showing ho
142. Every Iteration Value o Iteration Unit Hours x Run continuously Run between Stop Time Run forever Stop later at OK Alt 0 Apply Alt a Cancel it c gt Figure 8 12 Specify new playback schedule properties 2 Provide appropriate values for all the properties of the new schedule Select a name according to the standards you have defined which easily conveys the purpose and frequency of the new playback schedule For example telia_trade_sti_15mins Set Start Time to Start as soon as possible or Start later at depending on your preference If you select Start later at the dialog opens a set of input fields for you to fill in the desired start date Set Iteration to Run Once or Run Every In case you choose the latter you will be prompted for a Iteration Value and Unit 250 End to End e business Transaction Management Made Easy Incase Run Every was chosen in the previous step set the Stop Time to Run forever or Stop later at and specify a Stop Time in case of the latter Press OK to save the new schedule 8 4 5 Playback policy creation After having defined a schedule or determined to reuse one that had already been defined the next step is to create a Playback policy for the STI recording Follow the steps below to complete this task For a thorough walk through and descriptions of all the parameters and properties specified during the STI playback definition p
143. JKS file which is proddmz jks and its password Chapter 4 TMTP WTP Version 5 2 installation and deployment 123 124 Install Store and Forward Agent 210 l x If communication flows directly to the management server you must pe information for the management server If communication flows across a firewall to the management server ou must type information for a management agent that is running the Store and Forward Service Specify a User account that exists on the WebSphere Application Server of the management server This user account must have the agent role nF Post Name fully canberra itsc austin ibm com qualified User Name root User Password haii Enable SSL M Yes Use default port number C No Port Number 443 SSL Key Store File clinstalliproddmz jks SSL Key Store Password z Back Next gt Cancel Figure 4 39 Communication specification 8 In Figure 4 40 on page 125 we have to specify a local administrative user account what will be used by the Store and Forward agent service We specify the local Administrator account which already exists End to End e business Transaction Management Made Easy w Install Store and Forward Agent Specify a User Account Specify a user account for running the management agent service This user account must be a member of the Administrators group on Windows You have two options Specify an existing administrative user acc
144. M API functions arm_update is not declared since TMTP doesn t use it Declare Function arm_init Lib libarm32 ByVal appl_name As String ByVal appl_userid As String ByVal flags As Long ByVal data As String ByVal data_size As Long As Long Declare Function arm_getid Lib libarm32 ByVal appl_id As Long ByVal tran_name As String ByVal tran_detail As String ByVal flags As Long ByVal data As String ByVal data_size As Long As Long Declare Function arm_start Lib libarm32 ByVal tran_id As Long ByVal flags As Long ByVal data As String ByVal data_size As Long As Long Declare Function arm_stop Lib libarm32 ByVal start_handle As Long ByVal tran_status As Long ByVal flags As Long ByVal data As String ByVal data_size As Long As Long Declare Function arm_end Lib libarm32 ByVal appl_id As Long ByVal flags As Long ByVal data As String ByVal data_size As Long As Long 2 Then declare variables to hold the returns from the ARM API calls Again note the comment line preceded by a single quote mark Declare variables to hold returns from ARM API calls Dim appl_handle As Long Dim getid_handle As Long Dim start_handle As Long Dim stop_rc As Long Dim end_rc As Long Next we added the ARM API calls to the script Note that even though they are C functions they are not terminated with a semicolon Make ARM API setup calls and display the return from each one app _handle arm_init Rational_tests 0 0 0 Remove line belo
145. MsgBox Password successfully stored 64 Password Encryption End Sub Running this script will generate the pop up window shown in Figure 9 32 which asks for the password and name of a file to store the encrypted version of that password within Password Encryption A x Password mypassword Cancel Filename c encryptedpassword tat Figure 9 32 Entering the password for use in Rational Scripts Once this script has run the file you specified above will contain an encrypted version of your password The password may be retrieved within your Rational Script as shown in Example 9 10 Example 9 10 Retrieving the password Sub Main Dim Result As Integer Dim bf As Object Dim strPasswd As String Dim fchar Dim x As Integer Create the Encryption Engine and store a key End to End e business Transaction Management Made Easy Set bf CreateObject EncryptionAlgorithms BlowFish bf key ibm Open file and read encrypted password Open C encryptedpassword txt For Input Access Read As 1 Redim fchar Lof 1 For x 1 to Lof 1 2 fchar x Input 1 1 strPasswd strPasswd amp fchar x Next x Decrypt strPasswd bf DecryptString strPasswd rational SQAConsoleWrite Decrypt amp strPasswd End Sub The resulting unencrypted password has been retrieved from the encrypted file in our case we used the encryptedpassword txt file and placed into the variable strPasswd and the variable
146. Place a check mark H MSIE next to each V HTML Netscape 4 7x Sete goan HTML Netscape 4 x Java Oracle Forms PeopleT ools PowerBuilder Visual Basic Corcel Hen Figure 9 19 Select extensions Ensure that the Java check box is selected if it was not you would also need to restart Rational Robot to load the Java Extension Loaded Application Extensions loaded have a performance downgrade drawback if you are not writing simulations on the other application types in the list deselect them Setting up the HTML extensions Rational Robot supports simulations that run in a Web browser thanks to browser specific extensions that must be loaded by Rational Robot The browsers supported for testing are all versions of Microsoft Internet Explorer Netscape 4 x and Netscape 4 7x By default Rational Robot supports MSIE and Netscape 4 7x You can check the loaded extensions by selecting Tools Extension Manager this will display the Extension Manager dialog shown in Figure 9 19 Any changes in the Extension Manager list will require Rational Robot to restart in order to load the selected extensions If you plan to test only a specific set of the application types listed in the Extension Manager deselect those you do not plan to use to increase Rational Robots performance One important point to consider when planning a simulation in a browser is that the machine that will run the simulation s browse
147. Provisioning Policy based Orchestration vvvvy Products within each of these areas have been made available over the years and as they are continually enhanced have become accepted solutions in enterprises around the world With these core capabilities in place IBM has been able to focus on building applications that take advantage of these solution silos to provide true business systems management solutions A typical business application depends not only on hardware and networking but also on software ranging from the operating system to middleware such as databases Web servers and messaging systems to the applications themselves A suite of solutions such as the IBM Tivoli Monitoring for products enables an IT department to provide consistent availability management of the entire business system from a central site and using an integrated set of tools By utilizing an end to end set of solutions built on a common foundation enterprises can manage the ever increasing complexity of their IT infrastructure with reduced staff and increased efficiency End to End e business Transaction Management Made Easy Within the availability group in Figure 1 11 on page 30 two specific functional areas are used to organize and coordinate the functions provided by Tivoli products These areas are shown in Figure 1 12 Rapid time to value 0Open architecture Event Correlation and Automation May be deployed independently
148. SL Key File Name Key File Password Trust File Name instal l keyfiles prodms jk Trust File woo Password Port for non SSL post agents Port for SSL B446 agents Port for the management 9445 server Console InstallShield lt Back Next gt Cancel Figure 4 26 SSL enablement window gt The installation wizard automatically detects the location of the installed WebSphere if the environment variables are set correctly In our environment the WebSphere Application Server security is not enabled so we unchecked the check box and set the user to root Figure 4 27 on page 112 Since the WebSphere Application Server security is not enabled the user you specify here must have root privileges to perform the operation The installation automatically switches the WebSphere Application Server security on once the product was installed and the WebSphere Server has been restarted Chapter 4 TMTP WTP Version 5 2 installation and deployment 111 4 Install the Management Server Figure 4 27 WebSphere configuration panel gt As the DB2 database is already installed we choose for the Use an existing DB2 database option Figure 4 28 on page 113 112 End to End e business Transaction Management Made Easy E Install the Management Server lol x E Database Options Use an existing Oracle database FUse an existing DB2 database installShield lt Back Next gt Cancel N Figu
149. STALLING COPYING ACCESSING OR USING THE PROGRAM YOU AGREE TO THE TERMS OF THIS AGREEMENT IF YOU ARE Tivoli software ACCEPTING THESE TERMS ON BEHALF OF ANOTHER PERSON ORA COMPANY OR OTHER LEGAL ENTITY YOU REPRESENT AND WARRANT THAT J FG YOU HAVE FULL AUTHORITY TO BIND THAT PERSON COMPANY OR LEGAL ENTITY TO THESE TERMS IF YOU DO NOT AGREE TO THESE TERMS InstallShield DO NOT DOWNLOAD INSTALL COPY ACCESS OR USE THE PROGRAM AND acceptthe terms in the license agreement Ido not acceptthe terms in the license eneen Cancel Back Figure 8 5 STI Software License Agreement dialog 7 Select the I accept radio button and click Next Then the installer depicted in Figure 8 6 on page 244 will be displayed Chapter 8 Measuring e business transaction response times 243 Installer 5 x ER Sterne Management Server Information CE z Hostname tivdce4 itsc austin ibm com a a a z eee SSL Enabled ime a Ws C NO Port Number 9082 InstallShield Back Next Cancel Figure 8 6 Installation of STI Recorder with SSL disable 8 Either select to enable or disable the use of Secure Socket Layer SSL communication Figure 8 6 shows a configuration with SSL disabled and Figure 8 7 shows the selection to enable SSL loj xj Internet Management Server Information Hostname tivdce4 itsc austin ibm com SSL Enabled Ve Use default Port N mo SE se default Port Number No ls
150. Seconds 0 0 08 18 08 19 08 19 08 20 08 20 10 00 00 20 15 00 05 30 20 00 Time Yoar Month Day Hour Minute Stat Time 2003 x 8 15 20 o gt Stop Time 2003 6 20 gt Ge 21 o Figure 7 4 Topology Line Chart The main line shown in the sample Topology Line Chart shown in Figure 7 4 represents the hourly averages for the node while a blue shaded area represents the minimum and maximum values for those same hours If the time range is for 24 hours or less then each point is a hyperlink that shows the aggregate topology for that hour If there are 25 hours or more shown there are no points to click but the time range can be shortened around an area of interest to provide access to these topologies 218 End to End e business Transaction Management Made Easy 7 5 STI Report The STI Report shows the hourly performance of the STI playback policy over time The initial view shows the time length of the overall transactions which are color coded to show if any thresholds were breached yellow or if there were any availability violations red An example of the STI Report main dialog is shown in Figure 7 5 BpSoand gt EN Chet Policy ST googie enat T Na hun coat iha va Transactica ST poo ghe merih Poir mM go mnd Ai Iainsg sicet Apes pia O EG ah Trreuaction ST googla merh 2 SD ms sm a EE aveati Motion am E Trasoje veiatos im ie Vasten E ripi poges pse
151. Server gt You should enable the Java Virtual Machine Profile Interface JVMPI to improve performance analysis The JVMPI is available on the Windows AIX and Solaris platforms However you do not need to enable JVMPI data reporting to use the Resource Models included with IBM Tivoli Monitoring for WebSphere Application Server Chapter 5 Interfaces to other management tools 157 IBM HTTP Server For the prerequisites needed to monitor the IBM HTTP Server refer to BM Tivoli Monitoring for Web Infrastructure Apache HTTP Server User s Guide Version 5 1 SH19 4572 5 1 3 Creating managed application objects Before you start to manage Web server resources they must first be registered in the Tivoli environment This registration is achieved by creating specific Web Server objects in any policy region When installing IBM Tivoli Monitoring for Web Infrastructure a default policy region corresponding to the IBM Tivoli Monitoring for Web Infrastructure module is automatically created For the WebSphere Application Server module this policy region is named Monitoring for WebSphere Application Server Note Normally managed application objects are created in the default policy regions If you want to create the managed application objects in a different policy region you must first add the relevant IBM Tivoli Monitoring for Web Infrastructure managed resource to the list of resources supported by the specific policy region The WebSph
152. Service and J2EE monitoring components Two playback components Playback components robotically execute or play back transactions that you record in order to simulate actual user activity For example you can record and play back an online ordering transaction to assess the relative performance of different Web servers or to identify potential bottlenecks before launching a new interactive application Playback components are Synthetic Transaction Investigator and Rational Robot Generic Windows Discovery listening and playback operations are run according to instructions set forth in policies that you create A policy defines the area of your Web site to investigate or the transactions to monitor indicates the types of information to collect specifies a schedule and provides a range of other parameters that determine how and when the policy is run The following subsections describe the discovery listening and playback components The discovery component When you use the discovery process you create a discovery policy in which you define an area of your Web environment that you want to investigate The discovery policy then samples transaction activity and produces a list of all URI requests with average performance times that have occurred during a discovery period You can consult the list of discovered URIs to identify transactions to monitor with listening policies A discovery policy is associated with one of the two li
153. TCTL_FROM_INTSEQ 1 UPDATE TWG Extract_control SET EXTCTL_TO_INTSEQ 1 UPDATE TWG Extract_control SET ExtCtl_From_DtTm 1970 01 01 00 00 00 000000 UPDATE TWG Extract_control SET ExtCtl_To DtTm 1970 01 01 00 00 00 000000 192 End to End e business Transaction Management Made Easy Tools The extract_win bat script resets the Extract Control window for the warehouse pack You should use this script only to restart the Extract Control window for the BWM_m05_Mart_Process If you want to reset the window to the last extract use the extract_log to get the last values of each DB2 BWM extract The bwm_c10_CDW_process bat script executes the BWM_c10_CDW_Process from the command line The bwm_m05_MART_Process bat script executes the BWM_m05_Mart_Process from the command line The bwm_upgrade_clear sql script undoes all the changes that the bwm_c05_s030_upgrade_convertdata process made This script helps with troubleshooting for the IBM Tivoli Monitoring for Transaction Performance Version 5 1 upgrade process If errors are raised during the data converting use this script to help clear up the converted data After the problem is fixed you can rerun the bwm_c05_s030_upgrade_convertdata process to continue the upgrade and migration For more details about managing the Tivoli Data Warehouse see the Tivoli Enterprise Data Warehouse manuals and the following Redbooks gt Planning a Tivoli Enterprise Data Warehouse Project SG24 6608 gt Introd
154. THER LEGAL ENTITY YOU REPRESENT AND WARRANT THAT YOU HAVE FULL AUTHORITY TO BIND THAT PERSON COMPANY OR LEGAL ENTITY TO THESE TERMS IF YOU DO NOT AGREE TO THESE TERMS DO NOT DOWNLOAD INSTALL COPY ACCESS OR USE THE PROGRAM AND PROMPTLY RETURN THE PROGRAM AND PROOF OF ENTITLEMENT TO THE PARTY FROM WHOM YOU ACQUIRED IT TO OBTAIN A REFUND OF THE AMOUNT YOU PAID IF YOU DOWNLOADED THE PROGRAM CONTACT THE PARTY FROM WHOM YOU ACQUIRED IT isl accept the terms in the license agreement do not accept the terms in the license agreement lt Back Next gt Cancel N Figure 4 35 License agreement window gt Figure 4 36 on page 121 specifies the installation location of the Store and Forward agent We leave this on the default setting End to End e business Transaction Management Made Easy ml Install Store and Forward Agent H ol x Click Next to install the management agent to this folder or click Browse to install to a different folder ey Directory Name ees caProgram FilesVBMiTivoliiSnF Browse InstallShield i Cancel Figure 4 36 Installation location specification 5 In the first field of Figure 4 37 on page 122 we can specify the Proxy URL This URL can be either the Management Server itself or in a chained environment and another Store and Forward agent This specifies the URL where the Store and Forward agent connects to We specify the Management Server sinc
155. TP 5 2 components 0 00 cee ee 40 2 3 Reporting and troubleshooting with TMTP WTP 4 44 2 4 Integration points 0 0 2 eee 51 Chapter 3 IBM TMTP architecture 20000 eee eae 55 3 1 Architecture overview 0 0 eee 56 3 1 1 Web Transaction Performance 00 0c eee eee 56 3 1 2 Enterprise Transaction Performance 220005 58 Copyright IBM Corp 2003 All rights reserved iii 3 2 Physical infrastructure components 00 02 eee eee eee 61 3 3 Key technologies utilized by WTP 002 02 e eee 67 3S ARM Soca aie ae ES fhe SMa aed aan are TD SOE RES 67 3 3 2 J2EE instrumentation 00 ees 72 3 4 Security features 2 ee 76 3 5 TMTP implementation considerations 0000 eee 79 3 6 Putting it all together 0 eere dane eee 80 Part 2 Installation and deployment 0 00 eee 83 Chapter 4 TMTP WTP Version 5 2 installation and deployment 85 4 1 Custom installation of the Management Server 04 87 4 1 1 Management Server custom installation preparation steps 88 4 1 2 Step by step custom installation of the Management Server 107 4 1 3 Deployment of the Store and Forward Agents 118 4 1 4 Installation of the Management Agents 05 130 4 2 Typical installation of the Management Server 137 Chapter 5 Interfaces
156. Table 10 3 lists the process that needs to be scheduled for the IBM Tivoli Monitoring for Transaction Performance ETLs to run Table 10 3 Warehouse processes TMTP ETL1 BWM_c10_CDW_Process periodically TMTP ETL2 BWM_m05_Mart_Process periodically To schedule a process no matter if it has to run once or multiple times the same basic steps need to be completed The only difference between one time and periodically executed processes is the schedule provided The following provides a brief walk trough using the process BWM_c10_CDW_Process to describe the required steps 1 On the TEDW Control Center server using the Data Warehouse Center window expand Subject Areas 2 Select the appropriate Subject Area for example BWM_Tivoli_Monitoring_for_Transaction_Performance_v5 2 0_Subject_Are a and explode it to see the processes 3 Right click on the process to schedule in our example BWM_c10_CDW_Process and choose Schedule as shown in Figure 10 19 on page 402 Chapter 10 Historical reporting 401 402 iin Data Warehouse Center Warehouse Selected Edit View Tools Help Hog aang AE Warehouse C Subject Areas AMx_IBM_TIVOLI_Monitoring_v5 1 1_Subje AMY_Operating_Systems_PAC_v1 1 0_Su ANM_IBM_Tivoli_Netview_v1 1 0_Subject al BWM_Tivoli_Monitoring_for_Transaction_F Processes E BymM_cO5_Upgrade51_Process EA BWi_c10_CDW_Proc p TE BWM_m05_Mart_Proce Defne x Sa CDW _TivoliEnterpriseDataWa C War
157. The SSL protocol will be enabled using these files We are using the custom KEY and STASH files prodsnf kdb and prodsnf sth 122 End to End e business Transaction Management Made Easy net Install Store and Forward Agent E Ioj x InstallShield The Store and Forward Service runs in a process called the WebSphere Caching Proxy WCP The installation program installs WCP and enables the SSL protocol Specify the name ofthe key database kdb file and its password stash sth file Pathname for kdb file c keyfiles prodsnf kdb Pathname for password c key lesiprodsns hane cAkeyfilesiprodsnf sth Copy KDB files to local a config directory Back Next gt Cancel Figure 4 38 KDB file definition 7 In Figure 4 39 on page 124 we have to specify the following things SnF Host Name The Store and Forward agent fully qualified host name In our case it is canberra itsc austin ibm com User Name User Password We have to specify a user that has an agent role on the WebSphere Application Server which is the same as the Management Server in our environment We specify the root account Enable SSL We select this option since we have a secure installation of the Management Server We use the Default Port Number which is 433 This will be the communication port for the Management Agents connecting to this Store and Forward agent SSL Key store file SSL Key store file password We use the previously created
158. The last zone is the Internet zone where we also need to deploy a Store and Forward agent and Management Agents on the client workstations The host name of the Store and Forward agent in this zone is frankfurt The canberra Store and Forward agent will be connected directly to the Management Server while the frankurt Store and Forward agent will be connected directly into the canberra Store and Forward agent So the Canberra will basically serve as a Management Server for the frankfurt Store and Forward agent Chapter 4 TMTP WTP Version 5 2 installation and deployment 87 4 1 1 Management Server custom installation preparation steps 88 In this section we will discuss the preparation steps of the Management Server custom installation We already have installed DB2 Version 8 1 and WebSphere Application Server Version 5 0 with FixPack 1 applied Note The version number of the WebSphere Application Server changes to 5 0 1 from 5 0 after applying WebSphere FixPack 1 The following steps will be performed Operating system requirements check File system creation Depot directory creation DB2 configuration 1 2 3 4 5 WebSphere configuration 6 Port numbers 7 Generating JKS file 8 Generating KDB and STH files 9 Exchanging certificates 1 0 Environment variables and last checkups Here are the steps in more detail 1 Operating system requirements check In our scenario we are using AIX Version 4 3 3 as the h
159. These tiger teams often generate a lot of finger pointing and blaming This is unpleasant and itself leads to longer problem resolution response times Chapter 2 IBM Tivoli Monitoring for Transaction Performance in brief 39 All of this is very painful and can be very expensive TMTP 5 2 solves this problem by pinpointing the exact cause of a transaction performance problem with your e business application quickly and easily and then facilitating resolution of that problem 2 2 Introducing TMTP 5 2 IBM Tivoli Monitoring for Transaction Performance Web Transaction Performance TMTP WTP is a centrally managed suite of software components that monitor the availability and performance of Web based services and Microsoft Windows applications IBM Tivoli Monitoring for Transaction Performance captures detailed performance data for all of your e business transactions You can use this software to perform the following e business management tasks gt Monitor every step of an actual customer transaction as it passes through the complex array of hosts systems and applications in your environment Web and proxy servers Web application servers middleware database management systems and legacy back office systems and applications gt Simulate customer transactions collecting what if performance data that helps you assess the health of your e business components and configurations gt Consult comprehensive real time reports that
160. To be able to clearly identify the scope and purpose of a TMTP monitoring policy it is suggested that a standard for naming policies be developed prior to deploying TMTP in your production environment gt Including network related issues in you monitoring data If you want to simulate a particular business transaction executed from specific locations in order to include network latency in your monitoring you will have to plan for playing back the transaction from both the corporate net intranet and Internet in order to be able to compare end user experienced time from two different locations This may help you determine inexpedient routing in your network infrastructure This technique may also be used to verify transaction availability from remote locations gt Trace levels for J2EE and ARM data collection Depending on your level of tracing you might incur some additional overhead up to as much as 5 during application execution Please remember that only instances of transactions that are included in the scope of the filtering defined for a monitoring policy will incur this overhead All other occurrences of the transaction will perform normally Chapter 8 Measuring e business transaction response times 227 gt Back out updates performed by simulated transactions If Synthetic Transaction Investigator or Generic Windows is used to playback a business transaction that updates a production database with for example purchase
161. Topology View but this report offers flexibility in changing which Listening Playback policy to show the data for This allows older no longer active data to be viewed in addition to any currently active policies All other behaviors for line charts instance topology views and so on are the same Availability Graph Shows the health of the chosen monitoring policy as a percentage over time The line represents the number of failed that is availability violations transactions per hour expressed as a percentage Figure 7 8 General Reports gt Availability Chari Change settings Policy STI google search Management Agent bgehman ma austin ibm com Transaction STI google cearch 2 6 0 100 0 NIZ Percent Available 80 0 Year Month Day Hour Minute Start Time 2003 y 8 19_y a 20 z 00 Stop Time 2003 8 20 BY 20 x 00 7 Apply Alt a Figure 7 8 Availability graph 222 End to End e business Transaction Management Made Easy Page Analyzer Viewer The Page Analyzer Viewer is the same data display mechanism as in TMTP Version 5 1 and provides a breakdown of Web page loading when loaded through the STI Choices are made through drop down boxes for the policy agent and time of collection Data is collected if the Web Detailer box is checked in the STI Playback policy An example of a Page Analyzer Viewer report is provide
162. TradeBean getMarketSummaryQ gt Configuration vReports View Big Board View General Reg View Component vSystem Administ Work with Agents Configure Systerr Component Mana Configure User Se Work with Event F View System Eve View Log Files View Managemer b Downloads Average Min Max Range 10 01 10 01 10 02 10 02 10 02 19 00 23 45 04 30 09 15 14 00 Time al l kaa N l Figure 8 54 Trade EJB response time view get market summary Figure 8 55 on page 306 shows you how to drill all the way into a JDBC call to identify the database related bottlenecks on a per statement basis Chapter 8 Measuring e business transaction response times 305 MEOIN 6H J2EE WebS phere 5 0 BMTIV9 IBMTI vec am DB2PreparedStateme execute Query x Figure 8 55 Topology view of J2EE and trade JDBC components For root cause analysis we can combine the topology view showing the e business transaction subtransaction and EJB JDBC and JSP methods with ITM events of different resource models like CPU processor database Web and Web application using the ITM Web Health Console Ultimately we can send the violation event to TEC Figure 8 56 on page 307 shows you how to launch the ITM Health Console directly from the topology view 306 End to End e business Transaction Management Made Easy joes o Ww oa ie iS daa e Sar ae Address a ht
163. U scripts 0 5 344 9 1 4 Steps to record a GUI simulation with Rational Robot 345 9 1 5 Add ARM API calls for TMTP in the script 351 9 2 Introducing GenWin 0 aaaea 365 9 2 1 Deploying the Generic Windows Component 365 9 2 2 Registering your Rational Robot Transaction 368 9 2 3 Create a GenWin playback policy 0 2 0005 369 Chapter 10 Historical reporting 20 00 0c eee aes 375 10 1 TMTP and Tivoli Enterprise Data Warehouse 376 10 1 1 Tivoli Enterprise Data Warehouse overview 376 10 1 2 TMTP Version 5 2 Warehouse Enablement Pack overview 380 10 1 3 The monitoring process data flow 0 0 eee eee 382 10 1 4 Setting up the TMTP Warehouse Enablement Packs 383 10 2 Creating historical reports directly from TMTP 24 405 10 3 Reports by TEDW Report Interface 00 0 0 c eee eee 406 10 3 1 The TEDW Report Interface 0 0 0 0 cee ee eee 406 10 3 2 Sample TMTP Version 5 2 reports with data mart 408 10 3 3 Create extreme case weekly and monthly reports 413 10 4 Using OLAP tools for customized reports 000000005 417 10 4 1 Crystal Reports overview aaau eee eee 418 10 4 2 Crystal Reports integration with TEDW 418 10 4 3 Sample Trade application reports
164. WH_MART_Target BWH_TWH_MD Target Edit the properties of each one of the entries above i Data Warehouse Center Warehouse Selected Edit View Tools Help HR J j a agaaga BE ea BWM_TMTP_DATA_SOURCE m a a Warehouse Sources ER AMX_ITM_RIM_Source AMX_TWWH_CDVV_Source a AMY_TWH_CDVV_Source R AMY_TWH_MART_Source ANM_AVAIL_Source ANM_TWWH_CDVY _Source U ayM_TMTP_Dy 2 BWM_TWH_CDW_Source 2 BWM_TWH_MART_Source ee CDW _TWH_CDW_Source a Warehouse Targets ER AMX_TWH_CDW_Target ER Anty_TWH_MART_Target ER AMy_TWH_MD_Target ER ANM_TWH_CDW_Target ER ANM_TWH_MART_Target ER ANM_TWH_MD_Target ER BWM_TWH_CDW_Target ER ewM_TWH_MART_Target aE BYWM_TWH_MD_Target ER CDW_TWH_CDW_Target fil Warehouse Schemas Figure 10 13 TMTP ETL Source and Target E il Remove Locate Change User ID and Password Show Related ic E E Refresh Hpk Dh amp In order to edit the properties of the ETL sources right click on the actual object and select Properties from the pop up menu Then select the Data Source tab Fill in the database instance owner user ID information For our environment the values are shown in Figure 10 14 on page 396 using the BWM_TMTP_DATA_SOURCE as an example Chapter 10 Historical reporting 395 iz Properties BWM_TMTP_DATA_SOURCE 3 x BWM_TMTP_DATA_SOURCE Warehouse Source Agent Sites
165. We 2p_2_httplibmtiv9 itsc austin ibm com 82itradefapp 2003 10 0 0 625 Step_5_hi ibmtiv9 itsc austin ipbm com 82itrade app action portfolioa 2003 10 0 3 203 _ Step_3_http ibmtiv9 itsc austin ipm com 82itrade app p 2003 1 0 0 1 063 Step_4_httpvibmtiv9 itsc austin iom com 82itrade app action quotes amp symbols s 0 s 1 2003 1 0 0 0 64 Step_6_httpvipmtiv9 itsc austin ipm com 82itrade app action logout 2003 10 0 0 035 We Backend Service Time_4 2003 10 0 0 076 0 005 Backend Service Time_6 2003 10 0 0 012 0 004 Backend Service Time_2 2003 10 0 0 013 0 005 Backend Service Time_5 2003 10 0 2 602 0 008 Backend Service Time_3 2003 10 0 0 034 0 03 com ibm websphere samples trade web OrdersAlertFilter doFilter avax servlet ServietRe 2003 10 0 0 015 0 013 com ibm websphere samples trade web OrdersAlertFilter doFiltergavax serviet ServietRe 2003 10 0 2 625 2 076 corm ibm websphere samples trade web OrdersAlertf ilter doF iiter javax serviet ServietRe 2003 10 0 0 072 0 043 com ibm websphere samples trade web OrdersAlertFilter doFi javax servlet ServietRe 2003 10 0 0 008 0 006 com ibm websphere samples trade web OrdersAlertFilter doFil ax serviet ServletRe 2003 10 0 2 614 2 068 com ibm websphere sarpples trade web TradeAppServiet doPoSijyyax seniet http HttpS 2003 10 0 2 497 1 973 org apache jsp _tradehomp _ispService iavax serviet http HttpSerleqgeq
166. WeFrameManager jsp Microsore Interne Fle Edit View Favorites Tools Help Back gt amp A Gt Gsearch Gjravortes Media G ES 6 SI la Address https forcrist tiviab austin ibm com 9445 tmtpUL jsp console weFrameManager jsp gt Links Tivoli Monitoring for Transaction Performance User Name root gt Configurat Reports View Big View Ger View Cor b System A gt Downloads Her amen oe amp d 4 quickbeam tiviab austin ibm com J2EE WebS phere 5 Ofquickbeanmvquic EE z Servlet Bane ul Timer m is Pa e al JSP doGet http q ulokbes m 9080 ServietTest 6 004 httpvfquickbearn 9080 ServietTesw HE gt 2 Opening https forcrist tiviab austin bm com 9445 tmtpUI ilog views sdm renderer graphlayout IlvTreeLayoutParamel W Internet Figure 2 7 Instance topology Again this topology has the one second filtering turned on so any extraneous nodes are filtered out Here the administrator can see that as suspected the Timer goGet method is taking up a majority of the time ruling out a problem with the root transaction The Timer goGet method has an upside down orange triangle indicating it has been deemed the most violated instance This calculation is determined by comparing the instances duration 6 004 seconds in this case to the average for the hour 4 303 seconds as we saw above while taking into a
167. Z Some of these considerations are discussed further in Chapter 8 Measuring e business transaction response times on page 225 3 6 Putting it all together Figure 3 10 on page 81 shows a typical modern e business application architecture around which we have placed the TMTP WTP components This will 80 End to End e business Transaction Management Made Easy help the reader to visualize how the WTP components could be placed The application architecture introduced below will form the basis of most of the scenarios that we cover in later chapters In the rest of this book we have used the Trade and PetStore J2EE applications for our monitoring scenarios Each of these examples is shipped with WebSphere 5 0 1 and Weblogic Figure 3 10 shows an e business architecture that may be used to provide a highly scalable implementation of each of these applications Typical features of such an infrastructure include the use of a Web tier consisting of many Web servers serving up the applications static content and an Application tier serving up the dynamic content Generally a load balancer will be used by the Web tier to distribute application requests among the Web servers Each Web Server may then use a plug in to direct any requests for dynamic content from the Web Server to the back end application server The application server provides many services to the application running on it including data persistence that is access to back end d
168. _MAX_VAL a MSMTTYP MSMTTYP_NM a MSMT MSMT_STRT_DT Report Area Avg of MSMT ME Report Area Sum of MSMT M Group 1 COMP COMP_NM E Group 2 MSMT MSMT_STF E e TWH_CDW ODBC TWH_CDW COMP a COMP_ID a COMPTYP_CD a CENTR_CD a CUST_ID s Po of Design Report Preview Sample Help Cancel lt lt Back Next gt gt Finish Figure 10 33 Crystal Reports filtering definition MSMTTYP MSMTTYP_NM COMP COMP_NM Add gt lt Remove ik Browse Data Response Time gt Provide a title for the report for example Telia Trade Stock Check Report and click Finish Tip You can make a filter for the MSMTTYP_NM field and choose different values such as Response time Round trip time Overall Time and more to create different type of reports 10 4 3 Sample Trade application reports We have created the following sample reports using a very simple Crystal Reports report design Average Simulated Response Time by date J2EE Response Time by date JDBC Response Time by date Average End user Experience by date vvvy You can download the Crystal Reports files containing the report specifications Please refer to Appendix C Additional material on page 473 for details on how to obtain a copy Chapter 10 Historical reporting 421 Average Simulated Response Time by date The Average Simulated Response Time by date report in Figure 10 34 shows that the response times
169. _db2_1 dd1 keyfiles lib lost found media inf prereqs dtd reboot exe 532041609 Sep 08 09 58 setup_MS jar 18984898 Sep 08 09 58 setup_MS_aix bin setup_MS_aix cp MS_lin bin setup_MS_lin cp MS_11n390 bin setup_MS_1in390 cp _MS_sol bin setup_MS_sol cp setup_MS_w32 cp 18516023 Sep 08 09 58 setup_MS_w32 exe startpg exe tmp w32util dl l was5 wasFp1 4 DB2 configuration As we already mentioned DB2 Version 8 1 is already installed We need to perform additional steps to enable the setup to run successfully a d As we are emulating a production environment we have already created a separate db2 instance for the TMTP database The instance name and user is set to dbtmtp Note To create a new DB2 instance you can either use the db2setup program or the db2icrt command We have to create the TMTP database before we start the installation You can choose any name for the TMTP database In this scenario we name the database TMTP We perform the following commands in the DB2 text console to create the TMTP database in the previously created opt IBM dbtmtp directory create database tmtp on opt IBM dbtmtp DB20000I1 The CREATE DATABASE command completed successfully We also need to create the buffpool32k bufferpool So we first connect to the database connect to tmtp Database Connection Information Database server DB2 6000 8 1 0 SQL authorization ID DBIMTP Local database alias TMTP a
170. a BEE ed baled baw XX Prolite aa AS AE Nace AOE IER De Ata ihe eee ie A A ole a xxi The team that wrote this redbook 000s xxii Become a published author 0 0 cece ee xxiv Comments welcome 0 000 cect a XXiV Part 1 Business value of end to end transaction monitoring 1 Chapter 1 Transaction management imperatives 3 1 1 e business transactions oerna saaa E a a F RE e eie ee 4 1 2 J2EE applications management 0 00 c eee ee 5 1 2 1 The impact of J2EE on infrastructure management 7 1 2 2 Importance of JMX oeeaaeaii aa a E o S ia 8 1 3 e business applications complex layers of services 11 1 3 1 Managing the e business applications 04 15 1 3 2 Architecting e business application infrastructures 21 1 3 3 Basic products used to facilitate e business applications 23 1 3 4 Managing e business applications using Tivoli 26 1 4 Tivoli product structure 0 0 ee 28 1 5 Managing e business applications 0 0 0 e eee eee 32 1 5 1 IBM Tivoli Monitoring for Transaction Performance functions 33 Chapter 2 IBM Tivoli Monitoring for Transaction Performance in brief 37 2 1 Typical e business transactions are complex 00 eee 38 2 1 1 The pain of e business transactions 2000 eae 38 2 2 Introducing TMTP 5 2 1 1 eae 40 2 2 1 TM
171. a lower level from your poorly performing transaction and can allow you to identify issues such as poorly configured systems Also with the addition of products such as IBM Tivoli Monitoring for Databases IBM Tivoli Monitoring for Web Infrastructure and IBM Tivoli Monitoring for Business Integration you will be further able to diagnose infrastructure problems and in many cases resolve them prior to their impacting the performance of your e business transactions 9 3 4 209 STI Overall Transaction zSeriestTrade 5 08 Events View Response Times View Web Health Console Thresholds view Minimum Maximum view Figure 2 12 Launching the Web Health Console from the Topology view Chapter 2 IBM Tivoli Monitoring for Transaction Performance in brief 51 52 Tivoli Enterprise Console TEC The IBM Tivoli Enterprise Console provides sophisticated automated problem diagnosis and resolution in order to improve system performance and reduce support costs Any events generated by TMTP can be automatically forwarded to the TEC TMTP ships with the Event Classes and rules for TEC to make use of event information from TMTP Tivoli Data Warehouse TDW TMTP ships with both ETL1 and ETL2 which are required to use the Tivoli Data Warehouse This allows historical TMTP data to be collected and analyzed It also allows TMTP to be used with other Tivoli products such as the Tivoli Service Level
172. a the Web to demonstrate the business value of IT As described above TMTP ships with the required ETLs needed for the Tivoli Service Level Advisor to utilize the information gathered by TMTP to create and monitor service level agreement compliance Simple Network Management Protocol SNMP Support For environments that do not have existing TEC implementations or where the preference is to integrate using SNMP TMTP has the ability to generate SNMP traps when thresholds are breached or to monitor TMTP itself Simple Mail Transport Protocol SMTP TMTP is also able to generate e mail messages to administrators when transaction thresholds are breached or when TMTP encounters some error condition End to End e business Transaction Management Made Easy gt Scripts Lastly TMTP has the capability to run a script in response to a threshold violation or system event The script is run at the Management Agent and could be used to perform some type of corrective action Configuring TMTP to integrate with these products is discussed in more depth in Chapter 5 Interfaces to other management tools on page 153 Chapter 2 IBM Tivoli Monitoring for Transaction Performance in brief 53 54 End to End e business Transaction Management Made Easy IBM TMTP architecture This chapter describes the following gt High level architectural overview of IBM Tivoli Monitoring for Transaction Performance gt Detailed architecture for IBM Tivoli M
173. action Management Made Easy Installing Put the Rational Robot CD ROM in the CD ROM tray of the machine where simulations will be recorded or played back setup is identical in both cases Double click on the C517JNA exe application which you can find in the robot2003GA folder in the Rational Robot CD The setup procedure will start You should get the window shown in Figure 9 1 Rational Robot for Windows InstallShield Wizard Location to Save Files Where would you like to save your files Please enter the Folder where you want these files saved If the folder does not exist it will be created for you To continue click Next Save files in Folder C Program Files Rational Robe Change InstallShield Figure 9 1 Rational Robot Install Directory Change the install directory if you are not satisfied with the default setting and select OK The install directory will be displayed at a later stage but no changes will be possible After you click Next the install continues for a while see Figure 9 2 on page 328 Chapter 9 Rational Robot and GenWin 327 Rational Robot for Windows InstallShield Wizard Extracting Files The contents of this package are being extracted Please wait while the InstallShield Wizard extracts the files needed to install Rational Robot for Windows on your computer This may take a Few moments R Reading contents of package Ins
174. action Performance Enterprise Transaction Performance will be used to demonstrate the tasks that needs to be performed and the changes needed to implement the Warehouse Enablement Pack for IBM Tivoli Monitoring for Transaction Performance Web Transaction Performance will be noted at the end of the walkthrough The installation and configuration of the Warehouse Enablement Packs is a four step process that consists of Pre installation steps These steps have to be performed to make sure that the TEDW environment is ready to receive the TMTP Warehouse Enablement Packs Installation The actual transferral of code from the installation images to the TEDW server and registration of the TMTP ETLs in the TEDW registry Post installation steps Provides additional configuration information to ensure the correct function of the TMTP Warehouse Enablement Packs Activation Includes scheduling and transfer to production mode of the TMTP specific ETL tasks Pre installation steps Prior to the installation of the Warehouse modules you must perform the following tasks 1 Upgrade to DB2 UDB Server Version 7 2 FixPack 6 or higher 2 Apply TEDW FixPack 1 1 TDW 002 or higher 3 Update the TEDW environment to FixPack 1 1 TDW FP01a 4 Ensure adequate heap size of the TWH_CDW database You are only required to perform these steps once since they apply to the general TWDW environment and not to any specific ETLs Upgrade to DB2 UDB Server V
175. actions data All six types of reports can be reached from the main General Reports dialog shown in Figure 7 6 ial General Reports 09272019 00280219 09280819 Overall Transaction Over Time Transaction With Subtransactions Hoste y Was Select _Name___Severty Date M nameo1 Minor 12 03 02 ppe M name02 Minor 12 03 02 m 50s 218 1 28 M name03 Minor 12 03 02 KAN M names Minor 12 03 02 Vv C name0s Minor 12 03 02 oa a q Page 20f5 D Go 28 18 Slowest Transactions Topology Page Analyzer Viewer Report cn Pray atten eet Akenj gt AA 18 09 27 20 19 00280219 03 2808 19 3 2 Availability Page Analyzer Viewer Figure 7 6 General reports Overall Transactions Over Time This report shows the hourly performance of an transaction for a specified policy and agents over time It allows multiple agent s averages to be plotted against 220 End to End e business Transaction Management Made Easy each other for comparison In addition a solid horizontal line represents the policy threshold Transactions with Subtransactions This report shows the hourly performance of subtransactions for a specified transaction and policy and agent in a stacked area graph as shown in Figure 7 7 General Reports gt Transaction With Subtransactions Change settings Policy STI googla seasch Management Agent bgehmanme mstnibm com Transaction STI goagle avatch
176. ade Easy E4 IBM Key Management install keyfiles prodagent jks Key Database File Create View Help Dis td XR Key database information DB Type JKS database file File Name _finstall keyfiles prodagent jks Token Label Key database content Signer Certificates Mi Add prodsnf Delete verisign class 1 public primary certification authori n verisign class 2 public primary certification authoriy View Edit rsa secure server certification authority verisign class 2 public primary certification authori Extract prod verisign class 3 public primary certification authori verisign test ca root certificate j verisign class 1 ca individual subscriber persona n verisign class 3 public primary certification authori thawte premium server ca verisign class 1 public primary certification authori thawte personal basic ca ri A signer certificate is from a certification authority CA or from another web Figure 4 19 Add a new self signed certificate Select the prodms arm file and press OK to add it to the prodagent jks file Figure 4 20 Data type Base64 encoded ASCII data v Certificate file name prodms arm Location install keyfiles Figure 4 20 Adding a new self signed certificate After pressing OK the ikeyman tool asks for the label of the certificate Use the same name as in the a
177. age 310 gt 8 8 3 J2EE discovery and listening policies for Weblogic Pet Store on page 312 Chapter 8 Measuring e business transaction response times 307 gt 8 8 4 Event analysis and online reports for Pet Store on page 316 8 8 1 The Java Pet Store sample application 308 The WebLogic Java Pet Store application is based on the Sun Microsystems Java Pet Store 1 3 demo The Java Pet Store 1 3 is a J2EE sample application It uses a combination of Java and J2EE technologies including gt gt gt The JavaServer Pages JSP technology Java servlets including filters and listeners The Java Message Service JMS Enterprise JavaBeans including Container Managed Persistence CMP Message Driven Beans MDB and the EJB Query Language EJB QL A rich client interface built with the Java Foundation Classes JFC and Swing GUI components XML and Extensible Style Sheets for Transformation XSLT a reusable Web application framework The welcome dialog is provided in the window shown in Figure 8 57 on page 309 and technical details are available at http java sun com features 2001 12 petstorel3 html End to End e business Transaction Management Made Easy ZR Welcome to the BluePrints Petstore Microsoft Internet Explorer File Edit View Favorites Tools Help Bak gt gt A GsSearch Favorites history E4 Sh Mi n Search Java Pet Store coon J2EE BluePrints Sampl
178. age User Groups Manage Data Marts 800000 500000 4000007 3000007 200000 100000 Oct 1 2003 7 Oct 1 2003 Oct 1 2003 Oct 1 2003 Oct 2 2003 Oct 3 2003 Oct 5 2003 Oct 6 2003 Oct 6 2003 Oct 6 2003 Oct 6 2003 Oct 7 2003 p Oct 7 2003 p Oct 2003 gt Time 1 Number of Executions total O Welcome Manage Reports and Report Output JEU Ie Figure 10 30 Weekly performance load execution by user for trade application Usually the reports are scheduled and run automatically when the data mart is built However you can run the report manually at any time by choosing Run from the reports pop up menu You can now save this report output You will find it in the folder Report Output 10 4 Using OLAP tools for customized reports Online Analytical Processing OLAP is a technology used in creating decision support software that allows application users to quickly analyze information that has been summarized into multidimensional views and hierarchies By summarizing predicted queries into multidimensional views prior to run time OLAP tools can provide the benefit of increased performance over traditional database access tools OLAP functionality is characterized by dynamic multi dimensional analysis of consolidated enterprise data supporting end user analytical and navigational activities including gt Calculations and modeling applied across dimensions through hierarchi
179. agement SG24 5508 gt Tivoli Application Performance Management Version 2 0 and Beyond SG24 6048 gt Unveil Your e business Transaction Performance with IBM TMTP 5 1 SG24 6912 The TMTP ARM engine is a multithreaded application implemented as the tapmagent tapmagent exe on Windows based platforms The ARM engine exchanges data though an IPC channel using the libarm library libarm32 dll on Windows based platforms with ARM instrumented applications The data collected is then aggregated in order to generate useful information correlated with other transactions and thresholds are measured based upon user Chapter 3 IBM TMTP architecture 67 requirements This information is then rolled up to the Management Server and placed into the database for reporting purposes The majority of the changes to the ARM Engine pertain to measurement of transactions In the TMTP 5 1 version of the ARM Engine each and every transaction was measured for either aggregate information or instance data In this version of this component the Engine will be notified as to which transactions need to be measured This is done via new APIs to the ARM Engine that allows callers to identify transactions either explicitly or as a pattern Measurement can be defined for edge transactions which will result in response measurement of the edge and all its subtransactions Another large change in the functionality of the ARM Engine is monitoring for threshol
180. ailable in 3 3 2 J2EE instrumentation on page 72 8 6 1 J2EE component deployment From a customization and deployment point of view the J2EE component is treated just like STI and QoS A Management Agent can be instrumented to perform transaction performance measurements of this specific type of transactions and it will report the findings back to the TMTP Management Server for further analysis and processing Use the following steps to deploy the J2EE component to an existing Management Agent 1 Select System Administration Work with Agents from the navigation pane on the TMTP console 2 Select the Management Agent to which the component is going to be deployed and choose Deploy J2EE Monitoring Component from the drop down menu above the list of endpoints as shown in Figure 8 33 on page 279 When ready click Go to move on to configuring the specific properties for the deployment through the Deploy Components and or Monitoring Component dialog shown in Figure 8 34 on page 280 278 End to End e business Transaction Management Made Easy IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer File 01 XJ Edit view Favorites Tools Help Go Links gt rs Tivoli Monitoring for Transaction Performance b Configuration b Reports YvSystem Administration Work with Agents Configure System Event Details C
181. al Services Figure 1 7 e business solution specific service layers The presentation layer must be a commonly available tool that is installed on all the machines used by users of the e business solution It should support modern development technologies such as XML JavaScript and HTML pages and usually is the browser The standard communication protocols used to provide connectivity using the Internet are TCP IP HTTP and HTTPS These protocols must be supported by both client and server machines The transformation services are responsible for receiving client requests and transforming them into business transactions that in turn are served by the Solution Server In addition it is the responsibility of the transformation service to receive results from the Solution Server and convey them back to the client in a format that can be handled by the browser In e business solutions that do not interact with legacy systems the transformation and Solution Server services may be implemented in the same application but most likely they are split into two or more dedicated services This is a very simple representation of the functions that take place in the transformation service Among other functions that must be performed are identification authentication and authorization control load balancing and transaction control Dedicated servers for each of these functions are usually implemented to provide a robust and scalable e b
182. ality of Service you should note that QoS listening policies may be executed without prior discovery However if you do not know which areas of your Web environment require monitoring create and run a discovery policy first and then create a listening policy To create a a QoS discovery policy for the home page of the TMTP Version 5 2 Console select Configuration Work with Discovery Policies This will make the Work with Discovery Policies dialog shown in Figure 8 22 on page 267 appear End to End e business Transaction Management Made Easy IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer File Edit View Favorites Tools Help Back gt A A GAsearch GFavorites meda B Si a Tivoli Monitoring for Transaction Performance Address E http tivdce4 9082 tmtpUI jsp console WcFrameManager jsp fad e Go User Name administrator onfiguration Work with Discovery Policies Work with Listening Policies Work with Playback Policies Work with Schedules Work with Agent Groups Work with Transaction Recort Work with Realms eports ystem Administration ownloads Please make as petstore_j2ee_dis Schedule petstore_j2ee_dis In scheduled window petstore_qos_dis petstore_j2ee_dis In scheduled window trade_j2ee_dis trade_dis_sch In scheduled window trade_gqos_dis Page 1 gos_gtp trade_dis_sch In schedule
183. ame administrator Configuration Seon z Configure QoS Thresholds Work with Discovery Policies Create Listening Policy Work with Listening Policies Z Configur ne Performance Threshold Type Work with Playback Policies pile Back End Senice Time E Work with Schedules Work with Agent Groups Condition Threshold Above fi 0 0090 Seconds Work with Transaction Recordit Violation Response Level Recovery Response Level Warning Y Harmless Work with Realms Event Response Event Response b Reports b System Administration b Downloads Assign Name i Choose Agent Group ChangeBufferSize ChangeBufferSize Apply Alt a 1 lt Back Alt b Next Alt n gt Finish Alt f Cancel Alt c System Administration E Local intranet Figure 8 31 Configure QoS automatic threshold for Back End Service Time 7 Inthe Configure QoS Thresholds you can specify thresholds specific to each of the types chosen in the previous dialog A Quality of Service transaction status threshold is used to detect a failure of the monitored transaction or to detect the receipt of an HTTP response code from the Web server or specific response times related to the QoS transaction during monitoring Violation events are generated or triggered when failure occurs or when a specified HTTP response code is received Recovery events and the associated notification are generated when the transaction executes as expec
184. ample Figure A 3 on page 435 shows a Custom design that does not have a mandatory Collaboration business pattern or an Extended Enterprise business pattern for a business problem 434 End to End e business Transaction Management Made Easy Collaboration optional Extended Enterprise optional Figure A 3 Custom design A Custom design may also be a Composite pattern if it recurs many times across domains with similar business problems For example the iconic view of a Custom design in Figure A 3 can also describe a Sell Side Hub composite pattern Several common uses of Business and Integration patterns have been identified and formalized into Composite patterns which are shown in Table A 3 Table A 3 Composite patterns Composite Description patterns Electronic User to Online Buying gt www macys com Commerce gt www amazon com Portal Typically designed to aggregate gt Enterprise intranet portal multiple information sources providing self service and applications to provide functions such as payroll uniform seamless and benefits and travel personalized access for its expenses Heer gt Collaboration providers who provide services such as e mail or instant messaging Account Access Provide customers with gt Online brokerage trading around the clock account apps access to their account information gt Telephone company account manager functions gt Bank
185. ample business application from http www 3 ibm com software webservers appserv benchmark3 html and follow the readme html to install Trade on a WebSphere Application Server 5 0 1 application server Trade3 builds off of Trade2 which is used for performance research on a wide range of software components and platforms including WebSphere DB2 Java Linux and more The Trade3 package provides a suite of IBM developed workloads for determining the performance of J2EE application servers Trade3 s new design enables performance research on J2EE 1 3 including the new EJB 2 0 component architecture Message Driven Beans transactions 1 phase and 2 phase commit and Web Services SOAP WSDL and UDDI Chapter 8 Measuring e business transaction response times 235 236 Trade3 also drives key DynaCache WebSphe The architecture of the WebSphere performance components such as re Edge Server AXIS and EJB caching Trade3 application is depicted in Figure 8 1 EJB Container Web Container Entity EJBs Trade Servlets Trade JSPs Holdings EE Websph CMP Trade 3 lebsphere TJ Database ey Command PA 3 E Beans A Websphere SOAP Router Trade Session EJ et lebsphere Web Services TradeBroker UDDI Trade Registry wsDL MDB Queue Streamer T MDB ba
186. anagement Server notifies you in real time of the status of the transactions you are monitoring Application events are generated when performance thresholds exceed or fall below acceptable limits System events are generated for system errors and notifications From the user interface you can view recently generated events at any time You can also configure event severities and indicate the actions to be taken when events are generated gt Object model store for monitoring and playback policies The object model store contains a set of database tables used to store policy information events and other information gt ARM data persistence All of the performance data collected by Management Agents is sent using the ARM API The Management Server keeps a persistent record of the ARM data collected by Management Agents for use in real time and historical reports gt Communication with Management Agents The Management Server uses Web services to communicate with the Management Agents in your environment Figure 3 3 gives an overview of the Management Server architecture Web Services Middle Layer Data Access Layer Axis web services Controller serviet JSP JSP JSP JDBC data access layer Entity Beans 7 y CMP Database MBeans Stateless Session Beans Figure 3 3 Management Server architecture
187. and the appropriate descriptions refer to the BM Tivoli Monitoring for Web Infrastructure Reference Guide Version 5 1 1 GC23 4720 and the IBM Tivoli Monitoring for Web Infrastructure WebSphere Application Server User s Guide Version 5 1 1 SC23 4705 If all the parameters supplied to the Tivoli Desktop the command line or the task are correct the managed server objects icons shown in Figure 5 4 on page 162 are added to the policy region Chapter 5 Interfaces to other management tools 161 Z Monitoring for WebSphere Application Server panda Monitoring for WebSphere Application Server panda sSite Analyzer Figure 5 4 WebSphere managed application object icons 5 1 4 WebSphere monitoring The following section will outline tasks needed to activate monitoring of the availability and performance of the Tivoli Web Site Analyzer application s operational environment with IBM Tivoli Monitoring for Web Infrastructure Resource Models A Resource Model is used to monitor capture and return information about multiple resources and applications When adding Resource Models to a profile these are chosen based on the type of resources that are being monitored WebSphereAS is the abbreviated name of the IBM Tivoli Monitoring category of the IBM WebSphere Application Server Resource Models It is used as an identifying prefix Planning The following list gives the indicators available in the Resource Models provided with
188. and up to five of its subtransactions over a specified period of time A line with data points represents the aggregate response times collected for a specific transaction URI or URI pattern that is monitored by a specific monitoring policy running on a specific Management Agent Colored areas below the line represent response times for up to five subtransactions of the monitored transaction When a transaction is considered together with its subtransactions as it is in this graph it is often referred to as a parent transaction Similarly the subtransactions are referred to as children of the parent transaction By default when you open the Transactions With Subtransactions graph the display shows the parent transaction with the highest recent aggregate response times The default graph also shows the five subtransaction children with the highest response times You can specify a different transaction for the display and you can also specify any subtransactions of the specified transaction In addition you can manipulate graph contents in a variety of other ways to see precisely the data that you want to view Chapter 2 IBM Tivoli Monitoring for Transaction Performance in brief 49 13 38 Step_1_http tiviab01 itsc austin ibm com Step_2_http tiviabO1 itsc austin iom com Step_3_http tiviab01 itsc austin ibm com Step_4_http tiviabO1 itsc austin iom com Step_5_http tiviab01 itsc austin ibm com petstore_2_order_7001 BU
189. ansaction Can be used as a Can be combined Simulated simulation complement of STI with QoS and end user and a Windows J2EE but without experience application any correlation 234 End to End e business Transaction Management Made Easy Component Operation Real time Page Rendering Time and Back End Service Time with correlation Transaction breakdown Advantage First step to measure back end application service for end user transactions Full breakdown analysis of business application EJB JavaServlet Java Servlet pages and JDBC Correlation with other components Can be combined with STI and J2EE with correlation Can be combined with STI and QoS with correlation Description Real time end user experience Application transaction response time and other metric data For more details please see 3 3 Key technologies utilized by WTP on page 67 8 2 The sample e business application Trade Trade3 is the third generation of the WebSphere end to end benchmark and performance sample application The new Trade3 benchmark has been re designed and developed to cover WebSphere s significantly expanding programming model and performance technologies This provides a real world workload enabling performance research and verification tests of WebSphere s implementation of J2EE 1 3 and Web Services including key WebSphere performance components and features Note You can download Trade3 s
190. ansaction and can accept the defaults in order to achieve an acceptable level of monitoring For specific transactions users can create unique policies that provide a finer level of control over the monitoring of those transactions An example would be the decision to enable subtransaction collection of all methods within WebSphere as opposed to the default of collecting only Servlet EJB JMS and JDBC 3 Instance and aggregated performance statistics Users have come to expect support for the collection of instance performance data This provides both additional metrics and a complete and exact trace of the path taken by a specific transaction The TMTP 5 1 ARM agent implementation was designed to provide an either or model where all Chapter 3 IBM TMTP architecture 69 70 statistics are collected as instance or aggregate regardless of the specific transaction being monitored Support is provided by TMTP Version 5 2 for collecting both instance and aggregate at the same time All ARM calls contain metrics regardless of the users request to store instance data This occurs because the application instrumentation is unaware of any configuration selections made at higher levels In the past the ARM agent when collecting aggregated data would normally discard the metric data provided to it This has been changed so that any ARM call that becomes the MAX for a given aggregation period will have its metrics stored and maintained This functio
191. any programming language The result is an extremely modular server architecture and a server easily managed and configured remotely using a number of different types of tools Impact on IT organizations The addition of tools requires adequate training in their use But the types of problems that these tools are going to uncover also require skills and organizational groups with IT operations For example gt The capability to handle more event types in the operation center Transaction availability events and performance events are typical of the new applications This requires that the operation center understand the impact of these events and the immediate action required to maintain the service in a service assurance oriented rather than network and system management oriented environment gt The capability to handle and analyze application problems or what appears to be application problems This requires that the competency groups in charge of finding permanent fixes understand the application architecture and are able to address the problems gt A stronger cooperation between QA and operations to make sure that the testing phase is a true preparation of the deployment phase and that recurring tests are made following changes and fixes Periodic tests to validate performance and capacity parameters are also good practice Chapter 1 Transaction management imperatives 9 While service assurance and real time root c
192. apache org Computer Measurement Group Web site http www cmg org Crystal Decisions home page http www crystaldecisions com IBM DB2 Technical Support All DB2 Version 7 FixPacks http www 3 ibm com cgi bin db2www data db2 udb winos2unix support v7fphis t d2w report IBM Patterns for e business http www ibm com developerWorks patterns IBM Redbooks Web site http www redbooks ibm com IBM support FTP site ftp ftp software ibm com software IBM Tivoli software support http www ibm com software sysmgmt products support IBM WebSphere Application Server Trade3 Application http www 3 ibm com software webservers appserv benchmark3 html Related publications 481 The Java Pet Store 1 3 Demo http java sun com features 2001 12 petstorel3 html Java Web site for JNI documents http java sun com products jdk 1 2 docs guide jni The Object Management Group http www omg org The Open Group http www opengroup org OpenGroup ARM Web site http www opengroup org management arm htm Tivoli IBM Tivoli Monitoring for Transaction Performance Version 5 2 manuals http publib boulder ibm com tividd td IBMTivol iMonitoringforTransactionPe rformance5 2 html How to get IBM Redbooks You can order hardcopy Redbooks as well as view download or search for Redbooks at the following Web site ibm com redbooks You can also download additional materials code samples or diskette CD ROM images from that site
193. arch GyFavorites meda yy Sp Si a Tivoli Monitoring for Transaction Performance User Name administrator http ibmtivaArade app 0 274 0 0020 1 827 9 2003 09 http ibmtiva itse austin ibrn com trade app lbo 1305405405405405 0 0010 1 162 37 2003 09 ve Page 1 All Times are in Seconds Query String Keys Limit 2 pem Bea b Apply Alt a Cancel Alt c z R 7 ERIE oi Z Work with Discovery Policies Choose Create Edit etc BE Local intranet Figure 8 42 Creating listening policies and selecting application transactions 4 From the View Discovered Transactions depicted in Figure 8 42 you select the specific transaction that you want to monitor Now perform the following a Make a selection for the URI or URI Pattern you want use to create listening policies b Select a maximum of two query strings for the listening policies if any are available for the particular URI Select Create Component Policy From in the action drop down list d Press Go and the Configure J2EE Listener dialog shown in Figure 8 43 on page 291 is displayed 290 End to End e business Transaction Management Made Easy B oli Monitoring for Transaction Performance oso ernet Explore E 0 x File Edit View Favorites Tools Help El Address is http Htivdee4 9082 tmtpUL jsp console WcFrameManager jsp 6o Bak gt Q A Qsearch Favorites Meda C4 S aaga Tivoli Moni
194. are that many of the home grown components may be promoted to standard status to ensure specific company standards or policies At first glance breaking up the e business application into many specialized services may be regarded as counterproductive and very expensive to implement However specialization enables sharing of common components such as Web application security and database servers between more e business application systems and it is key to ensuring availability and Chapter 1 Transaction management imperatives 13 14 performance of the application system as a whole by allowing for duplication and distribution of selected components to meet specific resource requirements or increase the performance of the application systems as a whole In addition this itemizing of the total solution allows for almost seamless adoption of new technologies for selected areas without exposing the total system to change Whether the components in the e business system are commercial standard or application specific each of them will most likely require other general services such as communication facilities storage space and processing power and the computers on which they run need electrical power shelter from rain and sun access security and perhaps even cooling As it turns out the e business application relies on several layers of services that may be provided internally or by external companies This is illustrated in Figur
195. art of the intra company network that the DMZ can talk to is the application tier Application Tier This is usually implemented as a dedicated part of the network where the application servers reside End user requests are routed from the DMZ to the specific servers in this tier where they are serviced In case the applications need to use resources from company wide databases for example these are requested from the back end tier where all the secured company IT assets reside As was the case for communication between the DMZ and the Chapter 1 Transaction management imperatives 21 22 Application Tier the communication between the Application Tier and the back end systems is established through firewalls and using well known connection ports This helps ensure that only known transactions from known machines outside the network can communicate with the company databases or legacy transaction systems such as CICS or IMS Apart from specific application servers this tier also hosts load balancing devices and other infrastructural components such as MQ Servers needed to implement a given application architecture Back end Tier This is where all the vital company resources and IT assets reside External access to these resources is only possible through the DMZ and the Application Tier This model architecture is a proven way to provide secure scalable high availability external access to company data with a minimum of exp
196. as ODBC system data sources The ETL programs provided with the IBM Tivoli Monitoring for Transaction Performance Enterprise Transaction Performance Warehouse Enablement Packs require specific logical names of the data sources to be used Table 10 2 shows the values to be used for each of the data sources Table 10 2 Source database names used by the TMTP ETLs Warehouse Enablement Pack Source database ETL source database name TMTP Version 5 2 WTP TMTP TMTP_DB_Src At the TEDW Control Center server using a DB2 command line window issue the following commands in case your source databases are implemented on DB2 RDBMS systems for each of the source databases db2 catalog tcpip node lt nodename gt remote lt hostname gt server lt db2_port gt db2 catalog database lt alias gt as lt database gt at node lt nodename gt ODBC db2 catalog system odbc data source lt alias gt Chapter 10 Historical reporting 393 Where lt nodename gt A logical name you assign to the remote DB2 server lt hostname gt The TCP IP host name of the remote DB2 server lt db2_port gt The TCP IP port used by DB2 default is 50000 lt alias gt The logical name assigned to the source database Use the values for the TMTP databases provided in Table 10 2 on page 393 lt database gt The name of the database as it is known at the DB2 server hosting the database The values are most likely TMTP for Management Server Note If the sou
197. at that the browser will be able to import The resulting file should have a p12 file extension Chapter 6 Keeping the transaction monitoring environment fit 179 The export will ask if you want to use strong or weak encryption Select weak encryption as your browser will only be able to work with weak encryption Now open your browser and select Tools Options Content we have only tried this with Internet Explorer version 6 x Press the Certificates button Import the exported p12 file into the personal certificates of the browser Now the following URL will tell you if SSL works between your machine and the Management Server using the certificate you imported above https managementservername 9446 tmtp servlet PingServlet If the Management Server works properly you should see the statistics window shown in Figure 6 2 in your browser Figure 6 2 Management Server ping output gt To restart the TMTP server log on to the WebSphere Application Server Administrative Console http WebSphere_server_hostname 9090 admin Go to the Applications Enterprise Applications menu on the right side of the window you can see the TMTPv5_2 application Select the check box next to it and press Stop and then the Start button on the top of the panel gt To stop and start the Store and Forward agent you have to restart the following services IBM Caching Proxy Tivoli TransPerf Service 180 End to
198. atabases access to messaging infrastructures security and possibly access to legacy systems Internet DMZ Intranet Typical Internet End User _ Typical e business application ommunication paths ccecce TMTP Communication paths se WebSphere 3 Load Application Pana Balancer HTTP Server I ti Server nvestigator TER e Management Agent J2EE Agent fs Management H Quality A i of Service le H Ga i i 5 Management Generic Management KA en a Windows Agent s t e Management KA Store Agent and net i oo EINEDE WebSphere 5s Fm cece Application C 1 E er Management Server Chained Agent Store H ena Store and Forward Management Forward e Agent J2EE See Management Agent Figure 3 10 Putting it all together Chapter 3 IBM TMTP architecture 81 82 In the design shown in Figure 3 10 on page 81 we have made the following placement decisions Management Server We have placed it in the intranet zone as this is the preferred and most secure location for the Management Server Store and Forward Management Agent We have used only one and placed it in the DMZ This will allow the Management Agents within the DMZ and on the Internet to securely communicate with the Management Server Many en
199. ation for the minimum and maximum instances of that node for the hour This report is only available from the aggregate view areri Filter Encod ing Filt O dof Events View es Iter Response Times View Web Health Console Thresholds View J iay Minimum Maximum View B JDBC 0 016 Figure 7 3 Node context reports Examining specific instances of a transaction can be enabled during the creation of the policy or can occur after a violation of a threshold on the root transaction Instance topologies are reached by choosing the instance radio button on the Aggregate View and the instance in the list and clicking the Apply button Node s status icons are set to the most severe threshold reached or compared to the average for the hour and if the time greatly exceeds the average a more severe threshold is set These comparisons to the average are sometimes called the interpreted status and are useful because they show the slow transactions helping pinpoint the cause of the problem Chapter 7 Real time reporting 217 Line chart from Topology View The line chart is viewed by choosing Response Times View from the Topology View By default this shows data for the chosen node from the past 24 hour period showing the behavior of the node over long periods of time Sig Board gt Transaction Topalogy gt Line Chart 9 Ey Average Min Max Range 4 5 R Aoa RIN A 3 0
200. ause analysis are attractive propositions the J2EE management market is not yet fully mature Combined with the current economic climate this means that a number of the solutions available today may disappear or be consolidated within stronger competitors tomorrow Beyond a selection based on pure technology and functional merits clients should consider the long term viability of the vendor before making a decision that will have such an impact on their infrastructure management strategies J2EE application architectures have and will continue to have a strong impact on managing the enterprise infrastructure As the future application model is based on a notion of service rather than a suite of discrete applications the future model of infrastructure management will be based on service assurance rather than event management An expanded set of parameters and a close integration within a real time operational model offering root cause analysis is necessary Recommendations The introduction of J2EE application servers in the enterprise infrastructure is having a profound impact on the way this infrastructure is managed Potential availability performance quality and security problems will be magnified by the capabilities of the application technology with consequences in the way problems are identified reported and corrected As J2EE technologies become mainstream the existing infrastructure management processes which are focused today m
201. ays INSTALL_FAILED then verify that you entered the correct info for your J2EE component If you think everything was entered correctly then open a defect on Instrument 188 End to End e business Transaction Management Made Easy gt Verify that the J2EE appserver is instrumented Verify that the following files directory structure exists Management Agent Common J2EE Behavior files lt MA_HOME gt app instrument appServers lt UUID gt BWM logs trace log Possible problem If this file does not exist then the application server has not been instrumented or the application server needs to be restarted for the instrumentation to take affect Possible solution Restart the appserver and access one of your instrumented applications that is an application that you have defined J2EE a policy for If the trace log still does not exist then verify you entered the correct information into the policy If you have entered the correct information and the trace file has not been created then you may have encountered a defect in which case you will need to log a PMR with IBM Tivoli Support gt Verify that your Listening Policy exists on Management Agent This step will verify that the Management Server sent the Management Agent your listening policy correctly in order for this section to work you will need to re enable access to the HTTP Adaptor of the MBeanServer on your Management Agent The procedure to do this is described
202. b ShoppingClientC ontrollerEJB_5nga4g_ELOImpl getShoppingCl Work with Discover Work with Listening Work with Playback Work with Schedule Work with Agent Gr Work with Transacti Work with Realms vReports View Big Board View General Repor View Component Ey vSystem Administra Work with Agents Configure System E Component Manage Configure User Sett Work with Event Re o 0 Average Min Max Range Sesh Is 0 0 View System Event 10 06 10 06 10 06 10 06 10 06 Wisse Am Eilas x 11 00 11 45 12 30 13 15 14 00 alll L gt gt gt L_L_L_ _ L_L__L_ _ _ _ SS_ SSS ES View Component Events fea Local intranet WA Figure 8 71 Response time for getShoppingClienFacade method 322 End to End e business Transaction Management Made Easy Finally the real time transaction performance total Round Trip Time and Back End Service Time of the Pet Store site as well as J2EE components response time are shown in Figure 8 72 IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer 5 x File Edit View Favorites Tools Help Tivoli Monitoring for Transaction Performance A J2EE WebLogici7 0 1 E E aos iy s A Servlet 7 0 21 o Al Roun Tip Time aif p 5 _ y oA 0 265 5 5 y E amp A ilter JDBC k 5 0 224 0 009 g E i Back End Service Time Page Render Time 7 0 022 0 132 z J
203. base and data mart database during the installation of Tivoli Enterprise Data Warehouse is accessible only to the user that performed the installation If you are installing the warehouse pack using the same database user that installed Tivoli Enterprise Data Warehouse or if your database user has access to another user temporary table space in the target databases no additional action is required If you do not know the user name that was used to install Tivoli Enterprise Data Warehouse you can determine whether the table space is accessible by attempting to declare a temporary table while connected to each database as the user that will install the warehouse pack The commands in Example 10 3 are one way to achieve this Example 10 3 How to connect TWH_CDW db2 connect to TWH_CDW user lt installing_user gt using lt password gt db2 declare global temporary table t1 cl char 1 with replace on commit preserve rows not logged db2 disconnect TWH_CDW db2 connect to TWH_MART user installing_user using password db2 declare global temporary table t1 cl char 1 with replace on commit preserve rows not logged db2 disconnect TWH_MART 386 End to End e business Transaction Management Made Easy Where installing_user Identifies the database user that will install the warehouse pack password Specifies the password for the installing user Installing the Warehouse Enablement Packs The IBM Tivoli Monitoring for Transaction Per
204. base connection pool used average 30 000000 Figure 5 5 Example for an IBM Tivoli Monitoring Profile 4 Distribute the profiles You can do this by either using the wdmdistrib command or the Tivoli desktop Tivoli Enterprise Console adapter By default all the Resource Models will send an event to the Tivoli Event Console event management environment whenever a threshold is violated These events may be used to trigger actions based on rules stored in the TEC Server Another possible way to send events to the TEC environment is directly from the WebSphere Application Server using the IBM WebSphere Application Server Tivoli Enterprise Console adapter This adapter is used to forward native WebSphere Application Server messages SeriousEvents to the Tivoli Enterprise Console These messages may have the following severity codes FATAL ERROR AUDIT WARNING TERMINATE YYYY Y The Tivoli Enterprise Console adapter is also self reporting you can see adapter status events in the WebSphere Application Server console Chapter 5 Interfaces to other management tools 167 A task is created during the installation of the product in the WebSphere Event Tasks TaskLibrary This task Configure_WebSphere_TEC_Adapter is used to configure the adapter Before executing this task make sure that the IBM WebSphere Administration Server is running Then you have to configure which messages you want to be forwarded to the Tivoli Enter
205. based Web interface that allows you to create reports from your aggregated enterprise wide data that is stored in various data marts The GUI can be customized for each user Different roles can be assigned to the users according to the tasks they have to fulfill and the reports they may look at The users see only those menus in their GUI which they can use according to their roles The Report Interface can be accessed with a normal Web browser from everywhere in the network We recommend using Internet Explorer Other Web browsers like Netscape will also work but might be slower To connect to your Report Interface start your Web browser and point it to the following URL http lt your_ri_server gt IBMConsole Where you lt your_ri_server gt should be replaced by the fully qualified host name of your Report server The server port is 80 by default If you chose another port during installation of Tivoli Presentation Services use the following syntax to start the Report Interface through a different port http lt your_ri_server gt lt your_port gt IBMConsole When you log in for the first time use the login superadmin and password password you should change this password immediately After the login you should see the Welcome page On the left hand side you will find the pane My Work with all tasks that you may perform To manually run a report complete the following steps 1 From the portfolio of the IBM Console sele
206. blems are located and corrected A successful upgrade will complete silently and a failed upgrade can stop with or without pop up error messages in the DB2 data warehouse center Always check the log files to confirm the upgrade status Run TMTP data mart ETL processes to extract and load newly upgraded data into the data mart database 392 End to End e business Transaction Management Made Easy 12 Update the user name and password for the Warehouse Sources and Targets in the DB2 Data Warehouse Center Note The BWM_TMTP_DATA_SOURCE must reflect the database where the TMTP Management Server uploads its data For details on how to update sources and targets see the Tivoli Enterprise Data Warehouse Installing and Configuring Guide Version 1 1 GC32 0744 Post installation steps After successful installation the following activities must be completed in order to make TEDW suit your particular environment 1 Creating an ODBC connection to the TMTP source databases 2 Defining user authority to the Warehouse sources and targets 3 Modifying the schema information 4 Customizing your TEDW environment Creating an ODBC connection to the TMTP source databases The TEDW Control Center server hosts all the ETLs This server needs to have access to the various databases accessed by the SQL scripts imbedded in the ETLs TEDW uses ODBC connections to access all databases so the TMTP source databases needs to be cataloged at the TEDW DB2 server
207. bmtiv bS Transaction Backend Service Time_3 bDi a 0 E BA E com ibm websphere samples trade web OrdersAlertFilter doF ilter javax serviet Backend Service Time_3 10 01 10 02 10 02 10 02 10 02 21 00 03 00 09 00 15 00 21 00 Time Year Month Day Hour Minute Start Time poo z poA p de 21 o Stop Time 2003 10 z 2 gt 21 x 0z Apply Alt a a La gt g Figure 8 49 Time used by servlet to perform Trade back end process The drill down can basically go on and on until we have reached the lowest level in the subtransaction hierarchy 8 7 3 Using topology reports Another way of looking at the performance and responsiveness of the Trade application is to look at the topology By drilling down into the QoS topology by means of transactions and subtransactions and using decomposing through relationships between parent and child transactions we can find the real end user response time as shown in Figure 8 50 on page 301 Because STI QoS and J2EE are ARM instrumented and parent child relationships are correlated we can also see these transactional relationships in the Topology View 300 End to End e business Transaction Management Made Easy 3 IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer I Fie Edit View Favorites Tools Help Il Back gt OA A Asearch GyFavorites media B 3 a a Address fis http tivdce4 9
208. bot in background Display script only Display menus and toolbars only Cancel Help Figure 9 31 GUI Playback Options Select the Playback tab and increase the Delay between commands to 2000 this will leave a two second delay between commands during the playback You can also increase the Delay between keystrokes to 100 if you want better visual control on the keys being pressed Click on OK when you are done and get back to the script The next time you select Animate in the Debug menu you will have more time to understand what the script is doing Chapter 9 Rational Robot and GenWin 355 356 If the machine used to record and debug the simulation is the same that will execute ensure that you set Delay between commands back to 100 and Delay between keystrokes back to 0 before playing back the script with TMTP Other than executing scripts to a specific line and running in Animation Mode you can also investigate variable values in the Variable window This window is not enabled by default to ensure that you see it you must select Variables in the View menu The Variable window will be displayed in the right lower corner of the Rational Robot window but can be moved around the main window and docked where you prefer The values you see in this window are updated at each step of script playback Other interesting items Other than those mentioned above Rational Robot includes a set of extra features that you migh
209. by user This report Figure 10 26 on page 412 shows the number of times a user has run an application or transaction during the time interval This shows which users are using the applications and how often they are using them Such information can be used to charge for application usage The users names are their user IDs to the operating system If more than one user logs on with the same user ID the user ID displayed in the graph may represent more than one user This report uses the BWM_Daily_Transaction_Node_Star_Schema Chapter 10 Historical reporting 411 Report Output Performance Execution Load by User DAILY 1065732268250 1400000 7 12000007 1000000 800000 600000 400000 200000 Administrator Invoking User ReportOutput f Figure 10 26 Performance Execution load by User Transaction availability This report Figure 10 27 on page 413 shows the availability of a transaction over time in bar chart form This report uses the BWM_Daily_Transaction_Node_Star_Schema 412 End to End e business Transaction Management Made Easy Report Ouiput Performance Transaction Availability DAILY 1065734912703 100 90 80 70 60 50 40 30 20 O Welcome _Manage Reports and Report Output oa Figure 10 27 Performance Transaction availability Daily 10 3 3 Create extreme case weekly and monthly reports The extreme case report type provided by TEDW is a one m
210. c heed E ripi gnogiacar yr j E piiwmgogacar m ipowe E ipwmgegaes j ip dewmgneginces 1 15 po ow 20000 iy Tma ww an Tmo Yaar Month Owy Hour Mite lt ie 20 oo Yaw Moeth Day How Minute SatTime 200 6 Awe fos wz atma 2039 8 ss fos os sonm hegi las ex oz Bop tre me Ds 3 os 4p aha Figure 7 5 STI Reports Clicking on any bar will decompose the bar into subsequent pieces that represent each STI subtransaction that make up the recording This allows a comparison of the performance of each subtransaction against its peers Clicking any decomposed bar will take the user to the Topology View for that hour for STI 7 6 General Reports The General Reports option provides an entry point into reporting without going through the Big Board This means that policies that are no longer active may have their data viewed It provides access to six types of report Overall Transactions over time A line chart of endpoint s data plotted over time Transactions with Subtransactions A stacked area graph of subtransactions Chapter 7 Real time reporting 219 compared against each other and their parent over time Slowest transactions A table providing the slowest root transactions in the system General Topology Provides topologies for all policies whether they are active or not Availability Graph The health of a Policy over time Page Analyzer Viewer Detailed breakdown of the STI trans
211. cal intranet zi 7 Figure 8 45 Assign a name for the J2EE listener 8 7 Transaction performance reporting Before presenting the various online reports available with IBM Tivoli Monitoring for Transaction Performance Version 5 2 using the data from the sample Trade application you should review the general description of online reporting in Chapter 7 Real time reporting on page 211 As a reminder you should remember that IBM Tivoli Monitoring for Transaction Performance Version 5 2 provides three types of reports gt Big boards gt General reports gt Components events When working with the online reports please keep the following in mind gt All the online reports are available from the home page of the TMTP Console Use the navigation pane on the left to go to Reports and select the main category of our interest Chapter 8 Measuring e business transaction response times 295 To view the recent topology view for a specific QoS or J2EE enabled policy go to the Big Board and click on the Topology icon of the transaction you are interested in To view the most recent data you can click on the Retrieve Latest Data icon the hard disk symbol in order to force the Management Agent to upload the latest data to the Management Server for storage in the TMTP database In the topology views you may change the filtering data type to Aggregate or Instance and Show subtransaction slower than To see a general report
212. ccount the number of times the method was called by that method Doing this provides an estimate of the amount of time spent in a node that was above its average This calculation provides an indication of abnormal behavior because it is slower than normal Other slow performing nodes will be marked with a yellow upside down triangle indicating a problem against the average for the hour by default 5 of the methods will have a marking Chapter 2 IBM Tivoli Monitoring for Transaction Performance in brief 47 Selecting the Timer doGet node and examining the inspector would show any metrics captured for the Servlet In this example the Servlet tracing is minimal and the following figure is what would be displayed by the inspector Figure 2 8 If greater tracing were specified the context metrics could provide information on SQL statements login information and so on some of the later chapters will demonstrate this depending on the type of node selected and the level of tracing configured in the listening policy f IBM Tivoli Monitoring for Transaction Performance 5 xj g com ibm tivoli ibuver servietprobe serviets Timer doGetijavax seriet http HttpServietRequest javax seriet http HttpSerietResponse Property Value com ibm tivoll buver servietprobe serviets Timer doGetiavax semiet http _Hitp Name ServietRequest javax servlet http HittpServietResponse Start Time 2003 08 25 16 27 14 Duration 6 004 Status Most Vio
213. ce data yet has relevant instance data should a transaction problem be recognized 3 3 Key technologies utilized by WTP 3 3 1 ARM This section describes some of the technologies used in this release of TMTP and elaborates on some of the changes introduced to how some previously implemented technologies are utilized The Application Response Measurement ARM API is the key technology utilized by TMTP to capture transaction performance information The ARM standard describes a common method for integrating enterprise applications as manageable entities It allows users to extend their enterprise management tools directly to applications creating a comprehensive end to end management capability that includes measuring application availability application performance application usage and end to end transaction response time The ARM API defines a small set of functions that can be used to instrument an application in order to identify the start and stop of important transactions TMTP provides an ARM engine in order to collect the data from ARM instrumented applications The ARM standard has been utilized by several releases of TMTP so it will not be discussed in great depth here If the reader wishes to explore ARM in detail the authors recommend the following Redbooks as well as the ARM standard documents maintained by the Open Source Group available at http www opengroup org gt Introducing Tivoli Application Performance Man
214. ces Copyright IBM Corp 2003 All rights reserved xix Trademarks The following terms are trademarks of the International Business Machines Corporation in the United States other countries or both AIX Lotus Tivoli Enterprise CICS Notes Tivoli Enterprise Console Database 2 PureCoverage Tivoli Management DB2 Purify Environment server Quantify Tivoli IBM Rational TME ibm com Redbooks WebSphere IMS Redbooks logo The following terms are trademarks of other companies Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both Java and all Java based trademarks and logos are trademarks or registered trademarks of Sun Microsystems Inc in the United States other countries or both UNIX is a registered trademark of The Open Group in the United States and other countries Other company product and service names may be trademarks or service marks of others XX End to End e business Transaction Management Made Easy Preface This IBM Redbook will help you install tailor and configure the new IBM Tivoli Monitoring for Transaction Performance Version 5 2 which will assist you in determining the business performance of your e business transactions in terms of responsiveness performance and availability The major enhancement in Version 5 2 is the addition of state of the art ind
215. ch means that the additional transaction decomposition can be turned on only when required It is important that this capability is available as though TMTP has low overheads all performance monitoring has some overhead the more monitoring you do the greater the overhead The fact that J2EE monitoring can be easily enabled and disabled based on a policy request from the user is a powerful feature Just In Time Instrumentation explained As discussed above one of the key changes introduced by this release of ITM for TP is the introduction of Just In Time Instrumentation hereafter referred to as JIT JITI builds on the performance listening capabilities provided in previous versions by the QoS component to allow detailed performance data to be collected for J2EE Java 2 Platform Enterprise Edition applications without requiring manual instrumentation of the application How it works With the release of JDK 1 2 Sun included a profiling mechanism within the JVM This mechanism provided an API that could be used to build profilers called JVMPI or Java Virtual Machine Profiling Interface The JVMPI is a bidirectional interface between a Java virtual machine and an in process profiler agent JITI uses the JVMPI and works with un instrumented applications The JVM can notify the profiler agent of various events corresponding to for example heap allocation thread start and so on Or the profiler agent can issue controls and requests for
216. change the certificates we have to extract them into arm files Start the IBM Key Management tool by executing the following command ikeyman sh We open the prodms jks file and press the Extract Certificate button Figure 4 17 on page 104 Chapter 4 TMTP WTP Version 5 2 installation and deployment 103 E4 IBM Key Management install keyfiles prodms jks Key Database File Create View Help DOSEER Key database information DB Type JKS database file File Name install keyfiles prodms jks Token Label Key database content Personal Certificates oi Receive prime E View Edit Export Import Recreate Request New Self Signed A personal certificate has its associated private key in the database Figure 4 17 Extract Certificate We extract the certificate into the prodms arm file Figure 4 18 x Data type Base64 encoded ASCII data v Certificate file name prodms arm Browse Location finstall keyfiles ok canei Figure 4 18 Extracting certificate from the msprod jks file Now we add the extracted certificate into the dmzagent jks file We open the prodagent jks file and select the Signer Certificate menu from the drop down menu and press on the Add button Figure 4 19 on page 105 104 End to End e business Transaction Management M
217. chedule Playback Policy from the schedule type Work with Schedules Create New Alt w Configure Schedule Discovery or Listening Policy petstare_j2ee_dis Start as soon as possible Run forever Stap Time Start as soon as possible Run forever Every 12 Minutes T I petstore_sti_sch r trade_dis_sch Start as soon as possible Run forever I trade_sti_sch Page 1 Start as soon as possible Run forever Every 10 Minutes drop down menu and press Create New This will bring you to the Configure Schedule Playback Schedule dialog shown in Figure 8 12 on page 250 where you specify the properties for the new schedule Chapter 8 Measuring e business transaction response times 249 File Edit view Favorites Tools Help Address a http f tivdce4 itsc austin ibm cor Go ay Tivoli Monitoring for Transaction Performance User Name administrator My Work Configuration Work with Discovery Policies Work with Listening Policies Work with Playback Policies Work with Schedules Work with Agent Groups Work with Transaction Recordings Work with Realms b Reports b System Administration gt Downloads Configure Schedule Playback Policy Name Description Start Time Start as soon as possible Start later at Year Month Da Hour Minute 2003 z 10 z 26 z E1 z 33 z Iteration Run Once Run
218. ciated which has been generated because the transaction is being monitored by one of the other TMTP components such as QoS STI J2EE instrumentation on another J2EE Application Server or Rational Genwin If no correlator exists when a transaction enters the J2EE Application Server the server Requests a correlator from ARM If no policy matches J2EE does not get a correlator Subtransactions can detect their parent correlator If no correlator performance data is not collected If correlator performance data is logged vvvvy In summary This version of TMTP uses parent based aggregation where subtransactions are chained together based on correlators allowing TMTP to generate the call stack transaction path The aggregation is policy based which means that information is only collected for transactions that match the defined policy Additionally TMTP will dynamically collect instance data as opposed to aggregated data based on threshold violations TMTP also allows child subtransactions to be ordered based on start times 3 3 2 J2EE instrumentation In this section we describe one of the key enhancements included with the release of TMTP Version 5 2 its ability to do J2EE monitoring at the subtransaction level without the use of manual instrumentation 72 End to End e business Transaction Management Made Easy The problem There are many applications written in J2EE that are hosted on various different J2EE application s
219. controlled by user configured policies that are created on the Management Server The process of creating appropriate J2EE discovery and listening policies is described in Chapter 8 Measuring e business transaction response times on page 225 The monitoring policy is then distributed to the Management Agent Which transactions to monitor are specified using edge definitions for example the first URI invoked when utilizing the application and it is possible to define the level of monitoring for each edge In order to monitor a J2EE Application Server the machine must be running the TMTP Agent A single TMTP agent can monitor multiple J2EE Application Servers on the Management Agent s host Chapter 3 IBM TMTP architecture 73 74 TMTP Version 5 2 provides J2EE monitoring for the following J2EE Application Servers gt WebSphere Application Server 4 0 3 Enterprise Edition and later gt BEA WebLogic 7 0 1 TMTP s J2EE monitoring is provided by Just In Time Instrumentation JITI JITI allows TMTP to manage J2EE applications that do not provide system management instrumentation by injecting probes at class load time that is no application source code is required or modified in order to perform monitoring This is a key differentiator between TMTP and other products which can require large changes to application source code Additionally the probes can easily be turned on and off as required This is an important difference whi
220. ct Work with Reports Manage Reports and Report Output 2 In the Manage Reports and Report Output dialog in the Reports view right click on a report icon and select Run from the context menu To schedule a report to run automatically when the associated data mart is updated complete the following steps 1 From the portfolio of the IBM Console select Work with Reports Manage Reports and Report Output 2 In the Manage Reports and Report Output dialog in the Reports view right click on a report icon and select Properties from the context menu 3 Click the Schedule option and enable the Run of the report when the data mart is built Chapter 10 Historical reporting 407 10 3 2 Sample TMTP Version 5 2 reports with data mart IBM Tivoli Monitoring for Transaction Performance Version 5 2 provides the BWM Transaction Performance data mart This data mart uses the following star schemas BWM_Hourly_Tranaction_Node_Star_Schema BWM_Daily_Tranaction_Node_Star_Schema BWM_Weekly_Tranaction_Node_Star_Schema BWM_Monthly_Tranaction_Node_Star_Schema vvvy The data mart provides the following pre packaged health check reports Response time by application Response time by host name Execution load by application Execution load by user Transaction availability YYYY Y all of which are explained in greater detail in the following sections Response time by application This report shows response times during the day for in
221. ction Performance Management Agent To continue click Next See the installation guide for detailed descriptions of the installation steps NOTE The installation program installs the required Java Virtual Machine InstallShield Next gt Cancel Figure 4 45 Management Agent installation welcome window 130 End to End e business Transaction Management Made Easy 5 We accept the license agreement and click on the Next button Figure 4 46 net Install Management Agent yy E oj x Part1 General Terms BY DOWNLOADING INSTALLING COPYING ACCESSING OR USING THE PROGRAM YOU AGREE TO THE TERMS OF THIS AGREEMENT IF YOU ARE ACCEPTING THESE TERMS ON BEHALF OF ANOTHER PERSON OR A COMPANY OR OTHER LEGAL ENTITY YOU REPRESENT AND WARRANT THAT YOU HAVE FULL AUTHORITY TO BIND THAT PERSON COMPANY OR LEGAL ENTITY TO THESE TERMS IF YOU DO NOT AGREE TO THESE TERMS DO NOT DOWNLOAD INSTALL COPY ACCESS OR USE THE PROGRAM AND PROMPTLY RETURN THE PROGRAM AND PROOF OF ENTITLEMENT TO THE PARTY FROM WHOM YOU ACQUIRED IT TO OBTAIN A REFUND OF THE AMOUNT YOU PAID IF YOU DOWNLOADED THE PROGRAM CONTACT THE PARTY FROM WHOM YOU ACQUIRED IT El ept the terms in the license agreeme Ido not accept the terms in the license agreement InstallShield Back Next gt Cancel N Figure 4 46 License agreement window gt We leave the default location for the Management Agent target directory Clic
222. d text box remove the following entries lt MA gt app instrument lib jiti jar lt MA gt app instrument lib bootic jar lt MA gt app instrument ic config lt MA gt app instrument appServers lt n gt config Chapter 6 Keeping the transaction monitoring environment fit 197 198 lt MA gt app instrument lib jiti jar lt MA gt app instrument lib bootic jar lt MA gt app instrument ic config lt MA gt app instrument appServers lt n gt config where lt MA gt represents the root directory where the TMTP Version 5 2 Management Agent has been installed and lt n gt will be a random number 4 Click the OK button which will close the Advanced JVM Settings window 5 Back in the main WebSphere Advanced Administrative Console window click the Apply button The administrative node on which the instrumented application server is installed must be shut down so that the TMTP files that have been installed under the WebSphere Application Server directory may be removed On the WebSphere Administrative Domain tree on the left select the node on which the instrumented application server is installed Right click on the node and select Stop Warning This will stop all application servers running on that node After the administrative node is stopped remove the following nine files from the directory lt WAS_HOME gt AppServer lib ext where lt WAS_HOME gt is the home directory where WebSph
223. d control the monitoring of the transaction across all of the systems where it executes To that end monitoring policies are generic in nature and can be associated with any group of transactions gt Cross system correlation One of the largest challenges in providing distributed Transaction Performance monitoring is the collection of subtransaction data across a range of systems for a specified transaction To that end TMTP uses an ARM correlator in order to correlate parent and child transactions All of the Web Transaction Performance components of ITM for TP share a common infrastructure based on the IBM WebSphere Application Server Version 5 0 1 The first major component of Web Transaction Performance is the central Management Server and its database The Management Server governs all activities in the Web Transaction Performance environment and controls the repository in which all objects and data related to Web Transaction Performance activity and use are stored The other major component is the Management Agent The Management Agent provides the underlying communications mechanism and can have additional functionality implemented on to it The following four broad functions may be implemented on a Management Agent gt Discovery Enables automatic identification of incoming Web transactions that may need to be monitored Chapter 3 IBM TMTP architecture 57 gt Listening Provides two components that can listen to r
224. d in Figure 7 9 General Reports gt Page Analyzer Viewer Report hit Figure 7 9 Page Analyzer Viewer The initial view of the Page Analyzer Viewer report provides a table that lists all of the Web pages visited during the specified playback The table columns contains the following information gt Page displays the URL of the visited Web page gt Time displays the total amount of time that it took to retrieve the page and render it on a Web browser gt Size displays the number of bytes required to load the page gt Time Stamp displays the time at which the page was visited With the Page Analyzer Viewer you may also view page specific information to examine all of the activities and subdocuments of a visited Web page click the name of the page in the table A sequence of one or more bars is displayed in the right hand pane The bars indicate the following information gt Bar sequence corresponds to the sequence of activities on the Web page gt Overlapping bars indicate that activities run concurrently Chapter 7 Real time reporting 223 gt Bar length indicates the time required for the Web page to load gt The length of individual colored bar segments indicates the time required for individual subdocuments to load More detailed information about Web page activities and subdocuments can be accessed by right clicking on a line in the chart U
225. d layer it is valuable to understand how a single failure may cause problems in related components For example a router being down could cause database clients to generate errors if they cannot access the database server The integration to Business Information Services is a very important aspect as it provides an insight into how a component failure may be affecting the business as a whole When the router failure mentioned above occurs it is important to understand exactly what line of business applications will be affected and how to reduce the impact of that failure on the business Chapter 1 Transaction management imperatives 31 1 5 Managing e business applications As we have seen managing e business applications requires that basic services such as communications messaging database and application hosting are functional and well behaved This should be ensured by careful management of the infrastructural components using Tivoli tools to facilitate monitoring event forwarding automation console services and business impact visualization However ensuring the availability and performance of the application infrastructure is not always enough Web based applications are implemented in order to attract business from customers and business partners who we may or may not know Depending on the nature of the data provided by the application company policies for security and access control as well as access to and use of specific ap
226. d violations of a given transaction Once a transaction is defined to be measured by the ARM Engine it can also be defined to be monitored for threshold violations A threshold violation is defined in this release of this component to be completing the transaction i e arm_stop and having a unsuccessful return code or having a duration greater than a MAX threshold or less than a MIN threshold The ARM Engine will also communicate with the Monitoring Engine to inform it of transaction violations new edge transactions appearing and edge transaction status changes ARM correlation ARM correlation is the method by which parent transactions are mapped to their respective child transactions across multiple processes and multiple servers This release of the TMTP WTP component provides far greater automatic support for the ARM correlator Each of the components of WTP is automatically ARM instrumented and will generate a correlator The initial root parent or edge transaction will be the only transaction that does not have a parent correlator From there WTP can automatically connect parent correlators with child correlators in order to trace the path of a distributed transaction through the infrastructure and provides the mechanisms to easily visualize this via the topology views This is a great step forward from previous versions of TMTP where it was possible to generate the correlator but the visualization was not an automatic process a
227. d window Show Enabled Policies Show Disabled Policies E Work with Agent Groups Edit delete etc Figure 8 22 Work with discovery policies GE Local intranet To create a new policy you should perform the following steps 1 Select the QoS type of discovery policy and click Create New which will bring up the Configure QoS Listener dialog shown in Figure 8 23 on page 268 Chapter 8 Measuring e business transaction response times 267 268 B oli Monitoring for Transaction Performance oso ernet Explo ey Sic x Fie Edt View Favorites Tools Help a Heak gt A A Bsearch RyFavorites media Gy S St a Address a http tivdce4 9082 tmtput ispiconsole wcFramemanager sp dG U ay Tivoli Monitoring for Transaction Performance User Name administrator Feo eE Configure QoS Listener eee ve URI Filter ork with Discovery Policies tp nrade n Work with Listening Policies Hipa Work with Playback Policies Advanced Settings Work with Schedules nt Group Data Filter Work with Agent Groups sign Name Work with Transaction Recor Work with Realms eports ystem Administration ownloads Sample Rate 100 Percent Number of Samples 5 of lt Back Alt h URE Finish At Cancel Alt c zi Work with J2EE Listening Policies Choose Create Edit etc R E Local intranet Z Figure 8 23 Configure QoS discovery polic
228. d working with the Web Health Console refer to the IBM Tivoli Monitoring User s Guide V5 1 1 SH19 4569 5 2 Configuration of TEC to work with TMTP Follow these steps to configure TMTP to forward events to TEC 1 Navigate to the MS config directory Chapter 5 Interfaces to other management tools 171 2 Locate the eif conf file In the eif conf file define the TEC server by setting the ServerLocation property to the name of the Management Server see Example 5 1 Example 5 1 Configure TEC The ServerLocation keyword is optional and not used when the TransportList keyword is specified Note The ServerLocation keyword defines the path and name of the file for logging events instead of the event server when used with the TestMode keyword Hae EE E EA EEE EEA EE EE EE EE AARAA EE EEEE EEEEEEEEEREHEEEEH NOTE SET THE VALUE BELOW AS SHOWN IN THIS EXAMPLE TO CONFIGURE TEC EVENTS Example ServerLocation marx tivlab austin ibm com ServerLocation lt your_fully_qualified_host_name_goes_ here gt Hedd te E E EH A AAA AAAA AA AARAA a a a a a a a a ee a a a a a a a ServerPort number Specifies the port number on a non TME adapter only on which the event server listens for events Set this keyword value to zero 0 the default value unless the portmapper is not available on the event server which is the case if the event server is running on Microsoft Windows or the event server is a Tivoli Avai
229. de availability thresholds the topology has interpreted status icons for subtransactions that might be behaving poorly This is especially true when looking at instance topology where the user can compare subtransaction times to the average for the hour to help determine under performing transactions 212 End to End e business Transaction Management Made Easy Other changes which users experienced with previous versions need to be aware of are gt The STI graph bar chart is now based off of hourly data instead of instance data For a policy running every 15 minutes that means only one bar per hour Drilling down into the STI data for the hour s topology shows a drop down list of each instance gt QoS graphs are hourly now instead of the former one minute aggregates gt While not a reporting limitation data is only rolled up to the server every hour causing the graphs to not update as quickly as before However a user can force an update by selecting the Retrieve Latest Data The behavior of this function is explained in further detail in the following sections gt Page Analyzer Viewer is no longer linked from the STI event view Page Analyzer Viewer data is only accessible through the Page Analyzer Viewer report where you choose an STI policy Management Agent and time gt There is no equivalent to the QoS report with all the hits to the QoS system in one minute However if the collection of instance data is turn
230. de Easy 4 1 Custom installation of the Management Server As explained in the scenario description we have three zones in our customers environment as shown in Figure 4 1 Internet DMZ Intranet Quality Synthetic Transaction Investigator ee Management Agent 4 Management Agent of WebSphere Service HTTP Management Agent Edge Server Server Management Agent WebSphere Application Server Management Agent J2EE HTTP Plugin Management Server Generic tee IBMTIV4 Windows js AIX Store ant Management al Agent Forward 7 WebSphere i a a Management Application C gt D Chained a Server i rre astor ang Forward CANBERRA Management an Agent J2EE Forward e business application ommunication paths FRANKFURT TMTP Communication paths Figure 4 1 Customer production environment 1 The first zone where the Management Server and the WebSphere Application Servers are is the intranet zone The host name of the Management Server is ibmtiv4 The second zone is the DMZ where the HTTP servers and the WebSphere Edge server are located In this zone we will deploy a Store and Forward agent and Management Agents on the rest of the servers The host name of the Store and Forward agent in this zone is canberra
231. ditional Information The output produced by this tracing writes to the WebSphere log files found in lt WebSphere_Install_Dir gt WebSphere AppServer logs lt server_name gt where lt WebSphere_Install_Dir gt is the name of the WebSphere Installation Directory and lt server_name gt is the name of the server Perform one of the following actions to complete the procedure Restart WebSphere Application Services Restart the IBM Tivoli Monitoring for Transaction Performance from the WebSphere administration console Chapter 5 Interfaces to other management tools 175 5 2 3 Setting SMTP Set SMTP by following these steps 1 Open the lt MS_Install_Dir gt config directory where lt MS_Install_Dir gt is the name of the Management Server directory 2 Open the tmtp properties property file 3 Modify the SMTPServerLocation key with the fully qualified SMTP server host name Additional Information The host name is combined with the domain name for example my_hostname austin iobm com Optional Modify the SMTPProxyHost key to specify a fully qualified proxy server host name Optional Modify the SMTPProxyPort key to specify a port number other than the default value Optional Modify the SMTPDebugMode key to enable debug tracing in the classes found in the mail jar file when the value is set to true Additional Information Trace information can help resolve problems with e mail Perform one of the followi
232. dividual applications Application response time is the average of the response times for all transactions defined within that application The response time measurement unit is in seconds This report uses the BWM_Daily_Transaction_Node_Star_Schema The categories shown in the Response Time by Application report in Figure 10 23 on page 409 are labeled J2EE Vendor J2EE Version J2EE Server Name Probe name The actual values for this report are N A N A STI N A N A GenWin N AN A N A WebSphere5 0 server1 N A N A N A QOS ORNO N 408 End to End e business Transaction Management Made Easy b gt 4 i jg Ay PAN Report Output Performance Response Time by Application DAILY 1065732867609 pA 4 J2EE Vendor J2EE Version J2EE Server Name Probe Name Welcome Manage Reports and Report Output Report Output Figure 10 23 Response time by Application Response time by host name This report shows response times during the day for individual IP hosts The complete host name appears as hostname domain Each host can be a single user machine or a multi user server The response time measurement unit is seconds The report is based on the BWM_Daily_Transaction_Node_Star_Schema The categories shown in the Response Time by Hostname report in Figure 10 24 on page 410 are labeled Transaction Host Name Probe Host Name The actual values for this report are tmtpma xp itsc austi
233. e User Name administrator gt Configuration Work with Agents b Reports System Administration Work with Agents 2 Deploy Quality of Service Component Go Alt g Configure System Event Details Component Management Configure User Settings Work with Event Responses Generic Windows I Jibmtiva Online w32 ixBt View System Events I tivdced itse austin ibm com Online w2 ix View Log Files i A installed Online W32 ix8t View Management Server Details 4 L L gt Downloads Page 1 Show All Agents Show Online Agents C Show Offline Agents BE i O y of Configure System Event Details Edit etc E Local intranet A Figure 8 18 Work with agents QoS 2 Select the target to which QoS is to be deployed and select the Deploy Quality of Service component from the action selection drop down menu at the top of the Work with Agents dialog Click Go to go to the configuration of the new Quality of Service component Chapter 8 Measuring e business transaction response times 259 260 Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer loj x Edit View Favorites Tools Hel gt Address a http ftivdces 9082 tmtpUL jisp console WcFrameManager jsp 60 Ea Monitoring for Transaction Performance ne administrator TEC Deploy Components andlor Monitoring Component al eee Management Agent Name tivlab01 tem Administra
234. e 1 Show All Agents Show Online Agents Show Offline Agents DKS O Ml I MMMM gt View Management Server Details GE Local intranet 7 Figure 8 20 Work with Agents QoS installed 8 5 2 Creating discovery policies for QoS The purpose of the QoS discovery policy is to gather information about the URIs that are handled by the QoS Agent As is the case for STI Agents the URIs have to be discovered before monitoring policies can be defined and deployed The Quality of Service discovery policy returns URIs only from Management Agents on which a Quality of Service listener is deployed Note Please remember that specific discovery policies has to be created for each type of agent QoS J2EE and STI Before setting up any policies for a QoS Agent it is important to understand the concept of virtual servers The term virtual server refers to the practice of maintaining more than one server on one machine These Web servers may be differentiated by IP host name and or port number Chapter 8 Measuring e business transaction response times 261 QoS and virtual servers Even though the GUI for QoS configuration does not allow for defining multiple origin server virtual server pairs there is a way to use one QoS machine to measure requests for several back end Web servers The advantage to this setup is that only one machine is used to measure the transactions response times of a number of machines that do real work
235. e 1 3 Solution Solution Solution Solution Client I Client Il Server Il Server 3 Networking Subsystem Client Services Subsystem Server Services Services Server Operating Services Client Operating Services Environmental Services Figure 1 3 Layers of service As a matter of fact it is not exactly the e business application that relies on the services depicted above The correct notion is that individual components such as Web servers database servers application servers lines routers hubs and switches each rely on underlying services provided by some other component This can be broken down even further but that is beyond this discussion The point is that the e business solution is exactly as solid robust and stable as the weakest link of the chain of services that make up the entire solution and since the bottom line results of an enterprise may be affected drastically by the quality of the e business solutions provided a worst case scenario may prove that a power failure in Hong Kong may have an impact on sales figures in Greece and that increased surface activity on the sun may result in satellite communication problems that prevent car rental in Chattanooga While mankind cannot prevent increased activity of the sun and wind there are a number of technologies available to allow for continuing centralized monitoring End t
236. e 388 Click Next Chapter 10 Historical reporting 387 amp Tivoli Enterprise Data Warehouse Installation o AmE Welcome to the InstallShield Wizard for Tivoli Enterprise Data Warehouse The InstallShield Wizard will install Tivoli Enterprise Data Warehouse on your computer To continue click Next Tivoli Enterprise Data Warehouse IBM httovwww ibrn com InstallShield Next gt Cancel Figure 10 5 TEDW installation 4 The dialog for the type of installation see Figure 10 6 appears Select Application installation only and the directory name where the TEDW components are installed We used C TWH Click Next to continue amp Tivoli Enterprise Data Warehouse Installation Choose the setup type that best suits your needs install application extract transform and load ETL and reporting packages Directory name caw Tivoli Browse InstallShield lt Back Next gt Cancel Figure 10 6 TEDW installation type 5 The host name dialog appears as shown in Figure 10 6 Verify that this is the correct host name for the TEDW Control Center server Click Next 6 The local system DB2 configuration dialog is displayed It should be similar to what is shown in Figure 10 7 on page 389 The installation process asks for a 388 End to End e business Transaction Management Made Easy valid DB2 user ID Enter the valid DB2 user ID and password that were created during the DB2 installation on you
237. e Application 2t Sian in E el eA E I fax Local intranet ZA Figure 8 57 Pet Store application welcome page The Pet Store application uses a PointBase database for storing data It will populate all demonstration data automatically when an application is run for the first time Once installed you can log in to Weblogic Administration console see Figure 8 58 on page 310 to see details for the Pet Store application components and configuration Chapter 8 Measuring e business transaction response times 309 3 WebLogic Server Console Microsoft Internet Explorer File Edit View Favorites Tools Help Console a petstore 8 Sserers petstoreServer 2 clusters B machines Newa Channels A Deployments E Glapplications a B petstore asyncSenderEjb cartEjb tatalogEjb customerEjb petstore petstoreEjb signonEjb yidgenEjb petstoreadmin Prpetstoreope petstoresupplier eJ Sl web Applications E Web Service Components Connectors El startup amp Shutdown amp Osenices Ecom a Buse connection Pools El muttiPools a Data Caureae E Connected to tivlab01 itsc austin ibm com 7001 petstore gt Applications Active Domain petstore B Configure a new Application Customize this view Nme pn i arp ee T A a F pte eorgesenaieoaoasonposoweor 8 t 4 T Applet started Figure 8 58 Weblogic 7 0 1 Admin Console
238. e Java Enabler you will need to enable any JVM you add to the system and need to use You can set up the Java Enabler by selecting the Java Enabler setup icon which you can find by selecting Start Rational Software Rational Test program group After selecting the Java Enabler icon the setup starts and a dialog with a selection of Java Enabler Types is displayed see Figure 9 17 on page 336 Chapter 9 Rational Robot and GenWin 335 Rational Test Enabler for Java JavaEnabler Types Le Please select the type of JavaEnabling you want Project lt Not Yet Selected gt Quick This method only searches existing Java Environments in the registry for enabling Complete This method searches all the system drives for java environments to enable NOTE this process can take a few minutes Web Update Check the web for the latest JavaEnabler Special Java Proxies Enable proxies stored in the Rational project w efe e InstallShield Figure 9 17 Configuring the Rational Robot Java Enabler Select the Quick setup method to enable Rational Robot for the JVM in use If you have multiple JVMs and want to be sure that you enable all of them for Rational Robot you can instead select Complete and this will perform a full scan of your hard drive for all installed JVMs After selecting Quick a dialog will be displayed with the JVMs found on the system see Figure 9 18 on page 337 From this list you should sel
239. e action 13 31 168 correlate 168 correlating data 376 correlation 66 225 376 engine 31 Cost Management 17 counters 157 create bufferpool 91 database 91 datastore 448 depot directory 89 discovery policy 261 266 file system 88 listening policies 287 listening policy 271 new user 143 Playback policy 251 369 realm 255 creating reports 407 Crystal Decisions 377 Crystal Reports 418 current data 60 custom registry 79 CWM See Common Warehouse Metadata D data aggregate 66 aggregated 60 214 correlating 376 event 214 extract 378 484 End to End e business Transaction Management Made Easy gathering 34 historical 379 392 histrorical 376 management 378 measurement 377 persistence 62 reference 33 data aggregation 376 data analysis 379 data gathering 382 data mart 191 377 379 406 format 379 data mart database 381 data mart ETL 379 381 data mining 379 data source 378 393 ODBC 419 data target 378 data warehouse 379 database central warehouse 380 data mart 381 warehouse source 380 datastore create 448 DB2 112 fenced 144 instance 145 user 146 DB2 instance 64 bit 208 db2admin 143 db2start 178 db2stop 178 dbtmtp 113 debug 354 demilitarized zone 21 24 demilitarized zone DMZ 82 deploying GenWin 365 J2EE component 278 TMTP components 239 310 details policy 214 dimension tables 381 dimensions common 376 discovery policy 228 239 create 261 266 discovery task 160 DMLinkJre 156 DNS 118 dupl
240. e groups interested in the different phases of a business process and in its successful completion gt The application groups with an interest in the quality of the different logical components of the global application gt The IT operations group providing infrastructure service assurance and interested in monitoring and maintaining the services through the application and its supporting infrastructure People looking for a J2EE management solution must make sure that any product they select does along with other enterprise specific requirements provide the data suited to these multiple reporting needs Application management represents around 24 of the infrastructure performance management market But the new application architecture enabled by J2EE goes beyond application management The introduction of this new application architecture has the potential not only to impact the application management market but also directly or indirectly to disrupt the whole infrastructure performance market by forcing a change in the way enterprises implement infrastructure management The role of J2EE application architectures goes beyond a simple alternative to traditional transactional application It has the potential to link applications and services residing on multiple platforms external or internal in a static or dynamic loosely coupled relationship that models a business process much more closely than any other application did It is also a
241. e have to use a gskit5 tool provided with the WebSphere Application Server in installable format First we need to install it The installation files are located under WebSphereRoot gskit5install in our case it is usr WebSphere AppServer gskit5install We execute the installation with the following command gskit sh The product gets installed to the usr opt ipm gskkm directory The executable are located in the usr opt ibm gskkm bin directory We start the utility with the following command gsk5ikm We select the New option from the Key Database File menu as in Figure 4 10 on page 99 98 End to End e business Transaction Management Made Easy fa IBM Key Management Figure 4 10 GSkKit new KDB file creation We select the CMS Key Database file from the menu The file name will be prodsnf kdb see Figure 4 11 eS ee ed prodsnfkdb Browse C ee Figure 4 11 CMS key database file creation We set the password and select the Stash the password to a file option The stash file name will be prodsnf sth see Figure 4 12 on page 100 Chapter 4 TMTP WTP Version 5 2 installation and deployment 99 E4 Password Prompt Figure 4 12 Password setup for the prodsnf kdb Now we create a New self signed certificate see Figure 4 13 E4 IBM Key Management install keyfiles prodsnf kdb oo Le Personal Cermmentes _ _ _ _ 7I men Figure 4 13 New
242. e in Seconds Query String Keys Limit 2 Apply Alt a Cancel Alt c Figure 8 28 View discovered transaction of trade application 4 From the View Discovered Transactions dialog select the transaction that will be the basis for the listening policy a Select a transaction b Select Create Component Policy From in the function drop down menu at the top of the transaction list c Click Go This will take you to the Configure QoS Listener dialog shown in Figure 8 29 on page 274 Chapter 8 Measuring e business transaction response times 273 File Edit View Favorites Tools Help Address Tivoli Monitoring for Transaction Performance User Name administrator My Work Configuration Configure QoS Listener Work with Discovery Policies Work with Listening Policies ee All requests from IP address Work with Playback Policies i i Add Altew Remove Work with Schedules Config 5 Work with Agent Groups Work with Transaction Recordings Work with Realms b Reports b System Administration gt Downloads All pages with URI http VVibmtiv9 itsc austin ibm com 82VtradeV Data Filter Sample Rate 100 Percent C Number of Samples 5 Write on Disk Aggregate Data Only 5 Instances collected after failure C Aggregate and Instance gt lt Back Alt b Next Alt n gt Finish Ait Cancel Alt c Figure 8 29 Configure QoS set data filter write data 5
243. e of a transaction during a given one hour period Correlation is the process of tracking hierarchical relationships among transactions and associating transactions with their nested subtransactions When you know the parent child relationships among transactions and the response times for each transaction you are much better able to determine which transactions are delaying other transactions You can then take steps to improve the response times of services or transactions that contribute the most to slow performance gt Instance and aggregate data collection When a policy collects performance data the collected data is written to disk Because Management Agents are equipped with ARM functionality you can specify that aggregate data only be written to disk to conserve system resources and view fewer data points or that both aggregate and instance data be written to disk Aggregate data is an average of all response times detected by a policy over a one hour period whereas instance data consists of response times that are collected every time the transaction is detected TMTP will normally collect only aggregate data unless instance data collection was specified in the listening policy End to End e business Transaction Management Made Easy TMTP will also automatically collect instance data if a transaction breaches specified thresholds This second feature of TMTP is very useful as it means that TMTP does not have to keep redundant instan
244. e pattern This is what we deem discovery mode because in this situation we will be discovering all the edges that match the specified edge pattern When in discovery mode TMTP always generates a correlator with the TMTP_Flags ignore flag set to true to signal that we do not want to process subtransactions For all non edge aggregation we will be performing correlated aggregation What this means is each transaction instance will be directed to a specific aggregator based upon correlation using the following four properties 1 Origin host UUID 2 Root transID 3 Parent transID 4 Transaction classID Chapter 3 IBM TMTP architecture 71 By providing this correlation information in the aggregation you are better able to see the aggregation information in respect to the code flow of the transactions that have run Every hour on the hour this information will be sent to an outboard file for upload to the Management Server Database How are correlators passed from one component to the next Each component of TMTP passes the correlator it has generated to each of its subtransactions using Java RMI over IIOP Java RMI over IIOP combines Java Remote Method Invocation RMI technology with Internet Inter Orb Protocol IIOP CORBA technology and allows developers to pass any serialized Java object Objects By Value between application components Transactions entering the J2EE Application Server may already have a correlator asso
245. e system It shows hourly averages of the transactions called aggregates for each policy with options to see specific instances for that hour if enabled in the policy Each box shown in Figure 7 2 on page 216 represents a node and also provides a flyover with the specific transaction name and further data about the transaction Chapter 7 Real time reporting 215 Year Month Day Hour Owe pae Ie Fes No Instances Found Show sabtransectons slower thar foo Figure 7 2 Topology Report The Topology Report can provide topologies for any application data though the J2EE topologies have the most subtransactions Data within the Topology Report is grouped into four or more types of nested boxes gt Hosts Applications Types Transactions Yv y If the nodes group has had a violation then there will be a color coded status icon that indicates the severity of the violation From within the Topology Report five additional views are available via a right click menu as shown in Figure 7 3 on page 217 Event View A table of the policy events for that hour End to End e business Transaction Management Made Easy Response Time View An hourly averages over time line chart for the chosen node Web Health Console Launch the ITM Web Health console for the endpoint Thresholds View View and create a threshold for the chosen node s transaction name Min Max View View a table of metric values context inform
246. e the IBM Tivoli Monitoring Web Health Console to display check and analyze the status and health of any endpoint where monitoring has been activated by distributing profiles with Resource Models The endpoint status reflects the state of the endpoint displayed on the Web Health Console such as running or stopped Health is a numeric value determined by Resource Model settings The typical settings include required occurrences cycle times thresholds and parameters for indications These are defined when the resource model is created You can also use the Web Health Console to work with real time or historical data from an endpoint that is logged to the IBM Tivoli Monitoring database You can connect the Web Health Console to any Tivoli management region server or managed node and configure it to monitor any or all of the endpoints that are found in that region The Web Health Console does not have to be within the region itself although it may To connect to the Web Health Console you need access to the server on which the Web Health Console server is installed and the Tivoli Management Region on which you want to monitor the Health Console All user management and security is handled through the Tivoli management environment This includes creating users and password as well as assigning authority To activate the online monitoring of the health of a resource you have to log in to the Web Health Console This may be achieved by performing
247. e this Store and Forward agent is in the DMZ Chapter 4 TMTP WTP Version 5 2 installation and deployment 121 m Install Store and Forward Agent Configuration of Proxy Host and Mask The management server is the target host of the Store and Forward Agent This agent becomes a proxy for the management server Type the URL in the form http s lt hostname lt port number You can create a protective mask that specifies a set of management agents that can use the proxy host Use IP addresses to identify each management agent The following example shows a mask that enable access for two IP addresses Mask ALL ip_address ip_address Proxy URL https ibmtiv4 itsc austin ipm com 9446 Mask er InstallShield Next gt i Cancel Figure 4 37 Configuration of Proxy host and mask window As the Management Server has security enabled we have to specify the protocol as https and the connection port as 9446 The complete URL will be the following https ibmtiv4 itsc austin ibm com 9446 In the Mask field we can specify the IP addresses of the computers permitted to access the Management Server through the Store and Forward agent We choose the option which lets all Management Agents connect to this Store and Forward agent in this zone 6 In Figure 4 38 on page 123 we specify the SSL Key Database and its password stash file This is required for the installation of the WebSphere Caching proxy
248. e unchecked the Enable SSL option and left the port settings as the default So the port for the non SSL agents will be 9081 and the port for the Management Server Console is set to 9082 see Figure 4 55 on page 141 140 End to End e business Transaction Management Made Easy Install the Management Server SSL Enablement for Management Server Communication Deselect the Enable SSL check box and click Next if you do not want to enable SSL To enable SSL select the Enable SSL check box and type the required information in the text boxes Enable SSL Key File Name Key File Password Trust File Name Trust File Password Port for non SSL agents i081 Port for SSL agents paag Port for the management server Bos2 Console InstallShield lt Back Next gt Cancel Figure 4 55 SSL enablement window gt At the WebSphere Configuration window Figure 4 56 on page 142 we specify the root as the user ID which can run the WebSphere Application Server We leave the admin console port on 9090 Chapter 4 TMTP WTP Version 5 2 installation and deployment 141 A 1 eR Tivoli software spi Dame y Lee ee Figure 4 56 WebSphere Configuration window gt We select the Install DB2 option from the Database Options window Figure 4 57 on page 143 142 End to End e business Transaction Management Made Easy i Install the Management Server BRE Database Options Use an existing Orac
249. e_lis b Configuration Management Agent ibmtiv vReports 3 Transaction http VVibmtiv9 itsc austin iom comVtradeVapp View Big Board View General Reports 2 G View Component Events b System Administration b Downloads 0 19 Average od Min Max Range Threshold seconds a O 0 0 N 10 07 10 07 10 07 10 07 10 07 14 00 14 15 14 30 14 45 15 00 Time Year Month Day Hour Minute E o S S Local intranet Figure 8 53 Response time view of Trade application relative to threshold Figure 8 53 shows the overall Trade application response time relative to the defined threshold instead of the absolute times shown in Figure 8 52 on page 303 When drilling down into the Trade application response times shown in Figure 8 53 we see the response times form the getMarketSummery EJB see Figure 8 54 on page 305 End to End e business Transaction Management Made Easy E IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer File Edit View Favorites Tools Help z i an Ea epak gt E Gsearch Favorites EHmeda A Ar SI a f Address a http tivdce4 9082 tmtpUL jsp console WcFrameManager isp v Go Links 2 Tivoli Monitoring for Transaction Performance User Name administrator Policy trade_2_stockcheck_tivlab01 Management Agent ibmtiv Transaction comibmwebsphere samples trade ejb
250. eal end user transactions being performed against the Web servers These components also called listeners are the Quality of Service and J2EE monitoring components gt Playback Provides two components that can robotically playback or execute transactions that have been recorded earlier in order to simulate actual user activity These components are the Synthetic Transaction Investigator and Rational Robot Generic Windows components gt Store and Forward May be implemented on one or more agents in your environment in order to handle firewall situations More details on each of these features can be found in 3 2 Physical infrastructure components on page 61 3 1 2 Enterprise Transaction Performance 58 The Enterprise Transaction Performance ETP components are used to measure transaction performance from systems that belong to the Tivoli Management Environment Typically this implies that the transactions that are monitored take place between systems that are part of the enterprise network also known as the intranet ETP has changed little with the exception of the inclusion of the Rational Robot since the previous version of ITM for TP and is only discussed briefly in this redbook Other Redbooks that cover this topic more completely are gt Introducing Tivoli Application Performance Management SG24 5508 gt Tivoli Application Performance Management Version 2 0 and Beyond SG24 6048 gt Unveil Your e business
251. easurement versus many components type of report With this type of report you can find the components or component groups with the highest or lowest values of a certain metric The result will be a graph with the worst or best components in the x axis and the corresponding metric values in the y axis In the following sections we will demonstrate the procedure to create a Weekly Execution Load by User report 1 Open your IBM Console expand Work with Reports and click Create Report 2 Choose Extreme Case from the type selection and proceed The first difference in the summary report is in the Add Metrics dialog In an extreme case report you can choose one metric only for example the metric with the extreme value There is one additional field compared to the summary report below the metric list Here you can change the order direction If you choose ascending order the graph will start with the lowest value of the metrics Conversely you can use descending order to find the largest values As you already chose the order of the graph in this dialog the Order By choice will be Chapter 10 Historical reporting 413 414 missing in the Specify Attributes dialog Select the data mart BWM_Transaction_Performance_Data_Mart and click OK We chose the host name as the Group By entry and the relevant subdomain in the Filter By entry Check the Public button when you want to create a public report that can be seen and used by oth
252. eb Consortium Web Services Courier Web Site Investigator Web Transaction Performance World Wide Web eXtensible Markup Language Abbreviations and acronyms 477 478 End to End e business Transaction Management Made Easy 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 IBM Redbooks on page 482 gt gt gt Deploying a Public Key Infrastructure SG24 5512 e business On Demand Operating Environment REDP3673 IBM HTTP Server Powered by Apache on RS 6000 SG24 5132 IBM Tivoli Monitoring Version 5 1 Advanced Resource Monitoring SG24 5519 Integrated Management Solutions Using NetView Version 5 1 SG24 5285 Introducing IBM Tivoli Monitoring for Web Infrastructure SG24 6618 Introducing IBM Tivoli Service Level Advisor SG24 6611 Introducing Tivoli Application Performance Management SG24 5508 Introduction to Tivoli Enterprise Data Warehouse SG24 6607 Patterns for e business User to Business Patterns for Topology 1 and 2 Using WebSphere Advanced Edition SG24 5864 Planning a Tivoli Enterprise Data Warehouse Project SG24 6608 Serviet and JSP Programming with IBM WebSphere Studio and VisualAge for Java SG24 5755 Tivoli Application Performance Management Version 2 0 and Beyond SG24 6048 Tivoli Business Syst
253. eb server is located choose Web Server Specify the name of the realm for which you define credentials the fully qualified name of the system that hosts the Web site for which the realm is defined and the User Name and Password to be used to access the realm When finished click Apply 256 End to End e business Transaction Management Made Easy 8 5 Quality of Service The Quality of Service component in IBM Tivoli Monitoring for Transaction Performance Version 5 2 samples data from real time live HTTP transactions against a Web server and measures among other items the time required for the round trip of each transaction The Quality of Service component measurements include gt User Experience Time gt Back End Service Time gt Page Render Time To gather this type of information QoS intercepts the communication between end users and Web servers by means of reverse proxy technology This allows QoS to measure response times and to manage ARM correlators The use of ARM allows QoS to scale better and to be incorporated with other measurement technologies such as J2EE and STI When a HTTP request reaches QoS QoS checks the request to see if the HTTP headers contain an ARM correlator from a parent transaction If a correlator is discovered it will consider itself to be a non edge application a subtransaction in relation to gathering and recording ARM data In case of the absence of a correlator QoS will consider itself to be
254. ebSphereAS Thread Pools WebSphereAS Transactions Recent transaction response time is 180s 1000ms too high Timea out transactions are too high 180s MEE Web Applications Servlet JSP errors at application 90s 9 1 server level Servlet JSP errors at Web application fear a ace level ai Servlet JSP errors at servlet level 9s o o Servlet JSP performance at 90s 750ms 9 1 application server level Servlet JSP performance at Web 750ms application level Servlet JSP performance at servlet 750ms level Chapter 5 Interfaces to other management tools 165 166 Deployment After deciding which Resource Models and indications you need you have to deploy the monitors This means you have to 1 Create profile managers and profiles This will help organize and distribute the Resource Models A monitoring profile may be regarded as a group of customized Resource Models that can be distributed to a managed resource in a profile manager The profile manager has to be created first with the wertprfmgr command or from the Tivoli desktop After this you can create the profile which should be a Tmw2kProfile must be included in the managed resources of the policy region with the wertprf command or from the Tivoli desktop 2 Add subscribers to the profile managers The subscribers of a profile manager determine which systems will be monitored when the profile is distributed You can do this with eith
255. ect the JVM you will use with the simulations and select Next 336 End to End e business Transaction Management Made Easy Rational Test Enabler for Java E i x Rational Test Enabler for Java aw Check the Java environments you wish to enable lExplorer 6 0 2800 1106 1 10k v Sun JRE ver 2 gt 10K Space Required on C 29K Space Available on C 16814906 Description C Program Files Internet Explorer iexplore exe InstallShield lt Back Cancel Figure 9 18 Select appropriate JVM The setup completes and you are given an option to verify the setup log The log will show what files have been changed copied during the setup process Rational Robot is now ready to record and playback simulations on Java applications running in the JVM that you enabled If you add a new JVM or change the JVM you initially enabled you will have to re run the Rational Test Enabler on the new JVM Loading the Java Extension The Java enabler although important is not the only component needed to record simulations on Java applications a specific enabler has to be loaded when Rational Robot starts The Java Enabler is loaded by default after Rational Robot is installed to ensure that it is being loaded select Tools Extension Manager in the Rational Robot menu The Extension Manager dialog is displayed see Figure 9 19 on page 338 Chapter 9 Rational Robot and GenWin 337 338 Extension Manager 21x D
256. ect the available fields thaQgontain the data you want to report on Then add them to the Fields to Display list Available Fields Fields to Display aj a COMP COMP_NM a MSMT MSMT_MAx_VAL a MSMTTYP MSMTTYP_NM a MSMT MSMT_STRT_DT Report Area Avg of MSMT h MSMT MSMT_STRT_DT Add gt MSMT MSMT_MAX_VAL MSMTTYP MSMTTYP_NM Add All gt Report Area Sum of MSMT t Group 1 COMP COMP_Nb Group 2 MSMT MSMT_S TWH_CDW ODBC TWH_CD COMP a COMP_ID a COMPTYP Cn lt Remove lt Remove All tt He 4 gt Browse Data Formula Column Heading COMP_NM Find Field Design Report Preview Sample Help Cancel lt lt Back Next gt gt es A Figure 10 32 Choose fields for report generation 5 Click Group and choose the groups COMP COMP_NM and MSMT MSMT_STRT_DT 6 Click Total and choose MSMT MSMT_AVG_VA and summary type average 7 Click Select and choose MSMTTYPMSMTTYP_MN and COMP COMP_NM to define filtering for your report as demonstrated in Figure 10 33 on page 421 420 End to End e business Transaction Management Made Easy TopN Report Expert ie xj Data Links Fields Group Total TopN Drill Chat Select Style Optional Select a subset of information to display N The data can be filtered so that only a subset displays on the report Available Fields Select Fields E A Report Fields a COMP COMP_NM a MSMT MSMT
257. ed The previous version of TMTP included two different implementations of transaction recording and playback Mercury VuGen which supports a standard browser interface and the IBM Recording and Playback Workbench which provides recording capabilities for 3270 and SAP transactions This release of TMTP adds the Rational Robot as an enhanced mechanism for recording and playing back generic Windows transactions The Rational Robot functionality applies to both the ETP and WTP components of TMTP and is more completely integrated with the WTP component Appendix B Using Rational Robot in the Tivoli Management Agent environment on page 439 discusses ways of integrating the Rational Robot with the ETP component Figure 3 2 on page 60 gives an overview of the ETP architecture Chapter 3 IBM TMTP architecture 59 TBSM TMTP A WebGui TEC Enterprise Tivoli Management Region Enterprise Tivoli Managed Saiver eae Perfo erformance Transaction engine Web GUI Performance user interface responses calls and responses Tivoli Management Performance database Gateway TEDW Enterprise Transaction Performance Mid level Manager engine responses Web GUI pronis calls and pus and data upload responses and CLIs Tivoli Management Agent Endpoint Engine TMTP_AggrData resource model Log files ITM Health Console Pla
258. ed on which is not the default all QoS data may be viewed through the instance topologies 7 3 The Big Board The Big Board provides a quick summary of the state of all active monitoring policies with policy status being determined by thresholds defined by the user or generated based on the automatic baselining capabilities incorporated into the product Please refer to 8 3 Deployment configuration and ARM data collection on page 239 for a description of the automatic baselining and thresholding capabilities of TMTP Version 5 2 Figure 7 1 on page 214 shows an example of the Big Board with transactions failing violating thresholds and executing normally Chapter 7 Real time reporting 213 Big Board i CSV Qa Status Management Agent Component Event Tima Durztion Threshold Ava Minha amp a b amp s iirlab austin ibm cam BREES 2003 05 16 14 31 16 4 719 above 0 001 sec 4 877 4 719 f 5 03 slipes test pn bis p meriadocliatening E meradoc tidab austin ibm com J2EE 2009 0941 15 56 25 0 008 above 0 001 sec 0 014 0 008 0 271 bT SenletTet E b62s 1ivlab auetin ibrn cam WEE 2006 09 16 14 90 32 4 87 abaya 0 001 sec 4 669 0 005 18 0 s1 008 J9EF raliabiity E kisa tivlab austin ibrn cam sv 2003 05 12 11 04 08 1 624 equal Failure o 0 001 0
259. ed to access the central data warehouse database c Do not change the value of the Data Source field It must be TWH_MD Specify dependencies between the ETL processes and schedule processes that are to run automatically The processes for this warehouse pack are located in the BWM_Tivoli_Monitoring_for_Transaction_Performance_v5 2 0 subject area The processes should be run in the following order gt BWM_c05_Upgrade51_Process gt BWM_c10_CDW_Process gt BWM_m05_Mart_Process 400 End to End e business Transaction Management Made Easy Attention Only run the BWM_c05_Upgrade51_Process process if you are migrating from Version 5 1 0 to Version 5 2 Activating ETLs Before the newly defined ETLs can start extracting data from the source databases into the TEDW environment they must be activated This implies that a schedule must be defined for each of the main processes of the ETLs After having provided a schedule it is also necessary to change the operation mode of the all the related ETL components to production in order for TEDW to start processing the ETLs according to the specified schedule Scheduling the ETL processes In order to get data extracted periodically from the source database into the data warehouse a schedule must be specified for all the periodic processes This is also the case for one time processes that have to be run to initiate the data warehouse environment for each application area such as TMTP or ITM
260. een and the Rational Robot will continue to run in the client session Recording a GUI simulation on an HTTP application There is an important difference you must consider when you start to record a simulation on a browser based application the browser window must be started by Rational Robot You should not click on the Record GUI script and then start the browser by clicking on a Desktop link Chapter 9 Rational Robot and GenWin 363 364 To record the GUI simulation do the following steps 1 Click on the Display GUI Insert toolbar button located in the GUI Record toolbar GUI Record j This displays the GUI Insert toolbar wf Rat E O Ge wy gt ne jo jo O E Ym ee 2 Click on the Start browser button w This will display the Start browser dialog Figure 9 36 where you must type down the initial address the browser has to start with and a Tag that will be used by Rational Robot to identify the correct browser window if there are multiple windows running Start Browser Browse URL http tivlab01 itsc austin ibm com admin index html Tag WEBBrowser I Cancel Help Figure 9 36 Start Browser Dialog When you click on OK the browser opens on the address specified and all actions performed in the browser are recorded in the script Apart from the differences to start the application browser there are not any major differences compared to the procedure you usua
261. efer to 8 6 2 J2EE component configuration on page 282 1 We have created discovery policy petstore_j2ee_dis with the following configuration capturing data from the Pet Store application that generated by all users URI Filter http petstore User name In addition a schedule for discovery and listening policies has been created The name of the schedule is petsore_j2ee_dis_forever and it runs continuously Note Before creating the listening policies for the J2EE applications it is important to create a discovery policy and browse the Pet Store application and generate some transactions 2 The J2EE listening policy named petstore_j2ee_lis has been defined to listen for Pet Store transactions to the URI http tivlab0l itsc austin ibm com 7001 petstore product screen cat egory_id FISH as shown in Figure 8 60 on page 313 End to End e business Transaction Management Made Easy File Edit View Favorites Tools Help Tivoli Monitoring for Transaction Performance Iser Name administrator My Work 7Configuration Work with Discovery Policies View Discovered Transactions Work with Listening Policies Work with Playback Policies a Work with Schedules Work with Agent Groups Work with Transaction Recordinc a Please make a selection ac Work with Realms 5 gt Reports Ror URI Pattern Average Time Minimum Time Maxim gt System
262. efore it will incur larger overhead on the instrumented J2EE application server There are also larger amounts of data to be uploaded to the Management Server and persisted in the database As a result it may take a longer time to retrieve the latest data from Big Board Chapter 6 Keeping the transaction monitoring environment fit 207 You can now drill down into the topology for the violating policy and view the instance records that violated with the highest J2EE tracing detail You can see exactly which J2EE class is performing outside its threshold and view its metric data to see what it was doing when it violated Once you have finished debugging the performance violation it is recommended that the Listening Policy be changed to its default trace level of Low so that a minimal amount of data is collected at normal operation levels This will improve the performance of the monitored J2EE application server and reduce the amount of data to be rolled up to Management Server Running DB2 on AIX gt Do not create a 64 bit DB2 instance if you intend to use TEDW 1 1 as the DB2 7 2 client cannot connect to a 64 bit database gt Make sure to select Large File Enabled during the file system creation so it can support files larger than 2 GB in size gt While performing large scale testing we found that creating a file system of 14 GB in size to accommodate the TMTP DB was sufficient gt The database instance owner must have unlimited
263. ehouse Sources C Warehouse Targets C Warehouse Schemas O Administration ic E October 8 EB TRANSACTION October 9 E comp October 8 Task Flo Notification Remove Print to Printer Properties Refresh Figure 10 19 Scheduling source ETL process 4 Provide the appropriate scheduling information as it applies to your environment As shown in Figure 10 20 on page 403 we scheduled the BWM_c10_CDW_Process to run every day at 6 AM End to End e business Transaction Management Made Easy Schedule BWM_c10_CDW_Process x Schedule Task Flow Notification Occurs Schedule list Interval Startdate Starttime Interval Daily z 10 09 2003 06 00 00 Frequency Every day v Add gt Change Remove Start T Date 10 09 2003 we Time 06 00 00 End Run indefinitely Cancel Help Figure 10 20 Scheduling soure ETL process periodically Note To check if the schedule works properly with every process in the source and target ETLS use the interval setting One time only It may also be used to clear out all previously imported historical information Figure 10 20 shows an interval of Daily In general data import should be scheduled to take place when management activity is low for example every night from 2 to 7 AM with a 24 hour interval or with a very short interval for examp
264. elevant JSK or KDB files 10 Environment variables Prior to the installation we have to source the DB2 and WebSphere environment variables as follows usr WebSphere AppServer bin setupCmdLine sh home dbtmtp sql1ib db2profile End to End e business Transaction Management Made Easy This will enable you to set up the program to detect the location and perform actions on DB2 and WebSphere Also set up the variable TMPDIR to define the new temporary installation directory which will be used by the setup program export TMPDIR instal1 tmp Note Before you start the installation make sure that both the DB2 server and the WebSphere server are up and running 4 1 2 Step by step custom installation of the Management Server In this section we will go through the steps of the Management Server installation As in the previous section we have prepared our environment for the installation gt We launch the shell setup program using the following command setup_MS_aix bin is tempdir TMPDIR The TMPDIR variable represents the directory where the temporary installation files will be copied gt Press Next in Figure 4 23 on page 108 to proceed to the next window Chapter 4 TMTP WTP Version 5 2 installation and deployment 107 EA Install the Management Server oj x Welcome to IBM Tivoli Monitoring for Transaction Performance Follow the instructions in this installation program to install the following product c
265. ems Manager A Complete End to End Management Solution SG24 6202 Tivoli Business Systems Manager An Implementation Case Study SG24 6032 Tivoli Enterprise Internals and Problem Determination SG24 2034 Tivoli NetView 6 01 and Friends SG24 6019 Tivoli Web Services Manager Internet Management Made Easy SG24 6017 Copyright IBM Corp 2003 All rights reserved 479 Tivoli Web Solutions Managing Web Services and Beyond SG24 6049 Unveil Your e business Transaction Performance with IBM TMTP 5 1 SG24 6912 Using Databases with Tivoli Applications and RIM SG24 5112 Using Tivoli Decision Support Guides SG24 5506 Other resources These publications are also relevant as further information sources gt Adams et al Patterns for e business A Strategy for Reuse MC Press LLC 2001 ISBN 1931182027 IBM Tivoli Monitoring for Transaction Performance Enterprise Transaction Performance User s Guide Version 5 1 GC23 4803 IBM Tivoli Monitoring for Transaction Performance Installation Guide Version 5 2 0 SC32 1385 IBM Tivoli Monitoring for Transaction Performance User s Guide Version 5 2 0 SC32 1386 IBM Tivoli Monitoring User s Guide Version 5 1 1 SH19 4569 IBM Tivoli Monitoring for Web Infrastructure Apache HTTP Server User s Guide Version 5 1 0 SH19 4572 IBM Tivoli Monitoring for Web Infrastructure Installation and Setup Guide Version 5 1 1 GC23 4717 IBM Tivoli Monitoring for Web Infrastructure Reference Guide V
266. eneration 20000 eee eeee 420 10 33 Crystal Reports filtering definition 00000200 0 421 10 34 trade_2_stock check_tivlab01 playback policy end user experience 422 10 35 trade_j2ee_lis listening policy response time report 423 10 36 Response time JDBC process Trade applications executeQuery 424 10 37 Response time for trade by trade_qos_lis listening policy 425 A 1 Patterns layered asset model 0 002 eee eee eee 432 A 2 Pattern representation of a Custom design 2 5 434 A 3 Custom design 0 00 tee eee 435 B 1 ETP Average Response Time 0 00 eee ee eee 441 B2 ARMAPI Calls 0 00000 e eee 442 B 3 Rational Robot Project Directory 0 0 00 eee eee 443 B 4 Rational Robot Project 0 0 cece eee 444 B 5 Rational Robot Project 0 0 eee eee eee 445 B 6 Configuring project password 2 0 0c eee eee eee 446 B z lt Finalize projects oie sce arean teat O E A dad s eta EE AORA 447 B 8 Configuring Rational Project 0 0c eee eee 448 B 9 Specifying project datastore 0 02 c eee eee 449 B 10 Scheduler iis canis adie bie be eee Waly Oh petit ees 454 B 11 Scheduling wizard 0 0 ccs 455 B 12 Scheduler frequency 00 00 cece ete ee 456 Figures XV xvi B 13 B 14 B 15 B 16 B 17 B 18 B 19 B 20 B 21 B 22 Schedule start time 0 0 0 ccc eee 45
267. eption message IBM JDBC Driver CLIO600E Invalid connection handle or connection is closed SOLSTATE 5 1000 rror 500 nested exception is javax resource spi ResourceAllocationException DSRAOQOSOE An exception was received by the Data Store Adapter See original exception message IBM JDBC Driver CLIO600E Invalid connection handle or connection is closed SQLSTATE 5 1000 R Ne Ki E Done Internet Figure 6 1 WebSphere started without sourcing the DB2 environment gt To check if the TMTP Management Server is up and running type the following URL into your browser this will only work for a nonsecure installation for a secure installation you will need to use the port 9446 and will need to import the appropriate certificates into your browser key store this process is described below http managementservername 9081 tmtp servlet PingServlet gt If you use the secure installation of the TMTP Server you can use the following procedure to check your SSL setup Import the appropriate certificate into your browser key store If you are checking to see if SnF should be able to connect to Management Server the following is required Open the Store and Forward machines kdb file using the IBM Key Management utility that is the key management tool which can open kdb files Export the self signed personal certificate of the SnF machine to a PKCS12 format file this is a form
268. er the wsub command or from the Tivoli desktop The subscribers for IBM Tivoli Monitoring for Web Infrastructure would be the managed application objects that were created in 5 1 3 Creating managed application objects on page 158 3 Add Resource Models We recommend that you group all of the Resource Models to be distributed to the same endpoint or managed application object in a single profile You can now add the Resource Models with the parameters you have chosen to the profiles You can do this by using either the wdmeditprf command or the Tivoli desktop as shown in Figure 5 5 on page 167 End to End e business Transaction Management Made Easy IBM Tivoli Monitoring Profile P 5 xj Profile Edit view Help Profile VWAS_BP_ApplSvr Set Label Profile Manager WAS_WSA_ApplSvr Subscription Path AWAS_WSA_ApplSviWAS_BP_ApplSvr Resource Model Cycle Time sec Category Enable ere Application Server WebSphereAS EJBs WebSphere Application Server YES WebSphereAS HTTP Sessions WebSphere Application Server YES WebSphereAS JVM G WebSphere Application Server YES WebSphereas Thread Pools F S WebSphere Application Server as YES 8 Entries WebSphereAS DB Pools Threshold Name Threshold Value Database connection pool average wait time 250 000000 Thresholds Database connection pool faults EENE E C Parameters Percent data
269. er users You see the public entry only when you have sufficient roles to create public reports Click on the Metrics tab You will see the list of chosen metrics which is still empty In a summary report there a typically many metrics Click Add to choose metrics from the star schema You will see the list of all star schemes of the chosen data mart Figure 10 28 on page 415 Select one of them and you will see all available metrics of this star schema You see that there is a minimum maximum and average type of each metrics These values are generated when the aggregation of the source data to hourly and daily data is done Each aggregation level has its own star schema with its own fact table In a fact table each measurement can have a minimum maximum average and total value Which values are used depends on the application and can be defined in the D_METRIC table When a value is used a corresponding entry will appear in the available metrics list in the Reporting Interface Choose the metrics you need in your report and click Next You will see the Specify Aggregations dialog In this dialog you have to choose an aggregation type for each chosen metric A summary report covers a certain time window defined later in this section All measurements are aggregated over that time window The aggregation type is defined here End to End e business Transaction Management Made Easy Administer Users and Roles
270. ere Application Server Advanced Edition is installed armjni jar copyright jar core_util jar ejfit jar eppam jar jffde jar jfltjar jlog jar probes jar 8 Remove the file lt WAS_HOME gt AppServer bin ijitipi dll 9 The administrative node and application server may now be restarted End to End e business Transaction Management Made Easy Manual J2EE uninstall on WebSphere 5 0 1 Start the WebSphere 5 Application Server Administrative Console on the computer on which the instrumented application server resides or on the Network Deployment server 2 In the navigation tree on the left expand Servers Click on the Application Servers link 3 In the Application Servers table on the right click on the application server that has been instrumented Under the Additional Properties table click the Process Definition link Under the Additional Properties table click the Java Virtual Machine link Under the General Properties table look for the Generic JVM Argument field see Figure 6 7 Fle Edt Vew Favottes Took Hep Address la htplfemenss0 HEEB Aviston sener Administrative Const ie Home Save Preferences Logout Help Application Server Java ine vert gt Process Definition gt User ID admin 2 Def intiva 5 Servers Advanced Java vitual machine settings E Applications Configuration Enterprise
271. ere managed application objects are created differently from the other Web server objects In order to manage WebSphere Application Servers two types of WebSphere managed application objects need to be defined 1 WebSphere Administration Server managed application object 2 WebSphere Application Server managed application object The WebSphere Administration Server managed application object must be created before the WebSphere Application Server managed application object You can create the managed application object for the WebSphere Server in three different ways 1 Using the Tivoli desktop in which case you need to follow these two steps a Create the WebSphere Administration Server managed application object by selecting Create WSAdministrationServer in the policy region which will open the dialog shown in Figure 5 1 on page 159 158 End to End e business Transaction Management Made Easy Create WSApplicationServer ol x i icati a Create WSApplicationServer Application Server Name DefaultServer Administration Server Label pplication Server panda Endpoint Name BL Has Web Module C No Yes Has EJB Module C No Yes Set and Execute 1 Figure 5 1 Create WSAdministrationServer b Create the WebSphere Application Server managed application object by selecting Create WSApplicationServer in the policy region The dialog in which you can specify the parameters fo
272. ers of TMTP have expressed a desire to be able to lock the screen while the Rational Robot is playing The best and most secure solution to this problem is to lock the endpoint running simulations in a secure cabinet There is no easy alternative solution as the Rational Robot requires access to the screen context while it is playing back During the writing of this redbook we attempted a number of mechanisms to achieve this result including use of Windows XP Switch User functionality without success The following Terminal Server solution implemented at one IBM customer site was suggested to us We were unable to verify it ourselves but we considered it useful information to provide as a potential solution to this problem This solution relies on the use of Windows Terminal Server which is shipped with the Windows 2000 Server When a user runs an application on Terminal Server the application execution takes place on the server and only the keyboard mouse and display information is transmitted over the network This solution relies on running a Terminal Server Session back to the same machine and running the Rational Robot within the Terminal Server session This allows the screen to be locked and the simulation to continue running 1 Ensure that the Windows Terminal Server component is installed If it is not it can be obtained from the Windows 2000 Server installation CD from the Add On components dialog box see Figure 9 33 on page 361
273. ersion 5 1 1 GC23 4720 IBM Tivoli Monitoring for Web Infrastructure WebSphere Application Server User s Guide Version 5 1 1 SC23 4705 Tivoli Application Performance Management Release Notes Version 2 1 GI10 9260 Tivoli Application Performance Management User s Guide Version 2 1 GC32 0415 Tivoli Decision Support Administrator Guide Version 2 1 1 GC32 0437 Tivoli Decision Support Installation Guide Version 2 1 1 GC32 0438 Tivoli Decision Support for TAPM Release Notes Version 1 1 Gl10 9259 Tivoli Decision Support User s Guide Version 2 1 1 GC32 0436 Tivoli Enterprise Console Reference Manual Version 3 7 1 GC32 0666 Tivoli Enterprise Console Rule Builder s Guide Version 3 7 GC32 0669 480 End to End e business Transaction Management Made Easy gt gt Tivoli Enterprise Console User s Guide Version 3 7 1 GC32 0667 Tivoli Enterprise Data Warehouse Installing and Configuring Guide Version 1 1 GC32 0744 Tivoli Enterprise Installation Guide Version 3 7 1 GC32 0395 Tivoli Management Framework User s Guide Version 3 7 1 SC31 8434 The following publications come with their respective products and cannot be obtained separately gt gt gt NetView for NT Programmer s Guide Version 7 SC31 8889 NetView for NT User s Guide Version 7 SC31 8888 Web Console User s Guide SC31 8900 Referenced Web sites These Web sites are also relevant as further information sources gt Apache Web site http www
274. ersion 7 2 FixPack 6 or higher Upgrade IBM DB2 Universal Database Enterprise Edition Version 7 2 to at least FixPack 6 on your Tivoli Enterprise Data Warehouse environment 384 End to End e business Transaction Management Made Easy FixPack 6 for IBM DB2 Universal Database Enterprise Edition can be download from the official IBM DB2 technical support Web site http www 3 ibm com cgi bin db2www data db2 udb winos2unix support v7fphist d2 w report Apply TEDW FixPack 1 1 TDW 002 or higher Apply the FixPack 1 1 TDW 0002 on every database server in your TEDW environment FixPack 1 1 TDW 0002 for Tivoli Enterprise Data Warehouse can be downloaded from the IBM Tivoli Software support Web site under the Tivoli Enterprise Data Warehouse category http www ibm com software sysmgmt products support Update the TEDW environment to FixPack 1 1 TDW FP01a FixPack 1 1 TDW FP01a for Tivoli Enterprise Data Warehouse can be downloaded from the IBM Tivoli Software support Web site under the Tivoli Enterprise Data Warehouse category http www ibm com software sysmgmt products support The documentation that accompanies the FixPacks details the steps for installation in greater detail Ensure adequate heap size of the TWH_CDW database The applications control heap size on the TWH_CDW database needs to be set to at least 512 as follows 1 Log on using the DB2 administrator user ID to your TEDW Server machine in our case db2admin a
275. ervers at varying version levels A J2EE transaction can be made up of many components for example JSPs Servlets EJBs JDBC and so on This level of complexity makes it hard to identify if there is a problem and where that problem lies We need a mechanism for finding the component that is causing the problem J2EE support provided by TMTP 5 1 In TMTP 5 1 the ETP component could collect ARM data generated by applications on WebSphere servers that had IBM WebSphere Application Server Version 5 0 installed This data was provided by the WebSphere Request Metrics facility This was a start but only limited detail was provided such as the number of servlets and number of EJBs The ETP component could supplement this data by collecting ARM data independently of the STI Player and the STI player could trigger the collection of ARM data on its behalf ETP then uploaded all the ARM data from all the transactions within an application that have been configured in WebSphere The administrator could turn data collection on or off at the application level These capabilities solved some business problems but led to the need for greater control and granularity as well as the need for greater scope J2EE support provided by TMTP Version 5 2 TMTP Version 5 2 provides enhanced J2EE instrumentation capabilities The collection of ARM data generated by J2EE applications is invoked from the new Management Server not from ETP The ARM collection is
276. es and or across members gt Trend analysis over sequential time periods Chapter 10 Historical reporting 417 gt Slicing subsets for on screen viewing gt Drill down to deeper levels of consolidation gt Reach through to underlying detail data gt Rotation to new dimensional comparisons in the viewing area 10 4 1 Crystal Reports overview The OLAP tools used to demonstrate creation of OLAP reports in the following provides connectivity to virtually any enterprise data source rich features for building business logic comprehensive formatting and layout and high fidelity output for the Web or print In addition Crystal Reports provides an extensible formula language for building complex reports requiring complex business logic Built in interactivity personalization parameters drill down and indexing technologies enable custom content to be delivered to any user based on security or on user defined criteria Finally any report design can be outputted to a variety of formats including PDF Excel Word and our standard published XML schema XML can also be tailored for to match other standard schema The value of a standard tool extends beyond the widespread availability and general quality of the product It includes all the value add often associated with industry standards large pools of skilled resources large knowledge base partnerships and integration with other enterprise software vendors easy access to consul
277. es confirmation of the completed Order on a subsequent request 238 End to End e business Transaction Management Made Easy 8 3 Deployment configuration and ARM data collection There are four different type of components that can deployed to a single Management Agent It is possible of deploy all four components to the same system They are gt Synthetic Transaction Investigator gt Quality of Service gt J2EE gt Generic Windows Once deployed monitoring is activated by configuring and deploying different sets of monitoring specifications known as policies to one or more Management Agents The monitoring policies include specifications directing the monitoring components to perform specific tasks so the specific monitoring component referenced in a policy has to have been deployed to a Management Agent before the policy can be deployed IBM Tivoli Monitoring for Transaction Performance Version 5 2 operates with two types of policies Discovery policy The discovery component of IBM Tivoli Monitoring for Transaction Performance enables identification of incoming Web transactions that may be monitored When using the discovery process a discovery policy is created and within the discovery policy an area of the Web environment that is under investigation is specified The discovery policy then samples transaction activity from this subset of the Web environment and produces a list of all received unique URI requests includi
278. ess sites In addition application run time technologies play a major role as they must ensure platform independence and seamless integration to the legacy back end systems either directly to the mainframe or through the server part of the old client server solution Furthermore making the applications accessible from anywhere in the world by any person on the planet raises some security issues authentication authorization and integrity that did not need addressing in the old client server systems as all clients were well known entities in the internal company network Because of the central role that the Web and application servers play within a business and the fact that they are supported and typically deployed across a 12 End to End e business Transaction Management Made Easy variety of platforms throughout the enterprise there are several major challenges to managing the e business infrastructure including gt Managing Web and application servers on multiple platforms in a consistent manner from a central console gt Defining the e business infrastructure from one central console gt Monitoring Web resources sites and applications to know when problems have occurred or are about to occur gt Taking corrective actions when a problem is detected in a platform independent way gt Gathering data across all e business environments to analyze events messages and metrics The degree of complexity of e business infrast
279. ess the Save Transaction button Now a XML document containing the recording is generated as shown in Figure 8 9 on page 247 End to End e business Transaction Management Made Easy net STI Recorder 5 x http tivdced itsc austin ibm com 3082 tmtpUl LogOn jsp Reset Transaction Completion Time A Progress fey apy pee Back Forward Refresh J Repaint _ Saa irnata 10 seconds Done Help Create STI Transaction Recording Transaction Name trade _2 oder Transaction Document lt xml version 1 0 encoding UTF 8 gt lt http transaction version sti 5 1 gt lt request source gesture target gt lt request line gt lt CDATA GET http ibmtiv9 trade app http 1 1 gt lt request line gt lt headers gt lt hl source user gt Pragma no cache lt hl gt lt hl source user gt Cache Control no cache lt hl gt lt headers gt lt meta info gt lt meta tag URI gt lt CDAaTA http ibmtiv9 trade app gt lt meta gt lt meta info gt lt request gt lt request source gesture target gt lt request line gt lt CDATA POST http ibmtiv9 trade app http 1 1 gt lt request line gt lt headers gt lt hl source user gt Pragma no cache lt hl gt lt hl source user gt Cache Control no cache lt hl gt lt hl source user gt Content Type application x www form ur lencoded lt hl gt lt headers gt lt content gt lt w3c enc type text gt lt CDATA uid uid 340 gt lt w3c enc gt
280. est Assets Associated Test Datastore Create Select Change Requests Associated ClearQuest Database oes Models Associated Rose Models Close Help Figure 9 23 Configuring Rational Project A Rational Test datastore is a collection of related test assets including test scripts suites datapools logs reports test plans and build information You can create a new Test datastore or associate an existing Test datastore For testing Rational Robot the user must set up the Test datastore To create a new Test datastore 1 In the Configure Project dialog box click Create in the Test Assets area The Create Test Datastore tool appears see Figure 9 24 on page 344 Chapter 9 Rational Robot and GenWin 343 Create Test Datastore New Test Datastore Path CAR ationalT est T estD atastore Browse Initialization Options Initialize Assets from the following Test Datastore a Initialize Test Users and Groups from the Rational Project Test Sept o Advanced Database Setup Cancel Help Figure 9 24 Specifying project datastore 2 Inthe Create Test Datastore dialog box a In the New Test Datastore Path field use a UNC path name to specify the area where you would like the tests to reside b Select initialization options as appropriate c Click Advanced Database Setup and select the type of database engine for the Test datastore d C
281. eters may be filled with randomly generated values at request time For example a HTML page containing a form element could fill at request time A hidden input field value could be updated with a random value generated from JavaScript before the request is sent The playback uses the result from the recorder JavaScript it does not execute the JavaScript when filling in the form data This can cause incorrect data or the request to fail Since the STI playback runs as a service without a user interface the JavaScript alert cannot be answered and hangs the transaction Since the STI playback runs as a service without a user interface the window cannot be acted upon and hangs the transaction When a Web server redirects a page server side redirect a subtransaction may end prematurely and fail to process subsequent subtransactions Chapter 8 Measuring e business transaction response times 231 Usually the server redirect occurs on the first subtransaction To avoid this behavior you may initiate the recording by navigating to the server side page to which STI was redirected In addition you should be aware of the following gt Synthetic Transaction Investigator playback does not support more than one security certificate for each endpoint gt STI might not work with other applications using a Layered Service Provider LSP gt STI cannot navigate to a redirected page if the Web browser running STI is configured thr
282. etes the management agent will restart automatically Would you like to automatically restart your management agent now OK Alt 0 Apply Alt a Cancel Alt c aft Figure 9 38 Deploy Components and or Monitoring Component Tip The Rational Project does not have to exist prior to this step In fact it is far easier to create this Rational Project after deploying the GenWin project because the Project must be located in the directory MA app genwin lt project gt MA is the home directory for the Management Agent and this path is not created until the Generic Windows component has been deployed After you have deployed the Generic Windows component you must create a new Rational Robot Project on the Management Agent with details that match the details you have entered into the Deploy Components and or Monitoring Component window When you specify playback policies the Rational Robot scripts will automatically be placed into this project 5 Create a Rational Robot Project for use by the Generic Windows component for playback The procedure for creating a Rational Robot Project is covered in 9 1 2 Configuring a Rational Project on page 339 In order for GenWin to use the project it needs to be located using a subdirectory to the Chapter 9 Rational Robot and GenWin 367 MA app genwin directory When the project has been created it will resicde in a subdirectory of the MA app genwin lt project gt directory 9
283. evelopment company Deployment Method Enterprise deployment Create a network release area and customize it using Siteprep Desktop installation from CD image cot vee Figure 9 5 Rational Robot deployment method Select Desktop installation from CD image and click on Next the installation will check various items and then display the Rational Robot Setup Wizard see Figure 9 6 on page 330 Chapter 9 Rational Robot and GenWin 329 ji Rational Robot Setup Wizard Rational Welcome to the Setup Wizard for Rational the software development company Robot The Setup Wizard will install Rational Robot on your computer To continue click Next WARNING This program is protected by copyright law and international treaties Figure 9 6 Rational Robot Setup Wizard Click on Next the Product Warnings will be displayed see Figure 9 7 ip Rational Robot Rational Wizard Rational the software development company Product Warnings Please take note of the following warnings regarding installation of this product onto your machine There are some product specific warnings for this installation STOP Before proceeding with this install please close all applications and disable anti virus software Check http solutions rational cor solutions display jsp solutionld 182435434 for information on how to prevent potential system corruption Rational Software E Cancel Figure
284. eving data to from the DB make sure the hard drive and the disk interface have good read write performance Consider keeping the database on a dedicated physical disk if possible and using RAID gt Ina large scale environment we suggest increasing the Maximum Heap size for the WebSphere Application Server 5 0 JVM where the Management Server runs From the WebSphere Application Server admin console select Servers gt Application Servers server1 Process Definition Java Virtual Machine and set the Max heap Size to 256 gt Larger Value Consider changing the WebSphere Application Server JVM Maximum Heap size to half the physical memory on the system if there are no competing products that require the unallocated memory Note Having a higher setting for the WebSphere Application Server JVM Maximum Heap size means that WebSphere Application Server can use up to this maximum value if required gt Run db2 reorgchk daily on the database to prevent the Ul Reports performance from degrading as the database grows This command will reorganize the indexes Note The db2 reorgchk command might take some time to complete and may need to be scheduled at off peak times Best practice for J2EE application monitoring and debugging Out of the box the TMTP J2EE Monitoring Component records a summary of the transactions in the J2EE application server This default summary level is optimal Chapter 6 Keeping the transaction monitori
285. f duplication is needed to ensure high availability and to handle a large number of concurrent users The architecture that you see here is different in several ways from the past In the past all of these components were often on a single infrastructure the mainframe This all changed with the evolution of client server and is now changing again with the trend towards Web Services 2 1 1 The pain of e business transactions 38 Generally when monitoring an environment such as that described above the response to a customer complaint about poor performance can be described as follows Step 1 Typically a call comes in to the help desk indicating that the response time for your e business application is unacceptable This is the first place where you need a transaction performance End to End e business Transaction Management Made Easy product to find out if there is a problem hopefully before the customer calls you to identify a problem Important At step 1 if the customer has IBM Tivoli Monitoring then they would see far few problems even show up because they are being automatically cured by resource models If the customer has TBSM and itis a resource problem then there is a good chance that the team is already working on solving the problem if it is in a critical place Step 2 Step 3 Step 4 Step 5 The next step usually involves the operations center The Network Operations Center NOC gets the message and s
286. figure System Component Manag Name I petstore_j2ee_lis J2EE j2ee_agent_group discov_lis_sch_forever Status In scheduled window O qos _dis_pol Qos sti_q0s_agent discov_lis_sch_forever In scheduled window Vv itrade_j2ee_dis J2EE j2ee_agent_group discov_lis_sch_forever In scheduled window I ftra Page 1 e lis J2EE j2ee_agent_group discov_lis_sch_forever In scheduled window Configure User Set G ae Work with Event R Show Enabled Policies Show Disabled Policies View System Even 4 afl 4 ofl I aa Work with Discovery Policies Choose Create Edit etc aa ZE Local intranet Ui Figure 8 41 Create a listening policy for J2EE 3 Now to choose the transactions to be monitored through this listening policy perform the following a First make sure that the active policy type is J2EE b Select the discovery policy of your interest c Select View Discovered Transactions from the action drop down menu d Finally click Go to open the View Discovered Transactions dialog as depicted in Figure 8 42 on page 290 Chapter 8 Measuring e business transaction response times 289 E IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer ee i oj xj File Edit View Favorites Tools Help Address T http tivdce4 9082 tmtpUI jsp console WwcFrameManager jsp G Go 2 Back gt A A Ase
287. for STI transactions and have events generated at a subtransaction level Configure QoS settings You can not create a QoS setting during the creation of a STI playback policy However when playback policies has been executed once and a topology has been created this option becomes available Configure J2EE settings If the monitored transaction is hosted by a J2EE application server you should configure J2EE Settings using the default values as a starting point Chapter 8 Measuring e business transaction response times 253 254 Choose schedule Select the schedule that is defined when the STI Playback policy is executed You may consider using the schedule created in the beginning of this section as described in 8 4 4 Playback schedule definition on page 248 Choose agent group Select the group of Management Agents to execute this STI Playback policy Please remember that the STI component has to have been deployed to each of the Management Agents in the group to ensure successful deployment and execution Note If you want to correlate STI with QoS and J2EE choose the Agent Group where QoS and J2EE components are deployed Assign Name Assign a name to the new STI Playback policy In the example shown in Figure 8 15 on page 255 the name assigned is trade_2_stock check End to End e business Transaction Management Made Easy File Edit View Favorites Tools Help Address http ti
288. formance Warehouse Enablement Pack extracts data from the ITMTP Enterprise Transaction Performance RIM database TAPM and the Web Services Courier database respectively and loads it into the TEDW Central Data Warehouse database TWH_CDW The two modules acts as a source ETLs All TEDW ETL programs follow a naming convention using a three letter application specific product code known as measurement source code Table 10 1 shows the measurement codes used for the TMTP Warehouse Enablement Packs Table 10 1 Measurement codes Warehouse module name Measurement code IBM Tivoli Monitoring Transaction and Performance 5 2 WTP The installation can be performed using the TEDW Command Line Interface CLI or the Graphical User Interface GUI based installation program Here we describe the process using the GUI method The following steps should be performed at the Tivoli Enterprise Data Warehouse Control Center server once for each of the IBM Tivoli Monitoring for Transaction Performance Warehouse Enablement Packs that are being installed Note You need both the TEDW and the appropriate IBM Tivoli Monitoring for Transaction Performance products installation media 1 Insert the TEDW Installation CD in the CD ROM drive 2 Select Start Run Type in D setup exe and click OK to start the installation where D is the CD ROM drive 3 When the Install Shield Wizard dialogue window for TEDW Installation appears Figure 10 5 on pag
289. gement Russ Blaisdell Oliver Hsu Jose Nativio Steven Stites Bret Patterson Mike Kiser Nduwuisi Emuchay Tivoli Development J J Garcia Greg K Havens II Tina Lamacchia Tivoli SWAT Team Become a published author Join us for a two to six week residency program Help write an IBM Redbook dealing with specific products or solutions while getting hands on experience with leading edge technologies You ll team with IBM technical professionals Business Partners and or customers Your efforts will help increase product acceptance and customer satisfaction As a bonus you ll develop a network of contacts in IBM development labs and increase your productivity and marketability Find out more about the residency program browse the residency index and apply 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 comments about this or other Redbooks in one of the following ways gt Use the online Contact us review redbook form found at ibm com redbooks gt Send your comments in an Internet note to redbook us ibm com gt Mail your comments to IBM Corporation International Technical Support Organization Dept JN9B Building 003 Internal Zip 2834 11400 Burnet Road Austin Texas 78758 3493 XXiV End to End e business Transaction Management Made Easy Part 1 Business value of end to end transaction monitori
290. gions and Window Images using OCR but in the case of e business applications Object Properties Verification Points are easier to use reliable and less subject to suffer changes in the application interface or data displayed The state of an application working in a client server environment during the playback of a simulation often changes if the data retrieved from the server is different from the one retrieved during the recording so to avoid errors during the playback it is a good idea to use Verification Points Using Verification Points you can verify that an object s properties are those expected Verification Points can be added in a script 1 During the recording 2 While editing the script after the recording In both cases you need to press the Display GUI insert Toolbar in the Rational Robot floating toolbar during the recording or on the Standard Toolbar while editing but you must be sure that the cursor is at the point where you want to add the Verification Point if you have already recorded the script After you press the Display GUI Insert Toolbar button you will see the GUI Insert toolbar floating Figure 9 26 on page 346 Select the type of Verification Point needed for example Object Properties and type a name for the Verification Point in the Verification Point Name dialog Figure 9 27 on page 348 Chapter 9 Rational Robot and GenWin 347 erification Point Name Name Object Properties 1
291. gure B 20 Terminal Server Add On Component As the Terminal Server session will be back on the local machine there is no reason to install the Terminal Server Licensing feature Due to this fact you should also select the Remote Administration mode option during Terminal Server install After the Terminal Server component is installed you will need to reboot your machine 2 Install the Terminal Server client on the local machine The Terminal Server install provides a facility to create client installation diskettes This same source can be used to install the Terminal Server client locally Figure B 21 on page 470 by running the setup exe the path to this setup exe is by default c winnt system32 clients tsclient win32 disks disk1 Appendix B Using Rational Robot in the Tivoli Management Agent environment 469 470 N C WINNT system32 clients tsclient win32 disks diski Eile Edit view Favorites Tools Help se Back gt v Qseach ares A A K A Ea EUS ja C WINNT system32 clients tsclient win32 disks disk1 z Go Folders x Name Size EB appmomt a acmsetup exe 345KB A CD catRoot QP acmsetup hip 15KB H i hO cea e commonss dil 57KB A BA certsry 247KB A BAA dents 2KB T EH tsclient 259KB A net 1KB C ce wins SKB 5 E wins2 7KB 5 EHO disks 1KB I ski 80KB A disk2 Maes Plier 1KB C C com 2KB L O config 1KB T a dhcp diicache i drivers a DTCLog i O expo
292. hapter 8 Measuring e business transaction response times 313 314 Tivoli Monitoring for Transaction Performance User Name administrator My Work Configuration Work with Discovery Policies Work with Listening Policies Work with Playback Policies Work with Schedules Work with Agent Groups Work with Transaction Recording Work with Realms gt Reports b System Administration gt Downloads View Discovered Transactions 0 Q Please make a selection j So Alttg URI or URI Patter Page 1 All Times are in Seconds Query String Keys Limit 2 category_id Discovered average response time Apply Alt a Cancel Alt c sf Figure 8 61 Choose Pet Store transaction for Listening policy A threshold is defined for the listening policy for response times 20 higher than the average reported by the discovery policy as shown in Figure 8 62 Tivoli Monitoring for Transaction Performance Configuration Pilea Create J2EE Threshold Work with Discovery Policies SERA IL Se GUNE Work with Listening Policies 2 2EE Threshold wh Work with Playback Policies g s Performance espon se time th reshold Work with Schedules Transaction Work with Agent Groups Cho p http Vtivlab01 itsc austin ibm com 7001 jge product screen Work with Transaction Recording a aa Work with Realms Choose aie Candition Threshold b Reports Above z 0 074 Seconds b S
293. has not tested those products and cannot confirm the accuracy of performance compatibility or any other claims related to non IBM products Questions on the 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 them as 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 business enterprise is entirely coincidental COPYRIGHT LICENSE This information contains sample application programs in source language which illustrates programming techniques on various operating platforms You may copy modify and distribute these sample programs in any form without payment to IBM for the purposes of developing using marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample 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 You may copy modify and distribute these sample programs in any form without payment to IBM for the purposes of developing using marketing or distributing application programs conforming to IBM s application programming interfa
294. he E Step_9_http tiviabO1 itsc austin ibm com petstore signoff do Step_7_http tiviabO1 itsc austin iom com petstore enter_order_it petstore_2_order_tiviab01 0 0 10 01 10 03 10 05 10 07 10 09 16 00 15 15 14 30 13 45 13 00 Time JJ of i Downloads E Local intranet A Figure 10 22 Pet Store STI transaction response time report for eight days Please refer to 8 7 Transaction performance reporting on page 295 for more details on using the IBM Tivoli Monitoring for Transaction Performance General Reports 10 3 Reports by TEDW Report Interface The following discusses how to use the new TEDW ETL2 reporting feature of IBM Tivoli Monitoring for Transaction Performance Version 5 2 10 3 1 The TEDW Report Interface Using the Tivoli Enterprise Data Warehouse Report Interface RI you can create and run basic reports against your data marts and publish them on your intranet or the Internet The Report Interface is not meant to replace OLAP or Business Intelligence tools If you have multidimensional reporting requirements or need to create a more sophisticated analysis of your data Tivoli Enterprise Data Warehouse s open structure provides an easy interface to plug into OLAP or Business Intelligence tools 406 End to End e business Transaction Management Made Easy Nevertheless for two dimensional reporting requirements Tivoli Enterprise Data Warehouse Report Interface provides a powerful tool The RI is a role
295. he process of obtaining a license Choose one of the selections below and click Newt to continue Point to a Rational License Server to get my licenses C Import a Rational License File Get Return or Move Keys Enter a Temporary or Evaluation License Key T Dont show this wizard on startup again Iuse the toolbar to activate it Ready DISPLAY FILTER is OFF Figure 9 12 Rational Robot license key administrator wizard In the License Key Administrator Wizard select Import a Rational License File and click on Next The Import License File panel is displayed click the Browse button and select the ibm_robot upd provided in the root folder of the Rational Robot CD see Figure 9 13 on page 334 Chapter 9 Rational Robot and GenWin 333 Import a License File a xij Select the license file you want to import Point to a upd or txt file on your machine or network that contains license information received from Rational Software Click Import to complete the process License Import File E ibm_robot upd Import lt Back Finish Cancel Help Figure 9 13 Import Rational Robot license Click on the Import button to import the license The Confirm Import panel is displayed see Figure 9 14 Confirm Import xj lt 9 Would you lke to import these Node Locked Licenses Product License Type License Term gi Expiration Rational Robot NodeLocked Valid uncounted permanent Figure 9 14 I
296. he application specific data mart database 10 1 2 TMTP Version 5 2 Warehouse Enablement Pack overview IBM Tivoli Monitoring for Transaction Performance Version 5 2 has the ability to display the detailed transaction process information as real time reports The data is stored in the TMTP database that runs on either DB2 or Oracle database management products This database is regarded as the source database for the warehouse pack When the TMTP real time reporting data is stored in the source database the central data warehouse database ETL periodically processes normally once a day and extracts data from the source database to the central data warehouse database TWH_CDW Once in the central database the data is converted to the TMTP warehouse pack data model shown in Figure 10 2 on page 381 This data model allows the TMTP reporting data to fit into the general schema of Tivoli Enterprise Data Warehouse Version 1 1 380 End to End e business Transaction Management Made Easy Si BWM_TRANSACTION M d BWM_TX_NODE uy USES SUBTR J2EE_DONAIN i h pcuitp PCHILD PCHILD J2EE_CELL PCHILD u Figure 10 2 TMTP Version 5 2 warehouse data model After the central data warehouse ETL processes are complete the data mart ETL processes load data from the central data warehouse database into the data mart database In the data mart database fact tables dimension tables and helper tables are created in the BWM
297. he degree of certainty that was available in other applications Duplicating the production environment in a test environment becomes difficult To be more effective operations should participate in QA to bring infrastructure expertise into the process and should also be prepared to use QA as a resource during operations to test limited changes or component evolution The infrastructure management solution adapted to the new application architecture must include a real time monitoring component that provides a service assurance capability It must extend its data capture to all components including J2EE and connectors to other resources such as EAI and be able to collect additional parameters beyond availability and performance Content verification and security are some of the possible parameters but transaction availability is another type of alert that becomes relevant in this context close to the business process Root cause analysis which identifies the origin of a problem in real time must be able to pinpoint problems within the transaction flow including the J2EE application server and the external components of the application An analytical component to help analyze problems within and without the application server is necessary to complement the more traditional tools aimed at analyzing infrastructure resources 1 2 2 Importance of JMX 8 In the management of J2EE platforms the JMX model has emerged as an impo
298. he following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND EITHER EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF NON INFRINGEMENT MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE Some states do not allow disclaimer of 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 made to the information herein these changes will be incorporated in new editions of the publication IBM may make 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 any manner serve as an endorsement of those Web sites The materials at those Web sites are not part of the materials 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 without incurring any obligation to you Information concerning non IBM products was obtained from the suppliers of those products their published announcements or other publicly available sources IBM
299. he position where you need to remove the J2EE instrumentation from the Web Application Server manually If this happens you can use the following procedure as a last resort Important You should only use this procedure when all else fails Manual J2EE uninstall on WebSphere 4 0 1 Start the WebSphere 4 Advanced Administrative Console on the computer on which the instrumented application server resides Expand the WebSphere Administrative Domain tree on the left and select the application server that has been instrumented see Figure 6 6 on page 197 196 End to End e business Transaction Management Made Easy gi WebSphere Advanced Administrative Console OR 8 x Console View Tools Help eer xg wv WebSphere Administrative Domain Vinual Hosts Server Groups E ristalled Web Modwes gt Nodes gt O hmeknnezx Application Servers pm General Advarced Fte Transaction JVM Setings services Custom H n App Server E Generic Seners Initial java heap size m Enterprise Appacations Resources Maximum java heap size MB Ciasspahis Name J Add System Properties om am tvoll ranspertiogging baseoir C NANAON sthamenhappServerst com Dm tivoli j2 probe drectory CAMMlappunstrumentabyed comm tivoli j0 config CiMMappwisinenentiibiconfig properties Ly Ateanced JVM Setings Generated Command Line Arguments bootclasspalh s C UMAlapplinstum erd IDY ar C WMAlspolin
300. her times For the unique cases where these violations are not caught via this mechanism it is expected that a user will change the monitoring policy for this transaction to be an instance in order to ensure the capture of an offending transaction Given that each MAX transaction and subtransaction will already have instance metrics the benefits of this will be seen in the collection of subtransactions that were normally not being traced The last statement is due to the fact that a monitoring policy may preclude the collection of all subtransactions within WebSphere and possibly other applications from occurring during normal monitoring To enable a complete breakdown of the transaction all instrumentation agents collect all data when the trace flag is present Sibling transaction ordering Sibling transaction ordering is the ability to determine the order of execution of a set of child transactions relative to each other However when ordering End to End e business Transaction Management Made Easy sibling transactions from data collected across multiple systems the information gathered may not be entirely correct because of time synchronization issues In case the system clocks on all the machines involved are not synchronized the recorded data may show sibling transaction ordering sequences that are not entirely correct This will not affect the overall flow of the transaction only the presentation of the ordering of child transacti
301. his project you will get the error message shown in Figure 6 5 on page 196 that is you end up with an orphan project that is not displayed in the Rational Administrator tool and the name of which cannot be reused Chapter 6 Keeping the transaction monitoring environment fit 195 Rational Administrator e ki 1 The Project name already exists Please enter a different name Figure 6 5 Rational Project exists error message If you find yourself in this unfortunate position the following procedure may help The Rational Administrator maintains its project list under the following registry key HKEY_CURRENT_USER Software Rational Software Rational Administrator ProjectList If you delete the orphan project name from this key you should now be able to reuse it 6 5 4 Removing the J2EE component manually In most instances you should use the Management Server interface to remove the J2EE component from a Management Agent Doing this will remove the J2EE instrumentation from the Web Application Server correctly Occasionally you may find yourself in a situation where the Management Agent is unable to communicate with the Management Server when you need to remove the J2EE component The best way of removing the J2EE component in this situation is to just uninstall the Management Agent as this will also remove the J2EE instrumentation from your Web Application Server Very occasionally you may get yourself into t
302. hotfix There is a hotfix provided in the Rational Robot CD under the folder robot2003Hotfix You can install it by doing the following 1 Close Rational Robot if you are already running it 332 End to End e business Transaction Management Made Easy 2 Search the folder where Rational Robot has been installed for the file rtrobo exe Copy the rtrobo exe file and the CLI bat files provided in the robot2003Hotfix folder into the folder where you found rtrobo exe 3 Open a command prompt in the Rational Robot install folder and run CLI bat This is just a test script if you do not get any errors the fix is working OK and you can close the command prompt Installing the Rational License Server Repeat all the steps in the above section but select the Rational License Server in the Product Selection panel Complete the installation as you did with Rational Robot After setting up the Rational License Server you can install the named user license provided in the Rational Robot CD Installing the Rational Robot License 4 To install the named user license you have to start the Rational License Key Administrator by selecting Start Programs Rational Software and clicking on the License Key Administrator icon The License Key Administrator starts and displays a wizard see Figure 9 12 Rational License Key Administrator ol x ei license Revs Sattiigs Hel The License Key Administrator Wizard steps you through t
303. ialize the simulation as an ARM ed application and to do this you perform the operations shown in Example 9 4 in the script Example 9 4 Initializing the ARM application handle appl_handle arm_init GenWin 0 0 0 The code in Example 9 4 retrieves an application handle using the ARM API so that the application is universally defined this is needed because with applications that have been ARM instrumented in the source code you might have multiple instances of the same application running at a time Important In order for the TMTP Version 5 2 GenWin component to be able to retrieve the ARM data generated with this Rational Robot script the Application handle needs to use the value GenWin as shown in Example 9 4 Next you need a transaction identifier and you will need one for each transaction your script will simulate 352 End to End e business Transaction Management Made Easy wD Important The second parameter should match the pattern ScriptName where the indicates any characters and ScriptName is the name of the Rational Robot Script Using our example above valid transaction IDs could be MyTransaction and MyTransactionSubtransaction1 The third parameter is the description which will be displayed in the TMTP Topology view so it should be a value that will provide useful information when viewing the Topology As you can see the application handle is sent to the ARM API and a transact
304. ication 14 duration 214 dynamic data tables 382 E ease of use 32 e business application 14 38 80 architecture 81 infrastructure 80 management 40 patterns 22 e business performance 38 Edge Aggregation 71 effectiveness 204 EJB performance 163 encryption 356 464 endpoint database 382 Endpoint Group 265 end to end view 376 Enterprise Application Integration 8 enterprise transaction 5 33 Enterprise Transaction Performance 58 environment variable 106 ETL central data warehouse 379 data mart 379 381 process 394 processes 404 source 379 target 379 upgrade log files 392 ETL processes 380 ETL programs 378 ETL1 upgrade 392 ETL1 name 389 event 168 169 224 class 168 data 214 notifications 31 view 216 event generation 240 exchange certificate 101 extract data 378 Index 485 extreme case reports 413 extreme value 413 F facttable 414 facttables 381 filtering Big Board 215 format data mart 379 framework xxiii 28 60 77 functionality 32 G gathering data 34 gathering data 382 General report 296 general management 15 topology 222 generating JKS files 93 KDB files 98 STH files 98 Generic Windows 229 GenWin 233 GenWin 195 363 365 471 deploy 365 limitations 234 placing 80 recording 233 ggregated correlation 71 graph QoS 213 STI 213 GUI script 344 record 345 guidelines 22 H hacking 24 health monitoring policy 222 health check reports 408 heap size control 385 Help Desk 19 helper
305. ice spanning multiple components a typical J2EE application architecture is described in 3 6 Putting it all together on page 80 where the determination of a problem s origin requires some intelligence based on predefined rules or correlation This requires expertise in the way the Chapter 1 Transaction management imperatives 7 application is designed and the ability to include this expertise in the problem resolution process Another set of problems is posed by the ability to federate multiple applications from the J2EE platform using Enterprise Application Integration EAI to connect to existing applications the generation of complementary transactions with external systems or the inclusion of Web Services This capability brings the application closer to the business process than before since multiple steps or phases of the process which were performed by separate applications are now integrated The use of discrete steps in a business process allowed for a manual check on their completion a control that is no longer available in the integrated environment and must be replaced by data coming from infrastructure management This has consequences not only on where the data should be captured but also on the nature of the data itself Finally the complexity of the application created by assembling diverse components makes quality assurance QA a task that is both more important than ever and almost impossible to complete with t
306. ies essentially due to the inability of the solutions used to automatically model the infrastructure supporting an application or a business process This proved to be a problem already in client server implementations where applications spanned multiple infrastructure components This problem is magnified in J2EE implementations 1 2 1 The impact of J2EE on infrastructure management J2EE architecture brings important changes to the way an application is supported by the underlying infrastructure In the distributed environment a direct relationship is often believed to exist between the hardware resources and the application performance Consequently managing the hardware resources by type network servers and storage is often thought to be sufficient J2EE infrastructure does not provide this one to one relation between application and hardware resource The parameters driving the box performances may reflect the resource usage of the Java Virtual Machine JVM but they cannot be associated directly with the performance of the application which may be driven either by its own configuration parameters within the JVM or by the impact of external component performances The immediate consequence on infrastructure management is that a specific monitoring tool has to be included in the infrastructure management solution to care for the specificities of the J2EE application server and that the application has to be considered as a serv
307. imit is reached MaxAggregators 1000000 This is the maximum number of unique aggregators to keep in memory for any one hour period It is advisable to have this set as high as possible given your memory limit desires for the Management Agent Warnings will be logged when this limit is reached and the old aggregator in memory will be flushed to disk Application Dfile applications dat The file name to store previously seen applications RawTransactionQueueSize 500 This is the maximum number of simultaneously started transactions that have not yet completed that TMTP will allow 186 End to End e business Transaction Management Made Easy CompletedTransactionQueueSize 250 This is the maximum size of the completed transaction queue These are transactions that have completed and are awaiting processing When this limit is reached the ARM STOP call will block while it waits for transactions to be processed and space to be freed This can be raised at the expense of memory to allow your system to handle large rapid bursts of transactions to occur without noticeable slowdown of the response time Most of the other Key Value pairs in this file are legacy and do not have any effect on the behavior of the agent ARM Engine log file As described above the Management Agent ARM engine by default sends all trace logs to one of the following files Windows C Program Files ibm tivolii common BWM logs tapmagent log UNIX usr ibm tivoli commo
308. in 6 1 1 Checking MBeans on page 182 Open a browser and go to the address http MAHost 6969 where MAHost is the host name of the Management Agent you wish to check a Select Find an MBean b Select Submit Query c Select TMTP type MAPolicyManager Verify that your policy is listed here the URI pattern you have specified in the policy will be listed Possible problem If the policy does not exist but you selected Send to Agents Now in your policy then there was a problem sending the policy from the Management Server to the Management Agent Possible solution To get the policy a Select pingManagementServer Chapter 6 Keeping the transaction monitoring environment fit 189 b Select Invoke Operation Click Back twice and then press F5 to refresh the screen Verify that your policy is listed here If this has not fixed your problem you may have encountered a defect and should open a PMR with IBM Tivoli Support gt Verify that ARM is receiving transactions This step will verify that ARM is using your listening policy correctly and that J2EE is submitting ARM requests Open the ARM engine log file in which is located in the Tivoli Common Directory On Windows it is located in C Program Files ibm tivoliicommon BWM logs tapmagent log Search this file for arm_start If it exists then J2EE is correctly instrumented and making ARM calls Possible problem If arm_start does not exist then J2
309. in page display gt Playing back the transaction The Generic Windows component plays back the recorded transaction and measures response times 2 3 Reporting and troubleshooting with TMTP WTP One of the strengths of this release of TMTP is its reporting capabilities The following subsections introduce you to the various visual components and reports that can be gathered from TMTP and the way in which these could be used Troubleshooting transactions with the Topology view Your organization has installed TMTP V5 2 and it has been configured to send e mail to the TMTP Administrator as well as sending an event to the Tivoli Enterprise Console upon a transaction performance violation Using the following steps the TMTP administrator identifies and analyzes the transaction performance violation and ultimately identifies the root cause After receiving the notification from TMTP the Administrator would log onto TMTP and access the Big Board view shown in Figure 2 3 See Big Board 2 B ouick listen E BR quickbeam tiviab austin ibm com J2EE 2003 08 25 16 27 14 6 03 goes above 5 sec 6 023 6 016 6 03 A pb j2ee adminconsole2 fA ful tagamet tiviab austin ibm com STI 2003 08 25 14 29 25 3 469 above 1 sec 3 469 3 469 3 469 E tacamet admin console HX 4 tagamet tiviab austin ibm com J2EE 2003 08 25 14 20 40 0 237 0 185 0 089 0 237 E Redirect 0 Hi MH wanderl
310. in your browser after successfully connecting to the MBean Servers HTTP adapter mmand Ci Internet Explorer loxi and Centre Micr Fie Edt View Favorites Tools Help Address sa http tmtpma xp 6969 z Co Figure 6 3 MBean Server HTTP Adapter Some of the functions that can be performed from this interface are gt List all of the MBeans gt Modify logging levels gt Show change attributes of MBeans Chapter 6 Keeping the transaction monitoring environment fit 183 gt View the exact build level of each component installed on a Management Agent or the Management Server gt Stop and start the ARM agent without stopping and starting the Tivoli TransPerf service daemon gt Change upload intervals from the Management Server 6 2 Configuring the ARM Agent The ARM engine uses a configuration file to control how it runs the amount of system resources it uses and so on The name of this file is tapm_ep cfg This file is created on the Management Agent the first time the ARM engine is run The location of this file is one of the following Windows MA_DIR arm apf tapm_ep cfg UNIX MA_DIR arm apf tapm_ep cfg Where MA_DIR is the root directory where the TMTP Version 5 2 agent is installed The contents of this file are read when the ARM engine starts In general you will not have to change the values in this file as the defaults will cover most environments If changes are made to this file they are not loaded
311. ind your environment you must upgrade to one of the supported versions and rerun the Java Enabler For a list of supported environments see Supported Foundation Class Libraries link under the program s Help menu Using the ARM API in Robot scripts Rational Robot uses the SQABasic script language which is a superset of Visual Basic Since the ARM API is a set of C functions these functions must be declared to Robot before they can be used to define measurement points in SQABasic scripts This is best illustrated with an example We used Robot to record a simple user transaction opening Windows Notepad adding some text and closing the window This created the following script which contains the end user actions Sub Main Dim Result As Integer Initially Recorded 1 31 2003 4 12 02 PM Script Name test1 Window SetContext Class Shell_TrayWnd Toolbar Click ObjectIndex 2 ItemText Notepad Coords 10 17 Window SetContext Caption Untitled Notepad InputKeys hello MenuSelect File gt Exit 450 End to End e business Transaction Management Made Easy Window SetContext Caption Notepad PushButton Click Text No End Sub We added the following code to the script 1 Load the DLL in which the ARM API functions reside and declare those functions This must be done right at the top of the script Note that the first line here is preceded by a single quote it is a comment line Declare AR
312. indows System Pruning If you have established a schedule to automatically run the data mart ETL process steps on a periodic basis occasionally manually prune the logs in the directory DB2DIR logging The BWM_m05_s050_mart_prune step prunes the hourly daily weekly and monthly fact tables as soon as they have data older than three months If you schedule the data mart ETL process to run daily as recommended you do not need to schedule pruning separately Duplicate row problem due to Source ETL process hangs Problem The TMTP Version 5 2 process BWM_c10_cdw_process hangs and you restart the Data Warehouse or DB2 When you then try to rerun the BWM_c10_cdw_process you will get duplicate row problem see Figure 6 4 on page 192 This is because the TDW keeps a pointer to the last record it has processed If the TDW is restarted during processing the pointer will be incorrect and the BWM_c10_cdw_process may re process some data Chapter 6 Keeping the transaction monitoring environment fit 191 DB2 Message y E xj DWC07356E An agent s processing of a command of type runUDP failed for edition 0 of step BYVM_c10_s030_transform_loaq CDVW8087E IBM CLI Driver DB2 NT SQLO803N One or more values in the INSERT statement UPDATE statement or foreign key update caused by a DELETE statement are not valid because the primary key unique constraint or unique index identified by 2 constrains table TWG COMPATTR fram having d
313. iness Transaction Management Made Easy WAS_HOME bin admin config where WAS_HOME is the directory where you have installed your WebSphere Application Server gt To monitor performance data for your IBM WebSphere administration and application servers you must enable IBM WebSphere Application Server to collect performance data Each performance category has an instrumentation level which determines which counters are collected for the category You can change the instrumentation levels using the IBM WebSphere Application Server Resource Analyzer On the Resource Analyzer window you need to do the following Right click on the application server instance for example WebSiteAnalyzer and choose Properties click on the Services tab and select Performance Monitoring Settings from the pop up menu to display the Performance Monitoring Settings window Select Enable performance counter monitoring Select a resource and choose None Low Medium High or Maximum from the pop up icon The color associated with the chosen instrumentation level is added to the instrumentation icon and all subordinate instrumentation levels Click OK to apply the chosen setting or Cancel to undo any changes and revert to the previous setting Table 5 1 lists the minimum monitoring levels for the IBM Tivoli Monitoring for Web Infrastructure WebSphere Application Server Resource Models Table 5 1 Minimum monitoring levels WebSphere Application
314. inet There is no easy alternative solution as the Rational Robot requires access to the screen context while it is playing back During the writing of this redbook we attempted a number of mechanisms to achieve this result including use of Windows XP Switch User functionality without success The following Terminal Server solution implemented at one IBM customer site was suggested to us We were unable to verify it ourselves but we considered it useful information to provide as a potential solution to this problem This solution relies on the use of Windows Terminal Server which is shipped with the Windows 2000 Server When a user runs an application on Terminal Server the application execution takes place on the server and only the keyboard mouse and display information is transmitted over the network This solution relies on running a Terminal Server Session back to the same machine and running the Rational Robot within the Terminal Server session This allows the screen to be locked and the simulation to continue running 1 Ensure that the Windows Terminal Server component is installed If it is not it can be obtained from the Windows 2000 Server installation CD from the Add On components dialog box see Figure B 20 on page 469 468 End to End e business Transaction Management Made Easy Microsoft Windows 2000 CD Xx Install Add On Components Customize your Windows 2000 experience with a variety of optional components Fi
315. ing Interface machine allowing end users to obtain reports from data stored in the data marts AIX 4 3 3 AIX 4 3 3 DB2 Server DB2 Server DW Central Data Warehouse ITMTP Database ITMTP TEDW Server Database Server TMTP e Sab Database CEN a Reporting data using OLAP and business inteligence tools See TWH_CWD a Web Browsers Data Mart aw connecting to the Report Interface A Reporting Lo g ee Cer Sic fa Cee H Windows 2000 TEDW Control Center Server m DB2 Client ITM ETL TEDW Reporting Interface Tivoli Presentation Services TWH_M TEDW Control Center TEDW Reporting Interface Figure 10 4 Tivoli Enterprise Data Warehouse installation scenario 10 1 4 Setting up the TMTP Warehouse Enablement Packs The following sections describe the procedures that need to be performed in order to install configure and schedule the warehouse modules for the IBM Tivoli Monitoring for Transaction Performance product The description of the installation steps is based on our lab environment scenario described in Figure 10 4 It is assumed that the Tivoli Enterprise Data Warehouse environment Version 1 1 is already installed and operational Details for achieving this can be found in the redbook ntroduction to Tivoli Enterprise Data Warehouse SG24 6607 Chapter 10 Historical reporting 383 Throughout the following sections the Warehouse Enablement Pack for IBM Tivoli Monitoring for Trans
316. ing proxy After that the machine needs to be rebooted Click on Next on the screen shown in Figure 4 43 on page 128 Chapter 4 TMTP WTP Version 5 2 installation and deployment 127 net Install Store and Forward Agent 10 x Installation of the WebSphere Caching Proxy requires a system reboot The installation program will resume after reboot Figure 4 43 The WebSphere caching proxy reboot window 11 After the reboot the installation resumes and configures the WebSphere Caching proxy and the Store and Forward agent Click on Finish Figure 4 44 on page 129 to finish the installation 128 End to End e business Transaction Management Made Easy net Install Store and Forward Agent aoli The InstallShield Wizard has successfully installed IBM Tivoli Monitoring for Transaction Performance Store and Forward Agent Choose Finish to exit the wizard installshieiii n Figure 4 44 The final window of the installation 12 We will now deploy the Store and Forward agent for the Internet zone frankfurt itsc austin ibm com This Store and Forward agent will connect to the Store and Forward agent in the DMZ canberra itsc austin ibm com We follow the same installation steps for the previous Store and Forward agent The different parameters can be found Table 4 3 Table 4 3 Internet Zone SnF different parameters Parameter Value Proxy URL https canberra itsc austin ibm com 2443 SnF Host Name fully qualified
317. ingle point of failure There are a number of technologies available to allow centralized monitoring and surveillance of the e business infrastructure components These technologies will help manage the IT resources that are part of the e business solution This chapter provides a brief discussion on implementing additional Tivoli management tools that will help ensure the availability and performance of the e business platform as well as how to integrate TMTP with them including integration with the following gt Configuration of TEC to work with TMTP gt Configuration of ITM Health console to work with TMTP Setting SNMP Setting SMTP v v Copyright IBM Corp 2003 All rights reserved 153 5 1 Managing and monitoring your Web infrastructure e business transaction performance monitoring is important however it is equally important to ensure that the TMTP system itself as well as the entire Web infrastructure is running correctly One of the prerequisite components for implementing TMTP is WebSphere Application Server which in turn may rely on a prerequisite Web server for example IBM HTTP Server Without these components up and running the TMTP will not be accessible or worse will not work correctly The same reason is true for the database support needed by TMTP The IBM Tivoli Monitoring products provide the basis for proactive monitoring analysis and automated problem resolution A suite of solutions known as the
318. ion handle is retrieved Example 9 5 Example 9 5 Retrieving the transaction handle getid_handle a rm_getid app _handle MyTransaction LegacySystemTx 0 0 0 Now you can start the transaction The line below Example 9 6 needs to precede the script steps where the transaction you want to measure takes place Example 9 6 Specifying the transaction start start_handle arm_start getid_handle 0 0 0 Again ARM gets a handle ad returns another in this case it gets the transaction handle you got and returns a start handle The handle is needed to end the right transaction After the transaction completes with a successful Verification Point you need to end the transaction using the call in Example 9 7 Example 9 7 Specifying the transaction stop stop_rc arm_stop start_handle 0 0 0 0 This will close the transaction As you can see we ensure that we are closing the transaction by starting the stop call which includes the transaction start handle The last call Example 9 8 you need is for cleanup purposes and can be included at the end of the script The end call sends the application handle you received with the initialization Example 9 8 ARM cleanup end_rc arm_end app _handle 0 0 0 This will complete the set of API calls for the transaction you are simulating Chapter 9 Rational Robot and GenWin 353 Compile the script Rational Robot scripts are compiled before playback begins The compilation can be
319. ion time the number of subtransactions in each business transaction retry count lap time and timeouts In Version 5 2 of IBM Tivoli Monitoring for Transaction Performance the capabilities of STI have been greatly improved and now includes features like Enhanced URL matching Multiple windows support Enhanced meta refresh handling XML parser support Enhanced JavaScript support YYYY Y 230 End to End e business Transaction Management Made Easy However despite all of these enhancements a few limitations still apply Limitations of Synthetic Transaction Investigator When working with STI you might encounter any of the following behaviors Multiple windows transactions The recorder and player cannot track multiple windows Multiple JavaScript requests Example 8 1 JavaScript call The recorder and player cannot process JavaScript that updates the contents of two frames When you click the Change frame source button the newSrc javaScript call executes function newSrc Example 8 1 illustrates this behavior parent document getElementById myLeftFrame src frame_dynamic htm parent document getElementByld myRightFrame src page2 htm1 Dynamic parameters JavaScript alerts Modal windows Server side redirect The content of both the left and the right frame are updated but STI only records the first URL navigation the one to the left frame of the two invoked by this JavaScript Certain param
320. ions more effectively in your environment For more information ibm com redbooks
321. ipt Name TestEncryptedPassword Dim Result As Integer Dim bf As Object Dim strPasswd As String Dim fchar Dim x As Integer Create the Encryption Engine and store a key Set bf CreateObject EncryptionAlgorithms BlowFish bf key ibm Open file and read encrypted password Open C encryptedpassword txt For Input Access Read As 1 Redim fchar Lof 1 For x 1 to Lof 1 2 fchar x Input 1 1 strPasswd strPasswd amp fchar x Next x Decrypt the password into variable strPasswd bf DecryptString strPasswd rational Window SetContext Caption Program Manager Appendix B Using Rational Robot in the Tivoli Management Agent environment 467 ListView Db1Click ObjectIndex 1 ItemText Internet Explorer Coords 20 30 Window SetContext Caption IBM Intranet Microsoft Internet Explorer ComboEditBox Click ObjectIndex 2 Coords 61 5 InputKeys http 9 3 4 230 9082 tmtpUI ENTER InputKeys root TAB LEFT use the un encrypted password retrieved from the encrypted file InputKeys strPasswd PushButton Click HTMLText Log On Toolbar Click ObjectIndex 4 ItemID 32768 Coords 20 5 PopupMenuSelect Close End Sub Rational Robot screen locking solution Some users of TMTP have expressed a desire to be able to lock the screen while the Rational Robot is playing The best and most secure solution to this problem is to lock the endpoint running simulations in a secure cab
322. ipt from the text in Example 9 9 on page 357 and then running the resulting script End to End e business Transaction Management Made Easy Example 9 9 Stashing obfuscated password to file Sub Main Dim Result As Integer Dim bf As Object Dim answer As Integer Create the Encryption Engine and store a key Set bf CreateObject EncryptionAlgorithms BlowFish bf key ibm Begin Dialog UserDialog 180 90 Password Encryption Text 10 10 100 13 Password 1b1Pwd Text 10 50 100 13 Filename lblFile TextBox 10 20 100 13 txtPwd TextBox 10 60 100 13 txtFile OKButton 131 8 42 13 CancelButton 131 27 42 13 End Dialog Dim myDialog As UserDialog DialogErr answer Dialog myDialog If answer lt gt 1 Then Exit Sub End If If Len myDialog txtPwd lt 3 then MsgBox Password must have more than 3 characters 64 Password Encryption GoTo DialogErr End If Encrypt strEncrypt bf EncryptString myDialog txtPwd rational Save to file Open C secure txt For Output Access Write As 1 Write 1 strEncrypt Open myDialog txtFile For Output As 1 If Err lt gt 0 Then MsgBox Cannot create file 64 Password Encryption GoTo DialogErr Chapter 9 Rational Robot and GenWin 357 358 End If Print 1 strEncrypt Close 1 If Err lt gt 0 Then MsgBox An Error occurred while storing the encrypted password 64 Password Encryption GoTo DialogErr End If
323. ive Web and application server specific events are generated by the Resource Models provided by each of the IBM Tivoli Monitoring for Web Infrastructure modules These events are defined in TEC and a set of predefined rules exists to correlate and process the events To set up a TEC environment capable of receiving Web and application server related events from IBM Tivoli Monitoring for Web Infrastructure environment at least the following components have to be installed gt Tivoli Enterprise Console Server Version 3 7 1 gt Tivoli Enterprise Console Version 3 7 1 gt Tivoli Enterprise Console User Interface Server Version 3 7 1 End to End e business Transaction Management Made Easy gt Tivoli Enterprise Console Adapter Configuration Facility Version 3 7 1 TEC also uses a RDBMS system in which events are stored Please refer to the IBM Tivoli Enterprise Console User s Guide Version 3 8 GC32 0667 for further details on TEC installation and use IBM Tivoli Monitoring for Web Infrastructure events and rules In order to define the IBM Tivoli Monitoring for Web Infrastructure related events and rules to the TEC the proper definition files have to be imported into the TEC environment The IBM Tivoli Monitoring for Web Infrastructure events and rules are described in files that have baroc and rls file extensions All the files can be found in the directory in which the Tivoli Enterprise Console server code is installed in the subdirecto
324. k Alt b Next Alten gt Finish At Cancel Alte Figure 9 45 Specify Agent Group 7 Give the Playback Policy a name description and specify if you want the policy pushed out to the agents immediately or at the next polling interval by default polling intervals are every 15 minutes see Figure 9 46 on page 374 Chapter 9 Rational Robot and GenWin 373 374 Tivoli Monitoring for Transaction Performance Configuration Work with Discovery Work with Listening F Work with Playback F Work with Agent Gror Work with Transactio Work with Realms vReports View Big Board View General Reports View Component Eve b System Administrati b Downloads edule e Agent Group Assign Name Name Description Sent to Agents at next interval Send to Agents now R lt Back Alt b Next Altt n gt Finish Alt f l Cancel Alt c oils afl Figure 9 46 Assign your playback policy a name 8 Press the Finish button The Rational Robot scripts associated with your transaction recording will now be pushed out from the Management Server to the Rational Project located on each of the Management Agents in the specified Agent Group and the associated schedule will be applied to script execution End to End e business Transaction Management Made Easy 10 Historical reporting This chapter discusses methods and processes of collecting business transactio
325. k Next Figure 4 47 on page 132 Chapter 4 TMTP WTP Version 5 2 installation and deployment 131 Install Management Agent a 15 x InstallShield Click Next to install the management agent to this folder or click Browse to install to a different folder sey Directory Name Ra C Program FilesiiBMiTivoliimMa Browse Cancel Figure 4 47 Installation location definition 6 In Figure 4 48 on page 133 we specify the parameters for the Management Agent connection Host Name As we are in the intranet zone the Management Agent will directly connect to the Management Server We specify the Management Server s host name as ibmtiv4 itsc austin iom com User Name User Password We have to specify a user that has the agent role on the WebSphere Application Server which is the same as the Management Server in our environment We specify the root account Enable SSL We select this option since we have a secure installation of the Management Server Use default port number As the Management Server is using the default port number we select Yes at this option Proxy protocol Proxy Host Port number As we are not using proxy we specify the No proxy option SSL Key Store file oassword We previously created a custom JKS file to serve the agent connections so we specify the prodagent jks file and its password 132 End to End e business Transaction Management Made Easy ma Install Management Agent Fo
326. l Create Playback Policy trade_2_check_tivlab01 Playback Settings Number of Retries Retry Lag Time lt Choose Agent Group 3 3 Seconds Assign Name Timeout Period i 30 Seconds Cookie Cleaning Cache Cleaning Iteration z Iteration I Enable Page Analyzer Viewer M Abort On Violation CES lt Back Alt b amenes Finish Alt Cancel Alt c 4 gt FS Work with Playback Policies Choose Create Edit etc iea a ee Local intranet A Figure 8 14 Configure STI Playback 2 Fill in the specific properties for the STI playback policy you are defining in the Create STI Playback dialogs These are made up of seven sub dialogs each covering different aspects of the STI Playback The seven subsections are Configure STI Playback Configure STI Settings Configure QoS Settings Configure J2EE Settings Choose Schedule Choose Agent Group Assign Name The following sections highlights important issues that should be aware of when defining STI playback policies For a detailed description of all the properties please refer to BM Tivoli Monitoring for Transaction Performance User s Guide Version 5 2 0 SC32 1386 Please note that in order to proceed to the next dialog in the STI Playback creation chain just click on the Next button at the bottom of each dialog 252 End to End e business Transaction Management Made Easy Configure STI Playback Select the appropriate Playback
327. l be adequate for the transaction s you will be recording Please see Figure 8 8 on page 246 for an example When ready to start recording press Enter Note If the Completion Time is set too low a browser action in the recording can cause STI to perform unnecessary actions or fail during playback Setting a Completion Time that is too low is a common user error Chapter 8 Measuring e business transaction response times 245 246 MASTI Recorder 5j xj Location l ittp ibmtivS trade appl Completion Time Progress Reset Transaction Save Transaction Back Forward Refresh 0 escana I Repaint om wait up to 10 seconds Monitoring for Transaction Performance Version 5 2 Figure 8 8 STI Recorder is recording the Trade application Copyright 1990 2003 ByIBM Corporation All Rights Reserved See product license for details JAVA 4 Wait until the progress bar shows Done and start recording the desired transactions Important If the Web site you are recording a transaction against uses basic authentication that is you are presented with a pop up window where you need to enter your user ID and password you will need to write down the realm name user ID and password needed for authentication to the site This information is required in order to create a realm within TMTP The procedure to create a realm is provided in 8 4 6 Working with realms on page 255 5 When finished pr
328. lability Intermediate Manager see the following note If the port number is specified as zero 0 or it is not specified the port number is retrieved using the portmapper The ServerPort keyword is optional and not used when the TransportList keyword is specified Heddtd E He Ee AA AAAA Eee ee Ea a Ea a ae a ee ee ae a a a ServerPort 5529 3 Set the port number for the Management Server 4 Shut down and restart WebSphere Application Server on the management server system To shut down and restart WebSphere Application Server use the stopserver lt servername gt command located in the WebSphere AppServer bin directory 172 End to End e business Transaction Management Made Easy 5 2 1 Configuration of ITM Health Console to work with TMTP Use the User Settings window shown in Figure 5 7 on page 174to change any of the following optional settings gt Time zone shown for time stamps in the user interface gt Web Health Console usernames passwords and server This information enables IBM Tivoli Monitoring for Transaction Performance to connect to the Web Health Console The Tivoli Web Health Console presents monitoring data for those IBM Tivoli Monitoring products that are based on resource models For example the Web Health Console displays data captured by products such as IBM Tivoli Monitoring for Databases and IBM Tivoli Monitoring for Business Integration gt Refresh rate for the Web Health Console display Keep
329. lated User Name J2EE lava Applet Window Figure 2 8 Inspector viewing metrics Using these steps the administrator has very quickly determined that the cause of the poor performance is a particular servlet and the root cause is a specific method Timer doGet of that servlet Narrowing the problem down this quickly to a component of an application would previously have taken a lot of time and effort if it was ever discovered at all Often it is all just a little too hard to find the problem and the temptation is to buy more hardware This administrator has just saved his organization the expense of purchasing additional hardware because of a poorly performing servlet method Other reports provided with TMTP Some of the other reports available from within TMTP are shown in this section Overall Transactions Over Time This report Figure 2 9 on page 49 can be used to investigate the performance of a monitored transaction over a specified period of time 48 End to End e business Transaction Management Made Easy 2 Sa 8 98 tmtpma xp itsc austin ibm com Y tmtpmb xp itsc austin ibm com 875 O 0 0 0 0 0 0 0 0 0 0 0 0 0 0 9 0 0 0 0 0 0 45 Seconds 2 25 10 05 10 05 10 06 10 06 10 06 16 00 22 00 04 00 10 00 16 00 Time Figure 2 9 Overall Transactions Over Time Transactions with Subtransactions This report Figure 2 10 on page 50 can be used to investigate the performance of a monitored transaction
330. lation with J2EE application 8 8 4 Event analysis and online reports for Pet Store If we analyze the Pet Store business process from login to submit from the Pet Store Web site we have a total of nine steps 1 Log in to Pet Store site 2 Select pet 3 Select product category 4 Select view items for this product category 5 Add to cart 6 View the shopping cart 7 Proceed to checkout 8 Supply order information 9 Submit 316 End to End e business Transaction Management Made Easy STI QoS and J2EE combined scenario We want to find the User Experienced Time and the Back End Service Time for end users buying pets the e business way Since we cannot control the behavior of users STI is used to run the same transaction consistently To facilitate this an STI playback policy is created to run a simulated Pet Store transaction named petstore_2_order Petstore_2_order is configured to allow correlation with the back end J2EE monitoring The Transaction with Subtransaction report shown in Figure 8 65 shows that the total simulated end user response time for Pet Store playback policy is 8 12 sec It also shows that five subtransactions has been executed and that subtransaction number 3 is responsible for the biggest part of the total response time This report is very helpful to in order to identify over a longer period of time which subtransaction traditionally contributes most to the overall response time 4a sactio
331. le also referred to as the ISC Additional Information The Integrated Solutions Console is the portal for the Web Health Console These consoles run on an installation of the WebSphere Application Server ISC Username Name of a valid user account on the computer for the Integrated Solutions Console ISC Password Password of the user account gt Type the Internet address of the Web Health Console server in the WHC Server text box in the following format http host_computer_name LaunchITM WHC where host_computer_name is the fully qualified host name for the computer that hosts the Web Health Console Note The Web Health Console is a component that runs on an installation of WebSphere Application Server IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer sa 10 x Fie Edt View Favorites Tools Help Ea x w Tivoli Monitoring for Transaction Performance t E za User Name root a MyWork b Configuration Configure User Settings gt Reports eetan ad YSystem Administration Time Zone Work with Agents GMT 06 00 Central Standard Time zl Configure System Event Details Component Management Configure User Settings Work with Event Responses View System Events View Log Files View Management Server Deta b Downloads I Automatically adjust for Daylight Savings Time TME Host name TME Username x220svr austin ibm com webhcO1 TME Password ISC Use
332. le 15 minutes to ensure that only small amounts of data have to be processed The usage pattern requirements for up to date data of the data in the data warehouse should be used to determine which strategy to follow Note Since TEDW does not allow you to change the schedule once the operation mode has been set to Production you need to demote the mode of the processes to Development or Test if you want to change the schedule and do not forget to promote the mode of the processes back to Production to activate the new schedule Chapter 10 Historical reporting 403 Changing the ETL status to Production All IBM Tivoli Monitoring for Transaction Performance ETL processes are composed by components that have the Development status set by default In order for them to run their status need to be changed from Development to Production The following steps must be performed for all processes corresponding to your Warehouse Enablement Pack Table 10 4 provides the complete list In the following steps we use BWM_c10_CDW_Process as an example to describe the process Table 10 4 Warehouse processes and components Warehouse Components enablement pack BWM_c10_CDW_Process BWM_c10_s010_pre_extract BWM_c10_s020_ extract BWM_c10_s030_transform_load BWM_m05_Mart_Proces prepare_stage mart_pre_extrat mart_extract mart_load mart_rollup mart_prune On the TEDW Control Center server using the Data Warehouse Center wi
333. le database _lUse an existing DB2 database Install D82 SSS Tivoli software InstallShield lt Back Cancel Figure 4 57 Database options window gt Figure 4 58 on page 144 we have to specify the DB2 administration account We set this account to db2admin We also check the Create New User check box so the user will be automatically created during the setup procedure Chapter 4 TMTP WTP Version 5 2 installation and deployment 143 Tivoli software Database User Account ype the required information in the text boxes Specify an administrative user for the database that you want the management server to use v A fhome db2admin Figure 4 58 DB2 administrative user account specification gt We specify db2fenc1 as the user for the DB2 fenced operations This is the default user see Figure 4 59 on page 145 144 End to End e business Transaction Management Made Easy A x Tivoli software Fi Pea ype the required information in the text boxes Specify a UNIX user that eo can perform fenced operations in DB2 Vv AN fhome db2fenc1 R Figure 4 59 User specification for fenced operations in DB2 gt We specify the db2inst1 user as the DB2 instance user The inst1 instance will hold the TMTP database see Figure 4 60 on page 146 Chapter 4 TMTP WTP Version 5 2 installation and deployment 145 Install the Management Server ype the required information in the text boxes Specif
334. li Monitoring for Transaction Performance Microsoft Internet Explorer File Edit View Favorites Tools Help Address http tivdces itsc austin ibm com 9082 tmtpULjsp console WcFrameManager jsp Tivoli Monitoring for Transaction Performance User Name administrator My Work Configuration Create Discovery Work with Agent Groups Work with Discovery Policies Policy Work with Listening Policies Pear itai f A Work with Playback Policies opngun ide Create New Alt w Work with Schedules e Work with Agent Groups Agent Groups Work with Transaction Recordings Work with Realms gn ne 2 Please make a selection Go Alt g b Reports b System Administration Name STI Qos b Downloads ibrntiv9 itsc austin ibm com 82 petstore_j2ee_grp petstore_gqos_grp gos_grp sti_grp tivlabO1 itsc austin ibr com 80 C trade_j2ee_grp Page 1 lt Back Alt b Next Alt n gt Finish Alt f lI Cancel Alt c Figure 8 25 Selecting Agent Group for QoS discovery policy deployment 4 Before performing the final step you have to select the group s of QoS Agents that the newly created QoS discovery policy will be distributed to Select the appropriate group s and click Next 5 Finally you have to provide a name In this case trade_qos dis is used Also determine if the profile is to be sent to the agents in the Agent Group s immediately or wait until the next
335. lib ext core_util jar C beaHom e701 weblogic700 server 1ib ext armjni jar C beaHome701 weblogic700 server lib ext eppam jar rem End TMTP AppID169 4 Point a Web browser to the WebLogic Server Console The address will be something similar to http myHostname com 7001 console 5 In the left hand applet frame select the domain and server that was configured with J2EE Instrumentation Click on the Remote Start tab of the configuration for the server see Figure 6 8 Ai ViebLogic Server Console Microsoft Internet Explorer Cer Fis Edt Wew Favorkes Tods Help a Q x aA Da feres Que O Z B D http nivet qeyO yatie 700 1 console factions mbeanMBeanFranesetAction sidebaFrameld a_oonsole_frane_10E89023544 1 02dNewetakebframeldaw_consale fram EJ co i A p x domain gt Servers gt thinkAndy p Zhea he to tivali geyOyqht 700 Active Domain mydomain Jul 22 2008 2 43 49 PM COT TE Connections Monitoring Control Logging Deployments Services Notes General Cluster Memory f Deployment f Tuning f Compilers Health Monitoring Remote Start 5 Qbeptoynents i A JavaHome amp SWappiications amp BEAHome A amp P Root Directory amp Class Path amp Arguments Security Policy File a Glmessagny Bridge Syme 4 Username Ours a Asme amp Password Change eww 5 weblogic Tucedo Connect g Rooke ES E oplet sated 2 Local intranet Figure 6 8 WebLogic class path and argument setting
336. lication provider can gt Set the users expectations by providing sufficient information up front gt Make sure that the back end transaction performance is as fast as possible Neither of these will guarantee that users will return to the application but monitoring and measuring the total response time and breaking it down into the 32 End to End e business Transaction Management Made Easy various components shown in Figure 1 1 on page 4 will give the application owner an indication of where the bottlenecks might be To provide consistently good response times from the back end systems the application provider may also establish a monitoring system that generates reference transactions on a scheduled basis This will give early indications about upcoming problems or adjust the responsiveness of the applications The need for real time monitoring and gathering of reference and historical data among others are addressed by IBM Tivoli Monitoring for Transaction Performance By providing the tools necessary for understanding the relationships between the various components that make up the total response time of an application including breakdown of the back end service times into service times for each subtransaction IBM Tivoli Monitoring for Transaction Performance is the tool of choice for monitoring and measuring transaction performance 1 5 1 IBM Tivoli Monitoring for Transaction Performance functions IBM Tivoli Monitoring for
337. lick OK 9 1 3 Recording types GUI and VU scripts 344 The kind of recordings that can be performed with Rational Robot can be divided in two different types gt GUI scripts gt VU scripts GUI scripts are used to record simulations interacting with a graphical application These scripts are easy to use but have the drawback of not allowing more than one script to execute at a time and a requirement to have direct access to the computer desktop screen On the other hand they allow for recording very detailed graphical interaction mouse movements keystrokes End to End e business Transaction Management Made Easy and so on and allow the use of Verification Points to ensure that operations outcomes are those expected The language used to generate the script is SQABasic and GUI scripts can be played back with Rational Robot or as part of Rational Test manager GUI scripts can be used in a set of complex transactions repeated continuously to measure a performance baseline that can be compared when the server configuration changes or to ensure that the end user experience is satisfactory from the end user point of view to satisfy an SLA VU scripts record the client server requests at the network layer only for specific supported application types and can be used to record outgoing calls performed by the client network recording or incoming calls on the server proxy recording VU scripts do not support Verification Point
338. lin390 cp Chapter 4 TMTP WTP Version 5 2 installation and deployment 137 Yw r r 1 root Yw r r 1 root Yw r r 1 root Yw r r 1 root Yw r r 1 root YWw r r 1 root drwxr xr x 5 root drwxr xr x 7 root root root root root root root root root 18960067 24 24 18516023 5632 24665 4096 4096 Sep Sep Sep Sep Sep Sep Sep 16 Sep 16 o 09 09 09 09 09 09 04 09 58 58 58 58 58 58 54 32 setup_MS_sol bin setup_MS_sol cp setup_MS_w32 cp setup_MS_w32 exe startpg exe w32util dl was5 wasFp1 gt We start the installation by executing the following command setup_MS_lin bin gt Atthe management Server installation welcome screen we press Next Figure 4 52 InstallShield Welcome to IBM Tivoli Monitoring for Transaction Performance To continue click Next See the installation guide for detailed descriptions of the installation steps NOTE The installation program installs the required Java Virtual Machine Follow the instructions in this installation program to install the following product component on your computer IBM Tivoli Monitoring for Transaction Performance Management Server Next gt Cancel Figure 4 52 Management Server Welcome screen gt We accept the license agreement and press Next Figure 4 53 on page 139 138 End to End e business Transaction Management Made Easy International Program License Agree
339. line To run the script up to the selected line you have to select Go Until Cursor in the Debug menu or press F6 this will start playback of the script and stop before executing the line that is currently selected At any time you can choose the Step 354 End to End e business Transaction Management Made Easy Over Step Into and Step Out buttons which work as in any other debugging environment One interesting option you have in the Debug menu is the Animate option this will play back the script in Animation Mode Animation Mode plays the script by highlighting in yellow each line that is executed Keep in mind that the script will still playback at considerable speed not giving you time to evaluate what is occurring it is a good idea to increase the delay between key strokes to ensure that you can analyze the execution flow To do this you can change the delay between commands and keystrokes by selecting Tools GUI Playback Options This will display the GUI Playback Options dialog Figure 9 31 GUI Playback Options E 21 x Unexpected Active Window Error Recovery Trap Diagnostic Tools Web Browser Playback Log Caption Matching Wait State m Script control Delay between commands 100 __niilliseconds Use recorded think time Delay between keystrokes 0 milliseconds Use recorded typing delays Skip verification points I Acknowledge results Robot window Minimize Robot Put Ro
340. lly 196 6 6 TMTP Version 5 2 best practices 0 0 cee eee 204 iv End to End e business Transaction Management Made Easy Part 3 Using TMTP to measure transaction performance 05 209 Chapter 7 Real time reporting 0 0002 e eee eee 211 7 1 Reporting overview a ER E ees 212 7 2 Reporting differences from Version 5 1 0200 eee ee eee 212 To The Big Board ore rear e R eld in eee eens ae eee a Rs 213 7 4 Topology Report overview 0 00 e eee 215 FSS TROP OM sa vend ioe ae Beh Biles 0s See ae eae ata 219 7 6 General REPOS a caa Sindee ao aah aMe nis ata boca dock a E cn ia 219 Chapter 8 Measuring e business transaction response times 225 8 1 Preparation for measurement and configuration 227 8 1 1 Naming standards for TMTP policies 04 228 8 1 2 Choosing the right measurement component s 229 8 1 3 Measurement component selection summary 234 8 2 The sample e business application Trade 00008 235 8 3 Deployment configuration and ARM data collection 239 8 4 STI recording and playback 0 00 0c cee eee 241 8 4 1 STI component deployment 0000 cee eee eee eee 241 8 4 2 STI Recorder installation 20 0 0 0c cee ee 242 8 4 3 Transaction recording and registration 00 245 8 4 4 Playback sched
341. lly follow for recording any other application simulation End to End e business Transaction Management Made Easy Recording a GUI simulation on a Java application Before recording a simulation running on Java ensure that you installed and configured the Rational Java Enabler on the JVM you will be using and load the Java Extension To record a GUI simulation on a Java application select the Record GUI Script button on the toolbar in the main Rational Robot window and start the application in the usual way Simulate and perform all the actions that you need Rational Robot will record the simulation while you execute as on any other kind of application There are not any differences between Java simulations and generic Windows applications only the object properties slightly change 9 2 Introducing GenWin The GenWin allows centralized management of distributed playback of your Rational Robot Scripts When you use Rational Robot and Generic Windows together it allows you to measure how users might experience a Windows application in your environment 9 2 1 Deploying the Generic Windows Component In order to play back a Rational Robot script the Management Agent you intend to use for playback must have the Rational Robot installed and it must have the Generic Windows component installed on it The procedure for deploying the Rational Robot is covered in 9 1 1 Installing and configuring the Rational Robot on page 326 The pr
342. lode it to be able to see the sub folders 3 Open the Tables folder 396 End to End e business Transaction Management Made Easy 4 Right click on each table that appears in the right pane of the Data Warehouse Center window and select Properties The properties dialog shown in Figure 10 15 appears fn Data Warehouse Center lolx Warehouse Selected Edit View Tools Help i D Aae aada aaa aoo aA E a Warehouse Sources ee AMX_ITM_RIM_Source AMX_TWH_CDV _Source AMY_TWH_CDV _Source AMY_TWH_MART_Source ANM_AVAIL_Source ANM_TWH_CDW_Source BYiM_TMTP_DATA_SOURCE CJE O views BWM_TWH_CDW_Source BWM_TWH_MART_Source CDW_TAWH_CDW_Source a Warehouse Targets ER AMX_TWH_CDW_Target ER ANtY_TWH_MART_Target mE AMY_TWH_MD_Target EA ANM_TWH_CDW_Target mE ANM_TWH_MART_Target EA ANM_TWH_MD_Target ER BWM_TWH_CDW_Target c G BYWM_TWH_MART_Target FR pia DAH MN Tarnet Index table space Table space B B ic Remove Sample Contents Show Related ea se O F amp Figure 10 15 Warehouse source table properties Note that TEDW inserts a default name in the TableSchema field and that TableName contains the fully qualified name of the table enclosed in quotes 5 Type the name of the table creator or schema to be used in the TableSchema field and remove the creator information including periods and quotes from the TableName field The values
343. low nodes In Figure 2 4 you can see that there were only two slow performing nodes All nodes in the topology have a numeric value on them If the node is a container for other nodes for example a Servlet node may contain four different Servlets the time expressed on the node is the maximum time of what is contained within the node This makes it easy to track down where the slow node resides Once you have drilled down to the bottom level the time on the base node indicates the actual time for that node average for aggregate data and specific timings for instance data In Figure 2 4 the root node J2EE has an icon that indicates that it has had performance violations for that hour The administrator can now select the node that is in violation and click on the Inspector icon The Inspector view Figure 2 5 on page 46 reveals that the threshold setting of goes above 5 seconds was violated nine times out of 11 for the hour and that the minimum time was 0 075 and the maximum time was 6 03 The administrator can conclude from these numbers that this nodes performance was fairly erratic Chapter 2 IBM Tivoli Monitoring for Transaction Performance in brief 45 IBM Tivoli Monitoring for Transaction Performance 10 x E http quickbeam 9080 SerletTest t goes above 5 sec 11 ttp quickbeam 9080 ServletTest Minimum Duration Average Duration Threshold Violated Count Java Applet Window
344. lt a lt Back Alt b Next Alt n gt Finish Alt f Cancel Alt c Figure 8 63 QoS listening policies for Pet Store automatic threshold setting In addition we provided the J2EE settings for the QoS listening policy shown in Figure 8 64 on page 316 in order to ensure correlation between the QoS front end monitoring and the back end monitoring provided by the J2EE component Chapter 8 Measuring e business transaction response times 315 nitoring for Transaction Pei mtpUL jsp console WcFrameMm Tivoli Monitoring for Transaction Performance User Name administrator a l Configuration A k a j Work with Discovery Policies Create Listening Policy Tonnau MEE SAUNAA Work with Listening Policies ree Configure J2EE me M Work with Playback Policies Sergo g Threshold Type Work with Schedules fi hee Work with Agent Groups Performance x Crea Work with Transaction Recordings Work with Realms c e 5 gt Reports i IEE No Entries gt System Administration a gt Downloads Show Enabled Thresholds Show Disabled Thresholds a Advanced Listening Settings Choose Default Configuration High gt Trace Detail Level Off 1 Servlet Cc Session EJB c Entity EJB JMS oO c c 2 3 oC ce ce ce JDBC ce ce oa a0ao005 RMI IIOP Next Alt n gt Finish Alt Cancel Alt c lt Back Alt b do Figure 8 64 QoS corre
345. lt w3c enc type password gt lt CDATA passwd eHh4 gt lt w3c enc gt lt w3c enc type hidden gt lt CDATA action login gt lt w3c enc gt lt content gt lt meta info gt lt meta tag URI gt lt CDATA xl OK Alt 0 N Figure 8 9 Creating STI transaction for trade The XML document will be uploaded to the Management Server so it can be distributed to any Management Agent with the STI component installed To authenticate with the Management Server provide your credentials to Management Server in order to be allowed to save the transaction with a unique name Once the transaction has been played back a convenient way of getting an overview of the number of subtransactions is to look at the Transactions with Subtransactions for the STI playback policy During setup of the report the subtransaction selection dialog shown in Figure 8 10 on page 248 is displayed and this clearly shows that six subtransactions are involved in the trade_2_stock stock transaction Chapter 8 Measuring e business transaction response times 247 y Report Settings Microsoft Internet Explorer Policy trade_2_stock check z Management Agent tiviab01 gt Transaction trade_2_stock check gt Subtransactions Limit 5 Step 1 http ibmtiv9 itsc austin ibm com 82 trade Step_2_http ibmtiv9 itsc austin ibm com 82 trade app Step_3_http ibmtiv9 itsc austin ibm com 82 trade app Step_4_http ibmtiv9 itsc austin ibm c
346. lude the file with the Robot Transactions Figure 9 40 Create Generic Windows Transaction 9 2 3 Create a GenWin playback policy Now that you have registered a Rational Robot Transaction with TMTP you can specify how you wish to play the transaction back by creating a Playback Policy The procedure for deploying the Generic Windows component is outlined below Select the Work with Playback Policies option from the Configuration menu of the Navigation pane 2 Select Generic Windows from the Create New drop down box and then press the Create New button see Figure 9 41 on page 370 Chapter 9 Rational Robot and GenWin 369 370 2 IBM Tivoli Monitoring for Transaction Performanc osoft Internet Explorer Favorites Tools Help Tivoli Monitoring for Transaction Performance User Name Administrator Configuration Work with Discovery Policies Work with Listening Policies Work with Playback Policies Work with Schedules Work with Agent Groups Work with Transaction Recordings Work with Realms b Reports b System Administration b Downloads Work with Playback Policies Oo trade_2_stockcheck_tivlab01 sn trade_2_stock check sti_orp trade_sti_sch lin scheduled window Page 1 Show Enabled Policies Show Disabled Policies Figure 9 41 Work with Playback Policies You are then presented with the Create Playback Policy workflow see Figure 9 42 Fie Edit View Favorite
347. ludes both Quality of Service and J2EE listeners Please consult the manual BM Tivoli Monitoring for Transaction Performance User s Guide Version 5 2 0 SC32 1386 for more details The following outlines the procedure to create new discovery policies for a J2EE component 1 Start by navigating to the Work with Discovery Policies dialog from the home page of the TMTP console From the navigation pane on the left select Configuration Work with Discovery Policies 2 In the Work with Discovery Policies dialog shown in Figure 8 36 on page 283 select a policy type of J2EE and press Create New 282 End to End e business Transaction Management Made Easy IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer oj x File Edt View Favorites Tools Hel zi Address a http jitivdce4 9082 tmtpUlI jsp console WcFrameManager jsp Go Ea ES gt Tivoli Monitoring for Transaction Performance User Name administrator ir Configuration Work with Discovery Policies Work with Discovery Policies Work with Listening Policies Work with Playback Policies Work with Eiee DEE z Work with Agent Groups Work with Transaction Recordings Work with Realms vReports ele Show Enabled Policies View General Reports View Component Events Show Disabled Policies vSystem Administration Work with Agents Configure System Event Details Component Management Confiqure User Setting
348. ly created which will contain subdirectories for each of the instance records 6 3 J2EE monitoring maintenance During our work on this redbook we ran into a small number of problems using the J2EE monitoring component Most of these issues were because we were using prerelease code for much of our work While troubleshooting these issues the following steps were useful and may prove useful in a production environment ARM records not created If you are not receiving ARM records you can use the following steps to ensure that there are no problems with the policy J2EE or ARM These steps will verify that the ARM engine recognizes the policy and that ARM records are being generated by J2EE gt Verify that the J2EE component successfully installed Verify in the User Interface Work with Agents section that the J2EE component says RUNNING Possible problem UI does not say RUNNING Possible solution If the UI says INSTALL_IN_PROGRESS then keep waiting If you wait for an extremely long time 80 minutes and you checked Automatically restart Application server then the install is hung You will need to manually stop and restart the application server on the Management Agent If you do this and it does not switch to RUNNING open a defect on Instrument If the UI says INSTALL_RESTART_APPSERVER then restart the appserver on the Management Agent and rerun the PetStore or other application to collect ARM data If the Ul s
349. management tasks is to control and manage the service catalogue in which all the provisioned services are defined and described and the SLAs in which the commitments of the IT department are spelled out For this discussion we turn to the widely recognized Information Technology Infrastructure Library ITIL The ITIL was developed by the British Government s Central Computer and Telecommunications Agency CCTA but has over the past decade or more gained acceptance in the private sector One of the reasons behind this acceptance is that most IT organizations met with requirements to promise or even guarantee performance and availability agree that there is no point in agreeing to deliver a service at a specific level if the basic tools and processes needed to deploy manage monitor correct and report the achieved service level have not been established ITIL groups all of these activities into two major areas Service Delivery and Service Support as shown in Figure 1 4 on page 17 16 End to End e business Transaction Management Made Easy Configuration Management Figure 1 4 The ITIL Service Management disciplines The primary objectives of the Service Delivery discipline are proactive and consist primarily of planning and ensuring that the service is delivered according to the Service Level Agreement For this to happen the following tasks have to be accomplished Service Delivery Within ITIL the proactive di
350. may be used in place of the password where required A complete example of how this may be used in a Rational Script is shown in Example 9 11 Example 9 11 Using the retrieved password Sub Main Initially Recorded 10 1 2003 11 18 08 AM Script Name TestEncryptedPassword Dim Result As Integer Dim bf As Object Dim strPasswd As String Dim fchar Dim x As Integer Create the Encryption Engine and store a key Set bf CreateObject EncryptionAlgorithms BlowFish bf key ibm Open file and read encrypted password Open C encryptedpassword txt For Input Access Read As 1 Redim fchar Lof 1 For x 1 to Lof 1 2 fchar x Input 1 1 strPasswd strPasswd amp fchar x Next x Chapter 9 Rational Robot and GenWin 359 Decrypt the password into variable strPasswd bf DecryptString strPasswd rational Window SetContext Caption Program Manager ListView Db1Click ObjectIndex 1 ItemText Internet Explorer Coords 20 30 Window SetContext Caption IBM Intranet Microsoft Internet Explorer ComboEditBox Click ObjectIndex 2 Coords 61 5 InputKeys http 9 3 4 230 9082 tmtpUI ENTER InputKeys root TAB LEFT use the un encrypted password retrieved from the encrypted file InputKeys strPasswd PushButton Click HTMLText Log On Toolbar Click ObjectIndex 4 ItemID 32768 Coords 20 5 PopupMenuSelect Close End Sub Rational Robot screen locking solution Some us
351. me synchronization 71 time zone 173 timer 350 Timer goGet 47 times subtransaction 212 Tivoli Data Warehouse 191 Tivoli Enterprise Data Warehouse source applications 378 Tivoli Internet Management Server TIMS 57 TMTP 389 Index 491 application 149 database 149 ETL1 name 389 implementation 79 installation 85 portnumbers 92 roles 79 TMTP components 40 Discovery component 40 J2EE monitoring component 43 Listening components 41 Playback components 41 Quality of Service component 42 Rational Robot Generic Windows 43 Synthetic Transaction Investigator 43 TMTP_DB_Src 393 Tmw2kProfile 166 topology 212 aggregated 218 instance 47 213 J2EE 216 overview 51 report 212 216 view 44 212 215 218 219 296 318 topology view 300 trace performance 70 Trade3 application 236 transaction 3270 35 application 5 behaviour 212 breakdown 4 35 control 24 decomposition 57 enterprise 5 33 instance 217 path 212 reference 33 response time 163 root 76 217 SAP 35 simulation 35 slow 217 type 4 Web 4 33 worst performing 222 transaction process information 380 Transaction with Subtransaction 221 297 report 317 transactions 408 Transactions With Subtransactions 49 transformation services 24 trend analysis 417 troubleshooting 188 TWH_CDW 380 TWH_MART 380 TWH_MD 380 TWHApp log 391 U upgrade 193 upgrade ETL1 392 upload 187 user TEDW installation 386 temporaty table space 386 user access TEDW 394 User interface 61 V
352. ment lib config properties Dcom ibm tivoli transperf logging baseDir C ma 2003 07 03 0015 app instrumen t appServers 178 Dcom ibm tivoli jiti logging ILoggingImpl com ibm tivoli transperf instr contr oller TMTPConsoleLoggingImp1 Dcom ibm tivoli jiti logging FileLoggingImp 1ogFileName C ma 2003 07 03 001 5 app instrument BWM logs jiti log Dcom ibm tivoli jiti logging NativeFileLoggingImp logFileName C ma 2003 07 03 0015 app instrument BWM 1ogs native log Dcom ibm tivoli jiti registry Registry serializedFileName C ma 2003 07 03 00 15 app instrument lib WLRegistry ser Djlog propertyFileDir C ma 2003 07 03 0015 app instrument appServers 178 con fig 7 Click Apply to apply the changes to the Class Path and Arguments fields 8 Stop the WebLogic Application Server that was instrumented with J2EE Instrumentation 9 After the application server has been stopped remove the following nine files from the directory lt WL7_HOME gt server lib ext where lt WL7_HOME s is the home directory of the WebLogic 7 Application Server armjni jar copyright jar core_util jar ejfit jar eppam jar jffde jar jfltjar jlog jar probes jar After those nine files are removed remove the empty lt WL7_HOME gt server lib ext directory Chapter 6 Keeping the transaction monitoring environment fit 203 10 Remove the file lt WL7_HOME gt server bin jitipi dll or lt WL7_HOME gt server
353. menti Part 1 General Termsi BY DOWNLOADING INSTALLING COPYING ACCESSING OR USING THE PROGRAM YOU AGREE TO THE TERMS OF THIS AGREEMENT IF YOU ARE ACCEPTING THESE TERMS ON BEHALF OF ANOTHER PERSON OR amp COMPANY OR OTHER LEGAL ENTITY YOU REPRESENT AND WARRANT THAT YOU HAVE FULL AUTHORITY TO BIND THAT PERSON COMPANY OR LEGAL Perum 1 THESE TERMS IF YOU DO NOT AGREE TO THESE 5 DO NOT DOWNLOAD INSTALL COPY ACCESS OR USE THE PROGRAM AND PROMPTLY RETURN THE PROGRAM AND PROOF OF ENTITLEMENT TO THE PARTY FROM WHOM YOU ACQUIRED IT TO OBTAIN A REFUND OF THE AMOUNT YOU PAID IF YOU DOWNLOADED THE PROGRAM CONTACT THE PARTY FROM WHOM YOU ACQUIRED IT 2 IBM is International Business Machines Corporation or one of accept the terms in the license agreement I do not accept the terms in the license agreement InstallShield lt Back Next gt Cancel Figure 4 53 Management Server License Agreement panel gt We use the default directory to install the TMTP Management Server Figure 4 54 on page 140 Chapter 4 TMTP WTP Version 5 2 installation and deployment 139 Install the Management Server Click Next to install the management server to this folder or click Browse to install to a different folder pes Directory Name Vopt IBM Tivoli MS Browse Installshield lt Back Next gt Cancel Figure 4 54 Installation location window gt Since we perform a nonsecure installation w
354. mmand on the Canberra server setup _SnF_w32 exe P snfConfig wcpCdromDir C install wcp where the P snfConfig wcpCdromDir directory specifies the location of the WebSphere Edge Server Caching proxy installation binaries 118 End to End e business Transaction Management Made Easy Figure 4 34 should appear Click on Next net Install Store and Forward Agent Welcome to IBM Tivoli Monitoring for Transaction Performance Follow the instructions in this installation program to install the following product component on your computer IBM Tivoli Monitoring for Transaction Performance Store and Forward Agent To continue click Next See the installation quide for detailed descriptions of the installation steps NOTE The installation program installs the required Java Virtual Machine InstallShield Next gt Cancel Figure 4 34 Welcome window of the Store and Forward agent installation 4 In the next window we accept the License agreement Figure 4 35 on page 120 Chapter 4 TMTP WTP Version 5 2 installation and deployment 119 120 ml Install Store and Forward Agent jol x InstallShield Please read the following license agreement carefully International Program License Agreement Part 1 General Terms BY DOWNLOADING INSTALLING COPYING ACCESSING OR USING THE PROGRAM YOU AGREE TO THE TERMS OF THIS AGREEMENT IF YOU ARE ACCEPTING THESE TERMS ON BEHALF OF ANOTHER PERSON OR A COMPANY OR O
355. mport Rational Robot license cont Click on the Import button on the Confirm Import panel to import the IBM license in the License Key Manager if the import process is successful you will se a confirmation message box see Figure 9 15 Rational License Key Administrator 4 A File imported successfully Figure 9 15 Rational Robot license imported successfully Click on OK to return to the License Key Manager 334 End to End e business Transaction Management Made Easy The License Key Manager will now display the new license as being available see Figure 9 16 Rational I License Key Administrat File View License Keys Settings Help sjale Al 2 v Brationai Robot NodeLocked Ready DISPLAY FILTER is OFF Figure 9 16 Rational Robot license key now usable You can now close the License Key Administrator Rational Robot is now ready for use Configuring Rational Robot Java Enabler and Extensions For Rational Robot to correctly simulate operations being performed on Java applications the Java Extension must be loaded and a specific component called Robot Java Enabler must be installed and configured Configuring the Java Enabler The Java Enabler setup program is installed during the Rational Robot installation but has to be selected and customized for use before you can record a simulation successfully It is important that you ensure that Rational Robot is not running when you set up th
356. n BWM logs tapmagent log The location of this file is determined by the file fileName entry in one of the following files Windows MA_DIR config tapmagent logging properties UNIX MA_DIR config tapmagent logging properties To change the location of the ARM engine trace log file simply change the file fileName entry in this file Please note that the logging levels specified in this file have no effect To change logging levels for the ARM agent you will need to modify the logging level entries in the tmtp sc xml file as described in the previous section To get a more condensed version of the ARM engine trace log set the fmt className entry to ccg_basicformatter this line exists in the tapmagent logging properties file and only needs to be uncommented comment out the existing fmt className line ARM data The ARM Engine stores the data that it collects in the following directory ina binary format prior to being uploaded to the Management Server MA_HOME arm mar Dat By default this directory is hidden At each the end of each upload period this data is consolidated and placed into the MA_HOME arm mar Dat update Chapter 6 Keeping the transaction monitoring environment fit 187 directory from where it is picked up by the Bulk Data Transfer service to be forwarded to the Management Server If instance records are being collected by the ARM agent another directory called MA_HOME arm mar Dat current will be automatical
357. n Performance Microsoft Internet Explorer Fie Edit ls Help Tivoli Monitoring for Transaction Performance Address a http tivdce4 9082 tmtpUI jsp console WcFrameManager jsp User Name Administrator Configuration Work with Discover Work with Listening Work with Pleybacl LCharse setings Work with Schedule Policy trade_2_stockcheck_tiviab01 Work with Agent Gi Management Agent tivlab01 Work with Transact Transaction trade_2_stockcheck_tiviab01 Work with Realms z yReports 2 E 0 View Big Board View General Repo View Component E E Step_1_http ibmtiv9 itsc austin ibm com 82 rade System Administra E _ Step_2_http ibmtivd tse austin ibm com 82 trade app Work with Agents 6 45 es aa Ee Step_3_http ibmtiv9 itsc austin ibm com 82 trade app Configure Systern E E Step_4_http ibmtiv9 itsc austin ibm com 82 trade app action quotes amp symbols s 0 s Component Manage g Step_5_http Aibmtiva itsc austin ibm com 82 trade app action portfolio Configure User Sett 43 g trade_2_stockcheck_tiviab01 B General Reports gt Transaction With Subtransactions 8 58 Work with Event Re View System Event View Log Files 215 View Management gt Downloads 10 01 10 02 10 02 10 02 10 02 21 00 03 00 09 00 15 00 21 00 Time N Year Month Day Hour Minute Start Time 2003 z pomi 21 x 0 Stop Time 2003 m po h
358. n considerations on page 79 for a discussion of the implementation of the TMTP Management Agent 226 End to End e business Transaction Management Made Easy 8 1 Preparation for measurement and configuration Before measuring the real time performance of any e business application it is very import to consider whether or not a business transaction is a candidate for being monitored and carefully decide which data to gather Depending on what data is of interest User Experienced Time Execution Time of a specific subtransaction or total Back End Service Time are but a few examples you will have to select monitoring tools and configure monitoring policies according to your requirements In addition factors related to the nature and implementation of the e business application and your local procedures and policies may prevent you from being able to use playback monitoring tools such as Synthetic Transaction Investigator or Rational Robot Generic Windows because of the fact that they will generate what to the application system seems to be real business transactions for example purchases In case you cannot back out of or cancel the transactions originating from the monitoring tool you might want to refrain from using STI or GenWin for monitoring these transactions Several factors affect the decision of what to monitor how to monitor and from where to monitor Some of these are gt Use of naming standards for all TMTP policies
359. n data from a TMTP Version 5 2 relational database for a Tivoli Enterprise Data Warehouse and performing analysis and presentation of data from a business point of view In this chapter we introduce a new feature of the IBM Tivoli Monitoring for Transaction Performance Version 5 2 warehouse enablement pack ETL2 and show how to create business reports by using the Tivoli Enterprise Data Warehouse report interface and other OLAP tools This chapter provides discussions regarding the following gt gt gt TEDW methods and process Configuration and collection of historical data Sample e business transaction and availability report by the TEDW Report Interface Customized report by OLAP tools such as Crystal Enterprise Copyright IBM Corp 2003 All rights reserved 375 10 1 TMTP and Tivoli Enterprise Data Warehouse One of the important features of IBM Tivoli Monitoring for Transaction Performance Version 5 2 is the integration of the common Tivoli repository for historical data that is Tivoli Enterprise Data Warehouse Both the Enterprise and the Web Transaction Performance features provide these capabilities by supplying functions to extract historical data from the TMTP database The Tivoli Enterprise Data Warehouse TEDW is used to collect and manage data from various Tivoli and non Tivoli system management applications The data is imported into the TEDW databases through specialized extract transform and load
360. n db2ilist d For each instance listed above run DB2DIR instance db2idrop lt instance gt e From the DB2 install directory run the db2 deinstall script db2_deinstall f Remove the DB2 admin instance and fence users and delete their home directories On many UNIX platforms you can delete users with the following command userdel r lt login name gt r removes home directory This should remove entries from etc passwd and etc shadow g Remove var db2 if no other version of DB2 is installed h Delete any DB2 related lines from etc services i On Solaris check the size of textfile var adm messages DB2 can sometimes increase it to hundreds of megabytes Truncate this file if required j Remove any old db2 related files in tmp there will be some log files and other nonessential files here 194 End to End e business Transaction Management Made Easy 6 5 2 The wrong way to uninstall on UNIX Experienced UNIX administrators are often tempted to uninstall using a brute force method that is deleting the directories associated with the installs This will work but you should keep the following points in mind gt The DB2 installation will create several new users generally db2inst1 db2fenc1 and so on which will need to be deleted see the procedure for removing DB2 above gt IBM Tivoli keeps a record of each product it has installed in a file named vpd properties This file is located in the home direct
361. n facility to manage playback of your transactions Chapter 10 Historical reporting on page 375 This chapter discusses methods and processes of collecting business transaction data from the TMTP Version 5 2 relational database to Tivoli Enterprise Date Warehouse and analysis and presentation of that data as a business point of view The target audience for this part are the users of IBM Tivoli Monitoring for Transaction Performance who are responsible for defining monitoring policies and interpreting the results End to End e business Transaction Management Made Easy Real time reporting This chapter introduces the various reporting options available in IBM Tivoli Monitoring for Transaction Performance Version 5 2 both real time and historical Later chapters build on the information introduced here in order to show real e business transaction performance troubleshooting techniques using TMTP Copyright IBM Corp 2003 All rights reserved 211 7 1 Reporting overview The focus of IBM Tivoli Monitoring for Transaction Performance reporting is to help pinpoint problems with transactions defined in monitoring policies by showing how each subtransaction relates in the overall transaction and how those transactions compare against each other Two main avenues are provided for viewing the data from the Big Board with its associated topologies and line charts through the General Reports link which offers additional line charts a
362. n ibm com tmtpma xp itsc austin ibm com tivilab01 tiviabO1 tivlab01 N A ibmtiv9 ibmtiv9 ibmtiv9 N A OO N Chapter 10 Historical reporting 409 Report Output pA 3 g g 2 Transaction Host Name Probe Host Name Report Output E Figure 10 24 Response time by host name Execution load by application This report shows the number of times any transaction within the application was run during the time interval This shows which applications are being used the most If an application has an unusually low value it may have been unavailable during the interval This report uses the BWM_Daily_Transaction_Node_Star_Schema The categories shown in the Execution Load by Application report in Figure 10 25 on page 411 are labeled J2EE Vendor J2EE Version J2EE Server Name Probe name The actual values for this report are WebSphere5 0 server1 N A N A N A QOS N A N A STI N A N A N A N A N A N A Or AN 410 End to End e business Transaction Management Made Easy IBM Console Microsoft Internet Explorer ioj x Report Ouiput Performance Execution Load by Application DAILY 1065733056015 1400000 1200000 1000000 600000 400000 200000 E J2EE Vendor J2EE Version J2EE Server Name Probe Name Figure 10 25 Execution Load by Application daily O Welcome Manage Reports and Report Ou Execution load
363. n it should survive the above rules RewriteRule F Setup URL reverse mapping for redirect reponses ProxyPassReverse http 9 3 5 15 80 ProxyPassReverse http 9 3 5 15 lt VirtualHost gt In a live production environment chances are that multiple QoS systems will be used to monitor a variety of application servers hosting different applications as depicted in Figure 8 21 on page 265 End to End e business Transaction Management Made Easy www han telia com 80 www kal telia com 85 www sun telia com 82 telia com 80 www telia com 80 www telia com 80 LoadBalancer request for www telia com 80 Figure 8 21 Multiple QoS systems measuring multiple sites When planning to use multiple virtual servers on a single or multiple QoS system s please take the following into consideration Policy creation When scheduling a policy against particular end points it makes sense to schedule it against groups that are created and maintained as virtual hosts A customer that want to schedule a job against www telia com 80 for example would want to select the group with all of the above QoS systems When scheduling a policy against www kal telia com 85 however a group only contains QoS1 The name of the server QoS1 in this case does not give the user customer any indication of what virtual hosts exist on each machine Endpoint Groups Endpoint Groups are an obvious match for this needed functionality It i
364. n screen in the browser window Figure 4 33 on page 118 Chapter 4 TMTP WTP Version 5 2 installation and deployment 117 15 x IBM Tivoli Monitoring for Transaction Perfa Bak gt O A Qsearch Favorites Gmeda Address hd PG Links Jasas Fie Edit View Favorites Tools Help Log On User Name Password Log On vile Done E A internet Figure 4 33 TMTP logon window 4 1 3 Deployment of the Store and Forward Agents In this section we will deploy the Store and Forward agents into the DMZ and the intranet zone The following preparations are needed for the installation of the Store and Forward agents 1 Copy the installation binaries to the local systems We already did that task We created the c install folder where we copied the installation binaries for the Store and Forward agent We copied the binaries of the WebSphere Edge Server Caching proxy to the c install wcp folder 2 Check to see if the Management Server and Store and Forward agents fully qualified host names are DNS resolvable 3 The Store and Forward agents platform will be Windows 2000 Advanced Server with Service Pack 4 The required disk space for all platforms is 50 MB not including logs The installation wizard will install the following components a WebSphere Edge Server Caching proxy b Store and Forward agent c We start the installation executing the following co
365. nality enables a user to view the context metrics associated with the worst performing transaction for a given time period It is important to note see parent based aggregation that the term worst performing is specific to each subtransaction individually and not the overall performance of the parent transaction However the MAX for each subtransaction within a given transaction will store its context uniquely allowing for the presentation of the complete transaction including the context of each subtransaction performing at its own worst level Parent Performance Initiated Trace The trace flag within the ARM correlator is utilized by the agent x 80 in the trace field for transactions that are performing outside of their threshold This provides for the dynamic collection of instance data across all systems where this transaction executes The ARM agent at the transaction initiating point enables this flag when providing a correlator for a transaction that has performed slower then its specified threshold To limit the overall performance impact of this tracing this flag is only generated once for each transaction threshold crossing Trace will continue to be enabled for this transaction for up to five consecutive times unless transaction performance recedes below threshold This should enable the tracing of instance data for a violating transaction without user intervention while allowing for aggregated collection of data at all ot
366. nce for every system that will be used to record synthetic transactions However steps 3 through 5 has to be repeated for every new recording 8 4 1 STI component deployment To deploy the STI component to an existing Management Agent log in to the TMTP console and select System Administration Work with Agents gt Deploy Synthetic Transaction Investigator Components Go as shown in Figure 8 3 on page 242 Chapter 8 Measuring e business transaction response times 241 IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer 0 x File Edit View Favorites Tools Help EBak gt A Qsearch GaFavorites Meda lt 4 D 3 a a Tivoli Monitoring for Transaction Performance User Name administrator gt Configuration vReports Work with Agents View Big Board View General Reports View Component Events vSystem Administration Work with Agents Configure System Event Q ibmti3 Please make a selection STI QoS J2EE Name Installed Running 4 Component Managemer tivdce4 itsc austin ibm com View Log Files View Management Sent gt Downloads Show All Agents pene P SEE M itivlab01 Installed Installed Running Work with Event Respor i t View System Events I tmtpma xp itsc austin ibm com Page 1
367. nd tables The Big Board is greatly expanded from the Big Board in 5 1 and includes access to much more data and provides greater interactivity The primary report is the Topology View which shows the path of a transaction throughout the system The other reports provide additional context and comparison to the transactions behavior 7 2 Reporting differences from Version 5 1 There are a number of reporting differences between Version 5 2 and Version 5 1 of IBM Tivoli Monitoring for Transaction Performance Web Transaction Performance Most of the changes are good however a couple introduce differences that need to be understood by users familiar with previous versions Among the better changes are gt Version 5 2 now makes the Big Board the focus of reporting When problems arise TMTP Version 5 2 users are expected to access the Big Board first as it enables them to quickly focus on the potential problem cause gt The other reports are for either daily reporting or to gain extra context into problems What is the behavior of this policy over time What were my slowest policies last week What is the availability of this policy in the last 24 hours gt The Topology Report is a completely new way of visualizing the transaction The customer can now visually see the performance of a transaction for both specific transaction instances as well as an hourly aggregate view gt In addition to performance and response co
368. nd baselining gt For well known systems with specific programs installed Transaction simulation based on recording and playback Web transaction availability monitoring Enterprise transaction monitoring If the application provider wants to gather transaction performance characteristics from workstations situated within the enterprise network or machines that are part of the managed domain but initiates transactions through the Internet a different set of tools is available These are provided by the Enterprise Transaction Performance module of the IBM Tivoli Monitoring for Transaction Performance product The functions provided by Enterprise Transaction Performance are integrated with the Tivoli Management Environment and rely on common services provided by the integration Therefore the systems from which transaction performance data is being gathered must be part of the Tivoli Management Environment and at a minimum have a Tivoli endpoint installed This will however enable centralized management of the systems for additional functions besides the gathering of transaction performance data In addition to monitoring transactions initiated through a browser just like the ones we earlier called Web transactions Enterprise Transaction Performance provides specialized programs end to end probes which enable monitoring of the time needed to load a URL and specific transactions related to certain mail and groupware applications The
369. nd connect to the TWH_CDW database db2 connect to TWH CDW user db2admin using lt db2pw gt where lt db2pw gt is the database administrator password 2 In order to determine the actual heap size issue db2 get db cfg for TWH_CDW grep CTL_HEAP The output should be similar to what is shown in Example 10 1 Example 10 1 Current applications control heap size on the TWH_CDW database Max appl control heap size 4KB APP_CTL_HEAP_ SZ 128 3 If the heap size is less that 512 perform db2 update db cfg for TWH_CDW using APP_CTL_HEAP_SZ 512 The output should be similar what is shown in Example 10 2 on page 386 Chapter 10 Historical reporting 385 Example 10 2 Output from db2 update db cfg for TWH_CDW DB200001 The UPDATE DATABASE CONFIGURATION command completed successfully DB210261 For most configuration parameters all applications must disconnect from this database before the changes become effective 4 You should now restart DB2 by issuing the following series of commands db2 disconnect THW_CDW db2 force application all db2 terminate db2stop db2admin stop db2admin start db2start Limitations This warehouse pack must be installed using the user db2 If that is not the user name used when installing the Tivoli Enterprise Data Warehouse core application you must create a temporary user table space for use by the installation program The temporary user table space that is created in each central data warehouse data
370. nd could be quite difficult 68 End to End e business Transaction Management Made Easy fo Host B 9 WAS HostA Qos mt Bare E 5 Enti STI Page Servlet BaN Hoste Render B D B i QL 9 Sgasion Statement DB2 Figure 3 7 Transaction performance visualization TMTP Version 5 2 implements the following ARM correlation mechanisms 1 Parent based aggregation Probably the single largest change to the current ARM aggregation agent is the implementation of parent based correlation This enables transaction performance data to be collected based on the parent of a subtransaction This allows the displaying of transaction performance relative to its path The purpose served by this is the ability to monitor the connection points between transactions It also enables path based transaction performance monitoring across farms of servers all providing the same functionality The correlator generation mechanism will pass parent identification within the correlator to enable this to occur 2 Policy based correlators Another change for the correlator is that a portion of the correlator is used to pass a unique policy identifier within the correlator The associated policy will control the amount of data being collected and also the thresholds associated with that data In this model a user specifies the amount of data collection for the different systems being monitored Users do not need to know the actual path taken by a tr
371. nd create the required bufferpool create bufferpool buffpool32k size 250 pagesize 32 k DB200001 The SQL command completed successfully Now we have finished configuring the DB2 WebSphere configuration The most important thing is to make sure that the WebSphere FixPack 1 is applied because this is a critical prerequisite prior to the installation To check it out log on to the WebSphere admin console and click on the Home button in the browser window We see the window shown in Figure 4 2 on page 92 Chapter 4 TMTP WTP Version 5 2 installation and deployment 91 About your WebSphere Application Server IBM WebSphere Application Server 5 0 1 Build Number ptf1M0312 13 Build Date 03 29 2003 c Copyright IBM Corporation 1996 2003 Figure 4 2 WebSphere information screen Since the version of the WebSphere is 5 0 1 the WebSphere FixPack 1 is applied 6 Port numbers In this scenario we will use the default port numbers for the TMTP installation These are Port for non SSL clients 9081 Port for SSL clients 9446 Management Server SSL Console port 9445 Management Server non Secure Console port 9082 Important Since we will perform a custom secure installation the Management Server non Secure Console port is not applicable in this scenario however we mention it to show all the possibly required ports If you wish to perform a nonsecure installation the Management Server SSL
372. ndow select the desired components and right click on them Choose Mode gt Production as shown in Figure 10 21 on page 405 404 End to End e business Transaction Management Made Easy Warehouse Selected Edit View Tools Help EP gt a agaaga aa sD fe Warehouse a fix Subject Areas AM_IBM_TIVOLI_Monitoring_v5 1 1_S AM _Operating_Systems_PAC_v1 1 0 ANM_IBM_Tivoli_Netview_v1 1 0_Subj BWM_Tivali_Monitoring_fo t_Transactic Mo Development 5 0 Processes EB TRANSACTION Test v Test X BWM_c05_Upgrade51 Proces E comp Move BABM _c10_CDW_Process Print gt 5 BWM_m05_Mart_Process ga CDW_TivoliEnterpriseDataWarehouse e Warehouse Sources Warehouse Targets Warehouse Schemas Administration Ej Ej Ej a it Ke Ae Figure 10 21 Source ETL scheduled processes to Production status a ZE As demonstrated in Figure 10 21 it is possible to select multiple processes and set the desired mode for all of them at the same time Now all the process are ready and scheduled to be run in production mode When the data collection and ETL1 and ETL2 processes are executed historical data from IBM Tivoli Monitoring for Transaction Performance is available to TMTP Version 5 2 data mart and you will be ready to generate reports as described in 10 3 2 Sample TMTP Version 5 2 reports with data mart on page 408 10 2 Creating historical reports directly
373. ness User to Business Patterns for Topology 1 and 2 Using WebSphere Advanced Edition SG24 5864 which can be downloaded from http www redbooks ibm com Tivoli and IBM provide some of the most widely used products to implement the e business infrastructure These are IBM HTTP Server Communication and transaction control Tivoli Access Manager Identification authentication and authorization Chapter 1 Transaction management imperatives 25 IBM WebSphere Application Server Web application hosting responsible for the transformation services IBM WebSphere Edge Server Web application firewalling load balancing Web hosting responsible for the transformation services 1 3 4 Managing e business applications using Tivoli Even though the e business patterns help in designing e business applications by breaking them down into functional units that may be implemented in different tiers of the architecture using different hard and software technologies the patterns provide only some assistance in managing these applications Fortunately this gap is filled by solutions from Tivoli Systems When designing the systems management infrastructure that is needed to manage the e business applications it must be kept in mind that the determining factor for the application architecture is the nature of the application itself This determines the application infrastructure and the technologies used However it does not do any harm if the solu
374. ness approaches that have been tested and proven By making these approaches available and classifying them into useful categories LOB executives planners architects and developers can further refine them into useful tangible guidelines The patterns and their associated guidelines enable the individual to start with a problem and a vision find a conceptual pattern that fits this vision define the necessary functional pieces that the application will need to succeed and then actually build the application Furthermore the Patterns for e business provides common terminology from a project s onset and ensures that the application supports business objectives significantly reducing cost and risk The Patterns for e business layered asset model The Patterns for e business approach enables architects to implement successful e business solutions through the re use of components and solution elements from proven successful experiences The Patterns approach is based on a set of layered assets that can be exploited by any existing development Appendix A Patterns for e business 431 432 methodology These layered assets are structured so that each level of detail builds on the last These assets include gt Business patterns that identify the interaction between users businesses and data Integration patterns that tie multiple Business patterns together when a solution cannot be provided based on a single Business pattern Com
375. net zone Table 4 4 summarizes the changed parameters for the Management Agent installation in the DMZ and the Internet zone Table 4 4 Changed option of the Management Agent installation zone Parameter pMz o Internet zone Host Name The host name of the Store and Canberra Frankfurt Forward agent in the specified zone Port Number The default port number of the 443 443 Store and Forward agent SSL Key Store File password dmzagent jks dmzagent jks Note The User Name user password fields are still referring to the root user on the Management Server since this user ID needs to have access to the WebSphere Application Server 136 End to End e business Transaction Management Made Easy 4 2 Typical installation of the Management Server In this section we will demonstrate the typical nonsecure installation of the Management Server on SuSE Linux Version 7 3 There are no additional operating system patches needed We will use the root file system to perform the installation On this file system we have 6 GB of free space which will be enough for the TMTP installation The installation wizard will install the following software for us gt DB2 Server Version 8 1 UDB gt WebSphere Application Server Version 5 0 gt WebSphere Application Server Version 5 0 with FixPack 1 gt TMTP Version 5 2 Management Server The DB2 and the WebSphere installation binaries come with the TMTP installation CDs In order to perform a smo
376. nfigured to use the default HTTP port 80 It has two virtual servers backend1 and backend2 which in turn reverse proxy the hosts at 9 3 5 20 and 9 3 5 15 Example 8 2 Virtual host configuration for QoS monitoring multiple application servers This is for name based virtual host support NameVirtualHost backend1 80 NameVirtualHost backend2 80 For clarity place all listen directives here Listen 9 3 5 14 80 This is the main virtual host created by install Hedda tid te AAEE Ee ee ea eae ee eae a ee ee Pe a a a a lt VirtualHost backend1 80 gt 262 End to End e business Transaction Management Made Easy SSLEnable ServerName backend1 QoSMContactURL http 9 3 5 14 80 Enable the URL rewriting engine and proxy module without caching RewriteEngine on RewriteLogLevel 0 ProxyRequests on NoCache Define a rewriting map with value lists mapname key filename Rewri teMap server txt lt QOSBASEDIR gt IBMHTTPServer conf apache rproxy conf servers Make sure the status page is handled locally and make sure no one uses our proxy except ourself RewriteRule apache rproxy status L RewriteRule https http ftp FA Now choose the possible servers for particular URL types RewriteRule cgilshtml to 9 3 5 20 80 1 S 1 RewriteRule A1 to 9 3 5 20 80 1 and delegate the generated URL by passing it through the proxy module RewriteRule to ht
377. ng In this part we discuss an overview of transaction management imperatives a high level brief of IBM Tivoli Monitoring for Transaction Performance 5 2 and a high level and detailed architectural concept Copyright IBM Corp 2003 All rights reserved The following main topics are included gt Chapter 1 Transaction management imperatives on page 3 gt Chapter 2 IBM Tivoli Monitoring for Transaction Performance in brief on page 37 gt Chapter 3 IBM TMTP architecture on page 55 2 End to End e business Transaction Management Made Easy Transaction management imperatives This chapter provides an overview of the business imperatives for looking at transaction performance We also use this chapter to discuss in broader terms the topics of system management and availability as well as performance monitoring Copyright IBM Corp 2003 All rights reserved 1 1 e business transactions In the Web world users perceive interacting with an organization or a business through a Web based interface as a single continuous interaction or session between the user s machine and the systems of the other party and that is how it should be However the interaction is most likely made up of a large number of individual interrelated transactions each one providing its own specific part of the complex set of functions that implement an e business transaction perhaps running on systems owned by other organizatio
378. ng He has been an IBM employee since 1999 after working as an independent consultant for large software companies since 1994 He has three years of experience in the application performance measurement field His areas of expertise include test automation performance and availability monitoring and systems management Scott Henley is an IBM System Engineer based in Australia who performs pre and post sales support for IBM Tivoli products Scott has almost 15 years of Information Technology experience with a focus on Systems Management utilizing IBM Tivoli products He holds a Bachelors degree in Information Technology from Australia s Charles Stuart University and is due to complete his Masters in Information Technology in 2004 Scott holds product certifications for many of IBM Tivoli PACO and Security products as well as MCSE status since 1997 and the RHCE status since 2000 Zoltan Veress is an independent System Management Consultant working for IBM Global Services France He has eight years of experience in the field His major areas of expertise include software distribution inventory remote control and he also has experience with almost all Tivoli Framework based products Thanks to the following people for their contributions to this project The Editing Team International Technical Support Organization Austin Center Preface xxiii Fergus Stewart Randy Scott Cheryl Thrailkill Phil Buckellew David Hobbs Tivoli Product Mana
379. ng actions to complete the procedure Restart WebSphere Application Services Restart the IBM Tivoli Monitoring for Transaction Performance from the WebSphere administration console 176 End to End e business Transaction Management Made Easy Keeping the transaction monitoring environment fit This chapter describes some general maintenance procedures for TMTP Version 5 2 including gt How to start and stop various components gt How to uninstall the Management Server cleanly from a UNIX platform We also describe some of the configuration options and provide the reader with some general troubleshooting procedures Lastly we discuss using various other IBM Tivoli products to manage the availability of the TMTP application The TMTP product includes a comprehensive manual for troubleshooting this chapter does not attempt to reproduce that information Copyright IBM Corp 2003 All rights reserved 177 6 1 Basic maintenance for the TMTP WTP environment gt The TMTP WTP environment is based on the DB2 database sever and the WebSphere 5 0 Application Server so it is important to understand some basic maintenance tasks related to these two products gt To stop and start the DB2 Database Server open a DB2 command line processor window and type the following commands db2stop db2start The database log file can be found at instance_home sqllib db2dump db2diag log Tip Our recommendation is to use a tool
380. ng environment fit 205 206 for long term monitoring during normal operation The default settings include the following characteristics gt Only record aggregate records gt 20 sampling rate gt Low tracing detail With these settings the normal transaction flow is recorded for 20 of the actual user transactions and only a summary or aggregate of the data is saved The Low trace level turns on tracing for all inbound HTTP requests and all outbound JDBC and RMI requests This setting allows for minimal performance impact on the monitored application server while still providing informative real time and historical data However when a performance or availability violation is detected for the J2EE application server it may become necessary to turn up some of the tracing detail to allow for quick debugging of the situation This can easily be done by editing the existing Listening Policy and under the section Configure J2EE settings the J2EE Trace Detail Level to Medium or High Figure 6 9 shows how to change the default J2EE Trace Detail Level eM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer oj x File Edt View Favorites Tools Help Address a http 9 tmtpUL jsp console WcFrameManager jsp c a Back gt gt OA A Qsearch Favorites Bmeda G EY 4 St a Tivoli Monitoring for Transaction Performance User Name root Configuration F i i yeas Create Listening Policy C
381. ng performance through complex distributed computing networks ARM provides a way for business applications to pass information about the subtransactions they initiate in response to service requests that flow across a network This information can be used to calculate response times identify subtransactions and provide additional data to help you determine the cause of performance problems Some of the specific details of how ARM is utilized by TMTP are discussed in the next section Chapter 3 IBM TMTP architecture 65 66 Figure 3 6 gives an overview of how the ARM Engine communicates with the Monitoring Engine ARM Call Synthetic Transaction lt Investigator ye Correlator ARM Call _ Quality of Service ARM Engine O pce ARM Call lt q J2EE Instrumentation TCP IP socket one way only Monitoring Engine JNI ARM cli call ARM Call Generic Windows Figure 3 6 ARM Engine communication with Monitoring Engine All transaction data collected by the Quality of Service J2EE STI and Generic Windows monitoring components of TMTP is collected by the ARM functionality The use of ARM results in the following capabilities gt Data aggregation and correlation ARM provides the ability to average all of the response times collected by a policy a process known as aggregation Response times are aggregated once per hour Aggregate data gives you a view into the overall performanc
382. ng system 88 resolution problem 154 resource application 26 model 31 60 162 168 170 response automatic 168 response code HTTP 230 response time transactions 163 Response Time View 218 response time view 217 321 Retrieve Latest Data 213 reverse proxy 77 80 258 reverse proxy 257 RI See Report Interface RMI 206 roles reporting 407 root account 123 132 transaction 76 217 root cause 225 288 root cause analysis 306 Root cause analysis 8 rules 168 ruleset 168 169 Runtime patterns 436 S SAP 33 80 82 transaction 35 scalable 81 schedule 454 playback 248 report execution 416 screen lock 360 468 secure zone 79 security 156 170 features 76 protocol 76 TEDW 377 Seibel 82 server TEDW Control Center 388 virtual 261 server status 162 service 14 15 component 16 delivery 17 specialized 13 Service Level Management 17 sessions 163 setup wizard 329 severity violation 216 severity codes 167 sibling transaction 70 simulation transaction 35 single point of failure 153 Sizes 224 slow transaction 217 Slowest Transactions Table 222 SMTP settings 176 SnF agent 77 79 configuration 77 deployment 118 placing 79 redirect 181 SNMP settings 175 trap 182 Software Control and Distribution 19 solution 14 source data 393 warehouse 394 source applications 378 source ETL 379 specialized management 15 services 13 SSL 110 244 agent 140 490 End to End e business Transaction Management Made Easy
383. ng the average response times that were applied during the discovery period The list of discovered URIs may be consulted in order to identify transactions that are candidates for further monitoring Listening policy A listening policy collects response time data for transactions and subtransactions that are executed in the Web environment Running a policy produces detailed information about transaction and subtransaction instance response times A listening policy may be used to assess the experience of real users of your Web sites and to identify performance problems and bottlenecks as they occur Chapter 8 Measuring e business transaction response times 239 240 Automatic thresholding IBM Tivoli Monitoring for Transaction Performance Version 5 2 implements a new concept of automatic thresholding in both discovery and listening policies Every node on a topology group nodes as well as the final click nodes has a timing value associated with it The final click node s timings will stay the same but the group node s timings will now be the maximum timing contained within that group The worst performing overall transaction is marked Most Violated A configurable percentage default 5 of topology nodes is marked with the Violated interpreted status to show other potential areas of concern If only one node in the whole topology is to be marked it is the Most Violated node and there will be no Violated nodes The Topology algori
384. non device platform yet it is an infrastructure component with the usual attributes of a hard component in terms of configuration and administration But its performance is also related and very dependent on the resources of supporting components such as servers networks and databases The consequences of this profound modification in application architecture will ripple over time into the way the supporting infrastructure is managed The majority of today s infrastructure management implementations are confined to devices monitored in real time for fault and performance from a central enterprise console 6 End to End e business Transaction Management Made Easy In this context application management is based on a traditional agent server relationship collecting data mostly from the outside with little insight into the application internals For example gt Standard applications may provide specific parameters usually resource consumption to a custom agent gt Custom applications are mostly managed from the outside by looking at their resource consumption In depth analysis of application performance using this approach is not a real time activity and the most common way to manage real time availability and performance response time of applications is to use external active agents Service level management capacity planning and performance management are aimed at the devices and remain mostly stove piped activit
385. ns or legal entities Figure 1 1 shows a typical Web based transaction the resources used to facilitate the transaction and the typical components of a transaction breakdown user experienced time system q gt transaction time l a Ee I l l l _ gt a a a mt user sub transaction Sub transaction II sub transaction III time time f I time i i time 1 i l network i l l time I l l l l l l l I i I invoking l system l i i l s transaction backend time f providing Lat f f f f l l 1 sub transaction service provider T 1 1 l l f f service provider f f f browser l Web Server Application Database Server Server Figure 1 1 Transaction breakdown In the context of this book we will differentiate between different types of transactions depending on the location of the machine from which the transaction is initiated Web transaction Originate from the Internet thus we have no predetermined knowledge about the user the system and the location of the transaction originator 4 End to End e business Transaction Management Made Easy Enterprise transaction Initiated from well known systems most of which are under our control and knowledge of the available resources exists Typically the system
386. nsaction Performance Version 5 2 to gt Measure transaction and subtransaction response times in a real time or simulated environment gt Perform detailed analysis of transaction performance data gt Identify root causes of performance problems Real time end user experience measurement by using Quality of Service and J2EE will be introduced and the use of subtransaction analysis and Back End Service Time from Quality of Service is demonstrated along with the use of correlation of the information to identify the root cause of e business transaction problems This chapter provides discussions of the following topics gt Business and application considerations general issues and preparation for measurements gt The e business sample applications Trade and Pet Store Copyright IBM Corp 2003 All rights reserved 225 gt Comparison study of choice of tools Synthetic Transaction Investigator Generic Windows J2EE Quality of Service gt Real time monitoring analysis using the Trade sample application in a WebSphere Application Server 5 0 1 environment using Synthetic Transaction Investigator J2EE Quality of Service gt Weblogic and Pet Store case study For the discussions in this chapter it is assumed that the TMTP Management Agent is installed on all the systems where the different monitoring components STI QoS J2EE and GenWin are deployed Please refer to 3 5 TMTP implementatio
387. nt Object Model Data Source Name Document Type Definition Ephemeral Availability Agent now QoS Enterprise Java Beans End to End Probe platform Enterprise Resource Planning Enterprise Transaction Performance Global Enterprise Manager Greenwich Mean Time Global Security Kit Graphical User Interface Hypertext Markup Language Hypertext Transfer Protocol HTTP Secure International Business Machines Corporation International Data Encryption Algorithm Microsoft Internet Explorer Internet Inter ORB Protocol Internet Information Server Internet Message Access Protocol Inter Object Messaging Internet Server API 475 ITM ITMTP ITSO JCP JDBC JNI JRE JSP JVM LAN LOB LR MBean MD5 MIME MLM ODBC OID OLAP OMG OOP ORB Os oSI PKCS10 QoS RDBMS RIM RIPEMD RTE 476 IBM Tivoli Monitoring IBM Tivoli Monitor for Transaction Performance International Technical Support Organization Java Community Process Java Database Connectivity Java Native Interface Java Runtime Environment Java Server Page Java Virtual Machine Local Area Network Line of Business LoadRunner Management Bean Message Digest 5 Multi purpose Internet Mail Extensions Mid Level Manager Open Database Connectivity Object Identifier Online Analytical Processing Object Management Group Object Oriented Programming Object Request Broker Operating Systems Open Systems Interconnection Public Key Cryptog
388. nted at the origin server or on a remote computer that acts as a gateway to specific Web Servers Normally transactions within a Web server measures the time required to complete the transaction This virtual server runs within IBM HTTP Server Version 1 3 26 1 which comes with the QoS monitoring component Reverse proxy A physical HTTP Server that hosts the virtual proxy servers pointing to the origin servers The reverse proxy server also hosts the QoS monitoring component The reverse proxy server may be installed directly on the origin server or on a remote computer Running QoS on the same machine as the origin server may be beneficial because it eliminates network issues speed delay collisions and bandwidth Digital certificates Authentication documents that secure communications for Quality of Service monitoring 258 End to End e business Transaction Management Made Easy 8 5 1 QoS Component deployment To deploy the Quality of Service component to a Management Agent follow the steps below 1 From the home page of the Management Server console click on System Administration Work with Agents The Work with Agents dialog depicted in Figure 8 18 will be displayed E IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer Fie Edt View Favorites Tools Hel gt address a http tivdce4 9082 tmtpUL isp console WcFrameManager jsp Tivoli Monitoring for Transaction Performanc
389. nts behavior endpoint uuid endpoint name windows password endpoint port windows user You can modify the location of the JKS files by editing the endpoint keystore parameter in the endpoint properties file and restarting the relevant service s Component management It is important to manage the data accumulated by TMTP By default data greater than 30 days old is cleared out automatically This period can be Chapter 6 Keeping the transaction monitoring environment fit 181 changed by selecting Systems Administration Components Management If your business requires longer lasting historical data you should utilize Tivoli Data Warehouse gt Monitoring of TMTP system events The following system events generated by TMTP are important TMTP status indicators and should be managed carefully by the TMTP administrator TEC Event Lost Data J2EE Arm not run Monitoring Engine Lost ARM Connection Playback Schedule Overrun Policy Execution Failed Policy Did Not Start Policy Did Not Start Management Agent Out of Service TMTP BDH data transfer failed Generally the best way to manage these events is for the event to be forwarded to the Tivoli Enterprise Console however other alternatives include generating an SNMP trap sending an e mail or running a script Event responses can be configured by selecting Systems Administration Configure System Event Details
390. o End e business Transaction Management Made Easy and surveillance of the e business solution components These technologies will help manage the IT resources that are part of the e business solution Some of these technologies may even be applied to manage the non IT resources such as power cooling and access control However each layer in any component is specialized and requires different types of management In addition from a management point of view the top layer of any component is the most interesting as it is the layer that provides the unique service that is required by that particular component For a Web server the top layer is the HTTP server itself This is the mission critical layer even though it still needs networking an operating system hardware and power to operate On the other hand for an e business application server although it also may have a Web server installed for communicating with the dedicated Web Server the mission critical layer is the application server and the Web server is considered secondary in this case just as the operating system power and networking are This said all the underlying services are needed and must operate flawlessly in order for the top layer to provide its services It is much like driving a car you monitor the speedometer regularly to avoid penalties by violating changing speed limits but you check the fuel indicator only from time to time or when the indicator alerts you to
391. o do this are beyond the scope of this redbook however the documentation that comes with WebSphere 5 0 1 discusses this in some depth The redbook IBM WebSphere V5 0 Security SG24 6573 is also a useful reference for learning about WebSphere 5 0 security 3 5 TMTP implementation considerations Every organization s transaction monitoring requirements are different which means that no two TMTP implementations will be exactly the same However there are several key considerations that must be made Where to place the Management Server Previous versions of TMTP made this decision for you as placing the Management Server previously called TIMS anywhere other than in the DMZ necessitated opening excessive additional incoming ports through your firewall This release of TMTP includes the Store and Forward agent which allows communications from the Management Agents to the Management Server to be consolidated and passed through a firewall via a single configured port The Store and Forward agent can also be chained in order to facilitate communicate through multiple firewalls in a secure way In general the placement of the Management Server will be in a secure zone such as the intranet Where to place Store and Forward agents SnF agents can be placed within each DMZ in order to allow communications with the Management Server By default the SnF agent communicates directly with the Management Server however should your security infrastr
392. ocedure for deploying the Generic Windows component is outlined below 1 Select the Work with Agents option from the System Administration menu of the Navigation pane The window shown in Figure 9 37 on page 366 should appear Chapter 9 Rational Robot and GenWin 365 a IBM Tivoli Monitoring for Transaction Pe Performance Microsoft Internet erformance Microsoft Internet Explorer Tivoli Monitoring for Transaction Performance Configuration Work with Discovery Policie Work with Listening Policies Work with Playback Policies Work with Schedules Work with Agent Groups Work with Transaction Reco Work with Realms vReports View Big Board View General Reports View Component Events vSystem Administration Work with Agents Configure System Event Det Component Management Configure User Settings Work with Event Responses View System Events View Log Files View Management Server De gt Downloads Work with Agents 2 Deploy Generic Windows Component Go Alt g Name STI QoS J2EE Generic Windows Store and Forward M ibmtia Installed Running I tivices itsc austin ibm c com Ara Page 1 EO e a He installed linstalled Running Show All Agents Show Online Agents Show Offline Agents Fa Figure 9 37 Deploy Generic Windows Component 2 Select the Management Agent you wish to deploy the Generic Windows component to from the Work with Agents
393. oduction to Patterns for e business As companies compete in the e business marketplace they find that they must re evaluate their business processes and applications so that their technology is not limited by time space organizational boundaries or territorial borders They must consider the time it takes to implement the solution as well as the resources people money and time they have at their disposal to successfully execute the solution These challenges coupled with the integration issues of existing legacy systems and the pressure to deliver consistent high quality service present a significant undertaking when developing an e business solution In an effort to alleviate the tasks involved in defining an e business solution IBM has built a repository of patterns to simplify the effort In simple terms a pattern can be defined as a model or plan used as a guide in making things As such patterns serve to facilitate the development and production of things Patterns codify the repeatable experience and knowledge of people who have performed similar tasks before Patterns not only document solutions to common problems but also point out pitfalls that should be avoided IBM Patterns for e business consists of documented architectural best practices They define a comprehensive framework of guidelines and techniques that were actually used in creating architectures for customer engagements The Patterns for e business bridge the busines
394. oftware sla The LI may also be found in a Fs file in the Program s directory by the use of a system command or 7 1 accept the terms in the license agreement yl do not accept the terms in the license agreement InstallShield lt Back Next gt Cancel N Figure 4 24 License agreement panel gt We leave the installation directory on the default setting Figure 4 25 on page 110 We have previously created the opt IBM file system to serve as installation target Chapter 4 TMTP WTP Version 5 2 installation and deployment 109 E Install the Management Server E lol xl Click Next to install the management server to this folder or click Browse to install to a different folder Directory Name Popt tBH Tivolias Browse InstallShield lt Back Cancel Figure 4 25 Installation target folder selection gt In the next window Figure 4 26 on page 111 we enable the SSL for Management Server communication We previously created the prodms jks file which serves as the trust and key files We leave the port settings as the defaults 110 End to End e business Transaction Management Made Easy EA Install the Management Server pe lol x SSL Enablement for Management Server Communication Deselect the Enable SSL check box and click Next if you do not want to enable SSL To enable SSL select the Enable SSL check box and type the required information in the text boxes Enable S
395. olicy you specify a level of monitoring for each of the six subtransaction types You also specify a range of other parameters to establish how and when the policy runs Perform the following steps to create J2EE listening policies 1 Create and deploy a J2EE discovery policy and make sure that the transactions you want to include in the listening policy have been discovered 2 From the TMTP console home page select Configuration Work with Discovery Policies from the navigation pane on the left hand side This will display the Work with Discovery Policies dialog as shown in Figure 8 41 on page 289 End to End e business Transaction Management Made Easy 3 IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer 0 x Fie Edt view Favorites Tools Hep i Kai Address a http tivdce4 9082 tmtpUL jsp console WcFrameManager jsp fs Go Bak gt A A seach GFavortes meda C4 D 3 a a J x N Tivoli Monitoring for Transaction Performance User Name administrator J mywork B A ial Configuration c Work with Discove Work Discovery Policies Work with Listenin Work with Playbac Work with Sr J2EE Create New Alt w Work with Agent G Work with Transac 2 View Discovered Transactions x Go Alt g Work with Realms Reports Type Agent Group Schedule View Big Board View General Rept View Component E vSystem Administr Work with Agents Con
396. olicy that you create to monitor the banking application Threshold setting Management agents are capable of conducting a range of sophisticated threshold setting operations You can set basic performance thresholds that generate events and send notification when a transaction exceeds or falls below an acceptable performance time Other thresholds monitor for the existence of HTTP response codes or specified page content or watch for transaction failure In many cases you can specify thresholds for the subtransactions of a transaction A subtransaction is one step in the overall transaction HTTP Adaptor Connector J2EE Instrumentation Monitoring Engine Synthetic Transaction Investigator Bulk Data Handler Policy Manager Quality of Service Figure 3 5 Management Agent JMX architecture End to End e business Transaction Management Made Easy gt Event support Management agents send component events to the Management Server A component event is generated when a specified performance constraint is exceeded or violated during a listening or playback operation In addition to sending an event to the Management Server a Management Agent can send e mail notification to specified recipients run a specified script or forward selected event types to the Tivoli Enterprise Console or the simple network management protocol SNMP gt Communication
397. ollow the following steps to create a TMTP Version 5 2 report from Crystal Reports 1 Select Programs Crystal Reports Using the Report Expert gt OK Choose an Expert Standard 2 Select Database Open ODBC Choose the data source that you have created to connect to TWH_CDW database and select the appropriate database ID and password 3 Choose the COMP MSMT and MSMTTYP tables from the TWH_CDW database as shown in Figure 10 31 Click Add and Next to create the links Standard Report Expert F xj Data Links Fields Group Total Top N Chart Select Style Link together t Linking is need les you added to the report atch records of one table with corresponding records of another table Tables MSMTTYP MSMTTYP ID Arrange Tables MUNIT_CD MSRC_CD r Link Tables MSMTTYP_NM By Name COMP_ID MSMT_ID COMPTYP_CD COMP_ID CENTR_CD MSMTTYP_ID TMSUM_CD MSMT_STRT MSMTTYP_DS C ByKey MSMT_STAT Link MSMT_MIN_V MSMT_MAX MSMT_AVG_ Clear Links MSMT_TOT A7 Link Gptions Help Cancel lt lt Back Next gt gt Finish l Figure 10 31 Create links for report generation in Crystal Reports Chapter 10 Historical reporting 419 4 Click Field and choose fields from the list shown in Figure 10 32 i x Data Links Fields Group Total TopN Drill Chart Select Style Choose the information Wgtsplay on the report Sel
398. om 82 trade app action quotes amp sy Step_5_http ibmtiv9 itsc austin ibm com 62 trade app action portfolio Step_6_http ibmtiv9 itsc austin ibm com 62 trade app action logout OK Alt 0 Cancel Alt c Figure 8 10 Application steps run by trade_2_stock check playback policy 6 Click OK to import the XML document at the TMTP Version 5 2 Management Server 8 4 4 Playback schedule definition 248 Having uploaded the STI recording you are ready to define the run time parameters that will control the playback of the synthetic transaction This includes defining a schedule for the playback as well as a Listening Policy Follow the procedure below to create a schedule for running playback policy 1 Select Configuration Work with Schedules Create New The dialog shown in Figure 8 11 on page 249 will be displayed End to End e business Transaction Management Made Easy Tivoli Monitoring for Transaction Performance File Edit View Favorites Tools Help Address http tivdces itsc austin ibm com 9082 tmtpUL jsp console WcFrameManager jsp x Eo ay x z User Name administrator My Work Configuration Work with Discovery Policies Work with Listening Policies Work with Playback Policies Work wth SSE Work with Agent Groups Work with Transaction Recordings Work with Realms b Reports b System Administration b Downloads Figure 8 11 Creating a new playback schedule Select Configure S
399. om ARM API calls Dim appl_handle As Long Dim getid_handle As Long Dim start_handle As Long Dim stop_rc As Long Dim end_rc As Long Make ARM API setup calls and display the return from each one appl_handle arm_init Rational_tests 0 0 0 Remove line below when you put this in production MsgBox The return value from the arm_init call is amp appl_handle getid_handle arm_getid app l_handle Notepad Windows 0 0 0 Remove line below when you put this in production MsgBox The return value from the arm_getid call is amp getid_handle Start clock start_handle arm_start getid_handle 0 0 0 Remove line below when you put this in production MsgBox The return value from the arm_start call is amp start_handle Window SetContext Class Shell_TrayWnd Toolbar Click ObjectIndex 2 ItemText Notepad Coords 10 17 Window SetContext Caption Untitled Notepad InputKeys hello MenuSelect File gt Exit Window SetContext Caption Notepad PushButton Click Text No Appendix B Using Rational Robot in the Tivoli Management Agent environment 453 Stop clock stop_rc arm_stop start_handle 0 0 0 0 Remove line below when you put this in production MsgBox The return value from the arm_stop call is amp stop_rc Make ARM API cleanup call end_rc arm_end app _handle 0 0 0 Remove line below when you put this in production MsgBox The return val
400. ome One way is to use a Rational Robot Script that includes more than one transaction for example loops over the one transaction many times within the one script Another mechanism may be the use of multiple virtual machines on the one host with each virtual machine hosting its own Management Agent 6 Choose an agent group on which you want to run the playback see Figure 9 45 on page 373 Each of the Management Agents in the agent group must have had the Generic Windows component installed on it and the associated Rational Robot project created End to End e business Transaction Management Made Easy jew Favorites Tools Help Address a http tivdce4 9082 tmtpUI jsp console WcFrameManager jsp Tivoli Monitoring for Transaction Performance Configuration Work with Agent Groups Work with Discove Work with Listenir ee ybac Create New Alt w Work with Agent Agent Groups Work with Transac Please make a selection Go Alt g b Reports vSystem Administr Name STI O05 J2EE Generic Windows Number of Agents Work with Agents C petstore_j2ee_grp Fy an 1 Configure System m Component Mahal petstore_qos_grp x x xX 1 Configure User Se C sti gp E 1 Work with Event R tivab01 itse austin ibm comeo x x fx 1 View System Ever xp_genwin_grp x 1 View Log Files View Management Page 1 b Downloads z lt Bac
401. omponent Management Configure User Settings 7 v ibmtiva Work with Event Responses Ba bint View System Events m tive stin ibm com View Log Files o tivlabO1 View Management Server Details gt Downloads Page 1 Show All Agents Show Online Agents Show Offline Agents fei Configure Time Zones refresh rates etc fox Local intranet ZA Figure 8 33 Deploy J2EE and Work of agents Chapter 8 Measuring e business transaction response times 279 2 8 x Tivoli Monitoring for Transaction Performance Deploy Components and or Monitoring Component gt Configuration b Reports vSystem Adminisi Work with Agent Configure Syster Component Man Configure User Work with Event View System Evi View Log Files View Manageme gt Downloads Management Agent Name ibmtiv9 Choose Component or Monitoring Component Configure J2EE Monitoring Component Go Application Server Type Websphere gt Application Server Version 50 7 Application Serer Name Application Server Home servert esWVebSphere AppServer Cell Name Ema Node Name BMT M Automatically Restart the Application Server I Network Deployment is used by this server I Security is enabled on this server OK Alt 0 Apply Alt a Cancel Alt c Figure 8 34 J2EE deployment and configuration for WAS 5 0 1 3 Select a specific make and model of application server that applies to you
402. omponent on your computer IBM Tivoli Monitoring for Transaction Performance Management Server To continue click Next See the installation guide for detailed descriptions of the installation steps NOTE The installation program installs the required Java Virtual Machine InstallShield Figure 4 23 Welcome screen on the Management Server installation wizard gt We accept the license agreement in Figure 4 24 on page 109 and press Next 108 End to End e business Transaction Management Made Easy E3 Install the Management Server E BY DOWNLOADING INSTALLING COPYING ACCESSING OR USING THE PROGRAM YOU AGREE TO THE TERMS OF THIS AGREEMENT IF YOU ARE ACCEPTING THESE TERMS ON BEHALF OF ANOTHER PERSON OR A COMPANY OR OTHER LEGAL ENTITY YOU REPRESENT AND WARRANT THAT YOU HAYE FULL AUTHORITY TO BIND THAT PERSON COMPANY OR LEGAL ENTITY TO THESE TERNS IF YOU DO NOT AGREE TO THESE TERMS r is DO NOT DOWNLOAD INSTALL COPY ACCESS OR USE THE PROGRAM AND r k PROMPTLY RETURN THE PROGRAM AND PROOF OF ENTITLEMENT TO THE PARTY FROM WHOM YOU ACQUIRED IT TO OBTAIN A REFUND OF THE AMOUNT YOU PAID IF YOU DOWNLOADED THE PROGRAM CONTACT THE PARTY FROM WHOM YOU ACQUIRED IT is IBH is International Business Machines Corporation or one of its subsidiaries r E License Information LI is a document that provides information specific to a Program The Program s LI is available at http www ibm com s
403. on Engine and store a key Set bf CreateObject EncryptionAlgorithms BlowFish bf key ibm Begin Dialog UserDialog 180 90 Password Encryption Text 10 10 100 13 Password 1b1Pwd Text 10 50 100 13 Filename lblFile TextBox 10 20 100 13 txtPwd TextBox 10 60 100 13 txtFile OKButton 131 8 42 13 CancelButton 131 27 42 13 End Dialog Dim myDialog As UserDialog DialogErr answer Dialog myDialog If answer lt gt 1 Then Exit Sub End If If Len myDialog txtPwd lt 3 then MsgBox Password must have more than 3 characters 64 Password Encryption GoTo DialogErr End If Encrypt strEncrypt bf EncryptString myDialog txtPwd rational Save to file Open C secure txt For Output Access Write As 1 Write 1 strEncrypt Open myDialog txtFile For Output As 1 If Err lt gt 0 Then MsgBox Cannot create file 64 Password Encryption GoTo DialogErr End If Print 1 strEncrypt Close 1 If Err lt gt 0 Then Appendix B Using Rational Robot in the Tivoli Management Agent environment 465 466 MsgBox An Error occurred while storing the encrypted password 64 Password Encryption GoTo DialogErr End If MsgBox Password successfully stored 64 Password Encryption End Sub Running this script will generate the pop up window shown in Figure B 19 which asks for the password and name of a file to store the encrypted version of that password within
404. on provided in item 4 on page 270 for further details Click Next to finalize your policy definition 10 Having defined all the necessary properties of the J2EE listening policy all that is left before you can save and deploy the listening policy is to assign a name and determine when to deploy the newly defined listening policy to the Management Agents From the Assign Name dialog shown in Figure 8 45 on page 295 select your preferred distribution time provide a name for the J2EE listening policy and and click on Finish End to End e business Transaction Management Made Easy rancarkion Dari anra Micencofk Intarnak Funinvar ry AA TRM Tivoli Monikarina for T artian Darfarny Z IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer File Edit View Favorites Tools Help El Address a http tivdce4 9082 tmtpUL jspfconsole WeFrameManager jsp z Go Back gt gt A A Bsearch fajravorites Ameda B 3 SI a Tivoli Monitoring for Transaction Performance User Name administrator Configuration i s Create Listening Policy Assign Name Work with Discovery Work with Listening em Name he Work with Playback Configure J2EE Li trade _j2ee lis Description Work with Transactic Work with Realms Sent to Agents at next interval Send to Agents now gt Downloads lt Back Alt b Next Alten gt UES Cancel Alt c Ns Downloads Ei ea Lo
405. on that hard disk represents real value to the business in excess of 1000 Planning for recovery of the systems in case of a disaster also needs to be Chapter 1 Transaction management imperatives 15 addressed as being without computer systems for days or weeks may have a huge impact on the ability to conduct business There still is one important aspect to be covered for successfully managing and controlling computer systems We have mentioned various hardware and software components that collectively provide a service but which components are part of the IT infrastructure where are they and how do they relate to one another A prerequisite for successful management is the detailed knowledge of which components to manage how the components interrelate and how these components may be manipulated in order to control their behavior In addition now that IT has become an integral part of doing business it is equally important from an IT management point of view to Know which commitments we have made with respect to availability and performance of the e business solutions and what commitments our subcontractors have made to us And for planning and prioritization purposes it is vital to combine our knowledge about the components in the infrastructure with the commitments we have made in order to assess and manage the impact of component malfunction or resource shortage In short in a modern e business environment one of the most important
406. onents involved in an average sized Web application system management of all of these resources is more an art than a science We begin by providing a short description of the challenges of e business provisioning in order to identify the management needs and issues related to provisioning e business applications 1 2 J2EE applications management Application management is one of the fastest growing areas of infrastructure management This is a consequence of the focus on user productivity and confirms the fact that more and more we are moving away from device centric management Within this segment today J2EE platform management is only a fairly small component However it is easy to foresee that J2EE is one of the Chapter 1 Transaction management imperatives 5 next big things in application architecture and because of this we may well see this area converted into a bigger slice of the pie and eventually envision much of the application management segment being dedicated to J2EE Because J2EE based applications cover multiple internal and external components they are more closely tied to the actual business process than other types of application integration schemes used before The direct consequence of this link between business process and application is that management of these application platforms must provide value in several dimensions each targeted to a specific constituency within the enterprise such as gt The enterpris
407. onfigure J2EE Settings Work with Listening Configure J2EE Thresholds Work with Playback Threshold Type Work with Schedule kis Si Performance x Create Alt e e P l No Entries b System Administrat 2 b Downloads R Show Enabled Thresholds Show Disabled Thresholds 2EE Listener Advanced Listening Settings Choose Default Configuration Low hd Trace Detail Level Off 1 2 3 Servlet 6 o O Session EJB 0oo 6 Entity EJB ooc JMS 6060 6 JDBC oC C0C 6 RMI IIOP 6 Filter Threshold Events by Time Percentage Failed I Enable Intelligent Event Generation E Work with J2EE Listening Policies Choose Create Edit etc eg internet Figure 6 9 Configuring the J2EE Trace Level End to End e business Transaction Management Made Easy The next time a violation occurs on that system the monitoring component will automatically switch to collect instance data at its higher tracing detail Customers with high traffic Web sites should set the sample rate lower than 20 and specify the maximum number of instances after failure on the Configure J2EE Listener page Figure 6 10 shows how to set Sample Rate and specify the maximum number of Instances after failure IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer i 0 xj File Edit View Favorites Tools Help Address a http 9 3 4 230 9082jtmtpUI isp console WcFrameManager jsp x co Back gt
408. onitoring for Transaction Performance Web Transaction Performance WTP gt Introduction to the components of WTP gt Discussion of the various technologies used by WTP gt Putting it all together to implement a transaction monitoring solution for your e Business environment Copyright IBM Corp 2003 All rights reserved 55 3 1 Architecture overview As discussed in Chapter 2 IBM Tivoli Monitoring for Transaction Performance in brief on page 37 IBM Tivoli Monitoring for Transaction Performance hereafter referred to as TMTP is an application designed to ease the capture of Transaction Performance information in a distributed environment TMTP was first released in the mid 90s as two products Tivoli Web Services Manager and Tivoli Application Performance Monitoring These two products were designed to perform similar functions and were combined in 2001 into a single product IBM Tivoli Monitoring for Transaction Performance This heritage is still reflected today by the existence of two components of TMTP the Enterprise Transaction Performance ETP and Web Transaction Performance WTP components This release of TMTP blurs the distinction between the components and sets the stage for future releases where there will no longer be a distinction between ETP and WTP 3 1 1 Web Transaction Performance The IBM Tivoli Monitoring for Transaction Performance Web Transaction Performance component is the area of the TMTP product whe
409. ons in situations where the child transactions execute on different systems The recommendation is to synchronize the system clocks if you are concerned about the presentation of sibling transaction ordering This release of TMTP adds the notion of aggregated correlation Aggregated correlation will provide aggregate information that is does not create a record for each and every instance of a transaction but a summary of a transaction over a period of time Instead of a singular transaction being aggregated correlation will be used Previous versions of TMTP only allowed correlation at the instance level which could be an intensive process The logging of transactions will usually start out as aggregated correlation There may be times when a registered measurement entry will be provided to the ARM Engine that will ask for instance logging or the ARM Engine itself may turn on instance logging in the event of a threshold violation There are essentially three ways TMTP treats aggregated correlation 1 Edge aggregation by pattern 2 Edge aggregation by transaction name edge discovery mode 3 Aggregation by root parent transaction For edge aggregation by pattern we essentially have one aggregator per edge policy that all transactions that match that edge policy pattern will be aggregated against For edge aggregation by transaction name we essentially have a unique aggregator for each transaction name that matches this policy s edg
410. ons inside the script sequentially including one in another or overlapping To load the ARM API you can add code similar to Example 9 2 in the script header or cut the sample below and paste it into your script directly This may help avoid typing errors Example 9 2 Script ARM API declaration Declare Function arm_init Lib libarm32 ByVal app _name As String ByVal appl_userid As String ByVal flags As Long ByVal data As String ByVal data_size As Long As Long Declare Function arm_getid Lib libarm32 ByVal appl_id As Long ByVal tran_name As String ByVal tran_detail As String ByVal flags As Long ByVal data As String ByVal data_size As Long As Long Declare Function arm_start Lib libarm32 ByVal tran_id As Long ByVal flags As Long ByVal data As String ByVal data_size As Long As Long Chapter 9 Rational Robot and GenWin 351 Declare Function arm_stop Lib libarm32 ByVal start_handle As Long ByVal tran_status As Long ByVal flags As Long ByVal data As String ByVal data_size As Long As Long Declare Function arm_end Lib libarm32 ByVal appl_id As Long ByVal flags As Long ByVal data As String ByVal data_size As Long As Long To declare variables to hold returns from ARM API calls add the script in Example 9 3 Example 9 3 ARM API Variables Dim app l_handle As Long Dim getid_handle As Long Dim start_handle As Long Dim stop_rc As Long Dim end_rc As Long All the code above can be put at the top of the script Next you must init
411. ons into a single event making notification more useful and Chapter 8 Measuring e business transaction response times 293 294 reports such as the Big Board and the View Component Events table much more meaningful ii Type 1 2 3 4 or 5 in the Minutes field If you enable intelligent event generation you must fill both the Minutes and the Percent Violations fields The Minutes value specifies a time interval during which events that have occurred are merged For example if you specify two minutes events are merged every two minutes during monitoring Note that 1 2 3 4 and 5 are the only allowed values for the Minutes field Type a number in the Percent Violations field to indicate the percentage of transactions that must violate a threshold during the specified time interval before an event is generated For example if you specify 80 in the Percent Violations field 80 of transactions that are monitored during the specified interval must violate a threshold before an event is generated The generated event describes the worst violation that occurred during the interval 8 Schedules for J2EE listening policies are selected the same way as for any other policy Please refer to 8 4 4 Playback schedule definition on page 248 for more details related to schedules Click Next to go on to select Agent Groups for the listening policy 9 Agent Group selection is common to all policy types Please refer to the descripti
412. orites Tools Help eBack gt A A Asearch Favorites Zmeda C4 B S Ei a Address http tivdee 9082 tmtpLjsp console WeFrameManager jsp a i E co Tivoli Monitoring for Transaction Performance User Name administrator All Times are in Seconds AS ongan amp g Configuration Work with Discover Work with Listening Work with Playback Work with Schedule Work with Agent Gr Work with Transacti Work with Realms vReports View Big Board View General Repor J2EE Filler 0 026 0 671 Session EJB Entity EJB JDBC 0 161 0 234 0 04 Configure System E Component Manage Configure User Sett Work with Event Re View System Event Miawe nn Filac z af gt view Component Events om al ZB Local intranet A L IESS Figure 8 69 Problem indication in topology view of Pet Store J2EE application From the topology view we can jump directly to the Response Time View for the particular application component as shown in Figure 8 70 on page 322 in order to get the report shown in Figure 8 71 on page 322 Chapter 8 Measuring e business transaction response times 321 IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer File Edit View Favorites Tools Help gt A A Asearch Favorites Meda D 3 SI EF bs http ftivdce4 9082 tmtpUI jsp console WcFrameManager jsp Tivoli Monito
413. orts Transaction Backend Service Time_2 View Big Board View General Reports 2 S 3 0 View Component Events System Administration Work with Agents S Average Configure System Event Min Max Range Component Management 0 7 Configure User Settings Work with Event Respons View System Events Seansds View Log Files View Management Server gt Downloads 02 0 0 10 01 10 01 10 02 10 02 10 02 Esia 19 00 23 45 04 30 09 15 14 00 Time gt Year Month Day Hour Minute ES View Component Events fax Local intranet A Figure 8 52 Response time view of QoS Back end service 1 time Looking at the overall Trade application response time shown in Figure 8 52 we can break down the application response time gt EJB response time see Figure 8 53 on page 304 and Figure 8 54 on page 305 gt JSPpages response time gt JDBC response time see Figure 8 55 on page 306 and drill down to its child methods or execution In this way we can find any bottleneck of the application server database or HTTP server by using different TMTP components synthetic and real Chapter 8 Measuring e business transaction response times 303 304 EY IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer File Edit View Favorites Tools Help Back gt A A Asearch Gyravorites meda Co B S Sf a Tivoli Monitoring for Transaction Performance User Name administrator z Policy trade_j2e
414. ory of the user used for the installation in our case root If this file is not modified it will prevent later reinstall attempts for TMTP as it may indicate to the installation process that a particular product is already installed Generally you will only need to remove entries in this file that relate to products you have manually deleted In our test environment it was generally safe to delete the file as the only IBM Tivoli product we had installed was TMTP gt On UNIX platforms WebSphere Application Server and DB2 will generally use native package install processes for example RPM on Linux This means that a brute force install may leave the package manager information in an inconsistent state 6 5 3 Removing GenWin from a Management Agent Chapter 6 Removing a Component of the BM Tivoli Monitoring for Transaction Performance Installation Guide Version 5 2 0 SC32 1385 covers uninstalling the GenWin behavior from a Management Agent One of the points it highlights is that you must delete the Rational Robot project that you are using for the GenWin behavior prior to removing the GenWin behavior This point is important as removing the GenWin behavior will delete the directory used by the Rational Robot project associated with that GenWin behavior The ramification of this is that if you have not previously deleted the Rational Robot project you will not be able to create a new Rational Robot project with the same name as t
415. osoft Internet Explorer E lojx File Edit View Favorites Tools Help Address fa http x220svr dmwhe WeWworkAreaManager x Go Back gt OA A Qsearch Favorites Meda J Br GR B O onitoring User Administrator amp Signoff Endpoint panda Health Console Endpoint List View gt panda Resource Models on panda Indications Historical Data Select an action X Select Name Profile Status Health Monitoring for WebSphere Application Server panda Site C WebSphereAS_HTTP_Sessions_10 Analyzer WAS_BP_ApplSvr amp 220svr reaion Running 67 AV z Monitoring for WebSphere Application Server panda Site P o epin e ie Analyzer WAS_BP_ApplSvr x220svr region pama eel C Processor TMW2k_TMTP x220svr region Running 90 E C Memory Memory Win2k x220svr reaion Running 94 E H Indications on WebSphereAS_WebApps_10 j E Select Name Instance Health e WebSphereAS_high_Application_Server_servlet_response_time Name Node panda ApplicationServer Site Analyzer 89 E WebSphereAS_high_VWeb_Application_servlet_response_time Name Site Analyzer SiteAnalyzer Admin Webapp 89 M c WebSphereAS_high_Application_Server_serviet_errors 100 e WebSphereAS_high_Servlet_errors 100 B i e WebSphereAS_high_Servlet_response_time 100 E le WWehSnhereAS hinh Weh Annlicatian ceret errare ann m lE Done eR tocalintranet Figure 5 6 Web Health Console using WebSphere Application Server For detailed information on setting up an
416. ost operating system of the Management Server The required level of this particular version is 4 3 3 10 or higher We have previously applied the fix pack for this level To check if the operating system on the correct level issue the command shown in Example 4 1 its output is included as well Example 4 1 Output of the oslevel r command oslevel r 4330 10 2 File system creation The installation of the Management Server requires 1 1 GB of free space on AIX additionally we also need 1 GB of space for the TMTP database We have created two file systems as shown in Table 4 1 on page 89 End to End e business Transaction Management Made Easy Table 4 1 File system creation opt IBM 1 5 GB The TMTP installation will be performed here opt IBM dbtmtp 1 GB The TMTP database will reside in this directory install 4 GB This will be the root directory of the installation depot and the temporary installation directory during the product installation This will be removed once the installation is finished successfully 3 Depot directory creation There are two ways to install the TMTP either you use the original CDs or you download the installation code In the second case you need to create a predefined installation depot directory structure We are using the second option The following structure has to be created even if you are using a custom installation scenario however you do not have to copy the installation sou
417. ostly on availability and performance will have to evolve toward service assurance and business systems management Organizations should look at the following before selecting a tool for transaction monitoring 1 The product selected for the management of the J2EE application server meets the following requirements a Provides a real time Service assurance and an in depth analysis component preferably with a root cause analysis and corrective action mechanism b Integrates with the existing infrastructure products downstream enterprise console and help desk and upstream reuse of agents c Provides customized reporting for the different constituencies business development and operations 2 The IT operation organization is changed to reflect the added complexity of the new application infrastructure to a Handle more event types in the operation center Transaction availability events and performance events are typical of the new applications as well as events related to configuration and code problems 10 End to End e business Transaction Management Made Easy b Create additional competency groups within IT operation with the ability to receive and analyze application related problems in cooperation with the development groups c Improve the communication and cooperation between competency silos within IT operations since many problems are going to involve multiple hardware and software platforms d Establish
418. osure to security violations However the actual components such as application servers and infrastructural resources may vary depending upon the nature of the applications company policies the requirements to availability and performance and the capabilities of the technologies used If you are in the e business hosting area or you have to support multiple lines of business that require strict separation the conceptual architecture shown in Figure 1 6 on page 21 may be even more complicated In these situations one or more of the tiers may have to be duplicated to provide the required separation In addition the back end tier might even be established remotely relative to the application tier This is very common when the e business application hosting is outsourced to an external vendor such as IBM Global Services To help design the most appropriate architecture for a specific set of e business applications IBM has published a set of e business patterns that may be used to speed up the process of developing e business applications and deploying the infrastructure to host them The concept behind these e business patterns is to reuse tested and proven architectures with as little modification as possible IBM has gathered experiences from more than 20 000 engagements compiled these into a set of guidelines and associated them with links A solution architect can start with a problem and a vision for the solution and then find a patte
419. oth installation we created the installation depot as described in 4 1 2 Step by step custom installation of the Management Server on page 107 and copied all the necessary products to the relevant directories Our installation depot location is install The output of the 1s 1 install is shown in Example 4 3 Example 4 3 View install depot tmtp linux sbin 1s 1 install total 1233316 drwxr xr x 7 root root 4096 Sep 16 08 26 drwxr xr x 20 root root 4096 Sep 16 12 06 rw r r 1 root root 885 Sep 8 09 57 MS opt rw r r 1 root root 1332 Sep 8 09 57 MS_db2_embedded_unix opt rw r r 1 root root 957 Sep 8 09 57 MS_db2_embedded_w32 opt rw r r 1 root root 10431 Sep 8 09 57 MsPrereqs xml drwxr xr x 5 root root 4096 Sep 16 04 53 db2 rw r r 1 root root 233 Sep 8 09 57 dm_db2_1 dd1 drwxr xr x 2 root root 4096 Sep 8 09 57 keyfiles drwxr xr x 4 root root 4096 Sep 18 15 49 lib rw r r 1 root root 12 Sep 8 09 57 media inf rw r r 1 root root 3792 Sep 8 09 57 prereqs dtd rw r r 1 root root 16384 Sep 8 09 57 reboot exe rw r r 1 root root 532041609 Sep 8 09 58 setup_MS jar rw r r 1 root root 18984898 Sep 8 09 58 setup_MS_aix bin rw r r 1 root root 24 Sep 8 09 58 setup_MS_aix cp rwXr xr x 1 root root 20824338 Sep 8 09 58 setup_MS_lin bin rw r r 1 root root 24 Sep 8 09 58 setup_MS_lin cp rw r r 1 root root 19277890 Sep 8 09 58 setup_MS_lin390 bin rw r r 1 root root 24 Sep 8 09 58 setup_MS_
420. ottleneck 205 breakdown 33 220 223 STI transaction 220 transaction 4 35 70 transaction view 215 view 215 Brio Technology 377 browser 59 brute force 195 business process 8 system 30 Business Information Service 31 Business Intelligence 377 business intelligence reporting 379 Business Objects 377 BWM source information 192 483 BWM_c05_Upgrade_Processes 392 BWM_c05_Upgrade51_Process 400 BWM_c10_CDW_Process 400 BWM_DATA_SOURCE 399 BWM_m05_Mart_Process 400 BWM_TMTP_DATA_SOURCE 393 BWM_TWH_CDW_SOURCE 399 BWM_TWH_CDW_TARGET 400 BWM_TWH_MART_SOURCE 400 BWM_TWH_MART_TARGET 400 BWM_TWH_MD_TARGET 400 Cc cache size 186 Capacity Management 18 categories reporting 409 cause problem 212 CDW See central data warehouse central console 13 Central Data Warehouse 379 central data warehouse ETL 379 centralized management 365 monitoring 14 certificate 77 101 179 Change Management 19 Client Capture 59 client server 12 Cognos 377 collect performance data 157 Comments 224 common dimensions 376 Common Warehouse Metadata 377 component report 413 service 16 confidentiality 76 configuration adapter 168 DB2 91 playback 371 schedule 371 SnF agent 77 treshold 371 WebSphere 91 Configuration Management 18 Configure Schedule 249 connection ODBC 393 connection pool 163 console central 13 consolidate 187 constraint 29 Contingency Planning 18 control heap size 385 controlled measurement 35 cookie 338 correctiv
421. ough an authenticating HTTP proxy and a STI subtransaction is specified to a Web server redirected page Generic Windows can be used to circumvent these problems Quality of Service Quality of Service is used to provide real time transaction performance measurements of a Web site In addition QoS provides metrics such as User Experienced Time Back End Service Time and Round Trip Time Note QoS is the only measurement component of IBM Tivoli Monitoring for Transaction Performance Version 5 2 that records real time user experience data Like STI monitoring using QoS may be combined with J2EE monitoring to provide transaction breakdown and subtranaction response times for each transaction instance run through QoS For details on how Quality of Service works please see 3 3 1 ARM on page 67 J2EE The J2EE monitoring component is used to analyze real time J2EE application server transaction performance and status information of gt Servlets gt EJBs gt RMis gt JDBC objects J2EE monitoring collects instance level metric data at numerous locations along the transaction path It uses JITI technology to seamless insert probes into the Java methods at class load time These probes issue ARM calls where appropriate 232 End to End e business Transaction Management Made Easy For practical monitoring J2EE is often combines with one of the other monitoring components typically STI or GenWin in order to provide transaction
422. ount If the user is not already a member of the Administrators group the user will be added OR Create a dedicated administrative user account The default name is TMTPAgent You have the option to change this name to a unique string Specify an existing user account Create a new dedicated user account User Administrator Password hipid Verify Password wasaa InstallShield lt Back Next Cancel Figure 4 40 User Account specification window 9 We press Next in the window shown in Figure 4 41 on page 126 and the installation starts to install the Store and Forward agent first Figure 4 42 on page 127 Chapter 4 TMTP WTP Version 5 2 installation and deployment 125 ma Install Store and Forward Agent ae IBM Tivoli Monitoring for Transaction Performance Store and Forward Agent will be installed in the following location C Program FileswBMiTivolitSnF for a total size 72 1MB InstallShield Back Next gt j Cancel Figure 4 41 Summary before installation 126 End to End e business Transaction Management Made Easy we Install Store and Forward Agent A 10l x Installing IBM Tivoli Monitoring for Transaction Performance Store and Forward Agent Please wait 46 Cancel InstallShield Figure 4 42 Installation progress 10 Once the installation of the Store and Forward agent is completed Figure 4 43 on page 128 the setup installs the WebSphere Cach
423. overy policy 3 Provide the filtering values of your choice and click Next to proceed to schedule selection for the discovery policy In the example shown in Figure 8 37 we want to discover all user requests to the trade application as specified in the URI Filter and User name URI Filter http trade User name i Note The syntax used to define filters are that of regular expressions If your are not familiar with these please refer to the appropiate appendix in the manual BM Tivoli Monitoring for Transaction Performance User s Guide Version 5 2 0 SC32 1386 4 Use the Work with Schedules dialog depicted in Figure 8 38 on page 285 to select a schedule for the discovery policy Details regarding schedule definitions are provided in 8 4 4 Playback schedule definition on page 248 284 End to End e business Transaction Management Made Easy IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer Fie Edit View Favorites Tools Help Address http ftivdces Tivoli Monitoring for Transaction Performance User Name administrator Configuration Work with Discovery Policies Work with Listening Policies 5 i Create New Alt w Work with Playback Policies came Work with Schedules Work with Agent Groups Ey Schedule Table Work with Transaction Recordings x seas J Please make a selection rege ease make a selection Go Alt g Work with Realms ign Name _ Go attg b Reports
424. own as columns Uploaded aggregate data are used to update the Average Min Max column so that even if there is no event activity the row is changing Clicking the monitoring policy name displays a summary table describing the policy s details while clicking the Event icon displays a table with all the events for that policy Table 7 1 Big Board Icons Ca Display transaction events Display STI graph Display Topology View Export to CSV file Refresh view 214 End to End e business Transaction Management Made Easy The Big Board provides two entry points into further reporting The first is by clicking on the Display STI graph icon where you are taken to the STI Bar chart view The second is accessed by clicking on the Display Topology View icon which brings you to the Topology View A refresh rate may be set and stored in the user s settings to update the Big Board at a certain interval Users also have the option of clicking on the Refresh View icon to manually refresh the view The Big Board s columns may be filtered by entering criteria into the drop down box at the bottom of the dialog and choosing a column to filter The filtering is done by finding all the columns that start with the letters entered in the text field Data may be exported from the Big Board by clicking on the Export to CSV icon 7 4 Topology Report overview The Topology Report provides a breakdown view of a transaction as encountered on th
425. plications may be restricted to users whose identity can be authenticated In other instances for example online news services there are user authentication requirements for access to the application In either case the goal of the application is to provide useful information to the user and of course attract the user to return later The service provided to the user in terms of functionality ease of use and responsiveness of the application is critical to the user s perception of the application s usefulness If the user finds the application useful there is a fair chance that the user will return to conduct more business with the application owner The usefulness of an application is a very subjective measure but it seems fair to assume that an individual s perception of an application s usefulness involves at the very least Relevance to current needs Easy to understand organization and navigation Logical flow and guidance The integrity of the information is it trustworthy Responsiveness of the application YYYY Y Naturally the application owner can influence all of these parameters the application design can be modified the data can be validated and so on but network latency and the capabilities of the users system are critical factors that may affect the time it takes for the user to receive a response from the application To avoid this becoming an issue that scares users away from the application the app
426. porting 399 b In the Password field type the password used to access the central data warehouse database c Do not change the value of the Data Source field It must be TWH_CDW Specify the following properties for the target BVWM_TWH_MART_SOURCE a Inthe User ID field type the user ID used to access the data mart database The default value is db2admin w b In the Password field type the password used to access the data mart database c Do not change the value of the Data Source field It must be TWH_MART 4 Specify the properties for the warehouse target BWM_TWH_CDW_TARGET a In the User ID field type the user ID used to access the central data warehouse database The default value is db2admin b In the Password field type the password used to access the central data warehouse database c Do not change the value of the Data Source field It must be TWH_CDW 5 Specify the following properties for the target BWM_TWH_MART_TARGET a In the User ID field type the user ID used to access the data mart database The default value is do2admin b In the Password field type the password used to access the data mart database c Do not change the value of the Data Source field It must be TWH_MART 6 Specify the properties for the target BWM_TWH_MD_TARGET a In the User ID field type the user ID used to access the control database The default value is db2admin b In the Password field type the password us
427. posite patterns that represent commonly occurring combinations of Business patterns and Integration patterns Application patterns that provide a conceptual layout describing how the application components and data within a Business pattern or Integration pattern interact Runtime patterns that define the logical middleware structure supporting an Application pattern Runtime patterns depict the major middleware nodes their roles and the interfaces between these nodes Product mappings that identify proven and tested software implementations for each Runtime pattern Best practice guidelines for design development deployment and management of e business applications These assets and their relationship to each other are shown in Figure A 1 Customer requirements Composite patterns Business y patterns Application patterns Runtime patterns e Application Design e Systems Management Product Performance roduc Application Development mappings e Technology Choices Integration patterns Best Practice Guidelines Figure A 1 Patterns layered asset model End to End e business Transaction Management Made Easy Patterns for e business Web site The Patterns Web site provides an easy way of navigating top down through the layered Patterns assets in order to determine the preferred reusable assets for an engagement For easy reference to Patterns for e business refer to the Patterns fo
428. prise TMTP J2EE monitoring collects instance level metric data at numerous locations along the transaction path Servlet Metric Data includes URI querystring parameters remote host remote user and so on EJB Metric Data includes Chapter 3 IBM TMTP architecture 75 primary key EJB type stateful stateless and entity and so on JDBC Metric Data includes SQL statement remote database host and so on JITI probes make ARM calls and generates correlators in order to allow subtransactions to be correlated with their parent transactions The primary or root transaction is the transaction that has no parent correlator and indicates the first contact of the transaction with TMTP Each transaction monitored with TMTP gets its own correlator as does each subtransaction When a subtransaction is started ARM can link it with its parent transaction based on the correlators and so on down the tree With the correlator information ARM can build the call tree for the entire transaction If a transaction crosses J2EE Application Servers on multiple hosts the ARM data can be captured by installing the Management Agent on each of the hosts Only the host that registers the root transaction need have a J2EE Listening Policy TMTP Version 5 2 J2EE monitoring summarized gt JITI provides the ability to monitor the fine details of any J2EE applications It does this by dynamically inserting probes at run time gt There is no need to re run a
429. prise Console The WebSphere Event Tasks TaskLibrary also includes two tasks with which you can start and stop the Tivoli Enterprise Console adapter The task names are gt Start_WebSphere_TEC_Adapter gt Stop_WebSphere_TEC_Adapter 5 1 5 Event handling 168 Tivoli Enterprise Console TEC has been designed to receive events from multiple sources and process them in order to correlate and aggregate them and issue predefined corrective actions based on the processing TEC works on the basis of events and rules TEC events are defined in object oriented definition files called BAROC files These events are defined hierarchically according to their type Each event type is called an event class When TEC receives an event it parses the event to determine the event class and then apply the class definition to parse the rest of the event when the parsing is successful the event is stored in the TEC database When a new event is stored a timer expires or a field known in TEC terminology as a slot has changed TEC evaluates a set of rules to be applied to the event These rules are stored in ruleset files which are written in the Prolog language When a matching rule is found the action part of the rule is executed These rules enable events to be correlated and aggregated Rules also enable automatic responses to certain conditions usually these are corrective actions In the IBM Tivoli Monitoring for Web Infrastructure perspect
430. prompted to set up the working environment for projects Decide on the location of your project Before proceeding open Windows Explorer and create the top level directory of the project Make sure the directory is empty An example is shown in Figure B 3 QCA BAX File Edit View Favorites Tools Help a Q Back A Search E gt Folders x Address ae C JPE Folders x Name Size Type Date Modified fed Desktop A bea File Folder 2 20 2003 2 17 PM E 3 my Documents Documents and Settings File Folder 5 30 2002 10 43 ar W My Computer ve File Folder 5 30 2002 1 28 PM rs B 314 Floppy 4 Infoprint File Folder 12 11 2002 1 27 PM S PROGRAMS C languages File Folder 5 30 2002 1 30 PM D bea lexmark File Folder 7 8 2002 2 41 PM Documents and Settings omy Music File Folder 7 18 2002 9 47 AM DE RationalTest File Folder 3 11 2003 3 38 PM a Infoprint Notes File Folder 5 30 2002 1 45 PM a O languages SpnotesSbkp File Folder 12 18 2002 1 03 Pr O lexmark Program Files File Folder 5 30 2002 10 52 Al My Music Osdwork File Folder 5 30 2002 1 35 PM O Notes temp File Folder 5 30 2002 2 16 PM notesSbkp winoows File Folder 5 30 2002 10 40 Ar O Program Files _NavCclt Log 60KB Text Document 8 20 2002 1 32 PM RationalTest E address cs 2KB C Source file 12 12 2002 5 26 Pr a O sdwork cpsweb log 6KB Text Document 12 11 2002 1 34 Pr O temp f customer cs 2KB
431. r environment The Deploy Components and or Monitoring Component is built dynamically based upon the type of application server you select The values you are requested to supply are summarized in Table 8 2 on page 281 Please consult the manual BM Tivoli Monitoring for Transaction Performance User s Guide Version 5 2 0 SC32 1386 for more details on each of the properties End to End e business Transaction Management Made Easy Table 8 2 J2EE components configuration properties Application Server make Property Example value and model Application Server Name Default Server Application Server Home C WebSphere AppServe C WebSphere AppServer java Administrative Port 8008 Number Automatically Restart the Check Application Server Application Server Home C Progra 1 WebSphere AppServer Bere crete em a Node Manager starts this Check in applicable server To define the properties for the deployment of the J2EE component to a Management Agent installed on a WebSphere Application Server 5 01 system specify properties like the ones shown in Figure 8 34 on page 280 and click OK to start the deployment After a couple of minutes the Management Agent will be rebooted and the J2EE component has been deployed WebSphere Application Server Version 4 WebSphere b o gt a o c S2 3 5 2 gt a a lt Weblogic Version 7 0 Chapter 8 Measuring e business transaction response times 281 4 To ve
432. r Transaction Performance TMTP in order to measure typical end user response times Copyright IBM Corp 2003 All rights reserved 439 Rational Robot Rational Robot is a functional testing tool that can capture and replay user interactions with the Windows GUI In this respect it is equivalent to Mercury s WinRunner and we are using it to replace the function that was lost when we were forced to remove WinRunner from TAPM Robot can also be used to record and play back user interaction with a Java application and with a Java applet that runs in a Web browser Documentation is included as PDF files in the note that accompanies this package Tivoli Monitoring for Transaction Performance TMTP 440 TMTP includes a component called Enterprise Transaction Performance ETP The core of ETP is an Application Response Measurement ARM agent which recognizes start and stop calls made by an application or script and uses them to report response time and other data in real time and historical graphs Since ETP is fully integrated with the Tivoli product set thresholds can be set on response time and TEC events can be created when the response time is too long ETP saves its data in a database from which it can be displayed with TDS or sent to the Tivoli Data Warehouse and harvested using TSLA This way standard capabilities of the TMTP ETP product are used to measure response time which can also be viewed in real time g
433. r admin opens the script VBMenus which is in the project file Default rsp located in the directory c Sample Files Projects The script is opened for playback and then it is closed when playback ends The results are recorded in the MyLog log located in the Default directory Obfuscating embedded passwords in Rational Scripts 464 Often when recording Rational Scripts it is necessary to record user IDs and passwords This has the obvious security exposure that if your script is viewed the password will be viewable in clear text This section describes a mechanism for obfuscating the password in the script This mechanism relies on the use of an encryption library The encryption library that we used is available on the redbook Web site The exact link can be found in Appendix C Additional material on page 473 First the encryption library must be registered with the operating system For our encryption library this was achieved by running the command regsvr32 exe EncryptionAlgorithms d1 Once you have run this command you must encrypt your password to a file for later use in your Rational Robot scripts This can be achieved by creating a Rational Robot Script from the text in Example B 1 and then running the resulting script Example B 1 Stashing obfuscated password to file Sub Main Dim Result As Integer Dim bf As Object Dim answer As Integer End to End e business Transaction Management Made Easy Create the Encrypti
434. r bin ijitipi dll 14 The application servers running on this node may now be started 200 End to End e business Transaction Management Made Easy Manual uninstall of J2ZEE component on Weblogic 7 The following procedure outlines the steps needed to perform a manual uninstall of the TMTP J2EE component from a Weblogic server 1 The WebLogic 7 installation has two options A script starts this server and Node Manager Starts this server One or both of those options can be selected when J2EE Instrumentation is installed If J2EE Instrumentation was installed with A script starts this server follow steps 2 and 3 If the J2EE Instrumentation used Node Manager starts this server follow steps 4 through 7 Finally follow steps 8 10 to clean up any files that were used by J2EE Instrumentation 2 Edit the script that starts the WebLogic 7 server The script is a parameter to the installation which may be something similar to C beaHome701 user_projectsAJL mydomain startPetStore cmd 3 In the script remove the lines from rem Begin TMTP App IDnnn to rem End TMTP App IDnnn where nnn is a UUID such as 101 102 and so on The text to be removed will be similar to Example 6 4 Example 6 4 Weblogic TMTP script entry rem Begin TMTP AppID169 if SSERVER_NAME thinkAndy set PATH C ma 2003 07 03 0015 app instrument 1ib windows PATH if SSERVER_NAME thinkAndy set MA C ma 2003 07 03 0015 if SERVER_NAME
435. r e business Web site at http www ibm com developerWorks patterns How to use the Patterns for e business As described in the previous section the Patterns for e business are structured so that each level of detail builds on the last At the highest level are Business patterns that describe the entities involved in the e business solution A Business pattern describes the relationship among the users the business organization or applications and the data to be accessed Composite patterns appear in the hierarchy above the Business patterns However Composite patterns are made up of a number of individual Business patterns and at least one Integration pattern In this section we discuss how to use the layered structure of the Patterns for e business assets There are four primary Business patterns as shown in Table A 1 Table A 1 Business patterns Self Service Applications where users Simple Web site user to business interact with a business via applications the Internet Information Aggregation Applications where users Business intelligence user to data can extract useful knowledge management information from large and Web crawlers volumes of data text images and so on Collaboration Applications where the E mail community chat user to user Internet supports video conferencing and so collaborative work on between users Extended Enterprise Applications thatlinktwoor EDI supply chain business to busine
436. r local system In our case we used db2admin Click Next Tivoli Enterprise Data Warehouse Installation 3 Ale x Enter the information for configuring DB2 on the local system Enter the user name and password to use to access DB2 on the local system User name Jab2admin Password lt Back Next gt Cancel Figure 10 7 TEDW installation DB2 configuration 7 The path to the installation media for the application packages dialog appears next as shown in Figure 10 8 amp Tivoli Enterprise Data Warehouse Installation Enter the path to the installation media for the application packages or click Browse to select a folder This directory must contain the file twh_app_install_listefa Directory name Ic litmtpS2itedw_apps_etlibwm When do you want to verify that the source directory is accessible and that it contains the correct files Now prevents typing errors Later during the installation phase reduces the number of CD swaps when installing from a local CDROM drive Tivoli InstallShield Back Next gt Cancel Figure 10 8 Path to the installation media for the ITM Generic ETL1 program You should provide the location of the appropriate IBM Tivoli Monitoring for Transaction Performance ETL1 program Change the TEDW CD in the CD ROM drive with the desired installation CD Specify the path to the installation file named twh_app_install_list cfg Chapter 10 Historical
437. r must be of the same kind and use the same settings as the one where the simulation is recorded A typical error is to have different settings for the cookies so that one browser accepts End to End e business Transaction Management Made Easy them while the other displays a dialog to the user thus breaking the simulation flow Differences for Netscape users We recommend using Netscape 4 x only if it is specifically needed since it requires local browser caching to be enabled and would not simulate applications using HTTPS Also Netscape 4 7x and Netscape 4 x are mutually exclusive if you want to use one you should not select the other 9 1 2 Configuring a Rational Project Before you can record a Rational Script you must have a valid Rational Project to use During Rational Robot installation you will be taken through the following procedure However you will also have to use this procedure to create a Rational Robot project for use by the Generic Windows Management Agent First you need to decide on the location of your project All Rational Projects are stored in specific directory structures and the top level directory for each project has to be created manually before defining the project to Rational When using Rational with the TMTP Generic WIndows Management Agent the project directory has to be available to the Generic Windows Management Agent The base location for all projects are dictated by the Generic Windows Managemen
438. r the managed application object is shown in Figure 5 2 on page 160 Chapter 5 Interfaces to other management tools 159 loi x ay Create WWSApplicationServer Application Server Name Site Analyzer Administration Server Label pplication Server panda Endpoint Name O Has Web Module C No Yes Has EJB Module No Yes Set and Execute Figure 5 2 Create WSApplicationServer 2 By using the discovery task Discover_WebSphere_Resource in the TaskLibrary WebSphere Application Server Utility Tasks both objects will be created automatically for you When starting the task supply the parameters for discovery in the dialog as shown in Figure 5 3 on page 161 160 End to End e business Transaction Management Made Easy 8 Discover_WebSphere_Resources a y o x Configure Task Arguments Configure Discover WebSphere Resources from WebSphere Application Server Utility Tasks Policy Region Name Monitoring for WebSphere Application Server 4 Install path of WebSphere Application Server cWWebSphereiAppServer Endpoints panda Endpoint Object Destination Managed Node Name Set amp Execute Task Description Figure 5 3 Discover WebSphere Resources 3 Run the appropriate command from the command line wWebshpere c Note This method can only be used to create the WebSphere Application Server managed application object For all the specified parameters commands
439. ransaction Creating realms To create a realm click Configuration Work with Realms Create New on the home page of the TMTP Version 5 2 Management Server console The Specify Realm Settings dialog as shown in Figure 8 16 will appear Chapter 8 Measuring e business transaction response times 255 IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer it O x File Edit View Favorites Tools Help EJ Bak gt A Qsearch Favorites Media 3 Ay 48 8 Address sa hetp ftivdces 9082 tmtpULfispiconsole WcFrameManager isp lt mes Tivoli Monitoring for Transaction Performance User Name administrator Cigi Configuration Work with Discovery Policies Work with Listening Policies Work with Playback Policies Work with Schedules Work with Agent Groups Work with Transaction Recoil Work with Realms vReports View Big Board Specify Realm Settings Realm Type Web Server x Realm Name fibmntivd Realm Host Name fibmtivd View General Reports User Name View Component Events administrator gt System Administration gt Downloads Password ee eer OK Alt 0 Cancel Alt c g Work with Realms Create Edit Delete etc iS fax Local intranet As Figure 8 16 Specifying realm settings If the transaction accesses a proxy server in a realm where a proxy server is located choose Proxy If the transaction accesses a realm where a W
440. raphically with a specific iconography Rational Robot can be used to simulate transactions on applications running in generic Windows environment Visual Basic applications Oracle Forms Powerbuilder applications Java applications Java applets or Web sites Some of these applications are supported out of the box others require the installation of specific Application Enablers provided with Rational Robot and still others require the user to load a specific Application Extension It allows for quick visual recording of the application under test and playback ina debugging environment to ensure that the simulation flows correctly Scripts can be played back on a variety of Windows platforms including Windows NT 4 0 Windows XP Windows 2000 Windows 98 and Windows Me 9 1 1 Installing and configuring the Rational Robot Rational Robot is provided by TMTP Version 5 2 as a zip file that containing the Rational Robot CD iso image so that you can burn your own Rational Robot CD using your favorite software The setup procedure does not differ if the image is used from the CD or downloaded from TMTP Rational Robot is installed following the generic setup steps you need to follow on most Windows applications After the installation there are specific steps you must follow to enable and load all the components needed to record and playback a simulation on the application you will use Java HTML and so on 326 End to End e business Trans
441. raphs such as the one shown in Figure B 1 on page 441 End to End e business Transaction Management Made Easy J Tivoli APM Microsoft Internet Explorer Tivoli Endpoint SS C Hostname F se E Average Response Time z Transaction Load_homepage Tivoli APM Dataview ETE 3 405 3 116 2 474 m Average Response Time s 1 339 1 398 RTO ER l 0 938 l Maximum value 3 405 Time 12 22 Minimum value 0 938 Time 11 57 lE Done O E vocal intranet Figure B 1 ETP Average Response Time In order for TMTP ETP to record this data the ARM API calls must be made from Rational Robot scripts The ARM API The ARM API is an Open Group standard for a set of API calls that allow you to measure the performance of any application The most common use of the API is to measure response time but it can also be used to record application availability and account for application usage The ARM API is documented at http www opengroup org management arm htm The ARM Version 2 implementation is a set of C API calls as shown in Figure B 2 on page 442 Appendix B Using Rational Robot in the Tivoli Management Agent environment 441 Application Transaction arm_init arm_getid arm_start a response do user s work time ign Out arm_stop arm_end Figure B 2 ARM API Calls There are six ARM API calls arm_init arm_getid arm_start
442. raphy Standard 10 Quality of Service Relational Database Management System RDBMS Interface Module RACE Integrity Primitives Evaluation Message Digest Remote Terminal Emulation SAX SDK SHA SI SID SLA SLO SMTP SNMP SOAP SQL SSL STI TAPM TBSM TCL TCP IP TDS TEC TEDW TIMS TMA TME TMR TS TMTP UDB UDP End to End e business Transaction Management Made Easy Simple API for XML Software Developer s Kit Secure Hash Algorithm Site Investigator System ID Service Level Agreement Service Level Objective Simple Mail Transfer Protocol Simple Network Management Protocol Simple Object Access Protocol Structured Query Language Secure Socket Layer Synthetic Transaction Investigator Tivoli Application Performance Management Tivoli Business Systems Manager Terminal Control Language Transmission Control Protocol Internet Protocol Tivoli Decision Support Tivoli Enterprise Console Tivoli Enterprise Data Warehouse Tivoli Internet Management Server Tivoli Management Agent Tivoli Management Environment Tivoli Management Region Transaction Simulation IBM Tivoli Monitor for Transaction Performance Universal Database User Datagram Protocol URI URL UUID VuGen VUS Vuser W3C WSC WSI WWW XML Uniform Resource Identifier Uniform Resource Locator Universal Unique Identifier Virtual User Generator Virtual User Script Virtual User World Wide W
443. rce databases are implemented using other RDBMS systems such as Oracle the commands vary Instead of using the db2 command line interface you may use the GUI of the DB2 Client Assistant to catalog the appropriate ODBC data sources This method may also be used for DB2 hosted source databases Defining user authority to the Warehouse sources and targets You should inform the TEDW Control Center server of user access information for every source and target ETL process installed by the IBM Tivoli Monitoring for Transaction Performance ETL The following steps should be followed 1 Start the IBM DB2 Control Center utility by selecting Start Programs gt IBM DB2 Control Center On the IBM DB2 Control Center utility start the IBM DB2 Data Warehouse Center utility by selecting Tools Data Warehouse Center The Data Warehouse Center logon window appears Log in to the IBM DB2 Data Warehouse Center utility using the local DB2 administrator user ID in our case db2admin In the Data Warehouse Center window expand the Warehouse Sources and Warehouse Targets folder As shown in Figure 10 13 on page 395 there are three entries for the IBM Tivoli Monitoring for Transaction Performance ETL programs that need to be configured Warehouse Source BWM_TMTP_DATA_SOURCE e BWM_TWH_CDW_Source e BWH_TWH_MART_Source 394 End to End e business Transaction Management Made Easy Warehouse Target BWM_TWH_CDW_Target e BWM_T
444. rce files into the directories if a product like db2 is already installed a Create installation_root This will contain the Management Server installation binaries If you have the packed downloaded version once you unpack it will create the following two directories e installation_root lib e installation_root keyfiles If you are using CDs and you still would like to create a depot you need to copy the entire content of the CD into the installation_root directory b Create installation_root db2 This will hold the DB2 installation binaries c Create installation_root was5 This is the location where the WebSphere installation binaries will be copied d Create installation_root wasFp1 This is the directory for the WebSphere FixPack 1 Chapter 4 TMTP WTP Version 5 2 installation and deployment 89 90 Important The directory names are case sensitive For detailed descriptions of the files and directories to be copied into the specific product directories please consult the IBM Tivoli Monitoring for Transaction Performance Installation Guide Version 5 2 0 SC32 1385 In our scenario we have created a file system named install and use it to serve as the installation_root This file system can be removed after the installation To provide temporary space for the product installation itself we have also created the install tmp directory We have the output shown in Example 4 2 if we execute an 1s
445. rd 108 License agreement panel naaraana nnana 109 Installation target folder selection 0 c eee eee 110 SSL enablement window 200 cece eee eee 111 WebSphere configuration panel 000 0c eee eee eee 112 Database options panel uuaa uuaa cee eee 113 Database Configuration panel 0 00 cece eee eee 114 Setting summarization window 0000 0c eee eee eee 115 Installation progress WINdOW 0 ee 116 The finished Management Server installation 117 TMTP logon window 00 0 0 eee ee eae 118 Welcome window of the Store and Forward agent installation 119 License agreement window 0 eee 120 Installation location specification 00 e eee eee 121 Configuration of Proxy host and mask window 122 KDB file definition creerse dte adai eee 123 Communication specification s sasaaa eaaa ea 124 User Account specification window s aaaeeeaa aaea 125 Summary before installation 00 0c eee 126 Installation progress 2 eee 127 The WebSphere caching proxy reboot window 4 128 The final window of the installation 0 00000 eee eae 129 Management Agent installation welcome window 130 License agreement window 0 2 00 eee eee 131 End to End e business Transaction Management Made Easy 4 47 4 48 4 49 4 50 4 51 4 52 4 53 4 5
446. re 4 28 Database options panel gt As we already created the dbtmtp db2 instance and the TMTP database on the DB2 level We choose tmtp for the Database Name and the database user will be the DB2 instance user dbtmtp The JDBC path is home dbtmtp sqllib java see Figure 4 29 on page 114 Chapter 4 TMTP WTP Version 5 2 installation and deployment 113 E Install the Management Server E loj x y Database Configuration gt F D Type the required information in the text boxes to specify the ESES So database to be used for creating the management repository PBA 4 Tivoli software H TE y Database Name tmtp Database User ID dbtmtp Database Password irren JDBC Path home dbtmtp sqllib java InstallShield lt Back Next gt Cancel N Figure 4 29 Database Configuration panel Tip The JDBC path is located under instance_home sqllib java So for example if you use the default instance of the DB2 which is db2inst1 the JDBC path will be home db2inst1 sqllib java gt After the DB2 configuration the setup program reaches the final summarization window Figure 4 30 on page 115 We press Next and the installation of the Management Server starts Figure 4 31 on page 116 114 End to End e business Transaction Management Made Easy EJ Install the Management Server Figure 4 30 Setting summarization window Chapter 4 TMTP WTP Version 5 2 installa
447. re most changes have been introduced with Version 5 2 The basic architecture is shown in Figure 3 1 and elaborated on in further sections Web Interface Management Agent Ea RDBMS Management Agent Management Server Store and Forward WebSphere Server l Management Agent Management Agent Management Agent firewall Figure 3 1 TMTP Version 5 2 architecture 56 End to End e business Transaction Management Made Easy This version of the product introduces a comprehensive transaction decomposition environment that allows users to visualize the path of problem transactions isolate problems to their source launch the IBM Tivoli Monitoring Web Health Console to repair the problem and restore good response time WTP provides the following broad areas of functionality gt Transaction definition The definition of a transaction is governed by the point at which it first comes in contact with the instrumentation available within this product This can be considered the Edge definition where each transaction upon encountering the edge of the instrumentation available will be defined through policies that define each transactions uniqueness specific to the Edge it encountered gt Distributed transaction monitoring Once a transaction has been defined at its edge there is a need for customers to define the policy that will be used in monitoring this transaction This policy shoul
448. rectory in which to create it and whether or not the project is UCM enabled Project name testscripts Project location Aflotsam RationalT est Browse Use ClearCase and Unified Change Mar coe ie Figure B 5 Rational Robot Project 4 Click Next If you do create a password for the Rational project supply the password on the Security page Figure B 6 on page 446 If you do not create a password then leave the fields blank on this page Appendix B Using Rational Robot in the Tivoli Management Agent environment 445 New Project Security Each Rational Project may be associated with a password This password is required to connect to configure or delete the project Password Confirm lt Back Cancel Help Figure B 6 Configuring project password 5 Click Next on the Summary page and select Configure Project Now Figure B 7 on page 447 The Configure Project dialog box appears Figure B 8 on page 448 446 End to End e business Transaction Management Made Easy ro summary new Rational Project will be created If you want to review or change any settings click Back If you are satisfied with the settings click Finish Current Settings new project with a name of testscripts will be created in the directory C RationalT est The project will not be UCM enabled The project will not be password protected lt Back Cancel Help
449. reporting 389 If you use the Tivoli product CDs the paths to the installation files for the ETP and TMTP installation files are TMTP lt CDROM drive gt tedw_apps_ etl Leave the Now option checked prevents typing errors to verify that the source directory is immediately accessible and that it contains the correct files Click Next 8 Before starting the installation do not select to install additional modules when prompted Figure 10 9 Press Next amp Tivoli Enterprise Data Warehouse Installation AME Do you want to install additional application packages E Yes install additional packages fl 10 9 8 InstallShield Back Cancel Figure 10 9 TEDW installation Additional modules 9 The overview of selected features dialogue window appears as shown in Figure 10 10 Click Install to start the installation Tivoli Enterprise Data Warehouse Installation Tivoli Enterprise Data Warehouse will be installed in the following location CATWH with the following features Application ETL and report packages 8 6MB for a total size 8 6MB InstallShield Back Install Cancel Figure 10 10 TMTP ETL and ETL2 program installation 390 End to End e business Transaction Management Made Easy 10 During the installation the panel shown in Figure 10 11 will be displayed Wait for successful completion Tivoli Enterprise Data Warehouse Installation an ws1ox Installing
450. rformance Microsoft Internet Explorer File Edit View Favorites Tools Help Back gt a Qsearch Favorites media a 4a8 Address a http tivdce4 9082 tmtpUl isp consoleWcFrameManager jsp z Po Links gt Tivoli Monitoring for Transaction Performance User Name administrator E frade j2ee lis amp 9 J2EE 2003 10 01 19 02 00 0 232 0 033 0 033 0 0 E lirade qos is D ibmti aos 2003 10 01 20 06 15 0 117 0 273 0 064 1 41 W petstore aos is E A tivlab01 aos 2003 10 01 22 22 39 0 391 0 312 0 198 0 3E E frade 2 stockcheck tiviabo1 E Gil tivabo1 STI 2003 10 01 21 05 50 6 983 6 452 6 891 7 22 ME petstore 2 order tiviabor E ml tivabot STI 2003 10 01 21 56 14 10 78 10 648 971 711 fase 1 i Fa Z3 View Component Events fs fez Local intranet Figure 8 46 Event Graph Topology view for Trade application The Trade application is running on a WebSphere Application Server Version 5 0 1 and we have configured a synthetic trade transaction with STI data to correlate J2EE components and Quality of Service so we can figure out what is happening at the application server and database From the Big Board shown in Figure 8 46 we can see because of our use of consistent naming standards that the following active policies are related to the Trade application trade_j2ee_lis Listening policy
451. rformance characteristics is available to support the service delivery It also delivers capacity usage performance and workload management statistics as well as trend analysis to Service Level Management Availability Management Availability Management means planning and ensuring the overall availability of the services and providing management information in the form of availability statistics including security violations to Service Level Management Even though not explicitly mentioned in the ITIL definition for this discussion content management is included in this discipline This discipline may also include negotiating underpinning contracts with external suppliers and the definition of maintenance windows and recovery times The disciplines in the Service Support group are mainly reactive and are concerned with implementing the plans and providing management information regarding the levels of service achieved Service Support The reactive disciplines that are considered part of the Service Support group are shown in the following sections Configuration Management Configuration Management is responsible for registering all components in the IT service including customers contracts SLAs hardware and software components and maintaining a repository of configured attributes and relationships between the components 18 End to End e business Transaction Management Made Easy Help Desk The Help Desk acts as the main
452. rify the success of the deployment refresh the Work with Agents dialog and verify that the status for the J2EE Component on the Management Agent in question shows Running as shown in Figure 8 35 Z IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer A ioj i m Tivoli Monitoring for Transaction Performance Work with Agents Work with Age Q Please make aselection 0 Alt Configure Syst Component Mc Name STI QoS J2EE Generic Windows _ Store and Forward Status Platform Upload Start Time cemo Io ibmtiv3 Running Online w32 ix86 1 Hour Ee 00 View System E I tivdce4 itsc austin ibm com Online w32 ix6 1 Hour 03 00 View Log Files m riviabot Online w32 ix86 1 Hour 03 00 View Managen gt Downloads Page 1 Show All Agents C Show Online Agents Show Offline Agents E N y E Work with Email and Script Actions BE Local intranet Figure 8 35 J2EE deployment and work with agents 8 6 2 J2EE component configuration Once the J2EE component has been deployed discovery and listening policies must be created and activated as is the case for the other monitoring components STI and QoS Creating discovery policies for J2EE The J2EE discovery policies return URIs from Management Agents on which a J2EE listener is deployed You might need to create more than one discovery policy to get a complete picture of an environment that inc
453. ring for Transaction Performance User Name administrator Configuration All Times are in Seconds Work with Discovers i Work with Listening ae a 8 a Work with Playback Work with Schedule Work with Agent Gr Work with Transacti Work with Realms 5 z Reports Shopping ClientControllerEJB_Snqa4g_ELOImp fa g SSY Sony View Big Board getS hopping ClientFacade View General Repor v View Component Ey 2 vSystem Administra getS hopping ClientFacade getS hopping ClientFacade ps Work with Agents 0 008 0 006 Events View Configure System E Component Manage Sanaa Configure User Sett Web Health nsole Work with Event Re View System Event Thresholds View Miaow Lac Filoc ia Minimum Maximum View sla View Component Events Java Applet Window Figure 8 70 Topology view event violation by getShoppingClientFacade ing for Transa Performance Microsoft Internet Explorer ioj xj File Edit View Favorites Tools Help Back gt A Qsearch Favorites media B S Si a Address i http tivdce4 9082 tmtpUI jsp console WcFrameManager jsp zl Eao Tivoli Monitoring for Transaction Performance User Name administrator cy petstor_j2ee anagement Agent tivlab01 Configuration 7 x 3 5 ransachon com sunj2ee blueprints petstore controller ej
454. rm file Figure 4 21 on page 106 Chapter 4 TMTP WTP Version 5 2 installation and deployment 105 E3 Enter a Label Exi Enter a label for the certificate ai prodms ok Cane Figure 4 21 Label for the certificate The imported certificate is now on the Signer Certificates list Figure 4 22 E3 IBM Key Management install keyfiles prodagent jks Key Database File Create View Help DOSEER m Key database information JH DB Type KS database file File Name install keyfiles prodagentjks E Token Label Kg es Se Key database content Signer Certificates v Add prodms verisign class 1 public primary at ath d 2 Say DT NIN verisign class 2 public primary certificatior authori View Edit rsa secure server certification authority SSS verisign class 2 public primary certification authori Ene verisign class 3 public primary certification authori verisign test ca root certificate verisign class 1 ca individual subscriber persona verisign class 3 public primary certification authori thawte premium server ca verisign class 1 public primary certification authori thawte personal basic ca thawte personal premium ca The requested action has successfully completed Figure 4 22 The imported self signed certificate 4 We follow these steps to extract and add all self signed certificates into the r
455. rminal Server client nanana aaa 362 Terminal Client connection dialog s sasaaa eaea 363 Start Browser Dialog 0 000 c eee 364 Deploy Generic Windows Component 0 0 0005 366 Deploy Components and or Monitoring Component 367 Work with Transaction Recordings 0 ce eee eee 368 Create Generic Windows Transaction 20 000 000 369 Work with Playback Policies 0 00 0 e eee eee eee 370 Configure Generic Windows Playback 0 20 0005 370 Configure Generic Windows Thresholds 000000 371 Choosing aschedule 0000 cece eee 372 Specify Agent Group 6 6 0 cena 373 Assign your playback policy a name 2 0000 eee 374 A typical TEDW environment 0 02 00 eee eee eee 378 TMTP Version 5 2 warehouse data model 0 05 381 ITMTP Enterprise Transaction Performance data flow 382 Tivoli Enterprise Data Warehouse installation scenario 383 TEDW installation meta t enaA EREET EEEE EAE ee 388 TEDW installation type 2 eee 388 TEDW installation DB2 configuration 00 eee 389 Path to the installation media for the ITM Generic ETL1 program 389 TEDW installation Additional modules 0 005 390 End to End e business Transaction Management Made Easy 10 10 TMTP ETL1 and ETL2 program installation 390 10 11 TE
456. rn that fits that vision Then by drilling down using the patterns process the architect can further define the additional functional pieces that the application will need to succeed Finally the architect can build the application using coding techniques outlined in the associated guidelines Further details on e business patterns may be found in Appendix A Patterns for e business on page 429 End to End e business Transaction Management Made Easy For a full understanding of the patterns please review the book Patterns for e business A Strategy for Reuse by Adams et al 1 3 3 Basic products used to facilitate e business applications So far we may conclude that building an e business solution is like building a vehicle in the sense that gt We want to provide the user with a standard easy to use interface that fulfills the needs of the user and has a common look and feel to it gt We want to use as many standard components as possible to keep costs down and be able to interchange them seamlessly gt We want it to be reliable and available at all times with a minimum of maintenance gt We want to build in unique features differentiators that make the user choose our product over those of the competitors The main difference between the vehicle and the e business solution is that we own and control the solution but the buyer owns and manages the vehicle The vehicle owner decides when to have the oil changed and
457. rname ISC Password WHC Server fhanO1twhe LaunchITMAN R Refresh Rate 5 Minutes M Enable Refresh Rate OK Alt 0 Configure Time Zones refresh rates etc D i temet Figure 5 7 Configure User Setting for ITM Web Health Console 174 End to End e business Transaction Management Made Easy Configure the refresh rate for the Web Health Console as follows 1 Select the Enable Refresh Rate option to override the default refresh rates for the Web Health Console display Type an integer in the Refresh Rate field to specify the number of minutes that pass between each refresh Click OK to save the user settings and enable connection to the Web Health Console 5 2 2 Setting SNMP Set SNMP by following these steps 1 Open the lt MS_Install_Dir gt config directory where lt MS_Install_Dir gt is the directory containing the Management Server installation files 2 Open the tmtp properties property file 3 Modify the EventService SNMPServerLocation key with the fully qualified server name such as EventService SNMPServerLocation bjones austin ibm com Optional Modify the EventService SNMPPort key to specify a different port number than the default value of 162 Optional Modify the SMTPProxyPort key to specify a fully qualified proxy server host name Optional Modify the EventService SNMPV1ApiLogEnabled key to enable debug tracing in the classes found in the snmp jar file Ad
458. rocess please refer to the BM Tivoli Monitoring for Transaction Performance User s Guide Version 5 2 0 SC32 1386 1 From the home page of the TMTP Version 5 2 console select Configuration Work with Playback Polices From the Work with Playback Policies dialog that is displayed shown in Figure 8 13 set the playback type to STI and press the Create New button Next the Configure STI Playback dialog will appear An example is provided in Figure 8 14 on page 252 Tivoli Monitoring for Transaction Performance User Name administrator My Work Configuration Work with Discovery Policies Work with Playback Policies Work with Listening Policies Work with Playback Policies Work with Schedules X Create New AHN Work with Agent Groups Work with Transaction Recordings Work with Realms Reports b System Administration m itestNotepad GenWin TestNotepad xp_genwin_grp petstore_sti_s b Downloads r trade_2_stock check STI trade_2_stock check lsti grp trade_sti_sch Page 1 Show Enabled Policies C Show Disabled Policies Fi Figure 8 13 Create new Playback Policy Chapter 8 Measuring e business transaction response times 251 of Inkarnat Funinrar et Explorer File Edt view Favorites Tools Help Tivoli Monitoring for Transaction Performance User Name administrator J i innsin i Configure STI Playback OO STI Playback Recorded Transaction B
459. roduces a list of all URI requests with average response times that have occurred during the discovery period You can now consult the list of discovered URIs to identify transactions to monitor in detail using specific listening policies which monitor incoming Web requests and collect detailed performance data in accordance with the specifications defined in the listening policy Defining the listening policy is the responsibility of the TMTP user or administrator responsible for a particular application area 228 End to End e business Transaction Management Made Easy 8 1 2 Choosing the right measurement component s IBM Tivoli Monitoring for Transaction Performance Version 5 2 provides four different measuring tools each with different capabilities and providing data that measures specific properties of the e business transaction The four are Synthetic Transaction Investigator Provides record and play back capabilities for browser based transactions Works in conjunction with the J2EE monitoring component to provide detailed analysis for reference pre recorded business transactions STI is primarily used to verify availability and performance to ensure compliance with Service Level Objectives Quality of Service Is primarily used to monitor real time end user transactions and provides user specific data such as User Experience Time and Round Trip Time J2EE Monitors the internals of the J2EE infrastructure server such as
460. rt i H E GroupPolicy Clie poi inetsrv 4 Be gt f gt Type Application Size 79 6 KB 79 6 KB My Computer A Figure B 21 Setup for Terminal Server client 3 Once you have installed the client you may start a client session from the appropriate menu option You will be presented with the dialog shown in Figure B 22 on page 471 From this dialog you should select the local machine as the server you wish to connect to End to End e business Transaction Management Made Easy fal Terminal Services Client EA A S x Server dahouse z Screen area oUUxbUU Available servers M Expand by default 3 WORKGROUP J Enable data compression I Cache bitmaps to disk Cancel Help About Figure B 22 Terminal Client Connection Dialog Note It is useful to set the resolution to one lower than that used by the workstation you are connecting from This allows the full Terminal Client session to be seen from the workstation screen 4 Once you have connected you will be presented with a standard Windows 2000 logon screen for the local machine within your client session Log on as normal 5 Now you can run your Rational Robot scripts using whichever method you would normally do this with the exception of via GenWin You may now lock the host screen and the Rational Robot will continue to run in the client session Appendix B Using Rational Robot in the Tivoli Management Agent environment 471 472
461. rtant step in finding an adaptable management model End to End e business Transaction Management Made Easy The Java Management Extensions JMX technology represents a universal open technology for management and monitoring that can be deployed wherever management and monitoring are needed JMX is designed to be suitable for adapting legacy systems implementing new management and monitoring solutions and plugging into future monitoring systems JMX allows centralized management of managed beans or MBeans which act as wrappers for applications components or resources in a distributed network This functionality is provided by a MBean server which serves as a registry for all MBeans exposing interfaces for manipulating them In addition JMX contains the m let service which allows dynamic loading of MBeans over the network In the JMX architectural model the MBean server becomes the spine of the server where all server components plug in and discover other MBeans via the MBean server notification mechanism The MBean server itself is extremely lightweight Thus even some of the most fundamental pieces of the server infrastructure are modeled as MBeans and plugged into the MBean server core for example protocol adapters Implemented as MBeans they are capable of receiving requests across the network from clients operating in different network protocols like SNMP and WBEM enabling JMX based servers to be managed with tools written in
462. ructure system management is directly proportional to the size of the infrastructure being managed In its simplest form an e business infrastructure is comprised of a single Web server and its resources but it can grow to hundreds or even thousands of Web and application servers throughout the enterprise To add to the complexity the e business infrastructure may span many platforms with different network protocols hardware operating systems and applications Each platform possesses its unique and specific systems management needs and requirements not to mention a varying level of support for the administrative tools and interfaces Every component in the e business infrastructure is a potential show stopper bottleneck or even single point of failure Each and every one provides specialized services needed to facilitate the e business application system The term application systems is used deliberately to enforce the point that no single component by itself provides a total solution the application is pieced together by a combination of standard off the shelf components and home grown components The standard components provide general services such as session control authentication and access control messaging and database access and the home grown components add the application logic needed to glue all the different bits and pieces together to perform the specific functions for that application system On an enterprise level chances
463. running the playback will be interrupted gt If delay times are not used with the recording script the GenWin playback will fail to search the dynamic strings gt When a transaction is recorded by GenWin the user IDs and passwords for e business application site login are placed in the script file as a clear text To avoid exposing passwords in the script it may be stored encrypted in an file external to the script and passed into the script at execution time Please refer to Obfuscating embedded passwords in Rational Scripts on page 464 for a description on how to use this function gt For GenWin recording and playback you only need a single piece of Rational Robot software in contrast to STI Both recording and playback should not be run from the same Rational Robot because a Playback policy might trigger playback of a prerecorded Generic Windows synthetic transaction while you are recording another transaction 8 1 3 Measurement component selection summary Table 8 1 summarizes the capabilities and suggested use of the four different measurement technologies available in IBM Tivoli Monitoring for Transaction Performance Version 5 2 Table 8 1 Choosing monitoring components Component Operation Advantage Correlation with Description other components Transaction Simple to use Can be combined Simulated simulation with with J2EE andQoS end user subtransaction with correlation experience correlation GenWin Tr
464. rver Distributed Sys Mgmt Agents Tivoli Data Warehouse Server Tivoli Gateway Tivoli Endpoint Back End ITM Monitoring Engine Firewall Distributed Sys Mgmt Agents Tivoli Gateway piema Internal Tivoli Endpoint Customer Customer ITM Monitoring Engi Segment Segment lonitoring Engine Figure 1 9 Typical Tivoli managed e business application infrastructure Implementing the management infrastructure in this fashion there is minimal interference between the application and the management systems and the access to and from the various network segments is manageable as the communication flows between a limited number of nodes using well known communication ports IBM Tivoli management products have been developed with the total environment in mind The IBM Tivoli Monitoring product provides the basis for proactive monitoring analysis and automated problem resolution As we will see IBM Tivoli Monitoring for Transaction Performance provides an enterprise management solution for both the Web and enterprise transaction environments This product provide solutions that are integrated with other Tivoli management products and contribute a key piece to the goal of a consistent end to end management solution for the enterprise By using product offerings such as IBM Tivoli Monitoring for Transaction Performance in conjunction with the underlying Tivoli technologies a comprehensive
465. rward Agent he information that you must type depends on how the management agent connects to the management server If communication flows directly to the management server you must pe information for the management server If communication flows across a firewall to the management server ou must type information for a management agent that is running the Store and Forward Service Specify a User account that exists on the WebSphere Application Server of the management server This user account must have the agent role Host Name fully qualified jibmtiv4 itsc austin ipbm com User Name root User Password k Enable SSL M Yes Use default port number C No Port Number 9446 No Proxy Proxy Protocol Socks HTTPS Proxy Host Port Number SSL Key Store File eakeyflesiprodagentiks SSL Key Store Password ce X Back Next gt Cancel Figure 4 48 Management Agent connection window InstallShield 7 In Figure 4 49 on page 134 we specify a local administrative user account that will be used by the Management Agent service We specify the local Administrator account which already exists Chapter 4 TMTP WTP Version 5 2 installation and deployment 133 Tivol Install Management Agent Specify a User Account Specify a user account for running the management agent service This user account must be a member of the Administrators group on Windows You have two options Specify an
466. ry bin generic_unix TME The definition files for the IBM Tivoli Monitoring for WebSphere Application Server events are documented in the subdirectory WSAPPSVR in the following BAROC files itmwas_dm_events baroc Definitions for the events originated from all the Resource Models itmwas_events baroc Definitions of events forwarded to the TEC directly from the WebSphere Application Server and the Tivoli Enterprise Console adapter For the IBM Tivoli Monitoring for WebSphere Application Server events three different rulesets are supplied in the subdirectory WSAPPSVR itmwas_events rls Handles events that originate directly from the WebSphere Application Server Tivoli Enterprise Console adapter itmwas_monitors rls Handles events that originate from Resource Models itmwas_forward_tbsm rls Handles events that are forwarded to Tivoli Business System Manager Tivoli provides for all the IBM Tivoli Monitoring for Web Infrastructure solutions definition files and ruleset files They are located in the appropriate subdirectories For documentation regarding these files please refer to the appropriate User s Guides for the IBM Tivoli Monitoring for Web Infrastructure modules For further information on how to implement the classes and rule files refer to the IBM Tivoli Enterprise Console Rule Builder s Guide Version 3 8 GC32 0669 Chapter 5 Interfaces to other management tools 169 5 1 6 Surveillance Web Health Console You can us
467. s Tools Help Tivoli Monitoring for Transaction Performance User Name Administrator Configuration Work with Discovery Policie Work with Listening Policies Work with Playback Policies Work with Schedules Work with Agent Groups Work with Transaction Reco Work with Realms Choose Agent Group b Reports b System Administration gt Downloads Configure Generic Windows Playback Recorded Transaction Z Choose edule Assign Name Playback Settings Number of Retries Retry Lag Time B 3 Seconds lt Back Alt b Next Alt n gt Finish Alt f Cancel Alt c Figure 9 42 Configure Generic Windows Playback End to End e business Transaction Management Made Easy 3 Configure the Generic Windows playback options From here you can select the transaction that you have previously registered You can also configure the number or retries and amount of time between each retry if you specify three retries the transaction will be attempted four times Once you are happy with the settings press the Next button 4 The next part of the workflow allows you to configure the Generic Windows thresholds see Figure 9 43 This allows you to set both performance and availability thresholds as well as associating Event Responses with those thresholds for example running a script generating an Event to TEC generating an SNMP Trap or sending an e mail By default Events
468. s E Local intranet Ui Figure 8 44 Configure J2EE parameter and threshold for performance 7 To set thresholds for event generation and problem identification for J2EE applications do the following a Select the type of threshold you want to define You may select between Performance and Transaction Status b Click Create to specify the transaction threshold details These will be covered in detail in the following sections You are not required to define J2EE thresholds in the current procedure If you do the thresholds apply to the transaction that is investigated not to the J2EE subtransactions that are initiated by the transaction After the policy runs you can view a topology report which graphically represents subtransaction performance and set thresholds on individual End to End e business Transaction Management Made Easy subtransactions there You can then edit the subtransaction thresholds in the current procedure Define the your J2EE trace configuration The J2EE monitoring component collects information for the servlet subtransaction type as follows At trace level 1 performance data is collected but no context information At trace level 2 performance data is collected along with some context information such as the protocol that the servlet is using At trace level 3 performance data and a greater amount of context information is collected such as the ServletPath associated with the subtransaction
469. s 6 Edit the Class Path and Arguments fields to restore them to the original value before deploying J2EE Instrumentation If these two fields were blank before installing J2EE Instrumentation then they should be reverted to being blank If these two fields had configuration not related to J2EE Instrumentation only remove the values that were added by J2EE Instrumentation The values added by the J2EE Instrumentation install will be similar to those values shown in Example 6 5 Example 6 5 Weblogic Class Path and Arguments fields Class Path C beaHome701 weblogic700 server 1ib ext probes jar C beaHome701 weblogic700 s erver lib ext ejflt jar C beaHome701 weblogic700 server lib ext jflt jar C be aHome701 weblogic700 server 1lib ext jffdc jar C beaHome701 weblogic700 server 202 End to End e business Transaction Management Made Easy lib ext jlog jar C beaHome701 weblogic700 server lib ext copyright jar C beaH ome701 weblogic700 server 1ib ext core_util jar C beaHome701 weblogic700 serve r lib ext armjni jar C beaHome701 weblogic700 server 1ib ext eppam jar Arguments Xbootclasspath a C ma 2003 07 03 0015 app instrument lib jiti jar C ma 2003 07 03 0015 app instrument 1ib bootic jar C ma 2003 07 03 0015 app instrument ic config C ma 2003 07 03 0015 app instrument appServers 178 conf ig Xrunjitipi C ma 2003 07 03 0015 app instrument lib jiti properties Dcom ibm tivoli jiti config C ma 2003 07 03 0015 app instru
470. s Application Servers E Applications Total 4 Enterprise Applications Fiter Install New Application Preferences Resodrcas Stop Install Uninstall Update Export Export DDL Security a E Environment I Name Status V C Update Web Server Plugin 7 RefautApplication gt virtual Hosts IT aaininconsole gt Manage WebSphere Variable Shared Libraries m petstore gt Naming trades gt System Administration R Console Users Console Groups we WebSphere Status i Afro Peis October 3 2003 11 54 10 AM CDT Troubleshooting WebSphere Runtime Messages Logs and Trace p Clear All Total All Messages 380 jo O nev 0 total A Loew 7 total fy 373 new 373 total Configuration Problems E 4 r Preferences v a tgp tnternet 7 Figure 8 2 WAS 5 0 Admin console Install of Trade3 application In addition to a login page that is used to access the Trade system a main home page that details the users account information and current market summary information is provided From the user s home page the following asynchronous transactions are processed gt Purchase order is submitted gt New Open order is created in DB gt The new order is queued for processing gt The open order is confirmed to the user gt The message server delivers the new order message to the TradeBroker gt The TradeBroker processes the order asynchronously completing the purchase for the user gt The user receiv
471. s and thus will not react immediately if for example a monitored Web site becomes 60 End to End e business Transaction Management Made Easy unavailable The minimum time for reaction is related to the aggregation period and the thresholds specified 3 2 Physical infrastructure components As mentioned previously all of the components of IBM Tivoli Monitoring for Transaction Performance share a common infrastructure based on the IBM WebSphere Application Server Version 5 0 1 This provides the TMTP product with a lot of flexibility The TMTP Management Server is a J2EE application deployed onto the WebSphere Application Server platform The installation of WebSphere and the deployment of the Management Server EAR are transparent to the installer The Management Server provides the services and user interface needed for centralized management Management agents are installed on computers across the environment Management agents run discovery operations and collect performance data for monitored transactions The Management Server and Management Agents may be deployed on the AIX Solaris Windows and xLinux platforms Another key feature of the IBM Tivoli Monitoring for Transaction Performance infrastructure is the application response measurement ARM engine The ARM engine provides a set of interfaces that facilitate robust performance data collection The following sections describe the Management Server Management Agents and ARM in
472. s and IT gap by defining architectural patterns at various levels from Business patterns to Application patterns to Runtime patterns enabling easy navigation from one level to the next Each of the patterns Business Integration Application and Runtime help companies understand the true scope of their development project and provide the necessary tools to facilitate the application development process thereby allowing companies to shorten time to market reduce risk and most important realize a more significant return on investment The core types of Patterns for e business are Business Patterns Integration Patterns Composite Patterns Application Patterns Runtime Patterns and matching product mappings vvvvy When a company takes advantage of these documented assets they are able to reduce the time and risk involved in completing a project For example a line of business LOB executive who understands the business aspects and requirements of a solution can use Business patterns to develop a high level structure for a solution Business patterns represent common business problems LOB executives can match their requirements IT and business 430 End to End e business Transaction Management Made Easy drivers to Business patterns that have already been documented The patterns provide tangible solutions to the most frequently encountered business challenges by identifying common interactions among users business and data
473. s and cannot be used to simulate activity on a Generic Windows applications VU only supports specialized network protocols not generic API access on the network layer and VU scripts can only be played back using Rational Test Manager The playback of VU scripts is not supported by TMTP Version 5 2 so VU will be ignored in this book 9 1 4 Steps to record a GUI simulation with Rational Robot There are differences in how a simulation recording is set up and prepared on different applications For example to record an HTTP simulation in a browser you need to load the Extension for the browser you will be using while with Java you need to load the Extension and configure the Java Enabler on the JVM you will be using But whatever application you are using there are common points that will be followed 1 Record the script on the GUI 2 Add features to the script during recording ARM API calls for TMTP Verification Points Timers comments and so on 3 Compile the script 4 Play the script back for debugging 5 Save and package the script for TMTP Version 5 2 Record the script on the GUI To record a GUI script click the Record GUI script on the toolbar GUI Chapter 9 Rational Robot and GenWin 345 Type an application name in the Record GUI Dialog Figure 9 25 Record GUI Y xj Name HTTP pplicatior leuil Java Appplication GUI Cancel Options Properties Help Figure 9 25 Record GUI
474. s ba y 4 gt 4 Work with Discovery Policies Choose Create Edit etc i tocal intranet M Figure 8 36 J2EE Work with Discovery Policies This will bring you to the Configure J2EE Listener dialog shown in Figure 8 37 on page 284 where you can specify filters and sampling properties for the J2EE discovery policy Chapter 8 Measuring e business transaction response times 283 ai IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer Tivoli Monitoring for Transaction Performance Configuration Configure J2EE Listener Work with Discovery Polic Work with Listening Polic feg URI Filter Work with Playback Polic bo http trade Work with Schedules Usar Name Work with Agent Groups FAMER Enae E Work with Transaction Re Work with Realms Ea Advanced Settings apana Data Filter View Big Board View General Reports Sample Rate View Component Events 100 vSystem Administration parem Work with Agents C Number of Samples Configure System Event C 5 Component Management Configure User Settings Work with Event Respons View System Events View Log Files View Management Server b Downloads I oa CARERS lt Back Alt b Next Alt n gt Finish Alt f Cancel Alt c ire DL Neer use I cca ae G Work with Discovery Policies Choose Create Edit etc m fox Local intranet h Figure 8 37 Configure J2EE disc
475. s between the disciplines are shown in Figure 1 5 on page 20 Chapter 1 Transaction management imperatives 19 Deliverables Quality Services Requirements Quality Services Requirements Budget Performance Service Level Management Availability Disaster Problems Problem Reports Questions Inquiries Deliverables Costs Performance Requirements shes Availability Availability Recovery A Support Planning Contingency Management Help Desk Cost Management Capaci Management Change Management e Problem Management Pal Availability Management Deliverables Configuration Data Software Installations Requests IT Infrastructure Improvements Configurations Capacity Infrastructure Configuration Management Equipment Components mee Software Control and Distribution Figure 1 5 Key relationships between Service Management disciplines For the remainder of this discussion we will limit our discussion to capacity and availability management of the e business solutions Contrary to the other disciplines that are considered common for all types of services provided by the IT organization the e business solutions provide special challenges to management due
476. s events Pet Store J2EE performance scenario We want to identify the performance characteristics of different J2EE application components such as Pet Store JSP Servlets EJB and JDBC during business hours especially during peak hours In addition we want to identify the application s bottleneck and the component responsible in order to figure out if the application is under or over provisioned Furthermore we want to find the real Back End Service Time for all back end components and the Round Trip Time for an end user A J2EE listening policy is created and named petstore_j2ee_lis to capture specific Pet Store business transactions A QoS listening policy is created and named petstore_qos_lis to capture the real response time with the J2EE application components response for specific transactions against the Pet Store site Please refer to 7 1 Reporting overview on page 212 for details on how to use the online reports in IBM Tivoli Monitoring for Transaction Performance Version 5 2 320 End to End e business Transaction Management Made Easy From the J2EE topology view shown in Figure 8 69 we see that SessionEJB indicates an alert If we drill down in the SessionEJB we realize that the getShoppingClienFacade method is responsible for this violation as shown in see Figure 8 70 on page 322 4 IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer iu at O x File Edit View Fav
477. s executeQuery Average End user Experience by date The Average End user Experience by date report shown in Figure 10 37 on page 425 reveals that there might be networking issues that are related to the end users running trade transactions on 10 6 This report does not detail the difference in the locations of the active user population between the two days but it is obvious that troubleshooting and or tuning is needed 424 End to End e business Transaction Management Made Easy QoS Response Time vs Date For http Wibmtiv9 itsc austin ibrm com 82 vtradeVapp _ 111 AVG_VAL Avg of MSMT e MSMT_STRT_DT S Figure 10 37 Response time for trade by trade_qos_lis listening policy Chapter 10 Historical reporting 425 426 End to End e business Transaction Management Made Easy Part 4 Appendixes 428 End to End e business Transaction Management Made Easy Patterns for e business IBM Patterns for e business is a set of proven architectures that have been compiled from more than 20 000 successful Internet based engagements This repository of assets can be used by companies to facilitate the development of Web based applications They help an organization understand and analyze complex business problems and break them down into smaller more manageable functions that can then be implemented using low level design patterns Copyright IBM Corp 2003 All rights reserved 429 Intr
478. s initiating these types of transactions are managed by our Tivoli Management Environment Application transaction Subtransactions that are initiated by the application provisioning Web transactions to the end users Application transactions are typically but not always also enterprise transactions but also may initiate from third party application servers A typical application transaction is a database lookup performed from a Web application server in response to a Web transaction initiated by an end user From a management point of view these transaction types should be treated similarly Responsiveness from the Web application servers to any requester is equally important and it should not make a difference if the transaction has been initiated from a Web user an internal user or a third party application server However business priorities may influence the level of service or importance given to individual requestors However it is important to note that monitoring transaction performance does not in any way obviate the need to perform the more traditional systems management disciplines such as capacity availability and performance management Since the Web applications are comprised of several resources each hosted by a server these individual server resources must be managed to ensure that they provide the services required by the applications With the myriad servers and exponentially more individual resources and comp
479. s more useful For example a transaction might exceed and fall below a threshold hundreds of times during a single monitoring period Without intelligent event generation each of these occurrences generates a separate event with associated notification End to End e business Transaction Management Made Easy 8 4 STl recording and playback STI measures how users might experience a Web site in the course of performing a specific transaction such as searching for information enrolling ina class or viewing an account To record a transaction you use STI Recorder which records the sequence of steps you take to accomplish the task For example viewing account information might involve logging on viewing the main menu viewing an account summary and logging off When a recorded transaction accesses one or more password protected Web pages you create a specification for the realm to which the pages belong After you record a transaction you can create an STI playback policy which instructs the STI component to play back the recorded transaction and collect a range of performance metrics To set up configure deploy and prepare for playing back the first STI recording the following steps have to be completed STI component deployment STI Recorder installation Transaction recording and registration Playback schedule definition Ore SB Oe No a Playback policy creation Please note that the first two steps only have to be executed o
480. s of responsiveness performance and availability The major enhancement in Version 5 2 is the addition of state of the art industry strength monitoring functions for J2EE applications hosted by WebSphere Application Server or BEA Weblogic In addition the architecture of Web Transaction Monitoring WTP has been redesigned to provide for even easier deployment increased scalability and better performance Also the reporting functions has been enhanced by the addition of ETL2s for the Tivoli Enterprise Date Warehouse This new version of IBM Tivoli Monitoring for Transaction Performance provides all the capabilities of previous versions of IBM Tivoli Monitoring for Transaction Performance including the Enterprise Transaction Performance ETP functions used to add transaction performance monitoring capabilities to the Tivoli Management Environment with the exception of reporting through Tivoli Decision Support The reporting functions have been migrated to the Tivoli Enterprise Date Warehouse environment SG24 6080 00 ISBN 073849323 INTERNATIONAL TECHNICAL SUPPORT ORGANIZATION BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE IBM Redbooks are developed by the IBM International Technical Support Organization Experts from IBM Customers and Partners from around the world create timely technical information based on realistic scenarios Specific recommendations are provided to help you implement IT solut
481. s possible to name a group with the appropriate virtual host string www telia com 80 for example Modification of Endpoint Groups for QoS Virtual Hosts An extra flag will be added to the Object Model definition of an Endpoint Group to allow you to determine if each specific Endpoint Group is a virtual host It will be a Boolean value for use by UI and the object model itself Chapter 8 Measuring e business transaction response times 265 266 Implications for UI The UI will need to only allow the scheduling of QoS policies against an Endpoint Group that is also a virtual host The UI as well will need to not allow any editing modification of Endpoint Groups that are virtual hosts this will be handled by the QoS behavior on the Management Agents Update Mechanism Virtual hosts will be detected by the QoS component on each Management Agent When the main QoS service is started on the Management Agent a script will run which will detect the virtual hosts installed on the particular Management Agent Messages will then be sent to the Management Server a Web service will be created on the Management Server as an interface to the session beans that will create edit and otherwise manage the endpoint groups that are virtual hosts Please consult the manual BM Tivoli Monitoring for Transaction Performance User s Guide Version 5 2 0 SC32 1386 for more details Create discovery policies for QoS Before creating a discovery policy for Qu
482. s to match your installation environment media location and user and password settings Run the sh tedw_wpack_patchadm sh command a second time to install the patch scripts and programs 6 Open the DB2 Data Warehouse Center 7 Locate the BWM_c05_Upgrade_Processes group under Subject Areas 8 Set the schedule for this processes group as execute One Time Only and set the schedule to run immediately The upgrade process only needs to run once The upgrade processes defined in this group begin automatically You can execute the upgrade process without any IBM Tivoli Monitoring for Transaction Performance Web Transaction Performance Version 5 1 0 historical data In this case no data is added into IBM Tivoli Monitoring for Transaction Performance Version 5 2 historical data Set the Version 5 2 central data warehouse ETL and data mart ETL scripts to the Test status to temporarily disable the Version 5 2 central data warehouse ETL processes in the DB2 data warehouse center This prevents the scripts from automatically executing during the upgrade 10 After the upgrade processes are complete view the lt script_file_name gt log _ files in the lt DB2_HOME gt logging directory to ensure that every script completed successfully A completed message at the end of the log file indicates that the script was successfully performed If any errors occur restore the TWH_CDW database from the backup and rerun the processes after pro
483. sactions and uncomplicated to run transaction playback Compared to Generic Windows STI playback has more robust performance measurements simpler content checking better HTTP response code checking and more thorough reporting The most important advantage is the ability of STI to instrument a HTTP request with ARM calls thus allowing for decomposing a STI transaction in the same way that transactions monitored by the Quality of Service and J2EE monitoring components are decomposed Login information is encrypted STI is the first choice monitoring tool partly because it provides transaction and subtransaction response time data Theoretically it is possible to use 100 STI monitoring policies inside and 100 outside the corporate network simultaneously STI runs all the jobs in a serial fashion which is why you should avoid running an large number of transaction performance measurements from every STI To avoid collision between playback policies and thus ensure that all transaction response measuring tasks completes successfully it is recommended to limit the concurrent number of tasks at a single STI monitoring component to 25 within a five minute schedule You should also consider changing the frequency for each run of the policies from five to 10 minutes and distribute the starting times within a 10 minute interval Important The number of simultaneous playback policies you want to run depends on several factors such as policy iterat
484. schema Data from the central data warehouse database are filled into these dimension and fact tables in the data mart database You can then use the hourly daily weekly and monthly star schemes of the dimension and fact tables to generate reports in the TEDW report interface In addition the TMTP warehouse pack includes the migration processes for IBM Tivoli Monitoring for Transaction Performance Version 5 1 which enables upgrading existing historical data collected by the IBM Tivoli Monitoring for Transaction Performance Version 5 1 central data warehouse ETL IBM Tivoli Monitoring for Transaction Performance does not use resource models thus the IBM Tivoli Monitoring warehouse pack and its tables are not required for the TMTP warehouse pack Chapter 10 Historical reporting 381 10 1 3 The monitoring process data flow In this section we will discuss how the warehouse features of both IBM Tivoli Monitoring for Transaction Performance modules interact with the Tivoli Enterprise Data Warehouse We will also describe the various components that make up the IBM Tivoli Monitoring for Transaction Performance warehouse components We will demonstrate how the data is collected from the endpoint and how it reaches the data warehouse database as shown in Figure 10 3 The ETLs used by the warehouse components are explained in Table 10 3 on page 401 and Table 10 4 on page 404 TEDW Environment oA l TEDW Reporting Interface
485. sciplines are grouped in the Service Delivery area which are covered in the following sections Service Level Management Service Level Management involves managing customer expectations and negotiating Service Level Agreements This involves identifying customer requirements and determining how these can best be met within the agreed upon budget as well as working together with all IT disciplines and departments to plan and ensure delivery of services This involves setting measurable performance targets monitoring performance and taking action when targets are not met Cost Management Cost Management consists of registering and maintaining cost accounts related to the use of IT services and delivering cost statistics and reports to Service Level Management to assist in obtaining the correct balance between service Chapter 1 Transaction management imperatives 17 cost and delivery It also means assisting in pricing the services in the service catalog and SLAs Contingency Planning Contingency Planning develops and ensures the continuing delivery of minimum outage of the service by reducing the impact of disasters emergencies and major incidents This work is done in close collaboration with the company s business continuity management which is responsible for protecting all aspects of the company s business including IT Capacity Management Capacity Management plans and ensures that adequate capacity with the expected pe
486. se data marts TEDW can address most of the security requirements related to limiting access to specific data to those customers business units with a need to know gt TEDW provides a scalable architecture Since TEDW depends on the proven and industry standard RDBMS technology it provides a scalable architecture for storing and retrieving the data Tivoli Enterprise Data Warehouse concepts and components This section discusses the key concepts and the various components of TEDW in the logical order that the measurement data flows from the monitors collecting raw data to the final detailed report Figure 10 1 on page 378 depicts a typical Tivoli Enterprise Data Warehouse configuration that will be used throughout this section Chapter 10 Historical reporting 377 378 Figure 10 1 A typical TEDW environment It is common for enterprises to have various distributed performance and availability monitoring applications deployed that collect some sort of measurement data and provide some type of threshold management central event management and other basic monitoring functions These applications are referred as source applications The first step to obtaining management data is to enable the source applications This means providing all the tools and castigation necessary to import the source operational data into the TEDW central data warehouse All components needed for that task are collected in
487. se processeS 1 2 eee 401 10 4 Warehouse processes and components 0 e0 eee 404 A 1 Business patterns 0 0 ae 433 A 2 Integration patterns 0 0 eee 434 A 3 Composite patterns 00 c eee 435 B 1 Rational Robot command line options 00 eee 462 Copyright IBM Corp 2003 All rights reserved xvii xviii End to End e business Transaction Management Made Easy 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 Consult your 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 IBM product program or service may be used Any functionally equivalent product program or service that does not infringe any IBM intellectual property right may be used instead However it is the user s responsibility 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 license inquiries in writing to IBM Director of Licensing IBM Corporation North Castle Drive Armonk NY 10504 1785 U S A T
488. se this option specify a Sample Rate much lower than 100 or a relatively low Number of Samples to collect each minute Chapter 8 Measuring e business transaction response times 291 292 6 Click Next to continue to the J2EE threshold definition as shown in Figure 8 44 Micrncofk Inkarnat Funlorar J IBM Tivoli Monitoring for Transac Mi i internet Explorer ie File Edit View Favorites Tools Help Ea Address x http ftivdees 908z tmtpUYfjspiconsole WeFrameManager isp Gg HBBak gt A Qsearch GaFavorites Meda 63 D 3 a a Tivoli Monitoring for Transaction Performance User Name administrator vConfiguration Configure J2EE Settings Work with Discovery P Create Listening Policy e a Configure J2EE Thresholds a b Threshold Type Work with Listening Pc Performance z Create Alt e Work with Playback Pi R No Entries Work with Schedules Work with Agent Grou pap a Show Enabled Thresholds Show Disabled Thresholds C Work with Transaction Advanced Listening Settings D ai Choose Default Configuration Custom i Work with Realms b Reports b System Administratio J b Downloads Trace Detail Level Off 1 2 3 Servlet oO 6 6 Session EJB 6 6 6 Entity EJB O 6 6 JMS e 066 6 JDBC O 6 6 RMLIIOP o o 6 Filter Threshold Events by Time Percentage Failed 2 I Enable Intelliaent Event Generation z Download
489. server EJB container level which occur when a specified percentage of EJBs are being discarded instead of returned to the pool The returns discarded as a percentage of those returned to the pool exceeded the defined threshold If you receive this indication you may need to increase the size of your EJB pool WebSphereAS HTTP Sessions LiveSessions is too high which occurs when the number of live sessions exceeds the predefined normal amount for an application WebSphereAS JVM Runtime Used JVM memory is too high which occurs when the percentage of used JVM memory exceeds a defined percentage of the total available memory WebSphereAS Thread Pools Thread pool load which occurs when the ratio of active threads to the size of the thread pool exceeds the predefined threshold WebSphereAS Transaction The recent transaction response time is too high which occurs when the average transaction response time exceeds a predefined threshold The timed out transactions are too high which occur when transactions exceed the time out limit and are being terminated a maximum ratio for timed out transactions to total transactions Chapter 5 Interfaces to other management tools 163 gt WebSphereAS Web Applications Servlet JSP errors either at the application server or Web application or servlet level which occurs when the number of servlet error passes a predefined normal amount of errors for the application
490. sets 437 LDAP 25 79 legacy systems 9 11 23 81 License Key 333 334 443 listening policy 189 222 239 create 271 load balance 22 80 81 Local Socket Close 224 log files ETL upfrade 392 M MAHost 189 mail servers 59 managed application create 158 objects 158 managed node 173 managed resource 166 management application 5 6 general 15 needs _ 5 13 specialized 15 Management Agent 247 deploying 311 redirect 181 management agent 57 63 365 communication with server 65 discovery 57 event support 65 installation 130 listening 58 63 playback 58 63 store and forward 58 65 management data 378 Management Server 61 63 82 247 custom installation 88 107 placing 79 port number 140 typical installation 137 uninstall 193 MarProfile 60 Mask field 122 MBean 9 63 182 183 measurement 34 controlled 35 report 413 measurement data 377 metadata interchange 377 metrics report 414 middleware 30 migration 193 Min Max View 217 mission critical 15 Index 487 modules warehouse 378 monitoring 15 153 centralized 14 collection 60 proactive 154 profile 166 real time 35 171 monitoring policy 213 239 health 222 multi dimensional analysis 417 multidimensional reporting 406 multiple DMZ 77 79 multiple firewall 38 79 N non edge aggregation 71 Notes Servers 59 O Object Management Group 377 object model store 62 occurrences 164 170 ODBC data source 419 ODBC connection 393 OLAP 375 417 analysis
491. setting for Pet Store 2 04 314 8 63 QoS listening policies for Pet Store automatic threshold setting 315 8 64 QoS correlation with J2EE application 20000000 316 8 65 Pet Store transaction and subtransaction response time by STl 317 8 66 Page Analyzer Viewer report of Pet Store business transaction 318 8 67 Correlation of STI and J2EE view for Pet Store application 319 8 68 J2EE dofilter methods creates events 00 0020005 320 8 69 Problem indication in topology view of Pet Store J2EE application 321 8 70 Topology view event violation by getShoppingClientFacade 322 8 71 Response time for getShoppingClienFacade method 322 8 72 Real time Round Trip Time and Back End Service Time by QoS 323 9 1 Rational Robot Install Directory 0 0 0 eee eee eee 327 9 2 Rational Robot installation progress 00 eee eae 328 9 3 Rational Robot Setup wizard 0 000 cee eee 328 9 4 Select Rational Robot component 20000 eee 329 9 5 Rational Robot deployment method 020 cee eee 329 9 6 Rational Robot Setup Wizard 0 000 eee eee 330 9 7 Rational Robot product warnings 00 ee ee eee 330 9 8 Rational Robot License Agreement 000 ec eee eae 331 9 9 Destination folder for Rational Robot 00008 331 9 10 Ready to install Rational Robot 000
492. sing this mechanism you can get the following information Idle Times The times between Web page activities such as subdocument loads depicted in the chart by narrow bands between the bars in the line Local Socket Close The time at which the local socket closed depicted in the chart by a black dot Host Socket Close The time at which the host socket closed depicted in the chart by a small red caret character Properties A page that provides the following information about the bars in the selected line Summary A summary of the number of items connections resolutions servers contacted total bytes sent and received fastest response time Server Response Time Low slowest response time Server Response Time High and the ratio between the data points You can use this information to evaluate connections Sizes The total number of bytes that were sent and received and the percentage of overhead for the page Events A list of the violation and recovery events that were generated during page retrieval and rendering Comments An area in which you can type your comments for future reference Lastly by clicking on the Details tab at the bottom of the chart you may see a list of the requests made by a Web page to the Web server 224 End to End e business Transaction Management Made Easy Measuring e business transaction response times This chapter discusses methods and tools provided by IBM Tivoli Monitoring for Tra
493. so called warehouse modules for each source application In this publication IBM Tivoli Monitoring for Web Infrastructure is the source application providing management data for Web server and Application server data warehouse modules One important part of the warehouse modules are the Extract Transform and Load data programs or simply ETL programs In general ETL programs process data in three steps 1 First they extract the data from a source application database called the data source 2 Then the data is validated transformed aggregated and or cleansed so that it fits the format and needs of the data target 3 Finally the data is loaded into the target database End to End e business Transaction Management Made Easy In TEDW there are two types of ETLs central data warehouse ETL and data mart ETL Central data warehouse ETL The central data warehouse ETL pulls the data from the source applications and loads it into the central data warehouse as shown in Figure 10 1 on page 378 The central data warehouse ETL is also often referred to as the source ETL or ETLI Data mart ETL As shown in Figure 10 1 on page 378 the data mart ETL extracts a subset of historical data from the central data warehouse that contains data tailored to and optimized for a specific reporting or analysis task This subset of data is used to populate data marts The data mart ETL is also known as target ETL or ETL2 As a generic concept a da
494. ss more business processes management and so on across separate enterprises It would be very convenient if all problems fit nicely into these four Business patterns but in reality things can be more complicated The patterns assume that Appendix A Patterns for e business 433 all problems when broken down into their most basic components will fit more than one of these patterns When a problem describes multiple objectives that fit into multiple Business patterns the Patterns for e business provide the solution in the form of Integration patterns Integration patterns enable us to tie together multiple Business patterns to solve a problem The Integration patterns are shown in Table A 2 Table A 2 Integration patterns Access Integration Integration of anumber of services Portals through a common entry point Application Integration Integration of multiple applications Message brokers and data sources without the user and workflow directly invoking them managers These Business and Integration patterns can be combined to implement installation specific business solutions We call this a Custom design We can represent the use of a Custom design to address a business problem through an iconic representation as shown in Figure A 2 Figure A 2 Pattern representation of a Custom design If any of the Business or Integration patterns are not used in a Custom design we can show that with lighter blocks For ex
495. stallation and deployment In the first part of this chapter we will demonstrate the installation of TMTP Version 5 2 in a production environment There are two approaches to installing the TMTP Version 5 2 Management Server The first one is called typical installation where the setup program will install and configure everything for you including the required DB2 Version 8 1 WebSphere Application Server Version 5 0 and WebSphere Application Server FixPack 1 The second approach is to install TMTP Version 5 2 in an environment where either the DB2 or the WebSphere Application Server or both are already deployed This is called custom installation Both approaches have secure and a nonsecure options We will use the custom secure installation option on AIX Version 4 3 3 in this scenario We will show you how to configure your environment and how to prepare the previously installed DB2 Version 8 1 and WebSphere Version 5 0 1 Server to be able to install TMTP Version 5 2 smoothly The description of this environment and the architecture can be found in 3 6 Putting it all together on page 80 Copyright IBM Corp 2003 All rights reserved 85 In the second part of this chapter we will demonstrate a typical nonsecure installation suitable for the quick setup of the TMTP in a test or small business environment SuSE Linux 7 3 will be used as an installation platform 86 End to End e business Transaction Management Ma
496. static two dimensional reports of your data using the data marts The Report Interface is a role based Web interface that can be accessed with a simple Web browser without any additional software installed on the client You can also use other tools to perform OLAP analysis business intelligence reporting or data mining Chapter 10 Historical reporting 379 The TEDW Control Center is the IBM DB2 Universal Database Enterprise Edition server containing the TEDW control database that manages your TEDW environment From the TEDW Control Center you can also manage all source applications databases in your environment The default internal name for the TEDW control database is TWH_MD The TEDW Control Center also manages the communication between the various components such as the TEDW Central Data Warehouse the data marts and the Report Interfaces The TEDW Control Center uses the DB2 Data Warehouse Center utility to define maintain schedule and monitor the ETL processes The TEDW stores raw historical data from all Tivoli and third party application databases in the TEDW Central Data Warehouse database The internal name of the TEDW Central Data Warehouse database is TWH_CDW Once the data has been inserted into the TWH_CDW database it is available for either the TEDW ETLs to load to the TEDW Data Mart database the internal name of the TEDW Data Mart database is TWH_MART or to any other application specific ETL to process the data and load t
497. stening components A Quality of Service discovery policy discovers transactions that run through the Web servers in your environment A J2EE discovery policy discovers transactions that run on J2EE application servers Figure 2 2 on page 42 shows an example of a discovered application topology Chapter 2 IBM Tivoli Monitoring for Transaction Performance in brief 41 42 SIhMRRINIRINENIRERER TNL Microsoft internet Explorer Tivoli Monitoring for Transaction Performance All Times are in Seconds as ooga ad tivlabO7 J2EE WebLogic 7 0 1 petstore petstoreServer STI aA a f Overall Transaction 12 508 z Session EJB 1 594 a y 5 E URL 3 746 o 4 esi zi Pil lat l ss BE Local intranet Z E Work with Playback Policies Choose Create Edit etc Figure 2 2 Application topology discovered by TMTP Listening The Quality of Service component The Quality of Service component samples incoming HTTP transactions against a Web server and measures various time intervals involved in completing each transaction An HTTP transaction consists of a single HTTP request and response A sample of transactions might consist of every tenth transaction from a specific collection of users over a peak time period The Quality of Service component can measure the following time intervals for each transaction gt Back end service time This is the time it takes a Web server
498. t Agent to be the MA apps genwin directory where MA denotes the installation directory of the Management Agent Since this directory structure is created as part of the Generic Windows Management Agent installation procedure we advise you to install this component prior to defining and recording projects Before proceeding either install the Generic Windows Management Agent or open Windows Explorer and create the directory structure for the project Make sure the project directory itself is empty To create a Rational Project perform the following steps 1 Start the Rational Administrator by selecting Start Programs Rational Robot Rational Administrator 2 Start the New Project Wizard by clicking File New Project on the Administrator menu 3 On the wizard s first page Figure 9 20 on page 340 a Supply a name for your project for example testscripts The dialog box prevents you from typing illegal characters b In the Project Location field specify a UNC path to the root of the project referring to the directory name you created in above It does not really have to be a shared network directory with a UNC path Chapter 9 Rational Robot and GenWin 339 G New Project General Please specify the name of the new project an empty directory in which to create it and whether or not the project is UCM enabled Project name testscripts Project location Mflotsam RationalT est Browse
499. t a Cached HTML hitp tiv ab01 itsc austin ibrm corn petstorevitems screen pr 0 8489 Connect Idle 4 ile ae S Cache Ly httpuitivlab01 itsc austin ibm comipetstore cart do action p 1 081 24 mp Javascript 2 http itiviab01 Jtse austin ibrn comspetstore enter_order_info 2 8048 Socks Connect cached Unknown Text http Jitivlab01 itsc austin ibm comipetstore order do given_ 2 0142 E ean E Cached Java 1 httpuitiviab01 itse austin ibm com petstore signoff do 0 5586 J Cached Autoproxy E SSL Connect il Cached Unknown App ag Cached GIF i SSL Connect Idle E Cached JPEG lt Z Oe httpitiviabO1 itsc austin ibm com petstore enter_order_information screen el Applet started ia fia GE Local intranet Figure 8 66 Page Analyzer Viewer report of Pet Store business transaction The topology view in Figure 8 67 on page 319 shows how the STI transactions propagates to the J2EE Application Server and shows the parent child relationship with the Pet Store simulated transaction and various J2EE application components 318 End to End e business Transaction Management Made Easy E Le Microsort Intern E a livoh Monitoring tor Iransaction Pertormance Microsott internet Explorer File Edit View Favorites Tools Help Back gt 2 A Reach GFavortes meda B G SI Tivoli Monitoring for Transaction Performance User Name administrator All Times are in Seconds Be aeaagea 6h
500. t be interested in For example you can use datapools to feed data in the simulation that will change data entered in specific fields or use an Authentication Datapool if you want to store passwords and login IDs separately from the script although we recommend encrypting passwords locally using VB code the following section Obfuscating embedded passwords in Rational Scripts on page 356 describes how to do this You may also be interested in tips regarding screen locking discused in Rational Robot screen locking solution on page 360 Obfuscating embedded passwords in Rational Scripts Often when recording Rational Scripts it is necessary to record user IDs and passwords This has the obvious security exposure that if your script is viewed the password will be viewable in clear text This section describes a mechanism for obfuscating the password in the script This mechanism relies on the use of an encryption library The encryption library that we used is available on the redbook Web site The exact link can be found in Appendix C Additional material on page 473 First the encryption library must be registered with the operating system For our encryption library this was achieved by running the command regsvr32 exe EncryptionAlgorithms d1 Once you have run this command you must encrypt your password to a file for later use in your Rational Robot scripts This can be achieved by creating a Rational Robot Scr
501. t is easier to add the two script files required in the Create Generic Windows Transaction window if you are running your TMTP browser from the machine on which the scripts are located By default these two files will be located in the ProjectDir TestDataStore DefaultTestScriptDataStore TMS_ Scripts directory ProjectDir is the directory in which your source Rational Robot project is located Two files are required for each recording a rec and a rtxml file For example if the script you recorded was named TestNotepad you would need 368 End to End e business Transaction Management Made Easy to add both the TestNotepad Script rtxml and TestNotepad rec files Once you have added both files press the OK button l IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer Tivoli Monitoring for Transaction Performance vy Configuration Work with Discovery Create Generic Windows Transaction Work with Listening Work with Playback Work with Schedule Work with Agent Gr Step 1 Select a Robot file to upload Work with Transacti Browse Work with Realms gt Reports vSystem Administrai Work with Agents Configure System E i Robot Files PST PEA pees TestNotepad rec Configure User Setti TestNotepad Script rtxml Work with Event Re Remove Alt r View System Event View Log Files View Management OK Alt 0 Cancel Alt c gt Downloads Step 2 Click on Add to inc
502. t task Every jis 4 minutes Unti Time 6 iy PM C Duration 4 hours minute s If the task is still running stop it at this time Figure B 18 Advanced scheduling options It is also possible to schedule the execution of the Rational Robot using other framework functionality such as scheduled Tivoli Tasks or custom monitors These other mechanisms may have the benefit of allowing schedules to be managed centrally Rational Robot command line options You can use the Rational Robot command line options to log in open a script and play back the script The syntax is as follows rtrobo exe scriptname user userid password password project full path and full projectname play purify quantify coverage build build logfolder foldername log logname nolog close The options are defined in Table B 1 Table B 1 Rational Robot command line options 462 End to End e business Transaction Management Made Easy password password Optional password for login Do not use this parameter if there is no password project full path and full projectname Name of the project that contains the script referenced in scriptname preceded by its full path play If this keyword is specified plays the script referenced in scriptname If not specified the script opens in the editor purify Used with play Plays back the script referenced in scriptname under Rational Purify
503. ta warehouse is a structured extensible database environment designed for the analysis of consistent data The data that is inserted in a data warehouse is logically and physically transformed from multiple source applications updated and maintained for a long time period of time and summarized for quick analysis The Tivoli Enterprise Data Warehouse Central Data Warehouse CDW is the database that contains all enterprise wide historical data with an hour as the lowest granularity This data store is optimized for the efficient storage of large amounts of data and has a documented format that makes the data accessible to many analysis solutions The database is organized in a very flexible way which lets you store data from new applications without adding or changing tables The TEDW server is an IBM DB2 Universal Database Enterprise Edition server that hosts the TEDW Central Data Warehouse databases These databases are populated with operational data from Tivoli and or other third party applications for historical analyses A data mart is a subset of the historical data that satisfies the needs of a specific department team or customer A data mart is optimized for interactive reporting and data analysis The format of a data mart is specific to the reporting or analysis tool you plan to use Each application that provides a data mart ETL creates its data marts in the appropriate format TEDW provides a Report Interface Rl that creates
504. table 381 historical analysis 376 historical data 60 170 376 379 392 holes 164 hostname 87 132 376 Host Socket Close 224 hosting 22 hostname 118 hotfix 332 hourly performance 220 HTTP request 230 response code 230 hyperlink 218 l IBM Automation Blueprint 30 icon status 212 216 Idle Times 224 ikeyman 93 implementation 79 indications 166 170 171 indicators 162 information page specific 223 transaction process 380 infrastructure management 10 system management 26 installation Rational Robot 326 Web Infrastructure 155 instance 66 91 data 60 topology 47 213 transaction 217 instance owner 395 instrument 188 instrumentation 157 Integrated Solutions Console 174 integration 30 point 51 interactive reporting 379 Internet zone 129 interpreted status 217 486 End to End e business Transaction Management Made Easy intranet 58 zone 130 IP address 376 IPCAppToEngSize 185 J J2EE 229 application 5 81 architecture 7 component 278 component remove 196 components 307 monitoring 72 76 82 188 232 support 73 topology 216 J2EE monitoring 293 settings 204 J2EE Monitoring Management Agent 82 J2EE subtransaction 293 Java Enabler 335 Java Management Extension 61 Java Management Extensions 9 Java Runtime Environment 156 483 Java Virtual Machine 7 JDBC 206 error 178 JIT 74 probes 75 JKS 123 files 93 JSP errors 164 Just In Time Instrumentation 74 JVM 336 365 memory 163 K KDB files 98 L layered as
505. tallShield Figure 9 2 Rational Robot installation progress The setup wizard will be loaded and displayed see Figure 9 3 Rational Welcome to the Setup Wizard the software development company This Wizard will guide you through the installation of Rational products Click Next to continue lt Back Cancel Help Figure 9 3 Rational Robot Setup wizard Click on Next and the Product Selection panel is displayed In this panel you have the choice of selecting the Rational License Manager that you need to use Robot and Rational Robot itself Select Rational Robot in the left pane see Figure 9 4 on page 329 328 End to End e business Transaction Management Made Easy Rational Setup Wizard 4 x Product Selection g Choose the product to install R a t iona 1 the software development company 5 4 Rational Products Product Description Rational License Server A functional and performance test tool for a ARLEN software quality teams that want to automate performance regression and smoke testing of Java NET Web VB ERP and client server applications in a mixture of Windows and Unix environments lt Back Cancel Figure 9 4 Select Rational Robot component Click Next to continue the setup the Deployment Method panel is displayed see Figure 9 5 x Deployment Method P 5 Choose a deployment method for installation R at Iona 1 and configuration the software d
506. tarts by looking at the network to see if they can detect any problems at this level Operations team in the NOC calls the SysAdmins or Senior Technical Support Staff that is the more senior staff that are responsible for applications in production Then a lot of people are paged The number of pagers that go off is often dependent on the severity of the SLA or the customer involved If it is a big problem a tiger team will be assembled This typically large group of people are assembled to try and resolve the problem The SysAdmins check to see if anything has changed in the past day to understand what the cause may be If possible they roll back to a previous version of the application to see if that fixes the problem The SysAdmins then typically have a check list of things they do or tools they use to troubleshoot the problem Some of the tasks they may perform are gt Look at any monitoring tools for hardware OS and applications gt Look at the packet data number of collisions loss between connections and so on gt Crawl through the log files from the application middleware and so on gt The DBAs will check databases from the command line to see what response time looks like from there gt Call other parties that may be related host based applications application developers that maintain the application and so on Finger pointing Unfortunately it is still very difficult to solve the problem
507. ted after a violation Based on your selection you can set thresholds for the following Performance Back End Service Time Page Render Time Round Trip Time Transaction Status Failure or specific HTTP return codes For each threshold you are creating you should press Apply to save your settings and when finished click Next to continue to the Configure J2EE Settings dialog End to End e business Transaction Management Made Easy 8 Since this does not provide functions for the QoS listening policy click Next again to proceed to the schedule selection for the policy 9 Schedules for Quality of Service listening policies are selected the same way as for any other policy Please refer to 8 4 4 Playback schedule definition on page 248 for more details related to schedules Click Next to go on to select Agent Groups for the listening policy 10 Agent Group selection is common to all policy types Please refer to the description provided in item 4 on page 270 for further details Click Next to finalize your policy definition 11 Having defined all the necessary properties of the QoS listening policy all that is left before you can save and deploy the listening policy is to assign a name and determine when to deploy the newly defined listening policy to the Management Agents Z IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer E loj x File Edit View Favorites Tools Help Ea Address a
508. ted that the tools for Web and enterprise transaction performance monitoring complement one another and that there are no restrictions if the networking and management infrastructure is in place for using Enterprise monitors in the Web space or vice versa Chapter 1 Transaction management imperatives 33 34 Internet Transactions Corporate Firewall Browser Access Control Load Balancing f Demitarzed zone gt Firewall Browser e Business TAA gt Application Applicaton Zone D Firewall Enterprise Zone 7 N S LOB Geo LOB Geo LOB Geo LOB Geo LOB Geo LOB Geo Enterprise Transactions Figure 1 13 e business transactions Web transaction monitoring In general the nature of Web transaction performance measurement is random and generic There is no way of planning the execution of transactions or the origin of the transaction initiation unless other measures have been taken in order to do so When the data from the transaction performance measurements are being aggregated they provide information about the average transaction invocation without affinity to location geography workstation hardware browser version or other parameters that may affect the experience of the end user All of these parameters are out of the application provider s control Naturally both the data gathering and
509. th Agent Groups wi y Work with Transaction Recordings ies sae Please make a selection J Go Alttg Work with Realms Group Violation Response Level gt Reports Type Condition Threshold b System Administration Bere ees I Page Render Time Above 0 1 Seconds Warning gt Downloads Page as Show Enabled Thresholds Show Disabled Threshalds Advanced Listening Settings Back End Serice Time Page Render Time and Round Trip Time Back End Service Time Only Filter Threshold Events by Time Percentage Failed I Enable Intelligent Event Generation Time Interval minutes 4 Minutes Percentage Failed il Percent lt Back Alt b Next Alt n gt Finish Alt Cancel Alt c Figure 8 30 Configure QoS automatic threshold To create a specific threshold select the type in the drop down menu under the dialog heading Two types are available Performance Transaction Status When clicking Create the Configure QoS Thresholds dialog shown in Figure 8 31 on page 276 will be displayed Detailed descriptions of each of the properties are available in the BM Tivoli Monitoring for Transaction Performance User s Guide Version 5 2 0 C32 1386 Chapter 8 Measuring e business transaction response times 275 3 IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer Fie Edt View Favorites Tools Help Tivoli Monitoring for Transaction Performance User N
510. the Tivoli PAC for WebSphere Application Server gt WebSphereAS Administration Server Status Administration server is down occurs when the status of the WebSphere Application Server administration server is down gt WebSphereAS Application Server Status Application server is down occurs when the status of the WebSphere Application Server application server is down 162 End to End e business Transaction Management Made Easy WebSphereAS DB Pools Connection pool timeouts are too high which occur when the database connection timeout exceeds a predefined threshold DB Pools avgWaitTime is too high which occurs when the average time required to obtain a connection in the database connection pool exceeds the predefined threshold Percent connection pool used is too high which occurs when the percentage of database connection in use is higher than a predefined threshold assuming you have sufficient network capacity and database availability you might need to increase the size of the database connection pool WebSphereAS JEJB Enhanced Java Bean EJB performance either gathered at the EJB or application server EJB container level which occurs when the average method response time ms exceeds the response time threshold The load is also reported by concurrent active EJB requests and throughput is measured by the EJB request rate per minutes EJB exceptions either gathered at the EJB or application
511. the enterprise in order to monitor the transaction performance of our other enterprise systems such as SAP Seibel and our 3270 applications from an end user s perspective J2EE Monitoring Management Agent We chose to deploy the Management Agent and J2EE monitoring behavior to each of our WebSphere Web Application servers This will provide us with the ability to do detailed transaction decomposition to the method level for our J2EE based applications End to End e business Transaction Management Made Easy Part 2 Installation and deployment This part discusses issues related to the installation and deployment of IBM Tivoli Monitoring for Transaction Performance Version 5 2 In addition information regarding the maintenance of the TMTP solution is provided The following main topics are included gt Chapter 4 TMTP WTP Version 5 2 installation and deployment on page 85 gt Chapter 5 Interfaces to other management tools on page 153 gt Chapter 6 Keeping the transaction monitoring environment fit on page 177 The target audience for this part is individuals who will plan for and perform an installation of IBM Tivoli Monitoring for Transaction Performance Version 5 2 as well as those who are responsible for the overall well being of the transaction monitoring environment Copyright IBM Corp 2003 All rights reserved 83 84 End to End e business Transaction Management Made Easy TMTP WTP Version 5 2 in
512. the following steps 1 Open your browser and type the following text in the address field http lt server_name gt dmwhc where lt server_name gt is the fully qualified host name or IP address of the server hosting the Web Health Console 2 Supply the following information User Tivoli user ID Password Password associated with the Tivoli user ID Host name The managed node to which you want to connect 3 The first time you log in to the Web Health Console the Preferences view is displayed You must populate the Selected Endpoint list before you can access any other Web Health Console views When you log in subsequently the endpoint list is loaded automatically 170 End to End e business Transaction Management Made Easy 4 Select the endpoints that you want to monitor and choose the Endpoint Health view This is the most detailed view of the health of an endpoint In this view the following information is displayed a The health and status of all Resource Models installed on the endpoint b The health of the indications that make up the Resource Model and historical data After setting up the Web Health Console you are able to display the health of a specific endpoint to view the data use the theoretical view option Figure 5 6 shows an example of real time monitoring of an WebSphere Application Server Z IBM Tivoli Monitoring Connected to Managed Node x220sur Micr
513. thm does not rely on timing percentages to determine what is Violated and Most Violated Instead it compares the absolute difference between the instance and aggregate timing data while subtracting the sum of the values of the children instances This provides for a more accurate estimate of the worst performing subtransaction because it is an estimate of the time actually spent in the node The value calculated for each node is determined by the formula sum of transaction s relations instance time sum of children instance time sum of transaction s relations aggregate time sum of children aggregate average This will provide a value in seconds that is an approximation of time spent in the node method The transaction with the greatest of these values will be the Most Violated The top 5 by default of these transactions will have status Violated The calculated values will not be shown to the user If a node has a Zero or negative value when sum of transaction s relations instance time sum of transaction s relations aggregate time occurs then it will not be marked The reason for this is because a negative value implies the node performed below its average for the hour and hence cannot be considered slow Intelligent event generation Enabling this option can reduce event generation Intelligent event generation merges multiple threshold violations into a single event making notification and report
514. ting and training third party books and documentation and so on Standard tools tend to travel with a whole caravan of support and services that help organizations succeed Crystal Reports is designed to produce accurate high resolution output to both DHTML and PDF for Web viewing and printing Output to RTF enables integration of structured content into Management Server Word documents Built in XML support and a standard Report XML schema deliver output for other devices and business processes and native Excel output enables further desktop analysis of report results For more information about Crystal Reports go to http www crystaldecisions com 10 4 2 Crystal Reports integration with TEDW 418 The following section provides information on how to customize and use Crystal Reports to generate OLAP reports based on the historical data in the TEDW database gathered by IBM Tivoli Monitoring for Transaction Performance End to End e business Transaction Management Made Easy Setting up integration Follow the following steps to configure Crystal Reports 1 Install Crystal Reports at your desktop 2 Install DB2 client at your desktop if you have not installed it already 3 Create ODBC data sources at your desktop to connect TWH_CDW database Crystal Reports and TMTP Version 5 2 sample reports TWH_CDW database ETL1 source data has been used here to create TMTP reports through Crystal Reports Steps to create a report F
515. tion environment 87 204 production status 404 Profile Manager 166 profile monitoring 166 Properties 224 protocol layer 326 provisioning 29 proxy 26 121 132 prune 191 public report 414 Q QoS 229 232 configuring 253 graph 213 placing 79 Quality of Service 229 232 257 deployment 259 Quality of Service Management Agent 82 R Rational Robot 58 59 195 233 440 installation 326 license key 333 Rational Robot GenWin Management Agent 82 raw data 376 RDBMS 377 realm 255 create 255 settings 256 real time 170 monitoring 8 33 35 171 report 40 62 realtime reporting 50 record 337 440 GUI script 345 simulation 344 recording 35 Redbooks Web site 482 Contact us xxiv reference data 33 transaction 33 refresh rate 175 Big Board 215 register 368 remove J2EE component 196 report automatic 407 availability graph 222 categories 409 component 413 general topology 222 measurement 413 metrics 414 overall transactions over time 220 Page Analyzer Viewer 223 public 414 schedule 416 Slowest Transactions Table 222 summary 413 time inteval 416 transaction performance 295 Transaction with Subtransaction 221 types 295 Report Interface 379 TEDW 407 report interface TEDW 381 reporting 34 60 business intelligence 379 capabilities 44 interactive 379 multidimentional 406 roles 407 Index 489 reports creating 407 extreme case 413 health check 408 request HTTP 230 requests Web page 224 requirements operati
516. tion Choose Component or Monitoring Component aret NADENE Deploy QoS Component z Go anfigure System Event Details amponent Management onfigure User Settings HTTP Proxy Server Configuration ork with Event Responses ew System Events Host Name Port Number ew Log Files tivlab01 itsc austin ibm co 80 ew Management Server Details nloads SSL F Key Database File Path Key Name Optional Origin HTTP Proxy Server Configuration Host Name Port Number tivdce4 itsc austin ibm cor 80 ssl O Key Name Optional R After deployment completes the host computer for the management agent will restart automatically OK Alt 0 Apply Alt a Cancel Alt c X SAA D M af with Email and Script Actions jell fax Local intranet Figure 8 19 Deploy QoS components The Deploy Components and or Monitoring Component dialog shown in Figure 8 19 is used to configure the parameters for the QoS component The information to be provided is grouped in two Server Configuration sections HTTP Proxy Specifies the networking parameters for the virtual server that will receive the requests for the origin server The host name should be that of the Management Agent which is the target of the QoS deployment and the port number can be set to any free port on that system Origin HTTP Proxy Specifies the networking parameters of the origin server which will serve the requests forwarded from the virtual server residing on the QoS system The host name should be set
517. tion and deployment 115 E Install the Management Server Tivoli software Ee Creating the project JPEG o x n Cd X lt 4 installShield Figure 4 31 Installation progress window gt The installation wizard now creates the TMTP database tables two additional tablespaces TMTP32K and TEMP_TMTP32kK It also registers the TMTPv5_2 application in the WebSphere Server gt Once the installation is finished Figure 4 32 on page 117 the WebSphere Server must be restarted because the WebSphere Application Server security will now be applied To stop and start the WebSphere server we use the following commands These scripts are located in the was_installation_directory bin In our case it is usr WebSphere AppServer bin stopServer sh serverl user root password password startServer sh serverl user root password password End to End e business Transaction Management Made Easy E Install the Management Server _ 15 x The InstallShield Wizard has successfully installed IBM Tivoli Monitoring for Transaction Performance Management Server Choose Finish to exit the wizard installShield Nw Figure 4 32 The finished Management Server installation gt Once the WebSphere server is restarted we log on to the TMTP server by typing the following URL into our browser https ipaddress 9445 tmtpUI gt As the installation was successful we see the following logo
518. tion and recording the transaction times in the TMTP environment the GenWin recording which is saved as a VisualBasic script has to be executed from a Management Agent and ARM calls must be inserted manually into the script in order to provide the measurements The advantage of this technology is that it is possible to measure and analyze the response time of specific infinitely small or large parts of an application because the arm_start and arm_stop calls may be placed anywhere in the script This is an excellent supplement to STI In addition GenWin provides functions to monitor dynamic page strings which is currently a limitation in the STI endpoint For details see Limitations of Synthetic Transaction Investigator on page 231 For more details on the Generic Windows endpoint technology please refer to 9 2 Introducing GenWin on page 365 Chapter 8 Measuring e business transaction response times 233 Limitations of Generic Windows Before planning to use GenWin scripts for production purposes you should be aware of the following limitations in the current implementation gt GenWin runs playback in a visual mode using an automated operator type of playback One implication of this mode of operation is that the playback systems has to be dedicated to the playback task and that a user has to be logged on while playback is taking place If a user local or remote manipulates the mouse and or keyboard while playback is
519. tion architect consults with systems management specialists while designing the application The systems management solution has to play more or less by the rules set up by the application Ideally it will manage the various application resources without any impact on the e business application while observing company policies on networking use security and so on Management of e business applications is therefore best achieved by establishing yet another networking tier parallel to the application tier in which all systems management components can be hosted without influencing the applications Naturally since the management applications have to communicate with the resources that must be managed the two meet on the network and on the machines hosting the various e business application resources Using the Tivoli product set it is recommended that you establish all the central components in the management tier and have a few proxies and agents present in the DMZ and application tiers as shown in Figure 1 9 on page 27 26 End to End e business Transaction Management Made Easy pa Distributed Sys Mgmt Agents Tivoli Gateway Tivoli Endpoint ITM Monitoring Engine Firewall at Demilitarized Zone Firewall Distributed Sys Mgmt Agents Tivoli Gateway Application Tivoli Endpoint gt ITM Monitoring Engine mer BEA Mgmt Resources Tivoli Firewall paeng TEC Server Tier TBSM Se
520. to receive the request process it and respond to it gt Page render time This is the time it takes to process and display a Web page on a browser gt Round trip time also called user experience time This is the time it takes to complete the entire page request from the moment the user initiates the End to End e business Transaction Management Made Easy request by clicking on a link for example until the request is fulfilled Round trip time includes back end service time page render time and network and data transfer time Listening The J2EE monitoring component The J2EE monitoring component collects performance data for transactions that run on a J2EE Java 2 Platform Enterprise Edition application server Six J2EE subtransaction types can be monitored servlets session beans entity beans JMS JDBC and RMI The J2EE monitoring component supports the following two application servers gt IBM WebSphere Application Server 4 0 3 and up gt BEA WebLogic 7 0 1 You can dynamically install and remove ARM instrumentation for either type of application server You can also enable and disable the instrumentation Playback Synthetic Transaction Investigator The Synthetic Transaction Investigator STI component measures how users might experience a Web site in the course of performing a specific transaction such as searching for information enrolling in a class or viewing an account Using STI involves the following
521. to specify an area where you would like the tests to reside b Select initialization options as appropriate c Click Advanced Database Setup and select the type of database engine for the Test datastore d Click OK Working with Java Applets If you are going to use Robot with Java applets follow these simple instructions By default Java testing is disabled in Robot To enable Java testing you need to run the Java Enabler The Java Enabler is a wizard that scans your hard drive looking for Java environments such as Web browsers and Sun JDK installations that Robot supports The Java Enabler only enables those environments that are currently installed If you install a new Java environment such as a new release of a browser or JDK you must rerun the Enabler after you complete the installation of the Java Appendix B Using Rational Robot in the Tivoli Management Agent environment 449 environment You can download updated versions of the Java Enabler from the Rational Web site whenever support is added for new environments To obtain the most up to date Java support simply rerun the Java Enabler Running the Java Enabler 1 Make sure that Robot is closed Select Start Programs Rational Robot Rational Test Java Enabler N Select one of the available Java enabling types Select the environments to enable Click Next Click Yes to view the log file D Or oe o Note If the Java Enabler does not f
522. to the name of the system hosting the application server for example WebSphere Application Server and the port number should be set to the port that the application server listens to for a particular application End to End e business Transaction Management Made Easy Provide the values as they apply to your environment and click OK to start the deployment After couple of minutes the Management Agent will be rebooted and the Quality of Service component has been deployed 3 To verify that the installation was successful refresh the Work with Agents dialog and verify that the status for the QoS Component on the Management Agent in question shows Installed as shown in Figure 8 20 IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer Il Fie Edt view Favorites Tools Hel gt address la http tivdee4 9082 tmtpUI isp console WcFrameManager jsp Tivoli Monitoring for Transaction Performance User Name administrator gt Configuration Work with Agents b Reports System Administra Work with Agents Q Configure System E Component Manag Name STI QoS J2EE Generic Windows Store and Forward Status Platfor Configure User Seti z Work with Event Re E ibmtne Running Online w32 ix86 View System Event I tivdce4 itsc austin ibm com Online w32 ix86 View Log Files T tiviabot R Installed instanea Offline w32i86 View Management gt Downloads Pag
523. toring for Transaction Performance User Name administrator Configure J2EE Listener URI Filter http ibmtivO trade app User Name Advanced Settings Assign Name Data Filter Sample Rate 100 Percent Number of Samples 5 Write on Disk Aggregate Data Only Collect 5 Instance after failure C Aggregate and Instance lt Back Alt b _ IINERZNENIES Finish Alt f _ Cancel Alt c Ei a Work with Transaction Recordings Create Lt etc oil fox Local intranet ao Figure 8 43 Configure J2EE listener 5 Choose the appropriate values for filtering and data collection and filtering Selecting Aggregate and Instance specifies that both aggregate and instance data are collected Aggregate data is an average of all of the response times detected by a policy Aggregate data is collected at the monitoring agent once every minute Instance data consists of response times that are collected every time the transaction is detected All performance data including instance and aggregate data are uploaded to the Management Server once an hour by default However this value can be controlled through the Schedule Management Agent Upload dialog which can be accessed from the TMTP console home page by navigating to System Administration Work with agent Schedule a Collection For a high traffic Web site specifying Aggregate and Instance quickly generates a great deal of performance data Therefore when you u
524. tp 1 2 E SERVER 1 P L and make really sure all other stuff is forbidden when it should survive the above rules RewriteRule F Setup URL reverse mapping for redirect reponses ProxyPassReverse http 9 3 5 20 80 ProxyPassReverse http 9 3 5 20 lt VirtualHost gt Hea Ea RH EH BH EH EH EE PE a a second backend machine created manually Ha Ea RH EH BH EH EH PE AARRE ERARREEERREREEEEREEH lt VirtualHost backend2 80 gt SSLEnable ServerName backend2 QoSMContactURL http 9 3 5 14 80 Enable the URL rewriting engine and proxy module without caching RewriteEngine on Chapter 8 Measuring e business transaction response times 263 264 RewriteLogLevel 0 ProxyRequests on NoCache Define a rewriting map with value lists mapname key filename Rewri teMap server txt lt QOSBASEDIR gt IBMHTTPServer conf apache rproxy conf servers Make sure the status page is handled locally and make sure no one uses our proxy except ourself RewriteRule apache rproxy status L RewriteRule https http ftp A Now choose the possible servers for particular URL types RewriteRule cgilshtml to 9 3 5 15 80 1 S 1 RewriteRule AL to 9 3 5 15 80 1 and delegate the generated URL by passing it through the proxy module RewriteRule to http 1 2 E SERVER 1 P L and make really sure all other stuff is forbidden whe
525. tp ftivdce4 9082 tmtpUL jsp console WcFrameManager jsp foal o m gt vConfigurati Work with Work with Work with Work with Work with Work with Session EJB z Work with vReports 5 TradeBean View Big View Gen View Corr even getMarketSummary0 b System Ad 2 307 b Downloads Events View Response Times View o Web Health Console Thresholds View x Minimum Maximum View EJSRemmpteS tatelessTradeEJB_90439d68 lal Figure 8 56 Topology view of J2EE details Trade EJB get market summary 8 8 Using TMTP with BEA Weblogic This section discusses how to implement and configure the J2EE components in a BEA Weblogic application server environment In this section we introduce the Pet Store sample business application and demonstrate drill down into all the business processes step by step In addition front end as well as back end reports are provided for all activities in order to illustrate how IBM Tivoli Monitoring for Transaction Performance Version 5 2 standard components can be applied to a Weblogic environment to gt Measure real time Web transaction performance gt Measure synthetic end user time gt Identify bottlenecks in the e business processes This section contains the following gt 8 8 1 The Java Pet Store sample application on page 308 gt 8 8 2 Deploying TMTP components in a Weblogic environment on p
526. two activities gt Recording a transaction You use STI Recorder to record your actions as you perform the sequence of steps that make up the transaction For example you might perform the following steps to view an account log on click to display the main menu click to view an account summary and log off The mechanism for recording is to save all HTTP request information in an XML document gt Playing back the transaction STI plays back the recorded transaction according to parameters you specify You can schedule a playback to repeat at different times and from different locations in order to evaluate performance and availability under varying conditions During playback STI can measure response times check for missing or damaged links and scan for specified content Playback Rational Robot Generic Windows Together Rational Robot and Generic Windows enable you to gauge how users might experience a Microsoft Windows application that is used in your environment Like STI Rational Robot and Generic Windows involve record and playback activities gt Recording a transaction You use Rational Robot to record the application actions that you want to investigate For example you might record the actions involved in accessing a proprietary document sharing application Chapter 2 IBM Tivoli Monitoring for Transaction Performance in brief 43 deployed on an application server The steps might include logging on and obtaining the ma
527. u are trying to collect this information If the application you are trying to capture end user experience information for is an enterprise application such as SAP or 3270 then the GenWin component will be placed within the intranet However if you are using the GenWin component to capture end user experiences of your e business infrastructure it may make sense to place the GenWin component on the Internet In general STI is a better choice for capturing Internet based transaction performance information but in some cases it may be unable to get the information that you require A comparison of when and why to use GenWin versus STI is included in 8 1 2 Choosing the right measurement component s on page 229 Where and Why to place STIs The STI Management Agent is used to playback recorded STI scripts Placement of the STI component is dictated by similar considerations as those used to decide where the GenWin component should be placed that is what performance data you are interested in and what application are you monitoring If you are interested in capturing end user experience data as close as possible to that experienced by users from the Internet or from partner organizations you would place the STI component on the Internet or even within your partner organization If this is of less interest for example if you are more interested in generating availability information it may make sense to place the STI endpoint within the DM
528. u selected are displayed in the Object Properties Verification Point panel Figure 9 29 on page 350 Chapter 9 Rational Robot and GenWin 349 Object Properties erification Point a E Oj x Selected object EditBox Type EditBox Index 1 Properties Edit List True RGB 255 255 255 None EE AGB 0 0 0 caretColor Link None caretPosition 0 0 text plain 0 GG AGB 153 153 153 None True False True True False focusA ccelerator uffff focusCycleR oot True I Show verification method Cancel Recapture Help Figure 9 29 Object Properties Verification Point panel Select the property value pair that you want to check in the Verification Point and click on OK If you were recording the simulation the Verification Point will be included in the correct point of the script If you where adding the Verification Point after the script recording the Verification Point will be included where the cursor was in the script Here is how a Verification Point on a Java Label would look like in the script Example 9 1 Example 9 1 Java Label Verification Point Result LabelVP CompareProperties Type Label Name TryIt Logo VP Qbject Properties Wait 2 30 Add timers to the script Rational Robot supports the use of timers in scripts to measure performance but these timers do not support the ARM API standard and cannot be used to
529. ually have multiple Application patterns identified that describe the possible logical components and their interactions For example an Application pattern may have logical components that describe a presentation tier for interacting with users a Web application tier and a back end application tier The Application pattern requires an underpinning of middleware that is expressed as one or more Runtime patterns Runtime patterns define functional nodes that represent middleware functions that must be performed 436 End to End e business Transaction Management Made Easy After a Runtime pattern has been identified the next logical step is to determine the actual product and platform to use for each node Patterns for e business have product mappings that correlate to the Runtime patterns describing actual products that have been used to build an e business solution for this situation Finally guidelines assist you in creating the application using best practices that have been identified through experience For more information on determining how to select each of the layered assets refer to the Patterns for e business Web site at http www ibm com developerWorks patterns Appendix A Patterns for e business 437 438 End to End e business Transaction Management Made Easy Using Rational Robot in the Tivoli Management Agent environment This appendix describes how to use Rational s Robot with a component of Tivoli Monitoring fo
530. uct provides similar management functions for the supported Web and application servers gt Monitoring for IBM HTTP Server gt Monitoring for Microsoft Internet Information Server 154 End to End e business Transaction Management Made Easy gt Monitoring for Sun iPlanet Server gt Monitoring for WebSphere Application Server The following sections provide information on how to set up and customize IBM Tivoli Monitoring for Web Infrastructure to ensure performance and availability of the Tivoli Web Site Analyzer application We will focus on the monitoring for the WebSphere Application Server For the other Web severs refer to the redbook Introducing IBM Tivoli Monitoring for Web Infrastructure SG24 6618 5 1 2 ITM for Web Infrastructure installation In order to install IBM Tivoli Monitoring for Web Infrastructure you need to complete the following steps 1 Plan your management domain 2 Check the prerequisite software and patches 3 Choose the installation options 4 Verify the installation For all these steps refer to the BM Tivoli Monitoring for Web Infrastructure Installation and Setup Guide V5 1 1 GC23 4717 or the redbook Introducing IBM Tivoli Monitoring for Web Infrastructure SG24 6618 These publications contain all the information you need to set up IBM Tivoli Monitoring for Web Infrastructure including the prerequisites needed to install the product As a prerequisite to ensure the availability of TMTP
531. uction to Tivoli Enterprise Data Warehouse SG24 6607 6 5 Uninstalling the TMTP Management Server De installing TMTP is generally straightforward and well covered in the TMTP manuals Uninstallation on the UNIX Linux platform is a little more problematic so we have included some information below to make this easier 6 5 1 The right way to uninstall on UNIX The following steps are required to uninstall TMTP after completing a typical install that is an embedded install The uninstall program for the TMTP Management Server will not uninstall the WebSphere and DB2 installations that were installed by the embedded install that is they will have to be performed using their own native uninstallation procedures 1 Uninstall the TMTP Management Server by running the following command MS_HOME _uninst52 uninstall bin Chapter 6 Keeping the transaction monitoring environment fit 193 2 Uninstall WebSphere by running the following commands by default WebSphere is installed in a subdirectory of the Management Server home directory by the embedded install process MS_HOME WAS bin stopServer sh serverl user userid password password MS_HOME WAS _uninst uninstal 3 Uninstall DB2 a Source the DB2 profile this will set the appropriate environment variables INSTDIR sqllib db2profile INSTDIR is the db2 instance home directory b Drop the administrative instance DB2DIR instance dasdrop c List the db2 instances DB2DIR bi
532. ucture necessitate it it is possible to use the SnF agent in order to connect multiple DMZs This configuration is discussed in Chapter 4 TMTP WTP Version 5 2 installation and deployment on page 85 Where and why to place QoSs Placement of the QoS component is usually dictated by the placement of your Web Application Infrastructure Components The QoS sits in front of your Web Chapter 3 IBM TMTP architecture 79 server as a reverse proxy that forwards requests to the original Web server and relays the results back to the end user s Web browser Several options are possible such as in front of your load balancer behind your load balancer and on the same machine as your Web server There is no hard and fast rule about the placement so placement is dictated by what you want to measure However the QoS component is designed as a sampling tool This means that in a large scale environment where you have a Web Server farm behind load balancers the QoS only needs to be in the path of one of your Web Servers This will generally get a statistically sound sample that can be used to extrapolate the performance of your overall infrastructure Where and why to place the Rational GenWin component The GenWin component allows you to playback recorded transactions against generic Windows applications Placement of the GenWin component will depend on what performance information you are trying to obtain and against what type of application yo
533. ue from the arm_end call is amp end_rc End Sub Scheduling execution of the script You will probably want to run the script at regular intervals throughout the day There is no standard way to schedule this using the ETP component of TMTP but you can do it quite easily using the local scheduler in Windows NT 2000 The NT Task Scheduler was introduced with an NT 4 0 Service Pack or Internet Explorer 5 01 but on Windows 2000 systems it is typically already installed The Windows scheduler can be set up using the command line interface but it is easier and more flexible to use the graphical Task Scheduler utility which you can find in the Windows Control Panel as the Scheduled Tasks icon see Figure B 10 oix File Edt view Favorites Tools Help ej ak gt fey Gsearch Gyrolders CBristory AG GE X wa Ea penon O O oe fa g T w 8 y o F Accessibility AddiRemove Add Remove Administrative Date Time Display Fax Folder Options Control Panel Options Hardware Programs Tools Scheduled Tasks A amp se D fi D E3 Schedules computer tasks to run automatically Fonts Gaming Internet Keyboard LiveUpdate Mail Mouse Network and Options Options Dial up Co Windows Update Windows 2000 Support nu P E 34GB Phone and Power Options Printers RealPlayer Regional SAP Scanners and Modem Options Configuration Cameras Schedules computer tasks to run automatically Schedules computer tasks to
534. uest javax servl 2003 1 0 0 2 484 1 965 org apache jsp _marketSummary _jspService iavax serviet http HttpS yletRequest javax 2003 10 0 Sa 2 476 1 957 com ibm websphere samples trade ejb Trade_Stub getMarketSummayo 20003 10 0 0 7 2 461 1 944 com ibm websphere samples trade ejb EJSRemoteStatelessTradeEJB W0439d68 getM 2003 10 0 2 442 1 928 com ibm websphere samples trade ejb TradeBean getMarketSummary0 2003 10 0 Java Applet Window J2EE methods Figure 8 51 QoS Inspector View from topology correlation with STI and J2EE However so far we have not analyzed how much time is spent in the WebSphere Application Server 5 0 1 application server and database that is the combined total for gt Trade EJB gt Trade session EJB gt Trade JSP pages gt Trade JavaServlet gt Trade JDBC gt Trade database 302 End to End e business Transaction Management Made Easy E IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer File Edit View Favorites Tools Help seek gt O A A Aseh fayravortes Breda SIR SG _ il Address ia http tivdce4 9082 tmtpUL jsp console WcFrameManager jsp Tivoli Monitoring for Transaction Performance User Name administrator Policy trade_2_stockcheck_tivlabO1 gt Configuration Management Agent ibmtiv9 vRep
535. ule definition 0 0002000 cee 248 8 4 5 Playback policy creation 000 000 eee 251 8 4 6 Working with realms 0000 eee 255 8 5 Quality Of SOviCC ie ccs ee mde nan eet nko d ee Lda EE eas 257 8 5 1 QoS Component deployment 00 ccc eee eee 259 8 5 2 Creating discovery policies for QoS 000000 08 261 8 6 The J2EE component 0 ERIRE R eee 278 8 6 1 J2EE component deployment 000 c eee ee eee 278 8 6 2 J2EE component configuration 0c eee eee 282 8 7 Transaction performance reporting 00 eee eee eee 295 8 7 1 Reporting on Trade os ersa rosan PERENE ee 296 8 7 2 Looking at subtransactions ssas sa aeaaea 297 8 7 3 Using topology reports 0 0 nanana arrana 300 8 8 Using TMTP with BEA Weblogic aaua aeaa 307 8 8 1 The Java Pet Store sample application 308 8 8 2 Deploying TMTP components in a Weblogic environment 310 8 8 3 J2EE discovery and listening policies for Weblogic Pet Store 312 8 8 4 Event analysis and online reports for Pet Store 316 Chapter 9 Rational Robot and GenWin 0 05 325 9 1 Introducing Rational Robot 00 cece eee 326 9 1 1 Installing and configuring the Rational Robot 326 9 1 2 Configuring a Rational Project 00002e eee eee 339 Contents v 9 1 3 Recording types GUI and V
536. ult the upload interval is once per hour The Management Agent Management Agents are installed on computers across your environment Based on Java Management Extensions JMX the Management Agent software provides the following functionality gt Listening and playback behaviors A Management Agent can have any or all of the listening and playback components installed The components Chapter 3 IBM TMTP architecture 63 64 associated with a Management Agent run policies at scheduled times The Management Agent sends any events generated during a listening or playback operation to the Management Server where event information is made available in event views and reports ARM engine for data collection A Management Agent uses the ARM API to collect performance data Each of the listening and playback components is instrumented to retrieve the data using ARM standards Policy management When a discovery listening or playback policy is created an agent group is assigned to run the policy You define agent groups to include one or more Management Agents that are equipped to run the same policy For example if you want to monitor the performance of a consumer banking application that runs on several WebSphere application servers each of which is associated with a Management Agent and a J2EE monitoring component you can create an agent group named All J2EE Servers All of the Management Agents in the group can run a J2EE listening p
537. ultiple DMZs is discussed further in Chapter 4 TMTP WTP Version 5 2 installation and deployment on page 85 The SnF agent is comprised of two parts the reverse proxy component which utilizes WebSphere Caching Proxy and the JMX TMTP agent which manages the reverse proxy both of these components will be installed transparently when Chapter 3 IBM TMTP architecture 77 you install the SnF agent The TMTP architecture utilizing a SnF precludes direct connection from the Management Server All endpoint requests are driven to the Management Server via the reverse proxy All communication between the SnF agent and the Management Server is via HTTP HTTPS over a persistent connection Connections to other Management Agents from the SnF agent are not persistent and are optionally SSL The SnF agent performs no authorization of other Management Agents as the TMTP endpoint is considered trusted because registration occurs as part of a user manual process Figure 3 9 shows the SnF Agent communication flows Management Agent Management Server Management Store and Forward WebSphere Server Agent ea a WebSphere Caching Proxy Management Agent Management Agent Management Agent lag lt Requests and responses to and from the Store and Forward Mangement agent and other Management Agents JMX commands from the Management Server to the Management
538. up starts creating the TMTP database and the database tables and installs the TMTP application itself on the WebSphere Application Server Figure 4 64 on page 150 Chapter 4 TMTP WTP Version 5 2 installation and deployment 149 Install the Management Server Canfiguring the management server Cancel InstallShield Figure 4 64 Configuration of the Management Server gt Once the installation is finished Figure 4 65 on page 151 the WebSphere Application Server must be restarted because the WebSphere Application Server security will now be applied To stop and start the WebSphere Application Server we use the following commands These scripts are located in the was_installation_directory bin In our case it is opt IBM Tivoli MS WAS bin stopServer sh serverl user root password password startServer sh serverl user root password password 150 End to End e business Transaction Management Made Easy Tivoli software Fx Figure 4 65 The finished Management Server installation gt Once the WebSphere Application Server is restarted we log on to the TMTP server by typing the following URL into our browser http ipaddress 9082 tmtpUI Chapter 4 TMTP WTP Version 5 2 installation and deployment 151 152 End to End e business Transaction Management Made Easy Interfaces to other management tools Every component in the e business infrastructure is a potential show stopper bottleneck or s
539. uplicate rows for those columns SQ LSTATE 23505 insert into twg cormpgttr compattr_id comp_id AttrTyp_Cd Compattr_Strt_DtTm CompAttr_End_DtTm CompaAttr_Val select 0 as compattr_id c1 comp_id as comp_id BVWM_RT_CDW_ID as AttrTyp_Cd current timestamp current timezone as Compattr_Strt_DtTm 9999 01 01 00 00 00 000000 as Compattr_End_DtTm char r comp_target_id as Compattr_Val from session tmp2_cdw_tind c1 session tmp2_cdw_tnd c2 WWG CUR_COMPRELN r session tmp2_tend_root_id ca1 where ca1 comp_id c1 comp_id and cal last_value is null and integer c1 tend_rt_idj c2 tend_id and 2 comp_id r comp_source_id and r relntyp_cd INSTOF group by 1 comp_id r comp_target_id RC 7356 RC2 8410 Close Figure 6 4 Duplicate row at the TWH_CDW Solution The cleancdw sqI script see Example 6 2 will clean the BWM source information if we need to clean TMTP database information from TWH_CDW Example 6 2 cleancdw sql CONNECT to twh_cdw Delete from TWG compattr Delete from TWG compreln Delete from TWG msmt Delete from TWG comp Delete from bwm comp_name_long Delete from bwm comp_attr_long UPDATE TWG Extract_control SET EXTCTL_FROM_INTSEQ 1 UPDATE TWG Extract_control SET EXTCTL_TO_INTSEQ 1 We then need to run the resetsequences sqlI script see Example 6 3 to reset the TMTP ETL1 process after running the cleancdw sq I script Example 6 3 resetsequences sq CONNECT to twh_cdw UPDATE TWG Extract_control SET EX
540. urce AMY_TWH_MART_Source O Views BWM_TWH_CDW_Source BWM_TWH_MART_Source CDW_TWH_CDW_Source S Warehouse Targets a EB AMX_TWH_CDW_Target m EA AMY_TWH_MART_Target ER AMY_TWH_MD_Target a EA ANM_TWH_CDW _Target EA ANM_TWH_MART_Target ER ANM_TWH_MD_Target ER BWM_TWH_CDW_Target c ER BWM_TWH_MART_Target fF BR AAM DAH MD Tarnet Figure 10 18 Warehouse source table names immediately after installation D H E Customizing your TEDW environment After installation of the warehouse enablement pack use the procedures described in the Tivoli Enterprise Data Warehouse Installing and Configuring Guide Version 1 1 GC32 0744 manual to use the Data Warehouse Center to perform the following configuration tasks for data sources and targets 1 Make sure the control database is set to TWH_MD a Specify the properties for the BWM_TMTP_DATA_SOURCE data source ODBC Source b Set Data Source Name DSN to the name of the ODBC connection for the BWM_TMTP_DATA_SOURCE The default value is DM c Set the User ID field to the Instance name for the configuration repository The default value is db2admin d Set the Password field to the password used to access the BWM_TMTP_DATA_SOURCE 2 Specify the properties for the target BWM_TWH_CDW_SOURCE a Inthe User ID field type the user ID used to access the Tivoli Enterprise Data Warehouse central data warehouse database The default value is db2admin Chapter 10 Historical re
541. ures is detailed in Figure 8 1 on page 236 A new feature of the WebSphere Application Server 5 0 persistence manager architecture for performance is various optimizations to minimize the number of database roundtrips by reading ahead and caching object structures in order to avoid round trips Entity bean run time data access characteristics can be configured to improve database access efficiency includes access type concurrency control read ahead collection scope and so on WebSphere provides critical support for extended features in EJB QL such as aggregate functions min max sum and so on The extended addition also provides dynamic query features To see the Trade application component details as shown in Figure 8 2 on page 238 log in to https hostname 9090 admin and click Application Enterprise Applications Trade Chapter 8 Measuring e business transaction response times 237 44 WebSphere Administrative Console Microsoft Internet Explorer File Edit view Favorites Tools Help Ea if WebSphere Application Server Administrative Console o Version 5 x Home Save Preferences Logout Help afal User ID adri i icati leer ID admin Enterprise Applications ibmtiv9 A list of installed applications A single application can be deployed onto multiple servers B E Server
542. usiness environment In addition some of these are placed in a dedicated network segment the demilitarized zone DMZ which from the point of view of the e business owner is fully controlled and in which client requests are received by well known secure systems and passed on to the enterprise network also known as the intranet This architecture is used to increase security by avoiding transactions from unknown machines to reach the enterprise network thereby minimizing the exposure of enterprise data and the risk of hacking 24 End to End e business Transaction Management Made Easy To facilitate secure communication between the DMZ and the intranet a set of Web servers is usually implemented and identification authentication and authorization are typically handled by an LDAP Server The infrastructure depicted in Figure 1 8 contains all components required to implement a secure e business solution allowing anyone from anywhere to access and do business with the enterprise B Browser Web Server _ Load Balancer Web Server Browser a Application Server i Business Figure 1 8 Logical view of an e business solution Me For more information on e business architectures please refer to the redbook Patterns for e busi
543. ust tivlab austin ibm com STI 2003 08 25 13 23 260 156 2 076 1 762 3 406 wat alpho discvg1 E morgul tiviab austin ibm com QOS 2003 08 25 15 31 14 0 248 goes above 2 sec 2 885 0 232 3 214 E ibuwin02 intevent1 10 E F ibuwin02 tiviab austin ibm com QOS 2003 08 25 17 12 58 0 187 Page 1 Refresh Rate Minutes 5 Filter Starts With Event Transaction Apply Alt a Status Harmless B Unknown 4 amp Minor amp Warning Critical Fatal Figure 2 3 Big Board View From the Big Board View the administrator can see that the J2EE policy called quick_listen had a violation at 16 27 The user can also tell the policy hada threshold of goes above 5 seconds which was violated as the value was 6 03 seconds 44 End to End e business Transaction Management Made Easy The administrator can now click on the topology icon for that policy and load the most recent topology that TMTP has data for see Figure 2 4 All Times are in Seconds Bsr oora 2H quickbeamtiviab austin ibm com J2E E WebS phen Serviet SABE Timer St r 4 http 7 q uickbea m 3 08 O S ervietTesv doGet ii 4 303 4 293 Figure 2 4 Topology view indicating problem Since by default topologies are filtered to exclude any nodes that are slower than one second this is configurable the default view is to show the latest aggregated data for s
544. ustry strength monitoring functions for J2EE applications hosted by WebSphere Application Server or BEA Weblogic In addition the architecture of Web Transaction Monitoring WTP has been redesigned to provide for even easier deployment increased scalability and better performance Also the reporting functions has been enhanced by the addition of ETL2s for the Tivoli Enterprise Date Warehouse This new version of IBM Tivoli Monitoring for Transaction Performance provides all the capabilities of previous versions of IBM Tivoli Monitoring for Transaction Performance including the Enterprise Transaction Performance ETP functions used to add transaction performance monitoring capabilities to the Tivoli Management Environment with the exception of reporting through Tivoli Decision Support The reporting functions have been migrated to the Tivoli Enterprise Date Warehouse environment Because the ETP functions has been documented in detail in the redbook Unveil Your e business Transaction Performance with IBM TMTP 5 1 SG24 6912 this publication is devoted to the Web Transaction Performance functions of IBM Tivoli Monitoring for Transaction Performance Version 5 2 and in particular the J2EE monitoring capabilities This information in this redbook is organized in three major parts each targeted at specific audiences Part 1 Business value of end to end transaction monitoring on page 1 provides a general overview of IBM Tivoli
545. vdces its austin ibm com 9082 tmtpUL jsp console WcFra Go HBBak gt amp A Qsearch GaFavortes meda D SEI E V BQ Tivoli Monitoring for Transaction Performance User Name administrator My Work vConfiguration Work with Discovery Policies Work with Listening Policies eT ERI Name Work with Playback Policies cae i trade 2 stock check Work with Schedules onfigure g Description Work with Agent Groups Configure Q ey k check Trade transaction Work with Transaction Recordings ge Work with Realms RSS SIG Sent ta Agents at next interval b Reports a Choose Schedule C Send to Agents now b System Administration gt Downloads Z Choose Agent Group lt Back Alt b Next Alttn gt Finish Alt Cancel Alt c E Figure 8 15 Assign name to STI Playback Policy In addition you can decide whether or not to distribute the STI Playback Policy to the Management Agents that are member s of the selected group s immediately or you prefer to postpone the distribution to the next scheduled regular distribution Click Finish to complete the creation of the new STI Playback Policy 8 4 6 Working with realms Realms are used to specify settings for a password protected area of your Web site that is accessed by an STI Playback Policy If a recorded transaction passes through a password protected realm realm settings ensure that STI is able to access the protected pages during playback of the t
546. vironments may have multiple levels of DMZ in which case chaining Store and Forward agents would have been a better option Quality of Service Management Agent We have chosen to use only one and place it behind our load balance yet in front of one of the back end Web Servers We considered that this solution would give us a good enough statistical sample to monitor end user experience time Another option which we considered seriously was placement of a Management Agent and Quality of Service endpoint on each of our Web Servers This would have given us the capability to sample 100 of our traffic We discarded this option as we felt that we did not need this level of detail to satisfy our requirements Synthetic Transaction Investigator Management Agent We chose to place one of these on the Internet as this will allow us to closely simulate a real end user accessing our e business transactions We also plan to place additional Synthetic Transaction Investigator Management Agents both in the DMZ and intranet as well as on the Internet as specific e business transaction monitoring requirements arise Rational Robot GenWin Management Agent Again we chose to place one of these on the Internet in order to allow us to test end user response times of our e business infrastructure where it uses Java applets or other content which is not supported by the STI Management Agent Later plans are to deploy Rational Robot GenWin Management Agents within
547. w to report on aggregated maximum data collected from TWH_CDW cleancdw sql The SQL script used to clean ITMTP source data from TWH_CDW resetsequences sql The SQL script used to reset the ITMTP source ETL process End to End e business Transaction Management Made Easy Abbreviations and acronyms ACF AIX AMI AMS API APM ARM ASP BAROC BDT BOC CA CGI CICS CIM CLI CMP CMS CPU CTS DB2 DBCS DES Adapter Configuration Facility Advanced Interactive Executive Application Management Interface Application Management Specifications Application Programming Interface Application Performance Management Application Response Measurement Active Server Pages Basic Recorder of Objects in C Bulk Data Transfer Business Objects Container Certificate Authority Common Gateway Interface Customer Information Control System Common Management Information Command Line Interface Container Managed Persistence Cryptographic Message Syntax Central Processing Unit Compatibility Testing Standard Database 2 Double byte Character Set Data Encryption Standard Copyright IBM Corp 2003 All rights reserved DLL DM DMTF DNS DOM DSN DTD EAA EJB EPP ERP ETP GEM GMT GSK GUI HTML HTTP HTTPS IBM IDEA IIOP IIS IMAP IOM ISAPI Dynamic Link Library Tivoli Distributed Monitoring Distributed Management Task Force Domain Name Service Docume
548. w when you put this in production MsgBox The return value from the arm_init call is amp appl_handle getid_handle arm_getid app l_handle Notepad Windows 0 0 0 Remove line below when you put this in production MsgBox The return value from the arm_getid call is amp getid_handle Start clock Appendix B Using Rational Robot in the Tivoli Management Agent environment 451 start_handle arm_start getid_handle 0 0 0 Remove line below when you put this in production MsgBox The return value from the arm_start call is amp start_handle The arm_init and arm_getid calls define the application and transaction name The application name used must match what is set up for collection in TMTP The arm_start call is used to start the response time clock just before the transaction starts 4 Finally after the business transaction steps we added the following Stop clock stop_rc arm_stop start_handle 0 0 0 0 Remove line below when you put this in production MsgBox The return value from the arm_stop call is amp stop_rc Make ARM API cleanup call end_rc arm_end app _handle 0 0 0 Remove line below when you put this in production MsgBox The return value from the arm_end call is amp end_rc The arm_stop call is made after the transaction completes The arm_end call is used to clean up the ARM environment at the end of the script For the purposes of testing we used MsgBox statements to
549. window Then select the Deploy Generic Windows Component from the drop down box and press Go This will display the Deploy Components and or Monitoring Component window see Figure 9 38 on page 367 In this window you must enter details about the Rational Robot Project in which your playback scripts are going to be stored End to End e business Transaction Management Made Easy f IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer 4 i loj x l it iS File Edit View Favorites Tools Help Address E http tivdee4 9082 tmtpUL jsp console WeFrame eco EA Tivoli Monitoring for Transaction Performance User Name Administrator Configuration Work with Discovery P Work with Listening Pc Work with Playback Pi Work with Schedules Work with Agent Group Work with Transaction Work with Realms vReports View Big Board View General Reports View Component Even vSystem Administratio Work with Agents Configure System Ever Component Manageme Configure User Setting Work with Event Respe View System Events View Log Files View Management Ser gt Downloads Deploy Components and or Monitoring Component Management Agent Name tivdce4 itsc austin ibm com Choose Component or Monitoring Component Deploy Generic Windows Component Go Project User ID Admin Project Password Scam Project Name GenericWindows After deployment compl
550. y 2 Add your URI filters and provide sampling information Click Next to proceed to choose a schedule in the Work with Schedules dialog shown in Figure 8 24 on page 269 End to End e business Transaction Management Made Easy oli Monitoring for Transaction Performance Microsoft Internet Explore ox File Edit view Favorites Tools Help Address http tivdce4 itsc austin ibm com 9082 tmtpUL isp console WcFrameManager jsp Tivoli Monitoring for Transaction Performance User Name administrator Configuration Work with Schedules Work with Discovery Policies Work with Listening Policies Work with Playback Policies Work with Schedules Work with Agent Groups Work with Transaction Recordings Work with Realms b Reports b System Administration gt Downloads Create New Alt w Schedule Table D Please make a selection z Go Alt g Name Start Time Stop Time Run the policy petstore_j2ee_dis Start as soon as possible Run forever trade_dis_sch Star as soon as possible Run forever Page 1 lt Back Alt b Next Alt n gt Finish Ait Cancel Ait c aft Figure 8 24 Choose schedule for QoS 3 Select a schedule or create a new one that will suit your needs Click Next to continue with Agent Group selection as shown in Figure 8 25 on page 270 Chapter 8 Measuring e business transaction response times 269 E IBM Tivo
551. y a user for the Vv A fhome db2inst1 Figure 4 60 User specification for the DB2 instance gt After the DB2 user is specified the Management Server installation starts The setup wizard copies the Management Server installation files to the specified folder which is opt IBM Tivoli MS in this scenario see Figure 4 61 on page 147 146 End to End e business Transaction Management Made Easy Tivoli software npk ngi y A Figure 4 61 Management Server installation progress window gt Once the Management Server files are copied the setup starts with the silent installation of the DB2 Version 8 1 server and the creation of the specified DB2 instance see Figure 4 62 on page 148 Chapter 4 TMTP WTP Version 5 2 installation and deployment 147 Tivoli software _ Figure 4 62 DB2 silent installation window gt When the DB2 is installed correctly the installation wizard installs the WebSphere Application Server Version 5 0 and the WebSphere Application Server FixPack 1 see Figure 4 63 on page 149 148 End to End e business Transaction Management Made Easy Install the Management Server Installing WebSphere Application Server Tivoli software t Fx ig iY Percent Complete 90 Cancel Io 2 InstallShield Figure 4 63 WebSphere Application Server silent installation gt If both the DB2 Version 8 1 server and the WebSphere Application Server successfully install the set
552. yback Engine ARMed Third Party Client Applications Capture EPP Figure 3 2 Enterprise Transaction Performance architecture To initiate transaction performance monitoring a MarProfile which contains all the specifics of the transactions to be monitored is defined in the scope of the Tivoli Management Framework and distributed to a Tivoli endpoint for execution Based on the settings in the MarProfile data is collected locally at the endpoint and may be aggregated to provide minimum maximum and average values over a preset period of time Data related to specific runs of the transactions instance data and aggregated data may be forwarded to a central database which may be used as the source for report generation through Tivoli Decision Support and as data provider for other applications through Tivoli Enterprise Date Warehouse Online surveillance is facilitated through a Web based console on which current data at the endpoint and historical data from the database may be viewed In addition two sets of monitors a monitoring collection for Tivoli Distributed Monitoring 3 x and a resource model for IBM Tivoli Monitoring 5 1 1 are provided to enable generation of alerts to TEC and online surveillance through the IBM Tivoli Monitor Web Health Console Note that both monitors are based on the aggregated data collected by the ARM receiver running at the endpoint
553. ystem Administration b Downloads Violation Response Level Recovery Response Level Warming a Harmless z Event Response Event Response ChangeBufferSize ChangeBufferSize Apply Alt a lt Back Alt b Next Alt n gt Finish t Cancel Alt c Figure 8 62 Automatic threshold setting for Pet Store End to End e business Transaction Management Made Easy Quality of Service listening policy for Pet Store To define a QoS listening policy for the Pet Store application pestore_qos_lis we used the following transaction filter http tivlab01 itsc austin ibm com 80 petstore signon_welcome screen Settings for the Back End Service Time threshold are shown in Figure 8 63 Z IBM Tivoli Monitoring for Transaction Performance Microsoft Internet Explorer Tivoli Monitoring for Transaction Performance User Name administrator Configuration ae with Discovery Policies Create Listening Policy contigs See urate Work with Listening Policies Aas Ae Performance Threshold Type Work with Playback Policies Back End Senice Tiel Work with Schedules Work with Agent Groups Condition Threshold Work with Transaction Recording Above E 0 013 Seconds gt ete Realms Violation Response Level Recovery Response Level CI se G 7 b System Administration SURES eels Waring gt Harmless gt Downloads Z Assign Name Event Response Event Response ChangeBufferSize ChangeBufferSize Apply A

End-to-End e-business Transaction Management

Contents

Download Pdf Manuals

Related Search

Related Contents