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
  • Procedure Overview
  • OS Server Preparation
  • DBMS Server Preparation

• Installation
  • LeasePak License File
  • LeasePak SETUP Program
  • LeasePak Environments and Databases
  • LeasePak User Accounts
  • LeasePak Queue Manager
  • Registration Codes

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.

1. Create the required groups, users, and directories for LeasePak installation.

2. Make the necessary kernel adjustments and other preparations for LeasePak installation.

3. 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

4. Copy the LeasePak license file(s) to the /tmp directory.

5. 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:

• 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

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.

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 LeasePak release administrator for the version you are working in. For this situation, NetSol strongly recommends setting up separate, version-specific LeasePak 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).

NetSol 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
NetSol 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

Temporary Directory

LeasePak Queue Manager Temporary Directory

LeasePak Queue Manager Temporary Release Directory

Swap Partition

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.

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
• Linux
• Sun

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

maxswapchunks

maxusers

For the following parameters, configure msgseg, msgmnb, and msgssz first, then set msgmax.

msgseg

msgmnb

msgssz

msgmax

nflocks

nproc

npty

nstrpty

semmnu

swchunk

Linux

Other Requirements

My.sql /usr/bin/isql

Linux users: RedHat installs My.sql by default, including the executable /usr/bin/isql. Shell scripts naturally find /usr/bin before finding the correct Sybase path. This will cause errors in any LeasePak shell script using isql. Allowing a default installation of My.sql on a LeasePak server is inherently incompatible with the operation of Sybase. NetSol strongly recommmends not installing My.sql on the LeasePak server. Where My.sql is installed alongside Sybase, users must remove, rename, or relocate /usr/bin/isql so that LeasePak shell scripts will not find it when searching for the Sybase isql.

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

msgsys:msginfo_msgmnb

rstchown

semsys:seminfo_semume

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

1. Log in as root. If you use su to log in as root, use  su -
2. Verify that /usr/bin is included in the root user PATH.
3. 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.
4. Proceed to the instructions for running the LeasePak SETUP program.

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:

• -b    install the new build only (and live will point to the new build)
• -s7    install 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.

YOURSERVER_ORACLE =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = yourserver)(PORT = 1521))
    )
    (CONNECT_DATA =
      (SERVICE_NAME = lpak.yourserver.yourcompany.com)
    )
  )
		

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.

• SETUP output with Oracle configurations
• SETUP output with Sybase configurations

Running SETUP

To run the SETUP program

1. Log in as root. If you use su to log in as root, use  su -
2. Verify that /usr/bin is included in the root user PATH.
3. 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 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), NetSol strongly recommends creating a LeasePak supervisor user, by convention referred to as lpsuper. You can create a different lpsuper user for each environment (this avoids having to use change_env), or log on the server as msiadm and use change_env to switch lpsuper from one environment to another. For more information on lpsuper, refer to the LeasePak Supervisor User section in LeasePak Server Configuration and Maintenance.

LeasePak Environments and Databases

setup_new_env

Use setup_new_env to create new production, test, and visitor environments.

Common Usage

The following are the two most common examples of using setup_new_env:

Production Environments

setup_new_env env-name db-type db-server db-name

where env-name is the environment the new database will be associated with, db-type is either ora for Oracle or syb for Sybase, db-server is the the DBMS server, and db-name is the database name.

Test Environments

setup_new_env -tl env-name db-type db-server db-name build-descriptor

(the options are the letters t and l for test environments), where build-descriptor is either live, host, or an actual build number bldn.nn.nnnn (for example, bld.0000).

Multiple concurrent versions: if you have more than one version of LeasePak installed on the same server, note that database names must be unique for the entire server, not just the individual versions of LeasePak.

setup_new_env Worksheet

Note the following values for running setup_new_env:

Running setup_new_env

1. Log on the server as msiadmin

   Terminal emulation: you must use one of the supported terminal types. Refer to the System Requirements for more information.

2. Either run setup_new_env with the common usage described above, or click here to see the complete syntax of setup_new_env (opens in a new window).
3. The server will display something similar to the following:

   	2007-07-25 11:42:11 setup_new_env:  PRODUCTION doctest ora HUMMER_ORACLE lpr_doctest live; Start
   	2007-07-25 11:42:12 setup_new_env: Creating environment directory structure...
   	2007-07-25 11:42:19 setup_new_env: Creating logdb.*...
   	2007-07-25 11:42:46 setup_new_env: Creating envdb.msirc...
   	2007-07-25 11:42:52 setup_new_env: Creating msidba placeholder ...
   	2007-07-25 11:42:52 setup_new_env: Creating .lp*...
   	2007-07-25 11:42:56 setup_new_env: Setting environment security...
   	
   	You will need the following for Leasepak PC Client setup:
   	IP Address or name: hummer
   	Environment name:   doctest
   	Server Port:        6011
   	
   	2007-07-25 11:42:58 setup_new_env: End
   		

db_create

Use db_create to create a new LeasePak database for a particular environment.

Do not create a database in the administrative environment (adm_ora or adm_syb).

Common Usage

The following is the most common example of using db_create:

db_create env-name

where env-name is the environment the new database will be associated with. You will be prompted for the srvadm password and, if necessary, the dbo password.

