Select the objects and properties that you want to change for the JMSProviders configurable service.
For JMSProviders configurable services, you must stop and start the integration server for a change of property value to take effect.
Supplied configurable services that are created for each broker | Properties for each configurable service that is defined | Description of properties |
---|---|---|
ActiveMQ |
clientAckBatchSize |
This property is optional. Set this property to configure JMS message flows to send a batch acknowledgment of non-transactional messages that have been received. The value of this property is an integer that represents the threshold number of messages received before the batch acknowledgment is sent. This property can be used in combination with the clientAckBatchTime property. If both properties are set, and the time interval set on clientAckBatchTime has expired, the batch acknowledgment is sent even if the clientAckBatchSize threshold for the number of received messages has not been reached. A
batch acknowledgment is also sent when:
The minimum non-zero value is 2. To disable batch acknowledgment, set clientAckBatchSize to 0 and ensure that clientAckBatchTime is set to 0. |
clientAckBatchTime |
This property is optional. Set this property to configure JMS message flows to send a batch acknowledgment of non-transactional messages that have been received. The value of this property is an integer that represents the length, in milliseconds, of a repeating interval. At the end of each interval a batch acknowledgment is sent for all unacknowledged non-transactional JMS messages that were received during the preceding interval. This property can be used in combination with the clientAckBatchSize property. If both properties are set, and the threshold set on clientAckBatchSize is reached, the batch acknowledgment is sent even if the time interval specified by clientAckBatchTime has not yet expired. A
batch acknowledgment is also sent when:
To disable batch acknowledgment, set clientAckBatchTime to 0 and ensure that clientAckBatchSize is set to 0. |
|
connectionFactoryName |
This property is optional. The name of the connection factory that is used to create a connection to the JMS provider. If this property is set it overrides the property on a node that uses this JMS Provider, but can be overridden using a local environment override. If you require additional security, you must set this property. See Securing JMS connections and JNDI lookups |
|
initialContextFactory |
This property is optional. The fully qualified class name of the class used to perform JNDI lookups. If set it overrides the property set on a node that uses this JMS Provider. If you require additional security, you must set this property. See Securing JMS connections and JNDI lookups |
|
jarsURL |
A URL that specifies the file location of the JMS provider JAR files. Omit file:// from the URL. If you do not set the -n parameter on the mqsicreateconfigurableservice command, the default location for the JMS provider JAR files is the broker shared-classes directories. To connect to different versions of the same JMS provider (for example, JBoss), create a JMSProviders configurable service for each version of the JMS provider, then set the jarsURL property to a unique path. |
|
jmsAsyncExceptionHandling |
This property is optional. If you set this property to true, the broker registers an exception listener on the JMS connection when the connection is created, and handles connection exceptions asynchronously from the main flow. When this parameter is set to true, the broker can detect when the connection has been broken and can try to reconnect. By default, this parameter is set to false for all JMS providers except JBoss. |
|
jmsProviderXASupport |
This property is optional. If you set this property to true, it indicates that the selected JMS provider does support XA coordinated transactions. If you set this property to false, it indicates that the selected JMS Provider does not support XA coordinated transactions. See Configuring JMS and SOAP nodes to support XA coordinated transactions. The default value for this property is true. If you set this property to true, and the selected JMS provider does not support XA transactions, an exception is raised. If you set this property to false, but the Transaction mode property on the node is set to Yes and the Coordinated Transaction message flow property is selected, an exception is raised. |
|
jndiBindingsLocation |
This property is optional. The location used to look up JNDI Administered objects such as Connection Factories and Destinations. If set, this property overrides the property set on a node that uses this JMS Provider. |
|
jndiEnvironmentObject |
This property is optional. This property enables you to define an object that can be used for JNDI administered objects. The format of this property is:
where <object type> is java.util.Vector and <name of object env> is the name that is given to the vector. For example:
The string values for the vector are defined in the jndiEnvironmentObjectParm1-5 property. |
|
jndiEnvironmentObjectParm1-5 |
This property is optional. This property enables you to define the values that are added to the vector that is specified in the jndiEnvironmentObject property. |
|
jndiEnvironmentParms |
This property is optional. A list of JNDI environment parameters expressed as name-value pairs separated by semicolons. Use these parameters in JMSInput, JMSOutput, and JMSReply nodes. |
|
nativeLibs |
The file location of any libraries that the JMS provider owns. If you do not set the -n parameter on the mqsicreateconfigurableservice command, the default location for any libraries that the JMS provider owns, is the broker LILPATH. |
|
proprietaryAPIHandler |
The name of the IBM® supplied Java™ class to interface with a proprietary API of a JMS provider. |
|
proprietaryAPIAttr1 |
These attributes are optional. If you configure these attributes, they might be used on one or more method calls to the vendor proprietary API. The usage of these attributes is specific to a vendor interface and their meaning is determined by the IBM proprietary API Handler. |