How to create devices and tasks

SOAP task

SOAP is a lightweight protocol for the exchange of information in a decentralized, distributed environment. It is an XML-based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined data types, and a convention for representing remote procedure calls and responses.

A SOAP task assigns agents to replicate one or more client requests and monitor the Web Services for availability, errors, and proper content. The agent will send alerts If an issue is detected based upon the preferences selected in the device setup.

Creating a task

You can manually configure a SOAP task using a SOAP envelope or you can use the SOAP Wizard by clicking the Use WSDL button at the top of the page.

The HTTP/SOAP wizard allows you to specify a WSDL URL and lets you select valid parameters to test before you continue. (You must specify the entire URL including http, such as “http://www.example.com/wsdl.asmx?WSDL”).

URL

Enter the URL of the page you wish to perform the task on. It should be formatted as such: www.example.com.

Completion Timeout (in seconds)

Enter the number of seconds the task should wait for a response from the web page before aborting the task and returning an error. If this is left blank the default timeout for a task is 120 seconds.

SOAPAction

The SOAPAction HTTP request header field can be used to indicate the intent of the SOAP HTTP request. The value is a URI identifying the intent. SOAP places no restrictions on the format or specificity of the URI or that it is resolvable. An HTTP client MUST use this header field when issuing a SOAP HTTP Request. The presence and content of the SOAPAction header field can be used by servers such as firewalls to appropriately filter SOAP request messages in HTTP. The header field value of empty string (“”) means that the intent of the SOAP message is provided by the HTTP Request-URI. No value means that there is no indication of the intent of the message.

Post XML

Enter the body of the XML request.

Content validation

Content Validation Keywords are used to ensure that the expected content was loaded onto a web page.

In the Keyword fields, you can specify one or more words or phrases that you wish to search for in the web page content.  If the expected keywords are not found the task will return an error.

You can enter multiple strings into the keyword fields.  The values you enter can be separated by logical expressions as follows:
{[(“keyword1″&”keyword2″)|!”keyword3″]}
]} – keyword expression end;
where
{[ – keyword expression start;
() – grouping brackets;
& – logical AND;
| – logical OR;
! – logical NOT;
“string” – a keyword;

A successful Keyword expression must include the start and end brackets as follows:

{[“keyword”]}

Basic Authentication

Basic authentication is used to allow users to access content on some websites.

Username: this field contains a username for HTTP/S basic or digest access authentication.

User Password: the field contains a password for HTTP/S basic or digest access authentication.

Read the article on Authentication username and password for more information.

Headers

The option allows to add any additional custom headers in the following format (by “=” symbol, each header should start from a new line):

Header_name_1 = "value"
Header_name_2 = "value"

Header Name: specify the name of the parameter as it will appear in the request.

Value: enter the value associated with the name of the parameter.

DNS Options

The DNS Options feature allows users to choose how domain name server (DNS) requests are conducted during a monitoring task.

To specify the mode of resolving hostnames, in the DNS Resolve Mode section, select one of the available modes. For more details on the feature configuration, see DNS Mode Options.

The Custom DNS Hosts section contains the mappings of IP addresses to hostnames.

To specify the mapping, enter the IP address and the host name in the corresponding fields.

Examples:

192.168.107.246   example.com user.example.com userauth.example.com tools.example.com
192.168.107.246   example.com
192.168.107.246   user.example.com
192.168.107.246   userauth.example.com