Page Comparison

...

1. Make sure that there is a backup copy of the working installation.
2. Stop the FIXEdge service process
3. Stop the FIXICC-agent service process
4. Uninstall the FIXEdge service(s)
5. Uninstall the FIXICC Agent service(s)

6. Upgrade FIXEdge binaries
   Copy and overwrite all files in FIXEdge's <FIXEdge installation>/bin/ directory with new binaries from the FIXEdge package
   

   Info
   If scripts in bin/ directory (*.sh or *.cmd) were modified earlier then they should be recovered from the backup

7. Make FIXEdge configuration parameters adjustment if it's needed. 
   Make sure that your configuration files correspond last changes/improvements in new product versions
   

   1. Visit FIXEdge Release Notes page and look through the changes made from the current FIXEdge version to target the FIXEdge version.
      1. If last product changes require an update of your current FIXEdge's and FIXICC's config files, adjust them to satisfy new requirements;
      2. If last product changes don't affect your current FIXEdge's and FIXICC's config files, you may leave them as is;
      3. In case of doubts, please contact SupportFIXAntenna@epam.com;

   Warning
   It is critically important to update all absolute paths in the configuration. The recommendation is to use relative paths for simplifying upgrade steps

   Note
   Until the version, 5.11 FIXEdge's instance directory had the name <FixEdge1>. Since version 5.11 FIXEdge's instance directory name is <FIXEdge1>.

8. Upgrade FIXICC
   Remove <FIXEdge installation>/fixicc-agent/ and <FIXEdge installation>/fixicc/ directories
   Copy all files in FIXEdge's <FIXEdge installation>/fixicc-agent/ directory with new binaries from the FIXEdge package
   Copy all files in FIXEdge's <FIXEdge installation>/fixicc/ directory with new binaries from the FIXEdge package

9. If there were changes in fixicc-agent and fixicc configuration then replace the new configuration with the configuration from the backup

   Info
   the default Windows path for fixicc-agent configuration is: fixicc-agent\FIXEdge1.fixicc-agent\conf\ the default Linux path for fixicc-agent configuration is: fixicc-agent/conf

   I.e the following configuration should be re-used from the old FIXEdge

   • fixicc/etc/fixengine.properties
   • fixicc/etc/fixicc/log4j.properties
   • fixicc-agent/conf/fixengine.properties
   • fixicc-agent/conf/agent.properties
   • fixicc-agent/conf/log4j.properties
   • fixicc-agent/conf/OrderAckTCPMonitor.properties 
   • fixicc-agent/conf/security.properties
10. Upgrade Transport Adaptors and Handlers if use them:
    1. Visit FIXEdge Release Notes page;
    2. Look through the changes made with Transport Adaptors and Handlers from the current FIXEdge version to target the FIXEdge version:
       1. If any improvements/bugfixes were done in JMS Adaptor, then:
          1. Replace all jar files for JMS adapter with new jar files from the FIXEdge package in FIXEdge's FIXEdge1\conf\jms-ta-distribution\lib directory;
          2. Replace all jar files for JMS adapter with new jar files from the FIXEdge package in FIXEdge's FIXEdge1\conf\jms-ta-distribution\tool\lib directory;
       2. If any improvements/bugfixes were done in RabbitMQ Adaptor, then:
          1. Replace all jar files for RMQ adapter with new jar files from the FIXEdge package in FIXEdge's FIXEdge1\conf\amqp-ta-distribution\lib directory;
       3. If any improvements/bugfixes were done in other Transport Adaptors or Handlers, then:
          1. Replace corresponding binaries with new ones from the package with SupAdapters in FIXEdge's <bin> directory;

       Note
       In case you have several instances of one Transport Adaptor (it means there are several copies of one TA library), need to upgrade all of them.

    Note
    "Replace" in this context means that files should be deleted from the current FE directory and new files from the package should be added there. This clarification is made in order to avoid the situation when two (or more) same libraries with different versions appear in the directory as it may cause issues.

11. If using the Managed Queue, (i.e. FixLayer.ManagedQueue.Sessions parameter is configured) recover the queue files that were done in Preparation step #5
    If data from the queue is not needed then you can skip this step. A new file will be created automatically after restarting the FIXEdge instance if it will be missing
12. Copy your FIXEdge license into the license file path;
13. Install the FIXEdge service(s);
14. Install the FIXICC-agent service(s);
15. Start the FIXICC-agent process;
16. Start the FIXEdge process.

...