• Single OMS – OMS application that runs from a single OMS instance of the system. OMSPatcher performs patching and deployment operations

• Multiple OMS – OMS applications that run on two or more hosts. The OMSes are connected by the Oracle WebLogic domain and separate managed servers. There is a one-to-one mapping between the managed servers and the separate OMS bits residing on a single machine. There are two ways in which patches are applied on a multiple OMS setup.

  • Automated: A job is automatically submitted that deploys the patches (Linux systems) on each OMS.
  • Manual: OMSPatcher provides auto-generated bash scripts (one per OMS instance) for UNIX based systems. OMSPatcher on Linux skips automatic patching on add OMSes if the -skipautopatch_addoms parameter is passed (one per OMS instance expect primary OMS).

    OMSPatcher does not support automatic patching of add OMSes on Windows. For Windows, OMSPatcher provides auto-generated batch scripts, one per OMS instance expect primary OMS.(text and HTML)

    For both cases, the administrator needs to follow the steps given by OMSPatcher.

• Single Instance Database or Real Application Cluster - shared or Real Application Cluster (RAC)

Example: Multi-OMS System

The following figure illustrates a multi-OMS deployment. The following terms are used:

• Administrator: Person installing patches to the OMS core and plug-in homes.

• Local OMS: OMS instance on which the administrator runs OMSPatcher.

• Add OMS: OMS instances on other machines (within the same OMS domain as the local OMS) where the administrator has not started any patching operations.

Figure 5-1 Simple Multi-OMS System

For a single OMS system (primary), OMSPatcher will execute the patching steps. For a multi-OMS UNIX system, a job is automatically submitted to deploy the patches. If you need to deploy the patches manually, OMSPatcher generates bash scripts for execution, one per OMS instance for all OMSes (except the primary OMS); follow the instructions given by OMSPatcher to find those scripts. For Windows multi-OMS systems, OMSPatcher will generate bash scripts for all OMSes except the primary OMS.

Enterprise Manager patches have been converted to a System patch format in order to support patch automation.

What is a System Patch?

A System patch contains several sub-patches whose locations are determined by a file called bundle.xml in the top level directory of the patch. The sub-patches are intended for different sub-systems of a system that correspond with the OMS core and plug-in home organization.

A typical System patch format is organized as follows:

<System patch location - directory>
|_____ Readme.txt (or) Readme.html
       bundle.xml
       automation
	      |_____ apply_automation.xml
         |_____rollback_automation.xml
       Sub-patch1
                |_____ etc
                       |_____config  
                                |_____ inventory.xml
                                |_____ actions.xml
                                |_____ artifact_apply.xml
                                |_____ artifact_rollback.xml
                |_____ files/Subpatch1 'payload'
       Sub-patch2
                |_____ etc
                       |_____config  
                                |_____ inventory.xml
                                |_____ actions.xml
                                |_____ artifact_apply.xml
                                |_____ artifact_rollback.xml
                |_____ files/Subpatch1 'payload'

OMSPatcher supports rolling mode only for System patches without any automation (binary-only patching through OMSPatcher). For all other artifacts, such as Metadata Registration Service (MRS) or SQL, OMSPatcher only supports complete system downtime patching operations.

Rapid Platform Update

OMSPatcher also supports {Varref: nzdt}Rapid Platform Update, which allows most of the patching process to take place while the OMS is running, significantly reducing system downtime. For more information about Rapid Platform Update, see .Rapid Platform Update

Refer to the patch README for the explicit information on supported patching methodologies.

export WLST_PROPERTIES="-Dweblogic.security.SSL.ignoreHostnameVerification=true"

1. Navigate to the Oracle home and run the following script to create the WebLogic encrypted configuration and key files.

   On UNIX:

   $ OMSPatcher/wlskeys/createkeys.sh -oh <ORACLE_HOME> -location <location to put the encrypted files>

   On Windows:

   $ OMSPatcher\wlskeys\createkeys.cmd -oh <ORACLE_HOME> -location <location to put the encrypted files>

   When prompted, enter the credentials of the Oracle WebLogic Administration Server that manages the Managed Server on which OMS instance is deployed. Two files are generated with the file names: config and key.

