ITCAM4Tx: RPT/RFT ITCAM Rational export can't connect to AMC
ericmtn 1000009W88 Visits (7583)
This blog describes a way to transfer robotic script from Rational Functional Tester (RFT) or Rational Performance Tester (RPT) recorder machine to "another" Application Management Console (AMC/t3) agent depot, when the direct network connectivity between RFT/RPT recorder machine and the "real" AMC agent machine is not working currently. Or some restrictions apply in the connectivity between the recorder machine and the AMC machine.
If the RFT/RPT recorder machine can't communicate directly to the AMC agent machine using JMX SOAP connector on port 1976 (default), while kt3agent is up and running and this port 1976 socket is opened on AMC machine, then :
bad case example:
good case example:
So if you are blocked, one way to possibly workaround this case is doing the following :
1) Install a "fake" AMC t3 agent ** on the RFT/RPT recorder machine **, using ITCAM for Tx installation image.
Once completed you should get this :
2) During AMC agent installation or configuration , when asked for the TEMS location, enter for example : 'localhost'.
3) Then after installation and configuration of your 'fake' AMC t3 agent is completed, and while AMC t3 agent is up and running,
launch the ITCAM Rational plug-in, and it should produce a <script>.zip on your local RFT/RPT recorder machine.
The important step during the Rational export action is to specify, as AMC agent target host : 'localhost'. Example:
4) you can then take these script files from your local AMC fake machine, and transfer them to the real AMC agent machine for later playback,
by a transfer method that is accepted in your environment.
Here are the details and steps needed to manually copy over the relevant files, from the fake AMC to the real AMC agent machine
4a) The Rational Functional Tester (RFT) archive .zip script(s) file(s), once exported, will be stored locally (thanks to 'localhost' trick)
4b) The Rational Performance Tester (RPT) archive .zip script(s) file(s), once exported, will be stored locally (thanks to 'localhost' trick)
e.g. on Windows : C:\I
4c) Then you can transfer manually :
- for RFT script:
** into same location ** in the recipient "real" AMC agent machine.
On real AMC agent:
copy over into :
for RFT : in <ITM
for RPT : in <ITM
4d) Then, on the "real" AMC agent machine, you will need to do this :
Once all this is done, you should be able to deploy your new scripts in your robotic profiles for playbacks, using TEP AMC configuration Editor GUI.
Subscribe and follow us for all the latest information directly on your social feeds: