Create WSDL

The Create WSDL Wizard is used to create a new WSDL document to be used for publishing a service. This WSDL document can be custom created or it can be composed from existing WSDL documents. The steps in the wizard correspond to the six main and child elements in a WSDL document.
gateway91
The Create WSDL Wizard is used to create a new WSDL document to be used for publishing a service. This WSDL document can be custom created or it can be composed from existing WSDL documents. The steps in the wizard correspond to the six main and child elements in a WSDL document.
The Create WSDL Wizard supports the WSDL 1.1 standard.
 
The Create WSDL Wizard is intended for advanced users who are familiar with WSDL, XML, SOAP, and the SOAP protocols. If there is already a WSDL document that meets your needs, use the Publish SOAP Web Service Wizard instead.
 
Using the Wizard
 To access the Create WSDL Wizard, do any of the following:
  • Click
    Create WSDL
    on the Home Page
  • Select [
    Tasks
    ] >
    Services and APIs > Create WSDL
    from the Main Menu
  • Right-click the root folder at the top of the Services and Policies list and then select
    Create WSDL
    .
Complete the wizard as described below.
 
Click [
Preview
] at any time during the configuration process to view the in-progress WSDL for the web service.
 
Step 1: Overview
This step introduces the wizard.
Click [
Next
] to continue.
Step 2: Compose WSDL
The Compose WSDL screen lets you compose or aggregate existing WSDLs to create a WSDL document by copying elements from other WSDLs. Using this feature, it is possible to publish a "virtual service" to the gateway. This allows the gateway to proxy request for multiple services with distinct WSDLs.
If you do not wish to compose your own WSDL document and only want to define your own messages, operations, port types/bindings etc., click [
Next
] without entering anything to proceed to Step 3 of the wizard.
To compose a WSDL document:
  1. Populate the list at the top of the page with the WSDL(s) containing the elements you need to assemble your own WSDL.
    • To add a WSDL to the list, click [
      Add WSDL
      ] to display the Choose WSDL dialog. In the Location field, enter the URL that resolves the new web service WSDL.
    • To configure options for the URL (for example, to specify the credentials or configure a proxy), click [
      HTTP Options
      ] to open the Manage HTTP Options dialog.
    Alternatively:
    • If the WSDL is contained in a file, click [
      File
      ] and select the file.
    • If the WSDL is from a UDDI registry, click [
      UDDI
      ] and complete the Search UDDI dialog. For more information, see Searching the UDDI Registry.
  2. From the WSDL list, select a WSDL containing the operations that you wish to add to your WSDL. The Binding operations are shown in the Source WSDL list under the [Operations] tab.
    To see a tree containing more details about other elements of the WSDL, select the [Source Preview] tab.
  3. To add an operation in the target WSDL, select the operation from the [Operations] tab of the
    Source WSDL
    list and then click
    Add
    . This adds it to the
    Resulting WSDL
    list.
    To remove an operation from the target WSDL, select the operation from the
    Resulting WSDL
    list and then click
    Remove
    .
    Adding and removing operations only affect what is populated in the WSDL document being constructed. It does not necessarily define which WSDL operations should be excluded in the policy; this depends on whether SOAPAction being defined in the service resolution of the Gateway. To properly constrain operation availability, you should include the Evaluate WSDL Operation Assertion in the service policy.
  4. Repeat steps 2 and 3 until you are satisfied with the resulting WSDL.
