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


Introducing TIBCO AMX Policy Director

There is a common topic that many of you ask me about and it’s about how to implement security with the TIBCO BW processes. I explained in different post how to implement a basic security policy using the capabilities that the TIBCO BW tool gives us to do that kind of task. You can rembember these posts: Applying Security in Web Service with TIBCO BW and Invoking a Secured Web Service from TIBCO BW

But, that’s a not good practice to an overall architecture and that’s because if you are doing this kind of task you are linking the “life” of the security policy with the “life” of your developments, and that’s not correct. But, let to dig a little more about that philosophical debate.

Supose that you are in charge of the integration layer in your company, in charge of every TIBCO BW development your company has to do. Will you be in charge to define the security policy of your company as well? Probably not, it is not possible that you could have these two areas at once because the security policies has a more scope than the integration or EAI layer, and if is this is true, Why are linking these two concepts? 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

Deep BW6.1: First development and delpoyment

Now, we are going to do our first deployment in our newly created environment, first of all we are going to launch the new TIBCO Business Studio for Business Works Development, and we are going to create our first project using the TIBCO BS wizard.

We are going to create a very simple process: Only an in-out operation with an internal logger, as you can see is the simplest BW process you could see.

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