JMS Object Array Input Adapter

Adapter type: jms_objarray_in. The JMS Object Array Input adapter subscribes to messages formatted as arrays of Java objects from a JMS queue or topic, and writes these messages as stream records.

Note A null element in the array generates a null value for the corresponding column.

Ensure that stream column types correspond to Java classes as follows:

Stream Column Type	Java Class
`bigdatetime`	`java.lang.Double`
`binary`	`java.lang.String`
`boolean`	`java.lang.Boolean`
`integer`	`java.lang.Integer`
`interval`	`java.lang.Long`
`seconddate`	`java.util.Date`
`float`	`java.lang.Double`
`long`	`java.lang.Long`
`money1`	`java.math.BigDecimal`
`money2`	`java.math.BigDecimal`
`money3`	`java.math.BigDecimal`
`money4`	`java.math.BigDecimal`
`money5`	`java.math.BigDecimal`
`money6`	`java.math.BigDecimal`
`money7`	`java.math.BigDecimal`
`money8`	`java.math.BigDecimal`
`money9`	`java.math.BigDecimal`
`money10`	`java.math.BigDecimal`
`money11`	`java.math.BigDecimal`
`money12`	`java.math.BigDecimal`
`money13`	`java.math.BigDecimal`
`money14`	`java.math.BigDecimal`
`money15`	`java.math.BigDecimal`
`string`	`java.lang.String`
`msdate`	`java.util.Date`

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

Property Label	Description
Connection Factory	Property ID: connectionFactory Type: `string` (Required for adapter operation and schema discovery) Specifies the JNDI name for the JMS server connection factory. Consult your third-party vendor documentation for specific formats. Here are some examples: ActiveMQ™ ConnectionFactory TIBCO QueueConnectionFactory WebSphere MQ MyMQConnFactory The default value is ConnectionFactory.
JNDI Context Factory	Property ID: jndiContextFactory Type: `string` (Required for adapter operation and schema discovery) 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 The default value is org.apache.activemq.jndi.ActiveMQInitialContextFactory.
JNDI URL	Property ID: jndiURL Type: `string` (Required for adapter operation and schema discovery) 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. The default value is tcp://localhost:61616.
Destination Type	Property ID: destinationType Type: `choice` (Required for adapter operation and schema discovery) Destination type. Valid values are: QUEUE TOPIC Default value is QUEUE.
Destination Name	Property ID: destinationName Type: `string` (Required for adapter operation and schema discovery) Destination name. The default value is xmlout.queue.
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` (Required if subscription mode is set to DURABLE) Specifies the client identifier for a JMS client. Required for creating a durable subscription in JMS. Can be any string, but must be unique for each topic. No default value.
Subscription Name	Property ID: subscriptionName Type: `string` (Required if subscription mode is set to DURABLE) Specifies a unique name identifying a durable subscription. Required for creating a durable subscription in JMS. Can be any string, but must be unique within a given client ID. 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.
Stream Name Opcode Expected	Property ID: expectStreamNameOpcode Type: `boolean` (Advanced) If true, the first two fields in CSV records are interpreted as stream name, and opcode. Default value is false .

Known limitations:

If the connection to the message broker is lost, the adapter does not attempt to reconnect.