Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  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. Adjust FIXEdge configuration parameters if needed. 
    Make sure that your configuration files correspond to the most recent changes/improvements in the new product versions

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

    It is critically important to update all absolute paths in the configuration.

    We recommend using relative paths for simplifying the upgrade steps.

    Note

    Before version 5.11, FIXEdge's instance directory had the name <FixEdge1>. As of version 5.11, FIXEdge's instance directory name is <FIXEdge1>.

  8. Upgrade FIXICC
    Remove the <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 version

    • 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 you 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 the JMS Adaptor, then:
        1. Replace all jar files for the 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 the 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 the RabbitMQ Adaptor, then:
        1. Replace all jar files for the RMQ adapter with new jar files from the FIXEdge package in FIXEdge's FIXEdge1\conf\amqp-ta-distribution\lib directory;
      3. if using the Kafka Transport Adapter serializer plugins make sure that the adapter is already updated in the bin directory (see step #6) then update the Kafka plugins in the plugin plugins/ directory:
        For example:
        Windows: plugins/b2b_fixserver_kafka_test_serializer.dll
        Linux: plugins/libb2b_fixserver_kafka_test_serializer.so
      4. 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

      If you have several instances of one Transport Adaptor, (meaning that there are several copies of one TA library), you 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) of the same libraries with different versions appear in the directory as it may cause issues.

  11. If using the Managed Queue, update managed queue plugin in <FIXEdge installation>/pluginplugins/ directory:
    Windows: b2b_fixserver_plugin_queue_observer.dll
    Linux: libb2b_fixserver_plugin_queue_observer.so
  12. If using the Managed Queue, (i.e. FixLayer.ManagedQueue.Sessions parameter is configured) recover the queue files that were done in step #5 in the Preparation section.
    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 is missing.
  13. Copy your FIXEdge license into the license file path;
  14. Install the FIXEdge service(s);
  15. Install the FIXICC-agent service(s);
  16. Start the FIXICC-agent process;
  17. Start the FIXEdge process.

...