test

Sun Cluster Data Service for SWIFTAlliance Gateway Guide for Solaris OS

Installing and Configuring Alliance Gateway

To enable Sun 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 Sun Cluster Data Services, in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

ProcedureHow to Install and Configure Alliance Gateway

  1. Create a resource group for Alliance Gateway.


    # clresourcegroup create [-n node-zone-list] sag-rg
    -n node-zone-list

    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.

  2. Create a logical host.

    A logical host is required before you install Alliance Gateway.

    1. Add the hostname and the IP address in the /etc/inet/hosts file on all cluster nodes or zones that can master the resource group.

    2. Register the logical host, and then add the logical host resource to the resource group.


      # clreslogicalhostname -g sag-rg -h swiftgatewayhost sag-lh-rs

  3. Create the device group and file systems.

    Although you can use a global file system, create an HAStoragePlus failover resource to contain the Alliance Gateway application and configuration data.

    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

  4. Bring the resource group online to enable the IP address and access to the storage.


    # clresourcegroup online -M sag-rg

  5. Create the following directories and symbolic links before the installation.

    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.


    # 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

    Perform this procedure on all cluster nodes.


    # 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

  6. Install the WebSphere MQ client packages, if required.

    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.

  7. Install SWIFTNet Link.

    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.

  8. Configure and register HSM on the primary node as follows.

    • 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.

  9. Register HSM on the secondary node or zone.

    • 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.

      Note –

      You must be aware that the only difference between Step 8 and this step is that you configure and register the HSM on the first node or zone in Step 8, whereas you only register the HSM on the secondary node or zone in this step.

  10. Install Alliance Gateway software.

    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.

  11. Synchronize all nodes or zones with installation-specific changes to user files and system files.

    • 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.

ProcedureHow to Verify the Alliance Gateway Installation and Configuration

Perform this procedure on each node or zone that can master the Alliance Gateway resource group.

  1. Log in as superuser to a node or zone that can master the Alliance Gateway resource group.

  2. Switch the Alliance Gateway resource group to the node or zone that you logged in to in Step 1.


    # clresourcegroup switch -h node sag-rg
    sag-rg

    Specifies that the Alliance Gateway resource group is to be switched to another node or zone

    -h node

    Specifies the node or node:zone to which the Alliance Gateway resource group is to be switched

  3. Confirm that the Alliance Gateway instance can be started.


    # 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.

  4. Create another Alliance Gateway operator with an operating profile that contains only the functions to start and stop the application.

  5. Confirm that the Alliance Gateway instance can be stopped.


    # su - swnet
$ cd /swift/SWIFTAlliance/Gateway/bin
$ ./sag_bootstrap stop
Next Steps

Go to Installing the Sun Cluster HA for Alliance Gateway Packages.