Not that I know of, but we put together an appliance to simplify the Linux part of the setup (free download after a small hoop to jump through, see http://sinenomine.net/vm/sslenabler), and the IBM documentation covers most of the other issues you actually care about. Most of the hard parts are getting the Linux system set up, so skip that part and just use the enabler system.
Key points to understand that the VM implementation is a transparent wrapper around the basic service, so telnet, SMTP, etc don't really know it's there. In 5.3, some of the servers and clients have been modified to support awareness of TLS (transport layer security), but not all. The hardest thing will be dealing with certificates. X.509 is a *bear* to understand, but the important point is that you need a certificate to identify the system that matches the host name you use for that system. It's easier in terms of deployment to use one that is generated by an external certificate authority (look in your copy of Windows for the default companies), but not required. Get it, import it, and go through the configuration steps in the docs. After that, you can start the hunt for clients that implement requesting SSL-protected services.
