About Web Services in workflows

Process Engine (PE) leverages Web Services technology to enable workflow authors to define message interaction between FileNet processes, as well as between FileNet workflows and other business processes.

PE provides three Web Services features:

There are two modalities you can use to create or invoke a Web Service:

See the W3C site for a general introduction to Web Services technology. See WebSphere Service Registry and Repository (WSRR) and Oasis UDDI for information about WSRR and UDDI registries.

See Examples for using Web Services in FileNet workflows.

Invoking a Web Service provided by your company, a partner, or from a public UDDI registry

To invoke a Web Service, you need the description (WSDL) of the service, with the expected parameters and the endpoint where the service can be executed. Services are available in WSRR registries, UDDI registries, from business partners, or from your own FileNet workflows designed to provide a Web Service. Process Configuration Console and Process Designer provide interfaces for configuring and defining your Web Services.

Providing a Web Service for use within your company, to partners, or for public use

To provide a Web Service, you create a workflow with a Receive step, then make it available for use by other FileNet workflows or outside partners.

Advanced features

Authentication and security - Using the built-in authentication option in the Receive step, you can specify that a logon and password is required for a request. See Web Services - authentication example.

Correlation - By configuring correlation sets in Invoke, Receive, and Reply functions, you can identify specific conversations between Web Services. For example, in a purchase order conversation between the buyer and supplier, an order number can be used to identify the appropriate messages between the buyer and supplier. See Web Services - correlation example.

Attachments - You can pass attachments by reference between two FileNet workflow systems that have access to the same object store. The attachment reference information is included in the message.

You can pass attachments by value between any Web Services applications. When an attachment is passed by value, the complete document is sent in the Web Service message.