Workflow: Automated TAS server preparation (TAS 8)

Run the automated procedure to prepare the TAS servers in your deployment for installation readiness, as an alternative to preparing them manually. Automated server preparation can be run on a clean deployment, or after partial manual server preparation.

When run after partial or complete manual server preparation, be aware of the following:

  • Firewall ports: If the firewalld utility packaged in the RHEL distro kernel is not used, configure the firewall ports as defined in the Firewall Ports Configuration.

  • If the data directory (opt/app/data by default), exists, it is recursively removed and recreated. If you are re-running automated server preparation, make sure to back up the TAS tar files, if you need a copy.

  • GlusterFS volumes: Existing GlusterFS volumes on TAS Datastore servers are removed and new volumes are created.

  • NetworkManager service: The NetworkManager service is restarted.

  • Docker engine configuration:

    • Automated preparation overrides the existing configuration if any.

    • To support overlay2 on an XFS backing filesystem, d_type=true must be enabled.

      To verify, run xfs_info [mount point] and validate the partition's ftype is 1.

      [mount point] is mount path for the Docker home directory, set by default to /var/lib/docker.

  • Keys for tas_maint and tas_inst users are generated and distributed automatically to allow SSH access without passwords.

Automated TAS server preparation must be run on the TAS Management server.

Workflow 

  1. Download and extract ISO package for TAS installation

    Download the ISO package for TAS installation, and mount it in the specified location. Then extract the TAR files required for automated server preparation from the TAS installation mount.

  2. Download and extract ISO package for RPM (TAS 8)

    Optional. Mount the RPM ISO and install the Verint repository on all TAS servers in your deployment, including the Management server. Alternatively, you can install the required third-party products on your own.

  3. Save CA certificates for TAS servers

    Copy the P12 and the root CA certificates on the TAS Management server in /opt/app/TAS_DRG. Make sure that you rename the root CA certificate as ca.pem before you copy them.

  4. Customize inventory file

    Customize the default inventory file with the topology that defines the customer's deployment, including server host names and other settings. Verify that the inventory file template matches the site deployment level as L1, L2, or L3 - standard or high-availability configurations.

  5. Run automated server preparation

    Run the automated server preparation script to prepare the TAS servers. The process runs in the background and takes several minutes to complete.