This section provides an overview of System Manager, and describes some
basic administrative tasks, such as starting up, shutting down, refreshing,
and setting system-wide flow control. For detailed information about
using System Manager for configuration and deployment tasks, refer to the
System Implementation Guide. This section covers the
following topics:
Steps for starting System Manager
Steps for shutting down System Manager
Steps for refreshing System Manager and updating components
Steps for configuring system-wide flow control
Perform the following step to start System Manager:
- Click Start > Programs > IBM WebSphere Business Integration
Express > Toolset Express > Administrative > System
Manager.
The System Manager perspective of the IBM WebSphere Studio Workbench
appears (see Figure 23).
Figure 23. System Manager

Perform the following step to shut down System Manager:
- In IBM WebSphere Studio Workbench, click File > Exit.
- Note:
- Be sure to shut down any InterChange Server Express instances before shutting
down System Manager. For instructions on shutting down InterChange
Server Express, see Shutting down InterChange Server Express.
Refreshing System Manager reloads objects from the local repository into
System Manager, but does not update InterChange Server Express. For
example, if you refresh System Manager after adding a newly created business
object definition, you can add the new business object to the connector's
supported business object list and bind the connector to a collaboration
port. But InterChange Server Express is not aware of the business
object unless you reboot the server, causing the business object's
specifications to be loaded from the repository into the server's
cache.
Perform the following steps to refresh System Manager:
- In System Manager, right-click the server instance.
- Click Refresh.
The following describes which components can be updated during system run
time:
- Business objects
- Not updated during run time. The repository is read only once when
InterChange Server Express starts up.
- Collaboration object properties
- Updated during run time. For example, collaboration object trace
levels take effect as soon as they are set.
- Collaboration object code changes
- Updated during system run time.
- Map code changes
- Updated during system run time. If mapping code is updated and
recompiled, connectors must be rebound to the altered maps.
Flow control is a configurable service that allows you to manage the flow
of connector and collaboration object queues. The parameters for
configuring flow control can be configured system-wide or on individual
components, or both. If you configure both, the individual component
configuration supersedes the system-wide configuration. For
instructions on configuring flow control for individual components, see Steps for configuring flow control for connectors or Steps for configuring flow control for collaboration objects.
- Note:
- Configuration changes for individual connectors or collaboration objects are
dynamic, meaning they do not require InterChange Server Express to be
rebooted. System-wide configuration changes for flow control require
InterChange Server Express to be rebooted.
To monitor how flow control is working in the system, you can view
the Flow Control monitor and view provided as part of System Monitor or you
can view the Statistics for collaboration objects or connectors from System
Manager in the InterChange Server Component Management view. For more
information on using the Flow Control monitor and view in System Monitor, see Steps for reviewing default monitors and Steps for using default views. For more information on viewing the
flow control from the InterChange Server Component Management view, see Steps for viewing collaboration object statistics or Steps for viewing connector statistics.
Perform the following steps to configure system-wide flow control:
- In the InterChange Server Component Management view, right-click the
InterChange Server Express instance for which you want to configure flow
control, and click Edit Configuration. The upper-right
quadrant of System Manager changes to an editing tool in which many system
properties can be changed.
- Click the Misc tab. A dialog box appears with a
Flow Control section (see Figure 24).
Figure 24. Edit configuration tool, Misc tab

- Under FlowControl, type information in the following
fields:
- Controller wakeup threshold: This property applies to
connector event queues. It has a decimal value ranging from 0 to 1, but
not including 0 or 1. Connector event queues are always of the blocking
type, meaning that if the queue is full, they do not allow new events to be
added. After a queue becomes full, the connector becomes
blocked. When the queue size equals or falls below the value of the
connector wakeup threshold multiplied by the maximum event capacity of that
connector (CONTROLLER_WAKEUP_THRESHOLD x
MaxEventCapacity), the connector becomes reactivated.
- Collaboration wakeup threshold: This property applies to
collaboration object event queues. It has a decimal value ranging from
0 to 1, but not including 0 or 1. This property applies only to
blocking-type collaboration objects, meaning that it does not allow the
connector to add more events to the collaboration queue. When the queue
size equals or falls below the value of the collaboration object wakeup
threshold multiplied by the maximum event capacity of that connector
(COLLABORATION_WAKEUP_THRESHOLD x MaxEventCapacity), the
connector is able to add more events to the collaboration queue for
processing.
- Collaboration def event capacity: This property sets the
maximum number of events you want queued for each collaboration object in the
system. The range of values for this property is from 1 to 2147483647,
inclusive.
- Conn def event capacity: This property sets the maximum
number of events you want queued for each connector in the system. The
range of values for this property is from 1 to 2147483647, inclusive.
- Saturated read size: Saturated readers attempt to process
saturated events. For example, if a collaboration object queue can
accept more events, the reader reads a particular number of events from the
database, and then adds them to the collaboration object queue. This
property reflects the maximum number of such events that can be read in one
iteration of the reader.
- Saturated min size: This property applies to saturated
readers, which are readers that process saturated events in the database, then
add those events to the appropriate collaboration object queue. This
property reflects the minimum number of threads doing these activities.
The default is 1.
- Saturated max size: This property applies to saturated
readers, which are readers that process saturated events in the database, then
add those events to the appropriate collaboration object queue. This
property reflects the maximum number of threads doing these activities.
The default is 3.
- Save the changes you made to the InterChange Server Express configuration
by clicking File > Save
<ServerName>.
- Restart InterChange Server Express.
