ITCAM for Transactions Cognos Report Best Practices

Transcription

1 IBM Tivoli Composite Application for Transactions Cognos Report Best Practices April, 2013 ITCAM for Transactions Cognos Report Best Practices Document version [1.0] Xiao Ming Hu ITCAM for Transactions SVT Team i

2 IBM Tivoli CAM for Transactions Cognos Report Best Practices [Copyright notice instructions: Include the legally required IBM copyright text and year of publication only once at the bottom of the back of the title page. The first date in the copyright notice is the earliest year in which at least 5% of the material was originally published. The second date is the year in which the current edition was published. Separate the two dates with a comma and a space. If the material is all new, use only the current year.] Copyright International Business Machines Corporation 2013 US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ii

3 IBM Tivoli CAM for Transactions Cognos Report Best Practices CONTENTS Contents... iii List of Figures... v List of Tables... vii Revision History... viii 1 Introduction Overview of Tivoli Common Reporting Technical Overview Overview of Transaction Tivoli Common Reporting Reports Technical Overview Install Transactions Cognos Reports Importing the Cognos Report Package into Tivoli Common Reporting Importing by using Tivoli Common Reporting import wizard Importing by using the trcmd import command Configure the data source for ITCAM for Transactions Report Run Database Scripts Create TRAM tables Pre-create all warehouse tables Enable Historical Data Collection Enable Historical data collection manually iii

4 IBM Tivoli CAM for Transactions Cognos Report Best Practices 4.2 Enable Historical data collection using scripts Generate Transactions Data for Collection Customizing the Web Response Time agent Customizing the Robotic Response Time agent Customizing the Internet Service Monitoring agent References... ix Notices... x Trademarks... xii iv

5 IBM Tivoli Composite Application for Transactions Cognos Report Best Practices April, 2013 LIST OF FIGURES Figure 1: Tivoli Common Reporting components overview... 2 Figure 2: Transactions Reports architecture... 3 Figure 3: Transactions Cognos compressed packages... 5 Figure 4: Import wizard entrance... 5 Figure 5: Select a deployment archive... 6 Figure 6: Select the public folders content... 7 Figure 7: Verify the DB2 connection... 8 Figure 8: Create a new data source... 9 Figure 9: Specify the connection type... 9 Figure 10: Specify the DB2 connection string... 9 Figure 11: Specify the DB2 connection credentials Figure 12: Test the connection Figure 13: Verify five TRAM tables Figure 14: History collection configuration window Figure 15: Create new collection settings Figure 16: View the new created collection Figure 17: Start collection on specified agent Figure 18: Set summarization and pruning parameters Figure 19: HistoricalDataEnable.sh usage Figure 20: Create a new WRT application Figure 21: Create transaction for application Figure 22: Transaction filter Figure 23: Create a new WRT profile Figure 24: Add applications and transactions into the profile Figure 25: Deploy the profile for monitoring Figure 26: Enable session tracking Figure 27: Create or edit the session keys Figure 28: Enable user tracking v

6 IBM Tivoli CAM for Transactions Cognos Report Best Practices Figure 29: Create or edit user identity information Figure 30: Enable anonymous users tracking Figure 31: Create a client group Figure 32: Create a filter for a client group Figure 33: View the client group on TEP Figure 34: Verify the user information tracking Figure 35: Select a user for Transactions Cognos reports Figure 36: RPT workbench Figure 37: Upload recorded scripts to Application Management Console Figure 38: Select the SimpleTrade application Figure 39: Verify the uploaded scripts in Tivoli Enterprise Portal Figure 40: Create a profile for RRT Figure 41: Add a transaction into the RRT profile Figure 42: Distribute the RRT profile to a RRT agent Figure 43: Verify the playback status on Tivoli Enterprise Portal Figure 44: Create a HTTP profile for Internet Service Monitoring Figure 45: Input the profile name Figure 46: Add monitor type to profile Figure 47: Customize the HTTP profile Figure 48: Deploy the profile to an ISM agent Figure 49: Change SLC to simulate bad HTTP services Figure 50: Verify the profile in Tivoli Enterprise Portal Figure 51: Internet Service Availability report Figure 52: View the result of Internet Service Availability vi

