Use a WSDL for elements with complex relationships.

To create a web service source or target with a complex element relationship, first create a WSDL to define the element hierarchy, and then import the source or target from the WSDL. Use a WSDL to create a web service source or target that contain multiple occurrences of elements or that contain elements of complex type.

Manually define simple web service source or target definitions.

To create a web service source or target with a simple set of columns and without nested elements, create the definition manually or use a relational or flat file source or target definition. You can specify that all columns in the web service source or target definition occur multiple times.

Create the source and target definitions in the same process.

Create a web service target definition from a relational or flat file source or target at the same time you create the source definition. To create the source and target of a web service mapping at the same time, verify that the Create Source and Create Target options are selected on Create Web Service Definition window. For example, in the Source Analyzer, select Sources > Web Service Provider > Create Web Service Definition. On the Create Web Service Definition window, select the Create Target option.

Use the same method to create the source and target definitions for a request-response mapping.

If you create a request-response web service mapping, create the source and target definitions using the same method. For example, if you import the source definition from a WSDL, import the target definition from the same operation in the WSDL. If you create the source definition by defining the columns or by using relational or flat file sources and targets, create the target definition using the same method.

Use a WSDL to create targets with fault views.

If you want the target definition to have fault views for specific data error, use a WSDL to create the web service target definition. You cannot define fault views in a target definition if you create it based on a flat file or relational source or target. If you define a web service target definition based on a flat file or relational source or target, the Web Services Hub can generate fault messages for system faults only.

The input and output message in the WSDL must have the same encoding style.

If you import web service sources and targets from a WSDL, the encoding style for the input and output messages must be the same. If the input message uses the RPC/SOAP Encoded style, the output message must also use the RPC/SOAP Encoded style. If the input message uses the Document/Literal style, the output message must also use the Document/Literal style.

If you create the web service source or target definition manually or based on relational or flat file sources or targets, the Designer uses the Document/Literal encoding style for the input and output messages.

Elements in the WSDL cannot refer to a standard W3C XML schema.

You cannot import web service source and target definitions from a WSDL that contains an element that refers to a standard W3C XML schema.

Import a WSDL with empty complexType elements in entity relationship mode.

If the WSDL contains complexType elements that will not contain values in the input message of the web service request, import the source and target definitions from the WSDL in entity relationship mode. If the source and target definitions are imported from the WSDL in normalized hierarchical mode, the web service generates a fault response if you send a request with an empty complexType element.

Import sources and targets from a WSDL with valid XML syntax.

If you import from an invalid WSDL, the Designer cannot correctly display the WSDL definition in the Web Services Wizard. In some cases, the Designer does not generate error messages but partially parses the WSDL and displays only the services and operations that were successfully parsed. If you import from a WSDL and the Web Services Wizard does not display the correct WSDL definition, open the WSDL as an XML file and verify that the syntax is correct.

Define a two dimensional array with the correct syntax.

If you define a complexType element in the WSDL as a two dimensional array of string, use the following syntax:

You cannot import web service source and target definitions from a WSDL that contains a two dimensional array defined using a different syntax.

You cannot import web service sources and targets from a WSDL that generates a large number of XML views.

The limit for the number of XML views that can be generated from a WSDL file is 400. To create web service sources or targets with more than 400 XML views, create the groups manually in the WSDL workspace.