This section has been extracted from the ACS Overview document, chapter 5
The configuration of ACS is determined by a number of environment variables.
Generally, these variables are set to a proper default value by the default login script whose template is available in $ACSROOT/config/.acs/.bash_profile.acs. Each user has to take care of copying this script in his home directory (typically in the .acs directory), eventually adapting it and executing it to prepare the environment.
Some variables have been already described in the previous sections, but we give hereafter a list of the most interesting ones.
ACS_CDB (default: $ACSDATA/config/defaultCDB)
Location of the configuration database files to be used when cdbjDAL is started.
ACSDATA
The root directory where all ACS configuration files (including
Configuration Database files) are stored.
By default it is /alma/ACS-2.0/acsdata.
ACS_INSTANCE (0..9, 0 if unset)
Based on this environment variable (and/or the –b <ACS_instance
#> option for most ACS commands) ports used by ACS services and
processes are automatically calculated
according to the rules described in section 6.
Users selecting two different values for ACS_INSTANCE will work without
interfering.
ACS_LOG_STDOUT
Control the amount of information sent to stdout.
By default, only LM_INFO log messages are sent to stdout.
See section 2.3.6.1.
ACS_NAME_SERVICE (default:
$MANAGER_COMPUTER_NAME:4000/NameService)
CORBA Initial Reference for the Naming Service.
Usually the reference of the Manage is sufficient for applications, but
some
special applications, like cdbjDAL need it.
ACSROOT
The place where ACS CMM modules are installed. For ACS 2.1
this is typically:
/alma/ACS-2.0/ACSSW
ACS_TMP ($ACSDATA/tmp/,
when not set)
The path where all ACS temporary files are written.
This environment variable “cooperates” with the following other
variables to
allow specifying in a flexible way where ACS temporary files are
written:
· ACS_LOG_FILE
· ACS_BACI_RECOVERY_FILE
· ACS_RECOVERY_FILE
The following policy is used to determine where an ACS temporary file is written:
· if none of the above is defined, all files are put in the $ACSDATA/tmp directory
· if ACS_TMP is defined, then temporary files are put in the ACS_TMP directory
· if ACS_LOG_FILE, ACS_BACI_RECOVERY_FILE or ACI_RECOVERY_FILE_NAME is/are defined than file(s) should are created using the env. variable(s) and ACS_TMP is ignored
The utility function getTempFileName() allows applications to generate a temporary filename according to this policy.
ALMASW_RELEASE
The current ACS release. For ACS 2.1
this is ACS-2.0.
This is (together with ALMASW_ROOTDIR) the main variable used to derive
all
other environment variables; for example, ACSROOT is built as:
$ALMASW_ROOTDIR/$ALMASW_RELEASE/ACSSW
Users can overwrite the default
value to switch between different versions of ACS.
ALMASW_ROOTDIR
The root directory for all ALMA ACS software components and all
releases.
This is (together with ALMASW_RELEASE) the main variable used to derive
all
other environment variables.
By default it points to /
INTROOT
The integration area where user software is installed.
Typically each user has their own
integration area.
See the ACS Installation Manual[3]
for details
MANAGER_REFERENCE
CORBA Reference for the MACI Manager (see section 2.3.9.1
for details)
NAMESERVICE_REFERENCE
CORBA Reference for the Naming Service (see section 2.3.9
for details)
CLASSPATH
form: <JARFILE01>:<JARFILE02>:<JARFILE03>
used by: Java runtime and compile time
Tells Java where to look for Java class files
JAVA_HOME
form: <DIRECTORY>
used by: Java tools
Tells Java/Java tools where to find the Java installation currently being used.
ACE_ROOT
form: <DIRECTORY:$ACE_ROOT_DIR/linux>
used by: ACS environment initialization
This tells where ACE is installed (used by ACE)
ACE_ROOT_DIR
form: <DIRECTORY>
used by: ACS environment initialization
ACS environment variable which tells where the various architecture specific versions of the ACE wrappers can be found
ALMASW_RELEASE
form: <DIRECTORY>
used by: ACS environment initialization
Tells what is the version of the current ACS system
ALMASW_ROOTDIR:
form: <DIRECTORY:/alma>
used by: ACS environment initialization
Tells
where the root of all
ALMASW_INSTDIR
form: <DIRECTORY:$ALMASW_ROOTDIR/$ALMASW_RELEASE>
used by: ACS environment initialization
Tells
where
ANT_HOME
form: <DIRECTORY>
used by: ACS make system
Tells where the ANT make system can be found
OMNI_ROOT
form: <DIRECTORY>
used by: ACS make system
Tells where OmniOrb is installed.
OMNIORB_CONFIG
form: <DIRECTORY:$OMNI_ROOT/config>
used by: OmniOrb
Tells where the configuration files for OmniOrb are found.
IDL_PATH
form: -I<DIRECTORY> -I<DIRECTORY> -I<DIRECTORY>
used by: ACS make system
Where to find IDL files.
JACORB_HOME
form: <DIRECTORY>
used by: ACS make system
Where JacOrb is installed.
PYTHON_ROOT
form: <DIRECTORY>
used by: ACS make system
Where Python is installed
PYTHONPATH
form: <DIRECTORY01>:<DIRECTORY02>:<DIRECTORY03>
used by: Python tools
Where Python source files can be found
GNU_ROOT
form: <DIRECTORY>
used by: <<UNKNOWN>>
Where ACS shipped GNU tools are found.
TCLTK_ROOT
form: <DIRECTORY>
used by: ACS make system
Where ACS shipped TCL/Tk
LD_LIBRARY_PATH
form: <DIRECTORY01>:<DIRECTORY02>:<DIRECTORY03>
used by: dynamic loader, ACS containers
Specifies where share libraries can be found.
PATH
form: <DIRECTORY01>:<DIRECTORY02>:<DIRECTORY03>
used by: Unix shells, ACS make system
Specifies where binaries can be found for shell & makefiles