+

Search Tips | Advanced Search

New Version 9.2.0 features for z/OS - Advanced and Advanced VUE entitlement

IBM MQ Version 9.2.0 delivers a number of new features and enhancements on z/OS that are available with Advanced or IBM MQ Advanced for z/OS Value Unit Edition entitlement and some that are available with IBM MQ Advanced for z/OS Value Unit Edition entitlement only.


Highly available Managed File Transfer agents

This feature is available with Advanced and Advanced VUE entitlement.

From Version 9.2.0, we can set up Managed File Transfer standard and bridge agents to be highly available. We can configure multiple instances of the same MFT agent on two or more servers in active and standby mode. If the active instance of the agent fails at any time, even when transfers are not in progress, another instance of the agent automatically starts up and enables file transfer to continue. This occurs, even in cases where one of the agents fails due to network issues, hardware issues, or any other reason that causes the agent to stop. For more information, see Highly available agents in IBM MQ Managed File Transfer.


Use of IBM Aspera fasp.io Gateway streaming for IBM MQ messages

This feature is available with Advanced VUE entitlement.

Queue managers can be configured so that IBM MQ system, application, and Managed File Transfer messages pass through an Aspera gateway to reach a destination using the Aspera FASP protocol in place of TCP/IP. For some use cases, this allows messages to move between destinations more rapidly than otherwise would be the case.

From Version 9.2.0, IBM MQ Advanced for z/OS VUE provides entitlement for using the IBM Aspera fasp.io Gateway.

An Aspera gateway is set up, under Linux or Windows, for use by sending and receiving queue managers. Each of these queue managers must be one of IBM MQ Advanced for z/OS VUE, IBM MQ Advanced for Multiplatforms, or IBM MQ Appliance queue managers. The gateway does not need to run on the same server as the queue manager, or on the IBM MQ Appliance.

For more information, see Defining an Aspera gateway connection on Linux or Windows.

Note that use of the Aspera gateway is limited to IBM MQ messages unless the gateway is separately entitled.


IBM MQ Bridge to blockchain Hyperledger Fabric support

This feature is available with Advanced VUE entitlement.

From Version 9.2.0, the IBM MQ Bridge to blockchain is updated to add support for Hyperledger Fabric for interaction between IBM MQ and the blockchain. This support replaces previous APIs that were used for connectivity. For more information, see Configure IBM MQ for use with blockchain.


Advanced Message Security interception on server-to-server message channels

This feature is available with Advanced and Advanced VUE entitlement.

Version 9.2.0 on IBM MQ for z/OS introduces AMS interception on server-to-server message channels. This feature allows you to support AMS and to communicate with business partners who do not support AMS by enabling you, for example, to decrypt outbound messages to a business partner who does not use AMS and to encrypt inbound messages from a business partner who does not use AMS. For more information, see Advanced Message Security interception on message channels and Server-to-server message channel interception example configurations.


Improved password protection for Java Advanced Message Security clients

This feature is available with Advanced and Advanced VUE entitlement.

An improvement has been deployed to Java Advanced Message Security (AMS) clients that allows them to parse configurations that contain encrypted passwords. This allows for the protection of keystore and truststore passwords inside an AMS configuration file.

This new improved system deprecates the old password protection system, and if your enterprise protected passwords in Java AMS clients prior to Version 9.2.0, we should protect the passwords again using the new command.

A command has been provided that can encrypt plain text passwords into the encrypted format usable with Java AMS clients. For more information, see Advanced Message Security - Java.


New features and enhancements for Managed File Transfer

These features and enhancements are available with Advanced and Advanced VUE entitlement.

    Highly available Managed File Transfer agents
    From Version 9.2.0, we can set up Managed File Transfer standard and bridge agents to be highly available. We can configure multiple instances of the same MFT agent on two or more servers in active and standby mode. If the active instance of the agent fails at any time, even when transfers are not in progress, another instance of the agent automatically starts up and enables file transfer to continue. This occurs, even in cases where one of the agents fails due to network issues, hardware issues, or any other reason that causes the agent to stop. For more information, see Highly available agents in IBM MQ Managed File Transfer.

    New fteClearMonitorHistory command for clearing resource monitor history
    From Version 9.2.0, the fteClearMonitorHistory command provides a mechanism for clearing the history of a Managed File Transfer resource monitor to simplify the process of re-initiating failed transfers. For more information, see Clearing resource monitor history and fteClearMonitorHistory.

    Option to specify wait time for Managed File Transfer database logger shut down
    From Version 9.2.0, a new property, immediateShutdownTimeout, is added to the logger.properties file. When this property is called, the logger waits for the specified amount of time for any outstanding operations to complete and shut down gracefully. For more information, see The MFT logger.properties file.

    New REST API calls for Managed File Transfer administration
    Version 9.2.0 expands the existing administrative REST API for Managed File Transfer, by adding

    • REST API calls for creating a new resource monitor, listing MFT resource monitor status along with other configuration information, and deleting an existing resource monitor, or deleting the history of an existing resource monitor. For more information, see admin/mft/monitor.
    • A REST API call for creating file transfers. For more information, see admin/mft/transfer.

    Support for the MQWebUser role in the MFT REST API
    From Version 9.2.0, we can use the MQWebUser role to authenticate:

      POST operations
      For more information, see POST for monitors and POST for transfers.

      GET operations
      For more information, see GET for agents, GET for transfers, and GET for monitor status.

    For more information, see admin/mft/transfer.

    Enhanced credentials protection
    Version 9.2.0 introduces enhanced security features. See the changes to fteObfuscate and Improvements to MFT security for more information.

Parent topic: What's new in Version 9.2.0


Related concepts

Last updated: 2020-10-04