Portal site configuration

Database configuration

The portal data are stored in the SQLite database by default, no need to install and configure. But before use, you need to choose the database language version. iPortal provides two language-version database file, iportal.db and iportal_en.db, you can switch the database version by modifying iportal.xml file under [SuperMap iPortal installation directory] \webapps\iportal\WEB-INF directory.

For large-volumn data and high concurrent access in production environment, we recommend you to use MySQL/Oracle/PostgreSQL to store the portal data, therefore you need to Configure database before you start iPortal. If you perform operations such as switching databases, etc., you should handle the information synchronization of the database by yourself.

Portal Customization

iPortal provides home page customization for you to customize the home page according to your business requirements; personal center customization to control the display and hiding of the navigation bar; App configuration to set the usage right of built-in WebApps. In addition, application developers can also implement in-depth customization according to needs, such as: front-end page customization development, new resource customization development. For usage, see: customizing iPortal.

Configuration before importing portal data

Before importing portal data, for example, administrator creates new users, or users contribute resources to portal, like create a map, register a GIS service, we recommend you to configure the following items. Of course, you can configure them later or in future according to your needs.

Proxy configuration for registered services: For unified control of service access, we provide service proxy function. You can enable or disable this function according to demands. When starting service proxy, the original registered service address is only visible for the service registrar and administrators, others only can view and visit the proxied service address.

User registration configuration: If your portal intends to use enterprise accounts (For using user's account data, refer to: Integrating user-owned account systems) or you want to create all the accounts as administrator, then you can disable this function.

Audit configuration for registered users: User audit function is disabled by default, that is, all users can directly become a portal user by click the "Sign up" button and finish the registration process without the audit operation by administrator. If you open the audit function, all the registered users need to wait administrator's audit before they can log in to the poral. If you open this function, we recommend you to open mail notification too for notifying the users the audit result.

Service audit configuration: If you need to determine which services can be registered into portal, you need to open service audit function, then you can manage all the incoming applications about the registration. And you also can determine which fields of service after modification need to be audited.

Map audit configuration: Used to determine which maps created by normal users can be added into portal or which map property fields need to be audited after modification.

Resource sharing scope configuration: Used to set sharing scope for resources such as maps, services, scenes. You can control whether the users can share the resources to departments, groups, or users.

Upload data capacity configuration: You can configure a unified maximum capacity for all users' upload data, and you can also configure specified capacity for specific individuals.

Mail notification configuration: We provide mail notification feature for registered users to receive the audit results timely. So if you enable the registered user audit function, it is recommended that you configure user registration supporting to fill in email, open mail notification function, and configure the mail server. After finished these configurations, the registered users will be prompted to wait for the administrator's audit. The audit results will be notified by mail. And only the user who is approved by the administrator can log in to portal.

Custom directory configuration: If your portal needs to display the resources such as maps, services or scenes, by year, area, business type, you can customize the directory to meet the actual business demands.

Organizational structure configuration: For portal applications involving multi-level units or departments, we recommend you configure the organizational structure to easily manage the users and resources by departments.

Hosted service configuration: If your portal needs to publish services, you need to configure one or more hosting servers.

Monitor server configuration: If you need to monitor the GIS servers inside your portal, for example, monitor the hardware status, including cpu usage, total memory or memory usage, then you need to configure this function.

Default thumbnail configuration: You can configure default thumbnails for your portal resources, like services, scene, data, app, etc.

DataViz configuration

As portal's administrator, you can configure the contents of DataViz to allow portal users to visualize their featured data on maps.

Default basemap configuration: You can add, delete or sort the default basemaps for users' use.

Layer settings: Control the layer sources and the display order on the DataViz app.

Add controls: Including: OverviewMap, Copyright, DisplayCoords, POI, etc.

Map settings: Set a unified central point and level for map.

Set logo for DataViz.

Storage directory: Set the default directory name for storing uploaded data and markers in "My Data".

Service settings: Configure Address Matching Service offered by SuperMap iServer to apply in DataViz app.

Other functions onfiguration

In addition to the above configurations, SuperMap iPortal also provides other function configurations, for example, whether to display users list when sharing resources, configure the update time interval for registered services.