1 Introducing Oracle Infrastructure Web Services

SOA service components

SOA composite applications include SOA service components. SOA service components are the basic building blocks of SOA applications, implementing a part of the overall business logic functionality.

The following SOA service components can be managed using Oracle WSM:

• BPEL Process—Provides process orchestration and storage of synchronous and asynchronous processes.

• Oracle Mediator—Routes events (messages) between different components.

• Human Workflow—Enables you to model a workflow that describes the tasks for users or groups to perform as part of an end-to-end business process flow.

• Business Rules—Design a business decision based on rules.

For more information about developing SOA service components, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

You can deploy SOA service components to the Oracle Fusion Middleware environment.

SOA service binding components

SOA Service binding components provide the outside world with an entry point to the SOA composite application. The WSDL file of the service advertises its capabilities to external applications. These capabilities are used for contacting the SOA composite application components. For more information, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

ADF Business Components

ADF Business Components simplify the development, delivery, and customization of business applications for the Java EE platform by providing a library of reusable components and supporting design time facilities in Oracle JDeveloper. You can use an ADF Business Component if you implement the Web service as an application module.

Using ADF Business Components, developers are not required to write the application infrastructure code required by the typical Java EE application to perform the following tasks:

• Connect to the database.

• Retrieve data.

• Lock database records.

• Manage transactions.

Additionally, you can use Oracle JDeveloper facilities to expose Business Components that encapsulate related business functions as Web services so that they can be consumed across modules of the deploy Fusion Web application.

For more information about developing ADF Business Components, see Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

WebCenter services

WebCenter services expose Web 2.0 technologies for social networking and personal productivity, such as Wiki, RSS, and blogs. WebCenter provides a set of features and services (for example, portlets, customization, and content integration) that you can selectively add to your application. For more information about developing WebCenter services, see Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

SOA reference binding components

SOA reference binding components connect the SOA composite application to external partners. For more information about developing SOA reference binding components, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

ADF Web applications

ADF Web applications can invoke a service, such as a WebLogic Web service, a SOA composite application, or an ADF Business Component, using a Web service data control or Web service proxy. For more information, see "Integrating Web Services into a Fusion Web Application" in Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

WebCenter portlets

WebCenter portlets enable you to surface WebCenter services. For more information about developing WebCenter portlets, see Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

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

• Web Services Description Language (WSDL) 1.1 and 2.0—XML-based specification that describes a Web service. For more information, see Web Services Description Language (WSDL) at http://www.w3.org/TR/wsdl.

• Web Services Policy Framework (WS-Policy) 1.2—General purpose model and corresponding syntax to describe and communicate the policies of a Web service. For more information, see: WS-Policy 1.2 Framework (Member Submission): http://www.w3.org/Submission/WS-Policy

• Web Services Policy Attachment (WS-PolicyAttachment) 1.5 and 1.2—Abstract model and an XML-based expression grammar for policies. For more information, see:

  WS-Policy Attachment 1.5 (Recommendation): http://www.w3.org/TR/ws-policy-attach/

  WS-PolicyAttachment 1.2 (Member Submission): http://www.w3.org/Submission/WS-PolicyAttachment

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/.

Security

• Web Services Security (WS-Security) 1.0 and 1.1—Standard set of SOAP [SOAP11, SOAP12] extensions that can be used when building secure Web services to implement message content integrity and confidentiality. For more information, see OASIS Web Service Security Web page at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss.

• Web Services Security Policy (WS-SecurityPolicy) 1.2—Set of security policy assertions for use with the WS-Policy framework. For more information, see Web Services Security Policy (WS-SecurityPolicy) specification at http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/ws-securitypolicy-1.2-spec-os.html.

• Security Assertion Markup Language (SAML) 2.0—XML standard for exchanging authentication and authorization data between security domains. For more information, see the Security Assertion Markup Language (SAML) specification at http://docs.oasis-open.org/security/saml/v2.0/.

• Security Assertion Markup Language (SAML) Token Profile 1.1—Set of SOAP extensions that implement SOAP message authentication and encryption. For more information, see the Security Assertion Markup Language (SAML) Token Profile 1.1 specification at http://www.oasis-open.org/committees/download.php/16768/wss-v1.1-spec-os-SAMLTokenProfile.pdf.

• XML Signature—Defines an XML syntax for digital signatures. For more information, see XML Signature Syntax and Processing at http://www.w3.org/TR/xmldsig-core/.

• XML Encryption—Defines how to encrypt the contents of an XML element. For more information, see XML Encryption Syntax and Processing at http://www.w3.org/TR/xmlenc-core/.

Reliable communication

• Web Services Addressing (WS-Addressing) 1.0—Transport-neutral mechanisms to address Web services and messages. For more information, see Web Services Addressing (WS-Addressing) specification at http://www.w3.org/TR/ws-addr-core.

• Web Services Reliable Messaging (WS-ReliableMessaging) 1.0 and 1.1—Implementation that enables two Web services running on different WebLogic Server instances to communicate reliably in the presence of failures in software components, systems, or networks. For more information, see:

  Web Services Reliable Messaging (WS-ReliableMessaging) 1.1 specification at http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-spec-os-01.pdf.

  Web Services Reliable Messaging (WS-ReliableMessaging) 1.0 specification at http://specs.xmlsoap.org/ws/2005/02/rm/ws-reliablemessaging.pdf.

• Web Services Reliable Messaging Policy (WS-ReliableMessaging Policy) 1.1—Domain-specific policy assertion for reliable messaging for use with WS-Policy and WS-ReliableMessaging. For more information, see Web Services Reliable Messaging Policy (WS-ReliableMessaging Policy) specification at http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.1-spec-os-01.pdf

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.