Multi-Tenancy

Submitted by Guest on Tue, 19/02/2019 - 11:22

General developer's discussion

I am new to the forum. I would like to know if openVPMS can be used in a multi-tenant setup. Are there any special settings provided to enable multi tenancy.

I was also going thru the code base and realized that most of the changes were made made in long back in 2011. Is this project not under active development.

Thanks

Rafi

Re: Multi-Tenancy

Submitted by tanderson on Tue, 19/02/2019 - 12:33.

Depends by what you mean by a multi-tenancy setup. What are you trying to achieve?

OpenVPMS is under active development. See the Bitbucket repository at https://bitbucket.org/OpenVPMS/openvpms .

Most development at present is taking place on the 2.1-dev branch.

Re: Multi-Tenancy

Submitted by rshaik (not verified) on Tue, 19/02/2019 - 12:45.

Clinic A Owned and operated by Mr A

Clinic B Owned and operated by Mr B

Clinic C Owner and operated by Mr C

All the Clinics can connect to the same instance of Tomcat Server hosted in the cloud . The URLs will off course be different for each one of the clinics like say :-

clinicA.xxxx.com

clinicB.xxxx.com

clinicC.xxxx.com

When Mr A logs into clinicA.xxxx.com he must only view and manage objects relevant to clinic A and likewise for Mr B and Mr C. Can this type of configuration setup be achieved without too much engineering effort.

Let me know if this is clear enough.

Thanks

Rafi

Re: Multi-Tenancy

Submitted by rshaik (not verified) on Tue, 19/02/2019 - 12:47.

Another Question:-

What is the install base of OpenVPMS in the USA . How many clinics are using this Software . Do you know.

Thanks

Rafi

Re: Multi-Tenancy

Submitted by Ben_Charlton on Tue, 19/02/2019 - 14:02.

Rafi there are a number of ways of achieving that config...using a combination of changing paths / clinic plus a apache webserver proxy etc

Your looking at a cloud based button click rollout it is possible you just need a good sysadmin that is familiar with tomcat.

OpenVPMS is a tomcat application and thus could be treated as any other tomcat application.

I would argue that OpenVPMS's user security needs improvement beyond a clear text user/pass config but again even in the current state its manageable

Regards

Ben

OpenVPMS Installer and Helper

Ph: +61423044823

Email: info[at]charltonit.com[dot]au

Re: Multi-Tenancy

Submitted by rshaik (not verified) on Wed, 20/02/2019 - 03:48.

Thanks Ben.

Re: Multi-Tenancy

Submitted by tanderson on Wed, 20/02/2019 - 07:42.

Some things to be aware of:

OpenOffice is used for merging and printing of .doc and .odt documents. It doesn't like multi-threading, so you will need to configure it to launch an instance per clinic.
memory use cannot be restricted if you deploy multiple clinics in a single tomcat instance. It would be better to start a tomcat instance per clinic.
OpenVPMS allows users to print to their local printers directly. To avoid clinics seeing those belonging to different users you can:
- run each clinic in a different host
- disable printing altogether, and require users to download PDFs and print locally
- re-work printing so that users only see their own printers
clinics running on different timezones need to be on separate hosts

Re: Multi-Tenancy

Submitted by tony on Wed, 20/02/2019 - 16:07.

Hi Rafi,

The simple answer is No. To support this you will need a separate tomcat instance and database for each customer as OpenVPMS only supports a single practice with shared customers and products etc. You can obviously give the impression of multi-tenancy by careful design of your front end application load balancers/proxies, banks of managed tomcat instances, a shared database server with individual databases per practice and a suitable dev-ops environment.

Cheers

Tony

Re: Multi-Tenancy

Submitted by rshaik (not verified) on Thu, 21/02/2019 - 04:02.

Thanks Tony,

Multi-Tenancy

Comment viewing options