FIXEdge installation on Windows. Step by step instruction
- 1 Prerequisites and System Requirements
- 2 Deployment of FIXEdge
- 3 Troubleshooting
- 3.1 FIXEdge doesn't install because of missing MSVCP100.dll
- 3.2 FIXICC doesn't connect to FIXICC agent
- 3.3 FIXICC agent doesn't start
- 3.4 FIXEdge doesn't start from FIXICC
- 3.5 FIXEdge doesn't start with 'FixEdge1.run.cmd' script in case of openssl bug
- 3.6 FIXEdge doesn't start with 'FixEdge1.run.cmd' script in case of incorrect FIXEdge.log path
- 3.7 FIXEdge cannot start with an incorrect or expired license
Prerequisites and System Requirements
Hardware:
Any modern Intel-based server or workstation with 64 bit CPUSupported operating systems:
Windows 10 1903 or later
Windows Server 2022 or later
The list of packages that should be installed before FIXEdge's installation:
VS 2015 - 2022 C++ Redistributable Package (x64) https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist
The list of ports that should be opened:
TCP: 8901, 8902, 8903, 8905
UDP: 18479
Deployment of FIXEdge
FIXEdge Components
FIXEdge-x.x.x.zip - FIXEdge package
engine.license - FIXEdge license file
Steps to Install
The installation assumes that FIXEdge will be installed in the C:\B2BITS directory. This directory should be created first.
Unpack the FIXEdge-x.x.x.zip archive into the C:\B2BITS directory
Put the engine.license file into the FIXEdge's directory
Open cmd.exe as Administrator and switch the current directory to the C:\B2BITS\FIXEdge\fixicc-agent\bat
Execute the following scripts in the console:
installService.FIXEdge1.bat startService.FIXEdge1.batIt can take up to several minutes to start at the first time:
Switch the current directory to the C:\B2BITS\FIXEdge\bin. Execute the following scripts in the console:
FIXEdge1.install.cmd
Launch FIX Integrated Control Center (FIXICC):
C:\B2BITS\FIXEdge\fixicc\bin\fixicc.exeOpen the context menu of the default 'FixEdge1' server on the 'Server List' tab of FIXICC:
Select the 'Connect' option and use the password: admin.
Select the 'Start Server' option in the context menu of the server.
Please refer to FIXICC User Guide for detailed instructions.
Installation complete.
See also:
How to setup secure SSL/TLS connесtion between FIXEdge, FIXICC-agent and FIXICC
How to change FIXICC Agent password
Troubleshooting
FIXEdge doesn't install because of missing MSVCP100.dll
Make sure that VS 2015 C++ Redistributable Package (x64) is installed if the following System Error appears:
The package can be found in C:\B2BITS\FIXEdge\Redist directory
FIXICC doesn't connect to FIXICC agent
Go to the C:\B2BITS\FIXEdge\fixicc-agent\FIXEdge1.fixicc-agent\logs directory and open fixicc-agent.log with any text editor.
Check if the following notes exist in the log:
INFO|13743/0|Service FIXICC - Agent Server|14-06-19 20:39:15|Agent is started successfully INFO|13743/0|Service FIXICC - Agent Server|14-06-19 20:39:15|Agent started on port: 8903If the notes are absent then go to the 'FIXICC agent doesn't start' section.
Select the 'Edit Server' option in the context menu of the FIXEdge server in FIXICC.
Make sure that the value of the 'Port' and 'Host' in the 'Basic Settings' corresponds to the FIXICC Agent port and the host of the FIXEdge machine.
FIXICC agent doesn't start
Go to the C:\B2BITS\FIXEdge\fixicc-agent\FIXEdge1.fixicc-agent\logs with any text editor.
Find the messages with [ERROR] and [FATAL] level. These messages are able to help with the understanding of the possible issues. If there is a requirement for technical assistance then contact the support team SupportFIXProducts@epam.com.
FIXEdge doesn't start from FIXICC
Open cmd.exe as Administrator and switch the current directory to the C:\B2BITS\FIXEdge\bin
Execute the following scripts in the console:
FixEdge1.run.cmdIf the script executed successfully then go to the C:\B2BITS\FIXEdge\fixicc-agent\FIXEdge1.fixicc-agent\logs directory and open fixicc-agent.log with any text editor (otherwise go to the 'FIXEdge doesn't start with 'FixEdge1.run.cmd' script' section).
Check if the following note exists in the log and make sure that the path presented below leads to the existing engine.properties file:
[INFO ] [main] [UtilProperties] Properties load successful: C:\B2BITS\FIXEdge\.\FIXEdge1\conf\engine.propertiesIf the note is absent find the messages with [ERROR] and [FATAL] level. These messages are able to help with the understanding of the possible issues. If there is a requirement for technical assistance then contact the support team SupportFIXProducts@epam.com.