> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure a Synthetic Scenario

> GermainUX synthetic scenarios can run with Firefox, Google Chrome, or Microsoft Edge in headless mode.

Components
[`RPA Bot Recorder`](https://docs.germainux.com/main/germain-ux-rpa-bot-recorder)

Service
`Automation`

Availability
2014.1 or later

> [card] [Firefox in Headless Mode](#firefox-in-headless-mode)
>
> Run Firefox without a display

> [card] [Google Chrome in Headless Mode](#google-chrome-in-headless-mode)
>
> Run Chrome without a display

> [card] [Microsoft Edge in Headless Mode](#microsoft-edge-in-headless-mode)
>
> Run Edge without a display

> [card] [Legacy Internet Explorer Configuration](#legacy-internet-explorer-configuration)
>
> Visible desktop session required

## Configure Browsers for Synthetic Scenarios

GermainUX synthetic scenarios can run with Firefox, Google Chrome, or Microsoft Edge in headless mode. Legacy Internet Explorer scenarios require a visible Windows desktop session and a dedicated configuration.

Before deployment, confirm that:

* The browser is installed on the GermainUX Engine host.
* The corresponding WebDriver is available.
* The browser and WebDriver versions are compatible.
* The Engine account can execute both the browser and driver.
* The synthetic scenario is configured to use the correct browser, driver, Monitoring Node, and Engine.

Modern Selenium releases include Selenium Manager, which can manage supported browser drivers automatically. If the GermainUX deployment requires an explicit driver path, install and configure the driver manually. See [Selenium Manager](https://www.selenium.dev/documentation/selenium_manager/).

## Firefox in Headless Mode

### Install Firefox

Install the current stable Firefox release using the package-management process approved for your Linux distribution.

#### Ubuntu

```text theme={null}
sudo apt update
sudo apt install firefox
```

Verify the installation:

```text theme={null}
firefox --version
```

Firefox installation methods can vary by Ubuntu release and package policy.

### Install GeckoDriver

Download a GeckoDriver release compatible with the installed Firefox version:

* [GeckoDriver releases](https://github.com/mozilla/geckodriver/releases)
* [Firefox and GeckoDriver compatibility](https://firefox-source-docs.mozilla.org/testing/geckodriver/Support.html)

After downloading the correct Linux archive:

```text theme={null}
tar -xf geckodriver-<VERSION>-linux64.tar.gz
sudo mv geckodriver /usr/local/bin/geckodriver
sudo chmod +x /usr/local/bin/geckodriver
geckodriver --version
```

Replace `<VERSION>` with the selected GeckoDriver version.

### Configure the Scenario

In the GermainUX synthetic scenario:

**1. Select Firefox as the browser**

**2. Enable headless execution**

**3. Set the driver path when required: `/usr/local/bin/geckodriver `**

**4. Select the Monitoring Node and Engine**

**5. Test the scenario manually before enabling its schedule**

## Google Chrome in Headless Mode

### Install Google Chrome

Install the current stable Chrome release using Google’s supported Linux package.

For Debian- or Ubuntu-based systems, download the current `.deb` package and install it using the organization’s approved package-management process.

Verify the installation:

```text theme={null}
google-chrome --version
```

### Install ChromeDriver

For Chrome 115 and later, Chrome and ChromeDriver releases are distributed through Chrome for Testing. Select a ChromeDriver version compatible with the installed Chrome version. See [ChromeDriver version selection](https://developer.chrome.com/docs/chromedriver/downloads/version-selection) and [Chrome for Testing availability](https://googlechromelabs.github.io/chrome-for-testing/).

After downloading the correct Linux archive:

```text theme={null}
unzip chromedriver-linux64.zip
sudo mv chromedriver-linux64/chromedriver /usr/local/bin/chromedriver
sudo chmod +x /usr/local/bin/chromedriver
chromedriver --version
```

### Configure the Scenario

In the GermainUX synthetic scenario:

**1. Select Chrome as the browser**

**2. Enable headless execution**

**3. Set the driver path when required: `/usr/local/bin/chromedriver `**

**4. Select the Monitoring Node and Engine**

**5. Test the scenario manually before enabling its schedule**

## Microsoft Edge in Headless Mode

### Install Microsoft Edge

Install the current stable Microsoft Edge release using Microsoft’s supported Linux repository or installation package.

Verify the installation:

```text theme={null}
microsoft-edge --version
```

### Install Edge WebDriver

Download Microsoft Edge WebDriver from the official [Edge WebDriver page](https://developer.microsoft.com/en-us/microsoft-edge/tools/webdriver/#downloads).

The first three components of the Edge WebDriver version must match the installed Microsoft Edge version. See [Microsoft Edge WebDriver documentation](https://learn.microsoft.com/en-us/microsoft-edge/webdriver/).

After downloading the appropriate Linux archive:

```text theme={null}
unzip edgedriver_linux64.zip
sudo mv msedgedriver /usr/local/bin/msedgedriver
sudo chmod +x /usr/local/bin/msedgedriver
msedgedriver --version
```

### Configure the Scenario

In the GermainUX synthetic scenario:

**1. Select Microsoft Edge as the browser**

**2. Enable headless execution**

**3. Set the driver path when required: `/usr/local/bin/msedgedriver `**

**4. Select the Monitoring Node and Engine**

**5. Test the scenario manually before enabling its schedule**

## Legacy Internet Explorer Configuration

Internet Explorer does not support headless execution. It requires a visible Windows desktop session and should be used only for supported legacy applications.

### Prerequisites

| Requirement | Description |
| - | - |
| **GermainUX version** | 8.6.13 or later |
| **Desktop session** | The GermainUX Engine must run within an active Windows desktop session. |
| **Administrator account** | The account running the Engine must have the required administrator privileges. |
| **PowerShell** | The host must allow the required PowerShell scripts to execute. |
| **Dedicated Engine** | Use a dedicated Engine Manager and Engine instance for Internet Explorer monitoring. |

### Configure the Dedicated Engine

Configure the Engine using the standard [Engine setup procedure](https://docs.germainux.com/main/engine-deployment.md), but dedicate the instance to Internet Explorer synthetic monitoring.

Set a unique node name in `germain-bootstrap.properties`:

```text theme={null}
germain.bootstrap.node=IE Synthetic Monitoring
```

If multiple Engine Managers run on the same host, assign each one a different unused port.

### Configure a Different Engine Manager Port

**1. Open GermainUX Workspace > Germain > State**

**2. Select the applicable Engine Manager or Monitoring Node**

**3. Update State Store URL to reference the new port**

**4. Update State Store Server Port with the same unused port**

**5. Save the configuration and restart the applicable component**

## Validate the Browser Configuration

Before scheduling the scenario:

**1. Run the browser-version command**

**2. Run the WebDriver-version command**

**3. Confirm that the Engine account can execute both**

**4. Run the scenario manually**

**5. Confirm that it completes successfully**

**6. Review its screenshots, video, events, duration, and errors**

**7. Enable the recurring schedule only after validation**

## Get Help

> [card] [Contact GermainUX Support](https://docs.germainux.com/main/support.md)
>
> The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

> [card] Can't find what you need?
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.