Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     When a user bombs out of a report....

Read-Only Read-Only Topic
Go
Search
Notify
Tools
When a user bombs out of a report....
 Login/Join
 
Lambo911
Member
posted
Quite often a user submits a report, gets bored waiting for it and shuts down their session.

This still leaves the report thread active so it goes ahead and creates the report.

Does anyone know if this can be automatically cancelled when the user closes their WF session ?

You can do this in Business Objects!

Thanks
Richard

This message has been edited. Last edited by: Lambo911,


Senior Analyst

WebFOCUS 7.1.11 on Windows
 
Posts: 12 | Registered: January 13, 2010Report This Post
Ramkumar - Webfous
Guru
posted Hide Post
Interesting Qn Lambo...


Something can be done in onunload() JS function... Still a ? on my forehead.

Is there any Java APIs or FEX functions, that can be used to kill out the particular agent or connection established while generating a report. Confused


Any suggestions?


Thanks,

Ramkumar.
WebFOCUS/Tableau
Webfocus 8 / 7.7.02
Unix, Windows
HTML/PDF/EXCEL/AHTML/XML/HTML5
 
Posts: 394 | Location: Chennai | Registered: December 02, 2009Report This Post
Dave
Master
posted Hide Post
Yeah, I thought of that too...

But the "waiting" page does not contain any information about which session it is. How would you know which Agent to kill?


_____________________
WF: 8.0.0.9 > going 8.2.0.5
 
Posts: 668 | Location: Veghel, The Netherlands | Registered: February 16, 2010Report This Post
j.gross
Virtuoso
posted Hide Post
Moreover, in addition to identifying which agent, you have to be certain that it is still processing this user's request...


A plan of attack to address both issues might be ...
1. create a file with a unique token as filename, at start of the report FEX session,
2. communicate that token to the browser session
3. on page unload, kick off a fex that will...
4. cycle through the agent directories trying to locate that file
5. when found, kill that agent and exit; if not just exit.

Whether [4] and [5] are feasible, and what tools to use, obviously depend on the operating system, and on security permissions.

