PDFMerge Client for FileConverterPro (FCpro) – extends the PDF(/A) converter-service by new functions

Based on PDFMerge we brought out a PDFMerge Client for the FileConverterPro (FCpro) Server. It makes it possible to produce document conversions and compilations as PDF or PDF/A from any workplace. The PDF-conversion and processing of the documents is done via a FileConverterPro Server-service reachable in the local network or via the internet, which is addressed with SOAP / REST through HTTP(S). With that resources can be used collectively more efficient: the local computers get relieved, applications installed centrally (MS-Office, DWG/DXF converter or an Abbyy OCR Engine) get installed centrally and used together and don’t have to be installed on the local workplaces.

Differences to a local installation of PDFMerge:

  • The PDF or PDF/A conversion doesn’t take place locally but via HTTP(S) communication through a central FCpro service.
  • No local installation of MS-Office, DWG/DXF converter and Abbyy OCR Engine needed – because the central FCpro service is used.
  • No configuration of own local conversion profiles needed – selection of centrally predefined FCpro profiles.
  • Document preview only possible for image and PDF documents.
  • More compact setup – 65MB to 240-500MB – because the PDF converter and the OCR engine aren’t installed locally.
  • Simplified usage because less configuration possibilities are available.
  • Cost-effective option to produce PMT / PMTX files on any workplace to process them via a FCpro Server or PDFMerge.

1_PDFMerge für FCpro - Auswahl der FileConverterPro Verarbeitungsprofile  2_Context Menü für die eingefügten Dokumente  3_Kommunikations Einstellungen und Default Profilauswahl für den FileConverterPro Server

New features for the FileConverter Pro through the PDFMergeClient _ FCpro

The PDFMerge Client for the FCpro not only allows pure PDF or PDF/A conversions but also offers the following functions:

  • Creates merged PDF and PDF/A documents from single documents which are structured via bookmarks
  • Setting of the PDF info fields, PDF-open parameters and PDF rights and opening password.
  • Pagination and text stamp with a multiplicity of variables and configuration options.
  • Underlay / Overlay of PDF stationery
  • TOC – table of contents generated from the bookmarks automatically (planned).

After the installation of the PDFMerge Client for the FileConverterPro (FCpro) Server the processing can be tested immediatly with our FCpro testserver which is freely reachable via the internet, because the connection data needed is already predefined in our setup. The commandline parameters of PDFMerge are also valid, whereby the profiles refer to the FileConverterPro profiles of the configured FCpro server.

Download – PDFMerge Client for FileConverterPro (FCpro) – about 60MB >>>

PDFMerge commandline parameters

PDFMerge can also be called with commandline parameters. Especially interesting thereby is the possibility to run the processing “silent” without user interface. With that e.g. overall PDF’s can be produced directly without user interaction through PMT (XML) files which are created from own applications. But it is also possible to work completely without template file only through a root folder to process the whole folder structure with any contained files.

Example:

“C:\program files\MAY COMPUTER\PDFMerge\PDFMerge.exe” “C:\1.pmt” /s

c:\1.pmt = PDFMerge template file – optional also a root folder can be specified

/s = processing runs “silent” – without user interface

As first parameter the file name of the PMT or PMTX template file or the path to a folder has to be provided like in the example above. If the path to a folder is provided the folder and all contained subfolders and files get read in and processed. If a folder is used the “pdfpath” parameter should be used for defining the destination PDF file. If this parameter isn’t specified the PDF file gets created on the same level as the folder chosen for processing and with the same name and there it could be that the required rights for the creation are missing.

The following additional parameters can be used:

/pdfpath=“<output path / name of the PDF file which should be created> ”  – if this is missing the definition from the template file is used

/profile=“<profile name for the processing>” – if not specified the last used profile is used

/gfi=“<PDFExport profile (=GFI) names >” name of the saved PDFExport profile or path to a GFI file