Page Comparison

...

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 1^st instance FIXEdge root directory (c:\B2BITS\FIXEdge_one\FIXEdge). Put license file to 2^nd  instance fixedge root directory (c:\B2BITS\FIXEdge_two\FIXEdge).         

3. Edit service names in a wrapper.conf file for 2^nd instance for they must be different from 1^st instance names.

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

   Code Block
   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 2^nd 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

   Code Block
   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://kbb2bits.b2bitsatlassian.comnet/wiki/display/B2BITS/FIXEdge+Installation+Guide)
   
   

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

...

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 1^st instance fixedge root directory /home/user/B2BITS/FIXEdge_one/FIXEdge. Put license file to 2^nd  instance fixedge root directory /home/user/B2BITS/FIXEdge_one/FIXEdge.        

3. Edit B2BITS/FIXEdge_two/FIXEdge/fixicc-agent/conf/wrapper.conf (change service names)

   Code Block
   #******************************************************************** # 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

   Code Block
   $>/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

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

...