2 Upgrading to Oracle Service Bus 11g Release 1 (11.1.1.7.0)

This chapter describes how to upgrade AquaLogic Service Bus (2.6 and 3.0) and Oracle Service Bus (10.3.1.0) to Oracle Service Bus 11g Release 1 (11.1.1.7.0).

This chapter contains the following sections:

Note:

Before proceeding with the upgrade, you must review the following:

2.1 Upgrade Overview

Direct automated in-place upgrade of AquaLogic Service Bus 2.6, 2.6 RP1, 3.0, Oracle Service Bus 10g Release 3 (10.3), and 10g Release 3 Maintenance Pack 1 (10.3.1) domain to Oracle Service Bus 11g Release 1 (11.1.1.7.0) domains is not supported. The upgrade process includes the following steps:

The upgrade to new Oracle Service Bus domains is supported for both clustered and non-clustered domains.

Before starting the upgrade process, refer to the Prerequisites for Upgrading to Oracle Service Bus 11g Release 1 (11.1.1.7.0) and Upgrade Considerations sections.

Table 2-1 identifies the version of Oracle WebLogic Server on which each version of AquaLogic Service Bus or Oracle Service Bus runs.

Table 2-1 Oracle Service Bus and Oracle WebLogic Server Versions

Service Bus Version WebLogic Server Version

Oracle Service Bus 11g Release 1 (11.1.1.7.0)

10.3.6

Oracle Service Bus 11g Release 1 (11.1.1.6.0)

10.3.6

Oracle Service Bus 11g Release 1 (11.1.1.5.0)

10. 3.5

Oracle Service Bus 11g Release 1 (11.1.1.4.0)

10.3.4

Oracle Service Bus 11g Release 1 (11.1.1.3.0)

10.3.3

Oracle Service Bus 10g Release 3 Maintenance Pack 1 (10.3.1)

10.3

Oracle Service Bus 10g Release 3 (10.3)

10.3

AquaLogic Service Bus 3.0

10.0 MP1

AquaLogic Service Bus RP1

9.2 MP2

AquaLogic Service Bus 2.6

9.2 MP1

2.2 Starting Points for Oracle Service Bus Upgrade

The follows starting points are supported:

  • AquaLogic Service Bus 2.6

  • AquaLogic Service Bus 2.6 RP1

  • AquaLogic Service Bus 3.0

  • Oracle Service Bus 10g Release 3 (10.3)

  • Oracle Service Bus 10g Release 3 Maintenance Pack 1 (10.3.1)

Note:

You cannot upgrade config.jar file from versions earlier than AquaLogic Service Bus 2.6, to Oracle Service Bus 11g Release 1 (11.1.1.7.0).

Note:

If you have an existing Oracle Service Bus 11g Release 1 (11.1.1.6.0) installation, you must patch Oracle Service Bus 11g Release 1 (11.1.1.6.0) to Oracle Service Bus 11g Release 1 (11.1.1.7.0) using the Patch Set installer, as specified in the Oracle Fusion Middleware Patching Guide.

In addition, complete any post patching procedure, including Domain Migration from 11g Release 1 (11.1.1.6.0) to 11g Release 1 (11.1.1.7.0). For more information, see the section Post-Migration Configuration for Oracle Fusion Middleware Components in the Oracle Fusion Middleware Patching Guide.

2.3 Prerequisites for Upgrading to Oracle Service Bus 11g Release 1 (11.1.1.7.0)

This section contains the following:

2.3.1 Backing Up Your Environment

Before upgrading to the latest version of Oracle Service Bus, ensure that you back up your OSB_HOME or ALSB_HOME and your domains (if they reside outside of OSB_HOME or ALSB_HOME).

If you want to revert to your previously installed version of Oracle Service Bus after upgrading to Oracle Service Bus 11g Release 1 (11.1.1.7.0), you must restore your Oracle Service Bus environment from backup.

