2. Upgrading to Lotus ® Notes ® and Domino ® 8 David Bell | Solution Architect | IBM Software Services for Lotus Tim Speed | Consulting IT Architect | IBM Software Services for Lotus ID103

3. 3 Introductions

4. 4 Agenda Planning the Deployment Deploying Domino 8 Servers Deploying Notes 8 Clients Considerations for Coexistence Q&A

5. 5 Been there, done that.... Hands up if you have been through a Notes / Domino upgrade before ? Keep your hands up if you have been through more than one ?

6. 6 But first, what is a "Best Practice" ? ■ Wikipedia defines it thus… Best Practice is a management idea which asserts that there is a technique, method, process, activity, incentive or reward that is more effective at delivering a particular outcome than any other technique, method, process, etc. ■ …but also goes on to say: T he notion of 'best practices' does not commit people or companies to one inflexible, unchanging practice. Instead, Best Practices is a philosophical approach based around continuous learning and continual improvement. 6 “When you see me, I am pointing out a good practice !”

7. 7 Overall Upgrade Approach ■ 1. Planning the Deployment  Evaluate the existing environment  Evaluate the system requirements  Research, evaluate, prioritize new features  Begin testing  Chart the course ■ 2. Deploying Domino 8 Servers  Upgrade vs. new install  Define the deployment sequence  Build procedures  Perform a pilot deployment  Execute deployment procedures 3. Deploying Notes 8 Clients  Evaluate the installation mechanisms  Choose the installation mechanisms  Create client install packages  Build procedures  Perform a pilot deployment  Execute deployment procedures 4. Dealing with Coexistence  Templates and design elements  System databases  Existing applications  New features

8. 8 Upgrade Process – 5 Important Principles ■ Five guiding principles for a successful deployment: １．Planning ２．Communication ３．Minimization of Labor and Effort (Automation) ‏ ４．Maximization of the Bang For The Buck (Opportunity) ‏ ５．Measurement and Management

9. 9 High Level Deployment Planning ■ Business Drivers  What is the driving force behind the upgrade ? ■ Define Project Expectations  Document the benefits that are expected and communicate them ■ Architecture Planning  What is the scope of this upgrade project ? ■ Test Planning  What and how are we going to test ? ■ Training and Communication Requirements  What training do we need to provide ? (Admin, Engineering, Support / Helpdesk, Users)  How do we market the upgrade ? ■ Pilot Planning  How will we pilot and who will be our pilot audience ? ■ Deployment Activity Planning  What are the high level activities and resources that will need to be included ?

10. 10 Evaluate the Existing Environment - ■ Do a thorough investigation of the current state (starting point) and use tools to facilitate data capture  Server infrastructure (incl. baseline statistics, performance, etc.)  Clients / workstations  Applications  3 rd party products ■ Document pre-existing conditions and problems  Try to resolve outstanding issues and problems prior to upgrading  No matter how tenuous the link, an upgrade can be held responsible for any problem whether old or new: "My car won't start, I bet it's because of that upgrade IT did yesterday !" ■ Document things you want or need to address while you have the opportunity, focus and resources available  We have never done an assessment where we could not find something that needed attention  Even environments perceived to be well performing need some attention  There is always cleanup that can be done ahead of time  Use these items as inputs into detailed planning 10

11. 11 Monitoring (Before and After) ■ Monitoring is a critical part of any upgrade even a point release upgrade ■ The goal is to understand your current cost of running the existing environment and to predict a problem before it happens in the new environment  This is really important when are you moving users and/or consolidating servers ! ■ Steps  Make sure you are capturing the available raw data from the servers – Operating system capacity and performance metrics – CPU, memory (usage, paging), disk (usage, I/O rates / performance), network – Domino Server specific statistics – Other components (e.g. SAN switches and disk metrics)  Interpret/analyze the data and create your base lines for your current environment – What are the typical operating parameters for your servers – What is the data telling you about your environment ?  Execute your monitoring processes using your base lines  Create your Daily/Weekly/Monthly reports based on your base lines  Create a remediation process based on outputs that exceed your baselines

