The 1.3.0 release brings support for Runtime and Instance Runtime Variables. Runtime variables are Global Variables that are set per Process Archive. For instance, say you had a Enterprise Archive with two process archives. Normally any Global Variable settings would apply to both Process Archives. With Runtime Variables, they can use the same Global Variable with different values. Instance Runtime Variables are a similar concept but these are set per Process Archive Instance. So, just say you had a Process Archive that uses a HTTP receiver and you would like to load balance it, but only have one machine to deploy it to. By setting appropriate Instance Runtime Variables, you can have both running on the same machine, listening on different ports. Whack a load balancer in front of them (for Services, you can use TIBCO Active Matrix Policy Manager as the proxy) and you’ve slightly increased the availability of your application.
The most relevant change for existing users, is that ant-contrib is no longer loaded automatically when you import TIBant. Instead you need to call the
load-ant-contrib macro before calling any of the other TIBant macros. The example project shows how this is done.
As usual the release notes are over at Assembla.
TIBant™ is distributed under the terms of the GNU Lesser General Public License (LGPL).