Connectivity facts between IBM WebSphere MQ 7.0 and new JMS adapter on PI 7.1 EHP1
Here we are mainly concentrating on the new aspects of PI 7.1 EHP1.
1. Introduction of new feature – ‘Create connection on demand’ with PI 7.1 EHP1
Till now with every communication of IBM WebSphere MQ and JMS adapter there was a TCP/IP connection established. IBM Websphere MQ, earlier called as MqSeries (version 6 and below) could not notify the JMS receiver channel that the TCP/IP connection is still up and running. Hence CONNECTION_TEST_POLL feature was used for reconnection which would initiate another TCP/IP connection for the same JMS receiver channel. This would result in large set of TCP/IP connections for each JMS receiver channel.
But now with the JMS adapter in PI 7.1 EHP1 a new feature ‘Create connection on Demand’ is introduced. The purpose of this feature is to create the connection to the IBM Websphere MQ on demand basis. It takes a keep alive time parameter which sets the connection for a specified period of time in seconds. This means that the connection opens for a time specified and closes after that. Incase, another message arrives on the same connection, then the connection will remain open for the amount of time left from the keep-alive parameter.
For eg : In the figure below, if you observe the keep alive time parameter is set for 20 seconds. Here the TCP/IP connection will open once the message is received from JMS receiver channel and will remain open for 20 seconds. By default the keep-alive parameter value is 0 which indicates the connection opens once the message is received from the channel and closes after that.
Note: Refer sapnote 0001305390 for more information.
2. Usage of username and password between IBM MQ 7.0 and PI
We did a couple of tests with IBM WebSphere MQ 7.0 and PI 7.11 and realised that now with the higher version of MQ it is mandatory to provide the username/password in the PI communication channels. The connection between the PI and the MQ Queue Manager is established using the username and password mentioned in the sender channel. Similary on the receiver side, the username is required for authenticating the PI message before entering the MQ server.
In order to omit userid/password, MQ configuration will need to be done.