It is time to show you how to build a cluster with Domain mode within JBoss EAP 7. Before you read this blog I suggest you to review the following blogs: JBoss terminologies, the Domain architecture understanding, and how to create a Domain. All these bogs will help you to better understand what we will do today 😉
After we made a global overview on Elastic Stack and we went more in deep in Elasticsearch terminologies. This third blog in the Elastic Stack series will allow you to know how to set up Elasticsearch, from Downloading, Installing, Configuring, and Starting.
In a previous blog, we got an overview on Elastic Stack (Elasticsearch, Logstash, Kibana, and Beets), in next blogs I will go through all these components to understand them, today we will go more in deep in Elasticsearch the heart of Elastic Stack.
ELK Stack or more recently called Elastic Stack, is a combination of three open-source projects: Elasticsearch, Logstash and Kibana. All these projects have been developed by Elastic and used to store, analyze, discover, and visualize data efficiently! I got the chance to install, configure and maintain Elastic Stack on Kubernetes since more than two years. Today, I would like to share with you a quick journey along the Elastic Stack 😊
In a previous blog I talked about the domain creation, we saw at the end that some server groups and servers are created by default which usually are not what we need. Through this blog, I will show you how to clean this unneeded configuration and how to configure your domain according to your defined architecture.
As promised in my previous blog, I will give you a short feedback on the second day here at DevOpsDays 2020 Geneva. In fact, I prepared a very interesting program of sessions to attend and people to meet. I must say that the open-spaces concept applied on the second day allowed participants to discuss on different topics without limit.
It is a pleasure to come back to Geneva after 5 years to attend my first DevOps event. I’m very excited to share with you my first day feedback, but before I would like to thank dbi services for allowing me to attend this event and continuously improving my knowledge in this growing field.
At a customer, we are upgrading Control-M Agents running on Windows/Unix from 9.0.00.400 to 188.8.131.52 using Agent Deployment, an upgrade of one agent fails with error talking about communication issue between Control-M/server and Control-M agent:
In a previous blog I talked about the emdef utility and how it can help to manage and standardize calendars across multiple environments. In this blog we will deal with folders definitions in the Control-M/EM database. This can be used to extract data as a backup, or for migration from one to another environment.