InterChange Server database overview

The following sections describe general database characteristics and specific requirements for setting up IBM DB2, Microsoft SQL Server, or Oracle Server as your ICS-system database.

Note:
The Monitor tool does not support Flow Monitoring for MS SQL server databases. However, for the purposes of this guide, all references to the database assume that all four database categories (Event Management, Transactions, Repository, and Flow Monitoring) are supported.

Database tables overview

The InterChange Server database tables are grouped into four categories: Event Management, Transactions, Repository, and Flow Monitoring. The Event Management tables store business objects that are currently being processed. Transaction tables store the status of each transaction being processed, which may include the action and compensation of business objects, depending on the transaction level. Repository tables store information about the collaborations, business objects, connectors, maps, and relationships that you can configure in the ICS system. Flow Monitoring tables store event information for flows that are traced from IBM MQ Workflow (MQWF) through InterChange Server.

Database table configuration

By default, Installer configures all four table categories in one database. However, for performance considerations, you can configure four separate databases, one each for the Event Management, Transactions, Repository, and Flow Monitoring tables (see "Partitioning database use").

Note:
A Flow Monitoring table should only be configured only if you include MQWF in the business process and you are tracing events through InterChange Server. The database administrator should reserve at least 20 MB for this tablespace.

User connections

InterChange Server requires at least 15 user connections; this number is configurable. For more information, see "Setting up database connections".

Repository database requirements

The InterChange Server database (also referred to as the InterChange Server repository database) must meet the following requirements:

Relationship tables overview

Native mapping requires the use of relationship tables. By default, the relationship tables are contained in the InterChange Server database. You can optionally create one or more separate databases for the relationship tables. If you do so, consider the following:

Copyright IBM Corp. 1997, 2004