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'm experiencing the same problem, previously it worked fine in the environment. Setting up two environments might have caused things to change in the configuration and not working anymore...
Any suggestions where to look?
Unfortunately, the link above does not work anymore for the newsletter (can't find it anymore either).This message has been edited. Last edited by: SWES,
WebFOCUS 8105m Windows 7, All Outputs
Member of the Benelux Usergroup
Posts: 198 | Location: Amsterdam | Registered: August 24, 2011
This is what I was looking for... I just fixed the issue.
Thanks again, SWES
ps. would you, by any chance, be able to tell me if I could place this SET statement somewhere central in the environment, so I don't have to repeat it for each individual procedure?
WebFOCUS 8105m Windows 7, All Outputs
Member of the Benelux Usergroup
Posts: 198 | Location: Amsterdam | Registered: August 24, 2011
i have two procedures in my baseapp SETBATCH.fex and SETBATCH_BACKEND.fex i use them as pre-processing conditions in a caster job (as Tony suggests), and find that i need two depending upon where the drill-to fex is located, mre or backend. if backend, then this works
SET FOCEXURL = h t t p://&&server|.nyumc.org:80/ibi_apps/WFServlet?
if mre then this works
SET FOCEXURL = h t t p://&&server|.nyumc.org:80/ibi_apps/WFServlet?IBIF_webapp=/ibi_apps
i'm in 7706/winserv2008r2. i agree w/ Tony that its best to leave it off the edasprof and put it only exactly where you need it.
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003