Sablime Configuration Management System • v8.3
This guide provides information and instructions for downloading and installing Sablime on UNIX* or Linux*. The guide is intended for first-time installations. If you already have Sablime and are upgrading to the current version, see the Upgrade Guide.
There are three types of installations covered by this document:
You’re installing Sablime for users on this machine and maybe by some Web users.
Network Client Installation (NFS*)
You’ve already installed Sablime on another host, and this machine will be sharing access to those databases via NFS-shared disks.
If the hosts are the same architecture, then you needn’t do any installation on this machine. Mount the databases and the binaries onto the new machine.
Network Client Installation (TCP/IP)
You’ve already installed Sablime on another host, and this machine will be sharing access to those databases via TCP/IP (i.e. without shared disks).
The three types follow the same process except where specifically noted.
Technical Notes The Sablime software and the installation
process are intended for use with the Korn shell (ksh).
The installation process and Sablime itself use perl (version 5.004_01 or later). The installation process uses gunzip to uncompress the downloaded file. These, as well as tar, sed, strings, and uname must be in the installer’s $PATH.
Note for Linux users: The shell variables $SHELL and $EXECSHELL must both be set to the location of ksh (normally /bin/ksh) and exported. $PWD must also be exported: pdksh, which is usually what /bin/ksh points to, does not export $PWD by default.
Download the appropriate file (sab83_architecture.gz) from the Sablime v8.3 download page. Also download the installation script sablime_install.
If you did not download it there directly, move or copy the file(s) to your UNIX or Linux Sablime host machine.
Log into the Sablime host as the user ID that will own the Sablime binaries and databases. You should not install Sablime as the “root” user.
Create a directory to be the location of the Sablime binaries. We’ll refer to this as SABHOME:
$mkdir SABHOME # for example: mkdir /usr/sablime/bin
Move the downloaded files into SABHOME:
$mv sab83_architecture.gz sablime_install SABHOME
Run the installation script:
$cd SABHOME $./sablime_install -newbin $PWD
$cd SABHOME $./sablime_install -newbin -master=DIR $PWD
The second version is for NFS clients only (that is, clients sharing the databases of the primary installation via NFS, but not sharing its binaries). DIR should be the path to the binaries of the primary installation. Note that the NFS clients must have DIR mounted, even though we will be installing a separate copy of the binaries into SABHOME.
sablime_install can be restarted if it is interrupted. It will announce it is ready to restart, and verify the installation location with you before proceeding to complete the interrupted installation.
At this point, the full set of Sablime files have been placed onto your machine. You can view the full set of Sablime documenation, or review the Sablime Administrator or User Training materials without needing to complete the installation (yet).
If you have a web server that can access the files on this machine, or if you have a browser that can browse local files, you can point the browser to SABHOME/web/docs/documentation.html to find an index of the available Sablime documentation. You could also copy that directory's contents to another machine if necessary to make it browsable.
To get an evaluation license for Sablime, run the admin_license script to generate the request file. Update the file as instructed and email it to the business office at firstname.lastname@example.org.:
(edit the file)
$cat request.txt | mail email@example.com
If you’ve purchased a license or requested an evaluation license, the business office will email you the license file. Save the contents to a file named .usrid in SABHOME (note that the file name starts with a “.”).
The physical installation of the software is now complete.
If you are doing a first time installation, the next step is to run the initsab command and create your first Sablime “product”. This process is described in the Getting Started Guide.
After that (assuming you intend to use Web Sablime), install Web Sablime according to the instructions in the Web Sablime Installation and Upgrade Guide.
Network Client Installation (NFS)
If you have already installed Sablime on another host, and you are simply installing it on the current machine in order to access those databases on NFS-shared disks, then your installation process is completed.
Network Client Installation (TCP/IP)
If you have already installed Sablime on another host, and you are installing it on the current machine in order to access that database via TCP/IP (i.e. without shared disks), then you have a few more steps to complete:
Update the file net_products in the config subdirectory of SABHOME. This tells Sablime what host to talk to and where to find things there. See the illustration below for details of the file.
Have someone with “root” permissions on the host and client add sablime nnnn/tcp to the /etc/services file on both machines. nnnn can be any number between 1524 and 6000 that isn’t already in use as a service. It must be the same on the host and client. The two machines must also be in each other’s /etc/hosts file (or the NIS equivalent).
Different Unix and Linux operating systems may require somewhat different procedures
for such things as automatically starting the Sablime daemon. Please refer to your local system
administrator and/or documentation for further assistance.
The instructions (3 and 4) are directly applicable to Solaris* systems. HPUX systems, though, place a daemon startup script (having the text described as being added to the rc.local script) into /sbin/init.d, and it is launched by having a symbolic link to it in /sbin/rc2.d.
Have someone with “root” privileges start the Sablime daemon on the host machine:
$cp SABHOME/sablimed /etc/sablimed # copy the daemon into root space $/etc/sablimed # start the daemon
Have your “root” person add the following to the host’s rc.local file (or equivalent) so that the daemon gets restarted upon system reboot:
if [-f /etc/sablimed]; then /etc/sablimed && (echo 'sablimed') > /dev/console fi
The net_products file tells Sablime where to find the databases and executables for products that are not accessible on the local machine. The file should be placed in the config subdirectory of the directory containing the local Sablime binaries (SABHOME).
The following is a sample net_products file, with callouts describing the (semi-colon separated) fields. The file may have multiple lines.
UNIX is a registered trademark of The Open Group.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
NFS and Solaris are trademarks or registered trademarks of Oracle and/or its affiliates in the United States and other countries.
Sablime is a registered trademark of Alcatel-Lucent Inc.
Contents copyright © 2010-2015 Alcatel-Lucent. Permission to photocopy in support of a licensed installation of Sablime is hereby granted.