Process Manager's Web service is used to initiate workflow
processes. The Web service event listener waits to be prompted by a
designated Web service. When the Web service receives values or
parameters from another application, the event listener is notified
of the event and initiates a workflow process based on the data it
received.
Setting up Web service event listeners
To set up your Web service event listener, you first need to
select which workflow to initiate. Then you specify which .XML file
from the client application to use, which contains the required
columns and corresponding values. You can then select a specific
column from the .XML file. The Web service event listener pulls the
value from the column, which serves as the external system
identifier. You can also have the system automatically generate the
external system identifier. The external system identifier
pinpoints the application that initiated the workflow and serves as
a reference number to the client application. It is used within all
Process Manager applications.
Once the Web service event listener is set up, you need to
configure the Web service itself to send records to Process
Manager. Sending the records to the following location initiates
the workflow process:
http://[server]/LANDesk.Workflow.ServiceHost/WebServiceListener.asmx?WSDL
To set up a Web service event listener
From the main menu, click Configure | Event
Listeners.
Click Add.
On the Type tab, select Web service.
Click the Details tab, specify a name for the
listener, and then select the workflow you want to be initiated
when the conditions of the event listener are met.
Click the Settings tab, then click Open, select the
appropriate .XML file, and click Open.
Check to see that the values inserted match the
expected XML string.
Click the Mappings tab, then click the
Autogenerate external unique system identifier checkbox or
use the drop-down list to select the external system
identifier.
(Optional) In the Requester field, use the drop-down
list box to include a Requester, if you want this information to be
included in the audit history and other reports.
Click Autogenerate field mappings, then click Yes to
save the changes to the event listener. If you want to define your
own field mappings, skip this step and use the field mapping tool.
See "Field
mapping".