Welcome to the #dominoforever Product Ideas Forum! 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 HCL 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 around #dominoforever, please visit our Destination Domino Page
Automating the MongoDB install with a Sametime deployment is under consideration. For awareness, provided is a support article with a script for MongoDB installation with Sametime. The script still requires a separate MongoDB install, but it's purpose is to simplify the MongoDB install with Sametime.
Note: Please review the support statement in this article and the article will be updated to include MongoDB 6.0 support soon!
Script for installing and configuring MongoDB for HCL Sametime on CentOS or Red Hat
Reviewing the comments, support for Domino (.nsf) and other databases are continuously under review. Adding database support would be provided as options and not forcing one or the other. Keeping the focus of this idea to MongoDB install with Sametime, consider creating or voting on Ideas for additional database support.
Thank you for the idea and continued feedback!
Sametime could run without Domino, but I doubt that this happens very often. All my known parties use Sametime in conjunction with Domino. However, I'm not the Sametime sales manager. ;-)
Using NSF as an alternate would be great, at least for those companies with Domino.
I really don't see the benefits of an additionan database management system. Why MongoDB, if Domino is available?
I also would prefer the solution with a Notes database. As long as persistent chat and chat history is still available.
Having a all-in-one package with Mongo DB would be neat, as well.
All nsf and Domino for me, nice and simple.
We should stay with Mongo DB, many have already switched over. It runs stable and reliable. As I said before, if we have to switch back to Mongo DB, this will only lead to many admins not switching to a new version or not switching at all. That would have the consequence that HCL Notes would not get further. We need success with Notes and Sametime otherwise it won't work.
Hi Manfred,
We are looking into using Domino as chat history storage db. There are some Aha ideas created for this request. Please feel free to vote on those. We may provide different options to our customers. If you want to keep using Mongo, you can certainly do that.
Thanks for all your feedback. This helps us in making decisions around the product features that are important to our customers. Appreciate it.
OK, i already found some hints that Sametime 12 is supposed to use NSF as storage.
That makes the situation with Sametime 11 even worse. All the work for setting up Mongo DB manually for just 1 Sametime version...
NSF as replacement would be a good idea. But can this really be implemented?
What if we replace it with an NSF?