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 just received an email from Information Builders entitled "ReportCaster and WebFOCUS Web Application combined into one Web Application in Release 7.7"
Here's a quote:
quote:
In WebFOCUS Release 7.7 the WebFOCUS and ReportCaster web applications have been combined into one web application. In prior releases the two applications were deployed separately with unique context roots whose default values were 'ibi_apps' and 'rcaster'. In WebFOCUS 7.7 there is only one context root for WebFOCUS and ReportCaster with a default value of 'ibi_apps'.
Does this mean ReportCaster will finally behave the same as the WebFOCUS server when running fexes?
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
I don't think that's the case, Francis. Based on what I read, they will move the Report Caster client application from the specific rcaster context to the more generic ibi_apps in the Application Server. So in essence, I think all of the .htm .jsp, .jar and other files that make part of the Report Caster client installation will now happily live among their WebFOCUS Client peers. This should not have any impact on how Report Caster actually behaves; it's just a new "path" to its different GUI components.
I did not see any mention to changes on the Report Caster Distribution Server, but I'll better re-check just in case I missed something.
Does this mean ReportCaster will finally behave the same as the WebFOCUS server when running fexes?
We could hope, but that might be asking a little too much. My understanding of the change is what nsjden noted.
It WOULD be nice to have them both behave in a more similar fashion. My estimate is that about 20% of the time, an "advanced" procedure will have a problem in Caster that is not exhibited in WF, and needs extra measures to ensure successful processing. Maybe we're just trying to get too much out of RC, but we sure do a lot with it. (I also do most of my work in the code as opposed to the GUI, with a lot of DM - I guess that's what I would call an advanced procedure.)
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007
• ReportCaster will require RDBMS for RC repository (jobs, schedules, etc.) - FOCUS DB no longer an option. • MR respository will move from basedir folder to DBMS.
WebFOCUS 7.7.05
Posts: 1213 | Location: Seattle, Washington - USA | Registered: October 22, 2007
I checked the communication again and definitely the impact is only on the Application Server components. The Distribution Server and the way it interacts with the Reporting Server will technically remain the same (unless there are new features/patches implemented in that version of course).
I think the change is positive. This actually simplifies a bit not only the App Server configuration but also the AJP connection between IIS and a Java-based App Server (for those who have such an environment).
quote:
It WOULD be nice to have them both behave in a more similar fashion
quote:
We could hope
Well Darin, you just said it all
quote:
MR respository will move from basedir folder to DBMS.
Wow, I had no idea about this one Dan! I'm certainly all for databases but wouldn't this change make too much of an impact on existing environments? I don't know, I sometimes like the dirty approach to opening (and CAREFULLY modifying) the mydomain.htm ... I know it's risky but it's just too convenient, especially when you need to access a database from "anywhere" and there's no database client software available.
Maybe it's just me but I really love being able to "function" with just a good text editor at hand!