Generating a configuration snapshot
When you have finished the configuration for your environment (see the chapters: Inventory and Configuration), you may create a snapshot of your current setup. A snapshot is taken by creating a new revision using the "commit" function within the environment. This task generates the necessary configuration files for all Nevis software components.
- navajo.xml for the nevisProxy instance
- bc.properties, qslog.conf and the global.conf files of the nevisProxy instance are automatically updated (partial update, you may edit these files outside the change marks written by nevisAdmin)
- web.xml of the nevisProxy service
- Sample error pages are created for the nevisProxy service the very first time a configuration snapshot is created (no exiting web.xml file)
- esauth4.xml file of the nevisAuth instance
- the log4j.xml file of the nevisAuth, nevisSign, nevisPortal, nevisLogRend, and nevisIDM instances if log settings have been configured for this instance type, see the chapter "Log settings".
- IcapServer instance: the clamd.conf, c-icap.conf, and freshclam.conf files are generated if they do not exist
After the commit command has been executed, the new revision is ready to be deployed to the instances.
The configuration generation process includes multiple validation functions which may write an event message if mandatory configuration parameters are missing, see the chapter Messages. Resolve these issues and recreate the configuration before you deploy the configuration.