TotalAgility can access web services to connect to the third-party software applications, regardless of how each web service is implemented. For example, TotalAgility can integrate with a web service that automatically validates a credit card number or retrieves delivery information from a transportation company for a dispatched order.

When defining a Web Service reference, you can specify custom headers so that when the corresponding Web Service or Restful node is executed, the custom header is passed to the Third party web service.

A custom header consists a name and value pair, such as Host: localhost, where Host is the name and localhost is the value. All SOAP, SOAP WCF and RESTful web services support custom headers.

When you import a site, you can reuse the existing web service proxies and proxy file names for any web service references used by TotalAgility processes or sites. Web service proxies are dynamically created at run time.

When you import a map and the proxy cannot be created for the web reference, the reference is still imported and the following message appears: "Web Service failed to create proxy DLL. To fix the issue regenerate client proxy."

When you export a site where a new web service reference has the same name as an existing web service reference, you see a message.

When you start a job on a map, the job suspends and the event log includes the following message: "Web service does not exist. "

This section describes the following:

• Web Services supported by TotalAgility

• Use a Web service

• Create a Web service reference