Database configuration |
The portal data(basic information such as maps, services, scenes, data, projects, insights, dashboards, Notebooks, accounts), security information(users, roles, etc.), and monitoring information in SuperMap iPortal are stored separately in SQLite databases by default. SQLite is a lightweight embedded database that provides database-level locking without installation and management configuration. While the SQLite database is suitable for testing and trial environments. In a production environment, it's recommended to use other relational databases to ensure performance and security instead.
Currently, MySQL/Oracle/PostgreSQL databases are supported to store the portal data and secure information. While only the MySQL database is supported to store the monitoring information. Otherwise, iPortal provides a portal database migration tool to migrate portal data between different types of databases.
If you didn't configure the database, iPortal uses SQLite database to store the information. The portal information is stored in the iportal.db under the [SuperMap iPortal installation directory]\webapps\iportal\WEB-INF\iportaldata directory; the monitoring information is stored in the monitor.db under the [SuperMap iPortal installation directory]\webapps\iportal\WEB-INF\iportaldata directory; the security information is stored in the [SuperMap iPortal installation directory]\webapps\iportal\WEB-INF\iserver-security.db.
Also, iPortal provides an English version SQLite database "iportal_en.db" for the portal data for you to switch to use the English version samples. To use the English version database, modify the database name "iportal.db" to "iportal_en.db" in the iportal.xml configuration file. Note, the data stored in both databases are independent of each other, i.e., the data added to an English version will not be added to the Chinese version database.