Professional Documents
Culture Documents
ETL Development Standards
ETL Development Standards
Table of Contents
ETL Development Checklist ................................................................................................................................................................................ 2
Technical Specification Development Guidelines ..................................................................................................................................................................................2 Informatica Naming Conventions...........................................................................................................................................................................................................2 Informatica Version Control Guidelines.................................................................................................................................................................................................3 Documentation........................................................................................................................................................................................................................................4 Miscellaneous Guidelines .......................................................................................................................................................................................................................4 Optimization/Security Considerations ....................................................................................................................................................................................................4 Change Management Considerations .....................................................................................................................................................................................................4
BAIRS Outages.............................................................................................................................................................................. 6 Issues Log....................................................................................................................................................................................... 6 Month-End Procedures .................................................................................................................................................................. 7 Archiving Procedures ..................................................................................................................................................................... 7 Student Data Warehouse Support................................................................................................................................................... 7
Appendix G Gaelen Standards........................................................................................................................................................................... 7 Appendix H - Peoplesoft Table Considerations ................................................................................................................................................... 8 Appendix I - Environment Objectives.................................................................................................................................................................. 8
Page 1
TargetName is Action is
Page 2
Session Naming Conventions Within Informatica Workflow Manager, sessions should be named using the following template: s_MappingName_Qualifier where: s MappingName is Qualifier is stands for session the name of the Informatica mapping associated with a given session A description of the functionality of the session. This only needs to be added if the mapping is associated with multiple sessions.
Workflow Naming Conventions Within Informatica Workflow Manager, Workflows should be named using the following template: wf_WorkflowName_Frequency where: wf WorkflowName is Frequency is stands for Workflow a description of the functionality contained within the workflow, e.g. HR_ADM_WKFORCE how often the workflow runs e.g. Monthly, Daily, Weekly. Daily can be used for workflows which run Monday through Saturday or Monday through Friday.
Page 3
Documentation
Documentation should be posted on the appropriate BearShare site: BearShare is backed up nightly with 2 hour snapshots taken during the day more info is available at : https://bearshare.berkeley.edu/C4/Implementing%20BearShare/default.aspx. Michael Leefers is contact for bearshare questions.
Miscellaneous Guidelines
Source to Stage Mapping Guidelines Update strategy: maintenance of code values not matching in the source system Workflows should be updated in info_dev repository to match production before new/revised maps, sessions and/or workflows are moved to production. Include considerations of shortcut folder management when existing maps are to be modified.
All documents on this list should be updated as part of any new development work. Report Inventories: https://bearshare.berkeley.edu/sites/RAPO/EDW/reporting/Reports/Shared%20Documents/Forms/AllItems.aspx - contains three documents containing report inventories for BAIRS, BIS and HR. It would be useful to augment these spreadsheets by adding the underlying tables associated with listed views.
Optimization/Security Considerations
Developer Roles (ADM_RO and ADM_HR_RO) should always be given read access to new database objects. Access privileges may prevent developers from being able to view data contained in database Views. Two ways to deal with this: 1. Update HRMS_OPR_XREF table (in QA) to allow access. Example below:
Update BAIR_HRMS_OPR_XREF Set userid = BISWJC Where oprid = 011502567 (or 011504738)
2.
Apply for security access through SARA (HRMS Dept. Security, Administer Workforce)
Page 4
To request mainframe production changes: send 2 emails: asdhelp@berkeley.edu ist-as-production@lists.berkeley.edu Enter objects to be moved into TSO MIGMGR - describe what needs to be moved and when. (e.g. move members xxx from EDW.PUB.STAGE.INCLIB to ASD.P.CTM.BIS.AEVARS).
Report Migrations Contact bairpthelp@berkeley.edu for report migration requests. Non-standard between 5-6 PM , 8-9 AM. Report users/ESS staff to review before general access is allowed.
Page 5
Page 6
Page 7
Page 8