September 2018

Case Monitor Dashboard, IBM Case Manager (ICM)

No Data is Available for This Chart in IBM Case Monitor Dashboard 5.3.3.0

September 27, 2018

One can use the IBM Case Monitor Dashboard to view of business activities data that is specific to case management systems. This dashboard, which is an IBM Content Navigator desktop provides a dashboard that displays widgets that show case and task activity across solutions. You can use this data to review volume, find and eliminate bottlenecks, and ensure that operations are working efficiently and effectively.

The IBM Case Monitor Dashboard retrieves data for the solutions that are deployed to a target object store from the Case Analyzer store that you configure for that object store. In the dashboard, users can switch between Case Analyzer stores to obtain information about solutions in different target object stores.

Note: By default, any user who has access to the target object store has access to the IBM Case Monitor Dashboard.

To configure IBM Case Monitor Dashboard, you need to perform following tasks accordingly:

Prepare the database for the Case Analyzer store. You enter the database schema name when you configure and enable the Case Analyzer store by using the IBM Case Manager administration client.
Create the Case Analyzer store:

Log in to the IBM Case Manager administration client.
Under the domain, expand Object Stores and click the target object store in which you want to create the Case Analyzer store.
Click New Case Analyzer Store and enter the information for the new store.

3. Log in to the IBM Case Manager configuration tool and run the Register the Case Monitor Widgets Package task to add the IBM Case Monitor Dashboard desktop to IBM Content Navigator.

Once performed all of these steps while ICM installing or upgrading, try to add and process few test cases using ICM Client desktop and check after sometime either data is fetching or not. First of all data will be fetched successfully into Case Monitor Dashboard charts but in case of “no data is available for this chart“, you need to perform step 2 again.

Delete Case Analyzer Store using icmadmin desktop for target object store.
Recreate Case Analyzer Store by providing relevant data source and schema information.

After that, check the data using http://servername:9081/navigator?desktop=icmmonitor desktop. Data will be available for all of the relevant charts according to cases working in ICM Client as shown below:

Further details, please go to following IBM recommended Knowledge Center & tech note:

https://www.ibm.com/support/knowledgecenter/en/SSCTJ4_5.3.0/com.ibm.casemgmt.installing.doc/acmcp084.htm

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

IBM Case Manager (ICM), IBM Case Manager Builder, ICM Business Rules

After upgrading to IBM Case Manager 5.3.3-IF001 Deployment of Rules Fails During Solution Deployment

September 27, 2018

After upgrading or applying IBM Case Manager V5.3.3-IF001 (5.3.3.0.1), rule(s) deployment fails when you deploy your case management solution. When you deploy your case management solution that contains rules, the deployment will fail, and you might see an error similar to the following logged:

[9/26/18 12:37:14:086 GMT] 000001c5 api E com.ibm.casemgmt.api error FNRPA0624E The rules could not be deployed because of the following error: An exception occurred in the event handler.
Message was: FNRPE0029E: [RULE_DEPLOYMENT_RULE_DEFINITION]: For case type SOL_Type1, exception occurred while converting following rule definition(s): TableRule1
com.ibm.casemgmt.intgimpl.deploy.handlers.ContinuableStepException: FNRPA0624E The rules could not be deployed because of the following error: An exception occurred in the event handler.
Message was: FNRPE0029E: [RULE_DEPLOYMENT_RULE_DEFINITION]: For case type SOL_Type1, exception occurred while converting following rule definition(s): TableRule1
at com.ibm.casemgmt.intgimpl.deploy.handlers.ContinuableStepException.createContinuableStepException

(ContinuableStepException….

Environment:

ICM 5.3.3.1
CPE 5.2.1.7
WAS 8.5.5.x

Cause:

IBM Case Manager 5.3.3 Interim Fix 001 updated the embedded IBM Operational Decision Manager SDK to 8.8.1.3-IF083. The updated version introduces classloader issues which now require the ODMMessages.jar file to be placed into the application server classpath on IBM FileNet Content Platform Engine server where the Rules_Operation component runs.

Solution:

Complete the following steps to copy the required file on your system before you reattempt solution deployment:

Copy the ODMMessages.jar file from the Case Manager installed home directory (/opt/IBM/CaseManagment/configure/AddOns/ODMMessages.jar) to the following directory where Content Platform Engine is deployed:
- WebSphere – <application server-home>/lib/ext. Where <application server-home> is where WebSphere is installed, e.g. /opt/IBM/WebSphere/AppServer/lib/ext.
- Weblogic – <java-home>/lib/ext. Where <java-home> is the JRE folder for the JDK that Weblogic is using, e.g. /opt/app/oracle/product/JAVA/jdk/jre/lib/ext.
Restart the WAS where IBM FileNet Content Platform Engine (CPE) is deployed.
Redeploy solution again from IBM Case Manager Builder. It will be succeed.

For further details, please visit: https://www-01.ibm.com/support/docview.wss?uid=ibm10719975

IBM FileNet Workplace XT

The solution cannot be Retrieved When Trying to Edit Solution from Process Designer in WorkplaceXT

September 25, 2018

The solution cannot be retrieved, possibly because it is not a version 5.2 solution error is generated in IBM FileNet WorkplaceXT when trying to open Process Designer. or trying to edit solution’s case type.

Cause:

The error occurs after Case Manager is upgraded from a previous version.
Case Manager Builder is configured to invoke Process Designer from Workplace XT.
The Workplace XT configuration has not been updated with the new version of the ICMSolutionEdit.jar file.

Environment:

ICM 5.2.x / 5.3.x

WorkplaceXT 1.1.5.2

Solution:

For the Workplace XT instance in a development pr production environment, additional configuration is required. These changes apply to the instance of Workplace XT that is used by Case Manager Builder.

To configure Workplace XT properly for editing solution in Process Designer for a development pr production environment, perform the following steps one by one:

On the IBM Case Manager server, navigate to the CaseManagement/WorkplaceXTConfig directory.
Copy the following files:

ICMSolutionEdit.jar
jaxb-api.jar
jaxb-impl.jar
weblogic.xml (only for WebLogic Server environments)
weblogic-application.xml (only for WebLogic Server environments)

3. On the Workplace XT server, navigate to WebClient/WorkplaceXT/WEB-INF/lib directory.

4. Paste the following files in the directory:

ICMSolutionEdit.jar
jaxb-api.jar
jaxb-impl.jar

5. For WebLogic Server systems, navigate to the WebClient/WorkplaceXT/WEB-INF directory and paste the copy of the weblogic.xml file into the directory.

6. For WebLogic Server systems, navigate to the WebClient/deploy/META-INF directory and paste the copy of the weblogic-application.xml file into the directory.

7. You must manually redeploy Workplace XT on the web application server.

8. Restart web application server and again try to open solution from IBM FileNet WorkplaceXT Process Designer, IT will, work properly and you will never be prompted again of “The solution cannot be retrieved, possibly because it is not a version 5.2 solution error is generated in Case Manager Builder when trying to open Process Designer”. Here is the screenshot once it will be successful.

For further details please visit the following IBM recommended knowledge center or tech notes:

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

https://www.ibm.com/support/knowledgecenter/SSCTJ4_5.2.1/com.ibm.casemgmt.installing.doc/acmin141.htm

No Data is Available for This Chart in IBM Case Monitor Dashboard 5.3.3.0

After upgrading to IBM Case Manager 5.3.3-IF001 Deployment of Rules Fails During Solution Deployment

Environment:

Cause:

Solution:

The solution cannot be Retrieved When Trying to Edit Solution from Process Designer in WorkplaceXT

Cause:

Environment:

Solution:

Subscribe