The entry contains a list of emitter descriptions separated by a semicolon. The emitter description must have the format type and the emitter id separated by a colon. For example, the PDF emitter is described as:
3 Add your emitter description to the beginning of the <entry name="RenderFormatEmitterIdMapping"> tag:<!-- The value is "render_format:emitter_ID" separated by ";", for example, pdf:org.eclipse.birt.report.engine.emitter.pdf;
xml:org.eclipse.birt.report.engine.emitter.xml -->MyCSV:org.eclipse.birt.report.engine.emitter.csv;
html:org.eclipse.birt.report.engine.emitter.html;
xhtml:com.actuate.birt.report.engine.emitter.xhtml;
pdf:org.eclipse.birt.report.engine.emitter.pdf;
postscript:org.eclipse.birt.report.engine.emitter.postscript;
xls:com.actuate.birt.report.engine.emitter.xls;
ppt:org.eclipse.birt.report.engine.emitter.ppt;
pptx:com.actuate.birt.report.engine.emitter.pptx;
doc:org.eclipse.birt.report.engine.emitter.word;
docx:com.actuate.birt.report.engine.emitter.docx
3 Restart the iServer to make it load the new plug-in in its classpath:
Restart Actuate iServer <Release> from Start→Settings→Control Panel→Administrative Tools→Services, as shown in Figure 30-2.
If you use a separately deployed Information Console, you must also restart Apache Tomcat for Actuate Information Console <Release>.
Figure 30-2 The following procedures show how to export a BIRT report to a custom format in different products. The procedures use an example format, MyCSV.
|
|
Copyright Actuate Corporation 2012 |