Monitor Workflow Processes

Identified below are several Oracle Workflow Administrator windows to help monitor your Workflow processes:

Transaction-Level Trace

The trace function is performed via centralized logging through the Applications Logging Framework. Using the logging framework you can enable logging and set log levels using FND profile options. For information on logging, see the Logging chapter, Oracle E-Business Suite Maintenance Guide.

Monitor Transaction Status

Use the Event Queue Summary window to monitor the status of a transaction. Select the Agent Listener and click the View Detail icon. Once you enter the selection criteria to identify the transaction, the detail information including status and an option to view the event data in XML or text format, are presented.

Review XML Message Returned by Generate Functions

Modify the subscription for the Generate XML Document or Generate Trading Partner XML Document function and set the Action: Out Agent field to the WF_OUT. The XML data gathered by the function is directed to the WF_OUT agent.

For instructions on viewing the XML message directed to WF_OUT see: Monitor Transaction Status.

Start Agent Listeners

There is one Agent Listener per inbound agent. The agents necessary to support the integration between Oracle Workflow Business Event System and Oracle XML Gateway are shown in the following table:

Agent Name Description
ECX_INBOUND Agent for inbound messages originating from outside the enterprise for B2B integration.
ECX_TRANSACTION Agent for inbound messages originating from within the enterprise for A2A integration.
WF_OUT Agent to stage outbound messages. ECX_OUTBOUND is the agent used to stage and deliver outbound XML messages to the Trading Partner.
WF_IN Agent to receive inbound messages sent to the Oracle E-Business Suite.
WF_DEFERRED Agent for outbound messages sent in deferred mode.
WF_ERROR Agent for errors detected by Oracle Workflow Business Event System or Oracle XML Gateway.

The agents must be enabled and the seeded agent listener service components must be running.

Note: Additional agents are provided for Web services. See Web Services Setup.

Use the Workflow Administrator: Agents window to enable the required agents if necessary (the agents are enabled by default). The same window can be used to disable an agent.

Use Oracle Applications Manager to schedule and manage agent listener service components. For more information, refer to the Oracle Applications Manager online help.

Ensure that the seeded agent listener service components named Workflow Deferred Agent Listener and Workflow Error Agent Listener, provided by Oracle Workflow, are running for the WF_DEFERRED and WF_ERROR agents, respectively.

The agent listener service components ECX Inbound Agent Listener and ECX Transaction Agent Listener are seeded with a manual startup mode and therefore must be manually started. The startup mode can be changed to "Automatic" using the Oracle Applications Manager, if desired.

Place any user-defined agents in their own container.