Welcome to the IBM Connections Product Ideas Lab! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by the IBM Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events, please visit our IBM Connections page.

If we install the non-Docker Elasticsearch environment, is it possible to switch later to the Docker-based ES?

This question was asked by a customer in a recent JUMP session:

Understanding and Configuring ElasticSearch for IBM Connections (on prem)



IBM Dev provided the following answer sometime later:

"Technically speaking, yes. You would need to install the new K8S or Docker based ES cluster then migrate (remote re-index) the data from old standalone ES cluster (after disable client certificate based authentication).
As we have not tested or documented how to do this yet however, we unfortunately would not be able to Support such a procedure."


This Enhancement Request is a request therefore for IBM to officially support such a migration path (from standalone ES to Component Pack ES) in the future.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Nov 22 2018
  • Under review
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    November 23, 2018 07:35

    This would be a really important feature. ES became more important with CR3, and we want to make use of it, but we do not want to set up a full Docker environment by now. So we really need a supported way of migrating from standalone to Docker, when it is time to do so.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    20 May 14:44

    Another customer requests this support/documentation. Please advice.