PDFSign Server – PDF, PDF / A and ZUGFeRD provided by folder monitoring with signature / time stamp

The PDFSign Server is based as well as our other PDF signature applications – the Web service, the CL command line application and the eDocPrintPro PDFSign plugin on the PDFSign .NET component as a common basis.

The PDFSign server is installed as a service on an MS Windows computer and is able to monitor one or more input folders via configured jobs. The incoming PDFs in the folders are recognized and processed either immediately or at a specific time and stored in the associated output folder.

 

PDFSign Server features:

  • MS-Windows service to sign or timestamp PDF, PDF / A and ZUGFeRD.
  • PDF / A and ZUGFeRD conformity is maintained.
  • Selection of signature parameters via stored PDFSign signature profiles.
  • One or more input folders can be monitored by job definition.
  • Processing the files via filter – name, created (date, time), changed (date, time)
  • Sorted processing (name or time).
  • Processing all PDF’s from a folder / subfolder structure – Options: Create the folder structure in the target folder, delete the folder structure after processing.
  • Definition of the file name in the target directory via text and variables (date, time, counter, original name).
  • Start processing via file events (immediately) as well as over time interval (min) or date / time (once, daily, weekly).

         

    Download – PDFSign Server – Signing PDF through Order Tracking >>>

PDFSignCheck – Check PDF signatures via web service (REST / SOAP)

PDFSignCheck – is a service which can be installed under MS Windows and which has a REST / SOAP web service interface to check signed PDF documents and to read out their signature parameters.

Scope – validation of electronic evidence:

In order to pay the customer for PDF invoices z.b. via a web application to give the opportunity to check whether an email sent as a PDF invoice really comes from your own company or to check whether the PDF document has not been changed or manipulated.

Using a valid PDF signature can ensure that the PDF document has not been tampered with, as any change invalidates the signature immediately.

With the help of the PDFSignCheck application, it can be checked whether the document / signature is valid and therefore unchanged and on the basis of the signature criteria stored on the PDFSignCheck server, it can also be checked whether the document was issued / signed by the company itself.

 

     

Definable criteria – AND shortcut for “Ok” / “not ok”

  • Signature status (0 – unknown, 1 – valid signature, 2 – file can not be opened, 3 – PDF not signed, 5 – signature invalid, 6 – validity unknown)
  • Issuer of the certificate / signer
  • reason
  • location
  • ContactInfo
  • Filter / Sub-Filter / algorithm
  • Revision
  • page
  • Signature Text

processing flow:

PDFSignCheck is installed under MS Windows as a service and provides a REST / SOAP web service interface for other applications. PDF files are transmitted via the web service and checked using a PDFSignCheck profile stored on the server. As a result, a file is created in JSON format that can be downloaded and processed further. The JSON file contains information about the read signature as well as the result of the check (“Ok”, or “not ok”).

In addition to the service, two C # sample programs / VS projects – one for REST and one for SOAP incl. EXE and source code are installed. Thus, the PDFSignCheck service can be easily tested or show the examples of how the functions can be integrated into your own applications.

 

     

Notice:

  1. Root certificates and revocation lists are constantly updated, therefore the computer installed on the PDFSignCheck should also have an active internet connection.
  2. By default, PDFSignCheck runs as a Windows service under the “System Account”, the user interface for configuring the application under the logged-in user. Each user and the computer itself use their own memory for the certificates. In order to use the same certificate store, the same user account should be used for the service as the logged-on user with whom the configuration is performed.

Download – PDFSignCheck – PDF Signaturen prüfen über REST / SOAP >>>

PDFSign CL – Command line application to sign PDF, PDF / A and ZUGFeRD as well as timestamp them

PDFSign CL – allows PDF, PDF / A or ZUGFeRD documents to be signed and / or timestamped. PDFSign CL is based on our PDFSign – .NET signature component and provides its functionality in the form of a command line application.

Features PDFSign CL:

  • Command line application based on the PDFSign – .NET signature component
  • PDF, PDF / A and ZUGFeRD PDFs can be provided with an electronic signature and / or an electronic time stamp.
  • PDF / A, ZUGFeRD compatibility is retained.
  • Processes – single files, lists of text files, folders, and entire folder structures.
  • Configuration and selection of signature settings via PDFSign profile files.
  • Logging the processing.

 

Download – Readme – Hilfe – Beschreibung der verfügbaren Parameter DE >>>
Download – Readme – Help – Description of the available parameters EN >>>
Download – PDFSign CL – Command line application to sign PDF >>>

PDFSign CL Client – Command line application for the PDFSign service

PDFSign CL Client – is a command line application to transfer PDF, PDF / A documents via a REST web service interface to a PDFSign service to sign and / or provided with a time stamp and then back to the calling client to transfer back.

