Changes

  defaults  force  migrate

  defaults  force  migrate

Dateien unter ''defaults'

=====Dateien unter ''defaults'=====

Defaults files are simple text files. If the corresponding database key/property already exists, it is skipped. Otherwise, the key/property is created and the value loaded. For example, this file:

Defaults files are simple text files. If the corresponding database key/property already exists, it is skipped. Otherwise, the key/property is created and the value loaded. For example, this file:

[root@gsxdev1 db]# cat configuration/defaults/sshd/status

[root@gsxdev1 db]# cat configuration/defaults/sshd/status

disabled

disabled

would create the sshd database entry if it doesn't already exist, create the status property for that entry, again if it doesn't already exist, and finally set the status property to disabled.

would create the sshd database entry if it doesn't already exist, create the status property for that entry, again if it doesn't already exist, and finally set the status property to disabled.

Force files

 

=====Force files=====

Force files are just like defaults files, except they overwrite the existing value. So, this file:

Force files are just like defaults files, except they overwrite the existing value. So, this file:

[root@gsxdev1 db]# cat configuration/force/sysconfig/ReleaseVersion

[root@gsxdev1 db]# cat configuration/force/sysconfig/ReleaseVersion

7.0rc2

7.1.3

would create the ReleaseVersion property of the sysconfig entry and unconditionally set its value to 7.0rc2

would create the ReleaseVersion property of the sysconfig entry and unconditionally set its value to 7.0rc2

Migrate fragments

 

=====Migrate fragments=====

Migrate fragments are small pieces of Perl text which can be used to perform more complex migrations than is possible with defaults and force files. They would normally be used to replace database keys or properties with new names, or to adjust policy settings during an upgrade.

Migrate fragments are small pieces of Perl text which can be used to perform more complex migrations than is possible with defaults and force files. They would normally be used to replace database keys or properties with new names, or to adjust policy settings during an upgrade.

       It is also possible to initialize and migrate database values in action scripts, but creation of migrate fragments is strongly preferred. Creating defaults is a simple matter of creating text files and migrate fragments require far less code than action scripts.

       It is also possible to initialize and migrate database values in action scripts, but creation of migrate fragments is strongly preferred. Creating defaults is a simple matter of creating text files and migrate fragments require far less code than action scripts.

Evaluation order: migrate, defaults, force

=====Evaluation order: migrate, defaults, force=====

When a database is loaded:

When a database is loaded:

This order allows migration of old format entries to occur prior to loading of new default values. Remember, defaults will not change an existing database property.

This order allows migration of old format entries to occur prior to loading of new default values. Remember, defaults will not change an existing database property.

Forcing database initialization

 

=====Forcing database initialization=====

The database is initialized during a number of events, including console-save, so a call to signal-event console-save will evaluate all of the database fragments.

The database is initialized during a number of events, including console-save, so a call to signal-event console-save will evaluate all of the database fragments.

     It is an SME Server requirement that all database entries and configuration files must be correctly configured after a "reconfiguration reboot". This is available from the console and server manager and performs the post-upgrade and reboot events. Packages should also provide links in other events (e.g. "email-update" for email related changes) to provide reconfiguration without the reboot.

     It is an SME Server requirement that all database entries and configuration files must be correctly configured after a "reconfiguration reboot". This is available from the console and server manager and performs the post-upgrade and reboot events. Packages should also provide links in other events (e.g. "email-update" for email related changes) to provide reconfiguration without the reboot.

Important notes about the configuration databases

=====Important notes about the configuration databases=====

     *

     *