9 Considerations When Upgrading Oracle SOA Applications

9.3.1.1 Upgrading to the Oracle Fusion Middleware Java API for Oracle Business Rules

The following sections introduce the Oracle Business Rules 11g SDK and API and provide instructions for upgrading to the Oracle Business Rules API:

• Overview of the Oracle Business Rules SDK and API Changes for 11g

• Accessing a Dictionary in the Development Environment

• Accessing a Repository in a Production Environment

• Generating RL Code

String path; // the path to the file repository
Locale locale; // the desired Locale
// The following code assumes that the path and locale have been set appropriately
RepositoryType rt =
RepositoryManager.getRegisteredRepositoryType("oracle.rules.sdk.store.jar");
RuleRepository repos = RepositoryManager.createRuleRepositoryInstance(rt);
RepositoryContext rc = new RepositoryContext();
rc.setLocale(locale);
rc.setProperty("oracle.rules.sdk.store.jar.path", path);
repos.init(rc);

protected static final String DICT_LOCATION ="C:\\scratch\\CarRental.rules";
...
RuleDictionary dict = null;
Reader reader = null;
try {
  reader = new FileReader(new File(DICT_LOCATION));
  dict = RuleDictionary.readDictionary(reader, new
                   DecisionPointDictionaryFinder(null));
  List<SDKWarning> warnings = new ArrayList<SDKWarning>();
  dict.update(warnings);
  if (warnings.size() > 0 ) {
     System.err.println("Validation warnings: " + warnings);
     }
     } catch (SDKException e){
         System.err.println(e);
     } catch (FileNotFoundException e){
         System.err.println(e);
     } catch (IOException e){
         System.err.println(e);
     } finally {
         if (reader != null) { 
              try { reader.close(); } catch (IOException ioe)
                  {ioe.printStackTrace();}
     }
}

String url; // the URL for the WebDAV repository
Locale locale; // the desired Locale
// The following code assumes that the url and locale have been set appropriately
RepositoryType rt =
   RepositoryManager.getRegisteredRepositoryType("oracle.rules.sdk.store.webdav");
RuleRepository repos = RepositoryManager.createRuleRepositoryInstance(rt);
RepositoryContext rc = new RepositoryContext();
rc.setLocale(locale);
rc.setProperty("oracle.rules.sdk.store.webdav.url", url);
repos.init(rc);
RuleDictionary dictionaryWithInitialVersion =
                repos.loadDictionary(dictionaryName);
RuleDictionary dictionarySpecificVersion = repos.loadDictionary(dictionaryName,
                dictionaryVersion);

import static
    oracle.rules.sdk2.repository.RepositoryManager.createRuleRepositoryInstance;
import static
    oracle.rules.sdk2.repository.RepositoryManager.getRegisteredRepositoryType;
import static oracle.rules.sdk2.store.mds.Keys.CONNECTION;
...
private static final String DICT_PKG = "oracle.middleware.rules.demo";
private static final String DICT_NAME = "CarRental";
private static final DictionaryFQN DICT_FQN =
new DictionaryFQN(DICT_PKG, DICT_NAME);
...
RuleRepository repo =
     createRuleRepositoryInstance(getRegisteredRepositoryType(CONNECTION));
repo.init(new RepositoryContext() {{
     setDictionaryFinder(new DecisionPointDictionaryFinder(null));
}});
RuleDictionary dict = repo.load(DICT_FQN);

//init a rule session
String rsname = "vehicleRent";
String dmrl = dict.dataModelRL();
String rsrl = dict.ruleSetRL( rsname );

9.3.1.2 Upgrading to the Oracle Fusion Middleware Infrastructure Management Java API for Oracle SOA Suite

Oracle SOA Suite 11g introduces a new infrastructure management API that replaces several other APIs previously available in Oracle SOA Suite 10g.

For more information about the new API, refer to the Oracle Fusion Middleware Release Notes, which are available as part of the Oracle Fusion Middleware 11g documentation library.

9.3.5.1 Verifying that serviceKey Endpoints Are Available Before Upgrade

If you have a 10g Release 3 (10.1.3) project that references an endpoint URL that uses a serviceKey from OSR, then you must be sure that the endpoint URL is up and available when you upgrade the application. Otherwise, the upgrade of the application will fail. To prevent such a failure, verify that the endpoint URLs are available, and if necessary, modify the endpoint URLs in bpel.xml or the routing service to point to new URL which is accessible.

9.3.5.2 Changing to the orauddi Protocol

In Oracle Application Server 10g Release 3 (10.1.3), Oracle BPEL Process Manager and Oracle Enterprise Service Bus projects used the uddi protocol to obtain resource references from OSR. In Oracle Fusion Middleware 11g, Oracle BPEL Process Manager and Oracle Mediator projects use the orauddi protocol.

As a result, prior to upgrading your Oracle BPEL Process Manager or Oracle Enterprise Service Bus projects, you must do the following:

