Tutorial

Environment Type Management

SuperMap iManager provides the environment type management.The administrator can add custom environment type/specification and import specifications (OpenStack platform). It can manage the existing environment type and specifications, such as editing environment types/specifications, deleting the new type/specification and importing environmental specifications. The environment type determines the GIS environment type, and the environment specification determines the CPU, memory and disk size of the GIS environment.

For any added environment type, the first is the input template type name, and the associated template name can be specified or not. If the specified associated template can be selected in the drop-down menu, it is the selection of operating system (including the Linux and Windows.)

Login as the administrator and access the URI address (http://localhost:8390/imanager/staticFiles/views/configuration/gisTemplatesManage.html) or click the “Environment Type” option to enter the environment type management page.

Add Environment Type

iManager built in GIS server, GIS portal, and load balancer. If you need to add a platform class, the method is as follows:

In environment type management page, click add environment type button to pop up the dialog box. Type in environment type name, choose associated template name, operating system type, and add all application to environment type in the template. Click OK to add the environment type. In general, environment types are added to specific industry application requirement, and new environment types can be viewed in the environment type list. When adding an application, please fill in the relevant information accurately. If incorrect, it will result in the failure to start and access to the common platform created by the environment.

• Environment type name (required): fill in the environment type name. When you add and apply to create a common platform, you will use the new environment type. Can’t add an environment with the same name as the built-in environment.
• The associated template name (required): Associate the template for environment type. The templates here are typically customized to meet specific industry application requirement and determine the generic platform type.
• Operating system type: the default is Linux system, and if the associated template is a Windows system, the selection is Windows.

• Application (required): please click the add button at the back of the application to add all the applications in the environment to the environment type. After the application is added, the application can be accessed by the GIS environment created by iManager through this environment type. After clicking the add button after the application, you need to fill in the application name, whether it is Web application, service protocol, service port, ContextPath, and other relevant information. This adds an application in the template to the environment type, and if there are more than one application in the template, you need to add the operation multiple times.

  

• Application name (required): fill in the application name.
• Whether it is Web application: if the application is a Web application, the choice is Yes; If it is the desktop applications, the choice is No.
• Service access protocol (required): the service access protocol that should be followed when the GIS environment is created through the environment type. Ensure that the application is consistent with the access protocol that is actually followed; otherwise, it can not access the protocol.
• Service access port (required): the service access port that should be followed when the GIS environment is created through the environment type. Make sure that it is consistent with the actual port.
• ContextPath (required): the root address that should be followed when the GIS environment is created through the environment type. Make sure that it is consistent with the actual root address.

After completing the above information, click the add button to complete the application. The application name will be displayed in front of the Add button. Here adding environment type points to add a new environment to iManager type. If the environment type already exists, it will remind you “environment type * * * has been existed”, and the operation you did is invalid.

Manage Environment Type

View Environment Type

In “Environment Type List” of environment type management page, you can either view the built-in environment type, such as “GIS server”, “GIS portal” and “Load Balancer”, you can also view the new types of environment. You can also move the mouse to the icon of environment type name to view the service access address formats of the GIS environment created by using this environment type. The built-in environment type only supports to edit, and new environment types support to edit and delete.

Manage Environment Type

In the environment management page, you can click the “Delete” button to remove the environment type. Also you can click “Edit” button after the environment type, to modify the template configuration, such as the service protocol, service port, and contextPath. For “GIS server”, “GIS portal”, GIS desktop, and “Load Balancer”, you can only edit them because they are built-in environment types. Click the “Edit” button corresponding to each environment type, and the “Edit environment type” dialog box will pop up. You can make template associations or modify templates as needed.

• Environment type name (unmodifiable): the name of this environment type is default value and can not be modified.
• Associate template name(required): Associate template to the environment type, and the correlation template is to correlate the corresponding GIS mirror image to the environment type. GIS Server environment type needs to associate the iServer mirror. GIS Portal environment type needs to associate to the iPortal mirror. GIS Desktop environment type needs to associate to the iDesktop mirror. Load Balancer environment type needs to associate to the Nginx mirror.
• Operating system type (unmodifiable): the built-in template, whose operating system is Linux by default and unmodifiable.
• Application: refers to the application contained in this template, which shows the application name. GIS Server environment type contains the iServer mirror. GIS Portal environment type contains the iPortal mirror. GIS Desktop environment type contains the iDesktop mirror. Load Balancer environment type contains the Nginx mirror. Click the application, and it will display the configuration information for the application. You can modify it as needed:
• Application name (required): the application name with default values. You can also modify as your needs.
• Whether it is a Web application(required): if the application is a Web application, the choice is Yes; If it is the desktop application, the choice is No. The desktop application does not have the following items: “service access protocol”, “service access port”, and “ContextPath”.
• Service protocol (required): the service access protocol of GIS environment when the GIS environment is created through the environment type. It has the default value. The default service access protocol of GIS server environment and GIS portal environment is http. If the application’s service access protocol is changed, it needs to be modified.
• Service port (required): the service access port of GIS environment after the GIS environment is created through the environment type. The default port of GIS server environment and GIS port environment is 8090. If the application’s service access port is changed, it needs to be modified.
• ContextPath (required): the GIS environment access root address after the after the GIS environment is created through the environment type. The default value of GIS server environment is /iserver, GIS portal environment default value is /iportal. If the application ContextPath is changed, it needs to be modified.

When creating GIS server and GIS cluster environment, the “GIS server” environment type is used by default. When creating a GIS portal environment, the “GIS portal” environment type is used by default; When creating a GIS desktop environment, the “GIS desktop” environment type is used by default; When creating a load balancer, the default environment type is “load balancer”; When creating a common platform environment, the new environment type is used.

Notes:
The associated environment is to create the GIS environment. If a GIS environment does not have an environment type association, the task cannot be executed. For example, when there is no corresponding environment type for the GIS portal, the creation will be a failure if creating a GIS portal. And you are reminded that “error: Adding portal failure: the template is not associated”.

Add Environment Specification

iManager built-in small, medium, and large three environment specifications. If you want to add other specifications, in the environment management page, click “Add Environment Specifications” button, and you can customize your own CPU, memory and disk size, then click the “Confirm” button. You can view the new environment specifications in the list of environment specifications. If your virtual platform is OpenStack, you will see a template name. You can directly link to an existing cloud hosting type. vCPU, memory and disk will automatically set the same depending on the type of your associated cloud hosting.

Manage Environment Specification

In “Environment Specification List” of environment type management page, you can view the built-in three environment types (large, medium, small ), and you can also view the new specifications of environment. “Large”, “Medium” and “Small” three built-in environmental specifications only support to edit operations. New environmental specifications not only support to edit, but also to delete.

Click the “edit” button after the environment specification name, and you can modify the basic configuration of the environment specification, such as CPU, memory, and disk size. If you do not change it, it will keep the default style. For the newly added environmental specification, click the “Delete” button. When creating a GIS environment, you need to select the environment specification. After selecting, the system will create the GIS environment according to the selected size. If your virtual platform is OpenStack, you will see a template name. You can directly link to an existing cloud hosting type. vCPU, memory and disk will automatically set the same depending on the type of your associated cloud hosting. If you have already been associated, you can modify the associated template name. If you want to customize your specifications, you can select unconnected and enter the specifications you want.