Search Results perform_start_processing

Overview

XDP_CONTROLLER_CORE is a core PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Diagnostics/Provisioning (XDP) infrastructure layer, which governs the lifecycle and runtime state of the diagnostic and management adapters that EBS deploys for monitoring, patching, and service-control activities. The package functions as the command-and-control hub for adapter processes: it verifies that the controller service itself is responsive, enumerates and validates the adapters registered with it, and issues operational commands such as launch, suspend, resume, connect, disconnect, stop, and terminate against individual adapters. Because these operations are long-running and asynchronous, the package also exposes entry points that the controller uses to notify callers when the controller is unavailable and to perform the internal start and stop processing that brackets command execution. Its clean VALID status and small, stable dependency footprint reflect its role as a foundational component rather than an application-level API.

Key Procedures and Functions

The package exposes fourteen documented procedures and functions, organized around three concerns.

• Controller and adapter validation: VERIFYCONTROLLERSTATUS confirms that the controller service is running and reachable. VERIFYADAPTERS checks that registered adapters are present and in an expected state.
• Adapter lifecycle management: LAUNCHADAPTER starts an adapter process; STOPADAPTER requests an orderly shutdown; TERMINATEADAPTER forces termination of an adapter that will not stop cleanly; SUSPENDADAPTER and RESUMEADAPTER pause and restart adapter activity without tearing down the process; CONNECTADAPTER and DISCONNECTADAPTER manage the adapter’s link to the controller.
• Generic and internal processing: GENERICOPERATIONADAPTER provides a generalized dispatch mechanism for adapter operations not covered by the specific verbs. PROCESS_CONTROL_COMMAND parses and routes incoming control commands. PERFORM_START_PROCESSING and PERFORM_STOP_PROCESSING carry out the setup and teardown work surrounding start and stop requests. NOTIFYCONTROLLERNOTRUNNING raises notification when the controller cannot be contacted, allowing callers to fail gracefully.

Parameter lists are not documented in the available metadata and should be confirmed against the deployed package specification before direct invocation.

Tables Accessed

No application tables are referenced. The package resolves two APPS synonyms that map to the SYS-owned packages DBMS_LOCK and PLITBLM. DBMS_LOCK supplies the locking primitives used to serialize control commands so that competing requests against the same adapter do not interleave. PLITBLM provides supporting PL/SQL infrastructure routines used internally by the package and the broader XDP stack. Because no persistent EBS tables are read or written, the package holds no application state of its own; runtime condition is maintained by the controller and adapter processes it manages.

Usage Notes

XDP_CONTROLLER_CORE is infrastructure code and is not intended for direct invocation from forms, concurrent programs, or customer extensions. It is referenced by two other packages in the XDP stack, XDP_ADAPTER and XDP_RECOVERY, and recursively by itself; XDP_ADAPTER in particular acts as the public-facing layer that most callers should use. Typical invocations originate from the Oracle Diagnostics controller and the service-control scripts that start, stop, and monitor the EBS application tier, including the recovery routines that re-establish adapter connections after a restart or an unexpected outage. Administrators most often encounter this package indirectly, through the diagnostics interface or through service-management utilities. Custom code should call the documented wrapper packages rather than XDP_CONTROLLER_CORE directly, since the control-command contract between the package and the adapter processes is internal and subject to change between releases. Any deployment that invalidates this package should be investigated promptly, as diagnostics, recovery, and adapter-based monitoring will fail while it remains invalid.