Results for “end_response”

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

Overview

SYS.UTL_HTTP is the Oracle-supplied PL/SQL package body that provides the database's native HTTP client functionality. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, this package enables PL/SQL code executing inside the database to construct and transmit HTTP requests to external or internal web servers, and to consume the corresponding responses. It is the foundational transport layer that allows EBS components — most notably Oracle Payments, EDI processing, and various integration touchpoints — to interoperate with remote applications, payment gateways, tax engines, and third-party web services without requiring middleware or a dedicated application-tier agent.

The documented object resides in the SYS schema, is marked VALID, and is classified as an OTHER API within the ETRM (E-Business Suite Technical Reference Manual) metadata. It is a foundational library rather than an EBS business API; EBS applications consume it indirectly through standard PL/SQL callouts and through dependent packages such as those in the Payments and integration stacks.

Key Procedures and Functions

The ETRM metadata documents 61 procedures and functions for UTL_HTTP. These fall into four functional groupings:

• Request construction and lifecycle: procedures such as CREATE_REQUEST_CONTEXT and DESTROY_REQUEST_CONTEXT manage the memory context in which a request/response exchange operates, while the well-known BEGIN_REQUEST, WRITE_TEXT, WRITE_RAW, WRITE_LINE, and END_RESPONSE routines build and dispatch the outbound message.
• Connection and proxy configuration: SET_PROXY and GET_PROXY control the proxy server used for outbound calls; SET_COOKIE_SUPPORT and GET_COOKIE_SUPPORT enable or disable cookie persistence across requests.
• Redirect and transport behaviour: SET_FOLLOW_REDIRECT and GET_FOLLOW_REDIRECT govern whether the client automatically follows HTTP 3xx redirects; SET_PERSISTENT_CONN_SUPPORT and GET_PERSISTENT_CONN_SUPPORT control HTTP keep-alive connections; SET_TRANSFER_TIMEOUT and GET_TRANSFER_TIMEOUT set the socket read/write timeout.
• Error handling and security: SET_RESPONSE_ERROR_CHECK and GET_RESPONSE_ERROR_CHECK determine whether non-2xx responses raise exceptions; SET_DETAILED_EXCP_SUPPORT and GET_DETAILED_EXCP_SUPPORT control exception verbosity; SET_WALLET configures an Oracle Wallet for HTTPS/SSL authentication; SET_BODY_CHARSET and GET_BODY_CHARSET manage character-set conversion of message bodies.

Response consumption is handled by GET_RESPONSE, READ_TEXT, READ_RAW, and READ_LINE, which retrieve status codes, headers, and body content from the remote server. The document references an internal helper package, UTL_HTT_LIB, which backs much of the actual socket handling.

Tables Accessed

The ETRM documentation lists no tables accessed via APPS synonyms for this package. This is consistent with its role: UTL_HTTP is a stateless network transport utility and does not read or write database tables directly. Any persistence of request or response payloads is performed by the calling EBS packages, not by UTL_HTTP itself. Configuration state, such as proxy settings and wallet locations, is held in session memory rather than in schema objects.

Usage Notes

SYS.UTL_HTTP is referenced by 11 documented EBS packages according to the ETRM metadata, confirming its role as a shared infrastructure dependency. Typical invocation scenarios include:

• Oracle Payments callouts: transmitting payment authorization and settlement messages to bank or gateway endpoints.
• Integration and web services: custom PL/SQL that consumes REST or SOAP endpoints to exchange data with external systems.
• Tax and address validation: invoking third-party tax determination or address-verification services during order and invoice processing.
• Concurrent programs and custom code: scheduled or ad-hoc programs that synchronize data with remote servers.

Because it is a SYS-owned package, direct execution privileges should be granted sparingly and through controlled roles. The package's dependencies — STANDARD, PLITBLM, UTL_RAW, and UTL_HTT_LIB — are all built-in components, and the absence of any dependent database objects indicates the package is a provider rather than a consumer in the dependency graph. When network access is required in an EBS environment, UTL_HTTP remains the canonical, supported mechanism for outbound HTTP communication from the database tier.