Backup for Server Configuration |
SuperMap iServer supports backup and recovery of server configuration information, user and authorization information. This is done by backing up and restoring the config file located at WEB-INF (【SuperMap iServer installation directory】\webapps\iserver\WEB-INF), including:
When the service is restored, the system will retain the current initial administrator (that is, the administrator created when the system is initialized) and will not be overwritten by the initial administrator saved in the backup file, because the two may be different in some special cases.
This can be done on the backup page of the service manager (http://localhost:8090/iserver/admin-ui/advanced/backupAndRestore).
That is, the current configuration information of the server is backed up. SuperMap iServer provides a default config file backup, packaged as config_default.zip at 【SuperMap iServer_HOME】\webapps\iserver\WEB-INF\lib\iserver-all-xxxx(xxxx represents the version number of SuperMap iServer.jar file.
In the "Backup" tab of the "Backup" page, enter the backup file name, click the "Backup" button, and prompt "Backup server is configured successfully", indicating that the backup is successful. After the config file is backed up, it will be packaged as "backup file name.zip" and placed in 【SuperMap iServer_HOME】\webapps\iserver\WEB-INF\backup.
In addition, iServer also provides the function of server config filescheduled backup to ensure system stability. The backup content and the saved path of the backup file are consistent with the normal backup function. Please refer to Server Config Files Cheduled Backup Settings for details on how to set the scheduled backup function
That is, restore the backed-up server configuration information, including "Restore" and "Restore to server factory Configuration. "Restore" means that the user selects the backup config file to restore, and "Restore to Default Configuration" means that the server configuration is restored to the default configuration (using the default config file backup: config_default.zip).
In the "Restore" tab of the "backup" page, if you select the config file to be restored and click the "Restore" button, it will be restored to the required configuration information; If you clicked the "Restore to server factory configuration" button, the default server configuration is restored.
Cross-version upgrade considerations:
1. When your service configuration information is stored in the configuration file, if you need to perform cross version backup and recovery, you need to delete the iserver-system.xml and iserver-services interfaces. xml configuration files from the backup file. In addition, if you have added security related configuration information, please copy the new entry from the new version shiro.ini file to the backup 【iServer installation directory 】\webapps\iserver\WEB-INF\backup\ backup ZIP file \shiro.ini file. If you have not added any security configuration information, you can directly delete the shiro.ini file from the backup file.
2. If your service is stored in the database, you do not need to perform the above backup and recovery operations when upgrading the version. Connect the database storing the configuration information of the previous version through the service configuration information storage. The purpose of restoring the service configuration information can be achieved