1. Use the service registry to modify the registered service so it uses the new bindings supported by Oracle Fusion Middleware 11g.

   For example, in OSR, do the following:

   1. Log in to your Oracle Service Registry.

   2. On the Search tab, click Businesses.

   3. Click Add Name to search for a business by name.

   4. From the search results, click the name of the business you want to modify.

   5. In the left pane of the View Business page, right-click the service you want to modify and select Add Binding from the context menu.

   6. From the Type drop-down menu on the Add Binding page, select wsdlDeployment.In the Access Point field, enter the URL.

      For example:

      http://machine:port/Proj_ep?WSDL/
      

   7. Click Add Binding.

   8. Click Save Changes.

2. Open and upgrade the application in Oracle JDeveloper 11g.

3. In Oracle JDeveloper, edit the composite.xml file for the upgraded project and configure the endpoint URL using the UDDI Registry option on the Resource Palette.

For more information about the UDDI registry, visit the following URL:

http://www.oracle.com/technology/tech/soa/uddi/index.html

9.3.6.1 Benefits of Using the Oracle SOA Suite Command-Line Upgrade Tool

The Oracle SOA Suite Command-Line Upgrade Tool has the following benefits:

• You can use the command-line tool to automate your application upgrade work, using scripts or other command-line automation tools.

• The command-line tool upgrades both Oracle BPEL Process Manager projects, and upgrades Oracle Enterprise Service Bus 10g projects to Oracle Mediator 11g.

• With the command-line tool, you can merge BPEL projects together and create a single composite out of multiple BPEL projects. This is not possible when you use the Oracle JDeveloper Migration Wizard.

• The functionality is exactly the same as the JDeveloper mode when it comes to dealing with SOA project contents because the same codebase is used.

9.3.6.2 Using the Oracle SOA Suite Command-Line Upgrade Tool with Oracle JDeveloper 11g

The Oracle SOA Suite Command-Line Upgrade Tool is compatible (with restrictions) with the Oracle JDeveloper Migration Wizard. In other words, you can choose to remain in command-line mode all the way through the upgrade process (upgrade, compile, package, and deploy), or you can choose to move to Oracle JDeveloper, or you use both tools, with no functionality loss.

However, it is important to note that the command-line tool upgrades SOA project artifacts only. Other Oracle JDeveloper artifacts (for example, the .jpr and .jws files) are ignored.

To work around this restriction, note the following:

• The Oracle SOA Suite Command-Line Upgrade Tool copies files from the BPEL suitcase directory (the BPEL subdirectory or the directory hosting the BPEL files) to the specified target directory, specified on the command line.

• The above copying action does not copy the .jpr or .jws files. After the upgrade, the target directory contains only the upgraded SOA project contents.

• To remedy this problem in Oracle JDeveloper, you can create a new application or new project, and then define the project directory to be the newly upgraded composite directory.

9.3.6.3 Limitations When Upgrading Human Workflow Applications with the Oracle SOA Suite Command-Line Upgrade Tool

If you attempt to use the Oracle SOA Suite Command-Line Upgrade Tool to upgrade an application that contains Oracle Human Workflow projects, note that the tool will create a separate project for each upgraded task form.

This resulting project is an Oracle ADF project and Oracle ADF does not support command line deployment. As a result, after using the Oracle SOA Suite Command-Line Upgrade Tool, you must open the upgraded projects in Oracle JDeveloper 11g deploy it from JDeveloper.

For information about how to open the upgraded project in Oracle JDeveloper, see Chapter 9, "Using the Oracle SOA Suite Command-Line Upgrade Tool with Oracle JDeveloper 11g".

9.3.6.4 Upgrading BPEL Projects with the Oracle SOA Suite Command-Line Upgrade Tool

The files required to run the Oracle SOA Suite Command-Line Upgrade Tool are installed automatically when you install Oracle JDeveloper 11g and when you install Oracle SOA Suite 11g:

• When you install the Oracle SOA Suite 11g, the required XML files are installed in the bin directory of the Oracle SOA Suite Oracle home.

• When you install Oracle JDeveloper 11g, the required XML files are installed in the bin directory of the Oracle JDeveloper home.

You can use this files in this directory, together with Apache Ant, to migrate your 10g Release 3 (10.1.3) SOA projects to 11g.

To use the ANT project:

1. Set the required environment variables, by running the following script:

   On UNIX systems:

   ORACLE_HOME/bin/soaversion.sh
   

   On Windows systems:

   ORACLE_HOME\bin\soaversion.bat
   

2. Run the Ant project, as follows:

   ant -f ORACLE_HOME/bin/ant-sca-upgrade.xml 
          -Dsource sourceDir 
          -Dtarget targetDir 
          -DappName app_name
   

When you run the Ant command, note the following:

• Your BPEL files from the source directory are migrated to the target directory you specified on the command line. The migration tool creates an application subdirectory using the value you entered as the appName value on the command line.

• The sourceDir you specified on the command line can be the bpel folder, the parent directory that hosts the bpel folder, or the Oracle Enterprise Service Bus project folder.

  Note that the source directory is backed up before migration; if you must re-run the upgrade, be sure to restore the source files using the backup that was created before the invoking the tool. You can identify the backup directory by the ".backup" suffix in its name.

