Modifying the Signature of a 6.5 SOAP-MSG Style Operation
A web service requires the input parameters from a signature and produces the output parameters. By default, an operation derives the input and output signatures from the services used to create the operation. However, in the case of a 6.5 SOAP-MSG style service, the input and output signatures consist of a soapRequestData and soapResponseData objects. In a WSDL document, this would result in an vague, meaningless signature. To create a meaningful service signature for a 6.5 SOAP-MSG style operation, you can override the original service signature by selecting an element declaration in an XML schema definition or an IS document type as the service signature. Overriding the service signature is necessary after adding a 6.5 SOAP-MSG style service as an operation to a provider WSD.
Keep the following points when modifying the operation signature source:
You can only modify the operation signature source in a provider WSD that was created from an IS service. You cannot add or modify the signature of a provider WSD created from a WSDL URL or a UDDI Registry.
The XML schema definition you select must be located on the web and must be network accessible to consumers of the WSDL. Do not use a local file URL to refer to an external schema.
If you use an IS document type as the signature for an operation that corresponds to an
Integration Server 6.5 SOAP message service, the IS document type must satisfy the service signature requirements for the SOAP MSG protocol a specified in the
Web Services Developer’s Guide version 6.5. For more information about adding an IS 6.5 SOAP message service as an operation, see
Using a 6.5 SOAP-MSG Style Service as an
Operation.
An IS document type used to represent the input or output signature of an operation cannot contain top-level fields named "*body" or top-level fields starting with "@".
To modify the signature type of a 6.5 SOAP-MSG style operation
1. In Package Navigator view, open and lock the provider web service descriptor containing the operation whose signature you want to modify.
2. In the Operations tab, select and expand the operation whose signature you want to modify.
3. Do one of the following:
To change the... | Do this... |
Input signature | Expand Request and select the Body element. |
Output signature | Expand Response and select the Body element. |
4. In the Properties view, next to the Signature field, click the browse button.
5. In the Modify I/O Signature dialog box, do one of the following:
Select... | To... |
Original IS service | Use the input or output signature from the originating IS service as the input or output signature. This is the default. |
Existing external XML schema | Use an element declaration from an XML schema definition as the input or output signature. |
Document type | Use an IS document type as the input or output signature. |
6. If you selected Existing external XML schema, do the following:
a. In the URL field, after http://, type the web location and name of the XML schema definition that contains the element declaration you want to use to describe the signature.
b. Click Load. Designer displays the global element declarations in the XML Schema.
c. Select the global element declaration for the input or output signature.
7. If you selected Document type, select the IS document type that you want to use to represent the input or output signature.
8. Click OK.
9. Click File > Save.
If you selected Existing external XML schema, Integration Server automatically uses the internal schema parser to validate the schema. If the Validate schema using Xerces property is set to True for the web service descriptor, Integration Server also validates the specified XML Schema definition using the Xerces Java parser. If either parser determines that the schema is invalid, Designer does not save the web service descriptor and displays the validation errors.