Skip Headers
Oracle® Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter Portal, and ADF
11g Release 1 (11.1.1.6.0)

Part Number E10127-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

12 Upgrading Oracle B2B Applications

This chapter provides important supplementary information upgrading Oracle B2B applications to Oracle Fusion Middleware 11g.

Use Chapter 8, "Overview of Upgrading Oracle SOA Suite, WebCenter, and ADF Applications" for the tasks required to upgrade any Oracle SOA Suite, WebCenter, and ADF application.

The following sections provide the information you should know about the Oracle B2B upgrade, as well as some specific post-upgrade tasks you might have to perform after upgrading to Oracle B2B 11g.

12.1 Features That are Not Upgraded to Oracle B2B 11g

The following Oracle B2B features are not upgraded automatically when you upgrade to Oracle Fusion Middleware 11g:

12.1.1 Host and Partner Security Certificates

Oracle B2B host and partner security certificates are not upgraded into the expected format for Oracle B2B 11g.

Instead, you must copy the certificates from the root directory of the export.zip file (created in Section 6.5.2.4, "Performing the B2B Schema Upgrade") and import them into the keystore.

Note that Oracle B2B now saves certificates in the keystore, rather than an SSL wallet.

For more information, see the following:

12.1.2 Callout Library JAR Files

If you created your own custom callout library jar files in Oracle B2B 10g, then those jar files are not upgraded to Oracle B2B 11g.

Instead, you must recreate your custom callout jar files using Oracle B2B 11g.

For more information, see "Managing Callouts" in the Oracle Fusion Middleware User's Guide for Oracle B2B.

12.1.3 Exchange Protocol Parameter Identifiers

In Oracle B2B 10g, you could specify identifiers for the exchange protocol parameter of a channel. Adding identifiers to the exchange protocol parameter is no longer supported in Oracle B2B 11g, and these identifiers are not upgraded to Oracle B2B 11g.

Instead, Oracle B2B 11g, you must recreate the required identifiers as part of a Trading Partner Profile.

For more information, see "Creating Trading Partner Profiles" in the Oracle Fusion Middleware User's Guide for Oracle B2B.

12.1.4 The Receipt Recipient Property of the AS2-1.1 Channel

If you set the Receipt Delivery Option property of the AS2-1.1 channel in your Oracle B2B 10g environment, then this property value is not upgraded to Oracle B2B 11g. After you upgrade, you must set this property accordingly.

For more information, see "Configuring Channels" in the Oracle Fusion Middleware User's Guide for Oracle B2B.

12.1.5 Generic TCP Channels

Generic TCP channels you created in Oracle B2B 10g are not upgraded automatically to Oracle B2B 11g. To create Generic TCP channels in Oracle B2B 11g, create an MLLP channel and specify TCP information. For more information, see the the section, "Generic Support for TCP" in "About MLLP" in the Oracle Fusion Middleware User's Guide for Oracle B2B.

12.1.6 PositionalFlatFile Documents

Any PositionalFlatFile documents (for example, SAP iDoc documents), created under the Custom Document protocol (using ECS files for translation and validation) in Oracle B2B 10g are not upgraded automatically to Oracle B2B 11g.

In Oracle B2B 11g, create these documents under a new document protocol called PositionalFlat file and specify the identification details and provide the ECS file in the document definition.

For more information, see the the section, "Using the Positional Flat File Document Protocol" in the Oracle Fusion Middleware User's Guide for Oracle B2B.

12.2 Features That are Changed After Upgrade to Oracle B2B 11g

The following Oracle B2B features behave differently or must be configured differently after you upgrade to Oracle B2B 11g:

12.2.1 Document Protocol Revision and Document Type Fields

These two fields have been modified for Oracle B2B 11g. In Oracle B2B 10g, both these fields included a name and version. Oracle B2B uses only the Document Protocol Version and Document Type Name fields.

As a result, when you enqueue a document to the IP_OUT_QUEUE, note that you must provide a different set of attributes than those provided in Oracle B2B 10g.

For more information, see "MS Enqueue and Dequeue Utilities" in the Oracle Fusion Middleware User's Guide for Oracle B2B.

12.2.2 Exchange Protocol Parameters for the MLLP Channel

The following exchange protocol parameters in Oracle B2B 10g are now attributes of the MLLP channel:

  • ImmediateACK

  • ImmediateACK-Custom-File

  • ImmediateACK-mapAckControlID

  • ImmediateACK-MapImmTriggerEvt

  • DiscardHL7ACK

If you set these parameters in Oracle B2B 10g, then you will need to set them as attributes of the MLLP channel.

For more information, see "Configuring Channels" in the Oracle Fusion Middleware User's Guide for Oracle B2B.

12.2.3 Channel Passwords

Oracle B2B 11g uses a new method for saving user credentials and password information. As a result, any passwords you entered for channels in 10g are not upgraded to Oracle B2B 11g.

Instead, after upgrade, you must enter the passwords as part of the channel parameters.

