Important: The procedures for installation, upgrade, and uninstallation of inPilot and RDP remain the same.
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.
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.
Step 2 inPilot must be installed as a root user on the system. Installation with other user privileges is not recommended.netstat -an | grep <port number>netstat -an | grep <port number>netstat -an | grep <port number>
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 Change the ownership of L-ESS installation to this new user using the following command - chown -R essadmin <LESS installation directory>
Step e
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.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.
Important: To perform the installation procedure explained in this section, you must be logged into the server as a root user.
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
• 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.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.
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. 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.
<inpilot_install_dir>/archive 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.
<rdp_install_dir>/archive Type (y)es to proceed with RDP installation. Type (y)es to start the RDP components immediately after installation.Important: To perform the installation procedure explained in this section, you must be logged into the server as a root user.
• 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../inst [MODE]
•
•
Step 5 Click Next to proceed.
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.
Click Browse to change the installation path. <inpilot_install_dir>/starbi/postgres/data Click Browse to change the installation path. <inpilot_install_dir>/archive Click Cancel to stop installation. Click Next to proceed. Click Done to quit the installer. http://<inpilot_installation server name or IP address>:<apache port>For information on using the inPilot GUI, see the inPilot Online Help documentation.Important: To perform the upgrade procedure explained in this section, you must be logged into the server as a root user.
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.
Step 2 Stop the inPilot application using the following command from the <inpilot_install_dir>/starbi/bin directory: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:
Step 6 Stop the postgres server by entering the following command from the <inpilot_install_dir>/postgres/bin directory: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 9 Restore the backed up data from postgres server by entering the following command from the <inpilot_install_dir>/starbi/postgres/bin directory: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.
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.
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>
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.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)../uninst [MODE]
•
•
![]() |
Cisco Systems Inc. |
Tel: 408-526-4000 |
Fax: 408-527-0883 |