Restarting the Gateway

Normally, you do not need to restart the Gateway. You need to restart only if any of the following events occur:

• You have created a new profile and need to assign the new profile to the Gateway.

• You have modified some attributes in the existing profile and need the changes to take effect.

• Gateway crashes due errors such as OutOfMemory error.

• Gateway stops responding and does not service any requests.

To Restart the Gateway with a Different Profile

1. Restart the Gateway:

   ./psadmin start-sra-instance –u amadmin – f <password file> –N <profile name>– t <gateway>

To Restart the Gateway

1. In a terminal window, connect as root and do one of the following:

   • Start the watchdog process:

     ./psadmin sra-watchdog -u uid -f password-filename -t instance-type on

     [--adminuser | -u] uid	Specifies the administrator's distinguished name (DN) or user ID.
     [-passwordfile | -f] password-filename	Specifies the administrator's password in the password file.
     [--type | -t] instance-type	Specifies the type of the Secure Remote Access instance. Enter: gateway, nlproxy, or rwproxy.

     For information on watchdog command, see the Sun Java System Portal Server Command Line Reference Guide.

     This creates an entry in the crontab utility and the watchdog process is now active. The watchdog monitors all running instances of a Gateway on a particular machine and Gateway port and restarts the Gateway if it goes down.

To Configure the Gateway Watchdog

You can configure the time interval at which the watchdog monitors the status of the Gateway. This time interval is set to 60 seconds by default. To change this, edit the following line in the crontab utility:

0-59 * * * * gateway-install-root/SUNWportal/bin/
/var/opt/SUNWportal/.gw. 5 > /dev/null 2>&1

See the crontab man page to configure the crontab entries.