Experience reports

For many customers the amount of data stored in the integrated file system is small enough that it is not a concern. However, for an increasing number of iSeries^(TM) customers the backup of their integrated file system data has created additional considerations for their backup. This experience report documents information about integrated file system backup. It is intended to help those customers who are experiencing concerns.

This report details Management Central connections and the configurations required to enable Management Central to operate within a variety of firewall environments. As a distributed management application, Management Central requires numerous incoming and outgoing TCP/IP socket connections. In contrast, the basic premise of a firewall is to restrict or modify incoming and outgoing connections.

Consolidating i5/OS^(TM), AIX^(R), Linux^(R), and Windows^(R) servers onto an eServer i5 system allows for maximum resource utilization. This report details the benefits of consolidation as well as outlining the general process for moving to the new system.

This report documents the IBM eServer^(TM) i5 Customer Solution Test team's experience of implementing a small-to-medium business (SMB) scenario using WebSphere^(R) Application Server - Express and Lotus^(R) Domino^(R). In this scenario, WebSphere Application Server - Express for iSeries is used to establish an initial Web presence through dynamic Web pages, database access, and directory server access. A Lotus Domino application meanwhile provides internal dynamic Web pages for iDrink employees.

Job accounting is a function available on every iSeries Server that can be used to track usage of system resources.

This document describes the process of migrating an Oracle^(TM) database to DB2^(R) Universal Database^(TM) for iSeries using the Oracle Migration Toolkit (MTK).

The iSeries server has the ability to automatically manage the shared memory pools without any user interaction. This function is controlled by the performance adjustment system value, QPFRADJ.

This report describes ways you can control how long it takes to start your iSeries server. The initial program load (IPL) for an iSeries server is made up of three major stages. First the hardware is powered up, second the Licensed Internal Code is initialized, and third operating system is started. This report focuses on performance aspects of the IPL that change based on how you configure and use your system.

At times you might need to perform work on your iSeries server without interference from other users. Performing that work while the system is in the restricted state allows you to do just that.

As hardware capacity and workloads on the iSeries increase, considerations should be made to ensure that performance of spool operations is efficient.

The default subsystem configuration included with the operatng system is a basic subsystem configuration that works well for small systems. However, as the number of users increase on the system, it is desirable to split the work into multiple subsystems to better manage the work on the system.

This document shows how to manage prestart jobs to improve overall system performance.

There are several work management interfaces that can be used to retrieve information about jobs. The same job attribute may be available on several different user interfaces. Determining the best interface to use for a particular piece of information can be difficult. This experience report provides a summary of information to make it easier to determine which interfaces to use when dealing with job attributes.