blog admin

IBM ACCE

Download Document Content in FileNet

August 25, 2020

You can also download document content in bulk using JavaScript. Following are the steps:

Logon to http://servername:9080/acce/
Go to the Search tab.
Select New object Store Search.
Select SQL View and mention your query to execute

Note: You can amend this query according to where clause.

SELECT TOP 100 This FROM Document;

Make sure bulk action is enabled.
Run Script must be selected.

Please change the output directory according to your environment. Make sure directory should be existing on the server.
importClass(Packages.com.filenet.api.collection.ContentElementList); importClass(Packages.com.filenet.api.core.ContentTransfer); importClass(java.io.FileOutputStream); importClass(java.io.InputStream); importClass(java.lang.Byte); function OnCustomProcess (CEObject)
{
CEObject.refresh();
var ce = CEObject.get_ContentElements();
if(ce.size() > 0)
{
var ct = ce.get(0);
var folderName = "/media/temp/content/"; // output directory         this._downloadContent(folderName, ct);
}
}
function _downloadContent(folderName, ct)
{
var out = new FileOutputStream(folderName + ct.get_RetrievalName());
var docLen = ct.get_ContentSize().intValue();
var buf = java.lang.reflect.Array.newInstance(Byte.TYPE, docLen)
var stream = ct.accessContentStream();
stream.read(buf, 0, docLen);
out.write(buf);
out.flush();
stream.close();
out.close();
}

Here is the screenshot:

Run this search and its output will be like:

Close this dialogue box.
Go to the output directory and you will see the download document content there as below:

For further details please visit knowledge center https://www.ibm.com/support/knowledgecenter/en/SSNW2F_5.2.1/com.ibm.p8.ce.admin.tasks.doc/p8pcc439.htm

IBM Case Manager (ICM), IBM Case Manager Client

Security Attributes Disallow Access Error in IBM Case Manager Client

August 17, 2020

FNRPE2131090068E security attributes disallow access error received recently, when we did upgrade IBM FileNet P8 system to 5.2.1 level. We didn’t upgrade IBM Case Manager and it was remained on version 5.1.1.0. After successful upgrade, It took too much time to populate Add Case list, Cases tab, and In-Baskets when trying to access IBM Case Manager Client.

When we enabled the console log, it shows the error FNRPE2131090068E security attributes disallow access. Here is the screenshot of Network tab while loading roles:

Here is the stack that is logged in the Process Engine Server log:
2013/10/18 10:21:00.735-0700 4624:WT=5 Reg#2 [Error] FNRPE2131090068E ; Exception: Security attributes disallow access. There is no additional information available. at filenet.jpe.rpc.orb.orb_rpc_fetchApplicationSpaces.execute(orb_r pc_fetchApplicationSpaces.java:82) at filenet.jpe.rpc.orb.ORBPERPC.orb_rpc_fetchApplicationSpaces(ORBP ERPC.java:3635) at filenet.pe.peorb.FileNet_PERPC.PERPCPOA._invoke(PERPCPOA.java:16 83) at com.ibm.CORBA.poa.POAServerDelegate.dispatchToServant(POAServerD elegate.java:407) at com.ibm.CORBA.poa.POAServerDelegate.internalDispatch(POAServerDe legate.java:339) at com.ibm.CORBA.poa.POAServerDelegate.dispatch(POAServerDelegate.j ava:262) at com.ibm.rmi.iiop.ORB.process(ORB.java:533) at com.ibm.CORBA.iiop.ORB.process(ORB.java:1574) at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2956) at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2823) at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:65) at com.ibm.rmi.iiop.WorkerThread.run(ThreadPoolImpl.java:193) at java.lang.Thread.run(Thread.java:738)

This is the response in JSON:
{“msg”:”filenet.vw.api.VWServerException”,”UnderlyingDetails”:{“Causes”:[“[FNRPE0450130071E] Security
attributes disallow access to Solution Name.”,”[FNRPE2131090068E]Security attributes disallow
access.\n”]},”UserMessage”:{“UniqueId”:”FNRPE2131090068E”,”Severity”:”ERROR”,”Text”:”[FNRPE2131090068E
]Security attributes disallow access.\n”}}

Environment:

