Service Integration 3-3
payload as one of its parts—typically the first part or the one identified by the top-level content-type header.
■
Messaging services : Messaging services are those that can receive messages of one
data type and respond with messages of a different data type. Supported data types include XML, Message Format Language MFL, text, untyped, binary and
attachments where interface is not described by WSDL.
Oracle Service Bus supports request and response as well as one-way paradigms, for both the HTTP and the JMS asynchronous transport protocols. If the underlying
transport supports ordered delivery of messages, Oracle Service Bus also extends the same support.
3.1.3 Transport Protocols
Oracle Service Bus supports the following service transport protocols:
■
EJBRMI
■
E-mail POPSMTPIMAP
■
File
■
SFTP
■
HTTPS
■
JCA
■
JEJB
■
JMS including MQ using JMS, and JMSXA
■
Local Oracle Proprietary for inter-ESB communication
■
MQ WebSphere MQ
■
SB RMI support
■
SOA-DIRECT Oracle SOA Suite
■
Tuxedo Oracle Tuxedo
■
WS WSRM, Web Services Reliable Messaging The service type selected defines the protocol to be used for communicating with the
service end point. The following table shows the service types and supported transports:
Service Type Transport Protocols
SOAP WSDL or XMLnic HTTPS, JCA, JMS, Local, SB, SOA-DIRECT, WS
JMS request and JMS response are not supported if WS-Security is enabled.
SOAP no WSDL HTTPS, JMS, Local, SB
JMS request and JMS response are not supported if WS-Security is enabled.
Transport Typed EJB, Flow Split-Join, JEJB
XML no WSDL Email, File, FTP, HTTPS, JMS, Local, MQ, SB, SFTP, Tuxedo
HTTP GET is only supported for XML with no WSDL. Messaging Type Binary,
Text, MFL, XML Email, File, FTP, HTTPS, JMS, Local, MQ, SFTP, Tuxedo
3-4 Oracle Fusion Middleware Concepts and Architecture for Oracle Service Bus
Oracle Service Bus also provides a Transport SDK to enable addition of native custom connectivity options.
For information on how to configure transport for a proxy service using the Oracle Service Bus Administration Console, see Proxy Services: Creating and Managing in
the Oracle Fusion Middleware Administrators Guide for Oracle Service Bus.
For information on how to configure transport for a business service using the Oracle Service Bus Administration Console, see Business Services: Creating and Managing
in the Oracle Fusion Middleware Administrators Guide for Oracle Service Bus.
3.1.4 Service Interfaces
Oracle Service Bus relies on WSDLs for the formal description of Web services. For Web services, a WSDL describes what the Web Services interface is, where it resides,
and how to invoke it. Oracle Service Bus defines proxy services and business services in terms of two WSDL entities:
■
The abstract WSDL interface, which defines the operations in that interface and the types of message parts in the operation signature
■
The binding WSDL interface, which defines the binding of the message parts to the message packaging, and the binding of the message to the transport
WSDLs can be imported into the WSDL repository using the Oracle Service Bus Administration Console. The Oracle Service Bus Administration Console can also be
used to resolve the references in the WSDLs, to ensure all schemas and WSDLs are linked correctly. After WSDLs are stored in the repository, they are available for use
when adding proxy services and business services. Oracle Service Bus uses its own representation of the interface for messaging services.
For information on how to import and resolve WSDLs using the Oracle Service Bus Administration Console, see Adding WSDLs in the Oracle Fusion Middleware
Administrators Guide for Oracle Service Bus.
3.1.5 Messaging Models
