Configuration
Database connection
SICS ADH Server requires a connection to the SICS database, in order to retrieve user access rights. It is therefore necessary to bind the JNDI resource named jdbc/sics to the correct JDBC resource. This can be done by editing META-INF/context.xml or though the application server administration pages.
One SICS ADH Server instance can serve only one SICS environment/database.
The database schema to be used can be specified by editing WEB-INF/web.xml.
Like SICS API Server, SICS ADH Server can use an application managed DB connection. Please refer to SICS API Server documentation for finding out how.
Logging
Server logging can be configured in WEB-INF/classes/log4j2.xml
Other configuration options
Other settings for the Server, that can be set in WEB-INF/web.xml, are:
| Setting | Description | Default value |
|---|---|---|
SystemPoolInitialSize |
Sets the initial size of the System Pool. This value indicates how many requests can be handled concurrently, since each request needs to get hold of a System in order to be processed. Must be an integer greater than 0. |
3 |
CloseConnectionBeforeReestablishFromJndi |
SICS ADH Server reestablishes a database connection before processing a request if the database source is a JNDI source. As a default the current connection will be closed before trying to request a new one. Set the value of this parameter to false to prevent closing the current connection. |
- |
RefreshCachedMappingsInterval |
Interval (in minutes) to wait before forcing an automatic light refresh of the system. A light refresh will make the server read Automated Document Handling mappings from the database, making sure that they are up-to-date. |
0(no automatic refresh) |
UserAuthorizationInterface |
The canonical classname of the class implementing the User Authorization Interface. This parameter is not mandatory and should be set only if the current configuration requires the user used for logging to the database must receive authorization through the UserAuthorizationInterface. |
- |
Security-Constraint |
This configuration enables the application to be exclusively accessed via HTTPS. All HTTP connections will automatically be redirected to HTTPS. |
- |