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.