JMS FIX Input Adapter

Adapter type: jms_fix_in. The JMS FIX Input adapter subscribes to messages from a JMS queue or topic, and writes these messages as stream records.

Each stream hosts FIX messages of a certain type. The adapter discards messages of any other FIX type. Most FIX fields are stored in the same order in stream columns however these fields can be stored in a different order:

BeginString
BodyLength
MsgType
CheckSum

If you use the CCL ATTACH ADAPTER statement to attach an adapter, you must supply the adapter type.

Property Label	Description
FIX Version	Property ID: fixVersion Type: `choice` (Required) FIX Version. Valid values are: 4.2 4.3 4.4 5.0 Default value is 4.2.
FIX Message Type	Property ID: fixMessageType Type: `string` (Required) FIX Message type. No default value.
Connection Factory	Property ID: connectionFactory Type: `string` (Required) Connection factory class name. Consult your third-party vendor documentation for specific formats. Here are some examples: ActiveMQ – ConnectionFactory TIBCO – QueueConnectionFactory WebSphere MQ – MyMQConnFactory No default value.
JNDI Context Factory	Property ID: jndiContextFactory Type: `string` (Required) Context factory for JNDI context initialization. Consult your third-party vendor documentation for specific formats. Here are some examples: ActiveMQ – org.apache.activemq.jndi.ActiveMQInitialContextFactory TIBCO – com.tibco.tibjms.naming.TibjmsInitialContextFactory WebSphere MQ – com.sun.jndi.fscontext.RefFSContextFactory No default value.
JNDI URL	Property ID: jndiURL Type: `string` (Required) 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. No default value. .
Destination Type	Property ID: destinationType Type: `choice` (Required) Destination type. Valid values are: QUEUE TOPIC Default value is QUEUE.
Destination Name	Property ID: destinationName Type: `string` (Required) Destination name. No default value.
Subscription Mode	Property ID: subscriptionMode Type: `choice` (Optional) Specifies the subscription mode for TOPIC. Default value is NONDURABLE. Valid values are DURABLE and NONDURABLE.
Client ID	Property ID: clientID Type: `string` (Optional) Specifies the client identifier for a JMS client. Required for creating a durable subscription. No default value.
Subscription Name	Property ID: subscriptionName Type: `string` (Optional) Specifies a unique name identifying a durable subscription. No default value.
Batch Size	Property ID: batchsize Type: `uint` (Optional) Specifies number of records in a batch to commit in durable subscription mode. Default value is 1.
PropertySet	Property ID: propertyset Type: `string` (Advanced) Specifies the name of the property set. Property sets are reusable sets of properties that are stored in the project configuration file. Using these sets allows you to move adapter configuration properties out of the CCL file and into the CCR file. If you specify the same properties in the project configuration file and the ATTACH ADAPTER statement, the values in the property set override the values defined in the ATTACH ADAPTER statement. No default value.
Date Format	Property ID: dateFormat Type: `string` (Advanced) Date format. Default value is YYYY-MM-DDTHH:MM:SS.SSS.
Timestamp Format	Property ID: timestampFormat Type: `string` (Advanced) Timestamp format. Default value is YYYY-MM-DDTHH:MM:SS.SSS .

Known limitations:

This adapter is not a full FIX engine.
Supports only FIX versions 4.2, 4.3, 4.4, and 5.0.
Repeating groups and components are not supported.
If the connection to the message broker is lost, the adapter does not attempt to reconnect.
Supports only INSERT opcode.