Monitoring SOAP Messages
(Doc ID 1494441.1)
Last updated on AUGUST 25, 2021
Applies to:
JPublisher - Version 11.1.0.7 to 12.1.0.2.0 [Release 11.1 to 12.1]Information in this document applies to any platform.
Goal
Using JPublisher Java proxy classes and PL/SQL API wrappers have been created to web service call outs. Calls to the web services are implemented from the application calling the API wrapper calls. The supplier of the Web services has asked us to supply the content of the actual SOAP we are sending. How can we monitor these actual SOAP messages?
NOTE: In this article, all configuration details like server names, usernames, instance names, schema names, domain names, etc. used in the images and examples below represent a fictitious sample for clarity or are default installation values. These and any value placeholder values including the which may surround the placeholders should be replaced by the actual values used in your environment. Any similarity to actual environments, past or present, or users, living or dead, is purely coincidental and not intended in any manner.
Solution
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
| Goal |
| Solution |