12. 12 Evaluate System Requirements ■ Should hardware refresh be included…  …because it has to be ?  …because it is time for an update ? ■ Is our current platform still supported ? ■ Does the current platform fit our strategic needs ? ■ Do we need more or different storage ? ■ Can we or should we consolidate ? ■ Do workstations need upgrades ? ■ What is the support position of each vendor of 3 rd party products ? ■ Lotus Notes/Domino system requirements online:  http://www-306.ibm.com/software/lotus/notesanddomino/sysreqs.html

13. 13 Research, Evaluate & Prioritize New Features ■ Can we eliminate customization by adopting a new feature ? ■ Which features should be introduced…  …that help the upgrade ?  …during upgrade ?  …after completion of the upgrade ? ■ What architectural impacts do new features have ? ■ Do new features impact other infrastructure components ?

14. 14 Research Product and Upgrade Information Sources ■ Leverage your Premium Support Manager (if you have one)  Product-specific information  PMRs / SPRs  Other PSP customer experiences  Assistance with FSS / ISSL ■ Review Public Information  Fix List database  Knowledge Base / Knowledge Collections  Notes/Domino 8 Resources  Forums (developerWorks, blogs, etc.)  Redbooks, Redpapers, Whitepapers  Product Documentation / Release Notes  Product Support Lifecycles

15. 15 Change Management ■ In any organization, change is embraced differently across the user population, represented here by the "Pyramid of Resistance" ■ Change management is an ongoing process throughout the project

16. 16 Communication ■ Things should be done in moderation, except communication  It's almost impossible to over-communicate with the user population ■ The 70/30 rule  Ratio that has been determined through experience and not a variant of Pareto's 80/20 rule  Indicates that 70% of end-users will successfully complete an automated installation process without generating even a phone call for the support staff  Provided the users are given proper communication of the roll-out plan as well as clearly written instructions on how the actual installation process if to be carried out. ■ Any reduction in communication makes this ratio fall quickly ■ Communication is an investment from a project point of view

17. 17 Begin Testing ■ Build a test environment if you don't have one  Try to make it as representative of your current and target hardware and platform as possible including both hardware and software resources  VMWare ® technology is great for quick reset to known starting positions, if not then use other backup/restore capabilities to facilitate rapid repeating and refinement of procedures ■ Use representative data from existing server(s) in performance or capacity tests e.g.  What impact does D8 have on your hardware for performance tests (Server.Load) ?  How long does compact run for a given volume of your data ?  What impact does design / document compression have on your data ? ■ Use results as inputs into defining the detailed plan ■ Use this environment to evaluate design decisions, coexistence strategies, application updates and upgrade procedures

18. 18 Chart the Course ■ Having determined…  …the starting point from your existing environment assessment  …current environment remediation opportunities  …coarse level architectural changes  …new features and their relative priorities of introduction  …testing needs  …training and communication needs  …pilot needs  …etc ■ …put together a detailed plan with activities, resources and time estimates to complete the design, pilot and deployment of the upgrade that will satisfy these needs and requirements ■ From the plan, gain consensus and buy-in from the stakeholders and assemble the project team ■ Try not to schedule multiple significant change events at the same time

19. 19 Project Team & Stakeholders ■ People and groups who need to be involved:  CTO/CIO  Users  Client/Desktop Software team  Deployment Team  Domino Admin/Operations Team  Help Desk/Support Team  Network Admin  Storage Admin  Other Admins (Portal, WAS, DB2, Web Servers) ‏

20. 20 Agenda Planning the Deployment Deploying Domino 8 Servers Deploying Notes 8 Clients Considerations for Coexistence Q&A

21. 21 Deploying Domino Servers – Upgrade vs. New Install ■ Given the defined requirements should servers…  …be upgraded in place ?  …replaced with new servers ?  …or some combination of these approaches ? ■ What impacts will there be on the client configuration ? ■ Should new servers inherit existing identities or have new ones ? ■ There are a range of approaches depending on the answers to these questions, let's take a look…

22. 22 Upgrade Existing Server ■ In place software upgrade of an existing server ■ Server identity remains the same ■ No change of underlying hardware or operating system ■ Upgrade process and configuration testing needs to be done in test environment ■ If clustered…  …upgrade one server at a time in the cluster  …remember that ACL's and replication settings do not prevent designs from propagating in a cluster

