Table of Contents

Search

  1. Preface
  2. Web Services
  3. SOAP Web Services
  4. WSDL Data Object
  5. Schema Object
  6. How to Create a SOAP Web Service
  7. Operation Mappings
  8. Parsing Web Service SOAP Messages
  9. Generating Web Service SOAP Messages
  10. Web Service Consumer Transformation
  11. REST Web Services
  12. How to Create a REST Web Service
  13. REST Web Service Consumer Transformation
  14. REST Web Service Consumer Transformation Use Cases
  15. REST and SOAP Web Service Administration
  16. Appendix A: Datatype Compatibility

Web Services Guide

Web Services Guide

Manually Create an Operation

Manually Create an Operation

Use the
Create Web Service
wizard to define operations and to define the operation input, operation output, and operation faults for each operation.
After you complete the steps to create a web service, you can create and configure the operation from within the
Create a Web Service
wizard.
  1. In the
    New Web Service
    dialog box, click the arrow next to the
    New
    button. Then, select
    Operation
    Create as empty
    .
    1. Enter a name for the operation.
      The Developer tool uses the operation name to define the names for the operation input and the operation output.
    2. Select the SOAP version for the operation as the
      Binding Type
      .
    3. To define fault messages, click the arrow next to the
      New
      button and then click
      Fault.
      You can choose to create each element for the fault message or select reusable elements. The wizard adds the elements to the detail element in the fault message.
  2. Click the operation input to display and configure its properties.
    1. Click the
      Operation Input
      tab.
    2. To add elements, click the arrow next to the
      New
      button, and then click
      Element
      . To add child elements, select an element, click the arrow next to the
      New
      button and click
      Child Element
      .
    3. To specify a type for each element, click the selection button in the
      Type
      field. Choose an XSD type or a schema object type and click
      OK
      .
      Click the
      Type
      field and enter the first few characters of the type you want to select. A list of XSD types with names that start with the characters you enter will appear in a list.
    4. Configure the minimum and maximum number of occurrences for each element.
    5. Optionally, enter a description for each element.
    6. Optionally, click the
      Mapping Input
      tab to map data from the operation input to the output ports.
      You can also map the data when you configure the Input transformation.
  3. Click each operation fault to display and configure its properties.
    You can click the
    Mapping Fault
    tab to configure how to map data from the input ports to the operation fault. You can also map the data when you configure the Fault transformation.
  4. Click the operation output to display and configure its properties.
    1. Click the
      Operation Output
      tab.
    2. To add elements, click the arrow next to the
      New
      button, and then click
      Element
      . To add child elements, select an element, click the arrow next to the
      New
      button, and then click
      Child Element
      .
    3. To specify a type for each element, click the selection button in the
      Type
      field. Then, choose an XSD type or a schema object type and click
      OK
      .
    4. Configure the minimum and maximum number of occurrences for each element.
    5. Optionally, enter a description for each element.
    6. Optionally, click the
      Mapping Output
      tab to map data from the input ports to the operating output.
      You can also map the data when you configure the Output transformation.
  5. Repeat steps 1 through 4 to add and configure more operations.
  6. Click
    Finish
    .
    The Developer tool creates an operation mapping for each operation based on how you configure each operation.
You can optionally create an element or a predefined fault.

0 COMMENTS

We’d like to hear from you!