Set up the Agent and JMS Plug-in for Non-OCI Environments

If your environment is on-premises or on a third-party cloud, then review this section to setup the agent and deploy the JMS plug-in by using the JMS Agent Installer.

For Oracle Linux hosts that are on-premises or on a third-party cloud, the JMS plug-in is deployed through Oracle Management Agent. Oracle Management Agent (OMA) is installed on a host machine. It can connect to Oracle Cloud Infrastructure (OCI) directly using the Management Agent cloud service. JMS is provided as a service plug-in to collect data from the host where you install the Management Agent.

There are two possible options for enabling JMS plug-in on such hosts:

Installation using the JMS installation script with Management Agent software.
For installation with JMS installation script, you must have the latest Oracle JDK 8 installed on your machine before you proceed.
Installation using JMS Agent Installer with the JMS_agent_configuration.rsp file.
The JMS Agent Installer comes with the latest version of Oracle JDK 8 and Management Agent software. You do not need to pre-install Oracle JDK 8 on your machine as the JMS Agent Installer manages this for you.

This solution uses the JMS Agent Installer.

Download Agent Installer Software

Download the JMS Agent Installer version for your Oracle Linux instance. The download includes an installer file and a configuration file.

Open the navigation menu and click Observability & Management, and then click Fleets under Java Management.
Select the fleet that you created earlier.
Click Download Agent Installer.
Select and download an appropriate Oracle Linux version of the Agent Installer for your host's architecture.
The following files are downloaded on the machine that you're carrying out the operation from:
1. jms_setup_version-number_os-type.tar.gz installer file
2. JMS_agent_configuration.rsp configuration file
Click Close.

Install the Agent Installer Software and Deploy the Plugin

Install the software and deploy the plugin on your Oracle Linux host.

Transfer the downloaded Agent Installer file (jms_setup_version-number_os-type.tar.gz) and configuration file (JMS_agent_configuration.rsp) to your Linux host.
You can use the following sample command to transfer the Agent Installer and configuration file to your host machine.
```
scp -r -i path-to-private-key/your-private-key-file path-mgmt-agent-installer/your-mgmt-agent-installer path-agent-configuration/JMS_agent_configuration.rsp username@x.x.x.x:copy-to-path
```
Connect to your host. Extract the Agent Installer and copy the configuration file to a common directory.
In the following example, jmsInstaller is the common directory.
```
mkdir ./jmsInstaller && cp JMS_agent_configuration.rsp ./jmsInstaller && tar -xvf your-mgmt-agent-installer.tar.gz -C ./jmsInstaller
```
Navigate to the common directory and verify that the Agent Installer is uncompressed to the same directory as the configuration file. Once verified, run the installJMSAgent.sh script using the following command:
```
sudo ./installJMSAgent.sh
```

When the installation is successful, you'll see a message similar to the following:

 ...
 Agent was successfully registered using key name-of-fleet(ocid1.managementagentinstallkey.oc1.region.some ocid hash).
 Instance has been assigned to JMS fleet name-of-fleet(ocid1.jmsfleet.oc1.region.some ocid hash).
 A copy of this installation log can be found at /path-to-log/JMSInstallScript/JMSInstallScriptLogs-Datestamp-Timestamp-log-number.log
 Removing the temporary files.
 The JMS installer and configuration file can be removed from the machine.
 /path-to-log/JMSInstallScript/JMSInstallerLogs-Datestamp-Timestamp-log-number.log contains the install log.
 Agent is successfully installed and is running.

Verify the Installation and Deployment

Verify the Management Agent installation, plugin deployment, and that the managed instance is associated with the fleet.

Verify the Management Agent installation.
1. In the Oracle Cloud Console, open the navigation menu, click Observability & Management, and then click Agents under Management Agent.
2. From the Agents list, look for the agent that was recently installed. This agent should be in the Fleet_Compartment compartment created in previous section. The Availability of the Agent should be Active.
Verify the JMS Plug-in deployment.
1. In your agent, click Deploy plug-ins and confirm that the Java Management Service plug-in box is checked..
Verify the successful association of the managed instance to your fleet.
1. Navigate to the fleet that you created earlier, then click the inventory log object.
2. In the Fleet Inventory log page, under the Explore Log section, is a new log entry jms.agent.plugin.start.log.
  The new log entry has been emitted from your newly associated managed instance to your Fleet Inventory log.