Before you begin: To modify alert notification settings, you must be assigned the Administrator role.

In order to send alerts from WVP via SYSLOG, the WVP SYSLOG component needs to be installed in the OSS space. This component receives messages from notification component of WVP and sends out corresponding traps to the SYSLOG receiver.

Please follow the below steps to install the SYSLOG agent on OSS:

1) Go to OSS space, create a directory named umpsl in the following location /usr/tandem

Commands:

cd /usr/tandem
mkdir umpsl

Example: /usr/tandem/umpsl
 
2) Transfer the umpslog.tar file to the newly created directory
 
Example: /usr/tandem/umpsl/umpslog.tar
 
3) Extract the contents from the tar file by running the below command.

tar -o -xvf umpslog.tar
 
/usr/tandem/umpsl: tar -o -xvf umpslog.tar
 

4) Edit umpSysLogStart.sh file
 
Modify the java related parameters
Change the directory name from /usr/tandem/dir/ to corresponding one
 
export CLASSPATH=$CLASSPATH:/usr/tandem/dir/cloudbees.jar:.
                                            to
 export CLASSPATH=$CLASSPATH:/usr/tandem/umpsl/cloudbees.jar:.
               
cd /usr/tandem/dir
                to
 cd /usr/tandem/umpsl
 
 Note: umpsl is an example directory. You can change that to your desired directory.
 
5) If the TCP Process is a different from $ZTC0, define the specific process name
   (add_define =tcpip^process^name file=\$NAME) in the umpSysLogStart.sh file.
        #!/bin/sh
        cd /usr/tandem/umpsl
        export _RLD_LIB_PATH=$_RLD_LIB_PATH:/usr/tandem/javaexth11/lib
        export JAVA_HOME=/usr/tandem/nssjava/jdk180_h80/
        export JREHOME=$JAVA_HOME/jre
        export CLASSPATH=$CLASSPATH:/usr/tandem/javaexth11/lib/tdmext.jar
        export PATH=/usr/tandem/javaexth11/bin:$PATH
 
        export APP=SLWrapr
 
        export CLASSPATH=$CLASSPATH:/usr/tandem/umpsl/cloudbees.jar:.
        add_define =tcpip^process^name file=\$NAME
        export DEBUG_PROG=’run -name=/G/umpsl’
        run -name=/G/umpsl /usr/tandem/nssjava/jdk180_h80/bin/java $APP
 
6) Give execute permission to the script file chmod 755 ./umpSysLogStart.sh
 
7) On guardian, add the persistent process information via SCF using the below commands
 
Note: Modify the required fields in the below commands and run it in SCF.
 
Change the CPU values if necessary
Change the DEAFULTVOL location. This could be the default volume of the user who is logged on to NonStop

Make sure the OSS path /usr/tandem/umpsl/umpSysLogStart.sh is the same one you created in Step 1.
Make sure the ASSOCPROC process i.e. $UMPSL matches the directory name created in Step 1.
 
ADD PROCESS $ZZKRN.umpsl , &
AUTORESTART 2 , &
CPU FIRST , &
DEFAULTVOL $IDEL00.QABKCOL , &
HIGHPIN ON , &
HOMETERM $ZHOME , &
INFILE $ZHOME , &
NAME $USVM0 , &
ASSOCPROC $UMPSL , &
OUTFILE $ZHOME , &
PRIORITY 146 , &
PROGRAM $SYSTEM.SYSTEM.OSH , &
SAVEABEND OFF , &
STARTMODE MANUAL , &
STARTUPMSG “-osstty /usr/tandem/umpsl/umpSysLogStart.sh <- >>/tmp/umpSysLog.out 2>>/tmp/umpSysLog.err” , &
STOPMODE STANDARD , &
TYPE OTHER, &
USERID SUPER.SUPER
 
8) To start the process (in SCF):
-> START PROCESS $ZZKRN.UMPSL
 
9) Verify that the process is running by running the below command.
 -> Status PROCESS $ZZKRN.UMPSL
 
NONSTOP KERNEL – Status PROCESS \NSCLOUD.$ZZKRN.#UMPSL
 
Symbolic Name                    Name   State    Sub Primary  Backup   Owner
 
                                                     PID      PID      ID
UMPSL                            $USVM0 STARTED      3 ,1026  None     255,255
UMPSL                            $UMPSL STARTED      3 ,1097  None     255,255
 
10) To stop the process (in SCF): ABORT PROCESS $ZZKRN.UMPSL