Skip to Content
avatar image
Former Member

Alerts for JDBC Receiver Adapter

Hi ,

I am using JDBC receiver adapter. I have configured the alert category and Alert rules. Alerts are getting for Mapping etc.

When ever error occured in the SQL server whether its firewall issue or some other issue. The alerts are not created. Instead I can see the error message in RWB Message monitoring and communicaton channel monitoring.

Please let me know How can raise alerts if the error occured at the JDBC receiver side.

Thanks in advance,

Kevin

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • Sep 20, 2010 at 05:04 PM

    hi,

    in RWB ALERT configuration check if you select Adapter Engine for the alert you configure previuosly under WHERE DID THE ERROR OCCURS there, select the adapter type.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Kelvin,

      You copy the alert category to a new category with the same configuration.. and check it once.

      kindly complete alerts from the AlertInbox. It will refresh the cache for alert, sometimes it's stuck in cache, even though u clear the cache..

      It should work..

      Kindly check the tcodes "alrtdisp" whether alert is generated or it's stuck somewhere in alert queue..

      I hope you haven't seperate alert server right?

      Regards,

      Sushama

  • avatar image
    Former Member
    Sep 20, 2010 at 05:06 PM

    I think you are getting mapping errors only because it occurs on IE and you might have selected IE in the alert configuration. Either make it ALL or create a new rule for AE as well.

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 20, 2010 at 06:19 PM

    Hi Kevin.

    Look at ALERT CONFIGURATION, maybe your rule isn't configured to every error (INTEGRATION SERVER and ADAPTER ENGINE).

    Good luck.

    Bruno

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 21, 2010 at 06:20 PM

    Hi Kevin,

    Probabaly the alert rule did not capture the error in the adapter engine.

    The filter for sender and receiver interface details in the alert rule can cause this issue depending on when and how the error occured. Can you create an alert rule with * for all entries, for adapter engine and check?

    Also do NOT check the option "suppress multiple alerts from this rule" because it will prevent subsequent alerts from this rule, if there is already one and not yet confirmed.

    Further please check the alerts in SALRT table in se16 if its created properly or via transaction ALRTDISP.

    Please use the report SXMSALERT_LOGREADER for troubleshooting and checking the alert logs.

    Hope this helps.

    Regards,

    Francis

    Add comment
    10|10000 characters needed characters exceeded