| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris Cluster Data Service for SWIFTAlliance Access Guide SPARC Platform Edition |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle Solaris Cluster Data Service for SWIFTAlliance Access Guide SPARC Platform Edition |
1. Installing and Configuring Oracle Solaris Cluster HA for Alliance Access
Overview of Installing and Configuring HA for Alliance Access
Planning the Oracle Solaris Cluster HA for Alliance Access Installation and Configuration
Oracle Solaris Cluster components and their dependencies
Installing and Configuring Alliance Access
How to Install and Configure Alliance Access
Verifying the Installation and Configuration of Alliance Access
How to Verify the Installation and Configuration of Alliance Access
Installing the HA for Alliance Access Packages
How to Install the HA for Alliance Access Packages
Registering and Configuring Oracle Solaris Cluster HA for Alliance Access
How to Register and Configure Oracle Solaris Cluster HA for Alliance Access as a Failover Service
Verifying the Oracle Solaris Cluster HA for Alliance Access Installation and Configuration
How to Verify the Oracle Solaris Cluster HA for Alliance Access Installation and Configuration
Understanding the Oracle Solaris Cluster HA for Alliance Access Fault Monitor
Probing Algorithm and Functionality
Debugging Oracle Solaris Cluster HA for Alliance Access
How to turn on debugging for Oracle Solaris Cluster HA for Alliance Access
The HA agent is written to work with Alliance Access versions 5.5, 5.9, 6.0, 6.2 and 6.3. IBM DCE version 3.2 is not used anymore by Alliance Access 5.9 and later, and must only be installed for Alliance Access 5.5. Alliance Accessis a trademark of SWIFT.
The Oracle Solaris Cluster HA for Alliance Access data service provides a mechanism for orderly startup, shutdown, fault monitoring, and automatic failover of the Oracle Solaris Cluster service. The Oracle Solaris Cluster components protected by the Oracle Solaris Cluster HA for Alliance Access data service are the following.
Table 1-2 Protection of Components
|
Note - By default the HA agent provides a fault monitor for the DCE component only when using the Alliance Access 5.5. The fault monitoring for Alliance Access is switched off by default. If the Alliance Access application fails, the agent will not restart the Alliance Access application automatically. This behavior was explicitly requested by SWIFT. It will enable you to operate the application in a way that the probe does not interfere with the normal behavior of some Alliance Access features like:
operator manually triggering the Alliance Access restart function , for example, to run Alliance Access in housekeeping mode.
automatic or scheduled Alliance Access restart, for example, to run database backup and other maintenance or end-of-day processes.
any graceful Alliance Access restart or recovery, in case of a Alliance Access transient local error.
The HA agent provides the start, stop, takeover, and switchover functionality. This means that when a node fails, the other node will automatically start the Alliance Access application. The HA agent also provides an option to turn on fault monitoring for Alliance Access at registration time. However, this option is not recommended by SWIFT.
|