Filter
Top Products
v Review the wf.log file in the install_dir/logs file for time and date stamp
information showing increases in execution time, and errors in each business
process.
v Review the Performance Statistics Report by navigating to Operations > System
> Performance > Statistics. This report shows the number of invocations and
processing time for each business process and system activity.
v Review business processes that show increasing execution time for improper
design, mode, or XPath statements, for example, using a Command Line adapter
to retrieve data instead of a File System adapter. The Command Line adapter
uses more resources than the File System adapter, which can accomplish the
same goal in some situations. Or, in some situations, you can create an XPath
statement in an Assign service, which will replace the need for both the
Command Line adapter and the File System adapter.
Also, use relative paths in XPath statements. For example, write
PurchaseOrder/text instead of /ProcessData/PurchaseOrder/text(). In addition,
do not use // at the beginning of an XPath statement because this causes the
entire process data to be traversed.
Resolving Halted, Halting, Waiting, or Interrupted Business
Processes
A business process in a Halting, Halted, Interrupted_Man, or Interrupted_Auto
state requires immediate attention because the business process has stopped
processing. Business processes remain in a halted or interrupted state until some
action is taken on the business process. Business processes that fail receive a state
of Halted, which enables you to take manual corrective action without the business
process being archived or purged.
When you notice a halted or interrupted business process, you have two options:
v Terminate the business process.
v Restart the business process.
When you notice a business process in a waiting state, you have three options:
v Allow the business process to remain in the waiting state if it is waiting on one
of the following:
– Resources
– A service or activity that is disabled, but will be enabled
v Terminate the business process.
v Restart the business process.
The following sections show how to diagnose and resolve issues with halting,
halted, waiting, or interrupted business processes:
v Symptoms of Halting, Halted, Waiting, or Interrupted Business Processes
v Causes of Halting, Halted, Waiting, or Interrupted Business Processes
Symptoms of Halting, Halted, Waiting, or Interrupted Business
Processes
Symptoms of an increasing number of business processes in a halting, halted,
waiting, or interrupted state may include:
v Slow system performance
For more information on resolving a slow system, refer to the topic “Slow
System: Symptoms, Causes, and Resolution” on page 234.
232 Sterling B2B Integrator: Performance Management