Date: Mon 27 Jun 2005 — Thu 30 Jun 2005,
Type: All Day Event
My colleageue Shreyas Kamat and I will be presenting a session at the 10th JavaOne (2005) in the BOF (Birds of a Feather) category. The details of the session should be available at the JavaOne site in a few weeks. Here is the abstract:
BOF-9042: Who Moved My J2EE Platform? How to Successfully Migrate Between Application Servers
SUMMARY
This session will provide guidelines, best practices, and a methodology to tackle a problem that is sapping the budgets of enterprise which have invested heavily in J2EE technology - the migration of enterprise applications. The migration areas addressed will include migration due to app server version upgrades, migration different J2EE application servers, and migration between hardware platforms/operating systems. The migrations have at least one driver in common – the dependency of the application on the consequent application server (including WebSphere, WebLogic, Oracle AS, SunOne, and JBoss).
TARGET AUDIENCE
The session will benefit senior developers, technical architects, team leads, IT managers, and others interested in learning about how to achieve a successful large scale migration for J2EE-based applications. After attending this session, you will be able to address the challenges of J2EE app server migration with confidence and with a structured approach.
PREREQUISITES
It is assumed that the audience is familiar with the capabilities provided by major J2EE app servers in the market, J2EE concepts including JSPs, Servlets, EJBs, messaging, etc., and enterprise Java development and deployment.
ABSTRACT
Though the Java platform does, to a large extent, live up to the promise of WORA (Write Once Run Anywhere), the effort to take an application out of a stable operational environment into new, untested territory is not trivial. The strategy and planning for such initiatives is very complex and requires planning in advance. Enterprise applications, once deployed, have a multitude of dependencies, besides the dependency on Java APIs. The drivers for migration can include version upgrades, corporate agenda, maintenance costs, industry alliances, rapid upgrades to the J2EE platform APIs, etc. A planned migration ensures a successful implementation while minimizing the impact.
In this session, we will describe a strategy to address the migration related to some of the major application servers, including IBM WebSphere, BEA WebLogic, Oracle Application Server, Sun One, and JBoss. Real world examples of how this strategy has been applied in the industry will be provided. Frameworks for planning and executing the migration, including effort and time estimation will be presented. A detailed case study will be covered to illustrate to the audience how the best practices and frameworks presented in this session have been applied for successful migration planning and execution.
OUTLINE
The outline of the session is as under. Please assume 2-3 PowerPoint slides for each bullet:
• Drivers behind migration
- Business and Technical Drivers
- Evolution of the J2EE App server market
• Popular types of J2EE based migration
- App server upgrades
- Cross-app server migration
- Migration between hardware/OS platforms
• Challenges of J2EE-based migration for large scale enterprise application portfolios
• Migration methodology: How to successfully undertake a large scale J2EE app server migration
- Migration Scoping: Plain vanilla migration vs. full blown migration
- Migration framework
- Migration strategy and roadmap
- Project planning
• Migration tools and IDEs
- How to leverage Integrated Development Environments for migration
- Automated tools to aid application migration
• J2EE platform and API focus for migration
- JDK upgrade
- Servlets and JSPs
- EJBs
- JDBC and other data sources
- Messaging
- Extension APIs
- Etc.
• Migration services
- Vendors providing migration services
- How to structure the team for app server migration
• Best practices for J2EE migration
• Planning example of one type of migration
• Case Studies
