/
                                   | .......................................$EFSDIR
                                   |/
                                  opt
                                   |
                      +------------+--------+------------+-------------+
                      |                     | ...........|.............|....$NSTDIR
                      |                     |/           |             |
                     qm                    msi        oracle        sybase
                      |                     |      
                  +---+------+       +------+-------+
                  |          |   ....|......|.......|.......................$QMPPATH
                  |          |  /    |      |       |
                  |          | /     |      | ......|.......................$TOPDIR
                  |          |/      |      |/      |
                v61a        v62a    v61a   v62a    cst......................$CSTDIR
                  |          |                      |
                  |          |  ....................|.......................$QMDIR
                  |          | /                    |                            
               qm_3_17    qm_3_17             +-----+-----+        
                                              |           |        
                                          6.10.8765   6.20.7654 

                                  /
                                  |
                                 opt.......................$EFSDIR
                                  |
                                 nst.......................$NSTDIR
                                  |
                   +--------------+---------------+
                   |              |               |
                   |     .........|...............|........$QMPPATH
                   |    /         |               |
                   |   /          | ..............|........$TOPDIR
                   |  /           |/              |
           qm_${INST_ID}62a      v62a            cst.......$CSTDIR
                   |                              |
                   | .............................|........$QMDIR
                   |/                             |
                qm_3_31                     +-----+-----+
                                            |           |
                                        6.20.8765   6.20.7654 

• $NSTDIR is central. NetSol suggests naming it nst but that is optional.
• $NSTDIR's parent directory is $EFSDIR, the External File System (meaning external to LeasePak)
• $EFSDIR cannot be / (root).
• $TOPDIR's parent directory is $NSTDIR. $TOPDIR must still be the LeasePak release version, as it has always been.
• $QMPURPOSE
  • Linux:
    $QMPURPOSE is qm_${INST_ID}62a, for example qm_prod62a
    Parallel to $TOPDIR is $QMPPATH, the Queue Manager Parent Path. $QMPPATH consists of $NSTDIR/$QMPURPOSE.
  • HP-UX & Solaris::
    $QMPURPOSE is qm/v62a
    Parallel to $NSTDIR is $QMPPATH, the Queue Manager Parent Path. $QMPPATH consists of $EFSDIR/$QMPURPOSE.
• $QMRELS is used frequently in this document and in the LeasePak administration scripts, and is equal to qm_+$QM_VERSION. In v62a, then, $QMRELS will be qm_3_17 or qm_3_31. See LeasePak Server and Queue Manager Directories
• Finally below $QMPPATH is $QMDIR, which is $QMPPATH/$QMRELS.
• Parallel to $TOPDIR is $CSTDIR, which has a child directory for each build attached to any of the $TOPDIRs release instances under $NSTDIR.
• All of the directories below $NSTDIR must follow the Queue Manager naming restrictions: lower case alpha, digits, and underscore only are allowed. No directories with . (period) or - (hyphen) in their names are allowed.

  #  visudo 

1. If there is no entry like this:

     User_Alias NST = 

   make one and add the names of $NSTADMIN and $NSTDBA separated by commas after the =.
   Use the actual login names, not the environment variables, for the entry:

     User_Alias NST = nsadm62a, nsdba62a

   If there is already a User_Alias NST = line, add the login names of $NSTADMIN and $NSTDBA to the list.
2. If there is no entry like this:

     NST    ALL=NOPASSWD:/bin/chown, /bin/chgrp

   then make one.
   Save and quit vi by:

     :wq(ENTER) 

   Now, anyone whose login name is in the User_Alias NST can run chown and chgrp as if they were logged in as root.
3. In subsequent LeasePak installations on the same application host, the administrator need only add the login names of new $NSTADMIN and $NSTDBA users to the User_Alias NST.

• @@lplicense.ora - for Oracle
• @@lplicense.syb - for Sybase

• Installing from CD:
  • HP-UX - usually SETUP, but may be setup
  • Sun - setup
  • Linux - setup
  • If all else fails, list the files on the CD!
• Installing from CD copy on local disk:
  • All - SETUP

 Red Hat Enterprise Linux Server release 5.4 (Tikanga) 

• Requirements for creating $SRVADM
• Requirements for creating LLDBs, DBOs, & $uetc/physdb.msirc
• Requirements for creating non-administrative users
• Requirements for creating tablespaces & datafiles

• $SRVADM must be created by the DBMS administrator before SETUP is run. The requirements for $SRVADM vary by database system. See also Database Server Administrator.

  DBMS	Requirements for Creating the $SRVADM user
  Oracle	The following are the commands used to create the Oracle $SRVADM
  	CREATE USER $SRVADM             IDENTIFIED BY $PWD_SRVADM; GRANT CREATE SESSION            TO $SRVADM WITH ADMIN OPTION; GRANT ALTER SESSION             TO $SRVADM WITH ADMIN OPTION; GRANT CREATE USER               TO $SRVADM; GRANT ALTER USER                TO $SRVADM; GRANT DROP USER                 TO $SRVADM; GRANT CREATE ROLE               TO $SRVADM; GRANT DROP ANY ROLE             TO $SRVADM; GRANT CREATE TABLE              TO $SRVADM WITH ADMIN OPTION; GRANT CREATE VIEW               TO $SRVADM WITH ADMIN OPTION; GRANT CREATE TRIGGER            TO $SRVADM WITH ADMIN OPTION; GRANT CREATE PROCEDURE          TO $SRVADM WITH ADMIN OPTION; GRANT CREATE TABLESPACE         TO $SRVADM; GRANT ALTER TABLESPACE          TO $SRVADM; GRANT SELECT_CATALOG_ROLE       TO $SRVADM; GRANT ANALYZE ANY DICTIONARY,       ANALYZE ANY               TO $SRVADM; ALTER USER $SRVADM              DEFAULT ROLE SELECT_CATALOG_ROLE; ALTER USER $SRVADM              DEFAULT TABLESPACE $ORA_DFLTSEG;
  Sybase	The Sybase $SRVADM is created as follows:
  	use master go exec sp_addlogin $SRVADM, $PWD_SRVADM grant role sa_role to $SRVADM grant role sso_role to $SRVADM go

• If the LLDB and its owner are created by the DBMS administrator, it should be done according to the information below, which varies according to the database system. See also Creating LeasePak Logical Databases.

  DBMS	Requirements for Creating LLDBs & DBOs
  Oracle	The Oracle LLDB and its owner are the same entity. These are the requirements for creating the owner/LLDB:
  	CREATE USER $MSIDB_DBNAME        IDENTIFIED BY $PWD_MSIDB_DBNAME; CREATE ROLE msi_$MSIDB_DBNAME    NOT IDENTIFIED; CREATE ROLE msir_$MSIDB_DBNAME   NOT IDENTIFIED; GRANT CREATE SESSION             TO $MSIDB_DBNAME; GRANT CREATE TABLE               TO $MSIDB_DBNAME; GRANT CREATE VIEW                TO $MSIDB_DBNAME; GRANT CREATE TRIGGER             TO $MSIDB_DBNAME; GRANT CREATE PROCEDURE           TO $MSIDB_DBNAME; GRANT ALTER SESSION              TO $MSIDB_DBNAME; GRANT msi_$MSIDB_DBNAME          TO $MSIDB_DBNAME WITH ADMIN OPTION; GRANT msir_$MSIDB_DBNAME         TO $MSIDB_DBNAME WITH ADMIN OPTION; ALTER USER $MSIDB_DBNAME         DEFAULT ROLE msi_$MSIDB_DBNAME,                                               msir_$MSIDB_DBNAME; ALTER USER $MSIDB_DBNAME         DEFAULT TABLESPACE $ORA_DFLTSEG                                  QUOTA quota ON tablespace; where quota is either numberM if using a common storage segment (tablespace), or UNLIMITED if using a dedicated storage segment.
  	The file $uetc/physdb.msirc must be updated, with ownership given to $NSTDBA, and the contents:      setenv MSIDB_SEG01 "tablespace,quota" where tablespace and quota must match the values used in creating the LLDB above
  Sybase	The Sybase LLDB is created as an actual Sybase database; its owner is created separately. Following are the requirements for creating the database:
  	use master go create database $MSIDB_DBNAME      on datadev = datasize      log on logdev = logsize go exec sp_dboption $MSIDB_DBNAME 'trunc log on chkpt', true go use $MSIDB_DBNAME go checkpoint go exec sp_addgroup msi exec sp_addgroup msir go
  	The 'trunc log on chkpt' option is NOT valid for production LLDBs and must be replaced with an option that will allow for proper database recovery in the event of failure or error.
  	The file $uetc/physdb.msirc must be updated, with ownership given to $NSTDBA, and the contents:      setenv MSIDB_SEG01 "datadev,datasize,DATA"      setenv MSIDB_SEG02 "logdev,logsize,LOG" where the devices and sizes must match the values used in creating the LLDB above
  	The Sybase database owner is created as shown below. If the $SYB_AUTODBO SETUP option is set to Y, then the database owner's name should be the same as the LLDB name ($MSIDB_DBNAME).
  	use master go exec sp_addlogin $DBO, $PWD_DBO exec sp_locklogin $DBO, 'lock' exec sp_modifylogin $DBO, defdb, master exec sp_locklogin $DBO, 'unlock' go use $MSIDB_DBNAME go exec sp_changedbowner $DBO go
  all	The NetSol Utility Script db_setup_phys may be run to update the physdb.msirc file. This interactive script requires the $SRVADM account password, but does not modify the database system master tables.
  	Under this arrangement, the DBMS administrator will perform the functions handled by the -b and possibly the -p options of db_create; the $NSTDBA may thereafter execute db_create -ocs. db_create will persist in requiring the $SRVADM password; this is not actually used for the -o, -c, and -s options. These three options are equivalent to using:      db_load_obj      db_load_code      db_set_security

• If the $SRVADM is not to create users, then the DBMS administrator will need to create all user accounts in the database system. A distinction is made between users who are to be LLDB owners and users who are not. The creation of all database system users except $SRVADM may be deferred until after SETUP has been run. See also LeasePak non-Administrative User Accounts. The NetSol Utility Scriptdb_add_user is used by the $NSTDBA to enable a user to access a particular LLDB. See also Granting Access to an LLDB to a user.

  DBMS	Requirements for Creating non-Administrative Users
  Oracle	CREATE USER $DBMS_USER IDENTIFIED BY $PWD_DBMS_USER; GRANT CREATE SESSION   TO $DBMS_USER; ALTER USER $DBMS_USER  DEFAULT ROLE NONE; ALTER USER $DBMS_USER  DEFAULT TABLESPACE $ORA_DFLTSEG;
  Sybase	use master go exec sp_addlogin $DBMS_USER, $PWD_DBMS_USER exec sp_locklogin $DBMS_USER, 'lock' exec sp_modifylogin $DBMS_USER, defdb, master exec sp_locklogin $DBMS_USER, 'unlock' go

• If the $SRVADM is not to create or alter tablespaces, then the DBMS Administrator must manage these functions. Tablespaces and their datafiles used by LeasePak must be made with the following characteristics:

  Oracle only - Requirements for tablespaces and datafiles

  To create a tablespace: CREATE TABLESPACE $TABLESPACE DATAFILE '$DATAFILE_PATH' SIZE $DATAFILE_SIZE ATTRIBUTES="AUTOEXTEND OFF EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO";

  To add a datafile: ALTER TABLESPACE $TABLESPACE ADD $FILETYPE '$DATAFILE_PATH' SIZE $DATAFILE_SIZE AUTOEXTEND OFF;

• SETUP -h

  to list out the different options available. Does not install any software

• SETUP $TOPDIR

  to install all parts of the package (this is sometimes called plain SETUP)

• SETUP -b $TOPDIR

  to install just the build part of the package

• SETUP -l $TOPDIR

  (minus small L) to install a new license file

• SETUP begins with loading the VERSION file. This file is part of the CD image shipped by NetSol, and contains information that is universal to all LeasePak installations in v62a and information that is particular to the hardware platform for which the CD image is intended.
• The top directory is cleared out. If LeasePak was installed in this area previously, a number of elements of that installation are maintained:
  • the $TOPDIR/env directories, except for adm_*
  • user data sets in $datasets
  • the previous installation's relscfg.msirc
• The basic system image (top directory tree) is laid down from CD.
• Additional variables based on the location of SETUP and $TOPDIR are set.
• The registry is searched for any previous installations of v62a on the same Application host.
• The Configure Release interview is run. Refer to SETUP Questions for important information about responding to the interview. The operator is given the opportunity to re-run the interview until satisfied with the results, which are displayed after each run.

