Installing KwikWork Integrator

The following steps are required to install KwikWork Integrator for Content Navigator.

Expand the installer

The installer must be extracted on the Content Navigator server by following the steps below:

unzip KwcnSetup-3.5.x.zip

Copy the kwcn-client.jar file from the installer to the 'ECMClient/plugins' directory
Create a directory called RepositoryAPI in the the IBM directory. Copy the files 'Jace.jar' and 'Pe.jar' from the 'navigator.ear\navigator.war\WEB-INF\lib' directory to the RepositoryAPI directory.
Log into the Websphere Integrated Solutions Console on the application server where IBM Filenet is installed then navigate to Environment → Shared libraries.
Click 'New' to create a new shared library called KwcnClient. In the 'Classpath' field enter the path of the kwcn-client jar file located in the Plugins directory then click the 'OK' button and save directly to the master configuration.
Click 'New' to create a new shared library RepositoryAPI (this name is mandatory for KwikWork' to function correctly). In the 'Classpath' field enter the path of the RepositoryAPI directory in the IBM directory then click the 'OK' button and save directly to the master configuration.
In the WebSphere enterprise applications section, edit the navigator application. Add a new shared library reference for the navigator web module and point it to the KwcnClient shared library that was created then click 'OK' and save to the master configuration.

The KwikWork engine can be installed in WebSphere by following the steps below.

Log into the WebSphere Integrated Solutions Console on the application server where IBM Content Navigator is installed.
Navigate to Applications → Application Types → WebSphere enterprise applications using the vertical navigation tree on the left then click the install button above the list of installed applications.
Click the 'Choose File' button under 'Path to the new application' and locate the kwcn-engine.ear file in the installer that was extracted earlier. Select the ear file, click 'Open' on the dialogue box then click Next.
Choose 'Fast Path' if it is not already selected then click Next.
Leave the default values for all steps of the install process and click next on each of the three screens. In Step 4, specify the 'Context Root' as '/kwcn-webapp' then click Next.
Finally verify the settings on the Summary page and click 'Finish' for WebSphere to install the Kwcn Engine then save to master configuration.
Edit the newly installed kwcn-engine and click 'Environment entries for the application' then update the WorkingFolder to point to the location on the server where KwikWork configurations will be stored. Click 'Ok' and save to master configuration.
Finally, start the KwikWork Engine by checking the box for kwcn-engine then clicking Start.

Navigate to the KwikWork working folder on the server.
From the working folder, navigate to the 'import/license' folder then copy the KwikWork Integrator license key provided by enChoice to the license folder.
After a few second the license file should disappear from within the /kwcn/import/license' folder. Once this has occurred, verify that it has been copied to the 'kwcn/import/success' folder.
Finally, restart the kwcn-engine application from the WebSphere console.

Click on Plug-ins from the left navigation bar
Click on new plug-in
The KwikWork Integrator plug-in jar file in now part of the kwcn-engine application and the path should be http://localhost:9081/kwcn-web/kwcn-integrator.jar(substitute 9081 for the port of the WebSphere application server where Navigator and the Kwcn Engine are installed). Once the path is entered click on "Load"
After the plug-in loads click on save and then close.

KwikWork Integrator can be configured for each IBM Content Navigator desktop after the Plug-in is loaded using the following steps: