Host and Partner Security Certificates

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. Upgrading Oracle B2B Applications 12-5

12.3.2 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 Developers Guide for Oracle SOA Suite.