Sunday, March 20, 2011

XML Bursting : Concurrent Output file and sent file are not the same fonts in Linux

Hi All

During the implementation of XML Bursting I found the issue:
The Concurrent Output and the pdf file that was sent to customer are different.

What was the problem? XML Bursting xdo.cfg file was missed.

Here the steps to fix this issue:

1. Copy the fonts that you use  to $AF_JRE_TOP/jre/lib/fonts folder. You can take them from windows fonts folder. If the linux fonts folder not exists, please create it.
2. Create xdo.cfg  file in  $AF_JRE_TOP/jre/lib
Here the example of my file:
=====================================================
<config version="1.0.0" xmlns="http://xmlns.oracle.com/oxp/config/">
<!-- Properties -->
<properties>
<!-- System level properties -->
<!-- PLEASE SELECT A VALID TEMPFILE DIRECTORY!!! --><property name="system-temp-dir">/hgold/applmgr/11510/jojo/11.5.0/templates</property>
<!-- PDF compression -->
<property name="pdf-compression">true</property>

<!-- PDF security ->
<property name="pdf-security">false</property>
<property name="pdf-open-password">user</property>
<property name="pdf-permissions-password">owner</property>
<property name="pdf-no-printing">true</property>
<property name="pdf-no-changing-the-document">true</property>
-->
</properties>
<!-- Font setting -->
<fonts>
<!-- Windows  font -->
<font family="Times New Roman" style="italic" weight="normal">
<truetype path="/usr/java/j2sdk1.4.2_17/jre/lib/fonts/TIMESI.ttf" />
</font>
<font family="Times New Roman" style="italic" weight="bold">
<truetype path="/usr/java/j2sdk1.4.2_17/jre/lib/fonts/TIMESBI.ttf" />
</font>
<font family="Times New Roman" style="normal" weight="normal">
<truetype path="/usr/java/j2sdk1.4.2_17/jre/lib/fonts/TIMES.ttf" />
</font>
<font family="Times New Roman" style="normal" weight="bold">
<truetype path="/usr/java/j2sdk1.4.2_17/jre/lib/fonts/TIMESBD.ttf" />
</font>
</fonts>
</config>
======================================================
3. Restart Concurren Manager to take the xdo.cfg changes.
4. Recheck the issue.

No comments:

Post a Comment