Topic
6 replies Latest Post - ‏2013-11-12T19:21:43Z by tallurisri
grol
grol
29 Posts
ACCEPTED ANSWER

Pinned topic How to manage xml captured in probe

‏2013-10-31T11:43:09Z |

Hi,

Are there a way to manage an export probe?.

I want to make date searches or add filters. A tool that allow handle captured messages like you can do in wireshark for example..

 

Regards,

Grol

  • HermannSW
    HermannSW
    3131 Posts
    ACCEPTED ANSWER

    Re: How to manage xml captured in probe

    ‏2013-11-01T17:40:37Z  in response to grol

    Hi,

    Probe capture exports are only intended to be imported into the same or another DataPower box in order to be viewed by Probe.

    This posting explains the Probe capture structure and how you can view any (even Non-XML) context contents in <transaction-input> element:
    https://www.ibm.com/developerworks/community/blogs/HermannSW/entry/wanna_know_what_is_in_probe_context_displayed_empty

    There are no Probe capture tools.


    Hermann<myXsltBlog/> <myXsltTweets/> <myCE/>

     

    • grol
      grol
      29 Posts
      ACCEPTED ANSWER

      Re: How to manage xml captured in probe

      ‏2013-11-04T09:13:49Z  in response to HermannSW

      Thanks for the response.

      Then If you have a service with a lot of traffic and you are tracing it, how you can do to find one request in particular?

       

      Regards,

      Grol.

      • HermannSW
        HermannSW
        3131 Posts
        ACCEPTED ANSWER

        Re: How to manage xml captured in probe

        ‏2013-11-05T09:17:17Z  in response to grol

        First let me restate the most important message on Probe from  InfoCenter:
        http://pic.dhe.ibm.com/infocenter/wsdatap/v5r0m0/index.jsp?topic=%2Fcom.ibm.dp.doc%2Fproblemdetermination73.htm

        ...
        CAUTION:
        Do not leave the probe in the enabled state for production conditions. Disable the probe before moving the configuration into production.
        ...


        So we are talking on develeopment or test Probing here.

        One way to restrict the transactions that actually are captured is by using Probe Triggeres.
        From WebGUI help:

         

        Probe Triggers

        The probe captures transactions that meet one or more of the conditions defined by the triggers. These triggers examine the direction or type of the message flow and examine the message for an XPath expression match. When a message meets one of these conditions, the transaction is captured in diagnostics mode and becomes part of the list of transactions that can be viewed.

        Client-IP Match

        Specify a PCRE to match against client IP addresses. Requests from clients with matching IP addresses will trigger the probe. To create a match for all IP addresses, specify .* instead of * as the PCRE.

        Inbound URL Match

        Specify a PCRE to match against the inbound URLs. Requests from clients with matching URLs will trigger the probe. To create a match for all URLs, specify .* instead of * as the PCRE.

        Outbound URL Match

        Specify a PCRE to match against the outbound URLs. Responses from servers with matching URLs will trigger the probe. To create a match for all URLs, specify .* instead of * as the PCRE.

        Processing Type

        Select the rule direction or type that will trigger the probe.

        • Any
        • Response

          Response rule (server-originated)

        • Request

          Request rule (client-originated)

        • Call

          Call processing rule

        • Error

          Error rule

        Processing Rule Match

        Specify a PCRE to match against names of processing rules. Rules with matching names will trigger the probe. To create a match for all names, specify .* instead of * as the PCRE.

        XPath Expression Match

        Specify an XPath expression of use the XPath Tool to define an XPath expression to match against messages. Messages that contain the expression will trigger the probe.



        Hermann<myXsltBlog/> <myXsltTweets/> <myCE/>

         

        • grol
          grol
          29 Posts
          ACCEPTED ANSWER

          Re: How to manage xml captured in probe

          ‏2013-11-12T12:02:49Z  in response to HermannSW

          Sorry for the delay.

          I have been reading about how to logging request and response payloads. That's what we need. Triggers is not the solution.

          In one post someboy talks about to log this sending asynchronous messages to MQ and then insert them into a database. We don't have MQ but we have TIBCO EMS.

          Is this solution good for PRO enviroments?

          I'm not sure how to send request to EMS. I guess that you have to add a extra result action in the ws policy to route the messages. Is that correct? 

          Thank you

          Regards.

          Guillermo.

          • kenhygh
            kenhygh
            863 Posts
            ACCEPTED ANSWER

            Re: How to manage xml captured in probe

            ‏2013-11-12T18:02:01Z  in response to grol

            Guillermo,

            Check the InfoCenter for dp:url-open() for EMS endpoints to see how to specify the details if you want. Or, better, use an asynchronous-results action.

          • tallurisri
            tallurisri
            59 Posts
            ACCEPTED ANSWER

            Re: How to manage xml captured in probe

            ‏2013-11-12T19:21:43Z  in response to grol

            Hi Grol,

            we are doing this from transform action by using xsl file with dp:url-open to ftp server. 

             

            Thank you,

            Sri.