Patching Oracle Service Bus

Fusion Middleware patching through Enterprise Manager is supported for targets like WebLogic Domain, SOA, and Oracle Service Bus (OSB). This topic contains the procedure to patch an Oracle Service Bus using the Enterprise Manager.

A single node of Oracle Service Bus Domain consists of Service Bus Domain Target, Service Bus Cluster Target, Service Bus Target, WebLogic Cluster Target, and WebLogic Server Targets.

The Service Bus Cluster Target comprises of all the Service Bus targets. The WebLogic Cluster Target comprises all the WebLogic Server targets. The WebLogic Server Targets comprise of a single Administration Server and a Managed Server.

This procedure of patching an Oracle Service Bus through the Enterprise Manager patching framework comprises of creating a patch plan by selecting a Service Bus Target or a Service Bus Cluster Target. The user can select a single target and the associated targets are included automatically during patching. The user can also edit the plan to add more patches, analyze, rollback, and create a template.

For more information on creating a patch plan, see Creating a Patch Plan.

Before you begin patching of Oracle Service Bus, ensure that you meet the following prerequisites:

  • The user needs to ensure that Oracle Home collection is complete. Patching throws an error if one or more Oracle Homes are not discovered.

    Note:

    The pre-requisite for patching WebLogic domains is that the underlying Oracle Home must be discovered as a target. For SOA 11g, 12c and Service Bus domains this is automatically handled. However, for Service Bus 11g when the domain is discovered the OH is not discovered as a target. If you attempt to patch such a domain then the following warning is displayed. To overcome this, ensure that the Middleware Home and the underlying Oracle Homes are discovered as targets and the configuration collections for Oracle Home targets are the current ones.

    There is no Oracle Home (OH) target associated for the patch being applied. To rectify this issue the user should promote the OH being patched, by choosing the "Discover Promote Oracle Home Target" job in Enterprise Manager. Ensure the OH target is available after this operation is completed, and the configuration metrics for the OH target is collected.
  • The user needs to ensure to set the Oracle Homes and Domain administrator credentials.

  • For offline patching, the user needs to ensure to have the necessary OPatch downloaded from MOS and manually upload to the saved patches.

    For patching WebLogic Server 12.2.1.x Enterprise Manager expects Opatch release 13.3.0.0.0 to be available in the software library. At the time of releasing Enterprise Manager, this version of OPatch was not available for download from MOS. Hence, when patching WebLogic Server 12.2.1.x, Enterprise Manager uses the Opatch installed in the WebLogic Server Oracle Home instead of trying to download the latest OPatch from MOS.

  • The target selector needs metadata from My Oracle Support to filter the targets based on the patch types. The user must run Refresh from My Oracle Support job in online mode. In case of offline mode the user must upload the catalog.zip file.

  • Patching on Oracle Service Bus is supported on the following versions:

    • 11.1.1.5.0

    • 11.1.1.6.0

    • 11.1.1.7.0

    • 11.1.1.9.0

    • 12.1.3.0.0

    • 12.2.1.0.0

  • The SOA patch containing SQL script may fail if the metadata is not specified in the right format. The metadata has to be specified in the Deployment Options page in the field Location of Post Install SQL Script.

    Ensure that the SQL scripts are specified in the following format:

    <patch_number1>:<sql_script1_location>:<sql_script2_location>:<patch_number2>:<sql_script3_location>:...

    Example:

    14082705:%ORACLE_HOME%/rcu/integration/soainfra/sql/createschema_soa infra_oracle.sql

    Additionally, this information is available in the Post-Installation Instructions in the README.txt file. In case the Location of Post Install SQL Script field is left blank or the right SQL script is not specified then the following error message is mentioned in the log:

    One or more SQL files included in this patch are not selected for post-patch execution. To correct this, update your selection in the "Deployment options" page. To continue without making any changes, run the required SQL scripts manually after the patch is deployed successfully.
  • The relevant patch, target, and domain details are displayed in the following table:

    Patch Targets

    SOA

    SOA Infrastructure

    Oracle Service Bus

    Service Bus

To apply patching for Oracle Service Bus, follow these steps:

  1. Create a patch plan.
  2. From the Enterprise menu, select Provisioning and Patching, then select Saved Patches.
  3. Click Upload.
  4. Provide the location of the patch file and the patch metadata, and click Upload.
  5. Once the patch has been uploaded, select the patch. This takes you to the patch home page.
  6. Click Create Plan.
  7. Enter the name of the plan in the Plan Name field.
  8. Enter Oracle Service Bus or Service Cluster Targets As the target type.

    Note:

    In case a single Service Bus component is selected, all the associated targets are automatically picked up for patching. Ensure to select one Service Bus component.

  9. Enter the host name and click Create Plan.
  10. The patch plan is created and can be deployed.
  11. From the Enterprise menu, select Provisioning and Patching, then select Patches & Updates.
  12. Select the patch plan that you created from the list of patch plans.
  13. Click Next.
  14. Enter the rest of the details in the EM User Interface, validate the credentials, and choose the customization required. Ensure that the data prefilled or selected is accurate.
  15. Click Analyze. The deployment procedure is submitted.
  16. Once analysis is complete click Review, for the tool to review, analyze, and validate the details.
  17. Click Next.
  18. Click Deploy. The deployment procedure is submitted and patching is in progress.
  19. The patch is deployed.
  20. The Oracle Service Bus patch is successfully applied.

    Note:

    For Oracle Service Bus 11g targets patch recommendations are not displayed. The user can search for the recommended patches through the Recommended Patch Advisor search in the Patches and Updates.