2.1.1 Browsing to the WSDL Document from the GWWS Server
Each GWWS
server automatically generates a WSDL
document for each deployed inbound native WSDF. The WSDL document
can be downloaded from any of the HTTP/S listening endpoints via
HTTP GET.
Use the following URL to browse the WSDL document:
“http(s)://<host>:<port>/wsdl[? [id=<wsdf_name>] [&mappolicy=<pack|raw|mtom>] [&toolkit=<wls|axis>]]”
Table 2-1 WSDL Download Options
Option | Value Description |
---|---|
id |
Specifies the native WSDF name for the WSDL document. The specified native WSDF must be imported via inbound direction by the GWWS server. If the option is not specified, the first inbound native WSDF is used. |
mappolicy |
{pack | raw | mtom} Specifies the data mapping policies for certain Oracle Tuxedo Typed buffers for the generated WSDL document. Currently, this option impacts CARRAY typed buffers only. If the option is not specified, |
toolkit |
{wls | axis} Use this option only if you have previously defined |
Note:
The WSDL download URL supported by SALT 2.0 and later is different from the SALT1.1 release. In SALT 1.1, one GWWS server adaptively supports both RPC/encoded and document/literal message style, both SOAP 1.1 and SOAP 1.2 version, from a given configuration file.In SALT 2.0 and later, each WSDF file associated with the GWWS server must be pre-combined with a certain SOAP version and a certain SOAP message style. So the following WSDL download options for SALT 1.1 GWWS server are deprecated in this release.
Table 2-2 Deprecated WSDL Download Options
Option | Value Description |
---|---|
SOAPversion
|
This deprecated option is used to specify the expected SOAP version defined in the generated WSDL document. This option is now set in the WSDF file. |
encstyle
|
This deprecated option is used to specify the expected SOAP message style defined in the generated WSDL document. This option is now set in the WSDF file. |
Parent topic: Administering Oracle Tuxedo Web Services