Using the mechanism described above, custom download files can be produced in a text format, but it is not possible to produce binary format files, such as PDF, using an XSL stylesheet alone.
In order to provide the ability to produce such files, it is possible to define a custom download that uses a post processing step to convert an intermediate, text file into the final binary file.
To request a post processing step the download format should be specified in two parts, separated by a full stop e.g. xslfo.pdf. The first part (before the full stop) is used to define the name of the stylesheet i.e. search-results-xslfo.xsl. The second part (after the full stop) is used to define the post processor. The post processor is specified in the registry, in the WebService hive with a key of the form SearchResultsDownloadConvertTo'post-processor'. For the example format above, the key would be SearchResultsDownloadConvertToPDF.
The value assigned to the post processor registry key should be the path to a command line application, accessible on the iConsole application server, which simply takes the names of an input file and an output file as parameters and performs the conversion from one to the other.
Note: If the particular post-processor requires additional parameters to function correctly, a batch file should be produced that incorporates these.
Note: If the conversion may take some time it is possible to increase the time that the iConsole will wait for the converter to respond. By default the timeout is set to 90s but this can be overridden using the registry value SearchResultsConverterTimeoutSecs.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|