Setting up the high availability control scripts (Tivoli System Automation for Multiplatforms example)

Set up scripts to start, stop, and monitor the servers. Then, create the application resources.

About this task

Several sample high availability control scripts are supplied with IBM® InfoSphere® Information Server. These scripts are used in this example. See High availability control scripts included with IBM InfoSphere Information Server.

Procedure

Copy the script files to a directory on the storage area network (SAN).
For example: /opt/IBM/hascripts

Create an application resource configuration file for the services tier. Put the file in the same directory as the script files. For example: /opt/IBM/hascripts.

The following sample file defines an application resource for the services tier. The file is named /opt/IBM/hascripts/InfoSvrServices.IBM.Application:

PersistentResourceAttributes::
    Name="ServicesApp"
    StartCommand="/opt/IBM/hascripts/InfoSvrServices start"
    StopCommand="/opt/IBM/hascripts/InfoSvrServices stop"
    MonitorCommand="/opt/IBM/hascripts/InfoSvrServices status"
    MonitorCommandPeriod=60
    MonitorCommandTimeout=60
    NodeNameList={"myprimary","mysecondary"}
    StartCommandTimeout=240
    StopCommandTimeout=240
    UserName="root"
    ResourceType=1

Run the mkrsrc command to create the application resource for the services tier:
```
mkrsrc -f /opt/IBM/hascripts/InfoSvrServices.IBM.Application IBM.Application
```

Create an application resource configuration file for the engine tier.

The following sample file defines an application resource for the engine tier. The file is named /opt/IBM/hascripts/InfoSvrEngine.IBM.Application:

PersistentResourceAttributes::
    Name="EngineApp"
    StartCommand="/opt/IBM/hascripts/InfoSvrEngine start"
    StopCommand="/opr/hascripts/InfoSvrEngine stop"
    MonitorCommand="/opt/IBM/hascripts/InfoSvrEngine status"
    MonitorCommandPeriod=60
    MonitorCommandTimeout=60
    NodeNameList={"myprimary","mysecondary"}
    StartCommandTimeout=240
    StopCommandTimeout=240
    UserName="root"
    ResourceType=1

Run the mkrsrc command to create the application resource for the engine tier:
```
mkrsrc -f /opt/IBM/hascripts/InfoSvrEngine.IBM.Application IBM.Application
```
Run the rgreq command to lock the harg resource group:
```
rgreq -o lock harg
```
Run the addrgmbr command to add the services tier application resource to the resource group harg that was created:
```
addrgmbr -g harg IBM.Application:ServicesApp
```
Run the addrgmbr command to add the engine tier application resource to the resource group harg that was created:
```
addrgmbr -g harg IBM.Application:EngineApp
```
Run the mkrel command to define the relationship between the InfoSphere Information Server services tier application resource (ServicesApp) and the virtual IP resource (haip):
```
mkrel -p StartAfter -S IBM.Application:ServicesApp -G IBM.ServiceIP:haip 
   ServicesApp_startafter_haip
```
Run the mkrel command to define the relationship between the InfoSphere Information Server engine tier application resource (EngineApp) and the virtual IP resource (haip):
```
mkrel -p StartAfter -S IBM.Application:EngineApp -G IBM.ServiceIP:haip 
   EngineApp_startafter_haip
```

Run the lsrel command to verify the relationships:

lsrel -l

The command displays all the managed relations:

Displaying Managed Relations :


Managed Relationship 1:
        Name                        = haip_dependson_ha_nieq
        Class:Resource:Node[Source] = IBM.ServiceIP:haip
        ResourceGroup[Source]       = harg

Managed Relationship 2:
        Name                        = ServicesApp_startafter_haip
        Class:Resource:Node[Source] = IBM.Application:ServicesApp
        ResourceGroup[Source]       = harg
Managed Relationship 3:
        Name                        = EngineApp_startafter_haip
        Class:Resource:Node[Source] = IBM.Application:EngineApp
        ResourceGroup[Source]       = harg

Run the rgreq command again to unlock the resource group:
```
rgreq -o unlock harg
```