understand_server_com

Understanding Parent-Child Communication

The Product Directory enumerates the parent server and all child servers in a Control Manager network.

The following table describes the connection status in a Control Manager cascading tree:

Parent and child server relationship

Action	Parent Child	Parent Child	Parent Child	Parent Child	Stand- Alone Server
Direct unregistration	n
Registration					n
Uninstall Control Manager (save Database)	n	n	n	n	n
Uninstall Control Manager (delete Database)	n	n	n	n	n

Based on the table:

Direct unregistration of a disabled child server is not allowed
Direct or forced unregistration of an active child server retains the child server record in the parent server database and removes the child server record in the child server database
If you uninstall the Control Manager application on a disabled child server, save the Control database, reinstall Control Manager, and then re-register it to the same parent server, the child server status will remain the same—disabled
If you uninstall the Control Manager application on a disabled child server, delete the Control database, reinstall Control Manager, and then re-register it to the same parent server, the child server status will become active

In addition, the table highlights the following parent and child server relationship when the cascading relationship is set to enable:

The parent server:

Polls each child servers to update the Status Summary screen in real time
Updates a child server connection status every three minutes

The child server:

Sends logs to the parent server
Sends new or updated report profiles

Disabling a child server does not permanently cut the connection between the two Control Manager servers. The parent and child server connection is still present. The parent server issues a single command to the child server — Enable Cascading Control Manager. Once the child server receives and accepts this command, the parent server resumes managing the child server.