IBM ICM 5.1.1.0
WAS 7.0.0.23
CPE 5.2.1.7
CF 5.2.1.7
CSS 5.2.1.6
XT 1.1.5.2
Daeja ViewOne Pro 4.0.26

Solution:

As per IBM recommendations, this problem is fixed in IBM Case Manager FP 5.1.1.3/4.To fix this issue permanently, apply ICM 5.1.1.4 and problem will be solved.

Tech note: https://www.ibm.com/support/pages/apar/PJ43102

IBM Cognos

Cannot Install Cognos BI Using issetup on Linux

March 16, 2020

After downloading and trying to install IBM Cognos Real Time Monitoring in gui or graphical mode, it generates error:

Cannot install Cognos BI using issetup on Linux. libXm.so.4 is missing
./issetup: error while loading shared libraries: libXm.so.4: cannot open shared object file: No such file or directory

cannot_install_cognos_bi_using_issetup_on_linux

Environment:

WebSphere Application Server (WAS) 9.0.0.7
Cognos Real Time Monitoring (RTM) 10.2.1
Case Manager (ICM) 5.3.3.5
Oracle 11g 11.2.2.0.1

Solution:

For Cognos 10.2, you must install both the 32-bit and 64-bit OpenMotif packages.

openmotif.x86_64 (RHEL)
openmotif.i686 (RHEL6)

Run issetup command again.
Installer will be prompted properly without any error as demonstrated in below screenshot:

For more details, please visit these tech notes:

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

IBM Case Manager Timeline Visualizer Widget Exception after Upgrade to ICN 3.0.7

March 10, 2020

Since Content Navigator (ICN) 3.0.7 and its interim fix 3.0.7.001 has been released which is compatible with Content Platform Engine (CPE) 5.5.4.x. After upgraded to ICN 3.0.7.001 version, when tried to open case details page in Case Manager Client desktop, IBM case manager timeline visualizer widget generated an exception which is logged in systemout.log:

A connection to the web client cannot be established by using the following url …
java.lang.NoSuchMethodError: filenet/vw/server/rpc/chrpc/CHHistogramResult.getCH_BIN_WIDTH()I (loaded from file:/opt/WAS9/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/acmNode06Cell/navigator.ear/navigator.war/WEB-INF/lib/eeapi.jar by
com.ibm.ws.classloader.CompoundClassLoader@3339d91a[war:navigator/navigator.war]
  Local ClassPath: /opt/WAS9/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/acmNode06Cell/navigator.ear/navigator.war/WEB-INF/classes:
  Parent: com.ibm.ws.classloader.CompoundClassLoader@9d258aa4[PL][app:navigator]
  Delegation Mode: PARENT_LAST) called from class com.ibm.ecm.extension.icm.services.impl.CaseHistoryOverviewService (loaded from file:/opt/ICM/CaseManagement/configure/properties/plugins/ICMAPIPlugin.jar by java.net.FactoryURLClassLoader@bd041caa).

ibm case manager timeline visualizer widget

Environment:

WAS 9.0.5.2
ICM 5.3.3.0.5
ICN 3.0.7.1
CPE 5.5.4

Solution:

IBM Case Manager (ICM) 5.3.3.0.IF0066 fix pack has been released you can download from fix central.
Download, install or upgrade to IBM Case Manager (ICM) 5.3.3.0.IF006.
Deploy solutions using IBM Case Builder.
Open IBM Case Manager Client desktop again, open any case details page, you will see ibm case manager timeline visualizer widget is displaying all the events and data properly without any exception as mentioned in screenshot below:

Note: This error actually happens, because IBM made some changes to the methods used by the ibm case manager timeline visualizer widget in CPE 5.5.4, including the method in the error:

java.lang.NoSuchMethodError: filenet/vw/server/rpc/chrpc/CHHistogramResult.getCH_BIN_WIDTH().

This is planned to be fixed in Case Manager 5.3.3 IF06. For more details, please visit the case discussed on IBM Support Tech. https://www.ibm.com/mysupport/s/case/5000z00001PAM3WAAX/case-details-page-shows-exception-in-ibm-icm-client-53305

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

java.lang.reflect.invocationtargetexception Error – Creating or Enabling Case History Store in IBM icmadmin

