[V9.0.5 Mar 2018][AIX][Windows][z/OS][Linux]

IBM MQ 9.0.5 changes from earlier versions of IBM MQ

Changes in IBM® MQ 9.0.5 to functions and resources from earlier versions of IBM MQ are described in this section.

Review this information if you are moving from Long Term Support to Continuous Delivery, or if you are moving to IBM MQ 9.0.5 from an earlier Continuous Delivery release.

For additional information about system requirements for IBM MQ 9.0, see the System Requirements for IBM MQ 9.0 web page. You can use the Software Product Compatibility Reports (SPCR) tool to find information on supported operating systems, system requirements, prerequisites, and optional supported software. The web page includes more information about the SPCR tool and links to reports for each supported platform.

Removal of JSON4J.jar file and com.ibm.msg.client.mqlight package

The JSON4J.jar file and com.ibm.msg.client.mqlight package are not needed by the IBM MQ classes for Java and IBM MQ classes for JMS, therefore the following changes are made from IBM MQ 9.0.5:
  • The JSON4J.jar file is removed from the V.R.M.F-WS-MQ-Install-Java-All.jar file, where V.R.M.F is the product version number, for example 9.0.5.0.
  • The reference to JSON4J.jar file is removed from the class path statement within the manifest file for the com.ibm.mq.allclient.jar file.
  • The package com.ibm.msg.client.mqlight is no longer included inside the com.ibm.mq.allclient.jar file.

See Installing the IBM MQ classes for JMS separately, What is installed for IBM MQ classes for JMS, and What is installed for IBM MQ classes for Java.

Additional permission for java.security.policy file

From IBM MQ 9.0.5, if your Java application uses the Java security manager, you must add a RuntimePermission to the java.security.policy file, otherwise, exceptions will be thrown to the application. This RuntimePermission is required by the client as part of managing the assignment and closure of multiplexed conversations over TCP/IP connections to queue managers.

For more information, see Running IBM MQ classes for Java applications under the Java security manager.

New attribute to allow TLS v1.0 to be optionally disabled on a queue manager

From IBM MQ 9.0.5, a new attribute is available in the qm.ini file, under the SSL stanza:
SSL:
   AllowTLSV1=NO
If this attribute is set in the qm.ini file before the queue manager is started, the queue manager does not accept inbound connections using the TLS v1.0 protocol. Similarly, if an LDAP connection is configured using an AUTHINFO object, only TLS 1.2 is used to communicate with the LDAP server if secure communication is enabled for the AUTHINFO object.

Alternatively, the AMQ_TLS_V1_DISABLE environment variable can be set for the environment used to start the queue manager, listener, and channel processes.

If either property is set, as well as disallowing TLS 1.0 connection attempts at the network layer, the queue manager's command server also rejects attempts to define or alter a channel definition to use a TLS 1.0 CipherSpec.

The default queue manager behavior is unchanged, such that TLS 1.0 connections continue to be accepted if the new attribute or environment variable is not set.

Enhancements to runmqras utility

From IBM MQ 9.0.5, the following enhancements are made to the runmqras utility:
  • [Solaris][AIX][Linux]Environment variable information is retrieved by default.
  • [UNIX, Linux, Windows, IBM i]Queue manager data directory listings are retrieved by default.
  • [UNIX, Linux, Windows, IBM i]A leak section is added to the runmqras command to gather IBM MQ process resource usage information.

For more information, see runmqras (collect IBM MQ diagnostic information).

Change to output of fteDisplayVersion -v command

From IBM MQ 9.0.5, IBM MQ Light Service for Bluemix® JMS Provider is removed from the output of fteDisplayVersion -v command. Following this removal, you should review any automation that is based on the output from the fteDisplayVersion command.