Using Oracle BPEL Process Manager Deployment Plans After Upgrade

Upgrading Oracle BPEL Process Manager Applications 10-5 ■ Section 10.2.4, Verifying the Properties File Name When Upgrading Projects That Use Correlation Sets in an Asynchronous Service. ■ Section 10.2.5, Upgrading Projects With the transaction=participate Property ■ Section 10.2.6, Specifying Domain Descriptor Properties in Oracle BPEL Process Manager 11g ■ Section 10.2.7, Upgrading Applications That Use Multiple Oracle BPEL Process Manager Domains ■ Section 10.2.8, Verifying Process ID, Project Name, and BPEL File Name Conventions Before Upgrade ■ Section 10.2.9, Verifying Oracle BPEL Process Manager 11g Namespace Prefixes in XPath Functions

10.2.1 Verifying New and Deprecated Properties in the bpel.xml Deployment Descriptor

If any of your Oracle Application Server 10g Release 3 10.1.3 applications reference any properties that were stored in the bpel.xml deployment descriptor, note that these properties are now set in the composite.xml deployment descriptor file. For more information about the properties available in the composite.xml deployment descriptor, as well as important information about properties that are no longer supported in Oracle Fusion Middleware 11g, refer to Deployment Descriptor Properties in the Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.

10.2.2 Upgrading User-Defined Custom XPath Functions in an Oracle BPEL Process Manager Project

When you open and upgrade your applications in Oracle JDeveloper 11g, any custom XPath functions in the application projects are not upgraded automatically. As a result, after you upgrade your application, you must copy any XPath function classes into the server classpath and register the function in the server configuration file. This is a manual step because the Oracle JDeveloper Migration Wizard cannot assume the server information. For more information, refer to Creating User-Defined XPath Extension Functions in the Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.

10.2.3 Change in Support for Multiple BPEL Implementations

You cannot upgrade a single BPEL file with multiple implementations in Oracle BPEL Process Manager 11g. To migrate and merge multiple 10g Release 3 10.1.3 projects with a single BPEL implementation file, you must rename the BPEL file in each project. In the bpel.xml file in each project, the bpel filename and deployment ID name must be renamed the same name, as well. Before you upgrade the application, review the bpel.xml file and .bpel file. Make sure that the BPEL file name and the process name are the same; then review the bpel.xml file and verify that the BPEL file name is the same as the deployment ID name. 10-6 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF 10.2.4 Verifying the Properties File Name When Upgrading Projects That Use Correlation Sets in an Asynchronous Service. If you created an Oracle BPEL Process Manager 10g project that used correlation sets in an asynchronous service, as described in the Oracle BPEL Process Manager 10g Release 3 10.1.3 Developer’s Guide, make sure that the correlation set properties file uses the following proper naming convention: BPEL_FILE_NAME _Properties.wsdl If this file naming convention is not followed in the Oracle BPEL Process Manager 10g project, the properties will not be upgraded correctly. If you need to change the name to meet the file naming conventions, then also update the wsdl file that imports the property file name, accordingly.

10.2.5 Upgrading Projects With the transaction=participate Property

If you open and upgrade an Oracle BPEL Process Manager 10g project that has a configuration property, transaction=participate, then that property will not be migrated to 11g when you open the application in Oracle JDeveloper 11g. This configuration property is no longer supported in Oracle Fusion Middleware 11g. If you open and upgrade an Oracle BPEL Process Manager 10g project has a partnerLink binding property, transaction=participate, then that property will be dropped on the caller side. The callee project instead should have the property setting bpel.config.transaction=required. This caller to callee setting propagation is not performed by upgrade and must be performed manually after you upgrade the application and before you attempt to deploy it on Oracle Fusion Middleware 11g.

10.2.6 Specifying Domain Descriptor Properties in Oracle BPEL Process Manager 11g

In Oracle BPEL Process Manager 10g, you specify domain properties in the domain.xml descriptor file. In Oracle BPEL Process Manager 11g, you specify Oracle BPEL Process Manager engine properties in bpel-config.xml and soa-infra-config.xml both are accessible as MBeans. Table 10–1 compares the domain descriptor properties available in Oracle BPEL Process Manager 10g and Oracle BPEL Process Manager 10g. There is only one domain in Oracle BPEL Process Manager 11g, which means that these properties will affect the entire server.