18 Deploying JVMD for Hybrid Cloud

This chapter describes how to deploy Java Virtual Machine Diagnostics (JVMD) Agents in a Hybrid Cloud setup. It consists of the following sections:

18.1 Overview of Deploying JVMD for Hybrid Cloud

Enterprise Manager Cloud Control offers Hybrid Cloud Management that enables you to monitor certain Oracle Cloud targets using an on-premise Enterprise Manager Cloud Control instance. Leveraging this feature, Enterprise Manager Cloud Control enables you to deploy JVMD Agents on your Oracle Cloud virtual hosts, which can report to a JVMD Engine deployed on-premise. Thus, you can monitor your Oracle Cloud JVM targets and diagnose performance problems in Java applications that are deployed in Oracle Cloud, using an on-premise Cloud Control instance.

For more information on the Hybrid Cloud feature, see Oracle Enterprise Manager Cloud Control Administrator's Guide.

The deployed JVMD Agent (on the Oracle Cloud virtual host) uses the Hybrid Cloud Gateway Proxy and a Hybrid Cloud Gateway Agent to communicate with the on-premise JVMD Engine. The Hybrid Cloud Gateway Proxy forwards communication from the JVMD Agent to the on-premise Hybrid Cloud Gateway Agent, which in turn forwards the message to the JVMD Engine and from the JVMD Engine back to the JVMD Agent. Reverse communication follows the same flow, that is, the Hybrid Cloud Gateway Agent forwards communication from the JVMD Engine to the Hybrid Cloud Gateway Proxy, which in turn forwards the message to the JVMD Agent.

Note that except cross-tier functions, all JVMD features are supported for a Hybrid Cloud setup.

18.2 Prerequisites for Deploying JVMD Agents on Oracle Cloud Virtual Hosts

Before deploying JVMD Agents on Oracle Cloud virtual hosts, ensure that you meet the following prerequisites:

18.3 Deploying JVMD Agents on Oracle Cloud Virtual Hosts

To deploy JVMD Agents on Oracle Cloud virtual hosts, follow these steps:

  1. From the Setup menu, select Middleware Management, then select Application Performance Management.

  2. On the Application Performance Management page, under the Application Performance Management Agents section, click Manage Diagnostics Agents.

  3. For Operation, ensure that Deploy is selected.

    If you select Expand All from the View menu, you can view the target name, target type, target host, target status, platform, and so on of all the discovered WebLogic Administration Servers and Managed Servers (part of all discovered WebLogic domains).

    Select the WebLogic Managed Servers on which you want to deploy JVMD Agents. Click Next.

  4. On the Target Credentials page, for each WebLogic domain, specify a value for Oracle WebLogic Administration Server Host Credentials and Oracle WebLogic Domain Credentials, then click Apply.

    Click Next.

  5. To deploy JVMD Agents on Oracle Cloud virtual hosts, select Configure Hybrid Mode, and specify the Hybrid Cloud Gateway Proxy host and port that you want to use. When you select Configure Hybrid Mode, the value for Available JVMD Engine is automatically set to Other, as the JVMD Agent connects to the Hybrid Cloud Gateway Proxy, which in turn connects to the JVMD Engine (via the Hybrid Cloud Gateway Agent).

    By default, all JVMD Agents deployed on Oracle Cloud virtual hosts will effectively report to the JVMD Engine marked as the default end point.

    To view the default JVMD end point for all the Hybrid Cloud Gateway Agents deployed in your enterprise, on the Application Performance Management page, select JVM Diagnostics Engines, then click Configure. Select the Hybrid Gateways Configuration tab. The default JVMD end point is displayed. For information on how to change the default JVMD end point for the Hybrid Cloud Gateway Agents deployed in your enterprise, see Section 18.4.

    Click Next.

  6. On the Review page, review all the information, then click Deploy.

    Once the JVMD Agent deployment is successful, you can verify the deployment by navigating to the Application Performance Management page, and viewing the Application Performance Management Agents section.

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.

18.5 After Deploying JVMD Agents on Oracle Cloud Virtual Hosts

After deploying JVMD Agents to your Oracle Cloud virtual hosts, verify the deployment as described in Oracle Enterprise Manager Cloud Control Basic Installation Guide.