IBM R5 manual Setup a Pilot Project

Page 22

Lotus Domino Server R5 Implementation Guide

June 18, 2001

 

 

connectivity maps, and a list of possible errors that they or end users may encounter during the installation project and how to resolve them.

After an initial course, it is highly recommended that each administrator and support staff member receive full training on Domino R5. They should learn how to use the end user interface, administrator interface, designer interface, know what components are available, how to perform the daily functions all users perform, and how to access different features and functions. The more comfortable your support staff is with Domino, the more comfortable your end users will feel. A knowledgeable staff means a successful and efficient roll out, and less pain for everyone involved.

Education can be conducted using any of the following methods. Each method has its pluses and minuses depending on your particular environment.

ŸFormal Lotus training

ŸCBT self study course work

ŸCustomized training from a Business Partner

4. Setup a Pilot Project

Before installing Domino in your organization, you should test the install procedures in a non-production environment where you can try things, make mistakes, and gain valuable experience. While installing Domino is straightforward, each organization will have a different infrastructure, needs, and deployment plan. By testing, you familiarize yourself and your install team with the procedures and the process of installing.

A pilot project should reproduce, on a smaller scale, the proposed Domino system for your organization. This will give your organization an opportunity to test the Domino installation in an environment similar in nature to the production environment.

Create a list of Domino and Notes features that may be considered mission-critical for your organization. Make sure to test these features thoroughly. For example, your company may want to place all mail files on clustered mail servers to ensure high reliability, failover, and load balancing. List the different types of servers you plan to use -- some companies use Domino only for mail, others use it for messaging, application, Web site hosting, and directory services, among other roles. Test each of these items -- whether a vital application, server configuration, or role under Domino. This lets you accumulate knowledge and create best practices for the deployment of your organization.

Share the knowledge once you have compiled best practices, and communicate them to your install team and to all parts of your organization involved in the installation of Domino. This lets others benefit from your experiences, minimizing effort, mistakes, and duplication, and allowing you to maximize productivity.

As part of this pilot, consider an initial deployment. In larger companies and especially in enterprise organizations, consider a limited-scale deployment to one group or business unit that serves as a model for the rest of the organization. Use this deployment of Domino, along with your pilot project, to test your assumptions, plans and expectations regarding the installation, interoperability, and training on the new software. Choose a group for the deployment that is comfortable with change and learning. Make sure the group is invested in the project by discussing its benefits for them and encouraging them to share their concerns. Support their transition to Domino and capture their experiences and feedback for use in planning your organizational roll out.

Encourage users to share their experiences and feedback about Domino and about the roll out procedure so that you can adapt your plan to avoid problems and leverage strengths.

Think of this initial deployment as a beta release of your install plan. It allows you to test your plan under actual business conditions and to work out any issues before moving to a company wide roll out.

This type of initial, small-scale deployment may not be necessary for smaller companies, who have fewer issues regarding scalability, and for companies who need to install Domino quickly. Even without such a deployment, capture feedback and experiences to evaluate and modify your install strategy as you move through it.

Page 22

Page 21 Page 23
Image 22
Page 21 Page 23
Contents Revised June 18 Disclaimer PSeries Lotus Domino Server e-business Solution Overview Lotus Domino Server R5 Implementation Guide Supported Software Releases Domino Release AIX ReleasePTF Matrix Component Recommended LevelNetwork Protocols and Topology Performance GuidelinesWhat Affects Application Responsiveness? Network TopologySteps to Maximum Domino Performance Know the ConfigurationOther Workload Factors Log Performance Metrics Consistently Distribute I/O Across Physical DisksOptimize for Domino R5 Make Use of NotesBench Data Know the Symptoms of Server Over-UtilizationLearn from Semaphores Consider Partitioning Know When to Consolidate and When to DistributeConsider Clustering Lotus NotesBench28,032 38,235 $23.91 $17.53 Sizing Guidelines Domino R5 on AIX Client Type R5 Scalability IncreaseDomino R5 on AIX Specifics RS/6000 Domino Server Sizing Tool Medium Configuration Sample ConfigurationsSmall Configuration Large ConfigurationEducation Pre-installation SupportPre-sales Technical Support Course Name Course Cost Course Duration Course NumberLotus Domino Server R5 Implementation Guide Select an Install Team Implementation Process OverviewServers Train Domino and Network AdministratorsNetwork WorkstationsSetup a Pilot Project Create an Install Plan for the Network Infrastructure Create or Modify an Existing Disaster Recovery Plan Hardware Operating SystemServer Workstation Schedule and Perform the Installation of the Domino Servers Lotus Domino Server R5 Implementation Guide Document Experiences, Problems, and Solutions Monitor Servers and Assist Users as NeededLotus Domino Server R5 Implementation Guide Checklist for Implementation Completed?Check your Default Path Environment Variable Installation StepsLogin to AIX as the Root User Preparing the AIX EnvironmentCreate AIX Groups Create a Volume GroupCreate AIX Users Create a Logical Volume for the Domino Binaries Create a Logical Volume for the Domino Data DirectoryCreate a File System for the Domino Data Directory Mount the File Systems Check AIX Kernel ConfigurationCreate a File System for the Domino Binaries Change Ownership of the New File SystemsMounting the Cdrom Installing the Lotus Domino ServerRun the Install Program From the CD Welcome ScreenConfiguration Review Select the Type of Domino Server to InstallSetup for Partitioned Domino Servers File Installation CompleteNetwork and Communication Settings Start the Http Server Task For Server ConfigurationAdministration Settings Server Setup is CompletePost-installation Support Domino Product SupportAIX Support Hardware SupportServices Available Service Description ContactURLs Additional Technical ResourcesRedbooks Publications Appendix A. Sample Configurator Configurations Small ConfigurationCD-ROM Medium Configuration Lotus Domino Server R5 Implementation GuideJune 18 CD-ROM Large Configuration Lotus Domino Server R5 Implementation GuideJune 18 CD-ROM Appendix B. IBM Production Configuration Lotus Domino Server R5 Implementation Guide

R5 specifications

IBM R5, also known as IBM Notes R5, marked a significant evolution in the IBM Notes and Domino platform, offering users enhanced capabilities and features that improved productivity and collaboration in the workplace. Released in 1999, R5 introduced a more refined user interface, improved performance, and a range of new tools designed to facilitate communication and teamwork.

One of the standout features of IBM R5 was its comprehensive integration of email, calendaring, and tasks within a single interface. This centralized approach allowed users to manage their communications more efficiently, reducing the need to switch between multiple applications. The improved email functionality included enhanced filtering and sorting capabilities, enabling users to better organize their inboxes.

The R5 version also introduced significant advancements in the collaborative aspects of the platform. With new tools for team collaboration, such as enhanced discussion databases and a shared documents feature, R5 made it easier for teams to work together on projects irrespective of their physical locations. The introduction of instant messaging capabilities further bridged communication gaps, allowing users to connect in real time.

IBM R5 was built on a robust architecture that incorporated Domino server enhancements, which improved scalability and performance. The platform supported new technologies, including Java applets, allowing developers to build more dynamic and interactive applications. Additionally, the integration of the LDAP (Lightweight Directory Access Protocol) provided better directory services, making it simpler to manage user identities across the network.

Security features were also a focus in R5, with improvements in encryption and user authentication that helped safeguard sensitive data. The platform’s ability to integrate with other enterprise applications while maintaining robust security protocols made it a choice for organizations that prioritized data protection.

Moreover, IBM R5 incorporated a more modular and flexible architecture, enabling easier customization and management of applications and components. This adaptability catered to a wide range of business needs, thus positioning IBM Notes R5 as a versatile solution for organizations looking to enhance their workflow and communication processes.

Overall, IBM R5 served as a milestone in the evolution of enterprise collaboration solutions. Its innovative features, user-friendly interface, and robust security measures laid the foundation for future developments in the IBM Notes and Domino ecosystem, ultimately contributing to more efficient and effective business practices.
Top Page Image Contents