IBM Version 52 Computer Accessories User Manual


 
which may in turn affect other processes. It is recommended that you interrupt the
business processes from the Business Process Monitor.
To stop a thread, click Stop icon adjacent to the thread that is to be stopped. This
instructs the thread to immediately stop processing without waiting for any steps
to complete or exit with an error. In most cases, the thread will stop immediately.
However, this will not immediately change the display in the Thread Monitor. The
thread will eventually be marked as interrupted.
Note: In some cases, it is not possible to stop a thread, and your attempt will be
unsuccessful. Stopping a thread does not stop the service that is performing that
thread. The service is still available for Sterling B2B Integrator to use in other
business processes.
Setting the Refresh Option for the Thread Monitor
By default, the Thread Monitor is set to automatically refresh every 15 seconds. To
turn this option off, clear the Automatically refresh every 15 seconds check box.
Monitoring Messages
In Sterling B2B Integrator, business processes use messages to communicate with
each other. Certain business processes create Produce and Consume messages.
While the Produce business processes produce messages that are to be consumed,
the Consume business processes wait for messages from the Produce business
processes.
Sometimes the handoff from the Produce business processes to the Consume
business processes does not occur. Either the produced message has no waiting
Consume process, or the waiting Consume process waits without success for the
Produce message. Use the Message Monitor to track unsuccessful message
handoffs within Sterling B2B Integrator.
It is recommended that you keep the following considerations in mind when
monitoring messages within Sterling B2B Integrator:
v The Message Monitor pages of the Sterling B2B Integrator interface display only
those messages associated with a failed Produce or Consume activity. Messages
that are successfully produced or consumed are not monitored.
v Messages are tied closely to business processes. You can search for messages by
business process name, type of business process (Produce or Consume), and date
and time on which the associated business process step invokes the Produce or
Consume activity. However, messages also have identities that are separate from
business processes. Messages have names, and their names can be used as
search input.
v Sometimes Produce and Consume business processes have to choose between
messages having the same name. Let us for example consider that two Produce
processes run at different times; both produce a message named OutMsg1. Thus,
there are two messages named OutMsg1 in Sterling B2B Integrator, but with
different start date/times. When a Consume process detects the two messages, it
consumes the OutMsg1 with the later start date/time. The situation also works
in reverse. Two Consume processes request an identically named message
(InMsg1). When a Produce process produces InMsg1, it produces InMsg1 for the
Consume process with the earlier start date/time.
96 Sterling B2B Integrator: Performance Management