Internal documentation only

This page has been marked as draft.

Introduction to State Only Active Console (pilot feature)

Overview Copied

Caution

The State Only Active Console is a pilot feature. This feature is subject to change.

To run the Active Console in State Only mode, follow these steps:

1. Download the 6.4.x binaries of Active Console.
2. Open the ActiveConsoleStateOnly.exe file. The State Only Active Console configuration is stored in a binary workspace file in SWX format.

The State Only Active Console can run concurrently with a regular Active Console. However, if you are using a Gateway earlier than 6.4.x with the State Only Active Console, it will behave as a regular Active Console instead.

In this mode, the Active Console only uses the StateOnly synchronization level of the Gateway, eliminating the need to retrieve cell and headline data, and providing a more lightweight alternative. With less overhead, the State Only Active Console can sustain more Gateway connections.

Workspace Settings Copied

Take note of the following behaviors when using a State Only Active Console:

• The State Only Active Console configuration is stored in a binary workspace file in SWX format.
• Similar to the normal Active Console, there are a number of start-up flags and settings that you can define that modify the behavior and configuration of the State Only Active Console while it is running. These settings are configured by modifying ActiveConsoleStateOnly.gci.
• Workspace configurations and logs are saved in <User>\AppData\Roaming\ActiveConsoleStateOnly for the State Only Active Console, while the normal Active Console saves these files in <User>\AppData\Roaming\ActiveConsoleStateOnly.
• When running the State Only Active Console, the Gateway Setup Editor will always run in standalone mode.

Limitations of State Only Active Console Copied

• The Sampling Errors list view is no longer available in the State Overview Tab.

• The following features are no longer available:

  • Dashboard
  • Evaluate Paths dockable
  • Modifier
  • Notifier Manager
  • Remote dockable
  • Time Definitions
  • Use of cells, headlines, and descendants in XPaths

• A path is rejected if any of the following conditions are met:

  • The path contains rows, row, or cell as node names.
  • The last node in the path is not any of the following: Gateway, Netprobe, Managed Entity, Sampler, or a Dataview.
  • The path does not contain an ancestor or ancestor-or-self.
  • Path validation in the State Only Active Console does not allow descendants and descendants-or-self but allows ancestors.

• Critical and Warning (Under Selection) list view now references samplers instead of cells: