making the move from rich clients to browsers

35
© 2013 Wellesley Information Services. All rights reserved. Making the Move from Rich Clients to Browsers Rahul Garg | IBM Jeff Foster | IBM

Upload: rahul-garg

Post on 21-Jan-2015

584 views

Category:

Technology


0 download

DESCRIPTION

Standardizing on browser clients presents numerous benefits to many organizations in terms of cost, maintenance, flexibility and ease of use, but making the transition requires thought and planning. Get an understanding of the business drivers supporting standardization on browser clients as well as the unique benefits of making such a move. Learn important architectural and functional differences between the rich client and browser client as well considerations for your server infrastructure and how to optimize performance. Get advice on how to easily extend your existing IBM Notes client based applications out to the world of browser users.

TRANSCRIPT

Page 1: Making the move from rich clients to browsers

© 2013 Wellesley Information Services. All rights reserved.

Making the Move from Rich Clients to Browsers

Rahul Garg | IBMJeff Foster | IBM

Page 2: Making the move from rich clients to browsers

2

Please Note:

Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion.

Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision.

The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

Page 3: Making the move from rich clients to browsers

3

What We'll Cover

• Trends driving move to browsers• Client considerations• Application considerations• Server considerations• Wrap-up

Page 4: Making the move from rich clients to browsers

4

Trends Driving Move to Browser Clients

• Driving down Total Cost of Ownership (TCO)• Enterprise Web Applications• Role of Smart Devices• Bring Your Own Device • Browser is the new Operating System• Cloud Storage

Page 5: Making the move from rich clients to browsers

5

Trends• IBM Collaboration Solutions Web Apps• Role of Smart Devices

● Smart phones, tablets, ultra books● Reshaping user expectations on usability● Reshaping need for more expensive clients

• Bring Your Own Device (BYOD)● Web Apps allow no-touch updates● Security data with no data left on device● Build 1 App for multiple devices● Web Technologies HTML5/AJAX help provide native app feel to Web apps● Support calls reduced with one app

• Cloud Storage● Access your data from anywhere on any device

• Faster Connectivity● Broadband @ Home and Office● 4G Mobile Connectivity (Hotspots, Tablets, Devices)

IBM® Connections™

IBM® iNotes™ IBM® Docs™

IBM® Smart Cloud ™

IBM® Sametime™

Page 6: Making the move from rich clients to browsers

6

Browser Advantages

• Ease of access● Any device with a browser and an internet connection● Better performance on lower end machines● Remote access● Work/Life integration

• Removes barriers to consumption of innovation● Avoid hardware/software upgrade cycle lock-in ● Deploy latest product capabilities (server updates)● Common platform for disparate applications

– Cloud-based/Hybrid deployments• Maturation & stability of Web technologies (Java Script, HTML5, CSS,

JSON, etc.)

Page 7: Making the move from rich clients to browsers

7

Driving Down TCO

• Administration costs ● Centralized server management and upgrades● No-touch client upgrade

• Deployment costs ● Easy access via a URL and a browser

• Training costs● Familiar user experience● Consistent user experience between iNotes and Notes

• Increased Stupidity Mitigation Capabilities (ISMC) ● Robust and granular admin policy support● Fewer opportunities for a user to cause mayhem

Page 8: Making the move from rich clients to browsers

8

What We'll Cover

• Trends driving move to browsers• Client considerations• Application considerations• Server considerations• Wrap-up

Page 9: Making the move from rich clients to browsers

9

Client Considerations

• Architectural differences• User Interface (UI) considerations • Feature differences between IBM® Notes® & IBM® iNotes®

• Support information• Cross-pollination of capabilities

Page 10: Making the move from rich clients to browsers

10

Architectural Differences

• Need to internalize change from traditional client/server to server/browser• Has an impact on optimization of servers (more on that later)• iNotes stores mail, contacts, and notebook data in the mail file

● Notes has separate databases for mail, contacts, and journal (notebook)● Synch agents provided to sync contacts and journal to mail file

• iNotes designed to overcome some of the inherent limitations of the browser● Linear navigation model● Large data sets in a single UI● Removing complexity of rich client

• iNotes customizations provided through extended forms file• Not all browser clients are created equal

● Progressive loading

Page 11: Making the move from rich clients to browsers

11

User Interface DifferencesWhich Is Which?

Page 12: Making the move from rich clients to browsers

12

User Interface Differences Notes

Page 13: Making the move from rich clients to browsers

13

User Interface Differences iNotes (cont.)

Page 14: Making the move from rich clients to browsers

14

iNotes 9.0 User Interface

Simplified DatesSimplified Dates

Navigation Bar – Integrates Better with Portfolio Services

Navigation Bar – Integrates Better with Portfolio Services

Dark UI – Updated Styles, Fonts, Icons, Spacing

Dark UI – Updated Styles, Fonts, Icons, Spacing

Widgets Sidebar Panel- Google Gadgets- Drag & Drop

Widgets Sidebar Panel- Google Gadgets- Drag & Drop

Embedded Preview Experience

Embedded Preview Experience

Link to ConnectionsLink to Connections

Link to Browser PluginLink to Browser Plugin

Day-At-A-Glace” calendar view in the sidebar

Day-At-A-Glace” calendar view in the sidebar

Horizontal and vertical preview pane options

Horizontal and vertical preview pane options

Integrated Chat and AwarenessIntegrated Chat and Awareness

Page 15: Making the move from rich clients to browsers

15

Feature Differences Between Notes & iNotes• Key common features in both Notes & iNotes

● Encrypted mail, offline access, follow up flags, doclinks, attention indicators, Sametime integration, IBM Lotus Quickr™, IBM Connections™ Files integration, threads, recent contacts, archive, calendar overlays, livetext, server-side viewers on IBM Doc™, Connections integration, embedded experiences*, Notes links

• What Notes has that iNotes does not have● Notes application support (now with Notes Browser Plug-in no longer a limitation)● Color coded messages based on sender, import of contacts, paste images into editor,

integrated Symphony capabilities, customizable plug ins in side shelf, recent collaborations

• What iNotes has that Notes does not have● Scroll Hints, Mobile device access (without Traveler), ability to launch multiple instances,

Faster launch time

• Client feature comparison posted in Notes & Domino® wiki

* Intended for delivery with iNotes OpenSocial Component

Page 16: Making the move from rich clients to browsers

16

iNotes 9.0 Support Information

• Browser & Operating System Support

Firefox and Chrome are rapidly releasing new versions. iNotes statement on rapid browser releases:● Due to the increased rate at which vendors are now releasing new versions of their browsers, support for

browser updates will only be maintained for the most recent shipping release of iNotes. iNotes product testing on new browser versions will continue at periodic intervals which may or may not align with the browser vendor's release schedule. Should a problem be found when using a browser update with the most recent release of iNotes, we will make every effort to resolve the issue. To expedite this resolution it is our recommendation that you contact the browser vendor as well as IBM Support about the situation.

Microsoft® Windows®

XP Pro, Vista, 7 Win 8Apple® Macintosh®

OS® 10.7, 10.8

Linux®

RHED 6Ubuntu® 12

Internet Explorer® 10.0, 9.0, 8.0

Firefox® 17 ESR or greater

Chrome® 24 or greater

Safari6.0

Firefox® 17 ESR or greater

Chrome® 24 or greater

Firefox® 17 ESR or greater

Chrome® 24 or greater

Page 17: Making the move from rich clients to browsers

17

IBM Connections Mail

“Being in mail without being in mail”

• Lightweight social messaging tool• Provides simple, elegant Web mail and

calendar experience allowing people to remain within IBM Connections

• Quickly manage incoming mail without leaving your social context

• Make informed decisions in real-time with a social approach that brings information and expertise into easy and immediate reach

• Delivered as a plug-in to IBM Connections 4.0

Page 18: Making the move from rich clients to browsers

18

What We'll Cover

• Trends driving move to browsers• Client considerations• Application considerations• Server considerations• Wrap-up

Page 19: Making the move from rich clients to browsers

19

Application Considerations

• XPages• Notes Browser Plug-in for Windows

Page 20: Making the move from rich clients to browsers

20

• XPages – Web 2.0 framework● Use industry standard Web development skills (HTML, CSS, and JavaScript)● Java-based framework facilitates reuse of Java libraries ● One model for Web, Rich Client and Mobile

• Extend the reach of your Notes/Domino applications● Web browser● Mobile Web access● WebSphere Portal and Connections using iWidgets / OpenSocial Gadgets / Embedded Experience

• Notes/Domino apps → Social business apps● Integrate Connections and other social application services (e.g., Facebook, Twitter, Dropbox, etc.)

into XPages applications● Integrate Domino data and services into social business framework

– XPages as OpenSocial gadgets → Embedded Experience– Support for Activity Streams– Secured with SAML/OAuth

• Key decision criteria● Mobile Web access● Integration with other OpenSocial container apps

Modernize with XPages

Page 21: Making the move from rich clients to browsers

21

Notes Browser Plug-In for Windows

• Designed to easily extend applications previously available only to Notes users out to Web browser as well

• Allows applications to run in a browser with no design modification!• Designed to be similar to other popular browser plug-ins in size, deployment, and

configuration needs• Uses iNotes message composition screens on forwards• Copy and paste document links (and copy as table) from Notes application into Web

editors• Icons added to iNotes and Notes Browser Plug-in to easily switch between • Minimal limitations

● Windows only● Firefox, Internet Explorer

Page 22: Making the move from rich clients to browsers

22

IBM Notes Browser Plug-In Homepage

Recent ApplicationsRecent Applications

WorkspaceWorkspace

Link to iNotes integrationLink to iNotes integration

Page 23: Making the move from rich clients to browsers

23

IBM Notes Browser Plug-In

Notes Gutter Selection

Notes Gutter Selection

Page 24: Making the move from rich clients to browsers

24

IBM Notes Browser Plug-In (cont.)

Allows capabilities of Notes rich text editor in the web

Allows capabilities of Notes rich text editor in the web

Notes Tables Notes Tables

Page 25: Making the move from rich clients to browsers