Sybase only: for more information on dbo names and passwords, refer to the Database Owner section of Sybase 12.x Server.

Running db_create

1. Log on the server as msidba

   Terminal emulation: you must use one of the supported terminal types. Refer to the System Requirements for more information.

2. Either run setup_new_env with the common usage described above, or click here to see the complete syntax of setup_new_env (opens in a new window).

Database Configuration

Oracle

Oracle users: db_create will display a list of storage segments with available space. For example:

2007-07-25 11:51:01 db_setup_phys: Set up physical storage description for (doctest)lpr_doctest

Storage segments with available space:
		LPCOMMON

The script will prompt you for the segment name and database size:

[<RET>/Q/q]=quit  [R/r]=redisplay list  [V/v]=view physdb.msirc
Enter Segment name from list above: 
 Enter # MBs required from segment: 

Type a value for the segment and press Enter. Specify sizes in megabytes. In most cases, LeasePak requires approximately 60 K for each lease, plus an additional 30% for log files (this percentage will decrease for larger databases).

The script will then proceed to build the database.

Sybase

Sybase users: db_create will display a list of storage segments with available space. For example:

2007-07-25 13:10:06 db_setup_phys: Set up physical storage description for (doctest)lpr_doctest

Storage segments with available space:
		   msi_log01   1145                       msi_data04   3245
		   msi_log02   3210                       msi_data05   3420
		   msi_log03   3210                       msi_data06   3919
		  msi_data01   470                        msi_data07   3720
		  msi_data02   2126                       msi_data08   3520
		  msi_data03   3620                       msi_data09   3520

The script will prompt you to specifiy a data segment and a log segment:

[<RET>/Q/q]=quit  [R/r]=redisplay list  [V/v]=view physdb.msirc
Enter Segment name from list above: 
 Enter # MBs required from segment: 
 Segment type: 'D[ATA]' or 'L[OG]': 

You will need to repeat this process twice--once for the data ('D') segment and once for the log ('L') segment.

Type values for the data and log segments and press Enter. Specify sizes in megabytes. For the data segment, LeasePak usually requires approximately 60 K for each lease. The size of the log segment should be approximately 30% of the data segment (this percentage will decrease for larger databases).

Use different devices for the data and log segments. Do not create data or log segments on any device used by the DBMS for its system databases, schemas, or tables.

The script will then proceed to build the database.

Sybase only: the script creates a database with the "truncate log on checkpoint" option enabled. This will clean transaction logs generated each time an automatic checkpoint is performed. For production databases, disable the Sybase "truncate log on checkpoint" option so that the entire transaction log is available for recovery in the event of a system failure between full backups. You can always manually clean out the transaction log as needed. Refer to your Sybase documentation for more information or contact your NetSol representative.

Loading Data

After creating a new database, you will need to either load your data--or at the very least the seed dataset--prior to using the database in LeasePak. To load data:

1. Log on the server as msiadmin

   Terminal emulation: you must use one of the supported terminal types. Refer to the System Requirements for more information.

2. Run the following:

   db_restore environment-name dataset [dbo-password]

   where environment-name is the environment of the database you are loading and dataset is the name of the dataset to use. You can either enter the dbo password on the command line or wait for the script to prompt you for it.

Running db_restore clears all existing data from the database and replaces it with the dataset.

LeasePak User Accounts

For information on LeasePak OS and DBMS server roles and other types of users (such as mPower users), refer to LeasePak Roles and Users.

LeasePak Release Administrator and LeasePak Database Administrator

During installation, the SETUP script, with user input, creates the release administrator ($MSIADMIN, by default msiadm) and database administrator ($MSIDBA, by default msidba) accounts.

For most LeasePak administrative scripts (such as setup_new_env, upgrade_env, db_create, db_snapshot, and db_restore), you will need to log on the LeasePak server as either the $MSIADMIN or $MSIDBA user, depending on the script. Environment-related and general housekeeping scripts usually require the $MSIADMIN user, while database-related scripts usually require the $MSIDBA user.

These are highly specialized accounts. Their environment variables should always point to the administrative environment (adm_ora and/or adm_syb) where SETUP initially placed them. Do not change the environment for either of these accounts or set either of them up as LeasePak users.

LeasePak User Types

The steps for setting up the types of users listed below are detailed in Account Setup Steps.

Administrative User

For each environment you create within your LeasePak installation, NetSol recommends that you have a separate administrative user. You will need at least one user of this type, even if you decide to share it among environments. This is a user that can log on the LeasePak client, server, and DBMS to perform advanced LeasePak operational tasks such as End of Period administration, submission of LeasePak batch jobs, tasks within LeasePak Utilities, and user security through Security [U0706]. NetSol refers to this user as the LeasePak supervisor user, by convention lpsuper_env-name, where env-name is the name of the environment. The following are the basic steps for setting up this type of user:

1. Select a LeasePak user name and an initial client string password for the user. The string must be between 6 and 8 characters in length and conform to your company's password policies. The user lpsuper can change this client string (and the translated passwords with it) later through the LeasePak client Change Password function.
2. Use LeasePak Utility 112 Unix and SQL Server password translation to determine the translated server and DBMS server passwords based on the client string.
3. Create a OS server account for the user. The user name must be the same as the LeasePak user name, the primary group must be the LeasePak users' group (msi), and the password must be the translated OS server password.
4. Copy the .lplogin and .lpprofile files from the appropriate environment's $top/env/env-name/etc directory to the user's home directory.
5. Modify the user's .login and .profile files to include .lplogin and .lpprofile, or use the sample.login and sample.profile files located in the $top/env/env-name/lib directory.
6. Create a DBMS server account for the user. The user name must be the same as the LeasePak user name, and the password must be the translated DBMS server password.
7. Add the user to the appropriate LeasePak database.
8. Use LeasePak Utility 108 Add user security record to add a LeasePak security record for the user.

Do not use LeasePak Utility 108 Add user security record to add any user to the LeasePak security table other than the LeasePak administrative user. LeasePak Utility 108 provides no control in how the user is added to LeasePak security, and the LeasePak administrative user must still log on the LeasePak client in order to correctly configure other users' security settings.

Regular User

This is a typical user that logs on the LeasePak client, does not have direct sever logon privileges, and has access to various updates and reports as set by a supervisor user (lpsuper) through LeasePak Security [U0706]. The following are the basic steps for setting up this type of user:

1. Select a LeasePak user name and an initial client string password for the user. The string must be between 6 and 8 characters in length and conform to your company's password policies. The user lpsuper can change this client string (and the translated passwords with it) later through the LeasePak client Change Password function.
2. Use LeasePak Utility 112 Unix and SQL Server password translation to determine the translated server and DBMS server passwords based on the client string.
3. Create a OS server account for the user. The user name must be the same as the LeasePak user name, the primary group must be the LeasePak users' group (msi), and the password must be the translated OS server password.
4. Create a DBMS server account for the user. The user name must be the same as the LeasePak user name, and the password must be the translated DBMS server password.
5. Add the user to the appropriate LeasePak database.
6. Have the LeasePak administrative user add a LeasePak security record for the user through Security [U0706]. On the Port. Sec. tab, set LeasePak Account Status to 'Regular User'.

Report User

This is a specialized user that logs on the LeasePak client, does not have direct sever logon privileges, and has access to reports only. A supervisor user (lpsuper) can further restrict sets which reports the report user has access to by using LeasePak Security [U0706]. The following are the basic steps for setting up this type of user:

1. Select a LeasePak user name and an initial client string password for the user. The string must be between 6 and 8 characters in length and conform to your company's password policies. The user lpsuper can change this client string (and the translated passwords with it) later through the LeasePak client Change Password function.
2. Use LeasePak Utility 112 Unix and SQL Server password translation to determine the translated server and DBMS server passwords based on the client string.
3. Create a OS server account for the user. The user name must be the same as the LeasePak user name, the primary group must be the LeasePak users' group (msi), and the password must be the translated OS server password.
4. Create a DBMS server account for the user. The user name must be the same as the LeasePak user name, and the password must be the translated DBMS server password.
5. Add the user to the appropriate LeasePak database.
6. Have the LeasePak administrative user add a LeasePak security record for the user through Security [U0706]. On the Port. Sec. tab, set LeasePak Account Status to 'Report User'.

Partial Updates User

This is a specialized user that logs on the LeasePak client, either through the LeasePak client software or through a separate origination tool, does not have direct sever logon privileges, and only has access to Application [U08], Lessee [U0203], and other updates and reports related to origination. The following are the basic steps for setting up this type of user:

1. Select a LeasePak user name and an initial client string password for the user. The string must be between 6 and 8 characters in length and conform to your company's password policies. The user lpsuper can change this client string (and the translated passwords with it) later through the LeasePak client Change Password function.
2. Use LeasePak Utility 112 Unix and SQL Server password translation to determine the translated server and DBMS server passwords based on the client string.
3. Create a OS server account for the user. The user name must be the same as the LeasePak user name, the primary group must be the LeasePak users' group (msi), and the password must be the translated OS server password.
4. Create a DBMS server account for the user. The user name must be the same as the LeasePak user name, and the password must be the translated DBMS server password.
5. Add the user to the appropriate LeasePak database.
6. Have the LeasePak administrative user add a LeasePak security record for the user through Security [U0706]. On the Port. Sec. tab, set LeasePak Account Status to 'Partial Upd. User'.

Account Setup Steps

Password Selection

Select an initial password that the user will type to log on the LeasePak client. This is known as the client string or client string password. This password must be between 6 and 8 characters in length and conform to your company's password policies, which you can specify in LeasePak using Custom General [U0712]: Miscellaneous Customizations (refer to the LeasePak Reference Guide for more information on this update).

Password Translation

Use LeasePak Utility 112 Unix and SQL Server password translation to translate the client string into the OS and DBMS server passwords:

1. Log on the LeasePak server as $MSIADMIN or the LeasePak supervisor user (for the very first time, you may need to log on as $MSIADMIN).

   Terminal emulation: you must use one of the supported terminal types. Refer to the System Requirements for more information.

