If you don't have access to enterprise level monitoring tools (such as
patrol, MOM, splunk, etc...) and if this is windows OS you could use the
arapi.net and vbscript on the arserver to send an email notification of
error on login or vice versa of healthy login. If you execute remotely,
then this could also tell you if the server is even up and has network
connectivity. 

 

Something like below... you could fancy this up as needed e.g. to verify
email engine is processing by looking if outgoing is queuing.

 

            Dim oShell,hdserver,hduser,hdpass

            Set oShell = CreateObject( "WScript.Shell" )

            hdserver = oShell.ExpandEnvironmentStrings("%ComputerName%")

            

            hduser = <username>

            hdpass = <password>

 

Set server      = CreateObject("BMC.ARSystem.Server")

            server.Login hdserver, hduser, hdpass

Dim strerr 

            strerr = Err.Number

 

            If strerr <> 0  Then

 

                        Dim strsubject

                        strsubject = "Remedy is not responding on " &
hdserver

                        Dim strerrortxt

                        strerrortxt = Now & " -- Error Section: # " &
strerrsection & "; Error Number: " & Err.Number & "; Error Description:
" & Err.Description & "; Error Source: " & Err.Source

 

                        SendEmailNotify(strsubject, strerrortxt)

 

            End If

 

            server.Logout

 

Function SendEmailNotify(strsubject,strbody)

 

            On Error Resume Next

            Err.Clear

 

            Dim objMessage: Set objMessage = CreateObject("CDO.Message")


            Dim strTo

            Dim hdserver 

            hdserver = oShell.ExpandEnvironmentStrings("%ComputerName%")

            strTO = <sento address>

            objMessage.Subject = strsubject 

            objMessage.From = hdserver

            objMessage.To = strTO 

            'objMessage.Cc = ""

            'objMessage.Bcc = ""

            objMessage.HTMLBody = strbody

 

            '==This section provides the configuration information for
the remote SMTP server.

            '==Normally you will only change the server name or IP.

            objMessage.Configuration.Fields.Item _

            ("http://schemas.microsoft.com/cdo/configuration/sendusing";)
= 2 

 

            'Name or IP of Remote SMTP Server

            objMessage.Configuration.Fields.Item _

 
("http://schemas.microsoft.com/cdo/configuration/smtpserver";) = <your
smtp host>

 

            'Server port (typically 25)

            objMessage.Configuration.Fields.Item _

 
("http://schemas.microsoft.com/cdo/configuration/smtpserverport";) = 25 

 

            objMessage.Configuration.Fields.Update

 

            '==End remote SMTP server configuration section==

 

            objMessage.Send

 

            Set objMessage = NOTHING

 

End Function

 

Regards,

 

Andrew Goodall

Software Engineer 2 | Development Services |  jcpenney . www.jcp.com
<http://www.jcp.com/>  

________________________________

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing
Sent: Thursday, February 09, 2012 4:12 PM
To: arslist@ARSLIST.ORG
Subject: Server 'Alive' check

 

Listers,

As we have discussed several times in the past a simple 'port check'
isn't sufficient to tell you that your server is 'alive'.  I'm looking
for assistance with 'what do you check' when you are checking to see if
your remedy server is alive and healthy.  I'm not looking to check the
MidTier in this effort...just the Remedy server itself.  So far I have
my script performing the following actions

 

-          Login

-          Search User Form

-          Execute Service

 

The first of course ensures that the server is processing logins

The second asks the remedy server to connect to the DB and return
results

The third 'exercises' it just a bit, asking it to do some things that
one of our services does, and return a result

 

These are of course just a small sampling of things I can have my script
do...I was looking to the list to see if you have any 'oh yea, that's a
good check' type of things that you typically do when embarking on this
type of effort. 

_attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_
<font face="monospace"size="-3"><br>The information transmitted is intended 
only for the person or entity to which it is addressed and <br>may contain 
confidential and/or privileged material. If the reader of this message is not 
the intended<br>recipient, you are hereby notified that your access is 
unauthorized, and any review, dissemination,<br>distribution or copying of this 
message including any attachments is strictly prohibited. If you are not<br>the 
intended recipient, please contact the sender and delete the material from any 
computer.<br>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"

Reply via email to