You may have seen a blog published by me a few weeks ago called “Talend Studio: Tips and Tricks (Part 1)“. In this blog, I touched upon a few nifty ideas to help kickstart your use of Talend Studio 6.0. So, in the spirit of keeping things short and simple, here’s part two of that very topic. We’ll dive straight in but remember, as always, I’d be interested to hear both your feedback and any other issues you’ve encountered also, so please take the time to comment below.
Multiple Talend Installations on the same machine.
Simply, don’t. Having dealt with this in the past on numerous occasions, I can honestly say you will almost always run into issues.
- Talend is not designed to be used by multiple users at the same time
- Installing Talend multiple times, for each user, does not help. This is because:
- During job run time, Talend will try to use all available recourses of the machine, thus potentially starving other resources or other developers using their Talend instance.
- File locks may occur that can break Talend functionality. There is a fix for this under the second heading of this article.
- Don’t ever run the Talend Server features on the same machine as a regular Talend Studio for development.
File/folder lock or inability to import metadata
There are two scenarios I know of that could lead to this issue: insufficient privileges on the file/folder; or the system has multiple Talend installations and another user has locked the file. So how to prevent it this? Well, if the latter is true and you simply must have multiple Talend Studio instances on the same machine, than you will need to do the following:
- Add “-Djava.io.tmpdir=/path/to/tmpdir” to the .ini file located in the same location as the .exe or .sh file used to launch Talend. Make sure you amend the one with the same name. I would advise you to direct all of the files to a temp folder under the root directory of a user’s Talend installation. This will prevent files being saved to the system temp/tmp directory, thus insuring that no file locks occur.
- Make sure that the Talend installation directory is accessible in r/w mode for the user.
- Make sure that the user has access to his .m2 directory if the user is going to use remote connections for Talend Studio.
Cleaning up your Talend Studio
Everyone knows that the first thing to do when Talend is misbehaving is to clean up the workspace folder. Granted, you should save any local projects you might have beforehand. However, there is another step that you should do that may help you out… Drill down to your Talend Studio “configuration folder” and remove all folders that start with “org.eclipse.*”. Don’t worry Talend regenerates that on boot.
Once more, that’s it for now. Please share the post and leave a comment if you have any questions or you know of any other useful hacks in Talend Studio.