SOA Masterclass Core Technologies - SOA Governance

  • 439 views
Uploaded on

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
439
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
26
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • So what are the alternatives to application modernization? Some of organizations may consider rewriting their applications in Java or .NET or replacing an existing core system with a packaged application. In fact, many vendors have hijacked the term "legacy modernization" and now use it as a more acceptable way to say "rip and replace." While some organizations have successfully replaced core systems with newly written applications, most have not. The reason these projects often fail is due to the high cost and risk associated with a total replacement. Others attempt to rewrite their system from the ground up. Somewhere along the line they discover they lack a complete understanding of the original system. As a result they can't create a new system with comparable functionality. Still others believe the core issue is the lack of skilled workers to support the so-called "legacy" system. They think replacing both the old technology and the longtime employees will solve their problem. Unfortunately, they overlook a very important point. The more experienced and knowledgeable employees have more than just programming and system management skills- they also know and understand the business processes inside and out. Loss of key personnel can risk loss of domain knowledge. Attempting to replace an existing system without the benefit of the domain knowledge that these employees possess is truly a risky proposition. Many customers have taken those points into consideration when weighing a decision to rip and replace or modernize their existing systems and many have already decided that modernization is the less risky and less costly approach. A study we conducted last year confirms organizations’ desire to modernization applications. The study revealed that 75% of the 243 customers surveyed worldwide intended to modernize their systems compared with rewriting, replacing or outsourcing. We believe Application Modernization is the ideal way to move systems forward to support new business initiatives.
  • The SOA Edition, helps an organization leverage their existing application and data assets and make them available for use in a SOA. Our goal is to help you build the bridge to SOA faster.
  • Integration Your Way Customer Spain: “ I feel like we are missing a major opportunity because our systems aren't integrated. We have to do a ton of custom coding right now, and unfortunately no one has shown us a solution that doesn't ask us to change our business model to fit the package”.
  • Define each term High level what \ Full support for WS* and POX Standards Multi-Protocol Communications webMethods ESB (Integration Server) Enterprise-Class Foundation for your SOA Features Single services based container for application and partner integration Create services via Enablement, Link services via Orchestration, Enhance services via Mediation Full support for Web Service (WS*) and POX based standards Multi-protocol communications and document standards support Supports all integration patterns Benefits Foundation for your SOA and Integration Projects Orchestrate business services from many diverse sources Meeting the complex integration needs of your SOA
  • This slide is to setup what the components of the ESB Platform are. Highlight all of the pieces that make up the platform so that prospects understand our complete offering
  • How do you as an EA work with existing project management team and the lifecycles that have been in place for years. Need: Timely influence, not brute force enforcement of policies
  • Presentation Title Date Author

