The chief goal of this class is to teach how to build a SOA application from ground up. It covers the full lifecycle of a SOA project - requirements gathering, design, implementation and testing. If you are getting started with SOA development, this class offers a wonderful opportunity for your development team to get a concrete idea for how a SOA application is built. The course consists of both pen and paper labs and hands-on labs using IBM WebSphere Integration Developer V6.0 to build, test and run SOA applications. Note: We can offer the labs using other platforms such as BEA WebLogic or Microsoft .NET. Please ask your sales representative for your customization needs. * What is SOA and why we need this approach. * Enterprise Service Bus (ESB)). * How Enterprise Application Integration (EAI) is achieved using SOA. * How to capture requirements for a SOA project. * How to perform analysis and design. * How to implement services and business processes. * Technical details of XML schema, SOAP and WSDL. * How to test SOA applications.

Target Audience
J2EE developers who are responsible for developing SOA based application integration solutions. Architects who will like to get hands on practical experience developing a full SOA application from start to finish. For a more indepth SOA architecture related training, please use WA1471, Service Oriented Architecture (SOA) for Architects.

Key Topics

• SOA Fundamentals
• - Service Oriented Architecture
• - What's a Service?
• - Service Relationships / Roles
• - SOA and Business Process Implementation
• - Traditional Integration Solution
• - SOA & Business Process
• - Need for Integration
• - Factors that Affect Integration
• - Challenges of Integration
• - Common Solution Implementations
• - Channel Implementation Choices
• - How SOA Does Integration
• - About Services in SOA
• - SOA Helps Business Address
• - Elements of a Service
• - SOA's Goal
• - The Value of Transitioning from Applications to Services
• - Is this a New Concept?
• - Service Architecture is...
• - Interface Transparency
• - SOA Enhancements
• - Challenges to Services Assembly
• - Enterprise Service Bus (ESB)
• - ESB Features
• - Challenges in Process Implementation
• - SOA Capabilities
• - Web Services
• - Web Service and SOA
• - How Web Services Work
• - SOAP
• - UDDI
• SOA Case Study
• - STC Challenges
• - Acme Challenges
• - How Can SOA Help STC?
• - How can SOA Help Acme?
• - Additional Benefits Made Possible by SOA
• - Acme and STC's Use of SOA
• ESB and SOA Patterns
• - Service Oriented Architecture (SOA)
• - Service Invocation
• - Business Process
• - Enterprise Service Bus (ESB)
• - Legacy System Integration
• - Unsupported Protocol
• - The Role of ESB in SOA
• - Minimum ESB capabilities
• - Minimum ESB capabilities - Integration
• - Minimum ESB capabilities - Communication
• - Minimum ESB capabilities - Service Interaction
• - Minimum ESB capabilities - Management
• - Security and ESB
• Advantages of SOA
• - Learn By Example
• - Traditional EAI Approach
• - Problems With Traditional EAI Approach
• - Enter Service Oriented Architecture (SOA)
• - Build the Services
• - Build the Process
• - We Can Easily Change the Process
• - Change Flow Using Legacy Approach
• - Replacing an Application
• - Other Advantages
• - Business Advantages
• - Adoption Stages
• - Research
• - Savings
• Software Platform for SOA
• - Software Tools for SOA
• - The Need for a Tool
• - SOA Development Life Cycle
• - IBM Software Offering
• - Other IBM Software Options
• - Rational Application Developer (RAD)
• - Key Features
• - Web Services Support
• - WebSphere Integration Developer (WID)
• - Runtime Products for SOA
• - TIBCO BusinessWorks
• - TIBCO SmartMapper
• - IBM WebSphere Application Server
• - IBM WebSphere Process Server
• - WebSphere Message Broker
• - WebLogic Integration
• Introduction to WebSphere Integration Developer (WID) v6
• - WebSphere Process Server v6
• - WebSphere Integration Developer (WID) v6
• - SCA Basics
• - Wiring Example
• - Key Features of WID
• - Perspectives, Views and Editors
• - Creating Artifacts
• - Unit Testing Artifacts
• Introduction to Service Oriented Analysis & Design (SOAD)
• - Introduction to SOAD
• - Applying OOAD Principles
• - Abstraction
• - Abstraction in SOAD
• - Encapsulation
• - Encapsulation in SOAD
• - Modularity
• - Modularity in SOAD
• - Hierarchy
• - Hierarchy in SOAD
• - Why OOAD is not Enough
• - Granularity
• - The Need for Loose Coupling
• - The SOAD Methodology
• - The SOAD Methodology Steps
• - Stage 1 - Process Modeling
• - Stage 2 - Service Identification
• - Stage 3 - Service Design & Implementation
• - Stage 4 - Process Implementation
• Software Methodology - RUP Approach
• - Software Methodology
• - The Rational Unified Process
• - Inception Phase
• - Elaboration Phase
• - Construction Phase
• - Transition Phase
• - Software Development Life Cycle and the Rational Unified Process
• - In a SOAD World
• - New Artifacts
• Stage 1 - Business Modeling and Use Caseses
• - Stages of SOAD
• - Stage 1: Business Process Modeling
• - Requirements Workflow
• - What Is A Requirement?
• - Business Models
• - Use Cases
• - Example: Requirement For A Supply Chain Management Application
• - Classifying Use Cases
• - Use Case Modeling Steps
• - Finding Use Cases
• - Identified Use Cases or Business Processes
• - Finding Actors
• - Various Actors of: Supply Chain Management Application
• - Diagramming Use Cases
• - Example: Use Case Diagram in UML
• - UC1: Purchase Goods Use Case
• - Modeling the Business Processes
• - Use Case and Business Process
• - Trading Partner Design Pattern
• - Best Practices
• Stage 2 - Service Identification
• - Stages of SOAD
• - Identifying Services
• - Produce Service Specification
• - Functional Areas of The Business (a.k.a. Subsystems)
• - Services Belonging To These Functional Areas
• - Functionalities Belonging To These Services (User's Standpoint)
• - Documenting Service Hierarchy
• - Output of Stage 2
• - Retailer Service
• - The Service Is Further Described By Creating
• - Example of the WSDL File for the Retailer Service
• - Part Of The Schema File for the submitorder Operation
• - Best Practices
• XML Programming
• - Data and Document Structure
• - An Employee Document
• - Tags
• - First XML
• - Markup Languages
• - What is XML ?
• - Why XML?
• - An Example of XML Document
• - Well-formed vs. Valid XML Document
• - Enforcing Validity: DTDs
• - Presentation Style
• - Sections of an XML Document
• - XML Elements
• - Nesting and Hierarchy of XML Elements
• - Tag Attributes
• - Naming Rules
• - Namespaces
• - Using Namespaces
• - Java API for XML
• - The XML Example
• - Example SAX Handler
• - Example: Begin Parsing
• - Once Again With Namespace
• - Using DOM to Parse
• - With Namespace Enabled
• - Example: Build DOM Document
• - Example: Save DOM Document in a File
• XML Schema Basics
• - What is XML Schema?
• - Creating a Schema File
• - Defining a Simple Element
• - Defining a Complex Element
• - Defining Element Attributes
• - Referring to an Element From Another Element
• - Defining Abstract Data Types
• - Adding Restrictions
• - Referring to a Schema from a XML Document
• Web Services Description Language (WSDL)
• - WSDL Overview
• - WSDL Document Tags
• - WSDL Namespaces
• - Sample WSDL Document Structure
• -
• -
• -
• -
• -
• -
• - One-way
• - Request-Response
• - Solicit-Response
• - Notification
• - Modeling Simple Operation
• - Modeling Complex Operation
• - Modeling Complex Message
• -
• - More on
• - Syntax
• - SOAP Binding Example
• - and
• - More on
• - WSDL SOAP Binding Extensions
• - soap:binding
• - soap:operation
• - RPC or Document Style?
• - WSDL API for Java
• Simple Object Access Protocol (SOAP)
• -SOAP In Protocol Stack
• - SOAP Components
• - Message Envelope
• - Message Envelope - Headers
• - SOAP HTTP Request Example
• - SOAP HTTP Response Example
• - Header Attributes
• - SOAP Body
• - SOAP Fault
• - Communication Style
• - RPC/Encoded Style
• - RPC/Literal Style
• - Document/Literal Style
• - Document/Literal Wrapped Style
• - Details of the Wrapped Style
• Stage 3 - Service Design and Implementation
• - Stages of SOAD
• - How is a Service Developed?
• - Top Down Development
• - Web Service Implementation Choices
• - Apply OOAD in New Service Development
• - Retailer System - Identifying System Level Use Cases
• - Finding Classes And Relationships From Use Cases
• - Noun/Verb Analysis
• - Example: Noun/verb Analysis
• - Refinement
• - Classes Identified for the Retailer Subsystem
• - Final List of Classes Identified for the Retail System
• - The Class Diagram
• - Class Notation in UML
• - Class Diagram The Retailer System
• - Top Down Summary
• - Bottom Up Development
• - Bottom Up Technology Choices
• - Data Mapping
• - Interface Mapping
• Web Services Software Development Methodology
• - Need for a Software Methodology in Web Services
• - The Software Lifecycle
• - Software Lifecycle
• - Service Provider
• - Provider: Green Field
• - Provider: Top-down
• - Provider: Bottom-up
• - Provider: Meet in the Middle
• - The Service Requester
• Stage 4 - Business Process Implementation
• - Stages of SOAD
• - Business Process Diagram
• - Challenges in Process Implementation
• - BPEL4WS
• - Partnership
• - Example: a Buy-Sell Partnership
• - Modeling Partnership in BPEL
• - Variables
• - Simple Activities
• - Invoke Activity
• - Structured Activities
• - Lifecycle of Process Development
• - Phase II Process Definition Details
• - Phase III Compilation Details
• - Phase IV Deployment Details
• - Phase V Business Process Execution
• - What is a Good Process Design?
• - Follow Integration Patterns
• - Additional Process Design Considerations
• Testing Fundamentals
• - Section Layout
• - Testing
• - What is a Bug?
• - Common Types of Bugs
• - Best practices in bug reporting
• - Characteristics of a Good Problem Report
• - Typical States a Bug Goes Through
• - The Goals
• - Requirements of a System
• - The Use Case Document
• - UC01 - Add a New Appointment
• - Supplementary Specifications
• - Knowing the Testing Priority
• - The Severity Scale
• - The Priority Scale
• - The Likelihood Scale
• - Priority of Coverage
• - Beware of Test Escapes
• SOA Testing
• - Challenges of SOA Testing
• - SOA: Functional Testing for Services
• - Testing - Stages
• - Basics of Unit Testing
• - The Role of Emulators
• - Unit Testing a Service
• - Unit Testing a Business Process
• - Functional Testing
• - Types of Testing
• - Function Testing Incomplete Systems
• - Stress Testing
• - Stress testing tools
• - Designing stress test systems
• - Designing Stress Test Systems
• - Security testing
• SOA Testing Tools
• - Purpose of Testing Tools
• - What's New in SOA Testing
• - Empirix Inc: e-Test Suite
• - Empirix Inc: e-Test Manager Enterprise
• - Parasoft - SOA Test
• - Optimyz - WebServiceTester
• - Mindreef - SOAPScope
• - SOAPScope - Comparing WSDL Files
• - Checking WSDL for Compliance
• - SOAPScope - Analyzing Files
• - Viewing Methods in WSDL File
• - SOA Testing Features - Comparison
• - SOAPScope - Weather Application Testing
• - SOAPScope - Testing Scenario for Weather Application
• - SOAPScope Testing Scenario Step 1: Import a WSDL File
• - SOAPScope Testing Scenario Step 2: Invoke method(s) used
• - SOAPScope Testing Scenario Step 3: Test / Record
• - SOAPScope Testing Scenario Step 4: Store Test Runs
• Web Services Security (WS-Security)
• - The Challenges
• - Public Key Infrastructure (PKI)
• - Digital Signature
• - Overview of WS-Security
• - Integrity
• - Example: Signed XML Document
• - Canonicalization
• - Confidentiality
• - SOA Security Model
• - SOA Security Policies
• - Transport Level Security Policy
• - Message Level Security Policy
• - Data Level Security Policy
• - Security Tokens
• - Standards and Mechanisms for SOA Security
• - Securing Data
• - XML Digital Signatures
• - XML Encryption
• - WS-Security Tokens
• - WS-Security Considerations
• - WS-Security Extensions - WS-Trust
• - WS-Security Extensions - WS-SecureConversation
• SOA Governance
• - Challenges in Implementing and Managing SOA
• - SOA Challenges - Training
• - SOA Challenges - Emerging Standards
• - SOA Challenges - Immature Server Runtimes
• - SOA Challenges - Newer Methodologies
• - SOA Governance
• - SOA Governance Model
• - Managing Risk
• - SOA Governance Processes
• - Some Best Practices
• - SOA Project Roles
• SOA Anti Patterns
• - What are Antipatterns
• - Technology Driven SOA Adoption
• - So What's New?
• - SOA is the Cure All
• - Web Service is SOA
• - The Silo Approach
• - Fine Grained Service
• - Point-to-Point Communication
• - Stateful Services
• Appendix A. Patterns
• - Patterns for e-business
• - Quick Note: Application Patterns
• - Quick Note: Runtime Patterns
• - SOA Patterns
• - Exposed Direct Connection Application Pattern
• - Exposed Direct Connection Runtime Pattern
• - Exposed Serial Process Application Pattern
• - Exposed Serial Process Runtime Pattern
• - Advantages of using a Service Bus
• Appendix B. Introduction to UDDI
• - UDDI in Web Services Architecture
• - Businesses and Services in UDDI
• - Static and Dynamic Web Services
• - UDDI Registry Structure
• - UDDI Registry Structure -tModel
• - UDDI Registry Structure
• - UDDI Interactions
• - UDDI in WebSphere

Required Skills/Experience

• Java programming. Beginner level knowledge of J2EE and XML

Fee: $3,000.00

Course Schedule:
Back to Course Description

Austin

Please contact your sales representative for availability.

Charlotte

Please contact your sales representative for availability.

Columbia

Please contact your sales representative for availability.

Hunt Valley

Please contact your sales representative for availability.

Lansing

Please contact your sales representative for availability.

Madison

Please contact your sales representative for availability.

Milwaukee

Please contact your sales representative for availability.

Minneapolis

• Oct 27 - Oct 31

Oak Brook

Please contact your sales representative for availability.

Oklahoma City

Please contact your sales representative for availability.

Phoenix

Please contact your sales representative for availability.

Raleigh

Please contact your sales representative for availability.

San Antonio

Please contact your sales representative for availability.

Schaumburg

• Dec 08 - Dec 12

Tulsa

Please contact your sales representative for availability.

Washington DC

Please contact your sales representative for availability.