2 Bundle Patch 1 for Linux x86 and Linux x86-64

2.2.1 Setting Up My Oracle Support Credentials

Complete the follow steps to set up the My Oracle Support credentials. If you have already set up your MOS credentials, then you can skip this section.

1. From the Setup menu, select My Oracle Support, then select Set Credentials.

   Figure 2-6 Set Credentials

   
   

2. Supply your My Oracle Support credentials, click Apply to save this information, then click the Refresh From My Oracle Support link to see the job.

   This also triggers jobs to update Opatch and refresh MOS. You should check that these jobs complete successfully before proceeding. However, if these jobs have run successfully during the last 24 hours, they will not be triggered and you can just proceed.

2.2.2 About Infrastructure Set Up in Online Mode

This section describes the steps involved in setting up the infrastructure when using Management Agent patching in online mode.

Complete the following to setup the infrastructure if you are using Management Agent patching in online mode:

1. Check that the connection to My Oracle Support is set to Online.

   From the Setup menu, select Provisioning and Patching, then select Offline Patching.

   Figure 2-7 Provisioning and Patching

   
   

2. Set the connection setting to Online and click Apply.

   Figure 2-8 Patching Setup

   
   

3. Select the My Oracle Support and Proxy Connection tab.

   Figure 2-9 My Oracle Support and Proxy Connection

   
   

4. If needed, configure your Proxy Connection to connect to My Oracle Support (MOS). If you choose Manual Proxy Configuration, provide the required Proxy Server and Port and Realm details, then click Apply.

   Figure 2-10 Manual Proxy Configuration

   
   

5. Click Test to check that the connectivity works correctly when the configuration is complete.

   If connectivity is not working, you can switch to offline mode. For more information, see Section 2.2.3, "Setting up the Infrastructure if you are using Agent Patching in Offline Mode".

6. Click Apply to save the configuration following a successful test.

   The error message shown is for information proposes only. You can use the included link to set up MOS credentials. For more information, see Section 2.2.1, "Setting Up My Oracle Support Credentials".

   Figure 2-11 Proxy Settings Error

   
   

2.2.3 Setting up the Infrastructure if you are using Agent Patching in Offline Mode

If you cannot use the online mode and configure connectivity to MOS, then you must use the offline patching method. Follow the steps below to set up the infrastructure to patch your Management Agents with the Bundle Patch.

1. Verify that the connection to My Oracle Support is set to "Offline".

   From the Setup menu, select Provisioning and Patching, then select Offline Patching.

   Figure 2-12 Offline Patching

   
   

2. From the Patching Setup page, select Online and Offline Settings, then select Offline and click Apply.

   Figure 2-13 Patching Setup

   
   

