The following steps are needed only if you use a self-signed certificate for SSL (which is not recommended), and only in the case of configuring Talend Data Catalog to securely connect via HTTPS to another Talend Data Catalog server for metadata harvesting. You have to perform the following additional steps, only in such exceptional use case.
In order to support HTTPS from a Talend Data Catalog server acting as the "metadata manager" to a Talend Data Catalog server acting as a "metadata harvesting" server, the administrator needs to import the trusted certificate that the Talend Data Catalog harvesting server is using into the JRE that the Talend Data Catalog metadata manager server is using.
For more information about the process, see http://docs.oracle.com/javase/tutorial/security/toolsign/rstep2.html.
For example, the command can be as follows.
$ cd /opt/<TDC_HOME>/TalendDataCatalog/jre/lib/security $ ../../../bin/keytool.exe -import -alias john -file YourOwnCertificate.cer -keystore jssecacerts