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 currently running into this problem and I'm trying to figure out why its not working.
Anytime in Graphs, I can't set GRAPHEDIT = SERVER or else I get an Odin (This should not happen) error.
Anyone else have this problem?
I'm trying to get the Tool tip to display like they did in the 5.2 Graph Engine. I can't seem to have them pop up on the data points. Even when I set the tool tip to developer, I get a tool tip popup on every item on the graph except for the data points! They claim it works with GraphEdit = SERVER so I guess I'm working towards getting that next.
If you are using 5.3, there are various new CGI parameters that affects graphing.
You could try for instance add the following line to the beginning of your GRAPH report -TYPE WEBFOCUS CGIVAR WF_BURST_OUTPUT=OFF The WF_BURST_OUTPUT set to ON (default setting), caused some of the graphs not being display at all (but only some of them). There can be other parameters that affects graphing in your case. You can open the web console: http://.../ibi_html/wfconsole.htm, browse through the parameters trying to guess if they can affect your graph, and change their values just for the particular report with -TYPE WEBFOCUS CGIVAR. You can also open the case - IBI support were very responsive and fast solving the WF_BURST_OUTPUT problem .
I just went through this on our unix box. Here's what I added to site.wfs:
#--------------------------------- This block of code copied from cgivars.wfs <!WFConsole begin Graph> ENABLE_SSG =YES DISPLAY =localhost:0 IBIF_graphengine =GRAPH53 IBIF_graphservurl = &URL_PROTOCOL://&SERVER_NAME:&SERVER_PORT&IBIF_webapp/IBIGraphServlet IBIF_graphHeadLess=YES IBIF_graphAgents =10 SSG_EXTERNAL =YES <!WFConsole end Graph>
#--------------------------------- These commands from WF Install pp. 6-9 thru 6-14 IBIJAVADIR = /usr/java/jre IBIJAVACMD = /bin/java -Djava.awt.headless=true
We use site.wfs instead of cgivars.wfs because we can always get back to what the default values were when the product was installed. site.wfs is consulted right after cgivars.wfs, and anything we are over-riding from the defaults, we put into site.wfs.
I got the values for IBIJAVADIR and IBIJAVACMD from the sysadmin on our Sun unix box.
I believe this "Java-only" solution works only with the GRAPH53 engine. I had tried last summer to get SSG working with X Windows, but was never successful.
There may be more items than necessary in the block of code copied from cgivars.wfs (DISPLAY=localhost:0 might refer only to X Windows), but we've been successful for about a week now, so I'm not going to be picky!
Actually, I have a case in with IBI. We can direct graph output to the screen and to a printer, but haven't yet successfully directed it to a file.
HTH. Suzy
Posts: 124 | Location: Lebanon, New Hampshire | Registered: April 24, 2003
I'm running it on a Windows XP machine... since when reading a couple things the JSCOM3 seems to be affected on a windows machine. I'll try it on the Windows NT machine... but I'm pretty sure to get the same results.