23. 23 Install New Server (New Identity) ■ Build new server independently ■ Create new server identity ■ Permits change of underlying hardware and operating system ■ Permits testing of the configured state before cut-over ■ For mail users, requires some migration of users and client configurations from existing to new server ■ Permits monitoring as you ramp up users to verify that you don't overload the 'new' server ■ For applications, requires migration of applications to new server and redirection from old server ■ If clustered…  …create new servers and new cluster  …migrate users and client configurations to distribute users across the members  …migrate applications to new cluster

24. 24 Install New Servers (Inherit Identities) ■ Build new server independently ■ Create new temporary server identity ■ Permits change of underlying hardware and operating system ■ Permits testing of the configured state before cut-over ■ Create replicas on temporary server and keep in synch with server to be replaced via replication ■ At desired time, switch server host, network and Domino server identities ■ If clustered…  …repeat process for each server  …do not add temporary Domino server into cluster ■ Change is transparent to clients

25. 25 Deploying Domino Servers – Deployment Sequence ■ The classic recommended sequence… ■ … but this does not account for organizational, demographic or other such constraints ■ …and it should be used as a guiding principle while taking other factors into consideration

26. 26 Server Build and Deployment Procedures ■ Decide on the approaches needed for upgrade / replacement for each server to meet requirements ■ Decide on the deployment sequences given all of the factors that must be considered ■ Use these as inputs…  …to add further detail to the plan for server build, testing and deployment efforts  …to determine what build, deployment, user and application migration procedures are necessary ■ Define the procedures and validate them in the test environment

27. 27 Server Pilot ■ Determine feedback required from pilot users and success criteria ■ Choose your pilot groups carefully  Start with immediate IT staff, then add lowest risk user populations  Grow the pilot population over time, adopting new audiences  Target diverse roles: technical, power user, assistants, specific application users ■ Perform the upgrade procedures necessary for the pilot  Administration / Hubs / SMTP Gateways (No users)  Start with One (1) Domino mail server ■ Run a steady state environment for the defined duration ■ Review / update procedures after pilot feedback

28. 28 Server Deployment ■ Execute communication and upgrade procedures according to the plan to complete server upgrade ■ Monitor the new environment and compare to the baselines taken during the assessment of the current state  Server performance  Server capacity ■ Applications  8.0-certified apps can be migrated to new Domino 8.0 application server ■ Executives and Assistants often require hand holding

29. 29 Upgrade Checklist ■ Verify you have all of your plans and checklists ready ■ Pilots completed ■ Verify your backups are ready and back-out plan is ready for all steps ■ Change Control is loaded and approved ■ Normalized your environment (fix any crashing servers) ■ Verify that all of your 3rd party products  Not usually a problem with point releases but always worth checking 29

30. 30 Upgrade Checklist ■ Verify the the directory template (pubnames.ntf) is ready ■ Load new directory design (off-line) ■ Test new directory ■ Load / replicate directory into production ■ Run directory maintenance (updall -r ) ■ Upgrade each server as needed  Take a look at using the Server_Upgrade_No_Directory_ReDesign=1 to prevent the directory from being upgraded on each server ■ Add the Create_R8_Databases=1 or Create_R85Databases=1 to each server 30

31. 31 Upgrade Checklist ■ After the Domino code has been loaded then start the server and validate basic operations  You may want to consider using Server_Restricted to block users while allowing administrators to work ■ Shutdown server ■ Complete your standard server maintenance processes and then restart the server ■ Verify that your backup programs work correctly ■ Execute your final test programs and allow users to connect to the server ■ The complete (sanitized) checklist is available for your review with Tim at the ISSL Lab 31

32. 32 Server Deployment – 64-bit Considerations ■ 32-bit Domino to 64-bit Domino Upgrade  All existing full-text indexes will be discarded and rebuilt ■ Windows Only  All existing views currently built will be discarded and rebuilt ■ Updall process will take longer to run ■ Use indirect files to have multiple processes running at once "When you see me, I am thinking about an upgrade consideration !"

