cancel
Showing results for 
Search instead for 
Did you mean: 

IS_Retry and RSXMB_RESTART_MESSAGES

Former Member
0 Kudos

Hi all,

I have a requirement to re-send all failed messages automatically.

I've read from blog 2728 that there exists 2 out-of-the-box mechanisms in XI - IS_Retry and RSXMB_RESTART_MESSAGES.

My question:

1. IS_Retry: How do I verify that this is running? When I perform a manual re-start, I see a node "Restart:Message Branch According to Receiver List (Version xxx). However, I do not see the same when I do not perform a manual restart. So how do I know if the failed message has been re-sent?

2. RSXMB_RESTART_MESSAGES: I have scheduled this report to run every hour.

a) From SM36, I can see that the report is being scheduled and running. However, how do I verify that the failed messages are being re-started? Can I see this in SXMB_MONI?

b) The maximum number of re-tries is controlled by the configuration in SXMB_ADM -> Specific configuration 'DELETION' 'MAX_VERSION' 'BATCH_RETRY'. I have the DELETION category, but I do not have this parameter/subparameter. I do not have the report RSXMB_CREATE_CONF_ENTRIES3 either. As advised in /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically , I can run the above-mentioned report to generate the parameters. But I do not see this report in my setup.

Please help.

Thanks.

Ron Lai

Accepted Solutions (0)

Answers (1)

Answers (1)

bhavesh_kantilal
Active Contributor
0 Kudos

Hi,

1 --> IS_RETRY is a paramter that should be set in SXMB_ADM --> Integration Engine Configuration. If there is any error, and the message has been restarted automatically, you will see the Restart of the message when you see the open the message in MONI. It will have separate branch for Restart.

2. A) Same as 1 , but you need to schedule the job. Need not set the Integration Engine Parameter.

Regards

Bhavesh

Former Member
0 Kudos

Hi Bhavesh,

I have set the parameter in SXMB_ADM.

However, I do not see a seperate branch for Restart being created.

The failed messages show a status of "System Error - Manual Restart Possible" in SXMB_MONI, and I can restart them manually through the MONI.

Is there something I left out in the configuration for both IS_RETRY and the RSXMB_RESTART_MESSAGES?

Further observations:

1. I tried to manually run RSXMB_RESTART_MESSAGES using SE38. Without changing any parameters (Time Interval [Checked]. Restart Msg with Errs from last 60 minutes).

I got the message "No XML Messages exists for this selection"

I am using PI7.0 SPS10.

Please help.

Thanks.

Ron

Former Member
0 Kudos

I noticed that the column - "Man. Retry Counter" in SXMB_MONI is incremented periodically.

It is in sync with the frequency of executions of RSXMB_RESTART_MESSAGES scheduled to run as a background job.

Does this mean that the message is being retried?

To me, it seems so, because the start/end time changes as well.

Thanks.

Ron.

bhavesh_kantilal
Active Contributor
0 Kudos

Hi,

Just try this, try to restart some error message manually from MONI. After Restart double click on your message in MONI and you will a new set of entries mentioning that the message has been restarted.

Likewise, you should be able to see the same for IS_RETRY.

Regarding running the report. Are there any Messages in MONI with error? Maybe the report is not able to find the messages with error in MONI.

Regards

Bhavesh

Former Member
0 Kudos

Hi,

Here are my observations:

1. Manual click of "Restart" button in SXMB_MONI:

Additional entry in SXMB_MONI showing message has been restarted.

2. IS_Retry: Not sure how to monitor this.

3. RSXMB_RESTART_MESSAGES:

I scheduled this report to run periodically every 2min. Each time this is executed - by looking at SM37, the "Man. Retry Ctr" column in SXMB_MONI of the error messages are incremented. Additional entry in SXMB_MONI is reflected. Retry stops when "Man. Retry Ctr" reaches 21.

Is this correct?

Please let me know.

Thanks.

Ron

Former Member
0 Kudos

RSXMB_RESTART_MESSAGES:

I scheduled this report to run periodically every 2min. Each time this is executed - by looking at SM37, the "Man. Retry Ctr" column in SXMB_MONI of the error messages are incremented. Additional entry in SXMB_MONI is reflected. Retry stops when "Man. Retry Ctr" reaches 21.

>>this stops aftr 21 because this limit set in your system you can increase this limit in the repot ,to do that you nedd to copy std report to Zreport program and increase the limit.

1. Manual click of "Restart" button in SXMB_MONI:

Additional entry in SXMB_MONI showing message has been restarted.

>>yes our correct

2. IS_Retry: Not sure how to monitor this.

>> you should see in SXMB_MONI what the IS_rety value in SXMB_ADM. that many times it should retry i have feeling that its value right now is Zero so it not retrying

Regards

Sreeram.G.reddy