Next: About this document ...
Up: HID Web App Management/Configuration
Previous: HID Web App Management/Configuration
Contents
During the initial compilation and deployment, HID web application is setup with default parameters which are good enough
for basic HID web app usage. This parameters can be changed by using the configuration panels.
This functionality is also only available for the admin user of the primary database connected.
By clicking on the App Configuration link on the left menu (see Figure 3.1), the admin user will arrive at the
application configuration panels organized into four tabs named General, Mediation, Web Services and
Advanced.
In the General tab (see Figure 3.8),
there is only one parameter, namely Download Cache Root. The default for this parameter is
$HOME/download_cache, where $HOME is the home directory of the user the HID web app is deployed under.
This parameter corresponds to the local cache directory for image download scheduler and needs to be accessible from the
deployed HID web application.
In the Mediator tab (see Figure 3.9), there are three configuration parameters affecting mediated (federated) operation.
- Query Only Operation - for mediated queries, the mediator user does not own the schema and can not modify database, hence
unless the associated database schema name for the mediator DB user is provided in
this tab, you need to check this checkbox to make the whole application query only if your
HID web application is connected to multiple databases via non-schema owning database users
like the mediator user used in FBIRN.
- Mediator Mapping File - This path is relative to the deployment. An ontology based lookup for common assessment terms
is approximated by this simple mapping file. This parameter is currently not used.
- Mediator Schema Name - The schema named the mediator user is associated with.
If the mediator user is not the DB schema owner, the metadata associated from the actual DB
schema cannot be queried without explicitly specifying the schema name.
HID web app relies on DB schema metadata info for dynamic queries and metadata driven operation.
In the Web Services tab(see Figure 3.10) , there is only one parameter, namely, DB ID for Web Services.
This parameter must be set for HID web services to function properly.
Set this parameter to the database ID for the primary database
(the site hosting the HID web app). For example for UCSD the value
would be ucsd_fbirn.
In the Advanced tab (see Figure 3.11), more advanced configuration parameters are collected.
- Public Mode Login - If checked, read only public mode login is enabled. The user needs to enter her email address
only in that case. Public mode operation is only advised if HID web app is used to serve public
data as in the case of FBIRN BDR. Currently, once Public mode login is selected, the web based database/user and application
configuration is not available. This will be fixed in the next release.
- Check DB Schema Version - Toggles primary HID instance database schema version checking (default is true for version checking).
If the database schema and the current version of the HID web application are not compatible no user
login is allowed till the database schema and contents are updated.
- Email Host - mail server (e.g. smtp.ucsd.edu) for job status including download jobs) notification. All four
parameters (email host, email user, email password and email sender) must be specified for
notification process to be activated.
- Email User - User name for the email account used for notification.
- Email Password - Password for the email account used for notification.
- Email Sender - The notification email will be from this user (e.g iozyurt@ucsd.edu)
Figure 3.8:
General Configuration Tab
 |
Figure 3.9:
Mediation Configuration Tab
 |
Figure 3.10:
Web Services Configuration Tab
 |
Figure 3.11:
Advanced Configuration Tab
 |
Next: About this document ...
Up: HID Web App Management/Configuration
Previous: HID Web App Management/Configuration
Contents
Burak Ozyurt
2008-04-22