Upgrade Tasks associated with BPEL
The following sections describe some of the common upgrade tasks that have to be performed 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.
Developers should go through this section and verify the relevant steps pertaining to the individual BPEL Projects.
Ø Providing Missing Binding Information for External References
Issue: When a source project in the application depends on Oracle Application Server 10g Release 3 (10.1.3) Oracle BPEL Process 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. 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.
Action: 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 and 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.
Ø Correcting Problems With Oracle BPEL Process Manager Test Suites
Issue: 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.
Action: To set up the tests in your 11g environment, refer to "Testing SOA Composite Applications" in the Oracle® Fusion Middleware Developer’s Guide for Oracle SOA Suite 11g Release 1 (11.1.1) .
Ø Using Oracle BPEL Process Manager Deployment Plans After Upgrade
Issue: Deployment and configuration plans that are set up in Oracle Application Server 10g for Oracle BPEL Process Manager user projects are not upgraded in Oracle JDeveloper 11g.
Action: Create the 11g deployment plan manually, after the application is migrated in Oracle JDeveloper.
Ø Upgrading Fault Policies in an Oracle BPEL Process Manager Project
Issue: During upgrade, any fault policies and bindings that are set up in a user project are not automatically upgraded to 11g.
Action: Manually recreate the fault policies and bindings in the Oracle JDeveloper 11g project after you upgrade your applications.
Ø Verifying New and Deprecated Properties in the bpel.xml Deployment Descriptor
Issue: If any of the 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.
Action: 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 SOA Suite 11g, refer to "Deployment Descriptor Properties" in the Oracle® Fusion Middleware Developer’s Guide for Oracle SOA Suite 11g Release 1 (11.1.1) provided.
Ø Upgrading User-Defined (Custom) XPath Functions in an Oracle BPEL Process Manager Project
Issue: While upgrading applications in Oracle JDeveloper 11g, any custom XPath functions in the application projects are not upgraded automatically.
Action: After upgrade, 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.
Ø Verifying the Properties File Name When Upgrading Projects That Use Correlation Sets in an Asynchronous Service.
Issue: If Oracle BPEL Process Manager 10g project uses correlation sets in an asynchronous service, make sure that the correlation set properties file uses the following proper naming convention: BPEL_FILE_NAME_Properties.wsdl
Action: If the 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.
Ø Upgrading Projects With the transaction=participate Property
Issue: If Oracle BPEL Process Manager 10g project has a configuration property, transaction=participate, then that property will not be migrated to 11g when the application is opened in Oracle JDeveloper 11g. This configuration property is no longer supported in Oracle Fusion Middleware SOA Suite 11g.
Action: The property will be dropped on the caller side. The callee project instead should have the property setting bpel.config.transaction=required or bpel.config.transaction=requiresNew (participate in a new transaction). This caller to callee setting propagation is not performed by upgrade and must be performed manually after the application is upgraded and before attempting to deploy it on Oracle Fusion Middleware SOA Suite 11g.
Ø Specifying Domain Descriptor Properties in Oracle BPEL Process Manager 11g
In Oracle BPEL Process Manager 10g, domain properties are specified in the domain.xml descriptor file. In Oracle BPEL Process Manager 11g, Oracle BPEL Process Manager engine properties are specified in bpel-config.xml and soa-infra-config.xml (both are accessible as MBeans). There is only one domain in Oracle BPEL Process Manager 11g, which means that these properties will affect the entire server.
In the current release of 11g, there is only one Domain in Oracle BPEL Process Manager. If client has implemented multiple domains in BPEL, then all the processes in various domains have to be deployed onto a single domain.
If any custom values have been set for the properties in domain.xml for individual domains, they have to be migrated to bpel-config.xml and soa-infra-config.xml manually.
Refer Oracle® Fusion Middleware Developer’s Guide for Oracle SOA Suite 11g Release 1 (11.1.1) for various Descriptor properties.
1 comments:
Great reading yyour blog post
Post a Comment