Queues

[Former Member]

Hi

Can someone explain to me the step by step procedure for automatic start of these transactions, RSQIWKEX, RSARFCEX, RSXMB_RESTART_MESSAGES ? Are they set in the Integration Engine configuration of SXMB_ADM ?

Radhika

[Former Member · Accepted solution]

Hi Radhika,

All these reports are to perform retry with failed/error messages in PI and you either perform manually by processing qrfc (SMQ1), trfc (SM58) and manually 'restarting' a failed messages in SXMB_MONI, Otherwise you can schedule to do the same using below programs.

RSXMB_RESTART_MESSAGES - Mass Restart by scheduling the report RSXMB_RESTART_MESSAGES at a predetermined retry period like 1hr

RSQIWKEX - For automatic qRfc failure recovery you schedule this report to run periodically

RSARFCEX - - For automatic tRfc failure recovery you schedule this report to run periodically

so now, how you automat it...is basically you need create Background Job for each of these reports using SM36. You may name jobs as per standards(custom names for your understanding)

PI Periodic jobs information

http://help.sap.com/saphelp_nw70/helpdata/en/cd/20bc3ff6beeb0ce10000000a114084/frameset.htm

How to Schedule Background Job

http://help.sap.com/saphelp_nw70/helpdata/en/c4/3a7f87505211d189550000e829fbbd/frameset.htm

I hope this helps you in understanding and completing your task.

Regards

Sekhar

[Former Member · Accepted solution]

Thanks

I would like to know one thing. The " HOLDING " status is only for EOIO queues, right ? So that way, the " SCHEDULED " and " WAITING " status are for EO or EOIO ?

I am confused with the inter use of these three terms, " HOLDING ", " SCHEDULED ", and " WAITING ". Is there any parameter that a particular status is for a particular type of queue.

Can some one throw light on these terms ?

Radhika

[Former Member · Accepted solution]

Hi Radhika,

Well, you are right. EOIO/EO being Asynchronous based you have feasibility to for all such status of the messages.

Wherein BE is Synchronous.

There are no specific parameter as such....these status of messages by default the nature of the behavior of Asynchronous

You can monitor EOIO queues in Adapter Engine using below URL

http://<server>:<port>/MessagingSystem/monitor/systemStatus.jsp

Regards

Chandra Kanimeni.

[Former Member · Accepted solution]

Meaning of these terms here

http://help.sap.com/saphelp_nw04/helpdata/EN/05/d5fc3f8fc2c542e10000000a1550b0/frameset.htm

[Former Member]

Hi radhika,

The Adapter Engineu2019s Messaging System (MS) receives the message, processes it and forwards it to the receiver. While the MS processes the message, it passes several statuses:

● TO_BE_DELIVERED:

The state of message when it is initially handed over to the Messaging System.

● DELIVERING:

The state of message when it has popped out of the MS queuing system and is in the process of being transmitted across the wire or delivered to an application.

● DELIVERED:

The state of message when it has successfully reached its intended recipient.

● HOLDING:

The state of an EOIO message that cannot be delivered until its predecessors have been delivered.

● NON_DELIVERED:

The state assigned to a message when all attempts (retries) to deliver the message to its recipient have failed.

● FAILED:

The state assigned to a message when an administrator decides to abort sending the message, or when a message could not be delivered due to a fatal exception that cannot be repaired.

● WAITING:

The state of a message that has been attempted to be sent at least once, failed, and is currently waiting for another attempt.

Statuses such as HOLDING or FAILED usually happen only for delivery semantics EOIO (exactly once in order) or BE (best effort).

refer link: http://help.sap.com/saphelp_nw04/helpdata/EN/49/e3fb40ef74f823e10000000a155106/frameset.htm

Regards

Manisha

[Former Member]

The above reports need to be scheduled using the scheduler avaialble for this we use sm36 tcode and need to provide the report names and need to provide the time interval for how often these jobs need to be run and how many times it needs to be run....

HTH

Rajesh