From Version 2.5 the Aloaha Processes are able to communicate with each other. This is not only possible between different two different user but also between different machines.
This new technology allows the usage of a central remote configuration. It is also possible to move a printjob from machine A to machine B. This can be important if a user prints in a terminal session but wants his print job processed on the client machine.
Most commands are password protected and the inter process data is highly encrypted. Some commands are declared public. In case there is interest in this technology please contact our support for additional commands.
General Usage
First the Aloaha Pipe Object needs to be created. In VBS notation that would be:
set pipe = createobject("AloahaPipes.Monitor")
Next you would have to create the pipename. It is made of machine name and owner name of the pipe server (who is running Aloaha).
if pipe.Connect(pipename, server)= true then
if pipe.send_message("beep") = true then
msgbox "ok"
msgbox cstr(pipe.POP_Stack)
else
msgbox "Could not send message"
end if
else
msgbox "Could not connect to pipe"
end if
call pipe.DisConnect
set pipe = nothing
beep command
The command beep is a dummy command. It only instructs the server to send a beep via the computer speaker.
interactive
Interactive put Aloaha in Interactive (default) mode.
noninteractive
This command instructs Aloaha to work noninteractive. The automation mode requires at least a server license.
sign
Sign enables signing of every generated PDF Document. Signature settings such as appearance, position, certificate have to be set before!
nosign
Nosign disables automatic signing of PDF Documents.
reload
You call this command if you want Aloaha to reload all its settings from the registry. For example you changed registry settings manual.
exit
Instructs Aloaha to quit and exit!
emf: command
One great feature is to handover a remote machine a print job. Just call emf: <path to spl> and the remote Aloaha process will process that spool job.
For example emf: s:\20070725_115819_114_8.aloaha.emf
Please note that aloaha processes EMF files ONLY if a INI file with the same name exists in the directory. For example 20070725_115819_114_8.aloaha.emf.ini. It is essential that the user mentioned inside the ini file MUST match with the owner name of the remote process!
Together with the Aloaha Print Monitor this is great to move jobs between machines!
Please ask...
Although we really tried hard, there are always questions left open.
Please send us your question. We would be glad to answer it.