Published August 2010
Downloads for this series:
Enterprise software development has its challenges. Of particular interest is how to manage extremely complex change-control processes on a multitude of computing systems. Oracle Application Development Framework (Oracle ADF) presents its own change-control challenges, which need to be adapted to existing enterprise change-control procedures. This five-part article investigates the complex area of file version control using Subversion (SVN) for the life of an Oracle ADF application.
For those needing background, Oracle ADF is an innovative, yet mature Java EE development framework available from Oracle, and unlike most other frameworks, is directly supported and enabled by the award winning development environment, Oracle JDeveloper 11g. Oracle JDeveloper is a free integrated development environment (IDE) that simplifies the development of Java-based SOA applications and user interfaces, provides support for the full development life cycle, and integrates with Oracle ADF.
This series goes beyond simply explaining how to use SVN with Oracle JDeveloper 11g. It is intended to give development teams, managers, and change-control officers a heads-up on the complete end-to-end process of building, extending, and maintaining Oracle ADF applications through typical enterprise Development, Test, and Production environments.
Part 1: Challenges of Enterprise Development and Oracle ADF Development Collide
This installment explores some of the challenges presented in applying enterprise change-control procedures to Oracle ADF system development. In addition, this chapter describes the assumptions the article makes and it provides a disclaimer about adopting the article's proposals.
Part 2: Team Roles, Change-Control Workflow Scenarios, and the Initial Oracle ADF Build
This installment describes the main team players in the lifetime of an Oracle ADF application as it migrates between Development, Test, and Production environments. It also describes what is undertaken in the initial setup of an Oracle ADF application and what happens to development when multiple developers come on board.
Part 3: Migrating Your Oracle ADF Application to Test and Making Fixes
Once development is complete, and all the code is checked into the change-control system by developers, how is the Oracle ADF application migrated from Development to Test, and who does the work? This chapter explores that topic and how problems are addressed within the change-control procedures.
Part 4: Migrating Your Oracle ADF Application to Production and Writing Emergency Fixes
Here you'll learn how an application is migrated to Production after it is complete, and who does the work. It also explores what to do if errors are found in Production that require hot fixes and how this applies to the change-control procedures.
Part 5: Oracle ADF Application Architecture
Real-world Oracle JDeveloper 11g development includes the ability to split applications into multiple sub-applications that comprise bounded task flows, declarative components, and page templates. This chapter explains how that relates to the change-control procedures.
Chris would like to thank Ray Tindall from SAGE Computing Services and Susan Duncan from Oracle Corporation for their assistance in reviewing this article.