Show TOC

JMS Input Transporter Module ConfigurationLocate this document in the navigation structure

The JMS Input transporter receives JMS messages from a JMS server, and sends it to the next module that is configured in the adapter configuration file. Set values for this transporter in the adapter configuration file.

The transporter sends different Java objects to the next module if different messages are received:
Message Type Received Java Object to Send
TEXT (TextMessage) String
OBJARRAY (ObjectMessage) Object
MAP (MapMessage) String
XML Element Description
ConnectionFactory

Type: string

(Required) Specify the connection factory class name. No default value.

JndiContextFactory

Type: string

(Required) Specify the context factory for JNDI context initialization. No default value.

JndiUrl

Type: string

(Required) Specify the JNDI URL. Consult your third-party vendor documentation for specific formats. Here are some examples:

  • ActiveMQ tcp://server:61616
  • TIBCO tibjmsnaming://server:7222
  • WebSphere MQ file:/var/mqm/jndi/

WebSphere MQ is different as it requires a separate naming server to be configured with it. By default, WebSphere MQ only provides a file-based naming server.

You can also enable automatic reconnection here. Consult your third-party vendor documentation for specific formats. Here is an example for ActiveMQ, failover:tcp://<hostname>:<portnumber>.

No default value.

Destination Type

Type: string

(Required) Specify the destination type. Valid values are: QUEUE and TOPIC. The default value is QUEUE.

DestinationName

Type: string

(Required) Specify the destination name. No default value.

MessageType

Type: string

(Required) Specify the message type you want the JMS transporter to process:
  • TEXT – for receiving and sending messages in text string.
  • OBJARRAY – for receiving and sending messages in custom format.
  • MAP – for receiving and sending messages in sets of name-value pairs.
No default value.
SubscriptionMode

Type: string

(Optional) Specify the subscription mode for TOPIC (see the Destination Type element). Valid values are DURABLE and NONDURABLE.

Default value is NONDURABLE.

ScanDepth

Type: integer

(Optional) Specify the depth of the schema discovery. The adapter reads the number of rows specified by this element value when discovering the input data schema.

The default value is three.

ClientID

Type: string

(Required for DURABLE subscription mode) Specifies the client identifier for a JMS client. Can be any string, but must be unique for each topic. No default value.

Example: client1 .

SubscriptionName

Type: string

(Required for DURABLE subscription mode) Specifies a unique name identifying a durable subscription. Can be any string, but must be unique within a given client ID. No default value.

Example: subscription1.

Username

Type: string

(Advanced) Specify a valid username for connecting to a specific JMS server.

Password

Type: string

(Advanced) Specify a valid password for connecting to a specific JMS server. Contains an encrypted attribute which determines whether the Password value is encrypted.