2. Type $uexe/lpadriver.exe /util and press Enter The terminal will display:

         0    Exit
       108    Add user security record  
       109    Dump contents of linked-in maps
       111    Copy the batch payment and PAP files into LeasePak
       112    Unix and SQL Server password translation
       200    Lock/unlock updates
       207    DAS update
       212    Change key utility (change port/comp/regn/offc)
   	

   (and so on). Type 112 and press Enter. The terminal will display:

   	This Utility option may be used to translate a Client password 
   	into the equivalent Unix and SQL Server passwords.
   
   	Do you wish to continue (Y/N)? 
   	

   Type y and press Enter.

3. The utility will prompt for the client string

   	Unix and SQL Server password translation utility
   
   	Instructions: Enter the Client password. The equivalent Unix and SQL Server passwords will be displayed.
   
   	Enter the Client string, <RETURN> to exit: 
   	

   Type the selected client string (6-8 characters in length) and press Enter. If you type password as the client string, the terminal will display

   	Client string: password
   	SQL Server string: rkqcguh4
   	Unix string: rrchglt1
   	

   NetSol does not recommend using the word "password" as an actual client string.

4. The utility will prompt for another client string

   	Enter the Client string, <RETURN> to exit:
   	

   Press Enter to exit the utility.

Refer to LeasePak Roles and Users for more information on password translation.

OS Server Account

Follow the appropriate instructions for your OS platform to add a LeasePak user account with the translated password. Make the LeasePak group msi the primary group for the user, and ensure that the user can write to the $HOME directory. If you assign a user's UID number manually, do not use a number greater than 32757. Contact your NetSol representative for more information.

.lplogin and .lpprofile
For users who need direct server logon privileges

Every LeasePak environment includes two hidden files, .lplogin and .lpprofile, located in the $top/env/env-name/etc directory, where env-name is the name of the LeasePak environment. The file .lplogin is a C shell startup file and .lpprofile is a Korn/Bourne/HP-UX Posix shell startup file. You must include these files in the appropriate startup files of any user that needs to log directly on the server to perform LeasePak and LeasePak-related tasks.

NetSol provides two sample startup files containing the .lplogin and .lpprofile information, sample.login (for C shell users) and sample.profile (for Korn/Bourne/HP-UX Posix shell users), located in the $top/env/env-name/lib directory, where env-name is the particular LeasePak environment.

To use the sample files:

1. Log on the server as root.

   Terminal emulation: you must use one of the supported terminal types. Refer to System Requirements for more information.

2. Copy the file sample.login from $top/env/env-name/lib (where env-name is the particular LeasePak environment) to the user's home directory.
3. Edit the file:

   	###########################################
   	#  MSI Sample .login file
   	###########################################
   
   	# Source users .lplogin file to set up LEASEPAK/UX environment
   
   	        if ( -f $HOME/.lplogin )  then 
   	                source $HOME/.lplogin
   	        else
   	                echo "Warning:  You don't have a .lplogin file"
   	        endif
   	

   Insert any startup information needed for your particular server into the beginning of the file. Leave everything from the comment # Source users .lplogin file to set up LEASEPAK/UX environment to the end of the file in place.

4. Copy the file sample.profile from $top/env/env-name/lib (where env-name is the particular LeasePak environment) to the user's home directory.
5. Edit the file:

   	###########################################
   	#  MSI Sample .profile file
   	###########################################
   
   	# Source user's .lpprofile file to set up LEASEPAK/UX environment
   
   	        if [ -f $HOME/.lpprofile ] ; then 
   	                . $HOME/.lpprofile
   	        else
   	                echo "Warning:  You don't have a .lpprofile file!"
   	        fi
   	

   Insert any startup information needed for your particular server into the beginning of the file. Leave everything from the comment # Source user's .lpprofile file to set up LEASEPAK/UX environment to the end of the file in place

6. Save a backup copy of the user's current startup files.
7. Rename the two sample files:

   	mv sample.login .login
   	mv sample.profile .profile
   	

8. Copy the .lplogin and .lpprofile files from $top/env/environment/lib (where environment is the particular LeasePak environment) to the user's home directory.
9. Have the user log off and then back on for the changes to take effect.
10. The user can run whatami to verify that the startup files are properly configured. The terminal will display something similar to the following:

    	User                       : user_name
    	LeasePak version           : 
    	Environment name           : environment
    	Environment type           : (production, test, or visitor) 
    
    	Database name              : lpr_database
    	Database vendor            : (Oracle or Sybase)
    	Database server            : database_server_name
    	Database home              : (usually /opt/oracle or /opt/sybase)
    
    	Designated build           : live
    	Executable directory is a  : link to build directory
    
    	You will need the following for LeasePak PC Client setup:
    	IP Address or name         : server_name
    	Server Port                : 
    	

    Use the values for IP Address or name, Environment name, and Server Port to configure the LeasePak client for connection to this particular environment.

NetSol recommends setting up both the .lplogin and .lpprofile files, regardless of which shell is normally in use.

The following scripts are useful for the administration of users with direct server logon privileges.

change_env

$MSIADMIN can use change_env to change another user's settings from one environment to another.

$MSIADMIN cannot use change_env to change its own settings or the settings of $MSIDBA.

To use change_env, log on the server as $MSIADMIN:

	change_env [username version env-name modes]
	

