Interoperability Guide

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

SALT Interoperability

This chapter discusses the following topics:

 


Web Service Client Interoperability

SALT supports most Web service client programs accessing inbound Oracle Tuxedo services.

The SALT WSDL generator ( tmwsdlgen) generates WSDL 1.1 specification compliant WSDL documents that can be published to most standard UDDI servers.

Table 1 lists certified Web service client toolkits that are interoperable with SALT.

Table 1 Certified Interoperable Web Service Client Toolkits
 
WebLogic Server
Axis for Java 2.0
.Net 3.5
ALSB 3.0
Oracle BPEL
10.1.3.1.0
9.2
10.3
SOAP 1.1
RPC/encoded
Yes
Yes
N/A
N/A
Yes
Yes
SOAP 1.1
document/literal
Yes
Yes
Yes
Yes
Yes
Yes
SOAP 1.2
RPC/encoded
N/A
N/A
N/A
N/A
N/A
N/A
SOAP 1.2
document/literal
N/A
Yes
Yes
Yes
Yes
N/A

 


Web Service Server Interoperability

SALT supports most external Web service applications that are described using WSDL 1.1 standard documents with the exceptions listed in Table 2.

Table 2 Non-Supported Web Service Descriptions by SALT
WSDL Description
Explanation
RPC/literal message style
GWWS servers support only RPC/encoded and document/literal SOAP message style for outbound services. If RPC/literal message style is defined in the external WSDL file, the converted non-native WSDF file cannot be accepted by SALT configuration compiler.
<wsdl:import>
SALT WSDL converter cannot recursively retrieve the nesting WSDL document defined using <wsdl:import>.
HTTP binding
WSDL 1.1 specification defines HTTP GET & POST binding besides SOAP binding. HTTP GET & POST binding describes the interaction between a Web browser and a Web server using simple HTTP protocols.
Although the GWWS server supports HTTP transport, only SOAP protocol compliant XML messages are supported on the wire. If a WSDL document contains a HTTP GET & POST binding, this binding is ignored by the SALT WSDL converter.
WS-Policy Attachment
The SALT WSDL converter does not support WS-Policy attachments defined in the WSDL document. If WS-Policy attachments are defined in the WSDL document, policy information is ignored by the SALT WSDL converter.
MIME binding
SALT WSDL converter does not support any message-level MIME format association.
SOAP header and headerfault messages
SALT WSDL converter does not support <soap:header> and <soap:headerfault> descriptions in the WSDL 1.1 document. All <soap:header> and <soap:headerfault> messages defined for the wsdl operation are ignored by SALT WSDL converter.
More than one SOAP Fault message
SALT WSDL converter does not support more than one fault message to be defined for a WSDL operation.

Table 3 lists certified Web service servers that are interoperable with SALT.

Table 3 Certified Interoperable Web Service Server Toolkits
 
WebLogic Server
Axis for Java 2.0
.Net 3.5
ALSB 3.0
Oracle BPEL
10.1.3.1.0
9.2
10.3
SOAP 1.1
RPC/encoded
Yes
Yes
N/A
N/A
Yes
Yes
SOAP 1.1
document/literal
Yes
Yes
Yes
Yes
Yes
Yes
SOAP 1.2
RPC/encoded
N/A
N/A
N/A
N/A
N/A
N/A
SOAP 1.2
document/literal
N/A
Yes
Yes
Yes
Yes
N/A

 


WS-TX Interoperability

SALT supports most external Web service applications that are described using WS-TX standard documents as listed in Table 4.

Table 4 WS-TX Standards Interoperability
 
WebLogic Server 10.3.3
.Net 3.5
Client interoperability
WS-COOR 1.0 and WS-AT 1.0
Yes
Yes
Server interoperability
WS-COOR 1.0 and WS-AT 1.0
Yes
Yes

 


SAML Interoperability

Table 5 lists the SALT supported SAML standards and application server.

Table 5 SAML Standards and Application Server
WS-Security Policy
Application Server
SAML 1.1 with Asymmetric binding
  • InitiatorToken Always or AlwaysToRecipient
  • RecipientToken Never
Signed Supporting Token SAML v 1.1
WebLogic Server 10.3.5
SAML 2.0 with Asymmetric binding
  • InitiatorToken Always or AlwaysToRecipient
  • RecipientToken Never
Signed Supporting Token SAML v 2.0
WebLogic Server 10.3.5

 


See Also


  Back to Top       Previous  Next