Genius EAM – Management Summary

The solution consists of two main components. On the one hand an application monitoring software developed specifically for the Genius platform. On the other hand, support experts with many years of experience in complex IT infrastructures and large customer projects. This combination enables the implementation of an often proactive and comprehensive monitoring of Genius MFP, Genius BPM and Genius Server.

How does the service work (prerequisites)

You conclude a service contract with us, in which you select which services and to what extent they should be included. It always includes the installation and configuration of Genius EAM software components, adjustments to fine tune thresholds, etc.

Where to install?

Installation of Genius EAM software components on suitable hardware. That is, the Genius EAM server in a data center, at Genius Bytes or on-site (On Premise).
Installation of the agents. Each Genius Server is assigned an agent that monitors its core functions. The database gets its own agent, which runs on one of the Genius Servers in the cluster as well as a performance agent on one of the cluster servers.
If necessary, your IT team will set up the appropriate ports.

How do servers and agents communicate?

The communication between the agents and the Genius EAM server is secured as follows:
Communication is always from agent to server. Data transfer is secured by certificates, HTTPS and TCP over SSL. The agents themselves do not open TCP/UDP ports. This is the reason why a Genius EAM Server can also be operated in a data center/cloud.

Genius EAM overview architecture

Tasks of Genius EAM agents

Agents and Genius EAM

The agents are designed to consume as few resources as possible. The goal of the agents is to get the metrics from a server and send them directly to the Genius EAM server.

Each agent requires 150 MB of disk space to start the JVM and to write a cache file if the Genius EAM server is not available.

When the Genius EAM server is available again, the agent sends all cached information directly from the cached file. The agent never stores the metrics in memory.

There are 3 agents available to monitor the Genius Server:

CORE Agent

This agent has the task of checking the status of the application servers, the services and
to enter key figures.

Database Agent

Serves to monitor the database and collects data related to database tables. It is extremely important because the Genius Server is a database application.

Performance Agent

This collects speed data, for example to evaluate and compare response times, etc.

Note:
The Core Agent indirectly enables the monitoring of external components such as authentication providers like Active Directory or LDAP.

Features of Genius EAM

Self-monitoring

Additionally, Genius EAM sends and collects readings about itself and the agents to monitor the health status of the agent and the server, so you have an always-on monitoring platform.

User Management

The Genius EAM has an independent user administration. This is intentional as to not to create dependencies on other services.
Rights and roles can be assigned to individual persons or groups.

Dashboard (main overview)

Genius EAM screenshot from dashboard

The solution is accessed via a web frontend. It does not matter whether you access the dashboard via mobile device, tablet or computer.

You can see the status of the monitored infrastructure at a quick glance. Portlets, which are combinable components of the user interface, help you to get an immediate overview.

The color of a segment can be green, yellow, red or blue.
Blue means that this segment is only informative.
Green (everything OK), yellow (warning) and red (error) are used like a traffic light.

Functional overview

The dashboard in turn shows the segments (portlets) of various custom function overviews.

These function overviews are all basically the same. The example of the overview for incoming print jobs shows the principle.

Sample: Incoming print job overview

In this view you can see the inputs of the direct and pull print jobs. The Genius Server receives the jobs/files e.g. from PC clients, Microsoft Server, SAP, Main Frame or host systems.
The input values should usually be in the lower range.

In addition, the number of incorrectly executed jobs (e.g. for an interrupted TCP connection) and the live errors (errors in the last 30 seconds) are displayed.

If many errors are shown in the incoming data or thresholds are exceeded, the Genius Bytes Analysis Team itself (if they have been granted access) or a customer administrator of the monitored systems will request short-term action. This could include deleting erroneous data directly on the affected server, etc. to then fix the cause.

The disk space shows you how much free space is available on the disk on which you store your print jobs. This depends essentially on two factors.
Direct print jobs are usually deleted immediately after the print files have been spooled. Furthermore, we have Pull Printing jobs, which will remain for a longer period of time depending on the configured retention time.

The last figure shows you the performance when receiving print jobs. How much time is needed to receive the jobs? To calculate this is one of the tasks that a Genius Server performs with the highest priority, before any other tasks, so that no print job is lost.
If our analysts see longer runtimes, they will check with the system administrator to see if everything is okay, or if the physical TCP/IP network is having problems.

More than one – overview…

Similarly, the other function overviews show similarly detailed information about the status of the systems according to their intended use.

Further function overviews are:

  • Cluster overview
  • Print orders input
  • Direct print jobs
  • Pull Printing jobs
  • Authentication overview
  • BPM overview
  • DMS overview
  • Mail connections
  • Database overview
  • Hardware overview

The aim of the main overview and the individual other overviews is to give a visual impression of the situation and to graphically prepare the data of the agents.

Inspector

Genius EAM screenshot from inspector

The configuration center of the Genius EAM Server is the Inspector.

This area is used to determine which data (metrics) are of interest. This data can be grouped and combined into alarm groups.

The thresholds for warnings and alarms are defined for the respective monitored data. If a threshold value is exceeded, either a warning or an alarm is displayed in the function overviews and the main overview, depending on the definition.

Detailed, visualized reports can also be created here. This form of documentation is often very helpful for the subsequent analysis of error causes.

Samples from Genius EAM Reports

Depending on the Genius Server version, its agents can provide remote configuration of a server, server log files and further analysis data. Depending on the server version, it is also possible to restart the service.

YouTube

By loading the video, you agree to YouTube's privacy policy.
Learn more

Load video

Slider