Using JDeveloper with TFS: grayed out options

Having to use a unified versioning control system across the enterprise, the choice fell upon Microsoft Team Foundation Server 2010.It’s strong bet because it not only supports the versioning control, but has integrated tools to handle what is called the Application Lifecycle Management (ALM).
However, the not-Microsoft technology teams are faced with the challenge of finding the right integration between their development tools and TFS Source Control. One of those tools is Oracle’s JDeveloper.
You can find on the Web tutorials like this or this on how to install the JDeveloper plugin to integrate with TFS. The corresponding video is shown below:
However, it does not follow through a simple, yet required configuration in order for the plugin to work properly. You have to include to directory where the command line tool (TF.EXE) of Team Foundation client is installed. In my case, having a 32-bit Visual Studio 2010 installation, it’s on this  folder:
It also doesn’t inform you of an important software requirement: you must have TFS 2010 Anywhere or Visual Studio 2010 installed. The plugin doesn’t bring the client.
If you’re missing any of these two requirements, installing the TFS client or including the path to the “TF” command line utility, the options will appear grayed out.