System requirements

Overview Copied

This page outlines the software requirements and other prerequisites before you run the Active Console.

Active Console is a standalone Java and C++ application. It uses its own JRE included on the binary package, which means that any Java versions can be used on the operating system.

Note

Beginning Geneos 7.3.0, a Windows Active Console package without JRE is available if you who wish to run the Active Console using the Java installed on your machine.

Check that the Active Console can connect to the Gateway machines and port where the Gateway data is accessible.

Beginning Geneos version 5.0.0, this component is only compatible with other Geneos components that are version 3.6.0 or higher. For more information, see the Geneos Compatibility Matrix.

Minimum requirements Copied

The following minimum requirements must be met:

Expand table

The Active Console does not support cross-platform functions and operations. Importing components, such as dashboards, workspaces, list view settings, customised dataviews, and dockables, from one supported platform to another, may be successful at first. However, the import is not expected to work properly.

For Linux Copied

When Security-Enhanced Linux (SELinux) is running in Enforcing mode, it may deny certain functions of Geneos depending on the implemented configurations and policies. To see which functions SELinux denies, check the audit log. The log is typically located in /var/log/audit.log, where the log type entry is AVC. The audit log provides the details of any denied access. For example, denied connection to the TCP port. If you experience issues related to this mode, you may opt to disable SELinux, or create policy modules to grant the required access. Please contact your administrator or security team for assistance.

Active Console with packaged version of Java Copied

Active Console is supplied with a Java version as part of the installation package, this is referred to as the packaged Java. This is independent of the native Java that you may already have installed on your local machine. The packaged Java with the Active Console binaries is installed into a separate subdirectory which means that the native and packaged Java versions are isolated from one another. Updating either one of the Java versions will have no impact on the other.

It is recommended that you use the packaged version of Java with Active Console for the following reasons:

• The packaged version of Java with Active Console is always tested and verified. We would not be able to perform adequate testing against all possible versions of Java.
• It reduces support complexity and helps resolve issues quickly, as there is a one-to-one relationship between the product version and the Java version.
• Not relying on the native Java installed on a machine means it is simpler to upgrade and maintain Active Console using a single package.

Active Console without Java Copied

For Windows, an Active Console package is available without its own packaged Java. This means that the Active Console will rely on the native Java that you have installed on your local machine. During startup, the Active Console will look for a valid JAVA_HOME directory or a valid Java installation in the machine. Refer to the startup settings for more information.

Note

Ensure that your machine is using Java 17 or higher for the Active Console to successfully start up. Refer to the Java support compatibility matrix for more information.

Database support Copied

The Active Console supports the following databases:

• MySQL
• Sybase

  Note

  The jConnect for JDBC driver by Sybase is not included in the Active Console package. If you are using Sybase for generating history charts, you must manually supply the jConnect for JDBC driver file by following the steps outlined below.

• Oracle
• MSSQL

To view the list of supported versions, see Database support.

Installing the jConnect JDBC driver for Active Console Copied

1. Download the jConnect driver from the SAP portal. Use SAP ASE version 16.0 or up to ensure compatibility.

2. Copy the jConnect driver file from the jConnect-16_X > classes folder within the Sybase client or database installation. The filename may vary depending on the version you downloaded. For example:

   • jconn4.jar for version 16.0
   • jconn42.jar for version 16.1

3. Place the jConnect driver file in the jars > JDBC folder within your Active Console installation.

Success

Once the jConnect driver file has been copied to the correct location within the Active Console installation, you should be able to successfully connect to Sybase to generate history charts.