Controlling System Behavior › How to Modify the System Environment
How to Modify the System Environment
CA SDM uses environment variables specified in the environment template file (NX.env.tpl) to determine certain behaviors. You can use environment variables to modify some system behaviors. You typically use the Options Manager to control system behavior, but at times CA Technical Support instructs you to modify a particular environment variable directly.
Consider the following when editing the environment template file:
- Environment variables set in this file can be overridden by setting the environment variable in the process space in which a process runs. Although convenient in some limited cases, this setup is usually not wanted. Preceding a variable setting with an at symbol (@) prevents variables in the process space overriding the variable. Unless there is a specific reason for allowing an override, the @ symbol always precedes the variable name in the template file.
- The comment characters for this file are pound (#) and exclamation point (!). The exclamation point character is also used to disable an option.
Important! Modify the template file (NX.env.tpl) and allow the configuration process to apply the changes to the environment file. Never modify the environment file (NX.env) directly, including on your client or secondary server installations.
To modify environment template file
- Back up of the environment template file (.tpl) that corresponds to your system environment:
- UNIX—$NX_ROOT/pdmconf/NX.env.tpl.
- Windows—installation‑directory\pdmconf\NX.env_nt.tpl.
- Edit the environment template file on the primary server. You can view and modify this file using any text editor (Windows users use WordPad).
- Make the changes as instructed by your support technician, and save the changes.
- Run the configuration utility on your primary server installation to apply the changes you made to the environment template file to the actual environment file.
Note: For information about how to run the configuration utility, see the Implementation Guide.
- Stop and restart the CA SDM primary server for the changes made to the environment file to take effect. To avoid shutting down your system, your support technician can instruct you to stop and restart only certain processes rather than recycling your entire CA SDM server.
