Inside Apache Geronimo 1.1 - What makes it special?

1. Inside Apache Geronimo 1.1 - What makes it special? Rakesh Midha IBM Software Labs, Bangalore midharakesh@in.ibm.com midha.rakesh@gmail.com

2. Goal • Show case Geronimo open source story • Where it fits in Industry and Enterprise • How it facilitates easy development and deployment • Understand Geronimo 1.1 additions • Get you hooked with Geronimo

3. Agenda • Geronimo - An Introduction • Why Geronimo? • What makes it Special? • Where does it fit well? • Geronimo Architecture and Components • Geronimo 1.1 – Whats New? • Getting Started • Administration and Configuration • Development Enviornment • Quick Application Development • Getting Involved • Summary, Q&A

4. Geronimo - An Introduction

5. What is Apache Geronimo? Open source J2EE application server project developed by the Apache Software Foundation. Benefits from the efforts of collaborative development by an open community of Java developers worldwide. • Apache-licensed open source application server • Highly customizable • Small footprint • Community-driven Brings together leading technologies from the broad open source community to support J2EE

6. Apache Geronimo • Geronimo • Apache Geronimo an Apache Software Foundation top level project that is aimed at creating a world class, free, application server. • It is made up of over 30 best of breed open source packages (some not under the Apache domain). • The Geronimo kernel provides the common security, deployment, administration, management, and life-cycle services for these components. • Geronimo reached official J2EE 1.4 certification in Milestone 5 in Oct 2005.

7. Geronimo Open Source Packages • Howl • JDBM • JDom • Jetty • Juddi • Junit • Mx4j • OpenEJB • ActiveIO • ActiveMQ • Scout • Antlr • ASM • Axis • Castor • Concurrent • Apache Directory • TranQl • Wsdl4j • Xmlbeans • Xpp3 • Xstream • Xfire • Derby • Pluto • Slf4j • Oro • Servicemix • Spring • Stax • Tomcat • Regexp Commons • Beanutils • Collections • Digester • El • Fileupload • I/O • Lang • Modeler • Primitives

8. Geronimo History and Progress • Milestone 3 released • Geronimo passes J2EE Certification Test Suite • Apache Geronimo Project formed • V1.0 Released • V1.1 Released • V1.2 Released • IBM acquires Gluecode Software • Milestone 4 released • Milestone 5 released, full J2EE certification August2003 August2004 May2005 June2005 August2005 Oct2005 Jan2006 June2006 In Plan

9. Why Geronimo?

10. Geronimo – Key Features • J2EE 1.4 Certified • Certification from Sun Microsystems in October last year • Certified on the Sun JDK 1.4.2, works with JDK 1.5 without CORBA • Option for Jetty or Tomcat as a Web Container • Geronimo supports both Jetty as well as Tomcat. Separate package for download, available for Jetty and Tomcat. • Database Support • Comes with Apache Derby database • Also supports JDBC enabled databases using a connector framework from TranQL • Eclipse Web Tools Project support • Integrated development environment for creating, deploying, and debugging directly against Geronimo • Runtime customization • Advanced micro-kernel architecture enables runtime customization to save systems resources and improve performance • Allows for greater flexibility in creating different server personalities in the future

11. Geronimo – Key Features • Centralized configuration and control • Easy to use Web Console • Small Footprint ~60MB • Easy access - downloadable in minutes • Easily embeddable in customer or ISV stack • Liberal product license • Apache open source (ASF) license • Flexible and rapid deployment across multiple configurations • Directory-based hot deployment • Local and remote deployment through command line, console, and IDE • Improved reliability for most commonly deployed applications • Web-tier clustering

12. What makes it Special?

13. Geronimo – Key Design Principles Simple • Easiest platform to development on, obtain, use, and service. • Easy to understand, invisible to the customer. Application centric. • Easy to configure and change. • Embedded documentation, service functions, user interfaces, etc. • Default setting will get you running. Flexible • Can plug-in function while that application server is running. • J2EE function is just one of the personalities that can be plugged in. • Geronimo becomes the platform that partners/customers think when building apps. • Need to be the Eclipse of the tooling world. Reliable • ‘Appliance like’ reliability. Never fails. • Startup and recycle time should be minimal. • Customer never sees or cares about the server… it is about the application. • It is the ‘intel chip’ for your applications. • Administration is available and easy. • ‘Tomcat like’ reputation in open source.

14. Geronimo – Technical Advantage • Enchilada of best of breed open source products • GBean Architecture • A pluggable framework • Modular Architecture • Tomcat has web features but it lacks other J2EE features • Low memory and resource requirement • Better web performance as compared to other open source application servers • True open source community driven • Strategic commitment from IBM, Covalent, Chariot and other big players • Very Active community and dev/user list • Optional Support from IBM

