File Jockey User Manuals

On this page we explain how to setup various apps and programs to interact with the files in HCL Connections {HCL} via File Jockey. In all guides we use the File Jockey url https://greenhouse.file-jockey.com as an example. If you have File Jockey installed on premises the File Jockey URL will be different and you have to use your File Jockey URL instead.

Windows Computer

In Windows 7, 8 and 10 start your files explorer and choose tools map network drive.

or

Do not use below option in Windows by the way!

The URL is https://greenhouse.file-jockey.com

Then enter your Greenhouse credentials and the network drive will be created.

Usage notes and tips

With the network drive giving direct access to the files in Connections many usage possibilities are possible, for example drag and drop of files and or folder structures. In this section general usage notes and tips are listed that will explain why certain actions are not working.

In My Folders HCL Connections does not allow to create sub folders, so only one folder level is supported by Connection, thus the same applies for File Jockey. If you try to drag a folder with a sub folder to My Folders you will get an error. Dragging a folder with multiple files inside this folder is supported if the following tip is not applicable.

In My Files and My Folders you may only store a particular file name once. Suppose you have a file “projectdoc1.pdf” stored in My Files. Then you try to drag the same file “projectdoc1.pdf” to a folder in My Folders you will get an error.

In the Community Folder in File Jockey shows the Communities you have access to. The File Jockey network drive does not allow to create new Folders. Creating new Communities has to be carried out via the Connections interface in the browser.

In the Community Folders place you will see the folders created. It is only allowed to add files to the Folders. It is not allowed to add an file to the Community Folders Folder.

In the Community Files and Folders you may only store a particular file name once. Suppose you have a file “projectdoc1.pdf” stored in Community Files. Then you try to drag the same file “projectdoc1.pdf” to a Community folder you will get an error.

Problems

If you have problems with mapping the Windows network drive please check make sure you follow the instructions below.

• Make sure all Windows updates are installed on your computer, then test again, if still having problems carry out the following step.
• Windows 7 and Vista will fail to connect to the server using insecure Basic authentication. It will not even display any login dialog. Windows 7 and Vista requires SSL / HTTPS connection to be used with Basic. If you try to connect via Add Network Location Wizard you will get the following error: “The folder you entered does not appear to be valid. Please choose another“. However, you still can connect if you set the following registry key on a client machine: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters\BasicAuthLevel to 2. The BasicAuthLevel can be set to the following values:
  • 0 – Basic authentication disabled
  • 1 – Basic authentication enabled for SSL shares only
  • 2 or greater – Basic authentication enabled for SSL shares and for non-SSL shares
  • You must reboot your computer if you changed this registry setting, then test again, if still having problems carry out the following step.
• Next check this registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order\ProviderOrder. This contains a list of network provider services and make sure it also contains the “webclient” entry.
• Next try will be to implement this hotfix, then reboot your PC and try again, if still having problems carry out the following step.
• If the mapped was created you should see the Communities, My Folders and My Files. If the folder is empty, so you see nothing you have entered the wrong credentials, to fix disconnect the drive and reconnect with the correct credentials.

iPad – Goodreader

On your iPad, open (or install first) the Goodreader app and press the Add button on the right, choose WebDAV server. Fill in the File Jockey for {HCL} URL and use our own login. In this example we use the Greenhouse server URL. Please enable cookies and save the WebDAV server connection.

Your Goodreader will show the new server connection to HCL Greenhouse.

When you press the connection the Goodreader will show all the files and folders listed in your HCL Connectio9ns environment.

In this example we will select the File Jockey community in order to sync all File Jockey Community’s files to the iPad for offline usage.

Please press on File Jockey community once, it will turn Green. Then press the Sync button at the bottom of this Window.

A Download & Synchronize message is presented.

Click Proceed and choose a folder on your iPad (or create a new folder) where you want to sync the files to, for example My Documents.

After selecting a location, the sync parameters are presented which may be set as you like (read only enabled yes or now for example).

Fill the fields similar as the picture and press the Sync button at the upper right corner of the window.

Now the Goodreader will sync and downloading all the communities with all the files to the iPad for quick off line usage.

When the Goodreader completes the sync you will see the Remote sync option to the File Jockey community in Greenhouse. Every time you push the sync option Goodreader will download or upload new documents from and to Greenhouse. Isn’t this great?

On the Goodreader you may check out the Manage files options which allows you to manage the files you have replicated to the iPad (for example star, delete, move, add and remove files).

You may add more sync’s to the Goodreader, for example sync the My Files or a particular file in a community.

iPhone – Goodreader

Open (or install first) the Goodreader app on your iPhone, select the Connect option. The Servers tab is presented. Click the Add option to create a new connection to {HCL}. In this example we will use Greenhouse.

Select WebDAV Server and fill in the Greenhouse URL and use our own Greenhouse login. Click Save.

The new created Greenhouse connection will be presented. Click on the connection name and the connection will be established.

The Goodreader will show you all the files and folders listed in the Greenhouse environment. In this example we will select the Community folder in order to sync all Community’s files to the iPhone for offline usage.

Press on Communities once, it will turn Green, then press the Sync button at the bottom of this Window. A Download & Synchronize message is presented. Click Proceed

Choose a location where you want to sync the files to, for example Downloads. Click Download here & Synchronize. The Sync parameters are presented. Fill them like in the picture and press the Sync button at the upper right corner of the window.

Now the Goodreader will sync all the communities with all the files to the iPhone for quick off line usage. When the Goodreader completes the sync the Communities folder is available on the start screen.

You can now work offline with the files in the Communities folder. If you want to synchronize the complete folder, click on Connect, select the Downloads tab and press the Sync button besides the Communities. Now your iPhone is automatically synchronized with Greenhouse.

You may add more sync’s to the Goodreader, for example sync the My Files or a particular file in a community, even from other environments, like for example HCL Connections. You can even sync all your synchronizations at once by clicking the general sync button.

Isn’t this great?!

If you click the Tool icon you can Manage your files (rename, copy, move, star,…)

 

iPad – Notability

On your iPad, open (or install) the Notability app and press the gear button, select Manage Accounts and select WebDAV. Fill in the File Jockey for {HCL} and use your own login. In this example we use the Greenhouse environment. Click Link

The WebDAV connection is now established. Click Close in the right upper corner to close the Settings window. You can now Import files by clicking the share button in the right upper corner

Select WebDAV. The available folders and files in Greenhouse will be presented. Select the folder which contains the files you want to work with and select Import Files in the upper right corner

Push the Import button and the files will be downloaded and imported

When the import process is ready, the files are presented in the app

When you are ready with modifying the document, you can upload them back to Greenhouse. By pushing All Notes you can select multiple files to upload at once.

Push the share button in the left upper corner and choose WebDAV. The WebDAV destination settings are presented. You can select the requested location by clicking Folders/

Push Send to WebDAV and the files will be uploaded to Greenhouse. It is that easy!

 

Automatically Back Up your Notes

With Notability you can you automatically back up your notes to the cloud service of your choice. Notes are automatically backed up whenever you return the library after making changes to a note (Note; automatic backup is different than iCloud syncing).

To establish the automatic backup, go to the Notability Settings by pushing the gear icon. Select Auto-backup in the Settings screen. An Auto-Backup message is presented. Push OK to continue.

Select WebDAV as backup destination. Click the blue gear to go to the backup settings. The default Destination Folder is /Notability/. Select to folder to change the location.

Select for example My Files. Select Back Up To My Files in the upper right corner to select the folder.

The chosen folder is now presented ad Destination Folder. Click Settings to return to the Auto-backup Settings. Click Close to close them.

The first backup is now automatically started. From now on Notability will automatically backup the changes you make in the future.

iPhone – Notability

Open the Notability app on your iPhone, swipe the screen to the left and press the gear button.

The Settings are presented, click the Manage Accounts option. The Account options are presented. Click Log in beside WebDAV.

Fill in the File Jockey for HCL URL in and use your own login. In this example we use the Greenhouse environment. Click Link. The WebDAV connection is presented. Click the < Settings to go back to the Notability Settings.

