Personal Center |
Log in to SuperMap iPortal, click on the nickname in the upper right corner to enter the Personal Center, you can manage your account, portal resources, set your preferred theme, view and process received messages, view and manage your applications and authorizations, manage App development keys.
Display user name, nickname, email, user type, department, and other information.
Click "Edit My Profile" > "Basic Settings", you can change your avatar, nickname, email; click "Modify Password", enter your old password, new password, cofirm password, you can change your login password.
Note:
Under the "My Profile" tab, click the "My Resources" icon to enter "Resource Center" > "My Resources" to manage all the resources you have added to the portal, or you can directly enter from "Home" > "Resource Center" My Resources to enter.
If the portal administrator has enabled Organizational Structure, the "My Department" page will appear in the Personal Center. The "My Department" page displays basic information about your department, members, and resources. You can share resources to the department you are in, and remove resources shared by yourself in the department. If you are a department administrator, you can remove all the resources in your department.
The "My Department" page displays your department name, the parent department name, and the creation time. If you are a department administrator, you will see all departments that you manage (child departments not included).
On the "My Department" page, click on your department name to enter the department details page, which will display a list of members of your department, including department administrators and department members. You can search for department members by entering the key characters of the member's nickname through the search button. You can also browse and view all resource information that has been shared in this department, including: maps, services, scenes, data, apps, insights, dashboards, notebooks, GPA models, design 3D, etc.
In maps, services, scenes, data, apps, insights, dashboards, notebooks, GPA models, or design 3D resource lists. To remove a resource shared in your department, hover and click the appeared "Remove" button on the target resource. Note: the resource will not be deleted from iPortal, the remove action only changes the sharing permission of the resource. For department administrators, you can remove all resources shared with the department.
By default, the system provides light-mode themes and dark-mode themes for you to use. Light-mode themes include a blue theme and an orange theme; dark-mode themes include a dark orange theme and a dark red theme. If you set a theme, it will take effect only after you log in to the system. The administrator can set the system default theme, download themes, import and use custom themes developed based on existing themes. For details, see: Theme Management.
The system will send you notifications if your operations in iPortal involve resource review or authorization. These function modules that support message notification include: map review (Administrators can enable this function. If enabled, the maps added by ordinary users need to be approved by the administrator before they can be shared and viewed by other users), service review (Administrators can enable this function. If enabled, the services added by ordinary users need to be approved by the administrator before they can be viewed and used by other users), scene review (Administrators can enable this function. If enabled, the scene added by ordinary users need to be approved by the administrator before they can be viewed and used by other users), data review (Administrators can enable this function. If enabled, the data added by ordinary users need to be approved by the administrator before they can be viewed and used by other users), insight review (Administrators can enable this function. If enabled, the insight added by ordinary users need to be approved by the administrator before they can be viewed and used by other users), dashboard review (Administrators can enable this function. If enabled, the dashboard added by ordinary users need to be approved by the administrator before they can be viewed and used by other users), project review (Administrators can enable this function. If enabled, the project added by ordinary users need to be approved by the administrator before they can be viewed and used by other users), resource application and authorization, application approval for key quota, and group invitation or join approval. The group-related messages will prompt you to enter the corresponding module of the group for processing.
"My Applications" records all your application records (including applying view permission for searchable resources and applications for key quota), which is convenient for you to view application details and track application authorization or approval results.
"My Authorization" records all the application items waiting for your approval and completed by you (including view permission applications for searchable resources), which is convenient for you to approve and manage. If you reject a request for viewing resources, the rejected user can still reapply from the "My Applications" page.
When developing a Web GIS application, you can directly access the public service and data resources in the portal, but for the non-public services and data in the portal (including my private resources, shared with me, resources in my department, and my groups), you need to generate a Resource key in iPortal, and then use the resource address plus the key in your application to access these resources.
Resource Key is the password identification of resources. It is an access control mechanism to protect the security of data and service resources registered and managed by users in iPortal. Resource Key consists of 24 random letters and numbers and supports controlling access source, validity period, access content and access quota, etc. By default, iPortal provides 10,000 visits per day for each associated resource of the key (administrators can modify the default quota in the configuration file). In addition, iPortal also provides a quota review function. If the administrator has not enabled the quota review, users can set the quota by themselves; if the quota review function is enabled, the quotas set by users need to be approved by the administrator to take effect. When reviewing the quotas, the administrator needs to pay attention to the impact of the increased quotas on the operational stability and response speed of the entire portal software platform.
The following will introduce the generation, use, and management of Resource keys in iPortal.
When generating the key, you need to set the name (it is recommended to be consistent with your actual project name or application scenario for easy management), request verification mode, key tags, expiration time, and association resources. There are two ways to request verification: "Site Access" and "Service Request." The details are as follows:
Site Access: If you choose "Site Access," you need to fill in the application URL you developed (for example: http://www.supermapol.com). When iPortal receives a service access request, it will verify the legality of the visit from the requested referer to ensure the security of service resources in the portal. This method is suitable for the production environment that only needs to determine the domain name. Subsequent changes and upgrades of your application server's IP will not affect access to the service.
Service Request: If you choose "service request," you need to fill in the IP address that is allowed to access the service resource. When iPortal receives a service access request, it will verify the IP corresponding to the source domain name to ensure the security of the service resources in the portal. The disadvantage of this mode is that if the IP address changes, you need to modify the IP parameter value of the key, but the string of the key itself will not change. It should be noted that if the IP is set to 0.0.0.0, it means that any machine is allowed to use the key to access service resources. Please use it with caution. It is recommended to use it only in the test environment.
Fill in the name of the key. To be more manageable, it is recommended you use the naming rule as [Project Name-Application Scenario];
Select the request verification mode: site access or service request.
If you choose "Site Access," you need to set the referer parameter at the same time, that is, fill in your site address, such as: http://www.supermapol.com;
If you choose "service request," you need to set the access IP parameters, that is, the server IP address of your site, such as: 192.168.1.1. It also supports setting multiple network segments (separated by commas), such as: 192.168.1.1/24,192.168.1.1,192.168 .1.0-192.168.1.255.
Set the key tags. You can use the recommended tag or custom tag. Multiple tags should be separated by a comma, support up to 6 labels;
Select the expiration time, optional. When you set it to empty, the expiration time will not be limited;
Select the associated resources of the key, that is, the data and service resources that need to be accessed through the key in your Web GIS application. You can select one or more data and services, which support filtering by type or by name. Among them, "My Services/Data" lists all the private services/data resources you own in the portal, and "Shared Services/Data" lists all the services/data resources in the portal that you have permission to access, including Services/data shared with me, services/data in my department or group;
Click "OK" to complete the addition of the key.
The "My Keys" page will list all your keys. You can search for keys by tag filtering and keyword retrieval, view the basic information of keys and delete keys in batches.
For the single key, you can click the to modify the information, click the to view the access statistics, click the to view the information of the key associated resource, click "View Details" to view the key quota, and click the to set the key quota as needed.
By default, iPortal provides 10000 visits per day for each associated resource in the key. If the visit amount reaches the quota limit, you cannot continue to use the key to access the resource in your web application.
In each key, click "View Details," and the pop-up window will display the quota information of each associated resource, including the maximum quota and the remaining quota. You can monitor the usage of the quota here. If the current quota cannot meet your business needs, you can click the to reset the quota. If the administrator has enabled the quota review function, the quota application items will be synchronously recorded in My Application, and the administrator's approval result will be notified to you in the form of a message, which can be viewed in My Messages. Your application needs to be approved by the administrator before it becomes effective. The administrator needs to pay attention to the impact of the increased quotas on the operational stability and response speed of the entire portal software platform.
iPortal provides access statistics for a single key. You can click the to view it in the pop-up window. The pop-up window will display the change curve of the number of accesses within a period, and support switching the statistical unit (hour/day/month) and statistical period, helping you grasp the usage of keys in different time dimensions.
After adding the key, you can click the to view all the services and data resources associated with the key, search for resources by keyword retrieval, copy the resource address with one click, and quickly use the key in development applications.
Among them, iPortal provides multiple data addresses for you to choose to meet different data access requirements. You can click the to view the data addresses and related descriptions supported by the key in the pop-up window of "View Related Resource".
Table 1 Data addresses supported by Resource key
Data Address | Description |
http://{ip}:{port}/iportal/web/datas/{id}.json |
Get detailed information about the data, including permission information. |
http://{ip}:{port}/iportal/web/datas/{id}/content.json |
Get the content of the specified data (currently only supports json, csv, shp). |
http://{ip}:{port}/iportal/web/datas/{id}/download.json |
Download data. |
http://{ip}:{port}/iportal/web/datas/{id}/datasets.json |
Get the data set information contained in the data Data types that can be parsed: (1) When storing in DATASTORE and opening the relationship, it supports the analysis of data sets of relational data (udb/csv/excel/geojson/workspace). (2) The data set is contained in the registered hdfs data source. |
http://{ip}:{port}/iportal/web/datas/{id}/datasets/{dataSetName}.json |
Get detailed information on a specified data set. |
http://{ip}:{port}/iportal/web/mycontent/datas/{id}.json | Get detailed information about the data, including permission information. |
http://{ip}:{port}/iportal/web/mycontent/datas/{id}/download.json |
Download data. |
http://{ip}:{port}/iportal/web/mycontent/datas/{id}/simpledata.json | Get simpleData in HDFS. |
http://{ip}:{port}/iportal/web/mycontent/datas/{id}/services.json |
Get service information associated with data. |
http://{ip}:{port}/iportal/web/mycontent/datas/{id}/digest.json |
Get summary information on data storage. |
http://{ip}:{port}/iportal/web/mycontent/datas/{id}/sharesetting.json |
Get shared information of data. |
After the resource key is generated, when your application needs to access data and service resources, you only need to add the key after the resource address. For example, the following access request:
http://192.168.120.40:8195/iserver/services/map-HunanPopulationDensity/rest.rjson?key=v6ywlc7MJiAY6CQ0Ej4RXWD0
Among them, the part before "?" is the address of the service that needs to be called, and the part after it (key=......) is the key request parameter required for access, and the request can be accessed by sending the request with this URL.
For service resources, if your application is developed based on SuperMap iClient, you do not need to add "key=......" after each service request. You can directly use the registerKey method of the SuperMap.SecurityManager class provided by the class library, binding the corresponding key to the service address, and the set service address variable can be used normally in other places.