How System Types Are Used in XSL Transformation Files

The system type is used by the replication infrastructure to provide XSL transformations (if required) on data being replicated between sites.

When defining a site on the Sites or Sites/Entities form, you can specify the site's system type.

During non-transactional replication, this application looks in the source site's utility server for a file named [source_site_system_type][object_name][target_site_system_type].xsl where:

  • source_site_system_type is the system type specified in the Sites or Sites/Entities form for the site where the data originated.
  • target_site_system_type is the system type specified in the Sites or Sites/Entities form for the site to which the data will be imported.
  • object_name is usually the name of an object in a replication category.

    For example, chart_all is a table object in the G/L replication category.

    XSL files used with objects in the EXTFIN replication category do not follow this naming convention exactly; the object_name part of their XSL filenames must match the hard-coded name in the XML's UpdateCollection request.

This XSL file resides on the utility server in an XSL subfolder under the replication directory. The replication directory is specified in the Service Configuration Manager's Replication tab.

For example, Replication creates an XML document that replicates Chart of Accounts (chart_all) data from a source site whose system type is set to "SL9" to a target site whose system type is "BrandX". If an XSL file exists with a name matching the current source-object-target replication process (that is, a file named SL800chart_allBrandX.xsl), the XML data is transformed using that XSL file before being sent to the target site. If there is no XSL file with that name, the data is not transformed.

Note:  If the source site system type and the target site system type are the same, the system will not look for a transformation file to apply.
Related topics