IBM Connections, IBM Domino, and IBM Sametime provide Application Programming Interfaces (APIs) over HTTP. These communications can occur over an unencrypted channel such as HTTP on Port 80, or over an encrypted channel such as HTTPS on Port 443. The IBM SmartCloud for Social Business only allows access through secure communications over HTTPS.
Each channel has it's draw backs and benefits for a developer:
Pro - Easy to Access, No Special Settings Needed to Access
Con - Insecure, and Customers Rarely use it in production
Pro - Customers Use it in Production, and Secure
Con - Requires Additional Configuration to Access
As a developer, one finds there is a development environment connecting to a test server which provides APIs. These Test Server APIs are configured much like a customer environment using HTTPs with Self Signed Certificates. As self signed certificates are considered insecure, the developer must explicitly review and trust the signer of the self signed certificate in order to access the APIs from his development environment. The trust of a HTTPs Certificate Signer may need to be set up in both directions Developer-to-Test-Server and Test-Server-to-Development-Environment.
This article gives pointers and details on how to configure the security of your environment to setup trust on your test servers, and on your development environment.
Once the Communication is done over encrypted HTTPS. There is a need to establish trust between servers. You can update the cacerts on each of the Java Instances to support the Signer.