7 Upgrading and Redeploying ADP and JVMD

While upgrading Enterprise Manager, all the Application Dependency and Performance (ADP) Engines and JVM Diagnostics (JVMD) Engines are stopped as a part of the preupgrade process. Once Enterprise Manager is successfully upgraded to 12c Release 4 (12.1.0.4), the ADP and JVMD Engines that were part of your enterprise before the upgrade must be re-created.

Note:

For information about deploying JVMD Engines and JVMD Agents with basic and advanced options, see the following guides:

For information about deploying ADP Engines and ADP Agents with basic and advanced options, see the following guides:

This chapter consists of the following sections:

7.1 Upgrading or Redeploying JVMD and ADP Engine

This section describes the methods to upgrade or redeploy ADP and JVMD Engines. It consists of the following:

7.1.1 Upgrading JVMD Engine

This section describes the methods to upgrade JVMD Engine. It consists of the following:

Important:

  • 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 section.

  • You can only upgrade the JVMD Engines that are deployed on OMS hosts, and not the JVMD Engines that are deployed on remote hosts.

  • Before upgrading the deployed JVMD Engines, it is recommended that you first shut them down manually.

7.1.1.1 Upgrading JVMD Engine Using Application Performance Management Page

To upgrade JVMD Engine deployed on a Managed Server using the Application Performance Management page, follow these steps:

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

  2. 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.
  3. On the Upgrade JVMD Engines page, select the JVMD Engine you want to upgrade.

  4. 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.

  5. If you want to upgrade more than one JVMD Engine, on the Upgrade JVMD Engines page, select the JVMD engines you want to upgrade, then specify and apply values for Host Credentials, for each one of them.

  6. Specify a value for Admin WebLogic Credentials. These credentials are the credentials for the Administration Server of the Enterprise Manager WebLogic domain.

  7. Click Upgrade.

    If you encounter any errors during the upgrade, see Oracle Enterprise Manager Cloud Control Advanced Installation Guide.

Note:

After upgrading a JVMD Engine, if two entries exist for the same JVMD Engine on the Application Performance Management page, delete the old entry from the jam_managers table by logging in to the Enterprise Manager Repository as the sysman user and executing the following query:

delete from jam_managers where manager_id =<manager_id_of_old_jvmd_engine>

7.1.1.2 Upgrading JVMD Engine Manually Using ApmEngineSetup.pl

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:

  1. Navigate to the following location on the OMS host:

    $<MIDDLEWARE_HOME>/plugins/oracle.sysman.emas.oms.plugin_12.1.0.6.0/archives/jvmd/deployment_Scripts/engine/

  2. View the README.txt file, for information on using the ApmEngineSetup.pl script.

  3. 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:

After upgrading a JVMD Engine, if two entries exist for the same JVMD Engine on the Application Performance Management page, delete the old entry from the jam_managers table by logging in to the Enterprise Manager Repository as the sysman user and executing the following query:

delete from jam_managers where manager_id =<manager_id_of_old_jvmd_engine>

7.1.2 Redeploying JVMD Engine

To redeploy JVMD Engine deployed on a Managed Server, follow these steps:

Note:

You can only redeploy JVMD Engine if a different version of the JVMD Engine software is not available. If a newer version or an older version of the JVMD Engine software is available, you can only upgrade the existing JVMD Engine to the newer version, or downgrade it to the older version, but not redeploy the existing JVMD Engine version. For information on how to upgrade JVMD Engine, refer Section 7.1.1.
  1. From the Setup menu, select Middleware Management, then select Application Performance Management.

  2. 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.

  3. On the Redeploy JVMD Engines page, select the JVMD Engines you want to redeploy.

  4. 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.

  5. Specify a value for Admin WebLogic Credentials. These credentials are the credentials for the Administration Server of the Enterprise Manager WebLogic domain.

  6. Click Redeploy.

    If you encounter any errors during the redeployment, see Oracle Enterprise Manager Cloud Control Advanced Installation Guide.

