Skip to content
Psyncopate TIBCO Modernization Suite Docs

XSLT Converter

TIBCO® projects often utilize XSLTs (Extensible Stylesheet Language Transformations) for transforming XML data. However, TIBCO-specific XSLTs may contain proprietary functions that are not compatible with standard XSLT processors.

The XSLT Converter extracts and converts TIBCO®-specific XSLTs from all process files into standard XSLTs for consistent processing across environments.

Post-Processing Steps

  1. Click the XSLT converter icon (labeled XSLT / XSLT Files) to view results when processing completes.

    XSLT Icon

  2. Review Columns

    • XSL ID: Unique XSL file identifier.

    • TIBCO Count: Number of TIBCO-specific functions available in XSLT.

    • Converted Count: Number of TIBCO functions successfully converted to standard functions.

    • Line Count: Total number of lines in the source XSL file, indicating its size.

    • Accuracy: Conversion Success rate.

    • Compilation Status: Indicates whether the XSLT file compiled successfully.

    • Compilation Remarks: Additional information about the compilation status.

    • Failed Count: Number of functions that were failed to convert.

    • Failed Function List: List of TIBCO functions that were failed to convert.

    • Non-Converted Count: Number of TIBCO functions that were not converted due to lack of support.

    • Unavailable Functions: List of TIBCO functions that were not supported.

    • Custom Functions: TIBCO functions without native equivalent in the XSL library, requiring custom implementations.

    • Dependent Functions: Functions that rely on custom functions.

    Note: The output XSLs will handle the conversions appropriately. However, the “Compilation Status,” “Compilation Remarks,” “Failed Function List,” “Unavailable Functions,” “Custom Functions,” and “Dependent Functions” columns may indicate processing issues that require your attention if they contain any entries.

  3. Actions

    • Download: Request download of both original and converted (standard) XSL files as a ZIP archive.

      • If you select only one XSL row, a popup will offer the option to include the transformation factory in the download.

      • When selected, the download will include:

        • A ZIP archive containing the selected XSL files.
        • A transformer directory with all required libraries and scripts to test the transformation locally.

      • Please note that the transformation factory requires Java 17 (or above) and Maven to run.

      • Run mvn test command in the transformer directory to execute the test suite.

      Note: The transformation factory option is only available for single XSL file downloads.

    • Show Difference: Compares the TIBCO XSL file to the converted (standard) XSL file.

      • Highlights the differences between the two files while listing the number of lines added, removed, and modified.

    • Transform: Allows you to apply the converted XSLT to an XML file to verify that it behaves identically to the original TIBCO XSLT.

      • To use it, upload the same XML file you used with TIBCO XSLT.
      • The system applies the chosen converted XSLT to perform the transformation.
      • You can compare the resulting XML output with the one produced by TIBCO XSLT to ensure the conversion is accurate.

Working with Output Files

Users can utilize the converted XSLT files for consistent processing of XML files across various environments.

If your download included the transformation factory, you can use it to validate the converted XSLT files against the original TIBCO XSLTs:

  • The Transformer directory contains the necessary libraries (e.g., Saxon, Xalan) and a test suite.
  • Open the directory in your IDE or terminal to run the test suite and verify transformation accuracy.

When using these XSLT files for transformation, it is essential to reference the appropriate libraries, such as Saxon and Xalan. Ensure that these libraries are accessible in the environment where the transformation is being performed.



TIBCO® is a registered trademark of Cloud Software Group, Inc. and/or its subsidiaries in the United States and/or other countries. All other product names, logos, and brands are the property of their respective owners.