SOA an architecture on the Desktop

1,031 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,031
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

SOA an architecture on the Desktop

  1. 1. TA92 SOA: Une architecture jusqu’au poste de travail Vincent Perrin EMEA Lotus Technical Sales 2
  2. 2. Agenda At the quest of a new Rich Client Platform ? Extend the SOA beyond the Data Center Lotus Expeditor Architecture Samples 3
  3. 3. Enter SOA – Services Oriented Architecture … a service? … service oriented architecture (SOA)? A repeatable An IT architectural business task – e.g., style that supports check customer credit; integrating your open new account business as linked services "SOA impacts every aspect of IT and business.” 4
  4. 4. SOA & User Interaction Portal Rich Client SOAP Request (J2EE, .NET) B2B Flow – Interactions Process Data Existing Applications Business Process 5
  5. 5. Enterprise Portals Represent a Compelling First SOA Project “Through 2007, an enterprise portal will be the first major application of SOA concepts for more than 50 percent of enterprises (0.6 probability).” Analytical source: Gene Phifer, Gartner Research; Publication Date: 12 October 2005/ID Number: G00132930 Gartner 10/12/05 6
  6. 6. Extend SOA beyond the Data Center (the “Edge”)Customer Reasons for shift to Rich “…Growing trend back from browser- Clients based thin clients to something in the middle – richer, smart clients…” Better (faster and consistent) response time on the Web based UI 48% of future enterprise desktops deployed will be rich clients… "Richer" UI than available in a Browser Ability to integrate existing "Client based" applications into their web applications Local business process execution (enabling mobility if needed) 2002 Source: Giga: Return to the Rich Clients 2005 7
  7. 7. “Good things” we learned from the past Insulation from the native Operating System – The browser is a device which allows a web page to be displayed (and executed…) independently from the underlying Operating System – The browser provides an execution shell Role-based interaction – Most browser-based applications deliver content based on the user profile – A “portal” is very good in Identification, Authorization and Authentication Role-based aggregation – Most modern browser interface provide content coming from aggregating different sources – A “portal” is very good in Aggregating information Zero Management – The last version of an application is always delivered… – … the browser “cache” plays a nice role Zero-footprint – The browser itself is not “zero footprint”… – … but the browser-applications are ! 8
  8. 8. Rich Client – Common Concepts Establish a “Client-side Container” that Insulates from the Operating System Provides added-value services Defines a framework onto which to provide applications Rich desktop user experience and platform independence High-performance extensible platform Client-side processing and caching More responsive user experience Lower server loads Local data access Intermittently-connected mode Provide 360º aggregation and integration Both with the server … but also with local, native-client applications … and with the “Internet” world ! … But with a “web-like” manageability model To avoid the high cost of deployment and management Central server-based application provisioning and policy 9
  9. 9. Design Considerations Topology – Target device(s) (desktop, mobile device, or both) – Device capabilities (processor speed, memory, form factor) – Connectivity (always, intermittent, never or rarely) – Network capabilities (speed, cost, reliability) Interaction – Web or portlet user interface – Rich client application (GUI) user interface – Service-only (i.e. no user interface aka “headless”) Business logic – Online vs. offline operation – Distribution across tiers – Reusability across applications (and devices) 10
  10. 10. Design Considerations (continued) Persistence – Online vs. offline operation – Local data organization and access – Local data protection (if any) – Synchronization and conflict resolution – Amount and frequency of data distribution – Configuration Messaging – Online vs. offline operation – Security – Synchronous vs. asynchronous messaging – Transactional, event-driven, web services – Configuration Management – Componentization and distribution – Data formats Serviceability 11
  11. 11. We took the challenge ! Low Traditional Managed CO Goal: Rich portal- Browser Rich User wT based applications Applications Experience Lo enhanced with rich at user experience Cost of na lity Ownership nc tio Rich, Windows-centric uTraditional FClient / Server applications with R ich Applications connection to network, eve server resources hi e.g. Office, Notes High Ac Richness of Applications Basic Rich and Environment 12
  12. 12. Agenda At the quest of a new Rich Client Platform ? Extend the SOA beyond the Data Center Lotus Expeditor Architecture Samples 13
  13. 13. Lotus Expeditor A Server Managed Client platform that extends SOA apps to desktops, laptops, kiosks and mobile devices Desktop role-based process- Laptop driven in context Kiosk PDA/Smartphone 14
  14. 14. Lotus ExpeditorIncreases responsiveness and improves end user productivity by accessing composite applications regardless of network connectivity Call Center Retail Knowledge Field Bank Teller Agent Kiosk Worker Service Look up Customer Look up Access Info., suggest account Info. Access LOB Fill out work product services, answer and transfer applications orders catalog questions funds Always on / Always Connected Semi-Connected 15
  15. 15. Key Aspects of Expeditor Client 16
  16. 16. Lotus Expeditor: Web Enables web-based applications to become part of desktop Support all full featured web content – HTML + CSS + DHTML + JavaScript – Ajax (JWL, DoJo, Custom, Etc. ) Support Extensions – “Common” Browser Plugins (e.g. Flash, PDF, etc.) – Applets – ActiveX Controls (Win2K, WinXP only) Provide Lockdown Browser – URL management – Access Control 17
  17. 17. Lotus Expeditor: Rich Compelling user experience across platforms Enable Platform native look and feel … Enable Drag and Drop Enable Keyboard integration Enable 2D and Vector Graphics Enable Hardware Device Integration Enable protection from OS Level Changes 18
  18. 18. Lotus Expeditor: Composition Seamless Integration of client applications Enable “Mashups” across pre-existing and new application types – Swing, AWT, Native, .NET, Web, Portlet, Forms, – RCP, Flash/FLEX, Text Terminal, Etc. Expeditor – Local data integration between apps – Local event integration between apps – Create new views on existing apps Sametime Portlets Enable complete Desktop mgmt – Optimize real estate – Control overall look and feel – Custom branding – Configurable access Workplace Forms 19
  19. 19. Lotus Expeditor: Connections Enable better responsiveness – Minimal round trip to server(s) Improve end to end scalability – Locally hosted business logic Enable transparent server interaction when server becomes available – Outgoing - Complete transactions when connected – Incoming - Refresh/Update local content when connected Enable mobility – “Full” disconnected for long periods of time (i.e.: on an airplane) 20
  20. 20. Lotus Expeditor: Managed ClientInstall, configure and maintain both the platform & the applications Enable flexible points of control – One time setup; subsequent lockdown desktop Lockdown browser (URL, Access Control, etc.) Lockdown composite applications – Dynamic, self managed by end user – Dynamic centrally managed via server Continue to maintain a lockdown user view of the system – Combinations of end user and central server managed Enable central visibility – Applications – Configurations – History, Inventory and Status Enable remote access – Administrator scheduled jobs on the client 21
  21. 21. Expeditor MobileThe same value and services as desktop, enabled on mobile devices Windows Mobile 5, Symbian 22
  22. 22. Agenda At the quest of a new Rich Client Platform ? Extend the SOA beyond the Data Center Lotus Expeditor Architecture Samples 23
  23. 23. Lotus Expeditor Foundation for Client Technologies Desktop PCs –Desktop User Experience Client Footprint, Packaging Function, Richer UI Collaboration Services Larger Mobile Devices Technologies (Laptops, Tablet PC’s, PDA’s, Smart phones) – Expeditor Interaction Services Mobile User Experience Small Mobile – Basic Access Services Mobile User Experience Managed Client Services and Platform Mgmt Embedded - No Local User Experience Operating System (multiple) 24
  24. 24. Client Architecture Enterprise / ISV Applications Web Application Embedded Rich Client Composite Application Browser Rich Text Editor Spell Check Portlet Viewer Perspective Perspective Infrastructure UI Mobile Restricted Preference Workbench UI Personalities Application Launcher Application Manager Extensions Workbench Pages JFace SWT Eclipse UI Extensions Help System Draw2D GEF Provisioning Eclipse Core Extension Point Framework (Eclipse 3.2) Transaction Web Web Services OSGi Property Network Managed JMS JNDI Enterprise Container Container Client (JSR172) Event Admin Broker Awareness Settings Portlet ManagementMicro XML JDBC Web Services Agent Sync Container WSRF WSRP JAAS SSOBroker Parsing DB2e/Cloudscape Provider Manager MQe (JSR 168) OSGi DB Web Services Web ServicesMQTT XSD SDO EMF EMF Keystore Accounts SyncML ISync Services Lifecycle Security (OASIS) Client (JSR101) OSGi R4 Java Class Library (jclDesktop, Java SE 5.0) Virtual Machine (IBM J9 Technology for jclDesktop or JavaSE 5.0) Windows XP Pro Windows XP Tablet Windows XP Home Windows 2000 RedHat RHEL WS 4 Novell Linux Desktop 9 25
  25. 25. Lotus Expeditor Client for Desktop End-to-End Connections with Expeditor and Portal servers Applications Applications Lotus Expeditor Client for Desktop Administer layout, aggregation, and Lotus Expeditor Portal Projection access control based on role Portal Aggregator Server Portal policy provider Rule-based administration of Portal Policies Portal Server configuration and preferences Web Services Consume and publish web services Web Services SyncML Libraries Synchronize objects {SyncML Libraries} MQe Send and receive secure transactions MQe Server Enterprise DB2e or Cloudscape Synchronize relational data DB2e Sync Server SGDB Server-managed software Enterprise Mgmt Agent installation and maintenance DMS User-driven software Provisioning installation and maintenance Eclipse Update Site Managed Client Services WebSphere App Server Client Enterprise Server(s) 26
  26. 26. Agenda At the quest of a new Rich Client Platform ? Extend the SOA beyond the Data Center Lotus Expeditor Architecture Samples 27
  27. 27. Lotus Expeditor – Core of Lotus Rich Clients Lotus Notes 8.0 Lotus Sametime 7.5 Lotus Expeditor 28
  28. 28. Composite Application 29
  29. 29. ActiveXDesktop Integration Java Components Applications Web Applications HTML Portlet Applications System Services Text Terminal Java Apps Emulator 30
  30. 30. Expeditor for Devices 31
  31. 31. Our mission… Make more people… more productive… in the context of what they do… everyday 32
  32. 32. IBM Managed Client ! Destops Browser Mobile Clients 33
  33. 33. For more information… IBM home page www.ibm.com Lotus software home page www.ibm.com/lotus Lotus Expeditor http://www.ibm.com/software/sw-lotus/products/product1.nsf/wdocs/expeditor 34

×