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
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
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
When the BPM Engine is configured for persistence, general information about all Business Processes running on the engine is stored in the database. You can store and monitor additional information about a Business Process by configuring it for reporting persistence. You need to configure reporting persistence for each Business Process individually; the detailed information is only stored for those processes that are configured for it. This information can be accessed from the Enterprise Manager.
When you configure a Business Process for reporting persistence, a database script is generated that creates one database table for the Business Process. This table is populated with data from attributes of the WSD Object that are simple types (such as strings, integers, and so on). Data corresponding to complex attributes is not persisted, and a Business Process must include at least one simple attribute in order to be configured for persistence.
After you create your Business Processes, perform the following steps for each Business Process you want to enable for reporting persistence.
Scripts are also provided for you to uninstall the database components created for a Business Process. for information about supported database platforms and versions, see Java CAPS 6.3 Components and Supported External Systems in Planning for Oracle Java CAPS 6.3 Installation .
Reporting persistence for a Business Process is configured in the properties of the Business Process.
A folder named Database Scripts appears under the Business Process.
In order to connect with the database to run the scripts, you need to specify the database connection information for the scripts.
|
Once you configure the database connection information, you can run the database script. This procedure creates the table required for reporting on the Business Process. The name of the table created is unique to each Business Process, and begins with the first few characters of the Business Process name followed by a series of numbers and a version number.
Note - Before you can perform this step, the monitoring and recovery database must be created and running. The BPM Engine must be configured for persistence in order for information to be stored in the Business Process table. Both of these procedures are described earlier in this chapter.
BPM provides a simple way to uninstall the database tables created by the Business Process database installation script.