We’re proud to announce the HCL Domino Early Access Programa new program that gives our customers and business partners a chance to test new product features early in the development cycle. This program provides a preview of features and functionality that may be shipped with a future version of HCL Domino and gives us the ability to incorporate your valuable feedback. At this stage, we are providing early access to features that contribute to HCL Domino v12. 

The Early Access Program aims to get feedback on specific features, with a more formal traditional beta program planned at a later stage to receive feedback on the overall release quality and language packaging. 

The Early Access Program is feature-driven and iterative, meaning new iterations and code drops will be made available as soon as it is declared ready for testing by our development team. New code drops can be provided in just a few weeks after the previous one, on short notice, without sticking to a fixed release cycle.  

Based on your feedback we may proceed, improve or adjust the feature, or in some cases withdraw the feature from the code stream. The following graphic illustrates this concept:

Each code drop is provided in the form of a Docker image which enables us to ship new iterations faster and to minimize the time to upgrade from one code drop to the next. You can expect us to deliver code drops at a fast pace as we want participants to have exclusive access to our latest product feature set. Please note that only the newest code drop will be available for you to download.

How to Participate

HCL Ambassadors who have registered Domino v11.0.1 Beta Preview will automatically be added to Domino Early Access Program. Customers and partners with a current Notes/Domino entitlement will also have access to the Early Access Program as of today. There is no need to register separately to participate.

For overall documentation of the Early Access Program, the specific testing scope, system requirements and instructions for deploying the Domino server on Docker, please refer to the release notes or see the online documentation here.

For in-depth information on the program, check out this deck presented on the recent DNUG online event here.

Upcoming Code Drop: Automating Certificate Management

The focus of this first code drop is testing a new feature planned for Domino v12 that allows administrators to automate the creation and management of SSL Certificates for Domino Web servers through the Let’s Encrypt® certificate authority.

Including support for Let’s Encrypt was a feature that was requested on the Domino ideas portal some time ago. We are using this idea as a starting point to modernize the handling of SSL certificates in Domino in general, e.g. by moving away from having to create and manually distribute *.kyr files to your servers.

  • For details about the new automated certificate management feature, please refer to the online documentation here.
  • If you like what we have done, vote for this feature in our Domino ideas forum here.
  • To provide feedback on this code drop, you need to have an HCL account to join the discussion in our forum here.

For general input and new ideas or feature enhancement requests, please use the Domino ideas forum here.

Next Code Drop: TOTP

In the next iteration of the early access program, we intend to provide TOTP (Token based One-Time Password authentication). Stay tuned for more information about the next code drop.

We want Domino to be built for you and by you! We’re excited to include customers and partners as part of the feedback loop as we work towards the release of Domino v12. We look forward to hearing from you!

Comment wrap
Further Reading
Digital Solutions | November 16, 2020
Updates Regarding HCL Notes v11 on Apple Big Sur
Apple officially released macOS Big Sur, its latest operating system, on Nov 12. We are aware that customers were unable to run the HCL Notes v11/11.0.1 client on a Mac after upgrading. Various fixes have been applied to allow HCL Notes to run on Big Sur. You can read our tech note here. This has all been resolved. The fix pack is available on Flexnet.
Digital Solutions | November 5, 2020
Remotely Debugging Java Applications with Domino 11
For Domino customers on v9 or 10, you might be familiar with debugging a Java agent remotely on IBM JVM using the following server ini’s and set Port 8000 in Debug Configuration from the Designer client: JavaEnableDebug=1 JavaDebugOptions=transport=dt_socket,server=y,suspend=n,address=8000  This will work up to Domino v10 but not on Domino v11. In fact, doing so will cause it to crash! This article is going to help developers looking for a way to debug Java agents remotely on Domino v11. The pre-requisites are:  Domino v11 or above on Windows Server 2016 / 2019. HCL Domino Console. Notes, Designer and Administrator Client v11 or above. Java agent to be debugged. Any Web Browser to run Java agent.  Domino v11 uses OpenJDK. With the above ini's enabled, both the JVMs would attempt to bind to same port (8000) and the second process that attempts to bind to this port would fail and crash. To overcome this problem, the idea is to remove the Port 8000 from the Debug and attach it to some other random Port.  First, you will need to add the below ini’s to the server’s notes.ini.   JavaEnableDebug=1  JavaDebugOptions=transport=dt_socket,server=y,suspend=n  Note that we are not binding the Debug to Port 8000 by omitting address=8000, as compared to ini which was set on earlier version of Domino.  The JVM will then pick a random port. To know the random Port number, simply quit and load http or run your Java agent from web browser and check the console from HCL Domino Console Program. You will need to restart http task after adding those ini’s to make it work.  Note down this Port number somewhere as you would need it in next step. (The server console in the Administrator Client doesn’t show the Port number information.) With your Port number, you are going to bind to the Debug from the Designer client. Go to Tools menu > Debug Server-side Javascript > Manage Debug Configuration You should land on the Debug Configuration window. Here you need to mention the Port number which you noted down from the HCL Domino Console...
Sending future mails from your HCL Notes Client
Have you ever wanted to schedule future emails from your Notes Client? Well, now HCL Domino supports scheduling email messages, which allows you to do just that. So, draft your email, assign it a send date, and sit back and relax. The email will be delivered by the router at the time you specify. This feature is very useful for scheduling announcements, newsletters, or any mail which you want to be delivered at a future specified time. You need to be on Domino v10 or v11 (using the Mail10.ntf or Mail11.ntf template) to be able to schedule messages to be sent in the future. Here’s how it works. The configuration document setting “Allow users to schedule a delivery time for messages” is enabled by default, so you don’t have to change anything in that document. You would make sure that the mail policy setting has the checkbox selected to enable the delivery option, as illustrated here. If you don’t have a mail policy, then you can create a new one. If you already have a mail policy, you merely update it. After creating or updating the mail setting, you need to give the following command to update the mail policy in the user’s mail file. Tell adminp process mail policy The next step is to restart the Notes Client, so that it will pull the new policy settings from the server. Advanced users can use this command from the command prompt of their client machine to update the policy on the client's side without restarting: C:\notes\ndyncfg -2 Once the settings are pulled by the Notes Client, you will see the following option in delivery options while sending mail: “Delivery Options at the user side.” Simply select the date and time for delivery and the router will deliver it at that...
a/icon/common/search Created with Sketch.