Recreating Oracle BAM Enterprise Message Sources After Upgrade

Upgrading Oracle B2B Applications 12-3 ■ Document Protocol Revision and Document Type Fields ■ Exchange Protocol Parameters for the MLLP Channel ■ Channel Passwords ■ Optional Fields in Oracle B2B 10g That are Mandatory in Oracle B2B 11g ■ Inbound and Outbound Partner Agreements ■ RosettaNet Outbound Messages

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 Users 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 Users 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 Users 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. 12-4 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF ■ 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 Users 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 Users 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 Users 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: ■ Configuring MLLP Channels for Inbound and Outbound Messages ■ Considerations When Upgrading B2B-Related Oracle BPEL Processes

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 Users Guide for Oracle B2B.