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 recently migrated from WebFOCUS 7.1.4 to WebFOCUS 7.6.12. One of our application which uses Java Front end to schedule reports is having hard time coping with this upgrade.
It can schedule the report fine, but when I try to retrieve the job to download it, it gets a nullpointer exception. Its using function getLastLogByScheduleId to get the log info. Now with limited debugging skills I have I've debugged the Java code and found out that scheduleId being passed in getLastLogByScheduleId function is same as one displayed in ReportCaster Admin Home, but when I goto reportcaster console and see status of job which is running and which completes, it has different schedule ID. Also If I try to see log for the job in ReportCaster Home, it says to me no log generated, while I can see the log of job in reportcaster console.
I have my WF714 servers still running, and I can see this scheduleID was same everywhere in it. So I guess, this is the real problem breaking the code i.e. the difference of scheduleID of actual job (in RC console) and one being reported in Admin Homepage. Any one has any idea what might be causing this?
Regards,
Developer Studio 7.6.11 Windows Output Format: HTML, Excel, PDF
After lot of Research I found that if you trigger a schedule explicitly using manager.run(), when schedule is run its schedule ID is different from what was being generated. However, process ID returned by manager.run is constant and can be used to fetch the log instead of schedule ID. So modified the code accordingly.
Hope it helps anyone who may get stuck with the same problem..
Cheers
Developer Studio 7.6.11 Windows Output Format: HTML, Excel, PDF