ODTUG 2002 JavaJ2EE Application Development with Oracle Designer JHeadstart Designer Generator

1
Frank Brink Josef Megens Oracle
2

• J-RAG
• pka ANTGBU
• Contributors
• Rob Swinkels
• Raghu Narasimhamurthy
• Josef Megens
• Frank Brink

3
Agenda

• Introduction
• Terminology
• J-RAG steps
• Demo
• Restrictions
• Beyond release 1
• Summary and QA

4
Introduction

• J-RAG inspired by
• Nightly builds scripts - also with ANT
• Labour intensive release management procedure
• Missing Usage of DE Batch Generators in nightly
  builds through GBU files
• inaccessible (binary format)
• Non-updatable (one time only)
• Core create your own GBU files
• Supports Oracle SCM driven Development and
  Deployment
• J-RAG supports two flavours
• Nightly Builds
• Configuration usage
• Promises significant benefits through cost
  savings
• Release Management process 10
• Nightly Builds 20

5
Terminolgy

• Workarea
• Containers
• Configuration

6
Workareas

• A Workarea
• shows part(s) of one or more Application Systems
  and Folders...
• like a peephole in the repository
• Filters the objects versions you can see
• each object can showup in no, one or
  moreworkareas
• Does only reveals one version

7
Usage of workareas

• Represent your promotion model
• Development
• Test
• Production
• Apply fixes in the production environment
• Production fix workarea
• To support parallel development on multiple
  releases simultaneously
• Development_latest (main branch)
• Development_latest-1 (specific release branch)
• Temporary view
• To view a specific element version and its
  references

8
Repository Folder structure

• All repository objects are stored in Folders (or
  application systems)
• Folders can be nested
• Access Privileges are defined at Folder Level

• Folders can be mapped to File System Directories

9
Oracle Repository Concepts Configurations

• A configuration is a setof object versions
• Like a stripe or a label
• Configurations may represent
• Full releases
• Patch releases
• Component Versions
• Anything else you want it to represent

10
Relationship between object versions,
configurations and workareas
EMP 1.0 DEPT 1.0 PROJECT 1.0
EMP 1.2 DEPT 1.2 PROJECT 1.1
DMO 2.1.1.0
11
(No Transcript)
12
J-RAG pka ANTGBU steps

• Populate configuration with structured elements
• Generate GBU files
• DDL and TAPI
• Forms, Menu and Libraries
• Call GBU generators providing GBU files
• DDL and tapi scripts
• FMB, MMB and PLLs
• Upload output in repository
• Associate output with configuration

13
Tool stack

• JAVA -gt GBU files
• ANT (1.6.2) -gt driver or workflow engine
• DE GBU generators -gt output files
• RCL -gt Population and Configuration Update
• End User Interface -gt Text editor for properties
  files
• ANTGBU-gt J-RAG

14
Properties files

• Build.properties
• Repository connection
• Repository context
• Workarea
• Container
• Configuration
• Which GBU generator(s) by calling multiple
  properties files
• DDL.properties
• Naming of output and location
• Filters (incl. Configuration)
• Delta generation
• Other properties files (TAPI, Forms, Menu,
  Library)
• Naming of output and location
• Filters (incl. Configuration)

15
D E M O N S T R A T I O N
J-RAG Config-DDL
16
Terminolgy - continued

• External or Dangling References

17
Incomplete Compositions leading to Dangling
References

• Dangling or External References are references
  from elements in a Configuration or WorkArea to
  Objects that are NOT in that Configuration or
  WorkArea

JOB
EMP
DEPT
ADMEMP
EMP
Configuration
ADMEMP
18
Composing Object Collectionsor Ring Fencing

• First Fence to include the core objects you need

• Second Fence to include primary referenced
  objects, needed by the core objects
• second fence objects may have dangling references

19
Restrictions

• Only one root container per configurations
• Case sensitiveness and no spaces in names (e.g.
  configurations)
• Database Version in DE up to 9i (Unsolved)
  issues with defining a 10g database
• No support for Report generator relatively easy
  to add
• All structured elements checked-in when
  configurations are used
• GBU generation output window requires human
  interaction
• Does not add NO_KEYWORD_EXPANSION string in
  ToBeUploaded ddl files workaround use
  compression
• No support (yet) for Headstart Utilities in batch
  (e.g. Generate Capi)
• Does not resolve external references

20
Beyond release 1

• Integration with nightly build ANT script fully
  automation of - nightly build process
• Remove - some restrictions
• Workaround for the GBU human interaction
• Call Headstart Utilities in Batch
• Report generation

21
Summary

• IN a configuration with primarily structured
  elements
• Evaluate J-RAG properties files with text editor
• Workarea context, including configuration
• Which DE generators to call
• Run ANT builldall on command line
• OUT a configuration with structured elements and
  their derived file elements
• Will be available in October 2004 through the
  Supplement Option
• Certified with full Oracle 10g tool stack
  (Designer, Developer and database)
• Can be used for nightly builds and to automate
  (boost) the release management procedure

22
A
23
(No Transcript)