Results for “java_queue_handler”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WF_AGENTS is a core configuration table owned by the APPLSYS schema within the FND – Application Object Library product in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the agent definitions used by the Business Event System (WF), the Oracle EBS workflow and event infrastructure that routes business events between systems, applications, and subscribers. An agent represents a named communication endpoint — a target that can send or receive an event message — and every agent is registered in this table before it can participate in event subscriptions or workflow routing.

From a dimensional modeling perspective, the mined relationship structure classifies WF_AGENTS as hub-leaning. This is a suggestion rather than a documented constraint: WF_AGENTS behaves as a hub because it is referenced by several dependent tables (WF_AGENT_GROUPS and WF_EVENT_SUBSCRIPTIONS) but itself resolves to only a small number of parent references (WF_SYSTEMS and FND_SECURITY_GROUPS). It is not an event fact and does not accumulate transactional measures; it holds relatively static definitional metadata.

Key Information Stored

The table contains 21 documented columns. The most operationally significant are:

• GUID – The globally unique surrogate identifier for the agent and the basis of primary key WAT_PK. This is the value referenced by foreign keys elsewhere in the event system.
• NAME – The logical agent name. Together with SYSTEM_GUID it forms the business-key candidate captured in unique index WF_AGENTS_U2 (NAME, SYSTEM_GUID). A second unique index, WF_AGENTS_U1, covers (GUID, ZD_EDITION_NAME).
• SYSTEM_GUID – References WF_SYSTEMS, identifying the system on which the agent resides; a core component of agent uniqueness.
• PROTOCOL and ADDRESS – Define how and where the agent communicates (for example, queue-based or web-service delivery).
• QUEUE_HANDLER, JAVA_QUEUE_HANDLER, and QUEUE_NAME – Specify the handler technology and queue used for message delivery.
• DIRECTION – Indicates whether the agent is inbound, outbound, or bidirectional.
• TYPE and STATUS – Classify the agent and control whether it is enabled or disabled.
• DISPLAY_NAME and DESCRIPTION – User-facing labels and documentation.
• SECURITY_GROUP_ID – References FND_SECURITY_GROUPS, governing which users may access the agent definition.
• NUM_READY, NUM_WAITING, NUM_EXPIRED, NUM_UNDELIV, NUM_ERROR, NUM_PROCESS – Runtime counters reflecting message queue health and delivery backlog.
• ZD_EDITION_NAME – Editioning column supporting online patching in 12.2.x.

Common Use Cases and Queries

Administrators and developers query WF_AGENTS to audit event routing configuration, identify stalled delivery queues, and trace which subscriptions target a given agent.

To list all enabled outbound agents with their host system:

• SELECT a.NAME, a.PROTOCOL, a.DIRECTION, a.STATUS, s.NAME FROM WF_AGENTS a, WF_SYSTEMS s WHERE a.SYSTEM_GUID = s.GUID AND a.STATUS = 'ENABLED';

To find agents with delivery errors or undelivered messages:

• SELECT NAME, NUM_ERROR, NUM_UNDELIV, NUM_WAITING FROM WF_AGENTS WHERE NUM_ERROR > 0 OR NUM_UNDELIV > 0;

To locate subscriptions that use an agent as the outbound or inbound endpoint, join to WF_EVENT_SUBSCRIPTIONS on OUT_AGENT_GUID or TO_AGENT_GUID. These patterns are commonly used in event system health reports and during troubleshooting of workflow notification failures.

Related Objects

WF_AGENTS participates in a well-defined reference network:

• WF_SYSTEMS – joined via WF_AGENTS.SYSTEM_GUID; defines the system hosting the agent.
• FND_SECURITY_GROUPS – joined via SECURITY_GROUP_ID; enforces access control.
• WF_AGENT_GROUPS – references WF_AGENTS through both GROUP_GUID and MEMBER_GUID, enabling agents to be grouped for broadcast routing.
• WF_EVENT_SUBSCRIPTIONS – references WF_AGENTS through OUT_AGENT_GUID and TO_AGENT_GUID, linking subscription definitions to the agents they deliver to.

Together these objects form the primary configuration backbone of the Business Event System, with WF_AGENTS acting as the central hub for agent definitions.