Installing Applications

In general, it is not necessary to install single applications on a running system. Instead, the system is upgraded using app upgrade as described in the Upgrading Applications section.

The system collects all visible application versions for display using app list.

A screen for the app list command from the command line interface:

platform@cscluster1:~$ app list
selfservice - selfservice install script
   latest version 1.5.0 (2015-11-23 17:28) is installed

voss-deviceapi - voss-deviceapi install script
   latest version 1.5.0 (2015-11-23 17:26) is installed

cluster - cluster management
   latest version 1.5.0 (2015-11-23 17:25) is installed

template_runner - Template Runner
   not installed
   version available: 1.5.0 (2015-11-23 17:36)

mongodb - no-sql database server
   latest version 1.5.0 (2015-11-23 17:24) is installed

support - Diagnostic tools for tech support
   latest version 1.5.0 (2015-11-23 17:27) is installed

snmp - snmp management client and server
   latest version 1.5.0 (2015-11-23 17:31) is installed

nginx - lightweight web server
   latest version 1.5.0 (2015-11-23 17:24) is installed

services - Platform core services
   latest version 1.5.0 (2015-11-23 17:26) is installed

platform - Platform install/upgrade
   latest version 1.5.0 (2015-11-23 17:26) is installed

nrs - NRS install script
   not installed
   version available: 1.2.0 (2015-11-23 17:36)

security - Latest system security updates
   latest version 1.5.0 (2015-11-23 17:34) is installed

vmware - VMware tools
   not installed
   version available: 1.5.0 (2015-11-23 17:24)

Each application will display a short description of the application, the version installed, and whether other versions are available.

Additional applications can be downloaded using the instructions detailed under the System Control:Download section.

An application can be installed with app install <application-name>[version:<version>] [delete-on-success <[yes|y]|[no|n]>]

For example,

• app install snmp
• app install platform version 0.8.1 2014-01-09 00:46

For release 19.1.2 and later; when using the app install command to install patch scripts that have been added to the media/ directory, the delete-on-success parameter and yes|no value can be added to remove or keep the the patch file in the directory after successful installation.

Example: app install media/patch.script delete-on-success yes

By default, in other words without this parameter, the user is prompted whether to delete or keep the patch script:

Do you want to remove patch after successful completion?

If the --force parameter is appended to the parameter, no prompt is shown.

The application will automatically start its processes on install. In isolated rare cases, it may be necessary to manually provision the system afterward with system provision so that other applications are configured to work with the new application. This is taken care of automatically during the upgrade process described below.