Differences Between Operavix on Linux and Windows Operating Systems

Authentication

API Keys

Hotkeys in the Automation Module

Configuration File Editing

com.operavix.subsystem.frontend.json file

com.operavix.subsystem.monitoring.json file

com.operavix.subsystem.dashboard.json file

com.operavix.subsystem.automation.json file

com.operavix.subsystem.core.json file

# Differences Between Operavix on Linux and Windows Operating Systems

## Authentication

In the Operavix system on Linux, you cannot use [Standard Windows Authentication#Standard Windows Authentication](3.Platform/6.Authentication.md). This is because Standard Windows Authentication capabilities are provided by the Windows operating system on which the system is installed. Authentication via Active Directory on Linux is possible only through the Kerberos mechanism.

## API Keys

In the Operavix system on Linux, you cannot use [API keys](3.Platform/5.Api_keys.md) with Active Directory authentication. This is because the Windows Integrated Authentication mechanism used to verify API key authenticity is available only on the Windows operating system. Such API keys are suitable for monitoring agents on Windows.

## Hotkeys in the Automation Module

Canvas panning by holding the **Space** key on Linux is available only when using a TrackPoint.

## Configuration File Editing



If Linux is used as the server operating system, settings that can be modified in configuration files are specified through environment variables at Docker container startup.

[!NOTE] Not all settings can be modified this way, as not all are exposed as environment variables.

The parameters you can modify on Linux are listed below.

### com.operavix.subsystem.frontend.json file


|**Parameter**|**Description**|**Note**|
|---|---|---|
|`FE_URL`|Operavix server address|Must be specified in full, including protocol and port|
|`FE_SERVICE_MODE`|Service mode|Disabled by default. To enable, set to `true` (available from version 2308)|
|`FE_SERVICE_MODE_MESSAGE`|Message displayed when service mode is enabled|Appears only if service mode is enabled (available from version 2308)|

### com.operavix.subsystem.monitoring.json file

|**Parameter**|**Description**|**Note**|
|---|---|---|
|`MN_EMAIL_HASHING`|Hashing of data from the **To** and **Cc** fields|Default: `default`. To disable, set to `none`|
|`MN_STORAGE_GUID`|Parameter allows passing a storage GUID for activity data synchronization during system update or restart|By default, the `storage_guid` field is empty; for data synchronization, the GUID of the previous storage is automatically taken from the built-in file-based knowledge base|

### com.operavix.subsystem.dashboard.json file

|**Parameter**|**Description**|**Note**|
|---|---|---|
|`DB_ROWS_LIMIT`|Row limit setting for table export from dashboards|Default: `5000`; any value is allowed|

### com.operavix.subsystem.automation.json file

|**Parameter**|**Description**|**Note**|
|---|---|---|
|`AU_PROD`|Stable version parameter|Default: `true`. If set to `false`, experimental functionality becomes available (available from version 2310)|

### com.operavix.subsystem.core.json file

|**Parameter**|**Description**|**Note**|
|---|---|---|
|`CR_NOTIFICATION_MESSAGE`|Message for the notification dialog|Enabled automatically when a message is set (available from version 2311)|

Description of differences in the Operavix system installed on Linux and Windows operating systems

Installing and Removing the ClickHouse DBMS

System Emails to Users

What Is Operavix

Quick Installation of the Operavix Server Component

Monitoring Agent

JS Tracker (Customer Journey Tracking)

Quick Installation

Quick System Setup

Building a Custom Dashboard

Template-Based Reports for Data Analysis

First Dashboard

What’s Next?

Quick Start 

Functional Architecture

Network Interaction of the System Components

Description of the System Functioning

System Integration with External Automated Systems

Technical Requirements for the Server and Hardware Equipment

Architectural Scheme of the Operavix Application

Network Scheme of the Operavix Application

Glossary

Description of the Operavix System 

Installing, Activating, and Removing the Operavix Application on Windows

Installing the Operavix Application on Linux

Updating Operavix on Windows

Updating Operavix on Linux

Updating Operavix

Cluster Mode Configuration

Installing the Automation Module on a Separate Server

Installing and Running the AI Agent

Installing and Running the Webhook Agent

Instructions for Installing, Updating, and Removing the System

Release Types

License Key

Beta Version Functionality

System Licensing

Working with Databases

Working with the System

System Configuration Files

Prometheus Metrics

Access Roles

Working with GraphQL

Managing System Users

Administration 

Connecting the Application to the ClickHouse Analytical DBMS

Creating User Accounts in ClickHouse

Data Storage Structure in ClickHouse

ClickHouse 

Monitoring Agent Distribution

Monitoring Agent on Windows

Monitoring Agent on Linux

Starting and Stopping the Monitoring Agent

Installing, Updating, and Removing the Monitoring Agent

User Data Logging

Storing Monitoring Agent Logs

Export and Import of User Activity

Collecting Screenshots with the Monitoring Agent

Activity Archiving

Monitoring 

Signing In to the System

How to Recover Your Password

Home Page

Filtering

Navigation in the System

Workspaces

Personal Profile

System Setup

Users

Departments

Bulk Actions

Adding API Keys

Keytab File Creation for the Kerberos Authentication in Active Directory

Configuring Authentication Using OpenID Connect and Keycloak

Configuring SAML Authentication in Keycloak

Adding Authentication

The Monitoring Section

Connections Section

Data Storages

System Tables

System Settings 

Automation Agents

Execution Log

Control Panel

Connections

Automation Blocks

Trigger Blocks

Working with Files

Working with Services

Working with LLM

Tools

Event Processing

Editing a Script

Query and Code Editor

Script Validation and Publishing

Running a Script

Script Example

Automation 

Custom Integrations 

System Events

JS Tracker 

Workspace Access Settings

Adding and Configuring Tables

Table Replacement

Adding and Configuring Processes

Workspace Global Indicators

Display Rules

Data Model Configuration

Packages

General

Dashboard Access Settings

Click Filter

Table Report Export

Browse mode

Edit Mode

Views

Process Explorer

Sphere of Processes

Funnel Сhart

Table

Pivot Table

Strip Сhart

Combined Bar Chart

Bar Chart

Line Chart

Donut Chart

Histogram

Indicator

Percentage KPI

KPI List

Filter

Parameter

Text

Button

Widgets

Sorting

Markdown Usage Rules

Variables

Dimensions and Measures

Global Dashboard Indicators

Running a Script from a Dashboard

Go to the URL

Execute Script

Open View

Update Variable

Actions on Click

Input Methods

Displaying Monitoring Screenshots in Dashboards

Formula Editor

Formula Functions

The process Function

View Configuration in YAML

Widget Configuration in YAML

Dimensions and Measures in YAML

Data Formats and Formatting in YAML

YAML Editor

Dashboards

Report Example

Business Intelligence 

Package Creation Guide

Marketplace 

Configuring User Data Depersonalization upon Deletion in AD

LDAPS Activation

Synchronized Attributes Between the System and AD

Retrieving AD Security Groups Information via GraphQL Query

Configuring User Synchronization with Active Directory

User Synchronization 

Audit Mechanism Description

System Status Monitoring

Implemented Information Security Protection Measures in the System

Audit Logs

Docker Containers

Mutual Authentication Between Application Server and ClickHouse

For Security Administrator 

Known Issues and Limitations 

Parameter	Description	Note
`FE_URL`	Operavix server address	Must be specified in full, including protocol and port
`FE_SERVICE_MODE`	Service mode	Disabled by default. To enable, set to `true` (available from version 2308)
`FE_SERVICE_MODE_MESSAGE`	Message displayed when service mode is enabled	Appears only if service mode is enabled (available from version 2308)

Parameter	Description	Note
`MN_EMAIL_HASHING`	Hashing of data from the To and Cc fields	Default: `default`. To disable, set to `none`
`MN_STORAGE_GUID`	Parameter allows passing a storage GUID for activity data synchronization during system update or restart	By default, the `storage_guid` field is empty; for data synchronization, the GUID of the previous storage is automatically taken from the built-in file-based knowledge base

.css-wsrjzs{display:inline;margin-right:12px;}@media screen and (max-width: 691px){.css-wsrjzs{display:inline-block;margin-right:0;}}Differences Between Operavix on Linux and Windows Operating Systems