Digital Certificate Manager is found at UR.IP.Adr.**:2010. You should sign in as Qsecofr when creating certs and key stores so the ownership is easy to maintain. You will find wizards for creating the objects you need and importing them to other systems. As a remediation for PCI, all of our system network servers are SSL encrypted and the unencrypted ports are not open. HTTP for intranet was painless. Telnet was probably the hardest to implement as IBM doesn’t support downloading an image with the keys there, but it can be done. HTTP for outside vendors using a public/private key from Verisign or RSA is best managed through third party application tools, though you can do it if you take the time to really learn the concepts. I don’t know about iPads, but iPhones seem to be requiring add ons like Mcfee’s remote application support so those may be more challenging than just web enabling HTTP for SSL.
First of all,
I give you my opinion, I might have it wrong..
SSL is used mainly for HTTP traffic.
To answer your question we need to know what kind of OS you are running and which webserver.
To install an SSL certificate on a server it is very easy.
Buy a certificate, and the party where you buy it from will have a ton of examples how to install it.
It depends on the OS and the web server.
IIS or Apache for example.
Look for the correct versions of the webserver and your OS.