Converting a WSDL File into Oracle Tuxedo Definitions

1.1.3.2.1 Converting a WSDL File into Oracle Tuxedo Definitions

SALT provides a WSDL conversion command utility to convert external WSDL files into Oracle Tuxedo definitions. The WSDL file is converted using Extensible Stylesheet Language Transformations (XSLT) technology. Apache Xalan Java 2.7.0 is bundled in the SALT installation package and is used as the default XSLT toolkit.

The SALT WSDL converter is composed of two parts:

The xsl files, which process the WSDL file.
The command utility, wsdlcvt<WSDF>, invokes the Xalan toolkit. This wrapper script provides a user friendly WSDL Converter interface.

The following sample command converts an external WSDL file and generates Oracle Tuxedo definition files.

wsdlcvt -i GoogleSearch.wsdl -o GSearch

The following table lists the Oracle Tuxedo definition files generated by SALT WSDL Converter.

Table 1-3 Tuxedo Definition Files generated by SALT WSDL Converter

Generated File	Description
Oracle Tuxedo Service Metadata Repository input file	SALT WSDL Converter converts each `wsdl:operation` to a Oracle Tuxedo service metadata syntax compliant service called SALT proxy service. SALT proxy services are advertised by `GWWS` servers to accept ATMI calls from Oracle Tuxedo applications.
FML32 field table definition file	SALT maps each `wsdl:message` to an Oracle Tuxedo FML32 typed buffer. The SALT WSDL Converter decomposes XML Schema of each message and maps each basic XML snippet as an FML32 field. The generated FML32 fields are defined in a definition table file, and the field name equals to the XML element local name by default. To access an SALT proxy service, Oracle Tuxedo applications must refer to the generated FML32 fields to handle the request and response message. FML32 environment variables must be set accordingly so that both Oracle Tuxedo applications and GWWS servers can map between field names and field identifier values. Note: You may want to re-define the generated field names due to field name conflict or some other reason. In that case, both Oracle Tuxedo Service Metadata Definition input file and FML32 field table definition file must be changed accordantly. For more information, see Resolving Naming Conflict For the Generated SALT Proxy Service Definitions
Non-native WSDF file	SALT WSDL Converter converts the WSDL file into a WSDF file, which can be deployed to GWWS servers in the SALT deployment file for outbound direction. The generated WSDF file is anon-native WSDF file. Note: Please do not deploy non-native WSDF files for inbound direction.
XML Schema files	WSDL embedded XML Schema and imported XML Schema (XML Schema content referenced with `<xsd:import>`) are saved locally as `.xsd` files. These files are used by GWWS servers and need to be saved under the same directory. Note: New XML Schema environment variables `XSDDIR` and `XSDFILES` must be set accordingly so that GWWS servers can load these `.xsd` files.

Parent topic: Manual SALT Configuration