Is there a way to automatically resend the messages stuck with "Server Error" in RWB? I know we could use the resend button but i was curious is there any other way to resend these messages automatically like is_retry_limit that is available on the ABAP Stack for Integration Server.
RSXMB_RESTART_MESSAGES is for resubmiting messages in Integration Server (ABAP Stack.)
There are two good notes on resubmiting messages
786905
813029
Unfortunately both of then deal with resubmiting messages from Integration Engine.
Once a message is sent to Adapter Engine, the message is check as success in IE , but it could fail in AE due.
Whats going on is , we have a scenario in testing SOAP-XI-JDBC, XI talking with sybase and sybase goes down for maintenace for couple of hours each day. Hence we have many message in RWB with server error. We can manually resubmit all of them.
I initially thought rsxmb_resubmit_messages could handle these error... but i was wrong.
Michal : we do have it in a BPM , the problem in our scenario is that sybase goes down sporadically each day random in nature for maintenaince and for other stuff. This could be from few secs to few mins. During this time some messages will fail, AE will try to resubmit the messages 3 times as per the configuiration in Visaul admin. But after 3 times in puts the emssages as "system error". We have to manually go and resubmit. what would be nice is an automated program that we could shcedule for resubmiting the messges with system error status.
Anand: yes we did look at it and the post doesnt address the solution we are seeking.
If processing of a message on the Adapter Engine fails, the message state is changed to faulty. To notify administrators immediately of such processing failures, they can be propagated as alerts to CCMS. As CCMS is the SAP standard interface to third-party monitoring tools, these failure events may also become visible in non-SAP monitoring tools.
Configuration Steps
To make use of Adapter Engine alerts, you must configure the connection to CCMS as follows:
...
1. Make sure that the J2EE engine on which the Adapter Engine is running is configured to be monitored by the central CCMS system.
To do so, execute transaction RZ20 on your central monitor server. There, the J2EE engine should be visible in the CCMS monitor under SAP J2EE Monitor Templates ® All Systems. If not, follow the steps described in the Supportability Setup Guide for SAP NetWeaver 04 on SAP Service Marketplace at service.sap.com/nw04operation ® Cross-NW.
2. Check whether the Adapter Engine is configured to report errors to CCMS.
To do so, start the Visual Administrator and select service SAP XI AF Core. The value of property CCMSEnabled must be set to true (in lower case letters). If it is not, change the property value to true and restart the service.
To verify that the setting is effective, select the Visual Administrator Monitoring service. Under Root ® Applications, you should see a node for the Adapter Engine.
We found a work around solution. Like the retry limit which we can set in sxmb_adm , we can also change the retry count in AE, by defaut its set to 3 times, 3 minutes apart.
THis count can be changed in Visual Admin->server->services-> SAP XI Adapter: XI.
here we changed the numberRetries parameter from 3 to 10 and aslo changed retryInterval.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.