Publishing TIBCO Docker Images

In the last months I’ve been publishing different post related to Docker container technology and its application to the TIBCO world, and today I’m pushing this idea a step forward. I’m uploading to our GitHub repository the composition of these machines.

Obviously, I’ve removed every file that is under TIBCO copyright, but it will contain all the data and the information I use in my docker machines to test and try all the TIBCO product that I have to work with in my daily basis.

So, if you want to take a look, I start with a TIBCO EMS base machine with the data in the host machine, so you can change the EMS configuration files for every need you have.

Take a look at our repo! 

[ELK Series] Parsing the TEA logs to visualize right in ELK & Kibana

Today, I come back with another step in our connection between our TIBCO BW 6.x environment and the ELK stack to extract all the power about the log information we have inside our TIBCO BW components. And we started with the TEA component. In the previous post we get a sucessfull connection to ELK stack with the information inside the TEA. But we use the default message formt so, we cannot use the custom parts the TIBCO log file have inside.  Continue reading

[ELK Series] OOTB Connection between ELK and TIBCO TEA

If you have been followed these post series as a result of the last post we launch our ELK stack using docker, so we have all our components up and running to start integrating both of these worlds. And we are going to start with the log files from the TIBCO Enterprise Administrator, TIBCO TEA.

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

[ELK Series] Integrating your TIBCO AMX BW 6.x logs with the ELK stack

The idea of this post comes from one comment in my last post, as you can see here. In that post we were talking about different log capabilities that you can do now in the new TIBCO TEA Administrator tool. But, this user, ask why talking about the log capabilities the product OOTB provides you when you could integrate your traces with a great component stack to squeeze all the information these logs have. This stack was the ElasticSearch (ELK) stack, and I think: “That is a great idea”. So, I’m going to create a post series to explain how to integrate your logs with this stack.

Continue reading

[Docker Series] Creating a BW 6 environment with Docker

After a while since the last post about the docker series I’m here again to introduce how to create an BW 6 environment using our favorite container tool, Docker. The idea is to show not only the final files but all the thoughts and procedure I followed to create this containers and their configuration. So, please, come with me across this path which allow us to go deeper in our docker knowledge and to improve our capabilities and mental toolbox.

Continue reading

[Docker Series] Introducing Docker Compose to our Docker containers

We are back with another post from this new docker series oriented in our prefered environment, TIBCO environment and the idea is to introduce one of the newest tools in the Docker environment and how we could use it in our TIBCO docker containers.

In the previous post that you can read here, we create our first docker container with an EMS server inside. If we try to run this machine we need to do that with a very large run command, something like that:

docker run -tid -p 7222:7222 ems ./

Even if we use more complex configuration (the ones we are going to learn in the following chapters) we have a more complex sentence. A sentence we have to type every single time we want to start our container. Is this the only way to do that? The anwser is no. We could use Docker cCmpose to simplify this sentence. Continue reading