What's new in IBM MQ 9.2.1 for Multiplatforms - Advanced entitlement only

Deploying containers to IBM Cloud Pak for Integration

From IBM MQ 9.2.1, the IBM MQ Advanced container is supported for use as part of the IBM Cloud Pak® for Integration, or independently.

For detailed mappings between IBM MQ Operators, IBM Cloud Pak for Integration versions, and container images, see Release history for IBM MQ Operator and containers.

Applicable versions of the IBM MQ Advanced container image are available from December 18, 2020.

Containers and the EUS release model

The IBM Cloud Pak for Integration uses the Extended Update Support (EUS) release model, which provides 18 months support for each EUS release.

The IBM MQ Advanced container image is based on IBM MQ Continuous Delivery, and is typically supported as a CD release. However, from IBM MQ 9.2.1, if a container image is based on a version of IBM MQ marked as -eus, and the container is used as part of the IBM Cloud Pak for Integration, the container is instead supported as an EUS release.

For more information, see Support for IBM MQ Operator and containers.

Redistributable Managed File Transfer Logger

From IBM MQ 9.2.1, the Redistributable Managed File Transfer package includes the Managed File Transfer Logger component, enabling you to optionally copy published information about actions for analysis and auditing purposes. The logger supports FILE type loggers connecting in client mode to the coordination queue manager.

For more information, see Downloading and configuring Redistributable Managed File Transfer components.

Limiting the number of file transfers for each FTP endpoint

From IBM MQ 9.2.1, enhancements to the Managed File Transfer protocol bridge agent enable you to choose to limit file transfers per File Transfer Protocol (FTP) and Secure FTP (SFTP) endpoint to reduce the risk of bottlenecks and effectively prioritize file transfers. You can limit the number of file transfers for each FTP endpoint by using the additional attributes of maxActiveDestinationTransfers (at both the global and individual server level) and failTransferWhenCapacityReached. For more information, see Scenarios and examples for limiting the number of file transfers to individual file servers and Protocol bridge properties file format for details of the additional attributes.