Before we can start the Endur services, we need to build the config files that each of them will use to define environment variables, system classpaths etc. These config files will be built as part of the Code Upgrade process run above, so this step is to check them.
In the fileshare for the environment, there will be a ‘Resources’ folder, where the config files are held. These will be built against the template version specified in the Environment’s ‘EndurConfigTemplates’ application allocation.
There will be 4 Endur config files and one Spread:
- Endur_<EnvName>_GUI.cfg – This is a file used by Endur if AD Authentication is used for Single Sign On. This is not the case at Trailstone. The ESS component does not support AD Authentication, so SQL login is used for Endur instead.
- Endur_<EnvName>_noAD.cfg – This is the file that is used when User (GUI) sessions are run at Trailstone. This is referenced as part of the Citrix connection parameters that kick off the application.
- Endur_<EnvName>_x86.cfg – This is used by the Endur runsites that run the 32-bit Endur code, and it holds specific details for 32-bit components such as Connex Interfaces (Trayport, ECMS, ESS)
- Endur_<EnvName>_x64.cfg – This one us used by the Endur runsites that use the 64-bit Endur code.
- Spread_<EnvName>.cfg – This is the config file used by the Spread windows service to specify the networking components for the Spread integration to function within an environment. It contains the details specified in two of the Environment Wide Settings (OverrideSpreadIPRange and EnvSpreadPort).
0 Comments