18.4 Changing the Default JVMD End Point for Hybrid Cloud Gateway Agents

The deployed Hybrid Cloud JVMD Agents use the Hybrid Cloud Gateway Agents to communicate with an on-premise JVMD Engine. The JVMD Engine that is deployed by default with the 13c OMS is marked as the default end point for all the Hybrid Cloud Gateway Agents deployed in your enterprise. This means that, effectively, all the deployed Hybrid Cloud JVMD Agents will report to the JVMD Engine that is marked as the default end point. To change the default end point to a different JVMD Engine, or to a load balancer that is configured in your enterprise, follow these steps:

1. From the Setup menu, select Middleware Management, then select Application Performance Management.
2. Select JVM Diagnostics Engines, then click Configure.
3. Select the Hybrid Gateways Configuration tab. Click the edit icon displayed against JVMD default end point URL.
4. If you want to set the default end point to a load balancer that is configured in your environment, select Load Balancer URL, then specify the required value. If you want to set the default end point to a different JVMD Engine (that is, different from the default end point), select JVMD Engine, then select the required JVMD Engine from the drop down list.

   Note:

   Typically, all the Hybrid Cloud Gateway Agents deployed in your enterprise are configured for JVMD and are marked with the default JVMD end point. In case a particular Hybrid Cloud Gateway Agent is not marked with the default JVMD end point, select it from the list displayed in the Hybrid Gateways section, then click Update.