7.1.3 Upgrading ADP Engine

This section describes the methods to upgrade ADP Engine. It consists of the following:

Important:

  • When you upgrade the Enterprise Manager for Oracle Fusion Middleware plug-in to version 12.1.0.6, the deployed ADP Engines are not upgraded automatically. You must upgrade them using the methods described in this section.

  • You can only upgrade the ADP Engines that are deployed on OMS hosts, and not the ADP Engines that are deployed on remote hosts.

  • Before upgrading the deployed ADP Engines, it is recommended that you first shut them down manually.

7.1.3.1 Upgrading ADP Engine Using Application Performance Management Page

To upgrade ADP Engine deployed on a Managed Server using the Application Performance Management page, follow these steps:

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

  2. On the Application Performance Management page, click the upgrade icon displayed beside ADP Engines.

    Note:

    The upgrade icon is displayed only if a software version different from the current deployed version of the ADP Engine software is available.
  3. On the Upgrade ADP Engines page, select the ADP Engine you want to upgrade.

  4. Specify a value for Host Credentials. These credentials are the host credentials of the host on which the ADP Engine you selected is deployed. Click Apply.

  5. If you want to upgrade more than one ADP Engine, on the Upgrade ADP Engines page, select the ADP engines you want to upgrade, then specify and apply values for Host Credentials, for each one of them.

  6. Specify a value for Admin WebLogic Credentials. These credentials are the credentials for the Administration Server of the Enterprise Manager WebLogic domain.

  7. Click Upgrade.

    If you encounter any errors during the upgrade, see Oracle Enterprise Manager Cloud Control Advanced Installation Guide.

7.1.3.2 Upgrading ADP Engine Manually Using ApmEngineSetup.pl

You can upgrade ADP 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 ADP Engine manually using the ApmEngineSetup.pl script, follow these steps:

  1. Navigate to the following location on the OMS host:

    $<MIDDLEWARE_HOME>/plugins/oracle.sysman.emas.oms.plugin_12.1.0.6.0/archives/jvmd/deploymentScripts/engine/

  2. View the README.txt file, for information on using the ApmEngineSetup.pl script.

  3. 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 ADP.

    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 ADP 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.

7.1.4 Redeploying ADP Engine

To redeploy ADP Engine deployed on a Managed Server, follow these steps:

Note:

You can only redeploy ADP Engine if a different version of the ADP Engine software is not available. If a newer version or an older version of the ADP Engine software is available, you can only upgrade the existing ADP Engine to the newer version, or downgrade it to the older version, but not redeploy the existing ADP Engine version. For information on how to upgrade ADP Engine, refer Section 7.1.3.
  1. From the Setup menu, select Middleware Management, then select Application Performance Management.

  2. If you want to redeploy a single ADP Engine, on the Application Performance Management page, select the ADP Engine you want to redeploy, then click Redeploy.

    If you want to redeploy more than one ADP Engine, on the Application Performance Management page, select the ADP Engines node, then click Redeploy.

  3. On the Redeploy ADP Engines page, select the ADP Engines you want to redeploy.

  4. For each ADP Engine you have chosen to redeploy, specify a value for Host Credentials. These credentials are the host credentials of the host on which the ADP Engine you selected is deployed. Click Apply.

  5. Specify a value for Admin WebLogic Credentials. These credentials are the credentials for the Administration Server of the Enterprise Manager WebLogic domain.

  6. Click Redeploy.

    If you encounter any errors during the redeployment, see Oracle Enterprise Manager Cloud Control Advanced Installation Guide.

7.2 Upgrading or Redeploying JVMD and ADP Agents

This section describes the methods to upgrade or redeploy JVMD and ADP Agents. It consists of the following:

7.2.1 Upgrading or Redeploying JVMD and ADP Agents Using Application Performance Management Page

