April 11, 2012 9:37:40 AM PDT
Goal: Enable Model Side Logging to Help Troubleshoot Client Application Connection Issue to BPM Server
Fact: Interstage BPM (Business Process Manager) Version 11.0
Fact: Interstage BPM (Business Process Manager) Version 11.1
Fact: Interstage BPM (Business Process Manager) Version 11.2
Fact: Interstage BPM (Business Process Manager) Version 11.2a
Fact: iFlow.jar
Fact: Interstage BPM Model Layer
Fix:
Interstage BPM model library is encapsulated into iFlow.jar. While developing client applications using the model library, it may be helpful to enable the model logging to a log file. Specifically, the model side logging is made available by the package com.fujitsu.iflow.model.util.Log.
Make the following calls before calling any model API. When you troubleshoot any client side errors, you can check the model log to see what may have happened:
Log.setOutputFile("c:/clientapp/log/workflow.log", false); /*path and log file needs to pre-exist. */
Log.setOutputLevel(3); // max trace level
Look up the model java doc for the methods in com.fujitsu.iflow.model.util.Log.
Note: Although com.fujitsu.iflow.model.util.Log has been deprecated, it is still helpful to enable model side logging to help troubleshoot model side errors, especially connection issue to BPM server. Comment out these two lines of code after rectifying the issue.
Author: C.Y. Chen
Attachment: