Course Details


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Course Details

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