Preparation Checklist
Before attempting to establish a session with a FIX server/client using the FIX adapter, it is essential that at least the following parameters are configured. Depending on the target exchange and application requirements, further configuration may or may not be required in addition.
Configure transports
When acting as client, a separate transport must be configured for each target FIX server to be connected to. The following parameters must be specified for each transport:
Name | Description |
Transport Name | A name for the transport/session. |
SocketConnectHost (client only) | The target IP/hostname. (obtained from exchange) |
SocketConnectPort | The target port. (obtained from the exchange) |
TargetCompID | Identifies the receiving system. (obtained from the exchange) |
SenderCompID | Identifies the sending system. (obtained from the exchange) |
DataDictionary | The path to the data dictionary file. |
Configure sessions
Each transport must be identified and configured for the service monitors. Clients transports are configured using a com.apama.fix.SessionConfiguration event and server transports are configured using a com.apama.fix.ServerConfiguration or com.apama.fix.MDServerConfiguration event. The configuration parameters used will depend upon the target system and application requirements.