Wednesday, 18 July 2018
On August 2 a very interesting webinar will be organized by IBM, Introducing Domino Apps on Cloud. The registration for this webinar is available on the IBM website.
Today, IBM Domino Applications on Cloud is a Bring Your Own License (BYOL) subscription service that offers an IBM-hosted solution for Domino Applications on IBM Cloud. The service offers robust performance and high availability for mission-critical applications. It is offered as a managed service and can eliminate the cost, complexity, and risk of managing your own Domino application infrastructure.
But all of this is about to change. What if we told you, that you no longer have to maintain separate licenses for the service?
Join our subject matter experts Andrew Manby, Director of Product Management IBM Collaboration Solutions, and David Byrd, Distinguished Engineer - CTO, WW Lab Services and AVP IBM Collaboration Solutions, at this webcast to learn about new non-BYOL editions and service capabilities being announced for IBM Domino Applications on Cloud.
Learn how you can move your Domino workflow and other applications to the IBM Cloud for a secure, scalable and cost-effective way to manage them, and how to create a seamless experience for your Domino application users.
Title: Introducing Domino Apps on Cloud
Date: Thursday, August 02, 2018
Time: 10:00 AM Eastern Daylight Time
Duration: 1 hour
For more information about #domino2025 visit the Destination Domino webiste.
Don't forget, the brand new #domino2025 Product Ideas Lab website is up and running! So don't hesitate and submit new ideas to make Domino even better!
Geplaatst door Johnny Oldenburger op Wednesday, July 18, 2018
Monday, 16 July 2018
This application has failed to start because nsdhelp.dll was not found.
However the problem was resolved within a few minutes. After a quick tweet I almost immediately got a reaction from IBM Champion Oliver Busse. To solve the problem the nsdhelp.dll file could be copied from another Domino environment 9 (or backup) to the new Domino installation. With this the problem was indeed solved and the Domino Server could be started without any problems.
What do we have a great community in which everyone helps each other. Amazing!
The brand new #domino2025 Product Ideas Lab website is up and running!
This is the place where you can submit product ideas and enhancement request. IBM encourage everyone to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated jointly by the IBM & HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
So don't hesitate and submit new ideas to make Domino even better!
For more information about #Domino2025 visit the Destination Domino website.
Monday, 25 June 2018
In my recent role as Domino Administrator I picked up a number of tasks including monitoring our Domino Servers. Last week I watched episode 5 of the great #Perfect10 webcast by Gabriella Davis. In this webcast Gabriella mentioned the use of the Domino Domain Monitoring which is shipped with the Administrator Client. Below some basic information ans some links to useful resources for setting up the Domino Domain Monitoring. During the past few days I have set up the Domino Domain Monitoring further and this works correctly. The Domino Domain Monitoring database provides important information about our servers, the identified problems and possible solution. For every administrator a must to use together with the Domino Configuration Tuner (more information about the Domino Configuration Tuner in my previous blog post Using the Domino Configuration Tuner to Evaluate Server Settings). Domino Domain Monitoring (DDM) provides one location in the Domino Administrator client that can be used to view the overall status of multiple servers across one or more domains and then use the information provided by DDM to quickly resolve problems.
The UI for DDM is made up of two databases, events4.nsf and ddm.nsf.
The Monitoring Configuration (events4.nsf) database is used for configuring probes and DDM Filters and contains all events and formulas for how corrective actions are completed.
The Domino Domain Monitoring (ddm.nsf) database is the database where the results of probes are reported. They can be viewed in several different ways such as by severity, date, etc. This database is also where events can be assigned to administrators.
From the Domino Domain Monitor database administrators can select an event and view detailed information about an event. The administrators can use the Probable cause and possible solution tab to view information about the cause of the event, and, in some cases, use a database link to access the appropriate database from which the administrator can resolve the event. Some DDM Event documents include a Details tab that displays additional details about the event and a Correlation tab that contains links to other DDM Event documents that may be related to the open DDM Event document.
The first time that a Domino server starts, the Domino Domain Monitor database (DDM.NSF) is created from the DDM.NTF template.
Probes are the backbone of Domino domain monitoring and require Domino because they are embedded into the new server and addin task code. Probes are set and stored in individual Probe configuration documents, which are stored in the Monitoring Configuration database (events4.nsf). Probe configuration documents contain Basics, Target, and Specifics sections in the Basics tab. Depending on the probe type there may also be a Schedule tab in the document. All probes are categorized by a probe type. For each probe type, there are one or more probe subtypes. The probe subtypes further categorize the function of the probe.
Finally filters control the volume of Events that appear in DDM.nsf. Filters are used to specify what type of Events should be included in the Domino domain monitor database, not what Events should be excluded.
For more information:
Lotus Education on Demand: Domino Domain Monitoring (DDM)
RedBook Lotus Domino Domain Monitoring
Video Domino Configuration Tuner and Domino Domain Monitoring
Geplaatst door Johnny Oldenburger op Monday, June 25, 2018
Thursday, 21 June 2018
In the context of #domino2025 I have so far heard little or nothing about the future of XPages in Domino 10 and Domino 11. Everyone is full of praise for the current #domino2025 path taken by IBM and HCL, which is a great path for the Notes Domino community, but we must not lose sight of the current reality including the future of XPages. During the past years we have had little or no major changes , updates or new features regarding IBM XPages. The question of whether XPages is dead as a development platform is therefore again a justified question. Today I followed a short discussion on Twitter about whether there is a future for XPages. As Jason Roy Gary mentiond in this short discussion the majority of the investment in the coming period (V10 - V11) will be in Node.js, Loopback and an open API strategy and not in XPages. This was confirmed by Barry Max Rosen, XPages is over 10 years old and IBM want to focus on new technology.
Below a short summary what we have seen during the latest Fix Packs / Feature Packs regarding changes, updates and new features for XPages.
Fix Pack 6, no fixes and no new features for XPages. Fix Pack 7, no fixes and no new features for XPages. Feature Pack 8, one new feature, document encryption/decryption on the Web and an upgrade to the latests XPages Extension Library. Feature Pack 9, only some fixes and again no new features for XPages. Feature Pack 10, no fixes and again no new features for XPages.
All in all a sad list of what has been invested by IBM in XPages lately.
Well, I will tune in next week to the webcast although I have my doubts when it comes to the future of XPages as a development platform. In my humble opinion there has to be a very good story for XPages in general and for XPages as a development platform in V10 and V11 to preserve XPages as a credible development platform for developers during the coming years. I would say, IBM surprise me with a good story for XPages in V10 and V11 and make me believe again in XPages as a development platform for the future.
So let's hope that also for XPages as a development platform a new chapter will begin in Domino 10 and Domino 11.
Geplaatst door Johnny Oldenburger op Thursday, June 21, 2018
Wednesday, 20 June 2018
In my recent role as Domino Administrator I picked up a number of tasks including monitoring our Domino Servers. Yesterday I watched episode 5 of the great #Perfect10 webcast by Gabriella Davis. In this webcast Gabriella mentioned the use of the Domino Configuration Tuner which is shipped with the Administrator Client. Until now we did not use this Configuration Turner. The Domino Configuration Tuner (DCT) evaluates server settings according to a growing catalog of best practices. All servers in a single domain can be evaluated together. DCT generates reports that explain the issues DCT uncovers, suggests mitigations, and provides references to supporting publications.
DCT comes with easy-to-use, self-service configuration analysis so that installations are more robust and experience improved performance. A single Domino server includes thousands of configuration options. DCT provides best practice analysis as well as worst practice disclosure, and helps reduce total cost of ownership by assisting users in identifying configuration problems. DCT looks at settings in the Domino Server documents, the NOTES.INI file, and advanced database properties. Configuration settings are flagged when their values are known to cause problems based on prior customer experience. Out-of-range and unexpected values are reported so that undefined behavior can be prevented. Suggested adjustments help you achieve known server performance improvements.
I followed the steps below to enable / use the Domino Configuration Tuner on our Domino servers.
1. Open the Domino Administrator Client.
2. Open the Tab Server - Analysis
3. Select Domino Configuration Tuner
5. After the update and the deployment of the updated files the local application will be created.
The final result are generated reports that explain the issues DCT uncovers, suggests mitigations and provides references to supporting publications.
After selecting the option Domino Configuration Tuner the message below appeared continuously (even after the restart of the Notes Client).
During the first update 6 files were successfully deployed. In the Status Bar the error message 'Unable to deploy one updated file (probably locked and in use)' is shown.
The solution for this problem is to run the Notes Client in Administrator mode after selecting Domino Configuration Tuner in the Domino Administrator Client. The Notes Client can then deploy the dct.jar file into its destination folder: %notes%/jvm/lib/ext.
For more information: Domino Configuration Tuner (DCT)
Geplaatst door Johnny Oldenburger op Wednesday, June 20, 2018
Sunday, 17 June 2018
As already indicated, a large part of the Notes Domino XPages community already lives in the Domino 10 bubble. And that's a very good thing. One of the new features in Domino 10 is the introduction of Node.js in Domino. As indicated in my previous blog post, a webinar will be hosted by IBM on June 28, Node.js and Domino V10 Essentials - What You Need to Know.
Yesterday I came across this message from Mark Barton on Twitter.
In order to get a good idea of how to use Node.js in Domino, this is a more than excellent starting point. It is an excellent course that gave me a good insight regarding Node.js in Domino. You can find the course on this website.
For more information about Node.js and Node-Red, see the blog series of John Jardin, Node-RED Blog Series.
Geplaatst door Johnny Oldenburger op Sunday, June 17, 2018