Page 1 of 1

Two Companies on Same Instance

PostPosted:Tue Nov 03, 2015 1:07 am
by sigma
Hi,

Our company has been using OpenKM & I have been asked to make the changes to support another sister concern into the same instance to reduce the server & maintenance cost. I have downladed the portable Dev Environment but I don't see anything related to changing the folder based on the company. Can some one help me on this?.

Thanks,
Sigma

Re: Two Companies on Same Instance

PostPosted:Wed Nov 04, 2015 9:44 pm
by jllort
Community version has not "tenant" option what is only available from professional version. In your scenario the only solution is to have two folders on /okm:root/ for company1 and company2 and set privileges for each one. No other solution available from community version ( well have two VM on same server is another way to solve this kind of problem, with two openkm instances ).

Re: Two Companies on Same Instance

PostPosted:Thu Nov 05, 2015 12:47 am
by sigma
Thanks for the reply, I understand it is available in Professional version. But my company will not be able to buy it, so they are asking me to make the changes to handle it. Where do i have start if i have to make the changes myself?.

Thanks,
Sigma

Re: Two Companies on Same Instance

PostPosted:Sat Nov 07, 2015 9:52 am
by jllort
ufff, all application is affected by this change, on almosts tables is introduced the tenant value. Also must be changed soemthing in search engine, because each user should only see data in his own tenant.

It was a changed 1-2 years ago and sincerally when we do the periodical technical staff meeting is a topic what comes back again and again. Some of us we think in some scenarios is better have two instances rather merge on a tenant scenario ( it depends about the usage, number of files, concurrent users etc... ). The problem on shared application scenario is that the way on how one tenant is used can cause bad performance in other. I suppose it will not be your problem. However my suggestion is use two instances, virtualize a server, do not go on modify code direction this is a radical change ( we needed about 2 months for doing it, and after a lot of bugs introduced by the change ). Believe me, will be more cheap and less stress for you if you separate in two servers ( or virtualized ).