|
|
This topic includes the following sections:
BEA SALT provides bi-directional connectivity between Tuxedo applications and Web service applications. Existing Tuxedo services can be easily exposed as Web Services without requiring additional programming tasks. BEA SALT generates a WSDL file that describes the Tuxedo Web service contract so that any standard Web service client toolkit can be used to access Tuxedo services.
Web service applications (described using a WSDL document) can be imported as if they are standard Tuxedo services and invoked using Tuxedo ATMIs from various Tuxedo applications (for example, Tuxedo ATMI clients, ATMI servers, Jolt clients, COBOL clients, .NET wrapper clients and so on).
BEA SALT proxy services are Tuxedo service entries advertised by the BEA 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 BEA 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 a Tuxedo application, you must refer to the Tuxedo Service Metadata Repository to get the service contract description.
For more information, see Tuxedo ATMI Programming for Web Services.
To support Tuxedo application and Web service application integration, the BEA SALT gateway converts SOAP messages into Tuxedo typed buffers, and vice versa. The message conversion between SOAP messages and Tuxedo typed buffers is subject to a set of SALT pre-defined basic data type mapping rules.
When exposing 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 BEA SALT Message Conversion.
The following table lists a quick index of BEA SALT programming tasks. You can locate your programming tasks first and then click on the corresponding link for detailed description.
|