Starting/Stopping iServer

Feedback

As a Web application, SuperMap iServer can be deployed to a variety of Web servers. By default, SuperMap iServer is deployed on Tomcat included with the package. Starting Tomcat will start SuperMap iServer and all of its services.

In the %SuperMap iServer_HOME%\bin directory, batch files for starting/stopping SuperMap iServer are provided:

In addition, in %SuperMap iServer_HOME%/bin directory, iserver.bat/iserver.sh are provided to debug SuperMap iServer. Usage:

Usage:  iserver [Option]

Option:

        -start              Start iServer

        -stop               Stop iServer

        -v / -version    Display the version of iServer, including parameters of JRE/JDK, SuperMap iObjects Java, etc.

        -help               Show Help

After installing the SuperMap iServer setup package on Windows, you can start the service with the shortcut in the Start menu. Take Windows XP as an example:

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/manager/; 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 configuration 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"

Set communication port number for the monitoring process

SuperMap iServer offers two ways to set the communication port for the daemon process and the main process.

  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>