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

Add a new idea Subscribe
Status Needs Review
Workspace LEAP
Created by Guest
Created on Mar 6, 2023

RELATED IDEAS

Ability to change paths to databases for configurated services afterwards in Domino Leap

We have a productive and a test environment. If we want our Domino Leap application to run correctly in the productive environment, we currently have to make sure that the path to the database used in the configurated services on the productive server is the same as on the test server and that the database has the same name (e.g. application.nsf ) as on the test server. Then it works.

However, when we develop Domino Leap applications for customers, it is rather unpleasant that we have to create the same folder structure for the DB used on our test server as in the customer's productive environment, because we are not able to change the paths to the used databases afterwards. Here we would like to be able to subsequently select the right database again for the services, instead of having to create completely new services or provide the right path.

  • Attach files
  • Guest
    Reply
    |     Jun 18, 2024

    A possible solution could be to have some kind of database alias configured inside the app or maybe better in the LEAP configuration database. When creating a new service accessing a domino database you should have the option to use one of these aliases in addition to the list of all databases on the server.

    If this will be stored inside the app itself then upgrading the app should not overwrite the alias configuration or at least ask before changing the configuration.

    I think it would be sufficient if the alias is replaced with the actual database path during implementation/deployment of the application and not at runtime on every service call.

    This would allow to have different database locations on different environments (develop / production / customer) without having to change /recreate the services on each app import/upgrade.

Copyright © 2023 HCL Technologies Limited