Skip Navigation Links | |
Exit Print View | |
Configuring Oracle Java CAPS Business Processes Java CAPS Documentation |
Configuring Java CAPS Business Processes
Business Process and Element Properties Overview
Configuring Business Properties
Configuring General Properties
To Configure General Business Process Properties
Configuring Business Process Attributes
Creating a New Business Process Attribute
Editing a Business Process Attribute
Deleting a Business Process Attribute
Associating a Partner with an Activity
Binding Correlation Sets to Receive Activities
Linking and Sequencing With Message Correlation
Configuring Modeling Element Properties
Adding Logging and Alerts to an Element
Adding Alerts to a Modeling Element
Adding Logger Messages to a Modeling Element
Configuring Business Processes for XA Transactions
Persisting Reporting Data for Business Processes
Configuring a Business Process for Reporting Persistence
To Configure a Business Process for Reporting Persistence
Configuring Database Connection Information
To Configure Database Connection Information
Creating a Business Process Database Table
To Create a Business Process Database Table
Dropping a Business Process Database Table
To Drop a Business Process Database Table
Configuring BPM for the OCI Driver
System Requirements for the Oracle OCI driver
Copying the OCI Driver Library Files
Configuring the BPM Engine to use the Oracle OCI Driver
Implementing Transparent Application Failover
Many modeling element properties are automatically defined for you as you build a Business Process. Once you have all your modeling elements in place, view the property sheets for the elements to be sure they are configured correctly. The property sheets are accessed through the Show Property Sheet tool on the Business Process Designer toolbar, and the properties appear to the right of the Business Process.
Table 1 lists and describes all of the properties that appear on the properties sheet, but different types of elements have different combinations of properties. Some properties do not appear for certain elements, some properties are read-only for certain elements, and not all properties are required.
Table 1 Activity and Link Properties
|
You can initiate custom logging and alert entries from a Business Process modeling element. These entries can then be viewed in the logging and alerts pages for the Business Process in Enterprise Manager.
Java CAPS allows you to initiate alert entries from a Business Process element. You can define the following types of alerts (from most to least severe): critical, major, minor, warning, and information. The alert nodes take a Boolean data type, but you can specify that the data types be automatically converted when you define the mapping.
The properties for the element appear to the right of the Business Process.
The Specify Alerts dialog box appears.
Java CAPS allows you to initiate logging entries from a Business Process element. You specify one of the log4j log levels: FATAL, ERROR, WARN, INFO, or DEBUG. When you view the log entries in Enterprise Manager, these log levels are converted to the corresponding JDK log levels. Table 2 describes the log level mapping from most to least severe.
Table 2 log4j to Java Log Level Mapping
The logger level nodes take a Boolean data type, but you can specify that the data types be automatically converted when you define the mapping.
The properties for the element appear to the right of the Business Process.
The Specify Log Messages dialog box appears.
Distributed Transaction Processing (DTP), more commonly known as XA, is a proposed W3C standard for keeping multiple transaction system components secure during short-lived and long-lived distributed transactions. This helps to ensure the integrity of distributed transactions.
XA transactions fall into two broad categories: short-lived and long-lived. A short-lived XA transaction is simpler, quicker, and requires fewer system resources than a long-lived transaction, but it remains Atomic, Consistent, Isolated, and Durable (ACID) throughout the transaction. A long-lived XA transaction is generally more complex, more distributed, and longer-running. In BPM, short-lived XA generally applies to a whole Business Process (whole Business Process XA), and long-lived XA generally applies to an individual Business Process activity (activity-level XA).
This section provides details and procedures for enabling XA support for whole Business Process XA as well as activity-level XA using BPM. For details about getting started using XA, see http://www.w3.org.
Whole Business Process XA for a Business Process is configured from the General page of the Business Process Properties dialog box. The following procedure provides the steps for enabling whole Business Process XA.
The Business Process Properties window appears with the General page displayed.
Note - If you do not need to use persistence for other Business Processes in your Project, you do not need to enable XA for the entire Business Process.
BPM allows you to enable XA at the activity level for your Business Process. This is handled in the property sheet of any receive activity, invoke activity, or pick activity (OnMessage). The following procedure provides the steps for enabling activity-level XA.
Note - In order to enable activity-level XA, you must deploy the Business Process using persistence.