In previous post I showed how to create a REST based service using TIBCO BW 5.x, but today I’m going to do the same using the 6.x series to highlight the differences between both of them. Continue reading
In the previous post I talked about how to create a REST Interface using TIBCO BW 6. If you want to take a look back, please go ahead. But in this post I want to focus in another feature that it is important when we are working with REST Resource. And it is the way to add different REST Resources inside the same BW Process.
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
Usually I get a few mails from you regarding how to integrate with different services or systems that are not “standard” in the way we use when we are used to integration using TIBCO BW. This is so common when you are trying to consume REST services, because the standarization process is not the same in the REST Services that you can find when you are trying to integrate with a SOAP Service.
When you are trying to integrate with a SOAP Service you will always have your WSDL and that’s everything you need and the people from TIBCO only have to provide a way to generate all the artifacts from this WSDL but that’s not he same scenario when you are talking about a REST Services.
In different previous post I talked a lot about REST services and how they are so non-standard despite of the attempts like WADL in the first ages and now Swagger that maybe is the most common approach nowadays. But the purpose of this post is not to talk about the problems when you are trying to use TIBCO BW to work with REST Service but to trying to integrate with a specific REST Service: Nexmo.
In this post we are talking about how to secure our HTTP communication that we have in our TIBCO BW developments. So we need to activate the SSL protocol to ensure our communications. In this post we are going to describe only the SSL configuration in the server side, so there will not be authentication in the client side. Continue reading
In this new post we are about to discuss how to create a REST WebService using TIBCO BusinessWorks as a HTTP Server. The main goal of this new example is to continue learning how to use some of the basics of a TIBCO BW Development. First of all, we are about to present the ‘design’ (maybe, design it is a strong word for a little example).
In this new post we are going to know how to upload file to a TIBCO BusinessWorks Server, so we can learn how to deal with some important aspects like groups, http transport, and so on. We are going use an HTML file to define a form that upload a file to our system.