IBM Tivoli Composite Application Manager for Transactions
~ How to do stuff ~
By Kevin Baldwin -
Run Rational Robot scripts in an ITCAMfT 7.4 environment.
Alternatively, consider changing to RFT or RPT .
ITCAMfT 7.3.0.x is the last version that supports Rational Robot scripts being played back on the Robotic Response Time / T6 agent.
The most recent supported version of Rational Robot is 7.0.2
If you want to run Rational Robot scripts in an ITCAMfT 7.4 environment you need to use ITCAMfT 22.214.171.124 RRT agents as described in the How to upgrade RRT and AMC Agents to v7.4 to support Rational Robot technote.
The only Rational products supported for use on ITCAMfT 7.4 agents are Rational Performance Tester (RPT) and Rational Functional Tester (RFT).
You may find the following information useful in helping you decide if using RFT or RPT is right for you.
There isn't a migration path for Rational Robot scripts to RFT or RPT, the actions currently performed in Rational Robot will have to recorded in either RPT or RFT.
ARM instrumentation of RFT and RPT is completely different to the method used in Rational Robot.
When a Robot script is auto-instrumented, ARM code is physically added to the scripts.
Alternatively, you can manually add the ARM calls and custom code can be added to manage the way errors and verification point failures are handled. For example, ending the script run with an ARM_FAILED when a VP fails.
ARM instrumentation for RFT and RPT scripts does not directly alter the recorded scripts and it is not possible to manually add ARM instrumentation.
RFT and RPT manage Response Times and Verification Points in different ways.
Rational Performance Tester - RPT
RPT is used to monitor HTTP or HTTPS web applications, SAP, Siebel, or Citrix applications for performance.
RPT Workbench does not need to be installed on playback agents.
By default, playbacks run concurrently in the background and Response Time Breakdown is enabled for all pages and objects in the recording.
Instead of using Start and Stop timers, you can group items together to create nested response time measurements.
Prior to RPT 8.2 which is supported by ITCAMfT 7.3, if a Verification Point failed the script would continue to run to the end unless manual changes are made to the recording to alter this behaviour. With RPT 8.2 it is possible to easily specify a number of different actions when a VP fails. For example, Stop script execution or skip to next primary page.
Take a look at Adding Conditional Logic and Specifying error-handling behavior to see how this is done.
Rational Functional Tester - RFT
RFT is used to monitor applications not covered by RPT for functional testing, regression testing, GUI testing, and data-driven testing.
Like Robot, RFT has to be installed on playback agents and relies on desktop interaction to visibly run playbacks one at a time.
You can add start and stop timers during script development as described in the Using timer commands to define subtransactions in RFT scripts blog.
When played back on an agent, ARM Start and Stop calls are made corresponding to the RFT timerStart and timerStop commands.
For nested timers to work correctly you need to use ITCAMfT 7.3 (or higher) with RFT 126.96.36.199. + IF01 or higher
If a Verification Point fails the script will continue to run to the end unless manual changes are made to the recording to alter this behaviour.
RFT does not have the same type of automated error-handling now found in RPT 8.2 but if is possible to add conditional logic as described in the Inserting conditional statements section of RFT documentation.
Another source of useful information is the Testing Using Rational Robot versus Rational Functional Tester developerWorks article.
Visit the ITCAM for Transactions ~ How to do stuff ~ Homepage for more blogs in this series