Search Results refresh_component

Overview

FND_SVC_COMPONENT is a server-side PL/SQL package owned by APPS that provides the control plane for Oracle E-Business Suite Service Components. Service Components are the managed background containers—generic server processes (GSM) and servlet containers—that host middleware and integration workloads such as Business Event agents, Workflow Mailer, and XML Gateway listeners. The package exposes a uniform programmatic interface for starting, stopping, suspending, resuming, and refreshing these components, for interrogating their current state, and for validating and executing operations against them. In effect it acts as the runtime administrative API behind the Oracle Application Manager (OAM) Service Component pages, translating administrative intent into status transitions on the underlying service infrastructure. It is present in both release 12.1.1 and 12.2.2; the source header dates to 2005 and the design is stable across the 12.x family.

Key Procedures and Functions

The package declares 21 documented units, with GENERIC_OPERATION, SUBMIT_REQUEST, or the specific lifecycle verbs most frequently invoked by callers.

• GENERIC_OPERATION — the generalized entry point that dispatches a requested lifecycle action for a component, allowing a single call site to perform start, stop, suspend, resume, refresh, or related operations based on the supplied operation type.
• START_COMPONENT / STOP_COMPONENT / SUSPEND_COMPONENT / RESUME_COMPONENT / REFRESH_COMPONENT — perform the corresponding state transition on a named service component, respecting the component's current status constants (STARTING, RUNNING, SUSPENDING, SUSPENDED, RESUMING, STOPPING, STOPPED, STOPPED_ERROR).
• GET_CURRENT_STATUS / GET_CONTAINER_STATUS — return the present status of a component and of its hosting container, including the container-level states RUNNING, STOPPING, and STOPPED.
• GET_OAM_ROLLED_STATUS_BY_TYPE — aggregates component statuses into the OAM status codes (Down, Warning, Up, Not Available, Not Started, Cancelled), used for dashboard display.
• RESET_CONTAINER_COMPONENTS — reinitializes the components registered to a container.
• VERIFY_CONTAINER / VERIFY_ALL_CONTAINERS — validate that a container, or all containers, is reachable and healthy.
• NAME_CONTAINER_SESSION — assigns a session name to the container connection, aiding identification in monitoring views.
• REFRESH_CONTAINER_LOG_LEVEL — reloads the container log level setting (SVC_CONTAINER_LOG_LEVEL).
• VALIDATE_OPERATION — checks whether a requested operation is legal for the component's current state, returning codes such as 7000 (other component error), 7001 (invalid component state), and 7002 (container not running).
• INSERT_PARAM_VALS / RETRIEVE_PARAMETER_VALUE — persist and read component parameter values.
• UPDATE_STATUS — writes status changes back to the component repository.
• DELETE_REQUEST / EXECUTE_REQUEST — manage the request queue that carries component operations to the executing container.

Tables Accessed

The package reads and writes the FND_SVC_COMPONENTS repository and its parameter and request satellites. FND_SVC_COMP_PARAMS_B and FND_SVC_COMP_PARAM_VALS (with sequence FND_SVC_COMP_PARAM_VALS_S) hold parameter definitions and values. FND_SVC_COMP_REQUESTS, with history tables FND_SVC_COMP_REQUESTS_H and FND_SVC_COMP_REQUESTS_H_S, track operational requests and their audit trail. FND_CONCURRENT_QUEUES links components to concurrent managers. Supporting objects include WF_PARAMETER_LIST_T for parameter list handling, DBMS_APPLICATION_INFO for session context, DBMS_JOB for scheduling, GV$SESSION and DUAL for runtime inspection.

Usage Notes

FND_SVC_COMPONENT is invoked primarily from the Oracle Application Manager administrative interface and from concurrent programs that manage service components, rather than from end-user forms. Custom code should call GENERIC_OPERATION or the individual lifecycle procedures instead of updating FND_SVC_COMPONENTS directly, because the package enforces state validation and request queuing. Error handling should test for the documented return codes 7000–7002. The package is also referenced by two other packages, indicating internal reuse; any extension should preserve the OAM status constants and the SVC_CONTAINER_LOG_LEVEL key, which are deliberately synchronized with external Java classes.