I saw the link above, I did not follow at all since my Production Server already had the certificate validated with Goddady, so that server is already running IIS7 and it's a Webserver. I used another methods to incorporate the certificate into Windows OS.
What I did only was to configure a new port with the TMSHttpConfig only and change the ServerUrl property in both Client and Server to server the "https" prefix and the new port configured with TMSHttpConfig.
I tested and it works, I don't know yet if data is traveling secure, I assume it does, but I have not use a sniffer tool yet in order to check this point.
Can you please tell me if the BOLD instructions above was enought to migrate my projects [Server and App Client] into https????
Yes, they are. You can simply try to do a request to your server using HTTPS protocol. If it works, all is fine.
Actually if you changed your ServerUrl from http to https, your HTTP-only server should not be working anymore. You can test it, you probably won't be able to connect using HTTP, just HTTPS. So you're fine.
I will buy the suite at the middle of this week, so I will not say goodbye to you since I will ask another fetaures near at the future
Have a great Weekend, by the way It seems I'am trying to figure out the simplicity of RemoteDB and that's partially what I need for now.
Yesterday I modified slighly the RemoteDB server application in order to change the default "username" and "password". And all I need was a little time to research at forum and the examples.
------------------------------------
procedure TServidorWSF.StartServer;
begin
// just try to connect in the database before starting the server
// to make sure the connection string is correct. If not, an exception will be raised