Service-Oriented Architectures fo Enterprise Scale Systems
Vocational qualification
In Carshalton
Description
-
Type
Vocational qualification
-
Location
Carshalton
-
Duration
5 Days
Suitable for: This course is aimed at systems and business analysts and architects. Attendees are assumed to have an understanding of the aims and approaches of IT Systems Analysis and Business Process Modeling and Engineering as well as a basic understanding of XML. The course is oriented towards analysis and design as opposed to programming and implementation details.
Facilities
Location
Start date
Start date
Reviews
Course programme
The course combines intensive seminar presentations with small group discussion workshops
The course covers SOA and the underlying web service technologies typically used in the deployment of SOA systems. A key part of the course is that covering the analysis and design of SOA systems. Security issues are also discussed. As befits an architect and analyst oriented course the following important areas are also explored
- Risk and cost-benefit analysis
- Staff training
- Governance
- Testing and quality control
Course Contents
Foundations of SOA and Key Business Concepts
- Objectives
- SOA Motivation
- SOA Goals
- SOA in context
- SOA Job Role Impact
- The "service" viewpoint in Service Oriented Architecure
- What is a service?
- Example services
- Service actors
- The SOA Umbrella
- SOA and Business Process Management (BPM)
- BPM Value Add
- SOA Governance
- SOA Governance Model
- The Value of Transitioning from Applications to Services
- Is this a New Concept?
- Service Orienting the Enterprise
- Service Characteristics
- About Services in SOA
- Contract-driven software
- Elements of a Service
- What is a Web Service?
- How Web Services Work
- Web Service Standards
- SOA Standards
- SOA Capabilities
- Service Oriented Thinking
- What is layering?
- SOA layers
- Common Layers
- Auxiliary Layers
- Digesting the Layers
- The Application Service Layer
- The Business Service Layer
- The Orchestration Layer
- Layering Rules of Thumb
- SOA User Interface
- Portal Site's Context Awareness
- Web 2.0 Data Aggregation
- Reducing integration expense
- Analysis of Integration costs - an illustration
- Ripple effect of changes
- The value of SOA layering
- SOA reduces integration costs
- Increasing asset reuse
- Asset reuse illustration
- Increasing business agility
- Business Agility Illustration
- Traditional EAI Approach and associated problems
- Change Flow Using Legacy Approach
- SOA Agility
- Build the Services
- Build the Process
- We Can Easily Change the Process
- Reducing business risk
- Risk reduction illustration
- SOA Eases Compliance Risk
- Other Advantages
- Business Advantages
- Hasn't this been said before?
- ROI Quantification Hurdles
- Some real world examples
- What is a Pattern?
- SOA and the ESB Pattern
- Loose Coupling
- Service Invocation
- Business Process
- Data Integration
- Enterprise Service Bus (ESB)
- Legacy System Integration
- Unsupported Protocol
- The Role of ESB in SOA
- ESB: Software Artifacts
- Business Process
- Business Process: Example
- Minimum ESB Capabilities
- Integration
- Communication
- Service Interaction
- Management
- Security and ESB
- XML Schema - Foundations
- What is an XML Schema?
- Role of XML Schema in SOA
- Creating a Schema File
- Defining a Simple and Complex Elements
- Defining Element Attributes
- Referring to an Element From Another Element
- Defining Abstract Data Types
- Adding Restrictions
- Referring to a Schema from an XML Document
- Validating the XML Against the Schema
- WSDL - Web Services Description Language
- WSDL Principles
- WSDL Document Tags
- WSDL Namespaces
- Sample WSDL Document Structure
- <definitionss>
- <import>
- <types>
- <message>
- <portType>
- <operation>
- One-way <operation>
- Request-Response <operation>
- Solicit-Response <operation>
- Notification <operation>
- Modeling Simple Operation
- Modeling Complex Operation
- Modeling Complex Message
- <binding>
- <binding> Syntax
- SOAP Binding Example
- <service> and <port>
- More on <port>
- WSDL SOAP Binding Extensions
- soap:binding
- soap:operation
- RPC or Document Style?
- WSDL API for Java
- WSDL API for .Net
- SOAP - Simple Object Access Protocol
- SOAP in the Protocol Stack
- SOAP Components
- SOAP HTTP Request Example
- SOAP HTTP Response Example
- Message Envelope
- The Header Element
- Header Attributes
- SOAP Body
- SOAP Fault
- Communication Style
- RPC/Encoded Style
- RPC/Literal Style
- Enabling RPC Styles
- Document/Literal Style
- Document/Literal Wrapped Style
- Details of the Wrapped Style
- Enabling Document Literal Style
- SOA Adoption
- Adoption Stages
- Managing Services
- SOA Service Life Cycle Overview
- Discovery Phase
- Analysis and Design Phase
- Implementation Phase
- Deployment Phase
- Monitor Phase
- Retirement Phase
- What is SOAD?
- OOAD Principles underlying SOAD
- Abstraction
- Abstraction in SOAD
- Encapsulation
- Encapsulation in SOAD
- Modularity
- Modularity in SOAD
- Hierarchy
- Hierarchy in SOAD
- Why pure OOAD is not enough
- Abstraction
- Granularity
- The Need for Loose Coupling
- The SOAD Methodology
- The SOAD Methodology Steps
- Stage 1: Requirements Gathering & Process Modeling
- Stage 2: Service Identification
- Stage 3: Service Implementation
- Stage 4: Process Implementation
- SOAD Stages and SOA Lifecycle
- Stage 1: Business Modeling and Use Cases
- Foundations of Business Process Modeling
- SOA and Business Process Model
- Process Modeling and Business Process Use Cases
- Modeling the Business Processes
- Use Case and Business Process
- Trading Partner Design Pattern
- UML Use Case Analysis
- Best Practices
- Stage 2: Service Identification
- The Service Model
- Developing a service model
- Service model granularity
- Identifying Services
- Specifying the service interface
- Producing the Service Specification
- Functional Areas of the Business (a.k.a. Subsystems)
- Services Belonging To These Functional Areas
- Functionalities Belonging To These Services (User's Standpoint)
- Documenting Service Hierarchy
- Specification of the Artifacts
- Service Contract Templates
- Service Design Best Practices
- Stage 3: Service Design and Implementation
- Service Development strategies
- Top down or not ?
- OOAD applied to Service Development
- Identifying System Level Use Cases
- Finding Classes and Relationships from Use Cases
- Refinement
- UML diagrams and UML notation
- Data Mapping
- Interface Mapping
- Best Practices
- Service Development strategies
- Stage 4: Business Process Implementation
- Business Process Diagram
- BPEL
- Variables
- Partnership
- Example: A Buy-Sell Partnership
- Modeling Partnership in BPEL
- Simple Activities
- Invoke Activity
- Structured Activities
- Lifecycle of Process Development
- Phase II Process Definition Details
- Phase III Compilation Details
- Phase IV Deployment Details
- Phase V Business Process Execution
- What Is a Good Process Design?
- Integration Patterns
- Adaptors as a strategy for integrating systems
- Resource Adaptors
- Custom Adaptors
- Communication Modes and Adaptors
- Outbound
- Inbound
- Operational Data Replication Basics
- SOA and Data Basics
- Data Publishing Events
- Modeling Events
- Handling Events in a BPEL Process
- Data Mediation
- Data Formats
- Generic Data Model
- Mapping Data
- Loading Data
- Extract Transform Loading (ETL)
- ETL and SOA
- Data Federation
- Asynchronous Behavior in an SOA context
- Basic Messaging Patterns
- Callback Style Communication in SOA
- Implementing Callback
- Correlation Set
- Uses of Callbacks
- Non-Blocking Call in SOA
- Parallel Activity
- One-way Non-Blocking Call
- Assured Delivery
- Callback Style Communication in SOA
- SOA Client Behavior
- Client Multithreading
- Handling errors in a service
- Fault handlers and the raising of Faults in a process
- Transactions in the SOA context
- short lived processes
- long lived processes
- Compensation
- in a microflow
- in a long running process
- compensation handlers
- compensation guidelines
- Key concepts and the Need for an SCA
- Identifying Service Components
- Assembling services
- Imports and Exports
- Service Implementation Types
- Costs, Risks and Challenges
- Training
- Emerging Standards
- Immaturity of Server Runtimes
- Newer methodologies
- Strategic Role of IT
- governing IT
- ITIL (IT Infrastructure Library) and management of IT activities
- ICTIM (ICT Infrastructure Managment) - concepts and processes
- COBIT - Control Objectives for Information and Related Technologhy
- SOA Governance
- Issues
- Models
- Project Roles
- Risk Management
- Processes
- Policies
- Metrics
- Best Practices
- Need for and purpose of Service Registries
- Duties, roles and tasks of a registry
- Publishing
- Discovery
- Dynamic Discovery
- Management
- Enforcing Governance Lifecycles
- Overview
- Which SOA components to test?
- Challenges in SOA testing
- Layered component testing
- Phased testing
- Structure of the testing framework
- Unit testing
- Unit testing of a web service
- Verification scenarios
- Unit testing data maps
- Unit testing business processes
- Integration test teams
- Service integration test team
- Process integration test team
- Non-functional testing
- Performance testing
- Security testing
- Interoperability testing
- Process state persistence testing
- Process versioning testing
- Fundamentals
- Security issues in traditional systems
- Security issues in loosely coupled systems
- SOA Security issues
- Security Stack - Web Services
- Security Stack - other services
- Security Patterns
- Service Bus security
- Service Bus security layers
- Application-manged security
- Security as a service
- Reverse Proxy
- ESB Gateway
- Security Layering
- SOA layers
- Policy-driven security
- PEP/PDP in practice
- Loosely coupled security layer
- SES/SDS in action
- layering and service granularity
- Security service granularity
- Process centric security
- Patterns - an overview
- SOA patterns
- Messaging Channel Patterns
- Message Type Pattern
- Deferred Response in SOA
- Message Routing Patterns
- Message Transformation Patterns
- What is an AntiPattern?
- The Silo Approach
- Fine Grained Service
- Point-to-Point Communication
- Stateful Services
- Types of Software Needed to Support SOA
- Oracle SOA Suite
- IBM Software Offering
- IBM WebSphere Process Server
- IBM IT Service Management (ITSM) Tools
- TIBCO BusinessWorks
- TIBCO SmartMapper
- WebMethods Fabric
- webMethods: Enterprise Service Platform (ESP)
- webMethods: Business Process Management (BPM)
- webMethods: Business Activity Monitoring (BAM)
- webMethods: Composite Application Development
- WebLogic Integration
- Microsoft BizTalk Server 2006
- Windows Workflow Foundation (WF)
- The SOAD Methodology Steps
Service-Oriented Architectures fo Enterprise Scale Systems