1 Introduction to Oracle Infrastructure Web Services

An introduction of Oracle Infrastructure web services, description of concepts for developing Oracle Infrastructure web services, and an overview of supported standards and related documentation is described in this chapter.

For definitions of unfamiliar terms found in this and other books, see the Glossary.

1.1 Overview of Oracle Infrastructure Web Services

In Oracle Fusion Middleware 12c, there are two categories of web services to support the development, security, and administration of the following types of web services:

  • Oracle Infrastructure web services—SOA, Application Development Framework (ADF), Oracle Service Bus, and Oracle Enterprise Scheduler services

  • Java EE web services—SOAP (JAX-WS) and RESTful (JAX-RS) web services

For more information about the web service and client types, see "Overview of Web Services in Oracle Fusion Middleware 12c" in Understanding Web Services.

For more information about Java EE web services, see Overview of WebLogic Web ServicesUnderstanding WebLogic Web Services for Oracle WebLogic Server.

1.2 Supported Standards for Developing Oracle Infrastructure Web Services

Oracle considers interoperability of web services platforms to be more important than providing support for all possible edge cases of the web services specifications.

The following table summarizes the Oracle Infrastructure web service specifications that are part of the Oracle implementation, organized by high-level feature.

Oracle complies with the following specifications from the Web Services Interoperability Organization and considers them to be the baseline for web services interoperability:


For more information about Oracle Infrastructure web service security standards, see "Web Services Security Standards" in Understanding Oracle Web Services Manager.

Table 1-1 Specifications Supported by Oracle Infrastructure Web Services

Feature Specification

Programming model (based on metadata annotations) and runtime architecture

Web Services Metadata Exchange (WS-MetadataExchange) 1.1—Part of the WS-Federation roadmap which allows retrieval of metadata about a web service endpoint. For more information, see Web Services Metadata Exchange (WS-MetadataExchange) specification at http://xml.coverpages.org/WS-MetadataExchange.pdf.

Web service description

Data exchange between web service and requesting client

  • Simple Object Access Protocol (SOAP) 1.1 and 1.2—Lightweight XML-based protocol used to exchange information in a decentralized, distributed environment. For more information, see Simple Object Access Protocol (SOAP) at http://www.w3.org/TR/SOAP

  • SOAP with Attachments API for Java (SAAJ) 1.3—Implementation that developers can use to produce and consume messages conforming to the SOAP 1.1 specification and SOAP with Attachments notes. For more information, see the SOAP with Attachments API for Java (SAAJ) specification at https://saaj.dev.java.net

  • Message Transmission Optimization Mechanism (MTOM) you can specify that a web service use a streaming API when reading inbound SOAP messages that include attachments, rather than the default behavior in which the service reads the entire message into memory. For more information, see SOAP Message Transmission Optimization Mechanism specification at http://www.w3.org/TR/soap12-mtom/


Reliable communication

Atomic transactions

Web Services Atomic Transaction—Defines the Atomic Transaction coordination type that is to be used with the extensible coordination framework described in the Web Services Coordination specification. The WS-AtomicTransaction and WS-Coordination specifications define an extensible framework for coordinating distributed activities among a set of participants. For more information, see:

Optimizing XML transmission

  • Fast Infoset—Compressed binary encoding format that provides a more efficient serialization than the text-based XML format. Fast Infoset optimizes both document size and processing performance.The Fast Infoset specification, ITU-T Rec. X.891 and ISO/IEC 24824-1 (Fast Infoset) is defined by both the ITU-T and ISO standards bodies. The specification can be downloaded from the ITU Web site: http://www.itu.int/rec/T-REC-X.891-200505-I/en

  • Message Transmission Optimization Mechanism (MTOM)—Defines a method for optimizing the transmission of XML data of type xs:base64Binary or xs:hexBinary in SOAP messages.

Advertisement (registration and discovery)

  • Universal Description, Discovery, and Integration (UDDI) 2.0—Standard for describing a web service; registering a web service in a well-known registry; and discovering other registered web services. For more information, see the Universal Description, Discovery, and Integration (UDDI) specification at http://uddi.xml.org

  • Web Services Inspection Language 1.0—Provides an XML format for assisting in the inspection of a site for available services. For more information, see Web Services Inspection Language (WS-Inspection) 1.0 specification at http://download.boulder.ibm.com/ibmdl/pub/software/dw/specs/ws-wsilspec/ws-wsilspec.pdf.

1.3 Related documents for developing Oracle Infrastructure Web Services

Oracle Infrastructure web services development is one of the two categories of web service supported by Oracle Fusion Middleware 12c.

Refer the following section for a summary of documents related to Oracle Infrastructure web services development, security, and administration: Related Documents