Table of Contents
Overview
...
| Info |
|---|
Starting FixEdge version 6.10.0 it is recommended to use IBM MQ Client library version 8.x. The older and newer versions may lead to MQ adapters failures |
...
Monitoring and Administration
| Info |
|---|
Information about the configured TA's session parameters list and dynamic state is sent to the subscribed monitoring application when FIXEdge starts. When the TA session dynamic state is changed FIXEdge sends the update to the subscribed monitoring application. |
MQ TA provides the following monitoring information:
...
| Property Name | Default Value | Description |
TransportLayer.MQAdaptor.Description | MQ Transport Adaptor DLL | Description of the transport adaptor |
TransportLayer.MQAdaptor.DllName | bin/MQTAAddin.dll | Path to the transport adaptor module |
TransportLayer.MQAdaptor.TimeIntervalBeforeReconnect | 1000 | Time interval in milliseconds between reconnect attempts |
TransportLayer.MQAdaptor.StorageDirectory | FixEdge1/log | Logging directory for storage of outgoing messages. Required. |
TransportLayer.MQAdaptor.BufferSizeForMessage | 65536 | Message buffer size. Max value is 4194304. 0 means a default value 64 * 1024 |
TransportLayer.MQAdaptor.MQ_HOSTNAME | localhost | MS Series Server host name |
TransportLayer.MQAdaptor.MQ_PORT | 1414 | MS Series Server port |
TransportLayer.MQAdaptor.MQ_MANAGER_NAME | TestMQ | MS Series manager name |
TransportLayer.MQAdaptor.MQ_CHANNEL_NAME | TestConnection | MS Series Channel name |
TransportLayer.MQAdaptor.MQ_CCSID | 437 | MS Series Server CCSID. The coded character set identifier to use with the WebSphere MQ queue |
TransportLayer.MQAdaptor.SslKeyRepository | /var/mqm/ssl/key | Path to SSL certificate storage file without extension (SCKR,MQSSLKEYR) e.g. /var/mqm/ssl/key or C:\\Program Files\\IBM\\WebSphere MQ\\ssl\\key |
TransportLayer.MQAdaptor.SslCipherSpecification | TRIPLE_DES_SHA_US | SSL CipherSpec name (SSLCIPH), required to use SSL, e.g. TRIPLE_DES_SHA_US |
TransportLayer.MQAdaptor.SslClientAuthentication | false | Remote peer authentication (SSLCAUTH) |
TransportLayer.MQAdaptor.SslPeerName | CN=QMGR.*, OU=IBM, OU=WEBSPHERE | Remote peer DN filter(SSLPEER) |
TransportLayer.MQAdaptor.WaitIntervalForGet | 1000 | Time interval in milliseconds to wait between polling message on MQ Series Server |
TransportLayer.MQAdaptor.NumAttemptReconnect | 10 | Number of reconnect attempts to MQ Series Server |
TransportLayer.MQAdaptor.SessionNumber | 1 | Number of sessions with MQ Series. Each session is a set of MQ Series queues. |
TransportLayer.MQAdaptor.Session.1.ClientID | MQClient | MQ session ID. |
TransportLayer.MQAdapter.Session.1.FIXVersion | FIX44 | In every session, FIX messages use a particular version of the FIX protocol. Use this parameter to set the version of the FIX protocol for a given session. Acceptable values: |
TransportLayer.MQAdaptor.Session.1.SmartXMLProcessor | true | Enables mode of processing XML/FIXML messages:
|
TransportLayer.MQAdaptor.Session.1.ToClientQueue | MQClient_to | The name for Queue, dedicated for message coming from client to MQ via FIX Edge |
TransportLayer.MQAdaptor.Session.1.FromClientQueue | MQClient_from | The name for Queue, dedicated for message coming from MQ to client via FIX Edge |
TransportLayer.MQAdaptor.Session.1.ErrorQueue | MQClient_error | The name for Queue dedicated for message, which cannot be handled because of error. |
TransportLayer.MQAdaptor.Session.1.SenderID | - | Not required. SenderCompID (Tag = 49) in the received message is set to the property value. |
TransportLayer.MQAdaptor.Session.1.TargetID | - | Not required. TargetCompID (Tag = 56) in the received message is set to the property value. |
TransportLayer.MQAdaptor.Session.1.FromClientDropMessageFilter | - | Not required. Defines a regular expression (perl syntax) to drop matched messages coming from MQ. |
TransportLayer.MQAdaptor.Session.1.SmartXMLProcessorFromClientMessageFilter | - | Not required. Defines a regular expression (perl syntax) to apply SmartXMLProcessor to matched messages coming from MQ. Overrides default filter: case insensitive "<\?xml version.*|<FIXML.*" |
...
| Note |
|---|
Removing the storage files causes undelivered data will be deleted |
Start and Stop operations for IBM MQ TA
| Note |
|---|
Available since FIXEdge 6.13.0 release. |
FIXEdge C++ provides Start operation for Disconnected IBM MQ TA sessions and Stop operation for Connecting and Running IBM MQ TA sessions on request from the subscribed monitoring application.
Please refer to the Transport adaptor operations for FIXEdge C++ page for additional details about Start and Stop operations.
Start operation
Start operation can be applied to IBM MQ TA sessions in the Disconnected state.
FIXEdge starts a particular IBM MQ TA session on the request from the subscribed monitoring application and if the operation has been applied replies with a successful response.
In case when there is no session with the requested name FIXEdge logs an error and replies to the subscribed monitoring application with an error response below:
| Code Block | ||||
|---|---|---|---|---|
| ||||
Can't find session with id <session_name> |
In case when Start operation cannot be applied FIXEdge replies to the subscribed monitoring application with an error response and logs an error below:
| Code Block | ||||
|---|---|---|---|---|
| ||||
"Session '<session_name>': The session <session_name> can't be started: <description> Reason: Operation cannot be applied" |
Stop operation
Stop operation can be applied to IBM MQ TA sessions in the Running and Connecting states.
FIXEdge stops a particular IBM MQ TA session on the request from the subscribed monitoring application and if the operation has been applied replies with a successful response.
In case when there is no session with the requested name FIXEdge logs an error and replies to the subscribed monitoring application with an error response below:
| Code Block | ||||
|---|---|---|---|---|
| ||||
Can't find session with id <session_name> |
In case when Stop operation cannot be applied FIXEdge replies to the subscribed monitoring application with an error response and logs an error below:
| Code Block | ||||
|---|---|---|---|---|
| ||||
"Session '<session_name>': The session <session_name> can't be stopped: <description> Reason: Operation cannot be applied" |
In case when IBM MQ TA session is in a Disconnected state and IBM MQ TA receives the message, this message is persisted in storage to be sent on IBM MQ TA session start.
Troubleshooting
The message is not sent to the client with multiple MQ TA configuration
...
MQ TA has not supported the authentication in IBM MQ Server.
It can lead to failure in MQ TA initialization with the error records in the log:
...
Login to the remote server where MQ Instance is running
Open cmd
Run 'runmqsc'. Check if connected to correct QM:
Execute 'ALTER QMGR CHLAUTH(DISABLED)':
Try to reestablish connection by clicking 'No' in the dialog:
And Finish in the dialog:
- If the error is still here, look at Channel authentication records and make sure that your account is not in the Block User List:
- Try again steps 5-6.
Also you can find how to disable IBM MQ authentication on the official site.