我可以在没有支持许可证的情况下使用 JBoss EAP 6 吗? [英] Can I use JBoss EAP 6 without a support license?

问题描述

JBoss 应用平台有 2 个发行版，一个社区版和一个企业版，社区版就像企业版的 Beta 版，那么 JBoss 7.0 实际上是 EAP 6 beta 1，7.0.1 是 beta 2，7.1.0 是 beta 3而 7.1.1 是 rc 1.

JBoss AS 7.1.2 和 7.1.3 会发生什么?这是一个非常有用的链接:http://henk53.wordpress.com/2013/01/09/the-curious-case-of-jboss-as-7-1-2-and-7-1-3/

所以我的问题是:我可以在没有支持许可证的情况下使用 JBoss EAP 6 吗?

可从 access.redhat.com/downloads 获得下载，您必须从中点击Evaluations and Demos"，然后点击JBoss Enterprise Application Platform Evaluation".

我读到 JBoss EAP 仍然是开源的，您可以自由使用它，但前提是您从源代码编译它，这不是一件容易的事，他们也不希望如此.

因此，如果我在生产中使用从评估和演示"下载的版本，这是否违法?

解决方案

TLDR;是的，您可以在没有订阅支持的情况下使用，但不可以，如果您只下载最新的 EAP 二进制文件，则不允许在生产中使用它.

这里有三个案例来考虑如何在没有支持订阅的情况下运行 JBoss EAP，其中两个也允许生产使用:

1.开发使用

您可以将任何 JBoss EAP 二进制版本用于开发目的，无需付费订阅.您不会以这种方式获得补丁或支持，也无法在生产中运行它.来自用于开发的下载":

<块引用>

要下载 JBoss EAP，您必须拥有一个帐户.你还需要接受 JBoss 开发人员计划的条款和条件提供 0 美元订阅，仅供开发使用.

2.EAP 6.x alpha 版本

所有 alpha 版本，例如 JBoss EAP 6.1 Alpha，都可以以任何方式或形式免费使用，也在生产中.来自这条消息:

<块引用>

6.1 Alpha 二进制文件是免费提供的(都用于开发和生产用途)到整个社区.

还有这个主题:

<块引用>

但是，此开发限制不适用于 EAP alpha发布.如果您愿意，EAP alpha 版本可能会在生产中运行欲望.至于它们的质量，6.1.0.Alpha 的质量与 a社区最终版.然而，阿尔法是广泛的地方测试和强化开始，所以我们推荐 GA 或更高版本如果您对使用 EAP 感兴趣，则可以进行生产.

JBoss FAQ, 说

<块引用>

Q:如果EAP 6.1.0.Alpha和社区7.2.0.Final是一样的，为什么叫阿尔法?答:EAP 的发行方式更为保守和严格硬化过程，包括广泛的质量测试和合作伙伴认证.从历史上看，每个 EAP 版本都从我们最最近的社区决赛，然后随着这种强化而分阶段发布工作被执行.第一个 EAP 阶段 Alpha 是等效的，或者更好，社区质量最终版本.

问.我如何使用 EAP 6.1.0 Alpha 有任何限制吗?A. 否– 它具有与 AS 版本相同的许可和条款，但是因为它是一个我们不建议在生产中使用 Alpha 版本.

这两篇 Redhat 知识库文章证实 EAP 6.3.Alpha 也可供所有人在生产中运行(仅对付费订阅者可见):

• 红帽 JBoss EAP 6.3 Alpha 版可用性"
• 在不支持订阅的情况下在生产中使用 JBoss EAP alpha 版本"

现在是 John Doyle，负责红帽 JBoss EAP 6 的高级经理, 确认

<块引用>

之前关于 EAP 6.1 Alpha 的声明适用于所有 EAP 6 Alpha发布.它们可以在生产中运行.

3.自编译版本

EAP 也可作为源代码分发，如果您自己编译它们，删除任何 Red Hat 商标，在生产中运行它们应该是合法的.当然，你完全靠自己来支持他们.为了使编译更容易，这个 github 帐户 上有一个脚本，并使用该脚本构建您自己的EAP就这么简单

git clone git://github.com/hasalex/eap-build.gitcd eap-build./build-eap.sh