where username is the user whose environment you wish to change, version is the version to change to (or type the current version), env-name is the environment to change to (or type the current environment), and modes is the mode (read, write, execute for owner, group, world) number to apply to the .lp* files copied to the user's home directory. NetSol recommends a mode of either 640 (owner writable) or 660 (owner and group writable). After change_env, the user must exit and log back on for the changes to take effect.

change_env

Any user with direct server logon privileges can use whatami to determine the current environment settings. To use whatami, log on the server as a user with direct server logon privileges and run:

	whatami
	

The terminal will display something similar to the following:

	User                       : user_name
	LeasePak version           : 
	Environment name           : environment
	Environment type           : (production, test, or visitor) 

	Database name              : lpr_database
	Database vendor            : (Oracle or Sybase)
	Database server            : database_server_name
	Database home              : (usually /opt/oracle or /opt/sybase)

	Designated build           : live
	Executable directory is a  : link to build directory

	You will need the following for LeasePak PC Client setup:
	IP Address or name         : server_name
	Server Port                : 
	

DBMS Server Account

Use the LeasePak script db_add_login to create an account on your DBMS server:

To use db_add_login, log on the server as $MSIDBA:

db_add_login dbms-type new-login-name [new-login-password [srvadm-password]]

where dbms-type is either ora for Oracle or syb for Sybase, new-login-name is the same user name as the server account, new-login-password is the corresponding translated password, and srvadm-password is the password for the srvadm user.

LeasePak Database Permissions

Use the LeasePak script db_add_user to add a user to a specific LeasePak environment and database.

To use db_add_user, log on the server as $MSIDBA:

db_add_user environment-name legal-DBMS-user msi-access-group dbo-password

where environment-name is the specific LeasePak environment, legal-DBMS-user is the user's DBMS account user name, msi-access-group is either msi for normal read/write permissions or msir for read-only permissions, and dbo-password is the password for the dbo of the specific database (as specified during db_create).

LeasePak Security Records: LeasePak Utility 108
For the LeasePak administrative user only

Do not use LeasePak Utility 108 Add user security record to add any user to the LeasePak security table other than the LeasePak administrative user. The LeasePak Utility 108 function provides no control in how the user is added to LeasePak security, and the LeasePak administrative user must still log on the LeasePak client in order to correctly configure a other users' security records.

To user LeasePak Utility 108:

1. Contact your NetSol representative to obtain a daily password for LeasePak Utility 108. The daily password is only good during the day it is issued.
2. Log on the server as the LeasePak supervisor user (lpsuper_env-name)

   Terminal emulation: you must use one of the supported terminal types. Refer to the System Requirements for more information.

3. Use whatami to verify that you are in the correct LeasePak version and environment.
4. Type $uexe/lpadriver.exe /util and press Enter The terminal will display:

         0    Exit
       108    Add user security record  
       109    Dump contents of linked-in maps
       111    Copy the batch payment and PAP files into LeasePak
       112    Unix and SQL Server password translation
       200    Lock/unlock updates
       207    DAS update
       212    Change key utility (change port/comp/regn/offc)
   	

   (and so on). Type 108 and press Enter. The terminal will display:

   	This Utility option is an MSI Client Services tool used in initial client account setup. WARNING: Improper use of this utility will 
   	cause severe harm.
   	Do you wish to continue (Y/N)?
   	

5. Type y and press Enter. The terminal will prompt for the client string password:

   	Client Password?
   	

6. Type the LeasePak administrative user's client string password and press Enter. The terminal will prompt for the special LeasePak Utility 108 password:

   	Password?
   	

7. Type the daily password you received from NetSol and press Enter. The terminal will prompt for the user name:

   	Enter username, <RETURN> to exit:
   	

8. Type the LeasePak administrative user's user name and press Enter. The terminal will prompt for the user initials:

   	Enter user initials:
   	

   User initials are three characters and must be unique within the specific LeasePak database. Type the initials and press Enter to complete the update.

LeasePak Security Records: Security [U0706]

This section details a few items from Security [U0706] related to setting up the various types of user accounts. Refer to the LeasePak Reference Guide for the full documentation.

Determining the user type:

To specify whether an account is a regular, report, or partial updates user, select the appropriate LeasePak Account Status value on the Port. Sec. tab of Security [U0706]

Forcing a user password change:

In most cases, you will want users to change their passwords the first time they log on the LeasePak client. To force a user password change, select Force Password Change on next login on the Waiver Tol./Password tab of Security [U0706]. After the user logs on the client and changes the password, this box will clear.

LeasePak Queue Manager

NetSol 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.

Parameters

Configure the LeasePak queue manager parameters in the file Config (the file name begins with an uppercase C). You can find this file in /opt/qm/qm_3_version/library (or your equivalent), where version is the version of the queue manager appropriate for your platform.

The queue manager directories 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, or directories that cross physical drives or mount points.

To edit Config

1. Log on the server as msiadmin

   Terminal emulation: you must use one of the supported terminal types. Refer to System Requirements for more information.

2. If the batch or print queues are already set up and running, stop the queues before making any changes

   dcl -n /opt/qm/qm_3_version/com/stop_qmgr.com

