{"componentChunkName":"component---src-templates-guides-js","path":"/en/guides/InstalliManager/","result":{"data":{"markdownRemark":{"html":"

Install iManager

\n

This guide is used for deploying iManager on Kubernetes. There are two ways when you installing iManager, they are using Linux command and Helm command, choose either one is good.

\n

All the packages introduced below can be downloaded from the link:

\n

https://pan.baidu.com/s/1lWLyyT1jAbADGuxEG3m4gA

\n

Password: ge4d

\n

Requirement

\n
    \n
  1. \n

    The Kubernetes environment v1.9 or higher. Please make sure the time of node machines are the same as master machine(The time difference should be less than 30 seconds)

    \n

    If you do not have Kubernetes environment, please refer to Deployment Guide > Install Kubernetes > CentOS(Ubuntu) to install.

    \n
    2. \n
  2. \n

    Resources requirement:

    \n\n
    3. \n
  3. \n

    The supermap-imanager-for-kubernetes-10.1.4-linux-x64.tar.gz package

    \n

    Path: iManager部署包/iManager 10.1.4/iManager for Kubernetes部署包/supermap-imanager-for-kubernetes-10.1.4-linux-x64.tar.gz

    \n
    4. \n
  4. \n

    The NFS Server installation package(Download the version of the NFS Server package according to your system. If you already have NFS Server, skip this step)

    \n

    Path(CentOS): iManager部署包/软件工具包/NFS Server离线安装包/nfs-server-offline-centos-7.5.zip

    \n

    Path(Ubuntu): iManager部署包/软件工具包/NFS Server离线安装包/nfs-server-offline-ubuntu-18.04.zip

    \n
    5. \n
  5. \n

    Images preparation(If you use Alibaba Cloud registry, skip this step)

    \n

    Path：iManager部署包/iManager 10.1.4/iManager for Kubernetes部署包/supermap-imanager-for-kubernetes-registry-all-10.1.4.tar.gz

    \n
    6. \n
  6. If you choose Helm command to install iManager, you need to install helm package
    7. \n
\n

Install NFS Server

\n

The example below is installing on CentOS, it is almost the same as install on Ubuntu. If you have NFS Server, skip this step.

\n\n

The path of the NFS storage directory is: /opt/nfs_data

\n

Execute the command to verify if the NFS has installed:

\n
mkdir test\nmount -t nfs <ip>:/opt/nfs_data test
\n
\n

Notes:
\n<ip> is the machine IP where you installed the NFS on.

\n
\n

Install iManager Image Repository

\n

If you install iManager on the extranet, skip this step and set Alibaba cloud registry.

\n

Before installing the image registry, execute the command sudo docker version to make sure you have installed Docker.

\n
\n

Notes:

\n

It is better to use a new and clean machine to install the image registry.

\n
\n
    \n
  1. \n

    Put the image package in any directory and unzip(If the name of your package is not the same as below, replace the package name in the command to your package name):

    \n
    tar -zxf supermap-imanager-for-kubernetes-registry-all.10.1.4-linux-x64.tar.gz
    \n
    2. \n
  2. \n

    Enter the directory that you unzipped:

    \n
    cd supermap-imanager-docker-images
    \n
    3. \n
  3. \n

    Install image registry:

    \n
    sudo chmod +x startup.sh && sudo ./startup.sh
    \n
    4. \n
  4. \n

    Verify. Execute the following command, if no error prompts, you have successful installed image registry. Replace the IP below by the actual IP of your machine.

    \n
    sudo docker pull IP:5000/supermap/tiny-tools:3.12
    \n
    \n

    Notes:
    \nIf you install registry on ARM, change the image tag ‘3.12’ to ‘1.0-arm’.

    \n
    \n
    5. \n
\n

Install iManager

\n

You need to open the port of “deployimanagerport”(the port is 31100 by default) in the values.yaml file, and open the port 6443, 9100, and 2049(open 2049 when using NFS for data storage). If you use Alibaba Cloud ECS Server, add the ports to safety group rules. What is more, please make sure the port 3307 and 9183 is available.

\n

Execute all the commands by administrator permission:

\n
    \n
  1. \n

    Put the supermap-imanager-for-kubernetes-10.1.4-linux-x64.tar.gz package in any directory of Kubernetes master machine, and unzip(If the name of your package is not the same as below, replace the package name in the command to your package name):

    \n
    tar -zxf  supermap-imanager-for-kubernetes-10.1.4-linux-x64.tar.gz
    \n
    2. \n
  2. \n

    Enter the directory that you unzipped:

    \n
    cd supermap-imanager-for-kubernetes
    \n
    3. \n
  3. \n

    Execute the command to set iManager configurations:

    \n
    sudo  vi values.yaml
    \n
    4. \n
  4. \n

    Modify the parameters:

    \n
    \n

    Notes:

    \n
      \n
    1. The following configurations could only be set before starting, if you need any change, please execute ./startup.sh after modifying. The Helm command to update the configuration, please execute ‘helm upgrade imanager ../supermap-imanager-for-kubernetes -n supermap’.
      2. \n
    2. The configurations have default values, do not delete any configuration when modifying.
      3. \n
    3. The “Required” variables need to be modified by your actual environment. The “Optional” variables can keep in default, please do not delete the default values.
      4. \n
    \n
    \n
     # Required. The iManager image registry address. The default address is Alibaba cloud registry: registry.cn-beijing.aliyuncs.com. If you install iManager on the extranet, we recommended to keep in default.\n # If you install iManager on the intranet, please refer to Install iManager Image Registry above to install the registry, and fill the blank by the format <IP>:5000, <IP> is the machine IP on which you installed the registry, for example, 192.168.17.133:5000.\n deploy_registry: registry.cn-beijing.aliyuncs.com\n\n # Required. The external IP which is used for visiting Kubernetes. The IP cloud be any one of the Kubernetes node machines. For example, 192.168.17.110.\n deploy_kubernetes_public_ip:\n\n # Required. The administrator account name, used for logging iManager, the account name is admin by default, modify the account name by your requirement.\n deploy_imanager_user_name: admin\n\n # Required. The administrator account password, used for logging iManager, the account password is admin by default, modify the account password by your requirement.\n deploy_imanager_password: admin\n\n # Required(Optional if you have configured deploy_storage_class_name). Your NFS Server address, NFS Server is using for iManager data storage, the address could be IP or domain name, for example, 192.168.17.150. Please refer to Install NFS Server above to install NFS Server.\n # If you are going to use NFS Server for data storage, it is necessary to install NFS Client on the node machines of Kubernetes.\n deploy_nfs_server:\n\n # Required. The mount path of NFS Server, the default mount path is /. Fills in the actual mount path of your NFS Server. If you installed NFS Server by the package we provided, fills in the mount path as: /opt/nfs_data.\n deploy_nfs_path: /\n\n # Optional. The URL of Kubernetes master node, the value is https://kubernetes.default.svc by default, keep in default if your environment is private cloud.\n # It is required to configure if your environment is public cloud, execute the command 'kubectl cluster-info' to get the URL, for example, https://192.168.17.110:6443.\n deploy_kubernetes_master_url: https://kubernetes.default.svc\n\n # Optional. The Kubernetes node IP which is mapped by GIS Cloud Suite domain name(the IP that configured in DNS Server), required to configure if your GIS Cloud Suite has a domain name. The value is using the first Kubernetes node IP by default.\n deploy_domain_ip:\n\n # Optional. The name of your StorageClass, used for storing the data of iManager. StorageClass and NFS Server(deploy_nfs_server) are used for storing iManager data, if you configured both of them, the data will be stored in NFS Server.\n deploy_storage_class_name:\n\n # Optional. The Kubernetes namespace, the value is supermap by default, you can define a name by your requirement.\n # It is required to create a namespace by the command when using Helm Command to install iManager.\n deploy_namespace: supermap\n\n # Optional. The image pull policy, choose one of these:[Always|Never|IfNotPresent], the value is IfNotPresent by default.\n # Always: Pull the latest images from registry.\n # Never: Use local images and nerver pull the images from registry.\n # IfNotPresent: Use local images first. If local images are unavailable, pull the images from registry.\n deploy_image_pull_policy: IfNotPresent\n\n # Optional. The image pull secret, used for identity authentication when pulling private images. You need to create a resource with the same name as the Secret in the namespace of Kubernetes. Please refer Tutorial > Appendix > FAQ Question 6 to see how to create the resource.\n deploy_image_pull_secret:\n\n # Optional. The name of namespace which stores images in registry, the default name is 'supermap', you can define the name by the requirement.\n deploy_image_namespace: supermap\n\n # Optional. The service type of iManager, fills in [NodePort|LoadBalancer], generally keep in default. \n # If your environment is public cloud, the value here is: LoadBalancer.\n deploy_service_type: NodePort\n\n # Optional. The service protocol of iManager, fills in [http|https], the value is http by default.\n deploy_imanager_service_protocol: http\n\n # Optional. Disable the log function of iManager or not, fills in [true|false], the value is false by default.\n # true: Disable the log function of iManager.\n # false: Do not disable the log function of iManager.\n deploy_disable_log: false\n\n # Optional. Disable the alarm fuction of iManager or not, fills in [true|false], the default is false.\n # true: Disable the alarm function of iManager.\n # false: Do not disable the alarm function of iManager.\n deploy_disable_alert: false\n\n # Optional. The number of CPUs of a service in iManager, the number is 2 by default.\n deploy_cpu_limit: 2\n\n # Optional. The memory of a service in iManager, the memory should be larger than or equal to 4Gi, the memory is 4Gi by default.\n deploy_memory_limit: 4Gi\n\n # Optional. The image tag of iServer in iManager.\n deploy_iserver_tag: 10.1.4\n\n # Optional. The image tag of iPortal in iManager.\n deploy_iportal_tag: 10.1.4\n\n # Optional. The image tag of iDesktop in iManager.\n deploy_idesktop_tag: 10.1.2\n\n # Optional. The image tag of iserver_gisapplication in iManager.\n deploy_gis_app_tag: 10.1.4\n\n # Optional. The others image tag in iManager.\n deploy_image_tag: 10.1.4\n\n # Optional. The port of iManager, select the range between 30000-32767, except 31234, the default is 31100. If you define a port, make sure the port is different to others port setting.\n deploy_imanager_port: 31100\n\n # Optional. Whether the license center is going to disable local storage, fills in [true|false], the value is false by default. When the value is true, you must configure either deploy_nfs_server or default_storage_class_name.\n # true: License center do not use local storage.\n # false: License center use local storage.\n deploy_disable_bslicense_local_volume: false\n\n # Optional. HBase capability optimization, fills in [true|false]. If you would not use HBase environment, keep in default. If you want to optimize built-in HBase, set the value to true, and refer Question 9 in Tutorial > Appendix > FAQ to create PV.\n deploy_disable_hbase_nfs_volume: false\n\n # Optional. The WeChat Work application's Token, required to configure when using Wechat alarm. Please refer to SuperMap iManager Documentation to configure the Wechat Work alarm.\n deploy_weixin_token:\n\n # Optional. The WeChat Work Company ID, required to configure when using Wechat alarm.\n deploy_weixin_corp_id:\n\n # Optional. The WeChat Work application's EncodingAESKey, required to configure when using Wechat alarm.\n deploy_weixin_encoding_aes_key:\n\n # Optional. The WeChat Work Department ID, required to configure when using Wechat alarm.\n deploy_weixin_to_party:\n\n # Optional. The WeChat Work application's AgentId, required to configure when using Wechat alarm.\n deploy_weixin_agent_id:\n\n # Optional. The WeChat Work application's Secret, required to configure when using Wechat alarm.\n deploy_weixin_api_secret:\n\n # Optional. The webhook of Dingtalk, required to configure when using Dingtalk alarm. Please refer to SuperMap iManager Documentation to configure the Dingtalk alarm.\n deploy_dingtalk_webhook:\n\n # Optional. The secret of Dingtalkk, required to configure when using Dingtalk alarm.\n deploy_dingtalk_secret:\n\n # Optional. The time zone of the system. Fill in the relative path in the directory /usr/share/zoneinfo/, such as Asia/Shanghai and America/New_York.\n deploy_timezone: Asia/Shanghai\n\n # Optional. Disable metrics server or not, metrics server is used for monitoring the resources of Kubernetes, fills in [true|false]. The value is false by default.\n # true: Disable the metrics server.\n # false: Do not disable metrics server.\n deploy_disable_metrics_server: false\n\n # Optional. Enable Service Mesh(Istio) or not, fills in [true|false], the value is true by default. The Service Mesh is unavailable in ARM environment, the variable does not exist.\n # true: Enable Service Mesh.\n # false: Disable Service Mesh.\n deploy_istio_enabled: true\n\n # Optional. Enable ingressageteway and egressgateway in Service Mesh(Istio) or not, fills in [true|false], the value is true by default. Takes effect only if deploy_istio_enabled is true.\n # true: Enable ingressageteway and egressgateway.\n # false: Disable ingressageteway and egressgateway.\n deploy_istio_enable_ingress_egress: true\n\n # Optional. Enable kiali and tracing in Service Mesh(Istio) or not, fills in [true|false], the value is true by default. Takes effect only if deploy_istio_enabled is true.\n # true: Enable kiali and tracing.\n # false: Disable kiali and tracing.\n deploy_istio_enable_kiali_tracing: true\n\n # Optional. The service type of ingressgateway in Service Mesh(Istio), fills in [NodePort|LoadBalancer], generally keep in default. Takes effect only if both deploy_istio_enabled and deploy_istio_enable_ingress_egress are true.\n # If your environment is public cloud, the value here is: LoadBalancer.\n deploy_istio_ingress_service_nodetype: NodePort
    \n
    5. \n
  5. Save and quit the file.
    6. \n
  6. \n

    Install iManager(Executing the following command in supermap-imanager-for-kubernetes directory):

    \n

    There are two ways to install iManager, Linux command and Helm command, choose either of them.

    \n

    Using Linux Command

    \n
    sudo chmod +x startup.sh && ./startup.sh
    \n

    Using Helm Command

    \n

    6.1 Create a namespace which is named ‘supermap’(you can define the name of namespace, do not forget to change ‘supermap’ in next two steps to your defined name)

    \n
    kubectl create ns supermap
    \n

    6.2 Install iManager

    \n
    helm install imanager ../supermap-imanager-for-kubernetes -n supermap
    \n

    6.3 Check if iManager is installed successfully

    \n
    helm list -n supermap
    \n
    7. \n
\n

\n \n \n \n \n \n \n \n \n \n

\n
\n

Visit iManager UI by the address http://<ip>:31100 .Replace <ip> by the Master node IP of Kubernetes. If the value of deploy_imanager_service_protocol is https, the access address should be https://<ip>:31100.

\n
\n

The login account please refer to the administrator account information in values.yaml

\n

Activate License

\n

Click on Update on the License Center page, and follow the Operation Steps to activate the license (If you do not have the license, please apply the trial license on SuperMap official website).

\n

\n \n \n \n \n \n \n \n \n \n

\n

Check the License Status after activating the license.

\n

\n \n \n \n \n \n \n \n \n \n

\n

Appendix

\n

1.Delete iManager

\n

If you want to delete iManager environment, execute:

\n
chmod +x shutdown.sh && ./shutdown.sh
\n

If you want to completely delete iManager environment, execute:

\n
chmod +x shutdown.sh && ./shutdown.sh -v
\n

Using Helm command to delete iManager(the namespace and related environments will not be deleted):

\n
helm uninstall imanager -n supermap
\n

2.Short Message Alarm Service

\n

iManager provides Short Message Alarm Service, please refer to Tutorial > ALARM SERVICE > Short Message Alarm for more details.

","frontmatter":{"title":"Guides","next":null,"prev":null},"fields":{"path":"content/guides/InstalliManager.en.md","slug":"/en/guides/InstalliManager/","langKey":"en"}}},"pageContext":{"slug":"/en/guides/InstalliManager/"}}}