Printing all the HTTP request in TIBCO BW 6

Usually when you are working with Process that are invoked using HTTP (you can use SOAP or REST services ) it is needed to see the actual request you are getting. Specially to do some troubleshooting and to verify if the request was defined as expected.

As you probably know, in this new release the logging technology used has changed to the newer logback library (Logback it is the new library from the creator of the Log4J library) and we already talked about it.

If you want to do it on your own computer when you are doing testing that’s so easy because as I explained in the previous post you have your logback.xml to do it, but what about when the service is already deployed? Ok. step by step.

Continue reading

[PRO Tip] A fast way to generate your EAR file

When we are developing our TIBCO BW 6 application the last thing we need to do to deploy our application is to generate an EAR file, so you can deploy it in your different servers. And today, the idea is to show you another way to do that, and it is very quick! It’s an idea I never used before because I didn’t know about it ┬ábut I read it on the official documentation and it was so great. Because of that, I want to tell you about. Let’s start.

Continue reading

View Log File without Physical Access

One of our most usual task in our production environments or event any other environment where we have our TIBCO BW process is to access to the log files to see any unusual behavior or errors detected in the normal execution of our process. Until now, these access to the log files to see what happened require physical access to the machines where the BW agents are running to get and take a look at the files.

That normal behavior it is a normal threat for the security standards and policies inside almost every company and most of you probably have been faced the discussions and the burocracy to get a user to do SSH to a machine in production or even a test environment. Ok, this was the normal procedure until now, until BW 6.X arrived to our lives.

Continue reading

Application AppNodes using different ports in the same host

In the today post we are going to learn how to deploy a Web service in two AppNodes using different ports to receiving requests. When I named a “Web Service” I’m referring to a Process that expose an HTTP connection to receive requests.

You may think this is not a problem if I want to deploy an application using the TIBCO BW 6.x series I upload the Application Archive to the TEA and I start the Application deployment in the different nodes. Ok, first of all you should know that the configuration values are the same, at first, for every AppNode you deploy. Another important thing is that if you create an HTTP Resource with the default configuration the port is not configured used a property (this is not occurring with the hostname value, for example), so you have to do the following tasks:

  • Configure your HTTP Resource inside your application to specify the port number using a Module Property.
  • Change the initial configuration at least in one AppNode.

Continue reading

Tip: Verify the alignment between Java versions when you are including Java code inside your process

In this case we are going to give you a simple tip because we hear from some of you that you are facing this problem so I think it is better to put it common so nobody else could have the problem without a public solution.

Continue reading

Problems configurating Maven inside BusinessWorks 6.2

In the past days we explained how to configure and how to get to work Maven with the latests version of BusinessWorks at the moment (version 6.2) and if everything goes smoothy for you, I feel very happy, but if you have any kind of problem, please I beg you to leave a comment so we can get to work it out for you. I’ll updated this post with all the problems and the fixes for this configuration and I’ll from one that happened to myself Continue reading