Guide version 12 dated 13 March 2017 - Author firstname.lastname@example.org
Installation guide to install File Jockey on IBM WebSphere for IBM Connections.
File Jockey v 2 supports IBM Connections version 5 and higher and IBM WebSphere 8.5 and higher. File Jockey supports all operating systems where IBM 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 email@example.com.
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.
IBM Connections 5 runs on a different server.
Deploy the File Jockey WAR file.
Go to the ‘Enterprise applications’ section and press the ‘Install’ button:
Select the WAR file:
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 IBM 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
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 IBM 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.