Liferay - 选择组织与门户实例
我们正在尝试使用 Liferay 6 为多个（非相关）组织创建一个基于 SaaS 的门户。我们希望找到一种可以根据用户信息自动生成这些组织设置的方法。
我们可能要求每个组织拥有单独的域/网站。
到目前为止，我已经考虑过此
- 门户实例
- 组织
的两种选择。根据我的理解，我认为这可以通过上述两种方法来实现。我想了解您在以下几点上对这两种方法的体验。
- 从长远来看，哪一种易于管理
- 哪一种可以轻松编程以自动创建新设置。
- 与保留一个门户实例与多个实例相关的数据安全性如何（是否有这样的事情？不确定）
- 还有其他方法吗？
We are trying to create a SaS based portal using Liferay 6 for multiple (non related) organizations. And we want to go for a approach where we can generate these organization setup automatically based on user information.
We may require to have separate domains/websites for each organization.
As of now I have thought about two options for this
- Portal Instance
- Organizations
As per my understanding, i think this can be achieved by both of the above approaches. I would like to know your experience on both of these approaches on following points.
- Which one would be easy to administer in long run
- Which one can be easily programmed to create new setup automatically.
- What about data security related to keeping in one portal instance vs multiple instance (is there any such thing?? not sure)
- Any other approach to this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
简单的答案是门户实例，因为它是为多租户而构建的。
这种方法的好处是可以分离数据。每个实例都维护自己的用户、社区、博客条目等集合。
在管理方面，将有 1 个帐户（全管理员）可以访问所有这些实例。最重要的是，每个实例都可以有自己的管理员来管理该特定实例。
另外，我不认为使用组织将允许您为它们拥有单独的域。
在 Liferay 6.1 中，组织不再有页面，只有站点有页面，尽管我们可以模仿站点的行为。
希望这有帮助。
Simple answer would be Portal Instances, since it was built for multi-tenancy.
Benefits to this approach would be that there would be segregation of data. Each instance maintains its own collection of users, communities, blog entries, etc.
Administration wise, there will be 1 account, the omni-admin, that can access all of these instances. On top that, each instance could have its own administrator that admins that particular instance.
Also, I don't believe using organizations will allow you to have separate domains for them.
Also going forward in Liferay 6.1, Organizations don't have pages only Sites have them, though we can mimic the behaviour with Sites.
Hope this helps.
我正在为多个站点使用组织，它们都看不到对方，每个站点都有自己的用户、角色、部分和社区。
Apache 和 Liferay 虚拟主机 url 可以正确重定向到每个组织主页。
对于管理员来说，我认为更容易，因为在一个控制面板中您可以管理所有内容，或者只是您想要的“范围”。
I'm using Organizations for multiple sites, none of them sees each other, each one have their own users, roles, sections and communities.
Apache and Liferay virtual hosts url's makes the proper redirects to each organization home page.
For the admin I think is easier because in one control panel you can manage everything, or just the "scope" you want.
关于使用实例，请检查配置实例的过程，并查看是否可以自动创建新实例。对于组织来说也不太确定，但必须接触 Portal-ext.properties 可能对自动化来说更糟糕。
问候
About using Instances, check the procedure to configurate them and see if you find it possible to create new ones automatically. Not very sure about that for organizations either, but having to touch portal-ext.properties may be worse towards automatization.
Regards