15. Geronimo – Still Why? • It’s all Free!!! • Free Application Server • Free Development, Debugging environment • Free Management tools • Free resources like database, messaging • Free enterprise class documentation • Free Sample applications • Free educational material like articles, tutorials

16. Where does it fit well?

17. Where does this fit in the Enterprise? • Apache Geronimo are excellent positioned as developer runtimes • Integration into Eclipse helps to reduce software licenses • Small footprint • Single User Environments • Low end SMB companies • Quick, frictionless access to application server technology with no up-front costs • Departmental Applications in Enterprises • SMBs and departmental applications are a good target for this technology • Not quite ready to run your 4,000 AppServer farm • Advanced monitoring, integration with commercial / open source monitors not quite there yet.

18. Your Killer App Apache Tomcat Today – With Tomcat plus ‘other stuff’ you do yourself • Your developers have a job to do – write your killer app! • They chose Apache Tomcat because it helps them build apps quickly • But Tomcat doesn’t have web services support, a security framework, or messaging; so your developers added those components and integrated them into the stack • Then your rock star developer wrote some app-specific service and integrated that into the stack • Turns out your app needs clustering too, so they throw that into the stack • …but the web services component they got doesn’t do clustering; luckily there’s a newer version of that out now, so they get the new version and integrate THAT into the stack • Now your staff is maintaining your killer app, Apache Tomcat, the web services component, messaging, security, clustering, AND your custom components build apps quickly…? What happened to building apps quickly?? Developers maintain all this! JMS Messaging Other services you need/write SOAP/Web Services (Axis) Security / Authentication SOAP/Web Services (Axis) Web Tier Clustering Custom Integration Custom Integration

19. Apache Tomcat Security / Authentication SOAP/Web Services (Axis) Geronimo Plug-In Kernel Fully Integrated & ExtensibleKernel Services Your Killer App Web Tier Clustering JMS Messaging Other Optional Plug-ins for EJBs, Transactions, etc. Now, just much easier (oh, and future-proof)! • What if you could start with Tomcat • Extend Tomcat with pre-integrated features & services you need most (read: someone other than you did the tedious work) • Welcome to a little secret we like to call Tomcat+, use Apache Geronimo • It’s fully extensible, and it’s built on the innovative open-source Apache Geronimo kernel • Plus all the same Apache Tomcat you’re already using • Plus the leading components you want to use pre-integrated and tested (and the ability to turn off what you aren’t using) • Plus the support you need from IBM Apache Geronimo

20. Geronimo Architecture and Components

21. Geronimo Architecture - GBean • The Geronimo framework provides a set of cooperating classes, called GBeans, for combining an arbitrary set of components into a system • Everything in Geronimo framework is GBean • Lightweight kernel provides central integration based on Inversion of control pattern. • Manageable at runtime using JMX, JSR-77 • Example: • An EJB container • Web Module • It must be aware of every EJB in the system. • It registers a dependency on any EJB GBean • An EJBs are added to the system • The Geronimo kernel recognizes the relationship and injects information from the EJB GBean into the EJB container GBean where it updates its configuration state. • This action is called dependency injection. • A J2EE web module that contains servlets and uses EJB • It depends on the web container and the EJB container • When its GBean is started, the Geronimo kernel recognizes the dependency and starts the web container and the EJB container first

22. Geronimo Kernel • Kernel • Core of the component model • Provides central integration point • Binds all the subsystems • Based on Inversion of Control /Injection Pattern • Geronimo Beans • GBean is a manageable unit in the Geronimo framework • To add new component to the server, you deploy the collection of GBeans • A deployment plan is an XML document that provides server specific attribute values • GBeans can hold states and can define relationships amongst them • GBean life cycle is managed by the kernel. • A java class can be wrapped to become a GBean • GBeans are used to tie all the open source projects in Geronimo ( Derby, Tomcat, Axis, OPenEJB …. ) • GBean can notify events.

23. Geronimo components

24. Geronimo components - cont

25. Deployment Framework • Each Component has a GBean and deployment plan. • Plan is an xml file containing properties of GBean • Server is built using j2ee-server-plan.xml <gbean name="JettyWebConnector" class="org.apache.geronimo.jetty.connector.HTTPConnector"> <attribute name="host">localhost"</attribute> <attribute name="port">8080</attribute> <reference name="JettyContainer"><name>WebContainer</name></reference> <attribute name="maxThreads">50</attribute> <attribute name="minThreads">10</attribute> </gbean> • Can also deploy plan to running server using deployer • For modules you need specific file as deployment plan • Web Application (WAR) - WEB-INF/geronimo-web.xml • Enterprise Application (EAR) META-INF/geronimo-application.xml • Enterprise Java Beans (JAR) META-INF/openejb-jar.xml • J2EE Connectors (RA) META-INF/geronimo-ra.xml • Client Application META-INF/geronimo-application-client.xml

