Planning the Sun Cluster HA for SWIFTAlliance Gateway Installation and Configuration

This section contains the information that you need to plan your Sun Cluster HA for SWIFTAlliance Gateway installation and configuration.

Note –

Before you begin, consult your SWIFTAlliance Gateway documentation for configuration restrictions and requirements that are not imposed by Sun Cluster software. For information about restrictions that the Sun Cluster software imposes, see the Sun Cluster documentation.

Configuration Restrictions

The configuration restrictions in this section apply only to Sun Cluster HA for SWIFTAlliance Gateway.

Caution –

If your data service configuration does not conform to these restrictions, the data service configuration might not be supported.

For restrictions that apply to all data services, see Sun Cluster 3.1 9/04 Release Notes for Solaris OS.

Sun Cluster HA for SWIFTAlliance Gateway supports SWIFTAlliance Gateway version 4.0.20 or higher and 5.0 or higher.
You can only install the SWIFTNet Link and the SWIFTAlliance Gateway software on a failover file system. If Websphere MQ client software is needed for the operation of SWIFTAlliance Gateway, install Websphere MQ client software on the local file system on each node and in the same path. The default path is /opt/mqm.
You cannot configure Sun Cluster HA for SWIFTAlliance Gateway as a scalable data service.

Configuration Requirements

The configuration requirements in this section apply only to Sun Cluster HA for SWIFTAlliance Gateway.

Caution –

If your data service configuration does not satisfy these requirements, the data service configuration might not be supported.

For requirements that apply to all data services, see “Configuration Guidelines for Sun Cluster Data Services” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

You must configure Sun Cluster HA for SWIFTAlliance Gateway as a failover data service.
If you are running SWIFTAlliance Gateway 4.0, create a SWIFTAlliance Gateway operator with an operator profile that contains only the functions to start and stop SWIFTAlliance Gateway. This operator is used to send start, stop, and status commands to SWIFTAlliance Gateway. For security reasons, do not use the administrator profile to start and stop the application.

If you are running SWIFTAlliance Gateway 5.0, an operator name and password are not necessary to send the sag_system commands directly from the SWIFTAlliance Gateway system.

Configuration Considerations

The configuration considerations in the subsections that follow affect the installation and configuration of Sun Cluster HA for SWIFTAlliance Gateway.

Resource Dependencies

Configure Sun Cluster HA for SWIFTAlliance Gateway to protect a Sun Cluster instance and its respective components. The following table outlines these components and their dependencies.

Table 1–3 Sun Cluster Components


Component	Dependencies
SWIFTAlliance Gateway This component includes the SWIFTNet Link instance.	`SUNW.LogicalHost` resource `SUNW.HAStoragePlus` resource `SUNW.scsag` resource

Configuration Files and Registration Script

The Sun Cluster component has two configuration files and a registration script.

`/opt/SUNWscsag/etc/settings.sh`	This configuration file contains settings to enable the data service to find the correct instance of SWIFTAlliance Gateway and the necessary user and password combination.
`/opt/SUNWscsag/util/sag_config`	This configuration file contains settings to register the data service and the application in the Sun Cluster framework.
`/opt/SUNWscsag/util/sag_register`	This registration script enables you to register the data service.

Configuration Planning Questions

Use the questions in this section to plan the installation and configuration of Sun Cluster HA for SWIFTAlliance Gateway. Write the answers to these questions in the space that is provided on the data service worksheets in “Configuration Worksheets” in Sun Cluster 3.1 Data Service Planning and Administration Guide.

Do you have a SWIFTNet connection and an Internet connection? The installation requires a secure server from SWIFT nv.
Do you have your SWIFTAlliance Gateway license key? If not, retrieve this information.
Do you have your SWIFTAlliance Gateway installation documentation? If not, download this documentation from http://www.swift.com.
Before you run Sun Cluster HA for SWIFTAlliance Gateway as a failover data service, answer the following questions:
- Which resource groups will you use for the SWIFTAlliance Gateway application resource and the logical hostname resource?
- What is the logical hostname for the SWIFTAlliance Gateway resource? Clients access the data service through this logical hostname.
Where will the system configuration files reside?

See “Configuration Guidelines for Sun Cluster Data Services” in Sun Cluster 3.1 Data Service Planning and Administration Guide for the advantages and disadvantages of using the local file system instead of the cluster file system.