DB2 database configuration (iSeries)

In an iSeries environment, Sterling B2B Integrator uses the DB2® database that is included in the IBM i operating system. The installation process creates a new collection for Sterling B2B Integrator.

Before you install the Sterling B2B Integrator software, you must determine and record the collection name and the catalog name:
  • The collection name is the name of the collection (or library) that contains the database, journal, and journal receiver for your Sterling B2B Integrator system. This collection must not yet exist. Example: SIxxdb, where xx represents the version you are installing.
  • The catalog name is the database name of your iSeries system, as defined by the WRKRDBDIRE command. Generally, this value is the name of your system.

All database files are required to be journaled when those files are being used by the translator in Sterling B2B Integrator. If your application files are not currently journaled, and you plan to access these files through Sterling B2B Integrator, refer to the IBM® manuals for instructions on journaling physical files.

Sizing

Database sizing is designed to give you estimates of the database growth and to help you plan the disk requirements.

Capacity Planning

There are many factors to consider when you are estimating the amount of disk space that is required for Sterling B2B Integrator. As a result, trying to consider all growth factors is impractical because the user might not know the answers to many questions that are required to do a detailed forecast. Over the years, the cost of disks dramatically decreased, while their capacity and speed increased. How information system managers order disk capacity also changed from purchasing disk arrays that are dedicated to a particular database server and project to the concept of SANS.

Sterling B2B Integrator provides a way to estimate your initial disk requirements. Adjust your estimates to the confidence that you have in your data estimates when you are making the final purchase decision. After the initial purchase and production deployment, track the disk growth for future purchase forecasts.

Tracking and Estimating Future Disk Requirements

Track your actual database storage usage and the number of database records regularly. Correlating these two metrics helps you plan your future disk requirements. Moreover, determining the average space that is used for each order line or shipment line helps you accurately predict your future growth requirements.