If you want to save customizations you made to the Oracle Service Bus samples, export and save your sample configurations. You must import the configuration after upgrade to restore your customizations.

2.3.2 Patching Oracle WebLogic Server 10.3.5

If you are upgrading to the latest Oracle Service Bus from an environment running Oracle WebLogic Server 10.3.5, you must install two WebLogic Server patches, as described in the "Patches Required for Oracle WebLogic Server 11gR1 (10.3.5)" section in the Oracle Fusion Middleware System Requirements and Specifications document.

2.3.3 Patching Oracle WebLogic Server 10.3.6

If you are upgrading to the latest Oracle Service Bus in an environment running Oracle WebLogic Server 10.3.6, you must install the required WebLogic Server patches as described on the "Known Issues for Oracle SOA Products and Oracle AIA Foundation Pack" page on Oracle Technology Network:

http://www.oracle.com/technetwork/middleware/docs/aiasoarelnotesps6-1866030.html

2.4 Task 1: Exporting Configuration from Existing Domain

To export your existing domain configuration, complete the following steps:

  1. Start the Oracle Service Bus Administration Server for the domain you plan to upgrade to 11g Release 1 (11.1.1.7.0).

  2. Log in to the Oracle Service Bus Administration Console by using the Administration Server user name and the password.

  3. Select System Administration, and then Export Resources.

    The Export Resources page is displayed.

  4. Select the projects or resources you want to export.

    • If you selected Export Projects, you cannot deselect the check boxes for individual resources.

      1. Expand the project folders. The name, type, last modified time, and references for each resource contained in the project are displayed.

      2. Select the check boxes associated with the projects or resources you want to export.

      3. Clear the check boxes associated with the projects or resources that you do not want to export.

    • If you selected Export Resources, select or clear the Include Dependencies check box. Use this option to export any other resources that this resource references.

  5. Click Export to create a JAR file.

2.5 Task 2: Exporting Security Configurations

You can use the Oracle WebLogic Administration Console to export security data from the existing domain. To export security data to a file, complete the following steps:

  1. Log in to the Oracle WebLogic Administration Console by using the Administration Server user name and the password.

  2. In the left pane, select Security Realms under Domain Structure and then select the realm whose security data you want to export (for example, myrealm).

  3. Select the Migration tab, and then click the Export tab to export the data.

  4. In the Export Directory on Server field, specify the directory on the Administration Server to which to export the security data.

  5. Click Save.

    The security data is saved in a file in the location you specified.

Table 2-2 summarizes the security data and types of security providers in which the data is stored.

Table 2-2 Security Data and Providers

Security Data Security Provider Type

Group definitions

Authentication provider

User accounts

Authentication provider

Role definitions

Role mapping provider

User names and passwords in service accounts

Username and password credential mapping provider

PKI credential map entries

PKI credential mapping provider

SAML Relying Parties

SAML credential mapping provider V2

SAML Asserting Parties

SAML identity assertion provider V2

Trusted Certificates (for SSL and WSS)

Certification path provider (Certificate Registry)

Note:

The set of providers to export is different depending on what version you are upgrading from as described in the following sections.

Exporting AquaLogic Service Bus 2.6, 2.6 RP1, and 3.0 Security Configurations

Starting with the AquaLogic Service Bus 2.5 release, PKI, username and password credentials are stored in the WebLogic Server realm and in the ALSB configuration repository. Consequently, these credentials are exported as part of the configuration JAR that was generated and exported in Task 1: Exporting Configuration from Existing Domain. When the JAR is imported into the new domain, the realm data is populated based on the contents of the JAR file. This means that you do not need to export PKI Credentials or username/password credentials when you upgrade from AquaLogic Service Bus 2.6 and later.

For more information, see the "Migrating Security Data" chapter in the Oracle Fusion Middleware Securing Oracle WebLogic Server.

Exporting Proxy Services with Access Control Policies in AquaLogic Service Bus 2.6

