Yes, I know all that. I was basing on the assumption that the initial connection could be made. If not I would hope the server would know that KioskX has not checked in. Running an app in parallel is wasted overhead; we don’t know what kind of data is being pulled every ten seconds. If a parallel app is to be considered than would be better if the browser got its data from that app (local server) rather than make a duplicate request over the wire.
From: Ken Schaefer Sent: Thursday, October 31, 2013 9:23 PM To: [email protected] Subject: RE: [NTSysADM] test IE uptime? Firstly – java Applet <> javascript – let’s try not to confuse OP J Secondly, you need to be able to load a page in the first place, to be able to host a java applet or run a javascript. If the browser can’t connect to the server at all (network down, web server down, page taking too long to load), then your applet or script isn’t going to run. Instead, host a script or agent on the PC that can work autonomously of the browser. It just acts like a browser, and makes the same request. If there’s a connectivity issue, or web server issue, then it can still generate the necessary log files on the client, which can be retrieved when the network is up (or at any time if the issue is simply the web server being down). Using the browser itself seems to introduce unnecessary complexity /unless/ (as Richard has hinted) you need to check the actual rendering/display of the page within that specific browser. Cheers Ken From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Chenault Sent: Friday, 1 November 2013 1:04 PM To: [email protected] Subject: Re: [NTSysADM] test IE uptime? The assumption is the applet is part of the parent; it will stay active as long as focus remains on that page. The page shouldn’t take longer than X seconds to load so the applet checks for the trigger set; if not immediate fail. If trigger set and no errros, no problem. If IE cannot connect at all but the applet is loaded it can alert catastrophic failure via it’s own PUT. And if THAT fails no amount of fancy dancing with code is going to be able to alert central that the kiosk is off the net. Server side it should be looking for the applet’s confirmation of failure or success and log accordingly for metric purposes. From: Ken Schaefer Sent: Thursday, October 31, 2013 8:57 PM To: [email protected] Subject: RE: [NTSysADM] test IE uptime? Doesn’t really help if the page times out in loading, or IE isn’t able to connect to the server at all. Will need some other solution to track those occurrences. Cheers Ken From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Chenault Sent: Friday, 1 November 2013 12:42 PM To: [email protected] Subject: Re: [NTSysADM] test IE uptime? Is it possible to run a java script in the user environment? Web page loads and sets trigger Applet sees trigger and checks page for known error text If error found request a server side action to set a trigger Said trigger examined server side and appropriate action taken And all this science I don't understand It's just my job five days a week Elton John "Rocket Man" On Oct 31, 2013, at 19:24, "Jimmy Tran" <[email protected]> wrote: I’ve been tasked with determining a way to document if a web page in IE errors out. Basically, the page will refresh every 10 seconds with updated data. I need to find a way to see if the page comes back with a page error or not. Any ideas out there? These tests will be performed at kiosks that have no management that have poor internet connectivity. All I can currently measure is system up time, not internet connectivity uptime or page errors in IE. TIA Jimmy