January 17, 2020

java.lang.reflect.invocationtargetexception exception is received while creating or enabling case history store in ibm case manager configuration desktop. After upgrading IBM Content Navigator 2.0.3.7 and IBM Case Manager 5.2.1.7, an exception occurred while creating and enabling case history store in IBM Content Navigator icmadmin desktop for Case Manager which is:

Caused by: java.lang.reflect.invocationtargetexception at filenet.vw.server.rpc.BaseCHASession.executeRPC(BaseCHASession.java:170

Below is the problem screenshot:

In systemout.log file, exception is described here:

[1/8/20 20:25:29:883 PKT] 0000001b SystemOut O CIWEB.ICMAdminClientPlugin Error: [p8admin(unknown) @ 192.168.10.10] com.ibm.ecm.icm.accm.services.CreateCaseHistoryStoreService.callBackend() ACCM service is throwing exception
com.ibm.ecm.icm.accm.util.AccmException: java.lang.reflect.InvocationTargetException
at com.ibm.ecm.icm.accm.repository.ConfigureObjectStore.createCaseHistoryStore(ConfigureObjectStore.java:194)
at com.ibm.ecm.icm.accm.services.CreateCaseHistoryStoreService.callBackend(CreateCaseHistoryStoreService.java:98)
at com.ibm.ecm.icm.accm.services.CreateCaseHistoryStoreService.doExecute(CreateCaseHistoryStoreService.java:65)
at com.ibm.ecm.icm.accm.services.BaseService.execute(BaseService.java:130)
at com.ibm.ecm.util.PluginUtil.invokeService(PluginUtil.java:1294)
at com.ibm.ecm.struts.actions.PluginAction.executeBaseAction(PluginAction.java:144)
at com.ibm.ecm.struts.actions.BaseAction.execute(BaseAction.java:502)
at com.ibm.ecm.jaxrs.Actions.loadAndExecuteAction(Actions.java:280)
at com.ibm.ecm.jaxrs.Actions.handleAction(Actions.java:101)
at com.ibm.ecm.jaxrs.Actions.handleGetActions(Actions.java:116)
at sun.reflect.GeneratedMethodAccessor63.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
at org.apache.wink.server.internal.handlers.InvokeMethodHandler.handleRequest(InvokeMethodHandler.java:63)
at org.apache.wink.server.handlers.AbstractHandler.handleRequest(AbstractHandler.java:33)
at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:63)
at org.apache.wink.server.internal.handlers.CreateInvocationParametersHandler.handleRequest(CreateInvocationParametersHandler.java:54)
at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:63)
at org.apache.wink.server.internal.handlers.FindResourceMethodHandler.handleSubResourceMethod(FindResourceMethodHandler.java:183)
at org.apache.wink.server.internal.handlers.FindResourceMethodHandler.handleRequest(FindResourceMethodHandler.java:110)
at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:63)
at org.apache.wink.server.internal.handlers.FindRootResourceHandler.handleRequest(FindRootResourceHandler.java:95)
at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:63)
at org.apache.wink.server.internal.handlers.HeadMethodHandler.handleRequest(HeadMethodHandler.java:53)
at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:63)
at org.apache.wink.server.internal.handlers.OptionsMethodHandler.handleRequest(OptionsMethodHandler.java:46)
at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:63)
at org.apache.wink.server.internal.handlers.SearchResultHandler.handleRequest(SearchResultHandler.java:33)
at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:63)
at org.apache.wink.server.internal.log.ResourceInvocation.handleRequest(ResourceInvocation.java:92)
at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:63)
at org.apache.wink.server.internal.log.Requests.handleRequest(Requests.java:76)
at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:63)
at org.apache.wink.server.handlers.AbstractHandlersChain.run(AbstractHandlersChain.java:48)
at org.apache.wink.server.internal.RequestProcessor.handleRequestWithoutFaultBarrier(RequestProcessor.java:207)
at org.apache.wink.server.internal.RequestProcessor.handleRequest(RequestProcessor.java:154)
at org.apache.wink.server.internal.servlet.RestServlet.service(RestServlet.java:119)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1657)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1597)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:131)
at com.ibm.ecm.filters.ESAPIWafFilter.doFilter(ESAPIWafFilter.java:231)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:934)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:181)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:91)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:864)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1592)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)
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:1613)
Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at com.ibm.casemgmt.config.ContentEngineHelper.createCaseHistoryStore(ContentEngineHelper.java:7481)
at com.ibm.ecm.icm.accm.repository.ConfigureObjectStore.createCaseHistoryStore(ConfigureObjectStore.java:175)
… 82 more

