Post-installation Configuration |
When starting SuperMap iServer, iServer adopts the default settings defined by the environment configuration script (%SuperMap iServer_HOME%/bin/setenv.sh), and you do not need any post installation configuration to start using iServer.
The default settings include the following:
If you do not want to use the default configuration mentioned above, you can directly modify the script file to use a custom configuration or not use the environment configuration script, and manually set the environment variables to use the custom JRE and JDK. When using custom JRE and iObjects, please ensure that the number of bits for JRE/JDK, iObjects, and iServer is consistent. That is, when using 32-bit iServer, please use 32-bit JRE/JDK iObjects； When using a 64 bit iServer, please use a 64 bit JRE/JDK iObjects.
In addition, the catalina script (%SuperMap iServer_HOME%/bin/catalina.sh) also defines the configuration parameters of iServer for JVM memory, including the initial size of heap memory (- Xms), the maximum size of heap memory (- Xmx), and the memory size that each thread can use (- Xss). If you do not want to use the default configuration, you can directly modify the script file to use a custom configuration. When installing packages using rpm or deb, you can also use custom parameters by manually setting environment variables without using this script.
In addition to the custom configuration described above, if you need to use an Oracle data source, you also need to configure the environment.
If you do not want to use the default configuration during iServer start service, that is, you do not want to use the default JRE and JDK in the environment configuration script, you can directly modify the above script file to use the custom configuration, or you can use the custom configuration by manually setting the environment variables.
In addition to the custom configuration described above, if you need to use an Oracle data source, you also need to configure the environment.
When using a custom JRE by modifying the environment variables, you need to rename or delete the jre directory under the %SuperMap iServer_HOME%/support directory. Because in product packages after SuperMap iServer Java 6R(2012)(version 6.1.0)(excluding), if this is not done, the built-in JRE will continue to be used.
According to the software requirements for using iServer, JRE requires version 11.0.18+10. If you are installing JDK, you need to set JAVA_HOME to the directory of JDK; If JRE is installed, set JRE_HOME to the directory of JRE.
Using the example of configuring the JDK, you can set environment variables in the following ways:
(1) Set the JAVA_HOME in the system's profile file (default path: /etc/profile) as follows:
export JAVA_HOME=directory for/JDK
(2) Make the above settings effective:
source /etc/profile
(3) Execute the echo command to check whether the settings are correct:
echo $JAVA_HOME
The JRE is configured in the same way as the JDK by simply changing the environment variable name to JRE_HOME.
When using custom iObjects by modifying environment variables, you need to rename or delete the objectsJava directory under the %SuperMap iServer_HOME%/support directory. Because in product packages after SuperMap iServer Java 6R (2012) (version 6.1.0) (excluding), if this processing is not done, the built-in SuperMap iObjects Java will continue to be used.
Please configure and use the corresponding version of iObjects according to the software requirements of iServer. If the version is inconsistent, the availability of all services and features of iServer cannot be guaranteed.
The process of setting up the use of custom SuperMap iObjects Java and its font library is as follows:
(1) Set an environment variable named UGO_HOME in the system's profile file (default path is:/ etc/profile）and add $UGO_HOME/Bin to the LD_LIBRARY_PATH variable:
export UGO_HOME=/ the installation directory for SuperMap iObjects Java
export LD_LIBRARY_PATH =$UGO_HOME/Bin:$LD_LIBRARY_PATH
(2) Set the SUPERMAP_ROOT environment variable to point to the parent directory of the fonts folder in the font library. For example, in SuperMap iObjects Java, fonts are default and located in $UGO_HOME/Support. Therefore, SUPERMAP_ROOT can be set as follows:
export SUPERMAP_ROOT=$UGO_HOME/Support
(3) Make the above settings effective:
source /etc/profile
(4) Execute the echo command to check whether the settings are correct:
echo $LD_LIBRARY_PATH
The environment setting script (%SuperMap iServer_HOME%/bin/setenv.sh) used for SuperMap iServer startup also sets the system encoding method. If you modify this environment setting script yourself or configure not to use it when starting services, you will need to manually set the system encoding method.
(1) Set the RedHat system encoding method:
export LANG=zh_CN.UTF-8
(2) Set the SUSE system encoding method:
export LANG=zh_CN.UTF-8
unset LC_CTYPE
Three configurations are supported for using custom JVM memory parameters:
1.Modify the JAVA_OPTS parameter in %SuperMap iServer_HOME%/bin/catalina.sh, such as:
JAVA_OPTS="$JAVA_OPTS -Djava.awt.headless=true -Xms[initial heap memory size] -Xmx[maximum heap memory size] -Xss[usable heap size per thread]"
2.Modify the javaopts.config file in the %SuperMap iServer_HOME%/bin directory, such as:
-Xms[initial heap memory size] -Xmx[maximum heap memory size] -Xss[usable heap size per thread]
3.The process of using custom JVM memory parameters by modifying environment variables is as follows:
(1) Set the SUPERMAP_JAVA_OPTS in the system's profile file (default path:/etc/profile). You can select any of the -Xms, -Xmx, and -Xss parameters for configuration as follows:
export SUPERMAP_JAVA_OPTS="$JAVA_OPTS -Djava.awt.headless=true -Xms[initial heap memory size] -Xmx[maximum heap memory size] -Xss[usable heap size per thread]"
(2) Make the above settings effective:
source /etc/profile
(3) Execute the echo command to check whether the settings are correct:
echo $SUPERMAP_JAVA_OPTS
Note: 1. In classified systems, if permanent environment variables can be configured, it is recommended that you customize JVM memory parameters by configuring the SUPERMAP_JAVA-POTS environment variable; If permanent environment variables cannot be configured, JVM memory parameters need to be customized by configuring the Javaopts.config file. When there are custom JVM memory parameters configured in the above three ways simultaneously in the system, their priority is SUPERMAP_JAVA_OPTS > javaopts.config > catalina(tomcat). The default JAVA_OPTS parameter is configured
If the Oracle data source is used, the following environment variables need to be configured:
(1) Set ORACLE_HOME to point to the installation directory of Oracle; And add $ORACLE_HOME/lib to the LD_LIBRARY_PATH variable, as follows:
export ORACLE_HOME=/Oracle installation directory
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH
export PATH=$PATH:$ORACLE_HOME
(2) If the encoding method of the Oracle database is GBK, please set the NLS_LANG parameter to "simplified chinese"_china.zhs16gbk, as follows:
export NLS_LANG="simplified chinese"_china.zhs16gbk
If the Oracle client is used, after downloading and installing the client of the corresponding system, the following environment variables need to be configured:
(1) Set ORACLE_CLIENT_HOME to point to the installation directory of Oracle Client; And add $TNS_ADMIN to the LD_LIBRARY_PATH variable, as follows:
export ORACLE_HOME=/Oracleclient installation directory
export LD_LIBRARY_PATH=$ORACLE_CLIENT_HOME:$LD_LIBRARY_PATH
export PATH=$PATH:$ORACLE_HOME
(2) Set TND_ADMIN to point to the previous directory of the file tnsames.ora, as follows:
export TNS_ADMIN=Oracleclient installation directory/network/admin
If PG client is used, after downloading and installing the client of the corresponding system, the environment variables need to be configured as follows:
(1) Set PG_CLIENT_HOME to point to the installation directory of PGClient; And add $PG_CLIENT_HOME to the LD_LIBRARY_PATH variable, as follows:
export PG_CLIENT_HOME=/PgClient installation directory
export LD_LIBRARY_PATH=$PG_CLIENT_HOME:$LD_LIBRARY_PATH