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 email@example.com for further assistance. Reference the community FAQ to learn more about the community.
Hi All, Can some one advice on this issue. In my webfocus admin console I am trying to open the MR adminstration tab but it throws 500 error.
Webfocus admin console-->Diagnostics-->Traces-->MR Administration. This shows 500 Error. I suspected the ear was corrupted and hence I took the ear from other enivronment and placed here so the issue was resolved but created other errors so I had reverted back.
Can some one advice.
Thank youThis message has been edited. Last edited by: Kerry,
Francis, An EAR is an Enterprise ARchive format. Its used in WebSphere to deploy a collection of WAR files as a single unit (e.g. One might deploy ibi_apps, ibi_html, approot, and rcaster as one webfocus.ear file)
Rocky, Typically when I've seen HTTP 500 errors on accessing a trace area its either one of two things:
1) Traces were left on for a long time and you now have thousands of traces within your WebFOCUS76\logs directory. The list of these trace files is taking so long to compile it times out and gives the HTTP 500.
2) You have a log4j Jar file in your WebSphere bootstrap. This is causing the first log4j.xml definition file found to be used for all the WebFOCUS web applications. Since typically ibi_html or approot loads in an EAR before ibi_apps this means that all of the log4j definitions required for our tracing facilities to run are not defined and as a result they're not found when you access the log pages. This kicks off the HTTP 500.
In either case above, or some other cause not listed, more details as to why the HTTP 500 is being triggered should be found within your WebSphere logs.
Hi All, I have contacted IBI and they are unable to resolve the issue, since an year. 1)One more reason for raising this concern and concluding that the ear is corrupted is the Websphere application logs is not showing the information.Genarally in Prod they are working fine but in INT and STG. they dont work. 2)Multiple recycles of webfocus webserver,app server,RC is done. 3) IBI recomended the change of class loading policy and redeply the ear file. I am in process of the same....Keep you posted 4)@ dlogon....Please advice if you want me to verify the Log4j of STG and PROD. might get a clue.