Open

Overview

The B2BITS FIXEdge is a server application that provides FIX connectivity for standalone client applications. It can be configured to exchange messages via FIX connections or other supported connection types, such as Kafka, IBM MQ, and more.

FIXEdge can be deployed on either a single machine or multiple machines.

FIXEdge complies with the following FIX standards:

• FIX 4.0 - FIX Latest, FIXT 1.1, including Extension Packs

• FAST 1.1

FIXEdge is available for the following platforms:

• Windows (Windows 10 or later, Windows Server 2019 or later)

• Linux RHEL/CentOS 7 (support discontinued starting with FIXEdge 7.0.0)

• Linux RHEL/RockyLinux 9 (starting with FIXEdge 7.0.0)

• Ubuntu Server 22.04 (starting with FIXEdge 7.0.0)

For any questions, please contact the Support team at: SupportFIXAntenna@epam.com.

Requests for license updates can be directed to the Sales team at: sales@btobits.com.

Evaluation of System Requirements

There are no specific hardware requirements for FIXEdge (a standard machine is sufficient). However, hardware requirements may vary based on use cases, such as performance needs and expected load.

For an evaluation of hardware configuration and recommendations, you can contact the Support team with details about your expected performance requirements and other crucial information. Please ensure that at least the following information is included within your request:

• Expected number of FIX sessions, types of messages (such as market data, orders) in each session, and the expected number of messages per second.

• Operating system, number of processors (cores), amount of memory, type and size of the hard drive, network bandwidth, and adapter type (SolarFlare, other TCP offload, or standard network connection). Optional: SQL database and ODBC drivers.

The Support team will evaluate the feasibility of using existing configurations to meet the client’s requirements and will provide recommendations for configuration changes, if necessary.

Content of the Package

The FIXEdge package includes FIXServer, along with all the supported business components and transport adapters.

The installation packages for Windows and Linux do not include the Java runtime. It must be installed beforehand. The minimum required Java version is 11, and the recommended version is also 11.

Installation

Get the License File

The FIXEdge license file can be obtained by requesting it from the Sales team. The license typically has an expiration date, but it is possible to generate a perpetual license. License information is stored in the 'engine.license' file, which should be placed in the FIXEdge root directory. To apply a new license, simply replace the current file with the updated one and restart FIXEdge.

For additional information, please refer to the "How to Update License Files" article.

Install FIXEdge's Components

Refer to the detailed step-by-step guides for Linux and Windows:

• FIXEdge installation on Linux. Step by step instruction

• FIXEdge installation on Windows. Step by step instruction

Testing

Set up the Echo Configuration to ensure all components were deployed correctly. The test involves sending a FIX message from the FIX Client Simulator (also known as Simple Client) to the FIXEdge server and then returning the same message back to the Simple Client. This tool, based on .NET technologies, can be used to simulate FIX buy and/or sell-side endpoints.

To perform the test, download the FIX Client Simulator and follow the instructions in the "Echo Configuration Between FIXEdge and Simple Client (Fix Client Simulator)" article.

Configuration

Configure FIX Layer

The FIXEdge installation package includes a pre-configured FIX acceptor session. Session properties can be viewed via FIXICC H2 or in the 'FIXEdge.properties' file located in the 'FIXEdge/FIXEdge1/conf' folder. Once installed, FIXEdge is ready to create and maintain pre-configured and other FIX sessions/connections. Each FIX session is identified by a pair of SenderCompID and TargetCompID properties.

To configure FIXEdge according to your business needs, refer to the "FIXEdge Configuration" article.

Configure Transport Adaptors

Transport Adaptors enable clients to communicate with FIXServer over non-FIX transports. They are defined in the 'Transport Layer' section of the 'FIXEdge.properties' file. Transport Adaptors are dynamic link libraries with .dll (Windows) or .so (Linux) extensions, which FIXEdge loads at runtime. Transport Adaptor sessions are identified by the ClientID.

For guidance on configuring Transport Adaptors, refer to "FIXEdge Transport Adaptors."

Management

FIXEdge can be managed using the FIXICC H2 Control Center (refer to the "FIXICC H2 for FIXEdge C++: User Guide") or through the start/stop scripts. FIXEdge can be run as a service on both Windows and Linux (rpm package).

Starting FIXEdge

Steps for Windows

1. Run FIXEdge as a Service with the Script:

   1. Navigate to the B2BITS\FIXEdge\bin\ directory and run the 'FixEdge1.service.run.cmd' script as an Administrator.

2. Run FIXEdge as a Service using the Windows UI:

   1. Go to Administrative Tools --> Services. Locate the FIXEdge.FIXEdge1 service and select the 'Start' option from the context menu.

3. Run FIXEdge as a Console Application:

   1. Navigate to the B2BITS\FIXEdge\bin\ directory and run the 'FixEdge1.run.cmd' script.

Steps for Linux

Navigate to the /home/user/B2BITS/FIXEdge/bin directory and run the start script.

Stopping FIXEdge

Steps for Windows

1. Stop FIXEdge Service with the Script:

   1. Navigate to the B2BITS\FIXEdge\bin\ directory and run the 'FIXEdge1.service.stop.cmd' script as an Administrator.

2. Stop FIXEdge Service Using Windows UI:

   1. Go to Administrative Tools --> Services. Locate the FIXEdge.FIXEdge1 service and select the 'Stop' option from the context menu.

3. The console version of FIXEdge can be stopped by pressing the "Ctrl+C" keys combination.

Steps for Linux

• Navigate to the /home/user/B2BITS/FIXEdge/bin directory and run the stop script:

Session Management

Sessions can be configured, started, or stopped using FIXICC H2.

Monitoring

FIXEdge can be monitored by referring to log files or using FIXICC H2. Log files for each session are stored separately in the "FIXEdge/FIXEdge1/log" folder and can be viewed using any text editor/viewer. The 'FixEdge.log' file contains information about session creation, destruction, reconnection, and license expiration dates, among other details.

Analyzing Log Files with FIXEye

All log files containing incoming and outgoing FIX messages can be viewed using FIXEye. FIXEye is a multi-purpose FIX session surveillance and visibility platform. 

For more information, see the FIX log analyzer documentation: FIXEye User Guide.

Configuration of High Availability Failover Cluster  

FIXEdge Failover Cluster installation (based on Logs replicator)

FIXEdge Active-Passive Failover Cluster Deployment Guide

Uninstallation

Ensure that FIXEdge is stopped before proceeding with uninstallation.

Steps for Windows

Uninstall the FIXEdge service by running the following script as an Administrator:

Steps for Linux

There are no specific steps required.

FAQ

Frequently asked questions and "How to" articles can be found here: "How to..." articles

Useful Links

FIXICC H2 User Guide

FIXEdge Installation Guide

Deployment Schemas

FIXEdge Configuration

FIXEdge Transport Adaptors

FIX Client Simulator

FAQs and "How to" articles

FIXEdge Failover Cluster installation (based on Logs replicator)

FIXEdge Active-Passive Failover Cluster Deployment Guide