OCI and On-premises Windows

This section describes the steps to set up management and deploy plug-ins on an OCI or on-premises host running on Windows platform. JMS Fleets does not support Oracle Cloud Agent for OCI Windows. Hence, it is recommended to install Oracle Management Agent on all Windows platforms.

Prerequisites:

Download the agent software and response file as described in Download Management Agent Software and Manual Install sections.
For Windows 10 instances, the environment variable OVERRIDE_VERSION_CHECK is present and set to true to override Management Agent Service's version check. Management Agent Service supports only Java Management service on Windows 10 platform.

Steps

Go to the folder where you saved the management agent software and the response file.
Verify that the response file that you downloaded contains the following:
- Defined Tags in the format:
  [{"jms":{"fleet_ocid":"<fleet_ocid>"}}]
  
  where <fleet_ocid> is the OCID value of the fleet to which you wish to add the instance.
- JMS plug-ins parameters:
```
Service.plugin.jm.download=true
Service.plugin.jms.download=true
```
Also, ensure that the response file has read permissions for mgmt_agent user.
Install and start the management agent as described in Install Management Agents.
Note
- If the agent is already installed, proceed to the next step. If JMS plug-ins are not deployed yet, deploy Java Usage Tracking and Java Management Service plug-ins manually as described in the Deploy a Service Plug-in Using the Agents Page.
- The agent is installed with JMS lower telemetry frequency.
  In Windows 64 bit systems, you can change the parameter to MACS default telemetry frequency. Follow these steps to change the parameter:
  
  In command prompt, type NET STOP mgmt_agent to stop the agent if it is running.
  
  Replace the agent.json file located at C:\Oracle\mgmt_agent\agent_inst\config\destinations\OCI\services\Agent\1\types\ with the agent_high_freq.json file from C:\Oracle\mgmt_agent\$installedVersion\temp_interval\. Ensure that the name of the replaced file is agent.json.
  
  In the command prompt, type NET START mgmt_agent to restart the agent.
Log in to the host, open a command prompt as an administrator, and run the following commands:

Option 1: Generate usage tracker with standard functionality.
```
dir /b C:\Oracle\mgmt_agent\agent_inst\config\destinations\OCI\services\jms >%TEMP%\version.txt
set /p VERSION=<%TEMP%\version.txt
powershell -ep Bypass C:\Oracle\mgmt_agent\agent_inst\config\destinations\OCI\services\jms\%VERSION%\scripts\setup.ps1 --force
```
This script creates:
- usagetracker.properties in C:\Program Files\Java\conf
- usagetracker.log in C:\ProgramData\Oracle\Java
By default, the file usagetracker.properties contains the following lines:
```
com.oracle.usagetracker.logToFile = C:\\ProgramData\\Oracle\\Java\\usagetracker.log
com.oracle.usagetracker.additionalProperties = java.runtime.name
```
Option 2: Generate usage tracker with additional functionality to collect the user.name property for better identification of applications running in Application Servers like WebLogic and Tomcat.
Open the command prompt as administrator and run the following commands:
```
dir /b C:\Oracle\mgmt_agent\agent_inst\config\destinations\OCI\services\jms >%TEMP%\version.txt
set /p VERSION=<%TEMP%\version.txt
powershell -ep Bypass C:\Oracle\mgmt_agent\agent_inst\config\destinations\OCI\services\jms\%VERSION%\scripts\setup.ps1 --force --enable-user-name
```
This script creates:
- usagetracker.properties in C:\Program Files\Java\conf
- usagetracker.log in C:\ProgramData\Oracle\Java
By default, the usagetracker.properties file contains the following lines:
```
com.oracle.usagetracker.logToFile = C:\\ProgramData\\Oracle\\Java\\usagetracker.log
com.oracle.usagetracker.additionalProperties = java.runtime.name,user.name
```
For more information, see Enabling and Configuring Java Usage Tracker.
Verify the installation, as described in Verify the Management Agent Installation.
Optional. Specify how frequently the management agent will report data to JMS Fleets and which file system paths on the host will be scanned to discover Java Runtime installations. See Modifying a Management Agent Settings.

The log files are located in the C:\Oracle\mgmt_agent\plugins\jm\stateDir\log directory.

Oracle Cloud Infrastructure Documentation