HERO is installed using Docker.
You can install HERO on Linux 64 bit operating system.
Google Chrome
Mozilla Firefox (Quantum recommended)
Docker CE (Community Edition) Engine 18.09.0 or later
Docker Compose 1.23.2 or later
Docker must be installed and configured with the following minimum requirements:
CPUs 4
RAM 24GB
Swap 1024MB
HERO must be installed and configured with the following minimum requirements:
CPU 64 bit, 2+ core
RAM 32GB+
Storage 200 GB HDD
HERO can monitor Workload Automation environments starting from Workload Automation version 9.1. in which the prerequisite feature Plan data replication in the database (also known as "mirroring") is enabled. For more information about the “mirroring” feature, see Replicating plan data in the database.
HERO supports direct monitoring for Master Domain Manager (MDM), Backup Domain Manager (BKM), and Dynamic Workload Console (DWC). Monitoring for all the remaining agents is performed using the database on MDM.
The supported operating systems for MDM, BKM, and DWC are AIX and Linux 64 bit.
Once the monitoring scripts are deployed to the target workstations, they are scheduled by HERO to run on a regular basis.
The HERO server requires a connection to each DB2 or Oracle instance in the monitored environments from which to collect throughput data and information about the agent status.
The following prerequisites must be met for HERO to monitor Workload Automation environments:
SSH server daemon must be up (SSH daemon allows authentication with username and password)
The user specified at workstation discovery time, i.e. the owner of the WA instance, must have the following permissions:
Permission to write in his own home directory and in the <TWA_HOME> directory. Access permission must be through SSH.
Permission to read the WA registries.
Permission to create job and job stream definitions, to submit, and cancel them.
For some recovery actions, and for some monitors based on previous versions of Workload Automation, it might be necessary to run actions as “sudo”. In this case, the sudo user must be authorized without specifying a password.
It must be possible for the target workstation to open an https or http connection with the HERO server (typically using port 8080, but the port number can be customized).
Starting from version 9.5, Workload Automation can be deployed on Docker containers. During the server discovery process, if containerized components are present on a server, you are requested to provide the image name for each component to be retrieved.
For the communication between HERO and the product servers, make sure ports are opened as follows:
From HERO to the product servers:
SSH port (default port 22), used by HERO to connect to the product servers
From the product servers to HERO:
https on port 443 (default port) or any custom port, required for status updating
For machines connected through WinRM protocol over https, port 5986 must be opened.
Hardware requirements depend on the number of WA servers where you want to run the prediction, but you must consider that CPUs with AVX instructions support are required (for this reason, old CPUs might not work).
To start the training process, it is recommended to have at least 10 hours of new data for the prediction procedure.
The performance, in terms of computational time of the training (or retraining) procedure, is highly dependent on the technical specifications of the machine on which it runs.
There are no minimal requirements with the exception of 4GB of RAM to run FBProphet. With 8 GB of RAM available and an Intel core i7 processor, the estimated time is about 12 minutes for the training phase per server.
In addition to this time, the swap in / out time for writing and reading from OpenSearch should also be considered.