|
(Initial Section Addition about Dynamic Environment Variables Added)
|
(→Dynamic Environment Variables)
|
| Line 52: | |||
| When the agent is restarted, it will first look for the setenv script. If the script is found, it will be executed to update (or write out) the env.properties file. Then, the new variables in the env.properties file will be delivered to the AnthillPro server. | When the agent is restarted, it will first look for the setenv script. If the script is found, it will be executed to update (or write out) the env.properties file. Then, the new variables in the env.properties file will be delivered to the AnthillPro server. | ||
| + | == Prerequisites == | ||
| + | * Access the agent's /bin directory. | ||
| + | * Ability to write a shell script that can generate the environment variables in the proper format. | ||
| + | == Add Files to Agent's /bin Directory == | ||
| + | #Stop the agent. | ||
| + | #Create setenv file. In a text editor, create the setenv.bat file if the agent is running on Windows or setenv.sh file if the agent is running on a UNIX-like system. Save it to the agent's /bin directory. | ||
| + | ##You will need to have the shell script read the environment variables and then writes them out to the env.properties file. The script should be similar to this example below: | ||
| + | ##<font style=monospace>echo DYNAMIC_ENV_VAR=value > env.properites</font> | ||
| + | ###Note that the env.properties cannot reference other environment variables such as ''PATH=%PATH%'';..., etc. | ||
| + | ###AnthillPro requires the variables to be set using this exact pattern. | ||
| + | #Restart the agent. Upon restart, the variables will be updated. To update the environment variables in the future, simply restart the agent again. | ||
