> Installing inPilot
> This chapter describes how to install, upgrade, and uninstall the inPilot application.
> The following topics are explained in this chapter:

> l | Installing inPilot

> l | Upgrading inPilot

> l | Uninstalling inPilot

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

> l | Apache v2.2.11 with mod_python v3.3.1

> l | Python v2.6.4

> l | Postgres v 8.2.0

> l | Django v1.0.2

> l | JRE v1.6.0_12

> l | Quartz Schedular v1.6.4

> inPilot uses the following python/django packages:

> l | django_pagination-1.0.5

> l | django_sorting-0.1

> l | django_timezones-0.1

> l | psycopg2-2.0.8

> l | pytz-2009f

> Setting the Database Environment Strings
> WARNING: Failure to configure these settings may cause data loss and will minimally cause errors in the operation.
> 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.
> 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.

> 1 | The recommended filesystem for installation is ZFS. If installation is performed on any other filesystem, a warning message appears indicating the recommended filesystem.

> 2 | inPilot must be installed as a root user on the system. Installation with other user privileges is not recommended.

> 3 | Make sure no other Apache web server is running on the port being used for installation (default port is 8080). If it is, stop it before proceeding with the installation or provide a different port for Apache server. Check if an application is running on a given port by entering the following command:

> netstat -an | grep <port number>

> 4 | Make sure no other Postgres server is running on the port being used for installation (default port is 5432). If it is, stop it before proceeding with the installation or provide a different port for Postgres server. Check if an application is running on a given port by entering the following command:

> netstat -an | grep <port number>

> 5 | Make sure no other server is running on the port being used for installation for XML-RPC (default port is 9999). If it is, stop it before proceeding with the installation or provide a different port for XML-RPC server. Check if an application is running on a given port by entering the following command:

> netstat -an | grep <port number>
> 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. 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.

> l | Installing inPilot using Script based Installer

> l | Installing inPilot using GUI/Console based Installer

> Installing inPilot using Script based Installer
> Once the installation file has been copied to the server, use the following procedure to install the inPilot application.

> 1 | Go to the directory in which the file is stored.

> 2 | Unzip the file by entering the following command:

> gunzip starbi_x.x.x_x.tar.gz
> x.x.x is the version of the inPilot installation file.

> 3 | Untar the file by entering the following command:

> tar -xvf starbi_x.x.x_x.tar
> Decompressing the installation file results in the following files:

> l | README: A text file containing information pertaining to the release.

> l | install_starbi: A script to install the inPilot application.

> l | starbi.tar: A compressed file containing all the application files required for inPilot installation.

> l | uninstall_starbi: A script to uninstall the inPilot application.

> l | uninst: A GUI/Console based uninstaller to uninstall the inPilot application.

> l | inst: A GUI/Console based installer to install the inPilot application.

> l | In_Pilot_Installer.bin: The executable used by inst to install inPilot application.

> 4 | Execute the script by entering the following command:

> ./inst -console

> 5 | Respond to the on-screen prompts with the help of inputs given in the following table and configure various parameters as required.

> Parameter | Description | Default Value
> System Environment Variable Prompt
> | This dialog or script asks user to add variable values in ‘/etc/system’ file and restart the system. For more information, refer to the Setting the Database Environment Strings section. | N/A
> inPilot Installation
> Want to proceed | Type (y)es to proceed with the installation of inPilot application. | yes
> inPilot Installation Directory | Type the directory on the server in which the inPilot application is to be installed. | <current_director y>
> The following warning appears if the user performs installation on non-ZFS (UFS) partition path. ZFS is the recommended filesystem for installation. Warning! Path provided lies in ufs filesystem. Recommended filesystem for inpilot is zfs. Do you still want to continue? [no] ? Type (y)es or (n)o to proceed with the inPilot installation. | no
> inPilot Postgres login | Type an administrator name for the Postgres database administration. | sbgres
> inPilot Postgres Port | Type the port number over which PostgreSQL communication will occur with inPilot. Be sure no other Postgres server is running on configured port. | 5432
> inPilot Postgres uid | Type the UID over which PostgreSQL communication will occur with inPilot. | 100009
> inPilot Apache Port | Type the port number over which Apache web server communication will occur with inPilot. 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. | 8080
> inPilot RPC Port | Type the port number over which XML-RPC server communication will occur with inPilot. Be sure no other XML-RPC server is running on configured port. | 9999
> inPilot Bulkstat File Transfer Interval [seconds] | Enter the file transfer interval for bulk statistics in seconds. | 900
> inPilot Bulkstat Sample Interval [seconds] | Enter the sample interval for bulk statistics in seconds. | 300
> inPilot Archive Directory | Type the directory path for archiving parsed files. | <inpilot_install_di r>/archive
> The following warning appears if the user performs installation on non-ZFS (UFS) partition path. ZFS is the recommended filesystem for installation. Warning! Path provided lies in ufs filesystem. Recommended filesystem for inpilot is zfs. Do you still want to continue? [no] ? Type (y)es or (n)o to proceed with the inPilot installation. | no
> inPilot Configuration Confirmation
> Proceed with installation | Type (y)es to proceed with inPilot installation. | yes
> Do you want to start the inPilot components | Type (y)es to start the inPilot components immediately after installation. | yes

