TIBant‘s Property File to Engine Configuration Translation, has for some time allowed you to specify TIBCO Business Works engine properties (including global variables) for each of your environments in simple property files, which TIBant can translate into AppManage compatible configuration files. TIBant™ 1.3.2 comes with some great new features that will help you tighten up your control of your global variables and help prevent silly mistakes from happening.
Want to make sure that your Integer typed global variables actually get populated with an Integer? TIBant will do that. It will also type check your Boolean and Password typed global variables too.
Want to make sure that every global variable gets set, so when new global variables are added, they don’t get left pointing to Dev when you deploy to Prod? TIBant can make sure they get set. An optional flag on the
configure-ear macro will cause it to fail if any of the global variables in the template XML (extracted from the EAR) are missing from the specified global variables property set. But what if you have a few global variables that are OK to leave with their original template XML values? TIBant can handle that as well and allows you to specify a property set or global variables that don’t need to be set. It even allows you to specify a property set of global variables that should never be changed from their template XML values. Cool, hey?
These new options really allow you to put up some controls around your global variable configurations, so that you find out about mistakes when you’re building your configuration, not after you’ve deployed it to Prod.