3. Use vi or other editor to edit the file /opt/qm/qm_3_version/library/Config (the file name begins with an uppercase C). Locate and edit the following parameters
   
   

   SYSTEM

   Shared memory key. Change this to allow multiple queue manager versions on your system. If there are multiple installations of the queue manager, this must be unique for each installation. Shared memory keys should be spaced at intervals of at least 1000.

   When configuring shared memory in Sybase, use the following guide to determine the amount of shared memory needed by the Queue Manager:

   	The Queue Manager uses two (2) shared memory
   	segments. One is for storing the device mapping
   	and assignment information, the other for
   	additional process tables.
   
   	The size of these segments depends on two
   	parameters; Config:MAXJOB and Config:MAXDEV.
   
   	Currently, each process entry is 584 bytes, and
   	each device entry 220 bytes. Basic math show that
   	if you allow 200 users, you would need to be able
   	to allocate 200 * 582 (116400 / 1024 = 113K) bytes
   	of shared memory for the process table. Similarly,
   	for 250 devices you would need 250 * 220 (55000 /
   	1024 = 53K) bytes for the device table. This is
   	normally well within the limits for shared memory
   	access.
   
   	The Unix key for accessing the shared memory
   	segments (and all other Unix resources) is
   	governed by the Config:SYSTEM. Normally this will
   	be set to decimal 30000 (0x7530). This will tell
   	Unix to use key 0x7530 for the process table and
   	SYSTEM+1 (0x7531) for the device table.
   
   	The shared memory and all other resources can be
   	seen by executing an 'ipcs -a'.
   	

   MAXDEV

   Maximum number of devices to map. May need to change if you have many terminals or pseudo-terminals.

   MAXJOB

   Number of queue manager jobs. This should be set to two times the number of concurrent users, plus four times the job limit for each batch queue, plus one for each print queue.

   BINDIR

   Usually /opt/qm/qm_3_version/bin

   LIBDIR

   Usually /opt/qm/qm_3_version/a

   SYS$SYSTEM

   Unix/Linux path of the queue manager bin directory. Usually /opt/qm/qm_3_version/bin

   SYS$LIBRARY

   Unix/Linux path of the queue manager library directory. Usually /opt/qm/qm_3_version/library

   SYS$MESSAGE

   Unix/Linux path of the queue manager message directory. Usually /opt/qm/qm_3_version/message

   SNDOPRLOG

   Unix/Linux path to store queue manager SNDOPR log file. Usually /tmp/qm/

   LNMDIR

   Unix/Linux path to store queue manager Logical Name temporary files. Usually /tmp/qm/

   SORTDIR

   Unix/Linux path of queue manager sort files. Usually /tmp/qm/

   MBXDIR

   Unix/Linux path of queue manager mailbox directory. Usually /tmp/qm/

   JSPDIR

   Unix/Linux path to directory of the queue manager spool directory. Usually /opt/qm/qm_3_version/spool

   BATCH_INTERVAL

   Time interval between scans of the queues for new jobs. Default is 15 seconds, with a range of 1 to 60 seconds.

   BATCH_PRIORITY

   The Unix/Linux base priority of the batch queue jobs. The default is 20 (same as ordinary jobs). This can range from 0 to 40, with 0 being the highest priority. Setting it lower than 20 will affect other jobs on the system.

   DCLDIR

   Unix/Linux path of queue manager directory for DCL commands. Usually /opt/qm/qm_3_version/bin

Batch Queues

LeasePak primarily uses batch queues during End of Period processing. Configure batch queues in the file start_queues.com, located in /opt/qm/qm_3_version/com. LeasePak requires configuration of sys$batch. NetSol recommends setting up a separate batch queue for each portfolio, as each portfolio should use a different queue for its End of Period processing.

To edit start_queues.com

1. Log on the server as msiadmin

   Terminal emulation: you must use one of the supported terminal types. Refer to System Requirements for more information.

2. If the batch or print queues are already set up and running, stop the queues before making any changes

   dcl -n /opt/qm/qm_3_version/com/stop_qmgr.com

3. Use vi or other editor to edit the file /opt/qm/qm_3_version/com/start_queues.com

   $ if P1 .eqs. "" then P1 = 1
   $ init/que/start/job_limit='P1'/batch sys$batch
   $ init/que/start/job_limit='P1'/batch lp$eop1
   $ init/que/start/job_limit='P1'/batch lp$eop2
   $ wait 5
   $ init/que/start/job_limit='P1'/batch lp$eop3
   $ init/que/start/job_limit='P1'/batch lp$eop4
   

   init/que

   DCL initialize queues command. Creates the batch queue.

   start

   You must use the start parameter for queues to be ready to run jobs.

   job_limit

   Specifies how many jobs can run on the queue simultaneously. Values range from 1 to 255. Consult your NetSol representative when setting this parameter. Too low a number will slow End of Period processing, while too high a number may consume excessive resources on the server.

   batch

   Type of queue to initialize. For batch queues, this is batch

   sys$batch

   DCL default batch queue. Do not remove.

   lp$eop

   Format lp$eopn, where n is the portfolio number. Conventional name for a portfolio's End of Period batch queue.

   wait

   Format wait n, where n is the number of seconds to wait. Insert a wait command after every three init/que commands to ensure that all queues are initialized by the time start_queues.com is finished.

