Configuration after the installation |
When starting SuperMap iServer, iServer uses 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 configurations include:
If you do not want to use the default configurations, you can modify the script file directly to use a custom configuration or do not use the script, and use the custom JRE and JDK by manually setting the environment variable. When using customized JRE and iObjects, when using 32-bit iServer, please use the 32-bit JRE / JDK and iObjects; when using 64-bit iServer, use 64-bit JRE / JDK and iObjects.
In addition to the above custom configuration, if you need to use Oracle datasource, you also need to configure the environment.
If you do not want to use the default configuration when iServer starts the service, that is, you do not want to use the default JRE and JDK in the environment configuration script, you can modify the script file directly to use a custom configuration, or by manually setting environment variables.
In addition to the above custom configuration, if you need to use Oracle datasource, you also need to configure the environment.
When you use a custom JRE by modifying the environment variable, you need to rename or delete the jre directory in the% SuperMap iServer_HOME% / support directory. otherwise, it will still use the built-in jre and iObjects java.
According to the software requirements of iServer, JRE requires 11.0.18+10. If you are installing JDK, you need to set JAVA_HOME to JDK directory; if you are installing JRE, set JRE_HOME to JRE directory.
To configure the JDK as an example, you can set environment variables in the following ways:
(1) in the system profile file (default path: / etc / profile), set JAVA_HOME as follows:
export the JAVA_HOME = / JDK directory
(2) Make above settings take effect:
source /etc/profile
(3) Implement the echo command to check whether it's a correct settings:
echo $JAVA_HOME
The JRE configuration is the same with JDK, only the environment variable name is changed to JRE_HOME.
When you use a custom iObjects by modifying the environment variable, you need to rename or delete the objectsjava directory in the % SuperMap iServer_HOME% / support directory. otherwise, it will still use the built-in iObjects java.
Please use the corresponding version of iObjects according to iServer's software requirements. If the version is inconsistent, you can not guarantee the availability of all services and functions of iServer.
The steps to set how to custom SuperMap iObjects Java and its font library are as follows:
(1) Set the environment variable named UGO_HOME in the system profile file (default path: / etc / profile) and add $ UGO_HOME / Bin to the LD_LIBRARY_PATH variable:
export UGO_HOME= /SuperMap iObjects Java 11i(2023) directory
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 font library fonts folder. For example, in SuperMap iObjects Java it contains default fonts, located in $ UGO_HOME / Support, then set SUPERMAP_ROOT as follows:
export SUPERMAP_ROOT=$UGO_HOME/Support
(3) Make above settings take effect:
source /etc/profile
(4) Implement the echo command to check whether it's a correct settings:
echo $LD_LIBRARY_PATH
The environment encoding script used by SuperMap iServer (% SuperMap iServer_HOME% / bin / setenv.sh) also sets the encoding mode of the system. If you have modified this environment setup script or configured not to use the script when starting service, then you need to manually set the system encoding.
(1) set RedHat system encoding:
export LANG=zh_CN.UTF-8
(2) set SUSE system encoding:
export LANG=zh_CN.UTF-8
unset LC_CTYPE
If you use the Oracle datasource, you need to configure the environment variables as follows:
(1) Set ORACLE_HOME, point it to the Oracle installation directory; 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
(2) If the Oracle database is encoded as GBK, set the NLS_LANG parameter to "simplified chinese" _china.zhs16gbk, as follows:
export NLS_LANG="simplified chinese"_china.zhs16gbk
bsp;
If you use the Oracle client, after downloading and intalling the client of the appropriate system, you need to configure the following environment variables:
（1）Set ORACLE_CLIENT_HOME, point it to the installation directory of the Oracle Client, then add $TNS_ADMIN into the LD_LIBRARY_PATH variable, as follows:
export ORACLE_CLIENT_HOME=/Oracleclient installation directory
export LD_LIBRARY_PATH=$ORACLE_CLIENT_HOME:$LD_LIBRARY_PATH
（2）Set TNS_ADMIN, point it to the next upper directory of the tnsames.ora file, as follows:
export TNS_ADMIN=Oracleclient installation directory/network/admin
If you use the pg client, after downloading and intalling the client of the appropriate system, you need to configure the following environment variables:
（1）Set PG_CLIENT_HOME, point it to the PGClient installation directory, then add $PG_CLIENT_HOME into LD_LIBRARY_PATH variable, as follows:
export PG_CLIENT_HOME=/PgClient installation directory
export LD_LIBRARY_PATH=$PG_CLIENT_HOME:$LD_LIBRARY_PATH