Updating the plug-ins that are delivered with IBM Content Navigator
To get any updates that are included in the IBM® Content Navigator plug-ins, you must replace the plug-in JAR files on your web application server.
About this task
The following
plug-ins were delivered with a previous release of IBM Content Navigator,
and might need to be updated:
| Plug-in | File name | Notes |
|---|---|---|
| AFP viewer plug-in | The AFPViewerPlugin.jar file is in the plugins directory of the IBM Content Navigator installation directory. | |
| Content Federation Services plug-in | The cfsplugin.jar file is in the plugins directory of the IBM Content Navigator installation directory. | |
| External data services plug-in | The edsPlugin.jar file is in the plugins directory of the IBM Content Navigator installation directory. |
Remember: If you use the external data services plug-in, you must create your own
service.
|
| IBM Content Analytics plug-in | The icaplugin.jar file is in the plugins directory of the IBM Content Navigator installation directory. | This plug-in is deprecated. This plug-in is supported only with IBM Content Analytics Version 3.0 or later. If you install IBM Watson™ Watson Content Analytics Version 3.5, you must use the plug-in that is shipped with IBM Watson Content Analytics. |
| IBM Content Collector plug-in | The ICCViewerPlugin.jar file is in the plugins directory of the IBM Content Navigator installation directory. | |
| IBM Sametime® Connections plug-in | The ProfilePlugin.jar file is in the plugins directory of the IBM Content Navigator installation directory. | |
| Workplace XT Integration Support plug-in | The XTPlugin.jar file is in the plugins directory of the IBM Content Navigator installation directory. |
Procedure
To update a plug-in JAR file:
-
Replace the deployed plug-in with the JAR file from the plugins directory
of the IBM Content Navigator installation directory.
Important: If the plug-in configuration in the administration tool
specifies the fully qualified path (rather than the fully qualified URL) of the plug-in JAR file,
you must replace the JAR file that is deployed on each node in your cluster.