Appboard/old/configuration database

Upon initial installation, AppBoard/enPortal uses a pre-configured H2 database to store basic system information. This database is used to store a variety of system configuration details unique to your system, such as the following:

• enPortal users
• enPortal channel configuration
• enPortal Single Sign-on tokens
• AppBoard configuration Stacks, Widgets, filter rules, etc. (*)

* Prior to version 2.3, the AppBoard details were stored in an XML file. In versions 2.3 and later, they are stored in the database.

The instructions below are for establishing a connection between the AppBoard/enPortal server and a database. For instructions regarding the internal configuration of the database itself, please see Configuring Databases.

The database referenced in this document is used only for storing enPortal and AppBoard configuration. It is independent of any application databases that may house raw data that is being used in AppBoard Data Sources and visualizations.

You can optionally configure your own database to store this information, rather than the default H2 database. Once you do this, the database schema will be loaded into the specified database automatically when enPortal/AppBoard is started, and does not need to be pre-configured.

To configure your own database, perform the following steps:

1. Run the "portal dbsetup" command in ${INSTALL_HOME}/bin directory. When you run this command, there is a GUI that assists with selecting the database type and configuring the database connection. This tool saves changes to the file: /server/webapps/enportal/WEB-INF/config/persist.properties, with the specific configuration details that you provide for you database connection. If your server does not have a graphical display, you can modify this file directly in lieu of running the dbsetup command.
2. Configure a database connection in the dbsetup GUI, by completing the following:
   1. Click the Database button and select your type of database from the selection list (e.g. MySQL)
   2. Set the Host and Port fields to match the IP location of your database (as resolved from the enPortal/AppBoard server).
   3. Set the Database Name field to match the name of the database created to store the enPortal/AppBoard data.
   4. Set the User and Password fields to match the database user and password that were configured on your database to control access.
   5. Test the Connection by clicking the Test button to verify the database connection settings.
   6. Select Ok to save the changes and exit the tool.