The "classical migration" (heterogenous system copy of SWPM) uses either the file mode or the socket mode.
Using the file mode, the data are exported, and written into a file, using compression. The file is transferred over the network:
Using the socket mode, the data are exported and transferred over the network:
Now with DMO, both R3load are running on the same host, and they communicate using the main memory of that host, using the pipe mode per default:
:!: Warning (Unix only)!
Do not use the statement grep* on the migrate_* directories to check for error messages. This generic grep statement may corrupt the named pipes used in R3load communication and cause errors in R3load processing. (Using “grep*.LOG” in these directories is not dangerous.)
Note
Even with DMO, it would be possible to switch to the file mode. The R3load exports the data into a temporary file of limited size. As soon as this file is processed and the data are imported into the target DB, the temporary file is deleted.
Boris Rubarth
Product Manager, Software Logistics, SAP SE
[Update on June 1st 2015] File mode for DMO does use compression (this was initially wrongly stated in the blog).
[Update on March 15th 2016] Removed graphic for DMO file mode and shortened text; added warning on grep statement.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
21 | |
16 | |
13 | |
12 | |
11 | |
10 | |
7 | |
7 | |
7 | |
7 |