Procedure for Upgrading the XREF Runtime Data

10 Upgrading Oracle BPEL Process Manager Applications 10-1 10 Upgrading Oracle BPEL Process Manager Applications This chapter provides important supplementary information upgrading Oracle BPEL Process Manager 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. Use the following sections to learn about the upgrade tasks you will likely need to perform to upgrade your Oracle BPEL Process Manager applications and projects to Oracle Fusion Middleware 11g: ■ Manual Upgrade Steps After Migrating Oracle BPEL Process Manager Applications ■ Additional Considerations for Oracle BPEL Process Manager Applications

10.1 Manual Upgrade Steps After Migrating Oracle BPEL Process Manager Applications

The following sections describe some of the common upgrade tasks you will have to perform after you open your Oracle Application Server 10g Oracle SOA Suite application in Oracle JDeveloper 11g. These tasks represent items that are not upgraded automatically by the Oracle JDeveloper Migration Wizard: ■ Providing Missing Binding Information for External References ■ Correcting Problems With Oracle BPEL Process Manager Test Suites ■ Using Oracle BPEL Process Manager Deployment Plans After Upgrade ■ Upgrading Fault Policies in an Oracle BPEL Process Manager Project ■ Upgrading a 10g Project With No BPEL Folder ■ Post-Upgrade Steps for Projects That Use WSIF Bindings to EJBs

10.1.1 Providing Missing Binding Information for External References

This section describes how to fix compiler warning messages about missing bindings after you upgrade an Oracle BPEL Process Manager project in Oracle JDeveloper. Why the Warning Messages Occur When a source project in your application depends on Oracle Application Server 10g Release 3 10.1.3 Oracle BPEL Process 10-2 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF Manager or Oracle Enterprise Service Bus ESB services, then as a pre-cursor to migration, the Oracle JDeveloper Migration Wizard creates local copies of their abstract WSDLs. The abstract WSDLs, by definition, lack service and port endpoint information. During upgrade, when the Migration Wizard creates external composite references for the service dependencies, the references are created as abstract references with no binding information. These abstract references are flagged with WARNING messages in the upgrade log. After upgrade, when you attempt to compile the projects, Oracle JDeveloper will generate compilation errors alerting you to the presence of abstract references in the composite. Using 10g Release 3 10.1.3 or 11g Dependency Services Based on the upgrade and deployment schedules of all the services in the dependency tree, you can choose to continue to use 10g Release 3 10.1.3 dependency services or proceed with the upgrade and redeployment of the dependency service. In general, Oracle recommends that users study their source project and their dependencies before any upgrade work. This analysis will result in a smoother upgrade experience. How to Correct Binding Errors Discovered During the Recompile To correct binding errors due to the abstract references, right-click on the reference node in the Oracle JDeveloper 11g composite editor and choose the correct concrete WSDL. If you want to continue using a 10g Release 3 10.1.3 dependency service, you can do so. Some of the dependency service endpoint URLs that are captured in the upgrade log can be used for this step. You can also redesign the dependency in Oracle JDeveloper 11g, using the WSIL Browser Resource Palette, and discover the service from the UI in the composite modeler. For more information, refer to the Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.

10.1.2 Correcting Problems With Oracle BPEL Process Manager Test Suites

During upgrade in Oracle JDeveloper, BPEL test suites are converted to composite test suites. However, only the instance initiate action is migrated. This results in a composite test which initiates only a test run. The rest of any BPEL-based test actions are not automatically migrated and must be manually set up after the upgrade. To set up the tests in your 11g environment, refer to Testing SOA Composite Applications in the Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.

10.1.3 Using Oracle BPEL Process Manager Deployment Plans After Upgrade

Deployment and configuration plans that you set up in Oracle Application Server 10g for your Oracle BPEL Process Manager user projects are not upgraded in Oracle JDeveloper 11g. In Oracle Fusion Middleware11g, a composite can be accompanied by deployment and configuration plan during deployment. However, you must create the 11g deployment plan manually, after you have migrated the application in Oracle JDeveloper.