Workflow system leverages Web Services technology to enable workflow authors to define
message interaction between FileNet® P8 processes, as well as
between FileNet P8 workflows and other business
processes.
Workflow system provides three Web Services features:
- A Web Services API that provides a subset of the Process Java™ API. You can use the Web Services
API to write step processors.
- The ability to invoke Web Services defined in another workflow. This feature allows you to
create workflows that can use Web Services developed by others in your organization or available
externally on the Internet.
- The ability to provide a workflow as a Web Service, which enables other applications to interact
with your workflow via Web Services.
There are two modalities you can use to create or invoke a Web Service:
- The parameters modality allows you to invoke or create Web Services without requiring knowledge
or understanding of XML or XML schemas. This feature provides an easy way to start using Web
Services.
- The XML modality requires XML and XML schema knowledge, and allows users to deal with complex
XML messages that might not be suitable for the parameters modality.
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 P8 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 P8 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.
- 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.
- Attachments
- You can pass attachments by reference between two FileNet P8
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.