The WSDL document that you compose here can be refined further as you navigate through the remaining steps of the wizard. All messages and operations that are required for the selected operations are added to the WSDL document being constructed.
Step 3: Definition
The Definition step configures the root definitions element and its child elements. These elements define the particulars of the Web service.
Configure this step of the wizard as follows:
  • Name:
    Enter a descriptive name for the web service. This name appears on the Services and Policies list.
  • Target Namespace:
    The wizard pre-populates a suggested namespace that relates to your web service application. Make any adjustments if necessary. This namespace can be a URL or a SOAP payload namespace URI.
    The namespace plus SOAPAction combination determines the uniqueness of the web service. The Policy Manager checks for uniqueness during the publication process and prompts you for another URI if the web service WSDL is not unique.
    A namespace that resembles a URL does not necessarily point to a Web-based resource. Avoid using relative URI namespaces, if possible. A URI namespace causes XML canonicalization problems and prevents the use of message-level security such as those found in the XML Security assertions.
  • Default Namespace:
    Displays the default URI
    http://schemas.xmlsoap.org/wsdl/
    . The URI is the namespace convention for the main elements in the WSDL document. Make any adjustments if necessary.
  • Namespace Details:
    Displays information about the namespaces. This information cannot be edited here.
Step 4: Messages
The Messages step configures the message elements. A Web service contains multiple messages with one or more logical parts that define the communication between the web service client and server.
Configure this step of the wizard as follows:
  • Message List:
    Double-click the default entry and replace it with a name that describes the message type; for example: "GetQuoteResponse". To add more message names, click [
    Add
    ] and repeat the process. To remove a message name, select it and click [
    Remove
    ].
  • Message Part List:
    Click [
    Add
    ] to add a message part. Double-click the default name under
    Name
    and replace it with a name that describes the message part; for example: "stockSymbol". Select the part type from the
    Type
    drop-down list. To remove a message part, select it and click [
    Remove
    ].
Repeat to add as many messages and parts as necessary.
Step 5: Port Type and Operations
The Port Type and Operations step configures the port type element that includes the set of operations used in the web service. Each operation refers to one input message and one output message configured in the previous Messages step.
Configure this step of the wizard as follows:
  • Name:
    Enter a descriptive name for the port type; for example, "StockInfo".
  • Operation List:
    Click [
    Add
    ] to add an operation. Double-click the default under Name and replace it with a name that describes the operation; for example, "getQuote". Select the appropriate
    Input Message
    and
    Output Message
    from the drop-down lists. (These messages were defined in Step 4 of the wizard.) To remove an operation, select it and click [
    Remove
    ].
Step 6: Bindings
The Port Type Bindings step configures the binding element which specifies the binding definitions that govern message formatting and protocol details.
Configure this step of the wizard as follows:
  • Name:
    Enter a descriptive name for the port type binding; for example, "StockServiceSOAPBinding".
  • Style:
    Select a message format for the operations from the drop-down list.
  • Transport:
    Displays the default namespace URI. The URI is the namespace of the transport-specific elements in the WSDL document. This field is display only.
  • Operations:
    Lists the operations defined in Step 5 of the wizard. If you need to modify any of the SOAP Action shown, double-click an entry and edit as necessary.
Step 7: Service
The Service step configures the service element that defines the web service endpoint address (URL) and access port.
Configure this step of the wizard as follows:
  • Name:
    Enter a descriptive name for the service element into the Name field; for example, "StockQuote".
  • Port:
    Displays the default access port for the web service. Do not change this default.
  • Binding:
    Displays the port type binding name, as entered in Step 6 of the wizard.
  • Address:
    Displays the default URL
    http://localhost:8080/ws/NewServiceName
    , where:
    • "localhost" is the host name of the server hosting the web service
    • "8080" is the TCP port at which the web service can be reached
    • "ws/" is a sample folder that might contain the web service
    • "NewServiceName" is the web service name that was entered in the Name field.
Adjust the address as necessary to construct a valid URL for the web service.
The URL in the
Address
field determines the default web service Message Routing Assertion.
To update the default URL in the
Address
field with the information entered in the
Name
and
Port
fields, click [
Back
] and then [
Next
].
When you are satisfied everything is correct, click [
Finish
] to publish the service. The disabled web service is added to the Services and Policies list. You should now:
If you have specified a conflicting service resolution, you are given the option to correct the conflict, proceed as is, or cancel the publishing.