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

Ultra Messaging Responder Properties

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

The following table describes the configuration properties of an UM responder:

Property	Description
Name	Name of the responder. The responder name must be unique.
Description	Optional. Description of the responder.
Type	The responder type. Select Ultra Messaging Responder .
Connection	The type of connection to connect to the UM responder. Select umconnection .
Message Type	The intended message type. It can be Text (String), Byte Array, or LBM Message Properties.
Message Body	The body of the UM message that the responder sends on the configured external UM topic. The message type can be a text (string) of byte array, or the LBM properties: If you set the message type as Text or Byte Array, the Ultra Messaging Responder publishes the message on the destination UM topic and publishes it as the value of the response property "ummsg." If you set the message type as LBM Properties, the Ultra Messaging Responder writes response properties as Ultra Messaging message headers and sends them as message properties. The "ummsg" message property sets as an empty byte array of size 1.
Destination Topic	Name of the topic on the UM receiving application that receives the processed UM native messages.
Session ID	Enter a UM session ID, which is a 64-bit value to identify the UM receiver. The session ID is unique and must be the same for the UM source and the receiver. Default is -1. In this case, any receiver can receive the messages from the configured UM topics.
Source Parameters	The configuration parameters of the source defined in the lbm.cfg file. You can override the configuration parameters in the source type by specifying the options. Use the following pattern to enter the source parameters: [source option_name option_value] where: source is the scope to which the option applies. option_name is the predefined name for the option. option_value is the value that you want to assign to the option. If you have multiple source parameters, place each parameter on a separate line.
Marshaller Class Name	Class name of the marshaller. The marshaller class is responsible for converting or enriching the source event properties. It must include the full class name including the classpath. You must add the jar containing this class into the RulePoint library.
Marshaller Properties	Properties of the marshaller. You must pass the properties as key value pairs, separated by a comma, to the marshaller class. For example, property1=value1,property2=value2 .

Rename Saved Search

Table of Contents

User Guide

User Guide

Ultra Messaging Responder Properties

Ultra Messaging Responder Properties