The following post-installation procedures apply only to the Mechanical APDL and Ansys Workbench products. These are in addition to the post-installation procedures in the previous section.
Set the following environment variables based on the behavior you want. Set the environment variables following the conventions of your shell. Not all of these are required for all integrated Ansys Workbench products (such as Ansys Autodyn), but setting them correctly for Ansys Workbench will in no way hinder the performance of the other products.
The ANSYS242_DIR environment variable sets the location of the Ansys directory hierarchy. The default value is /ansys_inc/v242/ansys. You probably will not need to reset this variable, unless you change the location of the installed files. The ANSYSLIC_DIR environment variable sets the location of the Ansys licensing directory hierarchy. The default value is /ansys_inc/shared_files/licensing. You probably will not need to reset this variable, unless you change the location of the licensing files. ANSYS242_PRODUCT - set this to the correct product variable to run Mechanical APDL to start with the correct product without specifying the -p command modifier each time. See the Ansys Product to License Feature Mapping table located on Installation and Licensing Help and Tutorials page of the Ansys Customer Portal for a list of valid product variables. ANSYS_LOCK - set to ON (default) to create file locks to prevent users from opening a new job with the same name and in the same directory as the current job. Ansys242_WORKING_DIRECTORY - set this variable to the directory you want designated as your working directory. The working directory setting in the launcher will reflect this setting. ANSYS242_MAT161 - set this environment variable to 1 to enable use of the LS-DYNA *MAT_COMPOSITE_MSC material (requires an LS-DYNA MAT_161 license). ANSYS242_MAT162 - set this environment variable to 1 to enable use of the LS-DYNA *MAT_COMPOSITE_DMG_MSG material (requires an LS-DYNA MAT_162 license). ANSBROWSER - set this environment variable to the browser on your system (specify the full path) if the automatic browser detection fails. A browser is needed to view HTML reports and help for the ANS_ADMIN utility and the Mechanical APDL launcher. By default, ANSBROWSER points to one of several Linux browsers, based on the browser specified in your path (if any). If you will be using connection functionality, you may have additional environment variables to set. See the section Configuring CAD Products later in this guide for more information.
Create or update the at. files. The at.allow file should contain the username of all users allowed to run batch jobs; the at.deny file should contain the username of users who are not permitted to run batch jobs. The files consist of one username per line and can be modified only by the superuser. If neither file exists, only root will be able to run batch jobs.
The at. files are located in the /etc directory on Linux machines.
Specify the product order as it will appear in the Mechanical APDL launcher (optional). If you want to specify product order, use the ANSLIC_ADMIN utility. See the Ansys Licensing Guide for more information.
Explicit Dynamics, Rigid Dynamics, My Computer Background, and Remote Solve Manager (RSM) Users: — If you are running Ansys Workbench on a multi-user RSM machine, the ‘My Computer, Background’ Solve Process Settings will likely not function as expected due to write permissions for RSM working directories. In this situation, we strongly recommend that you set up RSM as a daemon. For more information see Starting the RSM Launcher Service Automatically at Boot Time for Linux in the Remote Solve Manager User's Guide.
This issue also affects Rigid Dynamics and Explicit Dynamics using both ‘My Computer’ and ‘My Computer, Background’ Solve Process Settings.
The following post-installation procedures apply only to the Ansys CFX product.
The Linux installation of Ansys CFX or Ansys TurboGrid automatically installs the Sun Java 2 Runtime Environment in the /ansys_inc/v242/commonfiles/jre directory. Regardless of whether you have modified your setup files, you can still run Ansys CFX commands by specifying the full pathname of the commands you want to run. This procedure may be useful if you have several releases of Ansys CFX installed and you want to run more than one release.
Unless you want to run Ansys CFX commands by typing their full path names, for
example cfxroot/bin/cfx5 (where
cfxroot is the directory in which Ansys CFX is
installed), your command search paths must be modified to search the directory
cfxroot/bin. This can be
done by one of the following methods:
Modification of individual user setup files — You can select from the Ansys CFX Launcher to modify your own setup files: .login for the C shell, .profile for the Bourne and Korn shells. The utility can also be run from the command line by entering:
cfxroot/bin/cfx5setupuserIf this modification is done, the Ansys CFX software will be available every time you log in, just by running the Ansys CFX commands by name. This method has the advantage that it need not be done by the system administrator, but has the disadvantage that it must be done by each user.
Use the -h option to view the optional commands.
If you choose to modify your setup files, you will see a message indicating that your setup files have been changed. You will then need to log out and log in again or source your setup files before you can use the software.
Manual execution of a setup script each time the software is used — You can also use the menu of the launcher to launch an editor to create new setup scripts which need to be run each time you want to use the Ansys CFX software. This method has the advantage of not requiring changes to existing setup files and allows you to use different versions of Ansys CFX software by running different setup files. The disadvantages are that all users must create their own setup files and run them manually in every session in which they want to run Ansys CFX software.
Having created the setup files, users of the C shell then need to do the following to run Ansys CFX:
source ~/cfx5.login cfx5
Having created the setup files, users of the Bourne or Korn shell then need to do the following before running Ansys CFX:
.$HOME/cfx5.profile cfx5
Modification of system setup files — The system administrator modifies the setup files (normally
/etc/profile), which are run by all users during login, to
include the directory
cfxroot/bin in the command
search path. While this has the advantage of only one file needing to be
modified in order to allow all users to use the software, it also:
Affects users regardless of whether they use Ansys CFX
Can only be done by the root user
Is system dependent
Refer to your system documentation for information about which files to change for your workstations.
Manual modification of individual user setup files — To start Ansys TurboGrid without using full pathnames every time you want to run the Ansys TurboGrid software, your path must be altered to include the Ansys TurboGrid directory. This can be done by adding the following line to the .login and .cshrc files in your home directory:
set path=(cfxroot/bin $path)and these lines to the .profile file in your home directory, and also the .bash_profile if it exists:
PATH=cfxroot/bin:$PATH
export PATH
and these lines to the .dtprofile file in your home directory:
PATH=cfxroot/bin:$PATH \
export PATH
With the path altered in this way, you can start Ansys TurboGrid in the current
working directory by typing cfxtg.
Modification of system setup files — The system administrator modifies the setup files ( normally
etc/profile), which are run by all users during
login, to include the directory
cfxroot/bin in the
command search path. While this method has the advantage that only one file
must be modified to allow all users to use the software, it:
Affects users regardless of whether they use Ansys TurboGrid
Can only be done by the root user
Is system dependent
Refer to your system documentation for information about which files to change for your workstations.
To create setup files to be merged or run manually, start the Ansys CFX Launcher using the command:
cfxroot/bin/cfx5and select . This
option runs
cfxroot/bin/cfx5setupuser
that modifies your setup files or writes the necessary commands to files, which
you can merge manually with your existing setup files.
If you choose to modify your setup files, you will see a message indicating that your setup files have been changed. You will then need to log out and log in again or source your setup files before you can use the software.
User setup can also be run from the command line by entering:
cfxroot/bin/cfx5setupuserEnter the flag -h to view the optional commands.
To start Ansys Fluent without using full pathnames every time you want to run the Fluent software, your path must be altered to include the Ansys Fluent bin directory. You can do this in the C shell and its derivatives by entering:
set path = (/ansys_inc/v242/fluent/bin $path)
or in the Bourne/Korn shell or bash, by entering:
PATH=(/ansys_inc/v242/fluent/bin $path) export PATH
We recommend adding these statements to your $HOME/.cshrc (C shell), $HOME/.profile (Bourne/Korn shell), or $HOME/.bashrc (bash shell) file for regular use.
After installing the Ansys Fluent software, you will need to reset the default values in the Ansys Fluent launcher as follows:
Verify that the FLUENT_INC environment variable is not set.
Remove the FLUENT_INC setting from your .cshrc, .profile, or .bashrc file if you have added it for previous versions. Verify that the environment variable is unset by typing:
printenv FLUENT_INC
This command should not return anything.
Add the following paths to all users' login startup files:
<
install_dir>/ansys_inc/v242/fluent/binRun the following command:
<
install_dir>/ansys_inc/v242/fluent/bin/fluentClick .
Click when asked if you want to discard the LAUNCHER history.
Click if you do not want to start Fluent at this time. The new defaults will have been saved.
Refer to the Ansys Fluent Quick Start Guide for more information.
Polyflow no longer requires the FLUENT_INC environmental variable. It should be deleted as is recommended for Fluent:
Remove the FLUENT_INC setting from your .cshrc, .profile, or .bashrc file if you have added it for previous versions. Verify that the environment variable is unset by typing:
printenv FLUENT_INC
This command should not return anything.
The following post-installation procedures apply only to the Ansys ICEM CFD product.
Add the following paths to all users' login startup files (that is, .cshrc or .login files).
/ansys_inc/v242/icemcfd/linux64_amd/bin Add the following environment variable to all users' login startup files.
ICEM_ACN - set to /ansys_inc/v242/icemcfd/linux64_amd Start Ansys ICEM CFD by typing
icemcfd.
The following post-installation procedures apply only to the AUTODYN product.
Add the following paths to all users' login startup files (that is, .cshrc or .login files).
/ansys_inc/v242/autodyn/bin
Software Launch
To launch FENSAP-ICE, execute:
<install_dir>/ansys_inc/v242/fensapice/bin/fensapiceGUI
Command Line Tools
To use Ansys FENSAP-ICE command line tools without using full pathnames, you will want to run FENSAP-ICE with your path altered to include the fensapice/bin directory. You can do this in the C shell and its derivatives by entering:
setenv PATH
<install_dir>/ansys_inc/v242/fensapice/bin/:$PATH
or in the Bourne/Korn shell or bash, by entering:
export
PATH=<install_dir>/ansys_inc/v242/fensapice/bin/:$PATH
We recommend adding these statements to your $HOME/.cshrc (C shell), $HOME/.profile (Bourne/Korn shell), or $HOME/.bashrc (bash shell) file for regular use.
To run fensapiceGUI or nti_3dview from the $PATH, without a leading access path, the environment must define the location of the installation directory. This is done by setting the NTI_PATH variable to the proper <install_dir>/ansys_inc/v242/fensapice/bin/ directory.
Launching Ansys FENSAP-ICE with a Wrapper Script
For convenience, a wrapper script can be set-up by the system administrator in order to quickly launch FENSAP-ICE along with any required environment variables. For example, a fensapiceR18.sh file could contain:
#!/bin/bash
export
ANSYS_LIC_DIR=<install_dir>/ansys_inc/shared_files/licensing/
<install_dir>/ansys_inc/v242/fensapice/bin/fensapiceGUI
$*
The script then requires to be set in the $PATH and have execution permissions set (chmod a+rx).
Workbench Extension
Some features of FENSAP-ICE are available in Workbench through the use of an extension. The plug-in is provided in the following directory:
<install_dir>/ansys_inc/v180/fensapice/workbench/FENSAPICE-WB
R24.2.wbex
While in Ansys Workbench, install the plug-in using the Extensions > Install Extension menu. You can then set it to load automatically at startup in the Extensions > Manage Extensions menu.
See Getting Started with FENSAP-ICE in Workbench for further details on running FENSAP-ICE in Workbench.
Ansys Licensing
The Ansys Licensing System is used by default. No special configuration is required if the Ansys License contains a feature enabling FENSAP-ICE and the Ansys R2024 R2 package is installed.
Ansys License Server Information will be recognized from the environment variables set on the system. See the Client Environment Variable Settings section of the Ansys Licesing Guide for more information.
If the NTI_LICENSE_FILE environment variable has been set, FENSAP-ICE will instead use legacy NTI FLEXLm licensing. To force the use of Ansys Licensing and ignore the NTI_LICENSE_FILE option, set an environment variable as ANSYS_LICENSE_FILE_ONLY=1
NTI Licensing
Legacy license keys from prior to Ansys R2024 R2 use the NTI FLEXLm license system. The option for NTI licensing must then be enabled in the licensing.txt file <install_dir>/ansys_inc/v242/fensapice/config/licensing.txt or by setting up the NTI_LICENSE_FILE environment variable.
Modify the licensing.txt file to contain the license server information NTI_LICENSE_FILE=port@server.
The default port is 27000.
For instructions on how to set-up the NTI license server or on how to force a specific licensing system, refer to the appropriate sections in the FENSAP-ICE Manual.
The following post-installation procedures apply only to the Ansys Sherlock product.
To launch Ansys Sherlock, execute:
<install_dir>/ansys_inc/v242/sherlock/runSherlock
To use Ansys Sherlock without requiring the full pathname, add the following paths to all users' login startup files (this is, .cshrc or .login files)
/ansys_inc/v242/sherlock/ansys_inc/v242/sherlock
ACP — When running ACP on Red Hat Enterprise Linux 7, the libpng12 and compat-libtiff3 libraries are required to be installed. You can install these by issuing the following commands with superuser privileges:
yum install libpng12 yum install compat-libtiff3