This message has been edited. Last edited by: j.gross,
 
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005Report This Post
<FreSte>
posted
Or see below
It stops all requests initiated from the current browser session
(I'm not sure with which release this was introduced, 7.6.xxx).


-Fred-

<html>
<head>
<script>
function killRequest() {
    document.getElementById("iframe2").src = "/ibi_apps/WFServlet?IBIWF_action=STOPREQ&IBIWF_SM_REQUEST_ID=ALL";
}

</script>
</head>

<body style="font-family:verdana; font-size:12px;">



<br><br>
<form id="idForm1" action="/ibi_apps/WFServlet" method="post" name="adhoc" target="iframe1">

<textarea id="idTextArea" cols=40 rows=8 tabindex="1" name="IBIF_adhocfex">
-REPEAT :LB_LOOP FOR &I FROM 1 TO 5;
-TYPE &I
SLEEP 1
-:LB_LOOP
-HTMLFORM BEGIN
Done at !IBI.AMP.TOD;
-HTMLFORM END
</textarea>
  
  <br>
  <button type=submit>Submit (target=left)</button>
  <button onclick="killRequest();">Kill (target=right)</button>
</form>

<iframe name="iframe1" id="iframe1" style="width:500px; height:250px;">
</iframe>
<iframe name="iframe2" id="iframe2" style="width:500px; height:250px;">
</iframe>
</body>
</html>

This message has been edited. Last edited by: <FreSte>,
 
Report This Post
<FreSte>
posted
Found some more info on this one:

Stop browser session
 
Report This Post
Lambo911
Member
posted Hide Post
Hi,

Thank you for your input.

The stop browsers link suggests that that the user does the cancelling..... nice idea but I'm not sure I can rely on them to do that!

The other suggestions might work if they can be transparent to the user. I'll pass it on to the technical team and see what they think.

j.goss and FreSte, have you been able to get your suggestions to work ? I guess its a combination of WF and Java to code it ?


Senior Analyst

WebFOCUS 7.1.11 on Windows
 
Posts: 12 | Registered: January 13, 2010Report This Post
Ramkumar - Webfous
Guru
posted Hide Post
quote:
WFServlet?IBIWF_action=STOPREQ&IBIWF_SM_REQUEST_ID=ALL


This is quite a new Info. Thank you Freste for the link.


Thanks,

Ramkumar.
WebFOCUS/Tableau
Webfocus 8 / 7.7.02
Unix, Windows
HTML/PDF/EXCEL/AHTML/XML/HTML5
 
Posts: 394 | Location: Chennai | Registered: December 02, 2009Report This Post
Alan B
Virtuoso
posted Hide Post
P'raps the window.onunload event handler could be utilised. This should trap even if someone closes the window down.


Alan.
WF 7.705/8.007
 
Posts: 1451 | Location: Portugal | Registered: February 07, 2007Report This Post
Ramkumar - Webfous
Guru
posted Hide Post
yeas Alan.

In case need be, we can show an alert that "Request is being processed. Are you sure to close it...?"


Thanks,

Ramkumar.
WebFOCUS/Tableau
Webfocus 8 / 7.7.02
Unix, Windows
HTML/PDF/EXCEL/AHTML/XML/HTML5
 
Posts: 394 | Location: Chennai | Registered: December 02, 2009Report This Post
ABT
Master
posted Hide Post
Interested in this thread. How about in the Fex's that just use the standard built-in prompting? Basically, Fex only?

Also, what about users who do the "Isn't (click) this (click) thing (click) ever (click) going (click) to (click) finish (click) ?" Where 'click' equals reload/refresh/rerun.

- ABT


------------------------------------
WF Environment:
------------------------------------
Server/Client, ReportCaster, Dev Studio: 7.6.11
Resource Analyzer, Resource Governor, Library, Maintain, InfoAssist
OS: Windows Server 2003
Application/Web Server: Tomcat 5.5.25
Java: JDK 1.6.0_03
Authentication: LDAP, MRREALM Driver
Output: PDF, EXL2K, HTM

------------------------------------
Databases:
------------------------------------
Oracle 10g
DB2 (AS/400)
MSSQL Server 2005
Access/FoxPro
 
Posts: 561 | Registered: February 03, 2010Report This Post
Waz
Expert
posted Hide Post
Very interesting, but seems to be 7.7.

Bugger, I'll have to wait!


Waz...

Prod:WebFOCUS 7.6.10/8.1.04Upgrade:WebFOCUS 8.2.07OS:LinuxOutputs:HTML, PDF, Excel, PPT
In Focus since 1984
Pity the lost knowledge of an old programmer!

 
Posts: 6347 | Location: 33°49'23.0"S, 151°11'41.0"E | Registered: October 31, 2006Report This Post
<FreSte>
posted
Yep, tested it this morning on a 7.6.9 installation, but gave me an error.
 
Report This Post
Ramkumar - Webfous
Guru
posted Hide Post
Same here. Tested in 714 and 769... Getting error.

Have to wait for 7 7.


Thanks,

Ramkumar.
WebFOCUS/Tableau
Webfocus 8 / 7.7.02
Unix, Windows
HTML/PDF/EXCEL/AHTML/XML/HTML5
 
Posts: 394 | Location: Chennai | Registered: December 02, 2009Report This Post
ABT
Master
posted Hide Post
Rats!

quote:
Originally posted by Waz:
Very interesting, but seems to be 7.7.


------------------------------------
WF Environment:
------------------------------------
Server/Client, ReportCaster, Dev Studio: 7.6.11
Resource Analyzer, Resource Governor, Library, Maintain, InfoAssist
OS: Windows Server 2003
Application/Web Server: Tomcat 5.5.25
Java: JDK 1.6.0_03
Authentication: LDAP, MRREALM Driver
Output: PDF, EXL2K, HTM

------------------------------------
Databases:
------------------------------------
Oracle 10g
DB2 (AS/400)
MSSQL Server 2005
Access/FoxPro
 
Posts: 561 | Registered: February 03, 2010Report This Post
jgelona
Master
posted Hide Post
If a request is taking so long that a user is killing the browser session, maybe you should try a different approach. We program our stuff so that the user's browser session is NEVER tied up for more than a few seconds. If a job is going to take longer than that, here is what we do:

1. The request along with any parameters are written into a .foc file
2. The logging program issues a DSTRUN for the report and the report is emailed to the user or
3. A job is scheduled hourly to process the unprocessed requests and the report is emailed to the user.

This way the browser session is never tied up.

One nice thing about this method is that if needed you can have a history of executions.


In FOCUS since 1985. Prod WF 8.0.08 (z90/Suse Linux) DB (Oracle 11g), Self Serv, Report Caster, WebServer Intel/Linux.
 
Posts: 975 | Location: Oklahoma City | Registered: October 27, 2006Report This Post
Ramkumar - Webfous
Guru
posted Hide Post
Hi Jgleona, Nice Idea this is is...

quote:
A job is scheduled hourly to process the unprocessed requests and the report is emailed to the user


Is this done using Report Caster ?


Thanks,

Ramkumar.
WebFOCUS/Tableau
Webfocus 8 / 7.7.02
Unix, Windows
HTML/PDF/EXCEL/AHTML/XML/HTML5
 
Posts: 394 | Location: Chennai | Registered: December 02, 2009Report This Post
GamP
Virtuoso
posted Hide Post
Since DSTRUN is involved, I'd guess it is indeed Report Caster.


GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
 
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007Report This Post
Lambo911
Member
posted Hide Post
Hi,

Some nice ideas thanks, but I don't think from what's been said there is an easy answer ?

The obvious answer is to ensure that reports run in a few seconds then users wouldn't feel the need to bomb out of the session, however as we all know reports can sometimes have a mind of their own !

Thanks for the suggestion Jgleona but users don't want to wait for the report to run....

So going back to killing the server side thread when the user closes their browser, did we determin if this could be done ? I like the idea of a pop up box that asks the user if they really want to close their browser is good. But do we then have a method to kill off the report request ?

Does anyone from IB know ?

Thanks
Richard

This message has been edited. Last edited by: Lambo911,


Senior Analyst

WebFOCUS 7.1.11 on Windows
 
Posts: 12 | Registered: January 13, 2010Report This Post
CLH
Platinum Member
posted Hide Post
Hi,

We use idle_agent_limit to get around this issue. We have it set to 120 seconds. This setting defines the tome that disconnected agents in excess of number ready can stay idle before theay are killed. This is set on the data Service that we use for on-line processing. (In plan installatio this would be the default service)

Crystal


Webfocus 8.0.7 on Windows
 
Posts: 176 | Location: Ohio | Registered: October 26, 2006Report This Post
Lambo911
Member
posted Hide Post
Hi CLH,

But does this work if the agent is active and generating a report that the user won't see as they have closed their browser ?


Senior Analyst

WebFOCUS 7.1.11 on Windows
 
Posts: 12 | Registered: January 13, 2010Report This Post
CLH
Platinum Member
posted Hide Post
It appears to. We tested and with the test cases we came up with it worked.


Webfocus 8.0.7 on Windows
 
Posts: 176 | Location: Ohio | Registered: October 26, 2006Report This Post
Lambo911
Member
posted Hide Post
That's interesting. We will have to give it a try.


Senior Analyst

WebFOCUS 7.1.11 on Windows
 
Posts: 12 | Registered: January 13, 2010Report This Post
Kerry
Expert
posted Hide Post
Hi Richard,

Per our technicals:
According the doc,
idle_agent_limit - Is the amount of time for which disconnected agents in excess of NUMBER_READY can stay idle before they are terminated.

Hope this helps.

Cheers,

Kerry


Kerry Zhan
Focal Point Moderator
Information Builders, Inc.
 
Posts: 1948 | Location: New York | Registered: November 16, 2004Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     When a user bombs out of a report....

Copyright © 1996-2020 Information Builders