The exports from AquaLogic Service Bus 2.6 or earlier releases will not have any access control policies in the exported JAR files. You must first export the security realm which includes access control policies, from the AquaLogic Service Bus 2.6 and 2.6 RP1 domain on Oracle WebLogic Server 9.2 to the new Oracle Service Bus 11g Release 1 (11.1.1.7.0) domain on Oracle WebLogic Server 10.3.4.

Then you must export the configuration JAR file with proxy services from the AquaLogic Service Bus 2.6 and 2.6 RP1 domain to the new Oracle Service Bus 11g Release 1 (11.1.1.7.0) domain. For more information, see "Export data from a security provider" chapter in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Help.

2.6 Task 3: Installing and Configuring the Oracle Service Bus 11g Release 1 (11.1.1.7.0)

To install and configure Oracle Service Bus, refer to the Oracle Fusion Middleware Installation Guide for Oracle Service Bus.

Note:

After installing and configuring the Oracle Service Bus, ensure that the Administration Server and the Managed Servers are up and running.

If you want to use Oracle Web Services Manager policies with Oracle Service Bus, 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.

2.7 Task 4: Configuring Oracle WebLogic Server security

In the new 11g Release 1 (11.1.1.7.0) domain, configure the Oracle WebLogic security framework with SSL and the security providers required to support your proxy and business services. For more information, see the "Configuring the WebLogic Security Framework: Main Steps" section in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.

If you are importing configuration, note the following:

  • If your new domain uses a PKI credential mapping provider, copy the keystores to the new domain and configure the PKI credential mapping provider to use the keystore.

  • If your domain has modified the Web Service security configurations named _SERVICE_BUS_INBOUND_WEB_SERVICE_SECURITY_MBEAN_ or _SERVICE_BUS_OUTBOUND_WEB_SERVICE_SECURITY_MBEAN_, make the same modifications in the new domain. For example, if in your 2. domain, you added the UseX509ForIdentity property to the _SERVICE_BUS_INBOUND_WEB_SERVICE_SECURITY_MBEAN_ configuration (which is required to support inbound authentication with an X.509 token), add the property in the new domain. For more information, see the "Use X.509 certificates to establish identity" topic in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Help.

2.8 Task 5: Re-creating Other Oracle WebLogic Server Objects

In the new Oracle Service Bus domain, re-create the Oracle WebLogic Server objects that could not be exported in Task 1: Exporting Configuration from Existing Domain, including the following:

  • JMS resources, such as connection factories, queues, topics, and so on

  • Work Manager definitions

  • SNMP agent and trap destination settings

For more information about configuring Oracle WebLogic Server domain resources, see the "Overview of WebLogic Server System Administration" chapter in the Oracle Fusion Middleware Introduction to Oracle WebLogic Server.

Note:

You should configure the domain-scoped SNMP agent in the Oracle WebLogic Server Console. Oracle WebLogic Server 10.x has enhanced SNMP features. For more information about SNMP, see the Oracle WebLogic SNMP Management Guide.

Add the Tuxedo domain ID as an Oracle WebLogic Server user (this is a requirement to successful invoke a Tuxedo service).

Configure WTC Local Access Point and Remote Access Point resources when your configuration includes Tuxedo transport-based services.

For information, see Configuring Oracle WebLogic Tuxedo Connector for Tuxedo Transport in Interoperability Solution for Tuxedo.

2.9 Task 6: Importing Security Data and Policies into the Oracle Service Bus 11g Release 1 (11.1.1.7.0)

Use the Oracle WebLogic Administration Console to import the security data that you exported in Task 2: Exporting Security Configurations into the new Oracle Service Bus domain. For more information, see the "Import data into a security provider" chapter in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Help.

Note:

Import the security information for each security provider separately.

Importing Proxy Services with Access Control Policies in AquaLogic Service Bus 2.6

