Test 000-655: IBM Tivoli Composite Application Manager for Transactions V7.3 Implementation

Section 1: Planning

1. Given customer input, Statement of Work and IBM Tivoli Composite Application Manager (ITCAM) for Transactions V7.3 architecture, identify the monitoring environment and customer requirements so that a deployment plan can be created.
   With emphasis on performing the following tasks:
   
   1. Identify the customer's monitoring requirements. (i.e. number of transaction reporters)
   2. Identify the existing IBM Tivoli Monitoring installation if it exists.
   3. Identify the applications, transactions, transaction flow, and servers to be monitored.
   4. Identify the network topology.
   5. Identify firewall configuration information.
   6. Determine where ITCAM for Transactions V7.3 components should be installed.
   7. Prepare a deployment plan.
2. Given the customer's current environment, product documentation, and appropriate access information, verify the prerequisites and access controls so that the hardware and software levels meet the minimum requirements or upgrades recommended to the customer.
   With emphasis on performing the following tasks:
   
   1. Verify and map the prerequisites for all components (hardware and software) to the deployment plan.
   2. Resolve missing hardware or software prerequisites.
   3. Identify and resolve permission issues.
   4. Resolve the size and scalability of the resources.
   5. Ensure there are no preexisting ARM libraries installed.
   6. Identify and resolve access controls for customer's systems and environments (for example: WebSphere, DB2, IIS, etc…).

Section 2: Installation

1. Given the deployment plan, product installation guide and media, install the Tivoli Enterprise Monitoring Agents (TEMAs) so that the TEMAs are available to be configured for measuring the response time of various applications.
   With emphasis on performing the following tasks:
   
   1. Install the TEMAs on Windows.
   2. Install the TEMAs on UNIX.
   3. Use the remote deployment feature to install the TEMAs if required.
2. Given the customer's deployment plan, product installation guide and media, install the IBM Tivoli Composite Application Manager (ITCAM) for Transactions V7.3 application support files on Tivoli Enterprise Management Server (TEMS) and remote TEMS (RTEMS) so that the appropriate attributes and situations will be available.
   With emphasis on performing the following tasks:
   
   1. Install the application support on TEMS/RTEMS on Windows.
   2. Install the application support on TEMS/RTEMS on UNIX.
3. Given the customer's deployment plan, product installation guide and media, install the ITCAM for Transactions V7.3 application support files on Tivoli Enterprise Portal Server (TEPS) so that the appropriate workspaces will be available.
   With emphasis on performing the following tasks:
   
   1. Install application support on TEPS on Windows.
   2. Install application support on TEPS on UNIX.
   3. Install Tivoli Enterprise Portal (TEP) browser client support on Windows.
   4. Install TEP browser client support on UNIX.
4. Given the customer's deployment plan, product installation guide and media, install the ITCAM for Transactions V7.3 application support files on TEP clients so that the appropriate workspaces will be shown in the appropriate format.
   With emphasis on performing the following tasks:
   
   1. Install TEP desktop client support desktop on Windows.
   2. Install TEP desktop client support on UNIX.
5. Given the customer's deployment plan, product installation guide, and media, install the Rational Robot on Windows so that synthetic transactions can be recorded and played back.
   With emphasis on performing the following tasks:
   
   1. Install Rational Robot on Windows.
6. Given the product installation media, the product installation guide and the deployment plan, install the Rational Performance Tester (RPT) so that it is able to record synthetic transactions.
   With emphasis on performing the following tasks:
   
   1. Install RPT on Windows, Linux, and AIX.
   2. Install the ITCAM for Transaction RPT workbench plug-in.
7. Given the product installation media, the product installation guide and the deployment plan, install the Rational Functional Tester (RFT) so that it is able to record synthetic transactions.
   With emphasis on performing the following tasks:
   
   1. Install RFT on Windows.
   2. Install the ITCAM for Transactions RFT plug-in.
8. Given the customer's deployment plan, product installation guides, and media, install the appropriate data collectors so that data collectors are ready to be configured.
   With emphasis on performing the following tasks:
   
   1. Install appropriate data collectors.
9. Given the customer's deployment plan, product installation guide and media, run the silent installation process so that the TEMAs application support files and the RPT are installed.
   With emphasis on performing the following tasks:
   
   1. Run silent installation on Windows - Perform a silent install of a monitoring agent (Windows).
   2. Run silent installation on UNIX or Linux - Perform a silent install and configuration for a monitoring agent (UNIX or Linux).
   3. Install application support for the agent - Install application support for Windows or Install application support for Linux and UNIX by using a silent installation.
   4. Install RPT by using the silent install method.
