search cancel

VIP Enterprise Gateway | How to Configure Services for Autostart for VIP Enterprise Gateway and other services after reboot in LINUX?

book

Article ID: 150116

calendar_today

Updated On:

Products

VIP Service

Issue/Introduction

 

Resolution

Perform the following steps with super user/root privileges:


For VIP Enterprise Gateway Service:

  1. Copy vipegconsole.rc from <VRSN_MAUTH_HOME>/server/bin to /etc/init.d.
  2. Make the script executable by using the following command. This is optional, as the rc files have execute  permissions, by default, when created:

    chmod +x /etc/init.d/vipegconsole.rc
     
  3. Create a start script symlink in the run level rc directory for the required services.rc files.

    $ ln -s /etc/init.d/vipegconsole.rc /etc/rc.d/rc5.d/S999vipegconsole

    Note: The run level of the Linux machine should be checked using the command: who --r
  4. Place the start script symlink in that particular run level rc directory.
  5. Set VRSN_MAUTH_HOME environment variable, by adding the below lines in vipegconsole.rc file,

    VRSN_MAUTH_HOME=<InstallDir> (For example, if it is default installation, the directory is:/opt/Symantec/VIP_Enterprise_Gateway)
    export VRSN_MAUTH_HOME
     
  6. Test start/stop of the service manually by calling function one of the following functions:

    /etc/init.d/vipegconsole.rc start

    /etc/init.d/vipegconsole.rc stop
     
  7. If the manual tests succeed, the configuration for autostart of services on reboot is considered complete.

For Validation Service: 

  1. Copy <valServer>.rc from <VRSN_MAUTH_HOME>/Validation/servers/<valServer>/logs/ to /etc/init.d.
  2. Make the script executable by using the following command. This is optional, as the rc files have execute permissions, by default, when created:

    chmod +x /etc/init.d/<valServer>.rc
     
  3. Create a start script symlink in the run level rc directory for the required services'.rc files.

    $ ln -s /etc/init.d/<valServer>.rc /etc/rc.d/rc5.d/S999<valServer>

    Note: The run level of the Linux machine should be checked using the command: who --r
  4. Place the start script symlink in that particular run level rc directory.
  5. Test start/stop of the service manually by calling function one of the following functions:

    /etc/init.d/<valServer>.rc start
     
    /etc/init.d/<valServer>.rc stop
  6. If the manual tests succeed, the configuration for autostart of services on reboot is considered complete.

For SSP IDP Service:

  1. Copy SSP.rc from <VRSN_MAUTH_HOME>/IDP/services/SSP/logs to /etc/init.d.
  2. Make the script executable by using the following command. This is optional, as the  rc  files have  execute permissions, by default, when created:

    chmod +x /etc/init.d/SSP.rc
     
  3. Create a start script symlink in the run level rc directory for the required services'.rc files.

    $ ln -s /etc/init.d/SSP.rc /etc/rc.d/rc5.d/S999SSP

    Note: The run level of the Linux machine should be checked using the command: who --r
  4. Place the start script symlink in that particular run level rc directory.
  5. Test start/stop of the service manually by calling function one of the following functions:

    /etc/init.d/SSP.rc start
     
    /etc/init.d/SSP.rc stop
  6. If the manual tests succeed, the configuration for autostart of services on reboot is considered complete.

For VIPMGR IDP Service:

  1. Copy VIPMGR.rc from <VRSN_MAUTH_HOME>/IDP/services/VIPMGR/logs to /etc/init.d.
  2. Make the script executable by using the following command. This is optional, as the   rc   files have   execute  permissions, by default, when created: 

    chmod +x /etc/init.d/VIPMGR.rc
     
  3. Create a start script symlink in the run level rc directory for the required services'.rc files.

    $ ln -s /etc/init.d/VIPMGR.rc /etc/rc.d/rc5.d/S999VIPMGR

    Note: The run level of the Linux machine should be checked using the command: who --r
  4. Place the start script symlink in that particular run level rc directory.
  5. Test start/stop of the service manually by calling function one of the following functions:

    /etc/init.d/VIPMGR.rc start
     
    /etc/init.d/VIPMGR.rc stop
  6. If the manual tests succeed, the configuration for autostart of services on reboot is considered complete.

For LDapSync Service:

  1. For LDapSync service, copy ldapService.rc from <VRSN_MAUTH_HOME>/LdapSync/services/ldapSync/logs to /etc/init.d.
  2. Make the script executable by using the following command. This is optional, as the   rc   files have   execute  permissions, by default, when created: 

    chmod +x /etc/init.d/ldapService.rc
     
  3. Create a start script symlink in the run level rc directory for the required services'.rc files.

    $ ln -s /etc/init.d/ldapService.rc /etc/rc.d/rc5.d/S999ldapService

    Note: The run level of the Linux machine should be checked using the command: who --r
  4. Place the start script symlink in that particular run level rc directory.
  5. Test start/stop of the service manually by calling function one of the following functions:

    /etc/init.d/ldapService.rc start
     
    /etc/init.d/ldapService.rc stop
  6. If the manual tests succeed, the configuration for autostart of services on reboot is considered complete.

Additional Configurations for RHEL 7.x

If you have an instance of RHEL 7.x, you must edit the respective script for each service.

Edit the file /etc/init.d/<script_name> and add the following lines:

#!/bin/bash (Note: this line may already exist)
# chkconfig: 2345 11 89
# description: <Starts the appropriate Service>

After you update script as mentioned above, you must additionally run the below command to each script:

'/sbin/chkconfig --add /etc/init.d/<script_name>'