Dynamic Log Level in TIBCO BW 6

How many times had you need to write log traces with different log levels? The anwser will probably be every time you develop a BusinessWorks process. But, how can you do this trick in the new TIBCO BW 6? Ok, let’s go for it.

Continue reading

Advertisements

Updating REST Resource Interface

In the previous post we show how to create a REST resource with different query string parameters and parameters inside the URL, but how about updating this REST resource?

Ok, first of all, the official documentation doesn’t give us any idea about how to do that. So, at glance, you will probably think you can do it and you are going to remove your REST resource and create it again.

If that was your only option, it has no sense. Do you image to have to remove all your work only because you need another parameter or have to change the name of anyone? It has no sense at all.

Continue reading

Creating a REST Resource with a Query String parameter

In previous post I showed how to create a REST Resource inside our TIBCO BusinessWorks 6 projects. If you don’t remember the post you can take a look again here. In that post I showed how to create a REST resource without any kind of parameter but that’s not the real word.

When you define a REST interface it is usual to have parameters inside the URL that you have to use inside your process to make some kind of processing logic. It is common to have parameters to filter the current invocation or so. For example, think about this URL:

freegeoip.net/{format}/ip={IP_or_hostname}

Here, we have two type of parameters:

  • The first one {format} it is “inside” the URL because it is a path step.
  • The second one {IP or hostname} it is a queryString parameter.

This post’s idea it is to show how to do this in TIBCO BusinessWorks 6.

Continue reading

Maven Support on BusinessWorks 6.3

We already talked about Maven Support on the new BusinessWorks 6 series, you can take a read to this post to get your mind ready for this new update on the topic. Even you can review our video that showed how to configure it.

But since the 6.3 version of BusinessWorks went out all the things changed regarding to this new capability. This post is to update all the information and to guide you through all the steps to get this working in this version (and newer versions too).

Continue reading

Enabling the OSGi Console for an AppNode

One of the most important changes for the architecture using TIBCO BusinessWorks 6 is that is OSGi-based and one of the most important things to know is how to enable the OSGi console.

The OSGi console is a tool which allows you to execute a lot of interesting commands to retrieve diagnostics and information related to the applications deployed on the node. You also could retrieve metrics about the processes or make changes to the logger configuration.

Continue reading

Enabling SSL debug info on AppNode

More than a year ago I write a post about how to print the SSL debug info inside your testing deployments on the TIBCO Studio for Designers, you can take a look here to the post because it is valid today to the current version.

But today, I want to talk about how to do it when your processes are already deployed on one AppNode running on your current environment.

Continue reading

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