Web Services Integration

BETA: This feature is currently in Beta testing. It's available for experimentation, but is not yet recommended for production use.

About Web Service Integration

Web Services whose connections are specified using the Web Service Description Language (WSDL) can be integrated into the platform without programming, by performing a few configuration steps.

In addition, the interface defined by the WSDL can be simplified by the IT admin, so it more closely matches the application, by:

• Ignoring fields that are not needed
• Hardcoding data for fields whose values are fixed
• Creating more application-friendly names for the remaining fields defined in the WSDL

Those steps are covered below, under Configuring a Web Service.

Once done, an application designer can add a step in a Process Model to utilize the Web Service. The designer then uses the application-friendly names to:

• Map current record fields to and from WSDL input and output fields
• Specify fixed values or expressions for WSDL input fields
• Define expressions that operate on WSDL output fields and store the results in the record

The mechanisms are discussed further below, under Working with a Web Service.

Managing Web Service Configurations

Creating a Web Service

Start by uploading the WSDL file:

1. Download the WSDL file for the service the application will connect to.
   (Web Services managed by the WebMethods integration server are recommended.)
2. Go to > Developer Resources > Web Services
3. Click [New Web Services Invocation]
4. Click [Select WSDL]
5. Browse to the folder that contains the WSDL file, and upload it.

You can now configure a service:

6. In the form that opens, specify:
   • Basic Parameters:

   • Title - Give the service a title. (Displays in the Name column of the Services list.)
   • Operation - Choose one of the operations defined in the WSDL file
   • Version - Optional. Enter text to identify the service version

   • Service Parameters:

   • URL - Optional. Use this field to point to a destination other than one defined in the WSDL file
   • Username -' Username required to use the service, when required
   • Password - Password required to use the service, when required
   • TTL - Time to Live. Optional. The amount of time the platform will wait before abandoning a service request, in milliseconds.

7. Click [Next]

You can now begin to simplify the service for designers.

Start by mapping input fields (fields going to the service) defined for the WSDL file.

8. For each input field, choose one of:
   • Ask for Mapping -

   • Friendly Name - Give the WSDL field a name the application designer will recognize

   • Ignore -
   • Hardcode - Provided a hardcoded value for the field. (The application will never even see it.)
   • Username - Supply the Username value defined in the initial configuration step ($username).
   • Password - Supply the Password value defined in the initial configuration step ($password).
9. Click [Next]

Then map output fields (fields coming from the service):

10. For each output field, choose one of:
    • Ask for Mapping - Ask the designer to supply the name of a record field to store the value into.

    • Friendly Name - Give the WSDL field a name the application designer will recognize

    • Ignore - Ignore this value
11. Click [Save]

The Web Service is now ready for use by an application designer.

Viewing and Modifying a Configuration

1. Go to > Developer Resources > Web Services
2. Click the Service name
3. Click [Details]
4. Follow the steps described in the previous section to view the configuration and make changes.

Adding a New Version

1. Go to > Developer Resources > Web Services
2. Click the Service name
3. Click [Add New Version]
4. Follow the steps described earlier to add another version of the service.
   (Be sure to provide a value in the Version field.)

Testing a Service

1. Go to > Developer Resources > Web Services
2. Click the Service name
3. Click [Test Service]
4. Provide input values.
5. Click [Execute]
6. Output values are displayed

Working with a Web Service

Once a Web Service has been configured, you can add it as a step in a Process Model:

1. Go to > Objects > {object} > Process Models
2. Select an existing process model, or create a new one
3. From the palette, drag the element to Execute Web Service into the model
4. Fill in the parameters for this process step:
   • Name - Give the step a name
   • Web Service - Select one of the Web Services configured for the application

     If the service has a version identifier, it is displayed following the service name

     For example: Some Service [Version 2]

   • Input Mapping - For each field that goes to the service, choose one of the following, and then choose the WSDL field that the value goes into, from the list of friendly names defined in the Web Service configuration:

   • Use Object Field - Select a field from the current record
   • Use Fixed Value - Define a fixed value
   • Use Expression -
   • Use Expression - Create an expression based on record fields. When the dialog opens:

     • Click Field to select a field in the record, or in a record referenced by a Lookup
     • Click the dropdown to select an operator
     • Click Function to select a Function
     • Click in the text area to enter a value
     • Click [Insert] to insert the result into the mapping field

   • Output Mapping - For each field that comes from the service, choose one of the following, and then choose the record field to store the value in:

   • Use WSDL Field - Select a WSDL output field from the list of friendly names defined in the Web Service configuration.
   • Use Expression - Create an expression based on WSDL fields. When the dialog opens:

     • Click Field to select a WSDL field
     • Click the dropdown to select an operator
     • Click Function to select a Function
     • Click in the text area to enter a value
     • Click [Insert] to insert the result into the mapping field

5. Click [Save]
   When the process reaches this step, the Web Service is automatically invoked, and the specified data interchange occurs.