7 IBM Tivoli Composite Application for Transactions Cognos Report Best Practices April, 2013 LIST OF TABLES Table 1: Software components in Tivoli Common Reporting Table 2: Products installed on each virtual machine... 4 Table 3: Minimum tables for ITCAM for Transactions reports vii

8 IBM Tivoli Composite Application for Transactions Cognos Report Best Practices April, 2013 REVISION HISTORY Date Version Revised By Comments 03/05/ Xiao Ming Hu Initial version 04/16/ Francis DeRespinis Edit the whole paper 04/26/ Xiao Ming Hu Add list of figures, tables, references 04/27/ Francis DeRespinis The second review 04/27/ Xiao Ming Hu Revise this paper based on Francis comments Document Authors: Min He/China/IBM, Jia Yi JY He/China/IBM, Yan Jiao Mao/China/IBM and Xiao Ming M Hu/China/IBM Acknowledgements: The authors would like to acknowledge the following people for their invaluable contributions to the content of this paper. Name Francis DeRespinis/Raleigh/IBM Denny O'Brien/Raleigh/IBM Shan Gao/China/IBM Ren Fu Ma/China/IBM Role Organization Technical editor and co-lead, IBM Style and Word Usage Council Manager, Service Management Connect and ID Enablement Manager, ITCAM for Transactions SVT Leader, ITCAM for Transactions SVT viii

9 Best Practices for IBM Tivoli CAM for Transactions Tivoli Common Reporting Reports 1 Introduction The ITCAM for Transaction Tivoli Common Reporting Cognos reports are historical reports, reporting against raw and summarized data that is collected in Tivoli Data Warehouse with any supported version of IBM Tivoli Monitoring. These reports run against ITCAM for Transaction agents, including Application Management Console, Client Response Time, Web Response Time, Robotic Response Time, Internet Service Monitoring, and Transaction Tracking. This paper is for persons who plan, configure, implement, or administer Tivoli Common Reporting Cognos reports. The examples in this paper are generally only focused on the ITCAM for Transaction Tivoli Common Reporting reports. This paper introduces the best practices on the installation and configuration of ITCAM for Transaction Tivoli Common Reporting Cognos reports, and also includes how to customize ITCAM for Transaction agents to generate historical data that is required by Transaction Tivoli Common Reporting Cognos reports. The environment described in this paper uses the following versions: IBM Tivoli Common Reporting Version IBM Tivoli Monitoring Version Fix Pack 1 IBM Tivoli Composite Application Manager for Transaction Version IBM Tivoli Composite Application Manager for Transaction Tivoli Common Reporting Reports IBM Cognos 8 Version 4 Business Intelligence IBM DB2 Enterprise Edition Version Overview of Tivoli Common Reporting Tivoli Common Reporting provides an integrated reporting solution for the products in the Tivoli portfolio. You can link multiple reports across various Tivoli products to simplify the report navigation and to accelerate access to key reporting information. Tivoli Common Reporting V2.1.1 is based on Cognos 8 Business Intelligence Reporting version 8.4.1, Fix Pack 3. The following Cognos components are available with Tivoli Common Reporting: Framework Manager: A modeling tool that you use to create data models Query Studio: A reporting tool for creating simple queries and reports Report Studio: A web-based tool for creating sophisticated reports against multiple databases Cognos Connection: An application than you use to see all your reports and manage them Technical Overview IBM Tivoli Common Reporting consists of data stores, reporting engines, and their corresponding web user interfaces displayed in Tivoli Integrated Portal, and a commandline interface. Tivoli Common Reporting provides a flexible structure that can be adapted for load balancing. To simplify the process of setting the Reporting environment and focus on ITCAM for Tivoli Common Reporting reports, in this paper all Tivoli Common Reporting components are installed on a single computer as shown in Figure 1. 1

10 Figure 1: Tivoli Common Reporting components overview Table 1: Software components in Tivoli Common Reporting Core components Tivoli Common Reporting Server Cognos based Tivoli Common Reporting engine Cognos Content Store Tivoli Integrated Portal web user interface Cognos gateway Description The application server is a J2EE lightweight implementation of the embedded WebSphere Application Server. It provides a single sign-on service based on the WebSphere security module and Lightweight Third-Party Authentication (LTPA). The dispatcher is the entry point for IBM Cognos 8 service requests sent by a web server gateway or other software. The dispatcher handles the routing requests and balances the load of user requests to the various IBM Cognos 8 services. A database that contains the data that IBM Cognos 8 needs to operate, such as report specifications, published models, and the packages that contain them; connection information for data sources; information about the external namespace, and the Cognos namespace itself; and information about scheduling and bursting reports. Based on Tivoli Integrated Portal, the following web user interface is available for the reporting solution: Common Reporting: A web portal for IBM Cognos 8 and a component that interacts with the Cognos Content Store. It is a frontend to publish, find, manage, organize, and view an organization's reports A portal enabling communication between Tivoli Common Reporting Server and the Cognos based Tivoli Common Reporting engine. 2

