Upgrade Java Agent
-
Read the Release notes for information about changes in Java Agent.
-
Back up the directories for the agent installation and the web application container configuration:
-
$ cp -r /path/to/java_agents/agent_type /path/to/backup $ cp -r /path/to/tomcat/webapps/agentapp /path/to/backup -
In remote configuration mode, back up as described in AM’s Maintenance guide.
-
-
Redirect client traffic away from the protected web application.
-
Stop the web application container where the agent is installed.
-
Remove the old Java Agent, as described in Remove Java Agent.
-
Install the new agent, as described in Install Java Agent.
The installer creates new
AgentConfiguration.propertiesandAgentBootstrap.propertiesfiles, containing properties for the agent version. -
Review the agent configuration:
-
In local configuration mode, see the
AgentConfiguration.propertiesfile. Use the backed-up copy of the configuration file for guidance, the agent’s Release notes, and AM’s Release notes to check for changes. Update the file manually to include properties for your environment.The
AgentBootstrap.propertiesfile created by the installer contains bootstrap properties relevant to the new version of the agent. -
In remote configuration mode, review the agent’s Release notes and AM’s Release notes to check for changes. If necessary, change the agent configuration using the AM admin UI.
-
-
Secure communication between AM and the agent with appropriate keys. For information, see Configuring AM servers to communicate with Java Agents.
-
Start the web application container where the agent is installed.
-
Check that the agent is performing as expected. For example, navigate to a protected page on the website and confirm whether you can access it according to your configuration.
-
Allow client traffic to flow to the protected web application.