Do you know now you can run Process Designer and Process Tracker from IBM Content Navigator (ICN)?

Body

IBM Case Foundation V5.2.1 has some new features for administrators. One of them is running Process Designer and Process Tracker from ICN. In previous versions, you should use WorkplaceXT or Workplace to access Process Designer and Process Tracker.

You can now register the Process Applets as a plugin from ICN using the CPEAppletsPlugin.jar. For detailed instructions refer to documentation link @http://www-01.ibm.com/support/knowledgecenter/SSNW2F_5.2.1/com.ibm.p8.c…

The following is the sample screenshot from ICN after registering the Process Applets.

After registering the Process Applets, make sure to enable the parameter "Display workflow definition class" on the ICN repository where the workflow definitions should be added. For instructions to enable this parameter refer to TechNote @http://www-01.ibm.com/support/docview.wss?uid=swg21697123.

If you have not enabled the "Display workflow definition class" parameter then you may run into the errors similar to the following in ICN and CPE application server logs.

BusinessExcep E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "invokeRPC" on bean "BeanId(FileNetEngine#peengine-ejb.jar#FNP8PESNDCMD, null)". Exception data: [FNRPE2131090139E]Work Class "Workflow Definition1" was not found.

Please note that opening Process Designer from ICN will end up adding an exception into the ICN application server log. This error is innocuous and can be ignored. The exception will look something like the following:

SystemOut O CIWEB.CPEAppletsPlugin Error: [P8Admin @ 192.168.0.100] com.ibm.ecm.cpea.CPEApplets.CPEAppletListenerPluginService.execute()

java.lang.Exception: Please verify that your client jar files match the server versions.

at com.ibm.ecm.cpea.CPEApplets.CPEAppletListenerPluginService.execute(CPEAppletListenerPluginService.java:82)

at com.ibm.ecm.util.PluginUtil.invokeService(PluginUtil.java:1095)

at com.ibm.ecm.struts.actions.PluginAction.executeBaseAction(PluginAction.java:144)

at com.ibm.ecm.struts.actions.BaseAction.execute(BaseAction.java:211)

at com.ibm.ecm.jaxrs.Actions.loadAndExecuteAction(Actions.java:254)

at com.ibm.ecm.jaxrs.Actions.handleAction(Actions.java:93)

at com.ibm.ecm.jaxrs.Actions.handleGetActions(Actions.java:108)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)

at java.lang.reflect.Method.invoke(Method.java:611)

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:75)

............................................................................

There is an APAR (APAR PJ43003) opened for this issue. The fix for this is currently targeted for CPE 5.2.1.2-P8CPE-FP002.

If you need additional help in implementing the procedure above, please open a Problem Management Record (PMR) with Enterprise Content Management Business Process Manager support for further assistance.