A Practical Roadmap to SOA Governance Enterprise Integration Services

Transcription

1 A Practical Roadmap to SOA Governance 2011

2 A Practical Roadmap to SOA Governance

3 Corporate Overview Staples is the world s largest office products company and a trusted source for office solutions. Provides products, services and expertise in office supplies, copy & print, technology, facilities and breakroom, and furniture. Invented the office superstore concept in 1986 Now has annual sales of $25 billion, ranking second in the world in ecommerce sales. With 90,000 associates worldwide, operates in 26 countries throughout North and South America, Europe, Asia and Australia, making it easy for businesses of all sizes, and consumers.

4 IT Overview 2400 FTE capacity in the global IT organization Multiple data centers domestic and international A portfolio exceeding 800 applications IT development, management and governance activities Applications Manage and prioritize enterprise work Reduce lights on costs by consolidating applications Migrate existing applications to common enterprise services Infrastructure Virtualization and enterprise governance Standard service catalog with well understood SLAs Implement ITIL, CMDB methodologies and tools

5 What is governance? The quick definition is 'governance makes the rules.' A lot of people think it will impose more work, but the best governance system is one that people appreciate, that helps people get work done, with the highest quality, and that is beneficial to business. -Ann Thomas Manes Q&A: A SOA Governance Primer Let s assume that governance isn t just making rules

6 First steps Merge or draft lists of service providers and consumers Merge or draft preliminary standards Understand existing non-soa governance domains Even early efforts provide value: Scopes domain Develops ideas about next steps Builds shared conventions

7 First steps Business stakeholders IT stakeholders Service owners Service consumers IT architects IT developers IT testers IT infrastructure What do you find out?

8 First steps How ready is your organization? How many people can work on governance? How do SOA priorities align with other governance concerns? Do SOA participants show ownership?

9 First steps What SOA terminology / standards do teams use? Do teams have standards for service contracts? Do teams follow the standards? Build a glossary and model based on the answers Keep refining and extending your glossary and models as you learn

10 First steps Explain key concepts Share models and views publicly Keep going even when concerns arise Make the ideas real implement them Show incremental improvements

11 Developing Who is ready for governance? Who needs governance? The groups may not always align Make sure you represent the needs of the willing in your work

12 Developing Everyone will have opinions What are the needs within the opinions? Multiple teams may work on the same problems Who owns governance? Too much debate may indicate scope overreach

13 Developing Aim for agility Be prepared to rework models and metadata Standards are likely to grow and shift as adoption increases What is not negotiable? What is negotiable?

14 Developing How sophisticated is your organization? Study open reference models and architectures OAGIS TOGAF ARTS Vendor sources Adopt / absorb what you can Simplify as needed

15 Developing Be relevant and realistic Don t worry about top-down, bottom-up, middle-out at first Don t pick a fight with the existing culture Over time the bigger picture will take shape There is no single right approach Don t stop when it gets difficult

16 Developing Start lightweight Excel Word Web pages Basic registry/repository features Create artifacts that are linkable and easily shared Allows you to refactor fast

17 Developing Set up a registry/repository sandbox Create simple ways to clear/reload service metadata Quickly demonstrate changes

18 Implementing Align with enterprise architecture Look to reuse existing inventories, catalogs, standards Where possible Join existing committees Extend existing documentation Where necessary Add groups to do additional reviews Aim to use living documents from design and development

19 Implementing What does an elevator talk for a service look like? Keep it short and non-technical Link it to the service owner and supporting details Document these talks in the service catalog Deliver an easy way to access the service catalog Publicize the service catalog Provide a SLA to help consumers find providers

20 Implementing Provide templates, patterns and examples Document decisions Include rationale & examples Watch people and process SOA surfaces impediments Advocate with decision makers Shield teams from larger organizational challenges

21 Implementing People need to trust the service catalog Do you want to pull service metadata from developers? or Do you want developers to push it to you? Builds publish to service catalog Schemas, WSDLs, SLAs

22 Implementing Manage run-time properties in registry and repository Schemas Validate at deploy time SLAs Enforce on each message Security Authorize service interactions Log all policy violations Block or forward traffic based on configuration

23 A Practical Roadmap to SOA Governance the best governance system is one that people appreciate, that helps people get work done, with the highest quality, and that is beneficial to business. First steps Don t wait Gather many viewpoints Size your ambitions Define your terms Share with others Developing Align with allies Expect debate Bend don t break Be credible Adapt to conditions Use lightweight tools Implementing Federate governance Help consumers Support providers Connect developers Enforce run-time policy

24 A Practical Roadmap to SOA Governance Page Page Page Page Page Page 9 Page Page Page Page Page Page Page Page Page Page Page It.jpg&newest=1 Page Page Page