What's new and changed in release 9.3.0

This topic describes new and changed features in version 9.3.0 of the appliance firmware.

Features that are new to continuous delivery users are identified by a light blue version flag, features that are new to long term service users are identified by a dark blue version flag.

Features new to CD and LTS users

The following features are new at version 9.3.0 to both continuous delivery (CD) and long term service (LTS) users of the IBM® MQ Appliance.

The following features are new for version 9.3.0:

Features new to LTS users

The following features are new at version 9.3.0 to long term service (LTS) users of the IBM MQ Appliance. (The features have been available to CD users in version 9.2.X CD releases.)

  • You can now choose synchronous communication for disaster recovery replication links. See Configuring queue managers for disaster recovery by using the command line and IBM MQ Console: Setting up disaster recovery - CD only.
  • You can now retrieve the crtdrsecondary command used when creating a disaster recovery configuration by issuing the new dspdrsecondary command. See Replacing a failed node in a disaster recovery configuration and dspdrsecondary.
  • You can now suppress the re-creation of DSA SSH host keys when you reset SSH keys, see reset-ssh-keys.
  • You can use the Application quick start feature in the Web Console to quickly and easily set up a messaging configuration with an application. See Quick tour of the IBM MQ Console - CD only.
  • You can discover whether there are any failed resource actions for a high availability queue manager, and clear them if necessary, see Failed resource actions.
  • You can process dead letter queues on the appliance by using client connection facilities in IBM MQ. See Processing dead-letter queues.
  • Failed resource actions for high availability configurations can now be viewed in the IBM MQ Console, see Failed resource actions.
  • You can now retrieve appliance high availability and disaster recovery attributes using the IBM MQ REST API. See /admin/qmgr GET in the main IBM MQ documentation.
  • You can now use encrypted file systems to protect data on the RAID (SSD) storage, see File system encryption. Support for encrypted file systems includes the following changes:
    • New parameters have been added to the crtmqm, createbackupfs, and mqrestore commands to specify that an encrypted file system is to be created. See crtmqm, createbackupfs, and mqrestore.
    • New dspfspass and setfspass commands have been added to manage encrypted file system passphrases, and to convert an IBM MQ system volume to have an encrypted or decrypted file system. See dspfspass and setfspass.
    • An optional parameter has been added to the mqrestore command to specify a custom size for the restored queue manager's file system. See mqrestore.
    • The status command has been updated to report additional file system information, and the format of the file system and memory usage information output by the status command has been revised. See status.
    • The dspmq command and its equivalent /ibmmq/rest/v2/admin/qmgr?attributes=extended REST URI have been updated to report whether the file system for each queue manager is encrypted. See dspmq and /ibmmq/rest/v2/admin/qmgr?attributes=extended.
    • The show qm-status command and its equivalent /mgmt/status/default/QueueManagersStatus REST URI have been updated to report whether the file system for each queue manager is encrypted. See show qm-status and /mgmt/status/default/QueueManagersStatus.
    • The show mq-resources command has been updated to report additional information about MQ system file systems. The REST URI for this command has changed from /mgmt/status/default/MQSystemResources to /mgmt/status/default/MQSystemResources2. The previous REST URI is available, but is now deprecated. See show mq-resources and /mgmt/status/default/MQSystemResources2.