The Settings are presented. Click Close to close the Settings. The Notability start screen is presented. Click the pencil to create a new document, also if you want to download a document through WebDAV.

You can choose to start a new document or edit a current document or you can click the Go back option. If you go back you will notice that an Import option has become available.

Choose WebDAV from the available import locations. The Greenhous environment is presented.

Choose a location in Greenhouse where you want to import your file(s) from and select one or more files. The file(s) is downloaded.

When the selection is finished, Notability present Import options. For this example we choose Create new note. Notability asks you if you want to download the complete document or just a subset. Press Ok.

When the download is finished you can see an Imported to All Notes line. Click File Jockey to go back to the Notability start screen where you can select the document to edit.

Click the document to open the document and edit it with Notability. When you are done with editing, click the tool and select Share. Choose WebDAV as location to share with.

Choose a destination on the Greenhouse environment and click the Send to WebDAV.

The file is uploaded to the Greenhouse environment.

This way you can download, edit and upload documents from and to any requested location in Greenhouse. It is that simple!

Automatically back up your notes

With Notability you can you automatically back up your notes to the cloud service of your choice. Notes are automatically backed up whenever you return the library after making changes to a note (Note; automatic backup is different than iCloud syncing).

To establish the automatic backup, go to the Notability Settings by pushing the gear icon. Select Auto-backup in the Settings screen.

Select WebDAV, you will receive an Auto-backup message, click OK

You can now configure the WebDAV settings by clicking the blue gear icon. You can choose a Destination Folder you like by selecting the default folder /Notability/. Choose the location you prefer, for example My Files.

Select Back Up To My Files in the upper right corner. The selected Destination Folder is presented. Push Auto-backup.

The Notability start screen shows a message in the left corner that the files are being back upped.

Back up will automatically backup your Notes when you change them.

iPad – Pages, Numbers and Keynote

For this manual I use the Pages app, but the same is applicable for Numbers and Keynote. Open the Pages app on your iPad.

Press the + icon and select Copy from WebDAV

Fill in the File Jockey for {HCL} and your own login. In this example we use the Greenhouse environment. Press the Sign In button.

The Greenhouse environment is presented. Choose a location, for example My Files or one of the Communities.

Only the Word documents are displayed. Select a file, which will be automatically downloaded and imported

When the file is in Edit mode and you are ready, click the share button and click Send a Copy

Choose WebDAV

Choose the file type

The is prepared for sending to WebDAV

Choose the location to send the file to and click the Send button

The file is uploaded to Greenhouse

If you have files in a folder, it is possible to upload a file without opening the file in edit mode. Open the folder, the files will be presented. Click the share button and choose Send a Copy

Select a file and choose WebDAV. You will be asked to select a location, etc.

Downloading, editing and uploading documents between Pages and Greenhouse becomes very easy when connected through WebDAV. Enjoy!

 

iPhone – Pages, Numbers and Keynote

For this manual I use the Pages app, but the same is applicable for Numbers and Keynote. Open or install the Pages app on your iPhone. Press the + icon and select Copy from WebDAV.

Fill in the File Jockey for {HCL} URL and your own login. For this example we use the Greenhouse environment. Press the Sign In button.

The Greenhouse environment is presented. Choose a location, for example My Files or one of the Communities.

Select a file, which will be automatically downloaded and imported

Choose the file type. The file is prepared for sending to WebDAV

Choose the location to send the file to and click the Send button. The file is uploaded to Greenhouse.

If you have files in a folder, it is possible to upload a file without opening the file in edit mode. Open the folder, the files will be presented. Click the + button. You will be asked to select a file.

Select a file and choose WebDAV. You will be asked to select a location, etc.

Downloading, editing and uploading documents between Pages and Greenhouse becomes very easy when connected through WebDAV.

Enjoy!

Android – FolderSync

On your Android device, open (or install) the FolderSync app. Go to Accounts. Click Add account and choose WebDAV as Account type.

