Syed,
I think you should go with ‘Service auditing’ keeping the following in mind…
-
Overall performance - yes, there will be an impact, but even if you write a custom logic, you would want to capture service start, end, logging fields etc.,
-
Service log - You can avoid database & choose flat file to capture service log. Even if you go with custom logic, you would want to capture these info into file system, which does IO operations over network.
-
You could enable auditing only for the top-level service, which will avoid doing this for all the other services.
-
You can’t anyway save the pipeline info into flat file
-
You can log selected fields from your service signature.
-
Custom value for auditing context, which is useful while searching for specific transactions through WmMonitor page.
If you write to custom log file, it just not stops there. You would have to think of archiving the log files, think of how to search for specific transaction, build a UI, search functionality (if not CAF UI, this would be manual which support team have to handle, knowledge transfer, maintenance, risk of not using public services etc.,
When something is already available, and choose options carefully, you don’t have to reinvent the whole wheel again.
HTH
Senthil
#Integration-Server-and-ESB#Flow-and-Java-services#webMethods