APC AP7602 Instruction Manual download pdf (Page 229)

Creating Alert Actions

228 InfraStruXure Central 4.0 User’s Reference

appropriate information in the following fields:

– Type in the Target URL field the custom HTTP GET statement that will be generated by the

device.

– Type in the Target User ID and Password fields the User ID and Password needed to execute the

custom HTTP GET command at the Target URL.

– Type the Password again in the Confirm Password field.

8. If desired, click the Advanced tab and select optional SSL Verify Options for the custom HTTP

GET commands (used for both the primary and backup hosts), or to provide information for use in

delivering the custom HTTP GET command to an alternate web host. This backup URL would be

used only if attempts to deliver the alert data to the primary Target Host failed. You can also check

the following check boxes:

– Use POST instead of GET: Uses the POST command instead of the GET command.

– Include XML-encoded Alert Parameter (xmlalert): Appends the parameter “xmlalert=<xml alert

encoding>” to the provided URL for the action. The encoded XML is the same as is generated by

the HTTP POST code, but is URL-encoded to enable those that can't easily handle multi-part/

form-data encoded POSTS to get the XML for the alert.

9. Click OK to save this Alert Action.

Example Target URLs

When creating a Send Custom HTTP GET alert action, a data handling application of some sort (CGI

script, ASP script, servlet, etc.) must be invoked on the web host invoked in the Target URL, and

appropriate data must be passed to the application in a format that is appropriate. Therefore, the content

of the Target URL field is entirely dependent on the configuration of the target server which will process

the HTTP GET. The following examples demonstrate two possible ways in which this alert action could

be configured, and are intended to help you to construct an appropriate Target URL value.

Example #1:

In this first example, the custom HTTP GET command provides user-specified values for a CGI script

(pagersend.cgi). This custom HTTP GET would send the message “hello there,” with a subject of “test

message,” from “mike” to the specified pin (telephone number):

http://www.mymmode.com/messagecenter/pagersend.cgi?pin=512

5551212&from=mike&subject=test+message&message=hello+there

Example #2:

In this example, alert data is sent to a pager using the same CGI script (pagersend.cgi) as we used in

Example #1, but this time we use BotzWare macros to dynamically generate the message content:

http://www.mymmode.com/messagecenter/pagersend.cgi?pin=512

5551212&from=${HOSTNAME}&subject=test+message&message=${SENSORNAME}+${S

ENSORVAL}+at+${ALERTPOD}

A message generated by this Target URL could read “Humidity 94% at Sensor Pod 0930261” from

“mybotz.netbotz.com.”

Note

The Target URL field accepts BotzWare macros.

1 2 ... 224 225 226 227 228 229 230 231 232 233 234 ... 293 294

No comments

APC AP7602 Instruction Manual Page 229