Print this Page

SOA Application & Service Development
A Step-by-step Guide for Developers, Programmers & Architects

SOA Application & Service Development teaches how to construct business applications and services for deployment on a Service-Oriented Architecture (SOA).  Focusing on what’s different about developing SOA applications and services, this two-day technical course prepares participants to:

  • Develop a SOA solution that includes long-running transactions, orchestrated workflows and multiple services spanning multiple organizational entities

  • Build SOA services

  • Create composite applications

SOA Application & Service Development provides an excellent vehicle for architects and developers making the transition to SOA.  The seminar uses demonstrations and case studies to explain the how’s and why’s of the SOA architecture as an application deployment environment.

  • How to architect a business solution based on SOA

  • How to orchestrate work flows

  • How to build long-running transactions via BPEL, Coordination and Policy

  • How to recognize trust boundaries and their security implications

  • How service descriptions are used in a SOA

  • Why semantics are important and when to use them

  • Why ontologies are important and when to use them

  • How and why to version services

  • How to use BPM (Business Process Management) servers, such as BizTalk, WebSphere, WebLogic, etc.

SOA Application & Service Development introduces and explains the core technical standards, techniques and practices shared by all SOA development and deployment platforms.  Architects and developers will find this course extremely useful as they prepare to construct business solutions via .NET, J2EE, IBM Websphere, BEA Weblogic and other SOA environments.

What You Will Learn

  • How to construct Loosely-Coupled Services

  • The anatomy of SOAP and how to use SOA messages

  • The anatomy of WSDL and how to use WSDL

  • What WS-* SOA technologies to use under what circumstances, including WS-Security, WS-Addressing, WS-Policy, WS-Security Policy, WS-Metadata Exchange, WS-Coordination, WS-Business Activity, WS-Transaction and WS-Trust

  • The different types of SOA services (Data, process, system)

  • How to determine who “owns” the various types of Enterprise data

Who Should Attend

Application developers, architects, project managers and other IT professionals who need a comprehensive technical foundation that will prepare them to construct sophisticated and complex business applications and services for deployment on a SOA.

Learners attending this course should have:

  • Minimum 1 year programming experience or equivalent

  • XML familiarity, as provided by “Understanding & Applying XML” or equivalent

  • Familiarity with basic web technologies (http, html, etc.)

  • Familiarity with basic SOA and Web Services concepts, as provided by “Understanding & Applying SOA” or equivalent

Seminar Outline

Part 1: Understanding Service Oriented Architecture

  • A Parable for Service Oriented Architecture

  • OASIS SOA Reference Model

  • What is a Service?

  • Business Capabilities

  • What is Policy?

  • What does Loose Coupling Really Mean?

  • Relationship between SOA and Object Orientation

  • From Applications to Services

  • A Parable for SOA Governance

  • Agility and. Reuse in SOA

  • Relationship of SOA to Web Services

  • Previous Technological Attempts at SOA

  • SOA Pioneers

Part 2: Medical Information System Case Study

  • What are the Business Problems Posed By the Case Study?

  • How can Service Oriented Architecture Help Solve Them?

  • What are the Business Processes?

  • What are the Business Services?

  • Trust Boundaries and Distributed Services

  • Service Description

  • Information Model

  • Data Definition and Data Semantics

  • Versioning

  • Behavior Model

  • Action Model

  • Process Model

  • Policies and Contracts

  • Choosing Your First Project

  • Moving Beyond Your First Project

  • Medical Information System First Project

Part 3: Architecting a Simple SOA Project

  • Scheduling Critical Care

  • Mutual Trust

  • Critical Care Application

  • Capabilities and Explicit Boundaries

  • Critical Care Messages

  • Critical Care Policies

    • Service Description and Versions

    • Long Running Transactions

  • Real World Effects

  • Role of User Interfaces in SOA

  • Semantics and Ontology

  • Loose Coupling

  • Advantages of the SOA Approach

Part 4: Implementing Your Simple SOA

  • Message Transport

  • SOAP Protocol

  • Admittance Request

  • Admittance Notification

  • Admission Failure

  • SOAP Fault

  • SOAP Intermediaries

  • Critical Care Scenario

  • SOAP Attachments

  • Medical X-Rays

  • WS-Addressing and Message Routing

  • WSDL and Messaging Metadata

  • Medical Admissions WSDL

  • Interoperability Profiles

  • Reliable Messaging and WS-Reliable Messaging

  • Policy and WS-Policy

  • WS-Metadata Exchange

  • Security

  • WS-Security, WS-Security Policy

  • Trust

  • Secure Sessions

  • Implementation Strategy

Part 5: Enterprise SOA

  • Moving to an Enterprise SOA

  • IT Governance

  • Enterprise SOA

  • Beyond the Enterprise

  • Beyond Critical Care Admissions

  • Enterprise Data Ownership

  • Types of Enterprise Data

  • Data Scalability

  • Federated Identity

  • Classic Transactions

  • WS-Atomic Transaction

  • Long Running Transactions

  • Coordination and WS-Coordination

  • Composite Applications

  • BPM Servers and Orchestration

  • Hospital Scenario

  • Hospital Orchestration

  • Compensation

  • Security

  • Discovery

  • Fault Handling

  • Policy

  • Distributed Policy

  • Policy Conflicts

  • Summary