HP OpenVMS Enterprise Directory Installing Revision/Update Information: Version 5.5 ECO1 This kit also contains HP Administrator for Enterprise Directory for V2.2. Checklist: 1. Read the Read Before Installing document. 2. Check prerequisite software and diskspace. 3. Install Version 5.5 ECO1 of the Directory. Print the release notes and run the IVP during the installation. 4. Edit SYSTARTUP_VMS.COM to submit the directory startup procedure during system startup. 5. If upgrading or reinstalling, recustomize any customized files, specifically: The schema files (recompile the schema if you customize it) DXD$DSA_STARTUP.NCL DXD$TEMPLATE_STARTUP.NCL DXD$DSA_STARTUP.COM DXD$DSA_SHUTDOWN.NCL Other files that might have been customized in a previous version are saved during installation. See Saving Files on Reinstallation. 6. Start the Directory. Prerequisite Software Before you install the HP OpenVMS Enterprise Directory V5.5 ECO1 ensure that you have the following installed and working on your system: o OpenVMS for Alpha V7.3-2 or later or o OpenVMS I64 V8.2 or later For the HP OpenVMS Enterprise Directory V5.5 ECO1 on OpenVMS Alpha V7.3-2 or later (excluding Topaz Alpha), the following optional softwares can be installed on your system: 1. For LDAP or X.500 protocols that use RFC1006 con- nections, HP TCP/IP Services V5.4 ECO5 or later for OpenVMS Alpha. 2. For X.500 protocols over an OSI network, DECnet- Plus for OpenVMS Alpha V7.3-2 or later including the application option (OSAK). Note: At least one of the above-mentioned optional softwares need to be installed for HP OpenVMS Enterprise Directory to work. 3. For LDAPv3 over SSL, HP SSL V1.1 or later for OpenVMS Alpha. For the HP OpenVMS Enterprise Directory V5.5 ECO1 on OpenVMS Alpha V8.2 or later, the following optional softwares can be installed on your system: 1. For LDAP or X.500 protocols that use RFC1006 connec- tions, HP TCP/IP Services V5.5 or later for OpenVMS. 2. For X.500 protocols over an OSI network, DECnet- Plus for OpenVMS Alpha V8.2 or later including the application option (OSAK). Note: At least one of the above-mentioned optional softwares need to be installed for HP OpenVMS Enterprise Directory to work. 3. For LDAPv3 over SSL, HP SSL V1.1 or later for OpenVMS. 2 For the HP OpenVMS Enterprise Directory V5.5 ECO1 on OpenVMS I64 V8.2 or later, the following optional softwares can be installed on your system: 1. HP TCP/IP Services V5.5 or later for OpenVMS Integrity servers. 2. For X.500 protocols over an OSI network, DECnet-Plus V8.2 or later for OpenVMS Integrity servers including the application option (OSAK). Note: At least one of the above-mentioned optional softwares need to be installed for HP OpenVMS Enterprise Directory to work. 3. For LDAPv3 over SSL, HP SSL V1.1 or later for OpenVMS Integrity servers. Information Required Before installing, make sure you have the following information: o The name of the device where the installation media will be loaded. o The UIC to be assigned to the DXD$SERVER account. o The name of the disk where the DXD$SERVER directory is to be created. o For clusters, the server node name. See Installing on Clusters. If this is an upgrade installation, the installation procedure will find the information from the current system. 3 Disk Space, Resource, and Time Requirements You need 40000 free blocks on the system device or Alternate Working Device that you use for the installa- tion. If you are installing either the HP AED Windows kit or the HP AED Utility, you need an additional 130000 free blocks on this disk. After installation, the components require disk space permanently on both the system disk and the disk where the DXD$SERVER directory is to be created. Some components need global pages and sections. These requirements are cumulative. __________________________________________________________ System DXD$SERVER Disk Disk Global Global Component_____________space______space______Pages______Sections Base (mandatory 8000 1000 3200 8 component) Server 18000 - - - Admin[1] 7000 - 3200 4 API 1000 - - - LUC 5000 - - - HP AED[2] Windows - 125000 - - kit HP AED Utility - 101500 - - [1]_______________________________________________________ This is not the HP Administrator for Enterprise Directory; it is the Admin component. [2] This is the HP Administrator for Enterprise Directory; it is the Windows GUI for managing the Directory. __________________________________________________________ The I64 system requires following set of resources to run the DIRECTORY server image. 4 __________________________________________________________ System DXD$SERVER Disk Disk Global Global Component_____________space______space______Pages______Sections Base (mandatory 17500 1000 3200 8 component) Server 25600 - - - Admin[1] 7000 - 3200 4 API 1000 - - - LUC 5000 - - - HP AED[2] Windows - 125000 - - kit HP AED Utility - 310000 - - [1]_______________________________________________________ This is not the HP Administrator for Enterprise Directory; it is the Admin component. [2] This is the HP Administrator for Enterprise Directory; it is the Windows GUI for managing the Directory. __________________________________________________________ Before installing, ensure that the system resources allow for all of the components you install, remembering that the Base component is mandatory. You are recommended to back up your system disk before you begin the installation. Installation of all components takes approximately 15 minutes. Release Notes and Read Before Installing Document Read the release notes before installing the software. Use VMSINSTAL OPTIONS N to print the release notes. The product documentation includes a Read Before Installing document, which you must also read. 5 Installing the HP OpenVMS Enterprise Directory Log in to an account with SETPRV and type: $ @SYS$UPDATE:VMSINSTAL DXDIECO01055 device OPTIONS N The installation procedure displays a menu. Select the components that you want to install and follow the instructions. The Base component is mandatory on all systems on which you want to run directory applications. It is installed automatically when you select any other component. Note that components you do not specify are deinstalled if present. You must specify all components that you want on the system, including any that are already present. HP Administrator for Enterprise Directory If you want to use HP Administrator for Enterprise Directory+ for management of your directory, you should first install the components "HP Administrator for Enterprise Directory-Windows" and "HP Administrator for Enterprise Directory-Utility". When the installation is complete, set DXD$DIRECTORY to be your default directory, and copy the file [.CAED_WIN32]DIRECTORYADMINISTRATOR.EXE to your PC. This file is an executable program that when run on a PC will install HP Administrator for Enterprise Directory. You can also check for a later version of the pro- gram that can be downloaded directly onto a PC from (http://h71000.www7.hp.com/commercial/edir/edir_mgt_gui_download.html). Handling Errors If an error occurs during installation, check the prerequisites, and refer to HP Enterprise Directory - Problem Solving for details of installation problems. ___________________ + See the file ReadMe.txt in the HP Administrator for Enterprise Directory kit for details. 6 Verifying the Installation To verify the installation, run SYS$TEST:DXD$IVP.COM. Tasks After Installation Edit SYS$STARTUP:SYSTARTUP_VMS.COM to include the following command line: $ SUBMIT SYS$STARTUP:DXD$COMMON_STARTUP.COM You also need to run that Directory Service startup file before configuring the product as described in HP Enterprise Directory - Management. If you are reinstalling or upgrading, then you might have old copies of customized schema files. You need to incorporate your customizations into the newly installed schema files, and recompile the schema before starting the DSA. The Read Before Installing document provides further information about upgrading. See the file ReadMe.txt in the HP Administrator for Enterprise Directory kit for details. Saving Files on Reinstallation The installation procedure saves copies of the following files if you reinstall the Directory. SYS$COMMON:[SYS$STARTUP]DXD$DSA_STARTUP.NCL SYS$COMMON:[SYS$STARTUP]DXD$DSA_STARTUP.COM SYS$COMMON:[SYS$STARTUP]DXD$DSA_SHUTDOWN.NCL SYS$COMMON:[SYS$STARTUP]DXD$TEMPLATE_STARTUP.NCL DXD$DIRECTORY:DXD$ACI_TEMPLATE.DXIM Each file is renamed by inserting _SAVn into the file name, where n is a number. If the installation procedure finds schema files, these are moved to a subdirectory called SAVn, for example, DXD$DIRECTORY:[DXD$SERVER.SAV1]. The procedure only moves schema files that were installed by the Directory product. Any schema files created by the customer are unaffected. 7 Installing on Clusters Only one node in a cluster can run the server. The installation prompts you for the server node name, and edits DXD$LOGICALS_STARTUP.COM to define a logical based on your answer. On a cluster that has multiple system disks (including mixed architecture clusters), you must repeat the installation for each system disk. All system disks must run V5.5 ECO1 of the Directory Service. You must install the same components and specify the same server node during each installation. The installation registers the DXIM command. To make the command available to all cluster nodes, use the following command on each node: $ INSTALL SYS$SHARE:DCLTABLES /REPLACE If you prefer, you can use the SYSMAN utility for this task. No AutoAnswer Support in Installation AutoAnswer files can only be used on installations that follow the pattern of previous installations. AutoAnswer files created during a first-time installation (that is, installation on a system that had no Directory previously), are not available during an upgrade. AutoAnswer files created during an upgrade will be available at the time of the next upgrade and any subsequent upgrade. Further Information HP Enterprise Directory - Problem Solving contains a list of the files installed on your system, their locations and approximate sizes. The guide also lists errors that you might see during installation and verification and explains what to do if they occur. 8 © Copyright 2006 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. A FULL SOFTWARE PATCH KIT HAS RECEIVED LIMITED TESTING AND IS CONSIDERED APPROPRIATE FOR GENERAL DISTRIBUTION TO CUSTOMERS. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS FULL SOFTWARE PATCH KIT IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL HP OR ANY OF ITS SUBSIDIARIES BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY SOFTWARE PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH SOFTWARE PATCH. 9