Hi,
I am runnning a large XSLT transformation (source XML ~
16MB - relatively flat format record structure from a POS
system converting to IS Retail IDOC WPUBON IDOC -
around5MB of converted XML).
The aim is that this is portable bewteen SAP Business
Connector and SAP XI (both using the SAP XML TOOKIT). It
was looking good (around 80 seconds conversion time on my
laptop) and then I got a sapxmltoolkit.jar update (then I
tried it on SAP BC 4.7 then tracked it down to versions
of the sapxmltoolkit).
I then looked at the command line performance on this for
various different versions of sapxmltoolkit (used to be
command line from inqmyxml.jar) - we use xmlspy for XSLT
development and you can hook in a command line call to
use the library... sample call:
C:jdk1.3.1_15jrebinjava -ms384M -mx1024M -cp D:testingsapxmltoolkit.jar;
C:jdk1.3.1_15jrelibrt.jar;D:testingSCTmapping.jar
com.sap.engine.lib.xsl.xslt.CommandLine %1 %2 %3 %4
LOOKING AT THE PROPERTIES file from the jar file the
following version works well. Run time around 80 seconds
completing in 500M of memory
version=630.20030828104710.0000 GOOD
the next two versions I have work very badly - run time
greater than 10 minutes, system pages itself to death
uses all 1GB of java memory (and my laptop only has 1GB)
version=630.20050221090341.0000 BAD
version=630.20040429124817.0000 BAD
I see the latest version available still seems to be
stamped 630 (even in 640 netweaver shipment). Who
develops this... My samples to replicate this problem are
rather large... but happy to post them to site for
interested party
Even on a 140K sized sample XML the same ratio exists
goes from a few seconds to convert to minutes.... just on
a change in sapxmltoolkit versions
Regds Doug.
mailto:doug.munford@supply-chain.com.au
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.