If you’re getting ready to download Domino 10 tomorrow (and who amongst us isn’t) and you want to use Domino Query Language (DQL) , HCL & IBM have already published a short list of behaviours that you should know about a few of which will change in 10.0.1
Read the technote here
Read the documentation here
you may need your IBM login
If you have trouble installing Notes 9.0.1 on Mojave with the installer erroring with
“File /Applications/Notes.app/Contents/MacOS/rcp/rcplauncher not found. Provisioning process failed to launch or was terminated before status could be determined.”
a very quick reminder for this error that occured first on the APFS file system using High Sierra – make sure you have downloaded the 9.0.1 installer from March 9th this year (passport advantage code CNQY7EN) and not the original one from 2015. The one from March will install correctly and then let you install the IF16 fix (901IF16) from IBM Fix Central that was released on September 24th on top to support Mojave.
If you already had Notes installed prior to upgrading to Mojave the IF16 fix installed on top should just work, this is primarily for new installs.
I would suggest going ahead and get rid of your 2015 9.0.1 client installers and get the new 2018 one in place just to be safe
This is my presentation from Icon UK on Thursday 13th September. There are lots of TCO features coming in Domino 10 that I’ve been working with and look forward to putting into production. In this presentation I cover things like cluster symmetry, pre send mail checking, deletion logs and the newrelic statistics reporting.
Say it with me….
28 days until the Domino 10 release.
So much interesting activity going on around the IBM/HCL products so in case you missed them I thought I could summarise for you. All are worthy of your time if you care about the future of Domino, Traveler, Verse or Sametime
Firstly – no time to lose – the registration for Beta 2 of Domino , Notes and Traveler closes TODAY at 12pm EST/5pm GMT. If you want access to that Beta due this month hopefully then go and sign up here now https://www.ibm.com/blogs/collaboration-solutions/2018/06/11/announcing-ibm-domino-v10-portfolio-beta-program-sign-today/. Don’t leave it then be disappointed when you don’t get access.
If you have ideas for what you want in Domino, Notes, Traveler, Sametime or anything else – there is a new site (requiring no login) where you can add your ideas and vote on other people’s. It’s been running for a few weeks and there are some great ideas there already to vote for so it’s a good place to browse during your next coffee break. Remember the rule – if you don’t ask you don’t get https://domino.ideas.aha.io/ideas
HCL are publishing a series of videos showing how features that are in v10 will behave. Here are three interesting features announced so far.
Next up in “cool admin things coming your way in v10” – folder syncing. By selecting a folder on a cluster instance you can tell the server to keep that folder in sync across the entire cluster. The folder can contain database files (NSFs and NTFs) but also NLOs.
Well that’s just dumb Gab.. NLOs are encrypted by the server ID so they can’t be synced across clustermates but a-ha! HCL are way ahead of you. The NLO sync involves the source server decrypting the NLO before syncing it to the destination where it re-encrypts it before saving.
So no more making sure databases are replicated to every instance in a cluster. No more creating mass replicas when adding a new server to the cluster or building a new server and no more worrying about missing NLOs if you copy over a DAOS enabled database and not its associated NLO files.
If you follow this blog you know that v10 of Domino, Sametime, Verse on Premises, Traveler etc are all due out this year and I want to do some – very short – blog pieces talking about new features and what my use case would be for them.
So let’s start with FILE REPAIR (or whatever it’s going to be called)
The File Repair feature for Domino v10 is designed to auto repair any corrupted databases in a cluster. Should Domino detect a corruption on any of its databases that are clustered, it automatically removes the corrupted instance and pulls a new instance from a good cluster mate. Best of all this happens super fast, doesn’t use regular replication to repopulate, doesn’t require downtime and the cluster manager is fully aware of the database availability throughout.
I can think of plenty of instances where I have had a corrupted database that I can’t replace or fix without server downtime. No more, and another good reason to cluster your servers.
In this 5th episode of my #Perfect10 webcast I look at how to identify any performance issues in your Domino environment prior to upgrade. Assuming most people will be doing an in place upgrade, we want to resolve or at minimum document any existing issues before starting