Using System Manager to configure InterChange Server Express

To use System Manager for configuration of InterChange Server Express, an instance of InterChange Server Express must be running and System Manager must be connected to it.

Do the following to open the InterChange Server Express configuration editor in System Manager:

  1. Start System Manager as described in Starting System Manager.
  2. Connect System Manager to the InterChange Server Express instance as described in Connecting to InterChange Server Express.
  3. Right-click the InterChange Server Express instance and choose Edit Configuration from the context menu.
  4. Make the desired changes in the configuration tabs as described in the following sections:
  5. When you are done use the keyboard shortcut Ctrl+S to save the file.

Viewing general properties using System Manager

The "General" tab of the System Manager configuration file editor has the following read-only fields:

Configuring database properties using System Manager

The "Database" tab of the configuration file editor allows you to change properties that specify the databases InterChange Server Express uses to store repository, event management, and transaction management data. Do the following to configure the database properties:

  1. Click the Database tab.
  2. Select the appropriate value in the Database Driver drop-down menu--either IBM DB2 Serveror MQ SQL Server--depending on the database vendor.
  3. Type the maximum number of connections you want InterChange Server Express to make with the database server in the Max Connections field, or enable the Unlimited checkbox to allow InterChange Server Express an unlimited number of connections.
  4. Type the maximum number of pools InterChange Server Express should establish to contain the database connections it caches in the Max pools field.
  5. Type the number of minutes you want a connection object to remain idle before being returned to the database connection pool for reuse in the Idle Timeout field.
  6. Type the number of times that the server should attempt to execute a deadlocked database transaction in the Max deadlock retry field.

    This field is related to the Deadlock retry interval field documented in step 7.

    For more information on the behavior of the server in the case of a database deadlock, see the System Administration Guide.

  7. Type the number of seconds that the server should wait in between attempts to execute a deadlocked database transaction in the Deadlock retry interval field.

    This field is related to the Max deadlock retry field documented in step 6.

    For more information on the behavior of the server in the case of a database deadlock, see the System Administration Guide.

  8. Do the following in the "Event Management" pane to configure the database connectivity for the event management service:
    1. If you chose MQ SQL Server(Type 4)in the Database Driver drop-down menu, then type the name of the computer on which the database server resides in the Host name field.
    2. Type the name of the database in the Database field.
    3. Type the maximum number of connections you want InterChange Server Express to make with the specific database server in the Max Connections field, or enable the Unlimited checkbox to allow InterChange Server Express an unlimited number of connections.
    4. Type the user name that should be used by InterChange Server Express to log in to the specified database in the Login field.
    5. Type the password for the user name in the password field.
    6. If you chose MQ SQL Server(Type 4), or Oracle(Type 4) in the Database Driver drop-down menu, then you must type the port number through which clients communicate with the database server in the Port Number field.
  9. Repeat step 8 in the "Transactions" pane to configure the database connectivity for the transaction management service.
  10. Repeat step 8 in the "Repository" pane to configure the database connectivity for the repository service.

Changing database passwords

Do the following to change the password for the user name that InterChange Server Express uses to access one of the databases:

  1. Click Change next to the Password field in the "Event Management", "Transactions", or "Repository" panes.
  2. Type the new password in the New Password field.
  3. Type the new password again in the Confirm Password field.
  4. Click OK.

Configuring tracing levels using System Manager

Do the following to set properties for flow tracing and subsystem tracing at the "Tracing Levels" tab:

  1. Click the Tracing Levels tab.
  2. To set the flow trace level for a business object, select the desired value in the Level column for the particular business object in the "Flow Tracing Levels" pane.

    For more information on flow tracing, see the System Administration Guide.

  3. To set the trace level for an InterChange Server Express subsystem, select the desired trace level from the drop-down menu associated with the subsystem.

Configuring logging and tracing properties using System Manager