33. 33 Server Deployment – ODS48 / 51 ■ Domino 8.0.x uses ODS48; Domino 8.5 uses ODS 51 and their use must be explicitly enabled on the server (and client):  Create_R8_Databases=1  Create_R85_Databases=1 ■ Features requiring ODS48  Optimized User Renames and Deletes  I/O Reduction and Performance Improvements  Enhanced user activity tracking (writes become adds/updates/deletes)  On-Demand view collation builds  Database Design compression  Document Data compression (8.0.1) ‏ – Recommended to not enable this unless running 8.0.2 or later  Enable both design / document compression and upgrade ODS with single copy style compact: – compact -c -n -v dbname.nsf – compact -c -n -v directoryname ■ Features requiring ODS51  Domino Attachment and Object Service (DAOS)

34. 34 Server Deployment – Domino Configuration Tuner ■ Leverage the Domino Configuration Tuner to validate your server configurations  Part of 8.5, but is template based and can be used with prior versions

35. 35 Server Deployment – Disable TCP Nagle Algorithm ■ Prior to Domino 8.5 TCP Nagle is enabled by default ■ Recommended to disable this on Domino prior to 8.5:  DEBUG_PD_NAGLE_OFF=1  Remove EnableNagle from notes.ini ■ As of Domino 8.5 it is disabled by default on all platforms  Remove both DEBUG_PD_NAGLE_OFF=1 and EnableNagle from notes.ini ■ See technote #1165068 - Downloading attachments from Domino R5 on AIX takes a long time  http://www.ibm.com/support/docview.wss?uid=swg21165068

36. 36 Server Deployment – Streaming Cluster Replication ■ Technote #1304671 - Streaming cluster replication does not work as expected  http://www-01.ibm.com/support/docview.wss?uid=swg21304671 ■ Technote #1326162 - Users are unable to retrieve mail through IMAP on Domino 8.0.1 server  http://www-01.ibm.com/support/docview.wss?uid=swg21326162 ■ Disable on all cluster members (8.0, 8.0.1, 8.0.2) using:  DEBUG_SCR_DISABLED=1 ■ Expected to be resolved in Domino 8.5

37. 37 Upgrading Domino Servers – Summary ■ Good planning and research reduces risk and sets proper expectations ■ Know where you are starting from and what you are trying to achieve ■ Don't upgrade a server that is having major problems unless the root cause is fixed in the target release ■ Testing helps to minimize and plan for the unexpected ■ Pilot is your PR campaign and you want it to be positive ■ Successful deployment is directly linked to the quality of your plans and procedures

38. 38 Agenda Planning the Deployment Deploying Domino 8 Servers Deploying Notes 8 Clients Considerations for Coexistence Q&A

39. 39 Client Architecture ■ Lotus Notes 8 Client  Built on Eclipse TM and Lotus ® Expeditor ®  One of many products on one client platform  Same extensions can work with other products (e.g. Lotus ® Sametime ® ) Lotus Expeditor Notes Sametime Expeditor (standalone) Eclipse 3.2 Foundation

40. 40 Lotus Notes 8.x Client - Under the Covers ■ Eclipse framework used to build:  Title bar, menu bar  Toolbar  Launcher and tabs  Views for PIM apps (mail, calendar, contacts)  Status bar  Sidebar ■ Forms built with C++ ■ All non-PIM views built with C++ ■ Preferences dialog uses the Eclipse dialog; most other dialogs still C++ ■ Domino Administrator and Designer clients are still completely C++ based clients

41. 41 Lotus Notes 8.x Client - Under the Covers ■ O ne program directory (with additional subdirectory)  C++ Code – Default - C:\Program Files\IBM\Lotus\Notes – Configurable during clean installation (unchanged during upgrade)  Java TM Code - \framework ■ One data directory (with additional subdirectory)  C++ Code – Default - C:\Program Files\IBM\Lotus\Notes\Data – Configurable during clean installation (unchanged during upgrade)  Java TM Code - \workspace ■ Single client with two configurations  “Standard” – full feature set including new Eclipse UI  “Basic” – reduced set of features for customers with workstations that do not meet minimum requirements, no Eclipse UI ■ Shared network drive for data is not allowed during installation

42. 42 Lotus Notes 8.5 Client - System Requirements