Environment:

WebSphere Application Server 7.0.0.23
Content Platform Engine 5.2.1.7
Workplace XT 1.1.5.2
Content Navigator 2.0.3.7
Case Manager 5.2.1.7

In trace.log file pointed that eeapi.jar, peResources.jar files are mismatched version in WebShpere Application server /lib/ directory from deployed navigator.war/WEB-INF/lib/ folder.

Solution:

Stop the WAS JVM where ICM / ICN deployed.
Copy the eeapi.jar, peResources.jar following files from deployed navigator path: /opt/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/acmNode02Cell/navigator.ear/navigator.war/WEB-INF/lib/
Paste or replace these files on path: /opt/IBM/WebSphere/AppServer/lib/
Clear the /tmp /wstemp directories under the WAS.
Start the WAS JVM where ICM / ICN deployed.

Again logon icmadmin desktop, try to create / enable the case history store again, and finally, case history store will be created and enables successfully as descibed in the screenshot and java.lang.reflect.invocationtargetexception excpetion will gone in logs:

Here is the technote: https://www.ibm.com/support/pages/node/1172686?myns=swgimgmt&mynp=OCSSCTJ4&mync=E&cm_sp=swgimgmt--OCSSCTJ4--E

IBM Case Manager (ICM), IBM Case Manager Builder

FNRPA0024E The Content Platform Engine is not Available Error in IBM Case Builder 5.2.1

January 17, 2020

FNRPA0024E The Content Platform Engine is not available or the connection definition is inaccurate error generated in filenet p8 when logon into Case Manager Builder. As described in below screenshot:

Here is the error description in systemout.log file:

[1/12/20 19:40:24:312 PKT] 0000001f handler E com.ibm.casemgmt.intgimpl.messages.CaseMgmtLogger error FNRPA0024E The Content Platform Engine is not available or the connection definition is inaccurate.
com.ibm.casemgmt.api.exception.CaseMgmtException: fnrpa0024 the content platform engine is not available or the connection definition is inaccurate.
at com.ibm.casemgmt.api.exception.CaseMgmtException.createException(CaseMgmtException.java:112)
at com.ibm.casemgmt.api.exception.CaseMgmtException.access$1800(CaseMgmtException.java:62)
at com.ibm.casemgmt.api.exception.CaseMgmtException$ClassBridgeImpl.createException(CaseMgmtException.java:457)
at com.ibm.casemgmt.api.context.BaseVWSessionCache.getVWSession(BaseVWSessionCache.java:80)
at com.ibm.casemgmt.api.admin.ConnectionDefinition.loadIfNecessaryAndGetVWSession(ConnectionDefinition.java:126)
at com.ibm.casemgmt.api.admin.ConnectionDefinition.getTargetObjectStoreReference(ConnectionDefinition.java:139)
at com.ibm.casemgmt.rest.handlers.RetrieveSolutionListHandler.onGet(RetrieveSolutionListHandler.java:121)
at com.ibm.casemgmt.rest.ACMRESTServlet.doMethod(ACMRESTServlet.java:386)
at com.ibm.casemgmt.rest.ACMRESTServlet.doGet(ACMRESTServlet.java:240)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:718)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1657)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1597)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:104)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:934)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:181)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:91)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:864)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1592)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)
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:1613)
Caused by: The Web Application id 11 is reserved
at filenet.vw.api.VWSession.setDefaultWebApplication(VWSession.java:3711)
at com.ibm.casemgmt.api.context.BaseVWSessionCache.getVWSession(BaseVWSessionCache.java:69)
… 31 more

I’ve also tried IBM Tech note to resolve the problem, but in my environment it didn’t work. https://www.ibm.com/support/pages/fnrpa0024e-content-platform-engine-not-available-or-connection-definition-inaccurate-error-generated-when-logging-case-manager-case-builder

