How to debug an IM tag call in OOB Infocenter or Custom JSP code
(Doc ID 1526501.1)
Last updated on JULY 18, 2017
Applies to:Oracle Knowledge - Version 18.104.22.168 and later
Information in this document applies to any platform.
There are several steps for debugging and figuring out why a given tag call is not returning as you would expect.
Before you start it can be helpful to have your weblogic server in development mode where the changes to the jsps are picked up automatically by the server. In Tomcat changes are picked up automatically.
How to Achieve Auto Compile of Updated JSPs in WebLogic Server (Doc ID 1358621.1)
Converting a Weblogic Server domain from Production Mode to Development Mode (Doc ID 1124118.1)
How Can Weblogic Server Be Changed From Production Mode Back To Development Mode? (Doc ID 1134809.1)
1 - First find the right JSP where the tag is executed and the data is displayed.
2 - Print the variables used in the call to the log or the screen.
3 - Identify which articles/objects should be returning for the call and what their matching attributes are.
4 - If a tag is not working as expected please open an SR with Oracle support.
5 - Test changes against an OOB unmodified version of InfoCenter.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|1 - First find the right JSP where the tag is executed and the data is displayed.|
|2 - Understand the Tag calls and Parameters being used.|
|3 - Print the variables used in the call to the log or the screen.|
|4 - Identify which articles/objects should be returning for the call and what their matching attributes are.|
|5 - If a tag is not working as expected please open an SR with Oracle support.|
|6 - Test changes against an OOB unmodified version of InfoCenter.|
|7 - Activating Changes in Weblogic|