Creating User-Specific Configurations

To protect against unplanned configuration changes, Enterprise Server for .NET configuration files install to a location that has read-only access to users.

However, you can create override configurations that are used only by specific users. When applying configurations, an Enterprise Server for .NET process performs the following:

• The operating system looks for the executable's application configuration file in the same folder as the executable.

  In a 64-bit system, the Server EE for .NET executables are installed in C:\Program Files (x86)\Micro Focus\product name\binAnyCPU\SEE. For example, the seelistener.exe.config file in this folder processes when seelistener.exe runs.

• The Enterprise Server for .NET executable then looks for a corresponding configuration file (that is, a configuration file with the same file name) in a location that is specific to the user.
• The Enterprise Server for .NET executable combines the two configurations, and uses any corresponding settings from the user-specific location file to override the settings in the configuration file.

The user-specific location is %APPDATA%\Micro Focus\SEE\<release number>\Config where <release number> is the release number of the software.

The %APPDATA% environment variable is set by the operating system, and refers to a user-specific folder:

You can create the following user-specific configuration files:

• seeconsoleviewer.exe.config
• seedeploy.exe.config
• seedispatch.exe.config
• seelistener.exe.config
• seemonitor.exe.config
• seerdfconv.exe.config
• seesep.exe.config
• seestart.exe.config
• seestop.exe.config