Transcript

  • 1. Core Technologies
  • 2. Quote of the Day “ SOA is all about designing for change; Designing for change cannot be realized without technology, however , technology alone could not enable SOA . Frédéric Faugère SOA Stratégies National Bank of Canada
  • 3. Stuff we need … 1. Service Enablement 3. Service Registry 2. Service Access/Interaction 4. SOA Governance
  • 4. Service Enablement
    • Easy for new bespoke apps
      • Java App Servers
      • .Net
      • SOAP, REST
    • Quite Easy for Packaged Apps
      • More vendors provide service interfaces
      • Are you on the right version ?
    • Service Enablement Tools
      • Adapters
      • Specialist tools
  • 5. The options Less risky Less costly 75% intend to modernize Rip and Replace Replace with package High cost High risk Rewrite Lack of understanding Loss of key personnel Application Modernization
  • 6. SOA Edition Building the bridge to SOA Green screens Isolated applications Difficult to change Mysterious “noodle code” Rich interfaces Service orchestration Designed to change Governable and Manageable Today SOA Possibilities
  • 7. One Size Does Not Fit All
    • ‘ On the fly’ transformation of ‘green screens’ into state-of-the-art Web pages
    • Without touching existing systems
    • Highly customizable
    • Modern SOA architecture for legacy applications
    • Choice of optimal integration architecture
    • Comprehensive support for existing environments
    • Rapid service enablement with governance built-in
    • Direct access to data
    Instant Web Enablement Comprehensive Mainframe Integration User Session Transactions Data Events Reusable Services
  • 8. Stuff we need … 1. Service Enablement 3. Service Registry 2. Service Access/Interaction 4. SOA Governance
  • 9. Service Access Enterprise Service Bus – Integration Platform An ESB is a middleware solution that enables interoperability among heterogeneous environments using a service-oriented model … - Burton … responsible for providing a distributed communications infrastructure … - Forrester … enables the separation of communication and integration logic from the application business logic - Gartner ESB is a communication and mediation layer that connects service consumers and providers … - Gartner
  • 10. Software AG Positioned as a Leader in the ESB Market
    • “ Software AG earned top scores for design-time support by including its CentraSite repository”
    Source: Forrester Research, Inc., The Forrester Wave™: Enterprise Service Buses, Q1 2009, January 26, 2009 The Forrester Wave is copyrighted by Forrester Research, Inc. Forrester and Forrester Wave are trademarks of Forrester Research, Inc. The Forrester Wave is a graphical representation of Forrester's call on a market and is plotted using a detailed spreadsheet with exposed scores, weightings, and comments. Forrester does not endorse any vendor, product, or service depicted in the Forrester Wave. Information is based on best available resources. Opinions reflect judgment at the time and are subject to change. “ The standout feature of webMethods ESB is its elegant tooling”
  • 11. webMethods Integration Platform Supports Business Goals
    • All integration patterns – SOA, EDA, B2B
    • Rapid to deploy - high productivity, reuse, cross platform
    • Sustained delivery speed - Governance
    • Single server to globally distributed solution
    • Proven architecture over 10 years
    • Low cost of management - low number of components, advanced monitoring.
    Service Mediation Service Orchestration Service Enablement
  • 12. What is the webMethods ESB Platform? webMethods ESB (Integration Server) JMS Provider (Broker) Developer & Adapters B2B (Trading Networks & eStandards) SOA Governance + + + + webMethods ESB Platform
    • Profile of Typical Implementations
    • Integration Backbone
    • B2B Integration
    • SOA Enablement
    • webMethods Broker
    • Over 1,200 Customers
    • webMethods Trading Networks
      • Over 1,100 Customers
    • webMethods ESB (Integration Server)
    • Over 1,800 Customers
    webMethods Market Presence
  • 13. Logical Architecture Broker or JMS
    • Integration Server offers invocation by
      • synchronous
      • asynchronous
    • Broker provides
      • request/reply
      • pub/sub
    ESB Integration Server ESB Integration Server Clients Asynchronous Synchronous
  • 14. Stuff we need … 1. Service Enablement 3. Service Registry 2. Service Access/Interaction 4. SOA Governance
  • 15. The Architecture of SOA Governance Service Consumers Registry/ Repository Business Users IT Developers IT Operations Collaboration, Policy Definition, Lifecycle Management, Impact Analysis, Measurement Policies, Service Metadata Service Providers Run-time Governance Design- and Change-time Governance Run-time policy enforcement Service Bus
  • 16. Structure: Multi-Organizational Capabilities enable SOA Federation DMZ
    • Collaboration among autonomous SOA providers and consumers
      • SOA Federation
      • Service promotion between registries and repositories
    • Policy driven access and actions
    • Service lifecycle control
    • Multiple taxonomies
    • Relationships and impact analysis
    App Dev Team Project Team App Dev Team LOB IT Partner Customer
  • 17. Aligning Governance with Traditional SDLCs in development in design in design requested Check Policy X … … requested in design in development in test in production in development requested in test
  • 18. Positioned in Leaders Quadrant of Integrated SOA Governance Technology Sets Magic Quadrant
    • “ SOA governance is about ensuring and validating that assets and artifacts within the architecture are operating as expected and maintaining a certain level of quality”
    Source: Gartner, Inc., Magic Quadrant for Integrated SOA Governance Technology Sets, 2007, L. Frank Kenney, Daryl C. Plummer, December 31, 2007 The Magic Quadrant is copyrighted December 31, 2007 by Gartner, Inc. and is reused with permission. The Magic Quadrant is a graphical representation of a marketplace at and for a specific time period. It depicts Gartner’s analysis of how certain vendors measure against criteria for that marketplace, as defined by Gartner. Gartner does not endorse any vendor, product or service depicted in the Magic Quadrant, and does not advise technology users to select only those vendors placed in the “Leaders” quadrant. The Magic Quadrant is intended solely as a research tool, and is not meant to be a specific guide to action. Gartner disclaims all warranties, express or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose. The Magic Quadrant graphic was published by Gartner, Inc., as part of a larger research note and should be evaluated in the context of the entire report. The Gartner report is available upon request from Software AG.
  • 19. Managed lifecycle enables Trust Lifecycle for Web Services etc (fully customizable) Designed In Test Productive Retired Active Policies™ controlling lifecycle transitions (freely definable)
    • Check WS-I compliance
    • Change access permissions for Test group
    • 3. Send out email to Test group
    • Apply runtime policies
    • Deploy on target endpoints
    • Undeploy
    • Change permissions: service will not be viewable for other organizations anymore
  • 20. Structure: Role-based Design for Customized User Interfaces Design Time Run Time Change Time Developer Business User Architect Service Consumer IT Operations Admin Over 50 pre-defined SOA roles serves multiple stakeholders. Extend and create new roles as needed.
  • 21. Structure: Flexible meta-data model adapts to your Enterprise
    • Custom Asset Types
    • Custom Attributes
    • Custom Relationships
    • Custom Taxonomies
    • Custom Meta Data Views
    • Custom Meta Data Extraction
  • 22. Scale: Unified System Of Record
    • Asset Registry
    • Basic Information
    • Binding Template
    • Company
    • WSDL
    • Asset Repository
    • Schema Documents
    • Documentation
    • Sample Client Code
    • Artifacts
    • Lifecycle Policies
    • Design Time
    • Run Time
    • Change Time
    • SOA Asset Relationships
    • Dependencies
    • Associations
    • Similarities
    • Service Delivery Contracts
    • Consumers
    • Services
    • Policies
    • Deployments
    • Performance Metrics
    • Response Time
    • Successful Transactions
    • Service Faults
    • Throughput
    UDDI SOA Assets Policies Relationships Contracts Performance
  • 23. CentraSite Governance Edition
    • APIs for…
      • Policy Enforcement Points (PEP)
      • Federated Registries / Repositories
      • Service Consumers
      • Design & Development Tools
    Registry Metadata Content Repository CentraSite Governance Edition Repository Engine Repository Interface ebRS JAXR API UDDIv3 Registry & Governance Application
  • 24. Case Study: Financial services institution
    • “ We approved 5 applications to use our service”
    • “ At some times of day the service gets slow – but we don’t know who’s causing it, and we don’t know who is impacted”
    They thought wrong!!! 34 apps used the service
  • 25. Visibility with Insight Step 1: Install Insight Agents Insight Agents add less than 5% overhead even under the most stressful situations
  • 26. Visibility with Insight Step 2: Let the Application Run Insight automatically discovers call flows and maps dependencies end-to-end with no custom coding or configuration
  • 27. Visibility with Insight Step 3: Slice & Dice Data
  • 28. Enterprise-scale SOA and BPM
  • 29. Software AG Positioned as a Leader in the Integration-Centric BPM Suites Market
    • “ Software AG received high scores across the board”
    Source: Forrester Research, Inc., The Forrester Wave™: Integration-Centric Business Process Management Suites, Q4 2008, October 6, 2008 The Forrester Wave is copyrighted by Forrester Research, Inc. Forrester and Forrester Wave are trademarks of Forrester Research, Inc. The Forrester Wave is a graphical representation of Forrester's call on a market and is plotted using a detailed spreadsheet with exposed scores, weightings, and comments. Forrester does not endorse any vendor, product, or service depicted in the Forrester Wave. Information is based on best available resources. Opinions reflect judgment at the time and are subject to change.
  • 30. SOA Governance -> Solution Governance
  • 31. Security Policies: Machine Enforceable Runtime Intermediary Authorization Policy What rights are granted? Runtime Intermediary Authentication Policy How are service consumers authenticated? Runtime Intermediary Encryption Policy How are messages secured? Registry Registry Access Control Who designs services? Who can change Policies? Requirement Repository Repository Access Control Enforcement Point Policy
  • 32. Reuse Policies: Machine Enforceable Service Delivery Contracts™ (Contract Manager) Reliability Can’t Trust Services? Can’t Achieve Interoperability? Can’t Understand how to Use Services? Can’t Find Services? Requirement Validation (Policy Manager) Validation Information Manager (Repository) Documentation Catalog, Search and Taxonomy (Registry) Service Registration Enforcement Point Policy
  • 33. Agility Policies: Machine Enforceable Lifecycle Manager (Approvals) Approvals Will this change break anything? Policy Standards Enforceability How do I know if policies be enforced? Governance Rules Engine Automation How do I automate change processes? Reporting Dashboard Metrics Key performance indicators (KPIs)? Who will be affected by the change? Requirement Change Manager Notification and Impact Analysis Enforcement Point Policy
  • 34. Organizational Policies: People Organizational Regulatory Policy What regulatory issues exist? Competency Center Policy Policy Who authors policies? Organizational Federation Policy Which policies apply where? What incentives are there for reuse? Who will pay for services? Requirement Organizational Incentives Policy Organizational Funding Policy “ Enforcement Point” Policy