Is this possible with WebSpeed?

[Chris Kelleher]

> Hi all,
>
> I am actually running Webspeed 2.1 and 3.0B on the
> same NT box.
> WebSpeed 2.1 is connecting to 8.3B DB
> Webspeed 3.0B is connecting to Oracle 7.
>
> So I have BROKER1 for Webspeed 2.1 and BROKER2 for
> Webspeed 3.0B
>
> I would like to write an application, which checks
if
> BROKER1 and BROKER2 are up and running at a time,
and
> also get some information per broker such as :
>
> -Version of Webspeed for BROKER1 or BROKER2
> -Name of the Broker
> -Type of Database that the Broker is connected to
(i.e
> : Progress 8.3B or Oracle 7 etc..)
> -Agents connection string
>
> Is that kind of application can be written with
> Webspeed ?
> Is so, if someone can give some general guideline,
It
> will help..

 

[Chris Kelleher]

I wrote a little "WS Broker/Agent Monitor" utility
for a client I worked for a few months back. One of
my responsibilities was to ensure everyone's WS Broker
(Development, QA, Implementation, etc) was up and
running. Since there could be up to 20-25 different
Brokers running at any given time I decided to create
a tool to show me a snap shot of all Broker activity
with the click of a button.

I'll call this utility "e-Monitor"... Ok, just
kidding.

Here's a screen shot:
(please ignore the Travel Manager name)
http://www.microserve.net/~rmirro/tmbroker.gif

I used ProCGI to fire off a Progress session (I
couldn't
rely on running a WS program to handle this because it
was very possible that no Brokers were running at any
given moment). I had one program that did everything,

such as define the HTML Frameset, load the leftmost
frame
by executing some UNIX commands and directly parsing
the
webspeed.cnf file, load the bottom most frame by
executing
WS utilities via the command line, etc.

I had a WS program that displayed the "Debugger"
window.
I actually created that program much earlier than the
"Monitor", then just rolled it in.

You can see the most information the Debugger displays
in the screen shot. I have the same functionality as
the WS Workshop for displaying invalid Propath
entries,
only I simple display the Propath entry in red (which
is not displayed in the screen shot). I also provide
a mechanism to search the Propath (as Workshop does)
at the very bottom of the webpage.

I used the Debugger program for quite a while before
rolling it into the Monitor utility. It was very
helpful for quickly viewing info on the Brokers
in-house that were set to Production Mode (i.e. can't
use Workshop to view Broker related data). It was
also very helpful with out in the field with the
Implementation team. It reduced my support related
calls by HUGE amounts.

Anyway, the Debugger program currently works with
either NT or UNIX (the Monitor is a different story).
This tool will not let you determine if a WS Broker
is running though. If your using NT/IIS, you might
want to create a quick ASP front end to handle that.
It's fairly simple.

I'd be happy to send it if you'd like to review some
of the code.