APEX Printing

What are my options for printing from APEX other then BI. I looking to print reports and screen shots. Im also trying to keep costs low.. Thanks in Advance

We have had the same problem
good app but realy poor paper output. We are now having to export to access and do the paper reports from there. Kinda defeats the purpouse.
The Apache Fop way is ok but it will only give you very basic reporting.
Using APEX Std reporting.
BI looks good but for us the cost would have been £56,000 ...a tad expensive when access is only £200
The other way mentioned is PL PDF
Off handI think this is a couple of hundered quid, We had a quick look at it and it looks like it could have prospects
good luck
Bjorn

Similar Messages

Cannot print a PDF using the Oracle APEX print feature

Hi,
I work from a Wondows 7 workstation.
I have Adobe FlashPlayer 11 installaed on that workstation.
I can open a regular *.pdf file.
I have the following configuration for my Oracle APEX application:
Report Printing:
Print Server Protocol: Advanced (requires Oracle BI Publisher)
Print Server Protocol: HTTP
Print Server Host Address: the IP address of my BI Publisher server
Print Server Port: 9704 (from installation of BI)
Print Server Script: /xmlpserver/convert
On the page (that is an interactive report) that I want to print, it is configured with:
Download:
PDF option is checked.
When I click on Action -> Download -> PDF for this page, I get the error:
report_customers_region.pdf file can not be opened because the file type is not supported or because it is damaged (because, for example as an e-mail attachment is not sent and correctly decoded)
Does someone has an idea what the problem is and where I should investigate further?
Thanks and Kind Regards.

Well, is the PDF actualyl allowing to be printed? Check File --> Properties in Reader/ Acrobat.
Mylenium

OC4J Install for APEX printing

Hi,
I have an Oracle 11g Enterprise Edition insalled on my Windows 2008 server. I am now trying to get the report printing option to work within APEX. One of the options was to use OC4J + Apache FOP to get this going. However, I'm hitting problems when trying to access my OC4J instance.
If I just do http://localhost:8888/ it works, but when I put in http://localhost:8888/em, it falls over with a 404 error.
Has anybody seen this before? I've tried finding something related but they all seem to point to Oracle iAS. I'm assuming that the OC4J that comes with the database qualifies as a stand-alone config?
If I can't use the application server console, is there any other way to deploy the .war file? Can I just use the admin_client.jar and install the war? Anybody hit any problems with this too?
Thank you,
Chandini

I have recently been deploying some war files without using the console. I did the following:
- in the j2ee_home/config: updated the application.xml and added a new <web-module> entry with my specific details
- in the j2ee_home/config: updated the default-web-site.xml and added a new <web-app> entry with my specific details
- copy the war in to the j2ee_home/applications folder
- restart the oc4j container
This has been working for me using OC4J 10.1.3.

SIMPLE APEX PRINTING IN 4.0

Question: Using APEX 4.0 I am finding that I am having a world of hurt trying to get very BASIC printing setup. I am not using BI and do not need PDF or RFT formats. Essentially, I would like to be able to create Interactive reports that do three things:
1) Provide a "Print" link for the user
2) Pass any interactive parameters to the print so the filtering and such are maintained
3) Disable the Interactive Search bar on the printer friendly page.
Working through the documentation I can't find any clear references to just printing a report on a page. I have found how to setup the printing for using the APEX_ADMIN site and I have found the "printer freindly" template and have been able to work with that. The rest is coming across very cryptic.
I thought these would be simple but every solution I try seems very "gummy". I have added a print link to the Navigation Bar but it always references the only a single page. So I added a print button to each page (which was easy) but it doesn't pass the Search and Filter parameters to the printer friendly view of the data.
I have also noticed that only about 2 pages of output go to the printer when I have about 800 records on the screen (that one is weird).
I am a very good PL/SQL programmer so if the solution is code-based, please hit me with it.
My platform is APEX 4.2 on Windows 2003 Server - Oracle XE
Any help would be great!
Thanks

