Hybrid Integration 10.2 | Integrating On-Premises Applications | Document Conventions | Working with Web Services | Viewing the WSDL Document for a Web Service Descriptor
 
Viewing the WSDL Document for a Web Service Descriptor
On the WSDL tab, you can view the WSDL document associated with a consumer or provider web service descriptor.
*For a consumer web service descriptor, the WSDL document is a local copy of the original WSDL document used to create the consumer web service descriptor with the following changes:
*The addition of any headers or faults added to the consumer web service descriptor.
*Modifications to the editable properties of the provider web service descriptor or its constituents, such as the use of a web service endpoint alias.
*For a service first provider web service descriptor, the WSDL document contains all the information a consumer needs to create a web service client that invokes the operations described in the WSDL.
*For a WSDL first provider web service descriptor, the WSDL document is the original source WSDL with the following changes:
*Addition of any headers or faults added to the provider web service descriptor.
*Modifications to the editable properties of the provider web service descriptor or its constituents, such as the use of a web service endpoint alias.
*Modification to the name attribute in the wsdl:service element to reflect the name of the web service descriptor.
*Removed all soapjms wsdl extensions for JMS bindings contained in the original wsdl:port, wsdl:service, or wsdl:binding elements.
*Addition of soapjms wsdl extensions to the wsdl:binding element for JMS bindings. This includes JMS transport properties defined in the web service endpoint alias assigned to the binder that specifies the JMS transport.
*Changes to the location attribute of the wsdl:port element to reflect any JMS connection related settings for the JMS URI.
*The displayed WSDL document contains all the information a consumer needs to create a web service client that invokes the operations described in the WSDL.
*For a web service descriptor created from a WSDL that contains relative URIs that are anonymously addressable, Integration Server replaces any relative URIs with an absolute URI using the base URI of the WSDL file.
*If you attach a WS-Policy to a provider web service descriptor that is not running in pre-8.2 compatibility mode (i.e., the Pre-8.2 compatibility mode property is set to false), the generated WSDL will be annotated with the policy. If you attach multiple policies to a web service descriptor, the generated WSDL will have policy annotations of all the attached policies. The policy is annotated using PolicyURIs attributes. Integration Server identifies the associated policies by specifying the policy IDs in the PolicyURIs attributes.
You must save the web service descriptor before the policy annotations will be included in the WSDL. If the web service descriptor is not saved after a policy is attached to it, the WSDL on the WSDL tab will not yet include the policy annotations. When you save the web service descriptor, Integration Server obtains the policy from the policy files so that Designer can display it in the generated WSDL.
*When viewing the WSDL for a WSDL first provider web service descriptor that was created from a policy annotated WSDL, the generated WSDL will be annotated with the attached policies. The generated WSDL will not include the annotated policy from which it was generated.
*For a consumer web service descriptor, the generated WSDL will always contain the original annotated policy from the source WSDL document.
* To view the WSDL document for a web service descriptor
1. In Package Navigator view, open the web service descriptor for which you want to view the WSDL document.
2. Click the WSDL tab.
Designer displays the WSDL document for the web service descriptor.

Copyright © 2015- 2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release