Task 5a: Start the Upgrade Assistant for an Oracle SOA Schema Upgrade

6-6 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF Figure 6–3 Upgrade Assistant Specify Operation Screen for a SOA Upgrade

6.5.2 Task 5b: If Necessary, Upgrade the B2B Schema

Refer to the following sections for information about upgrading the Oracle B2B schema: ■ General Information About the B2B Schema Upgrade ■ Applying the Required Patch Set to the Oracle B2B 10g Middle Tier ■ Setting the Maximum Message Size Attribute In the Oracle WebLogic Server Administration Console ■ Performing the B2B Schema Upgrade

6.5.2.1 General Information About the B2B Schema Upgrade

If you are using Oracle Application Server 10g Release 2 10.1.2 and you are upgrading Oracle Application Server Integration B2B, then you will need to upgrade the B2B schema in your database. When you upgrade the B2B schema from 10g Release 2 10.1.2, you must apply a software patch to your 10g Release 2 10.1.2 installation, and then export the B2B 10g schema from your database. The exported data is saved to a ZIP file on disk. Then, you can import the data into the database that contains your Oracle Fusion Middleware 11g component schemas. See Also: Oracle Fusion Middleware Users Guide for Oracle B2B in the Oracle Application Server 10g Release 2 10.1.2 Documentation Library on the Oracle Technology Network: http:www.oracle.comtechnologydocumentation Upgrading an Oracle SOA Suite Environment 6-7

6.5.2.2 Applying the Required Patch Set to the Oracle B2B 10g Middle Tier

Before you can perform the Oracle B2B schema upgrade, you must apply the a required patch set to the Oracle Application Server Integration B2B 10g Release 2 10.1.2 middle tier. This patch set is required in order to enable the Java command that you use to export the trading partner agreements, as described in the following step. For specific information about the patch set requirements for upgrade and interoperability with previous Oracle Application Server releases, see the Oracle Fusion Middleware Release Notes. 6.5.2.3 Setting the Maximum Message Size Attribute In the Oracle WebLogic Server Administration Console The exported customer data from your Oracle B2B 10g schema can result in a very large ZIP file on disk. To be sure that the large file can be imported successfully into the Oracle Fusion Middleware 11g metadata repository database, you should modify the default Maximum Message Size general protocol attribute for the WebLogic managed server where the SOA Suite components are deployed. To perform this task: 1. Log in to the Oracle WebLogic Server Administration Console: http:localhost:7001console

2. In the left pane of the Console, expand Environment and select Servers.

3. On the Summary of Servers page, select the server instance you want to configure. In most cases, the managed server that hosts the SOA components is called soa_ server1.

4. Click Protocols to display the general connection settings for network protocols.

5. Scroll down to the Maximum Message Size property and set it to 200000000.

6.5.2.4 Performing the B2B Schema Upgrade

To upgrade the B2B schema: 1. Apply the required patch set to the Oracle Application Server Integration B2B 10g Release 2 10.1.2 middle tier. For more information, see Section 6.5.2.2, Applying the Required Patch Set to the Oracle B2B 10g Middle Tier . 2. Export the 10g Release 2 10.1.2 trading partner agreements to an external ZIP file by using the following procedure: a. Export the 10g Release 2 10.1.2 trading partner agreements that you have deployed by running the following command in the Oracle Application Server Integration B2B Oracle home: java -ms1024M -mx1024M oracle.tip.repos.export.Export 11g Note: This procedure assumes you have installed and configured your new Oracle Fusion Middleware 11g environment, as described in Section 6.4, Task 4: Install and Configure the Oracle SOA Suite 11g Middle Tiers 6-8 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF This Java command creates the following directory, which contains the exported data: On Windows systems: TEMPexport.zip On UNIX systems: tmpexport.zip b. Create the following directory in the Oracle Fusion Middleware 11g Oracle home, which can be on the same host or on a different host from the 10g Oracle home: On Windows systems: ORACLE_HOME \b2b\upgrade On UNIX systems: ORACLE_HOME b2bupgrade c. Copy the export.zip file to the directory you just created. 3. Use the Oracle WebLogic Server Administration Console to increase the Maximum Message Size property for the SOA component managed server for example, soa_server1. For more information, see Section 6.5.2.3, Setting the Maximum Message Size Attribute In the Oracle WebLogic Server Administration Console . 4. Stop the administration server and the managed servers in the Oracle WebLogic Server domain that hosts the BAM application. For more information, see Starting and Stopping Oracle Fusion Middleware in the Oracle Fusion Middleware Administrators Guide. 5. Start the Upgrade Assistant as described in Task 5a: Start the Upgrade Assistant for an Oracle SOA Schema Upgrade .

6. Select B2B Schema on the Specify Operation screen

Figure 6–3 . 7. Refer to Table 6–2 for a description of the Upgrade Assistant screens that require input from you during a B2B Schema upgrade and the options on each screen. Note that you are not prompted for the location of the ZIP file that contains the Oracle B2B 10g schema and customer data. Instead, the Upgrade Assistant automatically locates the ZIP file in the location specified in Step 2. 8. After the Specify Target Database screen, the Upgrade Assistant performs the following tasks and provides the progress on each task: ■ Examines the components and schemas to be upgraded and verifies that they can be upgraded successfully. ■ Provides a summary of the components to be upgraded so you can verify that Upgrade Assistant is upgrading the components and schemas you expect. ■ Provides a progress screen so you can see the status of the upgrade as it proceeds. ■ Alerts you of any errors or problems that occur during the upgrade.