Search Results stop_adapter

Overview

XDP_CONTROLLER_CORE is the central PL/SQL package body within the Oracle EBS application (owner APPS, API classification OTHER) responsible for controlling the lifecycle of "adapters" and controllers used by the e-Commerce Gateway / EDI transaction infrastructure. Its core business function is to send control messages to concurrent processes (CPIDs) through the concurrent manager GSM/IPC messaging layer, allowing administrators and concurrent programs to launch, verify, suspend, resume, connect, disconnect, terminate, and stop adapter processes without manual intervention. In Oracle EBS 12.1.1 and 12.2.2, this package underpins the runtime orchestration of adapter processes attached to the Concurrent Processing framework — coordinating process state transitions via fnd_cp_gsm_ipc.Send_Custom_Message with predefined custom message constants such as pv_StartCustomMessage, pv_VerifyCustomMessage, pv_TermCustomMessage, pv_SuspCustomMessage, pv_ResuCustomMessage, pv_ConnCustomMessage, and pv_DisconnCustomMessage. This distinguishes it from the database-side adapter logic: XDP_CONTROLLER_CORE is the control plane, not the data transformation plane.

Key Procedures and Functions

Fourteen documented routines comprise the public interface. The primary lifecycle procedures — LAUNCHADAPTER, VERIFYADAPTERS, TERMINATEADAPTER, SUSPENDADAPTER, RESUMEADAPTER, CONNECTADAPTER, and DISCONNECTADAPTER — each deliver a corresponding custom message to the target CPID via fnd_cp_gsm_ipc.Send_Custom_Message. On receipt, the adapter daemon interprets the message and transitions state accordingly (start, verify health, terminate, pause, resume, open connection, close connection).

STOPADAPTER is the routine most directly associated with the user's search term "stop_adapter"; it signals one or more adapters to cease operation, typically via the private helper Stop_Impl_Adapter, which iterates the term_adapters_tab collection and honours a lock-retry flag and a configurable wait-to-kill interval returned by GetCtrlWaitToKillMins. STOPADAPTER cooperates with dbms_lock to serialize stop requests safely.

GENERICOPERATIONADAPTER provides an extensible entry point for adapter commands not covered by the fixed message set. VERIFYCONTROLLERSTATUS and NOTIFYCONTROLLERNOTRUNNING deliver controller-level diagnostics — confirming the controller is alive or alerting callers when it is absent. PERFORM_STOP_PROCESSING and PERFORM_START_PROCESSING wrap the stop/start control flow for the concurrent processing subsystem, and PROCESS_CONTROL_COMMAND dispatches an inbound control command to the appropriate handler. The private TYPE definitions (term_adapter_rec, term_adapters_tab) support batch stop processing across multiple channels.

Tables Accessed

The package body references two objects visible through APPS synonyms: DBMS_LOCK (Oracle's built-in lock management package) and PLITBLM (the PL/SQL internal table buffer/load module). DBMS_LOCK is used to acquire serialization locks before issuing stop or terminate requests, ensuring that concurrent administrators or concurrent programs do not race to control the same adapter. PLITBLM appears in the compiled dependency chain and reflects the package's use of index-by tables (associative arrays such as term_adapters_tab) whose runtime storage is managed by the PL/SQL internal table machine. No transactional application tables are read or written by this package; persistent state lives with the adapters and controller processes themselves.

Usage Notes

XDP_CONTROLLER_CORE is typically invoked from concurrent programs, from the Concurrent Managers administration screens, or from custom PL/SQL/SQL*Plus scripts that need to orchestrate EDI adapter processes. Oracle EBS forms related to e-Commerce Gateway administration and concurrent program definitions may call these routines internally; the package is also referenced by two other packages in the application database, indicating it is a shared control utility rather than a private helper. Because it calls fnd_cp_gsm_ipc.Send_Custom_Message, it requires a valid, running concurrent manager and the target CPID must be active; otherwise NOTIFYCONTROLLERNOTRUNNING or VERIFYCONTROLLERSTATUS will report failure. When investigating a "stop_adapter" event, DBAs and consultants should trace STOPADAPTER calls in combination with DBMS_LOCK wait activity and FND_CONCURRENT_REQUESTS rows for the associated CPID, since the package itself leaves no dedicated audit table.