Managed and unmanaged options and environment variables:
An option that is visible in Options Manager can be installed, uninstalled, or changed via the Options Manager; alternatively, the option can be updated by running the appropriate pdm_options_mgr with required parameters while the CA Service Desk Manager service is running. The preferred method is to use Options Manager; if you use the method of running the appropriate pdm_options_mgr commands, then you must run 2 commands for each option - one command would include the "-t" parameter, and the other command would not.
Options that are available via Options Manager are managed options; options that are not available via Options Manager are unmanaged options.
Unmanaged options are directly implemented as environment variables and are not available via Options Manager; some of those, such as NX_SLUMP_HASH, would need to be updated by manually updating both the NX.env file and the NX.env_nt.tpl file.
The "pdm_options_mgr" command, when run with no parameters, connects to the mdb database, reads the entries in the Options table, reads the NX.env_nt.tpl file, and regenerates the local NX.env file accordingly. Unmanaged options and environment variables are not propagated to the new NX.env file if they do not exist in the NX.env_nt.tpl file - for those, you would need to update the NX.env file to add them back in.
A recycle of the CA Service Desk Manager service is required in order to apply all unmanaged, and some Options-Manager-managed, options.
Warning! In an Advanced Availability configuration, when version control is enabled whilst the CA SDM service is starting, both customizations and options are automatically synchronized with other running servers. Disabling version control by running "pdm_server_control -v" on a server, before recycling the CA Service Desk Manager service, avoids synchronization of both.
Warning! Advanced Availability servers must be stopped and started in a specific order. Any customizations that should or should not be propagated to other servers by the Version Control process must be considered before recycling the servers.
For more information about restarting the CA SDM servers in an Advanced Availability (AA) configuration, please review Restart the CA SDM Servers in Advanced Availability Configuration.
For more information about publishing customizations in an Advanced Availability configuration, please be sure that you understand the information in the subsection titled "Publish Schema Modifications" in How to Modify Schema Using Web Screen Painter that is specific to Advanced Availability and Version Control.