7 Upgrading Oracle Service Bus

Describes the upgrade-specific tasks for upgrading Oracle Service Bus without Oracle SOA Suite and Business Process Management.

When upgrading Oracle Service Bus 11g to Release 12c, you must perform the pre- and post-upgrade tasks described in this chapter. Failure to do so may result in a non-functioning post-upgrade environment.

7.1 Understanding the Oracle Service Bus Upgrade to 12c

Follow this process flow to upgrade an Oracle Service Bus deployment that does not include SOA Suite.

Oracle Service Bus (OSB) can be upgraded to 12c (12.2.1.1) with or without Oracle SOA Suite and Business Process Management. The upgrade steps in this chapter describe how to upgrade Oracle Service Bus without SOA.

If OSB is part of your SOA 11g or previous 12c domain, and you will be upgrading OSB as part of your SOA Suite upgrade to 12c (12.2.1.1), follow the standard upgrade process described in Upgrading to SOA Suite and Business Process Management 12c (12.2.1.1).

If you are upgrading Oracle Service Bus without SOA, use the upgrade procedures documented in this chapter. Note that even though your domain does not include SOA, you will still have to upgrade the _SOAINFRA schema to upgrade OSB data. OSB does not have a separate schema.

Note:

Be sure to review all of the Oracle Service Bus-specific pre- and post-upgrade steps. All Service Bus upgrades (with and without SOA) require these additional steps when upgrading to 12c (12.2.1.1).

Description of GUID-BC505C48-EFBB-456B-9256-9979A9C6B2C9-default.png follows
Description of the illustration GUID-BC505C48-EFBB-456B-9256-9979A9C6B2C9-default.png
Step Description More Information

Upgrade the WebLogic server and JRF that will host your OSB domain.

You must install the 12c infrastructure and then upgrade the infrastructure domain before upgrading Oracle Service Bus.

 Installing WebLogic Server and JRF Infrastructure

Install Oracle Service Bus.

Obtain the Oracle Service Bus distribution and install the content to a new Oracle Home.

Installing the Oracle Service Bus

Upgrade Oracle Service Bus.

Upgrade your existing Oracle Service Bus domain.

Upgrading an OSB Domain (Without SOA)

Perform all post-upgrade tasks.

Perform the standard 12c post-upgrade tasks, as well as any post-upgrade OSB-specific tasks, that apply to your deployment.

Performing Post Upgrade Tasks

Performing Post Upgrade Tasks for Oracle Service Bus

Troubleshooting Oracle Service Bus

7.2 Upgrading Multiple Components that use UMS in a Single OSB Domain (Not Supported)

If your Oracle Service Bus 11g topology is configured with more than one component within a single domain, then you will not be able to upgrade to 12c (12.2.1.1)

Certain Fusion Middleware components such as Oracle SOA, Oracle Service Bus (OSB) and Business Activity Monitoring (BAM) have a dependency on User Messaging Service (UMS) in 12c. If you configure more than one of these components within a single 12c (12.2.1.1) domain, then each of these components must run within its own cluster — even if there is only one server that runs that component.

In order to upgrade these components, you must create a separate cluster for each component during the domain reconfiguration as described in Clusters.

The supported upgrade topology for these components is described in Upgrading a Clustered Topology.

7.3 Performing Pre-Upgrade Tasks for Oracle Service Bus (OSB)

If you are upgrading Oracle Service Bus, you must perform the following tasks before you begin the upgrade. Review your own use case scenarios and existing deployment to determine if the following tasks apply to your environment.

  1. Deploying Oracle Web Services Manager Policy Manager in Your 11g Environment
  2. Exporting Services, Projects and Resources when Upgrading Oracle Service Bus
  3. Deleting All Services, Projects and Resources
  4. Migrating Oracle Service Bus Resources from Previous Releases

7.3.1 Deploying Oracle Web Services Manager Policy Manager in Your 11g Environment

If Oracle Web Services Manager (OWSM) Policy Manager is not already deployed in your Oracle Service Bus 11g environment, then you must manually deploy it before you upgrade to 12c.

In 11g, both WebLogic security policies and OWSM policies were supported on Oracle Service Bus. As of 11g (11.1.1.7), WebLogic Security policies were deprecated, and are not supported in 12c (12.1.3). Because WebLogic security policies were available in 11g, deployment of the OWSM Policy Manager and use of the OWSM policies was optional. Since only OWSM policies are supported in 12c, OWSM Policy Manager deployment is mandatory.

For information on manually deploying the OWSM Policy Manager in your 11g environment, see "Installing OWSM with WebLogic Server" in Securing Web Services and Managing Policies with Oracle Web Services Manager.

