ITCAM4Transactions - AMC - Best practices and pitfalls (Part 1)
ericmtn 1000009W88 Comments (4) Visits (34266)
Here is a list of best practices and commonly encountered pitfalls while using Itcam for transactions and its Application Management Console ("AMC", ITM product code 't3') agent, and its associated Application Management Configuration Editor (AMCe) that you can start from ITM TEP client GUI.
I have put in bold below the key words that should help you to find out the subject that you are particularly interested in....
1. Check that you have installed ONLY ONE AMC agent in your ITM infrastructure. Installing several AMC agents within one ITM 6.x infrastructure (TEMS/TEPS) is not supported.
it can cause some issues like :
- Export of RFT or RPT script from RFT workbench or RPT workbench fails
- Deploying of profiles, or change in existing profiles, using AMC Editor, is ineffective
refer to this blog link that indicates how to check that only one AMC:T3 node is installed in your environment :
as described, you can use tacmd listsystems CLI command; or from the TEP GUI, you can check from the Navigator the Enterprise -> right mouse click -> Workspace -> "Managed system status", then in this view sort the result by using the Product column, and verify how many entries like :
appears in the Name column.
If more than one, uninstall any redundant T3 agent, remove any offline entry for <node>:T3 that would be left behind, reconfigure the "good" AMC agent and check its TEMS setting configuration to validate all is ok.
2. Check that you have the version of AMC agent matching exactly the AMC application support version deployed on TEMSs and TEPS and TEP desktop. Use "cinfo -t" (Unix) or "kincinfo -t" (Windows) command on the AMC agent system, and on all TEMSs, TEPS and TEP desktop client system, to compare versions laid down. If you see a difference, correct it.
3. Backup kt1depot directory on AMC agent system regularly.
4. Can we access the AMCe (AMC configuration editor) from TEP client concurrently?
yes, see technote :
5. Any tip to improve AMC agent performance?
- yes, possibly increase its heap size, especially if you see "OutOfMemory" error message found in agent log file : <hos
- install the AMC agent and connect it to the machine hosting the HUB TEMS (not to a remote TEMS), see :
- see other considerations for installing AMC at link :
6. Why using ISM or WRT or RRT agent for example, I can see no data reported in TEP under AMC workspaces?
one possibility is that the AMC agent was configured to Exclude Internet Service Monitor or Web response Time or Robotic Response Time data. it can be a synchronization issue, or a performance issue of the AMC agent
7. Why I can't start the AMC Configuration Editor from TEP after clicking on its icon from the menu bar of icons (or CTRL+A)?
this issue can have multiple origins....
7.1 one origin can be a conflict between ITCAM for Application Diagnostics (yn) application support (and/ or ITCA
- if you are using yn app support v 7.2.0.x where x<5, and have not deployed yet yn app support v188.8.131.52 , see :
- if you have deployed already yn app support v184.108.40.206, and use AMC app support V220.127.116.11.x where x < IFix11 see :
Resigned jar files for AMC are included in the following interim fix: 7.4
Solution : Make sure Application Support version on a
7.2 only the AMC agent application support was installed, but no other ITCAM4Tx agent application support was deployed yet.
this leads to an error message when you try to start the AMC editor stating "no
For example, for
7.3 if the the AMC Configuration Editor icon is missing from the TEP client menu bar,
it's generally because there is a mismatch between AMC agent version and AMC application support version, see 2. above
or it can be that the AMC application support has not been installed at all, in particular on TEPS or TEP.
For example, when installing the TEPS Desktop application support for AMC agent, also choose the option to install the 'Browser Client' application support as well.
Particularly relevant on Unix environment, see :
with message :
8.1 Check on the robotic response time agent, in BWM\
8.2 Try and stop and
Review the T6 TEMA log (<IT
Try and reconfigure the T6, and possibly connect it first to the HUB TEMS, then verify if the issue is still seen.
9. TEP AMC "Transaction Availability Analysis" workspace or "Transaction Response time Analysis" workspace shows partial or no data at all in historical data views (last 8 Hours), like in 'Transaction Response Time' view, 'Application volume' view, or 'Transaction Availabilty view
Check if you also see the following symptoms :
- AMC T3 agent TEMA log (*_t3_*.log) shows error message like, as an example :
ERROR MESSAGE: "Unable to open Metafile "/op
Example of TEP AMC views where historical data are missing :
Solution : If AMC version currently used is V18.104.22.168 (7.4 fp1) This issue is addressed with :
APAR # IV77635 "T3 NEEDS TO RETURN ALL DATA FOR HISTORY REQUEST"
included in 7.4.0. 1-TIV-CAMRT-IF0011. see :
10. AMC kt3agent doesn't start on AIX
T3 TEMA log *t3*.log file ends with the following error messages