Starting/Stopping iServer

SuperMap iServer, as a Web application, can be deployed to a variety of Web servers. SuperMap iServer is deployed in the built-in Tomcat by default. Starting Tomcat can start SuperMap iServer and also start the services provided by SuperMap iServer.

In the %SuperMap iServer_HOME%/bin directory, a batch file is provided for starting/stopping the SuperMap iServer server:

• startup.bat : Starting SuperMap iServer server on Windows system
• startup.sh : Starting SuperMap iServer server on Linux system
• shutdown.bat : Stopping SuperMap iServer server on Windows system
• shutdown.sh : Stop SuperMap iServer server on Linux system

In addition, iserver.bat/isurver.sh is provided in the %SuperMap iServer_HOME%/bin directory to start and debug SuperMap iServer, with the following usage:

Usage: iserver [options]

Options:

        -start              Startup iServer

        -stop               Shutdown iServer

        -v / -version    Display the version information of iServer, including parameter information such as JRE/JDK, SuperMap iOObjects Java, etc. used

        -help               Display help

After installing SuperMap iServer on Windows platforms using the setup package, you can also find it in the Start menu Shortcut for SuperMap iServer start/stop (Windows XP as an example):

• Start → Program → SuperMap → SuperMap iServer 2025 → Start iServer Service
• Start → Program → SuperMap → SuperMap iServer 2025 → Stop iServer Service

Note: SuperMap iEdge doesn't offer setup installation package. The startup mode above is only for SuperMap iServer.

When SuperMap iServer starts, it will publish the default GIS services automatically. You can manage services by accessing iServer Manager (in local host): http://localhost:8090/iserver/admin-ui/home/; and you can view all GIS services published by SuperMap iServer by accessing http://localhost:8090/iserver/services (in local host). (iEdge doesn't provide any sample GIS services, so the service list is empty the first time the iEdge service is start.)

SuperMap iServer provides the Automatic Restart function for restarting the server automatically when it is shut down abnormally, you can enable or disable this function with the <restartWhenCrash> parameter in System Config File.

Advanced Configuration

Start SuperMap iServer as Windows service

If you have registered Tomcat as a Windows service, you can start SuperMap iServer as a Windows service. Please refer to Start iServer in the way of Windows service.

Specify the configuration file directory to start SuperMap iServer

SuperMap iServer supports to start with a specified config path. This config directory contains all configuration information of SuperMap iServer. For non-war packages, the default config path is %SuperMap iServer_HOME%/webapps/iserver/WEB-INF. For the war package, the default config path is %iserver_server_path%/WEB-INF).

While starting, you can set the Java virtual machine parameter class with the name of iserver.config to specify the config path. For example, if iServer runs on Windows:

set JAVA_OPTS=%JAVA_OPTS% -Diserver.config="D:/WEB-INF1"

startup.bat

Then it will use the configuration files under "D:/WEB-INF1"directory to deploy SuperMap iServer.

For Tomcat, you can customize server.xml of Tomcat and config file of SuperMap iServer at the same time:

Start:

set JAVA_OPTS=%JAVA_OPTS% -Diserver.config="D:/WEB-INF1"

startup.bat -config="D:/server1.xml"

Stop:

shutdown.bat -config="D:/server1.xml"

Start SuperMap iServer by specifying the application server name

SuperMap iServer provides a default URL root address, http://<ip>:<port>/iserver, if you need to change the "iserver" to another application server name and display the jump by default when accessing the iServer. Please follow the following steps:

1. Change the name of the iserver folder under %SuperMap iServer_HOME%/webapps to the specified name;

2. Change the iserver in the %SuperMap iServer_HOME%/webapps/ROOT/index.htm file to the name from the previous step in the following code

    window.onload=function ()

    {

      window.location.href="iserver";

    }

Set communication port number of monitoring process

SuperMap iServer supports specifying the communication port number between the daemon and the main process. And provide two ways to set it:

1. Modify setenv.sh/setenv.bat

   Open [iServer root directory]\bin\setenv.sh (Linux) or setenv.bat (Windows), add the following contents:

   set com.supermap.server.mainprocessport=8091

   set com.supermap.server.daemonprocessport=8092

2. Modify iserver-system.xml

   Open [iServer root directory\webapps\iserver\WEB-INF\iserver-system.xml, add the following contents under <properties> node:

       <daemonprocessport>8092</daemonprocessport> 

       <mainprocessport>8091</mainprocessport>

   The complete configuration is as follows:

    <properties> 
       <outputPath>../../webapps/{contextPath}/output</outputPath>  
       <outputSite>http://{ip}:{port}/{contextPath}/output/</outputSite>  
       <realspaceCacheAccessKey>70 39 -37 -116 -91 105 73 111 -71 90 -24 -17 -115 80 -56 -17</realspaceCacheAccessKey>  
       <realspaceSecurityEnabled>true</realspaceSecurityEnabled>  
       <envCheckEnabled>true</envCheckEnabled>  
       <daemonprocessport>8092</daemonprocessport>  
       <mainprocessport>8091</mainprocessport> 
     </properties>