Enhanced IBM Connections Monitoring

in Blog, panagenda news, Products

panagenda Greenlight and Connections Expert allow monitoring at all levels of your IBM Connections environment. The focus of the two solutions are distributed as follows:

In this blog post I want to dive with you into the technical details of Connections Monitoring. IBM Connections analysis with ConnectionsExpert will be the topic of a future blog post.

Overview

Comprehensive IBM Connections monitoring is divided into the following sections:

The Network

The foundation is of course the networking level. Without the network, nothing would work.

Monitoring all different ports on the Websphere application server level (SOAP Connectors, Defaulthost, etc.), as well LDAP and DB2 ports are only few of those which one should monitor closely.

Operating System

Monitoring of the operating system is very important for example to detect certain bottlenecks (disk utilization, CPU load, etc.) and to be able to act proactively.

The screenshot shows the results of the GreenLight Performance Count sensor which allows to retrieve ANY Performance Counter from your Windows host.

Furthermore, you can monitor the status of your Windows services.

Monitoring the system services of your WebSphere Deployment Manager and the WebSphere Node Agent are only two of many examples.

Considering approximately 50 percent of all IBM Connections installations run on Linux, we also provide comprehensive OS monitoring for Unix-based platforms.

LDAP

The LDAP Directory is an important element of your deployment. It is used for authentication as well as for populating user data into Connections.

Although we are able to check the availability of the LDAP Directory using a Shell script, the LDAP source’s availability does not necessarily mean everything is functioning. We therefore extended the measurement to one or multiple users being are looked up in the corporate LDAP Directory where the output is the time it took to find the user in your directory.

WebSphere

It’s also essential to check the status for each of the installed WebSphere applications (Search, Activities, Communities, etc.).

However, panagenda Connections monitoring can do much more!

  • Analyzing the utilization of the Webpools/Threadpools
  • JVM, Memory, CPU Utilization, …
  • Data Source Check
    With our Data Sources check, we go one step further. In addition to our DB2 monitoring (see below), we also monitor whether the underlying WebSphere Application (e.g. Communities) can access the backend databases. This check is important as it allows you to determine whether the Connections application itself successfully connects and communicates with the backend database. A simple port check or connectivity check to the DB2 is not sufficient.

DB2

Besides of doing usual connectivity checks to your backend Connections database, we can do much more when it comes to retrieving valuable content.

In GreenLight it’s easy to query content using your own SQL statements. Popular examples are:

  • Active vs. inactive users
  • Orphaned files vs. total files
  • Public vs. private vs. moderated Community
  • Information about database schemas
  • And much more

IBM Connections

Of course we are able to retrieve all out of the box Connections Metrics which you could access via certain URLs.

Example: Files: https://<FQDN>/files/app#/statistics

Furthermore, certain Security checks are performed where our solutions determine whether

  • DSX Admin roles within an application are only assigned to administrators only and not to normal end users
  • Search Admin roles are assigned to the right group of people
  • Anonymous users can use certain applications (Reader roles)

User Simulations

Last but not least: Simulations! It doesn’t matter if you want to perform a simulation against the IBM Connections Cloud or against your on-premises Connections environment.

GreenLight authenticates and checks the availability of all your Connections applications from an end user perspective!

The user simulations show you several interesting things:

  • HTTP server is running and is accessible
  • Application is running
  • User can logon to Connections
    • LDAP authentication is working
    • User has a profile
    • SSO is working

Example (for IBM Connections Cloud)

Do you have any additional questions? Leave us a comment or contact us directly.

Stay in touch, more articles are about to come!

Recommended Posts

Leave a Comment

Kontaktieren Sie uns!

Sie haben eine Frage? Kontaktieren Sie uns und ein Mitarbeiter wird sich bei Ihnen melden!