In the previous post, we started a sample to create a SOAP wrapper to a SMS Rest API provided by Nexmo and we were capable of define a TIBCO BW 6 process that could create the exact request that the Nexmo Servers are expecting, but we need to configure the SSL connection to finish our sample, and that’s what we are going to do in this post.
If you miss the previous post I encourage you to take a look to get the context and the knowledge about the previos steps. Back to the
First of all, we have to define the compoments that we are going to need to establish the SSL connection. We need to create the following resources:
- Keystore Provider Resource
- SSL Client Resource
- HTTP Client Resource.
One of this resources is linked to the one listed below of them, so the HTTP Client uses a SSL Client Resource that uses a Keystore Provider Resource. But, which is the purpose of each of them?
Ok, probably you already knows the HTTP Client Resource, because if the client that we defined when we need to establish a HTTP Connection acting like a client. In this resource we specify at least the host and the port number of the target. We also can define a lot of techical details about the connection but that’s not the purpose of this post, but if you want to go deep you always can take a look at the official documentation from TIBCO where all this parameters are explained.
The SSL Client Resource is a resource that defines the parameters about the SSL Connection when you are acting like a Client, you have the specify the Keystore provider that you are using to create this connection and you also have a lot of technical parameters about the SSL connection (protocol, ciphers allowed, and so on).
And, the last one, the most important of all of them is the one which indicates where is the location of the real keystore (JKS file or similar) is going to use to create the SSL connection.
So we have all the chain in images:
- First the HTTP Client with the host and port definition and the references of the SSL Client Resource.
- Second, the SSL Client Resource and its link to the Keystore Provider Resource:
- And last but not least, the Keystore Provider Resource definition:
And, that’s it! With all these, we can get working our example, as you can see here:
And here it is the evidence from my phone 🙂