.ps60 .rm72 .lm8 .ap .para 0,1,2 .flags bold .centre;^*SDE Installation Notes\* .centre;^*April 28, 1989\* .lt Contacts: Kevin Angley, Tina Chambers, or Dave Moore Memorex Telex 3301 Terminal Drive Raleigh, N.C. 27604 (919) 890-1416, (919) 890-1544, or (919) 890-1527 .el .b .centre;^*Preparing Yourself for the Installation\* Before proceeding to install the SDE package, it would be a good idea to call us to get an up-to-date ^&SDE User's Manual\& sent to you free. We'd be glad to do it as we would like to keep up with who's using SDE (keeps our morale up, and encourages us to improve it). Without the ^&SDE User's Manual\&, SDE is not going to do you any good. Alternatively, if you are a whiz with LaTeX, you might be able to produce the manual by following SDE__MANUAL.COM (fetch from SDE's CMS library) after the installation is successfully completed. We say "might" because this command procedure may not be entirely bug-free (unlike the SDE software itself, of course). If, after you install SDE and look at the manual, you decide to deinstall it, that is a simple enough task as all the files created (with a single exception -- see below) reside in a single [SDE$SDE...] tree. The installation process does not alter anything else on your system. .b .centre;^*System Requirements\* The current version of SDE requires at least VMS 5.0 and CMS version 3.0 or better. At the moment, we are running SDE under VMS version 5.1 using CMS version 3.1 and MMS version 2.4. CMS must be installed as a shared image on your system. See CMSSTARTUP.COM in SYS$MANAGER for details. Much of SDE is written in PASCAL, but you won't need the compiler unless you plan to make some changes. SDE can be used either on a standalone system or in a cluster. .b .centre;^*Installation Philosophy In preparing the installation, I chose NOT to have an automated procedure for the installation. I am leary of a command procedure copying files onto my system hither and yon, modifying startup procedures, etc. So the installation is manual, but easy, so that you can see what's happening. .page .b .centre;^*Site-Specific Customization SDE was written for and runs in our environment on a homogeneous VAXCluster sharing a common system disk. However, it should work without change on a standalone system, or a cluster of any type. Some customization to the SDE__SYSTEM__STARTUP.COM file is necessary as part of the installation procedure. See that file for details. SDE rights identifiers are assigned beginning at %X108000 where there should be no conflict. If these values interfere with some pre-existing values, the installation will be a little hairy. Give us a call for assistance. .b .centre;^*Installation It is assumed that you have read the SDE distribution tape into some directory somewhere; let's call it sde__dist (i.e. assign this as a logical while doing the install, or plug in the hardcoded directory name where it appears in the installation instructions below). You should have the following files: .list,"o" .le;^*AAAREADME.TXT\* Your basic readme file telling what SDE is .le;^*SDE__INSTALLATION.RNO\* The DSR source for this file .le;^*SDE__PROCESS__STARTUP.COM\* Commands that must go into each process LOGIN.COM .le;^*SDE__SYSTEM__STARTUP.COM\* Commands that must be executed at system boot .le;^*SDE.BCK\* The backup save set for the [SDE$SDE...] structure .end list This whole directory can go away once installation is complete. You are now ready to proceed with the installation. .list .le;You must set up the VISION and INTEGRATOR identifiers for the SDE project as follows: .lt $ set def sys$system $ run authorize UAF>add/ident/val=ident=%X10803A vision$sde - /attr=(resource,dynamic) UAF>add/ident/val=ident=%X10803B integrator$sde - /attr=(NOresource,dynamic) .el .le;Select a disk where the SDE application is to reside. The SDE application is itself an SDE-managed project, and its directory structure must be set up as distributed. To make the installation a little easier, assign the following process logical: .lt $ assign/process target_disk_name DISK$SDE .el where target__disk__name is the physical device where the SDE software itself is to reside. .le;Recover the SDE.BCK save set to this disk as follows: .lt $ backup/verify sde_dist:SDE.BCK/save - DISK$SDE:[*...]/own=VISION$SDE .el .le;Because of the way backup works, the ACL and protection on the SDE$SDE root directory are not preserved. Execute the following exactly: .lt $ SET FILE/OWN=VISION$SDE DISK$SDE:[000000]SDE$SDE.DIR $ SET FILE/PROT=(S:RWE,O:RWE,G:RWE,W:R) - DISK$SDE:[000000]SDE$SDE.DIR $ SET ACL/ACL=((IDENT=INTEGRATOR$SDE,OPT=PROTECTED, - ACCESS=R+W+E+C), - (IDENT=VISION$SDE,ACCESS=R+E), - (IDENT=INTEGRATOR$SDE,OPT=DEFAULT+PROT, - ACCESS=R+W+E+D+C), - (IDENT=VISION$SDE,OPT=DEFAULT,ACCESS=R+E), - (DEFAULT_PROT,S:RWE,O:RWED,G,W)) - DISK$SDE:[000000]SDE$SDE.DIR .el .le;All of the SDE software resides in the [SDE$SDE...] tree with the single exception -- SDE's CMS event handler which must reside in SYS$SHARE:. Copy this file from the declared level of SDE's executables to your system's SYS$SHARE directory by following the instructions below. You will need to know the integration level (version number) of SDE before doing this step. This should be in the AAAREADME.TXT file in the distribution, on the label (if you got the tape directly from us), or in the comment of the backup save set header info. Alternatively, enter .lt $ DIR DISK$SDE:[SDE$SDE]IL*.DIR .el The "current" level of SDE is the highest IL number ^*minus one\*. For example, if the distribution of SDE that you have contains levels IL60, IL61, IL64, and IL65, then the version of this distribution is 64. Now that you know the version of SDE, use the following commands, replacing the "x" with the version number. .lt $ BACKUP - DISK$SDE:[SDE$SDE.ILx.EXE]SDE_ACTION_UPON_REPLACE.EXE - SYS$SHARE: $ SET FILE/PROT=(S:RWED,O:RWED,G:RWED,W:RE) - SYS$SHARE:SDE_ACTION_UPON_REPLACE.EXE .el .le;At this point, take a look at file SDE__SYSTEM__STARTUP.COM that came in the distribution kit. Following the instructions therein, customize it to your environment now. SDE__SYSTEM__STARTUP.COM must be somehow included in your system startup. One way to do this is to copy this command procedure to SYS$MANAGER, then include a line in SYSTARTUP.COM to invoke it. .le;After you have customized it, execute the SDE__SYSTEM__STARTUP.COM on the running system. You will need it for the rest of the installation. If you are supporting SDE across a cluster, execute on each node on which SDE will be supported. .le;The commands in SDE__PROCESS__STARTUP.COM must be executed at the beginning of each process that will be using SDE. One way to do this is to include the lines in your SYLOGIN.COM (if you have one), but any way you see fit to do it should work. Later on, you may want to move the command definitions therein to the system DCLTABLES. You can worry about that later. .le;Execute the SDE__PROCESS__STARTUP.COM in your current process. You will need it for the rest of the installation. .le;You now have SDE up and available. You will, in fact, use it for some of the remaining steps. Establish your SDE viewpoint as SDE by doing an SDEVIEW: .lt $ SDEVIEW SDE .el .le;The distribution of SDE may have some files deleted to save space. Recreate them now by simply typing: .lt $ MMS .el (Remember that SDEVIEW has defined an MMS symbol to pick up the current viewpoint's description file; also, the SDE project is the first target therein --- that's why MMS is all you need to type). The deleted files will be resurrected. .le;If you want to provide online help for SDE through the system help file, execute the following: .lt $ LIB/INSERT/HELP SYS$HELP:HELPLIB.HLB - SYS$SDE:SDE.HLP .el .le;Select the individual that will serve as SDE Administrator. They must have sufficient privilege to grant and revoke rights identifiers, create top level directories, and manage disk quotas. The SDE Administrator's account must also be granted at least the VISION$SDE identifier: .lt $ SET DEF SYS$SYSTEM $ RUN AUTHORIZE UAF> GRANT/IDENTIFIER/ATTRIBUTE=(DYNAMIC,RESOURCE) - VISION$SDE username UAF> EXIT .el .end list