Configuration
...
The VetView project contains four files that must be customized to your institution's settings. These files are named:
- VetView-authentication-config.properties
- VetView-database-config.properties
- VetView-communication-config.properties
...
File
To configure the web server to connect to external resource, like: Database, LDAP authentication, email server, metrics and logging, you will need to update the VetViewConfig.yml file. There is an example file below or you can find an example file included in the war after being deployed on the Tomcat server. The config file has been laid out in section that are covered below.
This file will be found at in the WEB-INF/classes folder (inside your VetView installation folder).
Configuring/Disabling LDAP
To configure the LDAP settings, open the VetView-authentication-config.properties file and change the settings to match your institution's. If your ldap requires more settings, you can add lines to this file.
| Info |
|---|
To read more about security in VetView, check out our page on Security. |
...
After:
Configuring Your Database
To configure the LDAP settings, open the VetView-database-config.properties file and change the settings to match the database you've setup for VetView.
Configuring Your Communications
| Note |
|---|
In previous version of VetView, there were more parameters stored in this file, but since version 0.9.2.4, many parameters were moved to the System Options Screen and are stored in the database. |
The VetView-communication-config.properties file contains the following settings:
| Setting Name | Possible Values | Meaning |
|---|---|---|
grails.vetview.external.report.interval | A number (in milliseconds) | This line supports a feature for routing your accession reports to an external processor. You can set the number (which is in milliseconds). |
| grails.vetview.external.report.enabled | "true" or "false" (without quotes) | This needs to be set to "true" if you want to use the external report system (using an external accession report system, rather than VetView's built-in system). If you aren't using the external report system, this should stay false (the default). |
| grails.vetview.request.status.change.queue.interval | A number (in milliseconds) | This relates the queue for status updates to be sent to external ordering systems (like UVIS). This should be a number (in milliseconds) that controls how often the queue gets processed. |
| grails.vetview.request.status.change.queue.enabled | "true" or "false" (without quotes) | This needs to be set to "true" if you want to push status updates to an external ordering system (like UVIS). |
| grails.vetview.machine.interface.server.interval | A number (in milliseconds) | If you are using the VetView TCP/IP Dawning/DI interface, this controls how often VetView polls the interface. |
| grails.vetview.machine.interface.server.enabled | "true" or "false" (without quotes) | This needs to be set to "true" if you want to use the VetView TCP/IP Dawning/DI interface. |
grails.machine.interface.server.url | A URL | For VetView installations using the TCP/IP Dawning/DI interface, this is the parameter you'll use to set the URL to reach that web application. The URL should be the address of the web app with "/Order" appended to it (for example, "http://128.192.84.39:8080/VvTcpIpInterface/Order"). |
| grails.uvis.url.timeout | A number (in seconds) | For VetView Labs installations that interact with UVIS Hospital, this is the number of seconds a link from UVIS into VetView will be valid. The primary reason there is a timeout at all is because of printing labels. When UVIS Hospital prints labels, it opens a webpage in VetView that can automatically print labels. If users were to refresh the page or navigate to this URL again (via the back button, for instance), it would print the labels again. |
| Info | ||
|---|---|---|
| ||
With VetView 2.0 the VetViewConfig.yml can now be added the to the Tomcat directory. This will allow for the configuration to be maintained between versions.
|
All configuration is now in the single VetViewConfig.yml file. The configuration file is broken up in section of Web Server Name, Database, Mail, Security, and Metrics. Each section is described below. ".yml" ( a recursive acronym for "YAML Ain't Markup Language" ) files use the # symbol to comment out the line and file format and spacing is important.
Web Server Name
With VetView 2.0 the API and Main project where merged into a single project and each Job and/or interface are assigned to run on a single web server by name. Set a unique name for each web server connected to database.
Database
Currently VetView only supports Oracle connection, however you will see an example of connecting to a PostgreSQL database for testing and future availability. The configuration settings that need to be updated are:
- URL: connection string. Example of a direct connect URL: jdbc:oracle:thin:@<hostname>:1521:<SID>
- Username:
- Password:
Email Setting ( SMTP mail server )
VetView uses Java mail plugin. Grails Mail Plugin Documentation This is an example UGA's Office 365 configuration.
Security
VetView uses Spring Security Plugin. Spring Security Documentation Currently we support local database stored authentication ( DAO ), LDAP, and JAAS. To configure which authentication provider active set the the providerNames setting. This is a list and multiple providers can be used. The plugin will check the USERNAME and password against each provider in the order listed in the providerNames list. If any provider is successful in authenticating the user is authenticated in VetView. This is used with login and in-app sign-off.
- providerNames: [ 'daoAuthenticationProvider', 'ldapAuthProvider' ] this is an example where it will check both local and LDAP. Local first then LDAP.
The example below has an example for LDAP settings but disabled.
Metrics
VetView has included a Elastic Search plugin able to send metrics. Micrometer Documentation This is an optional configuration if you have a local elastic installation or if you want to send metric to VetView directly in the future. VetVeiw's elastic search is currently not accessible due to firewall restriction and we are working with central campus IT to making this public.
