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.2
- 6.2
- 6.1

Back Next

Ultra Messaging Connection

The Ultra Messaging (UM) connection in RulePoint needs access to the configuration file in the Ultra Messaging application so that RulePoint communicates with the Ultra Messaging application.

When you create a UM connection, you enter the LBM file name and configuration details for the connection through the RulePoint user interface. UM configuration options defined in the LBM configuration files determine how the UM components and RulePoint read and write messages.

The following table describes the configuration properties for a UM connection:

Property	Description
Name	Name of the connection. The connection name must be unique.
Description	Optional. Description of the connection.
Type	Type of connection. Select Ultra Messaging Connection .
LBM Configuration File	The name of the LBM configuration file lbm.cfg in the UM sending and receiving application. The source and responder use the configuration file to read and write UM messages. You need to add the LBM configuration file in the following RulePoint installation directory path: RULEPOINT_HOME/service-conf . The LBM file contains the UM properties based on the type of UM edition used. The UM configuration file requires the following properties: UMS. resolver_unicast_daemon config UMP. ume_store config and resolver_unicast_daemon UMQ. umq_queue_name config and resolver_unicast_daemon The lbm.cfg file also contains the lbm configuration parameters that are bound to the scope, that is, context, source, or receiver. You can override the values in the lbm.cfg file by defining your own parameters and options. The following configurations are examples of properties that an LBM file contains: Host name of the LBMRD server to which the UM service connects. The LBMRD port number. The UM multicast interface address that the transmitter uses to send the outbound messages. Late join configuration, which enables the messaging receiver to get previously sent data from the transmitter's history buffer. With late join, the source stores sent messages according to its Late Join configuration options so that a joining receiver can receive any of these messages that were sent before it joined the group. Explicit ACK configurations that enable the receiver to send explicit acknowledgments to the transmitter, and acknowledges the receipt of a sent message. For information on configuration file samples for each of the UM source editions, see the Appendix.
LBM Context Parameters	The parameters used for overriding the configuration options provided in the LBM configuration file. You can also add the configuration options in the configuration file without modifying the file. The parameters of the LBMRD context defined in the lbm.cfg file. You can override the configuration options that are of the context scope, or define new configuration options in the lbm.cfg file. Use the following pattern to configure the LBMRD context parameters: [context option_name option_value] where: context 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.

Rename Saved Search

Table of Contents

User Guide

User Guide

Ultra Messaging Connection

Ultra Messaging Connection