23 Deinstalling ADP and JVMD

This chapter describes how you can deinstall Application Dependency and Performance (ADP), and Java Virtual Machine Diagnostics (JVMD) in the Enterprise Manager Cloud Control environment.

In particular, this chapter covers the following:

23.1 Deinstallation Procedure for ADP

This section consists of the following:

23.1.1 Removing ADP Engine

This section describes the methods to remove ADP Engines. It consists of the following:

23.1.1.1 Removing ADP Engine Using Application Performance Management Page

To remove the ADP Engine applications running on Managed Servers using the Application Performance Management page, perform the following steps:

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

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

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

  3. On the Remove ADP Engines page, select the ADP Engines you want to remove.

  4. For each ADP Engine you select, select Remove WebLogic Managed Server, if you want to remove the WebLogic Managed Server on which the ADP Engine is deployed.

  5. Specify values for Admin WebLogic Host Credentials and Admin WebLogic Credentials.

    Admin WebLogic Host Credentials are the host credentials for the host on which the WebLogic Administration Server (for the Enterprise Manager WebLogic domain) is deployed. Admin WebLogic Credentials are the credentials for the Administration Server of the Enterprise Manager WebLogic domain.

  6. Click Remove.

23.1.1.2 Removing ADP Engine Manually

To remove the ADP Engine application running on a Managed Server manually, perform the following steps:

  1. In Cloud Control, from the Targets menu, select Middleware.

  2. On the Middleware page, from the Middleware Features menu, select Application dependency and Performance.

    The Application Dependency and Performance is displayed.

  3. From the Registration tab, select the ADP Engine application, then click Remove.

  4. Log in to the WebLogic Administration Console of the Enterprise Manager domain.

  5. On the Home Page, click Servers.

  6. From the Summary of Servers page, click the Control tab, then select the ADP Engine Servers.

  7. From the Shutdown menu, select Force Shutdown Now to stop the servers.

  8. Click the Lock and Edit button present in the WebLogic Administration console.

  9. Click the Configuration tab, select ADP Engine Servers, then click Delete.

  10. Undeploy the ADP applications. For example, ADPManager_EMGC_ADPMANAGER1 for ADP.

  11. Connect to the host machine where the Managed Server was present, and navigate to the following location to manually delete the Managed Server:

    $DOMAIN_HOME/<ADP_managed_server>
    

    Where $DOMAIN_HOME is the location of the Enterprise Manager Cloud Control domain.

23.1.1.3 Removing ADP Engine Manually Using ApmEngineSetup.pl

You can remove 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

Important:

You can use the ApmEngineSetup.pl script to remove ADP Engine only on a host that is running the OMS, and not on a remote host.

To remove 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/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 remove, 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.

23.1.2 Removing ADP Agents

This section describes the methods to remove ADP Agents. It consists of the following:

23.1.2.1 Removing ADP Agents Using Application Performance Management Page

To remove the ADP Agents (that are deployed on monitored WebLogic domains) using the Application Performance Management page, perform the following 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.

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

    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 ADP Agents you want to remove. 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, specify values for the WebLogic Home and Middleware Home fields.

    These fields are displayed only 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.

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

    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.

  7. On the Review page, review all the information, then click Remove.

23.1.2.2 Removing ADP Agents Deployed to Targets Manually

To manually remove the ADP Agent deployed to a target, perform the following steps:

  1. In Cloud Control, from the Targets menu, select Middleware.

  2. On the Middleware page, from the Middleware Features menu, select Application dependency and Performance.

    The Application Dependency and Performance is displayed.

  3. From the Configuration tab, select the desired ADP Engine application on which the ADP Agents have been deployed.

  4. Expand the ADP Engine menu, then select Resource Configuration.

  5. From the Resource table, select the ADP Agent name, click Edit Resource, then click Deploy.

  6. From the Deploy Parameters table, select the servers from which you want to undeploy the ADP Agents. Change the default menu selection from Deploy to:

    • Remove, to erase all the ADP Agent files from the Managed Servers.

    • Disable, to remove the ADP Agent startup arguments from the Managed Servers.

      Note:

      Select the Server Started by Node Manager option only when the node manager is used.

23.2 Deinstallation Procedure for JVMD

This section consists of the following:

23.2.1 Removing JVMD Engine

This section describes the methods to remove JVMD Engines. It consists of the following:

23.2.1.1 Removing JVMD Engine Using Application Performance Management Page

To remove the JVMD Engine applications running on Managed Servers using the Application Performance Management page, perform the following steps:

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

  2. If you want to remove a single JVMD Engine, on the Application Performance Management page, select the JVMD Engine you want to remove, then click Remove.

    If you want to remove more than one JVMD Engine, on the Application Performance Management page, select the JVM Diagnostics Engines node, then click Remove.

  3. On the Remove JVMD Engines page, select the JVMD Engines you want to remove.

  4. For each JVMD Engine you select, select Remove WebLogic Managed Server, if you want to remove the WebLogic Managed Server on which the JVMD Engine is deployed.

  5. Specify values for Admin WebLogic Host Credentials and Admin WebLogic Credentials.

    Admin WebLogic Host Credentials are the host credentials for the host on which the WebLogic Administration Server (for the Enterprise Manager WebLogic domain) is deployed. Admin WebLogic Credentials are the credentials for the Administration Server of the Enterprise Manager WebLogic domain.

  6. Click Remove.

23.2.1.2 Removing JVMD Engine Manually

To remove the JVMD Engine application running on a Managed Server manually, perform the following steps:

  1. Log in to the WebLogic Administration console of the Enterprise Manager Cloud Control domain.

  2. On the Home Page, click Deployments.

  3. Select the JVMD applications (for example, jammanagerEMGC_JVMDMANAGER1, jammanagerEMGC_JVMDMANAGER2). From the Stop menu, select Force Stop Now.

  4. Click the Lock and Edit button present in the WebLogic Administration console.

  5. After the applications are stopped, select the same applications, then click Delete.

  6. Click Home to go back to the WebLogic Administration home page. From the Environment table, select Servers.

  7. On the Summary of Servers page, select the Control tab, then select the JVMD Engine servers that need to be shut down.

  8. From the Shutdown menu, select Force Shutdown Now to stop the servers.

  9. Click the Lock and Edit button present in the WebLogic Administration console.

  10. Click the Configuration tab, select the JVMD Engine servers, then click Delete.

23.2.1.3 Removing JVMD Engine Manually Using ApmEngineSetup.pl

You can remove 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

Important:

You can use the ApmEngineSetup.pl script to remove JVMD Engine only on a host that is running the OMS, and not on a remote host.

To remove 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 remove, 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.

23.2.2 Removing JVMD Agents

This section describes the methods to remove JVMD Agents. It consists of the following:

23.2.2.1 Removing JVMD Agents Using Application Performance Management Page

To remove the JVMD Agents (that are deployed on monitored WebLogic domains) using the Application Performance Management page, perform the following 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.

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

    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 Agents you want to remove. 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 JVMD Agents Configurations page, specify values for the WebLogic Home and Middleware Home fields.

    These fields are displayed only 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.

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

23.2.2.2 Removing JVMD Agents Deployed to Targets Manually

To manually remove the JVMD Agent deployed to a target, perform the following steps:

  1. Log in to the Administration Console of the target server.

  2. On the Home Page, click Deployments.

  3. Select the JVMD Agent application (javadiagnosticagent.ear or jamagent.war). From the Stop menu, select Force Stop Now.

  4. After the applications are stopped, select the same applications, then click Delete.

  5. Log in to Enterprise Manager Cloud Control.

  6. In Cloud Control, from the Targets menu, select Middleware.

  7. On the Middleware page, in the Search table, search for targets of type Java Virtual Machine, select the target corresponding to the server, then click Remove.