Do the following to configure the locations to which InterChange Server Express logs and traces runtime information:

  1. Click the Trace/Log Files tab.
  2. Do the following in the Logging pane to configure how InterChange Server Express logs runtime information:
  3. Repeat step 2 for the "Tracing" pane.
  4. To enable tracing for WebSphere MQ, type the name and path of the file to which output should be logged in the unlabeled text field in the "WebSphere MQ Tracing" pane, or click the browse button to select a file.
  5. To use stack tracing, select Enable Stack Tracing and then select the desired severity level from the Tracing Severity Level drop-down menu.

    For more information about stack tracing, see System Administration Guide.

Configuring e-mail notification properties using System Manager

InterChange Server Express can send e-mail notifications when errors occur in the business integration system. By default the server uses the Java e-mail APIs, and can send e-mail notifications for a number of different subsystems. To enable the server to send e-mail notifications for errors experienced by individual collaborations, you must configure the system to use the Adapter for e-Mail. For detailed information on configuring the system for e-mail notification, see the System Administration Guide. To make the necessary modifications to the configuration file (which is just one step in the total number of tasks described in the System Administration Guide), do the following:

  1. Click the E-mail tab.
  2. Select Java mail or Connector mail from the E-mail send type drop-down menu depending on which e-mail notification mechanism you want to use.
    Note:
    Keep in mind that collaborations will only be able to send e-mail notifications if you choose Connector mail.
  3. If you chose Java mail in step 2, type the name of the computer on which the SMTP server is installed in the SMTP mail host field.
  4. Type a valid e-mail address or comma-separated series of e-mail addresses in the text fields for each subsystem as desired.

Configuring miscellaneous properties using System Manager

The "Misc" tab in the System Manager configuration file editor has panes for configuring features such as persistent monitoring, flow control, and long-lived business processes. Do the following to configure settings for these features:

  1. Click the Misc tab.
  2. Do the following in the "Persistent Monitoring" pane:
    1. Select Continue in the Action on error drop-down menu if you want InterChange Server Express to continue running in the event of errors experienced by the persistent monitoring subsystem.

      Select Shutdown in the Action on error drop-down menu if you want InterChange Server Express to shut down in response to errors with the subsystem.

    2. Select the desired tracing level in the Persistent monitoring service drop-down menu to specify the tracing level for the subsystem.
  3. For information on the interface elements in the "Flow Control" pane, see the System Administration Guide.
  4. For information on the interface elements in the "Flow Monitoring" pane, see the System Administration Guide.
  5. In the "Workflow Management" pane, type a number in the Business object consumer processor to indicate how many threads you want spawned to manage business objects participating in a long-lived business process.

    These threads deliver business objects from the collaboration runtime to the appropriate connector controllers when the business objects are retrieved from persistent storage to resume processing in a long-lived business process. For more information on long-lived business processes, see the Collaboration Development Guide.

  6. For information on the "Server Memory" pane, see Using the memory checker thread.

Configuring environment variables using System Manager

At the "Environment Properties" tab, you can specify any Java user environment properties that might be required in the business integration system. Some environments may require such a variable to be specified; instead of adding them to the script that starts InterChange Server Express, you can add them to the configuration file by using the "Environment Properties" tab. Do the following to add a new environment property:

  1. Click the Environment Properties tab.
  2. Type the name for the property in the Property name field.
  3. Type the value for the property in the Property value field.
  4. Click Add Property.

To delete a property, select the property and click Delete Property.

To edit a property's value, select the property and edit the text in the Property value column for the property.

Configuring WebSphere MQ properties using System Manager

Do the following to configure the connectivity between InterChange Server Express and the WebSphere MQ persistent messaging software:

  1. Click the WebSphere MQ tab.
  2. Type the name of the computer on which the WebSphere MQ server is installed in the Host name field.
  3. Type in the Port number field the port over which WebSphere MQ allows clients to communicate with the server.

    The default port is 1414.

  4. Type in the Queue manager name field the name of the queue manager that has been created to contain the queues on which InterChange Server Express will persistently store messages for the flows it processes.
  5. Type in the Channel field the name of the channel over which clients of WebSphere MQ communicate with the WebSphere MQ server. The default value is CHANNEL1. Consult with the WebSphere MQ administrator at the site to determine if CHANNEL1 can be used and if not, which channel can be used.

Copyright IBM Corp. 2004