Your SlideShare is downloading. ×
  • Like
© The Middleware Company SOA Blueprints
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

© The Middleware Company SOA Blueprints

  • 372 views
Published

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
372
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
4
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. SOA Blueprints Learning Best Practices and Sample Applications for SOA Steve Wilkes Senior Middleware Maven 7 THE MIDDLEWARE COMPANY 09.22.2004
  • 2. AGENDA
    • Why are we doing this?
    • What are the goals?
    • SOA Concepts
    • The Reference Example
    • The Specification
    • Implementations
  • 3. Why are we doing this?
    • SOA is the new old thing
      • The concept has been around for years
      • The practical realization has only recently materialized
    • J2EE had the PetStore
      • Initially a Patterns application without specification
      • Very successful as a learning tool
      • In some ways too successful – people learned architectural anti-patterns in addition to the technology that was shown
    • SOA needs a PetStore not The PetStore
      • Demonstrating SOA best practice requires many applications
      • Industry focus on (inter) communication not eCommerce
  • 4. What are the goals?
    • Part of a long term project, SOA Blueprints aims to:
      • Define a baseline standardized set of enterprise applications
      • Focus on SOA principles
      • Highlight SOA design patterns and best practices
      • Encourage SOA adoption
      • Be industry agnostic
      • Be applicable to as many organizations as possible
    • The specification will lead to:
      • An agreement on SOA terminology
      • A reference open source implementation
      • An implementation by vendors
      • Additional modules with particular industry focus
  • 5. SOA Concepts
    • SOA Much More Than Web Services
    • Common SOA Terms
    • Patterns
    • SOA Platform Requirements
    • Standards
    • Glossary
  • 6. SOA Much More than Web Services
    • Service definition does not include protocol or wire format
    • How many protocols in your organization?
    • WSDL could be the key
    • Service providers should concentrate on the service
    • Service consumers just want to use the service
    • It’s the SOA that allows providers and consumers to communicate
  • 7. Common SOA Terms
    • Common SOA Terms (the specification includes those highlighted in blue)
  • 8. SOA Terms (cont)
    • Synchronous and Asynchronous Services
    • Component Services
    • Data Services
    • Composite (Business) Services
    • Conversational (Workflow) Services
    • Publish-Subscribe Services
    • Service Brokers
    • Exception Handling And Compensating Services
    • Service Security
    • Interception And Extensibility
    • Interoperability
  • 9. SOA Patterns
    • Initial patterns will include:
    • Service Registry and Static Binding
    • Service Registry and Dynamic Binding
    • Service Broker
    • Distributed Service Broker
    • Service Bus
    • Distributed Service Bus
  • 10. SOA Anti-Patterns
    • Overly granular business services
    • Remote access to local services
    • Overuse of XML
    • Use of loose coupling where tight coupling is required
  • 11. SOA Granularity
  • 12. SOA Development Requirements
    • Target implementation environments should provide:
    • Definition of services independent of implementation, location or use
    • Implementation and hosting of services as a provider
    • Location and usage of services as a consumer
    • Assembly of services from other services and business rules
    • Support for synchronous, asynchronous and conversational services
    • Orchestration of application presentation built on services and rules
    • Automated data transformation between disparate data structures
    • Provisioning of local and remote services
    • Support for simulating, testing and debugging of services
  • 13. Standards
    • Standards being considered for inclusion include:
    • WS-I
    • BPEL4WS
    • WS-Security
    • WS-Notification
    • Jini
    • WSRP
    • WS-Manageability
  • 14. Reference Example
    • Common Enterprise Applications (the specification includes those highlighted in blue)
  • 15. The Specified Applications
    • Based around fictitious enterprise - GeneriCo
    • A distributed enterprise wide security mechanism
    • An employee self service portal providing:
      • Authentication
      • Organization Browser
      • Task List Management
      • Expense Reporting
      • Employee Reviews
    • A Product data service
    • Some payroll & supply chain functions as required by the specification
    • A basic HR application for management of employees and departmental structure
  • 16. The Security Mechanism
    • Provide security for:
      • New Applications
      • Legacy Applications
    • Provide indentity management
    • Automate employee security
  • 17. The Employee Portal
  • 18. Employee Portal
    • Utilizes Security Adaptor Services
    • Provide Login / Logout Capabilities
    • Enable Password Change
    • Provide roles based access
      • to pages
      • to portlets
      • to actions
    Authentication
  • 19. Employee Portal
    • Search for Employees
    • Browse Departments
    • Get Department Details
    • Get Employee Details
    Organization Browser
  • 20. Employee Portal
    • View Task List
    • See Task Details
    • Add Tasks
    • Update Tasks
    • Link to Expenses
    • Link to Reviews
    Task List Management
  • 21. Employee Portal
    • View Report List
    • See Report Details
    • Add Report
    • Update Report
    • Authorize Report
    • Pay Report
    • Utilization of Pay Roll Services
    Expense Reporting
  • 22. Employee Portal
    • View Review List
    • See Review Details
    • Add Review
    • Update Review
    • Validate Review
    • Add Ratings
    • Finalize Review
    • Utilization of Pay Roll Services
    Employee Reviews
  • 23. Product Data Services
    • Two Product Databases
    • Different Schemas
    • Want single data service to access product information
    • Enable category listing
    • Enable product listing
    • Needs to generate unique keys
    • Add missing information
    • Query across sources
  • 24. Message Definition
    • Messages are defined within the specification in a platform agnostic fashion:
  • 25. Process Definition
    • Processes are also defined in an agnostic way:
  • 26. Implementation Guidelines
    • Specification is platform agnostic
    • Database schema will be supplied
    • WSDL will be provided for all services
    • Service testing will be provided by PushToTest
    • Transport protocols must be adhered to
    • Use of Portal server is recommended
    • Web design should follow guidelines
    • Standards should be adhered to where stated
  • 27. Vendor Implementations
    • Currently have commitment from the following vendors to provide implementations of the reference example:
    • BEA Systems
    • Diamelle Technologies
    • IONA Technologies
    • Microsoft
    • Oracle
    • Pramati
    • Sun Microsystems
    • Rogue Wave Software
  • 28. Open Source Implementation
    • Looking to build open source team
    • Currently have a number of committed members
    • Technologies we’re hoping to use include:
      • Hibernate for persistence
      • Spring as a lightweight container
      • Axis for web service provisioning
      • eXo as an enterprise portal
      • Twister as a BPEL4WS engine
      • Maven for build and management
    • Will become reference implementation for SOA
  • 29. Possible Interesting Things
    • An additional 10 or so vendors want to enhance the spec
    • Service management (Qos) an interesting add-on
    • Jini message board talking about an implementation
    • Some vendors considering CORBA implementation
    • Would like to include Mobility component
    • WSRP seems natural extension to Portal specification
    • Including more standards is a must
    • Launching an SOA Blueprints Wiki very soon
    • Open Source Implementation home announced soon
  • 30. Next Steps
    • Q & A
    • Goto soablueprints .com
    • Download the specification
    • Send us feedback
    • Get involved in open source implementation
  • 31. TheServerSide.com TheServerSide.NET MiddlewareRESEARCH.com Steve Wilkes Senior Middleware Maven 7