Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Solaris Cluster Data Service for SWIFTAlliance Gateway Guide Oracle Solaris ClusterSPARC Platform Edition |
1. Installing and Configuring Oracle Solaris Cluster HA for Alliance Gateway
Oracle Solaris Cluster HA for Alliance Gateway Overview
Overview of Installing and Configuring Oracle Solaris Cluster HA for Alliance Gateway
Planning the Oracle Solaris Cluster HA for Alliance Gateway Installation and Configuration
Configuration Files and Registration Script
Configuration Planning Questions
Installing and Configuring Alliance Gateway
How to Install and Configure Alliance Gateway
How to Verify the Alliance Gateway Installation and Configuration
Installing the Oracle Solaris Cluster HA for Alliance Gateway Packages
How to Install the Oracle Solaris Cluster HA for Alliance Gateway Packages
Registering and Configuring the Oracle Solaris Cluster HA for Alliance Gateway
How to Register and Configure Oracle Solaris Cluster HA for Alliance Gateway as a Failover Service
Verifying the Oracle Solaris Cluster HA for Alliance Gateway Installation and Configuration
How to Verify the Oracle Solaris Cluster HA for Alliance Gateway Installation and Configuration
Tuning the Oracle Solaris Cluster HA for Alliance Gateway Fault Monitor
Debugging Oracle Solaris Cluster HA for Alliance Gateway
How to Set the Debug Flag for Oracle Solaris Cluster HA for Alliance Gateway
How to Debug a Failed Restart for the Alliance Gateway Resource
To enable Oracle Solaris Cluster HA for Alliance Gateway to make Alliance Gateway highly available, additional installation and configuration operations are required. These operations supplement the standard installation and standard configuration of Alliance Gateway.
During a standard installation, Alliance Gateway is installed with a physical hostname. To enable Alliance Gateway to run in a cluster, you must modify Alliance Gateway to use a logical hostname.
For information about the standard installation and standard configuration of Alliance Gateway, see the appropriate documentation available in the Alliance Gateway CD-ROM.
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 Oracle Solaris Cluster Data Services, in Oracle Solaris Cluster Data Services Planning and Administration Guide.
# clresourcegroup create [-n node-zone-list] sag-rg
Specifies a comma-separated, ordered list of zones that can master the resource group. The format of each entry in the list is node. In this format, node specifies the node name and zone specifies the name of a non-global Solaris zone. To specify the global zone, or to specify a node without non-global zones, specify only node. This list is optional. If you omit this list, the global zone of each cluster node can master the resource group.
A logical host is required before you install Alliance Gateway.
# clreslogicalhostname -g sag-rg -h swiftgatewayhost sag-lh-rs
Although you can use a global file system, create an HAStoragePlus failover resource to contain the Alliance Gateway application and configuration data.
To create a device group and a file system for Alliance Gateway, see Planning the Global Devices, Device Groups, and Cluster File Systems in Oracle Solaris Cluster Software Installation Guide.
To create an HAStoragePlus failover resource, see Enabling Highly Available Local File Systems in Oracle Solaris Cluster Data Services Planning and Administration Guide.
This procedure uses /swift as the path that contains the Alliance Gateway application and configuration data.
# clresource create -g sag-rg \ -t SUNW.HAStoragePlus -x filesystemMountPoints=/swift sag-ds
# clresourcegroup online -M sag-rg
Without these symbolic links, the Alliance Gateway application will not be installed in the correct location. You must install the Alliance Gateway application in the correct location to ensure failover capabilities.
Perform this procedure on the node where the resource group for Alliance Gateway is online.
For Alliance Gateway 6.3 and prior versions:
# mkdir -p /swift/etc/opt/swnet # chown root:swnetg /swift/etc/opt/swnet # chmod -R 0555 /swift/etc # chmod 0775 /swift/etc/opt/swnet # mkdir -p /swift/var/opt/swnet # chown root:swnetg /swift/var/opt/swnet # chmod -R 0555 /swift/var # chmod 0775 /swift/var/opt/swnet # mkdir -p /swift/home/swnet # chown swnet:swnetg /swift/home/swnet
For Alliance Gateway 7.0:
# mkdir -p /swift/etc/opt/swnet /swift/etc/opt/secrets_backup # chown swnet:swnetg /swift/etc/opt/swnet /swift/etc/opt/secrets_backup # chmod -R 0555 /swift/etc # chmod 0775 /swift/etc/opt/swnet /swift/etc/opt/secrets_backup # mkdir -p /swift/var/opt/swnet /swift/var/opt/swift # chown swnet:swnetg /swift/var/opt/swnet /swift/var/opt/swift # chmod -R 0555 /swift/var # chmod 0775 /swift/var/opt/swnet /swift/var/opt/swift # mkdir -p /swift/home/swnet # chown swnet:swnetg /swift/home/swnet
Perform this procedure on all cluster nodes.
For Alliance Gateway 6.3 and prior versions:
# ln -s /swift/home/swnet /export/home/swnet # ln -s /swift/etc/opt/swnet /etc/opt/swnet # ln -s /swift/var/opt/swnet /var/opt/swnet
For Alliance Gateway 7.0:
# ln -s /swift/home/swnet /export//home/swnet # ln -s /swift/etc/opt/swnet /etc/opt/swnet # ln -s /swift/etc/opt/secrets_backup /etc/opt/secrets_backup # ln -s /swift/var/opt/swnet /var/opt/swnet # ln -s /swift/var/opt/swift /var/opt/swift
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 Alliance Gateway installation and have the appropriate license, install the WebSphere MQ client packages. The WebSphere MQ client package must be installed locally by using the same installation directory on all cluster nodes or zones that can master the resource group.
You must install SWIFTNet Link on the node or zone where the resource group for Alliance Gateway is online. You must also install SWIFTNet Link in the directory on the file system managed by the HAStoragePlus resource that you created in Step 3.
Follow the instructions in your SWIFTNet Link documentation. To refer the SWIFTNet Link documentation, obtain the SWIFTNet Link CD-ROM.
Specify the directory on which to install the failover data service: /swift/snl.
Install any patches for SWIFTNet Link, if required.
The Hardware Security Module (HSM) Installation/Configuration wizard starts up automatically when you click Finish at the end of SWIFTNet Link installation. Click Cancel to exit the HSM Installation/Configuration wizard.
Verify that connectivity with SWIFTNet Switch is established by running the SWIFTNet Link selftest command. For more information, see SWIFTNet Admin Services: Operational Interface on the Alliance Gateway CD-ROM.
Stop the SWIFTNet Link instance by running the SWIFTNet Link stop command.
Log on to the primary node or zone as the SWIFTNet Link instance owner with the swnet account.
Run the following command:
# perl SwHSMDiskClone.pl -a SETUP
Log off.
Log on as the SWIFTNet Link instance owner with the swnet account.
Use the HSM administration tool SwHSM to configure and register the HSM boxes connected to the primary node. See the SWIFTNet Link Installation and Administration Guide for UNIX for details.
Note - During the configuration and registration of the HSM, you must enter the boot IP address of the primary node in the SWIFTNet Link host IP address field of the Register screen. This source IP address is used to establish the connection. Do not use the logical host address that is used by the service.
Switch the resource group for Alliance Gateway to the secondary node or zone.
# clresourcegroup switch -n node2 sag-rg
Log on to the secondary node as the SWIFTNet Link instance owner with the swnet account.
Run the following command:
# perl SwHSMDiskClone.pl -a SETUP
Log off.
Log on as the SWIFTNet Link instance owner with the swnet account.
Use the HSM administration tool SwHSM to register the HSM boxes connected to the secondary node or zone. See the SWIFTNet Link Installation and Administration Guide for UNIX for details.
Note - During the registration of the HSM, you must enter the boot IP address of the secondary node or zone in the SWIFTNet Link host IP address field of the Register screen. This source IP address is used to establish the connection. Do not use the logical host address that is used by the service.
You must install Alliance Gateway on the node or zone where the resource group for Alliance Gateway is online. You must also install Alliance Gateway in a directory on the file system managed by the HAStoragePlus resource that you created in Step 3. In this procedure, /swift/SWIFTAlliance/Gateway is being used as the directory. You might install the Alliance Gateway patches, if necessary.
Follow the instructions in your Alliance Gateway documentation. To refer the Alliance Gateway documentation, obtain the Alliance Gateway CD-ROM.
Use the logical IP address as the IP with which the Alliance Gateway software communicates with remote hosts.
For Alliance Gateway 6.3 and prior versions: The ~root/vpd.properties directory has been replaced by the ~root/InstallShield directory structure. This directory structure needs to be copied on all cluster nodes or zones that can master the resource group. It enables you to install patches in the future. Moreover, after every SWIFTNet Link or Alliance Gateway patches installation or uninstallation, the synchronization of the ~root/InstallShield directory has to be redone.
Add all entries in /etc/system and /etc/services added by the installation on the first node to the secondary node or zone that can master the resource group. The entries in /etc/system must be applied to the global zone.
Next Steps
Go to How to Verify the Alliance Gateway Installation and Configuration.
Perform this procedure on each node or zone that can master the Alliance Gateway resource group.
# clresourcegroup switch -h node sag-rg
Specifies that the Alliance Gateway resource group is to be switched to another node or zone
Specifies the node or node:zone to which the Alliance Gateway resource group is to be switched
# su - swnet $ cd /swift/SWIFTAlliance/Gateway/bin $ ./sag_bootstrap -startsag start $ ./sag_system -- status system
Note - The application starts successfully if the preceding command returns a started status. This status indicates that the Alliance Gateway is operational.
# su - swnet $ cd /swift/SWIFTAlliance/Gateway/bin $ ./sag_bootstrap stop
Next Steps
Go to Installing the Oracle Solaris Cluster HA for Alliance Gateway Packages.