Because configuration data is stored in the Domain Administration Server’s repository (the central repository) and also cached on the node agent’s local machine, the two must be synchronized.
When a node agent is started for the first time, it sends a request to the Domain Administration Server (DAS) for the latest information in the central repository. Once it successfully contacts the DAS and gets configuration information, the node agent is bound to that DAS.
If you created a placeholder node agent on the DAS, when the node agent is started for the first time it gets its configuration from the central repository of the DAS.
During its initial start-up, if the node agent is unable to reach the DAS because the DAS is not running, the node agent stops and remains unbound.
If changes are made in the domain to the node agent’s configuration, they are automatically communicated to the node agent on the local machine while the node agent is running.
If you delete a node agent on the DAS, the next time the node agent synchronizes it stops itself and marks itself as awaiting deletion. Manually delete it using the local asadmin
command delete-node-agent
.
If you explicitly start a server instance with the Admin Console or asadmin
tool, the server instance is synchronized with the central repository. If this synchronization fails, the server instance doesn’t start.
If a node agent starts a server instance without an explicit request through the Admin Console or the asadmin
tool, the repository cache for the server instance is not synchronized. The server instance runs with the configuration as stored in its cache.
See Also: