next up previous contents
Next: Web App Configuration Up: HID Web App Experiment, Previous: Adding a clinical assessment   Contents

HID Web App Management/Configuration

As of version 2.1, HID web app has a web based user/database management and application configuration functionality. This functionality is only available for the admin user of the primary database connected. When operating under federated mode, HID web application will be connected to more than one database for mediated queries. It can also be used to manage more than one database. In both cases, one of the databases acts as the primary (default) database. For each configured database, there is mandatory web user named 'admin'. The admin web users of databases other than the primary database can update clinical data but they cannot manage users, databases and configure the web application. When the admin webuser of the primary database logs in to the HID web app primary database, she will see additional two options on the left menu (see Figure 3.1). Clicking the Configuration link, shows the User/Database management panel (see Figure 3.2). In this panel, new web users can be added, their privileges and passwords can be changed or removed. Also, new databases can be added or removed from the HID web app at runtime. For many panels and buttons context sensitive help is available by clicking on the question mark icons.

To add a new database for multisite queries, click the add button, next to the Database dropdown to arrive to the Database Configuration screen (see Figure 3.3). In this example, parameters for Duke's FBIRN Oracle database is provided. All the available sites shown in the dropdown are read from from the nc_site table of the primary HID. The database id provided must be unique within all configured databases. After pressing Add button, you will arrive at the User/Database management panel for Duke (see Figure 3.4). You need to add a new database user to be able to connect the the newly added database (Duke's in this case). By clicking on the Add New Database User button, you will arrive at the User Configuration screen (see Figure 3.5), where you will enter the database user name and password. It is a good idea to test the database connection before adding the database user to the system. This can be accomplished by pressing Test Connection button. If the connection is successful, you will see a screen like in Figure 3.6. After this, click the Add button to add the database user to the system. The system will, in addition, create the mandatory 'admin' web user with the default password 'admin', which you should change immediately. The newly added database user and the mandatory admin user is shown in the Database/User Configuration panel in Figure 3.7. Here you can change the admin web user password by clicking on the Edit button. New web application users can be added by clicking on the Add New User button. Adding and removing privileges for the web application users are also managed in this panel. Here the admin web user for the secondary database duke_fbirn has manageExperiment and manageSubject privileges. The admin privilege is not available for secondary databases.

Figure 3.1: Primary db admin user main view
Image first

Figure 3.2: Database/User Management Panel
Image db_config_1

Figure 3.3: Database Configuration
Image dbc_adddb

Figure 3.4: Database/User Management Pane for newly added DB
Image dbc_adddb_after

Figure 3.5: New Database User
Image dbc_add_dbuser

Figure 3.6: After Successful Connection Test
Image dbc_add_dbuser_testcon

Figure 3.7: After New Database User Addition
Image dbc_add_dbuser_after



Subsections
next up previous contents
Next: Web App Configuration Up: HID Web App Experiment, Previous: Adding a clinical assessment   Contents
Burak Ozyurt 2008-04-22