Defining Environment Variables for Platform Manager Assets
When deploying Software AG Platform Manager configuration assets, you must ensure that environment variables are resolved and applied correctly after Platform Manager is restarted. The following list gives you guidelines on how to define environment variables for Platform Manager assets. The guidelines apply for all supported platforms.
Set global system environment variables at the operating system level. The ACDL file can resolve the global system environment variables when
Platform Manager is restarted using the
.sh|.bat or native service/daemon scripts. For example:
set ENV_VAR=BAR
profiles\SPM\bin\restart.bat
export ENV_VAR=BAR
profiles/SPM/bin/restart.sh
The ACDL file gets the value of BAR by referencing $ENV_VAR.
Use Java system properties in place of environment variables for the scope of
Platform Manager. You can set the Java system properties using the COMMON-JAVASYSPROPS configuration type. For example, you can set the "ENV_VAR1" Java system property in a
Command Central template:
COMMON-JAVASYSPROPS:
COMMON-JAVASYSPROPS: |
ENV_VAR1=BAR1
When Platform Manager is restarted, the ACDL file can get the value of BAR1 by referencing $ENV_VAR1.
Set environment variables for the scope of
Platform Manager by editing the
custom_wrapper.conf file, located in the
PlatformManager_directory\profiles\SPM\configuration directory. When
Platform Manager is (re)started, the ACDL file can resolve the environment variable using the value specified in the
custom_wrapper.conf file. For example, if you set the ENV_VAR2 in the
custom_wrapper.conf file:
set.ENV_VAR2=BAR2
The ACDL file can get the value of BAR2 by referencing $ENV_VAR2.