We tried this and it works pretty slick. Unfortunately, I am not at libery to release the code. Our splitter makes separate prologue, process and protocol (thread) files in a netcfg directory. Our ‘mknetcfg’ script puts things back together again, but adjusts port and hostname assignments based on a table. This allows us to migrate more easily from one environment to another (like test to validation to production). I’m still working on fixing directory names for some file-localhost threads.
For liability and on-going support reasons, we would like to see Quovadx move forward with this enhancement request. Using customer (or shared) code to modify NetConfig files has some significant drawbacks.
- Mark Thompson
HealthPartners
