Configuration reference information

MQIPT uses a configuration file called mqipt.conf to define routes and to control the actions of the MQIPT server.

The configuration file comprises a number of sections. There is one [global] section, and an additional [route] section for each route that has been defined through MQIPT.

Each section contains name/value property pairs. Some properties can appear only in the [global] section, some can appear only in the [route] sections, and some can appear both in [route] and [global] sections. If a property appears in both route and [global] sections, the value of the property in the [route] section overrides the global value, but only for the route in question. In this way, the [global] section can be used to establish the default values to be used for those properties not set in the individual [route] sections.

The [global] section starts with a line containing the characters [global] and ends when the first [route] section starts. The [global] section must precede all [route] sections in the file.

Each [route] section starts with a line containing the characters [route] and ends when the next [route] section starts, or when the end of the configuration file is reached.

Any unrecognized property name is ignored. If a property in a [route] section has a recognized name but has an invalid value (for example MinConnectionThreads=x or HTTP=unsure), that route is disabled (that is, it does not listen for any incoming connections). If a property in the [global] section has a recognized name but has an invalid value, all routes are disabled and MQIPT does not start. Where a property is listed as taking the values true or false, any mixture of uppercase and lowercase can be used.

We can change the value of a property by either editing the mqipt.conf file or by using the IPT Administration Client GUI. To apply any changes, refresh MQIPT, either from the IPT Administration Client GUI or by using the mqiptAdmin -refresh command.

Changes to certain properties cause a route to be restarted only if other properties are already enabled. For example, any changes to the HTTP properties have an effect only if the HTTP property is also enabled.

When a route is restarted, existing connections are terminated. To override this behavior, set the RouteRestart property to false. This prevents the route from restarting, allowing existing connections to remain active until the RouteRestart property is reenabled.

For information about how to set up some simple configurations, see Scenarios: Getting started with MQIPT. For a sample configuration, see the mqiptSample.conf file in the MQIPT installation directory.