Managing inPilot Installation


Managing inPilot Installation
 
This chapter describes how to install, upgrade, and uninstall the inPilot application.
The following topics are explained in this chapter:
Important: The procedures for installation, upgrade, and uninstallation of inPilot and RDP remain the same.
Installing inPilot
This section provides instructions on how to install the inPilot application.
Important: Make sure that your system meets the minimum requirements as indicated in the System Requirements section in the inPilot Overview chapter of this guide.
The following inPilot components are installed by inPilot installer.
inPilot uses the following python/django packages:
Setting the Database Environment Strings
Prior to installing the inPilot components onto the server hardware, there are numerous system environment configuration settings that should be configured. While PostgreSQL will be installed during the installation procedure, these settings must be configured manually.
 
Warning: Failure to configure these settings may cause data loss and will minimally cause errors in the operation.
Add the following values to system file in the /etc/system directory if they are not present and restart the system before continuing with the installation of the inPilot components.
set msgsys:msginfo_msgmnb=65536
set msgsys:msginfo_msgtql=1024
set shmsys:shminfo_shmmax=1300000000
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=256
set shmsys:shminfo_shmseg=256
set semsys:seminfo_semmap=256
set semsys:seminfo_semmni=512
set semsys:seminfo_semmns=512
set semsys:seminfo_semmsl=270
 
Pre-installation Checks
Ensure the following checks are made before installing the inPilot application.
Step 1
Step 2
inPilot must be installed as a root user on the system. Installation with other user privileges is not recommended.
Step 3
netstat -an | grep <port number>
Step 4
netstat -an | grep <port number>
Step 5
netstat -an | grep <port number>
Step 6
Step 7
Step 8
If the L-ESS is installed as a root user, the ownership of L-ESS installation should be changed from root to non-root user. This new user must be added to inPilot Group. For example, if L-ESS is initially running as root and new user created is essadmin, then perform the following sequence of operations.
Step a
Step b
Add the user essadmin to inPilot group by entering the following command as root user - usermod -G <inPilot Group> essadmin
Step c
Step d
Step e
Login as essadmin with the command su essadmin
Step f
Step 9
If the L-ESS is installed as a non-root user say essadmin, this user should be added to inPilot Group.
Step a
Step b
Add the user essadmin to inPilot group by running the following command as root- usermod -G <inPilot Group> essadmin
Step c
Log off and relogin again as essadmin for the group addition to come into effect.
Step d
Step 10
Step 11
 
The NIS users should always be associated with NIS Groups. The non NIS users should be associated with Non NIS groups. Also, it is recommended to have separate non NIS users for inPilot installation.
inPilot Installation
The inPilot installation files are distributed as a single compressed file with a .tar.gz extension.
Important: The inPilot application supports both Solaris-Sparc and Solaris-x86 platforms. The installable tar file names help in identifying the platform. For example, starbi_x.x.x_sparc.tar.gz indicates that this file is for Solaris-Sparc platform. Similarly, starbi_x.x.x_x86.tar.gz indicates that this file is for Solaris-x86 platform.
For information on downloading the appropriate inPilot package for your requirements, contact your sales representative.
The inPilot application and its components can be installed using one of the following two methods.
 
Installing inPilot Using Script-based Installer
 
Important: To perform the installation procedure explained in this section, you must be logged into the server as a root user.
After copying the installation file to the server, use the following procedure to install the inPilot application.
Step 1
Step 2
gunzip starbi_x.x.x_x.tar.gz
x.x.x is the version of the inPilot installation file.
Important: After un-zipping the installation file, set the permission of .tar file to 700 using the following command and then continue with the installation process. - chmod 700 starbi_<release no>_<platform>.tar
Step 3
tar -xvf starbi_x.x.x_x.tar
Decompressing the installation file results in the following files:
README: A text file containing information pertaining to the release.
install_starbi: A script to install the inPilot application.
starbi.tar: A compressed file containing all the application files required for inPilot installation.
inst: A GUI/Console based installer to install the inPilot application.
In_Pilot_Installer.bin: The executable used by inst to install inPilot application.
Step 4
./install_starbi
Important: The installation script checks the disk space in the system. If the available disk space is lesser, then the script will give an error and abort the installation process.
Step 5
 
This dialog or script asks user to add variable values in /etc/system file and restart the system.
Type (y)es to proceed with the installation of inPilot application.
Type (y)es or (n)o to proceed with the inPilot installation.
Type i or press Enter to install the inPilot application.
To install RDP type r. Refer to the following table for the parameters associated with the RDP installation.
Important: The Administrator user created should be manually activated with a password once the inPilot installation is complete. This can be done by entering the following command as root user: passwd <adminusername> Upon executing this command, the user will be asked to enter a suitable administrator password.
Important: This input will be asked only if the Administrator login name provided does not exist.
Important: If the Administrator login name provided already exists, the Primary Group of this login will be considered as the inPilot User Group. Otherwise, the user will be asked to enter the Primary Group information.
Important: Be sure no other Postgres server is running on configured port.
Important: Be sure no other Apache web server is running on port which you are using while installation. If the port is being used, abort the installation.
Important: Be sure no other XML-RPC server is running on configured port.
Type (y)es or (n)o to proceed with the inPilot installation.
Type (y)es to proceed with inPilot installation.
Type (y)es to start the inPilot components immediately after installation.
 
Important: The Administrator user created should be manually activated with a password once the inPilot installation is complete. This can be done by entering the following command as root user: passwd <adminusername> Upon executing this command, the user will be asked to enter a suitable administrator password.
Important: This input will be asked only if the Administrator login name provided does not exist.
Important: If the Administrator login name provided already exists, the Primary Group of this login will be considered as the inPilot User Group. Otherwise, the user will be asked to enter the Primary Group information.
Important: Be sure no other Postgres server is running on configured port.
Important: Be sure no other Apache web server is running on port which you are using while installation. If the port is being used, abort the installation.
Important: Be sure no other XML-RPC server is running on configured port.
Type (y)es or (n)o to proceed with the RDP installation.
Type (y)es to proceed with RDP installation.
Type (y)es to start the RDP components immediately after installation.
After you have provided the inputs, the installation script starts the inPilot components and you receive a message indicating that inPilot installation is completed.
 
Installing inPilot Using GUI/Console based Installer
 
Important: To perform the installation procedure explained in this section, you must be logged into the server as a root user.
Follow the instructions below to install inPilot using the GUI/Console based installation wizard.
Step 1
Step 2
gunzip starbi_x.x.x_x.tar.gz
x.x.x is the version of the inPilot installation file.
Step 3
tar -xvf starbi_x.x.x_x.tar
Decompressing the installation file results in the following files:
README: A text file containing information pertaining to the release.
install_starbi: A script to install the inPilot application.
starbi.tar: A compressed file containing all the application files required for inPilot installation.
inst: A GUI/Console based installer to install the inPilot application.
In_Pilot_Installer.bin: The executable used by inst to install inPilot application.
Step 4
./inst [MODE]
where [MODE] is optional.
Two installation modes are supported namely:
The command ‘inst/uninst -help' provides usage of the scripts. This script installs the Apache, Postgres and Scheduling servers functionality. The display must be set for running in GUI mode, else the installation will run in Console mode.
The following inPilot Installer dialog appears displaying the inPilot version getting installed.
 
Step 5
Click Next to proceed.
Step 6
This dialog asks the user to check the variable values in /etc/system file. If one or more entries are missing, click Cancel to update /etc/system and restart the system to re-run installer.
Click Browse to change the installation path.
Important: The Administrator user created should be manually activated with a password once the inPilot installation is complete. This can be done by entering the following command as root user: passwd <adminusername> Upon executing this command, the user will be asked to enter a suitable administrator password.
Important: This input will be asked only if the Administrator login name provided does not exist.
Important: If the Administrator login name provided already exists, the Primary Group of this login will be considered as the inPilot User Group. Otherwise, the user will be asked to enter the Primary Group information.
Important: Ensure that no other Postgres server is running on configured port.
Click Browse to change the installation path.
<inpilot_install_dir>/starbi/postgres/data
Important: Ensure that no other Apache web server is running on the port being used for installation. If the port is being used, abort the installation.
Important: Ensure that no other XML-RPC server is running on the configured port.
Click Browse to change the installation path.
Click Cancel to stop installation or Install to continue installation.
Click Cancel to stop installation.
Click Next to proceed.
Click Done to quit the installer.
Confirming Successful Installation
Verify that the inPilot application is running and accessible by entering the following URL in your Web browser:
http://<inpilot_installation server name or IP address>:<apache port>
For information on using the inPilot GUI, see the inPilot Online Help documentation.
 
Upgrading inPilot
 
