connection ibmmq
The IBMMQ connection creates a (shared) connection to a IBMMQ broker (formerly WebsphereMQ).
- url: The url for the MQ server
- queuemanager: Queue Manager Name
- channel: Channel Name
A comma-separated list of host and port information which can be used to connect to a multi-instance queue manager. The format of the list is:
host[(port)],[host[(port)]]
The port is optional and defaults to 1414 if it is not set.
Example: 127.0.0.1(1414),host2.example.com(1400) The default setting of this property is 'localhost(1414)'
- username: User allowed to connect to MQ
- password: Password for the user
- channelreceiveexit: Class name of a receive exit
- channelreceiveexituserdata: Receive exit data
- channelsendexit: Class name of a send exit
- channelsendexituserdata: Send exit data
- channelsecurityexit: Class name of a security exit
- channelsecurityexituserdata: Security exit data
- appname: The application name on the connection factory
- clientid: The client identifier is used to uniquely identify the application connection for durable subscriptions
- reconnecttimeout: Interval in seconds before reconnection retries cease. The default is 1800 seconds (30 minutes).
- reconnectoptions: Options how to reconnect (Do not reconnect, Reconnect, Reconnect to the same queue manager)
- transporttype: Type of transport (default=0)
- pollinginterval: The interval between scans of all receivers during asynchronous message delivery.
- maxbuffersize: The maximum buffer size (integer)
- userauthenticationmqcp: true (MQCSP authentication mode) or false (Compatibility mode)
The default transporttype is 1 (CLIENTor WMQ_CM_CLIENT)
WMQ_CM_BINDINGS 0 WMQ_CM_CLIENT 1 WMQ_CM_DIRECT_TCPIP 2 WMQ_CM_DIRECT_HTTP 4 WMQ_CM_BINDINGS_THEN_CLIENT 8
BINDINGS
JNDI bindings are used to connect to the queue manager. BINDINGS is a shared memory protocol and can only be used when the queue manager is on the same node as the JMS client and poses security risks that must be addressed through the use of EJB roles.
CLIENT
IBM MQ client connection is used to connect to the queue manager. CLIENT is a typical TCP-based protocol.
DIRECT
For IBM MQ Event Broker using DIRECT mode. DIRECT is a lightweight sockets protocol used in nontransactional, nondurable, and nonpersistent Publish/Subscribe messaging. DIRECT only works for clients and message-driven beans using the non-ASF protocol.
SSL isn't supported yet.
- url: localhost: localhost(1416)
- queuemanager: QUEUE.MGR
- channel: MQ.Channel
- username: Administator
- password: ********
