Complete the Upgrade
Contents
apmdevops97
Contents
After the upgrade finishes, complete the following tasks before you start the Enterprise Manager. These tasks complete the upgrade.
For support with customizations to PBDs, EPAgent scripts, or JavaScript calculators, contact CA Technologies Professional Services.
Follow these steps:
- Transfer the custom .JAR files that are in the Enterprise Manager or WebView classpaths.If your previous Introscope installation included the following updates, restore them:
- Custom .JAR files on your Enterprise Manager
- WebView classpath in the LAX or CONF files
EM_Home>/backup/<iscXx>. <iscXx> is the release number of the old installation, for example, isc71P8. The upgrade backs up various property files to <EM_Home>/backup/<iscXx> for your convenience during post-upgrade tasks. These files provide an easy way for you to review your previous configurations.The backup/<iscXx> folder is organized like the Introscope root directory. For example:- .conf and .sh files are in backup/<iscXx>
- Properties files are in backup/<iscXx>/config
- System ProbeBuilder directives are in backup/<iscXx>/config/systempbd.
You cannot use these files to roll back an upgrade. The files are not a substitute for making a full backup of your Enterprise Manager before upgrading. - Transfer the property file comments.If your old installation property files include comments that you want to retain, restore them. Add the comments to the property files in your new installation.
- Restore the customizations to management modules.If you added business logic to the examples/SampleManagementModule.jar file in your previous installation, the upgrade has overwritten it with the new examples/SampleManagementModule.jar file. Restore your custom information manually from the backup file that was saved in backup/iscXx/examples.
- To see the new dashboards added in latest version, copy the management module jar files from:<EM_Home>\config\modules-upgrade<version>to:<EM_Home>\config\modulesThe new dashboards are available in SampleManagementModule.jar. If you have defined any elements from the previous release, deploy the new version of SampleManagementModule.jar and recreate the elements.
- Transfer customized system PBD files.If you installed ProbeBuilder with your Enterprise Manager and you customized any system PBD files, place the customized files in the new hotdeploy directory. You do not need to update the Agent.profile file.For more information, see theCA APM Java Agent Implementation GuideorCA APM .NET Agent Implementation Guide.
- Recreate application triage map alerts.
- If you have configured direct agent to Collector connections in the IntroscopeAgent.profile file, configure the agent Collector connections in loadbalancing.xml.The MOM can now redirect directly connected agents from overloaded Collectors to other Collectors.
- If you want a Workstation to be located in your Enterprise Manager directory, reinstall it now.The Workstation must be the same release number as the Enterprise Manager in the installation directory.
- Restart the upgraded Enterprise Manager.
Recreate Application Triage Map Alerts
Perform the following steps before you upgrade.
Follow these steps:
- Make an extra backup copy of the initial version of the TriageMapConfigurationsManagementModule.jar file. Put this backup copy in a location other than the <EM_Home>/modules or <EM_Home>/modules-backup directory. Having an extra backup copy helps ensure that it is not overwritten when you change the Triage Map Management Module from the Introscope Workstation.
- Re-create any application triage map alerts or metric groupings in the application triage map directly. The existing application triage map alerts and metric groupings are not upgraded automatically.For information about editing application triage map alerts, see theCA APM Workstation User Guide.
- Disable the old alerts and metric groupings if they are still active and you have created ones in the application triage map.
Configure Agent to Collector Connections
When any Collector gets overloaded, the MOM can disconnect and redirect any agents to rebalance the cluster. The MOM uses weighting properties and loadbalancing.xml to handle the load balancing. To avoid the MOM disconnecting and redirecting the agents, define the agent to Collector connections in loadbalancing.xml. Optionally you can configure the MOM host name or IP address in IntroscopeAgent.profile to allow the MOM to load balance the agents.
If you require agents to connect only to specific Collectors, make this configuration using load balancing.xml.
If you have agent to Collector connections defined in the IntroscopeAgent.profile, you can run this CLW command:
autoprepare loadbalancing.xml
This command adds the agent to Collector connection information to the existing loadbalancing.xml file. Run the command beforeupgrading the agents.
Follow these steps:
- Upgrade the MOM and Collectors.
- Back up loadbalancing.xml.
- If there are existing configurations in loadbalacing.xml, navigate to the MOM <EM_Home>/config directory and back up the file.
The MOM deletes existing loadbalancing.xml comments when running the autoprepare loadbalancing.xml process. The MOM preserves the existing agent to Collector connection information. - Be sure that all agents that are configured in IntroscopeAgent.profile to connect directly to a Collector are running and connected to their Collectors.
- On the MOM computer, run the CLW command: autoprepare loadbalancing.xmlRun this command after the MOM and all the Collectors are upgraded to the current release and before the agents are upgraded. If you run the command after the agents are upgraded, the MOM cannot gather the former agent to Collector connection information.The MOM collects the runtime information about all the agents that are connected directly to the Collectors. The MOM populates the connection information at the bottom of loadbalancing.xml.If a Collector is stopped or is not connected to the MOM, the MOM cannot collect the agent connection information for that Collector. Loadbalancing.xml is not updated with that information.
- Optional: If a Collector is stopped or not connected to the MOM, update loadbalancing.xml using one of these methods:
- Manually add the agent-Collector information to loadbalancing.xml.
- Restore the loadbalancing.xml backup file and run the command again with all the agents connected to all the Collectors.
Agent Name | Collector Name |
AgentA | Collector01 |
AgentB | Collector01 |
AgentC | Collector02 |
AgentD | Collector02 |
AgentE | Collector03 |
AgentF | Collector03 |
The organization uses loadbalancing.xml to load balance an agent named EPAgent2.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <loadbalancing xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="loadbalancing0.1.xsd"> <agent-collector name="Example 1"> <agent-specifier>.*\|.*\|EPAgent2</agent-specifier> <exclude> <collector latched="false" port="5001" host="Collector02"/> </exclude> </agent-collector> <agent-collector name="Collector01@5001 auto-generated configuration"> <agent-specifier>HostName|ProcessName|AgentA</agent-specifier> <agent-specifier>HostName|ProcessName|AgentB</agent-specifier> <include> <collector latched="false" port="5001" host="Collector01"/> </include> </agent-collector> <agent-collector name="Collector02@5001 auto-generated configuration"> <agent-specifier>HostName|ProcessName|AgentC</agent-specifier> <agent-specifier>HostName|ProcessName|AgentD</agent-specifier> <include> <collector latched="false" port="5001" host="Collector02"/> </include> </agent-collector> <agent-collector name="Collector03@5001 auto-generated configuration"> <agent-specifier>HostName|ProcessName|AgentE</agent-specifier> <agent-specifier>HostName|ProcessName|AgentF</agent-specifier> <include> <collector latched="false" port="5001" host="Collector03"/> </include> </agent-collector> </loadbalancing>
Example 1 was a loadbalancing.xml entry before the Administrator ran the command. The MOM added the auto-generated entries after Example 1.