This document discusses requirements for presentation layer solutions in service-oriented architectures. It notes that presentation layers need to cater to different experiences like rich internet, thin HTML, portals and desktop. It also stresses the need to manage security, performance, cross-browser compatibility, and other issues in a unified way across the enterprise. The document advocates separating presentation, process and integration logic into distinct layers to promote re-use and flexibility.

1. This Presentation Courtesy of the
International SOA Symposium
October 7-8, 2008 Amsterdam Arena
www.soasymposium.com
info@soasymposium.com
The Front Tier of SOA
Founding Sponsors Requirements for the Presentation Layer
Platinum Sponsors
2008
Gold Sponsors Silver Sponsors
©edge IPK Limited 2
1

2. The next logical step…
Data Integration Process Presentation
Middleware BPM
EAI Web Services
3 Managed Complexity 4
©edge IPK Limited ©edge IPK Limited
2

3. A single layer across the enterprise ! Front end to SOA and BPM
Presentation
Rich Internet Thin HTML WAI Compliant Portal Desktop
Data Integration
Process
Middleware
EAI
Business
Web Services Orchestration Workflow
LEGACY SOA BPM
Solution
Message Based Transactional “Screen scraping” API
Data
Relational File based / XML Documents / Images Other
©edge IPK Limited 5 ©edge IPK Limited 6
3

4. No 1: Cater for different experiences
Presentation
Rich Internet Thin HTML WAI Compliant Portal Desktop
Requirements for presentation  Rich Internet – Ajax enabled
“infrastructure”  Thin HTML
 WAI Compliant
 Portal – JSR 168
 Desktop – offline
 Typically these different experiences would require
different skills and create “presentation silo’s”
©edge IPK Limited 7 ©edge IPK Limited 8
4

5. No 2: Manage Security No 3: Manage Performance
 OWASP Top Ten:
www.owasp.org  Cross Site Scripting
 Injection Flaws  Application level approach needs to be agnostic /
 Malicious file execution
 Insecure direct object reference open to physical architecture
 Cross site request forgery (CSRF)


Information leakage and improper error handling
Broken Authentication and Session Handling
 Smart - Cache
 Insecure cryptographic storage
 Growing issues  Insecure Communications  Data
 Failure to restrict URL Access
 Application level implementations lead to:  Content
 Duplication of effort, cost and time  Smart compilation
 Inconsistency  Compression – gZip
 On-going management burden  Multi-threading
 Multi-processor
©edge IPK Limited 9 ©edge IPK Limited 10
5

6. No 4: Manage Cross Browser No 5: Memory Efficiency
 Internet Explorer losing ground  Smart allocation of session memory
 60-65% Internet Exploror, 30-35% Firefox, 3% Safari  Allocate as required
 Safari is where Firefox was 4 years ago  Clear at “process end points”
 Consider browsers on new devices  Create “global session stores” where possible
©edge IPK Limited 11 ©edge IPK Limited 12
6

7. No 1: Avoid Presentation Silo’s
 Consider same application but different:
 Channel (Call centre, internet, back office, ...)
Requirements for developing  User (Staff, customer, broker, ...)
 Language – international & channel/user specific
presentation layer solutions text
 Devices (Big screen, medium screen, small screen)
 Brand
 .........basically any variation
©edge IPK Limited 13 ©edge IPK Limited 14
7

8. No 2: Create layers Layered Presentation Logic
Presentation Output
 Model View Controller + Style Sheets – not enough !
Experience Language Device Other ...
 Clear separation of Presentation, Process, Integration
 Many presentations of a process
 Change integration points without changing
Presentation Process
process
 Think about “enforcement”
Session Data
 Pagination is a constraint of CSS/HTML and MVC
Presentation Integration
 Will become a key issue in future for multi-device Web
Java Com Other ...
support Services
©edge IPK Limited 15 ©edge IPK Limited 16
8

9. No 3: Create Re-use No 4: Skills, Productivity and Maintenance
 “Fragment”, Snippets, etc... Create libraries, then use  Front end development requires knowledge of many
them languages – HTML, CSS, Javascript, J/ASP, Java, C#
 Dynamic re-use etc...
 WSRP  Consider tools that auto-generate applications
 Dynamic re-use in web apps  Consider tools that avoid scripting and enable
evolutionary prototyping
 Manage versioning  Documentation – use tools to auto-generate
 Debugging – use tools that work in the browser as well
as server side
©edge IPK Limited 17 ©edge IPK Limited 18
9

10. Summary: HTML is simple, web applications aren’t ! Summary
Security Performance Resiliance
• Cross site script • Data caching • Session failover
• SQL Inject • Page caching • Clustering In selecting RIA tools remember:
•… •… •…
Business requirements may drive “silo based” presentations
It is possible to have rapid prototyping and an agile solution
Maintainability Technologies RIA is not only online web applications using Ajax, but also
• Documentation Web Application • Javascript/HTML
• Ease of • XML/CSS/XSD
portal, offline
Requirements
understanding • SOAP, …
• Debugging … RIA is not just client software, think about the “presentation
infrastructure”
Presentation infrastructure is not just about “rendering”
Cross Browser Architecture Experience
Compatibility • Design for re-use • Rich (Ajax)
• Agility, ease of • Portal (JSR168)
IE, Firefox, Opera… change • WAI (XHTML 4)
•… •…
©edge IPK Limited 19 ©edge IPK Limited 20
10

11. We can help you avoid simply doing this with RIA edge IPK
Thank you!
Hope you found this informative!
dharmesh.mistry@edgeipk.com
©edge IPK Limited 21 ©edge IPK Limited 22
11