#dominoforever | Product Ideas Portal


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

Provide a configuration possibility to redirect Notes client for a specific replica onto a specific cluster server

At the moment, if you have a cluster in place, users are accidentally (or by selecting icon on workspace) directed to replica R on cluster servers S1, S2 or S3. Therefore you can not plan as a Domino server hoster on which cluster server your users will be directed (e.g. if you have 1000 applications). With the new functionality, it would be easier to plan server capacity (e.g. if you can direct user onto cluster server S1 for application R1 and user onto cluster Server S2 for application R2). Additionally (at no cost) soft document locking would be working on cluster server.

  • Guest
  • Jul 18 2018
  • Already exists
  • Attach files
  • Guest commented
    11 Jan, 2020 09:33am

    Thanks for reviewing the idea. But sorry, I am confused.

    1. The referenced blog entry is about catalog replication, catalog ACL and update catalog entry functionality. Can you help me, where you find there details about Notes client connecting to a specific Notes application on a specific server?

    2. The lookup to the catalog by the notes client solves - in my opinion - only first/initial access to an application, and only in cases where users are not invited to a database/application by an invitation mail with a database link including a server hint... In my opinion this is a rare case. Standard case is - in my opinion - that user has an icon of the application on his workspace with a server hint to a replica. User receives a mail with a doc link to a document in the application. If user clicks on this link then the Notes client tries to open first the linked document on the server on which the icon on the workspaces pointed to.


    Today's solution for described situation/scenario above:
    The replica R1 on S2 is usually offline. If S1 is not available you have to take the R1 on S2 online. This is a manual process today.
    If you have several applications this is not practical. Therefore we implemented a mechanism to automate this, including the situation S1 come back and users are redirecting back to S1 (for R1 but not R2).
    Assumption in this scenario: There are a lot of other applications which uses standard cluster failover functionality on both servers.


    In my opinion this is something that Domino should provide natively.

    E.g. this would be possible to by adding the possibility to configure a main cluster server for some applications. Users trying to open the application on a cluster server not defined as a main cluster server are redirected to the replica on main cluster server.

  • Admin
    Thomas Hampel commented
    10 Jan, 2020 10:20pm

    You can improve your situation by reviewing your catalog strategy - the Notes client is looking up the catalog.nsf on the catalog server (if one is specified) or the home/mailserver. it will use the application from the first server that has a replica according to this catalog.nsf

    For more details please see http://blog.nashcom.de/nashcomblog.nsf/dx/domino-catalog-vs-domain-catalog.htm