![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Depending upon whether you are using a process engine in testing mode or a deployed process engine, the logs are stored in different locations. During test mode, the logs are stored in the TIBCO ActiveMatrix BusinessWorks working directory under the logs subdirectory. See TIBCO Designer User’s Guide for more information about specifying the working directory. For deployed process engines, the log location is specified by custom engine properties. See TIBCO ActiveMatrix BusinessWorks Administration for more information about custom engine properties.
Roles can be used to filter the log entries when displaying them. For example, if you set the role as Debug, you can choose to view or not view all log entries that have the role set to Debug.You can enable or disable system or user-defined roles using custom engine properties at deployment time. See TIBCO ActiveMatrix BusinessWorks Administration for more information. If unchecked, each log message has the Job number, process definition name, and activity name prepended to the message text.The Join Condition tab allows you to define an expression based on the values of the incoming transitions to the activity. If the expression evaluates to true, the activity is executed, if the expression evaluates to false, either the activity is bypassed or a fault is thrown. See Transitions and Join Conditions for more information about join conditions.
Specifies what action to perform if the join expression evaluates to false. The following options are available:
• Inherit setting — use the default action specified within the current scope. The current scope is either the current group containing the activity or the orchestration process if the activity is not within a group.
• Bypass activity if false — skip the processing of the activity, set the outgoing transition conditions to false without evaluating them, and resume processing.
• Throw fault if false — throw a joinFailure fault and switch control to an error-handling routine configured to catch all unhandled exceptions. If the exception is not caught, the fault is propagated to the calling environment. The expression to evaluate to determine if the activity should be executed. The only data available to this expression is the value of any transitions into the activity. You can use the XPath Formula Builder to create the join expression.See TIBCO ActiveMatrix BusinessWorks Process Design Guide for more information about mapping and transforming input data.
Logs are stored in the TIBCO ActiveMatrix BusinessWorks installation directory under the logs subdirectory.Note: When the message contains non-ASCII data, the default encoding of the Java Virtual Machine used by the TIBCO ActiveMatrix BusinessWorks process engine is used to encode the text when writing to the log file. The error code of the message. This is used as an identifier for the message so that applications can scan the log for the message.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |