502. Getting started with Foretify Manager Installation

Foretify Manager is a web server platform, designed to execute and manage AD/ADAS V&V flows. For more details, see Introducing Foretify Manager.

This guide will walk you through setting up Foretify Manager and its core dependencies.

502.1 Configuration and Working Directory Setup

All configuration files, such as application.properties, and other persistent data, including the Elastic keystore, should be placed in a dedicated Foretellix folder, rather than in the versioned install directories. This folder can also contain the installation itself. Service files must be updated so that the application’s WorkingDirectory points to this folder, ensuring that the application can locate its configuration at runtime. This setup protects configuration and persistent files from being overwritten during version updates.

502.2 Database Prerequisites

Foretify Manager requires Elasticsearch to store Test Runs & Intervals, and PostgreSQL to store application data. For more details on setting up, configuring, and integrating with these, see Prerequisites.

502.3 Installing Foretify Manager

See Install and start Foretify Manager for details on setting up and starting Foretify Manager.

502.3.1 User management and authentication

Foretify Manager can be integrated with existing user management & authentication services.

For more details, see Integrate with LDAP or Integrate with Okta Single Sign-On (SSO).

502.3.2 Securing Foretify Manager

Foretify Manager can be secured using HTTPS (SSL) for encrypted communication.

See Secure Foretify Manager for configuration details.

502.4 Advanced flows

Foretify Manager can be extended with additional services depending on your use cases. These services are not mandatory for basic operation but unlock advanced features.

502.4.1 Run Data Server

Foretify Manager allows debugging specific test runs natively via Single Run Debugger.

As most of the debugging data associated with the test run (e.g. Visualizer frames, traces, logs, etc.) isn't uploaded into Foretify Manager's database, it is read from disk or cloud storage in runtime.

When dealing with longer test runs, which contain larger data sizes, Foretify Manager will benefit from buffering this data by a separate Run Data Server.

For more details on how to set up and configure this service, see Foretify Manager Test Run Data Server.

502.4.2 Running Foretify Jobs at scale

Foretify Manager can integrate with your Kubernetes (K8s) cluster to run a large number of Foretify jobs at scale.

See Dispatcher Configuration for details on setting up and configuring the Dispatcher and K8s Orchestrator services.

502.4.3 Execution Manager flows (Controlled Availability)

For Controlled Availability users only, Foretify Manager offers an integrated Execution Manager that enables orchestration, management, and execution of scalable user flows such as "Extract Scenario & Run" and "Run CI/CD Tests".

The Execution Manager must be set up and requires Apache Airflow to manage the execution pipelines. See Setting up Execution Manager and Apache Airflow for details.

502.4.4 Triage

Foretify Manager can perform rule-based triage operations natively (see Triaging test suite results).

For more complex triage operations it is also possible to write custom Python rules scripts and run them as part of the Triage flow. The service running these rules is the Python Rules Service, which is communicating with Foretify Manager via RabbitMQ -- a messaging broker.

See Integrating with RabbitMQ and Setting up Python Rules Service for details on setting these up.

502.4.5 Integrating with Requirements Management systems

Foretify Manager can integrate with external Requirements Management systems (for example, to keep track of the requirements testing coverage).

See Integrate a Requirements Management Tool for details.