We all know that one little application option can make all the difference between a working solution and something that appears to be completely broken. Similarly, we have also all encountered the situation where something was working and then suddenly stops working – often because a standby component has kicked in and we forgot to change an application option on both the primary and the backup components (a sackable offence in my opinion 🙂 )
This situation is often compounded when there are multiple Genesys environments to manage as is the case on my current project were we have the luxury of development, non production and production environments.
Whilst framework 8 has introduced some useful configuration auditing it still leaves a lot to be desired and does not address the issue of multiple environments.
Therefore this week I wrote a Configuration Audit application in C# .NET using the platform SDK to read CME objects as well some other configuration elements such as the actual .EXE version deployed for each application, SQL server database and instance information, Virtual Hold (VHT) options (of which there are many) and GVP / EMPS configuration via LDAP.
The output from each environment is a single text file which I can then compare across environments using WinMerge (http://winmerge.org/). Equally within the same environment the tool can also be used to output the options for high availability pairs and compare them.
The screenshots below show the differences between two configuration snapshots taken in the same environment before and after the weekend.
I have now configured a scheduled task in all environments to take a daily configuration snapshot which should make change and release management much easier in the future.