10. Given a running ITCAM for Transactions V7.3 installation, with historical data collection configured and uploading to the Tivoli Data Warehouse (TDW), and a running Tivoli Common Reporting installation, install the Tivoli Common Reporting (TCR) package for ITCAM for Transactions V7.3, so that trending reports can be produced and published.
    With emphasis on performing the following tasks:
    
    1. Find in the installation media the reports package documentation and the reports package.
    2. Create the required model tables in the TDW.
    3. Install TCR.
    4. Run the reports.

Section 3: Configuration

1. Given a running IBM Tivoli Monitoring (ITM) installation, an installed and running Application Management Console (AMC) and an installed Robotic Response Time (RRT) Tivoli Enterprise Monitoring Agent (TEMA) configure the RRT TEMA so that it is ready to receive and run robotic playback profiles
   With emphasis on performing the following tasks:
   
   1. Start appropriate configuration command/interface for Windows or UNIX.
   2. Configure the RRT's Tivoli Enterprise Management Server (TEMS) connection parameters.
   3. Configure Robotic Monitoring playback parameters.
   4. Configure Rational Performance Tester playback parameters.
   5. Configure Rational Robot playback parameters.
   6. Configure Rational Functional Tester playback parameters.
   7. Configure LoadRunner playback parameters.
   8. Configure Data Analysis parameters.
2. Given an installed Web Response Time (WRT) TEMA and configured AMC and proper access controls, configure WRT agent so that Web response time and availability can be measured.
   With emphasis on performing the following tasks:
   
   1. Configure the WRT agent connection to a monitoring server.
   2. Configure the WRT to monitor web servers.
   3. Install and configure filters for the monitored Web servers if necessary.
   4. Configure the attributes for appliance mode and performance parameters if necessary.
   5. Create or modify and deploy an AMC profile to define web transactions.
3. Given an installed Client Response Time (CRT) TEMA and configured AMC and proper access controls, configure CRT agent so that client response time and availability can be measured.
   With emphasis on performing the following tasks:
   
   1. Configure the CRT agent connection to a TEMS.
   2. Use the default behavior file.
   3. Create or modify and deploy an AMC profile.
4. Given an installed Transaction Collector TEMA and configured AMC and proper access controls, configure the Transaction Collector agent so that the proper information can be collected.
   With emphasis on performing the following tasks:
   
   1. Configure the Transaction Collector agent connection to a monitoring server.
   2. Configure the Transaction Collector monitoring parameters.
5. Given an installed transaction reporter TEMA, configured AMC, and proper access controls, configure the transaction reporter so that the proper information can be collected.
   With emphasis on performing the following tasks:
   
   1. Configure the transaction reporter agent connection to a monitoring server.
   2. Configure the transaction reporter monitoring parameters.
   3. Create or modify and deploy an AMC profile.
6. Given a running ITCAM for Transactions V7.3 installation with required domains (WMB, WMQ, HTTP, IIS, ITCAM for AD, CICS, etc), and proper access controls and permissions, configure the required domains, so that transaction tracking data from those domains can be integrated with ITCAM for Transactions V7.3.
   With emphasis on performing the following tasks:
   
   1. Configure required domain to generate and send transaction tracking data to appropriate Transaction Collector.
   2. Install the appropriate ITCAM for Transactions V7.3 TEMA and modify the required paths to incorporate Applicant Response measurement libraries.
7. Given an installed Internet Services Monitoring (ISM) TEMA and configured AMC and proper access controls, configure ISM profiles so that Internet services response times and/or availability can be measured.
   With emphasis on performing the following tasks:
   
   1. Configure the appropriate ISM agent connection to a TEMS.
   2. Create and deploy ISM profiles.
8. Given proper access controls, and the AMC agent is installed, configure it as required so that transaction response times are collected and displayed in the Tivoli Enterprise Portal (TEP) console.
   With emphasis on performing the following tasks:
   
   1. Identify the procedure on how to start the configuration via GUI or command in both Windows and UNIX operating system.
   2. Identify if the TEMS hostname is required for this configuration.
   3. Identify if the TEMS listening port number is required for this configuration.
   4. Identify if the default values of "Data Collection Configuration" tab is sufficient for data collection for data collection and display or any values is required to be updated.
   5. Identify if the default values of "JMX SOAP Connector Server Configuration" tab is sufficient for data collection.
9. Given proper access controls, the situation events that will be generated in ITCAM for Transactions v7.3, configure and enable the forwarding of events to OMNIBUs with correct slot mappings and additionally integrate ITCAM for Transactions v7.3 with IBM Tivoli Business Service Manager (TBSM) so that ITCAM for Transactions situation events will be visible at the OMNIBus console and additionally ITCAM for Transactions will be fully integrated with TBSM.
   With emphasis on performing the following tasks:
   
   1. Configure ITM to send events to OMNIBus.
   2. Configure ITCAM for Transactions v7.3 situation for event slot mapping.
   3. Work with TBSM administrator to make sure TBSM is modified to include service templates, policies, and portlets to ITCAM applications, and sub transactions.
   4. Work with the OMNIBus administrator to modify the alerts.status table and probe rules file to collect transaction and application data from ITM situation events.
   5. Create Discovery Library Adaptor XML book and load it to TBSM.
   6. Work with TBSM Administrator to create a custom page to display ITCAM for Transactions data.

