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.
I have a FEX which takes in some parameters and then populates a DIALOGUE MANAGER AMPER variable with the FEX or HTML to invoke using EX or -HTMLFORM using the AMPER variable on a line by itself.
On the surface this would seem to be OK, if not for the changes to the way WebFOCUS parses your FEX before it runs it from pre-version 8 versions. WebFOCUS will throw an error on the
&MENU_OPT.EVAL
statement that the FEX or HTML file is not found.
To get around this problem and make WebFOCUS happy, you can put references to the FEX or HTM files somewhere in your FEX, even if you don't ever execute that code, like this:
This works, because WebFOCUS has pre-checked the existence of the file before it was referenced by the
&MENU_OPT.EVAL
line of code.
If there's only a few FEXes or HTM files to dynamically call using this method, it's no big deal, but when you start adding more, say 10 or 20, WebFOCUS can take a bit of time to pre-to check the existence of all the files, causing the page or report to take more time to load or display results.
Does anyone know if WebFOCUS allows you to switch off the file pre-check process before a FEX runs, or is that not possible at this time?
I have tried other techniques from other posts like using
-MRNOEDIT
, but still end up putting the references to the FEX and HTM files in as shown above to get it to work.This message has been edited. Last edited by: Dennis_V,
Local: AppStudio 8.2.03 - Win7 - Tomcat Server: WebFOCUS 8.2.03 - Windows 2008 R2 Enterprise on VMWare 2 CPU, 3.2GHz, 4GB of RAM Output Formats: HTML, Excel, PDF, PPT, Active Reports
Posts: 38 | Location: Denver, CO | Registered: March 16, 2005
If you are unaware, the WebFOCUS web client needs to parse the files in the repository to work out which ones will need to be "shipped" to the reporting server for execution.
We currently have an issue with the lead time where we can have 3 to 6 seconds before the execution starts.
Its quite annoying, and we know that there are issues (tested on 8.1.04) with multiple includes of the same code, all are sent separately. (We use common code and utilities)
We have a case open with IBI about this, no resolution yet.
although we use for different purposes. This might work.
TABLE FILE <some dummy>
PRINT COMPUTE CODELINE/A500 = &MENU_OPT;
BY dummyfield NOPRINT
WHERE RECORDLIMIT EQ 1
ON TABLE SAVE AS foccache/TEMPCODE
END
-RUN
-MRNODEDIT -INCLUDE foccache/TEMPCODE.ftm
...you might need to add some extra quotes in &MENU_OPT
It does the same thing but in a different way. Might be better performance.
I'm curious.
Greets, Dave
_____________________ WF: 8.0.0.9 > going 8.2.0.5
Posts: 668 | Location: Veghel, The Netherlands | Registered: February 16, 2010