How Does an XSLT Service Work?

When executed, the XSLT service calls an external XSLT engine to convert the XML data. The external XSLT engine must be Java API for XML Processing (JAXP)-compatible. By default, Integration Server includes the Xerces parser and the Xalan XSLT style sheet processor from the Apache Software Foundation. The Java archives for Xerces and Xalan are located in the Software AG_directory \common\lib\ext directory.

To use a more current version of the Xalan or other 3rd-party XSLT processor, you must place all the related jar files in the Integration Server_directory \instances\instance_name\packages\WmXSLT\code\jars directory and configure the transformer factory settings to specify the appropriate XSLT transformer class. You must also identify a package dependency on the WmXSLT package for XSLT services in custom packages. For more information about identifying package dependencies, see About Package Dependencies.

Note:
Transforming a very large XML file can exceed the memory parameters set in Integration Server, resulting in the following error message: “Could not run filename. java.lang.reflect.InvocationTargetException: OutOfMemoryError”. If this occurs, edit the wrapper.java.maxmemory property in the custom_wrapper.conf file. For information about changing the JVM heap size by editing the Java properties in the custom_wrapper.conf file, see the webMethods Integration Server Administrator’s Guide.