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.
The other option is to use the SCM capabilities that the TIBCO Designer has. This option has the advantage that you can manage all your artifacts inside your Designer, you don’t need any other tool, but on the other hand your choices are restricted to the ones supported by the product.
If we take a look at the options that we have when we create a new TIBCO BW 5.x project, we can see the options that we have to specify a SCM tool, as you can see here:
The options are the following:
- File Sharing
- Scriptable RCS Adapter
- Merant Version Manager (PVCS)
- Microsoft Virtual SourceSafe
- TIBCO XML Cannon
If you take a look you are going to use that the options are not the newest ones, and if you take a look at the launch dates you are going to have something similar to this:
- ClearCase (1992)
- CVS (1990)
- Perforce (1995)
- Merant Version Manager (PVCS) (1985)
- Microsoft Virtual SourceSafe (1994)
- TIBCO XML Canon (???)
You can take for sure that’s are not the newest options and neither the most used ones. Old alternatives like SVN is no there and the newest options like Mercurial or Git not even close.
But, TIBCO BW 5.X provides a tool (Scriptable RCS Adapter) that allow you to create a script to enable other SCM system to be use inside TIBCO Designer. As an example, in the oficial documentation TIBCO provides to us a script that enable SVN inside TIBCO Designer. So, who’s the next that want to create a script to support another SCM, like Git, Mercurial or Plastic??
Here it is the oficial link to the section that explains how to create an Scriptable RCS Adapter and the SVN sample,