About this task
On the Partner Links tab, specify the Web Services partner
links that will be used in this workflow. Partner links consist of
a name and the WSDL URL for Invoke functions, or a name and port definition
for Receive functions. These are required before you can create Invoke,
Receive, or Reply system functions. See Using
Web Services in
FileNet®
workflows for
examples.
Procedure
- If the Partner Links tab is not open, select Workflow Properties, and then select the Web Services >> Partner Links tab.
- In the Partner Links Name field, specify a name that will
identify a particular Web Service in this workflow definition. The
name can be a maximum of 15 characters—letters, numbers, underscore,
no spaces.
- Select Invoke or Receive/Reply or both, depending on how
this partner link will be used.
- Use Invoke if this partner link will request a web service.
- Use Receive/Reply if this partner link will provide a web service.
- For Invoke, complete the following steps.
- Specify the WSDL URL—the
location of the WSDL for this partner link—either by clicking Web Services Explorer, or by typing the
complete URL or path in the field.
In the Web Services Explorer dialog box, you can browse FileNet workflows that provide a Web Service—workflows that contain a
Receive system function. See Web Services Explorer for additional
information.
If you are
typing in a path to a local WSDL file, use the following format: "file:////c:\\temp\\helloelb.wsdl". (Use
the escape characters / and \ before the corresponding path delimiters.)
Note that you can directly enter the WSDL
URL in this field only if allowed to do so in the isolated region
properties.
- Click Port Type, then
select the appropriate port type returned by the WSDL.
For Receive/Reply, In Process
Port Type, enter a port name for this service.
Results
NOTES
- P8 supports the following WSDL message formats: - document/literal
- RPC/encoding
- P8 does not support the following WSDL message format: - RPC/literal
- If you select an existing partner link that specifies a WSDL that
is not valid, there can be a several minute delay before an error
message displays. You can configure the duration of this timeout as
a Java™ Runtime Environment (JRE)
system variable as follows: