Setting Up Document Conversion

Some documents -- including PDFs and those from Microsoft Office -- are supported in a preview view in Jive. To convert content from its native format into a form that can be previewed without altering the original document, you'll need the Document Conversion module, which you'll need to deploy on a server that is separate from your core Jive production instances.

We support converting the following file types on Office 2003 and 2007:

Note: For information about managing conversion attempts and reconverting documents if necessary, see Managing Document Conversion.
Here is an overview of the steps you'll perform to set up Document Conversion:
  1. Set up a production instance of the Jive application (see Installing the Linux Package). You'll be devoting one node in your installation to document conversion.
  2. Install the Jive platform RPM on your conversion node machine. Then disable the services not related to document conversion. For more information, see Installing and Configuring on the Conversion Machine
  3. If you're using version 6.0.2 or higher, download and install the correct RPM for the PDF2SWF utility on the conversion node machine. You can find the RPMs here.
    Note: On the document conversion node, use the --replacefiles flag if you receive the following error when installing either the jive_sbs rpm or jive_pdf2swf.
    file /usr/local/jive/bin/pdf2swf from install of rpm_name conflicts with file from package other_rpm_name the flag
  4. Enable the Document Conversion service using the following commands:
    chkconfig jive-docconverter on
    service jive-docconverter start
  5. On the application node, configure the application to communicate with the conversion machine(s).
  6. If you want to set up secure communication to the conversion machine, see Setting Up SSL for Document Conversion.