Product Upgrade Guide

Feedback

Different versions of SuperMap iServer have different functions. When you need to upgrade from a lower version to a higher version, you can refer to the upgrade steps.

Upgrade steps

Check whether the current system meets the use requirements of the system configuration of the new version of iServer. For details, please refer to System Configuration Requirements .
Determine the license information for the new version of iServer. For more information, see Licensing Configuration .
According to Table 1, migration requires services, system configuration and other related documents.

Table 1 List of services and system files involved in iServer upgrade

Belonging category	Description	Storage mode	The local storage location
Data source	Data sources used by the service	Local or shared storage (such as spatial database)	The detailed path can be viewed through service management-service detail
Service configuration	Published service configuration information	Local or database	{ISERVER_HOME}/webapps/iserver/WEB-INF/iserver-services.xml
	service interfacesconfig file	Local or database	{ISERVER_HOME}/webapps/iserver/WEB-INF/iserver-services-interfaces.xml
	Configuration information of iServer built-in services (such as geometry and map services)	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/isercer-services-buildin.xml
	data catalog servicesconfig file	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/iserver- datacatalog.xml (stored in iserver-datastores.xml prior to 10)
	The config file of the sample service	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/iserver-services-samples.xml
	REST Apply config file	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/iserver-rest-appContext.xml
	The config file of the extension resource	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/iserver-rest-resources.xml
	data flow servicesconfig file	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/iserver-dataflow.xml
	processing automationconfig file	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/iserver-geoprocessing.xml
	Machine learning config file	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/iserver-machinelearning.xml
	stream processing model setting films	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/iserver-streaming.xml
	Database for storing blockchain information	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/iserver-blockchain.db
Service security	Database that stores security information such as users, roles, and so on	Local or database	{ISERVER_HOME}/webapps/iserver/WEB-INF/iserver-security.db
Service security	Database for storing service author ization information	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/iserver-services.db
Cache	Cache file	Local	{ISERVER_HOME}/webapps/iserver/output directory
System configuration	Back up the file	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/backup directory
	System configuration information (including meta information, cluster, license, etc.)	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/iserver-system.xml
	Tomcat related configuration	Local	{ISERVER_HOME}/conf/server.xml
	Tomcat's own supported security config	Local	{ISERVER_HOME}/conf/web.xml
Log and log configuration	Log	Local	{ISERVER_HOME}/logs directory
	distributed analysis logsconfiguration information	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/distribute-log4j.properties
	Log config file	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/iserver-log4j.properties
System security	Security information	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/shiro.ini
System security	GIS system security config	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/web.xml
Other configurations	Web Print Layout Template	Local	{ISERVER_HOME}/webapps/iserver/templates/webprinting-layouts Catalog
	kml style configuration	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/config/kmlStyles.xml
	Account Information Compliance Verification Rule Configuration	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/config/accountInfoComplianceRules.xml
	Users develop their own extended content	Local	{ISERVER_HOME}/webapps/iserver/WEB-INF/lib or WEB-INF directory

When the file is stored locally, the file is directly copied to the new version iServer from the corresponding path of the old version iServer In the corresponding file path. If there is any change in the following config file, you need to edit and modify the contents in the new version according to the existing configuration of the old version:

iserver-services-interfaces.xml 、iserver-system.xml 、shiro.ini 、server.xml 、 web.xml 、iserver-geoprocessing.xml.

When the file is stored in the database, you only need to connect to the same database in the new version of iServer to achieve the purpose of migration synchronization.

Check the service, user, permission and other migration results.

Automatic upgrade

SuperMap iServer provides a script file for product upgrades that can be done quickly Upgrades to the iServer version, including autoUpgrade.bat files (for Windows Platform) and autoUpgrade.sh files (for Linux platforms). The product upgrade script can help you automatically migrate the services and system configuration files (see Table 1) involved in iServer upgrade. You can download the upgrade script directly from the SuperMap iServer official website help documentation: iServer Product Upgrade Guide .

The following describes how to use the upgrade script:

1. Before upgrading the iServer, make a backup of the old version of the iServer to avoid possible accidents.

2. If you are running an older version of iServer to be upgraded, stop the service first.

3. Extract the new iServer package that will be used to replace the older version of iServer.

4.Run the upgrade script. In the Windows system, double-click to run the autoUpgrade.bat, and in the Linux system, enter the following command:

./autoUpgrade.sh

5. According to the upgrade script prompt, enter the old version and new version of iServer path respectively. Take the Windows environment as an example as follows:

Please enter old version package path : F:\supermap-iserver-11.0.0-windows-x64

Please enter new version package path : F:\supermap-iserver-11.0.1-windows-x64

6. After the script is run, the services and system config files involved in the upgrade of the old version of iServer have been migrated to the new version of iServer. The upgrade of the product has been completed. Run the {IServer_HOME_NEW}\bin\startup.bat (startup.sh on Linux) to use the new version iServer.