To upgrade or redeploy JVMD and ADP Agents on monitored WebLogic domains using the Application Performance Management page, follow these steps:

Note:

You can only redeploy JVMD and ADP Agents if a different version of the JVMD or ADP Agent software is not available. If a newer version or an older version of the JVMD or ADP Agent software is available, you can only upgrade the existing JVMD or ADP Agent to the newer version, or downgrade it to the older version, but not redeploy the existing JVMD or ADP Agent version.
  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.

    Note:

    If no active JVMD or ADP Engines are present, and no JVMD or ADP Agents are deployed, the Manage Diagnostics Agents button is disabled.
  3. For Operation, select Upgrade.

    Note:

    Alternatively, to reach this point, you can click the upgrade icon displayed beside ADP Agents Count or 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 ADP or 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 or ADP Agents are deployed.

    Select the JVMD and ADP Agents you want to upgrade or redeploy. 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.

    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.

  5. On the ADP Agents Configurations page, for each WebLogic domain, select an ADP Engine for Available ADP Engines, then click Apply. All the ADP Agents deployed on the Managed Servers of the selected WebLogic domain will report to the selected ADP Engine.

    You can specify an alternate location for the ADP Agent software, which is used if the specified Administration Server Host Credentials do not have write permissions on the default location. To do this, under the Agent Directory section, select Edit the default ADP Agent Directory location if required, then specify a value for Agent Directory.

    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.

  6. On the JVMD Agents Configurations page, for each WebLogic domain, select a JVMD Engine for Available JVMD Engines, 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.

  7. On the Enterprise Manager OMS Credentials page, specify a value for Oracle Enterprise Manager WebLogic Administration Server Host Credentials, and Oracle Enterprise Manager WebLogic Domain Credentials.

    Note:

    The Enterprise Manager OMS Credentials page is displayed when you click Next on the JVMD Agents Configurations page, only if you have chosen to redeploy or upgrade at least one ADP Agent. OMS credentials are not required to redeploy or upgrade JVMD Agents.

    Oracle Enterprise Manager WebLogic Administration Server Host Credentials are the host credentials of the OMS host. The Oracle Enterprise Manager WebLogic Domain Credentials are the domain credentials of the Enterprise Manager WebLogic domain.

    Click Next.

  8. 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.

7.2.2 Upgrading or Redeploying JVMD Agents Manually Using deploy_jvmdagent.pl

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:

  1. 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.

  2. Navigate to the following location on the OMS host:

    $<MIDDLEWARE_HOME>/plugins/oracle.sysman.emas.oms.plugin_12.1.0.6.0/archives/jvmd/deployment_Scripts/agent/jvmd/

  3. View the README.txt file for information on how to use the deploy_jvmdagent.pl script.

  4. 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.

7.2.3 Upgrading or Redeploying ADP Agents Manually Using deploy_adpagent.pl

You can upgrade or redeploy ADP Agents manually, using the deploy_adpagent.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 ADP Agents manually using deploy_adpagent.pl, follow these steps:

  1. Navigate to the following location on the OMS host:

    $<MIDDLEWARE_HOME>/plugins/oracle.sysman.emas.oms.plugin_12.1.0.6.0/archives/jvmd/deploymentScripts/agent/adp/

  2. View the README.txt file, for information on using the deploy_adpagent.pl script.

  3. Specify all the inputs in a properties file, then use the following command:

    perl deploy_adpagent.pl <properties_file_name>

    If you do not pass the name of the properties file as a parameter while running deploy_adpagent.pl, deploy_adpagent.pl looks for a properties file named adpagent.properties in the folder containing the script. To learn how to specify the input details in a properties file, view the sample properties file SAMPLE_adpagent.properties.

7.3 After Upgrading or Redeploying

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.

After upgrading or redeploying your ADP Engines or ADP Agents, verify the deployment of their new versions, as described in Oracle Enterprise Manager Cloud Control Basic Installation Guide.