11 1.2 Overview of Transaction Tivoli Common Reporting Reports ITCAM for Transaction V Tivoli Common Reporting Cognos Reports are historical reports, reporting against raw and summarized data collected in Tivoli Data Warehouse. These reports are run against ITCAM for Transaction agents including AMC, WRT, CRT, RRT, ISM, and Transaction Reports (TO). ITCAM for Transaction V does not create reports against all the tables in the Data Warehouse. It creates a few key reports, but exports almost all the tables in a data model so that the customer can create reports on them if needed. The databases that are supported include those that are supported by Tivoli Data Warehouse: DB2 Oracle MS SQL The reports can be administered and run on IBM Tivoli Common Reporting Version 2.1 and later. The data from the Tivoli Data Warehouse will be displayed in Tivoli Integrated Portal using Cognos/Tivoli Common Reporting reporting Technical Overview ITCAM for Transaction reports must be deployed in a Tivoli Monitoring environment in which Tivoli Common Reporting and Tivoli Data Warehouse are installed. ITCAM for Transaction Reporting is installed on Tivoli Common Reporting. The user interface for Tivoli Common Reporting is Tivoli Integrated Portal. Create and view reports in the Tivoli Integrated Portal. The Tivoli Data Warehouse is the data source for ITCAM for Transaction Reports. When historical data collection is enabled for ITCAM for Transaction agents, collected data is stored in Tivoli Data Warehouse. The architecture overview is shown in the following figure. TCR server ITM Environment ITCAM for Transaction Reports ITCAM for Transaction Agents(Historical data enabled) Tivoli Integrated Portal Common Reporting AMC CRT RRT WRT TO ISM Tivoli Common Reporting Console TEMS Cognos-based TCR engine Warehous Proxy Agent Summarization and Pruning Agent TDW TDW Figure 2: Transactions Reports architecture 3

12 2 Install Transactions Cognos Reports ITCAM for Transactions V Cognos Report only provides a manual installation to install Cognos reports onto a Tivoli Common Reporting server. In this example, four virtual machines with the guest operating system of SUSE 11 are used to setup the environment for ITCAM for Transaction Tivoli Common Reporting Cognos Reports. On each virtual machine, products required by ITCAM for Transaction Cognos Reports are pre-installed as shown in Table 2: Table 2: Products installed on each virtual machine Virtual Machine Hostname/IP Preinstalled Product VM1 sysitmsles.poc.ibm.com - IBM Tivoli Monitoring Version Fix Pack AMC Agent - CRT Agent - ISM Agent - Transaction Report - Tivoli Data Warehouse (DB2 ESE V9.7) - WP and S&P Agent VM2 sysagentlesssles.poc.ibm.com WRT Agent VM3 sysportalsles.poc.ibm.com - Tivoli Common Reporting Version VM sysappsles.poc.ibm.com DB2 Client V9.7 - Simple J2EE application deployed on WAS application server - WebSphere Application Server Version Importing the Cognos Report Package into Tivoli Common Reporting You can import the ITCAM for Transaction Cognos report package using the Tivoli Common Reporting import wizard, or you can use the trcmd import command to import the report package. The ITCAM for Transactions Reports are provided in compressed file packages named ITCAMT _Tivoli Common Reporting_Cognos for DB2 and Oracle databases in zip or tar.gz files and ITCAMT _Tivoli Common Reporting_Cognos_MSSQL for Microsoft SQL databases in.zip or tar.gz file, located in the integration/tcr/cognos folder on the installation media Importing by using Tivoli Common Reporting import wizard 1. Unpack the ITCAMT _Tivoli Common Reporting_Cognos.tar.gz file on VM3 (Tivoli Common Reporting server), you can see two additional compressed packages: 4

