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 InterChange Server > IBM WebSphere Business Integration Toolset > Administrative > System Manager.
The System Manager perspective of the IBM WebSphere Studio Workbench appears (see Figure 21).
Perform the followin steps to shut down System Manager:
In IBM WebSphere Studio Workbench, select File > Exit.
Refreshing System Manager reloads objects from the local repository into System Manager, but does not update InterChange Server. 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 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 step to refresh InterChange Server:
Right-click the server under Server Instances, then select Refresh.
The following describes which components can be updated during system run time:
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.
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 the InterChange Server Component Management view of System Manager. 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 of System Manager, see Collaboration object statistics or Connector statistics.
Perform the following steps to configure system-wide flow control:
ControllerWakeupThreshold: 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.
CollaborationWakeupThreshold: 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.
CollaborationDefEventCapacity: 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.
ConnDefEventCapacity: 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.
SaturatedReadSize: 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.
SaturatedMinSize: 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.
SaturatedMaxSize: 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.