You must first export the security realm with access control policies in AquaLogic Service Bus 2.6 and 2.6 RP1 domain using Oracle WebLogic Server 9.2 to Oracle Service Bus 11g Release 1 (11.1.1.7.0) domain using Oracle WebLogic Server 10.3.4.

Then you must export the configuration jar with the proxy services from the AquaLogic Service Bus 2.6 and 2.6 RP1 domain to Oracle Service Bus 11g Release 1 (11.1.1.7.0) domain. For more information, see "Import data into a security provider" chapter in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Help.

2.10 Task 7: Importing Configuration JAR File into Oracle Service Bus 11g Release 1 (11.1.1.7.0)

You must import the JAR files that you have previously exported from your old domain to Oracle Service Bus 11g Release 1 (11.1.1.7.0) by completing the following steps:

  1. Log in to the Oracle Service Bus Console by using the Administration Server user name and the password.

  2. Click Create to create a new session, or click Edit to enter an existing session.

  3. Select System Administration, and then Import Resources.

    The Import Resources page is displayed.

  4. Select the project or resource JAR file that you exported in Task 1: Exporting Configuration from Existing Domain.

    1. In the File Name field, click Browse to locate the directory where the JAR file is stored.

    2. Select the JAR file, and then click Open.

  5. Click Next.

    The Import Resources - Resource JAR File page is displayed.

  6. Select Include Dependencies to import the resource JAR file and to ensure that all its associated resources are imported.

  7. Select the check boxes associated with the projects or resources you want to import, and clear the check boxes associated with the projects or resources that you do not want to import.

  8. Click Import.

    The Import Summary page is displayed. This page displays a summary of the files imported and their status.

  9. Click Activate in the Change Center. The Activate Session page shows the session name, user name, and a description field.

2.11 Task 8: Completing Any Required Oracle Service Bus Post-Upgrade Tasks

Some Oracle Service Bus domain configuration changes are not automated and must be implemented manually. For more information, see Upgrade Considerations.

You cannot upgrade the workspace that was used to develop Oracle Service Bus projects from the previous releases. Therefore, you must upgrade the workspace by performing one of the following steps:

Note:

Oracle Service Bus 11g Release 1 (11.1.1) uses the Oracle Enterprise Pack for Eclipse (OEPE) Integrated Development Environment (IDE). For more information, see "Interoperability Scenarios and Considerations" in the Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus.

  • Create a new workspace in Oracle Service Bus 11g Release 1 (11.1.1.7.0) using Oracle Enterprise Pack for Eclipse, and then export the config.jar files from the previous releases of workspace.

  • Import the exported configuration JAR file into the new workspace using Oracle Enterprise Pack for Eclipse for Oracle Service Bus 11g Release 1 (11.1.1.7.0). The import process will automatically upgrade the configuration JAR file. Alternatively, you can import the configuration JAR file into an Oracle Service Bus server on 11g Release 1 (11.1.1.7.0) to upgrade the configuration JAR file. Then export the configuration JAR file from server and import it into the workspace using Oracle Enterprise Pack for Eclipse for Oracle Service Bus 11g Release 1 (11.1.1.7.0).

    Note:

    When you import any configuration JAR into the 11g Release 1 (11.1.1.7.0) IDE, the operational and administrative settings are removed. To retain these settings, first import the configuration JAR file into the console, export and import the file into the 11g Release 1 (11.1.1.7.0) IDE, as described above. When you later move configuration from IDE to Console, enable Preserve operational settings, so that operational settings that were imported in the first step are preserved.

2.12 Verifying Your Upgrade

To verify that your upgrade was successful, find the new version number in the lower left corner of the login window when you access the Oracle Service Bus Administration Console, as shown in Figure 2-1.

Figure 2-1 Oracle Service Bus Administration Console

Description of Figure 2-1 follows
Description of "Figure 2-1 Oracle Service Bus Administration Console"

The URL for the Oracle Service Bus Administration Console is:

http://administration_server_hostname:administration_server_port_number/sbconsole