Jim Bole

1
Welcome!

• Jim Bole
• Vice President, SOA Solutions
• Software AG

2
Agenda Topics
900 1015 SOA Best Practices Jim Bole -
Is SOA Dead? - Target State The Agile
Enterprise - Agility Business/IT Alignment
Service Domains - Architectural Implications -
Infrastructure Requirements - Usage
Patterns - Federation Models - Best Practice
Take-aways 1015 1030 Break 1030
1200 The End Game PA JNET Frank Caloiaro -
Justice-based standards for information
exchange - NIEM/JXDM - Security for Justice
Networks - Policy-based governance
designtime/runtime/changetime
3
SOA Has Crossed the Chasm
4
SOA has Crossed the Chasm

• Which statement best describes the state of your
  SOA implementation?
• We have no plans to adopt SOA at this time
• We have begun planning for our deployment
• We have successfully implemented SOA-based
  projects or use SOA principles in our work
• We have implemented an enterprise SOA

5
Why Now SOA Infrastructure is Ready for Prime
Time

• Service enablement is mature and prolific
• Sources include SAAS, pre-packaged software,
  enablement tools
• You are service-enabled, you just may not know
  it..
• Security has been vetted and leverages existing
  models
• Intermediary patterns well-supported by a variety
  of solutions
• Enterprise Service Bus offerings
• Service Management products
• XML Appliances
• Registry/Repository offerings are
  enterprise-class
• Governance comes to the forefront.

6
Top Drivers for SOA
Support BPM Initiatives
Simplify Integration
Improve Business Agility And Adaptability
7
Governance is Recognized as a Key Enabler

• How important is governance to SOA strategy?
• Critical
• Moderate
• Minimal

8
Software AGs SOA VisionEnabling the 21st
Century Agile Enterprise
9
21st Century Composition-Driven IT Lifecycle
Business Vision
Business Requirements
Process Requirements
Business Assets Metadata
Library of re-usable services, data, processes,
rules, docs,
Requirement 3
Requirement 2
Requirement 1
10
Your Organization Probably Looks a Little Like
This
External Users
Partners Suppliers
Internal Applications
Flat Files
Message Queue
SOAP
XML
FTP
POX
SMTP
EDI
RPC
SOCKETS
XXX
YYY
11
Why is Enterprise IT such a mess?
12
Enterprise IT is an Evolved System

• Evolution
• Variation
• Try Things at Random
• Fitness
• Compete for Selection
• Conservation
• Throw Nothing Away

13
How did we get here?

• Project Based Funding
• ROI Measured Per-Project
• No incentive to Share
• Silos Good for me bad for you thinking

14
The cure?
15
The Cure
From this
to this
Composition
JBOWS
Is SOA just LEGOland for IT people?
16
The Real Power of SOA
17
(No Transcript)
18
(No Transcript)
19
Is this the complete story of SOA?
From this
to this
Composition
JBOWS
This story only reduces the cost and complexity
of IT
20
The SOA-Enabled Enterprise
21
ACH
21
22
Business Infrastructure for SOA
23
The SOA Tipping Point Key Success Indicators

• Target State Defined
• Infrastructure Funding
• ROA and TCO Measured Lifetime
• Value Visibility
• Continuous Process Improvement
• Innovation without the hangover

24
SOA Adoption Challenges

• Heterogeneity
• Security
• Interoperability
• Hoarding
• Lack of Trust
• Externally Imposed Rules
• Loss of Control
• Assigning Blame
• Ownership
• Distribution of Burden
• Distribution of Incentives

Page 24
25
SOA Strategy Engagement

• Key Elements
• Maturity Assessment
• SOA Success Factors KPIs and Gates
• Roadmapping and Adoption Planning
• Governance Models
• Organizational Impact and the SOA-CC
• Best Practices and Recommendations
• Pragmatic Next Steps with
• measurable adoption milestones

26
Core SOA Patterns

• Consumer Patterns
• Service Discovery Pattern
• The Service Consumption Pattern
• Provider Patterns
• Service Registration Pattern
• The Service Provider Pattern
• Governance Patterns
• The Management (run time) Pattern
• The Validation (design time) Pattern

