VMS Authentication Module Administration & User's Guide

Chapter 2 Installing and Configuring VAM

Introduction

This chapter takes you through the VMS Authentication Manager (VAM) product installation procedure and certain post-installation tasks. It is for the OpenVMS system manager, administrator, or technician responsible for product installation.

To prepare for installation, see Chapter 1, Before You Begin.

Note! Once you have installed VAM, you need to reinstall it after you have done a major OpenVMS upgrade.

To install VAM:

1 Load the software.

2 Run the VMSINSTAL procedure.

3 Install other products, if needed, and perform post-installation tasks.

Load the Software

VAM is downloaded from the Process Software FTP site. Information on downloading the software will be supplied to users by Process Software.

There are two steps to loading the VAM software:

1 Log in to the system manager's account.

2 Physically load the distribution media onto the appropriate device.

• In a VMScluster environment, if you want to access the media from more than one node, enter the following:

$ MOUNT/CLUSTER/SYSTEM device VAM010

• On a standalone system, or if you want to prevent multiple users from accessing the software, enter the following:

$ MOUNT device VAM010

Note! If you install VAM on a VMS cluster that has a common system disk, install the software on only one node in the cluster.

Be sure to configure VAM on all systems in a VMS cluster that has a common system disk, even though it only needs to be installed once.

Start VMSINSTAL

VMSINSTAL is the OpenVMS installation program for layered products. VMSINSTAL prompts you for any information it needs. Table 2-1 shows the steps to follow.

Table 2-1 Starting VMSINSTAL

Step	For this task...	Enter this response...
1	Make sure that you are logged in to the system manager’s account, and invoke VMSINSTAL	@SYS$UPDATE:VMSINSTAL
2	Determine if you are satisfied with your system disk backup	Return or Y (Yes) or N (No)
3	Determine where the distribution volumes will be mounted	The disk (and directory) where you want the software to be mounted.
4	Enter the products you want processed from the first distribution volume set	VAM010
5	Enter the installation options you wish to use (such as obtaining the Release Notes)	Return for no options or N for Release Notes.
6	Specify the device where you want the files installed.	Return if accepting default of SYS$SYSDEVICE:

Sample Installation

$ @sys$update:vmsinstal vam010 dka600:

OpenVMS Software Product Installation Procedure V8.2

It is 16-FEB-2006 at 14:09.

Enter a question mark (?) at any time for help.

%VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account.

%VMSINSTAL-W-ACTIVE, The following processes are still active:

DECW$SERVER_0

DECW$TE_043B

* Do you want to continue anyway [NO]? y

* Are you satisfied with the backup of your system disk [YES]?

The following products will be processed:

VAM V1.0

Beginning installation of VAM V1.0 at 14:09

%VMSINSTAL-I-RESTORE, Restoring product save set A ...

VMS Authentication Module (R)

This licensed material is the valuable property of Process Software.

Its use, duplication, or disclosure is subject to the restrictions set

forth in the License Agreement.

Other use, duplication or disclosure, unless expressly provided for in

the license agreement, is unlawful.

* What device do you want to install VMS Authentication Module on [SYS$SYSDEVICE:]:

* Do you want to purge files replaced by this installation [YES]?

The installation will now proceed with no further questions.

*******************************************************************

To complete this installation, you must refer to the documentation

and the Release Notes for post-installation instructions.

*******************************************************************

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

Installation of VAM V1.0 completed at 14:09

Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY

Creating installation data file: VMI$ROOT:[SYSUPD]VAM010.VMI_DATA

VMSINSTAL procedure done at 14:10

Installing VAM for the First Time on a Common VMScluster System Disk

No special preparation is required after installing VAM on one node of a VMScluster with a common system disk.

Installing VAM on Mixed Platform Clusters

VAM has no files which can be shared between cluster systems of different architectures.

Post-Installation Steps

The SDCONF.REC file must be obtained from the ACE/Server system or from another VMS system running VAM. This file is to be copied to the <install_device>:[VAM] directory. This is a binary file, so it must be transferred via ftp in binary mode from a non-VMS system.

Post-Installation Using the SecurID or Local UAF VAM Callable Module

To use the VAM callable module, the system manager must add the line

@<install_device>:[VAM]VAM_STARTUP

to the SYSTARTUP_VMS.COM file (SYSTARTUP_V5.COM on VAX/VMS 5.5-2).

Beyond that, no further configuration on the client system is required.

The user will be responsible for using the provided VAM API to integrate VAM into the desired application(s).

Post-Installation Using the SecurID VAM OpenVMS LOGINOUT Callouts

The OpenVMS system requires further configuration to enable the LOGINOUT callouts.

First, the dynamic SYSGEN parameter LGI_CALLOUTS must be set to "1":

Next, the system manager must determine which users are to be required to use SecurID. See chapter 4, Using VAM, for information on configuring the LGI callouts.

To use the VAM callable module, the system manager must add the line

@<install_device>:[VAM]VAM_STARTUP LGI

to the SYSTARTUP_VMS.COM file (SYSTARTUP_V5.COM on VAX/VMS 5.5-2).

Note! Including the LGI parameter on the VAM_STARTUP command line will enable both the VAM LGI callouts and the VAM callable module.

Optional Post-Installation Steps

The file <install-device>:[VAM]VAM_SPECIFIC_STARTUP.TEMPLATE may be edited and renamed to <install_device>:[VAM]VAM_SPECIFIC_STARTUP.COM. The file contains system-or-site-specific commands to be executed when VAM starts.