AD Linux Install - Additional Node
Review this link for details on downloading Workbench AD: Downloading Anomaly Detection (AD).
Important
- Ensure you have an installed and running AD Primary Node before installing any AD Additional Nodes
Please use the following steps to install Workbench AD 9.x.xxx.xx on Linux:
- Create a working directory (i.e. ~/tmp) adding the AD_9.x.xxx.xx_LINUX.tar.gz file
- Run tar zxf AD_9.x.xxx.xx_LINUX.tar.gz to extract the downloaded AD_Installer_Linux.tar.gz compressed file.
- Navigate into the ip\linux folder
- Run tar zxf AD_9.x.xxx.xx_Installer_Linux.tar.gz to extract AD Installer content; the following files should be extracted:
- install.sh
- jdk-11.0.2/
- lib/
- AD_9.x.xxx.xx_Installer.jar
- Run ./install.sh (DO NOT prefix ./install.sh with sudo)
- Genesys Care Workbench Anomaly Detection - Installation
- Genesys Workbench License Agreement
- Press Enter to view the Genesys Workbench License Agreement
- Review license agreement
- Genesys Workbench Terms and Conditions
- Workbench Installation Mode:
- There are 2 Installation Modes:
- New Installation - no Workbench Anomaly Detection components are yet running on this host/node
- Upgrade - you already have Workbench Anomaly Detection running on this host/node and wish to upgrade
- Press Enter for default value (new installation)Warning*AD currently does not support upgrade capability
*Therefore select New Installation and not Upgrade during the AD 9.x.xxx.xx installation
- There are 2 Installation Modes:
- Workbench AD Installation Type
- Continue with the next steps for both: Primary or Additional Node Installation.
- DEFAULT or CUSTOM installationInstall Workbench AD with Default or Custom settings:
- Default - the respective Workbench AD Default settings will be used.
- default settings being paths, ports, etc.
- Custom - or, if required, you can change the default settings by selecting a Custom install. In Custom mode, the following parameters are required:
- For Workbench Anomaly Detection:
- Binary files location
- Configuration files location
- Data files location
- Log files location
- Socket port
- Incoming data port from Logstash
- HTTP AD API port
- For Workbench Metricbeat:
- Binary files location
- Data files location
- Log files location
- HTTP port
- For Workbench Agent:
- For Workbench Anomaly Detection:
- Default - the respective Workbench AD Default settings will be used.
- Provide the Workbench Primary Zookeeper IP Address and Port.
- Provide the Workbench Anomaly Detection installation folder location:
- AD Hostname:AD Hostname:
- This Hostname will be utilized by the Workbench solution components.
- Primary components to be installed: Information on which Workbench components are being installed on this host/node
- Select / provide the Service Account details for the Workbench components:
- The Workbench Anomaly Detection installation will now progress
- The Workbench Anomaly Detection installation is complete
Post Installation Steps
- Validate (i.e. service --status-all | grep WB) if the AD Additional component Services are running:
- WB Anomaly Detection Node: WB_AnomalyDetection_9.x.xxx.xx
- WB Metricbeat: WB_Metricbeat_9.x.xxx.xx
- WB Agent: WB_Agent_9.x.xxx.xx
- Validate if the new AD host appears in Workbench/Configuration/Hosts as is presented in AD Configuration.
- Follow the steps in Post Installation Configuration if needed.
- If you are installing AD at first time, follow the guidelines given in Using AD to learn how to use the Workbench Anomaly Detection Insights features.
This page was last edited on December 24, 2021, at 18:03.
Comments or questions about this documentation? Contact us for support!