Installing Replication Server as a data service

You also need to perform these specialized tasks to install Replication Server as a data service:

As root, create the directory /opt/SUNWcluster/ha/repserver_name on both cluster nodes, where repserver_name is the name of your Replication Server. Each Replication Server must have its own directory with the server name in the path. Copy the following scripts from the Replication Server installation directory $SYBASE/$SYBASE_REP/sample/ha to:

/opt/SUNWcluster/ha/repserver_name

on both cluster nodes, where repserver_name is the name of your Replication Server:
```
repserver_start_net
repserver_stop_net
repserver_fm_start
repserver_fm_stop
repserver_fm
repserver_shutdown
repserver_notify_admin
```
If the scripts already exist on the local machine as part of another Replication Server data service, you can create the following as a link to the script directory instead:

/opt/SUNWcluster/ha/repserver_name
As root, create the directory /var/opt/repserver on both nodes if it does not exist.
As root, create a file /var/opt/repserver/repserver_name on both nodes for each Replication Server you want to install as a data service on Sun Cluster, where repserver_name is the name of your Replication Server. This file should contain only two lines in the following form with no blank space, and should be readable only by root:
```
repserver:logicalHost:RunFile:releaseDir:SYBASE_OCS:SYBASE_REP
```
```
probeCycle:probeTimeout:restartDelay:login/password
```
where:
- repserver – the Replication Server name.
- logicalHost – the logical host on which Replication Server runs.
- RunFile – the complete path of the runfile.
- releaseDir – the $SYBASE installation directory.
- SYBASE_OCS – the $SYBASE subdirectory where the connectivity library is located.
- SYBASE_REP – the $SYBASE subdirectory where the Replication Server is located.
- probeCycle – the number of seconds between the start of two probes by the fault monitor.
- probeTimeout – time, in seconds, after which a running Replication Server probe is aborted by the fault monitor, and a timeout condition is set.
- restartDelay – minimum time, in seconds, between two Replication Server restarts. If, in less than restartDelay seconds after a Replication Server restart, the fault monitor again detects a condition that requires a restart, it triggers a switch over to the other host instead. This resolves situations where a database restart does not solve the problem.
- login/password – the login/password the fault monitor uses to ping Replication Server.
To change probeCycle, probeTimeout, restartDelay, or login/password for the probe after Replication Server is installed as data service, send SIGINT(2) to the monitor process (repserver_fm) to refresh its memory.
```
kill -2 monitor_process_id
```
As root, create a file /var/opt/repserver/repserver_name.mail on both nodes, where repserver_name is the name of your Replication Server. This file lists the UNIX login names of the Replication Server administrators. The login names should be all in one line, separated by one space.

If the fault monitor encounters any problems that need intervention, this is the list to which it sends mail.

hareg -r repserver_name \

-b "/opt/SUNWcluster/ha/repserver_name" \

-m START_NET="/opt/SUNWcluster/ha/repserver_name/
repserver_start_net" \

-t START_NET=60 \

-m STOP_NET="/opt/SUNWcluster/ha/repserver_name/
repserver_stop_net" \

-t STOP_NET=60 \

-m FM_START="/opt/SUNWcluster/ha/repserver_name/
repserver_fm_start" \

-t FM_START=60 \

-m FM_STOP="/opt/SUNWcluster/ha/repserver_name/repserver_fm_stop" \

-t FM_STOP=60 \

[-d sybase] -h logical_host

where -d sybase is required if the RSSD is under HA on the same cluster, and repserver_name is the name of your Replication Server and must be in the path of the scripts.

Turn on the data service using hareg -y repserver_name.