2. Create the property file with the following entries:

   AdminServerURL=t3s://<host address from where admin server is running>:<port of the admin server>
   AdminConfigFile=<'config' file location>
   AdminKeyFile=<'key' file location>
   Sys_pwd=<sys password> 
   Sysman_pwd=<sysman password>

   The values for host address and port of admin server can be located by running emctl status oms -details on an Oracle Home.

   Example

   emctl status oms -details
           Oracle Enterprise Manager Cloud Control 13c Release 5
           Copyright (c) 1996, 2021 Oracle Corporation. All rights reserved.
           Enter Enterprise Manager Root (SYSMAN) Password :
           Console Server Host : host01.example.com
           HTTP Console Port : 7788
           HTTPS Console Port : 7803
           HTTP Upload Port : 4889
           HTTPS Upload Port : 4903
           EM Instance Home : /u01/oracle/EM135/gc_inst/em/EMGC_OMS1
           OMS Log Directory Location :
             /u01/oracle/EM135/gc_inst/em/EMGC_OMS1/sysman/log
           OMS is not configured with SLB or virtual hostname
           Agent Upload is locked.
           OMS Console is locked.
           Active CA ID: 1
           Console URL: https://host01.example.com:7803/em
           Upload URL: https://host01.example.com:4903/empbs/upload
           WLS Domain Information
           Domain Name : GCDomain
           Admin Server Host : host01.example.com
           Admin Server HTTPS Port: 7102
           Admin Server is RUNNING
           Oracle Management Server Information
           Managed Server Instance Name: EMGC_OMS1
           Oracle Management Server Instance Host: host01.example.com
           WebTier is Up
           Oracle Management Server is Up
           JVMD Engine is Up

   Following is the example of how a property file (constructed by the above mentioned guidelines) should appear:

   AdminServerURL=t3s://my_admin_server.mycompany.com:7101
   AdminConfigFile=/scratch/patch/oms_install_dir/middleware/oms/config/config
   AdminKeyFile=/scratch/patch/oms_install_dir/middleware/oms/config/key
   Sys_pwd=mysyspassword
   Sysman_pwd=mysysmanpassword

   Note:

   To retrieve the WebLogic Administration Server URL details, run the following commands on the OMS home that you are patching:

   On Unix:

   $ORACLE_HOME/bin/emctl status oms -details

   On Windows:

   %ORACLE_HOME%\bin\emctl.bat status oms -details

   The command output contains the WebLogic Administration Server details. Here is an example on how to construct the URL with these output details.

   Example:

   WLS Domain Information
    
   Domain Name : GCDomain
   Admin Server Host : my_wls.mycompany.com
   Admin Server HTTPS Port: 7103

   To construct the Administrator Server URL, use the following syntax:

   t3s://<admin server host>:<port>

   In this example, the URL translates as follows:

   t3s://my_wls.mycompany.com:7103

Once you have downloaded the patch, see the patch README for explicit patch details and instructions on applying the patch. You can find the README at the following location

<System patch location>/README.txt (or) README.html

As you step through the patching operations in the README, running omspatcher apply (depending on the configuration that is patched, primary or standby) will generate a custom, environment-specific version of the README for patching operations for the primary site multi-OMS or standby site OMS systems. For a primary site single OMS system, running omspatcher apply will perform patching and deployment operations.

On your local OMS instance, run the following command from the top level System patch directory:

omspatcher apply <patch>

In a multi-OMS UNIX system, the primary OMS is patched using the omspatcher apply command. Upon completing the primary OMS patching, the OMSpatcher utility will submit a job to patch additional OMS instances. The job name will appear in the terminal from which the OMSpatcher utility is executed on the primary OMS server. The status of the multi-OMS patching job can be verified through the Enterprise Manager console or via emcli command. For Windows multi-OMS systems, OMSPatcher will generate a bash script that can be run on all OMSes except the primary OMS.

There are two ways in which patches are applied on a multiple OMS setup.

• Automated: A job is automatically submitted that deploys the patches (Linux systems) on each additional OMS.
• Manual: OMSPatcher provides auto-generated bash scripts that can be run on all the OMSes except the primary OMS. (UNIX and Windows based systems).

See the patch README for explicit patch details and instructions on deinstalling the patch. You can find the README at the following location

<System patch location>/README.txt (or) README.html

As you step through the patch deinstallation operations in the README, running omspatcher rollback (depending on the configuration that is patched, primary or standby) will generate a custom, environment-specific version of the README for patching operations for the primary site multi-OMS or standby site OMS systems. For a primary site single OMS system, running omspatcher rollback will perform the deinstallation operations.

On your local OMS instance, run the following command from the top level System patch directory:

omspatcher rollback -id <list of comma separated sub-patches of System patch

For a multi-OMS UNIX system, OMSPatcher generates bash scripts for execution, one per OMS instance; follow the instructions given by omspatcher to find those scripts. For Windows multi-OMS systems, OMSPatcher will generate customized patching instructions/commands for the environment in text and HTML formats; administrators must execute these instructions to patch the various OMSs.

There are two ways in which patches are applied on a multiple OMS setup.

• Automated: A job is automatically submitted that deploys the patches (Linux systems) on each OMS.
• Manual: OMSPatcher provides auto-generated bash scripts (one per OMS instance) for UNIX based systems. For Windows, it only provides context-sensitive steps (text and HTML). For both cases, the administrator needs to follow the steps given by OMSPatcher.

After the patch is applied or rolled back, you can run the omspatcher lspatches command to generate a comprehensive Component type - patches map of the OMS homes and installed patches.

$omspatcher lspatches 
OMSPatcher Automation Tool
Copyright (c) 2017, Oracle Corporation.  All rights reserved.

OMSPatcher version : <latest_OMSPatcher_version>
OUI version        : 13.9.4.0.0
Running from       : $ORACLE_HOME 
Log file location  : $ORACLE_HOME/cfgtoollogs/omspatcher/opatch2023-02-15_11-56-30AM_1.log

Component Name/Version                Component Type     System Patch    (Sub)-Patches       Patch Description
------------------------              -------------      -------------   --------------      ------------------

oracle.com.fasterxml.jackson.jaxrs.jacks  Core           N/A             32253037            WLS PATCH SET UPDATE 12.2.1.4.201209
on.jaxrs.base/2.9.9.0.0 

oracle.jrf.iau/12.2.1.4.0                 Core           N/A             31666198            OPSS Bundle Patch 12.2.1.4.200724

oracle.wls.common.cam.wlst/12.2.1.4.0     Core           N/A             32253037            WLS PATCH SET UPDATE 12.2.1.4.201209

oracle.ohs2/12.2.1.4.0                    Core           N/A             31808404            OHS (NATIVE) BUNDLE PATCH 12.2.1.4.200826

oracle.com.fasterxml.jackson.jaxrs.jacks  Core           N/A             32253037            WLS PATCH SET UPDATE 12.2.1.4.201209
on.jaxrs.json.provider/2.9.9.0.0

oracle.com.fasterxml.jackson.core.jackso  Core           N/A             32253037            WLS PATCH SET UPDATE 12.2.1.4.201209
n.databind/2.9.9.0.0

oracle.wls.jrf.tenancy.common.sharedlib/  Core           N/A             32253037            WLS PATCH SET UPDATE 12.2.1.4.201209
12.2.1.4.0

oracle.jrf.adfrt/12.2.1.4.0               Core           N/A             32458315            ADF BUNDLE PATCH 12.2.1.4.210203 

oracle.com.fasterxml.jackson.module.jack  Core           N/A             32253037            WLS PATCH SET UPDATE 12.2.1.4.201209
son.module.jsonschema/2.9.9.0.0

oracle.jrf.toplink/12.2.1.4.0             Core           N/A             32412974            One-off

oracle.wls.jrf.tenancy.ee.only.sharedlib  Core           N/A             32253037            WLS PATCH SET UPDATE 12.2.1.4.201209
/12.2.1.4.0

oracle.webcenter.wccore/12.2.1.4.0        Core           N/A             31818221            One-off 

oracle.log4j.log4j/2.11.1.0.0             Core           N/A             32253037            WLS PATCH SET UPDATE 12.2.1.4.201209

oracle.xdk.jrf.xmlparserv2/12.2.1.4.0     Core           N/A             26626168            One-off 

oracle.fmwconfig.common.wls.shared.inter  Core           N/A             32253037            WLS PATCH SET UPDATE 12.2.1.4.201209
nal/12.2.1.4.0 

oracle.com.fasterxml.jackson.module.jack  Core           N/A             32253037            WLS PATCH SET UPDATE 12.2.1.4.201209
son.module.jaxb.annotations/2.9.9.0.0 

