|
uwcf |
Understanding Windows Communication Foundation (WCF) |
14 heures |
A two-day instructor-led course to provide participants with the knowledge to understand and help develop distributed applications using WCF 4 and Microsoft Visual Studio 2010. At the end of the course students will have clear indication on how and when to use the various settings and techniques.
Service-Oriented Architecture
SOA - Definition, scenarios and benefits
WCF and SOA
First steps into Windows Communication Foundation
The Service Contract and the Data Contract
The implementation of the Contract
Hosting a WCF service: why and how
How to consume a service
The endpoints
The ABC (Address, Binding, Contract)
Behaviors>
Sharing a contract
Proxy creation through Visual Studio
When and how to use the Channel Factory
Hosting a WCF service
Understanding the role of the host
The available options for hosting (custom vs. commercial) and how to choose
Hosting on IIS, WAS, AppFabric
Long running processes and Windows services hosts
Creating a custom host - why and how
Service host configuration and monitoring
Contracts, endpoints and behaviors
Contract types
The central role of bindings
Why having multiple endpoints
Interoperability
Default endpoints
The communication model
SOAP vs REST
Messaging patterns, how to choose
Instancing and Concurrency, combining the options
The protocols
Understanding the channel stack and the protocols
Reliability
Improve service reliability by using transactions, queues, and reliable messaging
Using routing
Discovery and announcements
How to discover and make services available through WS-Discovery
Testing and troubleshooting
How to individuate errors and how to deal with them
Exceptions vs Faults
Using Fault Contracts
How to write custom error handlers and why
Message logging and tracing
WCF services and security
The holistic view
Authentication and Authorisation
The security model
Transport and Message security
Extending WCF
How and when to extend WCF through behaviors, inspectors and host extensions
|
|
soamgrdev |
SOA for Managers & Developers |
35 heures |
This course is intended for developers and architects. After an in introduction to SOA and the purpose for its implementation the program is to cover its technical foundation through XML, WSD and SOAP and to proceed to hands on implementations with the different Java Libraries. This course should be the first when introducing SOA into any organization as it sets the basics for SOA enterprise wide architecture, integration patterns and ESB (Enterprise Service Bus) solutions.
SOA & Impact on Business
SOA Concepts
Anatomy of an Enterprise
IT Nightmare
Service Oriented Architecture
Componentization and Reuse
Benefits of Service Orientation
Defining SOA
Aligning the Enterprise
What s a Service?
Service Actors
Service Layering
Layers of Service
What Is Layering?
SOA Layers
Layering Illustration
Data Storage Layer
Application Logic Layer
Adapter Layer
Application Service Layer
Business Service Layer
Orchestration Layer
Aux: Data Service Layer
Aux: Security Service Layer
Layering Concepts
Layering Rules of Thumb
SOA Service Life Cycle
SOA Adoption
Adoption Stages
Managing Services
SOA Service Life Cycle Overview
SOA s Circle of Life
Discovery Phase
Analysis & Design Phase
Implementation Phase
Deployment Phase
Monitor Phase
Retirement Phase
How a Requirement Becomes a Service
How a Requirement Becomes a Service
Requirements Discovery
Analysis and Design
Development
New requirements
Discovery
Analysis & Design
Service Developments
Technical Foundations XML, WSD and SOAP
XML foundation for web services
XML Information Set
XML Namespaces
XML Schema: Types & Message Structures
WSDL
Anatomy of a Web Service Contract
Abstract Description Design
Concrete Description Design
WSDL and WS-*
WS-Policy o Policy Structure o Composite Rules o Attaching Policies to WSDL
WS-Addressing
SOAP Message Design
SOAP Message Structure
Nodes and Roles
SOAP Intermediaries
Fault Messages
SOAP & WS-*
WS-Security
WS-Transaction
Advanced XML schema (optional)
Message Flexibility, Type inheritance, Composition
Reusability, Relational Design, Industry schema
Modularization, Extensibility
Advanced WSDL (optional)
Message Dispatch, Service instance identification
Policy centralization
Custom policy assertion
Versioning
Versioning XML schema
Versioning WSDL contracts
Service implementation with Java
Java API for XML Processing (JAXP) (optional is attendees are familiar with JAXP)
DOM, SAX, & javax.xml.parsers
STAX & java.xml.stream
XSLT & javax.xml.transform
Java Architecture for XML binding (JAXB)
Overview and Architecture
Generating Java Classes from XML Schema
Customizing Generated Java
Generating XML Schema from Annotated Java Classes
Web Services, WSDL, JAXB
SOAP with Attachments API for Java (SAAJ)
SAAJ Overview, Message Structure and API
Creating/Sending Messages
DOM Overview
Using DOM with SAAJ
Soap Handlers
Java API for XML-Based Web Services JAX-WS
Related specifications: JAXB, SOAP, WSDL, WS-I Basic Profile 1.1, Annotations, JSR 109, Web Services Security (JSR 183)
WSDL to Java and Java to WSDL Mapping
Building clients with generated stubs
Asynchronous clients with callback or polling
MessageContext and WebServiceContext
Handler for payload and protocol
Engaging of handlers on a service, a port or the protocol layer
Non-HTTP Transport
Message Access and Session Management
Handling Binary Data (optional)
Overview and Issues
Default Handling
MTOM Overview
Using MTOM in Services and Clients
Using DataHandler
Value of SOA / ROI
SOA Value Proposition
The Value of SOA
Reducing Integration Expense
Integration Costs Illustration
Ripple effect of changes
Value of SOA Layering
Integration Costs
Asset Reuse
SOA Economics/ROI
Increasing Business Agility
SOA Agility vs Traditional EAI Approach
Reducing Business Risk
SOA Eases Compliance Risk
Business Advantages
ROI Quantification Hurdles
|
|
wsbnp |
Web Services Basics for Non-Programmers |
14 heures |
This course is intended to provide an understanding on how to use, debug and manage Web Services from a non-developer/programmer perspective.
Overview of Web Services
Why do we need Web Services?
Service-Oriented Architecture Principles (SOA)
HTTP and XML - what is the whole buzz about?
Simple Object Access Protocol (SOAP)
Web Service Description Language (WSDL)
Universal Description, Discovery and Integration (UDDI)
The WS-* profiles - what are these?
REST
The XML Technology
Why XML with Web Services?
The XSD Schema
Data representation in XML
XSLT based XML transformations
HTTP / XML Web Services case study
The SOAP
Messaging Model
Namespaces
SOAP over HTTP
The SOAP Envelope
The Message Header
The Message Body
SOAP Faults
Attachments
Web Services Description Language
Web Services as Component-Based Software
The Need for an IDL - history of Distributed Computing
Web Services Description Language
WSDL Information Model
The Abstract Model -- Service Semantics
Message Description
Messaging Styles
The Concrete Model -- Ports, Services, Locations
Extending WSDL -- Bindings
Service Description
Handling Binary Content
The WS-I Attachments Profile
Using base64Binary
MIME Attachments
Other technologies overview
REST
JSON
PHP Serialization
ESB
Integration Platforms
|
|
sysserarch |
Architecture Systèmes et Service - Architecture Microservices |
14 heures |
Building complex enterprise applications is very challenging in an ever-changing environment.
Changes in the integration between services or systems will trigger changes in the design of the system. This course covers how to design maintainable, fit to the size and purpose of your organisation service and systems architecture and practical infrastructure.
This course covers common problems with building the landscape of distributed apps, starting from integration problem, infrastructure and modern approaches, to solving complexity issues.
This course explains the pros and cons of each solution (e.g. traditional SOA vs Microservice architecture), available tools (mostly open-source) supporting the development and maintenance, etc..
Course Format
It is mostly discussion (with limited presentations).
Quick overview of traditional approaches
Monolithic systems
System of Systems
Early service orientation (EAI, CORBA, etc...)
Early webservices (SOAP, etc...)
Service Oriented Architecture (SOA)
Microservices
Desing concepts and tradesoff
Flexibility and Complexity tradeoff
Cohesion, Coupling
Hidden dependencies vs explicit dependencies
Small system vs Big System
Module/Component vs Service
Generic SOA
Benefit and Costs of SOA
Successes and failures in implementing SOA
Messaging and ESB
Infrastructure and tools supporting SOA
Microservices and implementation of SOA - concepts
Do one thing and do it well
Microservice vs Service
DevOps
Continuous Deployment and Delivery
Lightweight protocols
Microservice protocols and tools
HTTP, JMS, AMQP, Websockets, JSON, etc...
Deployment
Containers (Docker, K8N, LXC, etc...)
Configuration Management (Ansible, etc...)
Monitoring and Management
Infrastructure
Cloud and Auto Scalability
Microservice redundancy and fail-over
Performance scalability
Auto scalability
Implement: OpenStack, AWS, etc....
Real problems
Complexity of ecosystem
Network Performance
Security
Deployment
Testing
Nano-services
|
|
soaarchmgr |
SOA for Architects and Managers Overview |
14 heures |
This course has been created for managers and architects planning to implement or currently implementing SOA solutions. It gives the overview of pros and cons of SOA and explains when, why and which part of SOA you should use.
Some of the questions the course can answer:
What are the benefits of employing SOA
What are the risks associated with the SOA approach
What are the trade-offs
How to assess potential profit with SOA
What real business case studies has been already made
When and to what extent SOA should be implemented
What are simplification and decomposition benefits
How to migrate from existing solutions to SOA and why migration to SOA does NOT require rebuilding the whole existing infrastructure
How to extend legacy applications with SOA
What are the existing SOA suites and platforms
A Service Oriented Methodology
Introduction to a SOA adoption roadmap
Three analysis approaches
Service oriented analysis
Advantages of SOA
Traditional EAI Approach
Problems With Traditional EAI Approach
Enter Service Oriented Architecture (SOA)
We Can Easily Change the Process
Changing Flow Using Legacy Approach
Replacing an Application
Other Advantages
Business Advantages
Adoption Stages
SOA Past and Present
From XML to Web Service to SOA
How SOA was done before
Emerging standards for SOA
Compare SOA with other architectures
What is service oriented architecture?
What is SOA?
Creating a common understanding of SOA
The evolution of SOA
Introducing the concepts of services and SOA
Design principles of SOA
The relationship between SOA and web services
The advantages and risks of SOA
Introduction to modelling and UML
Why use models with SOA
The difference between model and methodology
Why use the Unified Modelling Language?
Identifying business processes
Notation, Patterns and Methodology
Which Methodology to choose?
Introduction to Business Processes
How a collection of services performs a task
Simple request response interaction
Complex interaction involving many services
Need for a coordinator service emerges
Birth of orchestration or business process
Composing processes using Business Process Execution Language (BPEL)
BPM based solutions for orchestration
Example business processes
Web Services
Basic web services elements
Core web services standards stack
The Importance of WSDL
The design of SOAP
The use of registries via UDDI
The basic concepts of service orientation
Distributing Services Across a Network
Aligning functional and non-functional requirements
The role of Intermediaries in Service Networks
Introductions to WS-* extensions
SOA tenets
Modelling SOA building blocks
Using UML to analyse and design interfaces
Generating a domain model
Implementing and realising Use Cases
Showing web service collaboration
Usage of communication diagrams
Enterprise Service Bus (ESB)
Objectives
Service Invocation
Legacy System Integration
Web Services to the Rescue
The role of ESB in SOA
Security and ESB
Process Driven Services
Service layer abstraction
Introduction to business process layer
Process patterns
Orchestration and choreography
The use of WS-BPEL for process automation
Service Oriented Reference Model
Reference models and reference architectures
The IMPACT SOA reference model and architecture
SOA vendors and their relationship with SOA
SOA support in .NET and Java EE platforms
Layered Architecture
The layers pattern
Classic three-tier architecture
Connecting to the domain layer
Linking to the User interface
Using packages to decompose a system
Avoiding mutual dependencies
What is layering and why do we need it?
Application service layer
Business service layer
Orchestration service layer
|
|
soabusi |
SOA: the Business View |
14 heures |
What is service oriented architecture?
Creating a common understanding of SOA
The evolution of SOA
Introduce the concepts of services and SOA
Why businesses need to innovate
SOA is not about web services
How SOA enables innovation
The Business Impact of SOA
The benefits of employing SOA
Review of common business goals
The risks associated with the SOA approach
Evaluating trade off strategies
SOA Roadmap
SOA maturity model
The SOA adoption roadmap
SOA expansion stages
Start with the business
Defining a business component model
Identifying differentiators and commodity
The different Service types
Categorizing services
Enterprise services and Process centric services
Data centric services and Logic centric services
Intermediary services and application front ends
Basic services
Modelling SOA building blocks
Using UML to analyse service requirements
Generating a domain model
Service oriented analysis and design overview
Identifying basic services
Usage of sequence and activity diagrams
The need for a structured analysis process
SOA Governance
Aligning IT and Business through governance
The importance of a repository
Dependencies between services and business components
Governance is not management
Metrics, KPI's and continuous improvement
Who sits on the SOA Board?
A Service Oriented Reference Model
Reference models and reference architectures
The OASIS reference model and architecture
SOA vendors and their relationship with SOA
SOA support in .NET and Java EE platforms
Case Studies
A telecommunications firm
The Vision, the strategy
Choosing a Pilot project -setting expectations
Setting up the SOA board
Establishing a business component model
Evaluating the Pilot's results and KPI's
Next Steps
Avoiding the 'big bang' situation
A phased approach with incremental improvements
Understanding the SOA maturity model
|
|
soad |
Service Oriented Analysis and Design |
21 heures |
During this course, we give an overview of the role of the UML modelling language in the context of SOA. We will use industry-standard modelling tools and you will learn the capabilities of UML in the area of service orientation. You will gain insight into the added value of using service contracts as part of your development process.
Setting the right scope
Modelling profile for SOA
Guidance to be added to RUP
Developing service-oriented solutions
Choosing the level of abstraction
The WS-* specifications
UML for SOA: tangible advantages
Quality-of-service
Manageability
Using a UML Profile
UML profile for software services
OMG profile document
Using tools conforming to the profile
Guidance on SOA architecture & design topics
Extensibility mechanisms
Key concepts and themes
What is SOA?
What kind of architectural style to choose?
The "pipe and filter" style
Constraints on data types
The development lifecycle
Providing an appropriate level of abstraction
Key themes addressed within RUP for SOA
Service identification and specification
Constructing a model of a service
WSDL-defined services
Developing service specifications
Defining service providers
Determining the granularity of a service
A behavioural specification
Policy specification
Defining candidate services
Refactoring services
Managing a service portfolio
Applications as a dynamic entities
A portfolio of available capabilities
Process time-binding
Run-time binding
WSDL, XSD and WS-Policy
The service portfolio management process
Configuring an SLA for a web service
Partitioning service-oriented solutions
Managing the models
Categorizing the elements
Different stakeholders reviewing the model
Using packages
Representing views into the model
Composite structure from UML 2.0
Using "parts" and "connectors"
Partitioning the managed services
RUP Update
The RUP update for SOA
Models of a service-oriented solution
New and updated workfare
Guidance for SOA solution construction
Identifying services
Responsibilities of the software architect
Service design
Designer tasks within analysis & design
New and updated artifacts
New and updated guidelines
Managing message attachments
Designing messages
Assuring consistency of message schema
Service data encapsulation
Relationship data schema - service boundaries
Service mediation
State management
The merits of stateful and stateless services
Managing resource state
Going from services to service components
The traditional design/implementation model
Message-centric design
Focus on the service domain
Domain engineering
Applying object-oriented analysis and design
Producing highly reusable models
The traditional business-to-business arena
EDI standardization
Hybrid message and service-centric approach
Use case analysis
Documenting requirements
Using business process models
Non-functional requirements
The requirements database
Service-centric design
Exposing functions expected of the business
Exposing operations of service providers
Making intuitive service interfaces
Service-centric modelling
Use-case driven approach
Understanding the needs of the actors
The project goals -from a business standpoint
Involvement of the software architect
Policy information, required by service consumers
The business executive role
Interaction with the back-end system
Connecting service to implementation model
Refining the service model
Addressing performance concerns
Collaboration-centric design
Collaborating services
Process view of the services
Traditional business modelling
Fulfilling roles in the collaboration
Partner Interchange processes (PIPs)
OAGIS standards
Process-centric mindset
The "business vs. IT gap"
"Black box" activities
Defining key performance indicators (KPIs)
Versioning and publishing a model
Producing metrics for monitoring
Choreography language
Business process execution language (BPEL)
Monitoring the services
Conclusions
When to use UML and the RUP for SOA
How to plan the different phases
When does the project end?
What about SOA 2.0?
What's next?
|
|
soa2eda |
SOA 2.0 and EDA |
14 heures |
Our ED-SOA training focuses on building and analysing an architecture framework that builds upon the SOA reference architecture. Services are used as event generators, signifying a problem or impending problem, an opportunity, a threshold, or a deviation.
SOA and EDA
The fusion of SOA and EDA into ED-SOA
Combining events and services
Business rule processing
Transforming messages
Solicit-Response
Different ways of thinking about problem solving
WS-Eventing
Potential overlap between SOA and EDA
Standardizing event processing rules
Fundamental EDA Characteristics
Decoupled interactions
Publish/Subscribe messaging
Many-to-many communications
Event-based triggers
Asynchronous interactions
How does ED-SOA support faster responses?
Event-driven Architecture
Event processors
Using a dashboard
Event monitoring
Event infrastructure
Propagation of events
Kicking off a business process
SOA Action Framework
Triggering actions
Subscribing to an event
The ESB and event propagation
Complex event processing
Event consumers
Event producers
Storing and forwarding events
Facilitating system responsiveness
Event processing Styles
Simple processing
Handling real-time flow of work
Reducing lag time and cost
Stream processing
Real time flow of information
Enabling in-time decision making
Complex processing
Inferring event occurrence
Event correlation
Sophisticated event interpreters
Responding to business anomalies
Enterprise Service Bus (ESB)
Standard-based connectivity
Transport services
Message routing capabilities
Message transformation features
Event services
Mediation capabilities
Protocol mediation
Content mediation
Configuring a simple ESB solution
Pervasive integration
Reliable integration
WS-Eventing
Delivery modes
Subscription managers
Notations and terminology
Subscription messages
Notifications
Faults
Security considerations
Message security
Access control
Complex Event Processing (CEP)
CQL - Complex Query Language
Event Attributes or properties
Granularity of events
Using timestamps
Creation time and arrival time
Event processing language (EPL)
Event processing agents (EPA)
Composite events
Derived events
Event source and event channel
SOA event Patterns
Discovering event patterns
Commands
Queries
Event pattern monitoring
Monitoring for control of process execution
Event cascade
When to use event patterns
Event sourcing
Structuring the event handler logic
Reversing events
SOA events and the SLA
Importance of a Service level agreement
Keeping services within the agreement
Instances violating the SLA
Priority for executing risk assessment steps
Building autonomous processes
Monitoring and event pattern triggering
Dependence between events
Software Platform for ED-SOA
Software Tools for ED-SOA
Event-optimized runtimes
Supporting bulk application of rules
Dynamic data-driven event definition
Agents and streams
Guaranteed pause times
Sensors and event-processing agents
Responders
Conclusions
Building of processes facilitated by ED-SOA
ED-SOA constructed using BPM
CEP principles as component of ED-SOA
The increasing quest for control of BP
Real time autonomous operation
Gathering business intelligence from events
|
|
soaovv |
SOA Overview |
14 heures |
Day 1:
Distributed computing
SOA and other architectures
SOA reference model
SOA principles
SOA Building blocks
Day 2:
SOA Methodologies
SOA Maturity model
XML Namespace
XML infoSet
XML Schema
WSDL
WS-Security and other WS
|
|
anafmd |
Applying NAF with MAGICDRAW |
21 heures |
This is a 3-day training covering principles of modeling, NAF, UPDM and use of MagicDraw following a case study, which demonstrates a typical defense architecture approach.
The course:
Includes lectures and hands-on practice in using MagicDraw for NAF modeling using UPDM;
Explains NAF views, sub-views and concepts;
Explains UPDM concepts and diagrams;
Provides hands-on experience building models;
Shows how to trace model elements in different views;
Explains how to use MagicDraw features efficiently;
Is based on a consistent modeling case study.
Audience:
Enterprise architects,
system architects,
system engineers,
software architects and other stakeholders who will create and use models
Methods:
Presentations, discussions, and case study-based practical assignments.
Course Materials:
Slides, case study model, and practical assignment descriptions.
Certificates:
Each participant receives No Magic and NobleProg certificate indicating that he attended the training.
Introduction
Trainer and Participant Introductions
Introduction to NAF
Introduction to UPDM
Introduction to MagicDraw
A Case Study Definition
Managing Capability Portfolio
Capability View
Sub-views for Capability View
Practical Assignment
Defining Operational Scenarios
Operational View
Sub-views for Operational View
Practical Assignment
Defining Capability Configurations
Systems View
Sub-views for Systems View
Practical Assignment
SOA
Service-Oriented View
Sub-views for Service-Oriented View
Incorporating Services into Operational and Systems Views
Managing Project Portfolio
Programme View
Sub-views for Programme View
Practical Assignment
Applying Standards
Technical View
Sub-views for Technical View
Describing Architecture
All View
Sub-views for All View
Practical Assignment
Establishing Traceability
Specifying and analyzing traces between different architecture Views
Wrap up
Summarizing Training
Discussing Remaining Questions
Identifying Further Action Points
|
|
soamlad |
Analysis and Design with SoaML |
14 heures |
This course explains the OMG SoaML standards and shows how to model the SOA landscape. It introduces the language and then shows how to discover, design and implement services and infrastructure for SOA.
This course always covers the newest version of the SoaML specification.
Motivation behind SoaML
Standards before SoaML
Vendors standards and Open Source standards
The IT and the business perspective on SOA
Contracts and Interfaces
Top-down and bottom-up approaches
Service classification
Compliance Level for SoaML
SoaML UML Profile Specification
Agent
Attachment
Capability
Consumer
Collaboration
Collaboration Use
Expose
MessageType
Milestone
Participant
Port
Property
Provider
Request
ServiceChannel
ServiceContract
ServiceInterface
Service
ServiceArchitecture
Categorization
Catalog
Categorization
Category
CategoryValue
RAS Placeholders
BMM Integration
MotivationElement
MotivationRealziation
SoaML Metamodel |
|
soadtbs |
Conception SOA avec TOGAF, BPM, SoaML |
21 heures |
Objectif:
Aider les analystes métier, architectes et concepteurs à spécifier et réaliser efficacement leur architecture orientée services sur la base des objectifs métier et d'aligner leur SI sur les besoins toujours changeants de leurs directions et utilisateurs.
Cette formation de 3 jours a pour but d'aider les analystes, architectes et concepteurs à comprendre comment spécifier et réaliser une Architecture Orientée Service capable de s'adapter au changement des besoins métier et des exigences utilisateurs tout en capitalisant sur les capacités métier..
Introduction
Avantages et Inconvénients des démarches actuelles vis-à-vis de l'Agilité Métier,
Objectifs de la SOA,
Connexions entre l'Architecture Métier, TOGAF, BPM et la SOA,
Définition et Catégories de Service,
Composants Producteur et Consommateur de Services,
Contrat de Service, Mesures,
Objets ou Données d'Echanges vs. Persistance,
L'orchestration,
Le Rôle de L'ESB,
L'approche Top-Down et Bottom-Up,
L'architecture Logique en Couches
Structure et Typologie des Services,
Les couches d'architecture du SI (métier, fonctionnelle, applicative, technique) dans la SOA,
Présentation des composants principaux par couche et relations de traçabilité,
Les Etapes par couche pour aligner l'informatique sur le changement des exigences métier,
L'Architecture de référence SOA de TOGAF
Couche Métier
Les composants de la couche métier : pourquoi faire?
La Modélisation Métier BMM, BPMN et UML avec traçabilité par les objectifs,
Objectifs Métier, Capacités Métier (Business Capabilities) et Processus Métier dans le « RUP for SOMA » d'IBM
Processus et Entités Métier alignés sur les Objectifs,
Identification des services à partir des Capacités métier,
Etude de cas : Raffinement de la Vision vers les Processus Métier par les Objectifs et Capacités,
Eléments du langage BPMN : Bonnes pratiques,
Etude de cas : Modélisation BPMN du Processus Métier précédent,
Modélisation et Répercussion du changement des objectifs métier sur les processus et responsabilités des acteurs,
Passage du métier vers le fonctionnel: Préparer l'Architecture au Changement : Composants fonctionnels réutilisables et traçables du Métier au Système d'Information,
Etude de cas : Elaborer l'épine dorsale métier de l'Architecture SOA structurée par les Objectifs,
Couche Fonctionnelle
Le rôle de l 'architecture fonctionnelle,
Les composants services de la couche fonctionnelle : pourquoi faire?
Découpage-type d'une architecture fonctionnelle urbanisée: (zone, quartier, îlot, bloc)
Services Métier Unitaire vs. Services Composés,
Spécification des services avec les « services points » et « request points » du SoaML,
Identification et spécifications des cas d'utilisation (UC) à partir des services métier,
Etude de Cas : Compléter l'épine dorsale métier de l'Architecture SOA par les composants de la couche fonctionnelle,
Invocation des composants de services et de UC à partir des actions de processus métier,
Le rôle des objets d'échanges,
Etude de Cas : Propager le changement depuis les Objectifs Métier jusqu'aux Composants de la Couche Fonctionnelle,
Passage du fonctionnel vers l'applicatif,
Couche Applicative
Les composants services de la couche applicative
Construction des composants applicatifs de sous-systèmes à partir des composants de blocs fonctionnels
Le Business Process Execution Language,
Le Mapping BPMN / BPEL,
Les WebServices: Définition, Soap, WSDL, UDDI, standards
Génération XSD à partir du Modèle de Données,
Génération WSDL à partir des Interfaces de Services,
Assemblage de modules et de composants
Etude de cas : Spécifier les composants de Use case et de Services Applicatifs,
Fonctionnalités d'un ESB et SOA,
JBI, Services Mix et Patterns d'Intégration,
Etude de cas : Intégrer les comportements des use case et des services à l'épine dorsale de l'architecture.
Aspects Transverses
Qualité de Service,
Administration et Supervision,
Le Business Activity Monitoring (BAM),
Les offres BAM,
La SCA, Sécurité et Performance,
L'agilité avec la SOA
Agilité: facteurs et analyse d'impact,
Factorisation, réutilisation et mutualisation (avantages et contraintes),
Gestion des Versions,
Gouvernance par les Objectifs ,
Apports de la SOA par les Objectifs Métier,
L'Agilité : Structure Orientée Objectif de l'Architecture SOA (Goal-Driven SOA) comme support au changement,
Du Métier au Système d'Information en capitalisant sur les Objets et les Business Capabilities,
Impact des Changements sur les Processus et Objets Métier,
Projection des Impacts sur le Système d'Information : Services et Use Cases susceptibles d'être impactés par le changement,
Description de l'impact du changement sur les comportements des composants de Use case et de Services Applicatifs,
Intégration des évolutions au backbone du Goal-Driven SOA et les tests.
Conclusion
Agilité et SOA : synthèse
Rappel sur les étapes d'une Modélisation Agile du Métier par les Objectifs,
Traçabilité des exigences métier du BMM aux structures du système d'information pour une meilleure réactivité au changement.
Panorama des Offres
Produits Open Source (Service Mix, Mule, Open ESB…),
Produits commerciaux
Note: Afin de servir de support à la traçabilité entre les spécifications métier et leur exécution, les sessions ci-dessus se déroulent en compagnie d'outils de Modélisation BMM, UML, SoaML et BPMN. Les concepts et livrables sont d'abord expliqués sur des cas simples et ensuite appliqués à vos propres besoins. Des sessions de revues peuvent être également planifiées selon besoin.
Fourni par GooBiz |
|
teeacmw |
Integrating the Extended Enterprise – On-Premise Applications, Cloud, Mobile and Web APIs |
21 heures |
IT architects, IT mid-level managers, IT consultants
Format of the course
currently 100% lectures, but some tests could be added
Why Integration Remains a Top Priority
Business strategies that drive integration
The perpetual challenge: increasing business velocity
The latest challenges: cloud integration and mobile access to back-end systems
Typical integration scenarios
Typical integration use case
Application Integration and Data Integration
Integration requirements
The messaging backbone
Data transformation
Content-based routing
Establishing application connectivity through adapters
Integration design patterns
Application integration vs. data integration
Service Oriented Integration (SOI)
What kinds of architectures can we employ for integration?
Service Oriented Architecture (SOA)
Services and SOA defined
Service layering
SOA vs. Event-driven Architecture (EDA)
Multi step process vs. Composite Application
When SOI is better than traditional Application Integration
Technologies for SOI
The need for Enterprise Service Bus
The Enterprise Service Bus (ESB)
Different ESB architectures
How do enterprises use Enterprise Service Bus today?
Product examples and Open Source
Repositories & Registries
Moving into the Cloud
Cloud definition
Choose your flavor: IaaS, PaaS, or SaaS?
Resource virtualization and sharing
Automated, elastic provisioning of resources
A Cloud Reference Architecture
Integrating with the Cloud
The need for Cloud integration
What are the Cloud integration challenges?
Moving from traditional Enterprise Service Bus (ESB) to Internet Service Bus (ISB)
Product example: Windows Azure AppFabric
Template-driven Cloud integration
Choices for Cloud Integration architectures
Extending Enterprise Applications with Mobile Applications
Use cases for mobile apps
Device native applications
Mobile Web applications
The impact of HTML5
Hybrid mobile applications
Comparison of the different approaches
Integrating Mobile Apps with Backend Applications
Mobile Enterprise Application Platform (MEAP)
Integration capabilities of MEAP
Connecting mobile apps to enterprise systems – step by step
A comprehensive enterprise mobile integration architecture
Mobile device management
The Rise of Web APIs
What are Web APIs?
Why do you need Web APIs
Using the API facade pattern for integration
Best practices: treat your Web API like a product
Putting It All Together: Developing an Integration Strategy for Your Company
Classification of integration architectures Approaches to leverage and migrate legacy systems
Comparison of integration approaches and technologies
Organizational impact of integration projects
Case study
Project Overview
Service Oriented Integration Architecture
Definition Of Service Layering
Designing Service Interfaces
Detailed B2B Gateway Logical Architecture
Verifying SOA Principles
Designing The Schemas – Componentization Yields Reuse
Composing business processes with BPEL
Adding Mobile Access
Conclusions on case study
Conclusions
Summary of the seminar
Main take away point, short and long term recommendations
Return on Investment (ROI) example
Future outlook
|
|
soagov |
SOA Governance |
14 heures |
Governance Framework
A Services Oriented Architecture governance program doesn't make operational decisions. SOA governance sets policies by deciding what decisions must be made, who should make them and how to make them. In a shared services environment like an enterprise SOA, no governance or dysfunctional governance, or even a bad governance policy, can have severe and negative impacts across the enterprise. This two-day workshop shows you how to do SOA right. You will learn how to design, build and operate an effective governance framework for creating, communicating and enforcing corporate web service policies throughout the enterprise SOA.
SOA Policies
The workshop focuses on showing you how to create the processes and policies that establish and manage shared web services. As organizations start to employ web services via an enterprise SOA, they move from "silo to shared." Ownership of the underlying business process transfers from a single business area and "externalizes" into an enterprise responsibility. SOA governance directs and coordinates the processes needed to accept and exercise the responsibility for shared Web Services on behalf of all of the stake-holders.
What is SOA Governance?
Compliance to standards or laws
Change management
Ensuring quality of services
Managing the portfolio of services
Managing the service lifecycle
Using policies to restrict behavior
Monitoring performance of services
The SOA Governance issue
Governance appearing as SOA initiatives
A dynamic environment for services to interact
Encouraging the reuse of services
Controlling how services interact with each other
The long-term ROI and manageability
Governance questions
Where they start on the governance ladder?
Governance as core feature of any SOA initiative
Establishing a timeline
Personnel training and operational procedures
Putting skills and procedures in place well ahead
SOA Governance Stages
First: realization that governance is needed
Second: governance improving business execution
Third: mixing technology & changes in behavior
Fourth: technology selection & implementation
Service Management
Design-time perspective
Run-time perspective
Repository of service for reuse
Services contained in heterogeneous platforms
Service-virtualization for run-time management of services
Critical governance components
Service registry service and an asset repository
Creating a "SOA Centre of Excellence”
Focusing on establishing SOA organizational guidelines
The organizational maturity
Agreed governance policies
SOA Governance tools
Real time monitoring of events
Failures in a BSM framework
Service-level instrumentation
Hooking into operational management systems
Virtualization as enabler to separate governance/service logic
Service virtualization managed by operational staff
Achieving governance
Measuring the goals for governance
The internal audit
Automating the audit
Developing core SOA governance
Why SOA technology stack has grown complex
Mixing between COTS & in-house
Justifying external consultants to help out
Figuring out which business we are really in
Roles and responsibilities involved in SOA Governance
Establishing a SOA Centre of Excellence
Enterprise-wide planning and assistance in execution
The roles of the SOA architect/governance architect
Solving potential conflicting interests
Ensure that governance guidelines are followed
Barriers to SOA governance
Not realizing the need for governance
Lack of Governance technologies
Lack of Service virtualizations
State of good governance
Interaction with external parties
Managing the business rules and BRE mgmt
Regulations for good governance
The agreements repository
Proactively embedding governance in the business
Governance by action rather than by statement
SLA monitoring to establish premium prices
Critical success factors
Start thinking about governance early
View governance as a moving target
Manage policies as entities with their own lifecycles
Choose a technology platform
The platform should address immediate governance needs
Future support as SOA infrastructure scales
Enforce service level agreements
Service virtualization
External configuration of encryption & routing
Authentication and schema validation
Transferring control from programmers to operational staff
Alleviating many of the SOA core pains
Avoiding services with internal policies
Technology and deployment neutral services
The 'dark path' in SOA
What if the service produces non-compliant data
Logging, tracking and auditing
Halting erroneous operations as they occur
Involving corrective business processes
Final thoughts and Conclusions
Greatest challenges with SOA
Critical aspects of SOA governance
Service reuse as a key benefit of SOA
The governance of reuse
Visibility, risk and control
|
|
soaarch01 |
SOA Architect |
35 heures |
This 5 day course is designed to give an understanding of the mechanics of Service Oriented Architecture. It includes the technical design of SOA based architectures and service oriented solutions to business problems.
Service Oriented Architecture and Computing
Service Oriented Computing
Terminology
Service Oriented Analysis and Design
Requirements and impact of adopting SOA
Enterprise Service Bus
Web Service and REST Services
SOA Connection Points
SOA Technology
XML and XML Schema
Web Services
JAX-WS and WSDL
REST Services
JAX-RS and WADL
Discovery and Service Registries
Enterprise Service Bus (ESB)
SOA Design and Architecture
SOA Model
Services and Service Capabilities
WSDL first or code first design
Principles of Service Orientation
Service coupling
Handling state
Service discovery
Advanced SOA Design and Architecture
SOA Architecture types
SOA Design Patterns
Message types
Data transformation
SOA Workshop
This hands on workshop consists of a number of individual and group exercises which allow the technologies and principles described in the previous modules to be applied.
Participants can also bring real world problems to the workshop. |
|
soaadv |
Advanced SOA - Architected, Governed, Integrated, and Cloud-Ready |
21 heures |
Audience
Who is this course addressed to
IT architects, IT mid-level managers, IT consultants
Format of the course
currently 100% lectures, but some tests could be added
1.First Things First: Enterprise and Application Architecture
Definition of (Enterprise) Architecture
What drives the need for architecture?
Architecture objectives, standards and frameworks
Logical vs. physical architectures
Common application architecture patterns
Multi-step Process pattern
Composite Application pattern
2.SOA Phase 1
The pieces of the SOA puzzle
How SOA enables business strategies
Services and SOA defined
What is the notion of “Applications” in SOA?
The Service Layer model
Infrastructure services
Application services
Orchestration services
SOA Case study
Sample outline for an SOA Blueprint document
Sample business event walk-through
Key SOA characteristics
Architecture level loose coupling
Service level loose coupling
Next Generation SOA
Synchronous vs. Asynchronous services
SOA in the cloud
SOA and standards
SOA challenges
3.Service- or Resource-Oriented Architecture, or Both?
Representational State Transfer (REST)
The concept of resources
The uniform interface
Architectural constraints
What about business logic?
Perceived deficiencies of REST
When to use REST, when to use a traditional SOA
REST as the choice to support the presentation layer
The synergy of Rich Internet Applications (RIAs) and REST
JavaScript Object Notation (JSON) vs. XML for RIAs
Case study
Conceptual architecture
RESTful vs. SOAP-type Services
4.Managing the SOA Evolution: SOA Maturity Models & Roadmap
Defining the goals – SOA maturity models
The Open Group Service Integration Maturity Model (OSIMM)
Overview
Maturity dimensions
Maturity levels
How to asses your SOA maturity
Example - Progress Software Maturity Model
How do we get there – developing a SOA Roadmap
Case study: mapping a Maturity Model to a Roadmap
5.From Chaos to Order: SOA Governance & the IT Organization
Why SOA needs governance
Business vs. IT vs. EA vs. SOA Governance
Categories of SOA Governance
Design time governance
Run time governance
SOA Governance goals
SOA Center of Excellence (COE)
Roles and responsibilities within the IT organization
6.Get a Running Start with SOA Governance Frameworks
Open Group standards
SOA Governance Reference Model (SGRM)
SOA Governance Vitality Method (SGVM)
IBM SOA Governance and Management Method (SGMM)
7. A ROI Calculator For SOA - Let The Numbers Do the Talking
Approaches to ROI calculation
Case Study
Business process walk-through
Architecture scope
Architecture overview
Service layer model
ROI Through Service Reuse
ROI Defined
ROI Model for Software Reuse
Reuse beyond the core application project
Conclusions
Keeping track of reuse
8.The New Frontier: Cloud Computing
Cloud definition
How did we get here? From application hosting to SaaS to public & private cloud
Chose your flavor: IaaS, SaaS, or PaaS?
Moving applications into the cloud
Resource virtualization
Automated, on-demand provisioning of resources
Shared infrastructure and applications
9.The Synergy of SOA and Cloud Computing
SOA and cloud are complementary
SOA/Cloud synergy
SOA + SaaS
SOA + PaaS
SOA + IaaS
Putting it all together: the SOA-Cloud
10.Across Application Silos: The Integration Landscape
The integration landscape – the big picture
Data level integration
Extract, Transform, Load (ETL)
Interface level integration (a.k.a. application integration)
The messaging backbone
Data transformation
Content-based routing
Establishing application connectivity through adapters
Integration design patterns
Service Oriented Integration (SOI)
Advantages over traditional Enterprise Application Integration (EAI)
11.From Enterprise Service Bus (ESB) to Internet Service Bus (ISB)
The Enterprise Service Bus
Introducing the ESB
Conceptual ESB architectures
How do enterprises use ESBs today?
The need for cloud integration and its challenges
From ESB to “Internet Service Bus” (ISB)
The product landscape – ESB and ISB examples
12.Putting It All Together: Developing an Integration Strategy for Your Company
Classification of integration architectures by the degree of coupling
Approaches to leverage and migrate legacy systems
Comparison of integration approaches and technologies
Decision criteria for selecting a particular approach
Integration with the data architecture
13.Conclusions
Summary of the seminar
Outlook: SOA, Cloud, mobile and the consumerization of IT
|
|
restapi |
REST API - a pattern of exchange of information between sites |
14 heures |
The course is designed for developers, web applications, aims to provide opportunities offered by the REST architectural pattern by which you can communicate between sites.
REST - base
The need for the exchange of information between sites
HTTP POST / GET / PUT / DELETE
Services such MushUp and popular applications
Services using REST
Conventions Rest
Mapping CRUD operations on HTTP calls
Conventions API URL structure
Passing Parameters
Return Values
HTTP statuses
JSON - a universal format for the exchange of information
API services
Examples of the popular API
RESTful frameworks
Create a REST API - Server
Gathering requirements and identify functionality
Design and API documentation
Installing the required libraries
Business Object - mapping the class
Controller methods
Representation of a business object as JSON
HTTP Headers - as metadata
Testing the API using cURL
Authentication mechanisms
|
|
soabpmn |
Enabling SOA with BPM and BPMN |
14 heures |
Although SOA is not specific to BPM software, there are a number of natural synergies between BPM and SOA. Perhaps most obvious of these is the separation of business process management as an independent function, allowing processes to be designed independently of any single application and leveraged as shared business logic.
BPM in Context
The many faces of BPM
The BPM umbrella
BPM and Governance
Industry players
Maturity within the market
Current BPM challenges
The future of BPM
BPM Layering
What is layering?
Common layers
Auxiliary layers
The BPM stack
Digesting the layers
Layering rules of thumb
The State of Standards
Standards – Friend or foe?
Standards bodies
Mature standards
Standards in flux
Emerging standards
Leveraging SOA and BPM standards
Roles within BPM
Enterprise roles within BPM
Project Manager responsibilities
Business Analyst responsibilities
Architect responsibilities
Developer responsibilities
QA/Tester responsibilities
Configuration manager responsibilities
Specialist roles and responsibilities
New role: Integration specialist
New role: Process champion
Process-centric SOA
The importance of Business Process Management (BPM) within SOA
Common BPM pitfalls
Mode ling business processes
Business process as documentation
Controlling business processes
Driving a process-centric enterprise
Rules-driven BPM
Business rules within BPM
Externalizing existing rules
Identifying new rules
Managing SOA business rules
Leveraging business rules
Supporting tools
Process and Service Identification Methodologies
Overview of popular methodologies
Top-down modelling
Bottom-up modelling
Goal-service modelling
BPM modelling pitfalls
BPM modelling recommendations
Service Lifecycle Recommendations
SOA lifecycle overview
High risk points within the SOA lifecycle
Handling service and process dependencies
Service composition
Configuration and control
Proper retirement of processes and services
Service Versioning Strategies
The problem of SOA versioning
Configuration control granularity
The role of the service registry
Naming conventions
Process versioning
Service versioning
Operation versioning
Supporting multiple simultaneous versions
Defining a version control policy (VCP)
BPM-SOA Testing Strategies
The problem of SOA testing
End-to-end testing within BPM
WS-I compliance
WS-Policy compliance
Mock clients and services
Regression testing gotchas
BPM testing recommendations
Security Recommendations
BPM and security considerations
The SOA security stack
Security standards
Single Sign On
Identity management
SOA security approaches
Point-to-Point security
ESB-brokered security
The security service layer
BPM Business Patterns
Business patterns
The Self-service model
The Information warehouse model
The Information subscription model
The User collaboration model
The Extended enterprise model
Custom business models
BPM and BPMN
The added value of BPMN
Composability and basic services
Promoting an incremental and iterative approach
Why should Use cases drive the project?
Declaration of message properties
Use of correlation sets
Develop a complex parallel execution of activities
Designing concurrency
|
