1) How to obtaining XML Publisher version ?
a) From the template/output in word/pdf format
If the output file (doc/pdf) file is generated then it can be used.Otherwise template stored inside can be used.
To get the XML Publisher version from template stored
Responsibility: XML Publisher Administrator
Tab: Templates
search for a pdf/RTF template
choose Preview
save the PDF file to locally
Open the PDF file in Adobe Acrobat
Menu File
Document Properties
Description: PDF Producer XML Publisher x.x.x.
Open the RTF file in MS Word
Menu File
Document Properties
Comments: PDF Producer XML Publisher x.x.x.
2)
Large Data Report Recommendations
When the report output is more than 10,000 pages the chances are that OPP gets timed out waiting for the request to complete.
Reduce the large data by running it for less data ( only one source at a time)
Run the report for the whole data but keep NO report output. Most of the times customer runs this for the whole data to check for errors.
Improve the performance of the concurrent request by using parallel processing.
Improve the performance of the OPP Manager
Modify the timeout parameters
3) if the log file of the reports says
Beginning post-processing of request <request number> on node <node name> at 24-feb-2012 22:12:45. Post-processing of request <request number> failed at 24-feb-2012 22:12:46 with the Error message: One or more post-processing actions failed. Consult the OPP service log for details.
OR
'****Warning!!! Due to high volume of data, got out of memory exception...***
'****Please retry with scalable option or modify the Data template to run in scalable mode...***
OR
java.lang.OutOfMemoryError: Java heap space
Solution:
1. Increase the memory from CP Definition:
Go to System Administrator responsibility.
Navigate to Concurrent - > Program - > Define.
Search for the report in the Concurrent Program (CP) window.
Set the Options field to "-Xmx2048M" (Note: Do not miss the dash before the X)
Press Save
Bounce the Concurrent Manager (optional).
2. Run the report with ScalableFlag = Yes, DebugFlag = Y with increased memory.
2.1 How to set P_SCALABLE_FLAG :
Access the System Administrator responsibility.
Navigate to Concurrent > Program > Define.
Search for the report (e.g., Account Analysis Report), "XLAAARPT" is the short name in the CP window.
Click on Parameters button.
Move to the last parameter.
Add a new parameter called ScalableFlag with the following:
Parameter- P_SCALABLE_FLAG
Description - ScalableFlag
Enabled - Check
Default Type - Constant
Default Value - Yes
Prompt - P_SCALABLE_FLAG
Token - ScalableFlag (Case sensitive. Give this exact value)
2.2 How to set P_DEBUG_FLAG
Access the System Administrator responsibility.
Navigate to Concurrent > Program > Define.
Search for the report (e.g., Account Analysis Report), "XLAAARPT" is the short name in the CP window.
Click on Parameters button.
Move to the last parameter.
Add a new parameter called DebugFlag with the following:
Parameter- P_DEBUG_FLAG
Description - DebugFlag
Enabled - Check
Default Type - Constant
Default Value - Y
Prompt - P_DEBUG_FLAG Token - DebugFlag (Case sensitive. Give this exact value)
When you run the report with P_SCALABLE_FLAG=Yes and P_DEBUG_FLAG=Y, the log file should include the following:
a. The report SQL
b. It should also show Calling XDO Data Engine and the Scalable mode on.
XML Generation is fine but OPP fails with "java.lang.OutOfMemoryError" exception.
1. Set the following properties from XML Publisher Administration:
Responsibility=>Administration UI
General => Temporary directory => \tmp
This could be any directory with full read and write access
FO Processing=>
Use XML Publisher's XSLT processor =>true
Enable scalable feature of XSLT processor=> true
Enable XSLT runtime optimization=>true
2. The above properties can be set to "xdo.cfg" as well.
<property name="xslt-xdoparser">True</property>
<property name="xslt-scalable">True</property>
<property name="xslt-runtime-optimization">True</property>