oracle.sysman.vi.oms.plugin/13.5.1.0.0    Plugin         1111112         1111140             EM nZDT Patch for TargetPrivs

oracle.com.fasterxml.jackson.core.jackso  Core          N/A              32253037            WLS PATCH SET UPDATE 12.2.1.4.201209
n.core/2.9.9.0.0

oracle.opss.wls/12.2.1.4.0                Core          N/A              31708760            One-off

oracle.org.bouncycastle.bcprov.jdk15on/1  Core          N/A              32253037            WLS PATCH SET UPDATE 12.2.1.4.201209
.60.0.0.0

oracle.wls.core.app.server/12.2.1.4.0     Core          N/A              32253037            WLS PATCH SET UPDATE 12.2.1.4.201209

oracle.wls.security.core.sharedlib/12.2.  Core          N/A              32253037            WLS PATCH SET UPDATE 12.2.1.4.201209
1.4.0

oracle.wls.shared.with.cam/12.2.1.4.0     Core          N/A              32253037            WLS PATCH SET UPDATE 12.2.1.4.201209

oracle.org.bouncycastle.bcprov.ext.jdk15  Core          N/A              32253037            WLS PATCH SET UPDATE 12.2.1.4.201209
on/1.60.0.0.0

oracle.coherence/12.2.1.4.0               Core          N/A              122146              Bundle patch for Oracle Coherence Version 12.2.1.4.6

oracle.xdk.jrf.jaxp/12.2.1.4.0            Core          N/A              26626168            One-off

oracle.wls.libraries/12.2.1.4.0           Core         N/A            32253037            WLS PATCH SET UPDATE 12.2.1.4.201209

oracle.com.fasterxml.jackson.dataformat.  Core          N/A            32253037            WLS PATCH SET UPDATE 12.2.1.4.201209
jackson.dataformat.xml/2.9.9.0.0 

oracle.opss.core/12.2.1.4.0               Core          N/A            31666198            OPSS Bundle Patch 12.2.1.4.200724
                                         N/A                 31708760              One-off

oracle.webservices.wls/12.2.1.4.0                Core          N/A            32253037            WLS PATCH SET UPDATE 12.2.1.4.201209

oracle.wls.security.core/12.2.1.4.0              Core          N/A            32253037            WLS PATCH SET UPDATE 12.2.1.4.201209

oracle.sysman.top.oms/13.5.0.0.0                 Core                1111112            1111143

oracle.sysman.rcu/12.2.1.4.0                     Core                N/A               30152128            One-off

oracle.org.bouncycastle.bcpkix.jdk15on/1         Core                N/A               32253037            WLS PATCH SET UPDATE 12.2.1.4.201209
.60.0.0.0

oracle.webservices.base/12.2.1.4.0                Core                N/A                32253037            WLS PATCH SET UPDATE 12.2.1.4.201209

oracle.com.fasterxml.jackson.core.jackso          Core                N/A                 32253037            WLS PATCH SET UPDATE 12.2.1.4.201209
n.annotations/2.9.9.0.0

oracle.wls.evaluation.database/12.2.1.4.          Core                N/A                32253037            WLS PATCH SET UPDATE 12.2.1.4.201209
0 

oracle.wls.admin.console.en/12.2.1.4.0            Core             N/A             32253037        WLS PATCH SET UPDATE 12.2.1.4.201209


NOTE: N/A indicates that the subpatch mentioned in the Subpatches column was applied as a one-off patch and not as part of any system patch.

OMSPatcher has saved inventory details for the above component at below location.
"/$ORACLE_HOME" 

For more details on installed patch(es), Please do "$ORACLE_HOME/OPatch/opatch lsinventory -details"

OMSPatcher succeeded.

To determine the version numbers of the various OMSPatcher utilities (OPlan, OsysModel) that reside on your system, you can run omspatcher version.

bash-3.2$ omspatcher version
OMSPatcher Version: <latest OMSPatcher version>
OPlan Version: 12.1.0.2.2
OsysModel build: Wed Mar 21 18:20:48 PDT 2018

If you have configured a standby OMS for High Availability, refer to the chapter on "Enterprise Manager Disaster Recovery" and the appendix on Standby OMSs Using Standby WebLogic Domain" both of which can be found in the Oracle Enterprise Manager Advanced Installation and Configuration Guide.