Overview

FIX Edge Java is an application server providing FIX connectivity to multiple clients. Client applications communicate with FEJ through one of the multiple transport protocols (e.g. Simple Sockets, TIBCO, JMS, HTTPs) employing transport adaptors. It is designed to be as easy as possible to install, configure, administrate, and monitor trading information flows. It is written in Java and has a performance profile suitable for the needs of all clients up to and including large sell-side institutions and large-volume traders.

Installation

Get the License File

The FIXEdge Java license file can be obtained upon request to the Sales team. The license has an expiration date but it is possible to generate a perpetual license. License information is stored in the fixaj2-license.bin file for FIXEdge Java versions earlier than 1.10.3. Since FIXEdge Java 1.10.3 the license information is stored in the fixedgej-license.bin file. The license file is expected to be placed in the FIXEdge Java config.rootpath=./conf directory. In order to apply for a new license, it is enough to replace the current file with a newer one and restart FIXEdge Java.

Please, refer to the How to update license files article for additional information.

...

• Installation in WildFly
• Installation in YAJSW
• Installation on Linux using packages
• FIXEdge Java with FIXICC H2: Deployment Guide

Testing

Set up the Echo Configuration to make sure that all components were deployed correctly. The test consists of sending a FIX message from FIX Client Simulator (aka Simple Client) to FIXEdge Java server and returning the same message back to Simple Client. The tool is based on .NET technologies and 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 from the How to configure Echo between FIXEdge Java and Simple Client article.

System Requirements

FIXEdge Java ver. 1.10.4 and Older

To get started, make sure your system has Java 8 or higher.

...

$ java -version
java version "1.8.0_60"
Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)

FIXEdge Java ver. 1.11.0 and Later

To get started, make sure your system has Java 17 or higher.

$ java -version
openjdk version "17.0.13" 2024-10-15
OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu124.04)
OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu124.04, mixed mode, sharing)

Configuration

This section will acquaint you with the basic information used during the configuration of the application.

...

1. Hazelcast cluster configuration. See Cluster Service.
2. Main Spring application context.
3. JMS related beans. See JMS Transport Adapter.
4. JMX and SSH related beans.
5. Replication-related beans.
6. Routing related beans.
7. Scheduler configuration.
8. Spring Security configuration. See Security configuration.
9. FIX server configuration.
10. FEJ configuration properties.
11. FIXAJ configuration properties. See FIX Antenna Java configuration.
12. JMS adaptor configuration properties. See JMS Transport Adapter.
13. Logging configuration. See Logging configuration.
14. Directory with templates for FIX reject messages
15. Replication service configuration. See Replication Service.
16. Custom routing rules go here. See Routing Rules.
17. Custom scheduler tasks go here.
18. Directory with session configuration. See FIX Session configuration.
19. Remote shell configuration. See Administrative shell configuration.
20. Properties file containing users for in-memory authentication. See In-Memory Authentication.
21. Wrapper configuration. See Wrapper configuration.

Management

FIXEdge Java can be managed with Remote Shell and with the scripts to start/stop FIXEdge as a service/daemon. Also, there are additional options for FIXEdge for Windows.

More information about Remote Shell is presented in FIXEdge Java Administration.

Starting FIXEdge Java

Steps for Windows

1. Run FIXEdge Java as a service in Windows Services
   • Go to Administrative tools --> Services. Find FIXEdgeJava service and select 'Start' option in the context menu.
2. Run FIXEdge Java as a console application
   • Go to the B2BITS\fixedgej-x.x.x\bat\ and run the 'runConsole.bat' script.
     
     

...

1. Run FIXEdge Java as a daemon with the script
   • Go to /home/user/B2BITS/fixedgej-x.x.x/bin and run the 'startDaemon.sh' script with sudo user rights.
2. Run FIXEdge Java as a console application
   • Go to the /home/user/B2BITS/fixedgej-x.x.x/bin and run the 'runConsole.sh' script with sudo rights.

Stopping FIXEdge Java

Steps for Windows

1. Stop FIXEdge Java service with the script
   
   • Go to the B2BITS\fixedgej-x.x.x\bat\ and run the 'stopService.bat' script as Administrator.
2. Stop FIXEdge Java service with Windows Services
   • Go to Administrative tools --> Services. Find FIXEdgeJava service and select 'Stop' option in the context menu.
3. The console version of FIXEdge Java can be stopped by pressing “Ctrl+C” keys combination.

...

1. Stop FIXEdge Java daemon with the script
   • Go to /home/user/B2BITS/fixedgej-x.x.x/bin and run the 'stopDaemon.sh' script with sudo user rights.
2. The console version of FIXEdge Java can be stopped by pressing “Ctrl+C” keys combination.

Session Management

Sessions can be configured, started, or stopped in the Remote Shell, see FIX Session management.

Analyzing Log Files with FIXEye

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

See more about the FIX log analyzer here: FIXEye User Guide.

Useful Links

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

...