有关详细信息，请参阅项目自述文件.还有关于其中一个问题关于构建的法律地位的扩展讨论，这是指声明，WildFly项目负责人说，合法使用产品的方法之一是

<块引用>

3. 自行构建和支持 EAP - 您可以获得企业版本的一些好处(例如旧主要版本的补丁等)，但是您必须投入时间和精力来构建和维护/验证您的应用服务器分发位.

JBoss Application Platform has 2 distributions, a community and an enterprise release, community releases are like Beta releases of enterprise releases, JBoss 7.0 is then actually EAP 6 beta 1, 7.0.1 is beta 2, 7.1.0 is beta 3 and 7.1.1 is rc 1.

What happens with JBoss AS 7.1.2 and 7.1.3? this is a very informative link: http://henk53.wordpress.com/2013/01/09/the-curious-case-of-jboss-as-7-1-2-and-7-1-3/

So my question is: Can I use JBoss EAP 6 without a support license?

Downloads are available from access.redhat.com/downloads, from which you have to click on "Evaluations and Demos", and then on "JBoss Enterprise Application Platform Evaluation".

I have read that JBoss EAP is still open source and you can use it freely, but only if you compile it from source, which is not an easy task nor they want it to be.

So if I use in production the version I have downloaded from "Evaluations and Demos", is this illegal?

解决方案

TLDR; yes, you can use without a support subscription, but no, if you just download the latest EAP binary, you're not allowed to use it in production.

Three cases here to consider how you can run JBoss EAP without a support subscription, two of which also allow production use:

1. Development use

You can use any JBoss EAP binary version for development purposes without a paid subscription. You won't get patches or support that way, and you can't run it in production. From "Downloads for Development Use":

To download JBoss EAP you must have an account. You also need to accept the terms and conditions of the JBoss Developer Program which provides $0 subscriptions for development use only.

2. EAP 6.x alpha versions

All alpha versions, such as JBoss EAP 6.1 Alpha, are free to use in any way or form, also in production. From this message:

The 6.1 Alpha binary is made available for free (both for development and production use) to the entire community.

And this thread:

This development restriction, however, does not apply to EAP alpha releases. EAP alpha releases may be ran in production if you so desire. As to their quality, 6.1.0.Alpha is of equivalent quality to a community final release. However, the Alpha is where the extensive testing and hardening begins, so we recommend GA or later for production if you are interested in using EAP.

This is also confirmed by entry in JBoss FAQ, saying

Q: If EAP 6.1.0.Alpha is the same as community 7.2.0.Final, why is it called Alpha? A: EAP has a much more conservative and rigid release hardening process, including extensive quality testing and partner certification. Historically every EAP release starts from our most recent community final, and then releases in stages as this hardening work is performed. The first EAP stage Alpha is of equivalent, or better, quality to a community Final release.

Q. Are there any restrictions on how I can use EAP 6.1.0 Alpha? A. No – it has the same license and terms as AS releases however as it's an Alpha release we don't recommend using it in production.

And these two redhat knowledgebase articles confirming that EAP 6.3.Alpha is also available for all to run in production (only visible for paid subscribers):

• "Red Hat JBoss EAP 6.3 Alpha Availability"
• "Using JBoss EAP alpha version in production without support subscription"

Edit: and now John Doyle, Senior Manager responsible for Red Hat JBoss EAP 6, confirmed that

The earlier statements about EAP 6.1 Alpha apply to all EAP 6 Alpha releases. They can be run in production.

3. Self-compiled versions

EAPs are also available as source distributions, and if you compile them yourself, removing any Red Hat trademarks, it should be legal to run them in production. Of course, you are completely on your own on supporting them. To make compiling easier, there is a script on this github account, and using that script building your own EAP is as easy as

git clone git://github.com/hasalex/eap-build.git
cd eap-build
./build-eap.sh

See the project readme for details. There's also extended discussion on one of its issues about the legal status of the build, which refers to statement by Jason Greene, WildFly project lead, saying one of the ways to legally use the product is

3. Self build and support EAP - You get some of the benefits of the enterprise releases (e.g. patches to older major versions and so on), but you have to invest time and energy to build and maintain/verify your app server distribution bits.

这篇关于我可以在没有支持许可证的情况下使用 JBoss EAP 6 吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！