Skip Headers
Oracle® Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter Portal, and ADF
11g Release 1 (11.1.1.6.0)

Part Number E10127-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

11 Upgrading Oracle Business Activity Monitoring Applications

This chapter provides important supplementary information upgrading Oracle SOA 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.

Refer to the following sections for information on upgrade tasks associated with Oracle Business Activity Monitoring:

11.1 Migrating Oracle BAM Users, Groups, and Other LDAP Information to 11g

In general, after upgrade of the Oracle BAM schema, any Oracle BAM 10g users will appear in the Oracle BAM Administrator as inactive if they don't exist in the Oracle Fusion Middleware 11g security provider. However, you can use Oracle BAM Administrator software to remap 10g users to new Oracle BAM 11g users.

For more information, see "Managing Oracle BAM Object Ownership," in Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite.

After upgrade, you might need to address the following for users and groups:

Further, if your Oracle BAM 10g environment takes advantage of an LDAP directory server to store your Oracle BAM user names or other Oracle BAM information, then you should make sure that the LDAP directory you were using in Oracle Application Server 10g is associated with your new Oracle Fusion Middleware 11g environment.

For more information, see Section 6.7.1, "Configuring Oracle SOA Suite 11g to Use Identity Management Components".

11.2 Verifying Oracle BAM Action Form Templates After Upgrade

After you upgrade from Oracle BAM 10g to Oracle Fusion Middleware 11g, some of the Action Form templates you created in Oracle BAM 10g may not function correctly.

As a result, after you perform the upgrade, you should review the templates and verify that they are functioning correctly.

Specifically, use the following instructions to search for typical issues that might need to be corrected after the upgrade to Oracle Fusion Middleware 11g:

See Also:

"Creating Action Form Templates" in the Oracle Fusion Middleware User's Guide for Oracle Business Activity Monitoring

  1. Open the Oracle BAM Start Page.

    See Also:

    "Starting the Oracle BAM Web Applications," in the Oracle Fusion Middleware User's Guide for Oracle Business Activity Monitoring

  2. Start Oracle BAM Architect.

  3. Select Data Objects from the menu.

  4. Expand the System folder and open the Views folder.

  5. Select the Action Form Templates data object and click Contents.

  6. Click Edit Contents.

  7. Click Edit next to the first row.

  8. Copy the contents of the FormInput column to a text editor and remove any white space following an element. (in other words replace "> " with ">").

  9. Search for the mixed case "ReportServer" and change to lower case "reportserver" to fix the links to the style sheets.

  10. Copy and paste the updated text back into the FormInput column.

  11. Repeat these steps for each entry in the FormInput column that contains data.

11.3 Upgrading Oracle BAM External Data Sources

External data sources defined in your Oracle BAM 10g environment are not upgraded to Oracle BAM 11g.

As a result, if you use external data sources in your Oracle BAM 10g environment, you must manually recreate those data sources in Oracle BAM 11g. This is because Oracle Fusion Middleware 11g supports a new set of database drivers, which are used to connect to an external database.

To configure external data sources for Oracle BAM 11g, refer to "Creating External Data Sources" in the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

11.4 Upgrading Images in Oracle BAM Reports

Any images you used in Oracle BAM 10g are not upgraded automatically to Oracle BAM 11g. As a result, you must manually move any of your Oracle BAM images to the Oracle BAM 11g before the images can be used in your Oracle BAM 11g reports.

11.5 Using Oracle BAM Web Services in 11g

The following sections describe how Oracle BAM Web services support in Oracle BAM 10g is affected by upgrade to Oracle Fusion Middleware 11g:

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

Note:

At the time of this document was published, the latest patch set available for Oracle SOA Suite 10g and Oracle JDeveloper was 10g Release 3 (10.1.3.5).

However, for more information on the latest patch sets required for Oracle Fusion Middleware 11g interoperability and upgrade, refer to the Oracle Fusion Middleware 11g Release Notes available in the Oracle Fusion Middleware documentation library on the Oracle Technology Network (OTN):

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.

11.5.2 Invoking Web Services from Oracle BAM Alerts

In Oracle BAM 10g, 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.

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

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

11.6 Upgrading Oracle BAM Sensor Actions

When you open and upgrade a Oracle BPEL Process Manager 10g Release 3 (10.1.3) project in Oracle JDeveloper 11g, any Oracle BAM sensor actions are migrated automatically to 11g.

Unlike the behavior in 11g, Oracle BAM sensor actions in Oracle Fusion Middleware 11g use the Oracle BAM connection Factory JNDI (as shown in the BAM Sensor Action dialog box) to connect to Oracle BAM server. They do not use the bpel.xml file as they did in 10g Release 3 (10.1.3).The migrated Oracle BAM 11g sensor actions can be identified by the eis/bam/soap connection Factory JNDI name. The Oracle BAM connection specified in the 10g bpel.xml file is migrated to an Application Resource BAM connection with the name of Migrated1.

All connection properties are preserved "as is" except for PORTS, which are set to 9001.

Note that Oracle JDeveloper 11g cannot connect to Oracle BAM 10g Release 3 (10.1.3). When you open an application in Oracle JDeveloper 11g, it is assumed that you have already installed and upgraded to Oracle BAM 11g.

Similarly, the Oracle BPEL Process Manager 11g runtime cannot connect to Oracle BAM 10g Release 3 (10.1.3).

11.7 Upgrading Enterprise Link Plans to Oracle BAM 11g

Enterprise Link for Oracle Business Activity Monitoring 10g is no longer available in Oracle BAM 11g. Instead, Oracle BAM 11g supports integration with Oracle Data Integrator (ODI), which replaces Enterprise Link.

When you upgrade to Oracle BAM 11g, you have the following options, depending on how you use Enterprise Link in Oracle BAM 10g:

11.8 Additional Considerations When Upgrading to Oracle BAM 11g

The following sections describe additional information to consider when upgrading to Oracle BAM 11g:

11.8.1 Using Oracle BAM Alert Actions After Upgrade

Some Oracle BAM alert actions were removed in Oracle BAM 11g, and after upgrading, any alerts using them may become invalid.

Specifically, the "Run a Plan" action was removed because Oracle BAM replaced Enterprise Link with Oracle Data Integrator, which uses the "Run an ODI Scenario" alert action.

For more information, see Section 11.7, "Upgrading Enterprise Link Plans to Oracle BAM 11g".

11.8.2 Recreating Oracle BAM Enterprise Message Sources After Upgrade

Enterprise Message Sources have changed from Oracle BAM 10g to Oracle BAM 11g. As a result, you must recreate any Enterprise Message Sources after you upgrade to Oracle Fusion Middleware 11g.

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