VetView 2.0 Portal and Web Services Calls

Owned by Cathy Allison
Last updated: Dec 17, 2021
2 min read

 

As part of the changes to the application in Version 2.0 of VetView, we modified how the Portal is allowed to access information. The Portal is no longer allowed unfettered access to the database, but must instead speak to a designated VetView application machine to obtain this information via REST web service calls.

These changes make VetView more secure, and will allow us to eventually add two-way communication between the Portal and the main application. For now, all calls made from the Portal will be GET commands for read-only information.

This page describes the functionality for version 2.0 of VetView. Significant changes were made in version 2.1. Documentation on the latest release is found in our User Guides at Version 2.1 and Greater API Web Services Documentation

New Structure of the Application

 

New Application Structure for version 2.0

As of version 2.0, the API and Main Application have been merged into a single project. You can have multiple instances of this application running on separate machines, or as VMs in a cluster, depending on how your internal IT service infrastructure is set up.

The Portal application will remain as a stand alone project, but it is a lot more light weight as everything that could be incorporated into the Main App has been removed. The Portal application can run on the same Tomcat as the main VetView application.

The major improvement for this is being able to designate a specific installation of the VetView main app server to handle all of your Portal service calls. This way you can minimize the impact of the primary applications your internal users are causing and leave the Portal calls to their own application, preventing lag and slowdowns.

We have also made the Portal project open source so you can customize the look and feel of your hospital and lab portals, and leverage the service calls for any of your own custom applications.

Setting Up the Portal and a dedicated VetView Portal application system

You will need:

  • The URL of your Portal web project

  • The URL or IP address of the VetView application server it will talk to

GET commands and their Structure

  • Common / Security

  • Labs Portal

  • Hospital Portal