• If the Queue Manager was already installed in that location, certain data is preserved:
  • Printer and Queue definitions: start_queues.com, the printer mapping commands from Config, and DEVINIT
  • The previous installation's ATT attachment file
  • The $QMDIR directory is cleared out and the image from the CD is laid down. A new ATT attachment file is written.
• The Config file is now self-customizing. The self-modifying file is run and customizes itself to create the new Config. However, the administrator must still enter the printer mapping commands.
• The queue job limit file is setup.
• The preserved data from the previous installation, if any, is restored. The preserved printer mapping commands are left in the file $QMDIR/library/PRIOR.QMLP. DEVINIT is restored, as is start_queues.com.

• If this is the first installation under the given $NSTDIR, then the $CSTDIR is set up.
• The build is installed from CD. It is linked to $TOPDIR/live to become the live build. A subtree for the build is created in $CSTDIR
• If the platform supports multiple database systems, and if the operator indicated in the interview that fewer than all are to be installed, then any others are removed from the newly-installed build. This means the $live/exe/$DBTYPE and $live/sql/$DBTYPE directories for each uninstalled database system are removed.

• The license file(s) for any remaining database systems should have been copied to the /tmp directory before running SETUP. If SETUP cannot find them, it stops and prompts for the operator to get the file(s) in place. SETUP will not proceed until a license for each installed database system has been found and retrieved.
• The license file(s) are copied into $CFGDIR, and also to their respective $live/exe/${DBTYPE} directories, where each is renamed to lplicense.dat

• The set_access command is run 3 times, once each for base system, for the build, and for the Queue Manager.
• set_access sets the owner, group and access modes of the files and directories in the list given to it.
• set_access is designed to tolerate a certain number of errors, usually 50, before aborting in error. The errors are reported to the screen, but only if they exceed the limit in quantity do these errors affect SETUP.
• There should be zero errors reported. If there are a few, but not enough to cause SETUP to abort, then it is possible that the installation was still successful. However, check with the NetSol Help Desk if any errors are reported during SETUP.

• SETUP creates the Queue Manager temporary directories, $QMTMPDIR/*.
• The Queue Manager spooler directory, $QMSPOOLDIR, is also created at this time.

• The program cfg_gen is then run. This program takes the relscfg.msirc created by the SETUP interview, the extended VERSION file now in $BOOTDIR/version.msirc, plus the templates in $live/lib/*.mtx and creates 3 files. These files define essentially the entire LeasePak release instance.
• The first file is ${HOST}_v62a_rt.msirc, and it contains setenv commands to build up the environment. When a LeasePak user logs into the Application host, this file is executed via the user's .lplogin or .lpprofile start-up file, and then that session is fully LeasePak enabled.
• The second file is ${HOST}_v62a_rt.lpkd, and it contains simple assignments that can be interpreted by leasepakd and mPowerd. When a LeasePak user logs into the Application host through the LeasePak Windows Client, this file is executed to ensure that the user environent is fully setup.
• The third file is ${HOST}_v62a_rt.com and it contains assignments to the environment in the Queue Manager DCL scripting language. It is executed at the beginning of every EOP batch job to ensure that the environment is fully configured before running the EOP driver.

• With the completion of the configuration generation, the release instance can now be registered in the /etc/netsol.conf registry. At this time, this file only associates the instance ID of the LeasePak instance with the top directory and thus also the release version of LeasePak.

• Next the program lp_sys_install is run. It is in charge of setting up the services requested by the operator via the interview. lp_sys_install does not start any of the init services; it only installs them.
• It sets up the Queue Manager init service, nst_qm_${INST_ID}62a, if requested.
• It sets up the Sybase init service, nst_dbsyb, if requested.
• It sets up the Oracle init service, nst_dbora, if requested.
• It sets up the leasepakd internet service nst_lp62a${INST_ID}_$LEASEPAKD_PORT on the $LEASEPAKD_PORT port.
• It sets up the mpowerd internet service nst_mp62a${INST_ID}_$MPOWERD_PORT on the $MPOWERD_PORT port.

• For each installed database system, do:
  • Oracle - delete any existing $SRVADM, recreate
  • Sybase - create $SRVADM if does not exist

• Find home directories of $NSTADMIN and $NSTDBA
• For each installed database system, do:
  • create adm_${DBTYPE} administrative environment
  • if primary database system, copy .lp* from the newly created environment to the $NSTADMIN and $NSTDBA home directories

• Perform final owner/group/access mode changes