26. Geronimo 1.1 – Whats New?

27. Geronimo 1.1 • Updated deployment plan • Running with JDK 1.5 without CORBA support • Improved scalability, portability and overall organization • Enhanced Web Console • Memory utilization graphics, Live console graph • Thread Pools statistics • Remote HTTPd configuration wizard and plugins • JMS resource wizard • Keystore manger • Improved Hot deployment • Application storage in repository • Enhanced SMTP support • Little-G • Plugin architecture • In-place deployment

28. Geronimo 1.1-Little-G • Lightweight distribution of geronimo available for both jetty and tomcat • Small space requirement ~20MB and smaller memory footprint • It includes a WebContainer, Transaction Manager and some other essential elements of Geronimo. • Not J2EE compliant • Can be upgraged for specific requirement like JMS, J2EE etc using plugins.

29. Geronimo 1.1-Plugins • A Geronimo plugin is a new packaging mechnism for geronimo modules • Geronimo applications, server features, and integrated products can be distributed as Geronimo plugins. • Plugins are easy to install, automatically download any dependencies, and do not require server restarts. • Using the plugin infrastructure, applications or modules can be copied from one Geronimo installation to another • Developer to Developer • Development environment to production environment • Plugin stays in Maven 2 repository and automatically downloads dependencies from other repositories • Web console can be used to create plugins

30. Plugin web console

31. Getting Started

32. Quick Start • Available for download from http://geronimo.apache.org/downloads.html • Linux, windows and MacOS installation in tar/zip format with jetty and tomcat available • System Requirements • Redhat Enterprise Linux 3.0 or 4.0, Suse Linux Enterprise .9 • Microsoft XP with SP2 • 120MB Disk Space • 128MB RAM (256MB Preferred, depends upon deployed Applications) • Installation • Windows • Install JDK, set JAVA_HOME and simply unpack geronimo-*-j2ee-1.1.zip • Linux • Install JDK, export JAVA_HOME and simply unpack geronimo-*-j2ee-1.1.tar.gz

33. Server Administration • Starting a Server • From application launcher, execute startup.bat or startup.sh, or run java – jar bin\server.jar • The server will display the TCP/IP ports where it is listening for requests • You can confirm readiness of server by navigating to welcome page http://localhost:8080/console and https://localhost:8080/console in browser • When Prompted enter System/Manager as userid/password • Startup options : -quite, -v, -vv • Stopping a Server • From Application Launcher, Execute shutdown.bat or shutdown.sh, or run java –jar shutdown.jar • Stop server using Web Console • Press Ctrl-C at the Server Started window

34. Tools and Commands • Deploy command - deploy.bat and deploy.sh • java -jar deployer.jar [general_options] <command> [command_options] • deploy [general_options] <command> [command_options] • Commands available • 1. Common Commands • deploy • redeploy • start • stop • undeploy • 2. Other Commands • distribute • list-modules • list-targets • 3. Configuration jar • install-plugin • search-plugin • General options • --uri --host --port --driver --user • --password --syserr --verbose --offline

35. Administration and Configuration

36. Web Console • The administration console provides a convenient, user friendly way to administer many aspects of the Geronimo Server. • Can be viewed in a browser at http://localhost:8080/console • Default password is system/manager • It can be used for server management, and viewing/editing following information: • Server/JVM usage statistics • Server logs • Control server functionalities • Web Server configuration • Database, JMS Resource configurations • Thread pool, database pool, J2EE connectors management • Apache HTTP, Derby maintenance • Application/ Modules/ Plugin management • Security realms management

37. Web Console view

38. Deploying JDBC and JMS resources • Database Pool is deployed as a connector in Geronimo • Database Connection pool can be configured at the server level, application level or part of single application module, as default • Configuring Database pool • Create Database Pool deployment plan containing configId, parentId, dependency, uri, connectionfactory-interface, name and configurable properties like Driver, user, passwd etc • Deploy pool as connector • Server wide java -jar bin/deployer.jar deploy database-pool.xml \ repository/tranql/rars/tranql-connector-1.0.rar • Application Scoped Create application.xml with Create geronimo-application.xml jar -tf my-app.ear my-web-app.war my-ejbs.jar tranql-connector-1.1.rar database-pool.xml META-INF/application.xml META-INF/geronimo-application.xml • Client Module Scoped A module scoped connection pool is declared in the geronimo deployment plan for the module

