IBM® MQ client behaviour can be customised through the mqclient.ini file, which provides access to a range of configuration options including channel settings, SSL/TLS parameters, tracing, and other advanced MQ client features.
While many Integration Runtime deployments work well with the default MQ client configuration, some environments require additional settings to meet specific connectivity, security, or operational requirements.
Prior to IBM® App Connect Operator v13.4, Integration Runtimes always used a default mqclient.ini file generated by App Connect. This simplified configuration for common use cases but limited the ability to tailor MQ client behaviour to the needs of individual deployments.
To provide greater flexibility, IBM® App Connect Operator v13.4 introduces a new mqclient.ini configuration type. By creating and associating an mqclient.ini configuration with an Integration Runtime, you can control the contents of the mqclient.ini file used by that runtime. This makes it possible to apply advanced IBM MQ client configuration settings directly through App Connect configuration objects, without modifying the runtime itself.
In this blog, we'll look at how to create an mqclient.ini configuration, associate it with an Integration Runtime, and use it to customise IBM MQ client behaviour.
Why is this useful?
The mqclient.ini file can be used to configure advanced MQ client behaviour, including channel settings, SSL/TLS options, tracing, and other MQ client parameters.
Previously, Integration Runtimes always used the default mqclient.ini file generated by App Connect. With the new configuration type, you can now supply your own configuration tailored to your environment.
Whether you need custom SSL/TLS settings, channel definitions, client reconnect options, or other MQ client parameters, you can now manage those settings through App Connect configuration objects rather than relying on the default generated configuration.
How it works
A new configuration type called mqclient.ini is available in the App Connect dashboard. When creating the configuration, you upload or enter the contents of the mqclient.ini file that you want the runtime to use.
The configuration can then be referenced by an Integration Runtime. When the runtime starts, the supplied content is written to the runtime's mqclient.ini file, replacing the default generated content. Existing runtimes can also be updated to use the new configuration.
The configuration can then be referenced by an Integration Runtime. When the runtime starts, the supplied content is written to the runtime's mqclient.ini file, replacing the default generated content. Existing runtimes can also be updated to use the new configuration.
Note: You can create multiple mqclient.ini configurations within your environment to support different IBM MQ connectivity requirements. However, each Integration Runtime can be associated with only one mqclient.ini configuration at a time.
Example
Suppose your organisation requires additional channel or SSL/TLS settings that are not present in the default configuration. You can create an mqclient.ini configuration containing those settings and associate it with your Integration Runtime. The runtime will then use your customised MQ client configuration whenever it connects to IBM MQ.
For example, one Integration Runtime might require additional SSL/TLS settings for connecting to a production queue manager, while another might require different channel settings for a development environment. By creating separate mqclient.ini configurations, you can reuse and manage these settings independently, while ensuring that each Integration Runtime uses the appropriate configuration.
Summary
With IBM® App Connect Operator v13.4, you can customise the mqclient.ini file used by Integration Runtimes through the new mqclient.ini configuration type. This provides a simple way to manage advanced IBM MQ client settings directly from App Connect while maintaining configuration consistency across your deployments.