Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

JBoss @ Slovakia, UNIZA & TUKE Universities November 2013

  • Login to see the comments

JBoss @ Slovakia, UNIZA & TUKE Universities November 2013

  1. 1. 7th November 2013 Red Hat & JBoss @ Universities UNIZA & TUKE JBoss Community x Enterprise Václav Tunka Software engineer JBoss Enterprise Platforms
  2. 2. What is JBoss?
  3. 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. 4. JBoss AS has a new name!
  5. 5. Runtime for back-end applications.
  6. 6. Programmers can concentrate on customer logic.
  7. 7. Transactions
  8. 8. Messaging
  9. 9. Load balancing
  10. 10. Persistence
  11. 11. Clustering
  12. 12. Caching
  13. 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. 14. Let's talk about community projects first
  15. 15. Packaging and component integration is the key
  16. 16. 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
  17. 17. 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.
  18. 18. Productization: Fedora x JBoss.org
  19. 19. 1) Legal, 2) branding, 3) usability, 4) security, 5) support, 6) packaging. Fedora is productized already
  20. 20. 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.
  21. 21. 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).
  22. 22. 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.
  23. 23. Productizing JBoss EAP
  24. 24. JBoss EAP productization 1) Legal, 2) branding, 3) usability, 4) security, 5) supportability, 6) packaging.
  25. 25. 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.
  26. 26. Lots of dependencies ● JBoss AS has ~200 direct dependencies. ● All build and test dependencies for all components? ● Greater than 1000.
  27. 27. Quick summary Community projects vs. Enterprise products What is productization? Why is it important?
  28. 28. 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
  29. 29. Additional references ● Geocaching CC image ● JBoss.org design & slide decks
  30. 30. 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
  31. 31. TITLE SLIDE: HEADLINE Presenter Thanks for listening! name Title, Red Hat Date

×