>"; } return true; } // --> "Silent" installation really means "non-interactive" installation of the product. Assuming there are no problems during the installation, the silent install method allows the user to perform a command line installation of the entire package with no need to answer prompts or make selections.  This can be useful, for example, in homogeneous clustered systems where the likelihood of installation failure is low but the cost of doing individual installs is high.

VTune™ Amplifier XE's installer supports "silent" installs via a configuration file.  The configuration file can be created during an initial install and then be used, for example, to repeat the install on other systems.  (Use the ">>" buttons to show and hide example output.)

1. The first step is to create a configuration file that includes your answers to the installer prompts.  Use the '-d' option of install.sh to create the file.

   [root@somesystem vtune_amplifier_xe_2011_update5]# ./install.sh -help
Extracting, please wait...
Usage: install.sh [options]

-h, --help                  print this message
-v, --version               print version information
-s, --silent [FILE]         run install silently, with settings in the configuration file
-d, --duplicate [FILE]      run install interactively, record the user input into the
configuration file
-t, --tmp-dir [FOLDER]      set custom temporary folder
--SHARED_INSTALL            install to a network-mounted drive or shared file system
for multiple users

Copyright 2006-2011, Intel Corporation, All Rights Reserved.
This script installs Intel® Software Products.

[root@somesystem vtune_amplifier_xe_2011_update5]# ./install.sh -d myinstall.cfg
Extracting, please wait...

1. Once the install completes, your configuration file will be ready for use.

   .
.
.
- To view a table of getting started documents:
/opt/intel/vtune_amplifier_xe_2011/documentation/en/documentation_amplifier.htm

To view movies and additional training, visit
http://www.intel.com/software/products
--------------------------------------------------------------------------------
q. Quit [default]
--------------------------------------------------------------------------------
Please type a selection or press "Enter" to accept default choice [q]:
[root@somesystem vtune_amplifier_xe_2011_update5]# ls
cd_eject.sh  EULA.txt    myinstall.cfg release_notes_amplifier_xe_linux.pdf  silent.cfg
CLI_install  install.sh  pset           rpm

The configuration file is a simple text file, which you can examine:

[root@somesystem vtune_amplifier_xe_2011_update5]# cat myinstall.cfg
ACTIVATION=exist_lic
DRIVER_MAKE_COMMAND=/usr/bin/make
DRIVER_KERNEL_SOURCE_DIR=/lib/modules/2.6.18-128.el5/build
DRIVER_C_COMPILER=/usr/bin/gcc
DRIVER_PER_USER_MODE=no
DRIVER_BOOT_SCRIPT=yes
DRIVER_LOAD=yes
POWER_DRIVER_INSTALL_TYPE=filesonly
SAMPLING_DRIVER_INSTALL_TYPE=build
DRIVER_PERMISSIONS=660
DRIVER_ACCESS_GROUP=vtune
CONTINUE_WITH_INSTALLDIR_OVERWRITE=yes
CONTINUE_WITH_OPTIONAL_ERROR=yes
PSET_INSTALL_DIR=/opt/intel/vtune_amplifier_xe_2011
INSTALL_MODE=RPM
ACCEPT_EULA=accept

1. Now, copy the install tar file and configuration file to the other system(s), extract the tar file and pass the configuration file to the install.sh script using the '-s' option.

   [root@someothersystem vtune_amplifier_xe_2011_update5]# ./install.sh -s myinstall.cfg
Extracting, please wait...
   
   After the script completes, you can see that the install was successful:
   
   [root@orspt-le64-59a vtune_amplifier_xe_2011_update5]# ls /opt/intel/vtune_amplifier_xe_2011/
amplxe-vars.sh bin64 documentation lib32 man resource sepdk uninstall.sh
bin32 config include lib64 message samples support.txt
[root@someothersystem vtune_amplifier_xe_2011_update5]#


Note: a valid license is required to install the software. This can be accomplished in several ways:

1. specify a valid serial number during creation of the silent configuration file
2. specify a directory that contains a valid license file in the INTEL_LICENSE_FILE environment variable
3. copy a valid license file to the /opt/intel/licenses directory
4. place a valid license file in a known location accessible from every system and reference it in the configuration file
5. set INTEL_LICENSE_FILE variable to point to your license server, in the case of floating licenses

---

 

Known issue: during the development of this article, we discovered that one piece of essential information not saved to the configuration file is the list of "components" to install.  This is part of the "custom" installation flow, so that if you configure the installer to install only the command-line interface and collectors, for example, that distinction is not saved to the configuration file.  As a workaround, you can manually add this specification to the configuration file.  Simply append a "COMPONENTS" line to the configuration file after the installer creates the file.  Possible values for the COMPONENTS line are:

• COMMON_NOARCH
• GUI_X86 or GUI_X86_64
• CLI_X86 or CLI_x86_64
• SEP_X86 or SEP_X86_64

COMMON_NOARCH is the uninstall and environment defining scripts.  GUI* is the graphical user interface, CLI* is the command-line interface, and SEP* is the event-based collector component.  As an example, to specify that only the command-line interface and collectors to be installed on an Intel®64 architecture system, add the following line:

COMPONENTS=COMMON_NOARCH;CLI_x86_64;SEP_X86_64

Note that the strings are case-sensitive and should be specified as documented here.

This known issue may be resolved in a future release.