Alfresco社区企业功能比较 [英] Alfresco Community Enterprise Feature Comparison

问题描述

我看过这个问题，但是答案根本不够好。我已经在网上搜索了，可以找到主要区别的清晰清单。

我特别惊讶地看到上述链接中存在矛盾，该矛盾仅包含4个简短答案

因此，问题是，除了支持之外，Alfresco Community和Enterprise版本（当然是当前版本）之间的（全部）区别是什么？

企业版中是否存在社区版中没有的功能或技术功能？

我找到了奇怪的是，很难获得清晰的清单。从业务的角度来看，在论坛上查找此答案不是一个严肃的选择。

直到现在，我发现此链接有用，但这是从2009年开始的。

特别是，我发现平台支持很有趣，社区版仅支持灯泡：

• Linux


• MySQL


• Tomcat


• OpenLDAP


• Firefox

企业版支持：

• Windows


• SQL Server


• WebLogic，WebSphere


• AD / Kerberos


• IE和Safari

显然，这些功能仅在企业版：

JMX监视

• 运行时管理：那到底是什么？那么社区版本中有什么？


• 运行时索引一致性检查和更新：那么社区版本中有什么？


• 高性能和可用性：如何


• 存储策略


• 开放源代码和专有技术堆栈支持：哪一个是正确的？社区版支持哪些版本？

如果有人可以指导我编写有关这些差异的详尽文档，那将是很好的。 / p>

我也浏览了Wiki，但在那里找不到我的问题的答案。

解决方案

企业版和社区版之间的差异在不同版本之间会有所不同，并且主要对管理员可见。我们会在中型到大型环境中看到或保持两种Alfresco口味，我想说的是，哪种口味或预算是最适合您的最佳决定/版本？对于两个版本都可以在生产环境中运行Alfresco，强烈建议具备出色的基础架构和Java技能。
技术差异并不像无法为用户提供非常相似的功能那样显着-因此，如果您实际上在做出决定，则应专注于良好的技术合作伙伴，支持服务以及以下事实：您只能在企业版订阅中获得正式补丁，而在社区中则不能。 BTW Alfresco Enterprise不是开源的，但对于大多数最终用户而言，这并不是真正的兴趣点。您可以作为订阅客户访问该代码，但该代码不是公共可用/不可访问的。

功能的主要区别已经或多或少地被命名：

1. 管理

   
   
   
   
   
   • 企业具有更多视图和设置管理Web GUI。在社区中，您只能从命令行访问大多数配置。这可能是一个限制，但实际上，管理员更喜欢命令行和脚本自动化。
   
   
   • 企业版可让您在运行时更改某些Alfresco设置（大多数设置仍需要重新启动）。可以在GUI中进行某些更改，在jmx界面中进行更多更改。此外，您还可以停止和启动CIFS协议服务器之类的子系统。我们使用此功能将系统切换为只读模式。这就是运行时管理的意思。社区要求重启服务才能进行大多数配置更改。可以通过诸如groovy之类的高级脚本或通过实现模块来解决此问题。
   
   



2. 索引

   
   
   
   
   
   • 运行时索引一致性检查和更新不是预期的自修复功能。您将必须（至少现在）了解到，即使在企业环境中，您也必须不时地重新创建Alfresco索引，并且最好将重点放在如何加快娱乐活动或如何设置备用索引上的好的策略上，而不是搜寻使用检查和更新方法的索引事务失败。对于主要的文档模型更改，您仍然需要重新创建索引。
   
   



3. 高性能和可用性

   
   
   
   
   
   • 这主要是群集和复制功能，在社区中不再可用。它与MS群集类似：由于缺少一些概念，因此需要进行大量的工作才能查看更多的可用性。就复杂性而言，价格很高，并且最终可能会失去鲁棒性。即使有企业支持，保持露天集群运行仍然是一项艰巨的任务-因此，您需要很好的论据，为什么要采用这种方式。但是，当然：它是可能的和可用的！
     高性能：应该没有什么区别，如果-我对这个解释很好奇。
   
   



4. 技术堆栈

   
   
   
   
   
   • 主要区别在于对数据库的支持。在社区中，您只能在MySQL和Postgres之间选择（社区没有Oracle或MS SQL）。所有其他技术都独立于企业或社区（AD，Kerberos，OS，浏览器等）
   
   
   • Java容器：我相信Alfresco的所有安装中有95％以上是在tomcat中运行的。该配置已记录，测试和扩展。使用WebLogic或WebSphere只会给您带来新的挑战，而没有其他附加值-恰恰相反：您必须自己解决大多数问题，并且不能从其他经验中受益。
   
   

