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 am trying to figure out a way to limit the number of simultaneous connections to a specific data source. Does anyone know if this is possible? For example, say that it is OK for hundreds of reports to run against Tables X and Y but Table Z can only have 5 at any one time.
Currently I am creating a record every time someone runs against table Z. Before the report runs, the number of records is checked and if it is greater than 5 then the user gets a message to try again later. The record is deleted when a running report finishes.
But I want the user to be able to run the report, either immediately or as deferred, and for WebFocus to not move it in to the run queue unless there is a free slot in the available 5. That way the user does not have to resubmit the report.
Can this be done? Off the top of my head I can think that one way would be to trap all of the user's params and then have some kind of cron job that runs every 5 minutes and checks for a free space in the queue. But is there an easier way?
Jodye, I don't think so. You could write all the user parms into a file. Have the cron job to retrieve all the parms and then delete the request info after the report. You could make this into a generic tool, with the name of the data source and the number of allowable users for each data source. As id for the user's request you could use the PID (since you're talking about cron I take it you're on some kind of unix box).
Best of luck H�kan
Posts: 319 | Location: Stockholm, Sweden | Registered: February 04, 2004