Upgrading Enterprise Link Plans to Oracle BAM 11g

12-2 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF ■ Configuring Identity and Trust in the Oracle Fusion Middleware Securing Oracle WebLogic Server.

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 Users 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 Users 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 Users 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 Users 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 Users 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: 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.