Different behavior format-dateTime between BW5 and BW6

When you are moving from TIBCO BW 5 to TIBCO BW 6 you probably have found everything in the same place. Of course, there are a lot of changes regarding the architecture and the base of both of the versions, but if you are “only a developer” you probably have find the same activities and the same tools you need to create your process. But, you have to be aware of a few things, and one of them is the one I’m going to explain to you right now:

– There are functions that are not working the same they did on previous version?

– Whaaaaaat?

– That’s impossible! If they things are not working like they were I’m not be sure if what I am creating is going to work!!!

Ok, ok, Keep calm! Don’t get there yet!! That’s only some of the functions we have in our XPath toolbox are not working as expected and one of them is format-dateTime.

Continue reading

TIBCO BW 5.X – SCM Capablities

Normally when you are working with TIBCO BW or any other tool that produce source code, you need a Software Configuration Management tool to manage all that code. These tools have been along with us all our life, from CVS to Git, from SVN to Mercurial.. we have plenty of options when we want to manage this kind of artifacts but our choices depends on the ones that are supported for the tools we are using.

In our case, inside the TIBCO BW 5.x world, we have two main options to manage our code that you can choose to meet your goals. The first and most usual is to manage the files that compose your BW5.X project at a file level from the File Explorer and not inside the TIBCO Designer tool.

This option has the main advantage that every SCM that is supported on your OS can be used to manage your files. That’s the option that I use when I share BW 5.x sample projects with all of you in my posts because I want to have a Git support that cannot be get with the other option.

Continue reading

How to specify the Content-Type in your API REST

In the previous posts we talked a bit about how to create your REST Interfaces. Usually, when you are developing this kind of interfaces you use a JSON format in your payload. But, there is no default way to tell that to your API that the content-type that is replying is JSON. So, in this post I’m going to tell you how to do it.

Continue reading

TIBCO BW 5.X – Compatiblity with SWAGGER

In the previous post, we talk about how to create a REST API using TIBCO BusinessWorks 5.x and the REST and JSON plug-in. If you missed that post you can take a look at it.  In this post we create an REST API and use it a WADL file to define and to create the request in the SOAP UI.

But, this is not the only way to do it. The WADL file always have been an artifact not so used in the REST world. Normally, when you try to it to document a REST service you don’t use a WADL file. In the previous days, you use a formal document or web page to explain the call you have to do, the parameters and so on. That’s the way, for example, Amazon or IMDB did with their REST API, but almost nobody was using the WADL file.


To cover this gap, a few years ago, we have another alternative call Swagger. If you take a look at the Swagger official website, you have this description:

Swagger is a simple yet powerful representation of your RESTful API. With the largest ecosystem of API tooling on the planet, thousands of developers are supporting Swagger in almost every modern programming language and deployment environment. With a Swagger-enabled API, you get interactive documentation, client SDK generation and discoverability.

And TIBCO BusinessWorks 5.x have SWAGGER compatibility, specifically with the 1.2 version. That’s a pity because the current version is the 2.0 and it brings a lot of new features and it’s now a non-official standard. Continue reading

TIBCO BW 5.X – Creating an API REST using the REST Plug-in

Normally when we create our process we include an input protocol to comunicate our process with the outside world. We can use a lot of technologies to do this expose to the outside, but normally the usual choices are HTTP and JMS. And when we talk about HTTP normally we are talking about WebService using HTTP/SOAP as the protocol.

But, nowadays it’s more common to have to deal with REST interfaces and also to expose a REST interface as a default option or as a second option (device oriented in most cases). Ok, so in this post we are going to see the main stepts to create an API REST in TIBCO BW 5.X. Continue reading

[BW5.X vs BW6.x] Differences working with Java Code (I)

For the last year I’ve been doing different posts about how to include Java Code inside our TIBCO BW processes to increase or extend the functionality the tool provide us. I’ve been doing this kind of work for both of the “current” versions: The 5.x series and the 6.x series.

And, if you have been awared or if you have been the oportunity to work with both tools you have seen some difference in the way and the posibilities you have using one or another tool. We are going to talk a little bit about them in this post.

Continue reading

Using a Java Code Activity in BusinessWorks 5.x

Until now, I didn’t think that a post about how to use properly the Java Code Activity has any value for any of my readers. But, now, after a few questions I’ve received by mail I think it could be useful because the TIBCO AMX BW doesn’t have the same user profile than I used to think. So, let me put this in other way.

I have a strong technicak background with my C.S Bachelor and I am a full-stack developer in different languages (Java, Python, C++, Scala..) so in my vision explain how to use this kind of activities is not worth it. But, that’s because I used to forget that the TIBCO AMX BW is a high-level tool that can be used by people with full technical background or with people with a little background. For the seconds group could be difficult to understand how to use this kind of activities that have almost nothing in common with the other ones.

Continue reading