Results for “xdb_endpoint_https”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The XDB.DBMS_XDB_CONFIG package is the Oracle XML DB configuration API, owned by the XDB schema and declared with AUTHID CURRENT_USER. In an Oracle E-Business Suite 12.1.1 or 12.2.2 environment, this package governs the database-resident HTTP, HTTP2, HTTPS, and FTP listener endpoints that Oracle XML DB exposes, as well as the repository-level configuration store and the servlet, MIME, and XML extension mappings registered against the embedded web container. Although EBS itself is a Forms-and-OC4J/Jserv application tier product, the EBS database (via Oracle XML DB, a mandatory component of the 11g/12c/19c database releases certified for 12.1.1 and 12.2.2) uses this package to control the ports and protocol bindings on which XML DB services listen. The reference to http://localhost/ reflects the common diagnostic or configuration entry point into these endpoints, where a local port number is substituted to reach the XML DB HTTP listener.

Key Procedures and Functions

The package exposes a documented set of 45 procedures and functions. The port management routines include USEDPORT, which returns the protocol port numbers of all pluggable databases as an XMLTYPE value, and paired getter/setter calls for each service: GETFTPPORT and SETFTPPORT, GETHTTPPORT and SETHTTPPORT, and GETHTTPSPORT and SETHTTPSPORT. Endpoint-level configuration is handled by SETLISTENERENDPOINT and GETLISTENERENDPOINT, with the package constants XDB_ENDPOINT_HTTP, XDB_ENDPOINT_HTTP2, and XDB_ENDPOINT_HTTPS identifying the endpoint type and XDB_PROTOCOL_TCP and XDB_PROTOCOL_TCPS identifying the transport protocol. SETLISTENERLOCALACCESS restricts listener access to the local host.

Configuration store operations are provided by CFG_REFRESH, CFG_GET, and CFG_UPDATE. Repository content mappings are managed through ADDMIMEMAPPING and DELETEMIMEMAPPING, ADDXMLEXTENSION and DELETEXMLEXTENSION, and the servlet registration routines ADDSERVLETMAPPING, DELETESERVLETMAPPING, and ADDSERVLET. Constants such as XDB_SERVICE_FTP, XDB_SERVICE_HTTP, and XDB_SERVICE_HTTP2 identify services for port validation, while ON_DENY_NEXT_CUSTOM and ON_DENY_BASIC govern denial behavior for unauthenticated access.

Tables Accessed

The documented table references reached through APPS synonyms are DBMS_ASSERT, DUAL, and XMLTYPE. DBMS_ASSERT is used to validate and sanitize schema and object name inputs before they are applied to repository configuration, mitigating SQL injection in dynamic configuration statements. DUAL supports singleton SELECTs for retrieving current port and configuration values. XMLTYPE is the return and storage datatype for structured configuration data, notably the output of USEDPORT and the configuration store entries read and written by CFG_GET and CFG_UPDATE. Persistence of these settings resides in the underlying XDB dictionary and repository tables, which the package manipulates on the caller's behalf.

Usage Notes

In EBS 12.1.1 and 12.2.2 deployments, DBMS_XDB_CONFIG is typically invoked manually by a DBA or system administrator connected as a privileged user such as SYS or SYSTEM, most often to change the XML DB HTTP or HTTPS listener port when the default (commonly port 8080 or 2100) conflicts with another service, to disable or restrict listener access, or to register a servlet or MIME mapping required by an integrated component. The user search for http://localhost/ corresponds directly to verification of these endpoints after such a change: the configured port is appended or substituted to confirm the XML DB listener responds on the local host. The package is reported as referenced by zero other packages within ETRM scope, indicating it is called directly rather than through dependent PL/SQL APIs. It is not invoked by standard EBS concurrent programs or Forms, but custom concurrent programs, installation or cloning scripts, and post-patch remediation scripts may call it to normalize XML DB listener configuration across environments. Because SETLISTENERENDPOINT and the port setters alter live listener bindings, changes should be coordinated with a database restart or listener reload and validated against EBS application-tier connectivity requirements.