Content Comparison

...

1. Supported operating systems:

   • Linux RHEL/CentOS 7 (support discontinued starting with FIXEdge 7.0.0)

   • Linux RHEL/RockyLinux 9 (starting with FIXEdge 7.0.0)

2. The list of packages that should be installed before FIXEdge's installation: 
   • unzip

   • libtool-ltdl

     Expand
     title optional since v. 5.11.0
     java-1.7.0-openjdk Code Block $ sudo yum install java-1.7.0-openjdk

     
     

   To install them use the following commands with superuser permissions:

   Code Block
   language bash
   $ sudo yum install unzip $ sudo yum install libtool-ltdl

   
   

3. The list of ports that should be opened:

   • TCP: 8005, 8901, 8902, 8905.
   • UDP: 1234

...

1. Go to the /home/user/B2BITS/FIXEdge/fixicc-agent/logs directory and open fixicc-agent.log 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. Go to the B2BITS/FIXEdge/bin directory and run FIXEdge:

   Code Block
   language bash
   $ cd /home/user/B2BITS/FIXEdge/bin $ ./FixEdge1.run.sh

   
   

2. If the script was executed successfully then go to the /home/user/B2BITS/FIXEdge/fixicc-agent/logs directory and open fixicc-agent.log with any text editor (otherwise go to the 'FIXEdge doesn't start with 'FixEdge1.run.sh' script' section).

3. Check if the following note exists in the log and make sure that the path presented below lead to the existing engine.properties file:

   Code Block
   [UtilProperties] Properties load successful: /home/user/B2BITS/FIXEdge/fixicc-agent/../FIXEdge1/conf/engine.properties

   
   

4. If the note is absent find the messages with [ERROR] and [FATAL] level. These messages are able to help with 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.sh' script

1. Go to the B2BITS/FIXEdge/FIXEdge1/log directory and open FixEdge.log with any text editor.
2. Find the messages with [ERROR] or [FATAL] level. These messages are able to help with understanding of the possible issues. If there is a requirement for technical assistance then contact the support team SupportFIXProducts@epam.com. 

FIXEdge cannot start with an incorrect or expired license

...

How to see if a specific port is used

To ensure that port 8005 is not used, using the netstat or the ss command.

netstat -na | grep :8005
ss -na | grep :8005
lsof -i:8005

If the output is blank, then the port is not currently used.

Open FIXEdge ports using firewalld

...

1. The following commands open ports 8005, 8901, 8902, 8905, 1234. The superuser permissions are required in order to change the system settings.

   Code Block
   language bash
   sudo firewall-cmd --add-port=8005/tcp --permanent sudo firewall-cmd --add-port=8901/tcp --permanent sudo firewall-cmd --add-port=8902/tcp --permanent sudo firewall-cmd --add-port=8905/tcp --permanent sudo firewall-cmd --add-port=1234/udp --permanent sudo firewall-cmd --reload

   
   

   The flag  --permanent is used to keep changes after the host reboot.

2. To verify the changes run the following command (superuser permissions are required)
   

   Code Block
   language bash
   sudo firewall-cmd --list-ports

   
   

...

1. Uninstall FIXICC-Agent daemon with superuser permissions:
   

   Code Block
   language bash
   cd /home/user/B2BITS/FIXEdge/fixicc-agent/bin/ ./uninstallDaemon.sh

   
   

2. Uncomment or adjust runlevels init.d directory for RH7 and Ubuntu distros to /etc/rcX.d in FIXEdge/fixicc-agent/conf/wrapper.conf
   

   Code Block
   title wrapper.conf
   wrapper.daemon.run_level_dir=/etc/rcX.d

   
   

3. Uncomment and enable default runlevels for automatic startup and stop of the daemon in FIXEdge/fixicc-agent/conf/wrapper.conf
   

   Code Block
   title wrapper.conf
   wrapper.daemon.update_rc = start 20 2 3 4 . start 30 5 . stop 80 0 1 6

   The syntax is similar to the update-rc.d (for Debian distributions) or chkconfig (for other distributions such as Red Hat).

4. If it is required to run FIXEdge and fixicc-agent application under a specific user then uncomment and specify properties wrapper.app.account in FIXEdge/fixicc-agent/conf/wrapper.conf
   

   Code Block
   title wrapper.conf
   wrapper.app.account=<user>

   Where <user> is a Linux user for running FIXEdge applications. Sometimes, it is required to set a user's password with the property wrapper.app.password

   Info
   If the property is not set FIXICC-agent and FIXEdge will be run under the root user.

   
   

5. install FIXICC-Agent daemon with superuser permissions:
   

   Code Block
   language bash
   cd /home/user/B2BITS/FIXEdge/fixicc-agent/bin/ ./installDaemon.sh

   
   

...