Section 4: Administration

1. Given the deployment plan, an installed and running Tivoli Data Warehouse (TDW), and application support files for IBM Tivoli Composite Application Manager (ITCAM) for Transactions are installed, configure historical data collection, summarization and pruning so that ITCAM for Transactions historical data is obtained.
   With emphasis on performing the following tasks:
   
   1. Identify the attribute groups specified in the deployment plan.
   2. Estimate database space utilization and availability.
   3. Configure and start historical collection in the TDW for the attribute groups identified.
   4. Set up the data collection time.
   5. Set the summarization and pruning intervals.
2. Given one or more installed Transaction Tracking agent(s), Rational Robot, Rational Performance Tester (RPT) or Rational Functional Tester(RFT) , uninstall the component so that it is removed from the environment
   With emphasis on performing the following tasks:
   
   1. Run the uninstall command for UNIX systems, select the component to uninstall from the list and verify component is uninstalled.
   2. Run the proper uninstall procedure for Windows (depending on Windows version installed).
3. Given a configured ITCAM for Transactions V7.3 environment, analyze workspace data so that the performance and availability of the monitored applications can be determined.
   With emphasis on performing the following tasks:
   
   1. Analyze data within the Robotic Response Time (RRT) agent workspaces.
   2. Analyze data within the Web Response Time (WRT) agent workspaces.
   3. Analyze data within the Client Response Time agent workspaces.
   4. Analyze data within the Application Management Console (AMC) agent workspaces.
   5. Analyze data within the Transaction Tracking agent workspaces.
   6. Analyze data within the Internet Services Monitoring (ISM) agent workspaces.
4. Given an installed RRT Tivoli Enterprise Monitoring Agent (TEMA) and AMC, installed robotic software and proper access controls, work with the RRT TEMA and create robotic scripts so that application response time and availability can be measured.
   With emphasis on performing the following tasks:
   
   1. Verify configuration of all the robotic monitoring components and AMC.
   2. Run transactions manually.
   3. Record and test robotic scripts.
   4. Upload robotic scripts.
   5. Create and deploy a profile to schedule playback.
   6. Verify playback in the RRT workspaces.
   7. Create ITM monitoring situations to manage applications.
5. Given the WRT agent is running and proper access controls, administer WRT agent so that the WRT profile including filtering have been set up and Web server/s can be monitored by the Web Response Time agent.
   With emphasis on performing the following tasks:
   
   1. Set up a WRT profile or use the default.
   2. Edit filtering properties if desired.
   3. Distribute the WRT profile to the WRT agent TEMA.
6. Given the Client Response Time agent is running and proper access controls, administer Client Response Time agent so that the behavior files have been set up and can be monitored by the Client Response Time agent.
   With emphasis on performing the following tasks:
   
   1. Set up a behavior file.
   2. Describe the seven default behavior files shipped with ITCAM for Transactions.
   3. Use ETEWatch to create a behavior file that can be used to monitor their protocol, if the customer wants to monitor a protocol that is not covered by the default seven behavior file shipped with it.
   4. Set up an application accessed by Citrix and Remote Desktop that can be monitored by Client Response Agent.
7. Given the ISM agent is running and proper access controls, administer ISM agent so that the monitors have been set up and can be monitored by the ISM agent.
   With emphasis on performing the following tasks:
   
   1. Create a user profile and add the desired ISM monitor elements within the ISM configuration GUI or ISM command line interface.
   2. Add the monitor type and make it active.
   3. Add any optional elements such as service level classifications or Service Level Agreements etc.
   4. Add any optional Regular expressions.
   5. Create a monitoring schedule or use the default.
   6. Distribute to the required managed system.
8. Given proper access controls, and the Application Management Console agent is installed, administer the Application Management Configuration Editor to create definitions of applications, clients and transactions to be monitored so that Application Management Configuration Editor is set up properly.
   With emphasis on performing the following tasks:
   
   1. Define applications and transactions for profiles.
   2. Define and update profiles appropriately.
