1. Testing: Ease Your Production Elevation Woes Presented By: Brian Picard

2. Introduction Intro –Personal Introduction –Meta-Directory Usage Growth Well Define ILM Roles and Responsibilities A Focus On Testing Well Documented Processes –Sections Infrastructure Initial Dev Elevation Dev => QA => Production Elevations Production Retirements

3. Introduction Cont. Roles And Responsibilities –Server Admin Operating System/ILM Patch Maintenance Server/Service Monitoring –ILM Development Current Connector Support New Connector Development Support Tool Development –ILM/Identity Architect Next Connected Systems Long Term ILM Direction Identity Considerations

4. Infrastructure Introduction Test Beds –Patch Testing –Next Version Testing –Tool Testing Development –Actual Development Sync Engine –Virtual Machines For Developers QA Server Roles –Actual QA Sync Engine –Stress Testing Server

5. Infrastructure Cont. Production Server Layouts –Normal Implementation

6. Infrastructure Cont. Tiered Implementation –Advantages: Faster Updates Batch & Frequent Cycles –Draw Backs: Extremely Complex

7. Initial Development Elevation Introduction Minimizing The Impacts Of Testing –Use Self Owned Resources To Represent Normal Connected Stores –Use Filtered Disconnectors To Represent Deprovisioning

8. Initial Development Elevation Cont. Test Cases –Adding A New User –Modifying A User –Deleting A User (Delayed Processing) –Deleting/Modifying A User In A Non-Authoritative Store –Attribute Precedence Verification –Multiple Flow On The Same Attribute –Special Attribute Flows (Ex. ObjectClass)

9. Initial Development Elevation Cont. N Unit Tests

10. Initial Development Elevation Cont. Approvals

11. Dev => QA => Production Elevations Introduction Elevation Flowchart

12. Dev => QA => Production Elevations Cont. Check List Backup Directories For Staging –File Backups –Prior Elevations –Forces Focus On Elevations

13. Production Retirements Testing Removals Actually Removing The Connector –Documented Process –Checklist

14. Questions and Answers Brian Picard (Brian_Picard@Progressive.com)Brian_Picard@Progressive.com