Properties for messaging queues
If you are using IBM MQ, you must set the following parameters in the customer_overrides properties. IBM® Sterling B2B Integrator supports only IBM MQ (formerly IBM WebSphere MQ) as a messaging queue for communication between ASI node and Adapter container.
Important: You must install IBM MQ before you create the adapter containers. You must
also set the properties for IBM MQ before you create the adapter containers.
Note: When creating the JKS Keystore file, the Key password must be the same as the Keystore
password.
Parameter | Description | Mandatory or Optional |
---|---|---|
iwfcqueue.jms.vendor | The MQ vendor name. The default value is IBMMQ . |
Mandatory |
iwfcqueue.jms.connectionFactory.impl | For IBM MQ, specify the class that is used as the JMS connection factory. For example,
|
Mandatory |
iwfcqueue.jms.queueName | The name of the queue for the MQ vendor. | Mandatory |
iwfcqueue.jms.username | The MQ vendor user name. | Mandatory |
iwfcqueue.jms.password | The MQ vendor password. | Mandatory |
iwfcqueue.jms.host | The host name used for the JMS connection to the JMS server that holds the IWFC queue
jms.host=&JMS_HOST . |
Mandatory for single-node MQ |
iwfcqueue.jms.port | The port used for the JMS connection to the JMS server that holds the IWFC queue
jms.port=&JMS_PORT . |
Mandatory for single-node MQ |
iwfcqueue.jms.connectionNameList | The host and port information of Active and Standby queue manager in the following
format.
|
Mandatory for High-Available MQ (Multi-Instance) installation |
iwfcqueue.jms.channel | The MQ vendor server connection channel. This is applicable and required for IBMMQ (SVRCONN channel). | Mandatory |
iwfcqueue.jms.enableSSL | Set to true to enable the secure communication with the MQ using
SSL. |
Mandatory, if you want to enable SSL; else Optional |
iwfcqueue.jms.keyStorePath | The keystore JKS cert physical path. | Mandatory, if SSL is enabled; else Optional |
iwfcqueue.jms.keyStorePassword | The keystore cert password. | Mandatory, if SSL is enabled; else Optional |
iwfcqueue.jms.trustStorePath | The truststore JKS cert physical path. | Mandatory, if SSL is enabled; else Optional |
iwfcqueue.jms.trustStorePassword | The truststore cert password. | Mandatory, if SSL is enabled; else Optional |
iwfcqueue.jms.cipherSpec | MQ specific ciphersuite required to open the secure SSL channel. The following ciphersuites
are supported:
|
Mandatory, if SSL is enabled; else Optional |
iwfcqueue.jms.protocol | Default value is TLSv1.2 . Use TLS1.2 protocol for SSL communication. |
Mandatory, if SSL is enabled; else Optional |
Note: For a new AC node setup, the system adds the above properties automatically from the
customer_overrides.properties
file of the ASI node. If the above properties are not
included in the customer_overrides.properties
file of the ASI node, then you must
manually include them on both ASI and AC nodes.Here are some recommended values for the above IBM MQ
parameters:
/* Without SSL */
iwfcqueue.jms.vendor=IBMMQ
iwfcqueue.jms.connectionFactory.impl=com.ibm.mq.jms.MQQueueConnectionFactory
iwfcqueue.jms.queueName=B2BACQ
iwfcqueue.jms.username=mquser
iwfcqueue.jms.password=mqpassword
iwfcqueue.jms.host=b2b-mq-server
iwfcqueue.jms.port=1416
iwfcqueue.jms.connectionNameList=10.10.10.99(1416)
iwfcqueue.jms.channel=SYSTEM.DEF.SVRCONN
iwfcqueue.jms.enableSSL=false
/* With SSL */
iwfcqueue.jms.vendor=IBMMQ
iwfcqueue.jms.connectionFactory.impl=com.ibm.mq.jms.MQQueueConnectionFactory
iwfcqueue.jms.queueName=B2BACQ
iwfcqueue.jms.username=mquser
iwfcqueue.jms.password=mqpassword
iwfcqueue.jms.host=b2b-mq-server
iwfcqueue.jms.port=1416
iwfcqueue.jms.connectionNameList=10.10.10.99(1416)
iwfcqueue.jms.channel=SYSTEM.DEF.SVRCONN
iwfcqueue.jms.enableSSL=true
iwfcqueue.jms.keyStorePath=<install directory>/truststore.jks
iwfcqueue.jms.keyStorePassword=password
iwfcqueue.jms.trustStorePath=/opt/mraj/truststore.jks
iwfcqueue.jms.trustStorePassword=password
iwfcqueue.jms.cipherSpec=TLS_RSA_WITH_AES_256_CBC_SHA256
iwfcqueue.jms.protocol=TLSv1.2
Important: For IBM MQ user, you must set the required permissions for connecting to a
queue manager. For more information on how to grant access to a queue manager, see IBM MQ Documentation.