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.
So, our programs run on a server that is located in the IT building. If I run a program that is taking forever, I have heard that we cannot stop it or cancel it ourselves. We have to call IT and get them to stop it. Does anybody know a way around this? Thanks!
You will need to have admin access to the reporting server console where you would access WorkSpace / Monitor / Agents. After identifying the correct agent process, left click to access a context menu and then choose Kill Agent. The agent will be closed in a "controlled" manner waiting for rollbacks etc.
If you don't have this access to the server console then it's a call to your IT group
T
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004
All, Yes you can stop a fex on the Reporting Server. However, The Request may still be running inside the Database Server. At that point you will have to have a Database Administrator or someone with that provilage to kill the request in the database.
We have 7.1.4 and even a hard kill is not stopping on DB2. One of the side effects of killing a query that talks to a DBMS is that it could affect the entire server if the corresponding DBMS thread is not killed.
WF7.1.4 Prod/Test, MRE, self serve, DM
Posts: 176 | Location: Desplaines | Registered: August 05, 2004
Read-Only Topic
