Configuring WorldServer to use encrypted communication with Microsoft SQL Server databases

The WorldServer configuration for encrypted communication requires changes to the general.properties file from the root WS_CONFIG folder.

About this task

Depending on how your environment was set up, you can configure these settings either in the general.properties file or in the Windows Registry. The following procedure presents the steps required for the configuration in the general.properties file, but the same settings apply if you manage your database connection settings in the Windows Registry.

Procedure

  1. Go to the WS_CONFIG folder and open the general.properties file with a text editor.
  2. Make sure that the following data connection settings are configured as in the following example:
    database_driver=com.idiominc.jdbc.sqlserver.SQLServerDriver
    database=jdbc:idiom:sqlserver://<host>;DatabaseName=<dbname>;EncryptionMethod=SSL;TrustStore=<path-to-certificate>\\<certificate-name>.<certificate-extension>;TrustStorePassword=<truststore-password>
    database_username=<dbuser>
    database_password=<dbpassword>
    In this case:
    • <host> is the fully qualified domain name of your database server
    • <dbname> is the name of your WorldServer database
    • <path-to-certificate> is the path to your TrustStore certificate; you must use double backslashes for the certificate path; for example, C:\\WorldServer\\SQL_Certificate
    • <certificate-name> is the name of your certificate; for example, sql_cert
    • <certificate-extension> is the extension of your certificate file; for example, .pfx
    • <truststore-password> is the password used to access the certificate file
    • <dbuser> is the username that you use to connect to your database
    • <dbpassword> is the password that you use to connect to your database
  3. Save and close the general.properties file.
  4. Stop WorldServer and start it again.