Skip to Content
author's profile photo Former Member
0
Former Member

Complex mapping performance

Posted on Feb 14, 2005 at 04:07 PM 17 Views

Hi All,

I've recently been on the SAP XI 3.0 Bootcamp in the UK and have an issue someone might be able to clear up. We were told that mapping is the biggest over head which makes sense. We were also told that complex mapping scenarios were more efficiently handled using XSLT mapping rather than Java Mapping via Message Mapping in the IR.

Has anyone got an opinion on this ?

Thanks

Gary

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • author's profile photo P. van Os
    P. van Os
    Posted on Feb 14, 2005 at 04:20 PM
    0

    Hi Gary,

    Mapping should be done outside BPM, XSLT is faster than JAVA.

    Cheers,

    Paul

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member
      Feb 15, 2005 at 05:26 AM

      That depends really!!!

      We do not have access to published benchmarks from SAP on the mapping performance of the XI Mapping Runtime, versus other XSLT implementations.

      Hence, I will dispute if complex mapping should be done outside XI; there is no published metrix that compares XSLT performance with SAP.

      Again, Java based mapping is faster than XSLT. In fact, we had to resort to custom mapping in Java when the xalan / xerces performance was unacceptably slow on a 25MB document for a certain scenario. This was of course using a different EAI product.

  • author's profile photo Former Member
    Former Member
    Posted on Feb 15, 2005 at 02:12 PM
    0

    When I say Java I am referring to the graphical mapping tool which I believe compiles into Java. Does this change things ?

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member
      Feb 15, 2005 at 10:40 PM

      Hi,

      Java vs XSLT mapping is not an easy question to solve but anyway mapping performance should be better than XSLT for mapping with calculation.

      Keep in mind that XSLT parsing is using character based processing so to do calculation with XSLT , the parser has to first convert all data into numeric which is not the case in Java using numeric as well as character data.

      But anyway I agree that depends on the mapping complexity.

      Greetings

      Nicolas

    Comment on This Answer
  • author's profile photo Former Member
    Former Member
    Posted on Feb 16, 2005 at 09:46 AM
    0

    Thanks to all of you. The message is not particularly clear but I deduce from this that the consensus is that graphical/Java mapping is more efficient for complex mapping scenarios.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.