Thanks for everyones help.
I have basically figured out the system now. here is what I have (maybe help someone else).
ON THE SERVER
1) I installed a standalong OC4J instance on my server
2) I connect to the admin control panel (port 8888 was the default)
3) I deployed toe FOP war file that comes with APEX
4) I started the OC4J
IN APEX ADMIN:
I logged into the APEX_ADMIN app and set the printing up in the Manage Instance section:
MANAGE INSTANCE ---> INSTANCE SETTINGS --> REPORT PRINTING TAB
STANDARD
HTTP
LOCALHOST
8888
/fop/apex_fop.jsp
Then I saved that.
IN APEX:
I The created a simple app with a Interactive Report. I edited the report to allow the DOWNLOAD section to use PDF.
When I ran the report and used the ACTION menu in the search bar, I was able to download to PDF and print the result. All parameters set in the search passed right through!
I then created another report of the "classic" variety and enabled printing and set the results for INLINE and PDF. That also worked fine.
Hope this helps.

Apex Print Functionality

Hi,
We want to enable print functionality on our Apex Engine. The issue that we are running into is that :-
1. Oc4J is a required component for "Apache FOP" and it is covered by development license.
2. BI Publisher is non free.
At this point we are looking for a Open source product to build our print functionality.
Am I missing anything or do we have any other options that we can explore?
Please let us know! Thanks

You can use the HTTP Server of the Database, you need to install it on the CD Companion of the Database, then you configure some files like httpd.conf and dads of the HTTP Server.
So you can print to PDF

APEX printing advice

I have some complex reporting that was previously done in Oracle Reports. I had tried the Report Query/Report Layout method in APEX, but it does not seem to have enough flexibility that the Data Template from BI would have.
I have seen some entries about integrating BI with APEX thru Web Service. Not sure if this is where I should be looking or not. I have all of my report parameters on my APEX page. I would need to pass them to BI (without the need for BI logins created etc.). Anybody did something like this?

Hello,
The following resources should help to determine if you are on the right track:
http://tylermuth.wordpress.com/category/bi-publisher/
http://www.oracle.com/technology/products/database/application_express/pdf/integrating_oracle_application_express_with_bi_publisher.pdf
Hope this helps,
Arie.
Please remember to mark appropriate posts as correct/helpful. For the long run, it will benefit us all.

APEX Print Attributes for Interactive Reports versus Reports

The Print Attirbutes tab for Interactive Reports does not have the Enable Report Printing option that the same tab does for Reports. The Enable Reports option when set to Yes" puts a print link on the Reports page. Since, the option doesn't appear for under the Print Attributes tab for Interactive Reports, how can I get a print link appear on an Interactive Report page?

Hi,
Those links are visible to end user in action menu -> Download
Br, Jari

Creating a print button to call a Report Query and pass filters

If i use the REPORT QUERY option in APEX 4 to create an statement that is the same one used in an interactive report, can I create a link or button to the REPORT QUERY and pass all the session and filter information from the interactive report to the report query?
This way I can have the interactive report screen where the user can do all sorts of modifications and such and then pass those to the REPORT QUERY so I can call that from a custom link or button.
You may ask "why does he need another print button?"
Answer: I am using a view that has some embedded HTML tags to format the output really nicely. The HTML download version created by the interactive reports works beautifully. The customer also wants a PDF version (meh) which does not render the HTML tags and actually echos them as part of the text. I found that I can create another view that uses the CHR function to create all the breaks and such I was doing with HTML and these do render properly in PDF. So, I figured just have 2 reports: 1 Interactive and 1 using a REPORT QUERY. I just want to call the REPORT QUERY version but use the Interactive Search form to set all the parameters.
Or, am I over thinking this and there is an easier method?
I made a previous post where I showed how I got the APEX printing to work and i hoped that helped someone out - fixing this issue would put the whole thing to rest.
Thanks

Is BI Publisher desktop (MS Word add-in) a possibility? This would allow you to use MS Word to create your output template (RTF) that would result in a properly formatted PDF. Of course, you'd have to right an updated version of the query without HTML embedded. Just thinking outside of the box.

Configuring Export to PDF and Report Printing

Greetings
using Apex 3.1,Oracle 10g Release 2 on Hp-Unix
i have got to Configure
Export to PDF and Report Printing
please mention Documents or Links for the Configuration
thanks a lot

