When you have a large and complex environment, it can get tedious to validate the configuration of all the applications within it and find erroneous configuration.
When you use GEM Automation and its centralized configuration feature, it now becomes easier to assess the validity of that environment.
To validate the configuration of an environment with GEM Automation, you can simply call:
Assert-EnvironmentConfiguration.ps1 -selectedEnvironmentShortName <environment short name>
Here’s what is being tested in the current release:
- URLs (i.e. web services URL)
- Database connection strings
- Windows credentials
Here what happens with this script:
- The script will retrieve all the configuration settings at the Global scope
- It will then iterate through all of those and test them
- It will then fetch a list of all the applications managed by GEM Automation from the configuration database
- It will then get configuration settings for those application and test them
- It will then scan the actual configuration files of the applications when applicable to extract URLs present in the configuration file
- It will then get a list of credentials used by the application and validate those