topic Re: multi client with ldap in Alfresco Archive

multi client with ldap

jwiersma — Sun, 16 Jun 2013 13:31:59 GMT

Hi,I have successfully installed Alfresco with openLDAP and it works great in our test environment.Now I need to deploy this standard configuration (with custom theme and share config) for 50+ clients.They all use the central ldap server for authentication. All client logins are located in a separat

Re: multi client with ldap

afaust — Sun, 16 Jun 2013 15:16:23 GMT

Hello,

you can use either a separate Alfresco installation or a multi-tenant environment to support your clients - depending on other factors like the amount of users, content and integration features, either one of these may be better suited.
As far as I know, the LDAP component has not yet been integrated with the multi-tenancy capabilities of Alfresco (<a href="https://issues.alfresco.com/jira/browse/MNT-1898">quick search JIRA documentation issue</a>). I have not invested to much time myself into this area, but I'd think this is largely a matter of implementation effort and priority, not something that is technically impossible / too challenging.

Regards
Axel

Re: multi client with ldap

jwiersma — Sun, 16 Jun 2013 19:41:15 GMT

Thanks. Can separate Alfresco installs (using mainly Share websites) exist on the same (Ubuntu / LAMP) server ? Or do I need to spawn a new linux server for every install ?

Re: multi client with ldap

mrogers — Mon, 17 Jun 2013 10:11:35 GMT

Yes you can run many instances of alfresco on one machine. Just make sure each instace has separate resources (IP ports, shared folder, database, content store)

Re: multi client with ldap

afaust — Tue, 18 Jun 2013 10:22:55 GMT

You <b>can</b> run as many Alfresco instances on one system as you want as long as you provide different resources like mrogers stated - the question is how much load the server can handle and what kind of usage you are expecting. A mere single CPU with just 2 or 4 GiB of RAM shouldn't be used to deal with more than one full Alfresco stack (Repository, Share, SOLR, supporting services) in production use or you'll have to severely restrict the computing power for each instance.