7.3.2 Exporting Services, Projects and Resources when Upgrading Oracle Service Bus

You must export services, projects and resources into a configuration JAR file before you can upgrade to Oracle Service Bus 12.2.1. After the upgrade, you will import the JAR file to the new 12c environment.

Note that you can manually export resources and services from older, supported releases. See Migrating Oracle Service Bus Resources from Previous Releases.

For more information, see "Importing and Exporting Resources and Configurations" in Developing Services with Oracle Service Bus.

7.3.3 Deleting All Services, Projects and Resources

After the export, you must delete all user-created services, projects and resources before the upgrade.

For information on using the Oracle Service Bus Console to delete resources, see How to Delete Projects, Folders, and Resources.

For information on using JDeveloper to delete resources, see How to Delete a Project or Resource.

7.3.4 Migrating Oracle Service Bus Resources from Previous Releases

You can manually export resources and services from the following releases and use them with Oracle Service Bus 12c (12.2.1.1):

  • Oracle Service Bus 12c Release 12.1.3 and 12.2.1.0

  • Oracle Service Bus 11g Release: 11.1.1.7.0

  • Oracle Service Bus 10.3 Releases: 10.3.1 and 10.3.0

  • AquaLogic® Service Bus Releases 3.0 and later

For more information, see "Importing and Exporting Resources and Configurations" in Developing Services with Oracle Service Bus.

7.4 Installing WebLogic Server and JRF Infrastructure

Before you can upgrade, you must first install Oracle WebLogic Server and JRF using the 12c (12.2.1.1) Infrastructure distribution.

SOA Suite requires that Oracle WebLogic Server and JRF must be installed using the 12c (12.2.1.1) Infrastructure distribution.

See Installing and Configuring the Oracle Fusion Middleware Infrastructure for detailed instructions.

Caution:

When installing the Infrastructure distributions, do not use the Configuration Wizard to configure the domain. You will use the new Reconfiguration Wizard to configure the 11g domain during the upgrade process.

Note:

You must have the Infrastructure distribution installed before you can upgrade to SOA 12c (12.2.1.1). The only application server that Oracle Fusion Middleware 12c (12.2.1.1) supports is the Oracle WebLogic Server.

If you previously installed and configured the Infrastructure components using a previous 12c release, then you must upgrade to Infrastructure 12c (12.2.1.1).

For more information, see Upgrading from a Previous Infrastructure 12c Release.

7.5 Installing the Oracle Service Bus

To install Oracle Service Bus, refer to Installing and Configuring Oracle Service Bus.

You can install and upgrade Oracle Service Bus without Oracle SOA Suite and Business Process Management, but you must still install the Oracle Fusion Middleware Infrastructure 12c (12.2.1) before upgrading Oracle Service Bus. For more information, see Installing and Configuring the Oracle Fusion Middleware Infrastructure.

Note:

If you want to use Oracle Web Services Manager policies with Oracle Servie Bus, then you must select the Oracle Web Services Manager extension template after selecting one of the Oracle Service Bus domain templates when configuring the Oracle WebLogic domain.

7.6 Creating Schemas for Oracle Service Bus

Oracle Service Bus 12c requires the <prefix>_SOAINFRA, <prefix>_UMS, and <prefix>_STB schemas. You must create these schemas before you start the Upgrade Assistant.

Oracle Service Bus does not have its own schema, as all database schema data for Oracle Service Bus is incorporated in the SOAINFRA schema. So, while its possible to run Oracle Service Bus without running Oracle SOA, you must create the _SOAINFRA, _UMS and _STB schemas before you begin the upgrade.

Note:

In Oracle Fusion Middleware 11g releases it was possible to run Oracle Service Bus (OSB) without a database, as the SOA schema was not required. In 12c, however, you must have a supported database configured with the required SOA schemas before you can run Oracle Service Bus 12c (12.2.1.1).

You will run the RCU from your new 12c Oracle Home directory.

  1. Set the JAVA_HOME variable and add JAVA_HOME/bin to $PATH, if you have not done so already..
  2. Navigate to the 12c_ORACLE_HOME/oracle_common/bin directory on your system.
  3. Start RCU:
    On Unix system, enter:

    ./rcu

    On Windows system, enter.

    .\rcu.bat

  4. Complete the schema creation by navigating the RCU screens. For more information, see Navigating the RCU Screens to Create the Schemas in Installing and Configuring the Oracle Fusion Middleware Infrastructure

7.6.1 Creating the Required SOA Schemas Before You Upgrade from 11g

If you are upgrading from a supported 11g release, you may need to create the new 12c required schemas in a supported database before you can upgrade.

