APM Top 20 Accessed KB Articles and Documents for August 2013

Discussion created by Hallett_German Employee on Sep 4, 2013
Latest reply on Sep 6, 2013 by MaryGreening
[left]APM Top 20 Accessed KB Articles and Documents for August 2013[left]
1. CA APM 9.1.6 Readme (m003591e)
2. CA APM 9.1.7 Readme (m003661e)
3. CA APM 9.1.4 Readme (m003551e)
4. CA Application Performance Management Release Notes (m003531e)
5. CA Application Performance Management Readme (m003401e)
6. CA Application Performance Management Readme (m003541e)

[left]KB Articles[left]
1. How to create the APM db in Oracle 11gR2
2. How to Configure CA APM to use LDAP Authentication (Introscope and APM CE)
[left]CA APM gives you choices for securing and authorizing access to some or all of the features and domains of the Enterprise Manager and Workstation. Using LDAP, you can authenticate user and group access with CA APM while maintaining user and group authorization in local configuration files.

There are 3 ways to secure CA APM

1) Local - Users and groups are both authenticated and given authorization via local configuration files maintained on the Enterprise Manager server.

2) LDAP - Users and groups are authenticated by LDAP directories but authorized by local configuration files maintained on the Enterprise Manager server or CA EEM.

3) EEM - Users and groups are both authenticated and authorized by a CA EEM (CA Embedded Entitlements Manager) server for CA APM activities.

This article discusses how you can integrate CA APM with your own LDAP directory for authentication to the APM Workstation and Enterprise Manager.

3. Agent keeps disconnecting from collectors and tries to connect to the other collectors, mom and the interfaces and it is failing to reconnect.
[left]Description:Agents disconnect and fail to reconnect to the configured primary and secondary Enterprise Manager (collectors) defined as Locations and Names in IntroscopeAgent.profile (introscope.agent.enterprisemanager.connectionorder property) hostname and port, it is trying all other interface names to the same server and ports on which the EMs are listening and it is failing to connect because of firewall or network issue:

[WARN] [IntroscopeAgent.ConnectionThread] Failed to re-connect to the Introscope Enterprise Manager at

You might have different interfaces on the EM servers and more than EMs running on different ports.
How can you avoid the Agents trying alternate names and ports?
4. How to enable Agent 9.1 JMX with Jboss 5.1 and enable the Thread and JDBC graphs available from the new Resources tab
[left]Description:None [left]
5. How to implement CA EEM and LDAP for Authentication and Authorization of CA APM
[left]Description:Using CA EEM, CA Embedded Entitlements Manager, in conjunction with a supported LDAP Server, it is possible to eliminate manual updates to CA APM configuration files every time you need to add a new user, change a password or update access permissions.

CA EEM allows you to utilize a supported LDAP server for authentication while it controls authorization policies for LDAP users and groups. If you do not use LDAP, EEM can even perform authentication duties using the secure, proprietary CA Directory, which is included.

CA EEM is bundled with CA APM and is available from the APM Product Downloads Page on support.ca.com. It can be installed on the same or a separate server as the Enterprise Manager.. CA EEM supports many CA products, serving as a single point of control for authentication and authorization.
6. Upgrading to Introscope r9.0.5.0 from CEM r4.5.6.1
[left]Description: Trying to upgrade to Introscope r9.0.5.0 from CEM r4.5.6.1.
7. Can a 9.1.x.x TIM be upgraded to a later 9.1.x.x service pack or 9.5 without needing to reinstall the RHEL 5.x operating system?
[left]Description: The Installation and Upgrade Guides for 9.1.x and 9.5 advise that an Operating System install step is required for TIM upgrades.
Is this necessary if the TIM is already at 9.1.x.x and therefore already running under RHEL 5.x?
8. Can the new 9.1.x Thread Dump feature be run from the Command Line Workstation to enable alert triggering of a thread dump using a shell action.
[left]Description: The 9.1.x Command Line Workstation (CLW) can be used to generate a thread dump, but this feature has not yet been formally documented because it was originally unsupported. Development has since confirmed it is supported and the documentation will be updated in the near future. In the meantime the relevant information is detailed below.
9. PATCH:: What's new in CA APM 9.0.8
[left]Description: These fixed issues are related to Introscope, extensions, and PowerPacks.[left]
10. SERVICE PACK::9.1.5
[left]Description:These fixed issues are related to Introscope, extensions, and PowerPacks.[left]
11. SERVICE PACK::9.1.6
[left]Description: What is fixed in 9.1.6[left]
12. Troubleshooting a 9.1.x .Net Agent Installation
[left]Description:This article will discuss basic steps that can be taken to troubleshoot a 9.1.x .Net installation.[left]
13. Troubleshooting Common EM Performance Problems ( Legacy KB ID WLY 1300 )
[left]Description:Common Network,Smartstor, Memory, and CPU Tips[left]
14. Why am I being requested to provide a SSLDump/packet capture (PCAP) for the TIMSoft/MTP?
[left]Description: Technical Support has just requested a SSLDump/packet capture for my TIM. What are they planning to do with this file? [left]
15. .NET agent instrumentation - dlls loaded twice
[left]Description: The customer has installed v8.1.1.0 .NET Agent previously and it appeared to instrument the .NET 2.0 app ok based on the saved log files. Later, customer experienced some high CPU issues and upgraded to per recommendation. He used nativeprofiler option and was getting errors. He switched to autoprobe option and still had problem instrumenting the .NET 2.0 app with no autoprobe log and agent log generated and finding of same dlls loaded twice in the w3wp.exe process. [left]
16. Agents Shown in Collector EMs But Not in MOM ( Legacy KB ID WLY 1329 )
[left]Description:Why are some agents shown in the Collector EMs, but not in the MOM? [left]
17. APM 9 Agent memory leak caused by Socket Tracer ( Legacy KB ID WLY 2906 )
[left]Description: After APM 9 Agent installation, the JVM heap size keeps increasing. One finding common from these dumps with the memory leaks is that one java.lang.ThreadLocal.ThreadLocalMap object accounts for a huge amount of retained heap memory and this object holds a large array of java.net.ManagedSocketOutputStreamHighPerformance objects.[left]
18. AutoProbe Connector ClassLoader Error ( Legacy KB ID WLY 2225 )
[left]Description: When trying to run the CreateAutoProbeConnector command, the following error appears:

In Unix, AIX, or Linux: "Unable to determine the identity of the JVM: Unable to locate the java.lang.ClassLoader classfile."

In z/OS: "Failed to complete iconv_open() setup"

In SAP systems: "JVMJ9VM015W Initialization error for library jclscar_23(14): JVMJ9VM009E J9VMDllMain failed. Could not create the Java virtual machine"[left]
19. CA APM Technical Advisory: APM/Introscope 9.1.x Agent Transaction Structure Memory Leak
[left]Description: CA Technologies has identified a memory leak issue with CA APM/Introscope 9.1.x agents that can have an operational impact for our customers. This technical advisory describes the affected versions and platforms in more detail, and explains the workarounds or remediation actions that are recommended to prevent this issue from impacting your application environments.
20. Can I change the way Introscope displays Perfmon Process names with Perfmon metric collection?
[left]Description: For instances where there are more than on process with the same name it may be helpful to change the way Procmon displays its process names. Can I do this?