13 Figure 3: Transactions Cognos compressed packages 2. Copy those two packages into the directory: /opt/ibm/tivoli/tipv2components/tivoli Common ReportingComponent/cognos/deployment 3. Log onto Tivoli Integrated Portal console by accessing with a valid ID and password. 4. Expand the Reporting node and click Common Reporting in the left navigation pane. 5. Under Work with reports, click Launch -> Administration. 6. In Configuration tab, select Content Administration. 7. Click the New Import icon. Figure 4: Import wizard entrance 5

14 8. The ITCAM for Transactions packages should be displayed, select the ITCAM for Transactions (Analysis) package to be imported, and click Next. Figure 5: Select a deployment archive 9. Accept the defaults and click Next. 10. Select the check box next to the public folders content name and click Next. 6

15 Figure 6: Select the public folders content 11. Accept the defaults for general options and click Next. 12. Confirm the summary information and click Next to perform the import operation. 13. Select the Save and run once option and click Finish. 14. Select now and Click Run to run the import. 15. Repeat these steps to import the ITCAM for Transactions (Query) package. 16. Verify that the packages are imported successfully by viewing the imported packages in the Public Folders listing Importing by using the trcmd import command You can use the trcmd import command to import the ITCAM for Transactions reports packages into Tivoli Common Reporting. 1. Locate the trcmd import command in the following directory: /opt/ibm/tivoli/tipv2components/tivoli Common ReportingComponent/bin 2. Run the following commands: 7

16 ./trcmd.sh import bulk ${YourPath}/ITCAM\ for\ Transactions\ \(Analysis\).zip -user tipadmin -password xxxxxx./trcmd.sh import bulk ${YourPath}/ITCAM\ for\ Transactions\ \(Query\).zip -user tipadmin -password xxxxxx 2.2 Configure the data source for ITCAM for Transactions Report The data store for Tivoli Common Reporting is Tivoli Data Warehouse. The Tivoli Common Reporting uses ODBC to connect to the database. In this paper, we use a DB2 database as a data store that is running on a different server (VM1) than Cognos (VM3). Thus, you need to have a native database client installed and have a local database alias created. 1. Configure the system library path to point to the database client library by modifying the environment variable in the starttivoli Common ReportingServer.sh script by inserting the following line before starting WebSphere Application Server: cp starttivoli Common Reportingserver.sh starttivoli Common Reportingserver.sh.org export LD_LIBRARY_PATH=/opt/ibm/db2/V9.7/lib32:$LD_LIBRARY_PATH 2. Switch the shell user to the user of the DB2 instance administrator on the Tivoli Common Reporting server: su db2inst1 3. Catalog the remote warehouse database by issuing the following DB2 commands: db2 catalog tcpip node ITMNODE remote sysitmsles.poc.ibm.com server db2 catalog database WAREHOUS as ITMDB at node ITMNODE authentication server 4. Verify the connection between the DB2 client and server by issuing the following command: Db2 connect to ITMDB user itmuser password Smartp0c Figure 7: Verify the DB2 connection 5. From the Common Reporting portlet, go to the Launch list and select Administration. 6. In the Administration window, select the Configuration tab and click New Data Source icon. 8

17 Figure 8: Create a new data source 7. Enter TDW for the data source name. Note: You can only use TDW as the data source name here. 8. Select DB2 as the type of the data source and click Next. Figure 9: Specify the connection type 9. Specify the warehouse database name or local alias name. Figure 10: Specify the DB2 connection string 10. Specify the user ID and password for Signons. 9

18 Figure 11: Specify the DB2 connection credentials 11. Click the Test the connection, make sure that the status is Succeeded. Figure 12: Test the connection 12. Click Finish to complete the creation of the data source and that a data source entry named Tivoli Data Warehouse is listed in the Data Source Connections. 3 Run Database Scripts ITCAM for Transactions V Cognos Report provides a set of database scripts to create Tivoli Reporting and Analytics Mode, warehouse tables and indexes for ITCAM for Transactions agents. Scripts for TRAM tables are located in the following directory: ${Image_Location}/schema/db2 Scripts for warehouse tables and indexes are located in this directory: ${Image_Location}/utilities/db2 3.1 Create TRAM tables Tivoli Reporting and Analytics Model (TRAM) is a set of shared tables required to create ad hoc reports and run Tivoli Common Reporting reports. Therefore you must create those tables for ITCAM for Transaction Cognos Report; otherwise the reports will not show any data. 10

19 In some other Tivoli Report products, for example, ITCAM for Application Diagnostics Cognos Reports provide a Tivoli Reports installer which creates TRAM tables and populate the TIME_DIMENSION table. In ITCAM for Transaction V Cognos Report does not have the installer to create TRAM tables, you must create them by running some scripts provided with the product. 1. Make sure TRAM tables are not in your data warehouse. su db2inst db2 connect to ITMDB user db2inst1 using Smartp0c db2 list tables for schema IBM_TRAM 2. If the output of the command returns the following results there are other Tivoli products already installed. Running the scripts will not replace those existing tables. Figure 13: Verify five TRAM tables 3. If no records are returned, you must run the database scripts with administrative privilege. su db2inst db2 connect to ITMDB user db2inst1 using Smartp0c 4. Create IBM_TRAM schema and TRAM tables by running the following command: db2 tf ${Image_Location}/schema/db2/create_schema_IBM_TRAM.db2 5. Five tables are created with a user schema of IBM_TRAM. 6. Create the stored procedure for generating the time dimension: db2 td@ -vf ${Image_Location}/schema/db2 gen_time_dim_granularity_min.db2 7. Populate the TIME_DIMENSION table: db2 "call IBM_TRAM.CREATE_TIME_DIMENSION(' ',' ', 5)" Note: The timestamp of historical data that you want Tivoli Common Reporting report to display should be in the period or data cannot be able to be displayed by reports. You can modify the population of the TIME_DIMENSION table by clearing out the record and re-populating. Example: su db2inst1; vi null.data; db2 "import from NULL.DAT of del replace into IBM_TRAM.TIME_DIMENSION"; db2 "call IBM_TRAM.CREATE_TIME_DIMENSION(' ',' ', 5)" 11

20 8. If you encounter an error of SQL0964C The transaction log for the database is full, you must increase the size of the log file by running the following command: db2 UPDATE DB CFG USING LOGFILSIZ Pre-create all warehouse tables This step is not mandatory if all the required warehouse and summarization tables are defined in the ITCAM for Transaction database. At a minimum, the following tables must exist in the warehouse database to run the reports. Table 3: Minimum tables for ITCAM for Transactions reports Agent Application Management Console (raw data, hourly) Client Response Time (raw data, hourly) Web Response Time (raw data, hourly, daily) Robotic Response Time (raw data, hourly) Transaction Tracking (raw data, hourly) Tables - AMC_Application - AMC_Client - AMC_Transaction - AMC_Server - AMC_Internet_Service - AMC_Internet_Service_Agent - AMC_Internet_Service_Element - CRT_Application_Status - CRT_Transaction_Status - WRT_Application_Status - WRT_Transaction_Status - WRT_User_Sessions - RRT_Application_Status - RRT_Transaction_Status - RRT_SubTransaction_Status - RRT_Robotic_Playback_Events - Aggregates - Interactions If any of these tables are not present, some report pages will fail to run. In most cases, you might not have all the agents installed in your environment, but still want to run part of the reports. Thus, you must run script that is provided in the report package. Note: There scripts for creating every possible ITCAM for Transaction table. 1. Connect to the DB2 database warehouse as the ITM Tivoli Data Warehouse user. su db2inst1 db2 connect to ITMDB user itmuser using Smartp0c 2. Create tables, views and indexes for ITCAM for Transactions Cognos report. db2 tf ${Image_Location}/utilities/db2/tdw_schema_table.sql db2 tf ${Image_Location}/utilities/db2/ tdw_schema_view.sql db2 tf ${Image_Location}/utilities/db2/ tdw_schema_index.sql db2 td# -f ${Image_Location}/utilities/db2/ tdw_schema_function.sql db2 tf ${Image_Location}/utilities/db2/ itcamt_db2_indexes.sql 3. All required tables by Transaction Cognos report should be created. You can verify this by running some of the reports in the Tivoli Common Reporting console. You should see no error occur. 12

