Announcing the IBM Domino V10 portfolio beta program: Sign up today

Make sure to sign up and take a look to the Domino V10 beta program.

Official Post

Beta 1: We will form an initial group of beta participants, based on the submissions received and then qualify and approve for beta program enrollment. Beta 1 will begin on June 25th, 2018.

What can be tested in Beta 1:

– Domino (Windows)
– Notes client (Windows)
– Notes, Designer & Admin clients (Windows)

This beta is English-only.

Beta 2: We will extend the initial group of Beta 1 participants as we get further along in the development cycle for Domino V10, by including additional participants at the Beta 2 stage. We expect the Beta 2 phase to begin the second half of July 2018.  Submissions received up to July 15th, for those not included in the Beta 1 group, will be considered for inclusion in the Beta 2 phase.

 What can be tested in Beta 2:

– Domino (Windows and Linux)
– Notes client (Windows and Apple Mac)
– Notes, Designer & Admin clients (Windows)
– Verse on Premises (Windows and Linux)
– DominoDB NPM package for Node.js

The goal of the IBM Domino V10 Portfolio Beta Program is for the community of beta participants to conduct honest, constructive and thoughtful review and testing of the Domino V10 beta software, which includes IBM Domino V10, IBM Notes V10, IBM Sametime V10 and IBM Verse On-Premises V10.

We’re seeking people who meet the following criteria:    

– A business end user, administrator, or developer, who has prior knowledge of Domino, Notes, and Verse.
– Those who bring diverse (role/industry/geography/company size) attributes to the beta team and, thus, ensure we get the right blend of input perspectives.

IBM is looking for participants to:

– Share their use case for the beta in their company.
– Engage in a dialog about Domino V10 and provide timely feedback.
– Be constructive and professional in all written/spoken interaction with program members, IBM and HCL.
– Attend the web conferences and meetings pertaining to the beta program.
– Experience the beta in a non-production environment.
– Be open to the idea of becoming a reference for IBM Domino V10.

Advertisements

Webcast – What’s new in Mail and Chat V10

Make sure you attend the Webcast about new Mail and Chat features in Domino V10, it takes place on 24th of May. Gabriella Davis will be one of the Speakers, so the webcast is surely going to be interesting.

Some of the “keywords”:

  • IBM Notes V10
  • IBM Verse on Premises V10
  • Sametime Chat V10

Details and a registration URL:

https://www-356.ibm.com/partnerworld/wps/servlet/ContentHandler/news/AYBJE6SP

 

 

 

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