1. 7th November 2013
Red Hat & JBoss @ Universities
UNIZA & TUKE
JBoss Community x Enterprise
Václav Tunka
Software engineer
JBoss Enterprise Platforms

2. What is JBoss?

3. What is JBoss Application Server?
●
Open Source Java EE server.
●
Found by Marc Fleury in 1999.
●
The name came from Enterprise Java Beans (EJB) ->
EJBoss.

4. JBoss AS has a new name!

5. Runtime for back-end applications.

6. Programmers can concentrate
on customer logic.

7. Transactions

8. Messaging

9. Load balancing

10. Persistence

11. Clustering

12. Caching

13. Java EE standards – to sum up
●
Web Server (HTTP, HTTPS).
●
Web container (JSP, JSF, Servlets, ...).
●
Enterprise Java Beans (EJB).
●
Persistence API (JPA).
●
Transactions API (JTA).
●
Web Services (JAX-WS).
●
Messaging (JMS).
●
Management (JMX).
●
Security (JAAS).

14. Let's talk about community projects first

26. Packaging and component integration is the key

27. What is productization?
●
●
●
Productization is a systematic effort to create a
supported and tested product version out of JBoss and
thirdparty opensource projects.
Cooperative effort with help of many other departments
Productization department is ultimately responsible for
the products

28. Why productize?
●
Meet software license requirements.
●
Provide consistent branding message.
●
Improve User Experience (UX).
●
Deliver secure applications.
●
Enable effective product support.
●
Improve packaging / installation / maintenance.

29. Productization: Fedora x JBoss.org

30. 1) Legal,
2) branding,
3) usability,
4) security,
5) support,
6) packaging.
Fedora is productized already

31. The JBoss Community is not productized
●
Focused on R&D.
●
Legal requirements are not always checked.
●
Over 70 JBoss.org projects.
●
Different brands.
●
Many different communities.

32. JBoss Community builds
●
Different project sites (JBoss.org, github, etc).
●
Different SCMs (svn, git, etc).
●
Different build tools (Ant, Maven, Gradle).
●
Thirdparty projects (Apache, Codehaus, Sun/Oracle).

33. Fedora vs. JBoss Community
●
●
Fedora takes community projects and packages them
into a coherent system.
The JBoss Community focuses on delivering a variety
of (very) loosely related projects.

34. Productizing JBoss EAP

36. JBoss EAP productization
1) Legal,
2) branding,
3) usability,
4) security,
5) supportability,
6) packaging.

37. Challenges
●
Java/Maven vs. RPM.
●
Rebuilding Takes Time:
●
●
understand the build,
●
find the dependencies,
●
build,
●
●
Locate the source,
add Bugs! :)
Delay between upstream changes and product
release.

38. Lots of dependencies
●
JBoss AS has ~200 direct dependencies.
●
All build and test dependencies for all components?
●
Greater than 1000.

40. Quick summary
Community projects vs. Enterprise products
What is productization?
Why is it important?

41. References
●
●
Dimitris Andreadis – JBoss.org x Jboss.com
http://www.slideshare.net/dandreadis/jbossorgjbossco
m
Backbone image CC
●
Craftman image CC
●
ATM image CC
●
Message image CC
●
Dogs images CC
●
Clock image CC
●
Grapes image CC

42. Additional references
●
Geocaching CC image
●
JBoss.org design & slide decks

43. 7th November 2013
Links: SLIDE: HEADLINE
TITLE
RedJBoss.org/jdf Universities
Hat & JBoss @
Visit
Presenter
UNIZA & TUKE
name
Title, Red Hat
JBoss Community x Enterprise
Date
Contact
Václav Tunka
Software engineer
JBoss Enterprise Platforms
@vtunka on twitter
vtunka@redhat.com

44. TITLE SLIDE: HEADLINE
Presenter
Thanks for listening!
name
Title, Red Hat
Date