DIGITAL Digital X.500 Directory Service Version 3.1 for Digital UNIX Systems Read Before Installing AV-Q1TFF-TE Prerequisite Software Before you install the Digital[TM] X.500 Directory Service, ensure that you have the following installed and working: o Digital[TM] UNIX[TM] V4.0D, or later. Digital UNIX V4.0A may be used, provided you apply patch 123.00 (OSF405-400151). Digital UNIX V4.0B may be used, provided you apply patch 44.00 (OSF410-400151). At the time of writing, no patch is available for Digital UNIX V4.0C. The installation requires the OSFBASE subset o DECnet[TM]/OSI[R] V4.0A for Digital UNIX, or later The installation requires the DNANETMAN subset, and the DNABASE and/or DNAKBIN subsets, depending on whether you want to use DECnet/OSI and/or TCP/IP transport services Year 2000 Conformance With this release, the time matching rules used by the DSA have been changed so that dates beyond the year 2000 are recognized by the DSA. Time syntaxes, such as, UTC Time, represent the year as a two digit number For example, 10.30am GMT on 5th January 1997 is expressed in UTC Time as 970105103000Z. With the new time matching rules, a time value with a year that is less than 50 is assumed by the DSA to be after 2000. For example, a time value containing the year 01 is assumed by the DSA to be 2001. A time value with the year equal to or greater than 50 is assumed by the DSA to be between 1950 and 1999. For example, a time value with the year 97 is assumed by the DSA to be 1997. Note that existing time values stored in the directory that con- tain a year value less than 50 will be affected by the new time matching rules used by the DSA. Upgrading from V3.0 of the Directory Service In Version 3.0, and later (including ECO kits), the DSA uses mem- ory image files instead of snapshot files. Memory image files are version specific, therefore, your current memory image files cannot be used by Version 3.1 of the Directory Service. To use your existing database with Version 3.1 of the Directory Service, create a snapshot file of your database before you upgrade. To create a snapshot file, disable and delete the DSA using the following NCL commands: NCL> DISABLE DSA NCL> DELETE DSA TO SNAPSHOT After installing Version 3.1 of the Directory Service, use the following NCL commands to recreate the DSA: NCL> CREATE DSA FROM SNAPSHOT NCL> ENABLE DSA When the DSA has been recreated and enabled successfully, you can delete the snapshot file from the DSA system as follows: # rm /var/dxd/DSA-information-tree.snapshot* The DSA does not need this file any longer, so you can save disk space by deleting it. Do not delete any of the other database files. Upgrading from Pre-V2.0 Versions of the Directory Service If you are upgrading from V2.0 or later, there is no need to read this section. The V3.1 installation converts any pre-V2.0 database to change the object identifiers of the following attribute types: ___________________________________________________________________ Table_1:__Attribute_Types_Whose_Object_Identifiers_Are_Converted___ Attribute_Type______________New_Object_Identifier__________________ name becomes {attributeType 41} givenName becomes {attributeType 42} initials becomes {attributeType 43} generationalQualifier becomes {attributeType 44} uniqueIdentifier becomes {attributeType 45} dnQualifier becomes {attributeType 46} enhancedSearchGuide becomes {attributeType 47} protocolInformation becomes {attributeType 48} distinguishedName___________becomes_{attributeType_49}_____________ 2 In pre-V2.0 releases, these attributes had the wrong object iden- tifiers. If you are upgrading from a more recent version, then this conversion has already happened. WARNING If you have a pre-V2.0 installation, and have corrected these object identifiers manually, contact Digital for details of how to upgrade. You must upgrade all pre-V2.0 Directory Service software as soon as possible. This is because changing object identifiers causes interworking problems between pre-V2.0 versions and more recent versions. If it is not possible to upgrade all pre-V2.0 systems, contact Digital. If the Directory Service is installed on any ULTRIX[TM] systems, contact Digital. The last version of the Directory Service to sup- port the ULTRIX operating system was V1.3, so there is no upgrade option. Do not use old schema files instead of the newly installed files, as old schema files contain the incorrect object identifiers, as well as lacking some new definitions. If you have customized the schema, you need to edit your customizations into the newly installed schema files. Your old schema files are saved during deinstallation of the old version of the Directory Service (see Files Saved When Deinstalling). Installing on a Distributed Computing Environment System If you install the DCE software after the Directory Service, you will need to reinstall the Directory Service. Make sure that the DCE software is installed before the Directory Service. Files Saved When Deinstalling The installation procedure saves some files if you use setld to deinstall a subset. The files that are saved are as follows: /var/dxd/scripts/create_inbound_clns_template.ncl /var/dxd/scripts/create_inbound_cons_template.ncl /var/dxd/scripts/create_outbound_clns_template.ncl /var/dxd/scripts/create_outbound_cons_template.ncl /var/dxd/scripts/start_dsa_event_dispatching.ncl /var/dxd/scripts/dxd_aci_template.dxim /var/dxd/scripts/start_dsa.ncl /var/dxd/scripts/stop_dsa.ncl Each of the above files is renamed by appending .savn to the file name. For example, create_inbound_clns_template.ncl becomes cre- ate_inbound_clns_template.ncl.sav1. 3 If any of the schema files from a previous installation have been edited, the deinstallation saves all schema files to a subdirec- tory called /var/dxd/savn where n is a number. The schema data file dxd_schema.dat is also saved to that directory. Configuration Tutorials Chapter 2 and Chapter 3 of Digital X.500 Directory Service Man- agement provide configuration tutorials. If you are installing Digital's Directory Service products for the first time, you might find the tutorials a useful introduction to managing the product. Digital Equipment 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. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. ©Digital Equipment Corporation. 1997. All rights reserved. 4