Enquiry Form

SOA Training Courses

Service-oriented Architecture courses

Client Testimonials

WebServices Basics for Non-Programmers

It was great to learn the basics of WebServices that was taught in a very easy to understand manner. The trainer thoroughly understood his subject and I enjoyed hearing the stories of his previous work history with web services.

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?

Objective:
Helping Business Analysts, architects and designers to understand how to efficiently specify and realize a Service Oriented Architecture on the basis of their business goals and align it to changing business and user requirements.
This 3 day training course aims at helping business analysts, architects and designers to learn how to specify and realize a featured Service Oriented Architecture to better deal with changes on the business and user requirements (changing objectives, strategies, tactics, rules, user interactions,...) while capitalizing on the business capabilities.
Introduction
Pros and Cons of the current development methodologies to support the Business Agility,
Objectives of the SOA,
Connections between Business Architecture, TOGAF®, BPM and SOA,
Service Definition and Categories,
Service Provider and Consumer Components,
Service Contract, Metrics
Data Transfer Objects vs. Persistence,
Service orchestration,
Role of the ESB,
Top-Down and Bottom-Up approaches,
The Layered Logical Architecture
The TOGAF® Reference Architecture for SOA,
Structure and Typology of Services,
Architecture Layers (business, functional, application, technique) in the SOA,
Presentation of the main components by layer and traceabilities,
Steps for aligning IT to changing business requirements,
Business Layer
Components of the business layer : objectives
Traceability in the Business Modeling using BMM, BPMN and UML standards,
From the business goals toward processes using Business Capabilities- the IBM's RUP for SOMA,
Alignment of business processes and entities on the changing goals,
Service Identification on the basis of Business Capabilities,
Case Study : Refinement from the Business Vision toward Processes using goal-driven business capabilities,
Language Structures of the BPMN : Good practices,
Case Study : BPMN Modeling of the previous business process,
From the Business to functional layer : Prepare the Architecture to deal with change using reusable and traceable components,
Case Study : Elaborate the business architecture backbone of the Goal-Driven SOA,
Functional Layer
The role of the functional architecture,
Service components of the functional layer : objectives
Blocks of an urbanized functional architecture : (zone, square, block)
Unit Business Services vs. Composite Services,
Service Specification using SoaML « services points » and « request points »,
Identification and specification of use cases (UC) on the basis of services,
Case Study : Complete the business architecture backbone of the Goal-Driven SOA using functional components,
Invocation of service and UC components from business process actions,
The role of the data transfer objects,
Case Study : Propagate change from Business Goals till Components of the Functional Layer,
From the functional to application layer,
Application Layer
Service components of the application layer
Building application components on the basis of functional ones,
The Business Process Execution Language,
BPMN / BPEL Mapping,
WebServices: Definition, Soap, WSDL, UDDI, standards
XSD generation on the basis of Data Models,
WSDL generation on the basis of Service Interfaces,
Module and Component Assembly,
Case Study : Design Application Use case and Service components on the basis of functional ones,
ESB features in SOA,
JBI, Services Mix and Integration Patterns,
Case Study : Integrate use case and service behaviours into the architecture backbone.
Horizontal Aspects
QoS,
Administration and Supervision,
Business Activity Monitoring (BAM),
Security and Performance,
Agility using SOA
Agility: factors and impact analysis,
Refactoring, reuse and mutualization (advantages and constraints),
Versioning,
Governance by Objectives ,
Benefices of the Goal-Driven SOA,
Agility : The Goal-Driven Structure of the SOA to support changes,
From the business to IT system capitalizing on Business Objects and Capabilities,
Impact of the Changes on Processes and Business Objects,
Projection on the IT System : Services and Use Cases to be impacted by the changes,
Description of the impact of changes on the Use case and Application Service Component behaviours,
Integration of behaviours into the backbone of the Goal-Driven SOA and tests.
Conclusion
Agility and SOA : synthesis
Overview on the steps of the Goal-Driven SOA,
Traceability from the BMM's business model structures to IT structures to better deal with changes.
Overview on the market products
Open Source Products (Service Mix, Mule, Open ESB…),
Commercial Products
Notice: The above training-mentoring sessions are conducted interactively using Business and IT Modeling tools in order to ensure good level of traceability between business specifications and their execution. Concepts are first explained using basic examples and are then followed by solution drafts to your own problems. After this session, we can accompany you by reviewing and validating your solutions depending on your needs.
Provided by GooBiz

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

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.

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
Using the API services - customer
Examples of the popular API
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

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

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

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

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

NobleProg® Limited 2004 - 2016 All Rights Reserved
This site is operated by the NobleProg franchisor . If you interested in opening a franchise in your country, please visit http://training-franchise.com for more information.

NobleProg® is a registered trade mark of NobleProg Limited and/or its affiliates.