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.
What we are trying to do is create an &-parameter that we can reference in HTML output that will show a the location of a .fex within the Content tree.
For example:
Say Procedure1.fex is saved in the content tree in Folder_1/Subfolder_A, so we would create a parameter &LOCATION_PARAMETER that reads "Folder_1/Subfolder_A/Procedure1.fex".
I searched through the documentation and in the forum, but I wasn't finding anything close. Does anyone know if this is possible?This message has been edited. Last edited by: barcher,
I see what you mean. For our purposes we wouldn't be concerned with every FEX with that name. Instead we only care about the location in the repository of the current running fex. Our aim is to create a -TYPE (or something similar) with &LOCATION_PARAMETER so that when we troubleshoot a fex we can more easily determine the location in the repository, instead of tracking down the person who created it.
I did find a parameter in our environment, &IBIMR_fullpath, that appears to be the parameter I am looking for. I'm not entirely sure how this is defined, so I can't say if fex's with the same name are still a problem.
A more clear example:
&LOCATION_PARAMETER would not be visible by the user, but by viewing source you would see the -TYPE and the commented code. So the user would only see the report, but when viewing source we would be able to see the value of &LOCATION_PARAMETER.
-* prints the location in the repository of
-* the FEX.
-TYPE Location of this FEX: &LOCATION_PARAMETER
TABLE FILE CAR
PRINT
MAKE
BY COUNTRY
ON TABLE PCHOLD FORMAT HTML
END
I didn't quite understand your original question, but yes, &IBIMR_fullpath is the correct parameter to use - you should never have a duplicate &IBIMR_fullpath (not that it matters).This message has been edited. Last edited by: Francis Mariani,
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
I also found &IBIMR_domain (showing the domain name) and &IBIMR_folder (showing the folder name containing the fex), which may help because there appears to be a limit on the string length for IBIMR_fullpath.