Prerequisites and System Requirements

...

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

   Expand
   title FIXEdge prior v. 5.11.3
   Put the fixaj2-license.bin into the root folder of FIXICC Agent

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:

      Code Block
      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:

      Code Block
      FIXEdge1.install.cmd

      

4. Launch FIX Integrated Control Center (FIXICC):

   Code Block
   C:\B2BITS\FIXEdge\fixicc\bin\fixicc.exe

5. Open the context menu of the default 'FixEdge1' server on the 'Server List' tab of FIXICC:

   Expand
   title Extra step for FIXEdge prior v. 5.11.3
   Import the fixaj2-license.bin license in FIXICC GUI: Help -> Import license...

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

6. Select the 'Start Server' option in the context menu of the server. 

...

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:

   Code Block
   language bash
   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:

   Code Block
   [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

1. Check the console output it is able to help with the understanding of the possible issues.

   • If the output contains the following errors then it is the issue related to third-party openssl bug with openssl.cnf location: 

     Code Block

     C:\Downloads\FIXEdge.6.1.0.windows\FIXEdge\bin>"./FIXServer.exe" -console "../FIXEdge1/conf/FIXEdge.properties" FIXEdge 6.1.0.r203 (engine 2.18.1.r54) Auto configuration failed 12324:error:02001015:system library:fopen:Is a directory:.\crypto\bio\bss_file.c:169:fopen('D:\environment\openssl-1.0.1l\vc10-x64\ssl\openssl.cnf','rb') 12324:error:2006D002:BIO routines:BIO_new_file:system lib:.\crypto\bio\bss_file.c:174: 12324:error:0E078002:configuration file routines:DEF_LOAD:system lib:.\crypto\conf\conf_def.c:199:

     To solve the issue add OPENSSL_CONF variable and set it to "C:\". Please, select the method most convenient to you:

     1. Append the following line to the first line of the scripts FIXEdge1.run.cmd and FIXEdge1.service.run.cmd to make FIXEdge runnable manually or via FIXICC:

        Code Block
        SET OPENSSL_CONF=c:\

     2. Add the OPENSSL_CONF variable to Environment Variables:

        

2. Go to the C:\B2BITS\FIXEdge\FIXEdge1\log directory and open the FixEdge.log file with any text editor.
3. Find the messages with [ERROR] or [FATAL] level in the log. 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 incorrect FIXEdge.log path

• Check the console output it is able to help with the understanding of the possible issues.
  If the output contains the following errors then it is the issue related to incorrect FIXEdge.log path.

  Code Block
  FIXEdge 6.4.0.r249 (engine 2.21.0.r60) ERROR: Unable to register Event source for category 'FIXEdge'. Reason: RegCreateKeyEx: Error while adding registry records. Access is denied. (Error code = 5)

  The FIXEdge.log path not correctly set. For this reason, FIXEdge tries to log another error throughEventLog. If there are no administrator rights, an error occurs.

• To solve the issue configure proper FIXEdge.RootDir in FIXEdge.properties and Log.File.RootDir in engine.properties.
• Restart FIXEdge after updating FIXEdge.properties and engine.properties to apply the changes.

FIXEdge cannot start with an incorrect or expired license

...