Previous	Next		Contents	Index	Glossary

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. The Propagations for Local Outbound Agents region displays a list of the combinations of local outbound agents and database links that may require propagations. This list matches each of your local outbound agents with each database link to a remote system that appears in the addresses of the inbound agents you have defined. Each local outbound agent is also listed with a Local destination in the Database Link column for propagation to inbound agents on the local system. See: Agents

Locate the outbound agent and database link combination for which you want to schedule a propagation.

4. If no propagation is scheduled yet for the agent and database link you want, choose the Create link in the Schedule column to schedule the propagation. The Edit Propagation page appears, displaying the name of the outbound agent's queue, as well as the database link name for a remote destination or Local System for a local destination.

5. In the Duration field, enter the duration of the propagation window, in seconds.

6. In the Run Every field, enter an interval in seconds to specify how often you want a propagation window to occur.

Note: The run interval must be longer than the duration of the propagation window.

7. In the Latency field, enter a latency time in seconds to specify how long you want to wait, after all messages have been propagated, before rechecking the queue for new messages to the destination.

The latency represents the maximum wait time during the propagation window for a message to be propagated after it is enqueued. To propagate messages as soon as possible after they are enqueued, enter a latency of zero. The default latency is 60 seconds.

Note: To enable AQ to enforce the latency time, the job queue interval setting in your database initialization parameters must be less than or equal to the latency value. See: Checking the Business Event System Setup.

8. Choose the Submit button to save the propagation schedule and return to the Check Setup page. You can also choose the Cancel button to return to the Check Setup page without saving the propagation.

Copyright © 2002 Oracle Corporation.
All Rights Reserved.