Search Results fnd_web_config




Overview
Explore in AI Chat

Overview

FND_WEB_CONFIG is a PL/SQL package body owned by the APPS schema that provides a central configuration and discovery service for Oracle E-Business Suite's web-tier connectivity and runtime environment. Its business function is to answer a recurring question throughout the EBS application stack: what are the current values of the web server, protocol, agent, and database identity attributes that the application needs in order to construct URLs, route requests, and validate that the PL/SQL environment is properly enabled? Rather than hard-coding such values in individual forms, JSP pages, or concurrent programs, callers query FND_WEB_CONFIG so that a single authoritative source supplies the data. In Oracle EBS 12.1.1 and 12.2.2 this becomes particularly relevant because the technology stack (Apache, OC4J/WebLogic, mod_plsql or the Applications Framework listeners) and the profile-driven configuration model changed between releases. The package abstracts those differences away from its consumers.

Key Procedures and Functions

The documented API exposes nine procedures/functions, each returning a discrete piece of web or environment configuration:

  • WEB_SERVER — returns the configured web server host and/or URL base used to build application links.
  • DAD — returns the Database Access Descriptor name associated with the current web request, used by mod_plsql style connectivity.
  • PROTOCOL — returns the protocol scheme (HTTP or HTTPS) in force for the current context.
  • TRAIL_SLASH — normalizes URL strings by ensuring or removing a trailing slash.
  • DATABASE_ID — returns the database instance identity, supporting environment detection and diagnostics.
  • PLSQL_AGENT — returns the PL/SQL agent configuration used by the web listener.
  • JSP_AGENT — returns the JSP agent configuration used to reach the Java/servlet tier.
  • GFM_AGENT — returns the agent configuration associated with the generic file manager/web services layer.
  • CHECK_ENABLED — verifies whether PL/SQL web access is enabled for the current configuration, guarding callers against unsupported environments.

Tables Accessed

FND_WEB_CONFIG reads configuration through the FND_ENABLED_PLSQL synonym, which records whether PL/SQL-based web access is permitted, and it consults V$INSTANCE to obtain the running database instance details used by DATABASE_ID and related checks. It also references OWA_UTIL, the Oracle Web Agent PL/SQL toolkit, for CGI-environment inspection such as retrieving the current DAD, request protocol, and server variables. FND_PROFILE is used to resolve profile option values that drive web configuration, and FND_MESSAGE supplies translatable messages for error and warning conditions. A self-reference to FND_WEB_CONFIG indicates internal recursion or helper calls within the package.

Usage Notes

The package is not referenced by any other database object according to the ETRM metadata, meaning it is invoked from outside the database schema layer — typically from the Oracle Applications Framework (OAF) pages, JSP/servlet code, the login and session-management layer, and custom PL/SQL that must generate absolute URLs or detect the runtime web topology. Because it is documented as referenced by sixty-nine other packages in the ETRM repository context, it is a widely consumed utility rather than an application-specific module. In 12.1.1 it commonly resolves values from the mod_plsql and OC4J configuration, while in 12.2.2 with the WebLogic-based architecture the same API returns values consistent with the new Fusion Middleware topology. Custom code should call these functions instead of querying profile options or CGI variables directly, and CHECK_ENABLED should be tested before relying on any web-tier value to avoid errors in environments where PL/SQL web access is disabled. Care should be taken not to modify the package body, as it is an Oracle-supplied, VALID object under the APPS schema.