IBM Version 52 Computer Accessories User Manual


 
v true – Enables the ability to steal threads.
v false – Disables the ability to steal threads.
Queues that are configured to steal threads from other queues (StealThreads
property set to true) steal only from queues that have the AllowStealing
property set to true. This value can be different for each queue.
.# indicates the queue number.
AllowStealing.#
Enables or disables the ability of other queues to steal threads from this queue.
Valid values:
v true – Allows other queues to steal threads.
v false – Does not allow other queues to steal threads.
Queues that are configured to steal threads from other queues (StealThreads
property set to true) only steal from queues that have the AllowStealing
property set to true. This value can be different for each queue.
.# indicates the queue number.
persistence_level
Persistence (storage to the database) level for Sterling B2B Integrator. Set the
persistence_level value to PERSISTENCE_NONE during day-to-day processing.
Valid values are:
v PERSISTENCE_DEFAULT
v PERSISTENCE_FULL – From user interface tracking, every step will be
persisted in full, which includes all the documents, status report (if any),
and instance data.
v PERSISTENCE_MINIMAL/PERSISTENCE_STEP_STATUS – From user
interface tracking, every step will be persisted, but the document, status
report (if any), and instance data will not be persisted in some of the steps
(for example, assign and sleepservice). Most of the services that create
documents will be persisted in full.
v PERSISTENCE_NONE/PERSISTENCE_BP_START_STOP – From user
interface tracking, the first step and last step will be persisted in full. Some
of the services will not be persisted (for example, assign and sleepservice).
Services that are defined as full will be persisted in full. Documents created
through a stream and stored in the file system will be persisted.
Note: If you have configured a business process with INVOKE_MODE set
to SYNC, which in turn invokes business processes with INVOKE_MODE
set to INLINE and the persistence_level set to BP Start Stop Engine May
Override, the business processes may fail. To counter the business process
failure, follow one of these workarounds:
Change the INVOKE_MODE of the second business process from INLINE
to SYNC.
Add a dummy <assign> statement after the </operation> statement as
shown:
<process name = "Call_BP_withError.kj">
<sequence name="Sequence Start">
<operation name="Invoke Sub-Process">
<participant name="InvokeSubProcessService"/>
<output
message="InvokeSubProcessServiceTypeInputMessage">
<assign to="INVOKE_MODE">INLINE</assign>
170 Sterling B2B Integrator: Performance Management