You can select the Subcompartments check box, near the compartment selector drop-down to get an overview of the agent details across the selected compartment and it's child compartments.

The Overview page provides summary information about the Management Agents and Management Gateways in your environment and consists of the following charts:

The following screenshot is an example of the Management Agents Overview page.

• Agents and Gateways
  • Agent Details
  • Gateway Details
• Agents with DataSource

Agents and Gateways

The Agents and Gateways page displays a table listing all the Management Agents and Management Gateways installed.

The table consists of the following columns:

The following screenshot is an example of the Agents and Gateways list.

You can click on a specific agent or gateway to open up the details page and quickly go and get more information.

• Agent Details
• Gateway Details

Agents Details

The Agents Details page shows information about the selected agent.

• Use Deploy plug-ins to deploy a plug-in on the selected agent.

• Use Enable Agent Logs to enable Logging Analytics service to gather Management Agent log files for the selected agent. For information, see Enable Agent Logs.

• Use Manage DataSources to view or edit properties and dimensions of the datasource type configured with the selected agent. For information, see Manage DataSources.

• Use More actions to Add tags or Delete an agent.
• The Agent Information tab shows detailed agent information. It displays the host name, compartment name, agent version, operating system, service plug-ins deployed on it, work requests, datasoruces and more.

  • Service Plug-ins: Use the Service Plug-ins link to list all the service plug-ins deployed on this specific Management Agent. For more information, see Deploy Service Plug-ins.
  • DataSources: Use the DataSources link to list all the datasources configured on this specific Management Agent. For more information, see Manage DataSources.

Gateway Details

The Gateway Details page shows detailed information about a gateway.

The Gateway Information tab shows detailed gateway information. It displays the host name, compartment name, gateway version, operating system, associated agents and more.

Associated Agents: Use the Associated Agents link to list all the Management Agents configured to use this specific Management Gateway. The Associated Agents pane displays the id, host, availability and operating systems information of the Management Agents.

Agents with DataSource

The Agents with DataSource page displays a table listing all the agents with datasources configured.

You can click on a specific agent to open up the details page and quickly go and get more information.

You need to create an install key before installing Management Agent.

An install key is issued against your identity domain and validates the authenticity of the installation. Ensure you create the install key before starting the Management Agent installation.

To create an install key:

1. On the Management Agents home page, click Download and Keys from the left menu to view the Install Keys pane.

   The Install Keys pane displays at the bottom of the page.

2. On the Install Keys pane, click Create Key to create a key.

3. Enter the required details in the Create Key window.

   1. In the Key Name field, specify a name to identify the key.

   2. In the Compartment field, select the compartment from the drop-down list. This is the compartment where the agent resource will be created.

   3. In the Maximum Installs field, specify a number that indicates the maximum number of installs that can be associated with the key. Default value is 1000.

   4. In the Valid for field, specify a number that indicates the period the key is valid for. The default value is 1 week.

   5. The Unlimited checkbox is optional.

      If it's selected, the key can be used for an unlimited number of agent and gateway installations and the key never expires.

      Risks of using unlimited keys: Oracle recommends to keep the life time of an Install Key to a minimum required time and limited number of agents. Ensure that you keep the downloaded key in a secure location to protect confidentiality. If the unlimited install key is compromised, an attacker can install rogue agents in your tenancy. A regular audit of your tenancy's agents can help to mitigate any potential risks associated with unlimited install keys. When an unlimited install key is not needed anymore, make sure to delete it either using the Management Agents Console or CLI.

   

   A new key is created.

The Install Keys pane offers different options available to manage the keys. During a later step, the Download Key to File option is useful to download a file that can be used as a response file template as described in Configure a Response File.

For more information about managing the install keys, see Manage Install Keys.

You can copy an install key to clipboard from the Install Keys pane.

The Copy Key to Clipboard option is useful to copy and paste the value of the key when creating the response file during the agent configuration process. For more details, see Create a Response File.

You can download an install key from the Install Keys pane.

The Download Key to File option is useful to download a file with the agent parameters that can be used as a response file during the agent installation process. For more details, see Create a Response File.

You can delete an install key from the Install Keys pane.

1. On the Management Agents home page, click Download and Keys from the left menu to open the Install Keys pane.

   The Install Keys pane is displayed listing all the existing keys.

2. From the list of install keys, select the key that you want to delete.

3. On the right side of the selected key, click on the action menu and select Delete Key.

   

4. Click on Delete Key.
5. Press Delete to confirm the operation.

The Delete Key option is useful when you suspect that an unauthorized user has obtained the value of an agent install key.

Management Agents service supports automatic upgrade.

Enabling the auto upgrade feature is done at the tenancy level: Users can enable auto upgrade for all management agents residing in their current tenancy.

Requirements:

Default Auto Upgrade Status: Disable.

Enable Auto Upgrade

You can enable auto upgrade using the Management Agents console.

• On the Management Agents home page, click Downloads and Keys from the left menu.

  The Agent Auto Upgrade pane is displayed at the top of the page.

  

• On the Agent Auto Upgrade pane, click Enable Auto Upgrade.

  The Enable Auto Upgrade window is displayed.

• On the Enable Auto Upgrade window, click OK to enable auto upgrade for all management agents in the current tenancy

Disable Auto Upgrade

You can disable auto upgrade using the Management Agents console.

• On the Management Agents home page, click Downloads and Keys from the left menu.

  The Agent Auto Upgrade pane is displayed at the top of the page.

  

• On the Agent Auto Upgrade pane, click Disable Auto Upgrade.

  The Disable Auto Upgrade window is displayed.

• On the Disable Auto Upgrade window, click OK to disable auto upgrade for all management agents in the current tenancy.

For a list of available CLI commands to enable and disable auto upgrade, see Oracle Cloud Infrastructure CLI Command Reference.

Management Agent supports manual upgrade for the following operating systems:

• Linux Manual Upgrade (RPM file)
• Linux Manual Upgrade (ZIP file)
• Windows Manual Upgrade
• Solaris Manual Upgrade
• AIX Manual Upgrade

Linux Manual Upgrade (RPM file)

Linux Manual Upgrade (ZIP file)

Windows Manual Upgrade

Solaris Manual Upgrade

AIX Manual Upgrade (ZIP file)

The agent's credential store can store credentials that are known and understood by the agent (for example, Oracle Database credentials), as well as credentials which are only understood by the specific service. The agent validates built-in credential types, but it also accepts other free-form types without any validation.

To add credentials or update existing ones, use the credential_mgmt.sh script with the upsertCredentials operation.

The credential_mgmt.sh script is located in the /opt/oracle/mgmt_agent/agent_inst/bin directory.

Syntax

credential_mgmt.sh -o upsertCredentials -s [service-name]

1. Create a JSON file with the credential information.

   The below example is a credential type format for a datasafe_db source named orcl123:

   {"source":"datasafe_db.orcl123", 
   "name":"audit_cred", 
   "description":"This is the audit credential for orcl123 Oracle RDBMS system.", 
   "properties":[ 
   {"name":"username","value":"CLEAR[scott]"}, 
   {"name":"password","value":"CLEAR[tiger]"}]
   }

   For example, you can save the file as my_credentials.json.

2. Add credentials using a JSON file.

   credential_mgmt.sh -o upsertCredentials -s [service-name]

   For example, you can run the following for DataSafe service using my_credentials.json file:

   cat my_credentials.json | sudo -u mgmt_agent /opt/oracle/mgmt_agent/agent_inst/bin/credential_mgmt.sh -o upsertCredentials -s datasafe

3. Delete JSON file created in step 1.

   The credential JSON file contains sensitive information. Customers are responsible for deleting the credential JSON file after completing the add or update credential operation.

To delete credentials, use the credential_mgmt.sh script with the deleteCredentials operation.

The credential_mgmt.sh script is located in the /opt/oracle/mgmt_agent/agent_inst/bin directory.

Syntax

