TIBant™ v18 Released

Automate My Way To Production TIBant v18 has been released and now provides support for no-outage deployments.

Features Implemented:

  • No Outage Deployments

    The `deploy` target will do a rolling restart of impacted BW instances, using AppStatusCheck to make sure each instance is running before moving onto the next. This means that in HA scenarios, there will be no outage.

  • Add Support for AppStatusCheck

    An `appStatusCheck` task will set ant properties with the current application statuses, using AppStatusCheck under the covers. An `instanceStatusCheck` task will do the same for a particular instance and can be used as a condition to check for a particular status.

TIBant is the premier build automation framework for TIBCO ActiveMatrix BusinessWorks™ and allows you to free up your time so that you can spend more energy and development dollars on delivering crucial integration and services and less time on the basics of writing the scripts necessary to get your code built and into production.

TIBant™ v17 Released

TIBant v17 has been released.

TIBant is the premier time-saving build and deployment automation framework for TIBCO ActiveMatrix BusinessWorks™ allowing you to spend less time on writing those scripts necessary to get your code built and into production and more energy and development dollars on delivering crucial integration and services.

Features Implemented:

TIBant™ v16 Released

TIBant v16 has been released.

TIBant is the premier build and deployment automation framework for TIBCO ActiveMatrix BusinessWorks™ and allows you to free up your time so that you can spend more energy and development dollars on delivering crucial integration and services and less time on the basics of writing the scripts necessary to get your code built and into production

Features Implemented:

  • Support Checkpoint Repository Source for `configure-ear`

    The `configure-ear` now supports selection of a checkpoint repository and table prefixes.

    The checkpoint repository and table prefix are set the following deployment properties.

    #par#-checkpoints-selected=<<resourcre name>>
    #par#-checkpoints-tablePrefix=<<database table prefix>>

  • Add support for starting the engine in the same JVM as Ant

    Previously, running BW engines used the `bwengine` to start the engine and TIBCO Hawk to stop the engine it. This could result in situations where it was not possible to stop the engine, due to Hawk not being correctly configured or if Hawk was not running.

    To overcome this, TIBant now provides additional macros for starting and stopping a BW engine within the same JVM as the Ant script, which ensures that the engine will stop when the Ant script completes.

  • Automatic TIBCO Path Detection

    Previously the paths for the various TIBCO products had to be set manually via Ant properties. TIBant will now try to determine the TIBCO product paths automatically, if the TIBCO product path properties have not been set.

Defects Fixed:

TIBant™ v15 Released

TIBant v15 has been released.

Features Implemented:

Defects Fixed:

TIBant is the premier build automation framework for TIBCO ActiveMatrix BusinessWorks™ and allows you to free up your time so that you can spend more energy and development dollars on delivering crucial integration and services and less time on the basics of writing the scripts necessary to get your code built and into production.

TIBant™ v14 Released

Download

Its free!

Get Support!

From only USD490.00/year

TIBant v14 has been released.

Bugs Fixed and Features Implemented in v14

TIBant is the premier build automation framework for TIBCO ActiveMatrix BusinessWorks™ and allows you to free up your time so that you can spend more energy and development dollars on delivering crucial integration and services and less time on the basics of writing the scripts necessary to get your code built and into production.

TIBant is free and it’s open source, but it also comes with extremely affordable enterprise support options. Free or with support, take your pick, you can’t fail to win.

TIBant™ v12 Released

Download

Its free!

Get Support!

From only USD99.00/year

TIBant v12 has been released.

Bugs Fixed and Features Implemented in v12

TIBant is the premier build automation framework for TIBCO ActiveMatrix BusinessWorks™ and allows you to free up your time so that you can spend more energy and development dollars on delivering crucial integration and services and less time on the basics of writing the scripts necessary to get your code built and into production.

TIBant is free and it’s open source, but it also comes with extremely affordable enterprise support options. Free or with support, take your pick, you can’t fail to win.

TIBant™ v11 Released

TIBant v11 has been released.