39. Deploying JDBC and JMS resources - Cont • JDBC Resources • In Modules Deployment descriptor ie web.xml Add resource ref <resource-ref> <res-ref-name>jdbc/DataSource</res-ref-name> <res-type>javax.sql.DataSource</res-type> <res-auth>Container</res-auth> <res-sharing-scope>Shareable</res-sharing-scope> </resource-ref> • For external references deployment plan is required with following info: <naming:resource-ref> <naming:ref-name>jdbc/DataSource</naming:ref-name> <naming:resource-link>SystemDatasource</naming:resource-link> </naming:resource-ref> • In Application code lookup datasource and use it. InitialContext ctx = new InitialContext(); DataSource ds = ctx.lookup("java:comp/env/jdbc/DataSource"); Connection con = ds.getConnection(); • JMS Resources • The default Geronimo server starts with ActiveMQ as messaging server • JMS Server must be running and its GBean is created and deployed • JMS application resources like connection factories, topics, and queues are deployed using J2EE connector, which can be used like JDBC resource.

40. Geronimo Classloader Bootstrap, Extensions – JVM Classes System – Geronimo System Server – Critical classes and services for J2EE EAR – EAR Classloader Dependency loaded as part of EAR Classloader.

41. Troubleshooting Logging • Administration Console provide 4 portlets for configuration and viewing the server’s log • Log Manager to specify log configuration file, Log Level, file size and Refresh Period • Server Log Viewer to view server log and set filters for refining results displayed • Derby Log Viewer to view Derby server logs • Web Access Log Viewer to view web server logs for both tomcat and jetty • Detailed log4j configuration settings can be done directly in server-log4j.properties, deployer-log4j.properties and client-log4j.properties file

42. Security Security • In Geronimo you can define and activate multiple security realms build around JAAS • Each realm can authenticate user, provide set of principles to authorize user • Each realm is a deployed as a component via GBean • Default plan in doc/plan/j2ee-security-plan.xml • In order to enable https access to web applications, Geronimo requires keystore.

43. Development Enviornment

44. Development Environment • Development Tools • Eclipse plug-in for creating, deploying, and debugging Geronimo applications • Plug-in provides integration between Eclipse Web Tools Platform and Geronimo • Eclipse Web Tools Platform (WTP) project extends the Eclipse platform with tools for developing J2EE Web applications • http://www.eclipse.org/webtools/ • Plugin available for download from geronimo website • Integrated test environment • Eclipse plug-in provides integrated test environment for Geronimo

45. Development Environment views

46. Quick Application Development

47. Quick first web application • Create HelloWorld.jsp • Create a plain text file in the <app_home> directory named HelloWorld.jap and copy the content • Create Standard J2EE complaint deployment descriptor web.xml in <app_home>/WEB-INF directory <%@ page contentType="text/html;charset=UTF-8" language="java" %> <html> <head> <jsp:useBean id="datetime" class="java.util.Date" /> <title>Hello IBM Geronimo Version 1.1</title> </head> <body> <h2>Welcome to Geronimo Version 1.1</h2> <p>Congratulations on running this simple application on ${datetime}.</p> </body> </html> <web-app version=“1.0" xmlns="http://java.sun.com/xml/ns/j2ee"> <welcome-file-list> <welcome-file>HelloWorld.jsp</welcome-file> </welcome-file-list> </web-app>

48. Quick first web application– cont. • Create Geronimo plan • Although this sample application does not require it, you can still create Geronimo deployment plan to get first view. • Create geronimo-web.xml in WEB-INF directory • Package the application • From command prompt, go to <app_home> directory and execute jar –cvf HelloWorld.war * • Deploy the application • You can use Geronimo web console to deploy and run application • From command line your can use the deployer.jar to deploy application using java -jar bin\deployer. jar --user system --password manager deploy sample\HelloWorld.war • Test the application • Test the application by pointing a Web browser to the following URL: http://localhost:8080/hello <?xml version="1.0"?> <web-app xmlns="http://geronimo.apache.org/xml/ns/web" xmlns:naming="http://geronimo.apache.org/xml/ns/naming" configId="HelloWorld"> <context-root>/hello</context-root> </web-app>

49. Getting Involved

50. What more? Geronimo 1.2 • The next version of Geronimo is focused on several areas, including: • Enhance the performance and usability of the server. • Improve cross-platform compatibility. • Improve integration with third-party development tools and server products. • Enhance configuration, administration and management tools. • Improve clustering support for web containers and EJBs. • J2EE 1.5 – EJB 3, Web 2.5 • Portal Server plugin