If you are using this section to perform additional queue manager configurations--that is, you have already completed the required configurations for LeasePak, you can now restart the queues. As msiadmin, use the following two commands to first start the queue manager, then start the queues

dcl -n /opt/qm/qm_3_version/com/start_qmgr.com

dcl -n /opt/qm/qm_3_version/com/start_queues.com

Printer Configuration

Your printer must be able to print 132-column output in order to print LeasePak reports.

When a user prints a report in LeasePak, the queue manager directs the print job to an emulated VMS-style printer queue, then maps the printing instructions to a Unix/Linux lp command, so that the Unix/Linux print spooler handles the actual printing.

The queue manager directories 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, or directories that cross physical drives or mount points.

To set up the printer, first define the printer on your server OS, then use the DEVINIT, Config, and start_queues.com files to define the printer in the queue manager.

Printer Name

LeasePak printer names must contain only lowercase letters (a-z) or numbers (0-9). Do not use an underscore ( _ ) in the name. In the following examples, assume there is a printer on the third floor of your office you will name 3fp.

Printer Installation and OS Configuration

Install the printer according to the manufacturer's instructions and connect it to the server, by either a direct (parallel or serial) or network connection. Logged on the server as root, define the printer using an administrative tool or direct commands. Verify that the system is ready to accept new print requests, the print queue is enabled, and the spooler is running, then test the printer

lp -d3fp file

where the -d option specifies the destination (name of printer) and file is any text file (with directory path if necessary).

DEVINIT

The DEVINIT file defines VMS-style pseudo-devices for disks, printers, magnetic tape, and null devices. The file name is all uppercase.

To edit DEVINIT

1. Log on the server as msiadmin

   Terminal emulation: you must use one of the supported terminal types. Refer to the System Requirements for more information.

2. If the batch or print queues are already set up and running, stop the queues before making any changes

   dcl -n /opt/qm/qm_3_version/com/stop_qmgr.com

3. Use vi or other editor to edit the file /opt/qm/qm_3_version/library/DEVINIT

   DUA0:    /               DK      512
   NL:      /dev/null       NL      10240
   LP:      /dev/lp         LP      512
   LP3FP:   /dev/null       LP      512
   LP3FPL:  /dev/null       LP      512
   LPBH:    /dev/null       LP      512
   LPSP:    /dev/null       LP      512
   

   (column 1)

   Column 1 contains the queue manager pseudo-device name. For each printer (other than the default LP), there are usually two listings--one for portrait printing and one for landscape. Pseudo-device names are always all uppercase and must be unique. The queue manager requires the entries for DUA0 (the disk device) and NL (the null device), and LeasePak requires an entry for the paperless print queue (LPBH). The above example includes entries for the sample printer 3fp, LP3FP (portrait) and LP3FPL (landscape).

   (column 2)

   Column 2 contains the full path of the corresponding Unix/Linux device. Since LeasePak print jobs are passed through to the Unix/Linux print spooler, all queue manager printer pseudo-devices are mapped to the Unix/Linux device /dev/null.

   (column 3)

   Column 3 specifies the device type:

   • DK - disk
   • LP - printer
   • MD - media (tape drive)
   • NL - null

   (column 4)

   Column 4 specifies an internal buffer size (for VMS emulation purposes only - this number is ignored by Unix/Linux).

Config

The Config file contains the parameters the queue manager uses to map printers to their corresponding Unix/Linux lp commands.

To edit Config

1. Log on the server as msiadmin

   Terminal emulation: you must use one of the supported terminal types. Refer to System Requirements for more information.

2. If the batch or print queues are already set up and running, stop the queues before making any changes

   dcl -n /opt/qm/qm_3_version/com/stop_qmgr.com

3. Use vi or other editor to edit the file /opt/qm/qm_3_version/library/DEVINIT. Locate the listings for the queue manager printer devices and their corresponding Unix/Linux commands by searching for the pattern LP. The required options for these listings will vary depending on your type of printer and which drivers you have installed.

   This is an example using an HP LaserJet printer with HP JetDirect

   LP3FP:  /usr/bin/lp -d3fp -odouble -otl66 -oc -c -s 2>>/tmp/qm//LP3FP_ERR < %s
   LP3FPL:  /usr/bin/lp -d3fp -odouble -olandscape -ofp12.5 -otl46 -c -s 2>>/tmp/qm//LP3FPL_ERR < %s
   LPSP:  /usr/bin/lp -dsysprint -s 2>>/tmp/qm/SYSPRINT_ERR < %s
   LPBH:  :
   

   This is an example using Postscript

   LP3FP:  /usr/bin/a2ps -P 3fp --columns=1 --rows=1 --portrait --chars-per-line=132 --major=rows -SDuplex:false -B --borders=no --medium=Letter 2>>/tmp/qm//LP3FP_ERR < %s
   LP3FPL:  /usr/bin/a2ps -P 3fp --columns=1 --rows=1 --landscape --chars-per-line=132 --major=rows -SDuplex:false -B --borders=no --medium=Letter 2>>/tmp/qm//LP3FPL_ERR < %s
   LPSP:  /usr/bin/a2ps -P sysprint 2>>/tmp/qm/SYSPRINT_ERR < %s
   LPBH:  :
   

   The syntax for mapping a normal printer device is

   S7DEVICE: command printer_name options error_output < %s

   The syntax for mapping the paperless queue device is

   LPBH: :

   Copy the pseudo-device names exactly from the DEVINIT file. If the printer has both portrait and landscape devices, create two configurations--one for portrait printing and another for landscape printing. Use whatever print command options are necessary to produce 132-column output with your particular printer(s). One of the print command options must specify that the spooler make a copy of the file to be printed. This ensures all files will be printed, particularly in the case where the user is running many reports of the same type, such as multiple Lease Inquiry [R0905] reports. If needed, contact your NetSol representative for assistance with mapping your printers.

