Aloaha Software

With Aloaha it is possible to automatically apply a barcode to PDF via Hotfolder

1. Right click on your grey Aloaha System Tray Icon and disable “Interactive”. Please note that Admin Rights are required to de-activate “Interactive” and you need at least a server license.
2. Your Barcode Folder is <InstallDir>\BarcodeFolder or the one defined in HKLM\Software\Aloaha\pdf\BarCodeFolder.
3. In your barcode folder you need a file BarCode.ini. If it does not exist you need to create one. It will be created automatically with default settings when placing the first .pdf file in that folder.
4. With BarCodeType in the .ini file you define which type the barcode will have:
   1. Code39 (or Code 3 of 9)
   2. EAN-13
   3. Code128
   4. PostNet
   5. Interleaved 2 of 5
5. The value of the barcode will be the filename. With the plugin PlugInObjectName you can define a plugin to deliver a different barcode value.

Aloaha added native support for the new V3 generation of the Berman Bundesdruckerei/D-Trust Smartcards/eIDs.

Following Aloaha Products can make use of the new cards WITHOUT having to install a special driver or middleware:

Aloaha Cardconnector (Middleware)

Aloaha PDF Suite (create digitally signed PDFs)

Aloaha PDF Signator and Multisignator (sign PDF documents)

Aloaha Smartlogin (Login to Windows with or without Active Directory).

Following V3 D-Trust Cards are supported:

• D-TRUST Card V3.0 advanced 2ga
• D-TRUST Card V3.0 standard 2ga
• D-TRUST Card V3.0 batch 2ga
• D-TRUST Card V3.0 multi 2ga

If you are running Aloaha in non-interactive mode (server or enterprise version required) Aloaha checks a couple of hotfolder for specific tasks. For example it prints every doc/docx dropped into the autoprint folder to Aloaha for PDF conversion.

In the enterprise version you can also utilize the APIs mentioned in:

http://blog.aloaha.com/2013/02/07/print-docdocxrtf-files-automatically-with-aloaha-api/

and

http://blog.aloaha.com/2012/03/21/convert-doc-docx-documents-directly-to-pdf-via-aloaha-api/

Please note: To switch Aloaha into non interactive mode you need to have admin rights and the correct Aloaha license. Then just right click on the Aloaha system try icon and disable the option “Interactive”

Who has not come accross the bugging Winword message “The paper size of section 1 is different from the printer page size” when automating document prints?

With our Aloaha printing APIs it is very easy to go around that message. Just use the following code:

Dim Aloaha
set Aloaha = CreateObject(“AloahaPrinterControl.Control”)

Call Aloaha.Doc2Aloaha(“c:\test.docx”,”Aloaha PDF Printer”)

set Aloaha = nothing

Please note that in the Aloaha installation folder you find the tool “PrintWinWordDocCMD.exe”. Just give it as a parameter the path to the file to be printed and it will print the document to Aloaha.

PrintWinWordDocCMD.exe is the ideal tool to define it as Doc/Docx Print Verb in your registry!

You can download Aloaha from http://www.aloaha.com/download/aloaha_pdf.zip

Please have also a look at: http://blog.aloaha.com/2012/03/21/convert-doc-docx-documents-directly-to-pdf-via-aloaha-api/

In many cases customer are using our MSI packages to roll out the Aloaha PDF Signator. To save the user from configuring the signature settings manually it is possible to configure them with a small VBS Script. Below you find such as script as a sample.

PDF Signature Settings Script

By using digitally signed documents, paper workflows which require signatures may be replaced by electronic workflows. This saves time (cost) and increases security, reliability and helps to comply with authoritative requirements and compliance regulations like 21 CFR Part 11 or Sarbanes-Oxley. Form based workflows, applications and approval processes or electronic invoices are only a few examples of attractive application areas for digital signatures.

With the new Aloaha PDF Signator and Aloaha PDF Suite it becomes even easier to implement signature based workflows since multiple signatures can be applied to ANY existing PDF document. Such PDF Documents do NOT require an prior preparation or special form fields!

Below you find an example of an PDF Document which was created with the Aloaha PDF Suite and several times signed/certified and  time stamped (RFC 3161 compliant):

SHA256_Signed_Document

Aloaha Signed PDF Screenshot

If you want to sign existing PDFs please download: https://dl.dropbox.com/u/20338532/beta/aloaha_signator.zip

