ibm content navigator Archives - iparagons blog ibm icn

IBM Content Navigator Pagination

October 9, 2020

IBM Content Navigator pagination limit setting will be implemented in this post. When browsing a folder within IBM Content Navigator (ICN), 200 results are shown per page by default. Even though folder or search results contain more than 200 values. Here is the description:

Environment:

IBM Content Navigator 2.0.3.x
IBM Content Navigator 3.0.x

Solution:

You can configure the page size (the number of items retrieved) on the ICN server by setting a pageSize environment variable at OS level. Do the following for ibm content navigator pagination settings:

Edit vi /root/.bash_profile and amend.

pageSize=1000; export pageSize;

save and close.
The application server where ICN is deployed must be restarted after the environment variable is defined in order to take effect.

Once done, you will see status bar will show the exact values in ICN desktop as described in below screenshot:

For details, please visit these tech notes.

IBM Content Navigator (ICN)

Java.lang.Outofmemoryerror Error while Deploying IBM Content Navigator

December 31, 2019

When you try to deploy IBM Content Navigator (ICN) on a WebSphere Application Server (WAS), deployment fails. The deployment failure usually occurs with WebSphere Application Server 7, but can also occur with other versions also.

Exception generated like; Java.lang.Outofmemoryerror error in console window of IBM Content Navigator configuration and deployment tool. Perform the any one of followings:

First way is to increase heap size of wsadmin jvm before deploying ibm content navigator.

Run the following command to increase heap size of jvm.

./wsadmin.sh  -javaoption "-Xms1024m" -javaoption "-Xmx2048m"

Than try to deploy the content navigator, it will be deployed successfully.

2. The second is way is to edit wsadmin.sh script and increase the heap size of jvm like;

Go to directory: /opt/WAS9/IBM/WebSphere/AppServer/bin/
Edit the wsadmin.sh script.
Increase the heap size.

Problem will be solved for content navigator successful deployment. For more details please go through these tech notes

IBM Content Navigator (ICN)

The Repository is not Available While Creating in IBM Content Navigator

December 19, 2019

After Installing or upgrading IBM Content Navigator 2.0.3 IF007, unable to create new repository using IBM Content Navigator admin desktop and it failed to connect. Error is the repository is not available which is attached below:

SystemOut.log file generated following error:

13/02/28 15:01:20:943 JST 0000001f SystemOut O CIWEB Error: p8admin @ servername.domain.com com.ibm.ecm.struts.actions.p8.P8LogonAction.executeAction()
com.filenet.api.exception.EngineRuntimeException:
FNRCA0031E: API_UNABLE_TO_USE_CONNECTION:
The URI for server communication cannot be determined from the connection object Class=com.filenet.apiimpl.core.ConnectionImpl
URI=iiop://tsv103376a:2809/FileNet/Engine Parameters={}.
at com.filenet.apiimpl.util.SessionLocator.getSession(SessionLocator.java:241)
at com.filenet.apiimpl.core.IndependentObjectImpl.getObject(IndependentObjectImpl.java:148)
at com.filenet.apiimpl.core.IndependentObjectImpl.refresh(IndependentObjectImpl.java:157)
at com.filenet.api.core.Factory$EntireNetwork.fetchInstance(Factory.java:359)
at com.ibm.ecm.struts.actions.p8.P8LogonAction.createP8Connection(P8LogonAction.java:256)
at com.ibm.ecm.struts.actions.p8.P8LogonAction.createP8Connection(P8LogonAction.java:136)
at com.ibm.ecm.struts.actions.p8.P8LogonAction.executeAction(P8LogonAction.java:100)
at com.ibm.ecm.struts.actions.p8.P8BaseAction.executeBaseAction(P8BaseAction.java:180)
at com.ibm.ecm.struts.actions.BaseAction.execute(BaseAction.java:176)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at com.ibm.ecm.struts.controller.ControllerServlet.process(ControllerServlet.java:239)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1224)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:774)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:456)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:79)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:928)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1025)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3751)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:962)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1690)

Environment:

FileNet Content Platform Engine 5.2.x
Content Navigator 2.0.3.x
WebSphere Application Server 8.5.5.x

Solution:

If you plan to run Content Platform Engine (CPE) and Content Navigator (ICN) in separate WebSphere Application Server profiles but on the same physical server, you must add a custom Java property to both WebSphere Application Server instances or profiles where CPE and ICN are deployed to resolve the repository is not available error. Perform the following steps:

Open the administrative console of the WebSphere Application Server instance on which Content Platform Engine is deployed.
Expand Application servers and click the server name on which Content Platform Engine runs. The default server name is Server1.
Expand Java and process management and click Process definition > Java virtual machine > Custom properties.
Click New.
Enter the name of property com.ibm.websphere.orb.uniqueServerName and set its value to true.
Save your settings and restart the application server.
Repeat the entire procedure for the WebSphere Application Server on which IBM Content Navigator is deployed.

