Configuring Modeling Element Properties

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

Adding Logging and Alerts to an Element

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.

Adding Alerts to a Modeling Element

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.

To Add an Alert to a Modeling Element

1. Open the Business Process containing the element to which you want to add an alert entry.
2. In the Business Process Designer, select the element.
3. In the Business Process Designer toolbar, click Property Sheet.

   The properties for the element appear to the right of the Business Process.

4. Click in the Alert Properties field, and then click the ellipsis (...).

   The Specify Alerts dialog box appears.

5. Define the alert using the available methods.
6. When you are finished defining the alert, click OK.

Adding Logger Messages to a Modeling Element

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.

To Add a Logger Message to a Modeling Element

1. Open the Business Process containing the element to which you want to add a logger entry.
2. In the Business Process Designer, select the element.
3. In the Business Process Designer toolbar, click Property Sheet.

   The properties for the element appear to the right of the Business Process.

4. Click in the Logging Properties field, and then click the ellipsis (...).

   The Specify Log Messages dialog box appears.

5. Define the log message using the available methods.
6. When you are finished defining the log message, click OK.

Configuring Business Processes for XA Transactions

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.

Enabling XA Support for a Whole Business Process

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.

To Enable XA Transactions for a Whole Business Process

1. In the NetBeans Projects window, right-click a Business Process and then click Properties.

   The Business Process Properties window appears with the General page displayed.

2. In the Enable XA for Entire Business Process drop-down list, click Yes.
3. Click OK.
4. In the Business Process Designer toolbar, click Show Property Sheet.
5. In the Business Process Designer, click an invoke activity.
6. In the Transaction Support property of the property sheet, select Participates.
7. Repeat steps 5 and 6 for any other invoke activities in the Business Process.

   ---

   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.

   ---

Enabling XA Support for an Individual Activity

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.

To Enable a XA Transactions for an Individual Activity

1. In the Business Process Designer toolbar, click Show Property Sheet.
2. Select a receive activity, invoke activity, or pick activity (OnMessage).
3. In the Transaction Support property on the property sheet, select XA.
4. For each activity to be XA-enabled, repeat steps 2 and 3.