Fill in a descriptive Name, Protocol should be HTTPS, and use the File Jockey for {HCL} URL and use your own login. In this example we use the Greenhouse environment.

Scroll back to the top of the screen and click Test connection. If you filled in the correct credentials you will see a ‘Login succeeded’ message (if not check your login credentials). Click the Save option at the top of the screen.

Now the connection with Greenhouse is arranged you can select which communities, folders and or documents you want to synchronize to the FolderSync app.

Go to the FolderSync settings and choose Folderpairs. Fill in a descriptive name for the new Folderpair.

Click the Remote folder to select the folder you want to synchronize the document in Greenhouse from. Click Select Folder when you have selected the requested folder.

Click the Local Folder field on the Folderpairs settings and select where you want to store the synchronized communities, folders and or documents. For example Documents/WebDAV/HCL/File Jockey. Click Select folder in the upper left corner.

On the Folderpairs settings, select Sync Type, we prefer Two-way synchronization.

Fill in the other Folderpairs options as you request. When you are finished, press Save on the top of the screen.

The synchronization is now available. Push the Sync button. The synchronization will start.

You can view the progress of the synchronization in the FolderSync settings, Sync Status.

When the synchronization finished, the synchronization remains available to start again. Just push the Sync button after you have changed documents and the documents will be synchronized automatically to the correct location.

Go to the File Manager to view the synchronized files

Notice you have to select the same path as chosen for the synchronization to get to the files.

While the connection with Greenhouse is arranged, you can also download files separately, with the File Manager. Notice that these files are not synchronized Two-way with the Greenhouse environment (or any other location)!

Push the Cloud button in the File Manager.

Choose the Greenhouse connection. Navigate to the correct location in Greenhouse and select a document.

iPad – PDF Expert

Open or install PDF Expert on your iPad, but of course the app is also applicable for use with the iPhone.

The PDF Expert app opens default in Documents

Select Network and choose WebDAV

Fill in the Greenhouse URL and your own login. URL: https://greenhouse.file-jockey.com (only applicable for use in apps) and we use our own Greenhouse login.

Click Save in the upper right corner.

The connection with Greenhouse is visible under Accounts and the connection is established immediately. The folders in Greenhouse are presented.

The Sync option has become visible in the upper right corner. So you can now decide which part of Greenhouse you want to synchronize with PDF Expert over File Jockey. The entire environment, a few communities or just some files. It is up to you.

Click Communities to select the Communities you are member of or follow. In this example we will sync the complete File Jockey community. So select File Jockey and press the Sync option in the upper right corner.

The File Jockey community is opened. Press Sync to synchronize the complete File Jockey community to PDF Expert.

Click ‘Sync This Folder’

The Folder is added to Documents.

Go to Documents. The File Jockey folder is available; the two arrows on the folder present the ongoing synchronization.

When the synchronization is ready, you can start editing documents or synchronize other communities or My Files. You can even decide to create another WebDAV connection.

Editing documents with PDF Expert

You can now edit and modify documents with PDF Expert. The following file types are supported:

Open the HCL Greenhouse connection and select a document you want to edit, it will turn blue.

You can now modify the document completely; highlight, strike out, add a signature, draw with your finger, make your notes, etc.

When are ready editing the document you just go back to the dashboard of PDF Expert and your changes are saved and automatically synchronized with the Greenhouse environment, during the next sync. The cloud icon beside the document indicates that the document is not yet synchronized with Greenhouse.

The document will automatically be synchronized in an instance (according to your Sync Settings). If you don’t want to wait for this to happen, you can select Network and click Sync in the upper right corner.

PDF Expert settings

With PDF Expert settings (push the gear button in the left upper corner) you can determine where files are downloaded to, if the data is protected or how synchronization is arranged.

Support for versioning

File Jockey installation guide on HCL WebSphere

Installation guide to install File Jockey on HCL WebSphere for HCL Connections.

File Jockey v 2 supports HCL Connections version 5, 6 and 7 and IBM/HCL WebSphere 8.5 and higher.

File Jockey supports all operating systems where HCL WebSphere can be installed on.

