Providing Missing Binding Information for External References

10-4 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF For example, after you upgrade a project that uses WSIF bindings and EJBs, it will fail to run on due to WSIF binding errors. To work around the these problems, you typically must perform the following steps after you have upgraded the project to Oracle JDeveloper 11g: 1. Replace the properties of the binding.wsif entry in the composite.xml file with the correct JNDI related properties for Oracle WebLogic Server. For example, the following are typical properties set for a Oracle WebLogic Server domain for an application called the BankTransferDemo application, which was deployed previously on Oracle Application Server 10g Release 3 10.1.3: binding.wsif port=....... location=...... . property name=jndiName ejbsessionBankTransfer property . property name=java.naming.factory.initial weblogic.jndi.WLInitialContextFactory property . property name=java.naming.provider.url t3:[SERVER HOST NAME]:[SERVER PORT] property . property name=java.naming.security.principal [DOMAIN ADMIN USER NAME] property . property name=java.naming.security.credentials [DOMAIN ADMIN PASSWORD] property . binding.wsif 2. Copy the EJB classes to the following directory in your newly upgraded 11g project: SOA_JDEV_PROJECT_HOME SCA-INFclasses For more information about using Oracle JDeveloper to modify your Oracle SOA Suite applications, see the Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.

10.2 Additional Considerations for Oracle BPEL Process Manager Applications

The following sections describe additional considerations you should review after upgrading Oracle BPEL Process Manager applications: ■ Section 10.2.1, Verifying New and Deprecated Properties in the bpel.xml Deployment Descriptor ■ Section 10.2.2, Upgrading User-Defined Custom XPath Functions in an Oracle BPEL Process Manager Project ■ Section 10.2.3, Change in Support for Multiple BPEL Implementations 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.