We have requirement for monitoring one the vendor application being used by customer.
The App details are:-
Tivoli Application Dependency Discover Manager(184.108.40.206)
JRE version IBM 1.7+
Red Hat linux 5.x +
CA APM environment is 10.7 SP3 Deployed.
Is it possible to to monitor via CA APM ?
Amit Singh Bisht
Converting to a Discussion since this a custom monitoring issue. Looking at https://www.ibm.com/support/knowledgecenter/en/SSPLFC_7.3.0/com.ibm.taddm.doc_7.3/AdminGuide/c_cmdb_overview.html
It appears to be a database tool
IBM® Tivoli Application Dependency Discovery Manager (TADDM) is a configuration management tool that helps IT operations personnel ensure and improve application availability in application environments. TADDM provides the details of configuration items (CIs) using automated, agentless discovery of assets and their application dependencies, and it includes a discovery library technology to help leverage data from other
What do you want to monitor? Can this be done with the Infrastructure Agent or is are theer Java calls involved.
It consist of both DB and app servers.
Can't we do it using default agent or default java agent ?
Please find below the java component being used by application.
Yes m you should be able to do a lot of that with the default Java agent
But the problem is it using JRE version IBM 1.7+.
So what will be your suggestion ?
IBM Java 1.8 is Supported for some agents. See https://pcm.ca.com/overview.php?mod=overview&solution=apm10.7.x
With any IBM JDK, we have found it is best to use AgentNoRedefNoRetrans.jar and IntroscopeAgent.NoRedef.profile, we are still supporting back down to Java 1.6 with the current agent.
There is no specific monitoring for this application, so you can use default pbls for this, if it is going straight for production, default-typical.pbl is safest, if you want to see what can be retrieved, you can try the default-full.pbl but it could cause the application to be slower or even fail.
Essentially, our Java agent is looking to monitor the container of the application, then any components running in the container that are designed to J2EE standards, and other basic parts of the Java framework.
We can also suggest this site curated by a colleague here, if you upload an AutoProbe log from the application, it will scan the logs to look for any other known extensions that could bring extra visibility into the application.