Skip to Main Content
HCL Domino 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

Status Assessment
Workspace Domino
Categories Administration
Created by Guest
Created on Mar 6, 2024

Updating of OTS V14 documentation necessary

As administrator I want to install and configure a V14 Domino server. I follow the instruction (Invoking one-touch Domino setup with parameters in a JSON file on Windows or UNIX) to run the OTS and can't start the Domino server with this commandline (in my Windows sandbox).

nserver.exe -autoconf c:\temp\setupFirstServer.json

With the hint from Rainer's blogpost "Running offline activities on databases with Domino V14" it works:

cd "\Program files\HCL\Domino\Data"
..\nserver.exe -autoconf c:\temp\setupFirstServer.json

Please update the documentation if this procedure is correct.

  • Attach files
  • Guest
    Reply
    |
    Jul 14, 2024

    There are multiple ways to run the setup. The pitfall you ran into is that the location of the notes.ini changed from program directory to data directory beginning with Domino 14 on Windows for a standard server (partitioned servers and Unix servers always had the notes.ini in the data directory).

    The notes.ini needs to be found by the server process when starting.
    A safe bet is always to specify the notes.ini via =c:\notesdata\notes.ini. This will always work.

    The documentation would need to distinct between different versions.

    Someone hitting the 14.0 documentation might configure a 12.0.x server and would run into the same challenge the other way round.

    The documentation has a feedback button on every page.
    AHA ideas are more for product features. The feedback on the documentation pages directly go into the right channel.