Embed Size (px)
Citation preview
OWB Implementation Testimonial
Presented byDavid CordasData Architecture Team LeadLUCRUM, Incorporated312 Plum Street, Suite 1110Cincinnati, OH 45202513.241.5949www.lucruminc.com
Topics
Client profile Architecture layout OWB standards Job scheduling/Monitoring Future state
Client Profile
Cinergy Corp.– Provider of gas & electric serving
approximately 2 million customers in OH/KY/IN
– Initiative began in early 2003 to consolidate numerous “data silos”
– Employed Lucrum to aid in the creation of an enterprise wide data warehouse
– Using both Microsoft and Oracle databases
Architecture layout
Hardware – 3 Sun Fire 4800 – Dev 2 1.4 GHz processors, 16 GB RAM
– Test/Prod 4 1.4 GHz processors, 16 GB RAM
Operating system – Sun Solaris 8 Database – Oracle 9.2.0.3.0 Oracle Warehouse Builder
– Dev 9.2.0.2.8/9.2.0.2.0
– Test/Prod 9.0.4.10.0/9.0.4.0.27
SAN backbone running on Clariion & Symmetrix
Architecture layout – cont.
Design Repository
Design Repository Design Repository
Runtime Repository
Test Runtime Repository
UAT Runtime Repository
Prod Fix Runtime Repository
Runtime Repository
Deploy
Promote
Test
UAT
Prod Fix
Product Release
Deploy
Deploy
Deploy
Deploy
Dev ProdTest
UAT Promote
Prod Fix Synch
Dev Synch
Prod Fix Promote
Redeploy
OWB Standards
OWB configured for 17 concurrent developers
Common module for conformed dimensions across all development paths
Separate modules for individual project development
Data sources defined by OWB administrator, not developers
No outbound reconciliation!!!!
OWB Standards – cont.
Fact table mappings configured for “set based” rather than “row based” processing
Dimension table mappings configured for “set based fail over to row based” processing
Process flows used to organize logical groups of work
Common processing tasks grouped in re-usable process flows
OWB Standards – cont.
Oracle sources handled via database links Non-Oracle sources handled via flat files Flat files configured as External Tables Custom PL/SQL written outside of OWB
and imported into meta data Objects currently deployed; Mappings &
Process Flows
Job Scheduling & Monitoring
Cron used to schedule nightly processing Data validation checkpoints throughout
ETL processing Parameterized stored procedure used to
launch OWB process flows Process flows used to handle execution of
dependent sub-processes
Job Scheduling & Monitoring – cont.
Utilize Runtime Audit Browser (RAB) and/or Workflow Monitor for information on OWB processing
OWB currently processing approximately 4+ million rows of data nightly from 3 source systems
Future State
Implement OWB templates Provide robust job notification facility
(email/paging) Implement OWB data validation plug-ins
(Fact & Dimension thresholding) Automate OWB meta data feed to custom
meta data system Consolidate 12 additional source systems
