Examine the Server Logs

TIBCO BPM components write out logging information as they process work. It can be useful to look at these logs when debugging scripts that are not working. In order to do this, ensure that the debugging level is turned up to maximum (see the Administrator interface documentation for your BPM runtime for more information about editing logging levels).

Log files are located in:

CONFIG_HOME/tibcohost/INSTANCE_NAME/nodes/BPMNode/logs/BPM.log

On Windows, the default location for CONFIG_HOME is:

C:\ProgramData\amx-bpm\tibco\data

On UNIX, the default location for CONFIG_HOME is:

/opt/amxbpm/tibco/data

The default INSTANCE_NAME is Admin-AMX BPM-AMX BPM Server.

Checking the log file can help locate the cause of scripting problems. For example: 

23 Mar 2011 17:53:50,417 [Default Service Virtualization Thread_72] [ERROR] com.tibco.n2.brm.services.impl.AsyncWorkItemSchedulerServiceImpl - [ERROR] - {BRM_WORKITEM_ASYNC_SCHEDULE_WORK_ITEM_WITH_MODEL_MESSAGE_FAILED} - Async schedule work item with model message failed ¬{extendedMessage=`Param [integer] Value [111222333444] exceeds the defined maximum limit of 9`, componentClassName=`com.tibco.n2.brm.services.impl.AsyncWorkItemSchedulerServiceImpl`, requestReceived=`Wed Mar 23 17:53:50 GMT 2011`, hostAddress=`10.100.83.80`, nodeName=`BPMNode`, eventType=`FAULT`, messageCategory=`WORK_ITEM`, componentId=`BRM`, stackTrace=`com.tibco.n2.brm.services.WorkItemFault: Param [integer] Value [111222333444] exceeds the defined maximum limit of 9
	at com.tibco.n2.brm.model.util.DataModelFactory.checkDataTypeValue(DataModelFactory.java:2280)
	at com.tibco.n2.brm.model.util.DataModelFactory.checkDataTypeValues(DataModelFactory.java:2185)
	at com.tibco.n2.brm.model.util.DataModelFactory.checkItemBodyDataTypesFromPayload(DataModelFactory.java:1707)
	at com.tibco.n2.brm.services.impl.WorkItemSchedulerBase.privScheduleWorkItem(WorkItemSchedulerBase.java:621)
	at com.tibco.n2.brm.services.impl.WorkItemSchedulerBase.scheduleWorkItemWithWorkModel(WorkItemSchedulerBase.java:1323)
	at com.tibco.n2.brm.services.impl.AsyncWorkItemSchedulerServiceImpl.scheduleWorkItemWithModel(AsyncWorkItemSchedulerServiceImpl.java:263)
	at sun.reflect.GeneratedMethodAccessor635.invoke(Unknown Source)
…
	at java.lang.Thread.run(Thread.java:619)
`, serviceName=`AsyncWorkItemSchedulerService`, principalId=`tibco-admin`, priority=`HIGH`, managedObjectId=`78`, hostName=`uk-keitht`, creationTime=`2011-03-23T17:53:50.417+0000`, methodName=`scheduleWorkItemWithModel`, methodId=`asyncScheduleWorkItemWithModel`, principalName=`tibco-admin`, correlationId=`6fb66791-595c-499b-ad55-5b56b7404fac`, threadId=`1056`, compositeApplicationName=`amx.bpm.app`, severity=`ERROR`, message=`Async schedule work item with model message failed`, contextId=`6fb66791-595c-499b-ad55-5b56b7404fac`, threadName=`Default Service Virtualization Thread_72`, environmentName=`BPMEnvironment`, lineNumber=`290`, messageId=`BRM_WORKITEM_ASYNC_SCHEDULE_WORK_ITEM_WITH_MODEL_MESSAGE_FAILED`, ¬}