On Linux* OS: After unpacking the Intel® Trace Collector archive in a folder of your choice read the file relnotes.txt for information on how to install Intel® Trace Collector.
On Microsoft Windows* OS: run the installation file setup.exe and follow the instructions given in the installation wizard.
To enable the software, Intel will issue you a license key. The license key is a simple text file containing details of the software that will be enabled. An evaluation license key contains a time limited license.
If called without a valid license, or with invalid settings of the above environment variable, installation aborts with an error message like the following one:
Checking for flexlm license Feature to check out: TRACE_COLLECTOR Error: A license for ITrColL could not be obtained (-1,359,2). Is your license file in the right location and readable? The location of your license file has to be specified via the $INTEL_LICENSE_FILE environment variable. License file(s) used were (in this order): Visit http://support.intel.com/support/performancetools/support.htm if you require technical assistance. FLEX_CHECKOUT test failed to acquire license (rc=-1)
License management has to be transparent, but if you have any problems during installation, submit an issue to Intel® Premier Customer Support (http://premier.intel.com).
To acquire a demo license or to find out how to purchase the product, visit the Intel Cluster Studio XE product page at http://software.intel.com/en-us/articles/intel-cluster-studio-xe/.
The installer creates itacvars.sh (for shells with Bourne* syntax) and itacvars.csh (for shells with csh syntax) on Linux systems. On Microsoft Windows systems you will find an itacvars.bat batch script. Sourcing the correct file in a shell (with . itacvars.sh, or source itacvars.csh or itacvars.bat respectively) will update $LD_LIBRARY_PATH and $PATH as well as set additional environment variables.
VT_ROOT points to the root of the Intel® Trace Collector installation. It is used to find the Intel® Trace Collector include and library files when compiling programs in the example makefile (Example: for using it with -I$(VT_ROOT)).
VT_LIB_DIR points to the folder containing the static Intel® Trace Collector libraries. It might be useful to create Makefiles or shorter linkage commands when using -L.
VT_SLIB_DIR (VT_DLL_DIR on Microsoft* Windows* OS) points to the folder containing the dynamic Intel® Trace Collector libraries. It might be useful to create Makefiles or shorter linkage commands when using -L.
VT_ADD_LIBS lists libraries Intel® Trace Collector is dependent on and needs to be linked against when using Intel® Trace Collector.
VT_MPI points to the currently selected MPI implementation as used by VT_LIB_DIR and VT_SLIB_DIR.
VT_MPI_DLL (Microsoft Windows version only) name of the MPI dll to be loaded by an Intel® Trace Collector dll. If the Fortran interface of MPI is involved and MPI offers this in a separate dll (for example, MPICH2*), it has to be specified through VT_FMPI_DLL.
The itacvars script accepts an optional argument on Microsoft* Windows* OS: impi64.
It is possible to install several different Intel® Trace Collector packages in parallel on the same machine by using different folders. Overwriting an old installation with a new one is not recommended, because this will not ensure that obsolete old files are removed. A single dot . can be used to install in the directory where the archive was unpacked.
To use Intel® Trace Collector on a cluster of machines, you can either install Intel® Trace Collector once in a shared directory which is mounted at the same location on all nodes, or you can install it separately on each node in a local folder. Neither method has a clear advantage when it comes to runtime performance. Root privileges are only needed if writing into the desired install folder requires them.
For using shared libraries, the installation path must be the same on all nodes.
On Microsoft Windows Compute Cluster Server*, most of this is handled by OS-provided mechanisms. For Linux there is a mechanism for unattended mass installations in clusters. It consists of the following steps:
Start the install script with the option --duplicate. It will install Intel® Trace Collector as usual, but in addition to that it will create a file called itc_<platform>_<version>_SilentInstall.ini in the current folder or, if that folder is not writable, /tmp/itc_<platform>_<version>/SilentInstall.ini. Alternatively you can modify the existing SilentInstallConfigFile.ini. It is necessary to acknowledge the End User License Agreement by editing that file and replacing ITC_EULA=reject with ITC_EULA=accept.
Run the install script on each node with the option --silent <.ini file>. This will install Intel Trace Collector without further questions using the install options from that .ini file. Only error messages will be printed, all the normal progress messages are suppressed.