Aloaha Software

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

1. Remove the Aloaha shortcut from the autostart group of the startmenu.
2. Right click on the Aloaha systray icon and choose exit.
3. Open the service control manager and configure the PDF Suite Service to automatic startup
4. 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

Aloaha PMonConfig

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:
[HKEY_LOCAL_MACHINE\SOFTWARE\Aloaha\pdf\printer]
“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!

“HardCopyPaperSize”=dword:00000009
“HardCopyOrientation”=dword:00000000
“HardCopyCollate”=dword:00000000
“HardCopyDuplex”=dword:00000000
“HardCopyColor”=dword:00000001
“HardCopyQuality”=dword:00000002

The values for HardCopyPaperSize you get from:
http://msdn.microsoft.com/en-us/library/windows/desktop/dd319099(v=vs.85).aspx

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.

Aloaha Smartlogin exists in two editions. One edition includes the Aloaha Smartcard Connector (CSP) supporting ca. 45 different cards. Those cards can be connected via PC/SC (CCID) or CTAPI (for example eHealth Terminals.

Some customers require a more generic Windows Logon Solution. For example because their card is not one of the 45 supported cards OR they are forced to use their own smartcard middleware.

The second edition supports any smartcard via its middleware (cryptoAPI/CSP) or PKCS #11 module. When using the card via middleware/crypto API the user credentials will be encrypted with the smartcard certificates and stored as a softtoken on the local harddrive or network share. Basically this solution is a 3-factor logon solution since it is require to know the PIN of the Card, the possession of the smartcard AND the existance of the Softtoken.

In case user do not want to use the softtoken based 3-factor solution they can opt to use the PKCS #11 Interface of their middleware. When using the PKCS #11 Library Aloaha will save the user credentials encrypted in a private object ON the card itself!

To store the credentials on the card the user needs to call “PKCS #11 Credentials” from the start menu or PKCS11Credentials.exe from the installation folder (<program files>\wrocklage)

Aloaha Smartlogin PKCS #11 Interface

As a first step the PKCS #11 Library to be used has to be defined! Once that library has been choosen all available token will be listed.

If there is more than one token the user has to select the token to be used in order to save user credentials to the token.

The token removal behavior will be read from the system policy OR from the file Userpass.ini. For details please contact support at info@aloaha.com

To install this edition of Aloaha please download http://www.aloaha.com/download/smartlogin.zip

Please note that a license key is ALWAYS required! Evaluation keys can be requested from info@aloaha.com

Aloaha accesses per default the connected Smart Card Reader via the Windows PC/SC or CCID driver. In some cases it might be required to use the reader via CT-API. For example in cases that no PC/SC or CCID driver exists. That is the case for most health terminals used in the german health system.

To be able to use CT-API it is required that a recent version of the Aloaha Smartcard Connector is installed. If you find the file AloahaCSPPlugin.exe in <common files>\Aloaha your Version is recent enough to be switched to CT-API.

To activate CT-API there have to be entries in the file CTAPIINI.ini in <program files>\wrocklage and entries in the registry.

CTAPIINI.ini:

[Settings]
activated=1
CTAPI=c:\windows\system32\ct8751.dll
[HID OMNIKEY 8751 e-Health LAN]
port=1
Units=01,02,03,04,40,50

Please note the the settings section is required. The rest Aloaha will try to fill in automatically.

Once the above seetings are done you you re-logged on into your machine you will see your CT-API eHealth Terminal in the Aloaha Systray as shown below:

Aloaha System Tray with e-Health Terminal

Even though any CTAPI Reader should work currently ONLY the ORGA 6041 eGK and OMNIKEY 8751 eHealth terminals have been accredited to work perfectly with Aloaha. More will follow on request!

Windows Logon with e-Health Terminal

Obviously the Aloaha Smartlogon does support Windows Logon via CTAPI based Smartcard Reader. That means that it is possible to use a HID 8751 or Orga 6041 eHealth Terminal to logon to with the german HBA (Health Professional Card).

Per default the e-Health Terminal is NOT connected to the Windows Logon Credentials Provider. To activate that you need to create the following entry in our CTAPIini.ini in your installation folder:

[Settings]
CTAPIAsSystem=1

After you create the key and set your credentials via Aloaha GUI you can logon via the Aloaha Tile as shown below:

Aloaha Windows Logon

You can download the Aloaha Middleware/Credential Provider from http://www.aloaha.com/download/credentialprovider.zip

Please make sure to request an evaluation key from info@aloaha.com

German cutomer should also read: http://blog.aloaha.com/2012/01/03/wie-richte-ich-mein-ehealth-terminal-ein-um-mich-mit-meinem-hba-oder-smc-karte-an-windows-anzumelden/