• The sourceDir and targetDir parameters must be fully-qualified path names.

• After upgrade, the logs can be found in the following output directory:

  ORACLE_HOME/upgrade/logs
  

• After upgrade, you must run the SCA-Compiler (ant-sca-compile.xml) which will verify the migrated sources. Because the SCA-Upgrade will not generate complete artifacts in all cases, you will see some errors or warnings from SCA-Compiler with pointers on how to fix them. Check the SCA Compiler for reference.

• After getting a clean pass from the SCA-Compiler you can use the ant-sca-package.xml tool to package your application. You can then deploy the application using ant-sca-deploy.xml. After deployment, your project will be available to the server for testing.

  Note, however, that in most cases, you will likely want to open the upgraded project in Oracle JDeveloper 11g. From there, you can easily review, verify, and make any necessary updates to the application projects.

  For more information, see Section 9.3.6.2, "Using the Oracle SOA Suite Command-Line Upgrade Tool with Oracle JDeveloper 11g".

9.3.6.5 Combining Multiple BPEL Projects Into a Single Composite with the Oracle SOA Suite Command-Line Upgrade Tool

Using the Oracle SOA Suite Command-Line Upgrade Tool, you can merge BPEL projects together and create a single composite. This is not possible when you use the Migration Wizard in Oracle JDeveloper.

To combine multiple BPEL projects into a single composite, provide multiple source directories as part of the -Dsource property on the command line.

Path separators can be a colon (:) or a semicolon (;). Ant will convert the separator to platform's local conventions. As a guideline, also use double quotes to identity the multiple source directories to prevent Ant from parsing the input in an unexpected manner.

The first source directory specified will be considered as the root of the 11g project and will determine the composite name.

For example:

ant -f ORACLE_HOME/bin/ant-sca-upgrade.xml
    -Dsource "sourceDir1:sourceDir2"
    -Dtarget targetDir
    -DappName app_name

The first project in the source list is considered the root project and only those services are exposed as Composite Services. Anytime you use the merge feature, it is recommended that the projects be related.

Merging of projects is supported for BPEL projects only. ESB projects cannot be merged with other BPEL or other ESB projects.

9.3.6.6 Upgrading Oracle Enterprise Service Bus (ESB) Projects with the Oracle SOA Suite Command-Line Upgrade Tool

The Oracle SOA Suite Command-Line Upgrade Tool can also be used to upgrade ESB projects to Oracle Mediator 11g.

To upgrade an ESB project, use the instructions in Section 9.3.6.4, "Upgrading BPEL Projects with the Oracle SOA Suite Command-Line Upgrade Tool", but replace the Ant command with the following:

ant -f $ORACLE_HOME/bin/ant-sca-upgrade.xml -Dsource sourceDir -Dtarget targetDir -DappName app_name mediator

9.3.6.7 Upgrading Domain Value Maps (DVMs) and Cross References with the Oracle SOA Suite Command-Line Upgrade Tool

If you use domain value maps (DVMs) or Cross References in your Oracle BPEL Process Manager 10g or Oracle Enterprise Service Bus 10g projects, then note the following:

• The xPath functions you use to access the domain value maps or cross references are upgraded automatically to Oracle BPEL Process Manager and Oracle Mediator 10g when you open and upgrade your applications in Oracle JDeveloper 11g.

• However, you must perform a manual upgrade task to upgrade the domain value maps and cross references that are saved in the Oracle Enterprise Service Bus repository. The upgrade process moves the domain value maps from the ESB repository to the Oracle Fusion Middleware 11g Metadata Services (MDS) repository.

  For more information, see "Managing the MDS Repository" in the Oracle Fusion Middleware Administrator's Guide.

To upgrade your 10g domain value maps in the ESB repository perform the following tasks.

Task 1   Export the domain value map metadata to a ZIP file

1. Change directory to the Oracle Enterprise Service Bus Oracle home.

2. Use the export script to export the metadata to a ZIP file.

   For example, on UNIX systems:

   ORACLE_HOME/export.sh metadata10g.zip
   

Task 2   Convert the ZIP file to an Oracle SOA Suite archive file

Use Apache Ant and the upgrade-xrefdvm target in the sca-upgrade.xml file to use the metadata ZIP file to generate an Oracle SOA Suite archive JAR file:

1. Change directory to the Oracle SOA Suite 11g Oracle home.

2. Use the following command to generate a SOA archive file, which will automatically be called sca_XrefDvmFiles10g_rev1.0.jar:

   ant -f ant-sca-upgrade.xml upgrade-xrefdvm
       -Dsource=location_of_the_zip_file
       -Dtarget=location_of_the_soa_archive
   

   For example:

   ant -f ant-sca-upgrade.xml upgrade-xrefdvm 
       -Dsource=$ORACLE_HOME/temp/upgrade/metadata10g.zip 
       -Dtarget=$ORACLE_HOME/temp/upgrade
   

Task 3   Import the archive file into MDS repository

1. Start Oracle JDeveloper 11g and create a new application.

