Geek Answers Handbook

Liferay - Organization Choice vs Portal Instance

We are trying to create a portal based on SaS, using Liferay 6 for several (unrelated) organizations. And we want to take such an approach when we can automatically create this organization based on user information.

We may require separate domains / websites for each organization.

At the moment, I’ve thought of two options for this

  • Portal Instance
  • The organization

According to my understanding, I think that this can be achieved by both of these approaches. I would like to know your experience regarding both of these approaches on the following points.

  • Which one will be easy to administer in the long run
  • Which program can be easily programmed to automatically create a new installation.
  • How about data security associated with storing in one portal instance against multiple instances (are there any such things not sure)
  • Any other approach to this?
+5
source share
3 answers

A simple answer would be an instance of the portal, since it was created for multi-tenant rentals.

The advantages of this approach are that there will be data sharing. Each instance maintains its own collection of users, communities, blog entries, etc.

, 1 , omni-admin, . , , .

, , .

, Liferay 6.1, , , .

, .

+8

, , , , . URL- Apache Liferay .

, , "", .

+2

On using instances, check the order in which they are configured and see if you can automatically create new ones. Not very sure about this for organizations, but touching portal -ext.properties might be worse for automation.

Hi

0
source

More articles:


All Articles