Preface
RulePoint
RulePoint Concepts
- RulePoint Concepts Overview
- Understanding RulePoint Entities
Using RulePoint
RulePoint Objects
- RulePoint Objects Overview
- State of RulePoint Objects
Working with Topics
Working with Connections
Working with Sources
Working with Responders
Working with Responses
Working with Watchlists
Working with Analytics
- Analytics Overview
- Analytic Types
- Creating an Analytic
- Copying an Analytic
- Editing an Analytic
- Deleting an Analytic
- Viewing Related Objects
- Predefined Analytics
  - abs
  - average
  - ceil
  - charat
  - clean
  - compareto
  - concat
  - confidence
  - correlation
  - count
  - current
  - date
  - datedifference
  - endswith
  - even
  - floor
  - getcurrentdate
  - getdatefrommillis
  - getdateinmillis
  - geodistance
  - geoinbound
  - geoinsidearea
  - geointersect
  - geooutbound
  - geooutsidearea
  - geopassthru
  - indexof
  - integer
  - isblank
  - isholiday
  - isnum
  - istext
  - isweekday
  - isweekend
  - large
  - list2vars
  - lower
  - max
  - min
  - mod
  - mode
  - mround
  - odd
  - parse
  - past
  - percentile
  - power
  - proper
  - range
  - regex
  - replace
  - round
  - rounddown
  - roundup
  - sign
  - small
  - startswith
  - stdev
  - stringequals
  - stringindexof
  - stringlastindexof
  - stringlength
  - substring
  - sum
  - trim
  - truncate
  - upper
  - xpath
- Predefined Operators
  - contains
  - equalsSet
  - has
  - in
  - match
  - notMatch
  - search
  - unique
  - group by
  - distinct
  - unmatched
- Using the distinct, group by, and ummatched Filters
DRQL
Working with Rules
Working with Alerts
Setting Access Controls
Troubleshooting RulePoint Issues
Connecting to an Ultra Messaging Application
Creating an Ultra Messaging JMS Source

User Guide

6.1
- 6.2
- 6.1.2

Back Next

HTTP Response Properties

When you create an HTTP response, you enter the name and the configuration details for the response through the RulePoint user interface.

The following table describes the configuration properties of a HTTP response:

Property	Description
Name	Name of the response. The response name must be unique.
Description	Description of the response. The description is optional.
Responder Information	Name and description of the associated HTTP responder. You must create an HTTP responder before you create an HTTP response.
Content Type	(Optional) The HTTP character set and content type to be used. If left blank, the default is ISO-8859-1 for the character set, and text or plain for the Content Type. Ensure that the HTTP server to which you are connecting supports and accepts one or both. To set the content type, enter text or html, text or xml into the field. To set the content type and character set, use the following format: text/xml;charset=ISO-8850-1
Target URL	The URL of the object.
User Name	(Optional) The user name used to access the HTTP server.
Password	(Optional) The password associated with the user name used to access the HTTP server.
Method	The method that you want to perform on the object specified in the URL field.
Message Body	(Optional) If you post data using the content type multipart or mime-encoded, the form data. If you use the body parameter, it ignores any specified key-value parameter pairs.
Parameters	(Optional) A comma-delimited list of key-value pairs provided in the response. For example, symbol=XYZ, price=10 are key-value pairs.

Rename Saved Search

Table of Contents

User Guide

User Guide

HTTP Response Properties

HTTP Response Properties