IBM FileNet P8, Version 5.2.1            

Web Services - General properties

Incoming Web Services Attachment Folder

If this workflow uses Web Services operations that might include incoming attachments, specify a folder in your object store or library where these files will be stored.

  1. In the Workflow Properties, select the Web Services tab.
  2. On the General tab, click Browse and locate a folder where the files will be stored.

Verify messages at runtime

To enable error checking for XML messages, select Verify messages at runtime.

When this option is enabled, the following messages will be verified against the schema in the WSDL:

Since this option can be set in FileNet® workflows that contain Invoke functions and workflows that contain Receive functions, the table below outlines when verification will occur.

Invoking workflow Receive workflow Result
Yes, verify messages Yes, verify messages

Invoking workflow verifies both the outgoing message to the web service, and the incoming message from the reply. If the web service is provided by an external source (not a FileNet workflow), the invoking workflow verifies both the outgoing and incoming messages.

Receiving workflow verifies the incoming (invoking) message. See note below.

Yes, verify messages No, don't verify Since the receiving workflow will not verify the message, the invoking workflow does not verify.
No, don't verify Yes, verify messages

Invoking workflow does not verify either the outgoing or incoming messages.

Receiving workflow verifies the incoming message.

No, don't verify No, don't verify Neither workflow verifies the messages

If the message contains an 'attachment by value', or if the message is RPC style, the message is not verified.

By default, this option is enabled except for workflows developed using previous versions of Process Designer. This allows previously defined workflow to continue to run, even if a schema is not valid.

When this option is not enabled, any errors in XML messages will go undetected until a process attempts to use the data, then the web service might generate a fault, or a process might generate an exception or end in an unpredictable manner.

Finalize existing web services operations

While you are developing a workflow that provides a web service, a workflow with Receive and Reply system functions, you will usually revise the Receive and Reply operations a number of times—the input and output parameters for the Receive and Reply operations can change with each revision of the workflow. During this development period, you should not select the Finalize existing web services operations option.

If you develop a separate workflow that invokes this web service during this development phase, the partner link in the invoking workflow identifies a specific version of the workflow that provides the web service. This ensures that the input and output parameters match between the web service and the invoking process. When you modify the workflow with the Receive and Reply system functions, you must update the partner link in any processes that invoke those web services if you want to invoke the latest version of that web service; you might also need to update input and output parameters if they have changed in the latest version of the web service.

When you are satisfied with the input and output parameters of Receive and Reply operations in a workflow, you can optionally finalize the web services in the workflow by selecting the Finalize web services operations option on the Web Services General tab. This has the following effects:

To finalize the input and output parameters of existing Receive and Reply operations:



Last updated: March 2016
bpfdh177.htm

© Copyright IBM Corporation 2016.