2. Import the Oracle SOA Suite archive into a new SOA project:

   1. From the Oracle JDeveloper 11g File menu, select Import, then SOA Archive into SOA Project.

   2. In the Create SOA Project from SOA Archive Dialog Box, click Browse and locate the sca_XrefDvmFiles10g_rev1.0.jar file that you created previously in this procedure.

   3. Make sure that the Project Name and Composite Name in the Create SOA Project from SOA Archive dialog box have the same name, which must be XrefDvmFiles10g.

   4. Click OK to create the new SOA project, which is called XrefDvmFiles10g.

      The new project consists of an empty composite, along with the upgraded XRef and DVM files.

3. Create a metadata archive (MAR) file for the application, which includes the XRef and DVM metadata, and then deploy the MAR to the Oracle WebLogic Server domain.

   For information about creating a MAR, see "Creating a Deployment Profile" in the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

After you upgrade the DVM and cross reference metadata to 11g, you can then use Oracle JDeveloper 11g to modify the entries in the XrefDvmFiles10g project as needed. Each time you make changes, you must then transfer them to the proper MDS repository using the MAR deployment process.

9.4.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 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.

Note that a similar message also appears when you are using Oracle SOA Suite 10g Web services that use HTTP bindings, which are not supported in Oracle SOA Suite 11g.

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 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.

For more information, refer to the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

9.4.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 Developer's Guide for Oracle SOA Suite.

9.4.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.

For more information about creating configuration plans in 11g, see "Moving SOA Composite Applications to and from Development, Test, and Production Environments" in the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

9.4.1.4 Upgrading Fault Policies in an Oracle BPEL Process Manager Project

When you open your 10g application in Oracle JDeveloper and use the Oracle JDeveloper Migration Wizard to upgrade the application, any fault policies and bindings that you set up in a user project are not automatically upgraded to 11g.

The reasons are as follows:

• In Oracle BPEL Process Manager 10g, fault policies were stored with the server and bindings were either stored with the server or specified in bpel.xml. In Oracle BPEL Process Manager 11g, fault policies and fault bindings are stored in the Oracle JDeveloper 11g project.

• In general, fault policies and bindings in Oracle BPEL Process Manager 11g are different than those in previous releases. For example, the file name and syntax is different, fault policies apply both to Oracle Mediator and Oracle BPEL Process Manager, and bindings are at a reference, component, and composite level in 11g.

For these reasons, you must manually recreate the fault policies and bindings in the Oracle JDeveloper 11g project after you upgrade your applications.

Similarly, when you upgrade an Oracle Enterprise Service Bus 10g Release 3 (10.1.3) project to 11g, you must add the retry parameters defined in esb_config.ini file to the 11g fault-policy.xml file.

For more information, see:

• "Using Fault Handling in a BPEL Process" in the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite

• "Using Mediator Error Handling" in the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

9.4.1.5 Upgrading a 10g Project With No BPEL Folder

If the 10g Release 3 (10.1.3) application you are upgrading includes a project where all the project artifacts are in one folder and the BPEL artifacts are not separated into their own folder in the project, then the Oracle JDeveloper Migration Wizard will not be able to upgrade those artifacts.

To avoid this problem, do one of the following:

• Before upgrading the project, use Oracle JDeveloper 10g to create a BPEL folder and move all the artifacts (except the build.xml and build.properties files) into that folder. Then you can proceed with upgrading the project.

• Use the Oracle SOA Suite command-line upgrade tool. The command-line tool will upgrade the artifacts even if a BPEL folder does not exist in the project. For more information, see Section 9.3.6, "Using the Oracle SOA Suite Command-Line Upgrade Tool".

9.4.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 Developer's Guide for Oracle SOA Suite.

9.4.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 Developer's Guide for Oracle SOA Suite.

9.4.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.

9.4.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.

9.4.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 propogation 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.

9.4.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).

There is only one domain in Oracle BPEL Process Manager 11g, which means that these properties will affect the entire server.

9.6.5.1 Using Web Services Clients with Oracle BAM 11g

If you have developed client applications that communicate via Web services with Oracle BAM 10g servers, then you can continue to use those clients after you upgrade to Oracle BAM 11g, with no changes to the client code.

This is possible because the DataObjectOperations Web service available in Oracle BAM 10g is still available in Oracle BAM 11g. The DataObjectOperations Web service has been renamed to DataObjectOperations10131, but the WSDL end point URL remains the same, so client processes can continue working with Oracle BAM 11g.

However, to ensure that your clients continue to work successfully with Oracle BAM 11g, Oracle recommends that you apply the latest patch set to any Oracle BPEL Process Manager 10g clients that are using Oracle BAM 11g environment.

http://www.oracle.com/technology/documentation/

If you are using the latest version of Oracle JDeveloper 10g Release 3 (10.1.3), to create a connection to Oracle BAM 11g, the Domain field in the BAM connection wizard is completely ignored and can be left blank.

For more information about the DataObjectOperations10131 Web service in Oracle BAM 11g, refer to "Using Oracle BAM Web Services" in the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

9.6.5.2 Invoking Web Services from Oracle BAM Alerts