43. 43 Lotus Notes 8.x Client – General Deployment ■ Client install options  Single user - Notes client and All Clients (Notes/Admin/Designer)  Multi-user - Notes client only  No shared network install (program files on server, data on local workstation) available for standard configuration  USB install available for standard configuration back in 8.0.1 ■ Install tools (automation)  MSI-based silent install and Eclipse component provisioning  Smart upgrade  3 rd party software deployment tools ■ Upgrades supported from 6.5.x and 7.0.x  Formally tested in product testing / QA cycles  Earlier versions can be upgraded, watch out for some specific smart upgrade issues/scenarios – http://www.redbooks.ibm.com/abstracts/redp4180.html

44. 44 Lotus Notes 8.x Client – Deployment Automation ■ Engineering is a small portion of the project costs, compared to the labor and effort required to deploy client software  Crucial to automate whenever and wherever possible, to realize benefits: – Labor savings and cost of deployment – Reduced time to value for the users – Improving consistency of the environment ■ The 90/10 rule  If the automation efforts deal with a population or scenario that represents less than 10% of the base there’s a good chance that the point of diminishing returns has been reached ■ Leverage software tools  Generic distribution products (e.g. ZENworks ®, Tivoli ®, SMS, etc.)  Products architected specifically for Lotus Notes client deployment (e.g. InstallShield ®, Automated Deployment Toolkit (ADT), InstallPump ®, etc.) ‏  Built-in tools (SmartUpgrade) ‏

45. 45 Lotus Notes 8.x Client – Maximize Opportunity ■ An automated deployment is your opportunity to correct the sins of the past ■ This would include, but not be limited to:  Relocating client code on the desktop  Setting or resetting mail quotas  Updating configuration settings  Enforcing consistency (i.e. install choices, bookmarks, preferences, certification schemes and hierarchies, etc.)  Better load balancing users across the new environment ■ Ensure a long-term return on investment resulting from reduced help desk costs and take advantage of:  Policies to improve consistency of the environment  DDM improvements (modular correction actions, event clearing, etc.)

46. 46 Lotus Notes 8 Client – Transform File ■ Similar to use in Notes 7  Program and data directory locations  Single user / multi-user  Core C++ client features  Add custom files  Modify registry entries  Modify shortcuts  Add/remove program support contact information  Set default notes.ini settings

47. 47 Lotus Notes 8 Client – Install Manifest (new to Notes 8) ■ Determine which of the default Eclipse features should be included (INSTALL.XML)  Productivity Tools  Composite Application Editor  Activities  Sametime  Feed Reader ■ Remove features from the Eclipse install package ■ Add features to the Eclipse install package

48. 48 Lotus Notes 8 Client – Launch Options ■ If your desktop hardware can't support the Standard client, don't install only the Basic client and then have to revisit that workstation ■ Do a full installation but control which client is launched ■ Use the new (as of 8.0.2) notes.ini variable UseBasicNotes=1 ■ Using this variable rather than a shortcut has the following advantages:  Allows other launch mechanisms such as a MailTo: URL, or launching an NSF file directly, to launch the client in Basic mode not just when launched from shortcut  Can be modified via desktop policy as user workstations are upgraded for centralized control

49. 49 Lotus Notes 8 Client – Anti-Virus Impact on Startup ■ The Notes 8.5 client program footprint contains more than 15,000 files  Lots of small Java archive, XML and properties files ■ Startup time can be impacted by aggressive scanning options ■ Determine whether AV policy is “on change” versus “on access”  On access requires a scan every time a file is used  On change imposes less overhead

50. 50 Client Build and Deployment Procedures ■ Decide on the approaches needed for client upgrade or installation to meet requirements and available software installation mechanisms ■ Use these as inputs…  …to add further detail to the plan for client build, testing and deployment efforts  …to determine what upgrade, install and deployment procedures are necessary ■ Define the procedures and validate them in the test environment

51. 51 Client Pilot ■ Determine feedback required from pilot users and success criteria ■ Choose your pilot groups carefully  Start with immediate IT staff, then add lowest risk user populations  Grow the pilot population over time, adopting new audiences  Target diverse roles: Technical, power user, assistants, specific application users ■ Perform the client upgrade procedures necessary for the pilot ■ Review / update procedures after pilot feedback

52. 52 Lotus Notes 8 Client – Managers and Assistants ■ Take care with manager / assistant delegation ■ Upgrade their clients / templates at the same time to prevent one using features unavailable to the other ■ Useful Technotes #1282123 - What new features in Notes 8 require a Domino 8 server or mail template? – http://www.ibm.com/support/docview.wss?uid=swg21282123 #1264690 - Supported configurations for Notes and Domino 8.x – http://www.ibm.com/support/docview.wss?uid=swg21264690

53. 53 Agenda Planning the Deployment Deploying Domino 8 Servers Deploying Notes 8 Clients Considerations for Coexistence Q&A

54. 54 Upgrade Approach – Considerations for Coexistence ■ Four main topic areas  Domino 6.5.x and Domino 8.x specifics  System databases (directory, policies, room & resource reservations, DDM)  Templates and design elements  Existing applications  New features

55. 55 Domino 6.5.x and Domino 8.x Coexistence ■ Encryption key length and large key support was changed in ND8  Be careful not to employ key roll-over (i.e. keep key strengths the same) until servers and clients are upgraded ■ Support for flat certification for Notes IDs was removed in ND7 ■ Mixed version clustered environments are supported ■ Resource Reservations (upgrade the RR Database to new design immediately)‏ ■ Smart Upgrade (For Notes 6.5.2 or earlier, Smart Upgrade download will not occur as a background task)‏ ■ Don’t upgrade the template before the client; an 8.x mail template with a Notes 6.5.x client will cause issues ■ For users who delegate mail access to others, upgrade both clients to 8.x before either mail template is upgraded ■ Out of Office - Notes 6.5 mail template users cannot utilize the new Out of Office router service on the Domino 8 server ■ Domino 7 and 8 policies will be ignored by Notes 6.5.x clients

56. 56 Coexistence – System Databases ■ Analyze the directory using tools (e.g. TeamStudio ® Delta) against base templates to detail customizations and resolve design issues prior to upgrading ■ Upgrade the Domino Directory offline and deploy to the domain ahead of the first server upgrade  Opportunity to set configurations manually rather than the first server setting them automatically e.g. message recall is enabled by default if the server upgrades the directory design  Take a look at using the Server_Upgrade_No_Directory_ReDesign=1 to prevent servers trying to upgrade design ■ If you must preserve customizations, you can modify the design offline rather than waiting for first server to be upgraded then applying them ■ Admin Requests and Events databases should be upgraded with first server ■ Check admin4.nsf for orphan / abandoned documents with $NoPurge values ■ Resource Reservations changed significantly between 6.5.x and 7.0  If you're upgrading from pre-7.0, ensure you understand the changes and constraints for RR (RnRMgr task instead of router/agents processing reservations, clustering requirements, etc.)

