What's new and changed in Version 8.0.0, Fix Pack 2

Support for Linux on POWER Systems - Little Endian

Security: LDAP authorization

From Version 8.0.0, Fix Pack 2, you can use an LDAP repository for authorization, without the need for a local operating system ID.

For more information, see Overview of LDAP authorization.

Deprecated CipherSpecs

IBM MQ C++ client libraries built by using Microsoft Visual Studio 2005

The IBM MQ 8.0 C++ client provides an object-oriented application programming interface (API) for developing messaging applications in the C++ language. The IBM MQ 8.0 C++ libraries are built with Microsoft Visual Studio 2012 C++ compiler. The IBM MQ C++ libraries that are built with the Microsoft Visual Studio 2012 compiler are not compatible with IBM MQ C++ applications that are developed by using releases of IBM WebSphere® MQ before IBM MQ 8.0 C++ libraries. This is because the Microsoft Visual Studio 2012 C++ standard libraries are not backwards compatible.

From Version 8.0.0, Fix Pack 2, IBM MQ provides C++ client libraries that are built with the Microsoft Visual Studio 2005 C++ compiler. These libraries are provided in addition to the existing IBM MQ 8.0 C++ libraries that are built with the Microsoft Visual Studio 2012 C++ compiler. Applications that are built by using a release of IBM MQ earlier than Version 8.0 can make use of these libraries since the libraries are compatible with earlier versions. For more information, see Building C++ programs on Windows.

For information about using IBM MQ C++ compiled with Microsoft Visual Studio 2012 and Microsoft Visual Studio 2005 on the same machine, see Differently named IBM MQ C++ libraries.

Stand-alone IBM MQ.NET client

From Version 8.0.0, Fix Pack 2, the IBM MQ.NET client gives you the ability to package and deploy an assembly without requiring the full IBM MQ client installation on production systems for running your applications. You can build your IBM MQ.NET applications on a machine where the full IBM MQ client is installed and later package the IBM MQ.NET assembly, that is, amqmdnet.dll, along with your application and deploy on production systems. The applications can be the traditional Windows.NET applications, Services, or Microsoft Azure Web/Worker applications that are running in an Azure PaaS environment.

In such deployments, the IBM MQ.NET client supports only managed mode connectivity to a queue manager. The server bindings and unmanaged client mode connectivity are not available as these two modes require a full MQ LightIBM MQ client installation. For more information, see Using the stand-alone IBM MQ.NET client.

IBM MQ Virtual System Pattern Type

IBM MQ Virtual System Pattern Type for IBM PureApplication® System (referred to in this documentation as IBM MQ Virtual System Pattern Type) contains an IBM MQ plugin (the virtual system software component) and associated script packages, which you can use to create a virtual system patterns for your IBM MQ environment. For more information, see Overview of IBM MQ Virtual System Pattern Type.

IBM MQ classes for JMS in a CICS OSGi JVM server

Version 8.0.0, Fix Pack 2 adds support for using the IBM MQ classes for JMS in certain versions of the CICS® Open Services Gateway initiative (OSGi) Java Virtual Machine (JVM) server.

For more information, see Using IBM MQ classes for JMS in a CICS OSGi JVM server

JMS Exception listener changes

From Version 8.0.0, Fix Pack 2, by default, IBM MQ classes for JMS delivers an exception to the exception listener only when a connection is broken. This behavior is consistent with the JMS specification. For IBM MQ classes for JMS to inform the exception listener of all exceptions, your application must set the ASYNCEXCEPTION property of the connection factory to ASYNC_EXCEPTIONS_ALL.