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 No Plans to Implement
Workspace Domino
Categories Administration
Created by Guest
Created on Dec 12, 2019

RELATED IDEAS

Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit DOMINO-I-634 Design Refresh handling of Agent (Scheduling) Properties option to only update program logic-leave server and schedule untouched..

Option when refresing databases to not overwrite, Agent Signer, Schedule and Enabled/Disabled state of Agents Merged

One of the biggest hassles for me administrating Domino servers is that every time we have new design changes I have to open the template, set the correct agents to be enabled/disabled, set the correct schedule for when the agent runs and set the correct server as Agent Signer as for where the agents should run.

 

These things are something that differs from server to server.  So I need to do this again and again, keeping track of what agents run on what server and if the correct server is set as Agent Signer.

 

It takes up so much time to go through each time and would be a relief not having to spend time on.

 

Would it be possible to add those two options when refreshing databases?

Don't overwrite Enabled/Disabled state
Don't overwrite Agent Signer or Agent Schedule settings (This would leave the Agent Signer and the Schedule as it is when refreshing.

  • Admin
    Thomas Hampel
    Reply
    |     Jan 8, 2020

    In terms of priorities this feature is less likely to be implemented. However we are keeping it here to gain more votes + see more demand to be considered for a future release.

  • Guest
    Reply
    |     Jan 8, 2020

    @Thomas, so for every agent we have we should have one more just to run it, that is not acceptable and are not something we are going to implement. We will end up having so many agents running on our servers. Wouldn't it be fairly easy to give us the option to choose whether or not we want these options to not be overwritten when refreshing the design of the databases?

  • Guest
    Reply
    |     Jan 7, 2020

    Yes, that would be a great addition to the Domino design and even make life easier for the Admin as well or for the person responsible for deploying new designs.

     

    @Thomas, I recognize your idea and that it may be a feasible way of doing it, but I fear that it would be too cumbersome for large scale deployments where you might have hundreds of agents besides other design updates. Not to mention that it would increase the number of design elements (agents) in templates and databases.

  • Admin
    Thomas Hampel
    Reply
    |     Jan 7, 2020

    You can solve this by using two agents. One agent that contains your sourcecode, and another agent (set to not refresh from template) which will only call the first agent. By that you can run design replace/refresh without messing up your agents.

    Is this an acceptable approach?

Copyright © 2023 HCL Technologies Limited