2 options
IBM Lotus Domino 6.5 for Linux on zSeries implementation / [Mike Ebbers ... et al.].
- Format:
- Book
- Series:
- IBM redbooks.
- IBM redbooks
- Language:
- English
- Subjects (All):
- Business enterprises--Computer networks.
- Business enterprises.
- Groupware (Computer software).
- Database management--Computer programs.
- Database management.
- Lotus Domino.
- Linux.
- Physical Description:
- xvi, 408 p. : ill.
- Edition:
- 2nd ed.
- Place of Publication:
- Poughkeepsie, NY : IBM, International Technical Support Organization, c2004.
- Language Note:
- English
- Contents:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Chapter 1. Introduction
- 1.1 Contents and audience
- 1.1.1 Scope and assumptions
- 1.2 Reasons to run Domino for Linux on zSeries
- 1.2.1 Domino on Linux
- 1.2.2 Value of the zSeries platform
- 1.2.3 Value of z/VM
- 1.2.4 Comparison of Domino on zSeries-Linux and z/OS
- 1.3 Domino's platform independence
- 1.3.1 Domino source code
- 1.3.2 Domino API application porting
- 1.4 Structure of Domino on Linux on zSeries
- 1.4.1 Domino
- 1.4.2 Linux
- 1.4.3 zSeries hardware
- 1.4.4 zSeries logical partitioning (LPAR)
- 1.4.5 z/VM
- 1.5 What's new in Domino 6.5
- Chapter 2. Planning
- 2.1 Building a team
- 2.2 Deciding where to run Linux on zSeries
- 2.2.1 Logical partition
- 2.2.2 VM guest
- 2.3 The effect on Domino
- 2.3.1 LPAR
- 2.3.2 VM
- 2.3.3 Conclusion
- 2.4 A few large servers - or many small servers
- 2.5 Required hardware and software
- 2.5.1 Hardware
- 2.5.2 Software
- 2.6 Linux planning and customizing
- 2.6.1 Linux kernel changes
- 2.6.2 Linux sysstat package
- 2.6.3 Linux user IDs
- 2.6.4 Linux network
- 2.7 VM planning considerations
- 2.7.1 VM user IDs
- 2.7.2 Minidisks
- 2.7.3 Page and spool space
- 2.7.4 Memory
- 2.7.5 CPUs
- 2.8 Domino planning
- 2.8.1 zSeries - just another server platform
- 2.8.2 Server consolidation
- 2.8.3 Partitioned servers
- 2.9 Where to find more information
- Chapter 3. z/VM basics, planning, and tasks
- 3.1 z/VM basics
- 3.2 z/VM planning
- 3.2.1 Base installation
- 3.2.2 Memory or storage
- 3.2.3 Processors or CPUs
- 3.2.4 Page and spool space
- 3.2.5 Disk space for z/VM and Linux
- 3.2.6 Defining user IDs for Linux images
- 3.3 z/VM tasks
- 3.3.1 Get help
- 3.3.2 Determine who is on the system.
- 3.3.3 Determine how busy the system is
- 3.3.4 Determine what DASD and minidisks you have
- 3.3.5 Format and add DASD to the system
- 3.3.6 Add page, spool and temporary disk space
- 3.3.7 Add Linux user IDs
- 3.3.8 Update the SYSTEM CONFIG file
- 3.3.9 Modify the logon screen
- Chapter 4. Disk configuration
- 4.1 Introduction
- 4.2 Mount points
- 4.2.1 Shared filesystems
- 4.2.2 Minidisks
- 4.2.3 Virtual disks
- 4.3 Brief introduction to Linux and UNIX filesystem
- 4.3.1 Linux is case-sensitive
- 4.3.2 Backslash versus forward slash
- 4.3.3 The directory tree
- 4.3.4 Pathname
- 4.3.5 Symbolic links
- 4.3.6 File permissions
- 4.3.7 Filesystem types: Journaled or non-journaled
- 4.4 Logical Volume Manager (LVM)
- 4.4.1 LVM for Linux
- 4.4.2 How to use LVM
- 4.4.3 Our example
- 4.5 Domino filesystem structure
- 4.5.1 Mount points and Domino
- 4.6 Placement of high-use Domino files
- 4.6.1 Transaction log
- 4.6.2 Names.nsf
- 4.6.3 mail.boxes
- 4.6.4 Log files for the Java Console (dcntrlr*)
- 4.6.5 Indexing and other temporary files
- 4.6.6 Use of database and directory links
- 4.7 Placement of other Domino databases
- 4.7.1 Mail files
- 4.7.2 Application databases
- 4.7.3 Estimating DASD space
- 4.7.4 Naming convention
- 4.7.5 Example of our filesystem
- Chapter 5. Networking
- 5.1 Two common networking methods
- 5.2 z/VM networking
- 5.2.1 Give OSA addresses to Linux user IDs
- 5.2.2 Add a guest LAN to the system
- 5.2.3 Add network interface cards (NICs) to Linux user IDs
- 5.2.4 Customize TCP/IP
- 5.2.5 Start or stop TCPIP
- 5.2.6 Dynamically changing TCP/IP
- 5.3 Linux networking
- 5.3.1 Connecting Linux to a z/VM guest LAN
- 5.4 Domino networking
- 5.4.1 Notes remote procedure call (NRPC) communication
- 5.4.2 Notes network ports
- 5.4.3 Notes named networks (NNN).
- 5.4.4 Resolving server names to network addresses in NRPC
- 5.4.5 TCP/IP: Domino on Linux
- 5.4.6 Recommendations for Domino partitioned servers (DPARs)
- 5.4.7 Network Address Translation (NAT)
- 5.5 Troubleshooting your network
- Chapter 6. Linux installation
- 6.1 Introduction
- 6.1.1 Bill of materials
- 6.1.2 High level steps
- 6.2 Prepare for Linux installation
- 6.2.1 Obtain a Linux distribution
- 6.2.2 Obtain the necessary networking resources and information
- 6.2.3 Mount the Linux CDs and set up an NFS or FTP server
- 6.3 z/VM first steps
- 6.4 Prepare and IPL Linux in an LPAR
- 6.4.1 Assumptions
- 6.4.2 Skills needed
- 6.4.3 FTP installation files to z/OS
- 6.4.4 Tape preparation
- 6.4.5 DASD preparation
- 6.4.6 Booting Linux from the HMC
- 6.5 Linux installation and customization
- 6.5.1 Answer the networking questions
- 6.5.2 Begin the graphical installation process
- 6.5.3 Format the DASD from an ssh or telnet session
- 6.5.4 Complete the graphical installation process
- 6.5.5 Reboot Linux system from disk and finish basic install
- 6.5.6 Apply the SLES-8 service pack 2 CD
- 6.5.7 Install the sys_epoll RPM
- 6.5.8 Re-IPL with the new kernel
- 6.5.9 Set up logical volumes
- 6.6 Set up swap space
- 6.6.1 Set up swap space on an LPAR
- 6.6.2 Set up virtual disk swap space under z/VM
- 6.6.3 Turning off unneeded services
- 6.6.4 Back up your system (optional)
- Chapter 7. Domino installation
- 7.1 Receiving the Domino CD
- 7.2 Checklist
- 7.3 Pre-installation steps
- 7.4 Installing the executable server code
- 7.4.1 Placing the tar file on your Linux filesystem
- 7.4.2 Extracting the files
- 7.4.3 Running the installation script
- 7.5 Setting up the Domino server
- 7.6 Starting the Domino server
- 7.7 Installing the server executables using Script mode.
- 7.8 Adding a partitioned Domino server (DPAR)
- 7.9 Installing multiple Domino versions
- 7.10 Avoiding installation problems
- Chapter 8. Domino administration
- 8.1 Ways to administer the Domino Server
- 8.1.1 Domino Controller and Domino Console
- 8.1.2 Domino Administrator
- 8.1.3 Web Administrator
- 8.2 How to start and stop the server
- 8.2.1 Manually starting the Domino Controller and Domino Server
- 8.2.2 Display error when starting Domino Controller
- 8.2.3 Starting and stopping the Domino Console
- 8.2.4 Stopping and starting the server from the Domino Console
- 8.2.5 Logging server output
- 8.2.6 Other uses of Domino Console
- 8.2.7 Levels of access
- 8.3 Monitoring the Domino system
- 8.3.1 System monitoring tools
- 8.3.2 Server availability
- 8.3.3 Performance monitoring
- 8.4 Transaction logging
- 8.4.1 Setting up transaction logging
- 8.4.2 View logging
- 8.5 Upgrading an existing Domino server
- 8.6 Problem determination
- 8.6.1 NSD tool
- 8.6.2 Running NSD
- 8.6.3 Fault recovery
- 8.6.4 CORE dump
- 8.6.5 Using Notes log
- 8.6.6 Problem scenario
- 8.7 Domino Web Access (DWA)
- 8.8 Best practices
- 8.9 New 6.5 features
- 8.9.1 Policies
- 8.9.2 Directory synchronization
- Chapter 9. Systems management
- 9.1 Linux administration
- 9.2 Managing the filesystem
- 9.2.1 Formatting a device
- 9.2.2 Creating a filesystem
- 9.2.3 Mounting a filesystem
- 9.2.4 Managing Logical Volume Manager (LVM)
- 9.2.5 Monitoring the filesystem size
- 9.2.6 Managing users
- 9.2.7 Scheduling of jobs with crontab
- 9.2.8 System logs
- 9.2.9 Remote administration
- 9.3 Monitoring
- 9.3.1 Linux tools
- 9.3.2 Performance monitoring with RMF PM for Linux
- 9.4 VM administration
- 9.4.1 VM CP commands
- 9.4.2 VM commands
- 9.5 Automating Domino startup and shutdown
- 9.5.1 Automated startup.
- 9.5.2 Automated startup on IPL of the VM operating system
- 9.5.3 Automated shutdown when running Linux under VM
- 9.5.4 Operating system maintenance with CheckOS
- 9.6 Problem determination
- 9.6.1 Domino server problems
- 9.7 Backup/recovery
- 9.7.1 Understanding your backup and recovery needs
- 9.7.2 Tivoli Storage Manager (TSM)
- 9.7.3 Data Protection for Lotus Domino
- 9.7.4 Transaction logging
- 9.7.5 Data Protection for Lotus Domino setup
- 9.7.6 Data Protection for Lotus Domino operations
- 9.7.7 Anti-virus
- 9.7.8 Anti-spam
- Chapter 10. Troubleshooting
- 10.1 Domino stalled under VM
- 10.2 Idle server still uses 2 to 3 percent of system
- 10.3 Domino Console message: Insufficient TCP sockets
- 10.4 Translog placed in wrong directory
- 10.5 DB2: Starting the database manager
- 10.6 DECS: Starting and testing connectivity
- 10.7 The DECS hang
- 10.8 A Domino panic
- Chapter 11. Capacity planning for Linux on zSeries
- 11.1 Recommendations
- 11.2 Estimating processor capacity
- 11.2.1 How users impact processor capacity
- 11.2.2 Which user counts are important?
- 11.2.3 Client types
- 11.2.4 Domino transaction rates
- 11.2.5 Consider the peak times
- 11.2.6 IBM initial sizing assistance
- 11.3 Capacity and performance testing for this redbook
- 11.3.1 Initial testing
- 11.3.2 LSC testing
- 11.4 Processor planning
- 11.4.1 How many CPs is too many?
- 11.4.2 z/VM processor costs
- 11.4.3 Optimum DPAR configuration
- 11.5 Storage planning
- 11.6 Network planning
- 11.6.1 Configuration
- 11.6.2 Domino considerations
- 11.7 Disk/DASD planning
- 11.7.1 Amount of disk
- 11.7.2 Placement of Domino databases
- 11.7.3 ESS default cache mode
- 11.8 Other Domino impacts to capacity
- 11.8.1 Clustering
- 11.8.2 Agents
- 11.8.3 Full-text indexing
- 11.8.4 Special functions and third-party products.
- 11.8.5 Notes.ini parameters.
- Notes:
- "Lotus software"--Cover.
- "SG24-7021-01."
- "December 2004."
- OCLC:
- 939263425
The Penn Libraries is committed to describing library materials using current, accurate, and responsible language. If you discover outdated or inaccurate language, please fill out this feedback form to report it and suggest alternative language.