are there any statements about scalability of the integration engine of XI 3.0? What can we do if we run into performance problems. Is the IE clusterable?
there are several possibilities that you can take into consideration. An additional java node can help you, even with a little bit of patience and thinking you could dedicate a java node only for mappings However, relying on the heap size of the j2ee, you can increase the maxthread and the maxconsumers in the j2ee so that more messages can be queued. This has to be done with a lot of care as you may run into outofmemory errors if the heap size is not enough to handle a high number of consumer and/or connections. Have a look at the quicksizer and check how your hardware resources should look like according to your scenarios (mappings, etc)
the adress is service.sap.com/quicksizer. It is relatively easy to use.
I read the document, Michal, chapter 3.1.3 about load balancing is quite helpfull. Thank's.
As I understand it right for scaling up the adapter engine (java stack) I would need a web dispatcher but for scaling up the integration engine (ABAP stack) this would do the message server. Right?
As I understand it, Jaime, most of the performance/memory is needed for the mapping in general? That's why normal mappings don't use XSLT?
Kind regards,
Horst
PS: The quicksizer did not work for me (with firefox)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.