Robotic Response Time deployment and administration

The following illustrates a typical Robotic Response Time deployment:

robotic script deployment
When using Robotic Response Time:
  • Install the agent in several strategic remote locations or branch offices to ensure 24x7 availability.
  • Install the agent both inside and out of the enterprise.
  • The preceding helps identify which client location is having problems before the customer becomes aware of the problem.
  • The recorder typically installed on 1 or 2 intranet systems with dedicated script developers.
  • If Rational Robot, Rational Functional Tester, or Mercury LoadRunner is used as a recorder, the recorder must also be installed on the same system with the Robotic Response Time agent.
  • A typical deployment is 10 to 20 robotic agents running 10 to 100 robotic scripts every 10 to 15 minutes. Note that the volume of scripts depends on various factors such as the complexity of the scripts, the number of elements in the scripts, and the time the script is run.

The following test scripts are supported by Robotic Response Time:

Keep in mind the following deployment considerations:
  • Install the agent on a dedicated system.
  • Rational® Robot GUI, Rational Functional Tester, Citrix, SAP, and Siebel playback run only on Windows systems.
  • Rational Performance Tester HTTP/HTTPS scripts run on Windows and xLinux (RHEL, SUSE) systems.
  • Rational Robot GUI and Rational Functional Tester require the screen to be unlocked, so system must be in a secure location or running in a VM instance with a locked host.
  • Scalability recommendations:
    • Rational Robot GUI, RPT running Citrix scripts: 10 scripts per agent every 10 minutes
    • CLI, Rational Robot VU, LoadRunner: 50 scripts per agent every 10 minutes
  • Both secure and non-secure web services are supported. For secure web services, only the following protocol specifications are supported:
    • HTTPS based SOAP
    • WS-Security
    • WS-Addressing
    • WS-ReliableMessaging

After you set up robotic playbacks, Robotic Response Time can identify bottlenecks in the Client, Network or Server by breaking down response time data into segments, so that you can understand trends and system loads. The breakdown availability of the response time data is determined by the type of robotic scripts and the availability of metric definitions. The availability of breakdown for different robotic scripts is explained in the following table.

Table 1. Breakdown availability to different robotic scripts
Robotic script type Client time Network time Server time
Rational Performance Tester HTTP/HTTPS Yes Yes Yes
Rational Performance Tester Citrix Yes No No
Rational Performance Tester SAP GUI Yes No No
Rational Performance Tester SAP Web Interface Yes Yes Yes
Rational Performance Tester Siebel Yes Yes Yes
Rational Performance Tester Web Services/SOA Yes No No
Rational Functional Tester Yes No No
Rational Robot GUI Yes No No
Rational Robot VU Yes No No
Mercury LoadRunner HTTP/HTTPS Yes No No
Command Line scripts Yes No No
BSD Oracle ERP scripts Yes Yes Yes

Robotic Response Time administration

The following table lists the configuration files for Robotic Response Time:
Restriction: Do not modify configuration files without explicit instructions from IBM® Support.
File Description
Windows environment
ITM_HOME\tmaitm6\kt6env Environment variables for the Tivoli Enterprise Monitoring Agent
ITM_HOME\tmaitm6\${HOSTNAME}_t6.cfg Saved Tivoli Enterprise Monitoring Agent configuration settings
ITM_HOME\tmaitm6\t6-logging.properties Robotic Response Time JLOG configuration
ITM_HOME\tmaitm6\app\RPT\config\itcam-rpt.properties Rational Performance Tester Configuration parameters
ITM_HOME\tmaitm6\app\RPT\config\itcamrt-logging.properties Rational Performance Tester JLOG configuration
ITM_HOME\tmaitm6\app\RPT\config\managed_jvm.xml Rational Performance Tester Managed JVM Java™ parameters
UNIX environment
ITM_HOME/config/t6.ini Environment variables for the Tivoli® Enterprise Monitoring Agent
ITM_HOME/config/${HOSTNAME}_t6.cfg Saved Tivoli Enterprise Monitoring Agent configuration settings
ITM_HOME/config/t6-logging.properties Robotic Response Time JLOG configuration
ITM_HOME/tmaitm6/app/RPT/config/itcam-rpt.properties Rational Performance Tester Configuration parameters (xLinux only)
ITM_HOME/tmaitm6/app/RPT/config/itcamrt-logging.properties Rational Performance Tester JLOG configuration (xLinux only)
ITM_HOME/tmaitm6/app/RPT/config/managed_jvm.xml Rational Performance Tester Managed JVM Java parameters (xLinux only)
The following table lists the trace and log files for Robotic Response Time:
Note: For more information about trace and log files, see the IBM Tivoli Composite Application Manager for Transactions Troubleshooting Guide.
File Description
Windows environment
ITM_HOME\tmaitm6\logs\${HOSTNAME}_t6_*.log Tivoli Enterprise Monitoring Agent RAS1 logs. RAS1 is the name of the IBM Tivoli Monitoring logging facility.
C:\Program Files\ibm\tivoli\common\BWM\logs\trace-robotic.log Tivoli Enterprise Monitoring Agent JLOG trace statements
C:\Program Files\ibm\tivoli\common\BWM\logs\msg-robotic.log Tivoli Enterprise Monitoring Agent JLOG message statements
C:\Program Files\ibm\tivoli\common\BWM\logs\RPT\ {runtime version}\trace-rpt.log Rational Performance Tester JLOG trace statements
C:\Program Files\ibm\tivoli\common\BWM\logs\{applicationname}\{scriptname}\msg-rptHistory.log Rational Performance Tester execution history
C:\Program Files\IBM\tivoli\common\BWM\logs\RFT\{scriptname}\* Rational Functional Tester
UNIX environment
ITM_HOME\logs\${HOSTNAME}_t6_*.log Tivoli Enterprise Monitoring Agent RAS1 logs. RAS1 is the name of the IBM Tivoli Monitoring I logging facility.
/var/ibm/tivoli/common/BWM/logs/trace-robotic.log Tivoli Enterprise Monitoring Agent JLOG trace statements
/var/ibm/tivoli/common/BWM/logs/msg-robotic.log Tivoli Enterprise Monitoring Agent JLOG message statements
/var/ibm/tivoli/common/BWM/logs/RPT/ {runtime version}/trace-rpt.log Rational Performance Tester JLOG trace statements
/var/ibm/tivoli/common/BWM/logs/{applicationname}/{scriptname}/msg-rptHistory.log Rational Performance Tester execution history