The following evaluation key can be used for the PDF Signator until christmas 2012: 3614AC99D-B0E850503-962806132-E2BCD4D7C-A0055E75E-0E2FDD4E0

To create signed PDFs you can download the PDF Suite from: https://dl.dropbox.com/u/20338532/beta/aloaha_pdf.zip

The following evaluation key can be used for the PDF Suite until christmas 2012: 640BFC31A-A4C3E4041-9449B4C5C-F5A6AEB1D-B217CFC72-F5F1AA406

With the Aloaha PDF Suite Server (http://www.aloaha.com/wi-software-en/aloaha-pdf-suite-server1.php) it is possible to print out PDF fully automatic and without user intervention. You just need to drop them into the dedicated hotfolder.

First setup the Aloaha PDF Suite to run non interactive. To do so right click on the grey system tray icon and disable Interactiv.

You could also run Aloaha as a windows service. Just remove the Aloaha Autostart/Startup shortcut and then open the service control center (services.msc). Now configure the PDF Suite Service to start automatically and start the service.

If you look into the Aloaha installation folder (usally <program files x86)\Wrocklage you find the subfolder autoprint. Every PDF dropped there will be printed to the configured printer. Please note that in the autoprint folder there are a couple of subfolders. Every folder is dedicated to a specific printer. So ideally you use those subfolders!

Man people whish to configure properties of the used Hardcopy printer. That can be done in hklm\software\aloaha\printer (globally) or hklm\software\aloaha\printer\<printer name> (per printer). Please note that the registry Hive on 64 Bit machines is: SOFTWARE\Wow6432Node\Aloaha

Settings can be configured directly in the registry as explained below OR just with the tool AutoPrintConfig (located in the installation folder)

Following settings are possible (please create values as DWord if they do not exist):

1. PaperSize
   1 to 68, DMPAPER (Win32 API DEVMODE data structure)
2. PaperLength
   in tenths of millimetres
3. PaperWidth
   in tenths of millimetres
4. Copies
   Number of copies
5. PrintQuality
   1 = high, 2 = medium, 3 = low, 4 = draft
6. Color
   1 = monochrome, 2 = color
7. Duplex
   1 = simplex, 2 = vertical duplex, 3 = horizontal duplex
8. Collate
   0 = no, 1 = yes
9. Bin
   1 to 15, DMBIN (Win32 API DEVMODE data structure)
10. MediaType
    1 = standard, 2 = transparency, 3 = glossy
11. Orientation
    1 = portrait, 2 = landscape
12. AutoRotateCenter
    1 = Rotate pages to fit on the output medium, and center on the page
13. PageScaling
    0 = None, 1 = Fit to paperm, 2 = Shrink large pages

Please contact info@aloaha.com for further information.

If you print with SAP to the Aloaha PDF Printer you might experience errors like: “Device Aloaha PDF Printer not capable to set paper size (9)”. It could also happen that SAP reports “printed OK” but never issued any print job.

The above symptoms are caused by wrong settings in SAP itself.

1. Make sure that your SAPWIN driver as configured as MS Windows driver.

2. SAPGUI normally sends the print data as RAW data but modern printer such as Aloaha require EMF Data.

To force the SAPGUI to send the data as EMF data add the following registry key:

HKEY_CURRENT_USER\Software\SAP\SAPlpd\SAPLPD
Type: String
Name: SwinDataType
Value: EMF

For the PDF automailer functionality of the Aloaha PDF Suite and Aloaha Multisignator it was possible to use WebDAV in the past. Since WebDav became something of the past WebDAV has been replaced with Exchange Web Services (EWS).

To be able to use this functionality please note that you need to have .NET 3.5 installed. Furthermore your Exchange Server needs to be configured to accept requests via HTTPS.

The PDF Suite can be downloaded from http://www.aloaha.com/download/aloaha_pdf.zip

The Multisignator can be downloaded from http://www.aloaha.com/download/aloaha_multisignator.zip

Many times we are asked how to enable / disable the option “Disable Mailing” of the PDF Suite.

The setting is saved in Software\Aloaha\pdf\skipmail

Setting it to one instructs Aloaha NOT to send out any emails. If you set the optional manually ideally you set it in HKCU\Software\Aloaha\pdf\skipmail and HKLM\Software\Aloaha\pdf\skipmail