However, when there are many such scenarios (for example, Technosoft develops and supports hundreds of complex integration scenarios), a problem arises how effectively monitors scenarios used java-proxy. When you use couple of integration scenarios, this is not a significant problem. Using that Log Viewer developer trace approach has its own downsides such as if your java-proxy works under relatively high load finding log entries for certain message could be challenging because Log Viewer search tool listing capabilities are limited with page scroll option.īesides, message monitoring becoming separated on two stages: first you have to check audit log in Message Monitor, and then or even at the same time – try to find (your java-proxy made) records for that message in Log Viewer.
Those allow you to log events which you can see in Log Viewer(view / developer trace, fig.1).įig.1 Example of developer trace logs Log Viewer. Usually methods of .logging.Location class can be used for that purpose. When developing custom java-proxy often enough there is a situation when you want to log actions/steps during java-proxy work.