Enterprise Rearchitecture Denver BEA User's Group May 2005

Soaring Eagle L.L.C. Copyright 2005

Enterprise Revolution

Denver BEA User’s GroupMay 3rd, 2005

Scott Ryan


Agenda

• Setting the Stage• Vision and Goals• The Journey• Where are we headed now• Conclusions


Setting the Stage

Where we were coming from


Environment

• High Technology Web facing Enterprise• 50% Java Technologies/40 applications• Some processes implemented using Ant• Full use of J2EE• MVC web applications using Traffic Cop• Minimal requirements process and insane

deadlines


Environment

• Entrenched BEA 6.1 Shop• Some senior developers and many junior

developers• Textpad was the editor of choice• Oracle 8 in use• PVCS and Tracker• Windows Development/Unix Production


Environment

• Development, SCM and Test Groups• Dev, Test and Production environments• Approx 2-4 hours to build and deploy• No indication of problems until build

completed• Non repeatable processes and no release

management.


Architecture


Vision and Goals

Why do all the work


Vision

• One Button Deployment


Goals

• Repeatable Processes• Separation of Business Logic• Position for Web Services• Raise Productivity• Enable Junior Developers• Capture Knowledge


The Journey

How did we proceed and what tools did we use


Enablement

• Increase Communication• Define overall architecture• Define and Demonstrate the Value• Automate repeatable processes• Move in small steps (minimize tools)• Get buyoff from supporting groups• Lead with focus group


Increase Communication

• Install wiki (moinmoin)• Weekly tools classes• Weekly code reviews• Install and use JIRA• Lead by example


Wiki

• Install Wiki• Force all communication through the wiki• Share the knowledge outside the group• Keep adding value to the wiki• Seed the wiki to show people the way


Architecture


Architecture Toolset

• Weblogic 8.1• Struts/JSTL• J2EE/EJB Entity and Session• Xdoclet• Ant/Maven• Workshop/Eclipse• Jira


Maven

• Built Weblogic and XML beans Plugins• Leveraged plugins and modified where

needed• Automated Documentation• Used as many tools as possible• Developed single commands for users• Everything is done with Maven


Eclipse

• Standardized bundle• Moved from MyEclipse to WTP• Leveraged multiple plugins• Integrated with Maven and Subversion• Try to make it the one stop shop for all

development• Not required for non development

processes


Define and Demonstrate Value

• Developers are hard to change• Management was extremely supportive• Use real measurements not feelings• Not everyone will support change• Find key change agents• Productivity is the key• We can’t change the business


Automation

• Xdoclet• Ant/Maven build processes• Took over labeling of releases• Eclipse automation• Automated documentation• Jira helps coordinate teams


Small Steps

• Set the vision and keep reinforcing that vision

• Change tools and processes in sync• Validate the benefits are realized before

moving forward• Let the processes mature before moving on


Get Buyoff

• Check that the value was realized• Get recognition of the value from multiple

groups• There will always be negatives• There will always be nay Sayers• Keep the vision alive


Lead with Focus Group

• Choose a team that understands the process• Choose a high impact area• Validate the benefits with the team• Hand hold if needed• Use multiple groups to validate processes


Today’s Reality

• True repeatable release system• Automated documentation and standards

enforcement• Quick builds and automated tracking• Easy version migration for external tools• Lots of shareable knowledge• Easy ramp up of new team members


Where are we headed now

What do we have and do we ever sleep


Today’s Reality

• Centralized business logic• Integrated monitoring• Enterprise is open to change• Leading other teams • Respected input to Open Source projects• Can respond to flawed business processes


Tomorrow’s Vision

• Move to new Eclipse Releases• Position for new Maven release• Finalize Cruise Control and move to

Continuum• Move to subversion• Implement Cargo• Migrate Web Service Development to

Eclipse


Conclusions

What did we learn and how can you take advantage of our experience


Lessons Learned

• Change is not easy but is worth the risk• Once you establish a vision you must keep

it current• Share your success and knowledge• Open source is amazing• Don’t be afraid to ask questions• Educate, Educate, Educate


How can you do it

• More education at User’s Group• Subscribe to mailing lists• Check out links on our site• We can educate, measure, communicate

and deliver.• Get the integrated DVD or download and

learn


References

• www.soaringeagleco.com• Scott Ryan – [email protected]• Brian Blitzer• Ted Coleman• Dave Poe

http://www.soaringeagleco.com/

mailto:[email protected]

Documents

Enterprise Rearchitecture Denver BEA User's Group May 2005