« Basic FIX Routing Application using ShortCut | Main | RapidAddition’s ShortCut Architecture and Overview »

Installing and Configuring the FIX Adapter for BizTalk

This is the third post in a short series on the FIX adapter for BizTalk.

  1. FIX for BizTalk (The basics)
  2. ShortCut Architecture and Overview
  3. Installing and Configuring RapidAddition’s ShortCut
  4. Basic Routing Application using ShortCut
  5. Mapping FIX Messages
  6. More complicated scenarios and patterns using a FIX-enabled BizTalk

This post will go through installing and configuring the RapidAddition’s FIX adapter for BizTalk. The screenshots are from BizTalk Server 2009 however it’s the same process for 2010 or even 2006.

If you’re interested in getting the adapter the best place to start would be to reach out to the guys at RapidAddition.


Installing the Adapter is pretty easy. You’ll get an MSI that will install the DLL’s on to the BizTalk server. Shortcut does not support host clustering although you can install the FIX host on multiple machines so that you could quickly bring the session online if you lost a server. Each FIX session can only run in a single host and you can have multiple sessions per host.

Once you run through the installation you’ll need to configure it. There’s a configuration app in the program directory created during the installation.



The config app has 4 functions to run through. The first will install the FIX Schema and Pipeline assembles on all servers in the BizTalk group and BTSDeploy’s them. The second option will install the adapter into the registry and the third will create the RapidAddition database. The last option will make some performance tweaks to set BizTalk up for low latency.



The adapter is now installed. The next step is to add the adapter to the group. The config setup above really only adds the necessary registry settings for adapters like the install folder.


From the BizTalk Administrator, Platform Settings, Adapters (new) as shown in the screenshot above. You should see FIX in the list of uninstalled adapters. You can call it whatever you want by FIX makes a lot of sense.


The Adapter is now installed. Once you add the adapter the default handlers will show. The send handler doesn’t have any properties.


As explained in the first post the send port for the FIX adapter doesn’t do much, the receive handler on the other hand does have some settings.


Property Description
Database The name of the RapidAddition database as installed by the config application. Default value is RapidAddition
IP Address IP Address that the adapter will listen on for inbound connections.
MaxOutgoingBatchSize Batch size for outgoing (sends) messages
Password Password for SQL Database if not using windows authentication (will be the host instance service account)
Port The port that the adapter will listen on for inbound connections.
Server The SQL server hosting the RapidAddition database
Username The username for the SQL database if not using windows authentication


Receive Locations

To configure the actual FIX engine most of those fields can be found in the receive  locations.


Property Description
BatchInterval The batch interval in milliseconds
ConnectRetryInterval The reconnect interval in milliseconds
CounterParty: CounterParty FIX details
                 CertificateID Certificate for encryption (FIX version dependent) 
                 CompID CompID of the counterparty
                 IPAddress IPAddress of the counteryparty
                 Port Port used by the counterparty
DataDictonaryVersion Data Dictionary to use for the FIX version, typically left blank unless using a custom data dictionary
FIXVersion The FIX version of the session
HeartbeatInterval Interval that heartbeats will be sent if no application messages are received or sent
IncludeHeartbeatMessages Setting to allow heartbeat messages to flow back into BizTalk
IncludeSessionRejectMessages Setting to allow session reject messages to flow back into BizTalk
IncludeTestRequestMessages Setting to allow test request messages to flow back into BizTalk
Initiator Determines how initiates the session, true we will false means the counterparty will initiate
MaxIncomingBatchSize Max number of messages in an incoming batch
MaxOutgoingBatchSize Max number of messages in an outgoing batch
Party: Party FIX details (us)
         CertificateID Certificate for encryption (FIX version dependent)
         CompID Our CompID as known to the counterparty
ResetSeqNumOnLogon Reset the sequence number upon logon, usually not set and the sequence is reset by an End of Day job
SequenceMessages Honor the sequence as they’re passed into BizTalk
SequenceMessagesTimeout Timeout of sequence
ServiceDays Days of the week that the session will start, format as MTWTFSS or MTWTFXX will mean it doesn’t logon on weekends
ServiceEndTime Time of day that the session will finish
ServiceStartTime Time of day that the session will start
StoreAndForward On by default, this tells shortcut to accept and ack outgoing messages back to biztalk regardless of there being an active session or not. This means BizTalk thinks the message went out even if the session is down. Shortcut will deal with the message once the session is up.


Send Ports

Send ports are a lot simpler.


Property Description
CounterParty: CounterParty FIX details
                 CompID CompID of the counterparty
FIXVersion The FIX version of the session
Party: Party FIX details (us)
         CompID Our CompID as known to the counterparty

These settings help Shortcut uniquely identify the session in the RapidAddition database so the application messages get sent out over the correct FIX session.

Pipeline Components

The Shortcut Pipelines need to be setup with the RapidAddition database connection string and data dictionary used to convert the messages to and from FIX and FIXML.


Property Description
DataDictionaryVersion the data dictionary to use in message conversion
Database Name of the RapidAddition database as setup above
Password Password for the SQL connection if not using windows authentication
Server the SQL server
UserName SQL username for the SQL connection if not using windows authentication


The next post will go through using shortcut for some basic routing scenarios which will demonstrate how these properties are used. 

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>