This idea is related to the subject of Configuration Management and Infrastructure As Code.
Domino servers can be installed in an automated manner.
But they cannot be configured in an automated manner.
This idea is suggests to introduce an extensive Admin Server API, which in turn could be used by existing, well-established Configuration Management frameworks (e.g. Ansible, Chef, Puppet, Saltstack, etc.).
With this Admin Server API, configuration of the following components should be possible:
Internet Website Document
Web SSO Configuration Document (LTPA Token)
Create/modify/remove Domino Keyring files (KYR/STH files)
Cluster Configuration Document
Add/remove Internet Certifier Documents
Configuration of da.nsf (Directory Assistance)
Configuration of iwaredir.nsf
Configuration of idpcat.nsf
Policy and Policy Settings Documents
Advantages of Configuration Management:
Install and configure Domino as if it was a cloud service (very little expertise required)
Configure Domino servers in an exact predefined manner (avoid misconfigurataions)
Ensure that all Domino servers are configured the same way (avoid misconfigurations, reduce necessity for audits)
Configure a large amount of Domino servers (scalability)
Configure Domino faster (reduce time to deploy)
Send Domino configurations to others (reduce TCO, allow to operate Domino servers with little amount of training, allow sending configuration fixes from support)
[ Toni Feric, Belsoft Collaboration AG ]