Managing DROPS in a main server and node configuration allows you to define the main DROPS Server that pilots one or several node DROPS servers in order to delegate deployment tasks to them.
This kind of architecture is useful:
- To separate the responsibilities on different parts of the organization.
- To dispatch the execution workload on different DROPS servers.
- To centralize all the deployment history on a unique point even if the real executions have been delegated.
You need to configure your servers settings before using the solution. In the server's 
Configuration Categories, you define if the current server is a node or a main server.
Further configuration is required specifically for the node and for the main server.
Main / node server settings
Remote scheduled deployment instance settings
Node connection settings
Node monitoring settings
Node synchronization settings
When you have set the server as node, the DROPS navigator lets you access the view to register to the main server and to synchronize with it. When you have set the server as main, the DROPS navigator lets you have access to the views to manage registered nodes.
Once the status of the servers is defined, the main and the node servers are ready to be paired and their data to be synchronized.
When the servers synchronized, the main server can be used to pilot the deployments which are executed by the node server.
