broker monitoring

[rob van kol]

Hi Guys,

My first post. I have a question. I am not a progress programmer but system administrator.

we have severall windows servers running progress v9 on which severall db are running accessable via (defined in services file) tcp ports.

I can do a simple scan on that port to see if the broker is running but I can also drop some expressions on it to see if the db is also serving requests.

Send statement= ???
Expected answer= ???

Because of a few dropouts of brokers we need to monitor these now to be sure they are up and running and in case not, a helpdeks call is generated.

I hope I make myself clear what I want.

Is there someone able to help me out on this one?

regards,

rob

 

[palthe]

If I'm not mistaking you just frequently want to "shoot" at the database broker to see if it's still up? How frequently?

Maybe you could just use a connect statement?
So you create a <procedurename>.p with just

connect <databasename> -H <hostname> -S <servicename> in it.

then you create a batch file to run it.
something like:

call <progress-root-dir>\bin\prowin32.exe -b -p <ProcedureName>.p

this will trigger an error if the broker (-S) is not started.

 

[rob van kol]

Hi,

Yep, thats what I want indeed.... every 10 minutes we want to check if the DB is still reachable.

thanks for the reply, I will test it today.

 

[palthe]

Rob,

I put this together for you (it's non-graphical and pretty fast):

1. Create a .cmd file (in my case testconnect.cmd) with the following lines:


SET DLC=c:\dlc101c
call %DLC%\bin\mbpro.bat -db exactcs -H localhost -S 5001 -b -p testconnect.p >.\testconnect.log

(of course your parameters are different).

2. Then you create a testconnect.p with the following lines:

DISPLAY "Connection to port 5001 for database exactcs established!!".
DISCONNECT exactcs.


If you now run testconnect.cmd you get a log file with either:

Connection to port 5001 for database exactcs established!!

And if your broker is offline:

** There is no server active for database exactcs on -H localhost -S 5001. (704)

You cann add a lot more call statements (for different databases) to you testconnect.cmd. If you, e.g., change only the log output to <databasename><servicename>.log for the different database brokers, you can do a different display in the .p (without the database reference).
Don't forget to disconnect the databases in the .p!!
In that way you run the .cmd once and you get output like:
exactcs5001.log
exactcs5002.log
sports20005003.log
and so on.
In thos logfiles there's only one statement, either the

** There is no server active for database <databasename> on -H <hostname> -S <portnumber>. (704)

Or the:

Connection to port <portnumber> for database <databasename> established!!