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

JMS Connection

The JMS source service produces events by receiving messages from a JMS provider and publishing those messages as events. When a JMS Service object is initialized, it instantiates its own JMS Connection Factory.

When you create a JMS connection, you enter the name and the configuration details for the connection through the RulePoint user interface.

The following table describes the connection and configuration properties that you need to enter:

Property	Description
Name	Name of the connection. The connection name must be unique.
Description	Optional. Description of the connection.
Type	Type of connection. Select JMS Connection .
JNDI Context Factory	The JMS provider specific initial JNDI context factory implementation for connecting to the JNDI service. This value is a fully qualified class name of the Initial Context Factory. For example, the class name of the Initial Context Factory for ActiveMQ is org.apache.activemq.jndi.ActiveMQInitialContextFactory . Your must add the JMS Client jars to the RulePoint server. For more information, see the documentation of the JMS provider.
JNDI Package Prefixes	Optional. A colon-delimited list of package prefixes to use when loading URL context factories. These are the package prefixes for the name of the factory class that will create a URL context factory. For values, see the documentation of the JMS provider.
Connection URL	The location of the naming service and port on which to connect. For example, tcp://jndiserverA:61616
JMS Connection Factory	The name of the object in the JNDI server that enables the JMS Client to create JMS connections. For example, jms/QCF or jmsSalesSystem . The default value is ConnectionFactory . For more information about this configuration, see the documentation of the JMS server administrator.
User Name	Optional. Enter authentication user name if required.
Password	Optional. Enter password for the authentication user name.

Rename Saved Search

Table of Contents

User Guide

User Guide

JMS Connection

JMS Connection