Tag: Early Access Program

Domino Early Access Program drop 2 is available

HCL Domino 12.0.2 Early Access Drop 2 is available for download on flexnet.

HCL Domino 12.0.2 Early Access Program drop 2 provides these new features and enhancements:

  • A new tab in the Server document, NIFNSF, allows you to configure moving database view indexes out of databases. Previously, you configured this feature through server notes.ini settings.
  • DAOS Encryption Manager (daosencmgr) now provides the -O [outfile] option to output command results to a specified file. In addition, the DAOS_ENCRYPT_MGR_ENABLE=1 notes.ini setting is no longer required to enable it.
  • Building or rebuilding views take 5-10% less time with Domino 12.0.2.
  • C API OSLoadLibrary changes
    On Windows, if a fully qualified path is not specified for a library to be loaded, the C API OSLoadLibrary no longer searches the path for the library. Instead, by default, this API searches the Notes or Domino executable directory, the Windows System directory, and the Windows directory. You can use notes.ini variables of the format OSSL_<#>= to specify up to five additional locations to search. For example: OSSL_3=”d:\Application\Libraries”. Full details of this this change will be available in the next release of the C API SDK.
  • Smart Server Startup
    A new feature called Smart Server Startup prevents users from connecting to a Domino server until it is fully up and ready to accept user requests. For example, if a server crashes, Smart Server Startup allows users to connect to it only after the server has fully recovered. To see Smart Server Startup activity during server startup, use the notes.ini setting debug_qos=1. To disable the feature, use the notes.ini setting DisableSmartServer=1.

Testing new DataBase methods in Domino V12 Early Access without Domino Designer V12

Domino V12 Early Access CodeDrop 3 comes with a couple of new Java/LotusScript transaction methods that have been added to the (Notes)Database class.
At the moment, there is no Domino Designer V12 available. So how can we test the new methods?

If you are familiar with Java, then this is possible, because Java development not neccessarily needs Domino Designer.

All we need is the Notes.jar file from the V12 Domino Docker container.

To access the Domino V12 program directory you can use the commands as described in https://help.hcltechsw.com/domino/earlyaccess/inst_dock_useful_commands.html

or you can create a volume and access the program directory in the same way as you do with the data directory.

docker run -it -p 80:80 -p 443:443 -p 1352:1352 --hostname=serv03.fritz.box --name domino12 --cap-add=SYS_PTRACE --stop-timeout=90 -v notesdata:/local/notesdata -v d12:/opt/hcl/domino/notes/latest/linux domino-docker:V1200_10082020prod

Now that you have access to the Domino V12 program directory, copy the Notes.jar file located in /opt/hcl/domino/notes/latest/linux/ndext to your development environment.

I have created a small JaveServerAddin based on the work of Dmytro Pastovenskyi https://dpastov.blogspot.com/2020/10/javaserveraddin-in-domino-introduction.html.

You can download the sources from here

JavaServerAddinDownload

In the BuildPath change the location of Notes12.jar to the location of Notes.jar in your environment.

To build the project, change to the bin directory inside the project and issue the command 

jar cfe D12Test.jar Domino12Test de

Copy the resulting .Jar file to the ndext folder in the Domino V12 program directory. Make sure to set the correct execution rights ( 755 ). Now you can start the addin with 

lo runjava de.eknori.Domino12Test

After the addin has started you will see the following on the Domino console

11/01/2020 05:45:15 Domino12Test: version 2
11/01/2020 05:45:15 Domino12Test: build date 2020-10-22 11:00 CET
11/01/2020 05:45:15 Domino12Test: java 1.8
11/01/2020 05:45:15 Domino12Test: seconds elapsed 30

During the next scheduled addin run, the code will create a new document in the d12test.nsf. You need to create this database on your server before running the addin. The database does not need to contain any design elements.

When the addin ran, you should see new documents in the database created with a form “commit”.

You should NOT see any documents that have a “rollback” form.

The same way, you can also test the new DQL enhancements in V12 Early Access Code Drop 3.