Using Zen Reports - InterSystems Documentation

More documents

Recommendations

Info

Troubleshooting Zen Reports• The Caché installation directory is /Applications/Cach81• The Web Server is configured on the default port, 80• The name of the Caché for Macintosh server machine is myproThese instructions assume that FOP is the XSL-FO to PDF rendering tool, but similar instructionsapply to RenderX:1. Use these Caché Terminal commands to point Caché to FOP on the Macintosh machine:zn "%SYS"Set ^%SYS("zenreport","transformerpath")="/Applications/fop-0.94/fop"2. Run the report from the browser on Windows; for example:http://mypro.local:80/csp/app/ZENApp.MyRep.cls?$MODE=pdfThe PDF report should display.If the PDF report does not display, you can test for problems in the FOP installation as follows:1. Make sure the /Applications/Cach81/mgr/temp directory on the Caché server is empty.2. Enter the following URI in the browser on Windows:http://mypro.local:80/csp/app/ZENApp.MyRep.cls?$MODE=pdf&$LOG=1&$NODELETE=13. Rename the XML and XSL output files from this run by entering the following commands on theMacintosh where Caché is installed:cd /Applications/Cache81/mgr/tempmv *.xsl test.xslmv *.xml test.xml4. While still in the /Applications/Cach81/mgr/temp directory, run FOP with the files test.xmland test.xsl, by entering the following command:/Applications/fop-0.94/fop -xml test.xml -xsl test.xsl -pdf test.pdf5. Examine the console output for any errors. If there are so many errors that they run off the consolescreen, you can redirect the console output to the file test.log as follows:/Applications/fop-0.94/fop -xml test.xml -xsl test.xsl -pdf test.pdf > test.log6. Try to view the output file test.pdf.74 Using Zen Reports
Viewing Intermediate Files9.2 Viewing Intermediate FilesSeveral URI query parameters are available to help in troubleshooting Zen reports. These parametersallow you to view and save the intermediate and final files generated by the transformation pipeline.These files might include generated XSL or XSLFO files, text files containing error messages fromthe XML parser, or the final XHTML or PDF files that result from the completed pipeline.Note:For information about how to supply report options as URI query parameters, and how tohandle side effects that may occur in some browsers, see the chapter “Zen Reports from aWeb Browser.” In that chapter, the table URI Query Parameters for Zen Reports lists allpossible URI query parameters. This chapter lists only a few of them.The diagnostic query parameters are:• $LOG — Use with $MODE=html or $MODE=pdf to view one of the intermediate files.• $MODE — Choose a value (tohtml, toxslfo, xslfo) to view one of the intermediate files.• $NODELETE — Save intermediate files to the general Caché temporary directory.• $REPORTNAME — Save intermediate files with the name and location of your choice.• $USETEMPFILES — Save generated XSL files in the CSP directory for your application.To enable diagnostic query parameters to produce a text file listing errors detected by the Saxon parser,you must configure Zen reports with the location of the Saxon .jar file. You can do this from the CachéTerminal command prompt. Depending on the version number for the Saxon parser, the requiredcommand may be:set ^%SYS("zenreport","saxjar")="c:\saxon65\saxon.jar"Or:set ^%SYS("zenreport","saxjar")="c:\saxon\saxon8.jar"The diagnostic query parameters for Zen reports produce most of the useful diagnostic files withoutthis command, but do not produce the additional messages from the Saxon parser unless you provideone of the commands described here.9.2.1 The $LOG Query ParameterWhen specifying $MODE=html or $MODE=pdf as described in “Zen Reports from a Web Browser,”you can also set the query parameter $LOG=1. This allows you to view the output of the transformationfrom XML to XHTML or the transformation from XML via XSLT to XSL-FO to PDF, respectively.For example:Using Zen Reports 75
Page 1 and 2:
Using Zen ReportsVersion 2008.210 O
Page 3 and 4:
Table of ContentsAbout This Book ..
Page 5 and 6:
List of FiguresHow a Zen Report Cla
Page 7:
About This BookThis book explains h
Page 10 and 11:
Building a Zen Report1.1 Preparing
Page 14 and 15:
Building a Zen Report14. Compile th
Page 16 and 17:
Building a Zen ReportTutorial Sales
Page 19 and 20:
2Zen Report Class ParametersA Zen r
Page 21 and 22:
EMBEDXSLA user can override the cur
Page 23 and 24:
Zen Report Class ParametersPRIVATEA
Page 25:
Zen Report Class ParametersUSETEMPF
Page 28 and 29:
XData ReportDefinition}field="Num"c
Page 30 and 31: XData ReportDefinitionAttributeexpr
Page 32 and 33: XData ReportDefinitionAttributefiel
Page 34 and 35: XData ReportDefinitionThe median of
Page 36 and 37: XData ReportDefinitionAttributename
Page 38 and 39: XData ReportDefinitionAlthough the
Page 40 and 41: XData ReportDefinitionAttributebrea
Page 42 and 43: XData ReportDefinitionThe following
Page 44 and 45: XData ReportDefinition...In this ca
Page 46 and 47: XData ReportDisplay• Style and ap
Page 48 and 49: XData ReportDisplayAttributenamesty
Page 50 and 51: XData ReportDisplayAttributenameDes
Page 52 and 53: XData ReportDisplayth.myTable {back
Page 54 and 55: XData ReportDisplayReport Display A
Page 56 and 57: XData ReportDisplayAttributenameDes
Page 58 and 59: XData ReportDisplayAttributeDisplay
Page 60 and 61: XData ReportDisplayAttributespecial
Page 64 and 65: XData ReportDisplayAttributelayoutD
Page 68 and 69: Charts in Zen ReportsAttributedataG
Page 70 and 71: Zen Reports from a Web Browser• T
Page 72 and 73: Zen Reports from a Web Browser• T
Page 75 and 76: 7Configuring Zen for PDF OutputWhen
Page 77 and 78: 8Zen Reports from a Command LineBef
Page 79: 9Troubleshooting Zen ReportsThis ch
Page 83 and 84: Viewing Intermediate Files9.2.3 The
Page 85 and 86: You can run a session like this wit
Page 87 and 88: IndexSymbols$DATASOURCE, 14$EMBEDXS
Page 89: PRIVATE, 17Qqueryreport, 30queryCla
show all

Using Zen Reports - InterSystems Documentation

Create successful ePaper yourself

Delete template?

Save as template?