When you click on the
Capture Signature button you will see the Form that displays
the captured signature.
The client would use the sign their
signatures on the Signature pad.
If the signature is
clear,
then the 'write to Power Broker' button is pressed.
The
signature would then be attached to the application or Form
that was being generated.
Click here to
download the install file
February 24th - 2010
Sample Install:
Sample Workflow
Reviewing Your Saved Signature
TERMINAL SERVER USERS SECTION:
If you are NOT using a terminal server setup, then please
ignore:
Installation procedures for Topaz
Signature pad in a terminal services environment
Ports Required:
TCP Ports 47289 and 47290 used.
(In our testing, there were no port adjustments needed to be
made.)
Download and SAVE
sigsockinstall.zip to
MyDocuments
Server Configuration:
Install Sigsockinstall.exe
using the same settings as from the instructions at
the top of this page.
Locate sigplus.ini in the
\Windows folder and copy this to c:\documents and
settings\<<username>>\Windows
Edit sigplus.ini changing
the TabletPortPath = clientname.
Note: ClientName defined
here must be derived from the following step.
In this example, the userid in Power Broker Version
4 is KV
Use PB + my PB
userid = PBKV ( as seen at the bottom right of this
screen capture )
Workstation Configuration:
Create a folder C:\Sigplus
Copy <Server>\windows\sigplus\tools\sigsock\sigsock.exe
to c:\sigplus
Create a batch file that
will launch the sigsock.exe with 3 paratmeters:
<<Servername.domainname>>
<< clientname>> 6
In this example, we are looking at C:\Sigplus and we
have created a blank batch file and called it
sigsock.bat.
Right click and edit the sigsock.bat
( To create a batch file, right click in Windows
Explore ( in the c:\sigplus folder ) and choose New
and then Text, and then
name the file sigsock.bat, and then say 'yes when it
warns you that you are changing the file extension
and that it may not work)
In the empty batch file, you would type in your own
details:
Example: sigsock.exe
myserver.mydomain.com MyClientName 6
Click FILE and then SAVE to record the changes made
in the batch file.
RUNNING SIGSOCK.BAT
Ensure that the sigsock.bat
is loaded before the terminal services connection
is initiated.
One method would be to include this in a Log-in
script or another option would be have an icon on
your local workstation
desktop that points to c:\sigplus\sigsock.bat and
the user would need to manually launch this file for
the integration to work.
Before connecting, the file would need to be
initialized with either method.
( In this example, we've simply launched it from
Windows explorer and a DOS window sits on the
desktop.
If it were installed with a log-in script, your
local technical support representative can hide the
dos window by adding a few lines to the batch file.
)
The user would then launch the Terminal Server
connection to connect to the server, and then
proceed with your
test signature.
This integration has been
tested on Windows XP, Vista, and Windows 7 using both
local and Terminal Services method.
July 19/2010
Signature Pad - Power Broker 4