Checking the Business Event System Setup (Oracle Workflow Administrator's Guide)

Oracle Workflow Administrator's Guide
Release 2.6.3
Part Number B10283-02


	Previous	Next		Contents	Index	Glossary

Checking the Business Event System Setup

If you are using the standalone version of Oracle Workflow, you can use the Check Setup web page to verify that the required parameters and components have been set up to enable message propagation for the Business Event System.

If you are using the version of Oracle Workflow embedded in Oracle Applications, you can use the Oracle Workflow Manager component of Oracle Applications Manager to verify some Business Event System setup information, such as the required database initialization parameters and the number of messages on local agents. For more information, please refer to the Oracle Applications Manager online help.

To Check the Business Event System Setup

1. Use a web browser to connect to the following URL:

 <webagent>/wf_setup.check_all

Replace <webagent> with the base URL of the web agent configured for Oracle Workflow in your Web server. See: Setting Global User Preferences.

Attention: This URL accesses a secured page, so if you have not yet logged on as valid user in the current web session, you will be prompted to do so before the page appears. You must have workflow administrator privileges to access the Event Manager web pages.

Note: You can also access the Check Setup web page from the Oracle Workflow home page. See: Accessing the Oracle Workflow Home Page.

2. The Check Setup page appears, displaying the propagation settings and components for your local system.

3. Use the Database Init.ora Parameters region to verify your settings for the database initialization parameters related to AQ. The Check Setup page displays the actual value defined for each parameter as well as the minimum recommended value for Oracle Workflow.

To modify any of these parameters when using Oracle8i Database, change the settings in the init.ora file for your database. Then you must restart your database to make the changes effective.

If you are using Oracle9i Database and higher, you can either modify the parameters in the init.ora file and restart the database, or you can use the ALTER SYSTEM statement to dynamically modify the values for AQ_TM_PROCESSES and JOB_QUEUE_PROCESSES for the duration of the instance.

AQ_TM_PROCESSES--This parameter enables the time manager process in Oracle Advanced Queuing (AQ). The time manager process is required by Oracle Workflow to monitor delay events in queues, as in the case of the Oracle Workflow standard Wait activity. The recommended number of time manager processes for Oracle Workflow is one or more.

JOB_QUEUE_INTERVAL--If you are using Oracle8i Database, specify the job queue interval to determine how frequently each SNP job queue process in your instance wakes up. Oracle Workflow requires the job queue interval to be less than or equal to the latency parameter defined for your AQ propagation schedules, to allow queues to be rechecked for messages with the specified latency. The recommended job queue interval for Oracle Workflow is five seconds.

Note: Because the JOB_QUEUE_INTERVAL parameter is desupported in Oracle9i Database, the Check Setup page does not display this parameter if you are using Oracle9i Database and higher, and you do not need to set a value for it.

JOB_QUEUE_PROCESSES--This parameter defines the number of SNP job queue processes for your instance. Oracle Workflow requires job queue processes to handle propagation of Business Event System event messages by AQ queues. You must start at least one job queue process to enable message propagation. The minimum recommended number of processes for Oracle Workflow is ten.

Note: If you want to review more detailed information about AQ processing, you can optionally use another initialization parameter, EVENT, for detailed database level tracing of issues related to AQ. Add the following line to your init.ora file:

           event = "24040 trace name context forever, level 10"

Then restart your database to make this change effective. Be aware that using this parameter may generate large trace files.

4. Use the Database Links region to verify your database links. The Check Setup page displays the name and status of each database link that is referenced in an agent's address. You should create any required database links that do not yet exist. See: Creating Database Links.

Note: Ensure that the database link names used in your agents' addresses are exactly the same as the database link names specified when the database links were created.

5. Use the Local Agents region to verify the queues that are set up for the agents defined on your local system. The Check Setup web page displays the name and direction of each agent, the name of the queue assigned to the agent, whether or not the queue has been created, how many messages on the queue have been processed and are ready to be consumed, and how many messages are still waiting to be processed. You should create any required queues that do not yet exist. See: Agents, Oracle Workflow Developer's Guide and Setting Up Queues.

6. Use the Listeners for Local Inbound Agents region to schedule listeners to receive inbound event messages. See: Scheduling Listeners for Local Inbound Agents.

7. Use the Propagations for Local Outbound Agents region to schedule propagation to send event messages. See: Scheduling Propagation for Local Outbound Agents.

Checking the Business Event System Setup

To Check the Business Event System Setup

See Also