File Jockey may also be installed on Apache Tomcat server (not documented yet). Installing File Jockey on JBoss / WildFly is not supported and will give problems.

If you have problems or questions please email us on support@lialis.com.

Installation approach

In this guide we will install File Jockey on a single WebSphere Application Server. File Jockey may also be installed on a clustered WAS setup only if the nodes are located of different servers from (virtual) hardware point of view. If you install File Jockey on a WAS cluster you need to carry out some manual xml file tweaking because of a limitation in the File Jockey administration interface.

Creating and configuring a dedicated WebSphere application server for File Jockey

Register a new WebSphere application server.

Choose default template, generate unique ports, choose confirm and save to create the new server.

Navigate to the Web servers (IHS), select the IHS server and choose Generate Plug-in

Then choose Propagate Plug-in. This will tell the IHS server there is a new WebSphere application server it has to serve.

Final step is to reboot the IHS server.

Installing File Jockey on single WebSphere application server located on one node.

In this installation guide File Jockey v2 will be installed on a single WebSphere application server.

HCL Connections runs on a different server.

Installation steps

Deploy the File Jockey WAR file.

Go to the ‘Enterprise applications’ section and press the ‘Install’ button:

Select the WAR file:

Press ‘Next’.

You can install the application via the Fast Path method.

Map the filejockey01 server and the IHS server to the File Jockey application.

Default settings at step 3 Map Virtual Hosts

The context root should be /FileJockey (case sensitive)

Make sure the application is installed successfully and save directly to the master configuration.

File Jockey Security

I assume you have configured LDAP within HCL WebSphere and application security has been enabled in the Global Security.

Next step is to configure the File Jockey Security rights. Press the ‘FileJockey_war’ link, then the link ‘Security role to user/group mappings’

In this example everybody will be authorized to use File Jockey, but feel free to assign groups or users instead.

And the File Jockey admin page will be authorized for two Admins only

Change the class loader as illustrated below (choose the right class loader!)

Now you should be able to start the File Jockey application on WebSphere as illustrated below (if you did not forget to start the WAS).

Configure File Jockey

You can access the File Jockey administration page using the URL http(s)://servername/FileJockey/admin/main.jsp (case sensitive) and you should see below screen. Tip, use another browser to access this administration page so you avoid credential problems because you may have already opened the WAS admin console with different credentials which will be passed by the browser to the File Jockey administration page.

Please press the Open Configuration button.

For a minimal setup you must enter the following settings.

• License key (you will have received this key form Lialis). This key is based on the servers computer name
• HTTP Cache folder, here File Jockey will store its cache
• HTTP Threads
• HTTP Cache time
• Log path

For example:

When all is set save the Configuration and reboot the File Jockey was application.

Please press the Open Repository button.

You will find a few example repositories, feel free to remove them. Make sure there is one repository linking to your HCL Connections environment. Advice, keep the name sort because it will be used in the URL accessing File Jockey. When set save the Repositories and reboot the File Jockey was application.

