Using System Manager

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

Steps for starting System Manager

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).

Figure 21. System Manager

The figure shows the System Manager screen. The upper left part of the screen displays the data included in the system, for example, User Projects, Components, and Connectors. The lower left part of the screen displays any server information. The console information is displayed in the lower right part of the screen.

Steps for shutting down System Manager

Perform the followin steps to shut down System Manager:

In IBM WebSphere Studio Workbench, select File > Exit.

Note:
Be sure to shut down any InterChange Servers before shutting down System Manager. For instructions on shutting down InterChange Servers, see Steps for shutting down InterChange Server.

Steps for refreshing System Manager and updating components

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:

Business objects
Not updated during run time. The repository is read only once when InterChange Server 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.

Steps for configuring system-wide flow control

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 to be rebooted. System-wide configuration changes for flow control require InterChange Server 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 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:

  1. In the InterChange Server Component Management view of System Manager, right-click the InterChange Server instance for which you want to configure flow control, then select Edit Configuration. The upper-right quadrant of System Manager changes to an editing tool in which many system properties can be changed.
  2. Click the Misc tab. A dialog box appears with a Flow Control section (see Figure 22).

    Figure 22. Edit configuration tool, Misc tab

    The figure shows the Miscellaneous tab of the edit configuration tool tab. This screen is displayed in four sections, two in the upper half and two in the bottom half. The upper left section contains your persistent monitoring options, including determining the action on error, for example, Shutdown, and the persistent monitoring service. The upper right section contains workflow management information, specifically the business object consumer processor, which is an integer. The bottom left section contains the flow control information, where you set integer values for the controller wakeup threshold, the collaboration wakeup threshold, the collaboration and connector event capacities, the saturated read size, saturated minimum size and the saturated maximum size. The bottom right section contains the server memory options, including the memory checker sleep time, the memory upper and lower threshold percentages and the connector pause time threshold, in minutes.

  3. In the FlowControl section, enter information in the following fields:

    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.

  4. Select File > Save <ServerName> to save the changes you made to the InterChange Server configuration.
  5. Restart InterChange Server.

Copyright IBM Corp. 1997, 2004