|
|
Many tips for configuring the Transaction Manager for high availability are found in 6.7, Transaction Manager high availability. However, there are a few differences to this in iSeries environments. Several of the tips in this section count on having a shared file system for sharing information and the iSeries integrated file system is not yet compatible with NFS V4.
One solution is to use the QNTC file system for sharing files in the iSeries environment. This means that we support an i5/OS™ WebSphere cluster as well as a heterogeneous WebSphere cluster containing both Windows and i5/OS cluster members when Transaction Manager logs are part of the configuration.
This section explains the high level steps for configuring high availability for the transaction logs using QNTC. For more details on configuring the transaction logs see 6.7, Transaction Manager high availability.
Before we configure the file system, there are a couple of important points to consider in order to ensure back-end failures are handled properly. First, we recommend that you use the same IASP to host both the transaction logs and the associated application databases. This ensures that both are made available at the same time during a failover event in order to avoid rollback processing. Journaling of access paths is also critical so that the application databases are truly available for reading and writing immediately after the IP takeover address becomes active. Following are the steps to configure the QNTC file system for the transaction logs.