Hello ahuja
I would start here...
[APEX Printing|http://www.oracle.com/technology/obe/apex/apex31nf/apex31rpt.htm]
Kind regards
Simon Gadd

Fop printing returns 0 byte pdf files

Hi,
Spent the whole day trying to get a PDF document out of APEX using Fop, but no luck sofar. Interestingly "fop" in Dutch means: tease, fool, trick, hoax, badger, vex, swindle, hoodwink
I've tried OC4J/Apache Fop:
http://www.oracle.com/technology/products/database/application_express/html/configure_printing.html#05
I've tried Cocoon Fop:
http://carlback.blogspot.com/2007/03/apex-cocoon-pdf-and-more.html
Both OC4J and Cocoon work fine when trying their sample pages.
I've setup the Apex print server parameters pointing first to the oc4j printserver and then to the cocoon printserver.
This is as far as the documentation gets me. How do I get a document produced? Here is what I did:
I created a form with a sql_query report, entered some query (select * from user_tables) and enabled PDF printing.
Both OC4J and Cocoon produce a zero byte pdf document.
I wonder if the printserver a being called at all since no activity is logged in ...\cocoon\WEB-INF\logs\cocoon.log
How do I find out what is going on. Is Apex calling the print server at all? What logs to check, any additional info to be sent to logfiles?
Another strange behaviour. When I turned on printing for an existing report region the print link has the following URL:
http://ngdwsrv/pls/apex/f?p=107:2:278743463863218506:FLOW_XMLP_OUTPUT_R3825265334087776571_nlThis results in : 404 The requested URL /pls/apex/f was not found on this server.
Rene

Hello!
Help me, please!
I need to print reports in PDF.
What I did:
1 I installed Apache Tomcat 6.0.14
2 I installed Cocoon 2.1.10
All works fine! http://localhost:8080/Cocoon opened OK
3 I copied fop_post to \apache-tomcat-6.0.14\webapps\cocoon\ , now I have apache-tomcat-6.0.14\webapps\cocoon\fop_post\sitemap.xmap
4 In apex I choose : Oracle BI Publiser - Standart Support
print server host address 192.168.1.112
print server port 8080
print server script \cocoon\fop_post\
Now I make simple report consists from 1 column from a simple table like emp table, and choose.
Output format - PDF
Report Layout - Default Report Layout
Apex is English.
I read that can be problem if I'll write use point in (example) 0.5 and everywhere I used 1.
When I run the programm and click print button I have error message : Acrobat could not open 'a[1].pdf' because is either not a supported file type or because
the file has been damage ......
I saved this file and opened with text editor but there was nothing and size of this file is 0 kb.
PLEASE, explain me where is problem and how to solve it?
Thank you!!!

Handling Special characters in call to apex_util.download_print_document

I am developing some custom reports that I need as PDFs. My client does not have BI Publisher so I am doing some custom xsl to generate the reports. I test as I develop by using a simple web page that POSTs to the apex_fop.jsp. Then I also test by saving the XML and XSL to the database and then query them and using apex_util.download_print_document, passing the XML and XSL as a blob and clob respectively.
The issue I have is an ampersand. The following line
<td>this & that</td>works great when sent via the web page post to apex_fop.jsp. However when the exact same file is saved to the database and run through apex_util.download_print_document and opened with Adobe Reader, it says the file has been damaged and the oc4j error log for the fop application says
oracle.xml.parser.v2.XMLParseException: Unexpected EOF
What's the difference between the two calling methods, and how do I get ampersands in the data using apex_util.download_print_document.
Thanks.

Larry,
When you submit your request to apex_fop.jsp through a simple web page, and include escaped characters such as "&", then your web browser takes care of encoding the & in your string. In APEX, you have a number of different ways to generate your PDF documents. You can use report queries, classic reports, interactive reports, or call the print API directly. When using any of the built-in reports (classic, interactive, report queries), the APEX engine generates the XML document holding your data for you. The APEX engine also takes care of escaping your data, so when you have a value like "this & that" in any of your queries columns, the engine escapes this to "this & that". The engine additionally encodes characters such as &, which gets encoded into %26. And after that, processing is handed of to an interface between APEX and the print rendering engine. This interface simply takes the incoming XML data and stylesheet / template and makes an HTTP request to the rendering engine (e.g. BI Publisher, apex_fop.jsp, etc). It does not do any encoding, since that had been done in a previous step. The APEX print API is calling this interface directly, which means, that the incoming XML data already needs to be encoded prior to calling the APE. So if you change your string "this & that" to "this %26amp; that", it should work as expected. We will have to look into whether we need to enhance the print API to allow for encoding the XML data supplied by the developer.
Hope this helps,
Regards,
Marc

How to Replicate Standard Alternating Colors using XSL-FO??

Hi All
I am using Apex_3.1, Apache fop and Standard Report Printing to produce PDF reports. We would like to replicate the theme 12 (Blue) standard alternating colors in our PDF output.
I do realise that this involves modifying the xsl-fo and have tried putting color attributes in the xsl-fo (Generic Columns). I know I can just put the color in the apex print settings but that doesn't give me the alternating colors.
Edited by: Keith Jamieson on Oct 22, 2009 4:04 PM

I believe this is the section of the xsl template that needs modified.
                   <fo:table-body>
                        <xsl:for-each select=".//ROW">
                           <fo:table-row >
                                  #PRN_TEMPLATE_BODY_ROW#
                           </fo:table-row>
                        </xsl:for-each>
                     </fo:table-body>and I have found this example which appears to do what I require.
<xsl:template name="table.row.properties">
<xsl:variable name="tabstyle">
    <xsl:call-template name="tabstyle"/>
</xsl:variable>
<xsl:variable name="bgcolor">
    <xsl:call-template name="dbfo-attribute">
      <xsl:with-param name="pis" select="processing-instruction('dbfo')"/>
      <xsl:with-param name="attribute" select="'bgcolor'"/>
    </xsl:call-template>
</xsl:variable>
<xsl:variable name="rownum">
    <xsl:number from="tgroup" count="row"/>
</xsl:variable>
<xsl:choose>
    <xsl:when test="$bgcolor != ''">
      <xsl:attribute name="background-color">
        <xsl:value-of select="$bgcolor"/>
      </xsl:attribute>
    </xsl:when>
    <xsl:when test="$tabstyle = 'striped'">
      <xsl:if test="$rownum mod 2 = 0"
        <xsl:attribute name="background-color">#EEEEEE</xsl:attribute>
      </xsl:if>
    </xsl:when>
</xsl:choose>
</xsl:template>Every time I try and add that section to the code, I end up breaking it and not getting any pdf output :(
eg my latest attempt
<?xml version = '1.0' encoding = 'utf-8'?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:xlink="http://www.w3.org/1999/xlink">
      <xsl:variable name="_XDOFOPOS" select="''"/>
      <xsl:variable name="_XDOFOPOS2" select="number(1)"/>
      <xsl:variable name="_XDOFOTOTAL" select="number(1)"/>
    <xsl:variable name="_XDOFOOSTOTAL" select="number(0)"/>
     <xs1:variable name="rownum" />
<xsl:choose>
    <xsl:when test="$bgcolor != ''">
      <xsl:attribute name="background-color">
        <xsl:value-of select="$bgcolor"/>
      </xsl:attribute>
    </xsl:when>
    <xsl:when test="$tabstyle = 'striped'">
      <xsl:if test="$rownum mod 2 = 0">
        <xsl:attribute name="background-color">#EEEEEE</xsl:attribute>
      </xsl:if>
    </xsl:when>
</xsl:choose>
   <xsl:attribute-set name="padding">
      <xsl:attribute name="padding-bottom">0.25pt</xsl:attribute>
      <xsl:attribute name="padding-top">0.25pt</xsl:attribute>
   </xsl:attribute-set>
   <xsl:attribute-set name="text">
      <xsl:attribute name="text-align">start</xsl:attribute>
      <xsl:attribute name="orphans">2</xsl:attribute>
      <xsl:attribute name="start-indent">0.0pt</xsl:attribute>
      <xsl:attribute name="linefeed-treatment">preserve</xsl:attribute>
      <xsl:attribute name="padding-top">0.0pt</xsl:attribute>
      <xsl:attribute name="end-indent">0.0pt</xsl:attribute>
      <xsl:attribute name="padding-bottom">0.0pt</xsl:attribute>
      <xsl:attribute name="height">0.0pt</xsl:attribute>
      <xsl:attribute name="widows">2</xsl:attribute>
   </xsl:attribute-set>
   <xsl:attribute-set name="align-left">
      <xsl:attribute name="text-align">left</xsl:attribute>
   </xsl:attribute-set>
   <xsl:attribute-set name="align-center">
      <xsl:attribute name="text-align">center</xsl:attribute>
   </xsl:attribute-set>
   <xsl:attribute-set name="align-right">
      <xsl:attribute name="text-align">right</xsl:attribute>
   </xsl:attribute-set>
   <xsl:attribute-set name="footer">
      <xsl:attribute name="text-align">right</xsl:attribute>
      <xsl:attribute name="start-indent">5.4pt</xsl:attribute>
      <xsl:attribute name="end-indent">5.4pt</xsl:attribute>
   </xsl:attribute-set>
   <xsl:attribute-set name="text_2">
      <xsl:attribute name="start-indent">5.4pt</xsl:attribute>
      <xsl:attribute name="end-indent">23.4pt</xsl:attribute>
   </xsl:attribute-set>
   <xsl:attribute-set name="text_20">
      <xsl:attribute name="height">13.872pt</xsl:attribute>
      <xsl:attribute name="end-indent">5.4pt</xsl:attribute>
   </xsl:attribute-set>
   <xsl:attribute-set name="text_0">
      <xsl:attribute name="end-indent">5.4pt</xsl:attribute>
   </xsl:attribute-set>
   <xsl:attribute-set name="page-header">
      <xsl:attribute name="color">#PAGE_HEADER_FONT_COLOR#</xsl:attribute>
      <xsl:attribute name="font-family">#PAGE_HEADER_FONT_FAMILY#</xsl:attribute>
      <xsl:attribute name="white-space-collapse">false</xsl:attribute>
      <xsl:attribute name="font-size">#PAGE_HEADER_FONT_SIZE#pt</xsl:attribute>
      <xsl:attribute name="font-weight">#PAGE_HEADER_FONT_WEIGHT#</xsl:attribute>
   </xsl:attribute-set>
   <xsl:attribute-set name="page-footer">
      <xsl:attribute name="color">#PAGE_FOOTER_FONT_COLOR#</xsl:attribute>
      <xsl:attribute name="font-family">#PAGE_FOOTER_FONT_FAMILY#</xsl:attribute>
      <xsl:attribute name="white-space-collapse">false</xsl:attribute>
      <xsl:attribute name="font-size">#PAGE_FOOTER_FONT_SIZE#pt</xsl:attribute>
      <xsl:attribute name="font-weight">#PAGE_FOOTER_FONT_WEIGHT#</xsl:attribute>
   </xsl:attribute-set>
   <xsl:attribute-set name="body-font">
      <xsl:attribute name="height">12.0pt</xsl:attribute>
      <xsl:attribute name="font-family">#BODY_FONT_FAMILY#</xsl:attribute>
      <xsl:attribute name="white-space-collapse">false</xsl:attribute>
      <xsl:attribute name="font-size">#BODY_FONT_SIZE#pt</xsl:attribute>
      <xsl:attribute name="font-weight">#BODY_FONT_WEIGHT#</xsl:attribute>
   </xsl:attribute-set>
   <xsl:attribute-set name="page-number">
      <xsl:attribute name="height">13.872pt</xsl:attribute>
   </xsl:attribute-set>
   <xsl:attribute-set name="header-font">
      <xsl:attribute name="height">#HEADER_FONT_SIZE#pt</xsl:attribute>
      <xsl:attribute name="font-family">#HEADER_FONT_FAMILY#</xsl:attribute>
      <xsl:attribute name="white-space-collapse">false</xsl:attribute>
      <xsl:attribute name="font-size">#HEADER_FONT_SIZE#pt</xsl:attribute>
      <xsl:attribute name="font-weight">#HEADER_FONT_WEIGHT#</xsl:attribute>
   </xsl:attribute-set>
   <xsl:attribute-set name="border">
      <xsl:attribute name="border-top">#BORDER_WIDTH#pt solid #BORDER_COLOR#</xsl:attribute>
      <xsl:attribute name="border-bottom">#BORDER_WIDTH#pt solid #BORDER_COLOR#</xsl:attribute>
      <xsl:attribute name="border-start-width">#BORDER_WIDTH#pt</xsl:attribute>
      <xsl:attribute name="border-start-color">#BORDER_COLOR#</xsl:attribute>
      <xsl:attribute name="border-start-style">solid</xsl:attribute>
      <xsl:attribute name="border-end-width">#BORDER_WIDTH#pt</xsl:attribute>
      <xsl:attribute name="border-end-color">#BORDER_COLOR#</xsl:attribute>
      <xsl:attribute name="border-end-style">solid</xsl:attribute>
   </xsl:attribute-set>
   <xsl:attribute-set name="cell">
      <xsl:attribute name="background-color">#BODY_BG_COLOR#</xsl:attribute>
      <xsl:attribute name="color">#BODY_FONT_COLOR#</xsl:attribute>
      <xsl:attribute name="padding-start">5.15pt</xsl:attribute>
      <xsl:attribute name="vertical-align">top</xsl:attribute>
      <xsl:attribute name="padding-top">0.0pt</xsl:attribute>
      <xsl:attribute name="padding-end">5.15pt</xsl:attribute>
      <xsl:attribute name="number-columns-spanned">1</xsl:attribute>
      <xsl:attribute name="height">0.0pt</xsl:attribute>
      <xsl:attribute name="padding-bottom">0.0pt</xsl:attribute>
   </xsl:attribute-set>
   <xsl:attribute-set name="header-color">
      <xsl:attribute name="background-color">#HEADER_BG_COLOR#</xsl:attribute>
      <xsl:attribute name="color">#HEADER_FONT_COLOR#</xsl:attribute>
   </xsl:attribute-set>
   <xsl:template match="/">
      <fo:root>
         <fo:layout-master-set>
            <fo:simple-page-master master-name="master0" margin-left="66.6pt" margin-right="66.6pt" page-height="#PAGE_HEIGHT#pt" page-width="#PAGE_WIDTH#pt" margin-top="36.0pt" margin-bottom="36.0pt">
               <fo:region-before region-name="region-header" extent="54.0pt"/>
               <fo:region-body region-name="region-body" margin-top="54.0pt" margin-bottom="54.0pt"/>
               <fo:region-after region-name="region-footer" extent="54.0pt" display-align="after"/>
            </fo:simple-page-master>
         </fo:layout-master-set>
         <fo:page-sequence master-reference="master0">
            <xsl:variable name="_PW" select="number(#PAGE_HEIGHT#)"/>
            <xsl:variable name="_PH" select="number(#PAGE_WIDTH#)"/>
            <xsl:variable name="_ML" select="number(72.0)"/>
            <xsl:variable name="_MR" select="number(72.0)"/>
            <xsl:variable name="_MT" select="number(90.0)"/>
            <xsl:variable name="_MB" select="number(90.0)"/>
            <xsl:variable name="_HY" select="number(36.0)"/>
            <xsl:variable name="_FY" select="number(36.0)"/>
            <xsl:variable name="_SECTION_NAME" select="string('master0')"/>
            <fo:static-content flow-name="region-header">
               <fo:block xsl:use-attribute-sets="text text_2 text_0 #PAGE_HEADER_ALIGNMENT#">
                  <fo:inline xsl:use-attribute-sets="page-header">#PAGE_HEADER#</fo:inline>
               </fo:block>
            </fo:static-content>
            <fo:static-content flow-name="region-footer">
               <fo:block xsl:use-attribute-sets="text footer">
                  <fo:inline xsl:use-attribute-sets="body-font page-number">
                     <fo:page-number/>
                  </fo:inline>
               </fo:block>
               <fo:block xsl:use-attribute-sets="text text_2 #PAGE_FOOTER_ALIGNMENT#">
                  <fo:inline xsl:use-attribute-sets="page-footer">#PAGE_FOOTER#</fo:inline>
               </fo:block>
            </fo:static-content>
            <fo:flow flow-name="region-body">
               <fo:block xsl:use-attribute-sets="padding">
                  <fo:table start-indent="0.0pt">
                     <xsl:variable name="_XDOFOPOS2" select="number(1)"/>
                     <xsl:variable name="_XDOFOTOTAL" select="number(1)"/>
                     #PRN_TABLE_CELLS#
                     <fo:table-header>
                        <fo:table-row>
                           #PRN_TEMPLATE_HEADER_ROW#
                        </fo:table-row>
                     </fo:table-header>
                     <fo:table-body>
                        <xsl:for-each select=".//ROW">
                           <xs1:choose>
                              <xs1:when> test = ".//ROW mod 2 = 0"
                           <fo:table-row bgcolor=#EEEEEE>
                                  #PRN_TEMPLATE_BODY_ROW#
                           </fo:table-row>
                              </xs1:when>
                              <xs1:when> test = ".//ROW mod 1 = 0"
                           <fo:table-row bgcolor=#DDDDDD>
                                  #PRN_TEMPLATE_BODY_ROW#
                           </fo:table-row>
                               </xs1>
                        </xsl:for-each>
                     </fo:table-body>
                  </fo:table>
               </fo:block>
               <fo:block xsl:use-attribute-sets="text text_2 text_20">
                  <fo:inline id="{concat('page-total-', $_SECTION_NAME, $_XDOFOPOS)}"/>
                  <fo:inline id="{concat('page-total', $_XDOFOPOS)}"/>
               </fo:block>
            </fo:flow>
         </fo:page-sequence>
      </fo:root>
   </xsl:template>
</xsl:stylesheet>

Page breaks in (html) printed apex report

I am having a strange problem that appears to be related to APEX page template.
I have a report that is html generated by a PL/SQL function. I need to have page breaks in the printed report at specific locations. I am adding this style to the html output of the function:
<STYLE>
DIV.pageBreak { page-break-before: always; }
</STYLE>
and I insert this at the locations I need breaks:
< D I V CLASS="pageBreak"/>
(without the spaces in DIV)
(found this technique here: http://www.unagibay.com/DesktopDefault.aspx?tabindex=1&tabid=100&itemid=1821 )
This works perfect when I run the report in IE, but FireFox is "ignoring" the page breaks. However, if I take just the output of the PL/SQL function in an html doc, FireFox works fine (breaks at the proper places). This makes me believe something related to the "page wrapper" content generated by APEX causes FireFox to not handle the breaks.
I have tried copying and editing the Popup and Printer Friendly page templates, but I either remove too much and the page doesn't render, or the page breaks don't work.
My questions for the APEX gurus are:
1. Is there an "approved" way to get page breaks in the printed version of an APEX report, or is there a better way to do what I need to do.
2. What is the minimum contents for a page template (what can I safely remove).
Thanks,
Bill

Hi Owen,
the page breaks are inserted before/after the section. Expand the report structure window and make sure that the properties window is open below. Once you click on the section part, you will see where you can insert the page breaks - the check boxes will appear in the properties.
yes on the second part - just insert the page break between the data providers and then repeat the header for the data provider on the pages (also check boxes on the properties tab)
Good luck

Apex Listener prints ### instead of cyrillic symbols

Hi everybody!
Apex listener (2.0.4/) prints ### insead of cyryllic symbols when printing to PDF from APEX.
In Glassfish log I found next entries:
[2013-10-02T10:31:44.040+0600] [glassfish 4.0] [WARNING] [] [org.apache.fop.apps.FOUserAgent] [tid: _ThreadID=20 _ThreadName=http-listener-1(3)] [timeMillis: 1380688304040] [levelValue: 900] [[
Glyph "н" (0x43d, afii10079) not available in font "Helvetica".]]
[2013-10-02T10:31:44.040+0600] [glassfish 4.0] [WARNING] [] [org.apache.fop.apps.FOUserAgent] [tid: _ThreadID=20 _ThreadName=http-listener-1(3)] [timeMillis: 1380688304040] [levelValue: 900] [[
Glyph "с" (0x441, afii10083) not available in font "Helvetica".]]
[2013-10-02T10:31:44.040+0600] [glassfish 4.0] [WARNING] [] [org.apache.fop.apps.FOUserAgent] [tid: _ThreadID=20 _ThreadName=http-listener-1(3)] [timeMillis: 1380688304040] [levelValue: 900] [[
Glyph "т" (0x442, afii10084) not available in font "Helvetica".]]
[2013-10-02T10:31:44.040+0600] [glassfish 4.0] [WARNING] [] [org.apache.fop.apps.FOUserAgent] [tid: _ThreadID=20 _ThreadName=http-listener-1(3)] [timeMillis: 1380688304040] [levelValue: 900] [[
Glyph "ь" (0x44c, afii10094) not available in font "Helvetica".]]
I have tried other fonts (Times-Roman and Courier), but result is the same.
Can anybody answer how to teach Apex Listener to work with cyrillic symbols?
My system is: Windows XP SP3, Glassfish 4, Apex Listener 2.0.4, Apex 4.2.3., Oracle XE 11g.

Finnaly, with help from other forums, solution is found:
1. In defaults.xml add entry:
<entry key="fop.configfile">C:\some_path\fop.xml</entry>
2. In fop.xml:
<fop version="1.0" encoding="UTF-8">
<renderers>
   <renderer mime="application/pdf">
   <filterList>
   <value>flate</value>
   </filterList>
<fonts>
<directory>C:\WINDOWS\FONTS</directory>
<auto-detect/>
</fonts>
   <stroke-text>false</stroke-text>
   </renderer>
</renderers>
</fop>
3. restart glassfish.

Report Printing: APEX 4.01 - APEX Listener - WebLogic 10.3.3

We have some report printing issues...
Our configuration is APEX 4.01 using the APEX Listener with WebLogic 10.3.3.
The first issue is that under "Print Attributes" the following is listed in red under "Printing":
"Report printing is currently not available, there is no print server configured."
The second one is that we need to print pdf format and I have not found a solution for doing this with the APEX Listener and WebLogic. I saw that the FOP solution for the APEX Listener didn't make it into the current release... Is there any way to do pdf type reports with the current APEX listener technology?
The third issue is that in the demo app when running a report there is a "Error loading file:" type error with "FLOW_FLASH_CHART" and apex_util.flash as part of the url.
Any help would be appreciated...
Thanks!
- Scott

I deployed in WebLogic the fop.war that came with APEX 4.0.1 and it got rid of the error message, but when I tried to download a report as pdf, I got an error saying it was corrupted or invalid. I downloaded the file it produced and opened it in a text editor. It was a small html type file with the following URL:
ORA-20001: The printing engine could not be reached because either the URL specified is incorrect or a proxy URL needs to be specified.
When I go to the URL that I think it should be going to based on what I put into Instance settings> Report Printing, I get:
Compilation of JSP File '/apex_fop.jsp' failed:
apex_fop.jsp:5:18: The import oracle.xml cannot be resolved
<%@ page import='oracle.xml.parser.v2.XMLDocument'%>
^------------------------------^
apex_fop.jsp:6:18: The import oracle.xml cannot be resolved
<%@ page import='oracle.xml.parser.v2.XSLProcessor'%>
^-------------------------------^
apex_fop.jsp:7:18: The import oracle.xml cannot be resolved
<%@ page import='oracle.xml.parser.v2.XSLStylesheet'%>
^--------------------------------^
apex_fop.jsp:8:18: The import oracle.xml cannot be resolved
<%@ page import='oracle.xml.parser.v2.DOMParser'%>
^----------------------------^
apex_fop.jsp:12:1: XMLDocument cannot be resolved to a type
XMLDocument v_doc;
^--------^
apex_fop.jsp:13:1: XSLStylesheet cannot be resolved to a type
XSLStylesheet v_xsl = null;
^----------^
apex_fop.jsp:15:1: DOMParser cannot be resolved to a type
DOMParser parser = new DOMParser();
^------^
apex_fop.jsp:15:28: DOMParser cannot be resolved to a type
DOMParser parser = new DOMParser();
^------^
apex_fop.jsp:16:1: XSLProcessor cannot be resolved to a type
XSLProcessor processor = new XSLProcessor();
^---------^
apex_fop.jsp:16:30: XSLProcessor cannot be resolved to a type
XSLProcessor processor = new XSLProcessor();
^---------^
apex_fop.jsp:21:13: XSLStylesheet cannot be resolved to a type
v_xsl = new XSLStylesheet(new java.io.StringReader(request.getParamet

APEX Printing

Similar Messages

Maybe you are looking for