In Oracle BAM 11g, you could configure alerts to invoke a Web service by invoking an external action. This method of using alerts to invoke a Web service is no longer supported in Oracle BAM 11g.

Instead, in Oracle BAM 11g, you can create an alert rule that calls the "Call a Web Service" action.

For more information, see "Creating Oracle BAM Alerts" in the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

9.6.5.3 Using the ManualRuleFire Web Service in Oracle BAM 11g

If you used the ManualRuleFire Web service in Oracle BAM 10g, note that the end point URL for this Web service has changed in Oracle BAM 11g.

For more information, refer to "Using the ManualRuleFire Web Service" in the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

9.6.5.4 New Support for Web Services in Oracle BAM 11g

For complete information about the new Web services features in Oracle BAM 11g, refer to "Using Oracle BAM Web Services" in the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

9.11.1.1 A Note About Oracle WSM 10g Gateways

As described in "Examining the Rearchitecture of Oracle WSM in Oracle Fusion Middleware" in the Oracle Fusion Middleware Security and Administrator's Guide for Web Services, Oracle Fusion Middleware 11g Release 1 (11.1.1) does not include a Gateway component.

You can continue to use the Oracle WSM 10g Gateway components with Oracle WSM 10g policies in your applications. For information about Oracle WSM 10g interoperability, see "Interoperability with Oracle WSM 10g Security Environments" in the Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

9.11.1.2 A Note About Third-party Software

As described in "Examining the Rearchitecture of Oracle WSM in Oracle Fusion Middleware" in the Oracle Fusion Middleware Security and Administrator's Guide for Web Services, Oracle WSM 10g supported policy enforcement for third-party application servers, such as IBM WebSphere and Red Hat JBoss. Oracle Fusion Middleware 11g Release 1 (11.1.1) only supports Oracle WebLogic Server.

You can continue to use the third-party application servers with Oracle WSM 10g policies. For information about Oracle WSM 10g interoperability, see "Interoperability with Oracle WSM 10g Security Environments" in the Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

9.12.2.1 OC4J 10g

Edit the deployment descriptors for the Web service and client, as described in the following sections.

For more information about the deployment descriptor elements, see "OracleAS Web Services Security Schema" in Oracle Application Server Web Services Security Guide in the Oracle Application Server 10g Release 3 (10.1.3.1.0) documentation library at:

http://www.oracle.com/technology/documentation/

Web Service Client (with sample data)

Define the <signature> and <encrypt> elements in the client deployment descriptor. For example:

<signature>
   <signature-method>RSA-SHA1</signature-method> 
   <tbs-elements>
      <tbs-element local-part="Body" name-space=
       "http://schemas.xmlsoap.org/soap/envelope/" /> 
      <tbs-element name-space=
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" local-part="Timestamp" /> 
   </tbs-elements>
   <add-timestamp created="true" expiry="28800" /> 
</signature>
<encrypt>
   <recipient-key alias="orakey"/>
   <encryption-method>AES-128</encryption-method> 
   <keytransport-method>RSA-OAEP-MGF1P</keytransport-method> 
   <tbe-elements>
      <tbe-element local-part="Body" name-space=
       "http://schemas.xmlsoap.org/soap/envelope/" mode="CONTENT" />
   </tbe-elements>
</encrypt>

Web Service (with sample data)

Define the <verify-signature> and <decrypt> elements in the service deployment descriptor. For example:

<verify-signature>
   <tbs-elements>
      <tbs-element name-space="http://schemas.xmlsoap.org/soap/envelope/" 
       local-part="Body" /> 
      <tbs-element name-space=
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" 
       local-part="Timestamp" /> 
   </tbs-elements>
   <verify-timestamp expiry="28800" created="true" /> 
</verify-signature>
<decrypt>
   <tbe-elements>
      <tbe-element 
       name-space="http://schemas.xmlsoap.org/soap/envelope/" 
       local-part="Body" mode="CONTENT" /> 
   </tbe-elements>
</decrypt>

9.12.2.2 Oracle WSM 11g

Perform the following steps:

1. Attach policies as follows:

   Client: oracle/wss10_message_protection_client_policy.

   Web service: oracle/wss10_message_protection_service_policy.

   For more information about attaching policies in Oracle Fusion Middleware 11g, see "Attaching Policies to Web Services" in Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

2. Leave the configuration set for message body signing and encryption.

9.12.3.1 OC4J 10g

Edit the deployment descriptors for the Web service and client, as described in the following sections.

For more information about the deployment descriptor elements, see "OracleAS Web Services Security Schema" in Oracle Application Server Web Services Security Guide in the Oracle Application Server 10g Release 3 (10.1.3.1.0) documentation library at:

http://www.oracle.com/technology/documentation/

Web Service Client (with sample data)

Define the <signature> element in the client deployment descriptor. For example:

<signature>
   <signature-method>RSA-SHA1</signature-method> 
   <tbs-elements>
      <tbs-element local-part="Body" name-space=
       "http://schemas.xmlsoap.org/soap/envelope/" /> 
      <tbs-element name-space=
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" local-part="Timestamp" /> 
   </tbs-elements>
   <add-timestamp created="true" expiry="28800" /> 
