mapping in integration server

[Former Member]

Hi Experts,

Between Java and abap mapping ,which is faster and recomended.

In which stack(ABAP/Java), mapping is happened.

As per my knowwledge,Integration engine runs on java server and mapping editor is a java application and graphical mapping is also a java application.

So does integration server pass the control to java stack for mapping in pipeline process.

Please help me out........

[Former Member · Accepted solution]

Hi Raj,

Usally Java Stack is faster than Abap.

IR - Java

ID - Java

IS - ABAP + Java

BPE - ABAP

AE - Java

IS has 3 main components - IE, BPE and AE. IE and BPE are ABAP based and AE is Java based

ABAP,Java Stackboth communicate with each other using a Middlewhere called JRFC

SAP actually very intelligently deals the integration process by involving both ABAP and Java runtime what ever suitable in combination. Such as ABAP is very efficient doing business logic and Java is very suitable for handling low level programming. So Java and ABAP both communicate with each other for the completion of whole process

Regards,

Ramesh.

[Former Member]

Hi,

The sequence is

Graphical

Java

XSLT

ABAP

IE sits on ABAP stack.

Pipleline Services that are nothing but the ABAP objects class

[Former Member]

Hi,

Java mapping will be faster than ABAP mapping

/people/udo.martens/blog/2006/08/23/comparing-performance-of-mapping-programs

/people/ravikumar.allampallam/blog/2005/02/10/different-types-of-mapping-in-xi

I think Java is better than ABAP for mapping, and if you can XSLT is the best.

You can test your Java mapping in your JDE (Eclipse) and it is more friendly than the ABAP debugger.

Java provide a very large API, I am not sure ABAP API too.

About transport system: Java is transporting with your Repository development, so you don't need to do anything more.

I think you must use ABAP mapping only when you can't do XSLT or JAVA mapping. For example when you want to use FM.

Java has better IDE tools than ABAP, and has a richer API library.

If you have a java version management system in place, such as sourcesafe, cvs, or SAP JDI, that won't be a problem.

Another issue with ABAP mapping is the performance. Natively, XI uses java mapping since that part is built on Java stack. When ABAP mapping is used, it has to make a RFC call from Java to ABAP stack which consume some resources and time.

For ABAP mapping you need to use

ABAP Mapping

I suggest you also go through these links to know more on ABAP Mapping:

https://websmp101.sap-ag.de/~sapdownload/011000358700003082332004E/HowToABAPMapping.pdf

/people/ravikumar.allampallam/blog/2005/02/10/different-types-of-mapping-in-xi

/people/r.eijpe/blog

Refer to following SDN Demo which explains the need and how to do the ABAP mapping.

https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/110ff05d-0501-0010-a19d-958247c9f798#jdi [original link is broken]

This document will help you to create ABAP Mapping.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e3ead790-0201-0010-64bb-9e4...

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/how%20to%20...

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5c46ab90-0201-0010-42bd-9d0...

JAVA Mapping

These are two article links on Java mapping i hope this will help u:

http://help.sap.com/saphelp_nw04/helpdata/en/e2/e13fcd80fe47768df001a558ed10b6/content.htm

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/java%20proxies%...

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/java%20proxies%...

Also go through these Blogs,

/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping

/people/michal.krawczyk2/blog/2005/02/25/simple-java-code-in-graphical-mapping--xi

ABAP XSLT mapping

/people/r.eijpe/blog/2005/11/04/using-abap-xslt-extensions-for-xi-mapping

Thanks

Swarup

[Former Member]

Hi folks,

in general I would recommend to use the XI Graphical Mapping tool, as the mapping can be maintained much easier afterwards from customer than specific XSLT or Java "coding" or ABAP "coding" mappings.

And with XSLT - the performance can be very bad if the message is getting larger and larger and a lot of nested loops are executed.

With Java/ABAP Coding: Please do not program bad performing algorithms (for example the easiest but worst sorting algorithm Bubble-Sort instead of binary search or better performing algorithms).

Usually in development phase you test with normal (small) messages to test the mapping funtionality itself, but sometimes the testing is not carried out with "real-life" data - meaning with larger messages from a real production system.

So please check your mapping development with real data first - and check the performance of the mapping execution with real-life messages.

In regards to ABAP Mapping, this is executed locally in the XI Integration Server, and no Jco-RFC Connection to the external Java Mapping Runtime is necessary. But again, ABAP Mapping might be harder to understand from your successor in the project that the graphical mapping (which is internally compiled to Java coding).

Therefore I would always suggest:

Try to use the XI Mapping Tool (and keep up with the additional features from SPS to SPS and release to release - in 7.1 a lot of new functionality is coming).

Best regards,

Silvia

[Jitendra_Jeswan]

Mapping Runtime is on Java Engine. So offcorse Graphical mapping are faster.

To perform ABAP mapping , Jco RFC calls are triggered which are comparatively time consuming..

Regards.

Jeet,