FIXEdge installation on Windows. Step by step instruction

FIXEdge installation on Windows. Step by step instruction

Prerequisites and System Requirements

  1. Hardware:
    Any modern Intel-based server or workstation with 64 bit CPU

  2. Supported operating systems:

    • Windows 10 1903 or later

    • Windows Server 2022 or later

  3. The list of packages that should be installed before FIXEdge's installation: 

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

  1. Unpack the FIXEdge-x.x.x.zip archive into the C:\B2BITS directory

  2. Put the engine.license file into the FIXEdge's directory

  3. Open cmd.exe as Administrator and switch the current directory to the C:\B2BITS\FIXEdge\fixicc-agent\bat

    1. Execute the following scripts in the console:

      installService.FIXEdge1.bat startService.FIXEdge1.bat

      It can take up to several minutes to start at the first time:

    2. Switch the current directory to the C:\B2BITS\FIXEdge\bin. Execute the following scripts in the console:

      FIXEdge1.install.cmd
  4. Launch FIX Integrated Control Center (FIXICC):

    C:\B2BITS\FIXEdge\fixicc\bin\fixicc.exe
  5. Open the context menu of the default 'FixEdge1' server on the 'Server List' tab of FIXICC:

    • Select the 'Connect' option and use the password: admin.

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

  1. Make sure that VS 2015 C++ Redistributable Package (x64) is installed if the following System Error appears:

  2. The package can be found in C:\B2BITS\FIXEdge\Redist directory

FIXICC doesn't connect to FIXICC agent

  1. Go to the C:\B2BITS\FIXEdge\fixicc-agent\FIXEdge1.fixicc-agent\logs directory and open fixicc-agent.log with any text editor.

    1. 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: 8903
    2. If the notes are absent then go to the 'FIXICC agent doesn't start' section.

  2. Select the 'Edit Server' option in the context menu of the FIXEdge server in FIXICC. 

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

  1. Go to the C:\B2BITS\FIXEdge\fixicc-agent\FIXEdge1.fixicc-agent\logs with any text editor.

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

  1. Open cmd.exe as Administrator and switch the current directory to the C:\B2BITS\FIXEdge\bin

  2. Execute the following scripts in the console:

    FixEdge1.run.cmd
  3. If 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).

  4. 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.properties
  5. If 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

FIXEdge doesn't start with 'FixEdge1.run.cmd' script in case of openssl bug