The PDFSign CL client is free of charge, available as an add-on to our PDFSign service and can be used as a client application on any MS Windows computer.

Features PDFSign CL Client:

PDFSign Service – PDF and PDF / A via SOAP & REST – Web service with signature or timestamp

On the technical basis as the FileConverterPro (FCpro) there is now also a Windows service to provide PDF or PDF / A documents via a SOAP or REST web service interface with a timestamp or with an electronic signature.

The service is based on our PDFSign .NET signature component, is installed as a Windows service and offers the same SOAP and REST web service interface as our FileConverterPro (FCpro) or AutoOCR.

Along with the main application, two C # sample projects for SOAP and REST including source code and executable applications are being installed. With the help of these examples, all PDF signatures and PDF timestamps provided via the PDFSign service can be tested and quickly integrated into your own applications.

                    

Download – PDFSign Service  ~21MB >>>

Transfer license – MOVE

Move license (to new PC)

This option allows to transer a license to a different PC. Input of UserID und Passwort is necessary! Product will remain as demo version on your PC.

OLD PC: ProductActivationManager | select license | „Move License“ Button | Username / Password | OK

NEW PC: ProductActivationManager | select application | „Activate Application“ Button | Username / Password | select license | OK

iPaper – Automated installation

An automated iPaper installation consists of the following parts:

  1. The installation of the version of GhostScript suitable for the iPaper version.
  2. Installing the iPaper application.
  3. Retrieve the license and activate the software.
  4. Configuration / distribution of the presets.

Normally our setups are executed as EXE. The EXE setup contains both the 32bit and the 64bit MSI of the application. With the EXE installation certain automated steps are executed automatically. The installation prerequisites (eg .NET Runtime, presence of the correct GhostScript version, etc.) are checked and if components are not available or not in the correct version, they are downloaded from the Internet and pre-installed. Likewise, the EXE setup decides whether on the computer the 32 or 64bit version must be installed.

Automated installation requires MSI installation packages. If the MSI packages are used, the installation prerequisites must be established correctly. It is also necessary to specify which version (32 or 64bit) has to be installed.

The “iPaperNET Client.exe” setup contains the required MSI files – but these must be extracted from the EXE.

Extract MSI from EXE:

  • /extract <path>Extracts the MSI contained in the EXE into the specified path. If the path contains spaces, it must be surrounded by quotation marks.
  • Beispiel: “C:\iPaperNET Client.exe” /extract “C:\temp” – This command-line command extracts the MSI to the folder “C: \ temp”

A description of the parameters can be found here >>>

Depending on the operating system, the 32 or 64bit GhostScript version must be installed – for iPapers up to version 2.99.1 the GhostScript version 9.18.1 is required.

Example Extracting the MSI and installing 64bit versions:

  • “C:\temp\iPaperNET Client.exe” /extract c:\temp
  • msiexec.exe /i “C:\temp\gs918.1×64.msi” /quiet
  • msiexec.exe /i “C:\temp\iPaperNET Client.x64.msi” /quiet

Retrieve the iPaper License:

To retrieve the licenses from our license server, this can either be done interactively via the installed PAM (Product Activation Manager) or via Commandline

  • “C:\Program Files (x86)\Common Files\MAYComputer\LicMan.exe/ACTIVATE MULTI=“AUTO” USERID=“user” USERPW=“passwort” APPID=“2PC” /SILENT

In the example, “user” and “password” must be replaced by the PAM login information. The AppID “2PC” is used up to iPaper version 2.99.1.

iPaper Configure and distribute presets:

All settings of the iPaper application are stored in the iPaper.xml file in the default path (C:\Users\%user%\AppData\Roaming\iPaper.NET\iPaper.xml)

If it is not found there then:

  1. Checked if an iPaper.xml exists in the iPaper installation folder
  • If it is found there, we automatically copy it to the default path
  • If it can not be found in the installation folder, then 2.) is executed.

2. It is checked whether the xml file exists in the ProgramData directory C: \ ProgramData \ iPaper.NET \ iPaper.xml

  • If it is found there, we automatically copy it to the default path
  • If the file is not found there, an iPaper.xml file with predefined (fixed-coded) default settings is generated and stored in the standard path.

To specify default settings, we recommend variant 2.)

In the iPaper.XML you can use absolute path data or system variables.

Download – Example iPaper.XML

In this example, the system variables% HOMEPATH% and% APPDATA% were used. This makes general presets and actions which can be used universally for all users.

! Note that the iPaper.XML is always written / overwritten when you exit iPaper. So you have to replace the application before you want to replace it. Otherwise the file will be overwritten with the last values from the user interface when you exit iPaper.

