Search Results get_all_dad_mappings

Overview

SYS.DBMS_EPG is the server-side PL/SQL interface to the Embedded PL/SQL Gateway (EPG), which runs inside the XML DB HTTP Server in the Oracle database. In Oracle E-Business Suite releases 12.1.1 and 12.2.2, the EPG provides the core functionality of mod_plsql — allowing a web browser to invoke PL/SQL stored procedures through an HTTP listener — without requiring the Oracle HTTP Server powered by Apache. The package is declared AUTHID CURRENT_USER and resides in the SYS schema; configuration changes through its API require the XDBADMIN role, and unauthorized modification attempts raise an "access denied" exception.

Within EBS the package is primarily an infrastructure and administration API. It defines Database Access Descriptors (DADs) that map incoming URLs to PL/SQL applications, sets global and per-DAD attributes that govern gateway behavior (including logging thresholds such as LOG_EMERG through LOG_DEBUG), and authorizes or deauthorizes DADs for use. In the context of the search term "ecc propagation" — E-Business Suite's ECC (XML publisher/reporting integration) propagation of concurrent request output — DBMS_EPG governs the HTTP-facing layer through which web-based upload and retrieval requests reach PL/SQL logic; it does not itself perform ECC data propagation, but it controls the DADs and gateway attributes upon which any HTTP-delivered EBS web service depends.

Key Procedures and Functions

The documented API comprises sixteen procedures grouped into configuration and DAD management functions.

• SET_GLOBAL_ATTRIBUTE — sets a gateway-wide configuration attribute, such as the log level.
• GET_GLOBAL_ATTRIBUTE — returns the current value of a named global attribute.
• DELETE_GLOBAL_ATTRIBUTE — removes a global attribute setting, reverting it to default behavior.
• GET_ALL_GLOBAL_ATTRIBUTES — returns the complete set of configured global attributes.
• CREATE_DAD — creates a new Database Access Descriptor.
• DROP_DAD — removes an existing DAD.
• SET_DAD_ATTRIBUTE — assigns an attribute value to a specific DAD.
• GET_DAD_ATTRIBUTE — retrieves the value of a named attribute for a DAD.
• GET_ALL_DAD_ATTRIBUTES — returns all attributes configured for a DAD.
• DELETE_DAD_ATTRIBUTE — removes an attribute from a DAD.
• MAP_DAD — maps a DAD to its database access path/URL context.
• UNMAP_DAD — removes an existing DAD mapping.
• GET_ALL_DAD_MAPPINGS — returns all current DAD mappings.
• GET_DAD_LIST — lists the DADs currently defined in the gateway.
• AUTHORIZE_DAD — grants access authorization for a DAD to a database user.
• DEAUTHORIZE_DAD — revokes previously granted DAD authorization.

Canonical exceptions are declared for invalid DAD names, missing DADs, and unknown attributes (error numbers -24240, -24231, and -24232), allowing callers to trap configuration errors precisely.

Tables Accessed

DBMS_EPG operates against the XML DB configuration repository rather than ordinary application tables. The documented references are DBMS_XDB and DBMS_XMLDOM (accessible via APPS synonyms), which underpin storage and manipulation of the gateway's DAD definitions and attribute settings. No EBS application tables — including ECC-related tables — are directly read or written by this package. Its persistent state lives in the XDB configuration and, where EBS employs the EPG, in the corresponding database access descriptor definitions used by the XML DB HTTP Server.

Usage Notes

DBMS_EPG is invoked administratively, typically from SQL*Plus or a privileged session holding the XDBADMIN role, not from EBS forms or concurrent programs. Typical EBS 12.1.1 and 12.2.2 scenarios include verifying or repairing the DAD used by browser-based EBS functionality and setting global attributes such as log level during diagnosis of HTTP-delivered PL/SQL requests. It may be referenced by custom code only in DBA/setup scripts; application packages generally do not call it at runtime. Because the package is owned by SYS and is AUTHID CURRENT_USER, changes take effect for the invoking user's privileges, and any modification performed without XDBADMIN fails with an access-denied exception. The package is referenced by zero other packages, confirming its role as a foundational, administrator-facing configuration API rather than a dependency of EBS business logic.