start_queues.com

This file, located in /opt/qm/qm_3_version/com, contains the commands for initializing the printer queues as well as the batch queues.

To edit start_queues.com

1. Log on the server as msiadmin

   Terminal emulation: you must use one of the supported terminal types. Refer to System Requirements for more information.

2. If the batch or print queues are already set up and running, stop the queues before making any changes

   dcl -n /opt/qm/qm_3_version/com/stop_qmgr.com

3. Use vi or other editor to edit the file /opt/qm/qm_3_version/com/start_queues.com.

   The first section of the file contains the initializations for portrait and landscape documents

   $ define/form default 0 -
     /description="Portrait Compressed Letter Document" -
     /Length=66 -
     /margin=(Bottom=6,Top=6, Left=10, Right=10) -
     /stock=default -
     /truncate -
     /width=132
   $ define/form landscape 50 -
     /description="Landscape Letter Document" -
     /Length=46 -
     /margin=(Bottom=6,Top=6, Left=10, Right=10) -
     /stock=default -
     /truncate -
     /width=132
   

   Do not alter the parameters in this section. Contact your NetSol representative for more information.

4. Farther down the file, you will find the printer queue initializations

   $ init/que/start/form=default/on=LP3FP: sys$print
   $ init/que/start/form=landscape/on=LP3FPL: csl$print
   $ init/que/start/form=default/on=LPBH: sys$blackhole
   $ wait 5
   

   init/que

   DCL initialize queues command. Creates the printer queue.

   start

   You must use the start parameter for queues to be ready to run jobs.

   form

   For a portrait printer device, use form=default. For a landscape printer device (such as the example LP3FPL), use form=landscape.

   on

   Set to the queue manager printer pseudo-device name, followed by a colon (:). The pseudo-device name is all uppercase.

   sys$batch, csl$print, sys$blackhole

   DCL printer queue names. You can specify queue names using the following rules

   • the queue name can include letters (a-z), numbers (0-9), the dollar sign ($), and the underscore ( _ )
   • the name can be up to 31 characters in length
   • begin the name with a letter or number
   • include at least one letter in the name
   • for letters, use all lowercase

   wait

   Format wait n, where n is the number of seconds to wait. Insert a wait command after every three init/que commands to ensure that all queues are initialized by the time start_queues.com is finished.

If you are using this section to perform additional queue manager configurations--that is, you have already completed the required configurations for LeasePak, you can now restart the queues. As msiadmin, use the following two commands to first start the queue manager, then start the queues

dcl -n /opt/qm/qm_3_version/com/start_qmgr.com

dcl -n /opt/qm/qm_3_version/com/start_queues.com

Registration Codes

Use the /ver option with lpadriver.exe to obtain registration codes for dx Generation (automated document generation) and Print Spy, FormPak (obsolete), EOP Monitor, and LeasePak EC.

$uexe/lpadriver.exe /ver

        LEASEPAK UX
        Copyright (c) 1995 -  by NetSol Technologies Incorporated
        ------------------------------------------------------------
        Version        : -
        Build date     : 15-Aug- 00:18   
        Client name    : LeasePak Development                
        Client code    : V5
        User License   : 99999
        Report License : 99999
        Partial License: 99999

        Registration Codes
        ------------------------------------------------------------
        dx Generation   : SER-0541-ZZZ-P92ERR
        Print Spy       : SER-0541-ZZZ-P92ERR
        FormPak         : SER-0541-ZZZ-FE2O3
        Eop Monitor     : SER-0541-ZZZ-SO2
        LeasePak EC     : SER-0541-ZZZ-AL2O3

LeasePak  Documentation Suite

©  by NetSol Technologies Inc. All rights reserved.

The information contained in this document is the property of NetSol Technologies Inc. Use of the i= nformation contained herein is restricted. Conditions of use are subject to change without notice. NetSol Technologies 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 NetSol Technologies Inc. is prohibited.

Your document is loading...

This message should disappear within 5-15 seconds, depending on the size of the document and the speed of your connection to the Documentation Suite.

If you can still see this message after 20 seconds, try clicking the Refresh or Reload button on your Web browser.

If your document still does not load, refer to Document Load Troubleshooting for instructions on how to fix possible problems with either your Documentation Suite installation or Web browser setup.

If you do not have read access to the parent docsuite directory, you will not be able to load the Document Load Troubleshooting document. In this case, contact your network administrator for assistance.