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.
According to advanced search this scotches all tracing.
SET TRACEOFF=ALL SET TRACEOFF=EDAAPI SET TRACEOFF=ODIN
The default in SRV76\WFS\CATALOG\WFTRACE.FEX seems to be
SET TRACEON=DEFAULT
which produces quite an amount of trace output in EDATEMP.
Anyone had any problems with switching all traces off since it does seem to improve performance. We are trying in the TEST server but dont want to risk production just yet.
nb You need to reboot server to see the trace settings change.
Check your TRACE setting with SET TRACEON=?
Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2 Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006
We have the default that you show but it is in ibitrace.fex. The only traces we get in edatemp with that are the Workspace Manager and Listeners default traces. We get traces in Data Services if developers leave trace commands in their programs that check out their SQL. If you can control that, I'm not sure I would turn them off completely. We just go in and delete the DS traces now and then.