</signature>

Web Service (with sample data)

Define the <verify-signature> element in the service deployment descriptor. For example:

<verify-signature>
   <tbs-elements>
      <tbs-element name-space="http://schemas.xmlsoap.org/soap/envelope/" 
       local-part="Body" /> 
      <tbs-element name-space=
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" 
       local-part="Timestamp" /> 
   </tbs-elements>
   <verify-timestamp expiry="28800" created="true" /> 
</verify-signature>

9.12.3.2 Oracle WSM 11g

Perform the following steps:

1. Attach policies as follows:

   Client: oracle/wss10_message_protection_client_policy.

   Web service: oracle/wss10_message_protection_service_policy.

   For more information about attaching policies in Oracle Fusion Middleware 11g, see "Attaching Policies to Web Services" in Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

2. Configure the policy assertion for message body signing only.

9.12.4.1 OC4J 10g

Edit the deployment descriptors for the Web service and client, as described in the following sections.

Web Service Client (with sample data)

Define the <encrypt> element in the client deployment descriptor. For example:

<encrypt>
   <recipient-key alias="orakey"/>
   <encryption-method>AES-128</encryption-method> 
   <keytransport-method>RSA-OAEP-MGF1P</keytransport-method> 
   <tbe-elements>
      <tbe-element local-part="Body" name-space=
       "http://schemas.xmlsoap.org/soap/envelope/" mode="CONTENT" />
   </tbe-elements>
</encrypt>

Web Service (with sample data)

Define the <decrypt> element in the service deployment descriptor. For example:

<decrypt>
   <tbe-elements>
      <tbe-element 
       name-space="http://schemas.xmlsoap.org/soap/envelope/" 
       local-part="Body" mode="CONTENT" /> 
   </tbe-elements>
</decrypt>

9.12.4.2 Oracle WSM 11g

Perform the following steps:

1. Attach policies as follows:

   Client: oracle/wss10_message_protection_client_policy.

   Web service: oracle/wss10_message_protection_service_policy.

   For more information about attaching policies in Oracle Fusion Middleware 11g, see "Attaching Policies to Web Services" in Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

2. Configure the policy assertion for message body encryption only.

9.12.5.1 OC4J 10g

Edit the deployment descriptors for the Web service and client, as described in the following sections.

For more information about the deployment descriptor elements, see "OracleAS Web Services Security Schema" in Oracle Application Server Web Services Security Guide in the 10g Release 3 (10.1.3.1.0) documentation library at:

http://www.oracle.com/technology/documentation/

Web Service Client (with sample data)

Define the <username-token>, <signature>, and <encrypt> elements in the client deployment descriptor. For example:

<username-token password-type="PLAINTEXT" add-nonce="false" 
 add-created="false" /> 
<signature>
   <signature-method>RSA-SHA1</signature-method> 
   <tbs-elements>
      <tbs-element local-part="Body" name-space=
       "http://schemas.xmlsoap.org/soap/envelope/"/> 
      <tbs-element name-space=
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" 
       local-part="Timestamp" /> 
      <tbs-element name-space=
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" 
       local-part="UsernameToken" /> 
   </tbs-elements>
   <add-timestamp created="true" expiry="28800" /> 
</signature>
<encrypt>
   <recipient-key alias="orakey" /> 
   <encryption-method>AES-128</encryption-method> 
   <keytransport-method>RSA-OAEP-MGF1P</keytransport-method> 
   <tbe-elements>
      <tbe-element local-part="Body" name-space=
       "http://schemas.xmlsoap.org/soap/envelope/" mode="CONTENT" /> 
      <tbe-element name-space=
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" 
       local-part="UsernameToken" /> 
   </tbe-elements>
</encrypt>

Web Service (with sample data)

Define the <verify-username-token>, <verify-signature>, and <decrypt> elements in the service deployment descriptor. For example:

<verify-username-token password-type="PLAINTEXT" require-nonce="false" 
 require-created="false" /> 
<verify-signature>
   <tbs-elements>
      <tbs-element name-space="http://schemas.xmlsoap.org/soap/envelope/" 
       local-part="Body" /> 
      <tbs-element name-space=
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" 
       local-part="Timestamp" /> 
   </tbs-elements>
   <verify-timestamp expiry="28800" created="true" /> 
</verify-signature>
<decrypt>
   <tbe-elements>
      <tbe-element name-space="http://schemas.xmlsoap.org/soap/envelope/" 
       local-part="Body" mode="CONTENT" /> 
   </tbe-elements>
</decrypt>

9.12.5.2 Oracle WSM 11g

Perform the following steps:

1. Attach policies as follows:

   Client: oracle/wss10_username_token_with_message_protection_client_policy.

   Web service: oracle/wss10_username_token_with_message_protection_service_policy.

   For more information about attaching policies in Oracle Fusion Middleware 11g, see "Attaching Policies to Web Services" in Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

2. Leave the configuration set for message body signing and encryption.

3. Configure the Authentication and Identity Assertion provider.