Note:

OID-based Security Store Users Only: If you are using an OID-based security store in 11g, you must create the new 12c schema _STB and the _OPSS schema using the Repository Creation Utility (RCU).

You do not need to reassociate an OID-based security store before upgrade. When upgrading schemas with the Upgrade Assistant, select the new OPSS schema and the Upgrade Assistant upgrades the OID-based security store automatically.

The 12c OPSS database schema is required so that you can reference the 12c schema during the reconfiguration of the domain. Your domain continues to use the OID-based security store after the upgrade is complete.

Table 7-1 Required Schemas for SOA and SOA integrated products

If you are upgrading... Create these 12c schemas before you upgrade

SOA Suite (SOA)

Service Table (_STB)

Audit Services (_IAU)

Business Process Monitoring (BPM)

Service Table (_STB)

Audit Services (_IAU)

Business Activity Monitoring (BAM)

Schemas required for SOA Suite

And:

WebLogic Services (_WLS)
Managed File Transfer (MFT)

Service Table (_STB)

Audit Services (_IAU)

Oracle Service Bus (OSB)

In Oracle Fusion Middleware 11g releases it was possible to run Oracle Service Bus (OSB) without a database, as the SOA schema was not required. In 12c, however, you must have a supported database configured with the required SOA schemas before you can run Oracle Service Bus 12c (12.2.1.1).

SOA Infrastructure (_SOAINFRA)

Service Table (_STB)

User Messaging (_UMS)

NOTE: It is possible to install Oracle Service Bus without running Oracle SOA, but you must create the _SOAINFRA and _STB schemas.

User Messaging Service (UMS)

Service Table (_STB)

Audit Services (_IAU)
To create schemas using the RCU:
  1. Set the JAVA_HOME environment variable and add $JAVA_HOME/bin to $PATH, if you have not done so already. The current supported JDK version is jdk1.8.0_77
  2. Navigate to the 12c ORACLE_HOME/oracle_common/bin directory on your system.
  3. Start RCU:
    On Unix operating systems:

    ./rcu

    On Windows operating systems:

    rcu.bat

  4. Complete the schema creation by navigating the RCU screens. When creating new schemas for the upgrade, make sure to choose Select existing prefix and locate the prefix you used to create your existing schemas.
    NOTE: The Common Infrastructure Services (prefix_STB) and Oracle Platform Security Services (prefix_OPSS) schemas are selected by default if they have not yet been created.
    .
    For more information, see Navigating the RCU Screens to Create the Schemas in Installing and Configuring the Oracle Fusion Middleware Infrastructure

7.7 Upgrading an OSB Domain (Without SOA)

To upgrade Oracle Service Bus, you will follow the basic procedures described in Table 7-2.

Table 7-2 Upgrade Assistant Screens: Upgrading Schemas

Screen Description and Action Required

Welcome

This screen provides an overview of the Upgrade Assistant and some information about important pre-upgrade tasks.

Schemas

Select Individually Selected Schemas.

NOTE: There is no OSB schema. All database schema data for Oracle Service Bus is incorporated in the SOAINFRA schema.

Available Components

This screen provides a list of installed Oracle Fusion Middleware components that have schemas that can be upgraded. When you select a component, the schemas and any dependencies are automatically selected.

When upgrading OSB, select Metadata Services, Audit Services and Oracle Platform Security Services.

Description of GUID-C1299CDA-792A-4250-8616-CDB6449CCE20-default.png follows
Description of the illustration GUID-C1299CDA-792A-4250-8616-CDB6449CCE20-default.png

Domain Directory

This screen appears if you selected Oracle Platform Security Services or Oracle Audit Services on the Available Components screen.

Enter the absolute path to the existing WebLogic domain directory, or click Browse to navigate to and select the 11g domain directory you are upgrading.

Prerequisites

Check that the prerequisites for schema upgrade are met. You must select each prerequisite before you click Next.

CAUTION: Upgrade Assistant will NOT verify that these prerequisites have been met.

Schema Credentials

Use this screen to enter database connection details for each of the schemas you are upgrading.

Examine

Review the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade.

Verify that the Source Version displayed for each schema is listing the correct version number for the schema to be upgraded.

Upgrade Summary

Review the summary of the options that you have selected for schema upgrade. Verify that the correct Source and Target versions are listed for each schema you intend to upgrade.

Click Upgrade to upgrade the schemas, or click Back if you wish to change the configurations.

Upgrade Progress

Review the status of the current upgrade process.

NOTE: The progress bar on this screen displays the progress of the current upgrade procedure. It does not indicate the time remaining for the upgrade.

