LeasePak
Server Preparation and Installation
Start here if you are installing LeasePak on your server for the first time. If you have a previous installation of LeasePak, refer to the document LeasePak Server Upgrade and Conversion for procedures to upgrade or update your LeasePak server and convert LeasePak databases.
Preparation
System Requirements
Review the LeasePak Server section of the document System Requirements before beginning the installation process to ensure your client computer meets the minimum requirements for LeasePak .
Procedure Overview
This is the procedure for installing LeasePak on a server where no previous installation of LeasePak exists. If the server has a previous installation, use the procedure described in LeasePak Server Upgrade and Conversion.
- Create the required groups, users, and directories for LeasePak installation.
- Make the necessary kernel adjustments and other preparations for LeasePak installation.
- Prepare the server using the document specific to your DBMS.
Oracle (all Platforms):
Oracle Server (coming soon)
Sybase (all Platforms):
Sybase 12.x Server
- Use the installation worksheet to note the information you will need during installation.
- Copy the LeasePak license file(s) to the /tmp directory.
- Run the LeasePak setup program.
OS Server Preparation
OS Verification
HP
Use the swlist command to verify that you are running the following version of the operating system:
Linux
Use the uname -a command to verify that you are running the following version of the operating system:
Sun
Use the showrev command to verify that you are running the following version of the operating system:
Groups, Users, Devices, and Directories
Use direct commands or system administration tools to create the following groups, users, devices, and directories.
Groups
| Description | Name (example) | Your Name |
|---|---|---|
| LeasePak users group | msi | |
| DBMS installation group (oracle) | oracle | |
| DBMS installation group (sybase) | sybase |
Users
For more information on users not mentioned here (such as LeasePak client users), refer to LeasePak Users.
| Description | Name (example) | Group (example) | Your Name | Your Group |
|---|---|---|---|---|
| DBMS installation user (oracle) | oracle | oracle | ||
| DBMS installation user (sybase) | sybase | sybase | ||
| MSI release administrator | msiadmin | msi | ||
| MSI database administrator | msidba | msi |
Multiple concurrent versions:
if you are running more than one version of LeasePak on the same server, you must use the appropriate startup files
(such as .lplogin and .lpprofile) with the MSI release administrator for the version you are working in.
For this situation, MSI strongly recommends setting up separate, version-specific MSI release administrator users.
Devices and Directories
Some of the following will already exist within your OS; others you will need to create. Note that many of the DBMS volumes/partitions must be unformatted (raw).
CD-ROM Device
| HP Examples |
Linux Examples |
Sun Examples |
Your Values | |
|---|---|---|---|---|
| Mount Point | /SD-CDROM | /mnt/cdrom | /cdrom | |
| MSI recommends that the CD-ROM device be attached directly to the server (not over a network) to avoid problems where the directory paths might be translated into uppercase. | ||||
Home Directory
| Examples | Your Values | |
|---|---|---|
| Name | /home | |
| Size | 200 MB minimum | |
| The directory is normally standard on the OS. Each LeasePak client user has a directory under /home on the server. For large numbers of LeasePak users, calculate the size based on average number of different reports each user will run and whether or not you will regularly truncate or archive each user's leasepak_error.log file. | ||
Temporary Directory
| Examples/Instructions | Your Values | |
|---|---|---|
| Name | /tmp | |
| Size | 1200 MB minimum |
Sector7 Temporary Directory
| Examples/Instructions | Your Values | |
|---|---|---|
| Name | /tmp/sector7 | |
| Owner:Group | root:sys | |
| Permissions | 755 | |
| The LeasePak setup program creates this directory. | ||
Sector7 Temporary Release Directory
| Examples/Instructions | Your Values | |
|---|---|---|
| Name | /tmp/sector7/ | |
| Owner:Group | msiadmin:msi | |
| Permissions | 777 | |
| The LeasePak setup program creates this directory. | ||
Swap Partition
| Examples/Instructions | Your Values | |
|---|---|---|
| Name | swap | |
| Size | 40 MB for each concurrent LeasePak (lpadriver.exe) connection. | |
| Minimum calculation of physical memory * 3. | ||
LeasePak Server Program Files
LeasePak server, Sector7, and DBMS server program files can reside on the same volume/partition (allow for appropriate space).
| HP Examples |
Linux Examples |
Sun Examples |
Your Values | |
|---|---|---|---|---|
| File System/Mount Point | /opt/msi/ | /opt/msi/ | /opt/msi/ | |
| Owner:Group | msiadmin:msi | msiadmin:msi | msiadmin:msi | |
| Permissions | 750 | 750 | 750 | |
| Size | 1400 MB minimum | 1400 MB minimum | 1400 MB minimum | |
| Physical Location | (separate logical volume) | (separate partition) | (separate volume) | |
| (Logical) Volume Name or Device | msiapps | /dev/hdxn, where x is the drive letter and n is the partition number | msiapps | |
| Type | file system, use HFS (or VxFS for journalling) | file system, use ext2 (or ext3 for journalling) | UFS file system, use mkfs to format |
Sector7 Program Files
LeasePak server, Sector7, and DBMS server program files can reside on the same volume/partition (allow for appropriate space).
| HP Examples |
Linux Examples |
Sun Examples |
Your Values | |
|---|---|---|---|---|
| File System/Mount Point | /opt/sector7 | /opt/sector7 | /opt/sector7 | |
| Owner:Group | msiadmin:msi | msiadmin:msi | msiadmin:msi | |
| Permissions | 750 | 750 | 750 | |
| Size | 300 MB minimum | 300 MB minimum | 300 MB minimum | |
| Physical Location | (separate logical volume) | (separate partition) | (separate volume) | |
| (Logical) Volume Name or Device | sector7 | /dev/hdxn, where x is the drive letter and n is the partition number | sector7 | |
| Type | file system, use HFS (or VxFS for journalling) | file system, use ext2 (or ext3 for journalling) | UFS file system, use mkfs to format | |
| The LeasePak setup program creates a version-specific directory under /opt/sector7/; s7_317 for HP, s7_318 for Linux, or s7_317 for Sun. | ||||
LeasePak and Sector7 directories:
the top and subdirectories of LeasePak and Sector7 must not include:
- hidden directories--that is, directories that begin with a dot or period (.)
- directory names containing a dot or period
- directory names containing uppercase letters
- directories that cross physical drives or mount points.
DBMS Server Program Files
LeasePak server, Sector7, and DBMS server program files can reside on the same volume/partition (allow for appropriate space). You may have both Oracle and Sybase installed; in this case, note your values for both.
| HP Examples |
Linux Examples |
Sun Examples |
Your Values | |
|---|---|---|---|---|
| File System/Mount Point | /opt/oracle or /opt/sybase | /opt/oracle or /opt/sybase | /opt/oracle or /opt/sybase | |
| Owner:Group | dbms:dbms, where dbms is either oracle or sybase | dbms:dbms, where dbms is either oracle or sybase | dbms:dbms, where dbms is either oracle or sybase | |
| Permissions | 750 | 750 | 750 | |
| Size | 600 MB minimum | 600 MB minimum | 600 MB minimum | |
| Physical Location | (separate logical volume) | (separate partition) | (separate volume) | |
| (Logical) Volume Name or Device | oracle or sybase | /dev/hdxn, where x is the drive letter and n is the partition number | oracle or sybase | |
| Type | file system, use HFS (or VxFS for journalling) | file system, use ext2 (or ext3 for journalling) | UFS file system, use mkfs to format | |
| The LeasePak setup program creates a version-specific directory under /opt/sector7; s7_317 for HP, s7_318 for Linux, or s7_317 for Sun. | ||||
Additional Preparation
HP
Kernel Parameters
Use SAM or direct commands to configure the following kernel parameters. After setting the parameters, you must reboot the server to rebuild the kernel.
The parameter values listed are minimum guidelines only. You may need to adjust these values to achieve optimal server performance. If you've already configured the kernel parameters for a previous LeasePak installation, your existing kernel parameters will, in most cases, work.
maxdsiz
| Description | Minimum Value | Your Value |
|---|---|---|
| maximum data segment size for a process executing in memory | 0x08000000 hexidecimal bytes |
maxswapchunks
| Description | Minimum Value | Your Value |
|---|---|---|
| maximum allocated swap space | configured swap space (in megabytes) / 2 * (size of swchunk) |
maxusers
| Description | Minimum Value | Your Value |
|---|---|---|
| resource allocation parameter | 4 * average number of concurrent users |
msgmax
| Description | Minimum Value | Your Value |
|---|---|---|
| maximum size of any single message | 32768 bytes | |
| Configure msgseg, msgmnb, and msgssz first, then set msgmax. Set msgssz to 8 bytes. | ||
msgmnb
| Description | Minimum Value | Your Value |
|---|---|---|
| maximum size of all messages existing simultaneously on a single message queue | 32768 bytes | |
| Configure msgseg, msgmnb, and msgssz first, then set msgmax. Set msgssz to 8 bytes. | ||
msgseg
| Description | Minimum Value | Your Value |
|---|---|---|
| number of message segments available on a single message queue | 4096 segments | |
| Configure msgseg, msgmnb, and msgssz first, then set msgmax. Set msgssz to 8 bytes. | ||
msgssz
| Description | Minimum Value | Your Value |
|---|---|---|
| message segment size | 8 bytes | |
| Configure msgseg, msgmnb, and msgssz first, then set msgmax. Set msgssz to 8 bytes. | ||
nflocks
| Description | Minimum Value | Your Value |
|---|---|---|
| maximum number of available file locks | 2000 file locks |
nproc
| Description | Minimum Value | Your Value |
|---|---|---|
| maximum number of concurrent processes | 20 + (8 * maxusers) |
npty
| Description | Minimum Value | Your Value |
|---|---|---|
| maximum number of available pseudo ttys | 2 * maximum number of concurrent users |
nstrpty
| Description | Minimum Value | Your Value |
|---|---|---|
| maximum number of available streams-based pseudo ttys | 2 * maximum number of concurrent users |
semmnu
| Description | Minimum Value | Your Value |
|---|---|---|
| maximum number of processes with pending undo operations on a semaphore | 60 processes |
swchunk
| Description | Minimum Value | Your Value |
|---|---|---|
| swap chunk size | 2048 kilobytes |
Linux
Other Requirements
Additions to the sudoers File
For the user msiadmin (or your equivalent), log in as root, then make the following entries to the /etc/sudoers file so that msiadmin can properly install LeasePak.
- echo "msiadmin ALL=NOPASSWD:/bin/chown" >> /etc/sudoers
- echo "msiadmin ALL=NOPASSWD:/bin/chgrp" >> /etc/sudoers
- echo "msidba ALL=NOPASSWD:/bin/chown" >> /etc/sudoers
- echo "msidba ALL=NOPASSWD:/bin/chgrp" >> /etc/sudoers
Sun
Kernel Parameters
Edit /etc/system to configure the following kernel parameters. After setting the parameters, you must reboot the server to rebuild the kernel.
The parameter values listed are minimum guidelines only. You may need to adjust these values to achieve optimal server performance. If you've already configured the kernel parameters for a previous LeasePak installation, your existing kernel parameters will, in most cases, work in the new version.
msgsys:msginfo_msgmax
| Description | Minimum Value | Your Value |
|---|---|---|
| maximum size of any single message | 32768 bytes |
msgsys:msginfo_msgmnb
| Description | Minimum Value | Your Value |
|---|---|---|
| number of message segments available on a single message queue | 32768 segments |
rstchown
| Description | Value | |
|---|---|---|
| enable users to chown their own files | 0 |
semsys:seminfo_semume
| Description | Minimum Value | Your Value |
|---|---|---|
| maximum number of processes with pending undo operations on a semaphore | 60 processes |
Installation
Installation Worksheet
Note the following values for installation:
All Platforms
| Description | Example | Your Value |
|---|---|---|
| CD-ROM device (directory path) | (varies; see the OS server document for your platform) | |
| LeasePak release directory | /opt/msi/ | |
| Sector7 release parent directory | /opt/sector7 | |
| DBMS(s) | O for Oracle, S for Sybase, or OS for both. | |
| DBMS server administrator name | srvadm | |
| MSI release administrator name | msiadmin | |
| MSI database administrator name | msidba | |
| MSI group name | msi | |
| TCP port for leasepakd inet daemon |
- LeasePak release directory
- This must already exist in Unix/Linux. The version portion of the path, , is optional.
- Sector7 release parent directory
- This must already exist in Unix/Linux. The installation will create the directory s7_version, where version is 317 for HP, 318 for Linux, and 317 for Sun).
- MSI group name
- This group must already exist in Unix/Linux.
- DBMS server administrator
- The name must not be an existing Unix/Linux or DBMS user. Depending on your DBMS, the setup program will either add this name as a login to Sybase and grant it sa privileges, or add it as a schema to Oracle (using a default tablespace) and grant it sysdba privileges. Refer to the document LeasePak Users for more information on the srvadm user.
- MSI release administrator
- This account must already exist in Unix/Linux. Refer to the document LeasePak Users for more information on the msiadmin user.
- MSI database administrator
- This account must already exist in Unix/Linux. Refer to the document LeasePak Users for more information on the msidba user.
- MSI group name
- This group must already exist in Unix/Linux.
- TCP port
- Port numbers must be greater then 1023 and unique. By convention, MSI matches the first two digits of the port number to the release (hence for version ). This is the 'base port number'. If you have more than one installation of LeasePak on a single server, assign each its own port number (add 10 to the base port number) and name for the leasepakd inet daemon.
- mPower port
- (if applicable) By convention, MSI uses a port number 6 greater than the LeasePak base port number. If you have more than one installation of mPower on a single server, assign each its own port number (add 10 to the base port number, then add 6) and name for the mPowerd inet daemon.
DBMS-Specific
Oracle
| Description | Example | Your Value |
|---|---|---|
Sybase
| Description | Example | Your Value |
|---|---|---|
| Sybase parent directory | either /opt/sybase (HP and Sun) or /opt/sybase (Linux) | |
| dataserver name | SERVER_SYBASE | |
| backup server name | SERVER_BACKUP |
You can find the data and backup
server names in the interfaces file, located under the Sybase parent directory. Be careful when viewing this
file not to change its contents. Use the proper Sybase configuration utilities to change the contents of the
interfaces file. Refer to your Sybase documentation or contact your MSI representative for more information.
Sybase parent directory: this must already exist in Unix/Linux. Refer to the document Sybase 12.x Server for the required configurations.
LeasePak License File
The diskette supplied with your LeasePak CD contains one (or both) of the following license files:
- lplicense.ora (Oracle)
- lplicense.syb (Sybase)
If your diskette contains only one file,
the file lplicense.dat, this is actually a Sybase LeasePak license file. You must rename the file to
lplicense.syb before you begin the installation.
To set up the license file for installation
- Log in as root. If you use su to log in as root, use su -
- Verify that /usr/bin is included in the root user PATH.
- Copy the license file(s) pertaining to the DBMS(s) you are using (either Oracle, Sybase, or both) from the diskette to your server's /tmp directory. If using FTP, transfer the file(s) in binary mode.
- Proceed to the instructions for running the LeasePak setup program.
LeasePak setup Program
The setup program prompts the user for various configurations (as listed in the installation worksheet), then sets up the server according to those configuration and installs the LeasePak server software.
If you have a previous installation of LeasePak on the server and are updating to a new release, you can use one of the following options:
- -b install the new build only (and live will point to the new build)
- -s7 install the new Sector7 only
- -l (the letter l) install the new license only
To run the setup program
- Log in as root. If you use su to log in as root, use su -
- Verify that /usr/bin is included in the root user PATH.
- At the prompt, type cd-rom_device/setup release_directory
where cd-rom_device is the full path of your CD-ROM device and release_directory is the full path of your LeasePak release directory.
HP only: both the cd-rom device
path and setup must be uppercase; for example, /SD_CDROM/SETUP, but remainder of the command
line, including the release directory, must be in lower case.Press Enter.
The terminal will display something similar to the following
setup /opt/msi/: Creating server administrator account(s), 'srvadm', in DBMS(s) syb ... -03-16 14:43:25 db_add_srvadm: Add syb server administrator srvadm -03-16 14:43:26 db_add_srvadm: Running commands as sa DBMS root account 'sa' password: -03-16 14:43:46 db_add_srvadm: syb server administrator already exists -03-16 14:43:46 db_add_srvadm: End# /cdrom/setup /opt/msi/ setup /opt/msi/: Loading setup VERSION file ... setup /opt/msi/: Setting up top dir ... setup /opt/msi/: Loading in base system image ... setup /opt/msi/: Extending /cdrom/VERSION ... setup /opt/msi/: Reading in extended version file ... setup /opt/msi/: Running 'Configure Release' utility ... Configure Release -- Type Ctrl-C at any time to abort operation
- The program will prompt for the following information, one line at time
Parent of Sector7 s7_$S7_VERSION directory [/opt/sector7]: Install Sector7 startup/shutdown in rc1.d/rc3.d? (Y/N) []:Type your values and press Enter or simply press Enter to accept the default values (in brackets). These files perform necessary initialization processes aside from startup and shutdown; consult with your MSI representative before declining to install them here.
DBMS's to support in this release (O=Oracle S=Sybase OS=both):
The following question only appears if OS (both) is selected
Primary DBMS on this server (O=Oracle S=Sybase):The program will then ask you to select a naming convention
Naming convention (S=strict, L=Loose, N=New strict) (S/L/N) []:
Type your values and press Enter.
If you have an existing installation of LeasePak version 5.0a or below, select L for Loose to use old naming conventions on existing data and Loose conventions on new data, or select N for New Strict to use old naming conventions on existing data but Strict conventions on new data.
If you have an existing installation of LeasePak version 5.1a or above, or you are installing LeasePak for the first time, select S to use Strict conventions, select L to use Loose conventions, or select N if you have previously used Loose conventions but want to switch to Strict for new data.
For more information detailing the differences between Loose and Strict conventions, refer to the document Naming Conventions
If you are using Oracle or both Oracle and Sybase, the program will prompt for the following
Path of Oracle home [/opt/oracle/product/9.2.0.1]: Install Oracle startup/shutdown in rc1.d/rc3.d? (Y/N) []: Name of Oracle installation account []: Oracle net service name(s) []: Oracle default tablespace [users]: Oracle NLS_LANG value [American_America.WE8ISO8859P1]:Type your values and press Enter or simply press Enter to accept the default values (in brackets). If you choose not to install Oracle startup/shutdown files in the rc?.d directories, MSI recommends you have some other way of restarting Oracle with the rest of your system. For the 'Name of Oracle installation account', use the Oracle installation user name.
If you are using Sybase or both Oracle and Sybase, the program will prompt for the following
Path of Sybase directory [/opt/sybase]: Install Sybase startup/shutdown in rc1.d/rc3.d? (Y/N) []: Include Sybase backup server in startup/shutdown? (Y/N) []: Sybase Data Server name(s) []: Sybase Backup Server name []: Automatically create Sybase database owner names? (Y/N) []:Type your values and press Enter or simply press Enter to accept the default values (in brackets). These files perform necessary initialization processes aside from startup and shutdown; consult with your MSI representative before declining to install them here. If you answer 'N' to 'Include Sybase backup server in startup/shutdown?', then the program will not ask for the backup server name.
DBMS server administrator name [srvadm]: Use a separate server security officer role? (Y/N) []: DBMS server security officer name [srvso]:Type your values and press Enter or simply press Enter to accept the default values (in brackets). You can choose to include the srvso role in srvadm.
MSI Admin login name [msiadmin]: MSI DBA login name [msidba]: MSI group name [msi]:Type your values and press Enter or simply press Enter to accept the default values (in brackets). If you are running more than one version of LeasePak on the same server, MSI recommends creating version-specific accounts for msiadmin and msidba.
TCP port assignment for leasepakd inet daemon []: Install LeasePak TCP port in inet configuration? (Y/N) []:Type your values and press Enter or simply press Enter to accept the default values (in brackets).
If you are using mPower, the program will also prompt for the following
TCP port assignment for mpowerd inet daemon []: Install MPower TCP port in inet configuration? (Y/N) []:Type your values and press Enter or simply press Enter to accept the default values (in brackets).
- After receiving the configurations, the setup program will display a summary and prompt to rerun the configurations or continue
(the following example is using Sybase DBMS)
Release path: /opt/msi/ Release sequence: 510 Sector7 shared? N New Sector7 path: /opt/sector7//s7_317 Sector7 in Rc? Y DBMS's in use: syb Primary DBMS: syb Naming convention: S Sybase path: /opt/sybase Sybase in Rc? Y Syb bkupsrv in Rc? Y Sybase servers: SERVER_SYBASE Sybase server nm: SERVER_SYBASE Sybase bkp server: SERVER_BACKUP Auto DBO naming: Y DBMS server admin: srvadm Use DBMS SO role? N MSI Admin login: msiadmin MSI DBA login: msidba MSI group: msi Leasepakd Port: Install Port? Y Configuration complete setup /opt/msi/: 'Configure Release' terminated normally Do you wish to [R]erun 'Configure Release' or to [C]ontinue with installation? (R/C): c - Assuming you type "C" and press Enter to continue, the setup program will continue with the installation,
displaying
setup /opt/msi/: Response=c; continuing with installation ... setup /opt/msi/: Loading the release configuration created by 'Configure Release' ... setup /opt/msi/: Installing Sector7 ... setup /opt/msi/: Sector7 installed setup /opt/msi/: Installing build .1338 ... setup /opt/msi/: Build .1338 installed setup /opt/msi/: Attaching build .1338 to live ... setup /opt/msi/: Build attached setup /opt/msi/: Fetch license(s) ...
- At this point, the setup program will look for the license file (either lplicense.ora or
lplicense.syb) in the /tmp directory. If the program can't locate the file,
it will prompt with the following
setup /opt/msi/: Can't find LeasePak license file '/tmp/lplicense.syb'. Do you wish to [C]opy in the license file or to [A]bort installation? (C/A):
- You can either type "a" to abort the installation or "c" to continue. If you continue, the setup program will
prompt
setup /opt/msi/: Response=c; copying license file... Please copy the lplicense.syb from McCue-provided license file diskette into /tmp on this system, and press <Return>.
To continue the installation, copy the license file to the /tmp directory and press Enter.
- The setup program will continue the installation, displaying something similar to the following
setup /opt/msi/: Copying /tmp/lplicense.syb ... setup /opt/msi/: Install license(s) ... setup /opt/msi/: Setting file protections on -03-16 14:38:31 set_access: Start: /opt/msi//boot/base_sys.prot -03-16 14:38:32 set_access: End: /opt/msi//boot/base_sys.prot -03-16 14:38:32 set_access: /opt/msi//boot/base_sys.prot: 32 Item(s); 0 Error(s) setup /opt/msi/: Setting file protections on Build -03-16 14:38:32 set_access: Start: /opt/msi//live/lib/bld.prot -03-16 14:39:38 set_access: End: /opt/msi//live/lib/bld.prot -03-16 14:39:39 set_access: /opt/msi//live/lib/bld.prot: 1405 Item(s); 0 Error(s) setup /opt/msi/: Setting file protections on Sector7 ... setup /opt/msi/: Loading basic shell function libraries ... setup /opt/msi/: Generating common configuration scripts ... Writing runtime msirc file... USEPKG boot v.20 USEPKG unix hpux11 USEPKG syb 12_0 USEPKG dbms v.20 USEPKG s7 3.17 USEPKG lprt v.20 USEPKG vms v.20 USEPKG msi v.20 Writing lpkd file... USEPKG boot v.20 USEPKG unix hpux11 USEPKG syb 12_0 USEPKG dbms v.20 USEPKG s7 3.17 USEPKG lprt v.20 USEPKG vms v.20 USEPKG msi v.20 Writing com file... USEPKG boot v.20 USEPKG unix hpux11 USEPKG syb 12_0 USEPKG dbms v.20 USEPKG s7 3.17 USEPKG lprt v.20 USEPKG vms v.20 USEPKG msi v.20 File generation complete; installing new config files... Installation of config files is complete setup /opt/msi/: Configuration generation is complete setup /opt/msi/: Loading generated settings via boot environment ... - The setup program will create automatic restart files for Sector7 and Sybase in the appropriate init.d
and rc?.d directories
setup /opt/msi/: Performing LeasePak System installation ... Sybase sa account 'sa' password: -03-16 14:17:00 lp_sys_install: Start - YYYY -03-16 14:17:00 lp_sys_install: Working in /etc ... -03-16 14:17:00 lp_sys_install: Install Sector7 startups in rc? Y -03-16 14:17:00 lp_sys_install: Installing Sector7 ... -03-16 14:17:00 lp_sys_install: Creating /etc/init.d/_sector7.que ... -03-16 14:17:01 lp_sys_install: Creating /etc/rc1.d/K10_sector7.que ... -03-16 14:17:01 lp_sys_install: Creating /etc/rc3.d/S90_sector7.que ... -03-16 14:17:01 lp_sys_install: Sector7 complete -03-16 14:17:01 lp_sys_install: Install Oracle 9i startups in rc? Y -03-16 14:17:01 lp_sys_install: Installing Oracle ... -03-16 14:17:01 lp_sys_install: Creating /etc/init.d/dbora9i ... -03-16 14:17:01 lp_sys_install: Creating /etc/rc1.d/K08dbora9i ... -03-16 14:17:02 lp_sys_install: Creating /etc/rc3.d/S85dbora9i ... -03-16 14:17:02 lp_sys_install: * * * Be sure to update /etc/mccue_oracle_instances ($MSI_INSTANCES_LIST) as needed * * * -03-16 14:17:02 lp_sys_install: Oracle complete -03-16 14:17:02 lp_sys_install: Install Sybase 12 startups in rc? Y -03-16 14:17:02 lp_sys_install: Installing Sybase ... -03-16 14:17:02 lp_sys_install: Creating /etc/init.d/sybase12 ... -03-16 14:17:02 lp_sys_install: Creating /etc/rc1.d/K09sybase12 ... -03-16 14:17:02 lp_sys_install: Creating /etc/rc3.d/S84sybase12 ... -03-16 14:17:03 lp_sys_install: Creating shutdown script ... -03-16 14:17:03 lp_sys_install: Shutdown script created; be sure to maintain tight security on the script -03-16 14:17:03 lp_sys_install: Sybase complete -03-16 14:17:04 lp_sys_install: Install leasepakd port in inetd configuration? Y -03-16 14:17:04 lp_sys_install: Installing Inetd config ... -03-16 14:17:04 lp_sys_install: Installing service leasepakd__... -03-16 14:17:04 lp_sys_install: Inetd config complete -03-16 14:17:04 lp_sys_install: End
- The setup program will begin creating the srvadm account and prompt for the
srvadm password
setup /opt/msi/: Creating server administrator account, 'srvadm', in syb DBMS .. setup /opt/msi/: (will abort if the srvadm DBMS account already exists) Server Administrator 'srvadm' password:
Create the srvadm password, type it here, and press Enter. The srvadm account and password must be compatible with all installed DBMSs supported by LeasePak. Echo is turned off, so no characters will appear as the password is typed. The program will prompt to confirm the password.
- The program will then prompt for the appropriate DBMS administrator account password (for Oracle, the
sysdba password; for Sybase, the sa password)
-03-16 18:00:14 db_add_srvadm: Add syb server administrator srvadm
-03-16 18:00:15 db_add_srvadm: Running commands as sa
DBMS root account 'sa' password:
-03-16 18:00:22 db_add_srvadm: End
Type the appropriate password and press Enter. This password must be compatible with its corresponding DBMS. Echo is turned off, so no characters will appear as the password is typed.
- The setup program will create an initial administrative environment for the DBMS and set protections on boot files. This is the
remainder of the setup program
setup /opt/msi/: Creating admin environment for syb DBMS ... -03-16 14:43:47 setup_new_env: -nfc PRODUCTION adm_syb syb PIDGEON_SYBASE non_admsyb_51a live; Start -03-16 14:43:47 setup_new_env: Creating environment directory structure... -03-16 14:43:48 setup_new_env: Creating syb_use... -03-16 14:43:48 setup_new_env: Creating logdb.*... -03-16 14:43:51 setup_new_env: Creating envdb.msirc... -03-16 14:43:52 setup_new_env: Creating msidba placeholder ... -03-16 14:43:52 setup_new_env: Creating .lp*... -03-16 14:43:52 setup_new_env: Setting environment security... -03-16 14:43:53 setup_new_env: End setup /opt/msi/: Setting file protections on bootstrap files ... -03-16 14:43:54 set_boot_prot: Start -03-16 14:43:54 set_boot_prot: Setting protections on miscellaneous boot flies ... -03-16 14:43:56 set_boot_prot: End setup /opt/msi/: setup is finished #
Administrative Environment
The setup program creates an administrative environment, either adm_ora or adm_syb (or both, if applicable), and copies the the files .lplogin and .lpprofile to the home directories of msiadmin and msidba. These adm_* environments are do not contain a database, but do contain the necessary environmental variables to enable access to the DBMS.
Do not create a LeasePak database in the
administrative environment. Refer to the document LeasePak Server
Configuration to create at least one environment and database for use with LeasePak.
The users msiadmin and msidba can no longer use change_env to change their own environments (or each other's). All scripts requiring a specified environment include the environment name as an argument on the command line; you do not need to change the environment of msiadmin or msidba. To perform tasks that do require a user to be within a specific environment (such as End of Period or LeasePak utilities), MSI strongly recommends creating a LeasePak administrative user, by convention referred to as lpadmin. You can create a different lpadmin user for each environment, or log on the server as msiadmin and use change_env to switch lpadmin from one environment to another. For more information on lpadmin, refer to the LeasePak Administrative User section in LeasePak Server Configuration and Maintenance.
Continue the installation with the document
LeasePak Server Configuration and Maintenance.
LeasePak System Administration Guide
©
by McCue Systems Incorporated. All rights reserved.
The information contained in this document is the property of McCue Systems, Inc. Use of the information contained herein is restricted. Conditions of use are subject to change without notice. McCue Systems, Inc. assumes no liability for any inaccuracy that may appear in this document; the contents of this document do not constitute a promise or warranty. The software described in this document is furnished under license and may be used or copied only in accordance with the terms of said license. Unauthorized use, alteration, or reproduction of this document without the written consent of McCue Systems, Inc. is prohibited.