|Before installing or upgrading to any Composer 5.9.x version, please read Composer 5.9.x Installation and Upgrade Process for Multiple Context Paths.|
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. The Chrome-based Screenshot microservice cannot be installed in CentOS 6 environments because the Google Chrome dependencies do not support that platform. See Setting Up the Screenshot Microservice.
The installation script works in the following environments:
- Centos 6.5, 7, and 8
- Ubuntu 16.04, and 18
- RHEL 6, 7 and 8
Java 11.0.5 or later is required to run Composer.
Support for CentOS 6 will be deprecated when it is no longer supported by Red Hat Enterprise Linux (RHEL).
If your environment is running CentOS 6, you must manually install OpenJDK 11. OpenJDK 11 is available from various vendors, such as AWS Corretto, OpenJDK11, or Oracle JDK11. See Manually Installing OpenJDK 11.
When you attempt to install or upgrade Composer in a CentOS 6 environment that does not have OpenJDK 11 installed, the installation script will start, but will produce FAIL messages during its execution because of the missing OpenJDK 11 software. When the installation script runs, the Composer binaries are upgraded to the latest version, but you will not be able to start Composer without first manually installing OpenJDK 11.
An option to install OpenJDK is included in the installation and upgrade scripts provided by Composer. If you skip this option or if you install or upgrade the product manually, make sure that Java 11.0.5 (or later) is installed. If you do not, Composer will not start after the installation.
The target server for the Composer software should meet the following prerequisites:
The server must be connected to the Internet.
If this is a new (fresh) installation, the server must not have PostgreSQL already installed. (Not required for upgrades.)
If this is a new (fresh) installation, the server must not contain any
zoomdatafolders or property files from previous versions. If a previous version of Zoomdata or Composer was installed on this server, ensure that all property files have been deleted before running the installer script.(Not required for upgrades.)
The user installing Composer must be able to use the
sudocommand on the server.
|If you do not have an internet connection on the server on which Composer is being installed, download the Composer installation package and load it onto the target server. After this is done, you can manually install Composer. See Installing Composer Manually.|
|If the server on which Composer is to be installed does not meet all of the prerequisites, see Alternative Installation Options.|
If you are installing Composer on a server running CentOS v6, see Configuring the Maximum Number of Open Processes and Files. Be sure to complete this prerequisite setup before installing Composer. If your server is running either CentOS 7 or 8 or Ubuntu 16 or 18, then you can skip this prerequisite step.
In addition, Composer benefits from having time synchronization in your network. Specifically, Composer leverages the Network Time Protocol daemon (NTPD), which performs time synchronization of networked servers to Coordinated Universal Time (UTC). If needed, read Using the Network Time Protocol to Synchronize Time for instructions to set this up.
After you have made any needed adjustments to your network configurations, you can continue the installation process.