9.12.6.1 OC4J 10g

Edit the deployment descriptors for the Web service and client, as described in the following sections.

Web Service Client (with sample data)

Define the <saml-token>, <signature>, and <encrypt> elements in the client deployment descriptor. For example:

<saml-token issuer-name="www.oracle.com" name="weblogic" 
 name-format="UNSPECIFIED">
   <subject-confirmation-method>
      <confirmation-method>SENDER-VOUCHES</confirmation-method> 
   </subject-confirmation-method>
</saml-token>
<signature>
   <signature-method>RSA-SHA1</signature-method> 
   <tbs-elements>
      <tbs-element local-part="Body" 
       name-space="http://schemas.xmlsoap.org/soap/envelope/" /> 
      <tbs-element name-space=
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" 
       local-part="Timestamp" /> 
   </tbs-elements>
   <add-timestamp created="true" expiry="28800" /> 
</signature>
<encrypt>
   <recipient-key alias="orakey" /> 
   <encryption-method>AES-128</encryption-method> 
   <keytransport-method>RSA-OAEP-MGF1P</keytransport-method> 
   <tbe-elements>
      <tbe-element local-part="Body" name-space=
       "http://schemas.xmlsoap.org/soap/envelope/" mode="CONTENT" /> 
   </tbe-elements>
</encrypt>

Web Service (with sample data)

Define the <verify-saml-token>, <verify-signature>, and <decrypt> elements in the service deployment descriptor. For example:

<verify-saml-token>
   <subject-confirmation-methods>
      <confirmation-method>SENDER-VOUCHES</confirmation-method> 
   </subject-confirmation-methods>
</verify-saml-token>
<verify-signature>
   <tbs-elements>
      <tbs-element name-space="http://schemas.xmlsoap.org/soap/envelope/" 
       local-part="Body" /> 
      <tbs-element name-space=
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" 
       local-part="Timestamp" /> 
   </tbs-elements>
   <verify-timestamp expiry="28800" created="true" /> 
</verify-signature>
<decrypt>
   <tbe-elements>
     <tbe-element name-space="http://schemas.xmlsoap.org/soap/envelope/" 
      local-part="Body" mode="CONTENT" /> 
   </tbe-elements>
</decrypt>
 

9.12.6.2 Oracle WSM 11g

Attach policies as follows:

• Client: oracle/wss10_saml_token_with_message_protection_client_policy.

• Web service: oracle/wss10_saml_token_with_message_protection_service_policy.

For more information about attaching policies in Oracle Fusion Middleware 11g, see "Attaching Policies to Web Services" in Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

9.12.7.1 OC4J 10g

Edit the deployment descriptors for the Web service and client, as described in the following sections.

Web Service Client (with sample data)

Define the <saml-token>, <signature>, and <encrypt> elements in the client deployment descriptor. For example:

<saml-token issuer-name="www.oracle.com" name="weblogic" 
 name-format="UNSPECIFIED">
   <subject-confirmation-method>
      <confirmation-method>HOLDER-OF-KEY</confirmation-method> 
   </subject-confirmation-method>
</saml-token>
<signature>
   <signature-method>RSA-SHA1</signature-method> 
   <tbs-elements>
      <tbs-element local-part="Body" 
       name-space="http://schemas.xmlsoap.org/soap/envelope/" /> 
      <tbs-element name-space=
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" 
       local-part="Timestamp" /> 
   </tbs-elements>
   <add-timestamp created="true" expiry="28800" /> 
</signature>
<encrypt>
   <recipient-key alias="orakey" /> 
   <encryption-method>AES-128</encryption-method> 
   <keytransport-method>RSA-OAEP-MGF1P</keytransport-method> 
   <tbe-elements>
      <tbe-element local-part="Body" name-space=
       "http://schemas.xmlsoap.org/soap/envelope/" mode="CONTENT" /> 
   </tbe-elements>
</encrypt>

Web Service (with sample data)

Define the <verify-saml-token>, <verify-signature>, and <decrypt> elements in the service deployment descriptor. For example:

<verify-saml-token>
   <subject-confirmation-methods>
      <confirmation-method>HOLDER-OF-KEY</confirmation-method> 
   </subject-confirmation-methods>
</verify-saml-token>
<verify-signature>
   <tbs-elements>
      <tbs-element name-space="http://schemas.xmlsoap.org/soap/envelope/" 
       local-part="Body" /> 
      <tbs-element name-space=
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" 
       local-part="Timestamp" /> 
   </tbs-elements>
   <verify-timestamp expiry="28800" created="true" /> 
</verify-signature>
<decrypt>
   <tbe-elements>
     <tbe-element name-space="http://schemas.xmlsoap.org/soap/envelope/" 
      local-part="Body" mode="CONTENT" /> 
   </tbe-elements>
</decrypt> 

9.12.7.2 Oracle WSM 11g

Attach policies as follows:

• Client: oracle/wss10_saml_hok_with_message_protection_client_policy.

• Web service: oracle/wss10_saml_hok_with_message_protection_service_policy.

