UNIT-IV��SOA-Governance� By� Dr.E.M.Roopa Devi

SOA Governance

• SOA Governance is a model of establishing policies, controls and enforcement mechanism within the contest of the activities and constructs associated with SOA implementation

​

Drivers for SOA

• Implementation of best practices
• Business and IT alignment
• Real-time service visibility
• Reduce risk
• Measurable ROI
• Realize service reuse
• Track and communicate progress of SOA implementation

Strategic Architecture

• Process
• Definition of processes that lead to the formulation of business,application,information and infrastructure architecture
• Technologies
• Establishment of standards for technologies used for development and depolyment
• People
• Governance team with architects and key stakeholders from across the enterprise with representation from senior management

Development of Services

• Governance of service Design
• Governance of service Execution
• Governance of service Modification

Technologies for SOA Governance

• The following capablities are needed to implement design time and run time governance
• Registry and repository
• Policy definition and enforcement
• Service monitoring and management

SOA Security

• The key capabilities for securing interactions between service providers and service consumers include
• Authentication
• Authorization
• Audit
• Identity
• Confidentiality and integrity

SOA Implementation

• SOA implementation involves two categories
• Strategy
• Development

Strategy

• Strategy for SOA in an enterprise is done in the context of business and IT of enterprise.Hence all the steps involved in defining an enterprise wide IT strategy.
• It has three steps
• Form team for strategy formulation
• Due Diligence
• Finalized Approach
• Strawman architecture
• Interview/workshop schedule

• AS-IS Assessment
• Understanding of business processes of the enterprise
• Technical details of IT applications and infrastructure
• In delivering to the business objectives
• To-Be Strategy
• To-Be strategic architecture
• Roadmap for implementation
• Governance model
• Business case

SOA Development

• On receiving the approval from the senior management of the enterprise, the next category of activities in SOA implementation are initiated
• It has five steps
• Transition Planning
• Transition plan
• Technology Decisions
• Architecturally significant scenarios
• Strategy Documents

• Validation
• PoCs
• Validated
• Decisions
• Revised Transition plan
• Business Process Model Creation
• Business Process Model
• Service Development
• Activity Services
• Business Process Services
• Client Services
• Data Services

• Service Deployment and Monitoring
• Orchestrated Business Processes implemented with services
• Trends in SOA may be viewed under 3 categories
• SOA adoption
• Technologies in relation to SOA
• Advances in SOA

SOA Adoption

• SOA adoption depends on the following critical factors
• Business alignment
• Organizational change management
• Communications
• Trust
• Architecture
• Scale and sustainability
• Governance

​

Technologies in Relations To SOA�

• Business process Development(BPM) is discipline that automate and optimize business processes and their performance in an enterprise.
• BPM products are of two types
• Human –centric suites that evolved from imaging technology
• Integration-centric suites that grew out of enterprise application integration tools

​

​

SOA and Web2.0�

• It represents a range of technologies that include
• Asynchronous javascript and XML(AJAX)
• Representational state Transfer(REST)
• JavaScript Object Notation(JSON)
• Really Simple syndication(RSS)
• Mashup
• Weblog
• Wikis

• SOA and Open Source
• Cost and simplicity therefore have been the main reason for a variety of open source products being available for implementation
• SOA Appliances
• SOA Applicances are XML devices that handles specific tasks related to messaging layer efficiently
• SOA Applicances provide an option to parse SOAP and XML at message level in hardware

​

​

Advances in SOA

• Event Driven Architecture
• EDA in conjuction with SOA may be used for
• Asynchronous communication between services
• Communication between workflow in business processes
• Processes where req/res based communication may not be suitable
• Complex Event Processing

​

Complex Event Processing�

• Invoking components in an asynchronous manner to events produced in EDA is to detect patterns in the events generated to bring intelligence to business applications in real-time.
• In order to be able to detect patterns in the events generated, CEP applications use rule engines to filter and aggregate events.

Software as a service(Saas)�

• Service consumer only pays for the services consumed.
• “pay-as-you-go” model is attractive for small and medium business
• General requirements of a platform to support Saas are as follows
• Hosted platform
• Multi-tenant
• Subscription –based business model
• Secure and performing
• Services-based integration model
• Parameterized
• Multiple delivery channels
• SLA based service

​

SOA Technologies-PoC

• The PoC implements the following functionality of a Loan Management System
• Three types of actors interact with LMS
• Customer
• Loan Officer
• Loan Manager
• Use cases of LMS
• Request Loan, Approve Loan, Confirm Loan

​

Architecture of LMS

• Presentation layer-mode-view-controller components
• Business layer-business delegate components and façade components
• Service layer-service proxy for loan service
• Integration layer-ESB and process orchestration engine

​

​

Process Orchestration

• Process orchestration engine usually provide visual tools to specify orchestration
• Create a new project in ActiveBPEL
• Import required WSDL files into the project
• Create a new BPEL process
• Drag and drop operations from web references
• Create assign tasks wherever there is need for assigning data
• Link these activities in BPEL editor

​

• Create correlation set and assign it to receive activities
• Create a deployment descriptor using the wizard available in the IDE and deploy onto the server using Export Wizard.

SOA-Best Practices

• The best practices are classified under three categories
• SOA Strategy
• SOA Development
• SOA Governance

SOA Strategy

• Establish a business case
• Adopt an enterprise wide view
• Start small grow big
• Senior management commitment
• Establish SOA guidelines
• Educate key stakeholders on paradigm shift with services model
• Ensure cloud is part of the architecture vision of enterprise
• Define a roadmap for implementation

SOA Development

• Externalize business processes
• Create a business process model
• Develop a PoC to validate technology stack
• Leverage open source to keep the cost down
• Define a reference model and reference implementation
• Architect and develop services that provide and manage master data
• Ensure team members in different roles
• Take advantage of services model to parallelize development
• Establish mechanism to publish and reuse services
• Consider cloud infrastructure to improve scalability of development environment

SOA-Governance

• Establish a governance team
• Identify a champion to lead the governance team
• Constitute an architecture group
• Ensure that the policies for security and change management are defined and operationalized
• Monitor and measure SOA results against projected benefits
• Ensure SOA governance takes into account cloud services
• Conduct service delivery benchmarking to understand health of SOA
• Build skills in SOA governance tools and technologies