Environment:

WebSphere Application Server 7.0.0.23
Content Platform Engine 5.2.1.7
Workplace XT 1.1.5.2
Content Navigator 2.0.3.7
Case Manager 5.2.1.7

Basically, I was upgrading whole IBM FileNet P8 environment to 5.2.1. All components were successfully upgraded to their updated state but in last step, when tried to upgrade solutions in IBM Case Manager Builder, exception occurred, “FNRPA0024E The Content Platform Engine is not available or the connection definition is inaccurate”.

Solution:

After enabling the classloader trace in WAS as described on https://www.ibm.com/support/pages/mustgather-classloader-problems-websphere-application-server and reproduced the problem again.

Enable and collect Application Server traces with the following trace string:
com.ibm.ws.classloader.*=all
Enable Java™ Virtual Machine (JVM) classloader traces through the Admin console as mentioned:

Select Servers, choose Application servers and select the server you want to configure.
In the Server Infrastructure section, open Java and Process Management and selectProcess Definition.
Under Additional Properties, select Java Virtual Machine.
Check the Verbose class loading checkbox.
Add the following string to the Generic JVM arguments field:
-Dws.ext.debug=true -Dws.osgi.debug
Click OK.
Save the changes. Restart the server.

In trace.log file pointed that jace.jar, pe.jar. pe3pt.jar, and json4j_apache.jar files are mismatched version in WebShpere Application server /lib/ directory from deployed CaseBuilder.war/WEB-INF/lib/ folder.

Stop the WAS JVM where ICM / ICN deployed.
Copy the jace.jar, pe.jar. pe3pt.jar, and json4j_apache.jar following files from deployed Case Builder path: /opt/IBM/WebSphere/AppServer/profiles/AppSrv02/installedApps/acmNode02Cell/CaseBuilder.ear/CaseBuilder.war/WEB-INF/lib/
Paste or replace these files on path: /opt/IBM/WebSphere/AppServer/lib/
Clear the /tmp /wstemp directories under the WAS.
Start the WAS JVM where ICM / ICN deployed.

Hope so, problem will be resolved and user can logging into IBM Case Builder successfully.

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 Platform Engine (CPE)

IBM FileNet Bulk Search and Update in Existing Document Class

December 9, 2019

Sometimes to meet the users requirements, we have to perform bulk operations such as; FileNet P8 bulk search and update existing document class(es) property value(s). Users want to add a new property to particular document class and want to update the existing records to populate this into new property.

There are three mechanisms to achieve this requirements;

FileNet Bulk Search and Update using FileNet vbscript.
Sweep jobs in FileNet or FileNet custom sweep job.
Set document property using JavaScript.

Here we are illustrating FileNet Bulk Search and Update using FileNet vbscript. You can configure as followed to add the new property template to the existing class and documents:

Add a new property template via FileNet Enterprise Manager (FEM) or FileNet ACCE.
Go to your document class – Property Definition tab and add the new property template to it then refresh the object store.
The new property template will be added to the existing document but contains no value.
To update the property value of several objects at the same time for the existing documents, you can use the Content Engine Enterprise Manager’s Search feature. First, using the Enterprise Manager, you will need to determine the Symbolic Name of the property that you want to modify. To do this, select the property under the “Property Templates” node and look for the value for the “Symbolic Name” property on the Properties tab.
Perform the new search and define the criteria for the new search.

Once search completed with results, do the following step by step.

filenet enterprise manager multi select operations

Select all the results values and perform multiselect operations option as mentioned above.

Bulk Operations window will be prompted, go the the script tab and paste the following script in the FileNet vbscript window (Please change the symbolic name of the property value according to yours):

 Public Sub OnCustomProcess (CEObject) 
 CEObject.DHA_Br_Ingestion = "BC" 
 CEObject.Save 
 End Sub

To confirm the FileNet bulk search and update results, try to search again you will see new property value is updated accordingly.

Query:

For further confirmation, you can also query from filenet docversion table. Here is the query:

