Page tree
Skip to end of metadata
Go to start of metadata

Overview

This document describes two-instance FIXEdge installation on one host using two independent sets of binaries and configs. These installations can be updated, managed, or uninstalled independently.

The general single-instance FIXEdge installation procedure is described in FIXEdge Installation Guide and it is recommended to read it before following this procedure. Keep in mind that our example may differ from that in the one-instance installation procedure (e.g. directories names).

It is assumed that the user has no installed instances of FIXEdge. The step-by-step procedure is provided for installation from a non-customized distributive package. 

Installation directories

Windows

  1. c:\B2BITS\FIXEdge_one
  2. c:\B2BITS\FIXEdge_two

Linux

  1. /home/user/B2BITS/FIXEdge_one
  2. /home/user/B2BITS/FIXEdge_two

where a user is the name of the user performing the installation

Important precaution notes before starting changes

Remember that Linux OS is case-sensitive. That means that e.g. FIXEdge1.sh and FixEdge1.sh are different files.

Pay attention to port values – using one port value in several instances may lead to conflicts and failures.

Installation

Windows

  1. Extract distribution archive of FIXEdge to the instance 1 folder (in our test case it is B2BITS1 on c: drive). Extract distributive archive of FIXEdge to the instance 2 folder (in our test case it is B2BITS2 on c: drive)
  2. Put license file to 1st instance FIXEdge root directory (c:\B2BITS\FIXEdge_one\FIXEdge). Put license file to 2nd  instance fixedge root directory (c:\B2BITS\FIXEdge_two\FIXEdge).         
  3. Edit service names in a wrapper.conf file for 2nd instance for they must be different from 1st instance names.

    wrapper.conf
    # Name of the service
    wrapper.ntservice.name=FIXICC - Agent FIXEdge2
     
    # Display name of the service
    wrapper.ntservice.displayname=FIXICC - Agent FIXEdge2
  4. Change port values in configuration files (see example in ExampleConfigurationusedfortesting)

    parameter

    configuration file

    ListenPort

    engine.properties

    Monitoring.ListenPort

    engine.properties

    ControlCentre.XMLSockMonitor.Port

    FIXEdge.properties

    AgentServerPort

    agent.properties

  5. Open cmd.exe as Administrator and run the following scripts

    C:>\B2BITS\FIXEdge_one\FIXEdge\fixicc-agent\bat>installService.FIXEdge1.bat
    C:>\B2BITS\FIXEdge_one\FIXEdge\fixicc-agent\bat>startService.FIXEdge1.bat
    C:>\B2BITS\FIXEdge_one\FIXEdge\bin\FIXEdge1.install.cmd
    
  6. Edit the following files for 2nd instance
    In B2BITS\FIXEdge_two\FIXEdge\FIXEdge1\conf\FIXEdge.properties file set parameter ServiceName=FIXEdge2
    In B2BITS\FIXEdge_two\FIXEdge\FIXEdge1\bin\FIXEdge1.install.cmd change  FIXEdge.FIXEdge1 to FIXEdge.FIXEdge2
    In B2BITS\FIXEdge_two\FIXEdge\FIXEdge1\bin\FIXEdge1.service.run.cmd change  FIXEdge.FIXEdge1 to FIXEdge.FIXEdge2
    In B2BITS\FIXEdge_two\FIXEdge\FIXEdge1\bin\FIXEdge1.service.stop.cmd change  FIXEdge.FIXEdge1 to FIXEdge.FIXEdge2
    In B2BITS\FIXEdge_two\FIXEdge\FIXEdge1\bin\FIXEdge1.uninstall.cmd change  FIXEdge.FIXEdge1 to FIXEdge.FIXEdge2
  7. Open cmd.exe as Administrator and run the following scripts

    C:>\B2BITS\FIXEdge_two\FIXEdge\fixicc-agent\bat>installService.FIXEdge1.bat
    C:>\B2BITS\FIXEdge_two\FIXEdge\fixicc-agent\bat>startService.FIXEdge1.bat
    c:>\B2BITS\FIXEdge_two\FIXEdge\bin\FIXEdge1.install.cmd
    
  8. You can connect to the server and start the server in FIXICC in the same manner as for one-instance case (for details see https://kb.b2bits.com/display/B2BITS/FIXEdge+Installation+Guide)

If everything is OK you can see services for both instances running


In FIXICC GUI you can see both servers started

 

Linux

  1. Extract distribution archive of FIXEdge to the instance 1 folder /home/user/B2BITS/FIXEdge_one. Extract distribution archive of FIXEdge to the instance 2 folder /home/user/B2BITS/FIXEdge_two.
  2.  Put license file to 1st instance fixedge root directory /home/user/B2BITS/FIXEdge_one/FIXEdge. Put license file to 2nd  instance fixedge root directory /home/user/B2BITS/FIXEdge_one/FIXEdge.        
  3. Edit B2BITS/FIXEdge_two/FIXEdge/fixicc-agent/conf/wrapper.conf (change service names)

    #********************************************************************
    # Wrapper Windows Service and Posix Daemon Properties
    #********************************************************************
    # Name of the service
    wrapper.ntservice.name=FIXICC_Agent_Server2
    # Display name of the service
    wrapper.ntservice.displayname=FIXICC - AgentServer2
  4. Change port values in configuration files (see example in Example Configuration used for testing)

    parameter

    configuration file

    ListenPort

    engine.properties

    Monitoring.ListenPort

    engine.properties

    ControlCentre.XMLSockMonitor.Port

    Fixedge.properties

    AgentServerPort

    agent.properties

  5. run installation and start service scripts

    $>/home/user/B2BITS/FIXEdge_one/FIXEdge/fixicc-agent/bin/installDaemon.sh
    $>/home/user/B2BITS/FIXEdge_one/FIXEdge/fixicc-agent/bin/startDaemonNoPriv.sh
    $>/home/user/B2BITS/FIXEdge_two/FIXEdge/fixicc-agent/bin/installDaemon.sh
    $>/home/user/B2BITS/FIXEdge_two/FIXEdge/fixicc-agent/bin/startDaemonNoPriv.sh
    
  6. Check processes via ps command

    ps -eF | grep java
    ps -eF | grep FIXEdge
  7. Connect to the server and start the server in FIXICC in the same manner as for a one-instance case (for details see FIXEdge Installation Guide)
     If everything is working you can see servers started in FIXICC GUI (on the picture below you can see our test case example. The first two string correspond to the windows case and the last two strings show two Linux fixedge instances running)


Example Configuration used for testing

For Windows installations, FIXICC GUI application is running on the same windows machine

Port configuration

parameter

configuration file

 

FIXEdge1 windows

FIXEdge2

 windows

FIXEdge1

  linux

 

FIXEdge2

  linux

 

ListenPort

engine.properties

8901

8911

8901

8911

Monitoring.ListenPort

engine.properties

 

8803

8813

8803

8813

ControlCentre.XMLSockMonitor.Port

FIXEdge.properties

8902

8912

8902

8912

AgentServerPort

agent.properties

8903

8913

8005

8006

Uninstall

If you wish to uninstall both instances of FIXEdge you should do the following steps depending on what operating system you are running

Windows

1. Open cmd.exe as Administrator and run scripts

C:\B2BITS\FIXEdge_one\FIXEdge\fixicc-agent\bat\stopService.FIXEdge1.bat
C:\B2BITS\FIXEdge_one\FIXEdge\fixicc-agent\bat\uninstallService.FIXEdge1.bat

C:\B2BITS\FIXEdge_two\FIXEdge\fixicc-agent\bat\stopService.FIXEdge1.bat
C:\B2BITS\FIXEdge_two\FIXEdge\fixicc-agent\bat\uninstallService.FIXEdge1.bat

C:\B2BITS\FIXEdge_one\FIXEdge\bin\FIXEdge1.uninstall.cmd
C:\B2BITS\FIXEdge_two\FIXEdge\bin\FIXEdge1.uninstall.cmd

2. Remove B2BITS\FIXEdge_one and B2BITS\FIXEdge_two folders recursively

Linux

1.  run scripts 

$>/home/user/B2BITS/FIXEdge_one/FIXEdge/fixicc-agent/bin/stopDaemonNoPriv.sh
$>/home/user/B2BITS/FIXEdge_one/FIXEdge/fixicc-agent/bin/uninstallDaemon.sh

$>/home/user/B2BITS/FIXEdge_two/FIXEdge/fixicc-agent/bin/stopDaemonNoPriv.sh
$>/home/user/B2BITS/FIXEdge_two/FIXEdge/fixicc-agent/bin/uninstallDaemon.sh

$>/home/user/B2BITS/FIXEdge_one/FIXEdge/bin/FIXEdge1.stop.sh
$>/home/user/B2BITS/FIXEdge_two/FIXEdge/bin/FIXEdge1.stop.sh

2. Remove B2BITS/FIXEdge_one  and B2BITS/FIXEdge_two folders recursively

Troubleshooting

Related articles:

Server installation fails with the error "Cannot create service. The specified service already exists in this database"

Check the ServiceName parameter in FIXEdge.properties file.

The second instance of fixicc-agent installs and starts without errors but doesn’t appear in services

 

Check wrapper.conf file – service names must be changed.

The server does not start from FIXICC GUI. The process starts and hangs for a long time, but no error messages appear in the details field.

Check server name parameter in FIXEdge1.service.run.cmd.

Try to run FIXEdge as console application to get full error using FIXEdge1.run.cmd or FIXEdge1.run.sh


  • No labels