MQ

 View Only

Upgrade IBM.XMS from 1.1.1.2 to 9.3.4.1

  • 1.  Upgrade IBM.XMS from 1.1.1.2 to 9.3.4.1

    Posted Wed April 03, 2024 01:41 PM
    Edited by Piper Wilson Wed April 03, 2024 07:02 PM

    Hello Everyone,

    Kindly suggest on following.

    Our application was using IBM.XMS version1.1.1.2 in our .Net Application to consume the MQ Messages.

    We were creating connection as following in order to connect with the Queue

    protected static IConnectionFactory CreateConnectionFactory()
            {
                IConnectionFactory cf;
                XMSFactoryFactory factoryFactory = XMSFactoryFactory.GetInstance(XMSC.CT_WMQ);
     
                cf = factoryFactory.CreateConnectionFactory();
                cf.SetStringProperty(XMSC.WMQ_HOST_NAME, WMQConfiguration.HostName);
                cf.SetIntProperty(XMSC.WMQ_PORT, WMQConfiguration.PortNo);
                cf.SetIntProperty(XMSC.WMQ_CONNECTION_MODE, 1);
                cf.SetStringProperty(XMSC.WMQ_QUEUE_MANAGER, WMQConfiguration.QueueManager);
                cf.SetIntProperty(XMSC.WMQ_BROKER_VERSION, 0);
                cf.SetStringProperty(XMSC.JMS_IBM_MSGTYPE, "bytes");
                cf.SetStringProperty(XMSC.WMQ_CHANNEL, WMQConfiguration.Channel);
                cf.SetStringProperty(XMSC.CLIENT_ID, WMQConfiguration.ClientID);
                cf.SetStringProperty(XMSC.WMQ_BROKER_PUBQ, WMQConfiguration.Stream);          
                return (cf);
            }
    However, upon upgrading to IBM.XMS version 9.3.4.1, the application stopped working and started giving error:
    System.ArgumentNullExceptionValue cannot be nullParameter namedest
    In order to get the component able to connect with MQ successfully, we needed to change the connection mode (to WMQ_CM_CLIENT_UNMANAGED) as following:
     cf.SetIntProperty(XMSC.WMQ_CONNECTION_MODE, XMSC.WMQ_CM_CLIENT_UNMANAGED);
    Now, despite we are able to connect and consume the messages, we observed, earlier version (1.1.1.2) was creating connection as JMS (in the subscription name) but the newer version (9.3.4.1) is creating connection as XMS. Unsure of its hidden implication.
    Can you please suggest, is it  the expected with this version.
    Also, if this may have any issue down the line. And, if there is any issue, what other change should we make to mitigate?



    ------------------------------
    Puneet Sharma
    ------------------------------