JOnAS 5.1 Application Server Profiles

JOnAS 5.1 Application Server Profiles Guillaume Sauthier / François Fornaciari

Summary
Introduction
Profiles
Using µJOnAS for profiles
What about dynamic profiles ?
Updating profiles
Conclusion

Introduction

Introduction
Time of big & fat application servers is now over !

Introduction / JOnAS
OW2 JOnAS application server based on OSGi TM
Highly dynamic and adaptable platform
Bridge toward OSGi world (M2M, home automation, RFID based applications, ...)
Version 5.1 Java EE 5 certified
EasyBeans, EclipseLink, Tomcat, CXF
Clustering support (using CMI)
Easy to use administration console
Global management tool: JASMINe
Cluster design, deployment and monitoring

Introduction / M2M [1/2]
Machine to Machine communications
From edge computing ...
Close to caption probes, RFID, ambient computing
… going through premises ...
Relaying informations
… to big central servers
Centralized Information processing
Monitoring, dashboards, ...
Application servers in the M2M World

Introduction / M2M [2/2]
All of them powered by JOnAS/OSGi !
Profiled depending on resources/applications
Normalize technologies in use and infrastructure management

Profiles

Profiles / Java EE 6
Profiles as a way to introduce agility inside application servers for the benefits of users
Break the monolithic image of application servers
Full Profile
All Java EE related specifications (Servlet 3.0, EJB 3.1, JCA, …)
Old school :)
Web Profile
Smaller profile including only a subset of all the specifications (Servlet 3.0, EJB 3.1 lite, …)
Targets web application's “most required” features (presentation layer, local business, simple persistence, transaction and web services)

Profiles / JOnAS
What means a JOnAS profile ?
An “implementation” of a Java EE profile (first step)
Towards custom made profiles
An assembly of bundles and resources composing a runnable application server (a zip)
This set of resources defines the feature level of the server
Represents a set of JOnAS technical services
Based on a micro JOnAS profile
Aka platform, kernel, nucleus, …
Running an OSGi platform with a minimal set of services
Providing extensibility
Allowing technical services composition (server linkage)

Using µJOnAS for Profiles

µJOnAS
Ultra light JOnAS (< 9 Mo but going lighter)
Quick to start (~3 seconds)
Manageable (JMX, RMI Connector)
Adaptable to constrained environments (set top box, PDA, …)
Includes an automated bundle builder
Convert a jar file to a bundle automatically
Just drop a jar in lib/ext/
Helps for faster OSGi adoption from Java EE users
Provides an extensible deployment system

µJOnAS / In practice
A kernel
Including Apache Felix
Providing the OSGi platform
and Apache Felix iPOJO
Providing the service component model (ease service development)
A minimal set of JOnAS components
Management through JMX RMI entry point
Start / Stop easily the underlying OSGi platform
Deployment system
Fundamental block for profile and management (deploy / undeploy)

µJOnAS / Build a profile
At first you need the micro JOnAS
Then augment it using the deployment plans you want
The profile's assembly is completely open and flexible
Additional profiles can be foreseen
User's can define their own profiles
Examples of web profiles
Micro + Tomcat + CXF + EasyBeans + EclipseLink
Micro + Jetty + Axis2 + EasyBeans + Hibernate
...
Currently only full and micro profiles are ready for JOnAS 5.1 Web profile is on the way !

µJOnAS / Deployment
Extensible Deployer System (Java EE archives, bundles, XML files, …)
Based on URLs (local and remote archives are deployables)
Extensible repository support (file, maven2, obr, ...)
Hot deploy
Fast development cycle
Ease cluster deployment
Exploded archive support
Deployment System
Deployment Repository

µJOnAS / Deployment / Plan
A description of a set of resources to be deployed on a server
XML file containing a list of resources with their location
Resources being Java EE archive, OSGi bundles, ...
A deployment plan can itself be considered as a resource
Ordered
Atomic (as an option)
Deployment Plan
< deployment-plan xmlns = "http://jonas.ow2.org/ns/deployment-plan/1.0" xmlns:m2 = "http://jonas.ow2.org/ns/deployment-plan/maven2/1.0" atomic = "false" > < deployment id = "org.ow2.easybeans.osgi:easybeans-core-for-jonas-eclipselink:jar" xsi:type = "m2:maven2-deploymentType" start = "true" reference = "true" startlevel = "1" > < m2:gr oupId > org.ow2.easybeans.osgi </ m2:groupId > < m2:artifactId > easybeans-core-for-jonas-eclipselink </ m2:artifac tId > < m2:version > 1.1.0-RC2_JONAS </ m2:version > </ deployment > </ deployment-plan >

µJOnAS / Deployment / Plan
Describe where the resources can be found
The resources can be obtained from local directories
Local Maven2 repository
Any file system location where archives can be found
Or from remote locations
Maven2 repositories
OBR (OSGi Bundle Repository)
HTTP server
Repositories
< repositories xmlns = "http://jonas.ow2.org/ns/deployment-plan/repositories/1.0" > < repository id = "maven2-bull" > < type > maven2 </ type > < url > http://repository.bull.net/maven2 </ url > </ repository > < repository id = "url-local-repository" > < type > url </ type > < url > file:///home/sauthieg/repository </ url > </ repository > </ repositories >

What about dynamic profiles ?

Dynamic profiles
This is the platform ability to change the current profile dynamically
From the needs of deployed applications
From an administrative operation
Add / start / stop JOnAS services on demand
No JVM reboot operation
Augment profile's perimeter (more featured)
Only add required services
Optimize memory
Even disk space if bundles are deleted (not ready)

Dynamic profiles / Application Reqs
Special MANIFEST entry
JOnAS-Require-Service <values>
Reference to deployment plan's name
Profile will be update at application deployment
Current profile composition compared to required services
Installation of extra services
“Construct” a new profile adapted to the need of an application
Only required services are part of the profile at execution

Updating profiles

Updating profiles (on going work)
Update center
Help tool for service update operations
Visualize service's available versions and ability to switch from one to another
Update is performed through OSGi modularity layer
Hot update
At next reboot
Plan update given the deployed applications or active sessions

Updating profiles (still on going work)
Process
Cluster topology initialisation
Target server selection
Target services to update
Monitor operations progress
Features
Rollback/Resume mechanism
Log operations
Planification
update

Conclusion

Conclusion
Profiles are now a reality in application servers
Monolithic application server EoL
“A la carte” application servers
Resource optimization
Quick, lightweight and extensible

Resources http://java.sun.com/javaee/technologies/javaee6.jsp http://felix.apache.org/site/apache-felix-ipojo.html http://www.osami-commons.org http://felix.apache.org http://jonas.ow2.org

JOnAS 5.1 Application Server Profiles

by Guillaume Sauthier on Jun 22, 2009

Accessibility

Categories

Upload Details

Usage Rights

1 Embed 5

Statistics

JOnAS 5.1 Application Server Profiles — Presentation Transcript