test

Sun Cluster Data Service for SWIFTAlliance Gateway Guide for Solaris OS

Installing and Configuring SWIFTAlliance Gateway

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 the appropriate documentation available in the SWIFTAlliance 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 SWIFTAlliance Gateway

  1. Create a resource group for SWIFTAlliance Gateway.


    # scrgadm -a -g sag-rg

  2. Create a logical host.

    A logical host is required before you install SWIFTAlliance Gateway.

    1. Add the hostname and the IP address in the /etc/inet/hosts file on both cluster nodes.

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


      # scrgadm -a -L -g sag-rg -j sag-lh-rs -l swiftgatewayhost

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

    This procedure uses /swift/SWIFTAlliance/Gateway as the path.


    # scrgadm -a -g sag-rg -j sag-ds -t SUNW.HAStoragePlus -x FilesystemMountPoints=/swift

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


    # scswitch -Z -g sag-rg

  5. Create the following directories and 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.

    Perform this procedure on the node where the resource group for SWIFTAlliance 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. 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. The Websphere MQ client package must be installed locally on all nodes using the same installation directory.

  7. Install SWIFTNet Link.

    Note –

    You must install SWIFTNet Link on the node where the resource group for SWIFTAlliance Gateway is online. You must also install SWIFTNet Link in the directory on the file system managed by the HAStoragePlus resource 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.

    • If necessary, install any patches for SWIFTNet Link.

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

    • Log on to the primary 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 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 nodes.

    • Switch the resource group for SWIFTAlliance Gateway to the secondary node.


      # scswitch -z -g sag-rg -h node2

    • 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 nodes. 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 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 need to be aware that the only difference here is that you configure and register the HSM on the first node, whereas you only register the HSM on the secondary node or nodes.

  10. Install SWIFTAlliance Gateway software.

    Note –

    You must install SWIFTAlliance Gateway on the node where the resource group for SWIFTAlliance Gateway is online. You must also install SWIFTAlliance Gateway in a directory on the file system managed by the HAStoragePlus resource created in Step 3. You may install the SWIFTAlliance Gateway patches, if necessary.

    • Follow the instructions in your SWIFTAlliance Gateway documentation. To refer the SWIFTAlliance Gateway documentation, obtain the SWIFTAlliance Gateway CD-ROM.

    • Use the logical IP address as the IP with which the SWIFTAlliance Gateway software communicates with remote hosts.

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

    • The ~root/vpd.properties has been replaced by the ~root/InstallShield directory structure. This directory structure needs to be copied on all nodes that are part of the cluster. This will enable you to install patches in the future.

    • Add all entries in /etc/system and /etc/services added by the installation on the first node to the secondary node or nodes.

Next Steps

Go to How to Verify the SWIFTAlliance Gateway Installation and Configuration.

ProcedureHow to Verify the SWIFTAlliance Gateway Installation and Configuration

Perform this procedure on each node that can master the SWIFTAlliance Gateway resource group.

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

  2. Switch the SWIFTAlliance Gateway resource group to the node that you logged in to in Step 1.


    # scswitch -z -g sag-rg -h node
    -z

    Specifies that the node that masters a resource group is to be switched

    -g sag-rg

    Specifies that the SWIFTAlliance Gateway resource group is to be switched to another node

    -h node

    Specifies the node to which the SWIFTAlliance Gateway resource group is to be switched

  3. Confirm that the SWIFTAlliance 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 SWIFTAlliance Gateway is operational.

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

  5. Confirm that the SWIFTAlliance 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 SWIFTAlliance Gateway Packages.