For more information, see "Configuring Channels" in the Oracle Fusion Middleware User's Guide for Oracle B2B.

12.2.4 Optional Fields in Oracle B2B 10g That are Mandatory in Oracle B2B 11g

Note that the following fields have changed from optional to required; as a result, after upgrade, you might have to provide values for these fields:

  • If you were using EDI EDIFACT and EDI X12 documents in Oracle B2B 10g, then note that the Group ID identifier is now a required identifier.

  • If you are using RosettaNet documents in Oracle B2B 10g, then note that the Collaboration Code and Time to perform for Collaboration fields are not required. In Oracle B2B 11g, they are required.

For more information, see "Creating Types" in the Oracle Fusion Middleware User's Guide for Oracle B2B.

12.2.5 Inbound and Outbound Partner Agreements

When you upgrade to Oracle B2B 11g, a partner agreement that exists in Oracle B2B 10g will be displayed in Oracle B2B 11g as two agreements: one agreement is for the inbound exchange; the other is for the outbound exchange.

For example, a 10g Rosetta 3A4 agreement is split into the following:

  • Pip3A4PurchaseOrderConfirmation_Inbound

  • Pip3A4PurchaseOrderRequest_Outbound

For more information, see "Creating and Deploying Trading Partner Agreements" in the Oracle Fusion Middleware User's Guide for Oracle B2B.

12.2.6 RosettaNet Outbound Messages

The behavior of RosettaNet outbound messages has changed in Oracle B2B 11g.

When using RosettaNet with Oracle B2B 11g, you must now set an additional enqueue property (msgType=2) for any outbound message that needs to be treated as a response message (for example, a PurchaseOrderConfirmation message).

Otherwise, the outbound message will be treated as a request message. In Oracle B2B 10g, this property was not necessary.

For more information, see "Utilities for Enqueuing and Dequeuing" in the Oracle Fusion Middleware User's Guide for Oracle B2B.

12.3 Oracle B2B 11g Post-Upgrade Tasks

The following tasks should be performed after you upgrade to Oracle B2B 11g:

12.3.1 Configuring MLLP Channels for Inbound and Outbound Messages

After upgrade, perform one of the following tasks, depending on how you configured the MLLP channel in Oracle B2B 10g:

  • If you used the singleDC property in the tip.properties file to enable one MLLP channel to transfer both inbound and outbound messages, then you must create a new channel and then update the partner agreement to use the new channel.

  • If you did not use the singleDC property, then set the connection mode of the host trading partner to Server.

For more information, see "About MLLP" in the Oracle Fusion Middleware User's Guide for Oracle B2B.

12.3.2 Migrating Oracle B2B Metadata

You can migrate your existing Oracle B2B 10g to Oracle B2B 11g using the command-line tool:

  1. Export the metadata from the Oracle B2B repository using the b2bexport utility as described in "Exporting Data" in the Oracle Fusion Middleware User's Guide for Oracle B2B.

  2. Import the B2B metadata ZIP file to the repository using the b2bimport utility as described in "Importing Data" in the Oracle Fusion Middleware User's Guide for Oracle B2B.

12.3.3 Considerations When Upgrading B2B-Related Oracle BPEL Processes

By default, Oracle SOA Suite 10g uses Oracle Streams Advanced Queuing (AQ) as the default connection between the Oracle BPEL Process Manager and Oracle B2B. The Oracle AQ connection relies on a data source being available on the OC4J server.

When you upgrade to Oracle SOA Suite 11g, the required data source used by Oracle AQ is not available by default. As a result, you should consider the following when upgrading to Oracle B2B 11g and Oracle SOA Suite 11g:

  • Before you upgrade to Oracle B2B 11g, create a data source in Oracle WebLogic Server that references the Oracle B2B 10g database. Note the JNDI name you provide for the database.

    For more information, see "Create JDBC data sources" in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help.

  • After the upgrade to Oracle B2B 11g, open the Open AQ Adapter External Reference, and enter JNDI name for the new Oracle WebLogic Server data source on the Service Connection page of the Connection wizard.

Note that when you open your Oracle SOA Suite 10g application in Oracle JDeveloper 11g, the Oracle JDeveloper Migration Utilty upgrades your application and makes the following related changes to your projects. These changes allow you to continue using the Oracle AQ connection between the Oracle B2B and Oracle BPEL Process Manager processes:

  • For Oracle BPEL Process Manager projects, the variables used by the Oracle AQ connection are upgraded automatically to properties within an Oracle BPEL Process Manager assign statement or transformation map within the BPEL process file.

  • For Oracle Enterprise Service Bus projects, the variables used by the Oracle AQ connection in are removed automatically from the 10g XSLT map file and upgraded to properties within an assign values field in Oracle Mediator.

Alternatively, you can recreate your projects in Oracle JDeveloper 11g, using the newer Oracle Fusion Middleware 11g features for defining the connections between Oracle Mediator projects and Oracle BPEL Process Manager processes.

For more information, see the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.