This section provides some example scenarios that demonstrate how you can use Configuration Parameter Files.
Remember that both ACS and TDK process the Configuration Parameters in ShdConfig.par file first (if present). ACS then processes the Configuration Parameters in AcsConfig.par (if present) and TDK processes the Configuration Parameters in TdkConfig.par (if present)
The full path of the ItsShadow\Exe folder is not shown in the Scenarios. If you install Modeler to the default location, the full path of the ItsShadow\Exe folder is as follows.
Scenario 1: Default installation with no parameter file
Most users will not require the use of Configuration Parameter Files.
Scenario 2: A user wants some settings always changed on his computer
In this example, a user wants to change the ComDir folder on their computer for both ACS and TDK. The user creates the following files and content in their ItsShadow\Exe folder:
ShdConfig.par:
ComDirRoot=c:\MyPath
Scenario 3: A user wants some settings always changed on his computer, but wants different settings for ACS and TDK
In this example, a user wants to change the ComDir folder on their computer, but also wants to disable the generate and reverse buttons and check boxes in ACS and enable file backups on TDK. The user creates the following files and content in their ItsShadow\Exe folder:
ShdConfig.par:
ComDirRoot=c:\MyPath
AcsConfig.par:
# This prevents changing of the generate and reverse options on the ACS/TDK Control toolbar and ACS/TDK Settings dialog
FlagsSettingDisabled=1
TdkConfig.par:
# This enables file backups in TDK
EnableFileBackup=1
Scenario 4: A user wants to centralize the ACS and TDK settings on their entire network:
In this example, the Configuration Parameters are set through a centralized Configuration Parameter File.
ShdConfig.par:
# The following line references the configuration parameters in a single, server-resident
# configuration parameter file that holds corporate settings for ACS/TDK
ParamFile=H:\SettingsDir\CentralizedShdConfig.par
Scenario 5: A user wants centralized settings for ACS and TDK, plus some additional private settings:
In this example, the Configuration Parameters are set through a centralized Configuration Parameter File, and then additional parameters are set through the AcsConfig.par and TdkConfig.par files.
If the centralized Configuration Parameter File had set EnableFileBackup=0, that value would be reset by the EnableFileBackup=1 configuration parameter that appears in the AcsConfig.par and TdkConfig.par files.
ShdConfig.par:
# The following line references the configuration parameters in a single, server-resident
# configuration parameter file that holds corporate settings for ACS/TDK
ParamFile=H:\SettingsDir\CentralizedShdConfig.par
AcsConfig.par:
# The following lines are additional private settings for ACS
EnablePreserveTaggedText=1
EnableFileBackup=1
TdkConfig.par:
# The following lines are additional private settings for TDK
EnablePreserveTaggedText=0
EnableFileBackup=1
Scenario 6: A user wants centralized settings for ACS, but private settings for TDK
In this example, wants to use the centralized Configuration Parameter File for ACS, but not for TDK.
This example makes use of the ResetAllParams and PerUserconfiguration parameters. Alternatively, we could have moved the ParamFileconfiguration parameter from the ShdConfig.par file to the TdkConfig.par file.
ShdConfig.par:
# The following line references the configuration parameters in a single, server-resident
#configuration parameter file that holds corporate settings for ACS/TDK
ParamFile=H:\SettingsDir\CentralizedShdConfig.par
AcsConfig.par:
# The following lines are additional private settings for ACS
EnablePreserveTaggedText=1
TdkConfig.par:
# The following line unsets the configuration parameters that have been set by the server-resident
#configuration parameter file
ResetAllParams
# The following line is required so that TDK can find the ComDir folder it has been using.
PerUser=1
# The following lines are additional private settings for TDK
EnablePreserveTaggedText=0
# The following line was in the server-resident file and we still want to use it, so we set it again.
