When we are developing our TIBCO BW 6 application the last thing we need to do to deploy our application is to generate an EAR file, so you can deploy it in your different servers. And today, the idea is to show you another way to do that, and it is very quick! It’s an idea I never used before because I didn’t know about it but I read it on the official documentation and it was so great. Because of that, I want to tell you about. Let’s start.
In the previous post we talk about one feature (the format-dateTime XPath function) which behavior on TIBCO BusinessWorks 6 wasn’t the same that on BusinessWorks 5, but today we are going to talk about another similar situation.
On BusinessWorks 5 it was usual to have Dynamic Call Processes, so you could invoke one SubPorcess or another depending on the data you have on real-time. This features is present on the BusinessWorks 6 version but to do that it’s not that easy or, at least, are not the same set of steps you have to do.
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?
– 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.
If you are a developer that are migrating from TIBCO BW 5 to TIBCO BW 6 and you have been working a bit with the new tools, you are probably aware that you don’t have a onStartup or onShutdown starter process like you have on your TIBCO BW 5 Designer. So, is it posible to have a process that execute when the application is starting or have we lost a useful feature? No, don’t worry my friend. You keep your same features but you have to do it using a different approach, but you are going to have the same functionality. Do you want to see it? Ok, let’s go for it!
In this post the idea is to talk about one of our “new friends” in TIBCO AMX BusinessWorks 6.x.
Its name is “bogusroot” and probably you haven’t heard from it. This is a new friend that is here to help us in our TIBCO BusinessWorks development but in a way that you have never imagined.
This is not a new killer-app for our BusinessWorks projects. Neither it is a new methodology to make that all your processes ends successfully. Neither is a plug-in or tool inside our new TIBCO BusinessWorks Studio for Designer. So, what is it?
It is only a XSD element definition provided OOTB by TIBCO. But, what make him so important?
Usually when you are creating a plug-in it is possible that you want to make changes on your model. For example, if you are working on a Input Adapter like the one we are creating here for RabbitMQ it is common that you want to support send data as String or as a ByteArray, and you want if you are going to send a String the input text to set the data should be coded as a String and if you want to send binary date (ByteArray) you want that the input text will be set like a binary field. This behavior it is common of the default activities at BusinessWorks. One example of that behavior it is on the Parse XML activity:
Ok, We understand now the behavior, but how can we do something like this? Ok, let’s go!
In the previous post we talked about how to create our activities through the wizard the TIBCO BusinessWorks Studio for Designers gives us when we have installed the plug-in Development Kit, but when we want to add our configuration items at the activity we have two defaults options: “General” and “Advanced”.
But if you look at the built-in activities some of them have custom categories when it specifices some of the configuration. So, how we can do the same with our activities? Ok. Let’s do it!
The only thing we have to do, if in the moment we are creating the activity configuration items, do not check none of the defined value (General and Avanced) but to type the one you want. For example, as you can see here:
And that’s everything when you build the plug-in and use if inside your processes you are going to see something like this: