Table of Contents Previous Next PDF


Introduction to Oracle Service Architecture Leveraging Tuxedo Programming

Introduction to Oracle Service Architecture Leveraging Tuxedo Programming
This section includes the following topics:
Oracle Service Architecture Leveraging Tuxedo Web Services Programming
Oracle Service Architecture Leveraging Tuxedo (SALT) provides bi-directional connectivity between Oracle Tuxedo applications and Web service applications. Existing Oracle Tuxedo services can be easily exposed as Web Services without requiring additional programming tasks. SALT generates a WSDL file that describes the Oracle Tuxedo Web service contract so that any standard Web service client toolkit can be used to access Oracle Tuxedo services.
Web service applications (described using a WSDL document) can be imported as if they are standard Oracle Tuxedo services and invoked using Oracle Tuxedo ATMIs from various Oracle Tuxedo applications (for example, Oracle Tuxedo ATMI clients, ATMI servers, Jolt clients, COBOL clients, .NET wrapper clients and so on).
Oracle Service Architecture Leveraging Tuxedo Proxy Service
SALT proxy services are Oracle Tuxedo service entries advertised by the SALT Gateway, GWWS. The proxy services are converted from the Web service application WSDL file. Each WSDL file wsdl:operation object is mapped as one SALT proxy service.
The SALT proxy service is defined using the Service Metadata Repository service definition syntax. These service definitions must be loaded into the Service Metadata Repository. To invoke an proxy service from an Oracle Tuxedo application, you must refer to the Oracle Tuxedo Service Metadata Repository to get the service contract description.
For more information, see Oracle Tuxedo ATMI Programming for Web Services.
Oracle Service Architecture Leveraging Tuxedo Message Conversion
To support Oracle Tuxedo application and Web service application integration, the SALT gateway converts SOAP messages into Oracle Tuxedo typed buffers, and vice versa. The message conversion between SOAP messages and Oracle Tuxedo typed buffers is subject to a set of SALT pre-defined basic data type mapping rules.
When exposing Oracle Tuxedo services as Web services, a set of Tuxedo-to-XML data type mapping rules are defined. The message conversion process conforms to Tuxedo-to-XML data type mapping rules is called “Inbound Message Conversion”.
When importing external Web services as SALT proxy services, a set of XML-to-Tuxedo data type mapping rules are defined. The message conversion process conforms to XML-to-Tuxedo data type mapping rules is called “Outbound Message Conversion”.
For more information about SALT message conversion and data type mapping, see Understanding Oracle Service Architecture Leveraging Tuxedo Message Conversion.
Oracle Service Architecture Leveraging Tuxedo Programming Tasks Quick Index
Table 1‑1 lists a quick index of SALT programming tasks. You can locate your programming tasks first and then click on the corresponding link for detailed description.
 
 

Copyright © 1994, 2017, Oracle and/or its affiliates. All rights reserved.