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.
RaghunathR, This type of problem you're probably best to open up a case with Techsupport if you haven't already, even if you also post your problem here.
Most of the time I've seen that problem its been because the HTTP Headers sent exceed the maximum allowed for a CGI application. The easiest way to reduce this size is to delete the "extra" information that is sent as part of the user-agent string in the registry.
If this is not possible since you can't control the end-user machines where this problem is occurring, I recommend you move away from CGI and over to calling WebFOCUS via a Servlet.
Typically this is as easy as sending requests to: /ibi_apps/WFServlet
Instead of the cgi URL.
This is a bigger change to implement, but long run everything in WebFOCUS is Servlet based and has been moving away from CGI for quite some time.