Topic
7 replies Latest Post - ‏2013-01-02T13:32:15Z by kenhygh
NILAY97
NILAY97
196 Posts
ACCEPTED ANSWER

Pinned topic Log Incoming Request

‏2012-12-27T11:22:19Z |
Hi All,

I want to log my incoming request(soap) so that i do not have to check the probe all the time for the hits.

I can goto that particular location of my logging and can extract all the requests that are being hit on DatPower.

I'am new to DP and do not have much idea about this. Please Help me.
Updated on 2013-01-02T13:32:15Z at 2013-01-02T13:32:15Z by kenhygh
  • Daviiid
    Daviiid
    282 Posts
    ACCEPTED ANSWER

    Re: Log Incoming Request

    ‏2012-12-27T11:35:15Z  in response to NILAY97
    Hi

    Maybe you can use a styleSheet with this command

    <xsl:message dp:priority="????">
                            <xsl:copy-of select="."/>
                    </xsl:message>
    
    Updated on 2014-03-25T02:44:15Z at 2014-03-25T02:44:15Z by iron-man
    • NILAY97
      NILAY97
      196 Posts
      ACCEPTED ANSWER

      Re: Log Incoming Request

      ‏2012-12-27T11:43:43Z  in response to Daviiid
      Hi David,

      Thanks for your reply.

      <xsl:message dp:priority="debug">
      <xsl:copy-of select="."/>
      </xsl:message>

      Is this what you want to convey? Where will this save my incoming request?

      Thanks,
      Nilay
      • Daviiid
        Daviiid
        282 Posts
        ACCEPTED ANSWER

        Re: Log Incoming Request

        ‏2012-12-27T12:42:30Z  in response to NILAY97
        Hi

        Your incoming request will be saved in general log (Status/view logs/system logs)
        • HermannSW
          HermannSW
          4357 Posts
          ACCEPTED ANSWER

          Re: Log Incoming Request

          ‏2012-12-27T13:11:29Z  in response to Daviiid
          Hi Nilay,

          David is right, but please be aware of the following log message size restriction (from this technote):
          ...
          WebSphere DataPower log event text is limited to a maximum length of 2048 bytes. Log text length over 2048 bytes will be truncated. 
          This limitation applies to every log priority and every type of log, including the log output from xsl:message. 
          This limitation currently exists on every firmware level.
          


          For the "why" on this, Datapower is designed for high throughput/concurrency processing.
          Unrestricted log messages would negatively affect the design targets.

          Btw, there is another thing to know about logging, also caused by previously mentioned design targets.
          If the box comes under very high load, then transaction processing has priority and log message might get dropped.

           
          Hermann <myXsltBlog/> <myXsltTweets/>
          Updated on 2014-03-25T02:44:10Z at 2014-03-25T02:44:10Z by iron-man
          • SystemAdmin
            SystemAdmin
            6772 Posts
            ACCEPTED ANSWER

            Re: Log Incoming Request

            ‏2013-01-02T09:07:28Z  in response to HermannSW
            The limit of 2048 bytes only applicable for xsl:message or it is applicable with log-action (processing action) also?

            RG
            • HermannSW
              HermannSW
              4357 Posts
              ACCEPTED ANSWER

              Re: Log Incoming Request

              ‏2013-01-02T11:32:55Z  in response to SystemAdmin
              Hi, its a general log message length restriction.

               
              Hermann<myXsltBlog/> <myXsltTweets/>
            • kenhygh
              kenhygh
              1427 Posts
              ACCEPTED ANSWER

              Re: Log Incoming Request

              ‏2013-01-02T13:32:15Z  in response to SystemAdmin
              Rohit,
              In working with several customers who needed to log the entire payload, they'd use dp:url-open() to their own logging server instead of using a log action.

              Ken