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 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 9i (all Platforms):
Oracle 9i Server
Sybase (all Platforms):
Sybase 12.5.4 Server
- Use the installation worksheet to note the information you will need during installation.
- Copy the LeasePak license file(s) to the
/tmpdirectory.
- Run the LeasePak
SETUPprogram.
OS Server Preparation
OS Verification
HP
Use the swlist command to verify that you are running the following version of the
operating system:
- HP-UX B.11.11
Linux
Use the uname -a command to verify that you are running the following version of the
operating system:
- Linux 2.6.x
Sun
Use the showrev command to verify that you are running the following version of the
operating system:
- SunOS 5.9
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 | |
| Oracle DBMS primary installation group | orainv | |
| Oracle DBMS secondary installation group | oradba | |
| Sybase DBMS installation group | sybase |
Linux users: your primary group must be
the msi group for all LeasePak users. By default, Red Hat will create an individual group for each user; you must
either turn this feature off before creating users or later change the primary group of users to the msi group.
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 |
|---|---|---|---|---|
| Oracle DBMS installation user | oracle | orainv (primary group) oradba (secondary group) | ||
| Sybase DBMS installation user | sybase | sybase | ||
| MSI release administrator | msiadm | 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).
MSI is integrating Sector7 into our Queue Manager. During this process, you may encounter instances of both
sector7 or s7 and the new qm in folder and file names.
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 |
LeasePak Queue Manager Temporary Directory
| Examples/Instructions | Your Values | |
|---|---|---|
| Name | /tmp/qm | |
| Owner:Group | root:sys | |
| Permissions | 755 | |
| The LeasePak setup program creates this directory. | ||
LeasePak Queue Manager Temporary Release Directory
| Examples/Instructions | Your Values | |
|---|---|---|
| Name | /tmp/qm/ | |
| Owner:Group | msiadm: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, LeasePak queue manager, 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 | msiadm:msi | msiadm:msi | msiadm: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 journaling) | file system, use ext3 | UFS file system, use mkfs to format |
LeasePak Queue Manager Program Files
LeasePak server, LeasePak queue manager, 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/qm | /opt/qm | /opt/qm | |
| Owner:Group | msiadm:msi | msiadm:msi | msiadm: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 | qmgr | /dev/hdxn, where x is the drive letter and n is the partition number | qmgr | |
| Type | file system, use HFS (or VxFS for journaling) | file system, use ext3 | UFS file system, use mkfs to format | |
The LeasePak setup program creates a version-specific directory under
/opt/qm;
/qm_3_17 for HP, /qm_3_19 for Linux, or /qm_3_17 for Sun. | ||||
LeasePak and queue manager directories:
the top and subdirectories of LeasePak and the queue manager 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.
Oracle DBMS Server Program Files
LeasePak server, LeasePak queue manager, 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 | /opt/oracle | /opt/oracle | |
| Owner:Group | oracle:orainv | oracle:orainv | oracle:orainv | |
| Permissions | 755 | 755 | 755 | |
| Size | 3.5 GB minimum for /opt/oracle | 3.5 GB minimum for /opt/oracle | 3.5 GB minimum for /opt/oracle | |
| Physical Location | Separate logical volume | Separate partition | Separate volume | |
| (Logical) Volume Name or Device | oracle | /dev/hdxn, where x is the drive letter and n is the partition number | oracle | |
| Type | File system, use HFS | File system, use ext3 | UFS file system, use mkfs to format |
Sybase DBMS Server Program Files
LeasePak server, LeasePak queue manager, 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/sybase | /opt/sybase | /opt/sybase | |
| Owner:Group | sybase:sybase | sybase:sybase | sybase:sybase | |
| Permissions | 755 | 755 | 755 | |
| Size | 2048 MB minimum for /opt/sybase | 2048 MB minimum for /opt/sybase | 2048 MB minimum for /opt/sybase | |
| Physical Location | Separate logical volume | Separate partition | Separate volume | |
| (Logical) Volume Name or Device | sybase | /dev/hdxn, where x is the drive letter and n is the partition number | sybase | |
| Type | File system, use HFS | File system, use ext3 | UFS file system, use mkfs to format |
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 |
For the following parameters, configure msgseg, msgmnb, and msgssz first,
then set msgmax.
msgseg
| Description | Minimum Value | Your Value |
|---|---|---|
| number of message segments available on a single message queue | 4096 segments |
msgmnb
| Description | Minimum Value | Your Value |
|---|---|---|
| maximum size of all messages existing simultaneously on a single message queue | 32768 bytes |
msgssz
| Description | Minimum Value | Your Value |
|---|---|---|
| message segment size | 8 bytes |
msgmax
| Description | Minimum Value | Your Value |
|---|---|---|
| maximum size of any single message | 32768 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 msiadm (or your equivalent), log in as root,
then make the following entries to the /etc/sudoers file so that
msiadm can properly install LeasePak.
- echo "msiadm ALL=NOPASSWD:/bin/chown" >> /etc/sudoers
- echo "msiadm 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 |
|---|---|---|
| maximum number of bytes on a single message queue | 32768 bytes |
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
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 usesuto log in asroot, usesu - - Verify that
/usr/binis 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
/tmpdirectory. If using FTP, transfer the file(s) in binary mode. - Proceed to the instructions for running the LeasePak
SETUPprogram.
LeasePak SETUP Program
The SETUP program prompts the user for various configurations, then sets up the server according to those configuration
and installs the LeasePak server software.
SETUP Options
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:
-binstall the new build only (and live will point to the new build)-s7install the new LeasePak queue manager only-l(the letter l) install the new license only
Release Configurations
Read through all of the following release configuration questions
before running the SETUP program. Note that although the order of the questions is always the same, the numbering of the sections
and the inclusion of certain questions are dynamic and will vary according to your selections. Also note that during the actual SETUP program,
the questions will be interspersed with output from the program. Use the links following the release configuration questions to view samples of the
SETUP program output.
| 1. Server Name
The LeasePak release directory, or $TOPDIR, must end in the LeasePak release version--for example, SETUP, you must supply the full path of $TOPDIR, but the final component does not need to exist. The recommended path is /opt/msi/. Only /opt/msi needs to exist prior to installation--SETUP will create the You must run SETUP as root, and you should not have any environment variables set for any version of LeasePak. Login directly as root or use su – to switch user to root. You may be able to install directly on top of an existing LeasePak installation, but MSI does not support this as it may result in installation or runtime failures.
|
| Name of the LeasePak Application Server [yoursrvr]:
Usually this is the hostname, which in turn is usually the node name. The hostname is available through the hostname command. The node name is available through the uname –n command. They can be different, but MSI does not guarantee LeasePak to work if they are. For LeasePak, MSI usually uses uname –n, but may in some cases (particularly when dealing with a network) use hostname instead.
This can also be the cluster name. Some LeasePak sites operate their servers in a cluster, enabling them to perform fail-overs if needed. The disk array is shared between the main server and the backup/fail-over server. Thus, the configuration files in $CFGDIR, which are named with the application server name, no longer match the server during a fail-over. For this reason, if the cluster name is used instead, then users logging on to the fail-over server will find themselves still running the same configuration from the disk array. |
| Path of End User Customized Code directory [/opt/msi/cst]:
This should be within the msi software area of the filesystem, but not within a LeasePak release directory (that is, not under $TOPDIR). MSI recommends /opt/msi/cst. The directory and path must exist before installation. Whenever a LeasePak build links to the system, the program creates a subdirectory of /opt/msi/cst ($CSTDIR) with the name of the build’s sequence number--for example, 6.00.2142. Within the build-specific directory, the program creates a cql and prg directory. Within cql, the program creates a directory for each installed DBMS, ora and/or syb. Although each release can have its own $CSTDIR, MSI recommends having only one.
|
| 2. Queue Manager
|
| Parent of Queue Mgr /qm_3_17 directory [/opt/qm]:
This is the directory that holds the release's LeasePak Queue Manager directories. MSI recommends /opt/qm. For users already on the OS/DBMS platform architecture introduced in 6.0a, they may already have a Sector7 directory (/opt/sector7) in place. MSI now supports a symbolic link as long as it links to an actual directory. Therefore, you can make /opt/qm as a link pointing to /opt/sector7. Only this parent directory must exist before installation; SETUP will create the remaining components. If SETUP finds a copy of the Queue Manager package already installed, it removes that installation and replaces it with the shipped package.
|
| Install Queue Mgr startup/shutdown in rc1.d/rc3.d? (Y/N) [Y]:
MSI recommends Y, which causes the program to create the file qmgr_ in /etc/init.d (or /sbin/init.d) with corresponding links from rc1.d and rc3.d. Each install of the same LeasePak release where the user answers Y to this question overwrites the previous init.d information, even if the user is installing different instances of the same LeasePak release, so that only the queues from the most recent install restart automatically on reboot.
|
| 3. DBMS configuration
LeasePak runs on two DBMSs; Oracle and Sybase. However, only two of the platforms--Linux and Sun Solaris--support both together. The first two questions in this section only appear if the user is running LeasePak on a Linux or Solaris platform. If you are on a Linux or Solaris platform and answer OS (meaning both DBMSs) to the first question, the SETUP program will then ask you the second question. You can pick either DBMS as the primary one; the $MSIADMIN and $MSIDBA accounts will point to the primary DBMS.
|
| DBMS's to support in this release (O=Oracle S=Sybase OS=both):
Running both Oracle and Sybase on the same Solaris server requires extensive amounts of memory. Contact your MSI representative for more information if you are considering this option. |
| Primary DBMS on this server (O=Oracle S=Sybase) [S]:
If you have installed both the Oracle and Sybase DBMS, you must select one to be primary. The $MSIADMIN and $MSIDBA accounts point to the primary DBMS by default.
|
| Naming convention (S=strict, L=Loose, N=New strict) (S/L/N) [S]:
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. In this case, MSI recommends selecting N for New Strict.
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. In this case, MSI recommends selecting S for Strict.
For more information, refer to the Naming Conventions document. |
| 4. Oracle configuration
The questions in this section only appear if you have selected either Oracle or both Oracle and Sybase as your DBMS. |
| Path of Oracle home [/opt/oracle/product/9.2]:
Oracle requires the variable ORACLE_HOME, which represents the location where the Oracle software was installed. This path must exist before running SETUP. MSI recommends using /opt/oracle/product. Within this directory, you should have a separate directory for each major release of Oracle. In this case, the directory would be 9.2 for 9i, so /opt/oracle/product/9.2 would be the full path.
|
| Install Oracle startup/shutdown in rc1.d/rc3.d? (Y/N) [Y]:
MSI recommends Y, which causes the program to install the file dbora9i in /etc/init.d (or /sbin/init.d) with corresponding links from rc1.d and rc3.d. SETUP also installs a file named /etc/mccue_oracle_instances, which must contain an assignment to the variable MSI_INSTANCES. This variable should have as its value all of the Oracle instances to be started on the server on reboot. The file dbora9i will not start or stop anything until mccue_oracle_instances is set up. These instances are defined by their ORACLE_SIDs. MSI recommends only one instance--called lpak--for each server.
|
| Name of Oracle installation account [oracle]:
This is the user account name used to install Oracle on the server. MSI recommends oracle. This must already exist prior to running SETUP. Refer to the documents LeasePak Server Preparation and Installation and Oracle Server for more information on this user account and its corresponding groups.
|
| Oracle net service name(s) [YOURSRVR_ORACLE]:
These are the names you will need to locate your Oracle instances on the network. These are not instance or service names. These names must be in the file $ORACLE_HOME/network/admin/tnsnames.ora and must have the following format:
YOURSERVER_ORACLE =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = yourserver)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = lpak.yourserver.yourcompany.com)
)
)
The service name is the machine name in the form of a URL and includes the instance name. MSI recommends that they users use YOURSERVER_ORACLE as the net service name. This is referred to in LeasePak as the 'Oracle server.' Multiple servers can be listed here; the first is the primary server which $MSIADMIN and $MSIDBA will point to by default (if Oracle is your primary DBMS). The Oracle OCI must be able to take this name and resolve it to a machine and port to find the instance you want to use.
|
| Oracle default tablespace [users]:
In Oracle, every user is a schema. This means that every user has, in theory, a place in the Oracle database to create database objects. In the case of LeasePak and LeasePak users, however, db_add_login assigns the user to the tablespace you designate here. LeasePak users have no quota on this tablespace, so they cannot create database objects. Instead, they use the objects belonging to the LeasePak logical database owner’s schema--what in LeasePak is known as the 'LeasePak database.' MSI recommends calling the default tablespace users. Usually Oracle creates this tablespace during installation. This tablespace (or the one you choose as the default tablespace) must exist before db_add_login can assign users to it.
|
| Oracle NLS_LANG value [American_America.WE8ISO8859P1]:
This determines the locale (language, monetary, and measurement conventions) under which LeasePak runs from the Oracle perspective. American_America.WEISO8859P1 is American English. This corresponds to the ISO-8859-1 character set, which includes the traditional ASCII characters along with additional characters for Latin alphabet-based European languages. This is not the same as the UTF-8, UTF-16, or Unicode character sets--MSI does not support these. MSI recommends the following values for servers running in the United States, depending on your platform: HP-UX: en_US.iso88591 Linux: en_US (ASCII character set) Solaris: en_US.ISO8859-1 |
| 5. Sybase configuration
The questions in this section only appear if you have selected either Sybase or both Oracle and Sybase as your DBMS. |
| Path of Sybase directory [/opt/sybase]:
Sybase requires the variable SYBASE, which represents the location where the Sybase software was installed. This path must exist before running SETUP. MSI recommends using /opt/sybase. The current Sybase releases create version-specific directories under this path as needed, so MSI strongly recommends that you do not attempt to do this yourself.
|
| Install Sybase startup/shutdown in rc1.d/rc3.d? (Y/N) [Y]:
MSI recommends Y, which causes the program to install the file sybase12.5 in /etc/init.d (or /sbin/init.d) with corresponding links from rc1.d and rc3.d.
|
| Include Sybase backup server in startup/shutdown? (Y/N) [Y]:
MSI recommends that the user configure a Sybase backup server. If you have configured this, MSI recommends answering Y, which includes the backup server in the /etc/init.d (or /sbin/init.d) configuration.
|
| Sybase Data Server name(s) [YOURSRVR_SYBASE]:
This is a list of dataservers that the user wants for LeasePak databases. All dataservers must all be in the interfaces file in $SYBASE. MSI recommends that the dataserver name be YOURSERVER_SYBASE. The first dataserver in the list is set as the primary dataserver which $MSIADMIN and $MSIDBA will point to by default (if Sybase is your primary DBMS), and LeasePak refers to this one as 'the server.'
|
| Sybase Backup Server name [YOURSRVR_BACKUP]:
You will only see this question if your answer to Include Sybase backup server in startup/shutdown? is Y. MSI recommends that you use YOURSERVER_BACKUP as the backup server name.
|
| Automatically create Sybase database owner names? (Y/N) [Y]:
MSI recommends Y, which directs the LeasePak server to create a DBO for each database using the same name as the database itself. This allows LeasePak to treat the two DBMSs (Oracle and Sybase) identically as far as the security model is concerned.
|
| 6. Required Leasepak & DBMS roles
|
| DBMS server administrator name [srvadm]:
Each DBMS has a user who has sufficient privileges to do the three things needed for LeasePak: create new user accounts, allocate space for LeasePak logical databases, and deallocate LeasePak logical databases. MSI recommends this user name be srvadm and that there be only one for each server. The user never uses this role directly for LeasePak operations or processing. If you have installed both Oracle and Sybase, the LeasePak server will use same name and the same password. This name cannot be an actual UNIX account name, and you cannot use this name as a database owner. This name cannot take on the privileges it grants to database owners, so cannot actually use a LeasePak logical database.
|
| MSI Admin login name [msiadm]:
MSI strongly recommends that you set up a new $MSIADMIN account for each LeasePak release. This account should never use a LeasePak database or run programs in LeasePak. Instead, this account exists to administer UNIX tasks on the LeasePak server. MSI recommends using msiadm. If you choose a different value, MSI recommends that it include the release number. In LeasePak documentation, this account is designated as either msiadmin or $MSIADMIN.
|
| MSI DBA login name [msidba]:
MSI strongly recommends that you set up a new $MSIDBA account for each LeasePak release. This account should never use a LeasePak database or run programs in LeasePak. Instead, this account exists to administer DBMS tasks on the LeasePak server. MSI recommends using msidba. If you choose a different value, MSI recommends that it include the release number. In LeasePak documentation, this account is designated as either msidba or $MSIDBA.
|
| MSI group name [msi]:
All LeasePak users, including the special $MSIADMIN and $MSIDBA users, must have as their primary group the one specified here. When setting up users on the Linux platform, take special care that LeasePak users have this group as their primary group, as Linux will assign each user to its own individual group by default. MSI recommends using the name msi for this group.
|
| 7. Leasepakd daemon configuration
LeasePak uses two inet-managed 'listener' daemons in addition to those used by the DBMSs. One is leasepakd, used by the traditional LeasePak interface. The other is mpowerd, used by the user-configurable, Web-service interfaces such as ChannelIT, which is part of the mPower Web-based technology platform.
|
| TCP port assignment for leasepakd inet daemon [6000]:
The leasepakd daemon setup is mandatory, and it requires a dedicated port on the server. MSI normally uses the LeasePak release version number to determine the port number. In this case, corresponds to port 6000. MSI recommends this numbering method but it is not required. If SETUP finds an identical daemon configured in the inetd configuration, it replaces the configured daemon with a new one. Otherwise it creates a new one and insists that the configuration be given a non-conflicting port number. The service name is leasepakd_leasepak_version_port. If the default number or the number that you choose is already in use, pick a higher number.
|
| Max bad logins before lockout (0=disabled) [0]:
This is the maximum number of failed logon attempts that LeasePak will allow before locking a user out. For example, if you set this to 3, LeasePak will allow the user to mistype the logon (the user name, password, or both) 3 times. If the user correctly types the logon on the fourth attempt, no lockout occurs. But if the user again mistypes the logon on the fourth attempt, LeasePak locks the user out. Set this to 0 to disable this feature, meaning no user will every be locked out, regardless of the number of failed attempts. To see a server-side procedure for unlocking an account, refer to the Housekeeping section of the System Administration Guide document LeasePak Server Configuration and Maintenance.
|
| Install LeasePak TCP port in inet configuration? (Y/N) [Y]:
Answer Y unless you are testing the installation process (and do not intend to use the Leasepak resulting from the installation). If you do not install the TCP port in the inet configuration, LeasePak will not function. For HP-UX and Solaris, SETUP makes an entry in /etc/services and in /etc/inetd.conf. For Linux, SETUP creates a file in /etc/xinetd.d using the service name.
|
| 8. mPowerd daemon configuration
|
| Install mPowerd daemon (Y/N) [N]:
If your license includes ChannelIT (the Web Application Entry module), you must answer Y. If you answer N, you will not see the remaining questions in this section.
|
| TCP port assignment for mPowerd inet daemon [6006]:
If your license includes ChannelIT (the Web Application Entry module), the mpowerd daemon setup is mandatory, and it requires a dedicated port on the server. MSI normally uses the LeasePak release version number to determine the port number. In this case, corresponds to port 6006, by convention 6 more than the leasepakd port number. MSI recommends this numbering method but it is not required. If SETUP finds an identical daemon configured in the inetd configuration, it replaces the configured daemon with a new one. Otherwise it creates a new one and insists that the configuration be given a non-conflicting port number. The service name is mpowerd_leasepak_version_port. If the default number or the number that you choose is already in use, pick a higher number.
|
| Max bad logins before lockout (0=disabled) [0]:
This is the maximum number of failed logon attempts that ChannelIT will allow before locking a user out. For example, if you set this to 3, ChannelIT will allow the user to mistype the logon (the user name, password, or both) 3 times. If the user correctly types the logon on the fourth attempt, no lockout occurs. But if the user again mistypes the logon on the fourth attempt, ChannelIT locks the user out. Set this to 0 to disable this feature, meaning no user will every be locked out, regardless of the number of failed attempts. To see a server-side procedure for unlocking an account, refer to the Housekeeping section of the System Administration Guide document LeasePak Server Configuration and Maintenance.
|
| Install mPower TCP port in inet configuration? (Y/N) [Y]:
Answer Y unless you are testing the installation process (and do not intend to use the ChannelIT resulting from the installation). If you do not install the TCP port in the inet configuration, ChannelIT will not function. For HP-UX and Solaris, SETUP makes an entry in /etc/services and in /etc/inetd.conf. For Linux, SETUP creates a file in /etc/xinetd.d using the service name.
|
SETUP Sample Output
The following are SETUP outputs showing samples with both Oracle and Sybase configurations. Both are text documents that open in new windows.
Running SETUP
To run the SETUP program
- Log in as
root. If you usesuto log in asroot, usesu - - Verify that
/usr/binis included in the root user PATH. - At the prompt, type
cd-rom_device/setup release_directorywhere 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 SETUPmust be uppercase; for example,/SD_CDROM/SETUP, but remainder of the command line, including the release directory, must be in lower case.Press Enter to start the program.
Failed Login/Bad Password Message for Oracle srvadm
Oracle users: if you are able to create the srvadm account during
SETUP, yet receive failed login/bad password messages when you attempt to log on, check the following parameter in the init.ora file:
REMOTE_LOGIN_PASSWORDFILE = EXCLUSIVE
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
msiadm 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 msiadm 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
msiadm 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 (this avoids having to use
change_env), or log on the server as msiadm 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 Documentation Suite
©
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.