Central Configuration - Detailed Explanation

  • 7020954
  • 08-Oct-2015
  • 07-Aug-2017


Post Redline 3.5.0 build 992 - present 4.x versions


Central Configuration - Detailed Explanation


Central Configuration

In the past, it was necessary to configure each Redline Agent by editing the associated rlagent.conf file. This can be tedious and easily prone to errors. It was also very difficult to remember the unique naming of each agent type and the configuration that followed. This often results in support calls that ultimately lead to support configuring the customers system. That is no longer necessary. Redline 3.5 and later employs a new configuration tool for monitoring GroupWise. Dubbed the Central Configuration, the only part of the rlagent.conf file that requires editing is the [CCenter1] section. Simply install the Redline Agent on the server to be monitored, and add the Registration Name, Code, IP, and Port of the Control Center. Start the Redline Agent. It will register with the Control Center. From there, click on the Redline Agent, and then the Manage page. It is this page for each Redline Agent where their monitored agents will be configured.

Here are a few guidelines:

First, it is not necessary to add a Redline type agent. In fact, the “Redline” option has been removed from the drop-down selection. This is because the Redline Agent now registers by default, and you are in fact managing the settings for that very agent. To add the Redline agent in the manage page would be like telling the Redline Agent to monitor another Redline agent. It doesn’t make sense.

Second, it is good advice to add the HOST if it is not already there. From the pull down, select Host, and check the enabled box. Click okay to continue.

From this point on, add each agent to be monitored. Each agent will be registered to the Control Center within one to two cycles of the Redline Agent. Be patient, this could take several minutes.

That’s it. For those that are curious about how all this works, it’s pretty simple. When a configuration change is made, the Control Center creates an xml file and within it is a command which instructs the Redline Agent to refresh its configuration. The xml file is titled by the Redline Agents GUID number with an xml extension. i.e. “2.xml”.

Upgrading from Redline 3

The new Central Configuration is ready for the upgrading of older Redline versions as well. After updating the Control Center, simply update the Redline Agent to 3.5 and start it. Redline will continue to monitor the already registered agents and it will import the settings from the old rlagent.conf file into the new Central Configuration database so they can be managed through the WebUI.

Regarding the import of existing agents, the –f parameter is no longer necessary. The 3.5 Redline Agent will always look in the rlagent.conf file initially and send any agent lists to the CC. The CC will determine if the agent already exists or not, then it will create the configuration and send it back to the Agent.

The rlagent.conf plays a much smaller role in this version of Redline as opposed to previous versions. Only global settings (managed in the CC), Control Center IP/PORT, and Registration Name/Code are needed. All monitored agents with the exception of the HOST are managed from the Control Center now.

Additional Information

This article was originally published in the GWAVA knowledgebase as article ID 2626