The coordination.properties file
The coordination.properties file specifies the connection details to the coordination queue manager. Because several WebSphere® MQ File Transfer Edition installations might share the same coordination queue manager, you can use a symbolic link to a common coordination.properties file on a shared drive.
The coordination.properties file is created by the installer or by the fteSetupCoordination command. You can use the fteSetupCoordination command with the -f flag to change the basic coordination queue manager properties in this file. To change or add advanced coordination queue manager properties you must edit the file in a text editor.
The coordination.properties file is located in your configuration_directory/coordination_qmgr_name directory.
Property name | Description | Default value |
---|---|---|
coordinationQMgr | The name of the coordination queue manager. | No default |
coordinationQMgrHost | The host name or IP address of the coordination queue manager. | No default |
coordinationQMgrPort | The port number used for client connections to the coordination queue manager. | 1414 |
coordinationQMgrChannel | The SVRCONN channel name used to connect to the coordination queue manager. | SYSTEM.DEF.SVRCONN |
If you do not specify a value for the coordinationQMgrHost property, bindings mode is used by default.
If you specify a value for the coordinationQMgrHost property but do not specify values for the coordinationQMgrPort and coordinationQMgrChannel properties, a port number of 1414 and a channel of SYSTEM.DEF.SVRCONN are used by default.
Property name | Description | Default value |
---|---|---|
Code page properties: | ||
coordinationCcsid | The code page the commands connect to the coordination queue manager with. Also any publications to the coordination queue manager made by the agent are performed with this code page. If you specify a value for coordinationCcsid you must also specify a value for coordinationCcsidName. | 1208 |
coordinationCcsidName | The Java™ representation of the coordinationCcsid. If you specify a value for coordinationCcsidName you must also specify a value for coordinationCcsid. | UTF8 |
Connection properties: | ||
javaLibraryPath | When connecting to a queue manager in bindings mode WebSphere MQ File Transfer Edition must have access to the WebSphere MQ Java bindings libraries. By default WebSphere MQ File Transfer Edition looks for the bindings libraries in the default location defined by WebSphere MQ. If the bindings libraries are in a different location use this property to specify the location of the bindings libraries. | /opt/mqm/java/lib |
Multi-instance queue manager properties: | ||
coordinationQMgrStandby | The host name and the port number used for client connections, in WebSphere MQ CONNAME format, for the standby instance of a multi-instance coordination queue manager defined by the coordinationQMgr property. For example, host_name(port_number) | No default |
Queue properties: | ||
dynamicQueuePrefix | This property defines the WebSphere MQ prefix to use for generating
a temporary queue name. The format of the dynamicQueuePrefix property follows the format of the DynamicQName field of the WebSphere MQ MQOD structure. For more information, see Creating dynamic queues in the WebSphere MQ Version 7.0.1 product documentation. You can also define this property in the command.properties file if you want to use a specific WebSphere MQ prefix for temporary reply queues that are generated by commands that require a response from the agent. |
WMQFTE.* |
modelQueueName | This property defines the WebSphere MQ model queue to use for generating
a temporary queue. You can also define this property in the command.properties file if you want to use a specific WebSphere MQ model queue for temporary reply queues that are generated by commands that require a response from the agent. For more information, see The command.properties file. |
SYSTEM.DEFAULT.MODEL.QUEUE |
Security properties: | ||
userIdForClientConnect | The user ID that gets flowed through the client connections to WebSphere MQ. If java is specified the user name reported by the JVM is flowed as part of the WebSphere MQ connection request. The value of this property can be None or java. | None |
Subscription properties: | ||
coordinationSubscriptionTopic | Use this property to specify a topic other than SYSTEM.FTE
to subscribe to in order to obtain publications about the status of
the WMQFTE network.
All tooling still publishes to the SYSTEM.FTE topic, but you can change
your WebSphere MQ topology to distribute
these publications to different topics based on their content. You
can then use this function to force the tooling to subscribe to one
of these other topics. This function is available for specific versions of WebSphere MQ File Transfer Edition only: V7.0.3 and V7.0.4.1 or later fix packs. If you are using 7.0.3, you also require an interim fix for APAR IC76641. If you are using WebSphere MQ File Transfer Edition Version 7.0.4.1 or later fix packs, you also require an interim fix for APAR IC96850 for the property to be recognized by the WebSphere MQ Explorer plug-in and the fteListMonitors command. |
SYSTEM.FTE |
coordinationQMgr=ERIS
coordinationQMgrHost=kuiper.example.com
coordinationQMgrPort=2005
coordinationQMgrChannel=SYSTEM.DEF.SVRCONN
ERIS is the
name of a WebSphere MQ
queue manager that is located on the system kuiper.example.com.
The queue manager ERIS is the queue manager that WebSphere MQ
File Transfer Edition sends log information
to.