Using Oracle BAM Alert Actions 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.