TIBCO BW 6 – Managing Big Attatchments using Persistence Options

If you are familiar with creating services to provide functionalities to another systems or final users you are maybe aware about the pain in the ass the attachments always are. We are use to work with all the data in memory. We receive a request with their data and we keep it inside the memory working with this data and do the job. That’s the procedure we always work.

But, what we have to do with the attachments? When we work with attachments we are usually working with a lot of data because files always are big. At least they are big if you compare them with the other data inside your request. When you are creating service interfaces a normal practice is to limit the amount of data we can fly inside our online request at a 1 MB maximum or something like this. But, usually we have to deal with this problem and now, the latest version of BusinessWorks 6.x has a native capability to deal with it. Continue reading


Retrieving a WSDL from an Deployed Service

In this post we are going to discuss how to do to get the WSDL source from a deployed Web Service using the TIBCO BW technology. Usually when we build web service using other technologies like Java (Axis2, JAX-WS or something-related) automaticly we can access to the path http://paththatyouwant?wsdl and get the WSDL source of your service, but this is not happen in TIBCO BW by default.

If we deployed a service and we try to access it, we will get an 404 response from the server indicating that there’s nothing in that path so nothing can be returned to us:



So we need to do a little development and use the Retrieve Resources that we have in our TIBCO Soap palette so we can achieve this funcionality. We need to build a very simple BW Process that receive the HTTP request and use the Retrieve resource artifact to get the WSDL from it, simple like that, as you can see here:



The configuration of the RetrieveResources is very easy as you can see here:


So we only have to start this little process when we started the SOAP service, and we have everything working!



As always we left the process example so you can take a deeper look of it: Download

I hope you can use these information in your new developments! See you in the next post!

Comparative between SOAP palette and Service palette (I)

When you are facing the problem or the need to provide a Web Service implementation using the SOAP protocol with the TIBCO BW technology you have to make a important decision. What component are you going to use the Soap palette or the Service palette. Continue reading

Applying Security in Web Service with TIBCO BW

In this post we are going to learn how to apply security policies to our TIBCO BW WebService using the Policy palette that we have in our TIBCO Designer software. First of all, we are going to share some resources to get the basic knowledge for this post:

Tracing SOAP and HTTP exchanges in TIBCO BW

In this first ‘real’ post we are about to discuss the way we can apply a trace to any soap and http request we have in our TIBCO BW processes. This is a very important feature you must learn because is one of the main actions of an integration tool, because the SOAP and HTTP request is the main transport for WebService invocation.

Continue reading