> 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.
> 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
> Follow the instructions below to install inPilot using the GUI/Console based installation wizard.

> 1 | Go to the directory in which the file is stored.

> 2 | Unzip the file by entering the following command:

> gunzip starbi_x.x.x_x.tar.gz
> x.x.x is the version of the inPilot installation file.

> 3 | Un-tar the file by entering the following command:

> tar -xvf starbi_x.x.x_x.tar
> Decompressing the installation file results in the following files:

> l | README: A text file containing information pertaining to the release.

> l | install_starbi: A script to install the inPilot application.

> l | starbi.tar: A compressed file containing all the application files required for inPilot installation.

> l | uninstall_starbi: A script to uninstall the inPilot application.

> l | uninst: A GUI/Console based uninstaller to uninstall the inPilot application.

> l | inst: A GUI/Console based installer to install the inPilot application.

> l | In_Pilot_Installer.bin: The executable used by inst to install inPilot application.

> 4 | Execute the script by entering the following command:

> ./inst [MODE]
> where [MODE] is optional.
> Two installation modes are supported namely:

> l | GUI

> l | Console

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

> 5 | Click Next to proceed.

> 6 | Respond to the on-screen prompts with the help of inputs given in the following table and configure various parameters as required.

> Parameter | Description | Default Value
> PostgreSQL System Settings screen
> | This dialog asks the user to check the variable values in ‘/etc/system’ file. If one or more entries are missing, click Cancel button to update ‘/etc/system’ and restart the system to re-run installer. For more information, refer to the Setting the Database Environment Strings section. | N/A
> inPilot Installation Directory screen
> Enter inPilot Directory Path | Enter the base directory path where inPilot is to be installed. Select Browse button to change the installation path. | <current_director y>
> PostgreSQL Server Configuration screen
> Administrator Login | Enter an administrator name for the Postgres database administration. | sbgres
> Administrator password | Enter the password for the Postgres database administration. | N/A
> inPilot Postgres UID | Enter the UID over which PostgreSQL communication will occur with inPilot. | 100009
> Port | Enter the port number on which PostgreSQL communication will be running. Ensure that no other Postgres server is running on configured port. | 5432
> Enter data directory path | Enter the data directory path of postgres being used. Select Browse button to change the installation path. | <inpilot_install_di r>/starbi/postgres/data
> inPilot Port Configuration screen
> Apache Port | Type the port number over which Apache web server communication will occur with inPilot. 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. | 8080
> RPC Port | Type the port number over which XML-RPC server communication will occur with inPilot. Ensure that no other XML-RPC server is running on the configured port. | 9999
> inPilot Archive Directory Configuration screen
> Enter archive directory path | Enter the directory path for archiving parsed files. Select Browse button to change the installation path. | <inpilot_install_di r>/archive
> inPilot Bulkstats Configuration screen
> inPilot Bulkstat File Transfer Interval [secs] | Enter the file transfer interval for bulk statistics in seconds. | 900
> inPilot Bulkstat Sample Interval [secs] | Enter the sample interval for bulk statistics in seconds. | 300
> Pre-installation Summary screen
> | The pre-installation screen displays the product name, install location, other product configurations, and disk space information before installing the product. Click Cancel button to stop installation or Install button to continue installation. | N/A
> Installing inPilot screen
> | The screen shows all the contents being loaded on the machine during installation. Click Cancel button to stop installation. | N/A
> inPilot Server Startup screen
> Start All Servers After Installation | Select the option to start all servers after installation. Click Next to proceed. | N/A
> Install Complete screen
> | The screen shows whether installation is successful or failed. Click Done button to quit the installer. | N/A

> 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.
> The upgrade procedure ensures that the data in the database 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.
> CAUTION: Please contact your local support representative to ensure compatibility prior to upgrading.
> The following steps describe how to upgrade the inPilot application:

> 1 | Stop the EDR file generation through L-ESS or HDD push. Run the following commands:

> ls -lrt <install path>/starbi/data/temp_data_files/<img name>/edr/normalized_data/data
> ls -lrt <install path>/starbi/data/temp_data_files/<img 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.]

> 2 | Stop the inPilot application using the following command from the <inpilot_install_dir>/starbi/bin directory:

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

> 3 | Install the new release of inPilot.

> inPilot is upgradable from:

> l | Earlier script installer based version to newer script installer based version

> l | Earlier script installer based version to GUI/Console installer based version

> l | Earlier GUI/Console installer based version to subsequent GUI/Console installer based version

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

> 4 | Once the installation is complete, start all the inPilot related processes.

> 5 | Restart the EDR file generation or HDD file push as needed.

> Uninstalling inPilot
> This section provides instructions on how to uninstall the inPilot application.
> WARNING: 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:

> l | Uninstallation using Script based Uninstaller

> l | Uninstallation using GUI/Console based Uninstaller

> Uninstallation using Script based Uninstaller
> 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
> This method must be used if installation has been done using GUI/Console based installer (using inst).
> Change to the directory in which inPilot is installed and execute the script by entering the following command:
> ./unins [MODE]
> where [MODE] is optional.
> Two modes are supported namely:

> l | GUI

> l | Console

> 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