Setting environment variables

Simulation Compute Manager environment variables override service parameters and apply to all versions of SCM installed.

Windows installations

Set the environment variables at the SYSTEM level and then restart the "Autodesk Simulation Compute Manager" service in the Windows Services app for SCM 1.X versions. Beginning with SCM 2.0 the major version of SCM is added to the name and it appears as "Simulation Compute Manager X".

Linux Thinclient installations

Set the environment variables and then restart the service manually.

Linux RPM installations

Where the SCM is running as a systemctl managed service, use one of these methods to set the environment variables so they are visible to the service:

1. Edit the /usr/lib/systemd/system/adskscmX.service file directly, where X is SCM major release, for example /usr/lib/systemd/system/adskscm2.service.

2. Edit the service with the systemctl edit command

After editing, the environment variable(s) will be listed in the [Service] section of the service file in the format Environment==. An example using the SCM_RETRIES environment variable is below.

[Unit]
Description=Autodesk Simulation Compute Manager @BUILD_MAJOR@ daemon
Wants=network-online.target
After=network-online.target

[Service]
Type=forking
User=scm
Group=scm
ExecStart=/opt/Autodesk/simulation-compute@BUILD_MAJOR@/bin/SimulationCompute --daemon --pidfilename /var/tmp/scm@BUILD_MAJOR@.pid.lock
PIDFile=/var/tmp/scm@BUILD_MAJOR@.pid.lock
Environment=SCM_RETRIES=20

[Install]
WantedBy=multi-user.target