An Oracle blog about BI Publisher

Bookbindng Samples

I have finally found a home for the bookbinding samples I have put together in support of my white paper on Bookbinding.

OTN has a great newish sample code site where you can create code samples to share with the community. In their own words: Welcome to the Oracle Sample Code public repository, where Oracle Technology Network members collaboratively build and share sample applications, code snippets, skins and templates, and more.

Note the word 'templates' I read that as an open invitation to share your latest and greatest!

If you have template samples or code snippets that you think would benefit the wider BIP community please create new code samples and let me know the link and I'll ensure they get promotion through the blog.


You just need an OTN account to get started. Scroll down for the BI Publisher entry.

I'll be pushing some more samples and snippets in the near future, its a great centrally managed repository. Finally, Oracle has somewhere to get code and files hosted.

The two samples I have created cover the book binding function from a couple of angles:

  • Oracle BI Publisher Bookbinding Examples - this walks you through a series of examples that show you how to create the bookbinding control files to generate the final bound document.

  • Oracle BI Publisher Bookbinding Demonstration - this is a sample J2EE application that demonstrates how to create an HTML/servlet combination to allow users to make sub document selections and then the document features e.g. TOC, page numbering, cross links, etc you would like added to the final document

I'd be very interested in any feedback. Happy Binding!

Join the discussion

Comments ( 8 )
  • Jorge Anicama Wednesday, May 12, 2010
    Hi Tim,
    Good post on Book binding.
    One comment though concerning the site:
    Just to make aware all those people willing to share code that they would be abiding to the following:
    4. Your Content
    You agree that you will only upload, share, post, publish, transmit, or otherwise make available (“Share”) on or through the Site Content that you have the right and authority to Share and for which you have the right and authority to grant to Oracle all of the licenses and rights set forth herein. By Sharing Content, you grant Oracle a worldwide, perpetual, royalty-free, irrevocable, nonexclusive, fully sublicensable license to use, reproduce, modify, adapt, translate, publish, publicly perform, publicly display, broadcast, transmit and distribute the Content for any purpose and in any form, medium, or technology now known or later developed.
  • Barry Markovic Friday, June 4, 2010
    Is it possible to take an FSG XML formatted report and post it within OBIEE as part of a "book" or as part of a dashboard? If the answer is yes, what are the steps to do so? Are there any tutorials or white papers on this topic? Thanks for any information you can provide on this topic.
  • guest Wednesday, August 3, 2011

    Has this been updated anywhere to reflect the changes incorporated in OBIEE 11g? That would be really helpful especially if there's been significant bookbinding enhancements.

  • ny_bi_dev Tuesday, July 23, 2013

    The download link for BookBinderExamples.zip is not working!

  • Tim Tuesday, August 6, 2013

    Links updated

  • Manish Tuesday, November 5, 2013

    The download link for BookBinderExamples.zip is not working!

  • Manish Tuesday, November 5, 2013

    The download link for BookBinderExamples.zip is not working!

  • Colin Tuesday, February 18, 2014

    How do I get the page numbers in the pagenum.rtf to appear in the footer so we can put then at the bottom of the bound documents. tried using word to put then in the footer the bookbinder crashes. Tried adding


    <?end body?>

    before the commands to add the page number crashed the bookbinder.

    The bookbinder seems very picky about this template file.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.