Resend

Resend is a process initiated by the Message Broker each time after its restart. It is meant to ensure that all unconfirmed messages, presumably undelivered, will be again sent to FSM. The point is to avoid any data loss. In many aspects, Resend and Fullsync are very similar to each other. Resend process should not be interrupted. It initiates its own queue while stopping all others.

Open

Resend ends with RESENDEND message. FSM Cockpit shows information that RESEND is running.

Open

The process starts with sending RESENDSTART to message broker to acknowledge it has started – otherwise, message broker would repeat process initiation. Resend ID must match in both messages. Also, only messages having this RESEND ID will get processed by Message Broker.

Open

Message Broker remains in the ‘RESEND MODE’ until RESENDEND gets sent. While being in this state no new message will get processed

Customizing

As in case of Fullsync, Connector gives control over which objects should be included by RESEND. In the Connector configuration /PACG/ECM_CLSASSIG (Outgoing Class Assignment), each object has a checkbox ‘Rel.for.resend’. Only objects having it enabled will be included in the process regardless of their status (whether they are confirmed or not). There is additional parameter that controls objects’ relevancy - in transaction /PACG/ECM_CPROP - ‘Take unconfirmed Idocs not older than’. It’s goal is to avoid resending objects which are too old and can be considered as irrelevant. It also improves performance of the RESEND process