Logi Composer Version 6 Release Notes

These release notes cover changes and fixes made to Zoomdata and Composer 6 releases. The latest updates are available in version 6.4. You can identify your release version on the login screen.

For more information about the supported Logi Composer and Logi Zoomdata releases, see Logi Composer (Zoomdata) Release Vehicles.

See the following Release Notes for different releases of version 6:

Email salesteam@logianalytics.com or emea_sales@logianalytics.com to purchase Composer.

For information about Composer's end-of-life policy for third-party software, see Composer's Third-Party End-of-Life Policy.

Migration Considerations

  • If you are upgrading from Zoomdata 2.6.1 to the latest version of Composer, you can change the default http port to enable https for your environment. For information and steps, see Configuration Property Files.

    If you are upgrading a Zoomdata environment older than 3.7 to Composer version 6 or later, upgrade first to Composer 5.9 and then upgrade to Composer version 6 or later. Otherwise, the upgrade will not work.

  • If you are upgrading to a newer version of Composer and you also want to change your encryption mode, perform the upgrade first and complete the steps described in Changing the Encryption Mode.

  • Manually upgrading Composer no longer provides the Java Runtime Environment (JRE) needed for Composer to start. Make sure you have Java 11.0.5 or later installed before you manually install or manually upgrade to Composer 5.8 or later. If you do not, Composer will not start.

  • Due to the upgrade of the HashiCorp Consul (service discovery) version from 0.7.5 to 1.2.2, custom connectors built before Zoomdata 3.2 ( built for versions 3.1 or earlier versions) will not appear after you migrate to Zoomdata 3.7 (or later) or to Composer 5 (or later). This is caused by incompatibilities between old connectors and the new Consul. To make your custom connectors compatible with Zoomdata 3.7 (or later) and Composer 5 (or later), you must migrate the connectors as described in Custom Connector Migration.

    This migration step is required only for custom connectors built with Zoomdata versions earlier than 3.2 or for connectors that were present before Zoomdata 3.2 but that are now deprecated (for example, the Hive on Tez connector, which was replaced by the Hive connector in Zoomdata 3.7).

  • Zoomdata version 3.2 (or later) and Composer 5 (or later) versions use headless Google Chrome instead of Firefox for the Screenshot microservice. See Setting Up the Screenshot Microservice.