Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Integration Builder Memory Consumption


we are experiencing very high memory consumption of the Java IR designer (not the directory). Especially for loading normal graphical idoc to EDI mappings, but also for normal idoc to idoc mappings. examples (RAM on client side):

- open normal idoc to idoc mapping: + 40 MB

- idoc to edi orders d93a: + 70 MB

- a second idoc to edi orders d93a: + 70 MB

- Execute those mappings: no additional consumption

- third edi to edi orders d93a: + 100 MB

(alle mappings in same namespace)

After three more mappings RAM on client side goes on 580 MB and then Java heap error. Sometimes also OutOfMemory, then you have to terminate the application.

Obviously the mapping editor is not quite will optimized for RAM usage. It seems to not cache the in/out message structures. Or it loads for every mapping very much dedicated functionality.

So we cannot really call that fun. Working is very slow.

Do you have similar experiences ? Are there workarounds ? I know the JNLP mem setting parameters, but the problem is the high load of each mapping, not only the overall maximum memory.

And we are using only graphical mappings, no XSLT !

We are on XI 3.0 SP 21


Not what you were looking for? View more on this topic or Ask a question