I have to create a Java Agent package manually without using ACC.
1. What things I have to keep in mind before creating a Java Agent package?
2. What configuration has to be done in the packages?
3. All the agents are of different versions we have to upgrade all the agents to the latest 10.7 version.
The Packages should contain Profile file for JBoss, Websphere, Tomcat, Java Standalone, WebLogic.
This is a duplicate of [DUPLICATE]:Create a Agent package manually?? I made this into a Discussion since more of a best practice question.
Can you help Imran with this? This also sounds like a good blog/knowledge doc topic.
I would say to begin with downloading the the 10.7 agent from support.ca.com and verify differences in the settings used in your IntroscopeAgent.profile in your current agents. App teams may have customized settings such as for agent & process naming, URL groupings, clamping, trace settings, SQL, JMX & PMI, .pbd's and smart instrumentation. This will also give you insight into any custom/extensions that may be required or no longer supported/required like an old powerpack.
I personally prefer to try the default agent for a new version first before modifying settings (other than agent & process naming) since the agent is continuously refined and tuned. For instance, URL groupings used to have only "default" enabled, but now they are enabled for several segment URL in the 10.7 default agent and are supported in Team Center as Experiences. Therefore, carrying over old settings may not always be best.
HTH get your started.
how can we create an Agent package manually without using ACC??
Without ACC you just have to download the required agent files package from support.ca.com.
Then customise agent profile, pbds etc to your requirements per Janelle's advice above.
NOTE: In 10.7 there is no Java agent installer so only "NO INSTALLER" file deployments exist
e.g. From DOWNLOAD MANAGEMENT product field enter: "CA Application Performance Management Agent (APM/Wily/Introscope)"
Click on the link for "Product Downloads Available"
Then click on "CA Application Performance Management Java and .NET Agent MULTI-PLATFORM"
e.g. for latest 10.7 Service Pack 2 (SP2)
You either download the DEFAULT AGENT agent package, a specific AppServer AGENT package, or "INTROSCOPE JAVA AGENT FILES FOR ALL APPLICATION SERVERS-NO INSTALLER" which will have all files for all AppServers and you just use the AppServer specific profile file that is provided for each.
Only if you need to add extension bundles do you then have to add them manually to what you have from above instead of using ACC:
Agent Extensions - CA Application Performance Management - 10.7 - CA Technologies Documentation
Hope that helps
What if I have 1000 agents in my environment it will be a lengthy process if it has to be done manually...is there another way to we create an agent package??
You are really only creating the agent package "once" meaning you can reuse that agent across environments and apps (typically) though this can vary depending on your application landscape. I would start with the all app server agents (download) for each of the platforms you mentioned. You will see differences between each. For instance, Tomcat will have JMX metrics captured enabled by default whereas Websphere you would use PMI. And both are optional, tho enabled by default.
As for deployment, it really depends on your target environment as to whether something like ansible scripts or what type of automation would be most appropriate.
The benefit of using ACC is that it will allow you define the agent packages, verify where they are deployed (if you choose to use that controller option) and facilitate version control for you. If you use the controller, some remote changes can be handled from ACC, which is a bonus.
Retrieving data ...