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 am not sure if this is a PMF issue or an operational report problem, but the customer is seeing 404 errors on their reporting server (7.6.4 WF and 4.1 PMF). A case has been opened on Tech Support. Does anyone have any suggestions?
Thanks!
WF 8.09
Posts: 68 | Location: United States | Registered: March 28, 2007
Bob, your suggestion to check the pmfdata folder and the a_hostname.fex was an excellent one. That is where the issue resided. Thanks again for coming through!
Janice
WF 8.09
Posts: 68 | Location: United States | Registered: March 28, 2007
For all those who do not know, a_hostname.fex in the pmfdata folder is a PMF/PMM configuration file, written out with the correct web server name by the PMF/PMM installer.
If the file is applied without the installer, it contains the web server "kaplan" as the host, which is of course going to cause problems when someone wants to run an operational report, since that's the http server PMF/PMM will assume for operational reports; plus PMF/PMF's AJAX code also uses that defined web server to make its queries - and PMF has a ton of AJAX code in it.
But since PMF/PMM is a WebFOCUS application, the temptation is very strong to copy app components in manually. We've actually encouraged that in the past, especially when patching issues, but we're now starting to have a change of heart. Starting with V5 we recommend all users run the installer to apply service packs - it will ensure a much higher factor of safety.
Bob Jude Ferrante Director of Business and Development WebFOCUS Performance Management Bob_Ferrante@ibi.com 917-339-5105
I'll take any questions about PMF - business or technical - anytime!
We modified the a_hostname.fex as instructed, but the 404 errors persist at about the rate of the number of visits to PMF (actually a few more). Once again, the users are not seeing the errors, but we wonder if it is impacting performance in some way. Thanks for your help.
Following up on this, we found that our administrator and author tabs had some old code in them that was asking for this page. Although it does not affect Web server performance or application performance, we have removed the code from the newest version of PMF and it will be removed, moving onward. You can also modify the files:
adnavbar.htm aunavbar.htm pmm_adnavbar.htm
and remove the quotes and the string "syscolum.xsl"
it's a safe change; we tested it here and it checks out.
all best
Bob Jude Ferrante Director of Business and Development WebFOCUS Performance Management Bob_Ferrante@ibi.com 917-339-5105
I'll take any questions about PMF - business or technical - anytime!