Primary Note for Oracle XML DB Protocols: FTP HTTP HTTPS WebDAV, APEX and Native Database Web Services (Doc ID 1083991.1)

Last updated on MAY 01, 2023

Applies to:

Oracle Database Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

Details

This primary note provides information on and links for accessing the database via XDB protocol servers:

Configuring Oracle XML DB repository to use HTTP and/or secure HTTP connections (HTTPS)
Configuring FTP access to the XDB repository
Configuring anonymous XDB repository access

Configuring XDB for Database Web Services

Configuring XDB to allow access to APEX and Embedded PL/SQL Gateway (EPG)
Disabling the XDB protocol server

What is the Native Oracle XML DB Web Services feature?

The Native Oracle XML DB Web Services feature is a SOAP 1.1. compliant lightweight web services engine in which applications use the HTTP method POST to submit SOAP requests to configurable services within the database. You can configure the locations of all native Oracle XML DB Web services and WSDL (Web Services Description Language) documents using the Oracle XML DB configuration file, xdbconfig.xml. You can also configure security settings for the Web services using the same configuration file. The access to the web service is via the HTTP(S) end point covered in the sections titled "How to configure XDB to use HTTPS for my connections?" and "Which support notes speak to configuring HTTPS?".

One available service lets you issue SQL and XQuery queries and receive results as XML data. Another service provides access to all PL/SQL stored functions and procedures. You can customize the input and output document formats when you use the latter service; the WSDL is automatically generated by the native database Web services engine.

You can use the Accept-Charsets field of the input HTTP header to specify the character set of Web-service responses. If this header field is omitted, then responses are in the database character set. The language of the input document and any error responses is in the local language of the database.

Error handling for native Oracle XML DB Web services uses the SOAP framework for faults.

How to configure the database to use the Native Oracle XML DB Web Services feature?

<Note:444191.1> : How to Setup Native Oracle XML DB Web Services

How to disable the XDB protocols?

There are certain environments where due to security reasons they do not want these protocols operational.
to disable them you simply set the port numbers to zero as follows.

For more details on any of these features please review the Oracle documentation referenced at the beginning of this article.