I got it working!!! Here is how.
1.) Setup a Windows 2K box which has CMS Supervisor installed and IIS.
2.) In CMS make a custom real-time report and get the info you want on it. On mine I put:
Current time at CMS
Calls in Queue
Oldest Call Waiting
Percent Service Level
Agents Available
Split #
3.) Using supervisor and its script function create a script that runs this report and that exports it to html.
3.a) When creating your script it asks for a html template to use. Setup a template in html via notepad that has only this in it
<CVSUP_BODY>
<HEAD>
<META HTTP-EQUIV="REFRESH" CONTENT="15">
</HEAD>
call this htmltemp.html or whatever.
3.b) The second question in the script is where do you want to save the file. Browse to wroot or wherever your IIS will make your data publically available. Save the file under whatever name you want.
4.) You need a scheduler. If you use the one in Win2K then your report will only run once per min. As you can see from the template CONTENT="15" I want to run mine every 15 sec. So I got a program called. AutoIntern... It allows you to write script files called WRL. I created a script that looks like this:
:Loop
Run("c:\cms\blah\blah\cmsreport.autocvs", ""
Delay (15)
Goto Loop
Then I set the sceduler up to run this command once!
Now you can go out and point your browser to the IIS and file.html. You will see that every 15 seconds the browser updates with the new CMS data.
There is a lot more you can do with this if you can do Java and Javascript. In my situation they wanted something that requires NO custom code. I could only use tools that were supported by a company. In this case... CMS Supervisor is supported by Avaya, CMS custom reports are avaya, Win2K is microsoft, AutoInter is GraphicDynamics, and the HTML is plain HTML that anybody can understand and finally the WRL scripting is supported by GraphicDynamics as well.
Benefits: This takes only one CMS Supervisor client to poll CMS. All data sent via http request is text only...to save bandwidth.
Downside: You have to watch the win2K box and make sure it doesnt get overtasked. You will know when it gets tasks cause your web updates might skip. The solution is to up the time so instead of polling 15sec move upto 30sec. You will want to watch your bandwidth to the win2k box, depending on the number of people you have getting updates.
Well that is about all I can think of.... Good luck,
Ray
