We have been a long time ago talking about the big change that is the new release of the TIBCO BusinessWorks producto, the 6.x series. So many new concepts, a new base using OSGi technology and TIBCO ActiveSpaces, new concepts that were not be in the 5.x series like the AppSpaces and AppNodes and you might be afraid of all this changes because you have a big set of BW5.x processes pretty functionals and you don’t want to loose all this work. But, people from TIBCO have been thought on you this time.
And I said this time because the previous big step like the one we are living right now was the big jump from the TIBCO Integration Manager 4.x to the TIBCO BusinessWorks 5.x we were living the past years and in this occasion nobody though on this problem or if anyone thought about it, he did nothing. But in this case, in the era we live now, we have the great tool that is the TIBCO BusinessWorks Process Migrator that comes out-of-the-box with the TIBCO BusinessWorks 6.x Business Studio, so you can migrate your old 5.x process to the new and fresh 6.x process without any work on your side.
Obviously, this last sentence is not true, because the migration process is not fully supported from TIBCO, so they don’t guaranteed to you a 100% success rate, and because in this kind of thing you always have to a big set of tests to be sure that everything is working correctly and the migration was sucessfully. Despite of this, the migration tool is a great tool to use in a process migration (probably the one you are now developing and the production release is too far away to continue to use the 5.x or any scenario you can have)
If you want to use the tool is too easy, and I can show you with the Twitter application we discussed in the previous post that it’s a fully compliant BW5.X project that event uses different not out-of-the-box plugins, so you can test the power of this tool.
The first thing we have to do is to open our TIBCO Business Studio and launch the Migration Wizard (and let it to do all the magic)
At the wizard panel, we only have to select the location of our BusinessWorks 5.x process (we can select a folder which contains multiples projects) and select the project we want to transform and the destination we want to store this new projects, and that’s all!
The process could lasts a few minutes but you follow the progress from the Migration Output text panel, and when the process finishes you will be able to close the panel and look at the results.
In our case, you can see, that the migration was complete and it generates one BW6.x process for each BW5.x process we have earlier.
We also have three errors on the migrated processes, all of three focused in the same process. So, 1/4 error rate, but we are going to take a deep look to the errors:
If we take a deep look inside the error, we can see that all the three errors are the same error, and the error is only a mapping error inside a call-process activity, because the xpath not exist in this new process as you can see here:
So if we solved this little mistakes in the migration we were ready to create the module descriptor to create our new package to be deployed inside our BW6.X container. In this case, is important to notice that we use different plug-ins like the Twitter plugin or the REST plug-in that in the BW6.x is a core feature, and there was no problems with it. No problems with the SCA behaviour in the new BW 6.x. No problems with the new shared resources even when the full-URL in the REST plugin was hard-coded it managed to create a new HTTP Client Shared Resource to do the full-migration.
To finish the post, only a thought you have to have in mind when you are using this tool. This tool is not a golden stone, is only a useful tool but you have to know well where and how to use it, to not get frustrated for any errors or mistakes it could make. Be patient and evaluate its value and you will be grateful to can use it!