57. 57 Coexistence – System Databases ■ Beware if you edit / update policy documents using agents or API programs ■ Policy settings form has code to remove temporary items in the Save action which are not removed if updated using an agent ■ Two ways to address the issue:  Only edit policy documents using client and provided action buttons  Update your agent or API program with the additional code to remove the temporary items (see technote #1299046) ■ #1299046 - Unexpected Desktop Policy settings pushed to clients after upgrade to Domino 8  http://www.ibm.com/support/docview.wss?uid=swg21299046

58. 58 Coexistence – System Databases ■ Domino Domain Monitoring corrective actions are now disassociated from the actual event form in modular documents ■ The event form has Lotus, Custom and Stock tabs…  …the Lotus tab contains the Probable Cause, Possible Solution and Corrective Actions defined by IBM Lotus Development and ship with Domino  …the Custom tab is where you can enter custom information for these items  …the Stock entries contain pre-8.0 information

59. 59 Coexistence – Templates and Design Elements ■ System database templates have replica ID's that remain consistent from release to release but they are not always replicated across the domain ■ If design task runs on multiple or all servers, either…  …make sure system templates replicate to all servers so if design runs it uses the updated template – or –  …disable or change the design task activity on pre-8.x servers until all old templates have been replaced ■ Standard Mail and DWA are no longer separated; there is one mail8.ntf template ■ Upgrade mail templates after clients have been upgraded  If you don't want to enable design / document compression right away, make sure those options are unselected in the template before applying to new or existing mail files

60. 60 Coexistence - Applications

61. 61 Application Considerations ■ I've planned to upgrade my Domino mail servers but I just remembered that I have applications ■ What do I do now ?  Is it time to panic yet ?  Can I just ignore them ? ■ How much effort is involved ?

62. 62 Applications – Relax & Breathe ■ Historically, Notes/Domino applications have upgraded extremely well  This is no different for Notes/Domino 8  The concept of rip and replace does not exist in the Notes/Domino world

63. 63 Applications - Planning ■ Start thinking about applications from the outset  There is a lot of work that can be done prior to the actual upgrade  Details about your application landscape will be needed in requirements and architectural discussions ■ Create an inventory of applications  This is a great opportunity to clean up your applications environment  Identify – Current owners – The current user population ● Executives, Managers, Entire organization, Small groups of people – Type of application ● Template based, Custom, Back end integration and connectivity, Complexity – Current issues ● After an upgrade, it is extremely important to know if the upgrade broke the application or if it was already broken

64. 64 Applications – Planning ■ Determine what to do with the applications  Do we upgrade the design ?  Do we fix issues before or after the upgrade ? ■ Plan your upgrade in “small” steps １． Prioritize those that must be fixed before upgrade and plan the effort and resource to perform that remediation, including those with existing issues if necessary ２． Correct minor issues with the applications – Concentrate your efforts on issues that are simple and easy to fix – Don't try to introduce new features at this point ３． Upgrade applications based on standard templates – Notify users first and make sure that they have the necessary training ４． Change the design of applications to incorporate new Notes/Domino 8 features if appropriate

65. 65 Applications - Testing ■ It's not about how hard you test but more about how intelligently you test ■ Based on your application inventory, group applications...  Based on a standard design templates  Complexity – External tools/products – Backend integration – 3 rd party software – Applications using undocumented functions and features  Importance – Is this a mission critical application ? – Audience ● Are executives using the application ? ● Is this a company wide application ?

66. 66 Applications – Testing ■ Do I test every application ?  No, not unless you have very few or truly enjoy boring and tedious work ■ Test a sample of applications  Mission critical applications based on different designs  Applications used by executives  Complex or custom applications – Backend integration – Reliance on 3 rd party software – Applications using undocumented functions and features – Extensions or addin tasks using nsf_hooks, ext_mgr and home grown APIs – Use recompile all (LotusScript) to check for LS issues  Sample of applications using a common or standard template ■ Leverage tools to assist with your testing  Get the Domino 8 specific upgrade rule sets for the tools you're using  Good at pointing out the most prevalent areas that could result in problems  Use the results in prioritisation of effort ■ Don't forget to document your findings and notify application owners

67. 67 Applications – Remediation ■ Use the priorities and testing results to guide the remediation efforts  Cover the most important items that must be fixed prior to upgrade  Create a small break-fix team for unforeseen problems after the upgrade for the lower priority applications ■ Put applications into the test environment for acceptance testing ■ On successful testing, archive copies of new templates

68. 68 Application – Execute the Upgrade ■ Depending on the server upgrade strategy…  …all critical applications need to be fixed for in place server upgrades  …critical applications need to be moved to new servers ■ After upgrading the server or once applications are deployed to new servers....  …make sure that you document and resolve any new issues  …start to look at new application features and how they can benefit your company

69. 69 Coexistence – New Features ■ Where new features are optional, they are typically one of the last activities in the upgrade project ■ Mixed release clusters…  …cluster replication will fall back to non-streaming with pre-8.0 servers  …out of office must run as an agent ■ Message recall only works with mail accounts hosted on Domino 8 servers ■ New ODS is optional, but is required to support… ...reduced I/O requirements ...design / document compression  …database names list for optimized user renames ...DAOS (Domino Attachment and Object Service) ...enhanced user activity logging – reads & writes become reads, adds, updates & deletes

70. 70 Upgrade Summary ■ Good planning and research reduces risk and sets proper expectations ■ Testing helps you avoid pitfalls and plan for the unexpected ■ Pilot is your PR campaign – you want it to be positive ■ Successful deployment is directly linked to the quality of your plans and procedures

71. 71 Reference Materials Notes and Domino Product Page http://www-306.ibm.com/software/lotus/notesanddomino/ What’s New in Notes/Domino 8.5 http://infocenters.lotus.com/help7/topic/com.ibm.notes85.help.doc/doc/fram_what_new_85_r.html developerWorks Lotus Notes/Domino Page http://www.ibm.com/developerworks/lotus/products/notesdomino/ Lotus Notes and Domino 8 Reviewer’s Guide http://www.redbooks.ibm.com/abstracts/REDP4359.html?Open IBM Lotus Notes and Domino 8 Deployment Guide (Redbook SG24-7506) http://www.redbooks.ibm.com/redpieces/abstracts/sg247506.html?Open Notes / Domino 8 Education Offerings http://www.ibm.com/developerworks/lotus/notes/education.html?S_TACT=105AGX13&S_CMP=LP Notes / Domino 8 Support Resource Page http://www-01.ibm.com/software/lotus/support/nd8/

72. 72 Reference Materials (continued) Notes / Domino 7 Upgrade Best Practices Redpaper (REDP-4120-00) http://www.redbooks.ibm.com/abstracts/redp4120.html Webcast: The top 8 reasons why you’ll love Notes 8 https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?lang=en_US&source=sw-pprod05&S_PKG=SW- 8Reasons2LoveLN Lotus Notes Domino 8: Upgrader's Guide http://www.packtpub.com/lotus-notes-domino-8/book

73. 73 Related Sessions ■ Assessment and Planning  BP112 - Speed Up Your Development and Testing with Virtual Machines  BP206 - Health Check: How's Your IBM Lotus Domino Environment?  ID101 - What's New in the IBM Lotus Notes Client  ID202 - Release the Power! Deploying New Features in IBM Lotus Notes/Domino 8.5  ID211* - Executing a Security Assessment of Your Lotus Domino Architecture ■ Server and Client Deployment  BP402* - Best Practices for IBM Lotus Notes 8.0 and 8.5 Client Upgrades  ID108 - Deploying IBM Lotus Notes 8 on Citrix  ID203 - IBM Lotus Domino 8.5 Server Performance Improvements  ID209 - Getting the Most Out of Your IBM Lotus Domino 8.5 Messaging Servers  ID213 - "Eating Our Own Cooking": Inside IBM's Deployment of Lotus Notes and Lotus Domino 8 ■ Applications  BP408* - Optimizing IBM Lotus Domino Application Infrastructures to Maximize Upgrade Success

74. 74 Find out more about IBM Software Services for Lotus Technical Consulting Helping address business challenges with innovative software and asset solutions. Training and Certification Accelerating successful product adoption and time to value with effective training options. Premium Support Providing personalized and proactive technical guidance that helps avoid costly outages, streamlines processes, and prepares you for ongoing change. Accelerating success with Lotus and WebSphere Portal technology ibm.com/software/lotus/services Meet ISSL at Lotusphere ✔ ISSL Lab: Dolphin – Europe 6 ✔ Product Showcase: Dolphin ✔ Lotus Training & Certification ✔ IBM Software Support Resources and Services ✔ Certification Prep and Testing: Swan – Peacock 1 & 2 | Lark 1 & 2 ✔ Lounges ✔ Premium Support Customer Lounge: Dolphin – Europe 11 ✔ IBM Certified Professional Lounge: Swan – Suite 706

75. Questions and Answers Come talk with us and other ISSL colleagues about Lotus technologies, integration and deployment in the “Meet the Lab Services Team” lab (Dolphin - Europe 6) Please remember to complete the session survey !

76. 76 Legal Disclaimer © IBM Corporation 2008. 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. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Expeditor, Sametime and Tivoli are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries 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. VMWare is a registered trademark of VMWare, Inc. in the United States, other countries, or both. Eclipse is a registered trademark of the Eclipse Foundation in the United States, other countries, or both. SUSE and ZENworks are registered trademarks of Novell, Inc. in the United States, other countries, or both. InstallShield is a registered trademark of Acresso Software, Inc. in the United States, other countries, or both. InstallPump is a registered trademark of SoftQuest Corporation in the United States, other countries, or both. RedHat is a registered trademark of Red Hat, Inc. in the United States, other countries, or both. TeamStudio is a registered trademark of TeamStudio, Inc. in the United States, other countries, or both.