|Table of Contents
Topics on this page include:
Overview of Upgrading Applications
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 application environment
- Identify 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
Determine what to do with the applications
- Do you upgrade the design?
- Do you 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.x features, if appropriate
Based on your application inventory, group applications...
- Based on standard design templates
- - External tools and products
- - Back-end integration
- - 3rd party software
- - Applications using undocumented functions and features
- Importance & Audience
- - Is this a mission critical application?
- - Are executives using the application?
- - Is this a company-wide application?
Test a sample of applications..
- Mission critical applications based on different designs
- Applications used by executives
- Complex or custom applications
- back-end integration
- reliance on 3rd party software
- applications using undocumented functions and features
- extensions or add-in tasks using nsf_hooks, ext_mgr, and home-grown APIs
- use recompile all (LotusScript) to check for LotusScript issues
- Sample of applications using a common or standard template
Leverage tools to assist with your testing
Don't forget to document your findings and notify application owners
Use the priorities and testing results to guide 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 lower priority applications
Put applications into the test environment for acceptance testing
On successful testing, archive copies of new templates
Execute the Upgrade
Depending on the server upgrade strategy...
- all critical applications must be fixed for in-place server upgrades
- critical applications must be moved to new servers
After upgrading the server or once applications are deployed to new servers:
Back to top
- make sure that you document and resolve any new issues
- start to look at new application features and how they can benefit your company
New in Domino Designer 8.5.1
Domino Designer 8.5.1 is avaiable for download at no charge. Click here
New to Domino Designer 8.5.1
- XPages are supported in the Notes client.
- XPage performance and scalability enhancements.
- XPage active content filtering.
- Dojo updated to 1.3.2.
- Improved ability to use Dojo in XPages.
- Designer performance enhancements.
- New LotusScript and Java editors.
- Working sets usability enhancements.
- Domino Designer extensibility APIs.
- New design element for building iWidgets.
- Composite application enhancements for Notes and Symphony applications.
- Composite application support for XPages.
- Provide Java APIs for Notes User Interface classes.
-- All about XPages
Admin Guide Lotus Domino Designer Basic User Guide & Reference
Technote Knowledge Collection: XPages (#7014929)
Technote Frequently asked questions (FAQ) about XPages (#1389133)
Back to top
To provide feedback on this content, please send an email to firstname.lastname@example.org
|Table of Contents