To enable Sun Cluster HA for SWIFTAlliance Gateway to make SWIFTAlliance Gateway highly available, additional installation and configuration operations are required. These operations supplement the standard installation and standard configuration of SWIFTAlliance Gateway.
During a standard installation, SWIFTAlliance Gateway is installed with a physical hostname. To enable SWIFTAlliance Gateway to run in a cluster, you must modify SWIFTAlliance Gateway to use a logical hostname.
For information about the standard installation and standard configuration of SWIFTAlliance Gateway, see http://www.swift.com.
To perform this procedure, you need the server root directory (the path to the application binaries). You can install the binaries on the local disks or on the cluster file system. For a discussion of the advantages and disadvantages of each location, see Chapter 1, Planning for Sun Cluster Data Services, in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
Create a resource group for SWIFTAlliance Gateway.
# clresourcegroup create sag-rg |
Create a logical host.
A logical host is required before you install SWIFTAlliance Gateway.
Create the device group and file systems.
Although you can use a global file system, create an HAStoragePlus failover resource to contain the SWIFTAlliance Gateway application and configuration data.
To create a device group and a file system for SWIFTAlliance Gateway, see Planning the Global Devices, Device Groups, and Cluster File Systems in Sun Cluster Software Installation Guide for Solaris OS.
To create an HAStoragePlus failover resource, see Enabling Highly Available Local File Systems in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
This procedure uses /swift/SWIFTAlliance/Gateway as the path.
# clresource create -g sag-rg -t SUNW.HAStoragePlus -x filesystemMountPoints=/swift/SWIFTAlliance/Gateway sag-ds |
Bring the resource group online to enable the IP address and access to the storage.
# clresourcegroup online sag-rg |
Create the following symbolic links before the installation.
Without these symbolic links, the SWIFTAlliance Gateway application will not be installed in the correct location. You must install the SWIFTAlliance Gateway application in the correct location to ensure failover capabilities.
# cd /swift # mkdir -p /swift/etc/opt/swnet # chown -R root:system /swift/etc # chown -R root:swnetg /swift/etc/opt/swnet # chmod -R 0555 /swift/etc # chmod -R 0775 /swift/etc/opt # cd /etc/opt # ln -s /swift/etc/opt/swnet swnet # mkdir -p /swift/var/opt/swnet # chown -R root:system /swift/var/ # chown -R root:swnetg /swift/var/opt/swnet # chmod -R 0775 /swift/var # cd /var/opt # ln -s /swift/var/opt/swnet swnet |
If necessary, install the Websphere MQ client packages.
Websphere MQ client software is software that guarantees and load-balances connections between the gateway and remote SWIFTNet Link systems. If you chose this type of SWIFTAlliance Gateway installation and have the appropriate license, install the Websphere MQ client packages.
Follow the instructions in your SWIFTNet Link documentation. To download the SWIFTNet Link documentation, see http://www.swift.com.
Specify the directory on which to install the failover data service: /swift/snl.
If necessary, install any patches for SWIFTNet Link before you proceed with the installation of SWIFTAlliance Gateway.
Install SWIFTAlliance Gateway software.
Follow the instructions in your SWIFTAlliance Gateway documentation. To download the SWIFTAlliance Gateway documentation, see http://www.swift.com.
Use the logical IP address as the IP with which the SWIFTAlliance Gateway software communicates with remote hosts.
If necessary, install Websphere MQ client software.
Websphere MQ client software is software that guarantees and load-balances connections between the gateway and remote SWIFTNet Link systems. If you chose this type of SWIFTAlliance Gateway installation and have the appropriate license, install the Websphere MQ client packages.
Create the following symbolic links.
# ln -s /swift/home/swnet /home/swnet # ln -s /swift/etc/opt/swnet /etc/opt/swnet # ln -s /swift/var/opt/swnet /var/opt/swnet |
Copy the ~root/vpd.properties file from node2 to the ~root/ directory on node1.
This information enables you to install patches in the future.
Go to How to Verify the SWIFTAlliance Gateway Installation and Configuration.
Perform this procedure on each node that can master the SWIFTAlliance Gateway resource group.
Log in as superuser to a node that can master the SWIFTAlliance Gateway resource group.
Switch the SWIFTAlliance Gateway resource group to the node that you logged in to in Step 1.
# clresourcegroup switch -h node sag-rg |
Specifies that the SWIFTAlliance Gateway resource group is to be switched to another node
Specifies the node to which the SWIFTAlliance Gateway resource group is to be switched
Confirm that the SWIFTAlliance Gateway instance can be started.
# su - swnet # cd /swift/SWIFTAlliance/Gateway/bin # ./sag_bootstrap start # ./sag_system -SagUser Administrator -SagPwd pwd-for-admin -- start |
The application started successfully if the following command returns a started status. This status indicates that the SWIFTAlliance Gateway is operational.
# ./sag_system -SagUser Administrator -SagPwd pwd-for-admin -- status system |
Create another SWIFTAlliance Gateway operator with an operating profile that contains only the functions to start and stop the application.
Confirm that the SWIFTAlliance Gateway instance can be stopped.
# su - swnet # cd /swift/SWIFTAlliance/Gateway/bin # ./sag_bootstrap stop |
Go to Installing the Sun Cluster HA for SWIFTAlliance Gateway Packages.