Configuration Files
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
These files 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.
To read more about security in VetView, check out our page on Security.
To disable LDAP completely (and rely solely on local VetView accounts), open the file and comment out each line with a '#'.
Before:
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
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. |