存储策略：我不太确定，如果社区中不再提供内容存储选择器/存储策略，请检查4.2.x ，但在3.x版本中已经存在。

：存储策略已在社区4.2.x中删除：

  NoSuchBeanDefinitionException：没有定义名为'storeSelectorContentStoreBase'的bean 
  

如果确实需要有人可以通过为社区编码模块来重新启用该功能。

致谢

I've seen this question but the answers are simply not good enough. I've searched the web and could find a clear listing of the main differences.

I am particularly surprised to see contradictions in the above link, that holds only 4 short answers.

So the question is, beyond support, what are (all) the differences between Alfresco Community and Enterprise editions (for the current versions of course)?

Are there functional or technical features that available in the Enterprise edition, that are not in the community edition?

I find it strange that it's so difficult to get a clear list. Looking at the forums to find this answer is not a serious option from a business perspective.

Until now, I found this link to be useful, but it's from 2009.

In particular, I find the platform support interesting, with the community edition supporting only lamp stuff:

• Linux
• MySQL
• Tomcat
• OpenLDAP
• Firefox

And the enterprise edition supporting:

• Windows
• SQL Server
• WebLogic, WebSphere
• AD/Kerberos
• IE and Safari

Apparently, these features are only available in the enterprise edition:

JMX monitoring

• Runtime admininstration: What's that exactly? And what's in the community edition then?
• Runtime indexing consistency check and update: What's in the community edition then?
• High performance and availability: How is that implemented and what's in the community edition then?
• Storage policies
• Open source and proprietary technology stack support: which ones exaclty? Which ones are supported in the community edition?

If anyone could guide me towards serious documentation about these differences, that would be great.

I also went through the wiki but could not find an answer to my questions in there.

解决方案

differences between Enterprise and Community vary in detail from version to version and are mainly visible for administrators. We see or maintain both flavors of Alfresco in midsize to very large environments and I would say it's more or less a question of taste and budget what the best decision / edition is for you. Excellent skills in infrastructure and java are highly advisable for both editions to run Alfresco in production. The technical differences are not as dramatic as not being able to provide very similar functionality for the users - so if you're actually in a decision you should focus on a good technical partner, the support services and maybe the fact that you only get official patches in the Enterprise subscription, not on the Community. BTW Alfresco Enterprise is not Open Source but this is not a real point of interest for most end users. You can access the code as a subscription customer but it is not public available/accessible.

The main differences in features are already named more or less:

1. Administration

   • Enterprise has more views and setting in the admin web GUI. In Community you can access most configuration only from the command line. This may be a restriction but in real live Administrators prefer the command line and scripting automation.
   • Enterprise lets you change some Alfresco settings during runtime (most settings still require restart). Some can be change in the GUI and more in the jmx interface. Also you're able to stop and start subsystems like the CIFS protocol server. We use this feature to switch a system in read only mode. This point is meant with "runtime admininstration". Community requires restart of the service for most configuration changes. It is possible to work around this by advanced scripting like groovy or by implementing modules.

2. Indexing

   • Runtime indexing consistency check and update is not a self healing functionality as expected. You will have to learn (at least for now) that you have to recreate the Alfresco index from time to time even in Enterprise environments and that it is better to focus on good strategies how to speed recreation or how to setup standby indexes instead of hunting failed indexing transactions using the check and update methods. For major document model changes you need to recreate the index anyway.

3. High performance and availability

   • This is mainly the cluster and replication functionality which is no longer available in Community. It's similar to MS Clusters: It's a lot, lot work for very view more availability since some concepts are missing. The price is high in terms of complexity and can end up in loss of robustness. Even with enterprise support it's a hard job to keep a alfresco cluster running - so you need very good arguments why to go this way. But of course: its possible and available! High performance: There shouldn't be any difference and if - I'm very curious about the explanation.

4. Technology stack

   • The main difference is the database support. In the Community you only can choose between MySQL and Postgres (No Oracle or MS SQL for Community). All other technologies are independent from Enterprise or Community (AD, Kerberos, OS, Browser, ...)
   • Java Container: I believe over 95% of all Alfresco installations run in tomcat. That's the configuration which is documented, tested and scales. Using WebLogic or WebSphere gives you no added value except new challenges - quite the contrary: You have to solve most issues for yourself and can't benefit from others experience.

Storage policies: I'm not pretty sure and should check in 4.2.x if the Content Store Selector / Storage policies is no longer available in the Community, but it was there in the 3.x versions.

[Edit]: storage policies have been removed in Community 4.2.x:

NoSuchBeanDefinitionException: No bean named 'storeSelectorContentStoreBase' is defined

If there is a really need for this functionality someone may re-enable that feature by coding a module for Community.

Regards

这篇关于Alfresco社区企业功能比较的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！