In this dialog it is possible to manage the list of existing configurations, like create, duplicate into different scope, activate, import to and export from a scope. Generally there is one configuration per server or application. In some cases it can make sense to use more than one configuration, e.g. in a test environment or if each server (instance) should use its own configuration on the same server machine.

The currently active configuration is highlighted with a star icon at the beginning of its name.

Configurations belong to one of three different, separate "scopes", which determine which Preferences to use as the backing store for the configuration properties. Configurations are saved in the preferences on the system where the server or application is running at. In order to copy a configuration from one scope to another, you can use the Duplicate action. Configurations can be moved between scopes with the drag-and-drop function.

• System - This scope means the configuration is stored in the system preferences and are visible for all users at the current maschine. Only user with administrating rights may be able to change their settings. If the buttons for creation and editing of configurations is not active, you don't have the necessary rights. To gain the rights, start the configuration manager as Administrator (in Windows) or root (in Linux). Services and background processes usually only have access to system resources.
• User - This scope means that the configuration is stored in the user preferences and therefore is only visible for the currently logged in user.
• Temporary - This scope means the configuration is not stored permanently at all, but only used for the current session. They are available while the application is running. After stopping the current process, all temporary configurations will be removed. Temporary configurations are only available if the Configuration Manager is started from an application. This can be used to test the configuration. If you have no write access to the System or User scope, then you can only use the temporary scope to store a configuration.

The following actions are available for each scope, if the user has write access to this scope:

• Create - This will create a new configuration and add it to the selected scope.
• Import - Imports a saved backup copy of a configuration from a file. If the import is started, you have to select a *.properties file from your local file system. If you have chosen one, a dialog appears where you have to enter the name of the configuration.

For each configuration the following actions are available. An action will be deactivated, if the user do not have write access to the scope containing the selected configuration.

• Delete - This will delete a configuration.
• Duplicate - Creates an identical copy of a configuration and adds it to the selected scope. If the user do not have write access to a scope, then it is possible to duplicate it to another scope.
• Export - In order to backup your existing configurations or to use them on another machine, they can be saved in your file system using the export functionality. The settings are saved in a file with the .properties extension and in the format key=value. This file which can then be imported using "Import".
• Rename - This will display a dialog in that you can set a new name for the selected configuration.