To be able to run this demo you need the MyPDFSigner-Tray application that comes with the Windows or Mac OS X (this hasn't been released for Linux so far) installer and to configure a signing certificate (see the configuration section of the manual) or you can start by using the preconfigured example that uses a PKCS#12 KeyStore file.
The installer ships with a Java KeyStore that includes an SSL certificate to run a local web server. Since the shipped certificate is in general valid for only 90 days the certificate may already have expired by the time you download the installer. You can download a more recent keystore and a new configuration to replace the ones in the tests directory of the installation.
To use the preconfigured example copy the C:\Program Files\MyPDFSigner\tests\mypdfsigner.conf file to C:\Users\username\.mypdfsigner. Then run the MyPDFSigner-Tray.exe application in C:\Program Files\MyPDFSigner. This will add a icon to the task bar. The instructions for Mac OS X are similar. This step, although instructive, can in fact be skipped since the Tray app will automatically autoprovision itself with the preconfigured example to be able to run the demo.
Next right click the tray icon and select View Certificate to confirm the configuration file was loaded. Then select Start HashSigner Service. You can then click the Sign Remote PDF button below.
The content of the visible signature, including a possible image, can be changed in the configuration file. The image is restricted to a PNG with transparency.
the resulting status will be shown here
the output of call 0 will be shown here
the output of call 1 will be shown here
the output of call 2 will be shown here
the output of call 3 will be shown here
the output of call 4 will be shown here
If you want to confirm that the local service is indeed participating in the signing process you can add the entry debug=on to the configuration file (and restart the service). This will create the log file C:\Users\username\mypdfsigner.log where the requests to the local service will be logged.
The local service is running, as can be seen in the configuration file, a small HTTPS server on port 8443. The hostname localhost.kryptokoder.com points to 127.0.0.1 and the SSL certificates for it are in the Java KeyStore indicated in the configuration file. Note that these certificates are for demo purposes (see this stackoverflow post for more information).