4.2.1 WSDL-to-Tuxedo Object Mapping

SALT converts WSDL object models into Oracle Tuxedo models using the following rules:

• Only SOAP over HTTP binding are supported. Each binding is defined and saved as a WSBinding object in the WSDF file.
• Each operation in the SOAP binding is mapped as one Oracle Tuxedo-style service (which is also called a SALT proxy service). The operation name is used as the Oracle Tuxedo service name and indexed in the Oracle Tuxedo Service Metadata Repository.

  Note:

  If the operation name exceeds the Oracle Tuxedo service name length limitation (255 characters), you must manually set a unique short Oracle Tuxedo service name in the metadata respository and set the <Service> tuxedoRef attribute in the WSDF.

  For more information, see SALT Web Service Definition File Reference in the SALT Reference Guide

• Other Web service external application protocol information is saved in the generated WSDF file (including SOAP protocol version, SOAP message encoding style, accessing endpoints, etc.).
• XML Schema definitions embedded in the WSDL file are copied and saved in separate .xsd files.
• Each wsdl:operation object and its input/output message details are converted as theOracle Tuxedo service definition conforms to the Oracle Tuxedo Service Metadata Repository input syntax.

The following table lists detailed mapping relationships between the WSDL file and Oracle Tuxedo definition files.

Table 4-1 WSDL Model / Oracle Tuxedo Model Mapping Rules

WSDL Object	Oracle Tuxedo/SALT Definition File	Oracle Tuxedo/SALT Definition Object
/wsdl:binding	SALT Web Service Definition File (WSDF)	/WSBinding
/wsdl:portType		/WSBinding/Servicegroup
/wsdl:binding/soap:binding		/WSBinding/SOAP
/wsdl:portType/operation	Metadata Input File (MIF)	/WSBinding/service
/wsdl:types/xsd:schema	FML32 Field Defintion Table	Field name type