Service migration when deploying SuperMap iserver war package

author yyy

Preface

         at present SuperMap iServer war The package can be deployed in a variety of middleware under a variety of operating systems . Use war Package deployment SuperMap iServer when , You need to install and configure JRE/JDK、SuperMap iObjects Java Environment, etc . 

         While deploying iServer war We will encounter this kind of problem when packaging ： In the deployment war Previously used SuperMap iServer The complete package of , Now, because of some special circumstances, we need to SuperMap iServer Redeploy to new middleware such as ：

1. SuperMap iServer Self contained Apache Tomcat Outdated Version , It does not meet the actual use requirements of the project , Need to upgrade Apache Tomcat edition ;

2. Due to the project and the actual situation , Out of commission Apache Tomcat, It needs to be replaced with other middleware products , Such as Dongfang Tong TonggWeb、 Kingdee Apusic Application Server、 Zhongchuang InforSuite AS etc. .

         So when you encounter the above problems , For those already in iServer Whether the services in use can also be synchronously migrated to the newly deployed middleware SuperMap iServer war What's in the bag ？

         We all know , In ordinary SuperMap iServer in , We can migrate services in two ways ：1、 The original iServer Of webapps\iserver\WEB-INF In the catalog iserver-services.xml Replace file with new iServer In the same directory ;2、 In the original iServer Use... In the interface “ Backup and recovery ” Function to generate backup package , Then put it in the same place as the new package , In the new iServer Use in “ Backup and recovery ” Function recovery backup package , In this way, the service will migrate to the new iServer It's in .

        Next, we will provide you with two ideas to solve the problem of deployment war How to perform service migration when packaging .

iServer war Service migration of packages

         Through the above situation, we need to know about war What is the service migration of the package , How to move ; First, we need to know iServer.war What middleware packages are deployed on 、 How to deploy 、 This war What does the package contain 、 How to use it after deployment ;

surface 1：SuperMap iServer war Middleware supported by the package

Middleware name	edition
Apache Tomcat	8.5.x
GlassFish	3.x
IBM WebSphere Application Server	8.5.5.9
WildFly Application Server	10.1.0.Final
Jetty	8.x/9.x
Oracle WebLogic Server	12c(12.1.3)
Kingdee Apusic Application Server	6.0
Eastcom TongWeb	5.0/6.0/7.0

surface 2：SuperMap iServer war What is included in the complete package

file name	Content description
iserver.war	uperMap iServer The core of , Contains library files 、 The configuration file 、 Demonstration data and other information . Use this war Packages can get SuperMap iServer All functions on the server side .iserver.war Accessed after publishing URI by ：http://<server>:<port>/iserver/services. if iserver.war Was renamed , For example, rename it to renameiserver.war, Then the access address is http://<server>:<port>/renameiserver/services.
iserver#help.war	SuperMap iServer Help documentation and sample code for , Use this war The package can publish help documents online .
iserver#iClient.war	SuperMap iServer Client software development kit for , namely iClient.war Package contains iClient The library files 、iClient Help documentation and iClient Sample code . Use this war Packages can get iClient The demonstration program effect .
Guide_smiserver_war_chn.pdf	SuperMap iServer The readme of .
BUILD_* file	SuperMap iServer Version of （ from * Content identification of ）.
licenses	Deposit SuperMap iServer The license agreement and statement of the open source library used .
support_win_x64.zip	be used for Windows x64 System dependencies , Include SuperMap iObjects Java、JRE、SuperMap Installation package of license configuration management tool 、vcredist etc. .
support_linux_x64.tar.gz	be used for Linux x64 System dependencies , Include SuperMap iObjects Java、JRE etc. .
support_arm64.tar.gz	be used for ARM 64 System dependencies , Include SuperMap iObjects Java、JRE etc. .

         For specific middleware ,SuperMap iServer war Packages all have different operation deployment methods , Here we can refer to SuperMap iServer To select the appropriate operation war Deployment of packages (supermap.com.cn) Deploy .

         Through the above operations, we have SuperMap iServer war Deploy the package to the middleware that meets the actual requirements , You can find it in the middleware folder , Copy to the corresponding directory iserver.war、iserver#help.war、iserver#iClient.war These three war The package will be automatically decompressed , The unzipped directory structures are described as follows ：

surface 3：SuperMap iServer war Directory structure after package decompression