25

What We'll Cover

• Trends driving move to browsers• Client considerations• Application considerations• Server considerations• Wrap-up

Page 26: Making the move from rich clients to browsers

26

Server Considerations

• Admin considerations• Optimizing for performance• Secure deployment considerations

Page 27: Making the move from rich clients to browsers

27

Enabling iNotes Check List

• Enable HTTP on your Domino Servers• Use Standard Mail8 (Mail8.ntf) or later Notes Mail Template• Enable iNote Redirector Application• Enable SSO with your other IBM Applications and Clustered Domino Servers• Enable SSL for security between Domino and client browsers• Deployment Considerations

● Reverse Proxies● SSL VPN's● Web Load Balancer● Integration with Sametime / Files / Quickr● External Access● Local Content → iNotes

– Contacts– Notebook

Page 28: Making the move from rich clients to browsers

28

Optimizing iNotes Performance

• Need to reflect the change in architecture from client/server to browser● Understand where & how the work takes place

– E.g., Notes is able to keep some internal Notes DB structures (like view indexes) open for an extended period of time

– Check client browser settings, especially caching & security

• Upgrade to Domino 9.0 if running an older server release!● Significant CPU & disk I/O savings can be had

• Check server peak CPU usage● Don't extrapolate from one data point to infinity

– Ensure an apples-to-apples comparison – Don’t double/triple current Domino CPU. CPU from user interaction is only a fraction. I.e., You may

have 25% CPU peaks, but only 5% is user triggered, so 2-3x would be 10-15%.● Server may be under-utilized and handle increased load

• Add CPU to upgradeable multi-CPU systems and virtual systems● Keeps server count equal and administration costs equal

Page 29: Making the move from rich clients to browsers

29

Optimizing iNotes Delivery

• Load balance mail files in a cluster● Reverse proxy or load balancer (sprayer)● Move subset of users to machine with more CPU● Client session failover● Server maintenance flexibility

• Web appliances for application acceleration● Cache Web content ● Boost client performance and reduce load on Domino server

• Offload expensive http activity to common Web infrastructure● Move SSL and/or compression to a dedicated device

• Relatively small up-front costs to enable iNotes● Bandwidth and storage is approximately 1 to 1 (Notes to iNotes)● Possible up-front CPU cost, a small part of the email cost model● Possible Web load balancer cost

Page 30: Making the move from rich clients to browsers

30

Secure Access Outside the Firewall

• Virtual Private Network – VPN● Helps provide network level of security to only allow authorized

users in• Reverse Proxy

● Helps provide High Availability as well as Load Balancing• SSL VPN

● Secure Sockets Layer – SSL – Help provides security from packet sniffers by encrypting

data over the network● Helps provide access control for mobile device users outside

the firewall

Page 31: Making the move from rich clients to browsers

31

What We'll Cover

• Trends driving move to browsers• Client considerations• Application considerations• Server considerations• Wrap-up

Page 32: Making the move from rich clients to browsers

32

Where to Find More Information

IBM Notes and Domino Wiki● www-10.lotus.com/ldd/dominowiki.nsf

IBM Webcast - ibm.com/lotus● Customer case studies, downloads

Lotus Developer Domain - www.ibm.com/developerworks/lotus/● Lotus iNotes 8.5 Articles● iNotes Performance and Scalability Papers

IBM Redbooks & Red Papers● www.ibm.com/redbooks

– Lotus Domino Web Access Admin & Deployment Redbook– Lotus Domino Web Access Customization Paper

OpenNTF● openntf.org

Page 33: Making the move from rich clients to browsers

33

7 Key Points to Take Home

• Many trends driving the move to browser clients• First understand the key differences between iNotes and Notes• Have a plan to get your Notes applications on the Web (Notes

Browser Plug-in, XPages, etc.)• Review the enabling iNotes checklist• Review your Web infrastructure for iNotes• Several ways to optimize iNotes for performance• Options for secure access outside the firewall

Page 34: Making the move from rich clients to browsers

34

Your Turn!

Email: [email protected]: @RahulGSJLinkedIn: linkedin.com/in/rgarg

Email: [email protected]: @JeffPaulFosterLinkedIn: linkedin.com/in/jefoster

Follow us: Facebook.com/IBMiNotes

Twitter.com/IBMiNotes

Page 35: Making the move from rich clients to browsers

35

Legal disclaimer

© IBM Corporation 2013. All Rights Reserved.

The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.

References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.

Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft, Internet Explorer and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.

All references to Greenwell Partnership refer to a fictitious company and are used for illustration purposes only.

All references to Renovations Inc. refer to a fictitious company and are used for illustration purposes only.

Android is a registered trademark of Google Inc in the United States, other countries, or both.

FireFox is a registered trademark of Mozilla in the United States, other countries, or both.

Chrome is a registers trademark of Google Inc. in the United States, other countries, or both.

Ubuntu is a registered trademark of Cononical in the United States, other countries, or both.

Apple, iPhone, iPod, iPad, Safari, iOS and Mac OS are registered tradmarks of Apple Inc. in the United States, other countries, or both.