For more information about attaching policies in Oracle Fusion Middleware 11g, see "Attaching Policies to Web Services" in Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

9.12.8.1 OC4J 10g

Edit the deployment descriptors for the Web service and client, as described in the following sections.

Web Service Client (with sample data)

Define the <x509-token>, <signature>, and <encrypt> elements in the client deployment descriptor. For example:

<x509-token /> 
<signature>
   <signature-method>RSA-SHA1</signature-method> 
   <tbs-elements>
      <tbs-element local-part="Body" 
       name-space="http://schemas.xmlsoap.org/soap/envelope/" /> 
      <tbs-element name-space=
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" 
       local-part="Timestamp" /> 
   </tbs-elements>
   <add-timestamp created="true" expiry="28800" /> 
</signature>
<encrypt>
   <recipient-key alias="orakey" /> 
   <encryption-method>AES-128</encryption-method> 
   <keytransport-method>RSA-OAEP-MGF1P</keytransport-method> 
   <tbe-elements>
      <tbe-element local-part="Body" 
       name-space="http://schemas.xmlsoap.org/soap/envelope/" mode="CONTENT" /> 
   </tbe-elements>
</encrypt>

Web Service (with sample data)

Define the <verify-x509-token>, <verify-signature>, and <decrypt> elements in the service deployment descriptor. For example:

<verify-x509-token /> 
<verify-signature>
   <tbs-elements>
      <tbs-element name-space="http://schemas.xmlsoap.org/soap/envelope/" 
       local-part="Body" /> 
      <tbs-element name-space=
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" 
       local-part="Timestamp" /> 
   </tbs-elements>
   <verify-timestamp expiry="28800" created="true" /> 
</verify-signature>
<decrypt>
   <tbe-elements>
      <tbe-element name-space="http://schemas.xmlsoap.org/soap/envelope/"
       local-part="Body" mode="CONTENT" /> 
   </tbe-elements>
</decrypt>

9.12.8.2 Oracle WSM 11g

Perform the following steps:

1. Attach policies as follows:

   Client: oracle/wss10_x509_token_with_message_protection_client_policy.

   Web service: oracle/wss10_x509_token_with_message_protection_service_policy.

   For more information about attaching policies in Oracle Fusion Middleware 11g, see "Attaching Policies to Web Services" in Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

2. Leave the configuration set for message body signing and encryption.

3. Configure the Authentication and Identity Assertion provider.

9.12.9.1 OC4J 10g

Configure the application server for SSL and edit the deployment descriptors for the Web service and client, as described in the following sections.

Web Service Client (with sample data)

Define the <username-token> and <signature> elements in the client deployment descriptor. For example:

<username-token password-type="PLAINTEXT" add-nonce="true" 
 add-created="true" />
<signature>
   <add-timestamp created="true" expiry="28800" /> 
</signature>

Web Service (with sample data)

Define the <verify-username> element in the service deployment descriptor. For example:

<verify-username-token password-type="PLAINTEXT" require-nonce="false" require-created="false" />  
<signature>
   <verify-timestamp expiry="28800" created="true" />  
</signature>

9.12.9.2 Oracle WSM 11g

Perform the following step:

1. Configure the application server for SSL.

2. Attach policies as follows:

   Client: oracle/wss_username_token_over_ssl_client_policy.

   Web service: oracle/wss_username_token_over_ssl_service_policy

For more information about attaching policies in Oracle Fusion Middleware 11g, see "Attaching Policies to Web Services" in Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

9.12.10.1 OC4J 10g

Configure the application server for SSL and edit the deployment descriptors for the Web service and client, as described in the following sections.

Web Service Client (with sample data)

Define the <saml-token> and <signature> elements in the client deployment descriptor. For example:

<saml-token name="weblogic" issuer-name="www.oracle.com" 
 name-format="UNSPECIFIED">
   <subject-confirmation-method>
     <confirmation-method>SENDER-VOUCHES</confirmation-method> 
   </subject-confirmation-method>
</saml-token>
<signature>
   <add-timestamp created="true" expiry="28800" /> 
</signature> 

Web Service (with sample data)

Define the <verify-saml-token> element in the service deployment descriptor. For example:

<verify-saml-token>
   <subject-confirmation-methods> 
      <confirmation-method>SENDER-VOUCHES-UNSIGNED</confirmation-method> 
   </subject-confirmation-methods> 
</verify-saml-token>  
<signature>
   <verify-timestamp expiry="28800" created="true" />  
</signature>

9.12.10.2 Oracle WSM 11g

Perform the following steps:

1. Configure the application server for SSL.

2. Attach policies as follows:

   Client: oracle/wss_saml_token_over_ssl_client_policy.

   Web service: oracle/wss_saml_token_over_ssl_service_policy.

9.12.11.1 OC4J 10g

Configure the logging and auditing interceptor.

9.12.11.2 Oracle WSM 11g

Attach the following policy to the Web service or client: oracle/log_policy.

For more information about attaching policies in Oracle Fusion Middleware 11g, see "Attaching Policies to Web Services" in Oracle Fusion Middleware Security and Administrator's Guide for Web Services.