Enabling Insight Monitor
Insight Monitor can be enabled on runtime servers or in a collective controller. You must add the features to the server.xml files and configure secured communication between the servers in your topology.
Before you begin
You must first decide whether you want to have operational metrics over all server types in your topology or only the runtime servers. To include all server types, you must establish a single administrative domain in the form of a Liberty collective.
About this task
Choose to add a collective controller server or use only the runtime servers.
A collective controller is a centralized administrative control point where operations such as MBean routing, file transfer, and cluster management in a collective are performed. A core role of the collective controller is to receive information from the members within the collective so that the data can be retrieved readily without having to invoke an operation on each individual member. Depending on your high availability requirements, you might want to complement your existing servers with a collective controller server. To use a collective controller, you must create a new server from the collective controller template and add each server as member of the collective. Then, you must add the monitor feature to all of the server members in your topology.
A collective controller server provides a simple control point for monitoring operational status of all servers in the same administrative domain. Since a Liberty collective has one or more members; typically many, it involves extra installation and configuration steps to get the collective controller operational.
If you want to use only the runtime servers, then add the adminCenter feature to a catalog server and the monitor feature to all of the runtime server.xml files.
In both cases, you must authenticate communication between the servers.
For more information, see Setting up Admin center.