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

[ELK Series] Launching your ELK stack using Docker

In the previous post we talked about how is going to be our architecture to squeeze all the information that’s inside our log file using the ELK stack. We also exaplined the main components involved and their role in this architecture. Now, we are going to start to build it, and we are going to start launching our ELK stack.

As you could guess from the title or event for the last post series we are going to use Docker to do this. But, this time we are not going to create any dockerfile. We are going to use a community image to do that. As we said in the last post, the ELK is an open-source stack so there are several images that could do the work for us.

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