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.
Currently, we only use the JSCOM3 service on our WFRS for generating XLSX reports. TO make that work with some of our XLST/XLSM templates, we had to increase the available memory to that service to 1GB. As long as we have only a single JSCOM3 service running, that's okay. A couple would probably still be okay, but as soon as were entering higher counts that is probably not going to fly well.
We are looking into adding a PostgreSQL adapter for our local datawarehouse, and it seems that it also uses JSCOM3, probably because it's using a JDBC connection to the database. Or is there a properly native adapter using libpq? that would have our preference...
Now we don't really need to allocate 1GB of Java memory for each connection to our datawarehouse and we would probably want to ramp up the number of available JSCOM3 agents to more than a single one when we go that route. And we want to go that route, it is a great database at hard to beat costs; we could spend most of the money otherwise wasted on licensing costs on hardware instead. If someone can confirm that the PG adapter does not depend on JSCOM3, that would solve this problem right away!
But if things are as we think they are, then I am wondering whether we can create another group of JSCOM3 agents besides the one named 'DEFAULT', much like we do with tscom3 agents. Is that possible? Where can we configure that?
To add a bit more to the challenge: Because of a memory leak in the XLSX unzip/zip JSCOM3 service, we have a script scheduled in the Windows Scheduler that checks every 5 minutes whether the available memory of the jscom3 process has fallen under 900MB and it kills it when that is the case (it restarts automatically when killed). It's far from an ideal solution, but at least this way our XLSX reports don't stop working for longer than 5 minutes...
Obviously, that hack is going to be a problem if we also have other jscom3 processes that are supposed to use under 900MB of memory. I don't think there is any way from the OS side to distinguish one from another, except maybe for its memory "Commit Size".This message has been edited. Last edited by: FP Mod Chuck,
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :