Search Results verify_adapter

Overview

XDP_ADAPTER is the core PL/SQL package body in the Oracle E-Business Suite that manages the lifecycle and configuration of adapters used by the XML Publisher (formerly XML Gateway / e-Commerce Gateway) infrastructure. Adapters in this context act as integration endpoints — file-based, JMS, JDBC, or custom — that the XML Publisher engine uses to move data between the EBS application and external systems. The package encapsulates the business logic that defines which adapter types are available, how specific adapter instances are created and configured, and how they are started, stopped, monitored, and torn down at runtime.

The package is owned by APPS and classified as OTHER in the ETRM repository. It is referenced by twelve other packages, confirming its role as a foundational service layer rather than a user-facing API. Its responsibilities span both metadata administration (defining adapters) and runtime control (driving adapter state machines).

Key Procedures and Functions

XDP_ADAPTER exposes twenty-five documented procedures and functions. The most central are listed below, grouped by function.

• CREATE_ADAPTER, UPDATE_ADAPTER, DELETE_ADAPTER, DELETE_ALL_FOR_FE — Administrative entry points for defining, modifying, and removing adapter instances. DELETE_ALL_FOR_FE removes every adapter associated with a given Flow Engine (FE).
• VERIFY_ADAPTER, IS_ADAPTER_CONFIGURED — Validation routines that confirm an adapter has the required configuration (channel, connection flags, inbound requirements) before it can be used.
• START_ADAPTER, STOP_ADAPTER, SUSPEND_ADAPTER, RESUME_ADAPTER — Runtime state control. These drive the adapter through its active lifecycle, respecting the startup mode and usage code defined at creation.
• CONNECT_ADAPTER, DISCONNECT_ADAPTER, TERMINATE_ADAPTER — Manage the underlying transport or session connection independently of the start/stop state, and force full teardown via TERMINATE_ADAPTER.
• GENERIC_OPERATION — A dispatcher for operations not covered by dedicated procedures.
• CREATE_ADMIN_REQUEST, UPDATE_ADMIN_REQUEST, DELETE_ADMIN_REQUEST — Manage administrative request records, presumably to queue or audit adapter changes.
• GET_ADAPTER_EXIT_CODE — Retrieves the last exit code for an adapter, supporting error diagnosis.
• VERIFY_RUNNING_ADAPTERS — The procedure this reference is most commonly associated with. It inspects the adapter registry to confirm which adapters are currently active, returning status information used by monitoring and recovery processes.
• GET_ADAPTER_LOG_FILE_URL — Returns a URL or path to the adapter log file for diagnostic review.

Tables Accessed

The package reads and writes the following tables via APPS synonyms:

• XDP_ADAPTER_REG — The adapter registry. Holds one row per configured adapter instance, including display name, startup mode, log level, connection flags, and command-line options.
• XDP_ADAPTER_TYPES_B — The adapter type definition table. Supplies the adapter class, application mode, connection-required flag, and inbound-required flag used to validate configuration.
• XDP_FES — The Flow Engine table. Adapters are scoped to a flow engine, so this table is consulted during creation and deletion.
• FND_FILE_TEMP — Standard EBS temporary file storage, used for log or output handling.

Usage Notes

XDP_ADAPTER is invoked primarily from XML Publisher / XML Gateway forms and concurrent programs rather than being called directly by end users. The VERIFY_RUNNING_ADAPTERS routine is typically triggered by monitoring concurrent programs or system health checks to detect adapters that have stalled or failed. Custom integrations should treat the documented procedures as the supported API and avoid direct DML against XDP_ADAPTER_REG, as the package enforces cross-table consistency (channel names, adapter type flags, and flow-engine scoping) that ad-hoc modifications would bypass. Because the package is referenced by twelve other packages, changes to its behavior can propagate across the XML Publisher adapter subsystem.