Unlike SOA composite instances, given that console-based troubleshooting of OSB is relatively weak, reliance on the log files becomes much more important in the case of troubleshooting OSB transactions. Here, message tracing and logging are features that can be enabled and disabled to provide more runtime insight into the OSB instances. For issues that are reproducible, these settings can simply be enabled and the transaction can be rerun to capture more relevant information in order to assist in the troubleshooting process. In cases that are not reproducible, if these settings were not enabled beforehand, you may have little information to fall back on to assist in troubleshooting. Thus, the challenge is finding an acceptable medium.

Chapter 6, Monitoring Oracle SOA Suite 12c, included a section titled Monitoring OSB instances that described in detail how to take advantage of multiple operational settings to increase different types of logging. They provide...