9. Given proper access controls, the Application Management Console TEMA, Transaction Reporter TEMA and Transaction Collectors are installed and running and collecting data, administer Transaction Reporter TEMA so that the Transaction Reporter are set up appropriately.
   With emphasis on performing the following tasks:
   
   1. Determine the correct Tivoli Enterprise Portal workspace to detect if any records are being dropped.
   2. Tune Transaction Reporter data collection settings.
   3. Tune Transaction Reporter Aggregation Agent data collection settings
   4. Modify the Reporter for various base line options.
   5. Modify the Reporter to update various options such as Implied and Pseudo interactions, Aggregation, etc.
10. Given the Transaction Collector has been integrated with WebSphere Application Server and WebSphere MQ, and the proper access, administer the integration between WebSphere and ITCAM for Transactions to display the stitching between WMQ and WebSphere with JDBC response time (Level 1) for ITCAM for AD so that the stitching between WebSphere MQ and WebSphere Application server with JDBC response time (Level 1) for ITCAM for AD will be displayed in ITCAM for Transactions Reporter Topology workspace.
    With emphasis on performing the following tasks:
    
    1. Set up the stitching between WebSphere MQ and WebSphere Application Server, via the ITCAM for Application Diagnostics Managing server, additional configuration has to be done.
    2. Set up the JDBC response time for the transaction between WebSphere Application Server and database in level monitoring level of AD, additional configuration has to done from the ITCAM for Applications Diagnostics managing server.

Section 5: Problem Determination

1. Given a failed IBM Tivoli Composite Application Manager (ITCAM) for Transactions V7.3 Tivoli Enterprise Management Agent (TEMA) installation and that Tivoli Enterprise Management Server (TEMS) and Tivoli Enterprise Portal Server (TEPS) are installed and functioning correctly, troubleshoot the installation so that the probelm with the TEMA installation is identified.
   With emphasis on performing the following tasks:
   
   1. Locate and analyze the common and TEMA installation log files.
   2. Locate and analyze platform specific trace information.
2. Given a non-functioning, installed ITCAM for Transactions V7.3 TEMA and no data in the workspaces, and TEMS and TEPS are installed and functioning correctly, troubleshoot the non-functional TEMA so that the problem with the non-functional TEMA is identified.
   With emphasis on performing the following tasks:
   
   1. Identify if the appropriate TEMA application support is installed on the TEMS and TEPS.
   2. Increase message and trace log level.
   3. Locate and analyze the appropriate TEMA log files.
   4. Determine that the appropriate TEMA has started.
   5. Identify and correct JAVA dump errors.
   6. Verify the TEMA is configured correctly.
3. Given that TEMS and TEPS are installed and functioning and there are Robotic Playback issues, troubleshoot the Robotic Playback issues so that the issues have been identified.
   With emphasis on performing the following tasks:
   
   1. Verify that the appropriate Robotic Playback script has been loaded into the Application Management Console (AMC) and agent depot directories.
   2. Verify the Robotic Response Time agent.
   3. Test the Robotic Playback script.
   4. Verify the status of the Robotic Playback script.
   5. Locate and analyze the trace Robotic Playback log files
   6. Locate and analyze the trace files for Citrix communication in Rational Performance Tester.
4. Given a running ITCAM for Transactions V7.3 installation, with historical data collection configured and uploading to the Tivoli Data Warehouse (TDW), verify and analyze the data flow between components so that the correct topology of the monitored transactions can be viewed
   With emphasis on performing the following tasks:
   
   1. Verify proper access controls and permissions are granted.
   2. Verify, analyze and correct or tune if necessary, the data flow between the Data Collectors and the Transaction Collectors.
   3. Verify, analyze and correct or tune if necessary, the data flow between the Transaction Collectors and the Transaction Reporter(s).
   4. Verify, analyze and correct or tune if necessary, the filtering of transaction data between the Transaction Collectors, the Transaction Reporter(s) and the AMC.
   5. Verify, analyze and modify if necessary the history collection configuration for the data that is collected in the TDW.
5. Given proper access controls, the AMC TEMA, Transaction Reporter TEMA and Transaction Collectors are installed and running and the AMC is performing poorly, troubleshoot the AMC so that the AMC issues are identified.
   With emphasis on performing the following tasks:
   
   1. Identify the location of configuration, log, trace files.
   2. Increase the debug level.
   3. Keep tab of all warning, error messages.
   4. Increase the Java Max Heap size if required.
   5. Verify if firewall exists and if it does, verify the configuration.
6. Given proper access controls, the Application Management Configuration Editor TEMA, Transaction Reporter TEMA and Transaction Collectors are installed and running and collecting data, troubleshoot the Application Management Configuration Editor so that the root cause of the Application Management Configuration Editor issue is determined.
   With emphasis on performing the following tasks:
   
   1. Locate the location of the compressed.encoded depot files, if neccessary.
   2. Record the error messages displayed by the Application Management Configuration Editor.
   3. Refer to the trouble shooting documentation.
   4. Determine if the software is at the appropriate level.