 |
|||||
|
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
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. | |||||
Focal Point 
Focal Point Forums WebFOCUS/FOCUS Forum on Focal Point [SOLVED] Distributed Configuration vs. Standalone
Focal Point Forums WebFOCUS/FOCUS Forum on Focal Point [SOLVED] Distributed Configuration vs. Standalone Read-Only TopicGo | Search | Notify | Tools |
| [SOLVED] Distributed Configuration vs. Standalone | Login/Join |
| Silver Member |
Hello and thank you for stopping by to read my post. I am wondering which WebFOCUS installation scenario would perform better, distributed configuration or standalone. I do have a SQL server that is separate from the application server, but it is under a heavy load sometimes. I looked through documentation, tech support, and this forum, but I can't really find anything that will tell me which configuration is best. I imagine that it depends on the computer hardware, network speed, and load for each of the machines. However, is there a recommended configuration? Does having the Reporting Server on the same machine as the DB generally perform better than having both the Reporting Server and Client on the same machine that accesses a remote database?This message has been edited. Last edited by: DivisionByZero, Local Development Environment: WF 7.6.10 on Vista Ultimate 64-bit Edition Client Environments: WF 7.1.3, 7.6.4, and 7.6.10 on various Windows Server platforms using servlet implementation over SSL Oracle and MSSQL DBs Output formats: HTML, PDF, Excel 2000, XML | ||
|
| Expert |
I think you may have to talk to IBI for recommended config. Usually install with the data is better, but that relies on so many things. Waz...
| |||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||
| Expert |
We have lots of relational adapters and the reporting server is separate from from all of them. Depending on your shop, it is highly unlikely that you will get a DBA to allow you to put a reporting server on their data base platform. With that said, what you should strive for is sending the most efficient generated SQL you can to the backend data base engine, thereby minimizing the number of rows returned to WF and reducing network traffic. Ginny --------------------------------- Prod: WF 7.7.01 Dev: WF 7.6.9-11 Admin, MRE,self-service; adapters: Teradata, DB2, Oracle, SQL Server, Essbase, ESRI, FlexEnable, Google | |||
|
| Member |
I agree with the previous posts - it depends on the horsepower available on all platforms. You really need to work with your IBI systems people on this. We have a distributed configuration with Web client, reporting server, and data on 3 different machines. Works well most of the time. However, our data warehouse is in DB2, which we access through the zOS side of the mainframe. WebFOCUS is negatively impacted when the mainframe is under a heavy load from our operational/production systems. Likewise, heavy DB2 use by WebFOCUS can impact the operational/production system. It takes a lot of tuning effort to get everything working well. WF 7.7.01 Reporting Server on zLinux or Windows Client on linux Output formats - EXL2K, HTML, PDF | |||
|
| Silver Member |
Thanks everyone for your advice. We have decided to use the standalone configuration since the DBAs do prefer to leave the data server alone. Local Development Environment: WF 7.6.10 on Vista Ultimate 64-bit Edition Client Environments: WF 7.1.3, 7.6.4, and 7.6.10 on various Windows Server platforms using servlet implementation over SSL Oracle and MSSQL DBs Output formats: HTML, PDF, Excel 2000, XML | |||
|
| Expert |
You just need to make sure that the comms between the reporting server and the DB server are fat and fast. Waz...
| |||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||
| Guru |
For optimal performance, putting Reporting Server close to the Database Server should be considered. This will reduce network issues. You can partition server to keep Reporting Server seperate from Database Server. Sayed WF 8.x and 7.7.x Win/UNIX/AS400, MRE/Portal/Self-Service, IIS/Tomcat, WebSphere, IWA, Realmdriver, Active Directory, Oracle, SQLServer, DB2, MySQL, JD Edwards, E-BIZ, SAP BW, R/3, ECC, ESSBASE | |||
|
| Powered by Social Strata |
 | Please Wait. Your request is being processed... |
Read-Only TopicFocal Point Focal Point Forums WebFOCUS/FOCUS Forum on Focal Point [SOLVED] Distributed Configuration vs. Standalone
Focal Point Forums WebFOCUS/FOCUS Forum on Focal Point [SOLVED] Distributed Configuration vs. StandaloneCopyright © 1996-2020 Information Builders
| View $GS_USERNAME's Public Profile |
| Add $GS_USERNAME to my Ignore List |
| View Recent Posts by $GS_USERNAME |
| Notify me of New Posts by $GS_USERNAME |