This section explains the procedure for preparing for the use of triggers.
When defining a trigger, you will be mapping the incoming XML data to User Defined Attributes (UDAs). To simplify data mapping, you are recommended to provide an XML schema (*.xsd file) that describes the format of the incoming XML data. This way, the elements of the XML file are available as a drop-down list in Systemwalker Runbook Automation Studio and can be easily mapped to UDAs. If you don't provide an XML schema, you need to specify the location of the elements to be mapped using XPath expressions.
To prepare for using triggers:
Recommended: Provide an XML schema that describes the format of the incoming data:
Create an XML schema.
Store the XML schema on a Web Server to which Systemwalker Runbook Automation Studio has access.
Ensure that you know the URL of the XML schema.
For example, if you have stored the XML schema in the root directory of the Web Server, the URL would be:
http://<computername>/<xml schema name>
To properly map XML data, you will need to know the element names, data types, and element description used in the incoming XML file.
As an example, the following table lists the information you need to know if the incoming XML files were order forms:
Element Name | XSD Data Type | Element Description |
|---|---|---|
orderperson | string | Name of the person taking the order |
name, address, city, state, zip | string | Name, address, etc. of the person making the order |
title, note | string | Item being ordered |
quantity | positiveInteger | Quantity of the item being ordered |
price | decimal | Price of the item being ordered |
Before starting process instances on the Management Server, ensure that the File Listener is configured to check for incoming files. Refer to the "11.13 Defining File Listener" for information on how to configure the File Listener.
