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
The sign bit operations are going away in Domino 14.5 EA2 and are replaced by a single log message which goes to console.log and log.nsf.
But keep in mind that AdminP sign operations are based on a request based model. OTS creates a request.
The new logging will allow you to monitor the log per database you sign.
Another way would be to look into admin4.nsf and look for the status of the requests.
But maybe you want to think about a different way to implement it.
You can run agents and sign them with the server.id before executing them.
"action": ["sign", "run"]
If you need more code to be signed then single agents, you can write Lotus Script code to sign a database before starting your other operations.
OTS signing of whole databases is mainly intended to kick off signing.
If you need the code to be executable immediately, that's probably the better approach.
Please have a look into the OTS HCL GitHub project.
https://github.com/HCL-TECH-SOFTWARE/domino-one-touch-setup
You find examples and can also raise issues if it is not directly a feature request.
Agree. And that would also be very useful if you develop XPages and have to sign with server prior to running....
I think an actionable event would be perhaps even better!