OpenJMS Presentation March 2000 © Copyright Exolab 2000

Overview Architecture Design Build Environment Release Schedule Resources © Copyright Exolab 2000http://openjms.exolab.org Contents

© Copyright Exolab 2000http://openjms.exolab.org Overview Open Source Implementation of JMS v1.0.2, Nov Support point-to-point and publish-subscribe models Support persistent and non-persistent message delivery Part of the Intalio platform Architecture completed in February and the development started in March.

© Copyright Exolab 2000http://openjms.exolab.org Architecture JMSClient Library Object Request Broker JNDI Client Library JMS Server Library JMS Server JNDI Server Library JNDI Server adaptive to facilitate loose coupling and product evolution can be deployed as a standalone service or embedded into another component

© Copyright Exolab 2000http://openjms.exolab.org Architecture (cont.) Adaptable Performance Scalable Deployment Architectural Influences

© Copyright Exolab 2000http://openjms.exolab.org Architecture (cont.) PersistenceServiceThreadPoolingLoggingLeasingMessagingConfigurationSessionDatabaseMonitoringConnectionAdministration JMS Server Library Layered architecture has promotes code reuse Messaging component is responsible for routing messages and managing the difference levels of service. Configuration component provides an access path to all JMS configuration entities Session component manages the lifecycle of all consumers and publishers. Connection component manages all JMS connection. Administration and Monitoring components

© Copyright Exolab 2000http://openjms.exolab.org Architecture (cont.) ConfigurationSessionDatabase Connection Persistence, Service and Logging as discussed previously. Collection core service is used to manage the JNDI hierarchical namespace. Configuration component abstracts the actual configuration file format and provides an access path to the configuration items Session provides transactions and isolation. Single threaded entities Connection is a server side representation of a client connection to the JNDI server. Database component abstract the persistence mechanism (JDBC, file-based etc) PersistenceServiceLoggingCollection JNDI Server Library

© Copyright Exolab 2000http://openjms.exolab.org Architecture (cont.) RMICORBAOTHER JMS Object Request Broker ORB specifics are managed through the configuration file Each ORB employs different discovery and communication mechanisms Alpha1 release will only support RMI Alpha2 release will also include support for our own lightweight ORB. Further release may support CORBA

© Copyright Exolab 2000http://openjms.exolab.org Architecture (cont.) JDBCOODBMSRecMan Persistence Adaptor Persistence mechanism specified in configuration file Can plug in different database including JDBC and OODBMS Client code is independent of the persistence mechanism Alpha1 release will only support RecMan developed by Cees de Groot Alpha2 release will support JDBC

© Copyright Exolab 2000http://openjms.exolab.org Architecture (cont.) CastorConfigJavaConifgOther Configuration Adaptor Configuration mechanism specified in configuration file CastorConfig adaptor supports XML-based configuration files generated through the Castor configuration file generator JavaConfig adaptor to support standard Java property files Alpha 1 release supports both adaptor types.

© Copyright Exolab 2000http://openjms.exolab.org Design Message Manager

© Copyright Exolab 2000http://openjms.exolab.org Design Consumer Manager

© Copyright Exolab 2000http://openjms.exolab.org Design Destination Manager

© Copyright Exolab 2000http://openjms.exolab.org Design JNDI Server

© Copyright Exolab 2000http://openjms.exolab.org Design Persistence Framework

© Copyright Exolab 2000http://openjms.exolab.org Schedule Alpha 1 : Feature Release Point-to-point and publish-and-subscribe messaging domains Persistent and non-persistent delivery modes Transacted sessions Five message objects MapMessage, ObjectMessage, StreamMessage, ByteMessage and TextMessage Durable destinations and consumers Embeddable and standalone server configuration Basic admin client to setup administered objects and to do some primitive monitoring Synchronous and asynchronous message delivery

© Copyright Exolab 2000http://openjms.exolab.org Schedule (cont.) Alpha 1 : Feature Release Example client code for using most aspects of the service Out of the box standalone JMS server JNDI access to all administered objects Due end of April

© Copyright Exolab 2000http://openjms.exolab.org Schedule (cont.) Alpha 2 : Performance Release Lightweight ORB with more efficient use of serialization Message Selection as specified in JMS Web based administration Some form of security Better administration and monitoring Due mid to end July

© Copyright Exolab 2000http://openjms.exolab.org Schedule (cont.) Alpha 3 : Scalability Release Peer to peer communication protocol between JMS servers Java 2 Security Platform (policy files) Better stability Due end of August

© Copyright Exolab 2000http://openjms.exolab.org Build Environment Ant - a Java based build tool pure Java (part of the Apache Jakarta Project) more portable between platforms extensible JTF - a framework for writing test harness hierarchical namespace facilitates grouping Nightly build, smoketest and package test harness will flag problems early

© Copyright Exolab 2000http://openjms.exolab.org Resources Web Site Mailing List openjms-devdevelopers’ mailing list CVS cvs -d login cvs -d checkout openjms

Q&A © Copyright Exolab 2000