select COUNT(docversion.u0398_dha_br_ingestion) AS TOTAL, classdefinition.symbolic_name 
 from docversion, classdefinition 
 where docversion.u0398_dha_br_ingestion IN ('BC','Tfr')
 and docversion.object_class_id = classdefinition.object_id
 group by classdefinition.symbolic_name
 UNION ALL
 SELECT SUM(TOTAL), 'SUM of All' from (
 select COUNT(docversion.u0398_dha_br_ingestion) AS TOTAL, classdefinition.symbolic_name 
 from docversion, classdefinition 
 where docversion.u0398_dha_br_ingestion IN ('BC','Tfr')
 and docversion.object_class_id = classdefinition.object_id
 group by classdefinition.symbolic_name
 )
 a

In next post, I’ll share other two options; custom sweep job and set document property using JavaScript. For information about FileNet bulk search and update please refer to following Tech notes:

IBM Content Navigator (ICN)

Failure to Launch IBM Content Navigator Configuration and Deployment Tool 3.0.6 IF002

October 17, 2019

On 19 September, 2019 IBM Content Navigator 3.0.6 IF002 is released. Which addressed and provide solutions to many problems for its previous version. One thing that is observed while applying / upgrading IBM Content Navigator (ICN) fix pack 3.0.6.2, failure to launch IBM ICN configuration and deployment tool after upgrading from 3.0.6.0 IF001.

IBM Content Navigator configuration and deployment tool does not load and an error occurs:

Symptom:
/opt/IBM/ECMClient/unzipear.xml:8: Error while expanding /opt/IBM/ECMClient/configure/deploy/navigatorEAR.ear
java.util.zip.ZipException: invalid stored block lengths
at org.apache.tools.ant.taskdefs.Expand.expandFile(Expand.java:148)
at org.apache.tools.ant.taskdefs.Expand.execute(Expand.java:107)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at com.zerog.ia.installer.util.AntUtility.go(Unknown Source)
at com.zerog.ia.installer.actions.AntRunner.installSelf(Unknown Source)
at com.zerog.ia.installer.InstallablePiece.install(Unknown Source)
at com.zerog.ia.installer.InstallablePiece.install(Unknown Source)
at com.zerog.ia.installer.GhostDirectory.install(Unknown Source)
at com.zerog.ia.installer.InstallablePiece.install(Unknown Source)
at com.zerog.ia.installer.Installer.install(Unknown Source)
at com.zerog.ia.installer.actions.InstallProgressAction.ae(Unknown Source)
at com.zerog.ia.installer.actions.ProgressPanelAction$1.run(Unknown Source)
Caused by: java.util.zip.ZipException: invalid stored block lengths
at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:175)
at java.io.FilterInputStream.read(FilterInputStream.java:118)
at org.apache.tools.ant.taskdefs.Expand.extractFile(Expand.java:286)
at org.apache.tools.ant.taskdefs.Expand.expandFile(Expand.java:141)
… 21 more

Solution:

Please make sure, before the upgradation of IBM ICN 3.0.6 IF002, grant full permission for the user running the install to the ECMClient directory.
Run the following command to assign full rights to root user:

chmod -R 777 Path of ICN installed directory (/opt/IBM/ECMClient/)

Once installed, try to run /opt/IBM/ECMClient/configure/./configmgr again, configuration and deployment tool will be launched successfully as described:

Older Posts

Newer Posts

Archives

Download Document Content in FileNet

Security Attributes Disallow Access Error in IBM Case Manager Client

Environment:

Solution:

Cannot Install Cognos BI Using issetup on Linux

Environment:

Solution:

IBM Case Manager Timeline Visualizer Widget Exception after Upgrade to ICN 3.0.7

Environment:

Solution:

java.lang.reflect.invocationtargetexception Error – Creating or Enabling Case History Store in IBM icmadmin

Environment:

Solution:

FNRPA0024E The Content Platform Engine is not Available Error in IBM Case Builder 5.2.1

Environment:

Solution:

Java.lang.Outofmemoryerror Error while Deploying IBM Content Navigator

The Repository is not Available While Creating in IBM Content Navigator

Environment:

Solution:

IBM FileNet Bulk Search and Update in Existing Document Class

Query:

Failure to Launch IBM Content Navigator Configuration and Deployment Tool 3.0.6 IF002

Solution:

Subscribe