Asia Pacific (change)
Shortcuts: Downloads Fedora Red Hat Network
JBoss Enterprise Middleware
- JBoss ISV
- Overview
- Why Join?
- Registration
Why Join?
Dear ISV:
On April 24, 2007, Red Hat announced a new model by which it will distribute the JBoss product line to end users. Rather than selling the various components of the JBoss Enterprise Middleware Suite as individual components, it will sell them as platforms built around the application server, portal and SOA. This also means that there will now be two versions of JBoss solutions that are available: the Community Edition and the Enterprise Edition. There are several implications for ISVs with this new model, and this document will attempt to address these issues.
Background
Shortly after the merger of JBoss and Red Hat, a decision was made to align the JBoss business model more closely with the way Red Hat sold Linux, while at the same time creating more value for the end user. Historically, JBoss components were sold as individual pieces that a customer or partner was required to assemble and test on their own. The new model takes the individual JBoss components and bundles them together as a complete solution. Now rather than having to test several distinct components to verify that they will work together, Red Hat provides a platform that has been tested and certified to ensure that each of the individual components will function optimally as a whole. The platform also allows Red Hat to make licensing and pricing the product much more simple and straight forward so that there is less confusion as to what an end user is getting. It also allows Red Hat to more readily enable the channel to resell the JBoss products.
The platforms were designed to be a complete solution and cannot be broken into their individual components. However, all of the products will continue to exist as individual products at jboss.org.
Community Edition Vs. Enterprise Edition
Both the Enterprise and Community Editions will remain open source products and Red Hat will continue to adhere to the LGPL (and in some cases the GPL) while developing and managing these products. The primary difference between the Community and Enterprise versions is that support for the community edition will be provided just by the communities contributors, whereas the Enterprise version will be tested and certified by Red Hat and the core development team. In many ways, the Enterprise version is a subset of the Community version that is certified, tested and supported for 7 years.
Generally, the community edition will be revved early and often and will tend to lead the enterprise version in early adoption of technology. However, due to the nature of this early innovation, it will probably not be as stable as the enterprise edition. Also, binary patches, security fixes, bug reporting, etc. will generally not be as available for the community edition as they are for the enterprise edition. (Please see the chart below which compares and contrasts the two offerings.
| Services | JBoss.org | JBoss Enterprise |
|---|---|---|
| Open Source | X | X |
| Benefits from testing by worldwide Community | X | X |
| Patch Update and Service Pack Program | X | |
| Security Errata Program | X | |
| Hot Fix Program | X | |
| Automated Software Update and Alert Service | X | |
| Bug Escalation Process | X | |
| 24x7 Production Support & Consultative Service | X | |
| Platform Certifications & Training Certifications | X | |
| Defined Support SLA and End-of-Life Policy | X | |
| Out-of-the-Box Configured for Enterprise Use | X | |
| Includes JBoss Operations Network (ON) | X | |
| Availability of JBoss ON Monitoring | X | |
| Extensive coordinated internal/external testing | X | |
| Ability to Redistribute Patched JBoss Distributions | X |
New EULA
In addition to the new Community/Enterprise model for redistributing JBoss components, a new End User License Agreement was released in conjunction with JBoss AS 4.0.5 and later versions. This EULA will also apply to the other middleware products as they are revved and released.
Just as the Community/Enterprise model aligns the JBoss business with the Red Hat business, the new EULA puts the JBoss products in line with the trademark usage that is highlighted in the Red Hat EULA. The EULA was developed to help Red Hat manage and protect its brand and trademarks.
The part of the the EULA that most affects ISVs is Section 2 which states:
“This agreement permits Client to distribute unmodified copies of the Software Packages using the Red Hat trademarks that Red Hat has inserted in the Software Packages on the condition that Client follows Red Hat's trademark guidelines for those trademarks located at http://www.redhat.com/about/corporate/trademark/. Client must abide by these trademark guidelines when distributing the Software Packages, regardless of whether the Software Packages have been modified. If Client modifies the Software Packages, then Client must replace all Red Hat trademarks and logos identified at http://www.jboss.com/company/logos, unless a separate agreement with Red Hat is executed or other permission granted. Merely deleting the files containing the Red Hat trademarks may corrupt the Software Packages.”
What this means is that as long as you are distributing the exact JBoss image that you download from JBoss .org, nothing else is required of you. However, if you apply a patch, make changes to the source code, etc., you will be required to either remove the trademarks from the source code and any other supporting documentation or enter into a redistribution agreement with Red Hat.
How Middleware ISVs Can Work With Red Hat
Red Hat wants to work with ISVs that are integrating the JBoss products and has developed a program that will allow ISVs to take advantage of the ecosystem surrounding JBoss For enrollment into the partner program please go to http://www.redhat.com/partners/.
Red Hat has developed special pricing for ISVs that want to embed and redistribute JBoss products with their solutions. In addition to being able to sell in smaller increments that standard licensing, you will also be able to sell individual JBoss components (or you can sell the Platforms as they are currently defined). Developer support and training discounts are also available to our ISV partners.
If you are an ISV that has an existing support contract with Red Hat that includes a redistribution component, you will continue to receive support as outlined in that agreement.
Conclusion
We understand that this is a departure from what you are used to and we want to make sure that the transition is a smooth one. We look forward to working with you and talking to you about your plans for deploying JBoss-based solutions.
Additional information can be found at the following links:
Press Release:
http://www.redhat.com/about/news/prarchive/2007/next.html
jboss.org info:
http://labs.jboss.com/blog/new_development__distribution_and_support_model_for_jboss
More platform info:
http://connollyshaun.blogspot.com/2007/04/driving-developer-preference.html
Please feel free to contact Red Hat directly for further clarification of this new change and how it might impact your organization. We look forward to working with you.
Sincerely,
Your Red Hat Partner Team
Your Red Hat Partner Team