Engage 2019 – Part Two – Notes 11, Future of Connections and more!

After the exciting first two days, we continued at the same pace, the first sessions started at 8 o´clock. So after grabbing a few cafe cups and making some hard decisions on which Sessions to visit, I started going toward the presentation rooms. Just like in the previous post, I will list the Sessions I have visited and add some Information, which from my perspective is most important.

IBM Engagement Center Quickstart: Get your first Intranet pages up and running in minutes – by Martti Garden

In this Session, Martti unleashed the full power of ICEC and showed some tips and tricks, like resizing YouTube videos automatically, in order to “rock” any Connections Environment.

Notes 11 – by Ram Krishnamurthy

This got pretty interesting, by the way, as you can imagine, the room was completely full. Ram presented us the new Notes 11 Client. The Session consisted from three parts, first we got to see what HCL is striving to Achieve with the new release. We basically got a glimpse of how it should look at the end.

After that, we got to see the current state of the pre Beta release.

After the Design was presented, Ram explained us some technical differences and improvements which are going to be available on the new Notes 11 client.


IBM Connections: The Future is Bright – by Danielle Baptiste and Martti Garden

In this Session Danielle confirmed that HCL is going to continue to invest into Connections Platform, because of a strategic importance for HCL. Martti also showed us some new features which are going to come with the new CR Releases, like Integration with Slack! We also got to see what is coming with Connections 6.0 CR5, which is going to be released in the next two weeks. After the CR5, we should get at least two more CR Updates this year.

Domino on Docker Bootcamp – by Daniel Nashed and Thomas Hampel

Interested in running Domino (including Traveler) on Docker!? If that´s the case, then this was the session to be. Daniel and Thomas explained everything you need to know to “kick-start” your Domino deployment on Docker.

Domino and SSO – New Ways for secure collaboration – Round Table by Daniele Vistalli

In this Round Table Daniele presented his own Application/Solution for generating SSO Tokens, meant for environments or Use Cases where you can’t use SAML. The application is great, it is based on Domino and it shows just how versatile the platform is.

IBM Connections Customizer – Have it Your Way! – by Miki Banatwala

Miki showed us the true power and flexibility of IBM Connections Customizer. What I liked the most was the possibility to show different content based on different user groups.

Sadly could not visit all Sessions, every track had at least two or three sessions which were interesting to me, so it was always a tough call which session to choose.
Like always, the organization of the Conference was brilliant, many thanks to Theo!

Advertisements

Domino Mail Routing – A tip about Global Domain documents

Some time ago we had a request from a customer to make sure that the incoming SMTP mails, for a specific internet domain, are routed only to users who have Internet Address with this exact internet domain set in their Person Document.

The Domino Router task behavior, at that point was the following (extremely simplified):

  1. Router gets an E-Mail over SMTP for intended recipient john.doe@acme.com.
  2. Router searches the “names.nsf” for the recipient.
  3. Finds john.doe@acme-marketing.tv and delivers the mail to this user.

There was one Domino Global Domain document in the “names.nsf” with a lot of alternate internet domain aliases. So, this would mean that if the primary domain is “acme.com” and an alternate internet domain “acme-marketing.tv”, your users would be receive e-mails addressed with alternate domain even though they do not have it specified in their Domino Person document.

For one specific Internet Domain, this was not a way to go. The solution for this was quite simple, we needed to create a new Global Domain document with this Internet Domain specified as a Primary Internet Domain and remove the same domain from the first (“old”) Global Domain Document. This prevents the Domino Router task from looking up this Domain as Alias, thus making sure the E-Mails addressed with this domain are only routed to users who have this domain specified in their Person document.

After a new Global Domain document is created and you are satisfied with the config, restart the Domino Router task, to make sure that the change is picked up by the Router task.

This behavior is described, in detail, in the following article.

https://www.ibm.com/support/knowledgecenter/SSKTMJ_9.0.1/admin/conf_specifyinghowdominolooksuptherecipientsofincoming_t.html

Sametime Community Server – LTPA Token Name

If you are planning on changing the LTPA Token on a Sametime Community Server, save yourself a lot of pain by using the existing LTPA Document and keeping the default name “LtpaToken”. You may not get any errors on the console but the SSO using LTPA just won´t work.

If you want to enable Internet Sites on the Community Server, you should read the instructions in the following article:

http://www-01.ibm.com/support/docview.wss?uid=swg21157740

Changing Domino Transactional Logging Style

Different backup strategy/software can lead to the need for changing the Transactional Logging style on a Domino Server. There are basically two possibilities for doing this.

Possibility 1

  1. Disable Transactional Logging on a Domino Server.
  2. Shutdown Domino.
  3. Start Domino
    1. You should get a message: “Transactional logging being disabled after this restart”.
    2. “NLOGASIO” or “LOGASIO” should not start.
  4. Rename or delete the Transactional Logging directory.
  5. Restart Domino Server to confirm there are no errors.
  6. Enable Transactional Logging and set the Transactional Logging Style option you want.
  7. Restart Domino and again confirm there are no errors on the console.

This is a subtler approach, although this takes a considerate amount of time, you can make sure there are no issues before letting your server back into production. You can also keep the old transactional logs if by renaming the Transactional Logging folder.

On the downside, a consistency check will be run on every database opened, for the first time, and a new DBIID will be assigned. This can take a lot of time depending on the size of your databases.

Possibility 2

  1. Change the Transactional Logging style.
  2. Restart the Domino Server.
    1. If you are changing from “Archive” to “Circular”, you can delete or move the old Transactional Logs.

After this, no consistency check or database fixup is will be done and the databases keep their old DBIID.

Here are some useful URLs about Transactional Logging:

General Information

Best Practices

How to clean corrupt Transactional Logs