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.
We have a functionality of scheduling a report on different frequency basis like daily, weekly , monthly etc. We use ReportCaster for scheduling purpose. We now face an entitlement issue.
Issue : A User with userid "ABC" is entitled for a report "XYZ" is scheduling that report to run for 5 days from Jul 1st to Jul 5th. Reportcaster will start creating the report from Jul 1st. Say on Jul 2nd his entitlement to that report is revoked, in such case from Jul 2nd onwards the report should not get generated. But as ReportCaster is not aware of it, the report gets generated now. So pre-processing has to be done before every instance of generation of the report.
we have an API in our own java application using which we can check the entitlement of that user. This API takes the user id as the input and returns as true or false. Kindly let me know how can we call that Java API from the preprocessing fex.
Understand that operating system commands is a security risk for any installation allowing the default adhoc fex facilty to remain exposed (https://server/ibi_html/homepage/adhoc.htm or linked from https://server/ibi_apps/homepage.jsp). It is also problematic from MRE users who have advanced analytical setting, as they can edit source.
The risk: basically, anyone with adhoc fex capability can poke around in the operating system, delete fexes authored by others, fill up the disk, zip up your application directories and expose them for download using FILEDEF, and a whole lot more painful stuff like that.
So be very careful about who all can run WF code on your installation when you allow OS CMDS to be available.
Regards,
-- Dan
University of Nebraska at Omaha WF 7.1.6 Linux -- Test: WF 7.6.1 Linux
That's a great point Dan! Thanks for filling in that hole.
Also, the ability to execute operating system commands from within focexecs can be disabled by using the following statement in a profile (edasprof.prf, user.prf, a service profile, etc.):
SET OPSYSCMD=OFF
Posts: 22 | Location: Atlanta | Registered: January 19, 2007