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.
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:
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
The Aloaha Time Stamping Authority can be run as a plugin in your local web server OR as a standalone product with inbuilt webserver.
In case you run the stand alone TSA please have a look at the internal Web Server Registry settings on: http://blog.aloaha.com/2012/10/15/aloaha-webserver-registry-settings/
The TSA settings are configured in: HKEY_CURRENT_USER\Software\Aloaha\TSA
PFX_Path defines the path to the PFX to be used. This key is ONLY used if UseCertfromStore is set to 0
UseCertfromStore defines if the TSA uses a time stamping certificate from the users current user store of the PFX file defined in PFX_Path.
PFX_Serial does not need to be set if a PFX is being used. Aloaha will set it automatically. It contains the certificate serialnumber
PFX_Serial should be set if a certificate is used from the current user store and the current user store contains several time stamping certificates. It it is NOT set Aloaha will use the first Time Stamping enabled certificate found in the store.
TSACount contains the number of time stamping tokens issued. The start value is set automatically and is built from the date and time of the local machine.
TSA_OID_ASN contains the OID used in the issued time stamping token. If not set Aloaha will set it to its default value.
UseMachineStore defines if the Current User Store or Local Machine store is used. Default is 0. If you set this to 1 the Local Machine Store is used. This setting is only for the expierenced user!
SNTPServer contains the NTP Server to be contacted to synchronize the local machine clock
NTPPollingTime defines the time in minutes between every NTP Sync
It is a very frequent requirement that the Aloaha PDF Creator generates dynamically the PDF filenames and the path. With the Alaoha Saving Filter it is pretty easy to configure:
- right click on the grey Aloaha PDF Suite System Tray Icon and disable “Interactive”
- right click on the grey Aloaha PDF Suite System Tray Icon and enable “Parse PDF for Commands”
- right click on the grey Aloaha PDF Suite System Tray Icon and choose “Configure Savings Filter” from “Advanced Settings”
- The new dialog has three input fields. In the first field you configure the root path, in the second field a regular expression to parse the PDF Name from the PDF Document itself and the third dialog a regular expression to define a optional path. If you enable “Do not create tree structure” Aloaha will not create sub directories but use all values for the new filename.
As an example we configure Aloaha that if a user prints an email to Aloaha it saves the email as PDF in c:\pdf and creates one long filename made of From:, Sent Time and Subject.
- Open the dialog “Configure Savings Filter” from “Advanced Settings”
- Enter c:\pdf into the first dialog field
- Enter From:(.*) into the second field and Sent:(.*) into the third field.
- If you now activate “Do not create tree structure” and print an email to Aloaha you will see that the Filename is made of From and Sent.
- Now you need to configure the Subject. To do so please open your registry editor and go to: HKLM\SOFTWARE\[Wow6432Node]\Aloaha\pdf\automailer
- You will find the values savefilter0 and pdffilename
- For the Subject you need to configure an additional filter savefilter1 with content Subject:(.*)
Daily builds can be downloaded from: https://dl.dropbox.com/u/20338532/beta/aloaha_pdf.zip
The official release download link is: http://www.aloaha.com/download/aloaha_pdf.zip
Please read this installation guide carefully if you are using Vista/W7 and have User Account Control enabled
No doubt this is one of the most common questions/frustrations about Windows Vista/W7.
Even if you log on as an administrator, you don’t really have administrative rights, thanks to UAC (User Account Control). But since setups require administrator rights this behavior could cause problems.
When you run a setup program, right-click the setup program, and then click Run As Administrator. Then, it will really run as an administrator.
What is User Account Control?
User Account Control (UAC) is a new security component in Windows Vista/W7.
UAC enables users to perform common tasks as non-administrators, called standard users in Windows Vista/W7, and as administrators without having to switch users, log off, or use Run As.
A standard user account is synonymous with a user account in Windows XP.
User accounts that are members of the local Administrators group will run most applications as a standard user.
By separating user and administrator functions while enabling productivity, UAC is an important enhancement for Windows Vista.
To help prevent malicious software from silently installing and causing computer-wide infection, Microsoft developed the UAC feature.
Unlike previous versions of Windows, when an administrator logs on to a computer running Windows Vista, the user’s full administrator access token is split into two access tokens: a full administrator access token and a standard user access token.
During the logon process, authorization and access control components that identify an administrator are removed, resulting in a standard user access token. The standard user access token is then used to start the desktop, the Explorer.exe process.
Because all applications inherit their access control data from the initial launch of the desktop, they all run as a standard user as well.
In enterprise environments document hardcopies and PDF documents go hand in hand. Hardcopies of every generated PDF might be needed for paper files or a PDF document for electronic archiving might be required for every document printed.
An easy solution is the Aloaha PDF Suite. Rather then sharing the physical printer to the network you share the Wrocklage PDF Printer to the network. Aloaha will convert every print to PDF and automatic print it to a physical printer connected.
The setup is pretty much straight forward. Log on to the console of your server and install the Aloaha PDF Suite. All you need to configure is to share the Wrocklage PDF Printer to your network, re-configure Aloaha to run as a service and enable Aloaha to generate a Hardcopy of every PDF. Below you will find a step by step guide on how to accomplish this.
Re-configure the Aloaha PDF Suite to run as a service
- Remove the Aloaha shortcut from the autostart group of the startmenu.
- Right click on the Aloaha systray icon and choose exit.
- Open the service control manager and configure the PDF Suite Service to automatic startup
- Choose the physical hardcopy printer and enable autoprint
1) Start PMonConfig.exe from the Aloaha PDF Suite Directory. Usually that is c:\program files\wrocklage\PMonConfig.exe
2) Choose the Wrocklage PDF Printer in the first drop down menu
3) Choose your hardcopy printer in the second drop down menu
4) Enable “Print Hardcopy to printer above”
Please refer also to the screenshot below
Start Aloaha and verify settings
1) Open the services control manager and start the PDF Suite service
2) Right click on the Aloaha Tray Icon and choose settings.
3) Make sure you find your hardcopy printer in the “Print Settings” tab choosen
4) Define PDF save location in the “Save” Tab
5) Click OK
6) Right Click on the Tray Icon and make sure there is NO checkbox besides the Interactive option
ATTENTION: The Tray icon does only show if you are logged on to the machine console. If you need to connect via Terminal Services make sure to call the client with the parameter /console
Hardcopy without Letterhead
In some cases it might be required that the hardcopy is being done before the PDF Letterhead is rendered to the document. For example when the hardcopy is done to company paper.
Should you require heardcopies without letterhead just create a registry key:
“HardCopyPrinter”=”HP LaserJet P1005″
HardCopyPrinter defines the printer to be used! The keys below will then created automatically.
Obviously you need to replace “HP LaserJet P1005” with your printer name!
The values for HardCopyPaperSize you get from:
Additional Tipps and Tricks
Instead of useing the localsystem account to run Aloaha it is adviced to dedicate Aloaha its own user. Some settings are saved user based and to change them you need to log on as that user.
In case you need to configure some advanced settings such as automatic emailing of PDF documents, sorting PDF documents by user or enabling script engine it is adviced to run Aloaha with a dedicated account instead of the local user account.
To configure the settings mentioned above please log on to the system as the same user configured above. Call the creator.exe from the Aloaha PDF Suite installation folder (c:\program files\wrocklage\creator.exe) and configure these advanced options.
When pressing the Mail Button in the Aloaha PDF Suite Preview Aloaha derives the mail attachment name from the spool job name. In case you might want to enter manually a PDF Name each time you email a PDF with Aloaha just create the following registry entry:
HKLM\Software\Aloaha\PDF\ShowPDFNameBox = 1