On-premises Linux

This section describes the steps to set up the Oracle Management Agent and deploy the JMS plug-ins on an on-premises Linux host.

Prerequisites: Download the agent software and response file as described in Download Management Agent Software and Manual Install sections.

Steps

Go to the folder where you saved the management agent software and the response file.

#To change ownership of the Java Management Service plugin to root
mgmt_agent ALL=(ALL)NOPASSWD:/opt/oracle/mgmt_agent/agent_inst/bin/chown_recursive_ep.sh
#To run the Java Management Service plugin under root user
mgmt_agent ALL=(root) NOPASSWD: ALL

Install and start the management agent, as described in Install Management Agents. The Java Management Service plug-in will be deployed during the installation.

Note

If the agent is already installed on the host, check if Java Management Service plug-in is deployed. If the JMS plug-in has not been deployed yet, deploy Java Management Service plug-in manually as described in the Deploy a Service Plug-in Using the Agents Page.
Verify the output from the setup script. If the console output indicates that the plug-in has failed to deploy, then ensure that the clock on your host is synchronized with the clock on the OCI platform. For more information, see Maximum Allowed Client Clock Skew.
Verify the installation, as described in Verify Management Agents on Compute Instances. You can identify your agent using the hostname of the host. Find the OCID of the agent in the Agent Id value in Agent information tab of the Agent's details page.
Register the agent to the JMS fleet by
1. In OCI console, using the fleet's Add Managed Instance(s) action in the Managed Instances view. If the host shows up in the Unregistered Managed Instances list, you can select it and add it to the fleet. It may take some time for the host to show up in the Unregistered Managed Instances list after the plugins are enabled. Alternatively, add the host using the OCID of the agent in the Manual registration section.
  OR
2. Using the OCI CLI command line:
```
oci jms jms-plugin create --fleet-id <fleet_ocid> --agent-id <agent_ocid> --compartment-id <agent_compartment_ocid>
```
  OR
3. Creating a registration.json file in the JMS plugin's configuration directory using the following:
```
{ 
"version": 1, 
"fleetId": "<fleetId>"  
}
```
  Replace "<fleetID>" with the OCID of the fleet to which you want to register the instance.
  
  Place the registration file under /etc/oracle/jms/auto-registration/registration.json
  
  Note
  
  The registration.json file is deleted when the registration succeeds.

The log files are located in the /etc/oracle/jms/auto-registration/registration.json directory.

Oracle Cloud Infrastructure Documentation