Reference Guide

Oracle SALT Web Service Definition File Reference

The following sections provide SALT Web Service Definition File (WSDF) reference information:

Overview

The Oracle SALT Web Service Definition File (WSDF) is an XML-based file used to define Oracle SALT Web service components (for example, Web Service Bindings, Web Service Operations, Web Service Policies, and so on). WSDF is a SALT specific representation of the Web Service Definition Language data model. There are two WSDF types:

For more information, see tmwsdlgen and wsdlcvt in the Oracle SALT Command Reference.

Oracle SALT WSDF Format

Figure A-1 shows a graphical representation of the WSDF format.

XML Schema

An XML Schema is associated with the WSDF. The XML Schema file that describes the WSDF format is located in the following directory: $TUXDIR/udataobj/salt/wsdf.xsd.

Oracle SALT WSDF Examples

Listing A-1 and Listing A-2 show native and non-native WSDF examples.

<Definition name="bankapp" 
  xmlns=http://www.bea.com/Tuxedo/WSDF/2007 >
  <WSBinding id="bankapp_binding" >
    <Servicegroup id="bankapp">
      <Policy location="/home/user/rm.xml" />
      <Service name="inquiry" />
      <Service name="deposit" />
    </Servicegroup>
    <SOAP>
      <AccessingPoints>
        <Endpoint id="HTTP1" address="http://myhost:7001" />
        <Endpoint id="HTTPS1" address="https://myhost:7002/bankapp" />
      </AccessingPoints>
    </SOAP>
  </ WSBinding >
</Definition>

<Definition name="myWebservice"
  wsdlNamespace="http://www.example.org/myWebservice"
  xmlns=http://www.bea.com/Tuxedo/WSDF/2007 >
  <WSBinding id="A_binding">
    <Servicegroup id="portType">
      <Service name="operation_1" soapAction="op1" />
      <Service name="operation_2" soapAction="op2" />
    </Servicegroup>
    <SOAP version="1.1" style="rpc" use="encoded">
      <AccessingPoints>
        <Endpoint id="example_http_port"
                  address="http://www.example.org/abc" />
        <Endpoint id="example_https_port"
                  address="https://www.example.org/abcssl" />
      </AccessingPoints>
    </SOAP>
  </WSBinding>
  <WSBinding id="B_binding">
    <Servicegroup id="portType">
      <Service name="operation_3" soapAction="op3" />
      <Service name="operation_4" soapAction="op4" />
    </Servicegroup>
    <SOAP version="1.2">
      <AccessingPoints>
        <Endpoint id="another_http_port"
                  address="http://www.example.org/def" />
      </AccessingPoints>
    </SOAP>
  </WSBinding>
</Definition>

Oracle SALT WSDF Element Descriptions

WSDF format elements and their attributes are listed and described in the following section.

<Definition>

Table A-1 lists the WSDF file root elements and attributes.

<WSBinding>

Defines concrete protocol binding information. Zero or more WSBinding objects can be specified in one WSDF file.

Native WSDF: you can set SOAP version, encoding style, several endpoints for Web Service Client connection through sub element <SOAP> and a set of Tuxedo services to be exposed for invocation through sub element <Servicegroup>.

Non-native WSDF: each SOAP binding object (i.e., wsdl:binding object with soap:binding extension) in the external WSDL document is translated into one WSBinding object. Table A-2 lists the <WSBinding> attributes.

<Servicegroup>

Defines a Servicegroup object for one WSBinding object. Each WSBinding object must have exactly one Servicegroup. The Servicegroup object is used to encapsulate a set of Tuxedo services. Table A-3 lists the <Servicegroup> attributes.

<Service>

Specifies a service for the WSBinding object.

Native WSDF: each service is a Tuxedo service.

Non-native WSDF: each service represents a converted Tuxedo service from a wsdl:operation object defined in the external WSDL document.Table A-4 lists the <Service> attributes.

<Input>

Specifies Input message attributes for a particular service. This element is optional.Table A-5 lists the <Input> attributes.

<Output>

Specifies Output message attributes for a particular service. This element is optional.Table A-6 lists the <Output> attributes.

<Fault>

Specifies Fault message attributes for a particular service. This element is optional.Table A-7 lists the <Fault> attributes.

<Msghandler>

Specifies a customized message conversion handler. Optional for <Input>, <Output> and/or <Fault> elements of any service. The value of this element is the handler name, which may contain a maximum of 30 characters (excluding the terminating NULL character).

The GWWS server looks for the message conversion handler from all known message conversion plug-in shared libraries using the handler name.The message conversion handler allows you to develop customized Tuxedo buffer and SOAP message payload transformation functions to replace the default GWWS message conversions.

For more information, see “ Programming Message Conversion Plug-ins“in the Oracle SALT Programming Web Services.

<Policy>

References one Web Service Policy file applied to one of the following two levels:

At most, 10 Web Service policies can be referenced for each object.Table A-8 lists the <Policy> attributes.

<Property>

Specifies SALT specific properties for each service object.Table A-9 lists the <Property> attributes.

Table A-10 lists all properties that can be specified for each service object.

<SOAP>

Specifies SOAP protocol information for the WSBinding object. SOAP version, message style accessing endpoints are specified in this element.Table A-11 lists the <SOAP> attributes.

<AccessingPoints>

Specifies the endpoint list for the WSBinding object. Each sub element <Endpoint> represents one particular endpoint.

There are no attributes for this element.

<Endpoint>

Specifies each accessing endpoint for the WSBinding object.Table A-12 lists the <Endpoint> attributes.

<Realm>

Specifies the HTTP Realm attribute of an HTTP and/or HTTP/S endpoint. If this element is configured for one endpoint, the GWWS tries to incorporate HTTP basic authentication information in the request messages when issuing outbound calls through this endpoint.

For more information, see “ Configuring Transport Level Security” in the Oracle SALT Administration Guide.