This content has been marked as final. Show 6 replies
As OSB is stateless, concept of instance is not applicable.
One of the ways is to use alerts, that you seem to have already tried. And if you use the log action, you should see the statements in the server logs.
Choose an appropriate log level for the different statements and ensure that the weblogic logging level is also set appropriately.
For ex. if the weblogic logging is set to ERROR and you try to have a log action at DEBUG level, you cannot see the logs.
if the weblogi logging is set to DEBUG and if you use log action with levels Debug,Info, Warning, Error - all of them will be visible.
If this is only for your debugging the scenarios, you can also enable tracing (in Operation Settings) on the proxy/business service to capture the complete trace of the execution. But ensure this setting is turned off in PROD environments as this hampers performance.
Hi Arun,1 person found this helpful
The server logs can be found at the following location - MiddlewareHome/user_projects/domains/<your_domain>/AdminServer/servers/<AdminServer or your osb server>/logs
Hope this helps.
Thanks a lot for your suggestion, where we need to find the weblogic logging level in the server? How we can find that this logging level is set in the weblogic? AS i am new to this OSB pls help me in this.
Thanks for your suggestion. I am able to find the logs in the path which u said.
Login to the weblogic console of your domain (http://local host:port/console)1 person found this helpful
Then browse to Home >Servers > server name > Logging tab.
You will find the necessary configurations there.
Always refer to documentation, you will find most of the details there. Refer http://docs.oracle.com/cd/E11035_01/wls100/logging/config_logs.html#wp1012001 fore details.
Thanks Partick, the document is useful.