This chapter describes how to upgrade or redeploy Java Virtual Machine Diagnostics (JVMD), and consists of the following sections:
Note:
For information about deploying JVMD Engines and JVMD Agents with basic and advancedoptions, see the following guides:
To obtain the latest JVMD features and use them to monitor the JVMs deployed in your enterprise, Oracle recommends that you upgrade your JVMD Engines and Agents to the latest available version. When you upgrade the Enterprise Manager for Oracle Fusion Middleware plug-in to version 12.1.0.6, the deployed JVMD Engines are not upgraded automatically. You must upgrade them using the methods described in this chapter.
All configurations wherein the JVMD Agent is of the same, or of a lower version than the JVMD Engine (that it reports to), are supported. For example, if a particular JVMD Engine is of version 12.1.0.6, JVMD Agents of version 12.1.0.6 and lower can report to this JVMD Engine. However, Oracle recommends that you upgrade the JVMD Agents in your enterprise to version 12.1.0.6 or higher.
When you upgrade your JVMD Engines, note that you can only upgrade the JVMD Engines that are deployed on OMS hosts, and not the ones deployed on remote hosts. To obtain the latest version of JVMD Engine on a remote host, remove the existing version, and deploy a new JVMD Engine of the latest version.
To upgrade the JVMD application deployed in your enterprise, follow this process:
Manually shut down all the JVMD Engines.
To manually shut down a JVMD Engine, from the Setup menu, select Middleware Management, then select Application Performance Management. Click the name of the JVMD Engine that you want to shut down. On the JVMD Engine target home page, click Shut Down.
Upgrade the JVMD Engines to the latest version.
For information on how to upgrade your JVMD Engines, see Section 7.3.1.
Upgrade the JVMD Agents to the latest version.
For information on how to upgrade your JVMD Agents, see Section 7.4.
This section describes the methods to upgrade or redeploy JVMD Engines. It consists of the following:
This section describes the methods to upgrade JVMD Engine. It consists of the following:
To upgrade JVMD Engine deployed on a Managed Server using the Application Performance Management page, follow these steps:
From the Setup menu, select Middleware Management, then select Application Performance Management.
On the Application Performance Management page, click the upgrade icon displayed beside JVM Diagnostics Engines.
Note:
The upgrade icon is displayed only if a software version different from the current deployed version of the JVMD Engine software is available.On the Upgrade JVMD Engines page, select the JVMD Engine you want to upgrade.
Specify a value for Host Credentials. These credentials are the host credentials of the host on which the JVMD Engine you selected is deployed. Click Apply. The Apply button is located above the Host Credentials section, to the right. You may need to scroll to the right to see it.
On the Upgrade JVMD Engines page, select all the JVMD engines you want to upgrade, and then specify and apply values for Host Credentials, for each one of them.
Specify a value for Admin WebLogic Credentials. These credentials are the credentials for the Administration Server of the Enterprise Manager WebLogic domain.
Click Upgrade.
If you encounter any errors during the upgrade, see Oracle Enterprise Manager Cloud Control Advanced Installation Guide.
You can upgrade JVMD Engine manually, using the ApmEngineSetup.pl script. You can run this script in the following ways:
In interactive mode, where you are prompted for input details in an interactive manner
In silent mode, where you specify all the input details using a properties file
To upgrade JVMD Engine manually using the ApmEngineSetup.pl script, follow these steps:
Navigate to the following location on the OMS host:
$<MIDDLEWARE_HOME>/plugins/oracle.sysman.emas.oms.plugin_12.1.0.8.0/archives/jvmd/deployment_scripts/engine/
View the README.txt file, for information on using the ApmEngineSetup.pl script.
Run the ApmEngineSetup.pl script.
If you want to run the ApmEngineSetup.pl script in interactive mode, such that you are prompted for the input details, use the following command:
perl ApmEngineSetup.pl
Ensure that you specify the operation as upgrade, and the Engine Type as JVMD.
If you want to run the ApmEngineSetup.pl script in silent mode, specify all the input details in a properties file, then use the following command:
perl ApmEngineSetup.pl -silent -file <properties_file_name> -password <password>
<properties_file_name> is the name of the properties file where the JVMD Engine and operation details are provided. <password> is the WebLogic console password.
To learn how to specify the input details in a properties file, view the sample properties file SAMPLE_engine.properties.
Note:
The process of redeploying a JVMD Engine is identical to the process of upgrading a JVMD Engine, except that no upgrade icon is displayed beside JVM Diagnostics Engines on the Application Performance Management page. You will have to select the JVMD Engines that you want to redeploy, then click Redeploy to access the Redeploy JVMD Engines page.To redeploy JVMD Engine deployed on a Managed Server, follow these steps:
From the Setup menu, select Middleware Management, then select Application Performance Management.
If you want to redeploy a single JVMD Engine, on the Application Performance Management page, select the JVMD Engine you want to redeploy, then click Redeploy.
If you want to redeploy more than one JVMD Engine, on the Application Performance Management page, select the JVM Diagnostics Engines node, then click Redeploy.
On the Redeploy JVMD Engines page, select the JVMD Engines you want to redeploy.
For each JVMD Engine you have chosen to redeploy, specify a value for Host Credentials. These credentials are the host credentials of the host on which the JVMD Engine you selected is deployed. Click Apply. The Apply button is located above the Host Credentials section, to the right. You may need to scroll to the right to see it.
Specify a value for Admin WebLogic Credentials. These credentials are the credentials for the Administration Server of the Enterprise Manager WebLogic domain.
Click Redeploy.
If you encounter any errors during the redeployment, see Oracle Enterprise Manager Cloud Control Advanced Installation Guide.
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.
You can upgrade or redeploy JVMD Agents using the following methods:
Upgrading or Redeploying JVMD Agents Using the Application Performance Management Page
Upgrading or Redeploying JVMD Agents Manually Using deploy_jvmdagent.pl
Upgrading or Redeploying JVMD Agents Manually Using the WebLogic Administration Console
Note:
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.For example, if a 12.1.0.6 JVMD Agent is deployed on a Managed Server, and the 12.1.0.8, or any other version of the JVMD Agent binaries is available, then you can upgrade the deployed 12.1.0.6 JVMD Agent. However, if the 12.1.0.6 version of the JVMD Agent binaries is the only version available, and no other version of the binaries is available, then you cannot upgrade the 12.1.0.6 JVMD Agent deployed on the Managed Server.
To upgrade or redeploy JVMD Agents on monitored WebLogic domains using the Application Performance Management page, follow these steps:
From the Setup menu, select Middleware Management, then select Application Performance Management.
On the Application Performance Management page, under the Application Performance Management Agents section, click Manage Diagnostics Agents.
For Operation, select Upgrade.
Note:
Alternatively, to reach this point, you can click the upgrade icon displayed beside JVMD Agents Count, on the Application Performance Management 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, platform, 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.
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 (to see, scroll right).
Oracle WebLogic Administration Server Host Credentials are the host credentials for the host on which the Management Agent that is monitoring the selected WebLogic domain is running. Oracle WebLogic Domain Credentials are the credentials for the Administration Server of the selected WebLogic domain.
Click Next.
On the JVMD Agents Configurations page, for each WebLogic domain, the previously chosen JVMD Engine is automatically applied. However, it is possible to change it. To do so, select a JVMD Engine from Available JVMD Engines, and then 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.
If the WebLogic Home and Middleware Home fields are displayed under the Additional Configuration section, specify values for them. The WebLogic Home and Middleware Home fields are displayed if their values could not be obtained internally.
Also, sometimes when 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 host value. In this case, you may need to provide some additional information in the Additional 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 may have to provide the virtual host IP address in the Additional Configuration section.
Click Next.
On the Review page, review all the information, then click Upgrade.
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:
Ensure that the latest version of javadiagnosticagent.ear or jamagent.war has been downloaded.
For information on how to download javadiagnosticagent.ear or jamagent.war, see Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.
Navigate to the following location on the OMS host:
$<MIDDLEWARE_HOME>/plugins/oracle.sysman.emas.oms.plugin_12.1.0.8.0/archives/jvmd/deployment_scripts/agent/jvmd/
View the README.txt file for information on how to use the deploy_jvmdagent.pl script.
Specify all the inputs in a properties file, then use the following command:
perl deploy_jvmdagent.pl [-appserver <server_type>] [-file <name_of_properties_file>]
For example, perl deploy_jvmdagent.pl -appserver WLS -file wls_upgrade.properties.
Using 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 WLS for -appserver. If you are upgrading or redeploying a JVMD Agent that is deployed on a GlassFish server, specify GF for -appserver. If you do not specify the -appserver parameter, it is assigned the value WLS by default.
The -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 WLS for -appserver, 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 GF for -appserver, 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 sample_weblogic_deploy.properties or sample_glassfish_deploy.properties.
You can choose to use the WebLogic Administration console to manually download and deploy the required JVMD Agent version.
After upgrading or redeploying your JVMD Engines or JVMD Agents, verify the deployment of their new versions, as described in Oracle Enterprise Manager Cloud Control Basic Installation Guide.