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

View the deployed process inside the TEA Administration

We have done a few posts explaining the main options of the TEA Administrator but today we are going to focus in simple aspects like the one in the subject. How many times did you have the need to know how implemented was the process inside the EAR you have running in Production? You probably had a great version control system to manage all the uploads but in a few cases there was maybe the doubt that the flow you were seeing in your Designer in the same flow that was running in the BWEngine. Ok, but today the new TEA gives you the posibility to see the diagram on any process deployed in your system.

Continue reading

How to manage BW Application inside the TEA Administrator

Today we are going to explain how to manage the BW Application inside the TEA Agent and which one are the difference with the old TIBCO Administrator, so you can learn how to use this new Administrator.

The first and main difference are the architecture behind the new administration. Using the old administrator you only have differente Folders to sort the application logically and the BW engine to execute the BW processes. This is a simplified scenario because you always have the posibility to manage differente domains with different engines but this is beyond the product capabilities. On the other hand, with the brand new Administrator you have the following clasification: AppSpaces that are a logical environment when you could use to sort the application logically; AppNodes that are contained in AppSpaces and that are runtime objects where the BW processes run. You also have a different view that is Application Archive that are the EAR uploaded into the administration, and finally the Application Instance that are the instantiation of an Application Archive in one or more BWEngine. Continue reading

TIBCO Hawk 5.1 : Introducing the new WebConsole

TIBCO Hawk is the main tool developed by TIBCO to do monitoring tasks, but in the last years its evolution had been a little confused. We have had the last version of the 4.x series, the 4.9 version for so long, that many people thought the idea of the company was to declare the producto as a “feature complete” (that means, no more features updates only bugfixes will be released). The adquisition of other tools like TIBCO Spotfire, the partnership with RTView could lead us to think that the time of the TIBCO Hawk was been passed away, but we could not be more wrong. Continue reading

How to change the TIBCO Hawk WebConsole Port

In previous post we talked about this new WebConsole introducing by the last version series of TIBCO Hawk, the 5.x series. You can see more information about it here. One of the most important things is that the webconsole is deployed using the 8080 as a default port. This post is so common that is almost imposible to be free in your server when you want to deploy or start the WebConsole. For example, this port is the default of the Tomcat web-server, the JBoss/WildFly application server, even is the default port of the TIBCO Administrator (the older one) so it’s an important thing to know how to change it.

Continue reading

Deep BW61: Managing BusinessWorks 6.1 environment inside TEA

After the first chapter of this blog series we have register an BW agent inside the TIBCO Enterprise Administrator, so now in our TEA web page,  we can see the BusinessWorks agent already register inside the TEA infrastructure:


After that we can go forward and get a fully functional administration domain where we can delpoy our application we need to perform some adminsitrative task.

Continue reading