Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents

Overview

The The B2BITS FIXEdge FIXEdge is a server application that provides FIX connectivity for standalone client applications. Client applications communicate with FIX Edge via one of the supported transport protocols (e.g. Simple Sockets, TIBCO, CORBA). FIXEdge can also be customized to use other connectivity bridges like CMS, ISE, INET, etcIt 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 different machines, however, the easiest way to use FIXEdge is running one instance on either a single machine or multiple machines.

FIXEdge complies with the following following FIX standards:

  • FIX 4.0 -

    5.0SP2 and

    FIX Latest, FIXT 1.1, including Extension Packs

  • FAST 1.1

FIXEdge supports is available for the following platforms:

...

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

  • Linux RHEL/CentOS

    6

    7 (support discontinued starting with FIXEdge 7.0.0)

  • Linux RHEL/

    CentOS 7

...

  • 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.

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

Evaluation of System Requirements

The configuration of modern computers is usually enough to build working system. However, the choice of particular configuration of hardware and software depends on the selected deployment scheme and FIXEdge performance requirements. 

Usually, the administrator sends a message to the support team with information about expected performance requirements and configuration. It is important to specify the following data in the message:

...

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 Support team evaluates will evaluate the possibility feasibility of using the existing configurations for expected requirements. If necessary the support team gives to meet the client’s requirements and will provide recommendations for configuration changingchanges, if necessary.

Content of the Package  

The FIXEdge

...

FIXServer, FMXML Handler, JMS Transport Adaptor, MQ Transport Adaptor, TIBCO Transport Adaptor, Universal Transport Adaptor, BLLanguageExtension, SMTP Transport Adaptor.

Others transport adaptors can be installed and configured later.

...

FIX Integrated Control Center (FIXICC) and FIXICC Agent.

FIXICC is a Java stand-alone application which provides monitoring and administration capabilities for FIX Edge.

FIXICC Agent is a wrapper that allows FIXICC to establish connection with several instances of FIXEdge.

The installation packages for Windows and Linux also contain Java components (java run-time engine).  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.

Expand
titlePackage Structure

FIXEdge is delivered as a FIXEdge-x.x.x.zip package for Windows and FIXEdge-x.x.x.tar.gz package for Linux

The package has the following structure:

  • FIXEdge - installation guide, readme and license files

    • FIXEdge/bin - FIXEdge binaries, libraries and shell scripts

    • FIXEdge/doc - config samples

    • FIXEdge/FIXEdge1

      • FIXEdge/FIXEdge1/conf - FIXEdge configuration files

      • FIXEdge/FIXEdge1/log - FIXEdge log folder

        • FIXEdge/FIXEdge1/log/archive - FIXEdge archive log folder

        • FIXEdge/FIXEdge1/log/backup - FIXEdge backup log folder

    • FIXEdge/

...

    • plugins -

...

    • pluggable components

Installation

Get the License File

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

Info

A separate license file for FIXICC and FIXICC Agent is required for FIXdge versions of before 5.11.3

Please, refer to the How to update license files article for additional informationFor additional information, please refer to the "How to Update License Files" article.

Install FIXEdge's Components

Info

All of FIXEdge components require ports for their work. Each instance of FIXEdge requires three ports, and one port is required for each instance of FIXICC Agent. Make sure that they are not used by other applications.

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

Testing

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

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

Configuration

Configure FIX Layer

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

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

Configure Transport Adaptors

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

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

Configure FIX Integrated Control Center

FIX Integrated Control Center (FIXICC) is a Java stand-alone application which provides out-of-the-box monitoring and administration capabilities for FIX Edge and any application embedding FIX Antenna C++, FIX Antenna Java and/or FIX Antenna .NET. Normally, no additional work is required to configure the application.

More information about FIXICC is presented in the FIXICC User Guide.

"

Management

FIXEdge can be managed from FIX Integrated using the FIXICC H2 Control Center (see FIXICC User Guide - Server level) or with the scripts to refer to the "FIXICC H2 for FIXEdge C++: User Guide") or through the start/stop scripts. FIXEdge can be run as a service /daemon. Also, there are additional options for FIXEdge for Windowson both Windows and Linux (rpm package).

Starting FIXEdge

Steps for Windows

  1. Run FIXEdge as a

...

  1. Service with the

...

  1. Script:

...

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

...

    1. script as an Administrator.

  1. Run FIXEdge as a

...

  1. Service using the Windows UI:

    1. Go to Administrative

...

    1. Tools --> Services.

...

    1. Locate the FIXEdge.FIXEdge1 service and select the 'Start' option

...

    1. from the context menu.

  1. Run FIXEdge as a

...

  1. Console Application:

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

...

    1. script.

Steps for Linux

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

Code Block
$ cd /home/user/B2BITS/FIXEdge/bin
$ ./FixEdge1.run.sh

Stopping FIXEdge

Steps for Windows

  1. Stop FIXEdge

...

  1. Service with the

...

  1. Script:

...

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

...

    1. script as an Administrator.

  1. Stop FIXEdge

...

  1. Service Using Windows UI:

    1. Go to Administrative

...

    1. Tools --> Services.

...

    1. Locate the FIXEdge.FIXEdge1 service and select the 'Stop' option

...

    1. from the context menu.

  1. The console version of FIXEdge can be stopped by pressing

...

  1. the "Ctrl+C" keys combination.

Steps for Linux

...

  • Navigate to

...

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

Code Block
$ cd /home/user/B2BITS/FIXEdge/bin
$ ./FixEdge1.stop.sh

Session ManagementSession Management

Sessions can be configured, started, or stopped from FIX Integrated Control Center, see FIXICC User Guide - Session levelusing FIXICC H2.

Monitoring

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

Analyzing Log Files with FIXEye

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

See more about the For more information, see the FIX log analyzer heredocumentationFIXEye User Guide.

Configuration of High Availability Failover Cluster  

FIXEdge Failover Cluster installation (based on Logs replicator)

FIXEdge Active-Passive Failover Cluster

...

Deployment Guide

...

Uninstallation

Make sure Ensure that FIXEdge had is stopped before uninstallingproceeding with uninstallation.

Steps for Windows

Uninstall the FIXEdge service

...

by running the following script as an Administrator:

Code Block
B2BITS\FIXEdge\bin\FIXEdge1.uninstall.cmd

...

Stop and uninstall the FIXICC Agent. Run the following scripts as Administrator:

...

languagebash

...

Steps for Linux

Stop and uninstall the FIXICC Agent

...

languagebash

...

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