Orient Me 126.96.36.199 has just been released and fixes the incompatibility between IBM Spectrum Conductor for Containers Community Edition 1.1.0 and Docker 17.06 which lead to failed installations. You can find the Orient Me 188.8.131.52 download at FixCentral here.
New fixes for Connections 6 and Orient Me 184.108.40.206 have been released on FixCentral. You can find the Connections 6.0 Fix here. Orient Me 220.127.116.11 can be found here. This is new for Orient Me: Support for a high availability solution. New installation package. Enhanced documentation to describe the upgrade process. Additionally, there is new information on connecting to Connections services on a windows server and managing Redis authentication. Support for these security proxies: ISAM SiteMinder SAML SPNEGO
In one of my environment Orient Me suddenly stopped working and even a reboot of your Linux machine did not help. My colleague Matt Milza pointed me in the right direction to solve this issue: Check your systems disk space with df . You may be seeing that your / has run out of space: Unfortunately there is a bug in the first release of Orient Me that will continue writing logs into /var/lib/elasticsearch/data/elasticsearch-default/nodes/0/indices until all space is used: The solution is simple: Delete all content in this folder ( rm -rf * ) and restart your machine. Then Orient Me should be happily…
Given that Orient Me is based on technology unfamiliar to many folks that had been working with Connections before, some people might be struggling with installing it. I have created a guide that should help you getting it running for a demo environment with everything from Orient Me (Kubernetes, Docker, all Boot-, Master- and Workersnodes) on a single CentOS image and help you integrate it with your Connections 6.0 server.