Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Maryan,</p> <p>ESB itself doesn't log messages anywhere until you tell it to.</p> <p><strong>a)</strong> The first approach is to write incoming and outgoing messages into the log using log mediator:</p> <pre><code>&lt;proxy xmlns="http://ws.apache.org/ns/synapse" name="YourProxyService" transports="https http" startOnLoad="true"&gt; &lt;target&gt; &lt;inSequence&gt; &lt;log level="full"&gt; &lt;property name="MESSAGE_ID" expression="get-property('MessageID')"/&gt; &lt;/log&gt; ... &lt;/inSequence&gt; &lt;outSequence&gt; &lt;log level="full"&gt; &lt;property name="MESSAGE_ID" expression="get-property('MessageID')"/&gt; &lt;/log&gt; ... &lt;/outSequence&gt; &lt;/target&gt; &lt;/proxy&gt; </code></pre> <p>Then you'll be able to find your incoming and outgoing messages in log files as the logs would contains something like following:</p> <pre><code> INFO {org.apache.synapse.mediators.builtin.LogMediator} - To: http://localhost:9763/services/YourProxyService, From: 127.0.0.1, WSAction: urn:mediate, SOAPAction: urn:mediate, Direction: request, MESSAGE_ID = urn:uuid:e11893c5-b033-4e99-9473-a43d66b65fbb , Envelope: &lt;ENVELOPE_GOES_HERE&gt; </code></pre> <p><strong>b)</strong> Another approach would be to create table in the database and store message id and envelope to it.</p> <p>Hope this helps. Vladimir.</p> <p><strong>UPD:</strong> You can also use built in SOAP tracer, but enable it with caution - it hits ESB performance. So I suggest use it only for short term debugging activities.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload