Oracle Cloud Infrastructure Documentation

Upgrading the Agent and Updating Java

Oracle recommends using the latest versions of agent software and JMS plug-ins to access the latest functionality and security vulnerability fixes.

Oracle Management Agent

See Upgrade Management Agents for the detailed procedure. It is recommended to Enable Auto Upgrade of OMA. Java Management Service plug-in is automatically updated.

Oracle Cloud Agent

See Updating the Oracle Cloud Agent Software for the detailed procedure. Java Management Service plug-in will be updated along with the OCA update.
Note

Re-running the installer or installation script on a system with an existing agent may result in an agent update.

Updating Java used by Oracle Management Agents

Oracle Management Agents require JDK 8 for their functioning. Guidelines for updating Java used by the agents can be found in Using Java with Management Agent.

Note

Java Runtime Lifecycle Management operations cannot be used on Java runtimes used by the agent.

Upgrading the Agent and Updating Java using Oracle Management Agent Bundle

When you run a new OMA installer on an instance with OMA already installed, the installer can update the JDK 8 used by the agents and upgrade the agent version as well.

To update JDK 8 and the agent, download the OMA installer bundle as mentioned in Download Oracle Management Agent Software Installer with Requisite Software. Ensure that you have downloaded JMS_Configuration.rsp file and placed in the same level as the compressed file. Run the setup JMS bundle:
  • In Linux: sudo ./setupJMS.sh
  • In Windows: Right click setupJMS.ps1 and select Run with Powershell.
  • In macOS: sudo ./setupJMS.sh

The JDK 8 and the agent upgrade differs based on the existing installation. Consider the following scenarios:

Scenario 1: Existing installation was done by JMS's OMA installer

If the existing OMA installation in the instance was done by JMS's OMA installer, the JDK 8 used by the agent will be installed in the management agent's installation folder. When the OMA installer is re-run in this instance, the installer will check for the latest versions of both JDK 8 and the agent. If either one or both are outdated, the installer will update the outdated components.

Scenario 2: Existing installation was done using JMS's installation script

If the existing OMA installation in the instance was done by JMS's installation script, the agent would have a symlink that points to the JDK installed directory on the instance. When the OMA installer is executed in this instance, the installer will install JDK 8 in the management agent's installation directory, which will then be used by the agent, updating the existing symlink. The installer will also upgrade the agent if a newer version is available.

Scenario 3: Existing installation was done by MACS's OMA installer

If the existing OMA installation in the instance was done by MACS installer, the agent would have a path or symlink to a JDK 8 directory on the instance. When the OMA installer is executed in this instance, JMS will ignore the JDK update and upgrade the agent if a newer version is available. If the user had provided a symlink that resolves to the JDK installed directory on the instance, an update can be done to the JDK 8. To update JDK 8, the installer must be run with the parameter jms.override-jdk-symlink = true added to the JMS_Configuration.rsp file. The installer will then install JDK 8 in the management agent's installation directory, updating the existing symlink.