Once done, try to create a new repository in IBM Content Navigator admin desktop. Repository will be connected successfully as described here:

IBM Content Navigator (ICN)

How to Enable Process Designer in ICN

October 4, 2019

Since IBM has launched IBM FileNet P8 related tools such as; Process Designer and Process Administrator which were previously available in IBM FileNet Workplace XT initially. Later on, thesethese features shift to Advanced Content Console for Content Engine (ACCE) and Content Navigator (ICN).

As you installed and configured IBM CPE 5.2.x or 5.5.x versions, by default these features are available in ACCE. On the other hand side, these features can also be enabled in IBM Content Navigator as well on specific desktop if needed. So, how to enable process designer in ICN without workplace XT?

Step by Step Instructions:

You can enable Process Designer to be run from IBM Content Navigator by configuring the appropriate desktops and menus which are demonstrated step by step as under:

Browse to your Content Navigator admin URL ( http://<icn-server>:<port>/navigator?desktop=admin )
Go to Settings > Plug-ins > New Pugin.
Type the url of plug-in or use the installed path of plug-in.
Register CPEAppletsPlugin in ICN.
Save and close Plug-ins section.

Go to Repositories and select your FileNet object store (e.g. FNTOSP8).
Connect to the object store.
Go to Configuration Parameters.
Scroll down and set “Display workflow definition class” to TRUE.
Save and Close to update your configuration.

Go to Menus and scroll down to Default repository context menu.
Type in a name (e.g. My Repository context menu).
Scroll through the “Available” ICN actions and select Process Designer and Process Tracker.
Click the arrow to add these two actions to your new menu.
Save and Close to create your new, custom ICN menu.

Go to Desktops, Select an existing desktop, or Add New Desktop.
Change Default Repository folder context menu to My Repository Folder Context Menu.
Save and Close to update your configuration.

Once you made above changes accordingly, logon through desktop for which you have configured process designer in icn.

Right click on top of the desktop repository name e.g. FNTOSP8 (In my environment).
You will see there is option of Workflow and furthermore these two options are available; process designer and process tracker as you can see below:

Hence, how to enable process designer in icn can be done by doing above steps. For more information please visit: Configuring Process Designer to run from IBM Content Navigator.

IBM Case Manager (ICM), IBM Content Navigator (ICN)

Unable to Preview Documents in IBM Content Navigator 3.0.6.x

August 17, 2019

As mentioned in last post about document conversion into view-able format problem in IBM Content Navigator 3.0.6. Clearly described, you have to revert it back to ICN 3.0.5.x version because according to ibm filenet compatibility matrix report it does not support IBM Case Manager 5.3.3.3 version yet.

Now, ICN fix pack 3.0.6.1 has been released which supports IBM Case Manager 5.3.3.3 fp. But problem persisting and users are unable to preview documents in any of desktop including ICN and ICM.

According to software compatibility report, new release of ICM fix pack 5.3.3.0.4 also supports ICN 3.0.6.1 and preview bug is resolved in this release for Case Manager.

One more way around that is given in fix pack readme file that:

Document thumbnails or preview
On AIX platform Case Package preview may not function as expected. The following steps can be used as a work around.
Add the following line to the “DocServices.properties.default” file. This file is located at <AppServerDir>/installedApps/<node>/navigator.ear/navigator.war/WEB-INF/DocServices.properties.default
Restart the application server.

I’ve also tried above steps but no luck and still unable to generate thumbnails of documents in any of ICN desktop.

Solution:

First way to sort out this problem is described here step by step:

Step 1

Download the icnviewing.jar file first. You can get this file inside the navigator extracted package.
Delete old icnviewing.jar file from deployed navigator path (Don’t rename original one just move to somewhere else location).
Copy downloaded file to deployed navigator step 2.
Also copy icnviewing.jar file to navigator deployed path (
/opt/WAS9/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/ICMServerNode02Cell/navigator.ear/navigator.war/WEB-INF/classes/).
Stop ICN JVM WAS, clear WAS cache, and start ICN JVM WAS again.
Try to preview document again in ibm icm desktop again. Problem will be solved, if not post your comment please.

Step 2

There is also second way around to use snowbound viewer and perform following steps:

Download SnowboundLicense.jar file if you have their license.
Extract files of SnowboundLicense-20.0.0.jar files into WAS where navigator is deployed as described:

/opt/WAS9/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/ICMServerNode02Cell/navigator.ear/navigator.war/WEB-INF/classes/

Note: Please amend above path according to your deployment.

Copy SnowboundLicense.jar:

 /opt/WAS9/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/ICMServerNode02Cell/navigator.ear/navigator.war/WEB-INF/lib/

Restart WAS JVM Where ICN is deployed.
Open any if IBM Content navigator or IBM Case Manager desktop and try to preview document. Now when you click on document, thumbnail preview will be generated. Secondly, when you will click on preview option by right clicking of any document, preview will be shown properly as described here:

Same problem occurred when i applied IBM ICN 3.0.6 IF 003 as well. Performed the above steps accordingly:

Copy icnviewing.jar file to /opt/WAS9/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/ICMServerNode02Cell/navigator.ear/navigator.war/WEB-INF/classes/ directory.
Restart WAS.
Try to preview documents again, hope so issue will be gone.

IBM Content Navigator (ICN)

The Document Cannot be Converted into a Viewable Format IBM ICN 3.0.6

July 24, 2019

In last month, IBM Content Navigator (ICN) 3.0.6 is introduced. I’ve applied this new release with IBM Case Manager (ICM) 5.3.3.0. After successful upgrade and deploy ICN 3.0.6 there was a new problem occurred while preview documents in IBM Case Manager Client desktop which is elaborated here:

By default when we click on any document in ICM, its thumbnails / preview automatically generated according to its mime type. But in this case, it doesn’t work and only document type was mentioned instead of preview document. Below is the error screenshot:

CIWEB1059
CIWEB1059: The document cannot be converted into a viewable format.
The document might have been deleted, the repository server
might not be running, or the viewer cannot convert the selected document.
Close the viewer, refresh the list of documents, and try to open the document again.
If the problem persists, contact your system administrator with the following information:
java.io.IOException: java.util.concurrent.ExecutionException:
com.ibm.mm.viewer.CMBDocumentEngineException:
Document was not recognized as a supported format.

I’ve also tried these two tech notes but didn’t work in my case.

https://www-01.ibm.com/support/docview.wss?uid=swg21992118

https://www-01.ibm.com/support/docview.wss?uid=swg21999391

But no luck. After talk to IBM Rep, identified that ICN 3.0.6 is yet not supported with ICM 5.3.3.x version but its upcoming ICN FP 3.0.6.x will be supported with ICM.

One can also confirm ibm software compatibility report as well. So there is only one option to revert back ICN to its previous version or state.

There is one more solution that is posted by IBM on 23 March 2020, you can also try this please: https://www.ibm.com/support/pages/node/6113362?myns=swgother&mynp=OCSSEUEX&mync=E&cm_sp=swgother--OCSSEUEX--E

Solution: Please read this post.

IBM Case Manager (ICM)

The Solution cannot be Retrieved Possibly Because it is not a Version 18.0 Solution

December 24, 2018

The solution cannot be retrieved exception when open solution in process designer. When a user tries to open and edit an IBM Case Manager V5.3.3 solution with Process Designer, the solution will not open and the following error will be logged in the application server logs:

SystemOut O CIWEB.CPEAppletsPlugin Error: [p8admin(unknown) @ xx.x.xxx.xxx] com.ibm.ecm.cpea.CPEApplets.CPEAppletListenerPluginService.execute()
The solution cannot be retrieved, possibly because it is not a version 18.0 solution.
If this solution is not at the version 18.0 level, it must be upgraded before you can open it in Process Designer.
Upgrade the solution to the version 18.0 level by using Case Builder and then try again to open the solution in Process Designer.

Here is the screenshot of problem description:

Environment:

ICN 3.0.3 IF004
ICN v3.0.4
ICM 5.3.3

Solution:

To resolve the solution cannot be retrieved error permanently in IBM Content Navigator (ICN) v3.0.3, apply ICN 3.0.3-IF005, as the problem has been corrected.

For ICN v3.0.x or v3.0.4-IF001, the problem can be resolved by replacing the ICMSolutionEdit.jar shipped with IBM Content Navigator with the one that is shipped with IBM Case Manager.

Copy the ICMSolutionEdit.jar from the Case Manager install directory:

\CaseManagement\WorkplaceXTConfig

into the following Navigator install directory:

\ECMClient\configure\explodedformat\navigator\WEB-INF\lib

After this, launch IBM Content Navigator Configuration and Deployment Tool and run the following tasks:

– Build the Web Application

– Deploy the Web Application

Once done, try again to edit solution in process designer after restart Application Server, problem will be solved as describer below:

open-edit-solution-Workplacext-processdesigner

Reference: https://www-01.ibm.com/support/docview.wss?uid=ibm10718327

ibm content navigator

IBM Content Navigator Pagination

Environment:

Solution:

Java.lang.Outofmemoryerror Error while Deploying IBM Content Navigator

The Repository is not Available While Creating in IBM Content Navigator

Environment:

Solution:

How to Enable Process Designer in ICN

Step by Step Instructions:

Unable to Preview Documents in IBM Content Navigator 3.0.6.x

Solution:

Step 1

Step 2

The Document Cannot be Converted into a Viewable Format IBM ICN 3.0.6

The Solution cannot be Retrieved Possibly Because it is not a Version 18.0 Solution

Subscribe