Difference between revisions of "Web Services Integration"
imported>Aeric |
imported>Aeric |
||
| Line 4: | Line 4: | ||
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. | 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 | 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 | :* Ignoring fields that are not needed | ||
:* Hardcoding data for fields whose values are fixed | :* Hardcoding data for fields whose values are fixed | ||
:* Creating more application-friendly names for the remaining fields defined in the WSDL | :* Creating more application-friendly names for the remaining fields defined in the WSDL | ||
Those steps are covered below, under [[#Configuring a Web Service|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: | 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: | ||
| Line 16: | Line 16: | ||
:* Define expressions that operate on WSDL output fields and store the results in the record | :* 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|Working with a Web Service]]. | |||
==Configuring a Web Service== | ==Configuring a Web Service== | ||
Revision as of 01:38, 12 September 2013
BETA:
This feature is currently in Beta testing. It's available for experimentation, but is not yet recommended for production use. It has been tested with the WebMethods integration server only.
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.
Configuring a Web Service
To configure a Web Service:
- Download the WSDL file for the service the application will connect to.
(Web Services managed by the WebMethods integration server are recommended.) - ...