FileConverterPro – MS-Office conversion and PDF / A

To convert MS Office formats (Word, Excel, PowerPoint, Visio …) to PDF / A, the FCPro provides either “direct” conversion or conversion based on a MS Office version installed on the FCpro computer.

We recommend using PDF/A as the output format, either the “direct” or the conversion via MS-Office 2013/2016 in the 32 or 64bit version. We have found in test that certain MS Word documents can not be converted to valid PDF/A documents via MS-Office 2010.

SmartTransformer – FileConverterPro integrated with Alfresco ECM

SmartTransformer is an integration of FileConverterPro (FCpro) with Alfresco ECM / DMS. The SmartTransformer consists of an Alfresco extension, an own, lean server that knows the context of the Alfresco documents and handles the processing and updating as well as the FileConverterPro.

High-quality previews and better alfresco performance:

Why does viewing previews affect Alfresco performance? Alfresco automatically generates document thumbnails and previews from Office documents. This mechanism leads to complaints among the users, especially in larger environments. On the other hand, Alfresco becomes unstable and slow because it is busy with conversions or even waiting for stuck conversion jobs. On the other hand, the users are dissatisfied with the quality of the previews – the presentation mostly does not correspond to the one in MS-Office or its expression.

The Smart Transformer tackles the problem at its roots and store any office conversion to an independent, robust and scalable transformation of service that converts Office documents with MS Office libraries. The previews are as if the user had saved the document in Microsoft Office as PDF.

There is avoidance of multiple conversions, through intelligent caching in the SmartTransformer. In the same process, it is also a real relief to the Alfresco server (repository) by outsourcing all transformation tasks (text extraction, preview, thumbnail generation) to a standalone service / server. No CPU is loaded on the Alfresco server. Thus it is reliable and robust: conversion jobs are managed by the SmartTransformer of a database.

The SmartTransformer solves bottlenecks in the Alfresco architecture:

  • Transformation tasks that can be performed by FCPro are simulated in Alfresco by placeholder documents and are instead entered as a “job” in a persistent job queue and transferred to the FCPro. As soon as FCPro has completed the transformation, the placeholder is replaced by the real transformation. From the point of view of Alfresco no load is created by the transformation since the result is immediately returned by the placeholder. The job queue also reboots and possible problem documents can be easily identified. In the Alfresco standard, transformations are implemented by Java threads, which can lead to scaling problems on a regular basis.
  • Multiple transformations of the same binary object as the Alfresco Transformer are avoided because they are recognized by the SmartTransformer. In the same way, jobs are automatically deleted during fast updates on an Alfresco document, if they have not yet started, or the jobs are replaced by new ones.
  • Unlike the Alfresco standard implementation, the transformation is already proactive when creating or modifying a document, not just when Alfresco Share is accessed. In this case, identically configurable sets are created with only one transformation (thumbnail, preview, gallery-view, …) so that the Office document has to be opened only once.

In Alfresco, a JavaScript Api is also available for the SmartTransformer.

The SmartTransformer was developed by our Alfresco development partner ECM4u.

Inquiries about the product can be directed directly to:

ecm4u GmbH
Heiko Robert [heiko.robert@ecm4u.de]
http://www.ecm4u.de
Hölderlinplatz 2b
70193 Stuttgart

t: +49 (711) 912775-72
m: +49 (176) 347475-72
f: +49 (711) 912775-80

eDocPrintPro free and PDF/A-1b, 2b, 3b & ZUGFeRD Version 3.25.3 available

Create several printersWith the “eDocPrintPro Tool”, additional additional printers with any names can be created.

With version 3.25.2, there were 2 errors that were fixed with version 3.25.3:

  1. When the first additional printer was created, a new printer monitor application was created and started automatically. This additional printer monitor, however, has 100% loaded the computer until the restart.
  2. Only a second additional printer could be created and no more. The other printers were created, but the required monitor application was not automatically started and not entered in the registry. Thus these printers were present in the printer list, but could not be used because no output file was created or the save under dialog was not high.

Create several eDocPrintPro printers – please note:

  1. The default printer created by the setup – “EDocPrintPro” must not be renamed or removed
  2. Additional printers can be created with any names and settings – The program “eDocPrintPro Tool” must be used to create this printer.
  3. For each additionally created printer a <print name> Monitor.exe is created, started and entered in the registry under “RUN”.
  4. If no PDF file is created for one of the created printers or if there is no “Save as” dialog, check whether the xxxMonitor.exe is present and started, or if the start has been entered correctly under the RUN key in the registry.

      

Download – eDocPrintPro free Version

Download – eDocPrintPro PDF/A & ZUGFeRD

GhostScript 9.21 Setup