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.
There is nothing in the webfocus product that can provide this for you, you'll have to come up with a way to do this yourself. Easiest way is to select the text in the window and copy it to the clipboard or do a 'View Source' which will bring it into an editor. A much harder way is to activate server traces, have them written to a file in a location that can be written to and read from, and then write some code that will filter out from the traces what you need. There are a few threads in this forum where this technique is discussed. But before you go and do this ask yourself the question if this is really neccessary. If it is just for analyzing what goes wrong, I'd do a view source, and then I have the code in a text editor, to be disposed of as I see fit.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007