3. Update the Enterprise Manager metadata files by completing the following:

   1. Download metadata files from My Oracle Support from the following location:

      https://support.oracle.com
      

      You can download all of the required XMLs using a wget script. Execute the script as instructed in the My Oracle Support note 1436338.1 at the following location:

      https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=1436338.1
      

      You can also select and download the files manually. Table 2-1, "Metadata Files" provides a list of the files to be downloaded and their locations.

      Table 2-1 Metadata Files

      Metadata XML File	Download Location
      aru_products.xml	https://updates.oracle.com/Orion/Services/metadata?table=aru_products
      aru_releases.xml	https://updates.oracle.com/Orion/Services/metadata?table=aru_releases
      aru_platforms.xml	https://updates.oracle.com/Orion/Services/metadata?table=aru_platforms
      aru_languages.xml	https://updates.oracle.com/Orion/Services/metadata?table=aru_languages
      aru_product_groups.xml	https://updates.oracle.com/Orion/Services/metadata?table=aru_product_groups
      aru_product_releases.xml	https://updates.oracle.com/Orion/Services/metadata?table=aru_product_releases
      aru_component_releases.xml	https://updates.oracle.com/Orion/Services/metadata?table=aru_component_releases
      aru_targets.xml	https://updates.oracle.com/Orion/Services/metadata?table=aru_targets
      certifications.xml	https://updates.oracle.com/Orion/Services/components?ctype=product,release,platform,platform_version,wildcard-release,config-group,release-component,certification
      patch_recommendations.xml	https://updates.oracle.com/Orion/Services/search?language_id=0&classification_group=recommended&patch_type=all&group_by=target_type&group_by=release&group_by=platform

      
      

   2. Download the URLs and store them in the local system.

      Copy and paste the contents of every URL into a separate text file and save it with the proper name and the .xml extension (for example, save the file as aru_products.xml).

      The URL opens in the browser and the contents are copied into Notepad and the file is then saved as an XML.

      Figure 2-14 Downloading Metadata Files

      
      

   3. Upload the metadata files to Enterprise Manager.

      From the Setup menu, select Provisioning and Patching, then select Offline Patching.

      Figure 2-15 Offline Patching

      
      

   4. Click Browse in the Metadata Cache section to select the xml metadata files.

   5. Click Upload to upload the metadata files

      Following a successful upload, the Status column for the XML files will be Green. Other column information will also be updated.

   6. From the Enterprise menu, select Job, then select Activity.

   7. Select Refresh From My Oracle Support from the Create Job list and click Go.

      Figure 2-16 Refresh From My Oracle Support

      
      

   8. Specify a name for the job and click Submit.

      Figure 2-17 Specifying a Job Name

      
      

      When the job is created and submitted, a confirmation screen is presented.

      Figure 2-18 Confirmation Screen

      
      

   9. Click the link to track the status of the job.

      Ensure that the job succeeds. You might have to refresh the page or set up the refresh to be every 30 seconds.

      Note: If the job fails, refer to the trouble shooting section at the end of the document or call Oracle Support.

      Figure 2-19 Job Activity Status

      
      

4. Download the required Management Agent patches and OPatch patches from My Oracle Support (https://support.oracle.com) by completing the following:

   1. Download the Management Agent patches by specifying the four patch numbers 13242776, 13491785, 13550565, and 13550561 as comma-separated entries In the Patch Search region of the Patches & Updates page, then click Search.

      Make sure you select the right platform, for example, Linux x86-64.

      Figure 2-20 Patch Search Screen

      
      

   2. Click Search.

      Figure 2-21 Patch Search Results

      
      

   3. Download the patch zip files and the patch metadata files for the patches.

      To download the patch metadata, click Download Patch Metadata, then click Download.

      Click the patch zip file to download the zip file.

      Note:

      Make sure you download both.

      Figure 2-22 ZIP File Download

      
      

      Figure 2-23 Download Patch Metadata

      
      

   4. Download the required OPatch patches from My Oracle Support (https://support.oracle.com).

      Search for patch "6880880" for the appropriate platform for the Management Agent target. For example, if your target is Linux x86-64, pick platform Linux x86-64.

      Figure 2-24 Patch Search

      
      

   5. Click Search.

      Download the patch for the version 11.1.0.0.0 series only.

      Figure 2-25 Patch Search Results

      
      

   6. Download both the patch zip file and the patch metadata.

      To download the patch metadata file, click Download Patch Metadata, then click Download.

      Figure 2-26 File Download

      
      

      Figure 2-27 Download Patch Metadata

      
      

5. Upload the Management Agent patches to the Software Library.

   1. From the Enterprise menu, select Provisioning and Patching, then select Saved Patches.

      Figure 2-28 Saved Patches

      
      

      Figure 2-29 Patching

      
      

   2. Click Upload to open the Upload Patches to Software Library page.

      Figure 2-30 Upload Patches to Software Library

      
      

      Of the four patches for Management Agents, two are for "Base platform" (13242776 and 13491785) and the other two are for "Oracle Home plug-in" (13550561 and 13550565).

   3. Set the Basic Information as shown.

   4. For patches 13242776 and 13491785, select the patch metadata file and patch zip file from the local directory on the system and click Upload.

      Figure 2-31 Patch Information

      
      

   5. Upload patches 13550561 and 13550565 by selecting their patch metadata and the patch zip file.

   6. Reset the Basic Information attributes as shown.

      Figure 2-32 Basic Information

      
      

   7. Select the patch metadata and the patch zip file and click Upload.

6. To upload OPatch 6880880 to the Software Library, specify the Basic Information attributes.

   Select the patch metadata and patch zip file for the Opatch patch 6880880 and upload it. Ensure that you fill in all attributes required in the page:

   • Release: Choose version as "11.1.0.0.0".

   • Created On: Use today's date

   • Description: Opatch for version 11.1.0.x

   • Platform: Select the platform for which you downloaded the patch (for example, Linux x86-64)

   • Language: Select 'American English'

7. Click Upload.

   Upon successful upload, all the patches will be visible in the Saved Patches page.

   Figure 2-33 Saved Patches in Software Library

   
   

   At the end of this process, all of the Agent patches and the Opatch patch should be listed in the Saved Patches in Software Library page.

2.3.1 Prerequisites for Deploying Plug-ins

Make sure that you upgrade all of your version 12.1.0.1 plug-ins to the 12.1.0.2 releases (with out revision) where available. Update all plug-ins on an OMS instance one after the other until all have been upgraded (plug-ins can only be updated one at a time).

To verify that your plug-ins are upgraded to the latest 12.1.0.2 release, complete the following:

1. Back up your Oracle Inventory, Repository Database, Middleware Home, Instance Home, Software Library, Management Agent. You can refer to the back up instruction from Enterprise Manager Cloud Control Administrator's Guide available here:

   http://docs.oracle.com/cd/E24628_01/index.htm
   

2. Log in to your repository database as SYSMAN and recompile invalid objects using the following command:

   EXEC EMD_MAINT_UTIL.recompile_invalid_objects
   SQL> EXEC 
   EMD_MAINT_UTIL.recompile_invalid_objects
   
   PL/SQL procedure successfully completed.
   

   Make sure that you do not have any invalid objects in your repository. To check any invalid object, log in to the repository as a system user and run the following command:

   SELECT object_name, object_type FROM ALL_OBJECTS WHERE owner='SYSMAN' and status <> 'VALID' ;
   
   SQL> SELECT object_name, object_type 
   FROM ALL_OBJECTS 
   WHERE owner='SYSMAN' and status <> 'VALID' ;
   
   no rows selected
   

   If you find any invalid objects, run the first SQL again:

   EXEC EMD_MAINT_UTIL.recompile_invalid_objects
   

3. Verify that DBMS jobs are running.

   If they are not running, run the following package as sysman user:

   EXEC EMD_MAINTENANCE.submit_em_dbms_jobs
   

   To check if jobs are running, open the Enterprise Manager console and from the Setup menu, select Management Services and Repository, then select Repository Operations.

   Figure 2-34 Repository Operations

   
   

   Figure 2-35 Repository Scheduler Job Status

   
   

4. Stop and start your Database and OMS before your start the plug-in upgrade.

   Do this on all the OMS instances of an multi-OMS environment.

5. Verify that the Target Management Agent (where you will be upgrading your plug-in) is up and running.

6. Follow the instructions in Section 2.7, "Upgrading ADP and JVMD (Optional)" if you are updating to the 12.1.0.2 release of the Oracle Fusion Middleware Plug-in and you already have Application Dependency and Performance (ADP) or JVM Diagnostics (JVMD) installed.

7. Stop the following components if they are running within your Cloud Control domain before updating any plug-in to the latest release:

   • Application Dependency and Performance (ADP) Manager

   • JVM Diagnostics (JVMD) Manager

2.3.2 Deploying Plug-ins in Online Mode on OMS

To deploy plug-ins in an online mode, complete the following:

1. From the Setup menu, select Extensibility, then select Self Update to get the complete list of available updates.

   Figure 2-36 Self Update

   
   

2. From the Plug-ins home page, select Actions, then select Check Updates.

   Figure 2-37 Check Updates

   
   

   A job gets triggered and updates the Available Update column. A confirmation screen is displayed when a job is successfully submitted.

   Figure 2-38 Confirmation Screen

   
   

3. Select Open from the Actions menu.

   Figure 2-39 Entity Type

   
   

4. Select an update from the list of available updates and click Download.

   The Schedule Download dialog appears. In the example shown below, the Oracle Audit Vault plug-in is selected.

   Figure 2-40 Schedule Download

   
   

5. Select when you want to download the update (immediately or at some later specified time).

   Note that multiple downloads can be scheduled simultaneously.

   Figure 2-41 Schedule Download

   
   

6. Click Select.

   An Enterprise Manager job is created to download the update to the Software Library. Enterprise Manager starts downloading the archive from the Oracle Enterprise Manager store.

   Note:

   The page is not refreshed automatically. Click Refresh to view the updated download status.

   Once an entity has been downloaded to the Software Library, it is ready to be applied to your installation.

7. Select an update from the list with a status of Downloaded, then click Apply.

   Figure 2-42 Plug-in Updates

   
   

   You are then redirected to the plug-in deployment page.

   Figure 2-43 Plug-ins

   
   

8. Select the plug-in and deploy it on OMS.

   Right click the plug-in name, select Deploy On, then select Management Servers.

   Figure 2-44 Plug-in Deploy On Management Servers

   
   

9. Provide the Repository SYS Password and click Continue.

   Figure 2-45 Deploy Plug-in on Management Servers

   
   

   Plug-in upgrade prerequisites checks are executed.

   Figure 2-46 Pre-requisite Checks

   
   

   Figure 2-47 Pre-requisite Checks Completed Successfully

   
   

10. Click Next.

11. Click Deploy when the prerequisite checks have completed successfully.

    Figure 2-48 Deploy Review Screen

    
    

    Figure 2-49 Deploy Confirmation Screen

    
    

    The OMS will be bounced automatically, So it is better to use $ emctl status oms -details to check for the plug-in deployment status.

12. From the Setup menu, select Extensibility, then select Plug-ins.

    The plug-in version on OMS is now 12.1.0.2.0, as shown in the On Management Server column.

    Figure 2-50 Plug-in Version

    
    

13. To deploy each updated plug-in on each Standby OMS, complete the following:

    1. Go to the Self Update page, click Plug-in, then select the required plug-in.

    2. From the Actions menu, select Export.

       A pop-up window showing two possible export steps opens. Note the value of the -id parameter displayed in the pop-up window. You will need this value for the next step.

       Figure 2-51 Export Steps

       
       

    3. Before proceeding with the export steps, log in to OMS Home (OMSHOME/bin) and run the sync command, as shown below:

       ./emcli sync
       

       The "Synchronized successfully" message should be displayed.

       Run the following EM CLI command on one of the primary site OMS servers:

       emcli export_update -id=<update id> -deep -host=<standby OMS host> -dir=<directory to export archives> <host credential options>
       

       For example:

       $ emcli export_update -id=725C4384A8D3AAB4BB1F672519378375 -deep -host=adc1140458.us.oracle.com -dir=/scratch/aime/plugins -credential_name=BDC -credential_owner=sysman
       

       The command syntax contains the following options:

       The -id option is taken from the pop up window.

       The -deep option is required. In a multiple OMS setup, the request can be processed by any OMS. Therefore, the directory should be a valid path (ideally shared) for each OMS that can process the request.

       The -host option identifies the target host to export the plug-in to.

       The -dir option identifies the directory on the target host to export the plug-in to.

       <host credential options> specifies the host credentials and can be one of the following:

       credential_set_name: The set name of the preferred credential stored in the repository for the host target. For example, HostCredsNormal (the default unprivileged credential set) or HostCredsPriv (the privileged credential set).

       credential_name: The name of a named credential stored in the repository. You must specify this option along with the credential_owner option.

       credential_owner: The owner of a named credential stored in the repository. You must specify this option along with the credential_name option.

       The command generates multiple zip files in the specified directory on the standby OMS host. The zip file with the name of the form version_OMS_platform_revision.zip, is the one to be used in the following steps. If you have multiple standby OMS hosts, copy this file to each host.

    4. Start the Standby Administration Server, if it is down, using the following command:

       $ emctl start oms -admin_only
       

    5. Install the OMS archive on the First Standby OMS Oracle Home using the following command:

       $ pluginia -archives path to plugin archive
       

    6. Configure the plug-in on the First Standby OMS Oracle Home using the following command:

       pluginca -action deploy -isFirstOMS true -plugins plugin-list -oracleHome oms oracle home -middlewareHome wls middleware home
       

       where plugin-list is the plug-in name in the format plugin-id=plugin-version.

    7. Copy the plug-in archive file to each Standby additional OMS.

    8. Run the following commands from each Standby additional OMS Oracle Home:

       $ pluginia -archives path to plugin archive
       
       $ pluginca -action deploy -isFirstOMS false -plugins plugin-list -oracleHome oms oracle home -middlewareHome wls middleware home
       

    9. This completes the plug-in deployment on Standby site. Validate the plug-ins by going to the Self Update page.

       Select a plug-in and view its information. All OMS servers should be listed.

2.3.3 Deploying Plug-ins in Offline Mode on OMS

To deploy plug-ins in an offline mode, complete the following:

1. From the Setup menu, select Extensibility, then select Self Update.

   Figure 2-52 Self Update Menu

   
   

   Figure 2-53 Self Update Page

   
   

2. Click Check Updates.

   The following message appears

   Figure 2-54 Check Updates in Offline Mode

   
   

   You must download the latest updates catalog using the link provided in the message.

   https://updates.oracle.com/Orion/Download/download_patch/p9348486_112000_Generic.zip 
   

   Note:

   Do not unzip the file.

   Make sure that you have this ZIP file on the OMS host. The following examples use a directory called "plugupdate " on the OMS host to store this catalog ZIP file.

   Figure 2-55 plugupdate Directory

   
   

3. Go to the <OMS home>/bin directory and log in into the EM CLI by running the following command as the install user:

   ./emcli login -username=sysman
   

   Figure 2-56 Login Screen

   
   

4. Execute emcli synchronize (mandatory) using the following command, as shown in the figure below:

   $OMS_OracleHome/emcli sync
   

   Figure 2-57 Synchronizing

   
   

5. Import the catalog file by executing the following command:

   $OMS_OracleHome/emcli import_update_catalog -omslocal  -file=<absolute location of the zip file>
   

   For example:

   $OMS_OracleHome/emcli import_update_catalog -omslocal  -file=/scratch/pluginupdate/p9348486_112000_Generic.zip
   

   Note: Run the above command on all of the other additional OMS servers incase of an multi-OMS environment.

   Figure 2-58 Importing the Catalog File

   
   

   Figure 2-59 Importing the Catalog File (cont'd)

   
   

6. Return to the Self Update page and refresh the page.

   You will see the Available Updates count updated.

   Figure 2-60 Count of New Updates

   
   

7. Select the Plug-in folder to see a list of the available new plug-ins.

   Figure 2-61 List of Available New Plug-ins

   
   

8. Select the plug-in and click Download.

   Figure 2-62 Plug-in Download

   
   

   Figure 2-63 Download Steps in Offline Mode Message

   
   

9. Follow the instructions provided in the message.

   Download the update file for the selected plug-in and make sure that it is on the OMS host.

   Note:

   Do not unzip the file. You must download the update file for all the plug-ins separately, one after the other.

10. Go to the <OMS home>/bin directory and import the update file you downloaded in the previous step by executing the following command:

    ./emcli import_update  -omslocal  -file=<absolute location of the zip file>
    

    For example:

    ./emcli import_update -omslocal -file=/scratch/pluginupdate/p13789099_112000_Generic.zip
    

    Note:

    If your session has expired, you might be prompted to log in again. You can do this using the following command:

    $ORACLE_HOME/bin/emcli login -username=sysman
    

    This command will make the update show up in "Downloaded" state in the Self Update Home page and can be "Applied" from the user interface.

    Figure 2-64 Import Update

    
    

11. Select Plug-in on the Self Update page.

    You will see the status has changed for the MOS plug-in from Available to Downloaded.

    Figure 2-65 Plug-in Updates

    
    

    Note:

    You must download the update files for the remaining plug-ins one after the other (repeat steps 9 to 12 for each plug-in update) and then run the command to change the status from Available to Downloaded.

12. Select the plug-in and click Apply.

13. Repeat steps 4 to 8 in Section 2.3.2, "Deploying Plug-ins in Online Mode on OMS" to deploy the plug-in on OMS

2.5.1 Deploying a Plug-in in Online Mode on a Management Agent

Next you will select plug-ins that were already upgraded on Oracle Management Service and upgrade the plug-ins on existing Management Agents. To deploy a plug-in in online mode on a Management Agent, complete the following:

1. From the Setup menu, select Extensibility, then select Self Update.

   Figure 2-77 Self Update Menu

   
   

2. Select Plug-in and from the Actions menu, select Open.

   Figure 2-78 Self Update

   
   

3. Click the Plug-in link.

4. R ight-click the plug-in, select Deploy On, then select Management Agent, as shown below.

   Figure 2-79 Deploy On Management Agent

   
   

5. Click Add to add the Management Agent where the plug-in will be deployed, as shown below.

   Figure 2-80 Add the Management Agent

   
   

6. Choose the required agent and click Select.

   You can select multiple agents in a single window.

   Figure 2-81 Search and Select: Targets

   
   

7. Click Continue, as shown below.

   Figure 2-82 Click Continue

   
   

8. Run the plug-in upgrade prerequisites checks and click Next, as shown below.

   Figure 2-83 Click Next

   
   

9. Click Deploy on the Review page to deploy the plug-in on the Agents.

   Figure 2-84 Click Deploy

   
   

   You can monitor the plug-in deployment by clicking Show Status.

   Figure 2-85 Show Status

   
   

   Make sure that the plug-ins are deployed successfully before moving forward.

2.5.2 Deploying a Plug-in in Offline Mode on a Management Agent

As plug-ins are readily available from the plug-in deployment to OMS, you can directly deploy the plug-ins to the agents. To deploy a plug-in in offline mode on a management agent, complete the following:

1. From the Setup menu, select Extensibility, then select Plug-ins

2. R ight-click the plug-in, select Deploy On, then select Management Agent to deploy the plug-in on the Management Agent.

   Figure 2-86 Deploy On Management Agent

   
   

3. Complete the remaining steps as described in Section 2.5.1, "Deploying a Plug-in in Online Mode on a Management Agent".

2.7.1 Upgrading Application Dependency and Performance

To upgrade ADP, complete the following:

1. Unzip the ADPManager.zip archive, which is in the following location:

   $MIDDLEWARE_HOME/plugins/oracle.sysman.emas.oms.plugin_12.1.0.2.0/archives/ocamm/
   

   This will create a folder called ADPManager.ear within the same directory.

2. Log in to the Oracle WebLogic Server Administration Console of the EMGC Domain and click Servers.

3. Locate all deployed ADP Managers.

   These will be managed servers that contain "EMGC_ADPMANAGER" in the server name. For example, "EMGC_ADPMANAGER1". Perform the steps below for each ADP Manager. For illustration purposes, the server name "EMGC_ADPMANAGER1" is used.

4. Shut down EMGC_ADPMANAGER1 using the Oracle WebLogic Server Administration Console.

   Figure 2-87 Oracle WebLogic Server Administration Console

   
   

5. Use the mv command to rename the existing ADPManager.ear folder in the EMGC_ADPMANAGER1 directory to ADPManager.ear_12cc01978:

   mv $MIDDLEWARE_HOME/gc_inst/user_projects/domains/GCDomain/EMGC_ADPMANAGER1/ADPManager.ear 
   $MIDDLEWARE_HOME/gc_inst/user_projects/domains/GCDomain/EMGC_ADPMANAGER1/ADPManager.ear_12cc01978
   

6. Use the mv command to move the ADPManager.ear folder you created to EMGC_ADPMANAGER1:

   mv $MIDDLEWARE_HOME/plugins/oracle.sysman.emas.oms.plugin_12.1.0.2.0/archives/ocamm/ADPManager.ear 
   $MIDDLEWARE_HOME/gc_inst/user_projects/domains/GCDomain/EMGC_ADPMANAGER1/
   

7. Change directory to the config directory under the ADPManager.ear_12cc01978 folder using the following command:

   cd $MIDDLEWARE_HOME/gc_inst/user_projects/domains/GCDomain/EMGC_ADPMANAGER1/ADPManager.ear_12cc01978/ADPManager.war/config/
   

8. Copy the Acsera.properties file as shown in the following command:

   Note:

   If you have previously installed but never started the ADP manager, then the listed configuration files will not exist. In this case, you can safely skip steps 8 and 9.

   cp -f configuration.xml Acsera.properties key 
   $MIDDLEWARE_HOME/gc_inst/user_projects/domains/GCDomain/EMGC_ADPMANAGER1/ADPManager.ear/ADPManager.war/config/
   

9. Add the following properties at the end of the Acsera.properties files you just copied:

   JMXContainer.DisableComputeClassPaths = true
   DeployerClient.CoreJAgentJars=lib/bcel.jar; lib/com.oracle.diagnostics.instrumentor_1.8.0.0-try-03.jar; lib/jManagement Agent1.5.jar
   DeployerClient.WLDFJar=com.oracle.diagnostics.instrumentor_1.8.0.0-try-03.jar
   

10. Start ADP Manager using the Oracle WebLogic Server Administration Console.

11. Redeploy all ADP Agents on the previously configured target servers.

    Note that you will essentially redeploy the Management Agents on top of the original Management Agents. For instructions, see the following:

    http://docs.oracle.com/cd/E24628_01/install.121/e22624/adp_installation.htm#CJHFFADD
    

12. Restart the target servers.

2.7.2 Upgrading JVM Diagnostics

To upgrade JVMD, complete the following:

1. Unzip the jvmd.zip archive, which is in the following location:

   $MIDDLEWARE_HOME/plugins/oracle.sysman.emas.oms.plugin_12.1.0.2.0/archives/jvmd/
   

   This will create a set of files in the same directory, including jammanager.ear.

2. Log in to the Oracle WebLogic Server Administration Console of the EMGC Domain and click Servers.

3. Locate all deployed JVMD Managers.

   These will be managed servers that contain "EMGC_JVMDMANAGER" in the server name, such as "EMGC_JVMDMANAGER1". For each JVMD Manager, perform the steps below. For illustration purposes, the server name "EMGC_JVMDMANAGER1" will be used.

4. Start EMGC_JVMDMANAGER1, if it is not already running.

5. Click Lock & Edit in the Change Center on the Oracle WebLogic Server Administration Console.

   Figure 2-88 Oracle WebLogic Server Administration Console Lock & Edit Button

   
   

6. Select Deployments, then click the checkbox for Enterprise Application for a JVMD Manager.

   For example: jammanagerEMGC_JVMDMANAGER1

7. Click Update.

8. Note the source path to the existing jammanager.ear.

   For example:

   $MIDDLEWARE_HOME/gc_inst/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/upload/jammanagerEMGC_JVMDMANAGER1/app/jammanager.ear
   

9. At the source path you noted in the previous step replace the existing jammanager.ear with the jammanager.ear from the following location:

   $MIDDLEWARE_HOME/plugins/oracle.sysman.emas.oms.plugin_12.1.0.2.0/archives/jvmd/
   

10. Click Next to complete the update.

11. If you have Middleware Diagnostics Advisor (MDA) enabled, complete the following to disable it for every Oracle WebLogic Domain and Oracle WebLogic Server target it has been enabled for:

    1. In Cloud Control, navigate to the target home page for a WebLogic Server domain.

    2. From the WebLogic Domain menu, select Diagnostics, then select Setup Middleware Diagnostics Advisor.

       Figure 2-89 Setup Middleware Diagnostics Advisor

       
       

    3. Select each target that MDA has been enabled for, then click Disable, as shown below.

       Figure 2-90 MDA Configuration (Enable / Disable)

       
       

12. Undeploy existing JVMD Management Agents from the target server.

    Management Agents will usually have names such as javadiagnosticManagement Agent_ServerName.

13. Remove the corresponding Java Virtual Machine targets using Enterprise Manager Cloud Control:

    1. From the Targets menu, select Middleware.

    2. Locate the Java Virtual Machine targets that correspond to the JVMD Management Agents you undeployed.

    3. Select each Java Virtual Machine target in the table, then click Remove.

14. Redeploy all JVMD Management Agents.

    For more information, see the following:

    http://docs.oracle.com/cd/E24628_01/install.121/e22624/jvmd_installation.htm#CHDCFFGC
    

15. After all JVMD Management Agents have been redeployed, return to the Middleware Diagnostics Advisor Configuration page and re-enable MDA for each target it was previously enabled for.