Show TOC

MigrationLocate this document in the navigation structure


Here, the procedure differs for inbound and outbound scenarios, which is why they are handled in separate sections.


The BW scenario is not currently included in the migration path, since it does not have a standardized procedure.


A queue name must not be used in parallel in classic qRFC and new bgRFC, since no dependencies can be represented, and the classic queues are always processed first in a migration phase before the entries of the new queue are processed. Any processed classic queues are ignored. This means that it is technically possible to keep using queue names in the classic procedure.

Therefore, the migration itself is limited to considering classic queues only temporarily.