Page tree

Versions Compared

Key

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

...

This article describes the ways to upgrade the FIXEdge to new version.

How to upgrade FIXEdge while the current version is up and running

This section shows how to setup an upgraded version of FIXEdge and transfer all required configuration without stopping the current working FIXEdge version.

Preparation

  1. Make sure you have sufficient administration permissions for further uninstall/install procedures.
  2. Download new FIX Edge package for the corresponding OS version;
  3. Make a copy of your current installation (configuration and binaries);
  4. Make a copy of your current license (engine.license).
    If your license has expired or was lost, contact sales@btobits.com to obtain the new one;
  5. Prepare configuration amendments in case you plan to change any credentials, destination folders, connection parameters, etc. Refer to configuration guides for assistance;
Note

Your current version of FIXEdge will be up and running all the time during the upgrade procedure.

Note

For FIXEdge version 6.5.0 and higher VS2015 C++ redistributable is required. It can be found in FIXEdge's \Redist directory or downloaded from Microsoft web-site.

...

  1. Upgrade FIXEdge itself:
    1. For Windows version:
      Replace* files in FIXEdge's <bin> directory with new binaries from the FIXEdge package;
    2. For Linux version:
      Replace* files in FIXEdge's <bin> directory with new binaries from the FIXEdge package - all except *.sh files;
  2. Upgrade FIXICC:
    1. Replace* files in FIXEdge's <fixicc-agent> directory with new ones from the FIXEdge package – all except *.properties files;
    2. Replace* files in FIXEdge's <fixicc> directory with new ones from the FIXEdge package – all except *.properties files;
  3. 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 you current FIXEdge version to target 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;
      4. If no improvements/bugfixes were done, you may skip step 4;
      5. In case of doubts, please contact SupportFIXAntenna@epam.com;
      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.

    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>.

  4. Make sure that your configuration files correspond last changes/improvements in new product versions:
    1. Visit FIXEdge Release Notes page;
    2. Look through the changes made from you the current FIXEdge version to target 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;
  5. Copy your FIXEdge license into the license file path;
  6. Install the FIXEdge service(s);
  7. Install the FIXICC-agent service(s);
  8. Start the FIXICC-agent process;
  9. Start the FIXEdge process.

...

In other words, the procedure is absolutely the same, the only difference is that you the backup copy is the target FIXEdge version in this case.

Troubleshooting

FIXEdge

...

started to fail after the Upgrade

Reason: 

additional CME STP Adapter was not upgraded

Solution

do the upgrade for installed additional CME STP Adapter.

If FIXEdge started to crash after the upgrade and some adapters or handlers is used in the configuration probably step #4 in Upgrade process wasn't done properly

Please check that all adapters and handlers (e.g. CME STP Adapter) have the same revision as FIXEdge in versions.log

Code Block
titleversions.log
2019-08-05 19:46:17,886 UTC   INFO    [Version]  22036  TransportLayer' version 0.1.1.5(r31)
2019-08-05 19:46:17,886 UTC   INFO    [Version]  22036  FIXEdge version 6.7.0 (r31)
2019-08-05 19:46:18,317 UTC   INFO    [Version]  22036  FIXMLConverter version 0.0.2.19(r31)
2019-08-05 19:46:18,390 UTC   INFO    [Version]  22036  BusinessLayer version 0.0.20.00(r31)
2019-08-05 19:46:18,392 UTC   INFO    [Version]  22036  Engine Adaptor version 0.0.1.17(r31)
2019-08-05 19:46:18,402 UTC   INFO    [Version]  22036  The B2BITS FIX Engine 2.25.1 (r51)
2019-08-05 19:46:19,279 UTC   INFO    [Version]  22036  FIX Engine AdminProtocol version 3.0
2019-08-05 19:46:22,398 UTC   INFO    [Version]  22036  FixEngine version 0.0.2.2(r31)
2019-08-05 19:46:22,399 UTC   INFO    [Version]  22036  FixLayer version 0.2.1.5(r31)
2019-08-05 19:46:22,411 UTC   INFO    [Version]  22036  STP Transport Adaptor version 0.1 (r31)

Solution:

Upgrade transport adapters and handlers to the same version as FIXEdge