21 4 Enable Historical Data Collection By enabling historical data collection on ITCAM for Transaction agents, the warehouse proxy agent collect data from Tivoli Enterprise Monitoring Agent and insert them into corresponding tables in the Tivoli Data Warehouse. And summarization and pruning agent aggregates and prunes the historical data in fixed interval. 4.1 Enable Historical data collection manually 1. Open History Collection Configuration Figure 14: History collection configuration window 2. Select the agent that you want to configure, for example, End User Response Time (AMC). Right-click the node, and select Create new collection settings. 3. Enter AMC Application as the name for this collection and select AMC Application from the list of attribute groups. Click OK. 13

22 Figure 15: Create new collection settings 4. Click on the new created collection; it looks like the following screen capture: Figure 16: View the new created collection 5. Click the Distribution tab, and select the available systems to add it to the Start collection on list. 14

23 Figure 17: Start collection on specified agent 6. Click Apply to start the collection. 7. Navigate back to End User Response Time and select AMC Application attribute groups to display configuration controls. 15

24 Figure 18: Set summarization and pruning parameters 8. Set Summarization and Pruning parameters and click Apply to take effect. 9. Repeat these steps to create and configure all the required attribute groups for ITCAM for Transaction agents. 4.2 Enable Historical data collection using scripts Because there are many attribute groups that must be enabled, you can write scripts to save time. Here is a sample shell script named HistoricalDataEnable.sh to enable historical data collection for a Linux environment. Example HistoricalDataEnable.sh #!/bin/sh function usage () { echo "" echo " Usage :" echo " HistoricalDataEnable.sh -s <Specifies the TEPS hostname to log into>" echo " -c <Specifies the Candle home direcotory, for example, /opt/ibm/itm>" echo " -u <Specifies the user name to authenticate>" echo " -p <Specifies the password to authenticate>" echo " -t <Specifies the product code>" echo " -n <Specifies the TEMS name to be started>" 16

25 } echo "" exit 1 ################################################################### ############# # # Read arguments # ################################################################### ############# while [ $# -ne 0 ] do case $1 in -s*) server=$2 ;; -c*) candle_home=$2 ;; -u*) user=$2 ;; -p*) password=$2 ;; -t*) product=$2 ;; -n*) manage_system=$2 ;; *) ;; esac shift 1 done if [ -z $server ];then usage exit 1 fi if [ -z $candle_home ];then usage exit 1 fi if [ -z $user ];then usage exit 1 fi if [ -z $password ];then usage exit 1 fi if [ -z $product ];then usage 17

26 exit 1 fi if [ -z $manage_system ];then usage exit 1 fi echo "$0: parameters parsed..." echo "$0: ============================== " echo "Login to TEMS." $candle_home/bin/tacmd login -s $server -u $user -p $password $candle_home/bin/tacmd histlistproduct -s $server -u $user -w $password > $PWD/histListProduct.txt grep $product $PWD/histListProduct.txt if [ $? == "0" ]; then $candle_home/bin/tacmd histlistattributegroups -s $server -u $user -w $password -t "$product" > $PWD/${product}_attributes.raw sed "s/[ ]*Not Configured$//g" $PWD/${product}_attributes.raw sed "s/[ ]*Configured$//g" sed "1,2d" > $PWD/${product}_attributes.txt cat $PWD/${product}_attributes.txt while read a do $candle_home/bin/tacmd histconfiguregroups -s $server -u $user -w $password -t "$product" -o "$a" -d YQMWDH -p "Y=1y,Q=1y,M=2m,W=2m,D=1m,H=1m,R=1m" -m $candle_home/bin/tacmd histcreatecollection -s $server -u $user -w $password -t "$product" -o "$a" -c 5m -l TEMA -i 15m -a "$a" $candle_home/bin/tacmd histstartcollection -s $server -u $user -w $password -a "$a" -n $manage_system done else echo "Invalid product code." echo "Please check the product code using $candle_home/tacmd histlistproduct" fi How to use this script: 1. Keep Tivoli Enterprise Portal Server and Tivoli Enterprise Monitoring Server running. 2. Run the HistoricalDataEnable.sh script without parameters to view the usage as follows: Figure 19: HistoricalDataEnable.sh usage 18

