Compaq_Office_Server/NEDERLANDS___________________ Installation Guide Revision/Update Information: Updated for Compaq Office Server Version 6.0 Operating system: OpenVMS VAX Version 7.1 or higher, and OpenVMS Alpha Version 7.1-2 or higher Compaq Computer Corporation Houston, Texas __________________________________________________________ April 2001 Possession, use, or copying of the software described in this documentation is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. While Compaq believes the information included in this publication is correct as of the date of publication, it is subject to change without notice. Compaq Computer Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. © 2001, Compaq Computer Corporation COMPAQ, the Compaq logo, the Digital logo, ALL-IN-1, DEC, DECnet, MAILbus and VAX are registered in U.S. Patent and Trademark Office Datatrieve, DECwindows, MailWorks, OpenVMS, Tru64, VMScluster, VT and WPS-PLUS are trademarks of Compaq Computer Corporation. Other product names mentioned herein may be the trademarks of their respective companies. This document was prepared using VAX DOCUMENT, Version 2.1. ________________________________________________________________ Contents Preface.................................................. ix 1 Preparing Your System for Installation 1.1 Checklist of Preinstallation Tasks........... 1-2 1.2 Reading and Printing the Online Release Notes........................................ 1-7 1.3 Checking Prerequisite and Optional Software..................................... 1-8 1.4 Licensing.................................... 1-14 1.4.1 Registering License PAKs for Software Provided with Office Server Version 6.0...................................... 1-15 1.5 Example Order for Installing Optional Software..................................... 1-16 1.6 Installation Procedure Requirements.......... 1-17 1.6.1 Installing Account Requirements.......... 1-17 1.6.2 System Parameters........................ 1-18 1.6.3 Displaying Current System Parameters..... 1-23 1.6.4 Changing System Parameter Values......... 1-23 1.6.4.1 Updating Dynamic System Parameters with AUTOGEN................................ 1-25 1.6.4.2 Updating Non-Dynamic System Parameter with AUTOGEN........................... 1-25 1.6.5 Disk Space on Your System Disk or Alternate Working Device................. 1-26 1.6.6 Using the OA$LIB_SHARE Disk as the AWD... 1-27 1.6.7 Disk Space for Office Server Areas on Target Disks............................. 1-27 1.6.8 Assigning Logical Names to Your Disks.... 1-28 1.6.9 New Installation: Disk Space for Office Server Areas............................. 1-29 iii 1.6.10 Upgrade Installation: Disk Space for Office Server Areas...................... 1-30 1.6.11 Addition of Architecture Support: Disk Space for Office Server areas............ 1-31 1.6.12 Disk Quota Allocation.................... 1-32 1.6.13 Installed Images......................... 1-32 1.6.14 Installing FDVMSG.EXE and FDVSHR.EXE Images................................... 1-37 1.6.15 Installing Other Images.................. 1-37 1.6.16 Checking The Location of DCLTABLES.EXE... 1-37 1.7 Additional Tasks for Upgrade Installations... 1-38 1.7.1 Copying Customized Data Files............ 1-39 1.8 Using the MAILbus 400 MTA and Compaq X.500... 1-39 1.9 Using a Remote Message Router................ 1-39 1.9.1 Create an Office Server Mailbox on the Remote Message Router Node .............. 1-40 1.10 Running the Preinstallation System Check..... 1-41 1.10.1 Types of Errors Reported................. 1-41 1.10.2 Running the Perform all Preinstallation Checks (PC) Option....................... 1-42 1.11 Final System Preparation Tasks: New Installations................................ 1-43 1.12 Final System Preparation Tasks: Upgrade Installations ............................... 1-43 1.12.1 Shut Down Office Server.................. 1-44 1.12.2 Deinstall Files Installed in Memory...... 1-44 1.13 Back Up Your System and Target Disks......... 1-44 2 Installation Procedure: New, Upgrade and Architecture Support 2.1 Installation Procedure for New and Upgrade Installations................................ 2-3 2.2 Adding or Upgrading Architecture Support..... 2-31 2.2.1 Before You Start......................... 2-32 2.2.2 Installation Procedure for Adding Architecture Support..................... 2-32 2.3 Automatic Postinstallation Tasks............. 2-41 2.4 Manual Postinstallation Tasks................ 2-42 iv 3 Installation Procedure: Additional Languages 3.1 Installation Procedure for Additional Language Installations....................... 3-2 3.2 Installing Architecture Support for an Additional Language.......................... 3-9 4 Installation Errors and Failure 4.1 Common Errors................................ 4-1 4.2 Failure During Postinstallation.............. 4-2 4.2.1 Failure of Upgrade Installations in Safety Mode.............................. 4-2 4.2.2 Failure of Upgrade Installations in Non-Safety Mode.......................... 4-2 4.2.3 Full Installations....................... 4-2 4.2.4 Failure Due to Insufficient Dynamic Memory................................... 4-3 4.3 Error Messages when Running the IVP.......... 4-3 4.4 IVP Failure.................................. 4-5 5 Postinstallation Tasks 5.1 Checklist of Manual Postinstallation Tasks... 5-1 5.2 Start Office Server on all Nodes in a VMScluster System............................ 5-5 5.3 Create or Modify the Site-specific Office Server Startup Procedure..................... 5-6 5.4 Edit the Site-specific Startup Procedure..... 5-6 5.4.1 Installations With Compaq X.500 and the MAILbus 400 MTA.......................... 5-7 5.4.2 Installations with Message Router........ 5-7 5.5 Replace the DCLTABLES on Cluster Systems..... 5-9 5.6 Delete Files That Are No Longer Required..... 5-9 5.7 Install Missing Images....................... 5-10 5.8 Recompile Form Libraries..................... 5-10 5.9 Migrating Your Customizations After Upgrading.................................... 5-11 5.9.1 Running the CART Resolution Procedure.... 5-12 5.9.2 Deleting Obsolete Files.................. 5-13 5.9.3 Replacing the Help Modules for Your Application.............................. 5-14 v 5.10 Migrate SITELINK50 Using Customization Management................................... 5-15 5.11 Link Office Server to Include Code-level Customizations............................... 5-15 5.12 Setting up Remote Mail When Using the MAILbus 400 MTA...................................... 5-15 5.13 Setting up Remote Mail When Using Message Router....................................... 5-16 5.13.1 Create a Mailbox for Office Server....... 5-17 5.13.2 Modifying the Message Router Mailbox Entry.................................... 5-19 5.13.3 Configuring the VMSmail Gateway for Remote Access............................ 5-19 5.13.4 Setting Up the Message Router Directory Service as the Mail Directory............ 5-20 5.13.4.1 Message Router is in the Same VMScluster............................. 5-20 5.13.4.2 Message Router is not in the Same VMScluster............................. 5-24 5.13.5 Remote Message Router Directory Service Startup Procedure........................ 5-29 5.14 WPS-PLUS Login Command Procedure............. 5-30 5.15 Moving the CDA DOC_STYLE Files............... 5-30 A Office Server Version 6.0 Distribution Media A.1 CD-ROM Distribution Kits (VAX or Alpha Installations)............................... A-1 B Office Server Version 6.0 Files and Directories B.1 Files in the Office Server Kit............... B-1 B.2 Files Installed in Non-Office Server Directories.................................. B-1 vi C ENGLISH Kit C.1 About Your ENGLISH Kit....................... C-2 C.1.1 Distribution Media....................... C-2 C.1.2 Savesets Provided........................ C-2 C.2 Disk Space Requirements...................... C-3 C.2.1 Disk Space Required on the System Disk or Alternate Working Device (AWD)........... C-4 C.2.2 Disk Space for Language Files on Target Disks.................................... C-4 C.3 Information on the English Language Component.................................... C-7 C.4 Information on the British Language Component.................................... C-7 C.5 Information on the US Market Component....... C-8 C.5.1 Keyboards Supported by the US Market Component................................ C-8 C.5.2 Modems Supported by the US Market Component................................ C-9 C.6 Information on the GB Market Component....... C-9 C.6.1 Keyboards Supported by the GB Market Component................................ C-10 C.6.2 Modems Supported by the GB Market Component................................ C-11 D Information on Market Components D.1 Belgian Market Component..................... D-2 D.2 Brazilian Market Component................... D-2 D.3 Canadian Market Component.................... D-3 D.4 Dutch Market Component....................... D-4 D.5 French Market Component...................... D-4 D.6 German Market Component...................... D-5 D.7 Swiss Market Component....................... D-6 Index vii Tables 1-1 Preinstallation Checklist................ 1-2 1-2 Prerequisite and Optional Software....... 1-9 1-3 Licenses for Migrating from MailWorks.... 1-14 1-4 Process Account Quotas for the Installing Account.................................. 1-18 1-5 Minimum System Parameter Values Required................................. 1-19 1-6 Changing System Parameter Values......... 1-24 1-7 New Installation: Disk Space for Office Server Areas............................. 1-30 1-8 Upgrade Installations: Disk Space for Office Server Areas ..................... 1-31 1-9 Addition, Upgrade or Update of Architecture Support: Disk Space for Office Server Areas...................... 1-32 1-10 Installed Images Required on VAX......... 1-32 1-11 Installed Images Required on Alpha....... 1-34 2-1 Information About the Installation Procedure................................ 2-2 2-2 Installation Procedure for New and Upgrade Installations.................... 2-4 2-3 When to Install/Upgrade VAX or Alpha Architecture Support..................... 2-31 2-4 Installation Procedure for Adding Architecture Support..................... 2-33 3-1 Installation Procedure for An Additional Language ................................ 3-3 3-2 Installation Procedure for Addition of Architecture Support for an Additional Language................................. 3-9 5-1 Postinstallation Tasks................... 5-1 5-2 Editing the OpenVMS Site-specific Startup File..................................... 5-8 5-3 Tasks for Setting up Remote Mail......... 5-16 C-1 Savesets Provided with the ENGLISH Kit... C-2 C-2 Disk Space Required on the System Disk or AWD (Blocks).......................... C-4 viii C-3 Disk Space for Language Files: New Installation............................. C-5 C-4 Disk Space for Language Files: Upgrade from Version 3.1......................... C-6 C-5 Disk Space for Language Files: Add, Upgrade or Update Architecture Support... C-6 C-6 Useful Information for the English Language Component....................... C-7 C-7 Useful Information for the British Language Component....................... C-7 C-8 Useful Information for the US Market Component................................ C-8 C-9 Useful Information for the GB Market Component................................ C-9 D-1 Useful Information for the Belgian Market Component................................ D-2 D-2 Useful Information for the Brazilian Market Component......................... D-2 D-3 Useful Information for the Canadian Market Component......................... D-3 D-4 Useful Information for the Dutch Market Component................................ D-4 D-5 Useful Information for the French Market Component................................ D-5 D-6 Useful Information for the German Market Component................................ D-5 D-7 Useful Information for the Swiss Market Component................................ D-6 ix ________________________________________________________________ Preface About This Book Before you use this book, you must plan your Office Server Version 6.0 installation by reading the Compaq Office Server Planning and Setup Guide. Note that the Compaq Office Server Planning and Setup Guide was not updated for Office Server Version 6.0, but that the instructions it gives still apply. The Compaq Office Server Installation Guide describes how to do the following: 1. Prepare your system for an Office Server Version 6.0 installation. 2. Install Office Server Version 6.0. 3. Set up Office Server Version 6.0 so that the Office Server manager can log in and use it locally. Office Server Installation: Language and Market Information The documentation provided with non-ENGLISH kits provides the disk space values for installing the Office Server Version 6.0 kit, and information on the language and market components that you will need during the installation. Prerequisite Knowledge This guide assumes that you have read the Compaq Office Server Planning and Setup Guide. To install Office Server Version 6.0 you must be familiar with the VMSINSTAL utility. ix The Office Server Management Documentation Set The following guides form the Office Server management documentation set: o Compaq Office Server Planning and Setup Guide o Compaq Office Server Installation Guide o The online help for Office Server Administrator ________________________Note ________________________ The V4.0 management guide may still be useful, but the most up-to-date management information is in the Office Server Administrator help. _____________________________________________________ Terminology and Conventions Used in this Guide The following table lists the terminology and conventions used in this guide. Office Server Means the Compaq Office Server for OpenVMS Alpha and OpenVMS VAX OpenVMS Alpha Means the OpenVMS Alpha operating system OpenVMS VAX Means the OpenVMS VAX operating system UCX Means DEC TCP/IP Services for OpenVMS AIDA Server Means the Distributed Access Server Client user Means a user of a client of Office Server. Client users include: o Users of personal computers (PCs) and workstations (PC client users) o Users of the video terminal (VT) interface to Office Server software, when they choose options that make use of an Office Server server (VT client users) x Architecture Is a term used to differentiate between OpenVMS VAX systems and OpenVMS Alpha systems Related Documents You may also need to refer to the documentation on the following products: o VAX Message Router and its Gateways o DEC Notes o OpenVMS system management o The MAILbus 400 MTA and its Gateways o Compaq X.500 o DECnet/OSI xi 1 ________________________________________________________________ Preparing Your System for Installation This chapter describes the tasks that you must do to prepare your system for an Office Server installation. The information in this chapter applies to all installations. You must read the Compaq Office Server Planning and Setup Guide before you install Office Server. The guide covers: o Information about this version of Office Server o Mail system planning o Installation planning, including a checklist of all the decisions that you need to make before starting the installation In addition, if your system has been customized, you must read the chapter Planning the Upgrade of a Customized System in the Overview and Planning Guide. This chapter explains how to run the Conflict Checking and Resolution Tool (CART) to check your customizations before you upgrade to Office Server. o Mail system planning o System policies and licensing This installation guide assumes that you have read the Compaq Office Server Planning and Setup Guide, made all your planning decisions and know what type of installation you are going to perform. Preparing Your System for Installation 1-1 Preparing Your System for Installation 1.1 Checklist of Preinstallation Tasks 1.1 Checklist of Preinstallation Tasks To prepare your system for an Office Server installation, you must do the tasks listed in Table 1-1. Table_1-1_Preinstallation_Checklist_______________________ For further information, Task___Description________________see_____________________ 1 Check the kit contents The Bill of Materials for a list of what the distribution kit should contain. Contact your Compaq representative if your kit is damaged or incomplete. __________________________________________________________ 2 Read the READ ME FIRST letter if one is supplied with your kit __________________________________________________________ 3 Make sure that you have Compaq Office Server planned your installation Planning and Setup Guide and Office Server mail system. The Compaq Office Server Planning and Setup Guide also lists any prerequisite configuration tasks that must be done for the messaging products that you plan to use with Office Server. These tasks must be completed before you start your installation. (continued on next page) 1-2 Preparing Your System for Installation Preparing Your System for Installation 1.1 Checklist of Preinstallation Tasks Table_1-1_(Cont.)_Preinstallation_Checklist_______________ For further information, Task___Description________________see_____________________ __________________________________________________________ 4 Read the online product Section 1.2 for release notes provided instructions on with the kit accessing the release notes. __________________________________________________________ 5 Check that you have the Section 1.3 correct versions of: o The prerequisite software for the installation o Any optional software that you want to install __________________________________________________________ 6 Check that you have a Section 1.4 valid license for the installing account __________________________________________________________ 7 Register the License Section 1.4.1 PAKs for the prerequisite and optional software provided with Office Server. __________________________________________________________ (continued on next page) Preparing Your System for Installation 1-3 Preparing Your System for Installation 1.1 Checklist of Preinstallation Tasks Table_1-1_(Cont.)_Preinstallation_Checklist_______________ For further information, Task___Description________________see_____________________ 8 Check the installation Section 1.6 for the procedure requirements: values required and o For the installing instructions for account checking and changing these parameters. o System parameters o Disk space o Logical names o Installed images o The location of DCLTABLES.EXE __________________________________________________________ 9 For upgrade installa- Section 1.7. tions, do any additional tasks. __________________________________________________________ (continued on next page) 1-4 Preparing Your System for Installation Preparing Your System for Installation 1.1 Checklist of Preinstallation Tasks Table_1-1_(Cont.)_Preinstallation_Checklist_______________ For further information, Task___Description________________see_____________________ 10 Check that all pre- Section 1.3 lists requisite and optional prerequisite and software is installed, optional software. In configured and running addition, you may want before you start to install DATATRIEVE or the Office Server ACMS if you are planning installation. to use these products with Office Server. All prerequisite messaging products such as Message Router or the MAILbus 400 MTA and Compaq X.500 must be installed, configured and running before you install Office Server. See the Compaq Office Server Planning and Setup Guide. For a suggested order of installing optional software, see Section 1.5. __________________________________________________________ 11 If you are installing a Section 1.8 new Office Server system with Compaq X.500 and the MAILbus 400 MTA, check that these products have been installed and configured correctly. __________________________________________________________ (continued on next page) Preparing Your System for Installation 1-5 Preparing Your System for Installation 1.1 Checklist of Preinstallation Tasks Table_1-1_(Cont.)_Preinstallation_Checklist_______________ For further information, Task___Description________________see_____________________ 12 If you will be using a Section 1.9. remote Message Router that is not in the same VMScluster, do any additional tasks. __________________________________________________________ 13 It is recommended that Section 1.10 you run the Perform all preinstallation checks (PC) option to check that your system is prepared for the installation. The PC option runs through the installation to check that you have all the prerequisite licenses, software, disk space and installation parameters correctly set up on your system. __________________________________________________________ 14 Do the final system Section 1.11 for new preparation tasks. installations and Section 1.12 for upgrade installations. __________________________________________________________ 15 Back up your system and Section 1.13 _______target_disks.______________________________________ 1-6 Preparing Your System for Installation Preparing Your System for Installation 1.2 Reading and Printing the Online Release Notes 1.2 Reading and Printing the Online Release Notes Online release notes are provided with the language and market components of Office Server. The release notes contain information that was unavailable before the books went to print. It is recommended that you read the release notes, because they may contain information relating to the installation. You can access the release notes using the VMSINSTAL procedure before you install the Office Server software. There are two parts to the Office Server release notes: o Release Notes Part 1 Language This part contains the release notes specific to the Office Server language being installed. o Release Notes Part 2 Market This part contains the release notes specific to your Office Server market component. Note that this document may not exist for all market components. To read or print the release notes, do the following: 1. Log in to the privileged OpenVMS system manager's account and enter the following command lines: $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL product device: OPTIONS N where device is the device on which the media containing the appropriate version of the release notes is mounted and product is the product code. The product codes are: o A1Llang060 for the Release Notes Part 1 Language, where lang is the 2-letter code for the language you are installing o A1Cmarket060 for the Release Notes Part 2 Market, where market is the 2-letter code for the market component you are installing If you are performing an additional language instal- lation, you need only print the Office Server Release Notes Part 1 Language that is supplied with your kit. Preparing Your System for Installation 1-7 Preparing Your System for Installation 1.2 Reading and Printing the Online Release Notes When you have read or printed the release notes, terminate the installation procedure. If you have accessed only one part of the release notes, repeat the procedure to access the other part. The following files are placed in SYS$HELP: o A1Llang060.RELEASE_NOTES, for the Release Notes Part 1 Language, where lang is the 2-letter code for the language you are installing o A1Cmarket060.RELEASE_NOTES, for the Release Notes Part 2 Market, where market is the 2-letter code for the market component you are installing 1.3 Checking Prerequisite and Optional Software Table 1-2 provides information about the prerequisite software for an Office Server installation. It also lists the software that is supplied with the Office Server kit, and optional software that you may want to install. The following definitions apply: o Prerequisite means that the software must be installed before you install Office Server. The installation will fail if the prerequisite software is not installed. o Optional means that the software is not required for the Office Server installation. Optional software provides additional functionality and the optional software that you install depends on the requirements at your site. For example, if you want to use Group Conferencing, you must install DEC Notes. ________________________Note ________________________ Both the prerequisite software, and any optional software that you want to install, must be in- stalled, configured and running before you install Office Server. _____________________________________________________ 1-8 Preparing Your System for Installation Preparing Your System for Installation 1.3 Checking Prerequisite and Optional Software Table_1-2_Prerequisite_and_Optional_Software______________ Supplied Software VAX Alpha With Product__________Version__VersionKit?___Notes_____________ OpenVMS VAX 7.1 or - N Prerequisite for higher installation on VAX. Must be a full untailored system OpenVMS Alpha - 7.1-2 N Prerequisite for or installation on higher Alpha. Must be a full untailored system __________________________________________________________ DECnet-VAX 5.5 - N Prerequisite for end-node remote messaging using Message Router DECnet for - 1.5 N Prerequisite for OpenVMS Alpha remote messaging using Message Router (continued on next page) Preparing Your System for Installation 1-9 Preparing Your System for Installation 1.3 Checking Prerequisite and Optional Software Table_1-2_(Cont.)_Prerequisite_and_Optional_Software______ Supplied Software VAX Alpha With Product__________Version__VersionKit?___Notes_____________ DECnet/OSI for 7.1 or 7.1 N Prerequisite[1] OpenVMS higher or for systems using higher Compaq X.500 or Compaq X.500 and the MAILbus 400 MTA. Optional alternative for systems using Message Router. __________________________________________________________ TCP/IP Services 4.2 or 5.0 N Optional. for OpenVMS higher or Install if you or other TCP higher want to use the /IP software TCP/IP network that emulates protocol to this[3] communicate with client applications. __________________________________________________________ [1]DECnet/OSI_is_a_prerequisite_for_Compaq_X.500._If______ you plan to migrate to use Message Router with Compaq X.500, you must install DECnet/OSI as the prerequisite for Compaq X.500. For Compaq X.500, you must also install the OSI Applications Kernel, OSAK, from the DECnet/OSI Applications component. See the Compaq X.500 installation documentation for more information. [3]For supported versions of other TCP/IP software that emulates TCP/IP Services for OpenVMS, see the Office Server Software Product Description. (continued on next page) 1-10 Preparing Your System for Installation Preparing Your System for Installation 1.3 Checking Prerequisite and Optional Software Table_1-2_(Cont.)_Prerequisite_and_Optional_Software______ Supplied Software VAX Alpha With Product__________Version__VersionKit?___Notes_____________ Message Router 3.5 - Y Optional. Install and configure if you want to send remote mail using Message Router. __________________________________________________________ Message Router 3.5 - Y Optional VMSmail Gateway Install if you want to send mail from Office Server systems using Message Router to VMSmail users. __________________________________________________________ MAILbus 400 2.0b 2.0b N Optional MTA[4] Install and configure if you want to use the MAILbus 400 MTA for remote mail. Note that Compaq X.500 is a prerequisite for the MAILbus 400 MTA. __________________________________________________________ [4]Office_Server_can_also_connect_to_a_MAILbus_400_MTA____ installed on a remote Tru64 UNIX node. (continued on next page) Preparing Your System for Installation 1-11 Preparing Your System for Installation 1.3 Checking Prerequisite and Optional Software Table_1-2_(Cont.)_Prerequisite_and_Optional_Software______ Supplied Software VAX Alpha With Product__________Version__VersionKit?___Notes_____________ Compaq X.500[5] 3.1[6] 3.1 N Prerequisite if you plan to use the MAILbus 400 MTA. Optional if you plan to continue using Message Router. __________________________________________________________ [5]DECnet/OSI_is_a_prerequisite_for_Compaq_X.500._If______ you plan to migrate to use Message Router with Compaq X.500, you must install DECnet/OSI as the prerequisite for Compaq X.500. For Compaq X.500, you must also install the OSI Applications Kernel, OSAK, from the DECnet/OSI Applications component. See the Compaq X.500 installation documentation for more information. [6]After V3.0 had been released, Digital X.500 Directory Service became Compaq X.500. A further change will happen during the lifetime of Office Server Version 6.0. The directory service, with added LDAP functions, will be bundled with OpenVMS Alpha V7.3, with the new name 'OpenVMS Enterprise Directory for eBusiness'. This product will be unlicensed and freely available with the operating system. On systems where only VAX machines are available, the (licensed) V3.1 will still be a prerequisite for Office Server. (continued on next page) 1-12 Preparing Your System for Installation Preparing Your System for Installation 1.3 Checking Prerequisite and Optional Software Table_1-2_(Cont.)_Prerequisite_and_Optional_Software______ Supplied Software VAX Alpha With Product__________Version__VersionKit?___Notes_____________ MAILbus 400 1.2 - N Optional Message Router Install if you Gateway want to exchange mail between Message Router systems and MAILbus 400 MTA systems. __________________________________________________________ DEC Notes 2.5 2.5 Y Optional. Install if you want to use Group Conferencing. __________________________________________________________ CDA Converter 2.2 - N Optional Library[7] Install if you require full CDA support on OpenVMS VAX. DECwindows[8] - 1.2 N Optional or Install if you higher require full CDA support on OpenVMS Alpha. [7]The_installation_procedure_checks_for__________________ SYS$SHARE:CDA$ACCESS.EXE, Version 1.7 [8]The installation procedure checks for SYS$SHARE:CDA$ACCESS.EXE, Version 1.8 __________________________________________________________ For information about the order of installing optional software, see Section 1.5. Preparing Your System for Installation 1-13 Preparing Your System for Installation 1.3 Checking Prerequisite and Optional Software For a list of all supported versions of products that can be used with Office Server, see the Office Server Software Product Description. 1.4 Licensing The way that your Office Server system is licensed depends on the whether you are migrating from ALL-IN-1 or MailWorks, or are installing a new system: 1. If you already have an ALL-IN-1 license, all appropri- ate subsets for Office Server are enabled, and current license Product Authorization Keys (PAKs) are honored. If you are migrating from MailWorks, a Client Access License must be acquired for every user of the system as shown in Table 1-3. Table_1-3_Licenses_for_Migrating_from_MailWorks___________ Migrating from________To__________Licensing_Required________________ MailWorks Office 100 Client Access Licenses are on VAX Server on supplied at no cost with each VAX Office Server License. If you are migrating more than 100 users, you must purchase an additional Client Access License for each additional user. MailWorks Office Update Client Access License on VAX Server on must be purchased for every user. Alpha After migration to Office Server, you must purchase an additional Client Access License for every additional user. (continued on next page) 1-14 Preparing Your System for Installation Preparing Your System for Installation 1.4 Licensing Table_1-3_(Cont.)_Licenses_for_Migrating_from_MailWorks___ Migrating from________To__________Licensing_Required________________ MailWorks Office Existing Capacity or User licenses on Alpha Server on can be traded for the appropriate Alpha number of Client Access Licenses, equal to the number of users supported during the migration. After migration to Office Server, you must purchase an additional Client Access License for every ________________________additional_user.__________________ 2. If you are installing a new system, licensing is controlled by Client Access Licenses (CALs). Functionality is restricted to Electronic Messaging, Group Services, Directories, File Cabinet, Word Processing (not including the WPS-PLUS editor), and User Setup. 1.4.1 Registering License PAKs for Software Provided with Office Server Version 6.0 You must register the License PAKS for additional products supplied with the Office Server Version 6.0 kit. The License PAKs for Message Router, Message Router gateway, DEC Notes, VAX FMS, and the CDA Converter Library can be registered automatically using the Office Server Version 6.0 installation procedure The License PAKs supplied for these products are for VAX installations only, and are for any number of users. If you already have a license for one of these products, it will be replaced by the license supplied with the Office Server Version 6.0 kit. To register the License PAKs automatically, follow Steps 1 to 5 in Table 2-2. Preparing Your System for Installation 1-15 Preparing Your System for Installation 1.4 Licensing Enter RL when the installation prompts you with the following question: * Which installation do you wish to perform [1]: ________________________Note ________________________ Choosing the RL option does not start the installa- tion. _____________________________________________________ The installation procedure checks your existing licenses, and if necessary registers and loads the appropriate licenses for the software products provided with the Office Server Version 6.0 kit. The installation then terminates. For prerequisite or optional products that are not supplied with Office Server, you must register the license PAKs manually using the License Management Facility (LMF). 1.5 Example Order for Installing Optional Software After you have installed and configured the prerequisite software, install and configure the optional software products. See the appropriate product documentation for installation and configuration instructions. The following installation order is suggested for installing optional software before the Office Server Version 6.0 installation: 1. Install ACMS 2. Install VAX DATATRIEVE or DEC DATATRIEVE 3. Install and configure your message transport and directory service software. o For new or upgrade installations with Message Router, make sure that Message Router is installed, configured and running before you start the Office Server installation. If you plan to use a remote Message Router Directory Service, you must do a customized Message Router configuration to enable remote Directory Service access and configure Message Router exception reporting for the Directory 1-16 Preparing Your System for Installation Preparing Your System for Installation 1.5 Example Order for Installing Optional Software Service and Transfer Service according to your planning decisions. o For new installations with Compaq X.500 and the MAILbus 400 MTA make sure that you have installed and configured all the required components on your Office Server node or cluster. Compaq X.500 and the MAILbus 400 MTA must be correctly installed, configured and running before you start the new Office Server installation. See the MAILbus 400 MTA and Compaq X.500 Planning chapter in the Compaq Office Server Planning and Setup Guide. 4. Install and configure optional gateway products. o The Message Router VMSmail Gateway if required with Message Router. o The MAILbus 400 Message Router Gateway if required with the MAILbus 400 MTA. o The MAILbus 400 SMTP Gateway if required with the MAILbus 400 MTA. 5. Install DEC Notes. 1.6 Installation Procedure Requirements This section describes the requirements for installing Office Server Version 6.0. It explains how to check the values and how to change them if necessary. 1.6.1 Installing Account Requirements Use the SYSTEM account to install Office Server Version 6.0. The installing account must have a valid rights identifier which is the same as the UIC for the account name. If you are using the SYSTEM account, the rights identifier must be the same as the UIC. To check the UIC and identifier values, do the following: $ RUN SYS$SYSTEM:AUTHORIZE UAF> SHOW/IDENTIFIER SYSTEM Preparing Your System for Installation 1-17 Preparing Your System for Installation 1.6 Installation Procedure Requirements The value that is displayed is the UIC of the system account. To add the rights identifier, if it is not set up, do the following: UAF> ADD/IDENTIFIER SYSTEM/VALUE:UIC=[1,4] UAF> EXIT The installing account must also have sufficient quotas to enable you to perform the installation. Table 1-4 summarizes the requirements. Note that these values are sufficient for installation, but they may not be appropriate for running Office Server. When you create new user accounts for Office Server Version 6.0 the process quotas are set to the appropriate values. Table 1-4 Process Account Quotas for the Installing __________Account_________________________________________ Account Quota_________VAX____Alpha__Notes_________________________ BYTLM 64 64 000 000 ENQLM 300 300 FILLM 200 200 JTQUOTA 1800 1800 JTQUOTA can be returned to its normal system running value after the installation has completed. PGFLQUOTA 25 65 000 000 _____________________pagelets_____________________________ 1.6.2 System Parameters Table 1-5 lists the minimum required system parameter values for the installation. Depending on the kinds of programs and applications running at your site, you may need higher values for some settings. If necessary, modify the parameters to at least these values. 1-18 Preparing Your System for Installation Preparing Your System for Installation 1.6 Installation Procedure Requirements ________________________Note ________________________ You must check the OpenVMS system parameters on each node in the cluster on which you install Office Server Version 6.0. _____________________________________________________ The values for the system parameters and quotas given in this section are those specific to Office Server Version 6.0 and are acceptable for most systems. Dynamic system parameters are labelled with a (D) after them. You do not need to reboot your system after changing dynamic system parameters. If you need to set new values for other system parameters, you must reboot your system in order for the changes to take effect. Table_1-5_Minimum_System_Parameter_Values_Required______________ System Parameter_____VAX_________________Alpha_________________________ CTLPAGES 100 100 ________________________________________________________________ GBLSECTIONS 250 (new) 250 (new) 50 (upgrade) 50 (upgrade) ________________________________________________________________ GBLPAGES 20000 (new) 35000 (new)[1] 5000 (upgrade) 5000 (upgrade)[1] ________________________________________________________________ [1]For_Alpha_systems_after_OpenVMS_Version_7.1,_the_value_of____ GBLPAGES is dynamic. (continued on next page) Preparing Your System for Installation 1-19 Preparing Your System for Installation 1.6 Installation Procedure Requirements Table_1-5_(Cont.)_Minimum_System_Parameter_Values_Required______ System Parameter_____VAX_________________Alpha_________________________ GBLPAGFIL For new installa- For new installations: tions: 1. Add 1 to the number of 1. Add 1 to the active users. There is an number of upper limit of 200 for this active users. value, so use 200 if your There is an value is greater than 200. upper limit 2. Add 32 of 200 for this value, so use 200 if your value is greater than 200. 2. Multiply your value by 16. 3. Add 500 __________________________________________________ (continued on next page) 1-20 Preparing Your System for Installation Preparing Your System for Installation 1.6 Installation Procedure Requirements Table_1-5_(Cont.)_Minimum_System_Parameter_Values_Required______ System Parameter_____VAX_________________Alpha_________________________ GBLPAGFIL For upgrade For upgrade installations: installations: 1. Add together the number of 1. Add together global buffers[2] on the the number following files in OA$DATA_ of global SHARE: buffers[2] on o ATTENDEE.DAT the following files in o MEETING.DAT OA$DATA_SHARE: o PENDING.DAT o ATTENDEE.DAT o PROFILE.DAT o MEETING.DAT 2. Add the total from Step 1 o PENDING.DAT to the number of global o PROFILE.DAT buffers in the shared document attributes files, 2. Add the total OA$DAF_n.DAT in OA$SHARn, from Step 1 to where n is a letter from A the number to E. of global 3. Divide the total by 4 to buffers in the convert to global pages shared document attributes 4. Add 32 files, OA$DAF_ n.DAT in OA$SHARn, where n is a letter from A to E. 3. Multiply the total by 4 to convert to global pages 4. Add 500 [2]To_find_the_number_of_global_buffers_do_a_DIR/FULL_for_each__ file. (continued on next page) Preparing Your System for Installation 1-21 Preparing Your System for Installation 1.6 Installation Procedure Requirements Table_1-5_(Cont.)_Minimum_System_Parameter_Values_Required______ System Parameter_____VAX_________________Alpha_________________________ ________________________________________________________________ LOCKIDTBL 100 multiplied 100 multiplied by the number by the number of of users active users ________________________________________________________________ MAXBUF (D) 5000 5000 ________________________________________________________________ MAXPROCESSCNT 50 plus the number 50 plus the number of active of active users users ________________________________________________________________ RESHASHTBL 50 multiplied 50 multiplied by the number of by the number of active users active users ________________________________________________________________ SCSNODE Must be the same Must be the same as the DECnet as the DECnet node node name name ________________________________________________________________ SCSSYSTEMID DECnet area number DECnet area number multiplied multiplied by by 1024, plus the DECnet node 1024, plus the number DECnet node number ________________________________________________________________ VIRTUALPAGECNT16]384 pages[4] 250 000 pagelets [3]A_high_value_of_VIRTUALPAGECNT_is_required_when_running_the__ File Cabinet test and repair procedure (FCVR program). For versions of OpenVMS after Version 7.0, VIRTUALPAGECNT is not required. [4]This value is approximately the same as 250 000 pagelets. ________________________________________________________________ 1-22 Preparing Your System for Installation Preparing Your System for Installation 1.6 Installation Procedure Requirements ________________________Note ________________________ For the majority of installations, the values for CTLPAGES are sufficient. If you are planning to reboot your system to change other system parameters, you can increase the value to 200 for the duration of the installation. _____________________________________________________ 1.6.3 Displaying Current System Parameters Run the SYSGEN utility to display the current parameter settings: 1. To display all the current system parameter settings, enter: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> SHOW /ALL 2. To show each system parameter setting separately enter: SYSGEN> SHOW parameter where parameter is the parameter you want to examine. 3. Press Ctrl/Z to leave SYSGEN. To check the number of free global pages and sections, enter the following commands: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") If the value of free global pages or global sections is less than the value in Table 1-5 you must increase the system parameter setting. If the values displayed by the system are greater than the required values, you do not need to change the values for these parameters. 1.6.4 Changing System Parameter Values Edit the file SYS$SYSTEM:MODPARAMS.DAT to change the system parameter values. The entry that you make in this file depends on which of the parameters you are modifying. See Table 1-6. Preparing Your System for Installation 1-23 Preparing Your System for Installation 1.6 Installation Procedure Requirements If you need to change and update non-dynamic system parameters, you must schedule time to reboot your system in order for the changes to take effect. The (D) after the system parameter value shows that they are dynamic parameters. Table_1-6_Changing_System_Parameter_Values________________ To change the following parameters_______Do_the_following_________________________ SCSNODE Edit SYS$SYSTEM:MODPARAMS.DAT and specify SCSSYSTEMID new parameter values. Use assignment statements of the form: parameter = parameter-value where parameter is the name of the parameter you want to change and parameter-value is the setting you want to change it to. See Table 1-5 for the required value. __________________________________________________________ CTLPAGES Edit the file SYS$SYSTEM:MODPARAMS.DAT to GBLPAGES specify new values. Include a line of the GBLPAGFIL following format for each parameter to be GBLSECTIONS changed: LOCKIDTBL ADD_parameter = increase-value MAXBUF (D) where parameter is the name of the MAXPROCESSCNT parameter you want to change, and RESHASHTBL increase-value is the amount by which VIRTUALPAGECNT you want to increase the setting of this parameter. For example, to increase the value of LOCKIDTBL by 60, enter: ADD_LOCKIDTBL=60 _________________See_Table_1-5_for_the_required_values.___ If you change any of the system parameter values, you must update them using AUTOGEN. See Section 1.6.4.1 and Section 1.6.4.2. 1-24 Preparing Your System for Installation Preparing Your System for Installation 1.6 Installation Procedure Requirements 1.6.4.1 Updating Dynamic System Parameters with AUTOGEN To update the dynamic system parameter values, do the following: 1. Run AUTOGEN as follows: $ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS 2. Write the changes to the current system: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE CURRENT SYSGEN> WRITE ACTIVE 3. Press Ctrl/Z to leave SYSGEN You do not need to reboot your system to make your new values take effect. For more information, see the OpenVMS manual describing the AUTOGEN utility. 1.6.4.2 Updating Non-Dynamic System Parameter with AUTOGEN To update non-dynamic system parameter values, do the following: 1. Run AUTOGEN as follows: $ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS 2. Check the values. 3. Manually reboot the system when convenient. ________________________Note ________________________ You must reboot your system in order for the new values to take effect. _____________________________________________________ For more information, see the OpenVMS manual describing the AUTOGEN utility. Preparing Your System for Installation 1-25 Preparing Your System for Installation 1.6 Installation Procedure Requirements 1.6.5 Disk Space on Your System Disk or Alternate Working Device This section discusses the disk space requirement for your kit working device during an Office Server Version 6.0 installation. The default disk for your kit working device is your system disk. If your system disk does not have sufficient space, you can specify an alternate working device (AWD) when you start the installation. The disk space values for your kit are given in the documentation provided with your kit. You must check the disk space requirements on the target disks where Office Server Version 6.0 will be installed. See Section 1.6.7. You can run the installation in either safety or non- safety mode. ________________________Note ________________________ Compaq recommends that you run your installation in safety mode (the default). _____________________________________________________ When you run the installation in safety mode, all of the Office Server Version 6.0 kit is restored onto the system disk or AWD before the files are copied to their target locations. This means that you need a disk space requirement greater than the total size of the Office Server Version 6.0 kit on your system disk. The disk space values for installing your kit in safety mode are given in Appendix C, or the documentation that is supplied with your kit, if not US or GB. If you do not have enough disk space to run the instal- lation in safety mode, you can run the installation in non-safety mode. In this case, each kit saveset is restored to the system disk before being copied to the target area. You need an amount of disk space on your system disk greater than the size of the largest saveset provided in the Office Server Version 6.0 kit. The disk space values for installing your kit in non-safety mode are given in Appendix C, or the documentation that is supplied with your kit, if not US or GB. 1-26 Preparing Your System for Installation Preparing Your System for Installation 1.6 Installation Procedure Requirements 1.6.6 Using the OA$LIB_SHARE Disk as the AWD If you have sufficient space on the target disk on which OA$LIB_SHARE will reside, Compaq recommends that you use this disk as the AWD. If you do have sufficient space to install on this target disk, the installation time can be reduced by approximately 20%. This is because the majority of the Office Server files reside in the OA$LIB_SHARE directory and therefore the installation procedure can move those files to their target directories by using a RENAME operation, rather than a COPY operation. 1.6.7 Disk Space for Office Server Areas on Target Disks You can install Office Server Version 6.0 in the following ways: o On a single target disk o Across several target disks by installing Office Server areas on separate disks. For upgrade installations, the installation procedure assumes that the Office Server disks and top-level directories for the Office Server areas have not changed, and that the Office Server directory tree is the same. If you have moved any of the directories, you must put them back to their correct locations before upgrading. You can install more than one Office Server area on the same disk. If you do this, add the disk space values for the two areas together to find the total space required on that disk. See Compaq Office Server Planning and Setup Guide for more information about Office Server areas. The disk space requirements for Office Server language and market areas that you are installing are provided in the documentation supplied with your kit. To calculate the total disk space requirements for your installation, add together the disk space requirements given in this section and the requirements given in Appendix C, or the documentation that is supplied with your kit, if not US or GB. Preparing Your System for Installation 1-27 Preparing Your System for Installation 1.6 Installation Procedure Requirements The disk space requirements for each Office Server area are listed in the following tables: o Table 1-7 for a new installation. See Section 1.6.9. o Table 1-8 for an upgrade installation. See Section 1.6.10. o Table 1-9 for the addition, upgrade or update of VAX or Alpha architecture support. See Section 1.6.11. These values can also be used for the addition, upgrade or update of architecture support for an additional language. You are prompted to specify the target disks for each Office Server area during the installation. 1.6.8 Assigning Logical Names to Your Disks Compaq recommends that you assign logical names to your disks where possible. ________________________Note ________________________ To avoid conflicts with system logical names, do not assign logical names that start with: o A1$ o OA$ o OA1$ _____________________________________________________ In all types of installation, the installation procedure checks for conflicting system and process logical names, which could cause the installation to fail. You can check for conflicts before you start the installation. See Section 1.10 which describes how to run the Perform all preinstallation checks (PC) option. The logical name checking includes a check for any exist- ing logical names that start with OA$. An informational message lists the names found, and a warning message warns you that these logical names may be redefined. 1-28 Preparing Your System for Installation Preparing Your System for Installation 1.6 Installation Procedure Requirements If a logical name conflict is found, an informational message is displayed. If the conflicting logical name is defined in a system table, you can remove the conflicting logical name from another process, and then repeat the check. If the conflicting logical name is specific to the installing process, then you must abort the installation to fix the problem and then restart it. The installation will not continue until the logical name checking has passed. For all upgrade or update installations, make sure that Office Server logical names do not point to system root directories; for example, OA$LIB_SHARE must not be defined as SYS$SYSROOT:[ALLIN1.LIB_SHARE]. Do not use SYS$SYSDEVICE in directory specifications if you are installing on a mixed architecture cluster as the SYS$SYSDEVICE is different for each architecture. 1.6.9 New Installation: Disk Space for Office Server Areas Table 1-7 gives the disk space requirements for installing Office Server areas on the system and target disks. The disk space requirements given are those used during the installation. The permanent space used when the installation has completed may be slightly less. ________________________Note ________________________ If you do not choose to integrate WPS-PLUS during the installation, you can decrease the disk space in the shared library area by approximately 6000 blocks. If you choose to integrate WPS-PLUS, but without the associated PostScript files, you can decrease the disk space in the shared library area by approximately 3000 blocks. _____________________________________________________ Preparing Your System for Installation 1-29 Preparing Your System for Installation 1.6 Installation Procedure Requirements Table 1-7 New Installation: Disk Space for Office Server __________Areas___________________________________________ Office_Server_Area_for_____VAX_________Alpha______________ System disk files[1] 21 000 61 000 Shared library files 71 500 112 000 Shared data files 12 500 12 500 Shared areas[2] 1000 1000 Office Server Manager 1000 1000 account[3] [1]Space_required_to_provide_Office_Server_shared_files_to system directories. Add the value given in the Appendix C (or the documentation that is supplied with your kit, if not US or GB) to get the total value. [2]Multiply the disk space required by the number of shared areas you wish to create during the installation. [3]Includes all utility accounts, for example, IVP and POSTMASTER. __________________________________________________________ For the disk space values for the primary language files, see Appendix C, or the documentation that is supplied with your kit, if not US or GB. ________________________Note ________________________ Do not create the Office Server manager's account in a subdirectory of an OpenVMS system directory. _____________________________________________________ 1.6.10 Upgrade Installation: Disk Space for Office Server Areas Table 1-8 gives the disk space requirements for upgrading Office Server areas on the system and target disks. The disk space requirements given are those used during the installation. The permanent space used when the installation has completed may be slightly less. The values given in the table assume that you choose to purge files during the installation. If you choose not to purge replaced files, you must use the values given in Table 1-7. 1-30 Preparing Your System for Installation Preparing Your System for Installation 1.6 Installation Procedure Requirements ________________________Note ________________________ If you do not choose to integrate WPS-PLUS during the installation, you can decrease the disk space in the shared library area by 5000 blocks. If you choose to integrate WPS-PLUS without the associated PostScript files, you can decrease the disk space in the shared library area by 2000 blocks. _____________________________________________________ Table 1-8 Upgrade Installations: Disk Space for Office __________Server_Areas____________________________________ Office_Server_Area_for_____VAX_________Alpha______________ System files[1] 10 500 61 000 Shared library files 14 500 112 000 Shared data files 2000 2000 [1]Space_required_to_provide_Office_Server_shared_files_to system directories. Add the value given in Appendix C (or the documentation that is supplied with your kit, if not US or GB) to get the total value __________________________________________________________ For the disk space values for the primary language files, see Appendix C, or the documentation that is supplied with your kit, if not US or GB. 1.6.11 Addition of Architecture Support: Disk Space for Office Server areas Table 1-9 gives the disk space requirements for adding, upgrading or updating architecture support on the system and Office Server target disks. These values also apply to the addition, upgrade or update or architecture support for an additional language. Preparing Your System for Installation 1-31 Preparing Your System for Installation 1.6 Installation Procedure Requirements Table 1-9 Addition, Upgrade or Update of Architecture __________Support:_Disk_Space_for_Office_Server_Areas_____ Office_Server_Area_for_____VAX___________Alpha____________ System files[1] 21 000 61 000 Shared library files 48 500 95 000 [1]Space_required_to_provide_Office_Server_files_to_system directories. Add the value given in Appendix C (or the documentation that is supplied with your kit, if not US or GB) to get the total value __________________________________________________________ For the disk space values for the primary language files, see Appendix C, or the documentation that is supplied with your kit, if not US or GB. 1.6.12 Disk Quota Allocation If disk quota is enabled, the installation procedure adds sufficient disk quota for accounts and identifiers created during the installation. 1.6.13 Installed Images Make sure that the shareable image and message files listed in Table 1-10 are installed on your VAX system and Table 1-11 are installed on your Alpha system before you install Office Server. Note that this list of required images applies to the versions of the products listed in Table 1-2. Table_1-10_Installed_Images_Required_on_VAX_______________ Product_______Image_Required_on_VAX_______________________ Always SYS$SHARE:CONVSHR.EXE required SYS$SHARE:CMA$TIS_SHR.EXE SYS$SHARE:DECC$SHR.EXE SYS$SHARE:FDLSHR.EXE (continued on next page) 1-32 Preparing Your System for Installation Preparing Your System for Installation 1.6 Installation Procedure Requirements Table_1-10_(Cont.)_Installed_Images_Required_on_VAX_______ Product_______Image_Required_on_VAX_______________________ SYS$MESSAGE:FDVMSG.EXE SYS$SHARE:FDVSHR.EXE[1] SYS$SHARE:LBRSHR.EXE SYS$SHARE:LIBRTL.EXE SYS$SHARE:MTHRTL.EXE[2] SYS$SHARE:PASRTL.EXE SYS$SHARE:PLIRTL.EXE SYS$SHARE:SCRSHR.EXE SYS$SHARE:VAXCRTL.EXE SYS$SHARE:VMSRTL.EXE __________________________________________________________ ACMS SYS$SHARE:ACMSHR.EXE __________________________________________________________ CDA SYS$SHARE:CDA$ACCESS.EXE SYS$SHARE:IMG$SHRLIB_NOX.EXE SYS$SHARE:DDIF$CC_VIEWSHR.EXE __________________________________________________________ DATATRIEVE SYS$SHARE:DTRSHR.EXE (the standard). If you are using another DATATRIEVE image that you want to link with Office Server, you must make sure that image is installed before the installation. SYS$SHARE:CDDSHR.EXE SYS$MESSAGE:DTRMSGS.EXE SYS$SHARE:CDDEXC.EXE [1]This_is_a_language-specific_image_which_can_have_a_____ different name on other language versions. [2]For certain processors, the logical is defined to point to SYS$SHARE:UVMTHRTL.EXE (continued on next page) Preparing Your System for Installation 1-33 Preparing Your System for Installation 1.6 Installation Procedure Requirements Table_1-10_(Cont.)_Installed_Images_Required_on_VAX_______ Product_______Image_Required_on_VAX_______________________ __________________________________________________________ DEC Notes SYS$SHARE:NOTES$SHARE.EXE __________________________________________________________ Compaq X.500 SYS$SHARE:DXD$DUA_SHR.EXE SYS$SHARE:DXD$XDS_SHR.EXE __________________________________________________________ The MAILbus SYS$SHARE:MTA$XAPI_SHR.EXE 400 MTA __________________________________________________________ Message SYS$SYSTEM:MRTALK.EXE Router __________________________________________________________ TCP/IP SYS$SHARE:UCX$IPC_SHR.EXE __________________________________________________________ WPS-PLUS [3] SYS$SHARE:LCI$SCLHSP.EXE [3]This_image_is_required_only_on_systems_that_have_the___ German kit installed. __________________________________________________________ Table_1-11_Installed_Images_Required_on_Alpha_____________ Product__________Image_Required_on_Alpha__________________ Always required SYS$SHARE:CONVSHR.EXE SYS$SHARE:CMA$TIS_SHR.EXE SYS$SHARE:DECC$SHR.EXE SYS$SHARE:DPML$SHR.EXE SYS$SHARE:FDLSHR.EXE SYS$MESSAGE:FDVMSG.EXE (continued on next page) 1-34 Preparing Your System for Installation Preparing Your System for Installation 1.6 Installation Procedure Requirements Table_1-11_(Cont.)_Installed_Images_Required_on_Alpha_____ Product__________Image_Required_on_Alpha__________________ SYS$SHARE:FDVSHR.EXE[1] SYS$SHARE:LBRSHR.EXE SYS$SHARE:LCI$SCLHSP_TV.EXE SYS$SHARE:LIBOTS.EXE SYS$SHARE:LIBRTL.EXE SYS$SHARE:LIBRTL_TV.EXE[2] SYS$SHARE:MTHRTL_TV.EXE[2] SYS$SHARE:PAS$RTL.EXE SYS$SHARE:SCRSHR.EXE SYS$SHARE:SECURESHR.EXE SYS$SHARE:SECURESHRP.EXE SYS$SHARE:SMGSHR.EXE SYS$SHARE:TIE$SHARE.EXE SYS$SHARE:VAXCRTL_TV.EXE[2] SYS$SHARE:VMS$IEEE_HANDLER.EXE __________________________________________________________ ACMS SYS$SHARE:ACMSHR.EXE __________________________________________________________ CDA SYS$SHARE:CDA$ACCESS.EXE SYS$SHARE:DDIF$CC_VIEWSHR.EXE SYS$SHARE:IMG$SHRLIB_NOX.EXE __________________________________________________________ [1]This_is_a_language-specific_image_which_can_have_a_____ different name on other language versions. [2]This is a logical which typically translates to something like the following example: LIBRTL_D56_TV.EXE (continued on next page) Preparing Your System for Installation 1-35 Preparing Your System for Installation 1.6 Installation Procedure Requirements Table_1-11_(Cont.)_Installed_Images_Required_on_Alpha_____ Product__________Image_Required_on_Alpha__________________ DATATRIEVE SYS$SHARE:DTRSHR.EXE (the standard). If you are using another DATATRIEVE image that you want to link with Office Server, you must make sure that image is installed before the installation. SYS$SHARE:CDDSHR.EXE SYS$MESSAGE:DTRMSGS.EX SYS$SHARE:CDDEXC.EXE __________________________________________________________ DEC Notes SYS$SHARE:NOTES$SHARE.EXE __________________________________________________________ Compaq X.500 SYS$SHARE:DXD$DUA_SHR.EXE SYS$SHARE:DXD$XDS_SHR.EXE __________________________________________________________ MAILbus 400 MTA SYS$SHARE:MTA$XAPI_SHR.EXE __________________________________________________________ TCP/IP SYS$SHARE:UCX$IPC_SHR.EXE __________________________________________________________ WPS-PLUS [3] SYS$SHARE:LCI$SCLHSP.EXE [3]This_image_is_required_only_on_systems_that_have_the___ German kit installed. __________________________________________________________ To check which images are installed on your system, enter the following commands: $ INSTALL INSTALL> LIST imagename imagename; Open Shar Lnkbl imagename is the directory and file specification of the image to be checked. 1-36 Preparing Your System for Installation Preparing Your System for Installation 1.6 Installation Procedure Requirements If there is no entry for the image or the qualifiers are incorrect, you must install the image with the correct qualifiers. To install: o SYS$MESSAGE:FDVMSG.EXE and SYS$SHARE:FDVSHR.EXE, see Section 1.6.14. o Other images, see Section 1.6.15. For more information about installing images, see the manual describing the Install Utility. 1.6.14 Installing FDVMSG.EXE and FDVSHR.EXE Images If the images SYS$MESSAGE:FDVMSG.EXE and SYS$SHARE:FDVSHR.EXE are not installed, do the following: 1. Edit the command procedure SYS$STARTUP:FMSTARTUP.COM to remove the EXIT command that appears before the entry: RUN SYS$SYSTEM:INSTALL 2. Execute the command procedure SYS$STARTUP:FMSTARTUP.COM 1.6.15 Installing Other Images Install other images as follows: $ INSTALL INSTALL> CREATE imagename /OPEN /SHARED /HEADER_RES INSTALL> EXIT 1.6.16 Checking The Location of DCLTABLES.EXE Check that DCLTABLES.EXE is in the directory SYS$COMMON:[SYSLIB]. If it is in a different directory, move it to this location before starting the installation. To check if DCLTABLES.EXE is in the correct location, enter: $ INSTALL INSTALL> LIST/FULL SYS$COMMON:[SYSLIB]DCLTABLES.EXE If it is not in the correct location, remove it: INSTALL> REMOVE DCLTABLES.EXE Preparing Your System for Installation 1-37 Preparing Your System for Installation 1.6 Installation Procedure Requirements Move DCLTABLES.EXE to the correct location and then replace it: INSTALL> CREATE DCLTABLES.EXE /OPEN/SHARED/HEADER_RES 1.7 Additional Tasks for Upgrade Installations If you are upgrading an existing Office Server system, do the following: 1. Review your object libraries. Your object libraries may have been updated if you installed layered products. Office Server provides two template .OLB files in the following directories: - OA$SITE_BUILD_SHARE:SITEOALIBR.OLB - OA$SITE_BUILD_LLV:SITEOALLV.OLB During the installation, a warning is displayed if there are additional .OBJ or .OLB files in these directories. Check that any additional object libraries or files in this directory are compatible with Office Server Version 6.0. Remove any object libraries or files that are not compatible. Although these files are not used during the installation, they will cause problems if you need to relink Office Server after the installation. 2. If you have a multilingual system, check that the files OA$LLV*.EXE are not in SYS$COMMON:[SYSLIB]. If they are, move them to the SYS$SYSROOT:[SYSLIB] directory before upgrading. 3. Check that all files in your site areas have at least system write access (S:W) and that Compaq Office Server directories in non-site areas also have system delete access (S:D). 4. Make copies of customized data files. See Section 1.7.1. 1-38 Preparing Your System for Installation Preparing Your System for Installation 1.7 Additional Tasks for Upgrade Installations 1.7.1 Copying Customized Data Files Office Server Version 6.0 uses modified versions of several data files: o Files that have not been converted but their records have changed or new ones have been added: o CM$SDC o CM$CART$RUNS.DAT o FORMAT.DAT o SM_UTILITY_MASTER.DAT Before upgrading, make copies of any data files that you have customized as new versions of data files are provided with Office Server Version 6.0. You must also return the data files to the Compaq standard format before you upgrade. 1.8 Using the MAILbus 400 MTA and Compaq X.500 You can install a new Office Server Version 6.0 system with the MAILbus 400 MTA and Compaq X.500. You cannot upgrade from ALL-IN-1 Version 3.1 using these products. For a new Office Server Version 6.0 installation, with Compaq X.500 and the MAILbus 400 MTA you must make sure that you have installed all the required MAILbus 400 MTA and Compaq X.500 components on your Office Server system, configured them and completed any additional setup tasks. See the checklist in the MAILbus 400 MTA and Compaq X.500 Planning chapter in the Compaq Office Server Planning and Setup Guide. 1.9 Using a Remote Message Router If you will be using a remote Message Router that is not in the same VMScluster, you must do the following: 1. On the remote Message Router node, create an Office Server mailbox for the node (or cluster) on which you are installing Office Server. See Section 1.9.1. 2. Create an entry for the remote Message Router node in the network nodes database on the local machine on which you are installing Office Server. Preparing Your System for Installation 1-39 Preparing Your System for Installation 1.9 Using a Remote Message Router 3. Ensure that Message Router is running on the remote node before you start the installation. If it is not running, you will see errors when the installation procedure starts up the Sender and Fetcher processes. 1.9.1 Create an Office Server Mailbox on the Remote Message Router Node Do this if you are planning to use a remote Message Router. If you do not create a mailbox before the installation, you will see problems when the installation procedure starts up the Sender and Fetcher processes. Message Router must be running and configured before you start the installation. If you are using a remote Message Router which is on a node in the same VMScluster as Office Server the Office Server mailbox name will be A1. If the remote Message Router is not in the same VMScluster, other Office Server systems may be sharing the same Message Router. The name of the Message Router mailbox must be unique for your system. For example, the mailbox name, mailboxname, could be localnodeA1 where localnode is the name of the node or the cluster on which you are installing Office Server. password is the password that you want to use for the Message Router mailbox. You are prompted for this password during the installation. On the Message Router node, do the following to create the Office Server mailbox: $ RUN SYS$SYSTEM:MRMAN MRM> ADD mailboxname /PASSWORD=password /COMPLETE_MESSAGES /IGNORE_SENDER _ /SERVICE_MESSAGES /SUPPRESS_DELIVERY_REPORTS MRM> EXIT Note that you must not use the /OWNER qualifier when setting up the mailbox. 1-40 Preparing Your System for Installation Preparing Your System for Installation 1.10 Running the Preinstallation System Check 1.10 Running the Preinstallation System Check The Office Server Version 6.0 installation procedure provides a Perform all preinstallation checks (PC) option. Compaq recommends that you use this option before installing Office Server Version 6.0 to ensure that you have made all necessary system changes before installing the software. You can use this option while an existing Office Server system is running so you do not have to ask your users to log out of the system. The option for preinstallation checks allows you to: o Run the phase of the installation in which you answer questions and the installation procedure performs system checks o Fix errors encountered by the installation procedure o Exit without performing the installation Where possible the installation checks are done in an order which finds fatal errors first. Section 1.10.1 describes the types of errors that are detected. Section 1.10.2 describes how to use the Perform all preinstallation checks (PC) option. 1.10.1 Types of Errors Reported The following types of errors are detected: o Fatal errors These are errors which cannot be corrected without stopping the installation procedure. Fatal errors include: - Errors that require the machine to be rebooted - Errors that require an upgrade to prerequisite software, including OpenVMS, Message Router and the Message Router VMSmail Gateway, or Compaq X.500, the MAILbus 400 MTA and Message Router Gateway. o Non-fatal errors Preparing Your System for Installation 1-41 Preparing Your System for Installation 1.10 Running the Preinstallation System Check These are errors that can be corrected from another process without stopping the installation procedure. Non-fatal errors include: - Shareable images that are not installed - Logical names that are not defined - System parameters that can be changed dynamically - Prerequisite software files that are missing - Insufficient disk space 1.10.2 Running the Perform all Preinstallation Checks (PC) Option To run the Perform all preinstallation checks (PC) option, follow Steps 1 to 6 in Table 2-2 until you are prompted with a list of installation options. If you are migrating from MailWorks, the MailWorks migration tool is installed as part of the installation desribed in Table 2-2. Do the following: 1. Press Return to choose the default option. ________________________Note ________________________ Choosing this option does not install the software. _____________________________________________________ The following message is displayed: The installation procedure allows you to perform the following actions: (I) Perform the installation (PC) Perform all preinstallation checks * Which action do you wish to perform [I]: 2. Choose the Perform all preinstallation checks (PC) option by entering: PC. 3. If a check fails with an error that can be corrected without stopping the installation procedure, you are asked if you want to correct the error before continuing. 1-42 Preparing Your System for Installation Preparing Your System for Installation 1.10 Running the Preinstallation System Check If you answer yes, the installation checking procedure pauses so that you can fix the error from another process. When the error is fixed, you can resume the procedure, and the check is repeated. If you choose not to correct the error, you have the option of halting the procedure or continuing to perform the remaining checks. If you choose to continue, the installation procedure will terminate when all the checks are performed. 1.11 Final System Preparation Tasks: New Installations To prepare your system for a new Office Server Version 6.0 installation, do the following: 1. Check that all prerequisite software is installed, configured and running. 2. Start the queue manager, if necessary. 3. Back up the system disk and any target disks. See Section 1.13. 1.12 Final System Preparation Tasks: Upgrade Installations For an upgrade installation from Office Server Version 4.0, carry out the following steps before starting the installation. Each step is described in the following sections. From the privileged SYSTEM account, do the following: 1. Shut down Office Server. See Section 1.12.1. 2. Ensure that Message Router is running and is correctly configured. 3. Deinstall files in the site areas that are installed in memory. See Section 1.12.2. 4. Start the queue manager, if necessary. 5. Back up the system disk and any target disks. See Section 1.13. Preparing Your System for Installation 1-43 Preparing Your System for Installation 1.12 Final System Preparation Tasks: Upgrade Installations 1.12.1 Shut Down Office Server Ask users currently on the system to log out, and then shut down Office Server. ________________________Note ________________________ Office Server must not be used by any batch jobs or users during the installation, or the installation will fail. _____________________________________________________ Do not allow anyone to log in again while the installation is in progress. You can allow OpenVMS users to remain on the system, but it is important to ensure that users do not use DCL HELP while the installation is in progress, as this can cause file locking problems when the DCL HELP library is updated during the installation. If possible, it is safer to ensure that there are no active users on the system. 1.12.2 Deinstall Files Installed in Memory If you have any files in the site areas that are installed in memory, for example, SITE$OA.A1$SECTION, deinstall them on all nodes in the cluster before you start the installation. Deinstalling files from memory will prevent them from being write locked. The installation sets an ACL on all files in the site areas so you must ensure that all files in the site area have system write access (S:W). Make sure that you deinstall any of your own code-level executable images that are installed in memory. 1.13 Back Up Your System and Target Disks Compaq recommends that you do a system disk backup before installing any software because: o If a system failure occurs at a critical point during installation, your Office Server system could be left in an inconsistent state. o You can verify that the backup copy contains a working system image and then replace the system disk with it. 1-44 Preparing Your System for Installation Preparing Your System for Installation 1.13 Back Up Your System and Target Disks o There is more contiguous free space, which may be needed for installation. If you are going to install Office Server Version 6.0 on more than one disk, back up the target disks that you will be using. Use the backup procedures that are established at your site. For details on performing a system disk backup, see the section on the Backup Utility in the OpenVMS System Management Subkit. At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Preparing Your System for Installation 1-45 2 ________________________________________________________________ Installation Procedure: New, Upgrade and Architecture Support This chapter describes the procedures for installing the Office Server Version 6.0 base, language and market components. The following installation examples are given: o A new installation of Office Server Version 6.0 on an Alpha system with the MAILbus 400 MTA and Compaq X.500. See Section 2.1. o Upgrade installation of Office Server Version 5.0 to Office Server Version 6.0 with Message Router and the Message Router Directory Service. The installation is done on the Alpha system in a mixed-architecture VMScluster, where Message Router is installed on a remote VAX node. See Section 2.1. o Addition or upgrade of additional architecture support on a mixed-architecture VMScluster. See Section 2.2. __________________Before You Start __________________ Do not start the installation until you have done the following: 1. Planned your installation by reading the Compaq Office Server Planning and Setup Guide. 2. Completed the system preparation tasks in Chapter 1 to check that your system is ready for the installation. _____________________________________________________ Questions asked by installation procedure are marked with an asterisk (*) at the beginning of the line. For help on answering a particular question, enter a question mark (?). Installation Procedure: New, Upgrade and Architecture Support 2-1 Installation Procedure: New, Upgrade and Architecture Support During the installation procedure a number of cautions and general informational messages are displayed. Read all the displayed messages carefully. Table 2-1 gives information which you may need during the installation. Table_2-1_Information_About_the_Installation_Procedure____ Question_________Answer___________________________________ How long On_Alpha will the As an example, installing on an Alpha installation 4000-610 system takes about 1 hour and 15 take? minutes for a full installation when the files are installed on an RZ28 disk using an alternate working directory (AWD). On_VAX The installation can take from one to six hours, depending on the type of processor you are using. The performance specification of the disks has the greatest effect. For example, an installation on a VAX 4000-300 system takes approximately 3.5 hours when files are installed on an RF71 disk and 1.5 hours if files are installed on an RZ26 disk. The times for new and upgrade installa- tions are approximately the same. How do I get Enter ? at any time help? What is A1060 the product identifier? (continued on next page) 2-2 Installation Procedure: New, Upgrade and Architecture Support Installation Procedure: New, Upgrade and Architecture Support Table 2-1 (Cont.) Information About the Installation __________________Procedure_______________________________ Question_________Answer___________________________________ What do I Restart the installation from the do if the beginning. See Chapter 4. installation fails before the automatic postinstalla- tion phase? How do I Press CTRL/Y. abort the The installation procedure deletes all installation? files in the installation temporary working directory. Note that this may take a long time. Any files that have been provided to target locations remain there. Note: VMSINSTAL does not delete any accounts, identifiers, or directory structures that are created. Restart the installation. How do I See Chapter 4. restart the installation?_____________________________________________ 2.1 Installation Procedure for New and Upgrade Installations Table 2-2 lists all the installation steps for a new or upgrade installation. The example scripts in the table show extracts from a new installation on an Alpha system using the MAILbus 400 MTA and Compaq X.500 and an upgrade installation from Office Server Version 5.0 with Message Router. Installation Procedure: New, Upgrade and Architecture Support 2-3 Installation Procedure: New, Upgrade and Architecture Support 2.1 Installation Procedure for New and Upgrade Installations Table_2-2_Installation_Procedure_for_New_and_Upgrade_Installations Step__Action____________________________________________________ 1 Create a log file for the installation. Compaq recommends that you keep a record of the installation in case of problems. You can keep a log by using either a hard copy terminal or a log file. To keep a record in a log file, enter: $ SET HOST 0/LOG=filename where filename is the name of the log file. The log file is created in the directory where you enter the command. If you do not specify a filename, the file is called SETHOST.LOG. The installation log file will be about 200 blocks. If you are running console management software, you can use this to record the installation. See your console management documentation for further information. ________________________________________________________________ 2 Load and mount the CD that contains the software kit. ________________________________________________________________ 3 Invoke the VMSINSTAL procedure from the SYSTEM account. Enter the following commands: $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL A1060 device To use an alternate working device (AWD), enter the following command lines: $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL A1060 device OPTIONS AWD=disk device is the device on which you have mounted the distribution media. You can use a physical or a logical device name but do not use logical device names beginning with A1$, OA$, or OA1$. A1060 is the product identifier and disk is the location of the alternate working device. ________________________________________________________________ (continued on next page) 2-4 Installation Procedure: New, Upgrade and Architecture Support Installation Procedure: New, Upgrade and Architecture Support 2.1 Installation Procedure for New and Upgrade Installations Table 2-2 (Cont.) Installation Procedure for New and Upgrade __________________Installations_________________________________ Step__Action____________________________________________________ 4 Verify your system backup. OpenVMS VAX Software Product Installation Procedure V7.1 It is 19-JAN-2001 at 13:04. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? Press RETURN to continue. __________________________________________________________ For installation type__________________Go_to_______________________________ New Step 5 Upgrade_______________Step_8______________________________ ________________________________________________________________ 5 New_Installation: Enter the number for the type of installation that you want to do. Logical OA$IMAGE is not defined. No Office Server image can be found using the default specification. Using the FULL Office Server V6.0 kit, the following installation types can be performed: (1) A new installation of Office Server V6.0 (RL) Register licenses for pre-requisite software (MM) Install MailWorks Migration Tool * Which installation do you wish to perform [1]: Enter 1 to install a new Office Server system. ________________________________________________________________ (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-5 Installation Procedure: New, Upgrade and Architecture Support 2.1 Installation Procedure for New and Upgrade Installations Table 2-2 (Cont.) Installation Procedure for New and Upgrade __________________Installations_________________________________ Step__Action____________________________________________________ 6 New_Installation: Confirm that you want to start the installation. The installation procedure allows you to perform the following actions: (I) Perform the installation (PC) Perform all pre-installation checks * Which action do you wish to perform [I]: Press RETURN to start the installation. ________________________________________________________________ 7 New_installation: Specify whether you want a File Cabinet only system. * Do you wish to install Office Server as a File Cabinet Only system [NO]? You should be aware that if you answer Y any future installation will take this option automatically. If, after installing Office Server as a File Cabinet only system, you want to revert to a full Office Server system, you will need to contact your Compaq Support Center. Press RETURN to install a full Office Server system. To_continue: go to Step 11. ________________________________________________________________ (continued on next page) 2-6 Installation Procedure: New, Upgrade and Architecture Support Installation Procedure: New, Upgrade and Architecture Support 2.1 Installation Procedure for New and Upgrade Installations Table 2-2 (Cont.) Installation Procedure for New and Upgrade __________________Installations_________________________________ Step__Action____________________________________________________ 8 Upgrade_Installation: Enter the number for the type of installation you want to perform. The current product image identification is V5.0. Using the FULL Office Server V6.0 kit, the following installation types can be performed: (1) Upgrade of Office Server V5.0 to Office Server V6.0 (2) Add, upgrade, or update Alpha components for an Office Server V6.0 system (RL) Register licenses for pre-requisite software (MM) Install MailWorks Migration Tool * Which installation do you wish to perform [1]: ? Enter 1 to upgrade an existing Office Server system. If you are running Office Server in a single-architecture VMScluster, you are not offered option (2). ________________________________________________________________ 9 Upgrade_Installation: Confirm that you want to start the installation. The installation procedure allows you to perform the following actions: (I) Perform the installation (PC) Perform all pre-installation checks (RC) Run conflict checking and resolution tool (CART) * Which action do you wish to perform [I]: Press RETURN to continue with the installation. ________________________________________________________________ (continued on next page) Installation Procedure: New, Upgrade and Architecture Support 2-7 Installation Procedure: New, Upgrade and Architecture Support 2.1 Installation Procedure for New and Upgrade Installations Table 2-2 (Cont.) Installation Procedure for New and Upgrade __________________Installations_________________________________ Step__Action____________________________________________________ 10 Upgrade_installation: Specify whether you want a File Cabinet only system. This question is asked only for upgrades to full Office Server systems. If the system you last installed was a File Cabinet only system, this question is not displayed. * Do you wish to install Office Server as a File Cabinet Only system [NO]? You should be aware that if you answer Y any future installation will take this option automatically. If, after installing Office Server as a File Cabinet only system, you want to revert to a full Office Server system, you will need to contact your Compaq Support Center. Press RETURN to install a full Office Server system. ________________________________________________________________ 11 In some cases, the following licensing question may be displayed: %A1-I-NOLICENSE, No license PAK was found for this product so it is assumed %A1-I-NOLICENSE, that you are using Client Access Licensing (CAL) * Do you have enough CALs licenses to run this system? [YES] * How many CALs licenses do you have: Enter the number of CALs licenses that you have for this system. ________________________________________________________________ 12 Upgrade_Installation: Confirm that you want to purge files. * Do you want to purge files replaced by this installation [YES]? Press RETURN to purge files. ________________________________________________________________ (continued on next page) 2-8 Installation Procedure: New, Upgrade and Architecture Support Installation Procedure: New, Upgrade and Architecture Support 2.1 Installation Procedure for New and Upgrade Installations Table 2-2 (Cont.) Installation Procedure for New and Upgrade __________________Installations_________________________________ Step__Action____________________________________________________ 13 If DATATRIEVE is already installed, indicate