credential_mgmt.sh -o deleteCredentials -s [service-name]

1. Create a JSON file using the following format:

   {"source":"datasafe_db.orcl123"
    "name":"audit_cred"} 

   For example, you can save the file as my_credentials.json.

2. Delete credentials using a JSON file.

   credential_mgmt.sh -o deleteCredentials -s [service-name]

   For example, you can run the following for DataSafe service using my_credentials.json file:

   cat my_credentials.json | sudo -u mgmt_agent /opt/oracle/mgmt_agent/agent_inst/bin/credential_mgmt.sh -o deleteCredentials -s datasafe

3. Delete JSON file created in step 1.

   The credential JSON file contains sensitive information. Customers are responsible for deleting the credential JSON file after completing the delete credential operation.

To add a credential alias or update an existing one, use the credential_mgmt.sh script with the aliasCredentials operation.

The credential_mgmt.sh script is located in the /opt/oracle/mgmt_agent/agent_inst/bin directory.

Syntax

credential_mgmt.sh -o aliasCredentials -s [service-name]

1. Create a JSON file using the following format:

   {"alias":
    {"source":"datasafe_db.orcl123",
     "name":"audit_cred"},
    "credential":
     {"source":"datasafe_db.host.1521.orcl123",
      "name":"datasafe_cred"}}
   

   For example, you can save the file as my_credentials.json.

2. Add a credential alias using a JSON file.

   credential_mgmt.sh -o aliasCredentials -s [service-name]

   For example, you can run the following for DataSafe service using my_credentials.json file:

   cat my_credentials.json | sudo -u mgmt_agent /opt/oracle/mgmt_agent/agent_inst/bin/credential_mgmt.sh -o aliasCredentials -s datasafe

3. Delete JSON file created in step 1.

   The credential JSON file contains sensitive information. Customers are responsible for deleting the credential JSON file after completing the add or update credential alias operation.

To delete a credential alias, use the credential_mgmt.sh script with the unaliasCredentials operation.

The credential_mgmt.sh script is located in the /opt/oracle/mgmt_agent/agent_inst/bin directory.

Syntax

credential_mgmt.sh -o unaliasCredentials -s [service-name]

1. Create a JSON file using the following format:

   {"source":"datasafe_db.orcl123",
    "name":"audit_cred"}

   For example, you can save the file as my_credentials.json.

2. Delete a credential alias using a JSON file.

   credential_mgmt.sh -o unaliasCredentials -s [service-name]

   For example, you can run the following for DataSafe service using my_credentials.json file:

   cat my_credentials.json | sudo -u mgmt_agent /opt/oracle/mgmt_agent/agent_inst/bin/credential_mgmt.sh -o unaliasCredentials -s datasafe

3. Delete JSON file created in step 1.

   The credential JSON file contains sensitive information. Customers are responsible for deleting the credential JSON file after completing the delete credential alias operation.

These instructions describe how to upgrade JRE on Linux 64-bit platforms, including the following: Oracle Linux, CentOS, Ubuntu and SUSE Linux.

This topic explains how to upgrade JRE on supported Windows 64-bit platforms to run Management Agent.

Management Agent installations on Windows environments require to set the environment variable JAVA_HOME prior to the installation. For details, see Update Custom JAVA_HOME for Windows environment to set the JAVA_HOME variable to a location that can be changed in the future.

To upgrade JRE on Windows, do the following:

There are environments that don't have a system default Java location. In those cases, Oracle recommends updating the custom JAVA_HOME location before starting the JRE upgrade process.

When using a custom JAVA_HOME location for the Management Agent installation, upgrading the JRE can cause issues if the Java version is included in the JAVA_HOME path. The solution is to create a symbolic link for the JAVA_HOME path which should make no reference to the JRE version number.

Problem: The above setup will result in JRE version confusion as the JAVA_HOME path refers to a value 'jre1.8.301' even though the actual JRE version after the upgrade is jre1.8.311.

Solution: Create a symbolic link with no version number included as part of it, and use it as the JAVA_HOME setting to install the Management Agent.