This section provides instructions on how to upgrade the installed inPilot application.
Important: To perform the upgrade procedure explained in this section, you must be logged into the server as a root user.
The upgrade procedure ensures that the database content is retained in the new installation. It also ensures that if there are any pending files to be processed in the old installation, then those file are also made available in the new installation.
Important: Before performing the upgrade process, ensure that the browser cache is cleared.
Caution: Please contact your local support representative to ensure compatibility prior to upgrading.
Important: If the previous installation is inPilot then the installation script will cause upgrading the software to inPilot and if the previously installed component is RDP then the script will cause upgrading to RDP.
The inPilot upgrade process is carried out in two steps:
1.
2.
The online upgrade is the conventional upgrade process. It will upgrade only last 7 days of available data i.e. it will get the latest date for which data is available and upgrade the last 7 days data only from that date.
Once the online upgrade is complete, offline upgrade starts in the background and it will upgrade all the remaining data older than last 7 days.
During the offline upgrade, there is a possibility of data outage. So, the reports older than last 7 days might be inaccessible from GUI during this period. Once the offline upgrade is over, these reports will be visible again.
The following steps describe how to upgrade the inPilot application:
Step 1
ls -lrt <install path>/starbi/data/temp_data_files/<chassis name>/edr/normalized_data/data
ls -lrt <install path>/starbi/data/temp_data_files/<chassis name>/edr/normalized_http_data/data
Check if the above commands return any pending input EDR files for the available gateways. If yes, wait for some time (5-10 minutes) to let the inPilot process finish these pending EDR files. Check again, and repeat the procedure until there are no pending EDR files for the available gateways. This is to make sure that you do not not stop any inPilot process while processing.
Step 2
./serv stop
Important: For all inPilot software versions 9.0.16 and later, use the serv stop command.
or
./shutdown.sh
Important: For all inPilot software versions 9.0.15 and lower, use the shutdown command.
Then, check the status of processes using the following command:
./serv status
Important: For all inPilot software versions 9.0.16 and later, use the serv status command.
or
./status.sh
Important: For all inPilot software versions 9.0.15 and lower, use the status command.
Important: Make sure that none of the processes is running.
Step 3
./psql -U <postgres username> -p <portnumber> -c "select tablename from pg_tables where tablename like '%2009'" starbidb
The following is a sample output:
tablename
-----------------------------------
sbi_edr_gw_proto_summary_06292009
sbi_edr_sub_06292009
sbi_edr_sub_topn_06292009
sbi_edr_gw_proto_summary_06302009
sbi_edr_sub_06302009
sbi_edr_sub_topn_06302009
Step 4
./pg_dump -p <postgres port> -U <postgres user> -F p -v -f "<file name with absolute path>" -t "\"public\".\"<table_name>\"" starbidb
Important: Be sure that there are different file names for different tables. It is recommended to have the file name same as the table name to avoid any confusion, and keep this file in the /export/home/ directory.
For example, assuming that you are in the postgres/bin directory:
./pg_dump -p 5432 -U sbgres -F p -v -f "/export/home/sbi_edr_gw_proto_summary_06292009.sql" -t "\"public\".\"sbi_edr_gw_proto_summary_06292009\"" starbidb
Step 5
./psql -U <postgres user> -p <postgres port> -c "copy sbi_gateway to '<old_inpilot_install_dir>/starbi/postgres/data/sbi_gateway" starbidb
Step 6
./pg_stop
Step 7
inPilot is upgradable from:
For instructions on different inPilot installers, refer to the inPilot Installation section.
In case of the first two upgrade options mentioned above, make sure that you enter the old installation path (<install_dir>) for upgrade when prompted for the 'inPilot Installation directory'. In case of the third upgrade option, it automatically detects the old installation path through registry information. The installation automatically detects earlier setup and reads required configuration for Apache, Postgres and RPC port, etc. You will be prompted with a confirmation message before proceeding with the upgrade process.
After upgrade, the log files are generated at /starbi/logs/ directory.
Important: The installation script will check if the Administrator user and Primary Group information is already present in database. If it does not exist, it will ask the user to enter this information and then continue with the upgrade.
Step 8
Step 9
./psql -U <postgres user> -p <postgres port> starbidb < <backedup table file name>
For example:
./psql -U sbgres -p 5432 starbidb < /export/home/sbi_edr_gw_proto_summary_06292009.sql
This creates required table and loads the data. Then, restore the gateway tables and schedules.
Step 10
Step 11
Important: The RDP should be upgraded manually. If the version of the RDP is not compatible with the inPilot, then inPilot may ignore the data sent by RDP. Thus, RDP should always be upgraded if it is not in sync with the inPilot. For change in mode from RDP to inPilot or vice-versa, re-installation is required.
Uninstalling inPilot
This section provides instructions on how to uninstall the inPilot application.
 
Important: It is recommended that you manually perform a backup of all critical and historical data files before proceeding with this procedure. Failure to do this causes removal of all the directories, files and database.
The inPilot application and its components can be uninstalled using one of the following two methods:
Important: The Administrator user and Primary Group configured during installation / upgrade will not be deleted during uninstallation. These have to be deleted manually by entering the following commands as root user: userdel <ADMINUSER> and groupdel <ADMINGROUP>
Uninstallation Using Script-based Uninstaller
 
Important: To perform the uninstallation procedure explained in this section, you must be logged into the server as a root user.
This method must be used if installation has been done using install_starbi script.
Execute the script by entering the following command:
./uninstall_starbi
Uninstallation Using GUI/Console-based Uninstaller
 
Important: To perform the uninstallation procedure explained in this section, you must be logged into the server as a root user.
This method must be used if installation has been done using GUI/Console based installer (using inst).
Change to the directory where inPilot is installed and execute the script by entering the following command:
./uninst [MODE]
where [MODE] is optional.
Two modes are supported namely:
This uninstall script stops all the servers if it is running and all the data is wiped off.
Important: The uninstall script does not cleanup the archive directory.
 
 

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883