Installation via a Batch Script

On UNIX, you can use a batch install script instead of the GUI version to install the files.

Run the command ./batch_install.csh
The values that control the installation are passed into the batch script as command line parameters, except for the "Existing Installation Directory". It gets the value for this from the $VOVDIR environment variable as it runs.
Because this is an update install to add a new platform to a previously installed release, the option -local copy should be used for specifying the handling of the "local" directory. Give it a value that corresponds to your policy on how the install should carry forward the local files from your current release into the upgrade.
  • create: Don't carry files forward. Create new starting state for files.
  • copy: Copy files from current release into upgrade.
  • link: Create symbolic link in upgrade to release-independent local directory.
Note: There is not an option value to cause a symbolic link in upgrade to the local directory in the current release.
Here is the logical description of calling the batch install for the scenario of installing an upgrade:
% # VOVDIR is set for current release
% cd /usr/tmp/rtda_download 
% ./batch_install.csh /opt/rtda/2016.09 -local link -rlm <port@host> -plat '<platform list>'

Here is a specific example of installing for the first time that compares to the example used in the GUI dialog example above.

%  source /opt/rtda/2015.03/common/etc/vovrc.csh
% cd /usr/tmp/rtda_download 
% ./batch_install.csh /opt/rtda/2015.09 -local link -rlm 7070@buffalo; -plat 'linux64 linux'

batch_install.csh

Run this from the temporary directory where you unpacked the .tar archives to install Altair Accelerator software into the <installationDirectory> target.

Usage

./batch_install.csh <installationDirectory> [OPTIONS]

Options

Use the below options for non-interactive installation.
-alm
port@host
Use port@host as the value of ALTAIR_LICENSE_PATH in this installation. If the -alm and -rlm options are both unspecified, then this utility will look for a license key file in the local directory.
-rlm
port@host
Use port@host as the value of RLM_LICENSE in this installation. If the -alm and -rlm options are both unspecified, then this utility will look for a license key file in the local directory.
-local
L
Specific handling of 'local' directory where L=create, copy or link (default).
-nocommon
Used when installing additional platforms.
-confirm
Prompt for confirmation.
-noconfirm
Default. Do not prompt for confirmation. All necessary directories will be created automatically.
-plat
'x y'
Platforms to install. Default is all available. Currently supported: armv8, linux64, win64.
-v
Increase verbosity of installation process.

Examples

./batch_install.csh /opt/rtda/<version>
./batch_install.csh /opt/rtda/<version> -rlm 7070@croc
./batch_install.csh /opt/rtda/<version> -local create -rlm 7070@croc
./batch_install.csh /opt/rtda/<version> -local link -plat 'linux win64'

Because this is an update install to add a new platform to a previously installed release, the options -nocommon and -local copy should be used. The copy choice for the local parameter will cause the process to copy the local files onto themselves, creating a non-destructive no-op operation.

Here is the logical description of calling the batch install for the scenario of adding platform-specific files for a new platform.
% cd /usr/tmp/rtda_download 
% ./batch_install.csh /opt/rtda/2016.09 -nocommon -local copy -rlm <port@host> -plat '<added-platform>'
Here is a specific example of doing an update by running the batch install to add the platform Linux to the release.
% cd /usr/tmp/rtda_download 
% ./batch_install.csh /opt/rtda/2016.09 -nocommon -local copy -rlm 7070@buffalo; -plat 'linux'