TIBant™ is the premier build automation framework for TIBCO ActiveMatrix BusinessWorks™ and allows you to free up your time so that you can spend more energy and development dollars on delivering crucial integration and services and less time on the basics of writing the scripts necessary to get your code built and into production.

TIBant is free and it’s open source, but it also comes with extremely affordable enterprise support options. Free or with support, take your pick, you can’t fail to win.

To see what’s new in TIBant v11, have a look at TIBant’s Closed Defects and Implemented Features List.

TIBant™ Exits Beta with Version 1.4.0

TIBant is out of Beta! Here at Windy Road we are really happy to finally bring to you a version of TIBant that we feel is ready for prime time. We’re sure you’ll be as happy using TIBant as we are bringing it to you. But don’t think that now that it’s out of Beta we aren’t going to develop it any more. We’ve still got some more features planned and we would really like to know what features you would like to see in future TIBant releases. While your at it, let us know what your favourite TIBant feature is.

So, what’s new in TIBant 1.4.0? We’ll over here we like to call it the Validation release. Since version 1.2.1 you’ve had the to option to validate Business Works projects. Then in version 1.3.1 we added the option to validate before your build a Business Works EAR or library, but it’s always been an on or off affair. If you turned validation on and there was an error, the build would fail. But what if your project doesn’t validate, but you know it works. For instance you might be using the preceding-sibling axes, which works just fine, but the validator thinks is an error. Up until now you would have to turn of validation for the entire project and deal with the risk of invalid EARs, but not any more.

TIBant 1.4.0 allows you to specify the number of errors you expect when you validate your project. For instance, just say you use preceding-sibling in two places. You validate your project and it has two errors. You confirm the errors are from the use of preceding-sibling and you set expected-errors to 2 in the input to validate-project or validate-expected-errors to 2 in the input to build-ear or build-library. Now when the project is validated, it will pass if you have 2 errors and otherwise fail. Now you can be sure that you aren’t introducing any more validation errors.

While we were looking at validation errors, we thought we may as well look at validation warnings as well, so TIBant now has a max-warnings option for validate-project and a validate-max-warnings option for build-ear and build-library. As you can guess, it allows you to fail the build if the number of validation warnings goes above the number specified. Nice!

These aren’t the only reasons why we call it the Validation release. In the last release we added checks to really let you control and manage your Business Works global variables. Well, this time we’ve added some validation around Adapter SDK Properties as well. For those in the know, there’s a little file at <TIBCO BW Home>/lib/tibco/deployment/bwengine.xml that controls what Adapter SDK Properties can be set within an EAR. If a property you want to use is not in that file when you build your EAR, then you won’t be able to set it using AppManage (even if you add it to your configuration XML) or TIBCO Administrator. Not a nice situation to be in when you realise it hasn’t been set in production and in order to turn it on, you need to rebuild the EAR (I hope you can trace it back to the correct revision in source control) and redeploy. To avoid these types of problems, configure-ear will now fail if you have a property in your adapter-sdk-properties-refid propertyset that’s not available to set in your EAR (assuming you produced the template XML using extract-config).

On top of that we have some bug fixes for you and a new Alpha feature for you to play around with. Quite often you want to be able to produce a WSDL from a service agent. So far your options have pretty much been limited to saving it manually from within TIBCO Designer or waiting till it’s deployed and using the built in resource provider. TIBant 1.4.0 now gives you a third option, the build-wsdl-ALPHA macro. build-wsdl-ALPHA uses the existing bw-start and bw-stop macros to run the bwengine locally, so the built in resource provider can be used to retrieve the WSDL without having to deploy the engine. There’s a question about build-wsdl-ALPHA‘s implementation that we are not 100% sure about yet, which is why we are giving it an Alpha status. If you are interested in this feature, please weigh in and let us know your thoughts.

That’s pretty much it for this release, but feel free to have a peak at the full list of Closed Defects and Implemented Features.

Tame Your Business Works Global Variables with TIBant™ 1.3.2

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.

There is some more information in the release notes and even more in the TIBant User Guide, which you can download along with the binary distributions.