iserver.war	iserver#help.war	iserver#iClient.war
data Folder ：SuperMap iServer Demonstration data in .	html Folder ：HTML Format SuperMap iServer help , For publishing online help .	forJavaScript Folder ： In the service mode GIS In Architecture , oriented HTML 5 Application development , Support multiple terminals 、 Cross browser client development platform . for3D Folder ： be based on SuperMap UGC The underlying class libraries and OpenGL 3D function development kit of 3D graphics processing library .
META-INF Folder ： contain MANIFEST.MF file , describe SuperMap iServer 10i(2021) Version information for .	META-INF Folder ： contain MANIFEST.MF file , describe SuperMap iServer 10i(2021) Version information for .	META-INF Folder ： contain MANIFEST.MF file , describe SuperMap iServer 10i(2021) Version information for .
output Folder ：SuperMap iServer The default output path of the cached image .	samplecode Folder ：SuperMap iServer Server side demo code .	resources Folder ： Deposit iserver#iClient.war Pictures used on the home page .
resources Folder ： Deposit SuperMap iServer Pictures used on the home page 、css file 、js Documents, etc. .	*.chm file ：CHM Format SuperMap iServer help .	index.htm file ： Client software development kit （iClient） Enumeration of contents .
WEB-INF Folder ： Deposit SuperMap iServer Rely on the jar file 、 Configuration files and so on .	WEB-INF Folder ：Web The configuration file .	WEB-INF Folder ：Web The configuration file .

         Then comes the key step , Through the information above , We know war Package deployment is mainly aimed at iserver.war From this bag , After decompression, a “iserver” Folder , And the main data 、 Configuration files are stored in this folder , So we can use this idea to expand , Migrate existing services to new services war In bag ; Then the following will be tomcat As an example war Service migration of packages ;

One 、 Replace the deployed war Package data and configuration files

        First of all, we are in Apache Tomcat The central department has signed the download from the official website SuperMap iServer war package , start-up tomcat And access iServer normal  (http://localhost:8080/iserver), Access access list , You can see both of them iServer Sample services ;

​

         Then you can directly In the new iserver in Data and configuration files can be modified and migrated through the following operations ;

        1、 Due to the present iserver/data All stored in iServer Sample data for , So we need to change the original iServer All the data are stored here again data Under the table of contents , The original data Remove or rename ;

        2、 Then delete META-INF In the catalog “war-tracker” file ( This file belongs to the war Package generated tracker , For new content , You need to remove ), eliminate output Cache in ;

        3、 take WEB-INF Under the iserver-services.xml Replace the file with the original iServer Of , In replacement xml You need to pay attention to changing the absolute path of the file to a relative path and making its location point to /data Data saved under the directory ( If you do not need the original sample service , Need to put iserver-services-samples.xml The file can also be deleted );

        4、 Finally restart Tomcat, visit iServer It is found that there is only the first service in the current service list , This indicates that the service migration is normal .

​

Two 、 The original iServer Repackage the corresponding content into war

        Through the first method, we can learn , Most middleware is directly read during deployment iserver.war package , And then decompress the deployed , So our second method here can repackage the required content into war, Then make it read directly .

         Then you can directly In the original iServer Of webapps\iserver Directory Through the following operations, you can modify the required content again, migrate and configure it, and then package it ;

        1、 Migrate the data that has been published as a service to a new folder , And name this folder data,

        2、 take iserver.war In bag META-INF Copy folder to current directory ,

        3、 Empty output All cache folders and files in the directory ,

        4、 modify iserver-services.xml file , take xml All parameter paths containing data in the file are changed from absolute paths to relative paths , And this relative path is for 1 Medium data Catalog ,

        5、 We need to pay attention to , Current WEB-INF The folder also contains information about war Other files for package configuration , Also need to consider , Here we can directly iserver.war In bag WEB-INF Directory to replace , And then modify it directly iserver-services.xml file ,

        6、 Finally, re - set this iserver The directory uses the command jar -cvf iserver.war * Pack it up iserver.war The format of , And then war Put the bag in tomcat Of webapps Under the table of contents , Restart again tomcat visit iServer(http://localhost:8080/iserver) Discoverer iServer The service of has been migrated to tomcat In middleware .

matters needing attention

1) When migrating services in two ways, we can find , All the data to be migrated is stored in webapps\iserver\data Under this catalog , This directory cannot be moved ;

2) Migration service configuration file iserver-services.xml The data path in the file must be written as a relative path “./data/****”;

3) About WEB-INF Be sure to note that the directory also contains war Other files for package configuration , To save operating steps , Consider copying directly iserver.war Contents of the package .

Expand

        About iServer.war The normal service migration of the package has been completed , So for other services , For example, processing automation services 、 Use iServer Built in spark And how to migrate ？
         To use war Package processing automation service , Please confirm war Whether the environment configuration before package deployment is correct ,war After the package is deployed successfully , You need to perform the following operations on each platform in turn to configure the environment for processing automated services ：

war Package processing automation service configuration
        1、 Unzip the corresponding platform support Compressed files , You can see that there are geoprocessing、objectsjava、iObjectsForSpark and spark Folder ;(support_win_x64.zip or support_linux_x64.tar.gz or support_arm64.tar.gz)

        2、 stay iserver Folder （ Middleware deployment iserver.war Generated on ） Create a new one at the upper level of the directory support Folder , Will step 1 Extract... From the directory geoprocessing、objectsjava、iObjectsForSpark and spark Folder is placed in ;

        3、 After restarting the middleware , Revisit iServer, It can be found that the processing automation service can be accessed and used normally .

war Built in package spark Cluster configuration

         Refer to the above processing automation service configuration , You also need to configure the corresponding cluster environment .