Please press the button Show Log and check the File Jockey log for errors (if the File Jockey log is empty it did not start properly and you should check the SystemOut.log for errors. Below the SystemOut.log how it should look like when there are no error’s.

[fusion_builder_container hundred_percent=”yes” overflow=”visible”][fusion_builder_row][fusion_builder_column type=”1_1″ background_position=”left top” background_color=”” border_size=”” border_color=”” border_style=”solid” spacing=”yes” background_image=”” background_repeat=”no-repeat” padding=”” margin_top=”0px” margin_bottom=”0px” class=”” id=”” animation_type=”” animation_speed=”0.3″ animation_direction=”left” hide_on_mobile=”no” center_content=”no” min_height=”none”][9/22/15 18:39:14:942 UTC] 00000080 SystemOut O Initializing FileJockey version: 2.0.0
[9/22/15 18:39:14:942 UTC] 00000080 SystemOut O Reading configuration
[9/22/15 18:39:14:942 UTC] 00000080 SystemOut O Using configuration file
[9/22/15 18:39:14:957 UTC] 00000080 SystemOut O Loading configuration
[9/22/15 18:39:14:988 UTC] 00000080 SystemOut O Loggers initialized to level: debug
[9/22/15 18:39:14:988 UTC] 00000080 SystemOut O Starting file userlogging.
[9/22/15 18:39:15:113 UTC] 00000080 SystemOut O FileJockey started
[9/22/15 18:39:15:113 UTC] 00000080 ServletWrappe I com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: [FileJockey_war] [/FileJockey] [FileJockeyServlet]: Initialization successful.
[9/22/15 18:39:15:113 UTC] 00000080 webcontainer I com.ibm.ws.webcontainer.VirtualHostImpl addWebApplication SRVE0250I: Web Module Lialis FileJockey has been bound to default_host[*:9080,*:80,*:9443,*:5060,*:5061,*:443,10.146.163.173:9080,10.146.163.173:80,10.146.163.173:9443,10.146.163.173:5060,10.146.163.173:5061,10.146.163.173:443,*:9081,*:9082].
[9/22/15 18:39:15:144 UTC] 00000080 ApplicationMg A WSVR0221I: Application started: FileJockey_war

The File Jockey configuration files displayed in the File Jockey Administration page are stored in the Users folder, for example C:\Users\Administrator\.FileJockey

WAS Cluster

If you have installed File Jockey on a WAS cluster you will notice that on one of the WAS servers the File Jockey app will complain about an invalid license key. You have to make sure each server is equipped with the right File Jockey license key which is based on the computer name. The best approach is to manual copy below 3 xml files from the WAS server without the license error to the WAS server with the license error. The edit the configuration.xml and add the correct license key you have received from Lialis.

File Jockey URL for WebDAV clients

The URL to access the files stored in HCL Connections is http(s)://serverhostname/FileJockey/root/

This URL can be used on mobile devices, Mac and Windows computers, Please note that Windows 7 computers might need some more attention with regards to Windows patches and security settings. Details on how to setup mobile devices, Mac and Windows computers for File Jockey are described on this page.

Changing the File Jockey URL

To change the File Jockey path first you need to open the FileJockey.war file with a zip program. And edit the web.xml file that’s located in the WEB-INF folder.

The web.xml file contains 2 xml sections that need to be updated. There is the servlet-mapping section with url-pattern tag. By default it will be set to /root/*. This part tells the server what URLs are linked to the File Jockey servlet classes. Changing this to /rt/* will change the File Jockey URL to: http(s)://serverhostname/FileJockey/rt/

There’s also the security-constraint section with the same url-pattern tag. The value in this tag must be set to the same value as the url-pattern tag in the servlet-mapping section. This section determines the role users need to have before they can make use of File Jockey. If it is not set correctly everybody will have access to File Jockey.

When you’re done, don’t forget to update the web.xml file in the FileJockey.war file.

Next we’ll change the /FileJockey/ part of the URL, which is quite simple. During installation of the FileJockey.war file you’re asked to map the context root for the web modules. As described above, this should normally be set to /FileJockey. But you’re free to set it to anything you like. For example setting this to /fj will result in a File Jockey URL like this: http(s)://serverhostname/fj/rt/

Self signed certificates

When your Connections server uses self signed certificates FileJockey will be unable to reach the Connections API the following post will explain how to fix the problem. Adding self-signed ssl certificate to the java truststore

Adding a self-signed ssl certificate to the Java truststore

After installing you may find that FileJockey still fails to connect to the Connections API and the following error appears in the FileJockey log: “PKIX path building failed: java.security.cert.CertPathBuilderException: unable to find valid certification path to requested target”. This happens because FileJockey in unable to recognize the ssl certificate of the Connections server, this can happen when the server uses a self-signed certificate or the signer of the certificate is unknown by the Java virtual machine. To make it work the certificate should be added to the Java truststore using the procedure below.

The first step is to get a copy of the certificate public key, the easiest way to get access is to open the connections website in Firefox.

Next click the lock icon in the address bar, a popup will appear with the site address with an > to the right. Click the > and then the “More Information” button at the bottom. In the following Dialog select the Security tab and click the “View Certificate” button.

In the next Dialog go to the Details tab and click the export button. Export the public key of the certificate to disk.

Copy the exported .pem file to your WebSphere server to be imported in the truststore.

Open a Command Prompt on the WebSphere server and navigate to the jvm installation in the WebSphere installation directory. You need to go into the lib\security folders within this folder.

%WEBSPHERE_ROOT%\AppServer\java\jre\lib\security

Use the following command to add the certificate to the trust store:

../../bin/keytool -importcert -keystore cacerts -storetype jks -file <path to your .pem datafile> -alias <any unique name>

You’ll be asked for a store password. The default password for the store is “changeit”

The application server needs to be restarted after the procedure for the jvm to pick up the certificate from the truststore.

If you have questions, don’t hesitate to contact me!

marten.vosmer@lialis.com

Detail comparison of the HCL Desktop Plugin and File Jockey

The HCL Desktop Plugin is a program to be installed on a Windows computer and it gives access to the Files in HCL Connections (cloud).

File Jockey is a program to be installed on a server (for example WebSphere running HCL Connections) and it gives access to the Files in HCL Connections (cloud) via a network drive.

Both programs intend to do the same, though are completely differed in their approach.

In this post we will compare the two solutions. We at File Jockey will do our best to make this comparison as objective as possible.

In the details below we are explaining the differences between the two solutions. All the items not mentioned are equal between the two solutions, so both solutions allows to edit for example Word files, only in a different way.

File Jockey advantages that HCL Desktop plugin does not offer

No software installation, works out of the box in Windows 8 and 10 – Windows 7 needs some windows fixes.

Only solution for Citrix environments because Windows program installations are not allowed in Citrix environments.

100% integration with Windows because the network drive is 100% Windows functionality. For example in XLS create links between xls files stored in Connections via File Jockey network drive. So take a File Jockey xls file field value and press copy. in other xls file on File Jockey press paste special and paste as link. You will see that the copied cell value is retrieved from the source xls file via the network drive. This is just an example of 100% Windows integration supported by network drives.

Support for preview pane in file explorer

Shows all communities the user has access to

When you delete a folder the folder and files are deleted as well

Right mouse click in File Jockey network drive to create new Word document for example

Any Windows program has access to the files in the network drive. Beyond compare can be used to compare the SharePoint and HCL Connections network drives. Notepad ++ file open shows HCL Connections via File Jockey

No program crashes possible because File Jockey is not a program installed on the PC

Support for Mac computers (though slow performance due to Mac WebDAV client)

Support for Mobile apps like Goodreader to be used to sync one or multiple communities to the iPad for offline usage

File Jockey is using the same approach as the Microsoft SharePoint network drives allowing easy migration of files between SharePoint and HCL Connections

Possibility to copy the whole community with everything inside to another file location – and all right mouse click options available like archive, unpack and so on

Microsoft upload center is used to cache files to be uploaded to Connections, in case Connections or File Jockey is down

Bottom line, a network drive showing the Connections files is easier for the users to work with because it behaves in the same manner as the C drive for example.

HCL Desktop plugin advantages that File Jockey does not offer

Below are the functions of HCL Desktop Plugin that are not supported by the File Jockey network drive. Everything not mentioned here is equal between the two solutions (give or take a few options that we have missed)

No extra costs

Allowed to move a folder to other folders

Support for pinned files and folders, files and folder shared by me, shared with me, shows people, trash bin

Option to open in browser

Show sharing details

Show versions

Option to lock and check in and check out files

Option to upload new version

Support to add files to activities and wikis

Office integration

Conclusion

We at File Jockey think HCL Connections is a great solution. We only do not like the HCL Desktop plug, its just not user friendly. A Windows network drive showing the files of HCL Connections is a better approach simply because users are used to with Windows network drives and because the network drive is a 100% Windows implementation resulting in a full integration with all programs on Windows.

And yes, File Jockey works with a Mac as well, only very slow. This is because of the Mac, we can not solve this.