1. Release Control with PowerCenter at UBS / Switzerland Friedrich Lehn Configuration & Release Manager October 2000

2. Agenda z z Project Overview z z PowerCenter Configuration z z Configuration Management z z Deployment Process z z Release Process z z Summary

3. Project Overview z z Global, integrated investment services firm offering - the full range of wealth management, asset management, investment banking and securities services - to the full spectrum of clients z z World’s largest private bank z z Top ten financial services firm by market capitalization - $62 billion dollars z z Total client assets of US$1 trillion UBS

4. Project Overview System Environments Development Production Test z z IBM AIX SP2 cluster z z DB2 UDB EEE z z PowerCenter 1.6

5. Project Overview Load Process File Preprocessing Conditioning AutoLoader PowerCenter SQL Apply AutoLoader System of Records Common Data Warehouse

6. Project Overview z z Main organizational element z z Three letter acronym as base for naming standards z z Each delivery stream gets the same infrastructure: UNIX directories, meta data area, PowerCenter folders z z Each delivery stream has business responsible, data modeler, database administrator, delivery stream manager z z Team size typically between 1 and 5 z z Delivery streams release independently from each other Delivery Stream

7. Project Overview Application Structure Delivery streams: RCLrelease control tools MDRmeta data repository DSFDWP sourcing framework FDSfeed specific data processing subject data area data mart... RCLMDRFDS System of Records DSF DWP Sourcing Framework... Common Data Warehouse

8. Project Overview z z Two areas: /dwp_rootUNIX based files, version controlled /dwp_datadynamic data, archival on demand z z Additional directory level for the environment in order to support more than one environment on one system z z /dwp_root is organized by delivery streams Directory Structure

9. Project Overview z z /dwp_data is organized by logical processing steps and by delivery streams z z Symbolic links from PowerCenter program area to /dwp_data z z Tool support for generation of directories (delta processing, integration with release procedures) Directory Structure (continued)

10. PowerCenter Configuration z z Start with one single (local) repository z z Support different, clearly separated environments with different responsibilities z z All environments have identical structure (products, databases, PowerCenter server configurations) z z All program changes (UNIX, PowerCenter) are done on the development system z z All changes on test and production systems go through the release process and are clearly tracked Design Principles

11. PowerCenter Configuration Repository Structure DSVSASP Server Ddevelopment Sstaging Vversioning Aintegration / user acceptance test Pproduction

12. PowerCenter Configuration Folder Structure Release area is identical in all environments. user area (avoid shortcuts) team area release area

13. PowerCenter Configuration developerdevelopment, unit and integration testing delivery stream managermanager, release planning release managerdeployment, tracking, configuration control PowerCenter administration session managersession management for test and production systems Roles and Responsibilities RoleResponsibility

14. Configuration Management z z External tool for software configuration management (Rational Corporation) z z Powerful version control, work space and build management z z Same directory structure as in development environment z z Fully automated access layer ClearCase

15. Configuration Management z z Integrate all release specific data: sourcing framework, DDL, documentation, scripts & SQL z z Avoid problems with current PowerCenter version mechanism (shortcuts, sessions) z z Enable automation of release process z z Different responsibilities for different environments z z Enforce change tracking Why external version control?

16. Configuration Management z z _.. z z e. g. ACC_1.0.1 z z major release number (high level “wave” planning) z z minor release number (delivery stream development plan) z z patch level (bug fixes, emergency releases) Release Naming

17. Configuration Management Versioning Example Labeling Schema: ACC_x.y.zrelease label RLS_Acurrent version in user acceptance test RLS_Pcurrent version in production /main/1 /main/2 /main/4 /main/5 ACC_1.0.0 ACC_1.0.1 ACC_1.0.2 ACC_2.0.0 RLS_P RLS_A reset_acc.sql /main/3

18. Deployment Process z z Repository Copy: - via GUI / database backup & restore - trackable (result is a file) - problem: overwrites server configuration z z Folder Copy: - only via GUI - and therefore not trackable z z Mapping Copy: - only via GUI - used only within development repository PowerCenter Deployment Facilities

19. Deployment Process z z “Repository Copy” is the only trackable method z z Delivery Streams require folder level deployment Approach z Introduce staging repositories in all environments z Staging repository is used to separate folder from repository, using the “Folder Copy” method z Staging repository is then deployed using the “Repository Copy” method Use combination of both methods:

20. Deployment Process Freeze, Deliver and Receive Processes DSVSASP manual folder copy database unload / load automated process delivery package ClearCase Freeze Deliver Receive

21. Deployment Process sub unload { system("db2 connect to $repository user $user using $password"); db2select(\@tables, ”SELECT tabname FROM syscat.tables WHERE tabschema = 'PCSTAGE' and (tabname LIKE 'OPB_%' or tabname LIKE 'REP_%') and type = 'T' ORDER BY tabname"); foreach $table (@tables) { system("db2 export to $table of del modified by coldel0x02 chardel0x03 select \\* from $user.$table”); }; system("tar cvf $tarfile *"); } Repository Unload

22. Deployment Process sub load { system("db2 connect to $repository user $user using $password"); system("tar xvf $tarfile"); foreach $file (("OPB_REPOSIT", "OPB_REPOSIT_INFO")) { system("sed -e 's/CDW_StagingD/$name/g' $file > tmp.out"); system("sed -e 's/DDBPCR/$dbs/g' tmp.out > $file"); } foreach $table ( ) { system("db2 delete from $user.$table”); system("db2 import from $table of del modified by coldel0x02 chardel0x03 delprioritychar insert into $user.$table”); }; } Repository Load

23. Release Process z z Responsible for high level planning and impact analysis z z Defines release scope and release numbers on base of delivery streams z z Assigns responsibilities (delivery stream manager, data modeler, database administrator, business responsible) z z Result is documented in “wave plan” document z z Wave plan is base for all subsequent design, implementation and quality assurance tasks Change Control Board

24. Release Process 1. Preparation of UNIX and PowerCenter release areasdelivery stream manager 2. Issue release requestdelivery stream manager 3. Create new release (Freeze)release manager - Copy to staging repository, unload - Create / update ClearCase file versions - Create release label and attach to new release 4. Create release package (Deliver)release manager - delta / full processing - lock release in ClearCase 5. Install release (Receive)IT integration / IT operation - Load, copy from staging repository - Post install script 6. Create / update database objects in target environmentdatabase administrator 7. Restart PowerCenter serverIT integration / IT operation Release Procedure Responsible

26. Release Process z z Provide easy-to-use information on all releases z z Today: ClearCase based z z In future: Integration with meta data repository Release Database DSF_1.1.4A27-Jul-00.17:32:27new config files DSF_1.1.320-Jul-00.13:16:38 fix for single node load problem DSF_1.1.2P19-Jul-00.14:05:30correct JDM, error handling DSF_1.1.118-Jul-00.17:51:19removed environment dependencies DSF_1.1.017-Jul-00.17:11:47see release notes DSF_1.0.211-Jun-00.14:07:01changed Gen_Environment DSF_1.0.109-Jun-00.13:20:03see release notes DSF_1.0.024-May-00.17:48:42initial version Example:

27. Summary z z PowerCenter was successfully introduced at UBS and proved to work well within the sourcing framework z z Configuration control with ClearCase is efficient and straight forward z z Release process meets the requirements and is efficient (so far ~200 successful releases, effort usually below ½ hour) z z Generally little administration overhead although some improvements in PowerCenter would make administrator´s and release manager´s life easier Experiences

28. Summary z z Copy of sessions z z Export / import folders via (UNIX) command line for further automation of release process z z Avoid restart after deployment z z Logical backups / restores via command line with result on server side (more flexible than database backup, avoid ODBC overhead) z z User administration via command line Wish List

29. Contact Information Friedrich Lehn UBS AG, Switzerland phone:+49 171 360 60 84 email:friedrich.lehn@t-online.de