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 Needs Review
Workspace Domino
Categories Administration
Created by Guest
Created on Oct 26, 2021

Don't update java.policy file if it is not changed at all in future Domino Fix Pack Installer.

One of our customer has their own setting in java.policy file on Domino 11.0.1 environment.

After installed Domino 11.0.1 FP4 on this server, he found the existing java.policy file was overwritten by Domino 11.0.1 FP4 installer. This customer has to add their own setting again to java.policy file provided by FP4.

Compared with the java.policy file provided by Domino 11.0.1 and previous Fix Pack, the content of the new java.policy provided by FP4 has to change at all.

Because java.policy file can be customized by customer, this customer wish HCL don't update java.policy file if it is not changed at all in future Domino Fix Pack Installer.

  • Attach files
  • Guest
    Oct 29, 2021

    Additional ideas:-

    If it is necessary to overwrite java.policy, keep a backup copy of the previous version of that file.

    Better yet, if java.policy needs updating, prompt the user whith three choices: Overwrite, preserve previous, edit manually (similar as with many installers in the Linux world).