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
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
Enabling XA Support for a Whole Business Process
Enabling XA Support for an Individual Activity
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 characteristics and components are automatically defined for you as you build a Business Process. Once you have all your modeling elements in place, view the properties of the Business Process to be sure it is configured correctly.
Perform any of the following functions to modify the configuration of a Business Process.
The General page is the first page you see when you begin to edit Business Process properties. You can change the Business Process name, edit the target namespace, select the persistence state, and so on.
The Business Process Properties window appears with the General page displayed.
Business Process attributes, also known as containers, are data values used by a Business Process. They allow you to share data between activities in a Business Process and to move data to and from the components that implement those activities. For example, a Business Process attribute could store information such as customer names, addresses, order quantities, or item descriptions. Complex structures such as OTDs and Collaborations are represented automatically in the NetBeans Projects window and are available for use in your Business Process.
Business Process attributes are used to pass values between the Business Process and external sources. Business Process attributes can also be assigned to specific activities. For example, the customer name is passed to an order process from the originating source. The customer name may be used by several of the activities in the Business Process and is included in the Business Process output.
BPM can pass all or part of a complex structure or it can even assemble a composite input to a component or web service from multiple Business Process attributes.
Attributes are automatically created for a Business Process as you add components to the process. You can create additional attributes to use in the Business Process.
The New Business Process Attribute dialog box appears.
|
Once you add a Business Process attribute, or one is added automatically, you can modify the attribute. If you only change the name of the attribute, you can specify that the rest of the Business Process be updated to reflect the change.
Note - To avoid this message in the future, select Don’t ask me again. The option you selected above will always be the default option.
Once you add a Business Process attribute, or one is added for you, you can delete the attribute. Business Process attributes that are in use cannot be deleted. Attributes that are not in use can cause validation warnings, but typically will not stop the Business Process from running.
A partner is an abstracted identification for an external system that is linked with the Business Process in the Connectivity Map. Multiple activities can use the same external system, meaning multiple activities can have the same partner. By default, BPM assigns this identification to speed up and automate model development.
If you are invoking multiple components such as web services, JMS messages, or connectors such as Adapters, you must create unique partner names for those components. Then, when you create the Connectivity Map, there will be a unique partner for each component rather than just one partner for multiple components. This enables you to successfully associate those components in your Deployment Profile and deploy your Project.
When creating a Business Process that will be used as a sub-process, you need to create a partner and associate it with the receive or receive and reply pair.
Some partners are created for you automatically, but you can add new partners to use in your Business Processes as needed. Partners are associated with the activities in a Business Process. After you create a partner, associate it with an activity as described in Associating a Partner with an Activity.
The partner is added to the partner list.
Once you add a Business Process partner, or one is added for you, you can modify the partner name. When you change the name of a partner, you can specify that the rest of the Business Process be updated to reflect the change.
The Confirm Refactoring dialog appears.
Note - To avoid this message in the future, select Don’t Ask Me Again. The option you selected above will always be the default option.
If you are not using a defined partner in the Business Process, you can delete the partner. Keeping partners that are not in use can result in validation warnings, which typically do not prevent the Business Process from running. You can only delete a partner that is not in use.
The partner is removed from the partner list.
Once you create a partner, you can associate it with an activity in the Business Process using the activity’s property sheet. You must create and select a partner for the receive and reply activities in a sub-process.
The activity’s property sheet appears.
BPM provides the means for matching existing Business Process instances to messages that are arriving into a Business Process. Correlation keys are individual data values contained within both the incoming message and the BPM engine. When an arriving message contains a value that matches a configured correlation key, the unique Business Process instance associated with that value continues processing to the next step of the Business Process. You can perform the following tasks to define message correlation.
For an example of using message correlation, see Linking and Sequencing With Message Correlation.
A correlation key is a value that you can define in a Business Process, like a purchase order number, that provides a way to associate and route information about specific Business Process instances. For asynchronous message exchange between components, you must implement correlation of the instance identification. An example of when you use asynchronous message exchanges is when you create a receive activity in the middle of a Business Process.
The New Correlation Key dialog box appears.
Note - The value for the Type field is automatically populated.
Once you create a correlation key, or one is created for you, you can modify the key by adding or removing message types.
Once you create a correlation key, or one is created for you, you can delete the key if it is no longer used. Some correlation keys cannot be removed.
Correlation sets are groups of properties (correlation keys) shared by all messages in the group. A correlation set matches messages and conversations with a Business Process instance. For example, you might want to assign a purchase order number and an invoice number to a transaction so all information about the purchase and payment are associated.
Note - When naming correlation sets, use unique names. Duplicate correlation set names cause indexing problems in the monitoring and recovery database. Consider including the Business Process name in the correlation set name to ensure uniqueness.
The New Correlation Set dialog box appears.
Once you create a correlation set, or one is created for you, you can modify the correlation set by adding or removing correlation keys.
The Edit Correlation Set dialog box appears.
Once you create a correlation set, or one is created for you, you can delete the set if it is no longer used. Some correlation sets cannot be removed.
When you use one or more correlation sets within a Business Process, you must bind the sets to a receive activity and initialize the sets before they are used. This ensures that the correlation set is created in memory before it is used.
If you choose to initialize a set within an activity, you must either choose to use both Business Process attributes or identify which Business Process attribute to use.
The Use Correlations dialog box appears.
The Assign Correlation Set dialog box appears.
The following topics provide information about linking and sequencing:
You can impose conditions on a set of messages, process a group of messages together, or make a decision contingent upon the receipt or non-receipt of all messages of a certain type. By using BPM’s linking and sequencing capabilities, you can sort messages into separate containers and execute Business Rules on containers of messages rather than on the individual messages. A container’s link identifier (a correlation ID) differentiates containers and links the messages identified with that container.
When BPM retrieves a message, it correlates the received message to a Business Process instance. If BPM finds a correlation match, it stores the message in the container for that Business Process. Otherwise, it instantiates a new Business Process instance.
For example, a Business Process handles HL7 messages that have been broken up with a continuation pointer. The Business Process contains logic that detects this condition and defers processing the HL7 message until it has been completely reassembled. The container qualifies as “full” when all HL7 messages for the same continuation pointer have been received.
In this example, the Business Process expects to receive three course grades in order to qualify a student for further studies. The courses are Math, English, and Computer Science. Each message contains the course grade, the course type, and a correlation ID to indicate where the message belongs.
A new message arrives with a correlation ID of 101. First, BPM correlates the message to see if there is a match on the newly arrived message. Since this is the first message, there is no match and a new instance is created. The second message has a correlation ID of 101. BPM correlates the message and finds a match, so the message is forwarded to the same business instance as the first message. The third message has a Correlation ID of 102. Because there is no correlation match, the message is forwarded to a new business instance. This continues until a grade is received for each course type.
This process can continue depending on conditions you set based on count or time expiration. A sample Business Process is shown below for message correlation. The main Business Process uses a File Adapter to read a DTD-based message, unmarshal the message, and then invoke a sub-process passing in the unmarshaled message.
The sub-process receives the unmarshaled message using an event-based decision and timer events in a while loop. The while loop continues until either a specified count has been reached or the time has expired. When messages are received, they are stored in containers until the requirements are met.
The timer event sets an expiration time. If time expires, the loop condition is set to false to terminate the loop. If a message is received, the message counter is incremented and, if the maximum number of messages have been received, the loop is terminated. When processing is complete, the date is written to a file.
Web Services Description Language (WSDL) is an XML-based language used to describe business services. WSDL provides a way for individuals and other businesses to electronically access those services. WSDL files are used to invoke and operate web services. They can be used for web services on the Internet and to access and invoke remote applications and databases.
The WSDL page provides a listing of all loaded WSDL files, which represent predefined Business Process attributes for use in a Business Process. For troubleshooting purposes, the WSDL page provides a listing of all unresolved target namespaces and also provides viewing access to all loaded WSDL files.
The WSDL Viewer appears.
Note - From the WSDL Viewer, you can copy and paste WSDL code to a text file. You cannot edit code in the WSDL Viewer.
The Grid page provides a collection of formatting attributes for the Business Process Designer. The grid can help you align the components of a Business Process by providing a visual guide or automatic alignment. Grid properties can also be accessed by right-clicking inside the Business Process Designer canvas.
|