Name of the source. The source name must be unique.

Optional. The description of the service. Make the description intuitive so that other users can relate to the use of this service.

Type of source. Select

JMS Source

.

Select the connection name to which you want to associate the source. You must create a JMS connection before you create a JMS source.

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 identifier to identify the connection.

Durable subscription name.

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.

Optional. Criteria for filtering message header or message properties, to limit which JMS messages RulePoint receives.

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.

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.