Error in File Adapter: no alert generated

[Former Member]

Hi folks,

I have a problem with monitoring our file adapters.

In one scenario we occasionally get the following error:

Fehler bei der Konvertierung des Dateiinhalts in XML an Position 0: java.lang.Exception: ERROR converting document line no. 2 according to structure 'eTSFlatDetailStructure':java.lang.Exception: ERROR in configuration / structure 'eTSFlatDetailStructure.': More elements in file csv structure than field names specified!

So I have build an alert category with me as recipient and an alert rule in Runtime Workbench with the following attributes:

- Rule active

- Alert-category as I have created above

- Bound to Message: no

- Error occures in Adapter Engine -> File Adapter

I have tested the Category... it works... but the rule does not fire any alert.

Has anyone an idea how to solve this problem?

Thanks

Greetings

Habib Sarbas

[Former Member · Accepted solution]

Hi,

Execute this report SXMSALERT_LOGREADER and check if your alert is getting triggered in first place.

Regards,

Siddhesh S.Tawate

[Former Member · Accepted solution]

Hi,

the report generates following output:

20090507072803,7018210          0  07.05.2009    09:28:03      0AFE24F09F47460132CAD06697A18964
*Error records received from AF on host rd-srxt0_RXT_00 (sysid: RXT client:  ). Try to send Alert...

20090507072803,7045260          0  07.05.2009    09:28:03      0AFE24F09F47460132CAD06697A18964
*Find rule for (From:vkeTSFlatBPM:vkeTSFlatBPM_var01_eTSSender:mi_eTSFlat_var01_out_asyn:urn:rsd-de:xi:ZRSD_XI_01:vkeTSBPM To::::)

20090507072803,7063530          0  07.05.2009    09:28:03      0AFE24F09F47460132CAD06697A18964
*No matching rule found

I also tried to specify the conditions with service, interface and namespace, but this is only possible if i switch bound to message to yes...

but the error occurs in file adapter... there is no message generated...

[Former Member · Accepted solution]

Hi,

It says No Matching rule found. You need to check your Alert Rule. I would suggest you keep rule to no restrictions initially and keep * in namespace and everything.

Also check by executing this report RSALERTDISP. Here you can view your triggered Alerts and their logs.

Regards,

Siddhesh S.Tawate

[Former Member]

hmm ok...

I think I have it...

now I entered the rule as followed:

Bound to message: yes

Filled partner, service, interface and namespace with the values from the log report

and no restriction...

Alert is generated!

[madanmohan_agrawal]

Habib Sarbas Says..
- Rule active
- Alert-category as I have created above
- Bound to Message: no
- Error occures in Adapter Engine -> File Adapter

Hi Habib,

set the following "Alert Configuration" ...it will work

- Rule active

- Uncheck "Supress Multiple Alerts"

- Bound to Message: not Relevant

- Sender Service : <as per your scenario>

- Sender Interface : <as per your scenario>

- Sender Namespace: <as per your scenario>

- Where did the error occur?: No Restriction

Regards,

Madan Agrawal

[Former Member]

set the following "Alert Configuration" ...it will work

- Rule active
- Uncheck "Supress Multiple Alerts"
- Bound to Message: not Relevant
- Sender Service : <as per your scenario>
- Sender Interface : <as per your scenario>
- Sender Namespace: <as per your scenario>
- Where did the error occur?: No Restriction

Doesn't work... no alert generated...

Edited by: Habib Sarbas on May 7, 2009 9:29 AM

[Former Member]

just check u had enabled Integration Engine in ur Rule

[madanmohan_agrawal]

>>Ok i will try this,

Also make sure that in Alert Catagories, you have entered your name in Fixed receipients.

>>but I only want an alert when an error in File Adapter occurs...

Once it worked successfully, you can chnage alert configuration to set alerts only for File Adapters. In this way you can be sure that alerts are working fine.

Regards,

Madan Agrawal

[Former Member]

check http://sapdocs.info/wp-content/uploads/2009/01/alert-configuration-in-xi.pdf