27
Consumer Pattern Service Discovery
Service Consumer
28
Consumer Pattern Service Discovery
Service Consumer
Registry
Lookup Request
29
Consumer Pattern Service Discovery
Service Registry
Service Consumer
Service Provider
Discovery
30
Consumer Pattern Consumption
Service Consuming Application
Service Provider
Service Request
31
Consumer Pattern Consumption
Service Consuming Application
Service Provider
Service Request
Service Response
32
Provider Pattern Service Registration
Service Registry
Service Provider
Registration Request
33
Provider Pattern Composite Application
Service A
Service Consuming Application
Composite Service
Service Request
Service B
Service Response
Composition can be synchronous or asynchronous
34
Governance Pattern Management (Run Time)
Service Consuming Application
Service Provider
Service Request
Service Response
Broker
XML Messages enable in flight machine processing
35
Governance Pattern Validation (Design Time)
Registry Repository
Service Provider
Registration Request
Validation
XML Declarations enable registration time
machine validation
36
Process Implications Service Lifecycle ! SDLC
37
Lifecycle Governance Pattern
Governance Registry
Service A
Service Consuming Application
Composite Service
Service Request
Service B
Service Response
Broker
Console
Lifecycle Governance encompasses Design Time
Validation, Run Time Management and Change Time
38
CentraSite Covers End-to-End Lifecycle Governance
Developer
Business User
Architect
Service Consumer
IT Operations
Admin
Design Time
Run Time
Change Time
SOA System of Record
CentraSite enables Collaboration and Trust
between Stakeholders
39
SOA Federation Patterns Sharing Scopes
40
Best Practice Recommendations The Soft Issues

• Governance from Day 1. Align with existing
  processes and ensure quality of service content.
• Establish service management roles beyond
  author. Formalize these new roles. Multiple
  roles per person is typical.
• Services as Products. Instill a product
  management approach and culture.
• Leverage existing processes to the hilt vs.
  creating new processes if possible.
• Dont over-govern. Start with advisory policies
  and tighten later.
• Visible executive sponsorship is essential to the
  success of an SOA initiative. This is more than a
  technology project.
• Solicit cross-functional participation when
  appropriate.
• Revisit Funding and Incentive models.

40
41
Target State Best Practice Recommendations -
Design-time

• Use of canonicals is becoming a strong indicator
  of SOA success. Should be introduced
  incrementally, but business service contracts
  should ideally utilize them from the start.
• Augment current EA review procedures with service
  aspects.
• Design your governance model up-front, even
  before tooling exists. Ensure that service
  definitions are complete and high quality
  metadata exists.
• Create templates for Service Design
  Specifications. These should focus on sound
  interface/contract design, not implementation.
• Define standards for namespaces and service
  naming. Make sure to allow room in namespaces
  for hierarchical extensions. Dont use
  organization names in names/namespaces they
  will change at the worst time.
• Start with approval-based governance initially
  augmenting design reviews. Learn from this an
  automate later.

41
42
Target State Best Practice Recommendations -
Runtime

• Establish mediation as part of the architecture
  asap. Not doing so will require substantial
  headaches and rework later.
• Design a security model that is policy-driven and
  enforced. Eliminate authentication in the
  provider service and migrate to mediator when
  available.
• Establish SDM-wide SLAs, monitoring best
  practices.
• Implement contracts to allow preferencing of
  consumer/provider relationships.
• Consider use of XML appliances for later phases
  and Inter-department SOA.

42
43
Target State Best Practice Recommendations -
Changetime

• Tackle consumer onboarding process now, implement
  manually until registry/repository is available.
  This will ensure you know what apps are consuming
  what services.
• Create templates for Service Requests and Service
  Access Requests. Maintain these artifacts along
  with the registry/repository.
• Establish service provision process/policies in
  conjunction with CCB activities today.
• Defer version management and offboarding
  processes to later phases.

43
44
The End GameFull Justice Integration PA
JNETFrank Caloiaro - DTC