27 3. To enable all the attribute groups of the AMC agents, you can run the following script:./historicaldataenable.sh -s localhost -c /opt/itm -u sysadmin -p Smartp0c -t KT3 -n TEMS_sysappsles 5 Generate Transactions Data for Collection Because ITCAM for Transactions Cognos reports are reporting against historical data in Tivoli Data Warehouse, you must generate transaction data for warehouse proxy agent to insert into historical tables. By default, WRT, RRT and ISM agents require customizations of each agent to collect transactions data. This section provides a few samples or guidelines to customize the configuration for Transaction agents. Generally, the customizations differ in different transaction environments. You have to customize the configuration according to your specified transaction environment. 5.1 Customizing the Web Response Time agent You can customize and tune Web Response Time (WRT) to meet the specific monitoring requirements. Therefore, it is important that you understand the transaction/application in your environment. Note: Before you start to customize the WRT agent make sure that the WRT agent is able to capture HTTP/HTTPS transaction data from the target server, either by the local mode or the appliance mode. In our environment, the WRT agent was installed on a remote server against IHS and a WebSphere Application Server on the same v-switch. You should enable Promiscuous Mode. 1. Define applications in the Application Management Configuration Editor (configuration editor). In this example the application name is WRT_4_TCR. 19

28 Figure 20: Create a new WRT application 2. To add a transaction into the new created application, right-click the name of the application in the application navigator. Enter the transaction name of PoC, and select Web Response Time as the agent type as shown in the following figure. Click OK. Figure 21: Create transaction for application 3. Create a filter for the transaction. 20

29 Figure 22: Transaction filter 4. Select Profiles from the top right of the navigator, and then expand Web Response Time node. 5. Right-click on the Web Response Time node to create a new profile. Figure 23: Create a new WRT profile 6. Click the Transaction tab from the WRT_Demo profile, and then click Add to add a transaction into the profile. 21

30 Figure 24: Add applications and transactions into the profile 7. Deploy this profile to the valid managed systems. 22

31 Figure 25: Deploy the profile for monitoring 8. From the default Applications view in the configuration editor, you can click the name of an application in the Applications list, and then click the Session tab to display the Session Identification configuration dialog box. 23

32 Figure 26: Enable session tracking 9. Before you add entries to the table, select the Enable session tracking check box. 10. Click Add to open the Session identification dialog box, and then enter a definition for the session. In the following example, a User-Agent key name for HTTP Header has been entered. You can add your preferred Session Identifier. Click OK. Figure 27: Create or edit the session keys 11. Click Apply to save your changes and return to the Application tab. 12. From the default Applications view in the configuration editor, click the name of an application and then click the Users tab to display the User Identification and Unique User Information configuration dialog boxes. 24

33 Figure 28: Enable user tracking 13. Select the Enable user tracking check box to enable user tracking for the users. 14. In the User Identification section of the Users tab, click Add. The User Identification dialog box opens in a separate window. Figure 29: Create or edit user identity information Note: The information used to identify HTTP user should be included in Session Identification keys. 15. In the Report anonymous users as field, you can type a string to represent the anonymous user name, such as Anonymous. 25

34 Figure 30: Enable anonymous users tracking 16. Click Apply to save your changes and return to the Application tab. 17. Create a client group for your transactions. Figure 31: Create a client group 18. Create a filter for the client group that you just created. In this case, if the source IP matches , it belongs to the VM1-TCR client group. Figure 32: Create a filter for a client group 19. Click OK to save your changes and exit the Application Management Configuration Editor. 20. Verify the client group that you created in Tivoli Enterprise Portal. 26

35 Figure 33: View the client group on TEP 21. Make sure that users information can be tracked by the WRT agent. Figure 34: Verify the user information tracking 27

36 22. View the User_Analysis report, which shows the response time and bandwidth consumed by the select user along with other metrics. Figure 35: Select a user for Transactions Cognos reports Note: You might not be able to observe the data from the User_Analysis report after you complete the customization. The User_Analysis report requires the hourly historical table WRT_User_Sessions_H, while it takes a while for the WRT agent to aggregate raw data to hourly data. 5.2 Customizing the Robotic Response Time agent 1. Record a RPT script in the Rational Performance Tester workbench as shown in the following screen capture. This example creates a SimpleTrade script to access a simple J2EE application on VM2 (sysappdemosles.poc.ibm.com). 28

37 Figure 36: RPT workbench 2. To upload the created script, right-click the name, then click Export. Figure 37: Upload recorded scripts to Application Management Console 3. Specify the host name and connection information for Application Management Console. 29

