While upgrading Enterprise Manager, all the JVM Diagnostics (JVMD) Engines are stopped as a part of the preupgrade process. Once Enterprise Manager is successfully upgraded to 13c Release 2, the JVMD Engines that were part of your enterprise before the upgrade must be re-created.
This chapter describes how to upgrade or redeploy Java Virtual Machine Diagnostics (JVMD) Agents. To obtain the latest JVMD features and use them to monitor the JVMs deployed in your enterprise, Oracle recommends that you upgrade your JVMD Agents to the latest available version.
The following topics are covered in this chapter:
For information about deploying JVMD Agents with basic and advanced options, see the following guides:
Enterprise Manager Cloud Control provides a user interface and a perl script that enable you to upgrade and redeploy JVMD Agents, which are simple web applications (
.war files). The user interface and the perl script enable you to simplify the process of upgrading or redeploying JVMD Agents, and upgrade or redeploy multiple JVMD Agents in one go. Alternatively, you can choose to use the WebLogic Administration console to download and deploy the latest JVMD Agent version.
Certain enterprise management tasks (such as configuring a custom certificate for OMS Oracle HTTP Server uploads, configuring a load balancer for multiple OMSes, etc.) introduce changes in the OMS configuration. These tasks may require you to re-secure the deployed Management Agents. If you re-secure the Management Agents deployed in your enterprise, ensure that you redeploy the deployed JVMD Agents, as described in this section.
You can upgrade or redeploy JVMD Agents using the following methods:
You can upgrade a JVMD Agent deployed on a particular Managed Server only if the available JVMD Agent binaries are of a different version than the deployed JVMD Agent version.
To upgrade or redeploy JVMD Agents on monitored WebLogic domains using the Setup page, follow these steps:
Alternatively, to reach this point, you can click the upgrade icon displayed beside JVMD Agents Count, on the Setup page. Note that this icon is displayed only if a software version different from the current version of the JVMD Agent software is available.
If you select Expand All from the View menu, you can view the target name, target type, target host, target status, and so on of all the Managed Servers on which JVMD Agents are deployed.
Select the JVMD Agents you want to upgrade or redeploy. Click Next.
In case host and domain preferred credentials are already set for the Admin server target, they are automatically applied to the domain, and it is not required to click Apply.
Oracle EMAgent Target Host Credentials are the login credentials for the host on which the Management Agent, that is used to discover the WebLogic domain's Admin Server, is running. Oracle WebLogic Domain Credentials are the credentials for the Administration Server of the selected WebLogic domain.
To set the preferred credentials for a WebLogic domain's Admin server (that is, the preferred EMAgent target host credentials and the preferred Oracle WebLogic Domain credentials), from the Setup menu, select Security, then select Preferred Credentials. Select the Oracle Admin Server target type, then click Manage Preferred Credentials. In the Target Preferred Credentials section, set the preferred host credentials and the preferred WebLogic administrator credentials for the required WebLogic Admin server.
If you want to upgrade or redeploy JVMD Agents on Oracle Cloud targets, select Configure Hybrid Cloud Mode, and specify the Hybrid Cloud Proxy Host and Hybrid Cloud Proxy Port that is configured in Oracle Cloud. When you select Configure Hybrid Cloud Mode, the value for Available JVMD Engine is automatically set to Other, as the JVMD Agent connects to the proxy host, which in turn connects to the JVMD Engine.
Note:If the Hybrid Cloud version has been upgraded to Enterprise Manager 13c, the Hybrid Cloud Proxy and the Hybrid Cloud Gateway used in the SSH tunnel between the target domain running in Oracle Cloud and the JVM Diagnostics Engine must also be upgraded to 13c.
If you have not selected Configure Hybrid Cloud Mode, then for each WebLogic domain, a default JVMD Engine is selected for each domain. If necessary, to change the Engine selected for a domain, select a new Engine from list of Available JVMD Engine(s) and click Apply. All the JVMD Agents deployed on Managed Servers of the selected WebLogic domain will report to this JVMD Engine. Alternatively, you can select Other to connect to a load balancer in case of multiple engines and manually specify the engine host, port, and protocol details.
In Enterprise Manager Cloud Control 13c, you can deploy multiple JVMD Agents that connect to JVMD Engines using HTTP or HTTPS. Hence, both the HTTP and HTTPS URLs for a JVMD Engine are displayed in the Available JVMD Engines list. However, if you have configured a load balancer in your setup, JVMD Agents can connect to the load balancer using HTTP or HTTPS, but cannot connect to the individual JVMD Engines using HTTPS. Hence, if you have configured a load balancer for your setup, only the HTTP and HTTPS URLs for the load balancer, and the HTTP URLs for the individual JVMD Engines are displayed in the Available JVMD Engines list.
If the WebLogic Home and Middleware Home fields are displayed in this section, specify values for them. The WebLogic Home and Middleware Home fields are displayed if their values could not be obtained internally.
Also, if the WebLogic Administration Server is behind a firewall or on a virtual host, the application may not be able to connect to it using the default information. In this case, you may need to provide additional information in the Advanced Domain Configuration section. For example, if the WebLogic Administration Server is on a virtual host, and the application cannot connect to it using the default host value, you must provide the virtual host IP address for Administration server host.
Under Advanced Domain Configuration, you can specify java args that would be used in the java processes used to deploy JVMD agent. For example, some of the java args that may be required are:
Dweblogic.security.SSL.trustedCAKeyStore=<path to cacert>
When you click Upgrade, the Diagnostic Agents Deployment Status page appears, which you can use to monitor the progress of the submitted job.
If you encounter any errors during the upgrade or redeployment, see Oracle Enterprise Manager Cloud Control Advanced Installation Guide
You can upgrade or redeploy JVMD Agents manually, using the
deploy_jvmdagent.pl script. You can run this script only in silent mode, that is, you must specify all the input details using a properties file.
To upgrade or redeploy JVMD Agents manually using
deploy_jvmdagent.pl, follow these steps:
jamagent.warhas been downloaded.
For information on how to download
jamagent.war, see Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide
README.txtfile for information on how to use the
perl deploy_jvmdagent.pl [-appserver <server_type>] [-file <name_of_properties_file>]
perl deploy_jvmdagent.pl -appserver WLS -file wls_upgrade.properties.
deploy_jvmdagent.pl, you can upgrade or redeploy only those JVMD Agents that are deployed on WebLogic Server and GlassFish, and not the JVMD Agents that are deployed on other application servers. The
-appserver parameter specifies the application server on which the JVMD Agent (that you want to upgrade or redeploy) is deployed. If you are upgrading or redeploying a JVMD Agent that is deployed on a WebLogic Managed Server, specify
-appserver. If you are upgrading or redeploying a JVMD Agent that is deployed on a GlassFish server, specify
-appserver. If you do not specify the
-appserver parameter, it is assigned the value
WLS by default.
-file parameter specifies the name of the properties file containing the upgrade or deployment inputs. If you do not specify this parameter, and have specified
deploy_jvmdagent.pl searches for a properties file named
weblogic_deploy.properties in the folder containing the script. If you do not specify the
-file parameter, and have specified
deploy_jvmdagent.pl looks for a properties file named
glassfish_deploy.properties in the folder containing the script. To learn how to specify the input details in a properties file, view the sample properties files
After upgrading or redeploying your JVMD agents, verify the deployment of their new versions, as described in Oracle Enterprise Manager Cloud Control Basic Installation Guide