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 Source Properties

When you create an Ultra Messaging (UM) source, you enter the name and the configuration details of the source through the RulePoint user interface.

The following table describes the configuration properties of a UM source:

Property	Description
Name	Name of the UM source. The source name must be unique.
Description	(Optional) The description of the source. Provide a description that is intuitive so that all users can relate to the use of this service .
Type	The type of source. Select Ultra Messaging Source .
Connection	Select the connection name to which you want to associate the source. You must create a UM connection before you create a UM source.
Topic	The configured topic to which you want RulePoint to publish the events. Select the topic name that corresponds to the source.
Message Type	The message type. It can be Text (String) or Byte Array, or LBM Properties. If you set the message type as Text or Byte Array, the Ultra Messaging Source reads the message on the UM topic and publishes it as the value of the event property "ummsg." If you set the message type as LBM properties, the Ultra Messaging Source reads information from the message headers and publishes them as event properties. The ummsg property is set as an empty byte array of size 1.
Source Topic	The name of the external UM topic configured in the UM sending application.
Session ID	The UM TCP session ID, which is a 64-bit value. You need to set the session ID for the UM source which is the similar to the session ID in the UM sending application. The session ID uniquely identifies the following UM sources and receivers with unique topics: If you are using a UMP source, the store uses the session ID to identify all the sources and receivers for a particular application. If you are using a UMQ source, the queue uses the session ID defined in the UM connection to identify each partition uniquely and to ensure that the queue delivers messages only once. If you are using a UMS source, the data stream uses the session ID of the receiver to receive messages from the UMS source with the same session ID. If you want to disable the session ID, set the value to -1.
Receiver Parameters	The configuration parameters of a UM receiving application. You can configure receiver parameters for a UM source to override the receiver parameters on which the UM runs. You can also define the receiver or context scopes for the configuration parameters in the lbm.cfg file. You define an option to assign values to an object's attributes. Use the following pattern to configure the receiver parameters: [receiver option_name option_value] where: receiver 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 that option.
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 Source Properties

Ultra Messaging Source Properties