Overview
SOA governance is one major part of SOA founding principles: it emphasizes services reuse to avoid useless developments, thus sparing time and money while controlling infrastructure complexity.
Main topics
This training provides extended practice of SOA governance through textbook and client case studies, to provide attendees with a complete understanding and know-how: understanding tools features and settings, searching for a service, reuse a service, rate and share services.
Main attendees
This module is intended for Architects and Projects managers in the first hand, as they are the first concerned with SOA governance. They will gain necessary skills to supervise and reuse services deployed in their SOA infrastructure with Petals Master.
Objectives
- Synthesize the major stakes related to Service Oriented Architecture
- Understand concepts and added value of services governance
- Handle Petals Master in order to initiate a governance framework project
With this course, Architects and developers have a complete overview of JBI concepts and the techniques for implementing a services infrastructure based on Petals |
Outline
Day 1: Introduction & Concepts
- Introduction and stakes of SOA
- What is SOA? What it isn’t?
- What is a Service?
- Architecture patterns and SOA standards
- SOA Governance
- Stakes of SOA Governance
- Service Lifecycle
- Service contract (SLA) and quality (Policy)
- Service Monitoring
- Benefits
Day 2: SOA Governance with Petals Master
- Introduction of Petals Master
- Main features
- Standards support
- Architecture
- Labs: Installation and Configuration
- SOA Governance tools overview
- Standards: UDDI and ebXML
- Main tools categories
- Petals Master Positioning
- Labs: Share services (Publish)
- Import services from service descriptions
- Import services from execution environment (Petals ESB)
- Labs: Reuse services (Find)
- Keyword based search
- Execution environment browser
- UDDI based search from Eclipse IDE
- Labs: Evaluate services (Document, Enrich)
- Service related documents (Specification, test reports…)
- Community aspects (ratings, tags and comments)
|
General informations
Duration: 2 days
Teaching method: 60% Theory, 40% Labs
Attendees: Architects, Project managers, Developers
Prerequisites: Java/J2EE experienced developers
|