System Manager tasks

This section describes system administration tasks of System Manager, such as starting up, shutting down, and refreshing. For detailed information about using System Manager while implementing the Business Integration Express for Item Sync system, refer to the System Implementation Guide. This section covers the following topics:

Starting System Manager

Shutting down System Manager

Refreshing System Manager and updating components

Configuring system-wide flow control

Starting System Manager

To start System Manager, click Start > Programs > IBM WebSphere Business Integration Express for Item Sync V4.3 > Toolset Express> Administrative > System Manager. The System Manager perspective appears.

Shutting down System Manager

To shut down System Manager, select Exit from the File drop-down menu of IBM WebSphere Studio Workbench.

Note:
Be sure to shut down InterChange Server Express before shutting down System Manager. For instructions on shutting down InterChange Server Express, see Shutting down InterChange Server Express.

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

To refresh InterChange Server, right-click the server under Server Instances, then select Refresh.

The following describes which components can be updated during system runtime:

Business objects
Not updated during runtime. The repository is read only once when InterChange Server Express starts up.

Collaboration properties
Updated during runtime. For example, collaboration trace levels take effect as soon as they are set.

Collaboration code changes
Updated during system runtime.

Map code changes
Updated during system runtime. If mapping code is updated and recompiled, connectors must be rebound to the altered maps.

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 Configuring flow control for connectors or 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 use the default Flow Control monitor provided as part of the Web-based System Monitor, or you can create new Flow Control monitors for individual connectors or collaboration objects. For more information about monitoring flow control, see the description of the default Flow Control monitor inUsing default monitors, and the instructions on creating new monitors inCreating new monitors using the Monitor Definition Wizard. After you have all the flow control monitors created, refer to the following sections to begin monitoring flow control: Using the Web-based System Monitor and Logging on to the Web-based System Monitor."Operating collaboration objects"

To configure system-wide flow control, do the following:

  1. In System Manager, right-click the server under Server Instances for which you want to configure flow control, then select Edit Configuration. The upper-right section of the window 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 9).

    Figure 9. Edit configuration tool, Misc tab


  3. In the Flow Control section, enter 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.

  4. Save the changes you made to the InterChange Server Express configuration by selecting Save <ServerName> from the File menu of System Manager.
  5. Restart InterChange Server.

Copyright IBM Corp. 1997, 2003