Legacy Installation
The procedures in this section describe the legacy method for installing the UNIX LSAM. For the preferred method, refer to Preferred Installation Procedures.
This section describes how to install the UNIX LSAM using the legacy method. The type of installation that you require will determine what steps you must take.
PREPARING FOR A NEW LSAM INSTALLATION
When performing a new installation, the procedure for 'Setting up the LSAM Installation Directory' will:
- Create the LSAM installation directory.
- Create a symbolic link from the LSAM installation directory to the LSAM root directory.
Set Up the LSAM Installation Directory
- Create the LSAM installation directory. Use the following syntax:
mkdir /usr/local/lsam<version>
The following example shows the syntax for creating an LSAM installation directory for LSAM version 4.01:
mkdir /usr/local/lsam-4.01
- Create a symbolic link from the new LSAM installation directory to the LSAM root directory with the following syntax:
ln –s <LSAM installation directory> <LSAM root directory>
The following example shows the syntax for creating a symbolic link from the new LSAM installation directory to the LSAM root directory:
ln -s /usr/local/lsam-4.01 /usr/local/lsam
Preparing for an Upgrade LSAM Installation
When performing an upgrade installation, the following procedure for 'Setting Up the LSAM Installation Directory' will:
- Create the LSAM installation directory.
- Change the LSAM root directory symbolic link to point to the new LSAM installation directory.
- Ensure that existing users' jobs will continue to execute.
Set Up the LSAM Installation Directory
- STOP the UNIX LSAM communication in OpCon Enterprise Manager (make sure all running jobs complete first).
- STOP the UNIX LSAM processes on the UNIX machine.
- Create the LSAM installation directory. Use the following syntax:
mkdir /usr/local/lsam<version>
The following example shows the syntax for creating an LSAM installation directory for LSAM version 4.01:
mkdir /usr/local/lsam-4.01
- Remove the symbolic link from the old LSAM installation directory (e.g., usr/local/lsam-3.06/) with the following syntax:
rm <LSAM root directory>
The following example shows the syntax for an installation upgrade:
rm /usr/local/lsam
- Create a symbolic link from the new LSAM installation directory to the LSAM root directory with the following syntax:
ln –s <LSAM installation directory> <LSAM root directory>
The following example shows the syntax for creating a symbolic link from the new LSAM installation directory to the LSAM root directory:
ln -s /usr/local/lsam-4.01 /usr/local/lsam
Update the Job Scripts
Users may need to modify their job scripts. Scripts need to be modified if they rely on the environment variable $PATH to resolve the location of any LSAM utilities when calling them, if they rely on the SAM Socket number (or environment variable $SAM_SOCKET), or if they rely on a hard-coded location. The environment variable $SMA_BINDIR is defined for use within OpCon jobs and contains the path pointing to LSAM utilities. This path may vary across different instances of the LSAM. Update any calls to a utility which may exist in job scripts.
If executed from a context other than a user job (e.g., a disk-monitoring utility that wishes to spawn an OpCon event) "$SMA_BINDIR/" must be replaced by whatever is appropriate.
If a script issues a job-status message via the command:
sma_status "Starting Phase 1"
- or -
/usr/local/lsam/sma_status "Starting Phase 1"
They should change the command to read:
$SMA_BINDIR/sma_startus "Starting Phase 1"
Installing the LSAM
Whether performing a new install or an upgrade, the following procedure:
- Installs the LSAM with the default configuration.
- Allows review and revision of the LSAM's configuration.
Install the UNIX LSAM
- Go to the LSAM root directory with the following syntax:
The following example shows the command for navigating to the LSAM root directory:
cd /usr/local/lsam
- Retrieve the LSAM tar file from /tmp with the following syntax (note the '.' at the end is part of the command):
mv /tmp/<LSAM tar file>
The following example shows the command for retrieving the 11_00.tar file from /tmp:
mv /tmp/<version>.tar.
- The following example shows the command for retrieving the 11_00.tar file from /tmp:
mv /tmp/<version>.tar.
The following example shows the command for extracting the 11_00.tar file on an HP-UX machine:
tar xvf <version>.tar.
- Change the ownership of the files in the bin directory to root with the following syntax:
chown 0 bin/*
- Change the group of the bin directory to root with the following syntax:
chgrp 0 bin/*
- Configure the new LSAM by executing the "install_lsam" script:
./bin/install_lsam `pwd`<SAM_Socket> <LSAM_instance>
(Optional)
<SAM_Socket>is a parameter that can be defined to identify the TCP/IP socket number the LSAM instance will use. If multiple LSAMs will be installed on the same machine to the same parent directory, be sure to specify this parameter.(Optional)
<LSAM_instance>is a parameter that can be defined to identify the name of the LSAM instance. This setting is useful for defining distinctly different operating environments (e.g., Production versus Development environments). Do not specify this parameter if fail-over LSAMs will be installed.
If planning to install fail-over LSAMs, SMA Technologies recommends specifying the same <LSAM root directory> and <SAM_socket>, but omitting the <LSAM_instance> parameter from the install_lsam command on each machine involved in the fail-over configuration.
Use the UNIX "pwd" command in back-quotes (`) as the <LSAM root directory>.
The following example shows the command for setting the SAM Socket Number to 3100 and the LSAM Instance identifier to "prod":
bin/install_lsam `pwd` 3100 prod
The installation process generates and executes the lsam<SAM_Socket> script (e.g., lsam3100). The script searches for the tar and gzip compression utilities on the system. If the search is unsuccessful, the script prompts the user for the utilities' location(s) or instructs the user to edit the LSAM configuration file. If the search is successful, the scripts execute the LSAM configuration program to set the SMAFT compression_support parameter and STDOUT/STDERR file capture (for use with the JORS).
- If installing on Linux, AIX, HP-UX, or Solaris, create the symbolic links to the start up directory so the LSAM will start automatically when the machine is rebooted. Use the following syntax:
bin/ install_lsam_service `pwd` <SAM _Socket>
The following example shows the command for creating the symbolic links for startup of an LSAM using SAM Socket number 3100:
bin/install_lsam_service `pwd` 3100
- Start the LSAM Configuration program to verify the JORS and SMAFT parameters defined in step 6, and to modify any other values as may be necessary. For information on configuring the LSAM, refer to UNIX LSAM Configuration. Use the following syntax:
bin/lsam<SAM_Socket> config
The following example shows the command for starting the configuration program for the LSAM using SAM Socket number 3100:
bin/lsam3100 config
- View and modify relevant configuration parameters.
- Enter
sto save the file. - Enter
qto quit the configuration program.