November 2018

Desktop Cannot be Found Error in IBM ICN Integrated IBM FileNet P8

November 15, 2018

There was an issue reported today when IBM Content Navigator (ICN) integrated with IBM FileNet P8 was running smoothly than suddenly when tried to open any of ICN desktops; icm, admin, icmadmin there was a window appears where it was mentioned that,

the desktop cannot be found. Ask your system administration to review web application server log file for information about why the desktop cannot be found.

Even though, navigator application was running absolutely fine in WAS administration console. Below is the problem screenshot:

Diagnosing the problem

From the ICN SystemOut.log, the following exception is happening after opening url of Admin/icm/icmadmin/ier desktops:

[11/15/18 11:21:27:171 PKT] 000000ec SystemOut O [11/15/18 11:21:27:171 PKT] 000000ec SystemOut O CIWEB Error: [ ] null.processCleanup() There was a SQL configuration error. org.apache.commons.configuration.event.ConfigurationErrorEvent[source=com.ibm.ecm.configuration.DatabaseConfiguration@d92c6d5c]
[11/15/18 11:21:27:171 PKT] 000000ec SystemOut O [11/15/18 11:21:27:171 PKT] 000000ec SystemOut O CIWEB Error: [ ] com.ibm.ecm.configuration.DatabaseConfiguration.getProperty() key = settings.navigator.default
java.sql.SQLException: ORA-28001: the password has expired
DSRA0010E: SQL State = 99999, Error Code = 28,001
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382)
at oracle.jdbc.driver.T4CTTIfun.processError(T4CTTIfun.java:600)
at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthenticate.java:445)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192)
at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:380)
at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:760)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:401)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:546)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:236)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)
at oracle.jdbc.pool.OracleDataSource.getPhysicalConnection(OracleDataSource.java:280)
at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:207)
at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:139)
at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:88)
at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:70)
at com.ibm.ws.rsadapter.spi.InternalGenericDataStoreHelper$1.run(InternalGenericDataStoreHelper.java:1366)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.rsadapter.spi.InternalGenericDataStoreHelper.getPooledConnection(InternalGenericDataStoreHelper.java:1385)
at com.ibm.ws.rsadapter.spi.WSRdbDataSource.getPooledConnection(WSRdbDataSource.java:2154)
at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.getConnection(WSManagedConnectionFactoryImpl.java:1802)
at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.createManagedConnection(WSManagedConnectionFactoryImpl.java:1572)
at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.createManagedConnection(WSManagedConnectionFactoryImpl.java:1128)
at com.ibm.ejs.j2c.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:2168)
at com.ibm.ejs.j2c.FreePool.createOrWaitForConnection(FreePool.java:1838)
at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:3835)
at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:3111)
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:1548)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:1031)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:646)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:613)
at org.apache.commons.configuration.DatabaseConfiguration.getConnection(DatabaseConfiguration.java:632)
at com.ibm.ecm.configuration.DatabaseConfiguration._getProperty(DatabaseConfiguration.java:821)
at com.ibm.ecm.configuration.DatabaseConfiguration.getProperty(DatabaseConfiguration.java:788)
at org.apache.commons.configuration.AbstractConfiguration.getStringArray(AbstractConfiguration.java:1081)
at org.apache.commons.configuration.AbstractConfiguration.getProperties(AbstractConfiguration.java:607)
at org.apache.commons.configuration.AbstractConfiguration.getProperties(AbstractConfiguration.java:584)
at com.ibm.ecm.configuration.ConfigurationObject.load(ConfigurationObject.java:245)
at com.ibm.ecm.configuration.SettingsConfig.load(SettingsConfig.java:226)
at com.ibm.ecm.configuration.ConfigurationObject.<init>(ConfigurationObject.java:105)
at com.ibm.ecm.configuration.SettingsConfig.<init>(SettingsConfig.java:194)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:83)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57)
at java.lang.reflect.Constructor.newInstance(Constructor.java:437)
at com.ibm.ecm.configuration.Config._getConfiguration(Config.java:1445)
at com.ibm.ecm.configuration.Config.getConfiguration(Config.java:1498)
at com.ibm.ecm.configuration.Config.getSettingsConfig(Config.java:529)
at com.ibm.ecm.configuration.Config.getSettingsConfig(Config.java:509)
at com.ibm.ecm.configuration.ConfigWrapper.getSettingsConfig(ConfigWrapper.java:723)
at com.ibm.ecm.configuration.ApplicationConfig.getSettingsConfig(ApplicationConfig.java:638)
at com.ibm.ecm.configuration.LoggingConfigThread.run(LoggingConfigThread.java:70)

Environment:

WAS 8.5.x

ICN 3.0.x

ICM 5.3.x

Oracle 11g

Solution:

This problem occurred when icn schema password expired or user locked.

Stop IBM FileNet P8 services.
Unlock icn schema by performing following:

SELECT username, account_status FROM DBA_USERS;

ALTER profile DEFAULT limit PASSWORD_REUSE_TIME unlimited;
ALTER profile DEFAULT limit PASSWORD_LIFE_TIME unlimited;

