Category: Domino

Today i upgrade one server to Domino 11.0.1 from Domino 11.0 on linux.  When the server starts the HTTP  the console show the error bellow:


[103028:000002-00007F2CD562E740] 06/18/2020 10:40:45 AM JVM: Java Virtual Machine initialized.
[103028:000002-00007F2CD562E740] 06/18/2020 10:40:45 AM HTTP Server: Java Virtual Machine loaded
[103028:000002-00007F2CD562E740] 06/18/2020 10:40:50 AM HTTP JVM: java.lang.reflect.InvocationTargetException
[103028:000002-00007F2CD562E740] 06/18/2020 10:40:50 AM HTTP JVM: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[103028:000002-00007F2CD562E740] 06/18/2020 10:40:50 AM HTTP JVM: at sun.reflect.NativeMethodAccessorImpl.invoke(
[103028:000002-00007F2CD562E740] 06/18/2020 10:40:50 AM HTTP JVM: at sun.reflect.DelegatingMethodAccessorImpl.invoke(
[103028:000002-00007F2CD562E740] 06/18/2020 10:40:50 AM HTTP JVM: at java.lang.reflect.Method.invoke(
[103028:000002-00007F2CD562E740] 06/18/2020 10:40:50 AM HTTP JVM: at
[103028:000002-00007F2CD562E740] 06/18/2020 10:40:50 AM HTTP JVM: at
[103028:000002-00007F2CD562E740] 06/18/2020 10:40:50 AM HTTP JVM: at
[103028:000002-00007F2CD562E740] 06/18/2020 10:40:50 AM HTTP JVM: at java.lang.ClassLoader.loadClass(
[103028:000002-00007F2CD562E740] 06/18/2020 10:40:50 AM HTTP JVM: at
[103028:000002-00007F2CD562E740] 06/18/2020 10:40:50 AM HTTP JVM: Caused by:
[103028:000002-00007F2CD562E740] 06/18/2020 10:40:50 AM HTTP JVM: java.lang.ClassNotFoundException: No class loader available for the bundle: [226]
[103028:000002-00007F2CD562E740] 06/18/2020 10:40:50 AM HTTP JVM: at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(


The solution was to delete all content of the folder /opt/lotus/notes/latest/linux/osgi/shared/eclipse/plugins and run the installer again.

Domino Linux

Just setup this on a customer today. Befor this setup you need to install a certificate on your server.

SMTP sessions conducted over a standard TCP/IP channel are vulnerable to eavesdropping because the unencoded transmission can be easily intercepted. To protect SMTP communications, servers can use transport-layer security (TLS), more commonly known as SSL encryption, to provide privacy and authentication.

Some servers support SSL for SMTP communications by sending and receiving SMTP traffic through the SSL port (port 465 by default) only. However, because this requires that both the sending and receiving servers support SMTP over SSL, this solution isn’t always practical.

To provide SSL security for SMTP transfers over TCP/IP, Domino® supports the use of negotiated SSL. In a negotiated SSL scheme, the sending and receiving hosts each use the SMTP STARTTLS extension, defined in RFC 2487, to signal their readiness to negotiate an SSL connection. The receiving server displays the STARTTLS keyword in response to the sending server’s EHLO command. The sending server issues the STARTTLS command to request the creation of a secure connection. After the initial TLS handshake completes successfully, the two parties proceed to set up an SSL channel between them. Both the sending and receiving server must possess SSL certificates.

Supporting STARTTLS for outbound SMTP sessions

A Domino server configured to use negotiated SSL for outbound mail connects to the receiving server’s SMTP TCP/IP port (port 25 by default). If the initial SMTP response from the receiving server indicates that it supports the STARTTLS extension, Domino issues the STARTTLS command to request the use of SSL to encrypt the rest of the session.

If the receiving server did not advertise support for STARTTLS in response to the Domino server’s EHLO command, the sending Domino server continues with an unencrypted SMTP TCP/IP session.

To enable outbound STARTTLS support, set the SMTP outbound TCP/IP port status to: Negotiated SSL.


I’m working on projects that involve many technologies and frameworks.

Particularly in one of our projects the IceGuard many things have been used such as Flutter for mobile application, Node-Red for  integrations,  IBM Cloud and IBM Watson IoT services.

We have reached a point where an asset management application such as sensors and gateways is required.

The application has the requirements:

1 – Run OffLine and Web

2 – Data replication

3 – Authentication and  Data security

4 – Integration with other applications.

5 – Implement a simple flow of approval.

Another detail is that we needed it to be developed rapidly.

Much is said that the Lotus IBM HCL Notes & Domino is dead.

Not for my case. If I were to use another product (s)/technologies I would spend two working days at least to architect the entire application, choose the Framworks to do the job, not to mention  database modeling,  authentication service, etc., etc.

With the HCL Notes & Domino i create the application in just one day!

It is a simple application, but that solved a real problem of my project.

Notes & Domino do the job.


As of April 10, 2018, Google has deprecated Google Cloud Messaging (GCM). The GCM server and client APIs are deprecated and will be removed as soon as April 11, 2019. IBM Traveler uses GCM for push notifications with IBM Verse for Android clients. Firebase Cloud Messaging (FCM) is the new supported notification infrastructure. This flash details what actions should be taken for IBM Traveler and the IBM Verse for Android clients to support the FCM notification infrastructure.

More information on this link

Domino verse

I miss some webinars about Domino V10 . Here is the link to Collaboration Solutions Webinars records

Comunidade Domino

IBM Verse is a powerful cloud-based email experience. It’s optimized for web browsers and mobile devices. It helps you focus on your top priorities and take control of action items. This one hour course will help you get started.


With the launch of Domino 10  knowledge of JavaScript and how to work with JSON Objects will be required for the new development model.

As i am working on a IoT project  i need to learn JSONata to manipulate lots of JSON objects.

JSONata is underpinned by the semantics of the location path inspired by XPath, the ability to format the output into any JSON structure inspired by XQuery, and the functional programming model inspired by Scheme.

The semantics of the location path inspired by XPath

  • Simple and intuitive syntax for selecting values within a structure.
  • Powerful predicate mechanism for complex queries and data joins.
  • Built-in functions and operators for manipulating and aggregating data.

The ability to format the output into any JSON structure inspired by XQuery

  • Standard JSON syntax used for constructing new objects and arrays.
  • Any valid JSON data is also a valid JSONata expression.
  • Allows template style queries to be constructed.

The functional programming model inspired by Scheme.

  • Implements the ‘metacircular evaluator’ described in SICP.
  • Supports user-defined functions (closures).
  • Turing complete.

The lightweight footprint of the runtime processor enables it to run in the web browser or as a node.js module with no package dependencies.

Take a look at


Domino 10 beta 2 started last week. I download the files and wish to run it on docker.

I follow Tim Clark’s blog series about Domino 9.0.1 on Docker.

I change a few lines on dockerfile (just change the installation file name).

Another difference was the line to start the container. I add the port 8585 to do a remote setup

docker run -it -p 1352:1352 -p 8888:80 -p 8443:443 -p 8585:8585 –name Domino10Beta -v domino_data:/local/notesdata kenio:Domino10Beta2



An issue was introduced in Domino 9.0.1 FP9 that could result in SMTP mail headers with random characters inserted into From, Sendto, and Copyto fields. This could then result in non-delivery of mail to/from Internet email addresses when using the Domino notes.ini parameter SMTPVerifyAuthenticatedSender=1.

Symptoms of the issue include receiving messages containing garbled sender names. Opening the message and replying results in a number of embedded garbled characters in the header. You can observe this by viewing the page source or by simply examining the content when opening an email. Another method is to capture the SMTP outbound message and examine the header.

Fix Available:
This issue is tracked as SPR# JCARAQSJB6 and is fixed in Domino 9.0.1FP9 Interim Fix 1. For download links, go to the Domino tab in technote 1657963Interim Fixes & JVM patches for 9.0.1.x versions of IBM Notes/Domino & add-ons.


IBM® Domino® Community Server for Non-Production will be a nonwarranted license option that enables your organization to test applications in a non-production environment. This offering will provide students, developers, and vendors with the capability to test their custom IBM Domino applications.

Announcement letter here



IBM Traveler enabled by default a feature that allows Traveler to “Run as a User” instead of as a server. This feature resolves several long standing issues with accessing the user’s data as the server ID.

The last point above may cause sync issues for mobile users. If the access controls are inadvertently set to values that restrict individual users, but do not restrict the Traveler server, then users that could sync when running as the Traveler server ID might not be able to sync when running as their user ID.

Note that the Traveler administrator can disable the Run as User feature by setting the notes.ini value NTS_USER_SESSION=false on all Traveler servers and restarting the servers. This may be a quick way of restoring sync capability to the few affected mobile users with restrictive access control settings. However, it is not recommended because it is a global setting, so all users will lose the benefits of Run as User when it is disabled.

Read the technote here

Domino TechNote

Last week a customer ask for a change in his Domino mail group management.

Some people with the right to change groups (with the role GroupModifier) made a change on several groups and a big problem arrives with mail routing to this groups.

The question was: How prevent Group Modifiers to modify some groups on Domino?

O only found one solution : Change the permission on the group document.

I created a simple agent and modify the group field “DocumentAccess” and put the Role ServerModifier. (Only admins has this role on Domino Directory) and also change the Group Owner to the group Administrators.

The simple agent is bellow.

FIELD DocumentAccess := “[ServerModifier]”;