What's new and changed in Version 8.0.0, Fix Pack 3
Changes to functions and resources in IBM® MQ 8.0.0, Fix Pack 3 are described in this section.
- Security: PAM authentication
- Deprecated CipherSpecs
- Serviceability enhancements for Managed File Transfer
- Support for MQTT Version 3.1.1 Oasis standard
- IBM MQ Virtual System Pattern Type
Security: PAM authentication
From Version 8.0.0, Fix Pack 3, you can use the Pluggable Authentication Method (PAM) on UNIX and Linux® platforms.
For more information, see Using the Pluggable Authentication Method.
Deprecated CipherSpecs
From Version 8.0.0, Fix Pack 3, the following CipherSpecs are
deprecated:
- RC2_MD5_EXPORT
- RC4_MD5_EXPORT
- RC4_MD5_US
- RC4_SHA_US
- RC4_56_SHA_EXPORT1024
- TLS_RSA_EXPORT_WITH_RC2_40_MD5
- TLS_RSA_EXPORT_WITH_RC4_40_MD5
- TLS_RSA_WITH_RC4_128_MD5
- ECDHE_ECDSA_RC4_128_SHA256
- ECDHE_RSA_RC4_128_SHA256
- TLS_RSA_WITH_NULL_SHA256
- TLS_RSA_WITH_RC4_128_SHA256
Serviceability enhancements for Managed File Transfer
From Version 8.0.0, Fix Pack 3, the following changes have been made
for Managed File Transfer:
- The default value for of the commandMessagePriority property in the installation.properties file has changed to 8. For more information, see installation.properties file.
- The default value for of the logTransferRecovery property in the agent.properties file has changed to true. For more information, see agent.properties file.
- A first failure data capture (FDC) is generated if an agent encounters an unrecoverable error.
Support for MQTT Version 3.1.1 Oasis standard
From Version 8.0.0, Fix Pack 3 you can set the MQTT channel to use the Oasis MQTT Version 3.1.1 client protocol. For more information, see IBM MQ Telemetry Transport format and protocol.
IBM MQ Virtual System Pattern Type
From Version 8.0.0, Fix Pack 3, you can add IBM MQ Multi-Instance support using different virtual machines in your pattern. For more information, see Adding IBM MQ Multi-Instance support.