XML transformations

The transmission processed notification task delivers normalized transmission processed notification XML to the Gateway outgoing directory. The Gateway Server gets the normalized XML file and delivers it to the target destination. It uses a corresponding routing file, created in conjunction with the normalized XML, to determine the channel and parameters for delivery.

If a different transmission processed notification file format is required, a transformation stylesheet can be configured when setting up the transmission processed notification task. The stylesheet transforms the normalized notification XML to a different format by using XSLT.

XSLT (Extensible Stylesheet Language Transformation) transforms a source XML document into another XML, XHTML, or non-XML format. The transmission processed notification task uses it to convert the transmission processed notification XML into any supported XSLT format.

The files that you need are provided in the FTM artifacts pod and must be downloaded from the pod. For more information about getting files from the artifacts container for your offering, see Getting the files from the artifacts container for your FTM offering.

Transmission processed notification provides a sample XSLT file. This sample file is at <ftm-artifacts-pod>/share/artifacts/development/common/service-framework/xml/SampleTransmissionProcessedNotification.xsl.

A sample XML validation schema (XSD) file diagrams the format of the normalized XML. This sample file is at <ftm-artifacts-pod>/share/artifacts/development/common/service-framework/xml/transmissionprocessednotification.xsd.