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.
by the by, you've hit on precisely why you have to put in this command SET FOCEXURL = http://servername/cgi-bin/ibi_cgi/webapi.dll when executing a fex with drilldowns that you are going to email out in Outlook. Otherwise, your drilldown, which starts right with that cgi bit, has no clue where to find this focus engine.This message has been edited. Last edited by: susannah,
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
I have tried both of your solutions and still receive "The page cannot be found" Could the problem be related to trying to call the .fex from a seperate webserver?
There are a few special parameters that you should pass in a fex call and they differ from MRE and Self Serve. Search on the instance of "IBIMR_domain" to find a recent posting with the MRE ones in. As for the self serve, you ought to get used to including the "IBIAPP_app" even though it is not always required if the fex you are intending to run resides in the APP PATH.
One big thing to ensure is that the "svr99wfrs" is a known DNS alias or is available.
T
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004
good point, where is the engine you're expecting to run? on svr99wfrs? and is the fex on that server's edapath or apppath (whichever you use)? or, are you expecting to run the fex using the engine on your host server and just grabbing the fex from your 99wfrs? and i for one still have no clue what a 4-tier env means? would you teach us?
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
By Default WebFOCUS 7.x uses the WebFOCUS Servlet. Try making your call using it. If the default web application context is not ibi_apps then you will have to change it to what it should be.
href="http://svr99wfrs/ibi_apps/WFServlet?"
just try calling the servlet with out any parameters to see if there is a response.
1)There is a DNS Arecord for the svr99wfrs server... as it responds from ping.
2) I checked, and the app I was trying to call was in the app path. Good point to check that, thanks!
3) href="http://svr99wfrs/ibi_apps/WFServlet?" I did this and got a "page cannot be found"
What I call a 4-tier architecture is a database server (Ibm as400), a webfocus reporting server (svr99wfrs is what we call it) running win server 2003, a seperate web server running IIS/ tomcat on win server 2003 (called svr99rvi in our shop), and the user's web browser being the fourth tier.
So, realizing that I should be referencing the web server and not the reporting server, I tried these links.