Results for “release_call”

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

Overview

SYS.UTL_DBWS is the Oracle-supplied PL/SQL package body that provides Database Web Services, a server-side API allowing PL/SQL code to invoke external SOAP-based web services directly from the database. The package implements a dynamic invocation framework: rather than generating static client stubs, it resolves a Web Services Description Language (WSDL) document at runtime, exposes the available ports and operations through introspection, and constructs calls on demand. Within Oracle E-Business Suite 12.1.1 and 12.2.2, this capability underpins integrations that must communicate with third-party or middleware endpoints — tax calculation engines, payment gateways, address validation services, and other external SOAP providers — without requiring an application-tier Java adapter.

The ETRM metadata record lists the object as VALID and owned by SYS. Its declared dependencies are limited to core server types and utilities: ANYDATA, XMLTYPE, PLITBLM, STANDARD, and URITYPE. Notably, UTL_DBWS is not referenced by any other database object, confirming that it is a self-contained utility package intended for direct invocation by custom PL/SQL rather than an internal dependency of other EBS code.

Key Procedures and Functions

The ETRM documentation records 26 procedures and functions. Principal entries include:

• CREATE_SERVICE — Instantiates a service handle from a WSDL document, establishing the logical connection used by subsequent calls.
• GET_PORTS / GET_OPERATIONS — Introspection routines that enumerate the ports exposed by a service and the operations available on a given port.
• CREATE_CALL — Creates a call handle for a specific operation, serving as the container for parameter binding and invocation.
• SET_TARGET_ENDPOINT_ADDRESS — Overrides the endpoint address resolved from the WSDL, permitting redirection to alternate environments.
• GET_PROPERTY / SET_PROPERTY / REMOVE_PROPERTY — Manage call-level properties controlling runtime behavior such as timeouts and HTTP characteristics.
• SET_HTTP_PROXY — Configures proxy settings for outbound HTTP transport.
• GET_RETURN_TYPE / GET_IN_PARAMETER_TYPES / GET_OUT_PARAMETER_TYPES — Metadata accessors used to determine an operation's signature before binding values.
• INVOKE — Executes the web service call and returns the response.
• GET_OUTPUT_VALUES — Extracts output and return values from a completed invocation.
• TO_QNAME / GET_NAMESPACE_URI / GET_LOCAL_PART — Qualified-name utility functions used when constructing or parsing XML Schema qualified names.
• RELEASE_CALL / RELEASE_SERVICE / RELEASE_ALL_SERVICES — Release the handles and associated resources, releasing memory held by open services and calls.

Tables Accessed

No application tables are referenced through APPS synonyms, and the ETRM record documents no table dependencies. UTL_DBWS operates entirely on in-memory handles and XML structures, with persistence limited to the WSDL and SOAP documents processed via XMLTYPE and ANYDATA. Service definitions may be stored in database tables or retrieved from a URL through URITYPE, but such storage is determined by the calling code, not by the package itself.

Usage Notes

UTL_DBWS is invoked from custom PL/SQL — including concurrent program logic, database triggers, and API extensions — rather than from standard EBS forms, which rely on the application-tier framework for web service consumption. Typical usage follows the sequence: create a service, optionally create a call, bind parameters, invoke, read outputs, then release handles to avoid resource leakage. EXECUTE privilege must be granted explicitly, as PUBLIC access is not assumed. Because outbound network access is required, the database must be able to reach the endpoint, and ACL or proxy configuration may be necessary. All handles should be released deterministically; long-lived sessions that omit RELEASE_CALL and RELEASE_SERVICE risk accumulating open resources.