38 4. Select the files to export to AMC and click Finish to complete the export. Figure 38: Select the SimpleTrade application 5. From the Robotic Scripts workspace, you should be able to see the scripts that you just exported. Figure 39: Verify the uploaded scripts in Tivoli Enterprise Portal 6. Open the Application Management Configuration Editor and select Profiles from the drop-down list. 7. Expand the Robotic Response Time node and right-click the node and select Create New Profile. 30

39 Figure 40: Create a profile for RRT 8. Enter RPT_SimpleTrade as the name of the profile and click OK. 9. Select RPT_SimpleTrade and click the Transactions tab to add transactions for this profile. Figure 41: Add a transaction into the RRT profile 10. Click the Distribution tab to distribute this profile to the RRT agent and then click the OK button. 31

40 Figure 42: Distribute the RRT profile to a RRT agent 11. You can check the playback status in the Playback Status workspace of the Robotic Response Time agent. It looks similar to the following figure. Figure 43: Verify the playback status on Tivoli Enterprise Portal 32

41 12. In the Application Management Console, you see the application SimpleTrade listed in the Applications folder. 5.3 Customizing the Internet Service Monitoring agent The customization for the Internet Service Monitoring (ISM) agent is similar to customizing the RRT agent. The following steps show how to configure the ISM agent to monitor the HTTP web server. Historical data from different profiles will be collected, which can be displayed in Tivoli Common Reporting Cognos reports. Note: You also can use the ISM configuration CLI to customize the ISM agent. 1. To open the ISM configuration GUI, click the ISM button in the Tivoli Enterprise Portal. 2. Create a profile to store the HTTP profile monitor element. Figure 44: Create a HTTP profile for Internet Service Monitoring 3. Click the Create New Profiles button. Enter TCR as the profile name, and press OK. Figure 45: Input the profile name 4. Add an HTTP monitor to the profile to store the HTTP profile monitor element. 33

42 5. Select the HTTP monitor type from the drop-down menu to add the profile. Figure 46: Add monitor type to profile 6. Select the HTTP profile in the navigation tree, type in the server name or IP address, page URL, and HTTP port. In this example, the HTTP server is VM4 ( ). 34

43 Figure 47: Customize the HTTP profile 7. Deploy the profile to an ISM agent. Figure 48: Deploy the profile to an ISM agent 35

44 8. If you want to simulate Bad services, you can enter a server name or IP address that does not exist. For example, create an HTTP service monitoring element and deploy it to a valid ISM Agent. Or you can change the clarification of service level. Figure 49: Change SLC to simulate bad HTTP services 9. To verify that your profiles take effect, view the ISM agent workspace. 36

45 Figure 50: Verify the profile in Tivoli Enterprise Portal 10. Navigate to the Internet Service Availability report. Figure 51: Internet Service Availability report 11. View history data in the ISM Cognos reports. The following example is based on previous customization of an ISM agent. 37

46 Figure 52: View the result of Internet Service Availability After you finish the customization for WRT, RRT, and ISM agents, most historical data can be generated to meet the requirement of ITCAM for Transaction Congos reports. Note: In this paper, the samples with the steps showing how to customize the three types of transaction agents are very simple and do not provide the steps for the customization of the Client Response Time (CRT) agents. You should customize ITCAM for Transactions agents based on your own requirements. 38

47 REFERENCES IBM Cognos 8 Version 4 Business Intelligence Information Center IBM Tivoli Common Reporting Version Information Center c-home.html IBM Tivoli Composite Application Manager for Transactions Version Information Center IBM Tivoli Composite Application Manager for Transactions Cognos Reports README ix

48 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 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd , Shimotsuruma, Yamato-shi Kanagawa Japan The 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 might 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 websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites 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. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/ Burnet Road Austin, TX U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. x

49 ITCAM for Transactions Cognos Report Best Practices Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM 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. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. 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 illustrate 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 interfaces. Each copy or any portion of these sample programs or any derivative work must include a copyright notice as follows: (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. Copyright IBM Corp. _enter the year or years_. All rights reserved. If you are viewing this information in softcopy form, the photographs and color illustrations might not be displayed. xi

50 TRADEMARKS IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Microsoft is a trademark of Microsoft Corporation in the United States, other countries, or both. VMware and all VMware-based trademarks are trademarks of VMware Incorporated in the United States, other countries, or both. Oracle is a trademark of Oracle Corporation in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. xii