Click Next when the upgrade is complete.

Upgrade Success

Click Close if the Upgrade was successful.

If the upgrade failed or if you canceled the upgrade before it completed successfully, you should review the log files, restore the backed up environment, and restart the Upgrade Assistant.

7.8 Reconfiguring an OSB Domain

After the schema upgrade, you must reconfigure the 11g OSB domain using the Oracle Reconfiguration Wizard. This process is identical to the SOA domain reconfiguration procedures described in Reconfiguring the Domain Using the Reconfiguration Wizard.

7.9 Upgrading the WebLogic Component Configurations

You will run the Upgrade Assistant a second time, after the domain reconfiguration, to upgrade any component configurations in the 11g OSB domain.

This process is described in Upgrading the Domain Component Configurations Using the Upgrade Assistant.

7.10 Performing Post Upgrade Tasks for Oracle Service Bus

After a successful upgrade, you may need to perform one or more of the following tasks. Review your own use case scenarios and existing deployment to determine if the following tasks apply to your environment.

Note:

If you experience any post-upgrade issues with Oracle Service Bus, refer to Troubleshooting Oracle Service Bus for a list of common solutions.

7.10.1 Importing Domain Configuration Data

After the upgrade you will need to import the domain configuration data that you exported in Exporting Services, Projects and Resources when Upgrading Oracle Service Bus.

For more information, see How to Import Resources from a Configuration JAR File in the Console and Executing a Configuration File.

7.10.2 Importing Security Configurations

Use the Oracle WebLogic Administration Console to import the security data that you exported pre-upgrade into the new Oracle Service Bus domain.

For more information, see the "Import data into a security provider" section of the Oracle WebLogic Server Administration Console Online Help.

Note:

You must import the security information for each security provider separately.

7.10.3 Upgrading Your XQuery Resources

Oracle Service Bus supports XQuery 1.0. The older XQuery 2004 is also supported. Any new XQuery resource created in Service Bus uses the XQuery 1.0 version, by default.

If you have upgraded from a pre-12c Service Bus project, all XQuery resources in the project are configured to use the XQuery 2004 version.

For more information on upgrading XQuery Resources, see How to Upgrade Your XQuery Resources to use XQuery 1.0.

7.10.4 Understanding 12c Split-Joins

The 11g split-join business service will no longer exist in 12c because in 12c there is a direct way to invoke a split-join component from a pipeline or a proxy service. The upgrade process will automatically change all statically configured invoke references to a split-join business service as follows:

  • The flow business service is removed. This means the Timeout property configured for the Flow business service is also removed.

  • If the business service is located in the same project as the proxy service that invokes it, then the pipeline associated with that proxy service invokes the split-join directly.

  • If the business service is located in a different project from the proxy service that invokes it, then a local proxy service is created to invoke the split-join. The local proxy service is invoked by the original proxy service.

7.11 Troubleshooting Oracle Service Bus Upgrade

If you experience post-upgrade issues with Oracle Service Bus, review the following and apply any relevant solutions.

7.11.1 Resolving the HTTP 404 Error After OSB Upgrade with OHS as Cluster Frontend Host

If you configure Oracle HTTP Server (OHS) as a cluster domain frontend host, then you must add the following code to the OHS configuration file (ohs.confg):

 <Location /sbconsole>
  SetHandler weblogic-handler
  WebLogicCluster [ADMIN_SERVER_HOST]:[ADMIN.SERVER:PORT]
</Location>
<Location /servicebus>
  SetHandler weblogic-handler
  WebLogicCluster [ADMIN_SERVER_HOST]:[ADMIN.SERVER:PORT]
</Location>

Where ADMIN.SERVER:PORT is the machine name, server name and port number used for the OHS.

mymachine.us.mycompany.com:7001 as shown in this sample code example:

<Location /sbconsole>
  SetHandler weblogic-handler
  WebLogicCluster mymachine.us.mycompany.com:7001
</Location>
<Location /servicebus>
  SetHandler weblogic-handler
  WebLogicCluster mymachine.us.mycompany.com:7001
</Location>

7.11.2 Resolving the HTTP 404 Error When Accessing OSB Console

Prior to 12c, the OSB console was accessed using the following URL: http://[HOST]:[PORT]/sbconsole

In 12c, the OSB Console URL has changed to: http://[HOST]:[PORT]/servicebus.

After the upgrade, if you enter http://[HOST]:[PORT]/sbconsole, it should redirect to http://[HOST]:[PORT]/servicebus.

If the redirect fails, and you receive a HTTP 404 error, try direclty entering the 12c URL: http://[HOST]:[PORT]/servicebus.