Planning the Oracle Solaris Cluster HA for Alliance Gateway Installation and Configuration

This section contains the information that you need to plan your Oracle Solaris Cluster HA for Alliance Gateway installation and configuration.

Configuration Restrictions

The configuration restrictions in this section apply only to Oracle Solaris Cluster HA for Alliance 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 Oracle Solaris Cluster 3.3 Release Notes.

• Oracle Solaris Cluster HA for Alliance Gateway supports Alliance Gateway version 6.0, 6.1, 6.3, and 7.0.

• You can install the SWIFTNet Link and the Alliance Gateway software only on a failover file system. If WebSphere MQ client software is needed for the operation of Alliance Gateway, install WebSphere MQ client software on the local file system in the same path on each cluster node or zone that can master the resource group. The default path is /opt/mqm.

• You cannot configure Oracle Solaris Cluster HA for Alliance Gateway as a scalable data service.

• If the Alliance Gateway instance is started through the cluster resource, do not stop it manually. Instead, stop Alliance Gateway by disabling the corresponding cluster resource.

Configuration Requirements

The configuration requirements in this section apply only to Oracle Solaris Cluster HA for Alliance 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 Oracle Solaris Cluster Data Services in Oracle Solaris Cluster Data Services Planning and Administration Guide.

• You must configure Oracle Solaris Cluster HA for Alliance Gateway as a failover data service.

• Create the following groups with the same group ID on all cluster nodes or zones that can master the resource group: sagsnlg, swnetg.

  # groupadd -g groupid1 swnetg

  # groupadd -g groupid2 sagsnlg

• Create the following user with the same user ID on all cluster nodes or zones that can master the resource group: swnet.

  # useradd -u userid -g swnetg -d /export/home/swnet -s /usr/bin/ksh swnet

• Create a Solaris project called swift on all cluster nodes or zones that can master the resource group.

  For Alliance Gateway 6.3 and prior versions:

  # projadd -U swnet swift

  # projmod -s -K 'project.max-sem-ids=(privileged,1080,deny)' swift

  # projmod -s -K 'process.max-sem-nsems=(privileged,512,deny)' swift

  # projmod -s -K 'project.max-shm-memory=(privileged,4294967295,deny)' swift

  # projmod -s -K 'project.max-shm-ids=(privileged,1200,deny)' swift

  # projmod -s -K 'process.max-msg-qbytes=(privileged,10485760,deny)' swift

  # projmod -s -K 'process.max-msg-messages=(privileged,8192,deny)' swift

  For Alliance Gateway 7.0:

  # projadd -U swnet swift

  # projmod -s -K 'project.max-sem-ids=(privileged,1320,deny)' swift

  # projmod -s -K 'process.max-sem-nsems=(privileged,512,deny)' swift

  # projmod -s -K 'project.max-shm-memory=(privileged,4294967295,deny)' swift

  # projmod -s -K 'project.max-shm-ids=(privileged,1500,deny)' swift

  # projmod -s -K 'project.max-msg-ids=(privileged,800,deny)' swift

  # projmod -s -K 'process.max-msg-qbytes=(privileged,10485760,deny)' swift

  # projmod -s -K 'process.max-msg-messages=(privileged,8192,deny)' swift

  # projmod -s -K 'process.max-sem-ops=(privileged,512,deny)' swift

  The previous values are examples only. For more accurate values refer to the SWIFTNet Link and Alliance Gateway latest documentation release notes.

• Assign project swift as default project for swnet user by editing the /etc/user_attr file and adding the following line at the end of the file on all cluster nodes or zones that can master the resource group:

  swnet::::project=swift

• Refer to the SWIFTNet Link and Alliance Gateway documentation Release Notes for the required setup in the /etc/system directory on all cluster nodes.

Configuration Considerations

The configuration considerations in the subsections that follow affect the installation and configuration of Oracle Solaris Cluster HA for Alliance Gateway.

Resource Dependencies

Configure Oracle Solaris Cluster HA for Alliance Gateway to protect an Oracle Solaris Cluster instance and its respective components. The following table outlines these components and their dependencies.

Table 1-3 Oracle Solaris Cluster Components

Configuration Files and Registration Script

The Oracle Solaris Cluster component has a configuration file and a registration script.

Configuration Planning Questions

Use the questions in this section to plan the installation and configuration of Oracle Solaris Cluster HA for Alliance Gateway. Write the answers to these questions in the space that is provided on the data service worksheets in Configuration Worksheets in Oracle Solaris Cluster Data Services Planning and Administration Guide.

• Do you have a SWIFTNet connection and an Internet connection? The installation requires a secure server from SWIFT.

• Do you have your Alliance Gateway license key? If not, retrieve this information.

• Do you have your Alliance Gateway installation documentation? If not, refer the documentation available in the Alliance Gateway CD-ROM.

• Before you run Oracle Solaris Cluster HA for Alliance Gateway as a failover data service, answer the following questions:

  • Which resource groups will you use for the Alliance Gateway application resource and the logical host name resource?

  • What is the logical hostname for the Alliance Gateway resource? Clients access the data service through this logical hostname.

• Where will the system configuration files reside?

  See Configuration Guidelines for Oracle Solaris Cluster Data Services in Oracle Solaris Cluster Data Services Planning and Administration Guide for the advantages and disadvantages of using the local file system instead of the cluster file system.