SOA, Service Oriented Architecture Training
- Participants / Prerequisite
This seminar presents the key concepts of SOA - Services Oriented Architecture- and the functional and technical stakes connected to its implementation. It also presents the best practices for the definition of its architecture as well as the link with Web Services. It explains how to move from the applications of a classical computing system to oriented services and how SOA can benefit your information system and what is required for its implementation.
- Current situation : evolution of IT system and evolution of companies needs.
- Business issues : Silos, " Spaghetti " programming, Computing ridigity...
- The search for integration solutions : EAI, CORBA, XML...
■ It covers the following aspects
- SOA definitions from Gartner, W3C ...
- Basic SOA concepts : what are the concepts behind SOA (subdivide method agreement, use existing, change for commercial reason, and react on the environment)?
- Why to use SOA ? We develop the reasons to implement SOA and approach the advantages and the risks in implementing SOA in a company.
- SOA stereotypes : common ideas about SOA. What SOA is or what it i not; What SOA covers or what it does not cover.
- Service concepts. We explain the key features of services: service contract (abstract and concrete WSDL, WS Policy, SLA..), loose coupling, abstraction, reusability (agnostic service), autonomy, statelessness, discoverability (through UDDI registry), composability (concept of separation of concerns).
- What are the definitions of SOA Governance: by Gartner, by Hoogervorst...
- What is a SOA Roadmap: the SOA project lifecycle - What are the main steps to implement SOA architecture in a company? How to deploy SOA architecture ?
- State of the situation - Why to use of different maturity models to estimate the state of the situation: to improve SOA fields simultaneously but at different speeds.
- The basic choices for organization and management.
- The choice of Business projects.
- The choice of projects to prepare the company for an effective implementation of SOA (capability projects).
- Organization of teams: Implementing SOA architecture means to assign roles and responsibilities, to establish a management mechanism, an organizational transverse structure, to determine the governance processes and determine the power of decision in these processes. Implementation of a Center of Excellence which is made of different roles.
- Modeling Framework: What is the position of this important aspect in SOA architecture, what are the market framework (TOGAF, Praxeme, RUP...), how to model business and activities services??What is the impact of service contract ?
- Reference Architecture: why to define a reference architecture, what is it (which components are made of it) and how to define it?
- Control and monitoring : a quick view of this important aspect in a SOA Architecture : Maturity model assessment, processes monitoring, PKI monitoring.
■ The results of the SOA roadmap
- Services infrastructure : what are the common components you find in a SOA platform. Preview of BPEL, BPMN, ESB, JMS, Event, Human task, CEP, BAM, BR...
- WSDL Contract to describe services: a practical example of the abstract and concrete parts of a service.
- WS-standards and their implementations : what are the different current standards for the following fields : security, transaction, reliable messages and messages identifications.
- Implementation of WS with Java: presentation of different Java implementation standards as JAX-RPC, JAX-WS, JAXB to develop services.
- Services orchestration : What are the standard behind this concept ? (Such as BPMN, BPEL, SCA (service components architecture). The development lifecycle use to implement business processes. Categories of processes. Emergence of BPMS : Business Process Management Suite. What are the components of BPMS ? What is the lifecycle with BPMS ? Evolution of BPMN to executable models.
- Enterprise Service Bus (ESB) : notion and basic features : transport, routing, transformation ..., definition of EDA (Event Driven Architecture), Java Business Integration (JBI) standard in the ESB field. View of several ESB design patterns. Typical uses of an ESB.
- Services Registry : research and publication of services through UDDI standard.
- Services Repository : enterprise reference system to document services, to manage services lifecycle (versions, variants, links between services, synchronization with UDDI registry ...).
- Business Rules (BR) : how to use them to increase business processes agility ? What is the typical implementation of Business Rules ?
- Master Data Management (MDM) : what is the business issues and how to manage the reference data of an enterprise ?
- Business Activity Monitoring (BAM) : It is a tool of supervision and piloting of the processes. It allows to define business metrics, business alerts and to build business reports based on these metrics.
- Complex Event Processing (CEP): Enables Advanced Event-Driven Analysis & Pattern Detection. Provides IT Users with a Rich, Declarative Language for Evaluating Events.
- Criteria for selecting a SOA platform : general criteria whatever the tool and specific criteria.
- Offers of the market: commercial software (IBM, Oracle, TIBCO...), open source (Mule, JBoss...), hybrid solution (JBoss Entreprise SOA Plate-forme, FUSE, Mule ESB Entreprise, WSO2) and other products (Amberpoint, EBX platform ...) for the different components of a SOA platform.