Today I had the pleisure to give a talk about Kubernetes Basics at the Docker Mannheim Meetup. I enjoyed it very much and we had some very good discussions after the talk with the traditional pizza and drinks sponsored by Stocard.
A big shout-out to Jens and Martina for organizing the meetup!
This week starts with Admincamp in Gelsenkirchen. Thanks Rudi Knegt and team for this awesome event! The conference or lets name it camp was real fun. In the end I did three sessions and a workshop. You can find download links to all slides and used files in this article or on https://stoeps.de/speaking/2018/. I learned and heared a lot of interesting stuff around IBM Notes, IBM Connections and Sametime. You can get most of the session slides through the Admincamp agenda.
Watson Workspace Clients are only available for Windows and Mac OS. I’m a 100% Linux user on my devices and I use a Windows virtual machine only if I can’t avoid it. To communicate with colleagues, IBM and DNUG I need to use Watson Workplace, opening the web view is possible, but then I need to search the right tab or forget to open it. Since some weeks there is Zoom (Web / Video meetings) integrated with Watson Workspace too.:
Watson Workspace clients are based on Electron. I’m not a big fan of Electron clients, most of them are big and need tons of system resources. There is enough written about advantages and disadvantages, so I just leave it that way.
:icons: font
After some deployments of IBM Connections pink and IBM Cloud private, I want to share some tools, links and hopefully helpful information around these products.
With IBM Connections 6 you can deploy the additional component Orient Me, which provides the first microservices which will build the new IBM Connections pink. Orient Me is installed on top of IBM Spectrum Conductor for Containers (CFC) a new product to help with clustering and orchestrating of the Docker containers.
This year I attended IBM Connect in San Francisco. In my eyes it was a great event and I enjoyed it very much.
Some announcements are very important for the future and evolution of the IBM portfolio:
Last week I wrote a post about Using Docker and ELK to Analyze WebSphere Application Server SystemOut.log, but i wasn’t happy with my date filter and how the websphere response code is analyzed. The main problem was, that the WAS response code is not always on the beginning of a log message, or do not end with “:” all the time.
I often get SystemOut.log files from customers or friends to help them analyzing a problem. Often it is complicated to find the right server and application which generates the real error, because most WebSphere Applications (like IBM Connections or Sametime) are installed on different Application Servers and Nodes. So you need to open multiple large files in your editor, scroll each to the needed timestamps and check the lines before for possible error messages.
