Using System Manager

System Manager provides more flexibility when configuring InterChange Server, but the server must be running and System Manager must be connected to it.

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

  1. Start System Manager as described in Starting System Manager.
  2. Connect System Manager to the InterChange Server instance as described in Connecting to InterChange Server.
  3. Right-click the InterChange Server 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:

Figure 40 shows the "General" tab of the System Manager configuration file editor:

Figure 40. Configuring InterChange Server general properties

The figure shows the InterChange Server general properties screen. On the left-hand side of the screen are the Server name, Server version, Total memory and Free memory fields. On the right-hand side are the Startup time, Local Time Zone, Server Time Zone and and Server locale 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 uses to store repository, event management, and transaction management data. You can also configure the InterChange Server for database resilience on this tab. Do the following to configure the database properties:

  1. Click the Database tab.

    Figure 41shows the "Database" tab in the System Manager configuration file editor:

    Figure 41. Database tab of System Manager


  2. Select the appropriate value in the Database Driver drop-down menu--either IBM DB2 Server, MS SQL Server, or Oracle Server--depending on the database vendor.
  3. Type the maximum number of connections you want InterChange Server to make with the database server in the Maximum number of connections field, or enable the Unlimited check box to allow InterChange Server an unlimited number of connections.
  4. Type the maximum number of pools InterChange Server should establish to contain the database connections it caches in the Maximum number of 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 Maximum 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 Maximum 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. Type in the number of times you would like the InterChange Server to try to regain a connection to the database should you lose your connection in the Max connect retries field.
  9. Type in the amount of time (in seconds) you want InterChange Server to wait to reconnect to the database in the Connect retry interval field.
  10. 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), or Oracle(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 to make with the specific database server in the Maximum number of connections field, or enable the Unlimited check box to allow InterChange Server an unlimited number of connections.
    4. In the Max connect retries field, enter the amount of times you would like InterChange Server to try to regain a connection should it be lost.
    5. Type the user name that should be used by InterChange Server to log in to the specified database in the Login field.
    6. Type the password for the user name specified in step 6d in the Password field.
    7. If you chose MS 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.
    8. Type in the amount of time (in seconds) you would like InterChange Server to wait between attempts at regaining a lost connection in the Connect retry interval field.
  11. Repeat step 6 in the "Transactions" pane to configure the database connectivity for the transaction management service.
  12. Repeat step 6 in the "Repository" pane to configure the database connectivity for the repository service.
  13. Do the following in the "Flow Monitoring" pane to configure the database connectivity for the flow monitoring service:
    1. If you chose Oracle(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.
      Note:
      Microsoft SQL Server is not a supported database for WebSphere Business Integration Monitor. If SQL Server is the database you are using for the other databases used by WebSphere InterChange Server, then you cannot use Flow Monitoring.
    2. Type the name of the database in the Database field.
    3. Type the name of the schema used by WebSphere Business Integration Monitor in the Schema field.

      If you are using Oracle for the flow monitoring database then the name of the schema is identical to the name of the user account. If you are using IBM DB2 for the flow monitoring database, however, the schema name can be different from the name of the user account, so you must specify the correct schema name.

    4. Type the maximum number of connections you want InterChange Server to make with the specific database server in the Maximum number of connections field, or enable the Unlimited check box to allow InterChange Server an unlimited number of connections.
    5. In the Max connect retries field, enter the amount of times you would like InterChange Server to try to regain a connection should it be lost.
    6. Type the user name that should be used by InterChange Server to log in to the specified database in the Login field.
    7. Type the password for the user name specified in step 13f in the Password field.
    8. If you chose 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. Type in the amount of time (in seconds) you would like InterChange Server to wait between attempts at regaining a lost connection in the Connect retry interval field.

    For more information about Flow Monitoring, see the System Administration Guide.

Changing database passwords

Do the following to change the password for the user name that InterChange Server 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.

    Figure 42 shows the Tracing Levels tab in the System Manager configuration file editor:

    Figure 42. Configuring InterChange Server tracing levels

    The figure shows the "Tracing levels" tab. On the left-hand side of the screen is the Flow Tracing levels section with the Component pull-down menu and a list of components and their trace levels. On the left-hand side of the screen is the IBM WebSphere Business Integration System trace levels section with pull-down menus to choose values for Event Management, Messaging, Repository, Database Connectivity, Domain State, Data Handlers, User Database Connections, HTTPS Authentication, Transport Layer Security, WebSphere MQ and Flow Monitoring.

  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 subsystem, select the desired trace level from the drop-down menu associated with the subsystem.

    For information on what information is reported at each level for each subsystem, see the "Configuration Parameters" appendix of the System Installation Guide for Windows or System Installation Guide for UNIX.

Configuring logging and tracing properties using System Manager

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

  1. Click the Trace/Log Files tab.

    Figure 43 shows the Trace/Log Files tab in the System Manager configuration file editor:

    Figure 43. Configuring InterChange Server logging and tracing properties

    The figure shows the "Trace/Log Files" tab. On the left side of the screen is the Logging section which includes the To Console and To files check boxes. Then there is a field where you can type in the Log file name. Beneath that is the WebSphere MQ Tracing section where you can provide a file name in the field provided. On the right-hand side of the screen is the Tracing section with the To Console and To File check boxes. Then there is a field where you can provide a file name and beneath that a check box where you can choose Enable Stack Tracing.

  2. Do the following in the Logging pane to configure how InterChange Server 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 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 WebSphere Business Integration 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.

    Figure 44 shows the "E-mail" tab in the System Manager configuration file editor:

    Figure 44. Configuring InterChange Server e-mail notification properties

    The figure shows the "E-mail" tab where you can choose a value from the E-mail send type pull-down menu. Underneath that yo can fill in the following fields: Default e-mail recipient, WebSphere MQ errors recipient, Repository errors recipient, Database persistance errors recipient, Database access errors recipient, Transactions errors recipient, Collaboration errors recipient, Map errors recipient, Security errors recipient, Connector controller errors recipient, DTP errors recipient, Connector agent errors recipient, CORBA errors recipient, Activation errors recipient, Submission manager errors recipient and Deadlock errors recipient.

  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.

    Figure 45 shows the "Misc" tab in the System Manager configuration file editor:

    Figure 45. Configuring InterChange Server miscellaneous properties

    The figure shows the "Misc" tab. On the left are the Persistent Monitoring, Flow Control, and Flow Monitoring sections. In the Persistent Monitoring section you can choose values from the Action on error and Persistent monitoring services pull-down menus. Beneath that is the Flow Control section where you provide values in the Controller wakeup threshold, Collaboration wakeup threshold, Collaboration def event capacity, Conn def event capacity, Saturated read size, Saturated min size and Saturatedmax size fields. Beneath that is the Flow Monitoring section where you can provide a value in the Max flow queue depth and choose the Max value check box. On the right-hand side of the screen are the WorkFlow Management and Server Memory sections. In the WorkFlow Management section you can provide a value in the Business object consumer processor field. Beneath that is the Server Memeory section where you can provide values for the Memory checker sleep time (minutes), Memory upper threshold percent, Memory lower threshold percent and Connector pause time at threshold(minutes) fields.

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

    Figure 46 shows the "Environment Properties" tab in the System Manager configuration file editor:

    Figure 46. Configuring InterChange Server environment variables

    The figure shows the Evironment Properties" tab with the Add Environment Property section and the Environment Properties section. In the Add Environment Property section are the Property name and Property value fields with the Add Property push button. In the Environment Properties section is the Delete Property push button and a list of properties and their values.

  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 and the WebSphere MQ persistent messaging software:

  1. Click the WebSphere MQ tab.

    Figure 47 shows the "WebSphere MQ" tab in the System Manager configuration file editor:

    Figure 47. Configuring InterChange Server WebSphere MQ properties

    The figure shows the "WebSphere MQ" tab. There are four fields that need to be filled in: Host name, Port number, Queue Manager name and Channel.

  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 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. 1997, 2004