Search Results java_engine_running

Overview

QP_JAVA_ENGINE_UTIL_PUB is a public PL/SQL utility package in the Oracle E-Business Suite Advanced Pricing module (QP) that provides the PL/SQL-side interface to the Oracle Pricing Java Engine. The Java Engine is a servlet-based pricing calculation component that runs outside the database tier and is invoked by EBS pricing flows when native PL/SQL pricing is either unavailable or configured to be bypassed. This package encapsulates the discovery, connectivity, session-context propagation, and request/response mechanics required to communicate with that external engine over HTTP.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the package owner. Its header (QPXJUTLS.pls, version 120.1) defines a substantial set of global constants used to construct the parameter string passed to the servlet, including keys such as dbc, UserId, RespId, RespApplId, LoginId, OrgId, AppShortName, CallType, Action, IcxSessionId, StatusCode, StatusText, Details, and DebugFlag. It also defines transfer timeout and maximum status-polling constants, the latter driven by the profile options QP_JPE_MAX_STAT_REQUESTS and QP_JPE_STAT_REQUEST_INTERVAL, added specifically to handle HTTP timeout conditions. The parameter string is delimited using the package constants G_HARD_CHAR ('&') and G_PATN_SEPERATOR ('|').

Key Procedures and Functions

• JAVA_ENGINE_INSTALLED — Returns a flag indicating whether the Java Engine has been installed and configured for the environment ('Y' if installed, 'N' if not).
• JAVA_ENGINE_RUNNING — Returns a flag indicating whether the Java Engine is currently running and reachable ('Y' if running, 'N' if not). This is the function most commonly associated with the search term "java_engine_running" and is the standard diagnostic entry point for determining whether the servlet tier is responsive.
• GET_ENGINE_URL — Returns the URL of the servlet where the Java Engine is deployed, providing the target endpoint used by the send procedures.
• SEND_JAVA_ENGINE_REQUEST — Accepts a URL parameter string and returns a status plus status text, transmitting the constructed request to the Java Engine. This is the primary orchestration procedure for engine calls.
• SEND_JAVA_REQUEST — A supporting procedure that performs the underlying HTTP request transmission to the target URL.

Tables Accessed

The package does not read or write to conventional EBS application tables. Its documented dependencies are database-supplied packages accessed through APPS synonyms: UTL_HTTP for outbound HTTP communication with the servlet, UTL_TCP for lower-level network transmission, DBMS_LOCK (used together with the G_QP_INT_TABLES_LOCK constant) for serialization of concurrent pricing activity, DBMS_UTILITY for general utilities, and PLITBLM for PL/SQL table manipulation. Profile option values for status polling are read via FND_PROFILE.

Usage Notes

QP_JAVA_ENGINE_UTIL_PUB is referenced by 26 other packages, indicating it functions as shared infrastructure rather than a directly user-invoked API. It is called from pricing flows that route calculations to the Java Engine, and JAVA_ENGINE_RUNNING and JAVA_ENGINE_INSTALLED are frequently used in diagnostics and preflight checks to confirm engine availability before a pricing request is attempted. When the returned status indicates failure or timeout, the StatusText and Details parameters carry the diagnostic payload. Because of the AUTHID CURRENT_USER declaration, any custom code invoking this package must be executed from a context with appropriate network and execute privileges. Customizations should call only the documented public procedures and avoid reliance on the internal global constants, which are implementation details subject to change.