Best practices ensuring a successful implementation
Download as PPTX, PDF2 likes1,222 views
The document outlines best practices for deploying an identity and access management (IAM) platform, focusing on project initiation, architecture, implementation, and testing strategies. Key recommendations include ensuring proper resource management, leveraging existing product functionalities, and automating continuous integration processes. It emphasizes the importance of thorough testing, including both functional and non-functional aspects, and maintaining proper supportability and documentation throughout the deployment lifecycle.
Best practices ensuring a successful implementation
- 1. OIS Deployment Best Practices Steve Ferris VP Services Tim Rault-Smith Director Services International
- 2. From Concept to Competition 2
- 3. Why are we here? We want to see customers and partners succeed Best practice is easier, cheaper and safer in the long term The goal should be a stable, supportable production platform, the question is how best to get there… Based on our experience in services and consulting in both ForgeRock and Sun • • • • 3
- 4. Project Initiation Project scope The 3 R’s; Resources, Responsibilities, Roles Planning; critical path; dependencies; expectations To PoC or not to PoC; a PoC helps you to trial functionality and features; hit issues early! Plan for Training and Professional Services • • • • • 4
- 5. Architecture Correct use of the products • Mapping requirements to features Ensuring architecture meets both functional and nonfunctional requirements; especially scale and security Implement for ease of management and scale; try to keep it simple • Simple does not mean basic; it should mean enough complexity to meet requirements, but no more. Cost of ownership is directly proportion to the complexity of the deployment 5
- 6. Implementation ■ Source Code Revision; even for configuration IAM deployments tend to be long lived; maintaining history and consistency across the project will yield long term benefits. ■ Leverage the products rather than custom code Plenty of plug-in points in the products; work with rather than against the product. Work with ForgeRock to raise improvements and/or changes Understand and record what's been configured/customised and why; you will not be there forever! ■ 6
- 7. Automation and CI ■ CI is Continuous Integration Use a tool such as Jenkins to ensure your unit tests are run, Maven artifacts are published, builds are consistent and everything is automated ■ Depends on customisations If you do not have many (or any) customisations (in terms of code) then CI may be overkill or inappropriate Unit testing; determining you've not broken anything ■ If you are developing customisations then ensure you include unit tests to ensure you’ve not broken anything 7
- 8. Functional Testing ■ What constitutes a good test plan Should encompass all functionality relied upon to deliver the solution You want to ensure that nothing breaks as you extend and build on your IAM deployment Ensure your configuration/customisations are in covered in the test plan ■ Remember: you are only ensuring your use of the product is functional rather than the product itself. 8
- 9. Non Functional Testing ■ Testing failover and DR procedures Always best not to leave these until the P1 hits! Load testing; the benefits of a load testing framework ■ Don’t just do this once; integrate load testing into your general test plan If you have not load tested how can you be sure any changes will not have effected the scale 9
- 10. Tuning ■ JVM tuning GC & heap ■ AM tuning basics Notifications SDK caching Container thread pool ■ DJ tuning basics Indexing Caches 10
- 11. Go live ■ ■ ■ Tested process Rollback procedure – also tested Tell us! (Especially if it’s the weekend…) Preferably not with 4 hours’ notice! If you are a ForgeRock subscription customer with 24x7 support Enough notice will ensure we can arrange the most appropriate out-of-hours cover 11
- 12. Supportability ■ Puppet not Word We are not living in the 20th century; puppet does the work, not you! ■ Effective Runbook Stable product – install and forget! The runbook is the operational team’s procedure manual, and your safety net ■ Debugging procedures Should be in the runbook so everyone knows the basics 12
- 13. Supportability ■ ■ Backup and Restore process Effective Change Control 13
- 14. European Summit 2013 Thanks for coming and see you next year! 14