Description

This seminar presents the functional and technical issues linked to the implementation of Service Oriented Architectures or SOA. It also presents an overview of best practices for defining a SOA architecture as well as the link with Web Services. The challenge: moving from IT essentially composed of applications to service-oriented IT in order to improve the responsiveness of the information system.

Who is this training for ?

For whom ?

Business and IT decision-makers wanting a holistic view of the SOA landscape and business opportunities.

Prerequisites

Training objectives

Understand the benefit of adopting a SOA approach

Discover the components, services and layers of a SOA architecture.

Recognize the main technical building blocks underlying a SOA architecture

Discover the approaches and models SOA design and architecture

Identify the key market players and products

Training program

• Introduction: why the SOA approach?
  • The challenges for the company.
  • Multilevel architectures and business components: limits of the interoperability of classic middleware.
  • Web services and IS interoperability .
  • From components to service-oriented architectures (SOA): limits of IS project management.
  • Introduction to services, service contracts, service orchestration, service bus 'enterprise (ESB).
  • Gains: alignment of IS with business processes, cost reduction, standardization, reuse, interoperability.
• Presentation of a SOA architecture
  • Components and layers of an SOA architecture.
  • Data access service, transaction management.
  • Process management, user interaction (portal.
  • ), security, administration, supervision.
  • Web Oriented Architecture (WOA) and architectures based on micro-services.
  • The principle of weak coupling between service provider and consumer.
• Services and processes
  • The concept of service.
  • Service exposure, weak coupling, synchronism vs asynchronism.
  • Service provider and consumer, service contract, typology of services ( business, technical.
  • ).
  • Differences between services and components, specification of quality of service.
  • Business application components.
  • Operating unit in SOA, implementation of contracts, dependencies between components and orchestration.
  • Mapping business processes/services.
  • Alignment of IS on processes business: the importance of process modeling by businesses.
  • The OMG BPMN modeling standard.
  • Positioning in relation to BPM.
  • Moving from a business process model to a service.
• Aspects techniques
  • Implementation of Web Services (Java EE, .
  • NET, PHP.
  • ).
  • XML foundations.
  • XML schema for interoperability and description of application data.
  • Description of services with WSDL and invocation with SOAP.
  • RESTfull approach.
  • Search and publish services (directories).
  • Design Patterns linked to Web Services.
  • Link between SOA and EAI.
  • Message Oriented Middleware (MOM) ).
  • Enterprise Service Bus: concept of ESB, ESB vs SOA.
  • Update on standards.
  • Web service orchestration and process integration professions (BPM, BPEL.
  • ).
  • Standards and their level of implementation: OMG, W3C, OASIS, WS-I.
  • Security and Web services (WS-Security), transaction management (WS-Coordination).
  • Message delivery (WS-ReliableMessaging), interoperability and message identification (WS-Addressing).
  • Links with other IS components and emerging technologies: Cloud, mobility, Big Data.
• SOA design and architecture patterns
  • SOA seen as an integration model and EIP patterns (Enterprise Integration Patterns).
  • SOA patterns.
  • Attempts at standardized SCA approaches and SDO.
  • Can we design a SOA architecture with REST? The question of orchestration and the place of BPEL, BPMN and traditional development technologies.
• The governance of an SOA IS
  • The specificities induced by the SOA model on the organization.
  • Organize the initial implementation and reuse with a SOA center of excellence.
  • The key roles: business director, technical director, domain architect, technical architect.
  • Typical governance activities: manage a service application, its implementation and its developments.
  • Moving from setting up an on-demand service to anticipating needs.
  • How to stay agile with what seems to be an extremely centralized model? Pitfalls and mistakes to avoid .
• SOA design methodological approach
  • The links between SOA and the Object approach.
  • Methods available on the market: UP, EUP, TOGAF, NAF, Praxeme.
  • Life cycle of an SOA project: strategic vision and organizational process.
  • Urbanization metaphor and aggregation levels.
  • Conceptual model of a SOA.
  • The modeling of services within the application architecture with UML.
  • The transition from the organizational process to business services, from business services to application services.
  • The MDA approach of OMG.
• Market players and products
  • Typology of existing products.
  • Enterprise Service Bus (ESB).
  • EAI platforms for new Web Services functionalities (Tibco, WebMethods.
  • ).
  • SOA orchestrators, the upper layers for directories, orchestration, administration.
  • Platform providers (IBM, BEA, Oracle.
  • ).
  • Cloud players (Amazon, Google.
  • ).
  • BPMN modelers and their orchestration possibilities.
  • Monitoring tools (business and technical) and administration solutions.
  • Open Source offering and projects: Apache ServiceMix/FUSE, Mule, Celtix, Synapse.