background image

Putting open source to the test: The making of JBoss Enterprise Middleware

8   

www.jboss.com

 

brAnching cOdE And AssEMbling cOMPOnEnts 

Once requirements have been agreed upon and code sources identified, the JBoss Enterprise Middleware 

productization team creates a code branch that will become the next release of the product. At this point, 
ongoing open source community development no longer affects the branched code, so the product team 
can stabilize and test the software without having to incorporate new capabilities. Any code changes to the 

branch, no matter how minor, are first submitted to the upstream JBoss.org project for approval, and then, 

once approved, incorporated into the associated Enterprise JBoss Middleware product. The productization 

team combines the code from these various sources — from JBoss.org projects or other open source proj-

ects — and integrates them to form a single enterprise software product.

When this analysis is complete, the product team identifies the specific components and versions that will 

be assembled and tested to become the next release of the product. The team then defines specific objec

-

tives for the release, balancing ambitious requirements with time and resource constraints. Requirements 

include not only functional capabilities, but also usability requirements, platform certification, perfor

-

mance characteristics, scalability requirements, installation and migration tools, and other requirements 
for capabilities that make customers’ lives easier.

crEAting JbOss EntErPrisE MiddlEwArE

To create each JBoss Enterprise Middleware product, JBoss productization and delivery teams proceed 

through a well-defined productization process that takes an average of four to five months to complete.

1

2

3

4

5

D

e

li

ve

ry

 p

h

a

se

P

ro

d

u

ct

iz

a

ti

o

n

 T

e

a

m

PLATFORM
CANDIDATE
RELEASE

QUALITY
ASSURANCE

jboss.org
projects

jboss.org

eng

community

Product

management

JBoss

productization

engineers

JBoss QA

documentation team, 

certified partners

JBoss release

engineering

Product

requirements

definition

Platform 

component

engineering 

+ integration

Platform 

testing

certifi

documentation

Platform release

(general availability)

Содержание JBOSS ENTERPRISE MIDDLEWARE -

Страница 1: ...tization process JBoss Enterprise Middleware teams continually harden and transform cutting edge open source technology into well tempered enterprise software products with unsurpassed quality performance and stability then deliver it with top notch support and mission critical SLAs Here s how it s done June 2008 ...

Страница 2: ... Testing function and quality Page 9 Certifying platform and database compatibility Page 10 Validating stack compatibility Page 11 Meeting requirements for performance scalability and resilience Page 11 Security analysis testing and monitoring Page 11 Platform certification Behind the scenes Page 12 Providing enterprise quality support and service Page 12 Legal assurance Page 13 Professional docum...

Страница 3: ...are developed by a vibrant open source community with the testing certifica tion documentation training and support traditionally found only with mature commercial software prod ucts This whitepaper describes how a collection of technology developed by open source projects becomes a set of JBoss Enterprise Middleware products This productization process incorporating careful require ments analysis...

Страница 4: ...a single in house team open source software design is the product of many great minds collaborating across the globe The pace of innovation is limited only by the amount of time developers can spend More rational vendor relationships Providers of open source software typically earn revenue through support subscriptions renewed on an annual basis giving them an incentive to provide high quality sup...

Страница 5: ...s and test them as an integrated solution in order to meet their organization s middleware requirements Variable access to documentation training support and expertise Documentation completeness and accuracy availability of training and availability of technical support can vary enormously among open source projects As a result IT organizations cannot always be sure of getting the timesaving infor...

Страница 6: ...ssociated with typical open source projects by Aggregating open source components into well defined products eliminating much of the integration and testing burden of working with granular components and also simplifying software management Ensuring production level quality and stability through a broad and deep testing process reducing validation time for IT organizations and minimizing downtime ...

Страница 7: ...To eliminate for IT organizations much of the integration work testing work and risk traditionally associated with using open source software To provide customers with service level agreements appropriate for 7x24x365 production use Defining products and identifying software sources Any product planning process begins with customer and market requirements and a strategy to address them While JBoss...

Страница 8: ...fies the specific components and versions that will be assembled and tested to become the next release of the product The team then defines specific objec tives for the release balancing ambitious requirements with time and resource constraints Requirements include not only functional capabilities but also usability requirements platform certification perfor mance characteristics scalability requi...

Страница 9: ... team When the definition process is begun for the next major release of an Enterprise product the team begins again by examining the open source community projects enabling enterprise customers to benefit from the vibrant development process that has been advancing the state of the art Of course this new release then undergoes the same productization process to ensure enterprise level quality sta...

Страница 10: ...l Police Board Certifying platform and database compatibility For open source projects the nature and extent of platform testing depends heavily on the platforms avail able to developers and the time they want to devote to platform testing vs development of new features As a result most open source software is tested only on a single common platform But developers have long known that differences ...

Страница 11: ...us performance testing including Testing of specific components to identify and eliminate performance bottlenecks and ensure that the product meets established performance criteria Reliability tests of products under high transaction loads for extended periods of time 24 36 hours In the past the JBoss Application Server was frequently used by customers in a clustered environment but it may not hav...

Страница 12: ...JBoss org projects and JBoss Enterprise Middleware consider the JBoss Application Server This compo nent was typically released to the JBoss org commu nity after it passed two suites of tests one suite of unit tests and another suite of compatibility matrix tests While these test suites were substantial with close to 4 000 tests each they were run on a single JVM Sun 1 5 JVM and on a single platfo...

Страница 13: ... that represent valuable time saving resources for customers For each JBoss Enterprise Middleware product a team of professional technical writers ensures that de tailed installation guides configuration guides and product release notes are delivered with each product release To enable products to meet the requirements of a global customer base these materials are local ized for each product relea...

Страница 14: ... production use JBoss Enterprise Middleware Delivering the best of both worlds Our adoption of the JBoss Enterprise SOA Platform together with Red Hat support has been extremely successful because it has enabled us to take advantage of the best of both worlds by increasing the reliability of performance levels and by optimizing our IT systems Maurizio Quattrociocchi IT Telecoms Director National I...

Страница 15: ...ion Overall quality Functional testing and some compatibility testing Excellent incorporating a broad array of tests and much more Long term stability Varies by project component due to constant innovation More stable due to the nature of the productization process Cumulative patch releases address defects without introducing instability Load testing Limited Fully load tested Localization Depends ...

Страница 16: ...s Learn more at www jboss com About Red Hat Red Hat the world s leading open source solutions provider is headquartered in Raleigh NC with over 50 satellite offices spanning the globe CIOs have ranked Red Hat first for value in Enterprise Software for four consecutive years in the CIO Insight Magazine Vendor Value study Red Hat provides high quality affordable technology with its operating system ...

Отзывы: