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

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

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

Property	Description
Name	Name of the source. The source name must be unique.
Description	Optional. The description of the service. Make the description intuitive so that other users can relate to the use of this service.
Type	Type of source. Select JMS Source .
Connection	Select the connection name to which you want to associate the source. You must create a JMS connection before you create a JMS source.
JMS Destination	Name of the Queue or Topic on the JMS Provider (as defined in the JMS Connection Factory created by the JMS Administrator) from where RulePoint will receive JMS messages, (e.g. 'QueueA' or 'topic/SalesSystemsTopic'). Use 'topic/' prefix to specify a Topic
Client ID	Client identifier to identify the connection.
Subscription Name	Durable subscription name. Durable subscriptions can receive messages sent while the subscribers are not active. Durable subscriptions provide the flexibility and reliability of queues, but still allow clients to send messages to many recipients.
Acknowledgement Mode	Specifies the acknowledgement mode for non-transacted sessions. Following are the three modes: Auto Acknowledge - The session automatically acknowledges a client's receipt of a message either when the client has successfully returned. Client Acknowledge - A client acknowledges a message by calling the message's acknowledge method (Needs subscription name to be supplied). Duplicates OK, Acknowledge - This option instructs the session to lazily acknowledge the delivery of messages. Note:- When using Client Acknowledge mode source HA needs to enabled.
JMS Message Selector	Optional. Criteria for filtering message header or message properties, to limit which JMS messages RulePoint receives.
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.