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 even took out the "/" in the front thinking it might be that, but it still doesn't work. Ugh...
Migrating Reporting Server stuff from 7.x to 8.x is not as streamlined as it should be... There should be a utility for Reporting Server content as well as Managed Reporting, ReportCaster, etc. content.
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015
That seemed to work. So by web server files you (more or less) mean any file extension that is/can be web related right? Because the /approot/ reference format has worked thus far for a .js file. So, if the file type is say .htm or .css we would use the /approot/ type of reference?
Thanks for your help and patience as I learn this stuff.
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015
The web server serves files associated with web pages - these could be html, js, css or images.
The reporting server deals with files related to WF, fex, html, sty...
in a multi-tier environment the main folders referenced by these two servers will most likely be two physically different folders one on the web server and one on the reporting server. On the reporting server the folder is usually Dive:\ibi\apps. On the web server it could be anywhere, with a web server alias called approot referencing the folder.
In a single-tier environment, the folders could be the same physical folder, with the reporting server and web server configured appropriately (the web server still needs an alias for approot).
In either situation, your code has to reference the files correctly - using approot for web server related files and -INCLUDE app-folder-name/blah_blah.fex or -HTMLFORM app-folder-name/bling_bling.htm
All this is in layman's terms - someone smarter than me can correct my terminology...
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
Your explanation was great. It was somewhat frustrating when that wasn't understood and I was trying to use /approot/... for IBFS:/... references, etc.
Important stuff to know!
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015
The distinction in paths is between referencing files on the file system (for -INCLUDE etc) and referencing web resources on your web-server.
For javascript, css and html files you need /approot, because your web-browser needs to locate those files on the web-server. The WebFOCUS server/client don't touch those files, that's (slightly simplified) the web-server's job.
On the other hand, fex files, focus databases, etc. are accessed by the WebFOCUS server/client, not by your web-browser, so those have to be physical paths on the file-system. Those paths be relative to the working directory of the WebFOCUS (server) application, or just somewhere in its search path (APP PATH).
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :
Thanks for your added insights. So, despite the htm, css, js, gif, etc. files being in an app folder on the Data Servers side with the other .fex,.mas,.acx,.foc, etc. files already there, they still must be called using the /approot/... referencing instead of the IBFS:/EDA/EDASERVE/baseapp/fileName.htm way of doing it? Because when I used a reference to an image that was on the Content side like...
So when having to reference a web type file under the Data Servers side, it needs /approot/... but if it's a .fex, .foc, .mas, etc. it needs the IBFS:/... way of reference. Am I getting that right?
Thanks!
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015