Upgrading Images in Oracle BAM Reports Upgrading Oracle BAM Sensor Actions

11-6 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF

11.8 Additional Considerations When Upgrading to Oracle BAM 11g

The following sections describe additional information to consider when upgrading to Oracle BAM 11g: ■ Using Oracle BAM Alert Actions After Upgrade ■ Recreating Oracle BAM Enterprise Message Sources After Upgrade

11.8.1 Using Oracle BAM Alert Actions After Upgrade

Some Oracle BAM alert actions were removed in Oracle BAM 11g, and after upgrading, any alerts using them may become invalid. Specifically, the Run a Plan action was removed because Oracle BAM replaced Enterprise Link with Oracle Data Integrator, which uses the Run an ODI Scenario alert action. For more information, see Section 11.7, Upgrading Enterprise Link Plans to Oracle BAM 11g .

11.8.2 Recreating Oracle BAM Enterprise Message Sources After Upgrade

Enterprise Message Sources have changed from Oracle BAM 10g to Oracle BAM 11g. As a result, you must recreate any Enterprise Message Sources after you upgrade to Oracle Fusion Middleware 11g. For more information, see Creating Oracle BAM Enterprise Message Sources in the Oracle Fusion Middleware Developers Guide for Oracle SOA Suite. 12 Upgrading Oracle B2B Applications 12-1 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. ■ Features That are Not Upgraded to Oracle B2B 11g ■ Features That are Changed After Upgrade to Oracle B2B 11g ■ Oracle B2B 11g Post-Upgrade Tasks

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: ■ Host and Partner Security Certificates ■ Callout Library JAR Files ■ Exchange Protocol Parameter Identifiers ■ The Receipt Recipient Property of the AS2-1.1 Channel ■ Generic TCP Channels ■ PositionalFlatFile Documents

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: ■ Security Features of Oracle B2B in the Oracle Fusion Middleware Users Guide for Oracle B2B 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: