Installing Detect Services

The HCL installation package comes as tarball which includes NameServer, Kafka, PinPoint and FastPast services.

Installing services

After configuring the MariaDB, reach out to the HCL Support team to download the HCL Detect package containing HCL_Detect_x.x.x_Docker_Services_Installer.zip, HCL_Detect_x.x.x_Docker_Feed_Image.zip, HCL_Detect_x.x.x_Docker_Tomcat_Image.zip and Helm charts.

The installation process begins by unzipping the "HCL_Detect_x.x.x_Docker_Services_Installer.zip" file using the following command.

unzip  HCL_Detect_x.x.x_Docker_Services_Installer.zip
The extracted folder contains "HCL_Detect_acme-x.x.x-rhelxx.tar.gz". Now, un-tar the software tarball using the following command.
Note: The rhel version referred above is for reference, and it might change accordingly to the specific releases of HCL Detect.
tar xvzf HCL_Detect_acme-x.x.x-rhelxx.tar.gz

After successful extraction, the tar package contains the following folders and files as shown in image below.

Before installing the Detect, ensure to run ‘dependency_checker’ available under the drive/bin folder to list dependencies with the required versions and installation status for each package.

After untaring the installation file, in the terminal navigate to drive/bin folder. Now, you are ready to perform the configuration steps:

$cd drive/bin
$ ./installer

For more information on interactive inputs in the terminal, refer to Installing Detect.

Now, the configuration is completed, a test can be executed. To run any HCL Detect application, the shell where the application is going to run must be configured by invoking the environment_setter script located in (<extracted acme tar location>/drive/bin/) folder:

$ ./environment_setter

Once the script is source'd, several environment variables are configured and activated, indicating that we are ready to start an HCL Detect application.

Before starting the detect application, update the nameServicePort number in the drive.json file (suggested before pinpoint) available in the drive/etc folder.

"nameServicePort": 41232
Similarly, in the runtime_environment.json file, update the network section as shown below:
  • "ipV6Available": false,
  • "usingIpV4": true

To start the Detect services, navigate to the directory drive/bin, and run the below command.

./services_manager start -o -p -s -t

In the producer_config.properties file, available in the acme/etc folder, edit the bootstrap.servers key with the VM IP address as shown below.

bootstrap.servers=<VM IP address>:9092
Note: Copy the Acme and instance_home folders to PVC.