ALTER USER ICN_USER ACCOUNT UNLOCK IDENTIFIED BY password;

Start services and try to connect to icn desktops again. It will work fine.

IBM Case Manager Client

IBM Case Manager Client Search Template Takes Time or Failed to Search Document

November 13, 2018

I’ve recent experienced a problem while using search template in IBM Case Manager Client (ICM). This issue arises after upgrading ICM from 5.1.1.x to 5.3.x in my case. Secondly, in our environment, CPE and XT on same JVM while, ICM and ICN are deployed on anther WAS profile. When tried to search document by providing metadata for that document, it takes some time first of all and after that, an exception occurred which is described below:

Problem:

Your request cannot processed. An error occurred on the Application Server Contact your system administration with the following information: FNRCD0009, CIWEB1016.

Environment:

WAS 8.5.5.x

ICM 5.3.x

ICN 3.0.x

CPE 5.2.x

Solution to resolve IBM Case Manager Search Template Loading:

Based on the error number FNRCD0009, CIWEB1016 I found this is an error related to Content Platform Engine (CPE) search (mostly text search).

Please perform the following steps:

1) Open the ICN web Admin console

2) Open Repositories

3) Select the affected repository

4) Connect to the repository as the repository admin

5) Open the Search tab

6) Increase the timeout setting x2 (e.g. 600)

7) Test the search template.

If it is still the same, go on and also following the following steps:

1) Increase the transaction lifetime timeout and the ORB Service timeout for WAS.

Open the WAS Admin console > Application server > Container Services > Transaction Service:

Set Total transaction lifetime timeout = 300

Open the WAS Admin console > Application server > Container Services > ORB Service:

Set Request timeout = 300

2)In the CPE server, increase the transaction lifetime timeout and the ORB Service timeout for the CPE application.

Open the WAS Admin console > CPE Server > Container Services > Transaction Service:

Set Total transaction lifetime timeout = 300

Open the WAS Admin console > CPE server > Container Services > ORB Service:

Set Request timeout = 300

Again, test the search in ICM client. Problem will be resolved.

IBM Case Manager (ICM)

IBM Case Manager Client Case History tab is slow sometimes

November 6, 2018

Case history tab is slow sometimes in case management software (ICM), when viewing the History tab in the Case Information widget in IBM Case Manager Client, if the case has a large number of case history records associated with it and the Event table in Content Engine has a large number of records, the views might load very slowly. Sometimes the following timeout error occurs, with very slow responses:

The case history is unavailable because of the following error: timeout exceeded (CDEWG5206E).

Problem

Open a case in the IBM Case Manager Client and click to the History tab in the Case Information widget. As you change the views, such as “Show Summary/All” and “for All/Case/Comments/etc.”, they load very slowly, for example, nearly in one minute. Below is the screenshot of problem description:

Cause

The information displayed on the History tab is stored in the Event table in the Content Engine database. The Event table index might not have been updated or configured to fit your environment needs. This causes a database performance problem.

Environment

ICM 5.1.1.x / 5.2.1.x ? 5.3.x
WAS 7.x / WAS 8.x
CPE 5.1.x / 5.2.x

Solution

Stop IBM FileNet P8 Services.
In the Content Engine Platform database (Target OS Schema), create one new index with the following definition:

DB2:

CREATE UNIQUE INDEX I_CASE_FOLDER
ON db2admin.EVENT (U88E7_CMACMCASEFOLDER ASC, AUDIT_SEQUENCE DESC)
INCLUDE (OBJECT_CLASS_ID, SOURCE_OBJECT_CLASS_ID, HOME_ID)
COMPRESS NO ALLOW REVERSE SCANS

Oracle:

CREATE INDEX I_CASE_FOLDER ON EVENT
(U88E7_CMACMCASEFOLDER ASC, AUDIT_SEQUENCE ,OBJECT_CLASS_ID, SOURCE_OBJECT_CLASS_ID, HOME_ID)
LOGGING
TABLESPACE USERS
PCTFREE 10
INITRANS 2
MAXTRANS 255
STORAGE (
INITIAL 64K
NEXT 1M
MINEXTENTS 1
MAXEXTENTS UNLIMITED
PCTINCREASE 0
BUFFER_POOL DEFAULT
)
COMPRESS REVERSE ;

Once done. Start IBM FileNet P8 Services.
Test ICM Client and click on history tab in Case Information Widget again. Now there will be no delay and Case History will be shown timely as mentioned below:

For further details, please visit this tech note http://www-01.ibm.com/support/docview.wss?uid=swg21587662

Desktop Cannot be Found Error in IBM ICN Integrated IBM FileNet P8

Diagnosing the problem

Environment:

Solution:

IBM Case Manager Client Search Template Takes Time or Failed to Search Document

Problem:

Environment:

Solution to resolve IBM Case Manager Search Template Loading:

IBM Case Manager Client Case History tab is slow sometimes

Problem

Cause

Environment

Solution

Subscribe