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

Advertisements

Bogusroot – Our new BW6 friend :)

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?

Continue reading

Working with CDATA inside your BusinessWorks Process

One of the most misterious things when you are working with your TIBCO BusinessWorks software is how to handle the CDATA sections inside the XML you are transforming in the BW process.

The CDATA section are special XML sections when you can use unescaped text (like XML tags or similar) as a XML tag value, as you can see here:

<script>
<![CDATA[
function matchwo(a,b)
{
if (a < b && a < 0) then
  {
  return 1;
  }
else
  {
  return 0;
  }
}
]]>
</script>

If you want to increase your knowledge about this sections, please visit this link: Link

The main problem you could be facing when you are trying to use this kind of section in BW is that the software always try to scape this kind of values and it not check if it is a CDATA section or something special. It always treats the value as a normal string value and it executes the ‘escape process’.

Continue reading