Print this Page

SOA Technical Architecture Strategies & Tactics
How to Put the Promise of Enterprise SOA and Web Services into Practice

The Promise:

SOA is an emerging architectural style that…

• Is business driven

• Enhances IT’s flexibility and responsiveness to changing business needs

• Improves the ability of a business to respond to rapidly evolving internal and external customer requirements

• Reduces the work necessary to integrate business solutions between companies or between divisions within the same company

• Decreases the IT application maintenance workload

• Shrinks the development workload for new applications via reuse of common operations

The Reality:

Early experience deploying large-scale Services-Oriented Architectures clearly demonstrates that successful enterprise-SOA implementation require far more than simply building SOAP wrappers and using WSDL to document Web Services.

SOA Technical Architecture Strategies & Tactics provides a comprehensive and realistic road map for putting the Services-Oriented Architecture promise into practice.  This two-day seminar examines in detail the technical, organizational and management issues surrounding the planning and implementation of a SOA.  It presents practical information and guidance that will help organizations plan the deployment of SOAs that employ internal and external Web Services to execute intra-business processes and inter-business processes.

SOA Technical Architecture Strategies & Tactics uses case studies, examples, and business language to introduce the topics and explain the choices that organizations face as they plan and build their Services-Oriented Architectures. Seminar topics include:

• Decisions, issues and challenges concerning the implementation of business processes as applications using a Services-Oriented Architecture

• SOA design, deployment and implementation options and alternatives

• Best practices for implementing business processes via SOA, including major implementation phases and their component steps

What You Will Learn

SOA Technical Architecture Decisions, Issues and Challenges

• How to retrofit legacy applications as Web Services

• How the SOA approach fits with conventional middleware

• How to determine what business processes & services are good SOA candidates

SOA Technical Architecture Options and Alternatives

• How to choose your 1st SOA project

• How to define internal intra-business processes & external inter-business processes

• How to build an SOA implementation project plan

• How to establish security rules via WS-Security and WS-Policy

• How to make SOA deployment decisions

  • Tight-coupling vs. Loose-coupling

  • Document vs. RPC

  • Service vs. Object

  • Business Services vs. Business Operations

• How to select and utilize an Enterprise Services Bus (ESB) (& what to avoid)

• How to govern an SOA

How to implement business processes via SOA

• How to design a good reusable web service

• How to evolve an existing architecture into a Service Oriented Architecture

• How to build a Web Service

• How to incorporate SOAP intermediaries

• How to build and coordinate large-scale, long-lived asynchronous processes

• How to secure services

• How to set policies for services

• How to utilize evolving best practices in SOA definition, construction and deployment

Who Should Attend?

• The IT and Business Area Leaders, Managers and Architects who plan and execute the SOA implementations

• The technical, business analyst and business area staff who design, create and deploy SOA applications composed of Web Services

Participants in this seminar should understand the concepts and principles explained in “Understanding and Applying SOA”.

Seminar Outline

Part 1: Defining the Business Problem

• Case Study: Medical Information System

• 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?

• Choosing Your First Project

  • Differences between SOA and Traditional Middleware (EDI, DCOM & CORBA)

  • New Development

  • Evolving Existing Applications

  • Corporate Visibility

  • Managing Complexity

  • Intranet, Extranet, Internet

• Relationships with Existing Vendors and Suppliers

• Moving out of Kindergarten

  • Inter-Business Processes and Inter-Company Processes

Part 2: Building Your Architecture Based on Service Oriented Architecture Principles

• Designing the Architecture to Automate the Business Process

  • Challenges and Issues in architecting SOA applications

  • SOAD – A possible emerging Methodology

• Using the Basic Elements of a Service Oriented Architecture?

  • SOAP Messaging

  • XML Documents

  • Addressing and Transport

  • Security

    • Using WS-Security to Solve the Security Problem

      • Tokens

      • Digital Signatures

      • Encryption

  • Non repudiation

  • Trust

  • Policy

  • Coordination

  • WSDL and other Metadata

• What is the Role of Intermediaries?

• No UI in SOA

  • Composite Applications

  • Machine Service Facades

• Architecture for the Medical Information System

Part 3: Implementing the Architecture

• How to Design a Good Service

  • Loose vs. tight coupling

  • Document vs. RPC

  • Service vs. Object

  • Business Services vs. Business Operations

  • Transactions

  • Sessions

  • Message Exchange Patterns

  • Avoiding Vendor Product-Centric Approach

• How to Evolve An Existing Architecture

  • How to Map Architecture to Concrete Implementation

  • Web Services as the Implementation Technology

• Building the Services

  • New Services or Wrap Existing Applications

  • Automatic code generation from WSDL

  • Coordinate the sub-services

• Incorporating Quality of Service

  • New Problems Associated with Distributed QoS

• How to Build an Intermediary

  • Dynamic SOAP Header Construction/Modification

• Advertising the Services

• Registries and Service Discovery

• Service Description

• How Semantics Solve Some of the Difficult Problems

  • Why is Semantics Important?

  • What's Available?

  • Moving Semantics to Description

• Dynamic Location Through Policy

• Deploying the Services

  • Addressing

  • Advertise, Find, Transact; Cycle

• Coordinating Multiple Services

  • Atomic vs. Long Running processes

    • Mixtures

  • Inter-company

    • Negotiation

    • Control

• Securing the Services

  • What Makes Distributed Security So Very Hard

  • Determining the Correct Level of Security

• Using Policy with Services

  • Business Driven

  • Service Patterns

  • Policy and Service definition and Service Semantics

  • Policy Specifics

    • Constraint/Permission

    • Obligation

    • Policy Construction

    • Policy Ownership

    • Negotiation

    • Policy Interrogation

  • Negotiating Security Using Policy

• WSDL, the Linchpin, but not sufficient

• Integrating With Outside Enterprises

• Business Process Lifecycle

  • Long Lived Processes

  • How to Use and Implement Asynchronous Processes

  • Using Large Scale Coordination

• Distributed Management

• Why an ESB is not sufficient

  • Using an ESB Pattern

• How to incorporate BPEL into your service

• Handling Faults in a Distributed System

  • Reporting

  • Recovery

• Coordination of the Business Analysis & Technical Analysis

• IT Governance and Infrastructure in Service Oriented Architecture

  • Role of Upper Management

  • Business responsibility contrasted with technical responsibility

  • Central vs. Local Control

  • Inter-company Control

  • Legal Considerations

    • Sarbanes-Oxley

    • HIPPA

  • Business Contracts

Part 4: Best Practices for Service Construction

• Completely separate Code and Data from other services

• Business Processes define the Architecture

  • Architecture defines the Implementation

• Using the SOA Models

  • Messaging Model

  • Service Model

  • Policy Model

  • Resource Model

• Service Contract

  • Service Definition

    • WSDL

  • Semantic Description

    • Semantic Language

    • Moving from semantics to description

• Loose Coupling

  • Messaging

  • Empowers IT Flexibility

• Reusability

• Integration & Interfacing

• Scalability and State

• Quality of Service

• Independent Deployment

• Advertising & Discovery of Service

Part 5: Vendor Products and Their Uses

Part 6: Complete and Present the Case Study

• Use the Principles Discussed Above to Complete the Study

• Discuss Alternate Approaches