Quantcast
Channel: XPages and more
Viewing all 628 articles
Browse latest View live

Domino 10 - Programatically Schedule Mail Using LotusScript

$
0
0

In my previous blog post Domino 10 - New Administrator Feature to Push to Notes Clients: Scheduled Messages I described the new Domino 10 feature scheduled delivery of mail messages. As mentioned in the blog post the new Domino 10 Mail Servers supports scheduled delivery of mail messages. For example a user can compose a new mail message during the weekend and schedule the delivery of the email to be sent during the next work week. Scheduled messages are stored in mail.box on the sender's Mail Server. The router delivers or routes the messages at the scheduled time. Scheduled mail is enabled on a Domino 10 Server by default. In the Server Configuration Settings document in the Domino directory it can be disabled by the Administrator.
Scheduled messages are supported for Notes client users with mail files that are upgraded to he Notes 10 Mail Template (mail10.ntf). The feature is not supported for IBM iNotes, IBM Verse or IBM Traveler clients.
In this blog post I will describe how you can programatically schedule mail using LotusScript.


Scheduling mail programatically
To programatically schedule mail messages you must use the Summary DateTime item $SendAt to cause a message to be scheduled. Below a basic example using a simple function which is called form an Action Button on a Notes form.

A. Function ScheduledMail
In the Funtion ScheduledMail I use a Variant sendTime which indicates when the mail should be sent. The value of the Variant sendTime in the Function ScheduledMail is replaced in the field $SendAt to cause the message to be scheduled on the Domino Server.

Function ScheduledMail(note As NotesDocument)
Dim session As New NotesSession
Dim db As NotesDatabase
Dim memo As NotesDocument
Dim body As NotesRichTextItem
Dim sendTime As Variant
Dim linkDoc As NotesDocument
Dim sendTo As String
Set db = session.CurrentDatabase
Set memo = db.CreateDocument
Call memo.ReplaceItemValue("Form", "Memo")
Call memo.ReplaceItemValue("Subject", "Review IT Ticket Solution")
sendTo = note.mailuser(0)
sendTime = Today + 8 + TimeNumber(8, 0, 0)
Call memo.ReplaceItemValue("$SendAt", sendTime)
Call memo.ReplaceItemValue("SendTo", sendTo)
Set body = memo.CreateRichTextItem("Body")
Call body.Appendtext("Please review this IT Ticket: ")
Call body.Appenddoclink(linkDoc, "", "")
body.Update
Call memo.Send(False)
End Function

B. Mail.Box
If the user selects the Action Button on the Notes Form the function ScheduledMail is called and the mail is not send immediately but is placed in the Mail.Box on the Server as a Pending Message.


By using sendTime = Today + 8 + TimeNumber(8, 0, 0) in the Function ScheduledMail the Scheduled Time for the Mail Message is set on 14-11-2018 08:00:00.


The above function can be easily adjusted so that the users can enter the scheduled date and time themselves. Another great new feature in Domino 10. In my next blog post more about scheduling messages using @Formula.

Domino 10 - Synchronize Database Replicas - New Option Replicate Command

$
0
0

This last blog post concerning the new IBM Domino 10 Administrator features  is meant purely for my own documentation in case I need the new replicate command in the near future. In IBM Domino 10 there is a new option for the Replicate command for Domino Administrators, -F, to force a full database replication when replicas of a database get out of sync. The replication takes place on the side and allows users to continue to see replication updates during the full replication. Administrators can use  the -L argument to log information about the documents (notes) that would replicate if the new option -F is used but without actually performing the replication. Until now the only option for Administrators to perform a full replication of content was by clearing the replication history. Be aware that for large databases a full replication can take time and delay the replication of new updates until it is complete. For example if the replication history of a mail file is cleared the mail user might not see new mail until the full replication completes.

To force a full replication Administrators can now use the following server command: replicate <server> <database> -F.
Example: replicate MS-DOMINO10/ALM mail\jdomino.nsf -F

Administrators can use the -L option to log details about the documents (notes) that would replicate if the -F option is used but without actually performing the replication. For example: replicate MS-DOMINO10/ALM mail\jdomino.nsf -L

Since I currently not have any replica's out of sync I don't get all the output as mentioned in the IBM documentation as shown below. Based on the new replicate command -F and the -L option to log details the output will look something like this on the Domino console.

[17F8:0002-1028] NoteRepl: CN=Mail\O=MSDOMINO10!!mail/jdomino.nsf to mail/jdomino.nsf Since 07/27/2018
 Replicating from remote replica (jdomino) to local replica (pull). Since = The replication history from 
[17F8:0002-1028]  07-11-2018 08:28:57 Starting replication with server Mail\MSDOMINO10
[17F8:0002-1028]  07-11-2018 08:28:57 Pulling mail\jdomino.nsf from Mail\MSDOMINO10 mail/jdomino.nsf
[17F8:0002-1028] NoteRepl: UNID 7235FD43:BB0874BA:852582A2:0052CF6C Cls 1
UNID and Cls = NoteClass
[17F8:0002-1028] Src: NID A96 SN 2 ST 07-11-2018 08:15:07  Mod: 07-11-2018 8:15:07
Source note info (in this case the source is the remote replica), NID = NoteID, SN = Sequence number
[17F8:0002-1028] Dest: NID 0 SN 0 ST Did not repl
Destination note info. "Did not repl" means that it should have replicated in the past, but the [17F8:0002-1028] NoteRepl: mail/jdomino.nsf to CN=Mail\O=MSDOMINO10!!mail/jdomino.nsf Since 07-11-2018 Replicating from local to remote. Since = Replication history from last push
[17F8:0002-1028] 07-11-2018 08:28:57  Pushing mail/jdomino.nsf to Mail\MSDOMINO10 mail/jdomino.nsf
[[17F8:0002-1028] NoteRepl: UNID 29BD9D7B:04808407:852582A2:0052CF6E Cls 1
[17F8:0002-1028] Src: NID A9E SN 2 ST 07-11-2018 08:28:43  Mod: 07-11-2018 08:28:43
[17F8:0002-1028] Dest: NID A9E SN 1 ST 12-10-2018 11:04:35 Waiting to repl
"Waiting to repl" means that this note will replicate the next time the databases replicate. [17F8:0002-1028] 07-11-2018 08:28:57 Finished replication with server Mail\Renovations
[17F8:0002-1028] 07-11-2018 08:28:57 AM Database Replicator shutdown

Another great new IBM Domino 10.0 Administrator feature. In my next blog post more about advanced search capabilities and query definitions in Notes databases using LotusScript.

Domino 10 - New Administration Feature: Document Deletion Logging (2)

$
0
0

As I mentioned in my blog post Domino 10 - New Administration Feature: Document Deletion Logging there is a new server compact option available in Domino 10 to enable logging of data about deleted documents in databases that can be specified. The deletion logging data is logged to entries in deletion log files added to the IBM_TECHNICAL_SUPPORT directory on the Domino Server. In my previous blog post I did not mention the possibility to log (field) items. Administrators can log up to four field values in a deleted document to help identify these documents. The items are specified when Administrators enable deletion logging for a specific database. Although Administrators can specify more than four field values only the first four that are found are shown in the log entries. Below an example enabling deletion logging in a mail database including four items.


The results of enabling deletion logging is that when documents are deleted from a specific database entries are added to the current deletion log file, delete.log. When the server is restarted a new deletion log file is created. Old deletion log files are renamed to delete_<servername>_yyyy_mm_dd@hh_mm_ss.log. As mentioned before the log files are stored in the IBM_TECHNICAL_SUPPORT directory. Below some examples from the log file including the logged (field) items.


delete_ICEDEARTH_2018_11_09@18_15_18.log
"20181109T183422,40+01","mail\joldenbu.nsf","C125832B:005DADBF","nserver","CN=Johnny Oldenburger/O=ALM","SOFT","0001","5CED9FCF:EF17A075C1258340:006074A4","Form","4","Memo","Subject","22","Items Deletion Logging","DeliveredDate","19","09-11-2018 18:33:33"
"20181109T183427,71+01","mail\joldenbu.nsf","C125832B:005DADBF","nserver","CN=Johnny Oldenburger/O=ALM","SOFT","0001","54060598:74EB0F79C1258340:00606893","Form","4","Memo","Subject","16","Deletion Logging","DeliveredDate","19","09-11-2018 18:33:02"

Next I will setup the nshDelLog - Domino Deletion Log Annotation and Backup V 0.9.0 database by IBM Champion Daniel Nashed. For more information see the blog post nshDelLog - Domino Deletion Log Annotation and Backup V 0.9.0. In one of my next blog post, I will describe my experience of this database. Thanks for sharing Daniel!

Consequences Administration Server Action Field Settings in the Access Control List Dialog Box

$
0
0

In my journey as Domino Administrator I performed a deep dive into the AdminP process during the past period especially for renaming and deleting users. One of the most important coherent settings that I encountered here are the Administration Server settings in the Access Control List of the databases especially the value in the action field. These setting can be set or modified using the Domino Administrator Client. From the Domino Administrator open the domain containing the server with the database for which an administration server must be added or changed. Next select the Files tab and select the database to which an administration server has to be assigned. From the Tools pane select Tools - Database - Manage ACL and select Advanced. In the Action field the values can be selected as described in the table below.

FieldValue
Administration ServerChoose one of these:
None -- If you do not want an administration server assigned for the database.
Server -- Select a server from the list.
ActionChoose one of these according to whether you want modifications to the indicated fields to occur during a rename group, rename user, or rename server action; or during a delete server, delete group, or delete user action:

Do not modify Names fields
Names fields are not updated during any of the above rename and delete actions.

Modify all Readers and Authors fields
Reader and Author fields are updated during the rename and delete actions listed above. Any item of type Item_Readers or Item_ReadWriters is modified.

Modify all Names fields
All names fields are updated during any of the rename or delete actions listed above. Any item of type "Item_Names" is modified, for example, a list of users or groups would be modified. Item_Names includes Item_Readers and Item_ReadWriters making it a super-set of modifications that include Readers and Authors fields.


For more information see also the IBM Support documents Specifying an administration server for databases and Modifying the Action field in the Access Control List (ACL).

In a number of custom Notes applications, including the mail databases, the value in the Action Field is set to Modify All Names Fields in our Notes environment. Further in several custom Notes applications the user names are stored in Readers fields, Authors fields or Names fields.
When it comes to renaming a user in the Domino Administrator Client the value Modify all Names fields in the Action field in the Administration Server settings in the ACL in these databases means that the AdminP process will update the user's name in all Readers Fields, Authors fields and Names fields in accordance with a name change performed in the Domino Administration client. So far so good since this is what we want to accomplish with the setting in the Action field.
But here is the problem when it comes to deleting a user. When a user has been deleted in the Domino Administration client AdminP removes the user's name from all Readers fields, Authors fields and Names fields. In the Administration Request database there is an Delete in Readers/Authors Field entry. For specific custom Notes applications this means that important workflow information will be deleted. In mail files this means that anywhere the user's name appears the name will be removed. This includes also the information about who created a document and the information about who sent mail.


However, regarding the settings in the mail databases IBM recommends that for heavy users of Calendar and Scheduling specific to recurring meetings the Action field for the user's mail database should be set to Modify All Names fields. For users who are not frequently involved in the use of Calendar and Scheduling the Action field for the user's mail database should be set to Do not modify Names fields.
For more information see the IBM document Modifying the Action field in the ACL dialog box.
I specific tested the AdminP process for removing a user and for mail databases en workflow applications this is a major problem. Critical information is deleted when the Action field is set to Modify all Names Fields. We use the setting Modify all Names Fields in our mail databases because of the Calendar and Scheduling and recurring meetings.


The above situation yields a dilemma regarding which setting is best used in which database in the situation where use is made of the AdminP process when a user is renamed and when deleting a user.
In my humble opinion it can not be the intention to redesign existing Notes applications so that they can work the one-sides way that AdminP processes deletion requests. I would like to hear any solutions by Domino Administrators regarding the AdminP process for deleting users when in the ACL the value Modify all Names Fields is selected.
Below the recommendations for the names.nsf and admin4.nsf databases by IBM.

NAMES.NSF - Domino Directory
By default, the Action field for the administration server for the Domino Directory is set to "Do not modify names fields." Do not change the Action setting for the administration server for the Domino Directory. The purpose of this setting is to allow the Administration Process to update names (people, group, or server names) in critical areas of a database. The Administration Process automatically manages the names in the Domino Directory. Changing the Advanced ACL setting for this database causes the removal of names which are critical to other Domino features, for example, mail routing and calendaring and scheduling.

ADMIN4.NSF - Administration Requests database
The Administration Requests database (ADMIN4.NSF) is a log database from which documents are routinely purged. If you set the Action field on the ACL dialog box to anything other than "Do not modify names fields," you may cause performance problems when the Administration Process (adminp) processes requests. This does not apply to cross-domain administration requests.

In any case the above is certainly something to think about when selecting a value in the Action Field in the Administration Server settings in the Access Control List of a Notes database. I hope to receive some solutions from other Domino Administrators how this can best be solved without redesign existing Notes applications.

View Replication and Save Conflicts Including Differences Main Conflict Agent (1)

$
0
0

One of the daily tasks as Domino Administrator is solving the Replication and Save Conflict documents that arise almost daily in various databases. The first tool we use for managing the Replication and Save Conflict document is an Agent that is included in all Notes Databases and sends a mail to the Administrators group if in a database Replication and Save Conflicts have been created. In addition a View is included in all databases in which the Replication and Save Conflict documents are included. Finally we use an Agent and a Script Library which performs a comparison between the Replication and Save Conflict document and the Main Document in the database. In Below a description of the setup and how to easily implement it within existing Notes databases. In this blog post the Agent for monitoring the Replication and Save Conflicts in various databases and the View including the Replication and Save Conflict documents.

Agent MonitorConflicts
The Agent MonitorConflicts uses a View in which the Replication and Save Conflict documents are included. In the next blog post this View will be looked at and built up in a Notes database. Furthermore a Profile Form is used in the specific databases on which the registration is included to whom the final mail must be sent, the Domino Administrator group.

Option Public

Sub Initialize
Dim session As New NotesSession
Dim db As NotesDatabase
Dim view As NotesView
Dim pdoc As NotesDocument
Dim maildoc As NotesDocument

On Error Goto ErrorHandler

Set db = session.CurrentDatabase
Set view = db.GetView( "(MonitorConflicts)" )
Set pdoc = db.GetProfileDocument( "ProfileForm" )

If view.EntryCount <> 0 Then
Set maildoc = New NotesDocument( db )
maildoc.Form = "Memo"
maildoc.Principal = "Administrators"
maildoc.~$AltPrincipal = "Administrators"
maildoc.from = "Administrators"
maildoc.Subject = "Database "& db.Title & " has Replication and Conflict Documents"
maildoc.SendTo = pdoc.DominoAdministrators(0)
Set rtitem = New NotesRichTextItem( maildoc, "Body")
Call rtitem.AddNewline(1)
Call rtitem.AddNewline(1)
Call rtitem.AppendText("This database has Replication and Save Conflict documents: ")
Call rtitem.AppendDocLink( db, db.Title )
Call maildoc.send(False)
End If

Exit Sub

ErrorHandler:
'exit routine
Exit Sub
End Sub

The Runtime for the Agent MonitorConflicts is On Schedule - Daily on Target All new & modified documents.


B. View MonitorConflicts
As mentioned above the Agent MonitorConflicts uses the View MonitorConflicts in which the Replication and Save Conflict documents are included. The View includes some reasonable information about the Replication and Save Conflict documents and not just the text 'Replication or Save Conflict'. First create a new View with no response hierarchy. Replication and Save Conflict documents are response documents. Next use the following Selection formula for the view: SELECT @IsAvailable($Conflict). In the View additional field information is displayed. For displaying additional field information the relative columns must be set as categorized or they will not appear. Use the following syntax for the Column Formula : @If(@IsAvailable($Conflict); @Text(FIELDNAME) + " - " + FIELNAME2;""). For including the notation "[Replication or Save Conflict]" for each document (which makes it easier to select them) simply create a non-categorized column with the formula "". The View will look something like this in the end.


In the next blog post I will describe the Agents performing the comparison between the Replication and Save Conflict document and the Main Document in the database.

The Best Of The Best - Welcome to the Next Era of Rapid Application Development and Easy Administration

$
0
0

The last period I have looked at the new functionalities in Domino 10 and I am very impressed with what has been realized in IBM Domino 10 and IBM Notes 10. In addition I am currently participating in the Beta program IBM Domino Mobile Applications (IDMA). IDMA is the Notes client that we already know for working with our Notes applications but on and optimized for the iPad. This is also an incredibly great new product. For those who have missed out on all new exiting developments so far below a replay of the Domino 10 demo as presented during the Domino 10 World Premiere.



For more information about the new Administrator features in Domino 10 see my previous blog post series regarding IBM Domino 10.

Domino 10 - New Administrator Feature to Push to Notes Clients: Set Limits for Sending Mail
Domino 10 - Managing Scheduled Mail in MAIL.BOX
Domino 10 - New Administration Feature: Document Deletion Logging
Domino 10 - New Administrator Feature: Dynamic Indexing of High-Usage Views
Domino 10 - New Administrator Feature - Automatic Dead Mail Processing
Domino 10 - Upgrade ODS Notes Client Local Databases
Domino 10 - ID Vault Scanning
Domino 10 - Automatic Archiving of User ID Vault Documents to Restart ID File Synchronization
Domino 10 - Programatically Schedule Mail Using LotusScript
Domino 10 - Synchronize Database Replicas - New Option Replicate Command
Domino 10 - New Administration Feature: Document Deletion Logging (2)

Notes 10 - Default Enabled Notes Client Preferences
Notes 10 - Forward Multiple Messages as EML Attachments

The future of IBM Domino and IBM Notes is great. Very happy to be part of this new IBM Domino and IBM Notes path. So stay tuned! More to come in the next few weeks.

Managing and Resolving Replication and Save Conflicts (2) - scanEZ Conflict Solver

$
0
0

For my daily Domino Administrator tasks I have the privileged position to use the Ytria EZ Suite complete. This also applies to resolving the Replication or Save Conflicts that arise in the various Notes database. In this blog post and short description how Replication or Save Conflicts can be solved by using the Conflict Solver in Ytria scanEZ. Ytria scanEZ is a powerful Notes database viewing and editing tool that allows developers and administrators to change database content visually through an intuitive user-interface. Domino Administrators can find and solve specific issues or even make mass modifications all without the need to create agents and views for database changes. Ytria scanEZ is a very powerful tool that saves developers and administrators time while helping them avoid errors.

To resolve Replication or Save conflicts in a Notes database the Domino Administrator can initially open the specific database in scanEZ. By selecting the Conflict Solver Domino Administrators can solve the conflict in the Notes database in a very simple way.


The Conflict Solver allows the Domino Administrator to see all the conflicts in a database. These are all the documents with $Conflict fields and their parent documents. By comparing the values of each document in the table Domino Administrators can then select which field values they want to keep and which field values Administrators want to discard or delete.

With scanEZ valuable information from Replication or Save Conflict documents can be stored in the Main document before the Replication or Save Conflict document is deleted. There is no longer need to manually copy the data from the Replication or Save Conflict document and paste this information into the Main document. With scanEZ Replication or Save Conflicts can be solved quickly and reliably. For more information see the video below and the documentation Getting Started with scanEZ and scanEZ Conflict Solver.



In my next blog post the second part of our own solution for managing and solving Replication or Save Conflict documents in Notes databases.

Essential How-Tos for IBM Domino Mobile Apps (IDMA)

$
0
0

On November 29 a very interesting webinar will take place, Essential How-Tos for IBM Domino Mobile Apps (IDMA).

Abstract
Don't miss the November 29 webcast and learn how to create mobile solutions from your Domino applications. Get the inside scoop on how easy it is to extend the value of your proven applications to your "road warriors" and executives. In the time it takes to watch the webcast, you could have your first application up and running on an iPad. Speaker are Luis Guirigay, Worldwide Executive IT Specialist IBM Collaboration Solutions and Andrew Manby, Director of Product Management IBM Collaboration Solutions.
Registration is open. You can register here for the webinar Essential How-Tos for IBM Domino Mobile Apps (IDMA).

Overview
Title: Essential How-Tos for IBM Domino Mobile Apps
Date: Thursday, November 29, 2018
Time: 10:00 AM Eastern Standard Time
Duration: 1 hour


Domino 9.0.1 Feature Pack 10 Interim Fix 5 Available for Download on Fix Central

$
0
0
IBM released IBM Domino Feature Pack 10 Interim Fix 5 on IBM Fix Central. We are of course all mainly waiting for the 10.0.1 release of Notes and Domino. Hopefully this release will be made available soon. In the meantime below the Fix List and the download link for IBM Domino 9.0.1 Feature Pack 10 Interim Fix 5.

Fix List IBM Domino 9.0.1 Feature Pack 10 Interim Fix 5

Fix introduced in releaseSPRDescription
Interim Fix 5

for Domino 9.0.1 Feature Pack 10
MSKAB56HC9Fix frequent crashes in GsKit on 9.01FP10. Windows only.
WSPRAWTJ5NFix an issue with multiple replicas processing the same connection doc at the same time
ROBEAXPFDPFix an issue with Pull Replication Failing When Run At The Same Time As A Pull/Push
OSAMAXAGGJFix a server crash when rmflush access the .ndx file while compact was finishing up
PMGYAKWECAFix crashes affected by the use of NIF/NSF in databases
OSAMAVSQQLFix a long held lock when compact is running

Download: IBM Domino 9.0.1 Feature Pack 10 Interim Fix 5

More info: Interim Fixes & JVM patches for 9.0.1.x versions of IBM Notes/Domino & add-ons.
This technote contains download links and fix lists for Interim Fixes for 9.0.1.x versions of Notes, Domino, and iNotes. Also included are Interim Fixes for ICAA and Verse On-Premises. Interim Fixes are cumulative and contain all of the fixes from previous versions.

Big Changes that Determine the Future of the IBM Collaboration Solutions

$
0
0

IBM and HCL Technologies (HCL) announced a definitive agreement under which HCL will acquire select IBM software products for $1.8 billion. The transaction is expected to close by mid-2019, subject to completion of applicable regulatory reviews. The software products in scope represent a total addressable market of more than $50 billion and include:
  • Appscan for secure application development,
  • BigFix for secure device management,
  • Unica (on-premise) for marketing automation,
  • Commerce (on-premise) for omni-channel eCommerce,
  • Portal (on-premise) for digital experience,
  • Notes & Domino for email and low-code rapid application development, and
  • Connections for workstream collaboration.
HCL and IBM have an ongoing IP Partnership for five of these products. Big question is how this will affect the future of the IBM Collaboration Solutions. More detailed information will be available for this in the coming period. The first roadmaps for Notes, Domino,  XPages, Connections and Sametime will be essential for the future of the current IBM Collaboration Solutions under the responsibility and guidance of HCL. So let's wait and see what the future will bring and in the meantime focus primarily on the upcoming Notes Domino 10.0.1 release.

A New World of Possibilities with IBM Domino V10 - Node.js - Domino Query Language and NodeRed

$
0
0

On December 17 a very interesting webinar will take place, A New World of Possibilities with IBM Domino V10, Node.js, Domino Query Language, and NodeRed.

Abstract
You told us that you want to reuse your existing Domino data, proven applications and skills to solve new business problems using JavaScript and we delivered this to you in Domino V10. In this session you will learn how to get started with Node.js and the Domino Query Langauge (DQL) and enter the next era in Domino app development. The webinar is led by experienced developers who will show you, step-by-step how to get started and what's possible. Join us to learn how to give your applications and skills a new lease on life.
Speakers are Darren Cacy, Collaboration Technical Specialist IBM Collaboration Solutions, Stefano Pogliani, Technical Sales IBM Collaboration Solutions and Andrew Manby, Director of Product Management IBM Collaboration Solutions

Registration is open. You can register here for the webinar A New World of Possibilities with IBM Domino V10, Node.js, Domino Query Language, and NodeRed.

Overview
Title: A New World of Possibilities with IBM Domino V10, Node.js, Domino Query Language, and NodeRed
Date: Monday, December 17, 2018
Time: 10:00 AM Eastern Standard Time
Duration: 1 hour

HCL Domino Advocacy Program - FAQ and Signup

$
0
0
HCL launched a new Collaboration website and a Client Advocacy Program for Domino. You can find the new website here.


HCL Client Advocacy FAQS - DOMINO
What is HCL Client Advocacy? A customer centric approach is the foundational element of the HCL Products business philosophy and a key component of the HCL Products and Platforms strategy to drive overall success of the product portfolios. The Client Advocacy program strives to deliver an interactive approach to customer relationships that compliments existing processes and provides the greatest value and service through strong connections to our product area experts. For more information visit the Client Advocacy Domino FAQ page. You can signup for the Client Advocacy here.

Domino 10.0.1 - Domino 11

$
0
0
As you may already know next week Notes Domino 10.0.1 will be released by IBM / HCL. The release is planned for Tuesday December 18. So stay tuned and get the fixes we are all waiting for. Also the new Domino Community and Notes Community 10.0.1 Server will be released. So it will be an exiting week just before the holidays.

You also get the opportunity to help and work on the future of Notes Domino 11. The Domino V11 jams are coming again to a city near you. Help HCL plan the next release of Domino during these in-person workshops and virtual events.
2018 was a game-changing year and a milestone in the Domino story. And it all started with the V10 jams. You can contact your local representative listed on the IBM Collaboration Solutions Blog website to join HCL for another exciting round of face-to-face workshops and virtual events and help to build a better Domino for the future. 

IBM Notes 9.0.1 Feature Pack 10 Interim Fix 6 Available for Download on IBM Fix Central

$
0
0

IBM just released IBM Notes 9.0.1 Feature Pack 10 Interim Fix 6 Available for Download on IBM Fix Central.


Fix List IBM Notes 9.0.1 Feature Pack 10 Interim Fix 6.

Fix introduced in releaseSPRDescriptionAdditional Information
Notes 9.0.1 Feature Pack 10 Interim Fix 6


Help > About shows 9.0.1FP10 SHF315
PCMAB4BMCEFixed an issue where File->Close All is not behaving as expectedStandard Client Only
RGAUAHBF9UFixed an issue in Xpages (Djtabcontainer Extlib Control - Toolbar In Rich Text Control) where is not consistent with different tabsStandard Client Only
LHEY9FNJQPFixed an issue in XPages where the XPinC resources are not being loaded correctlyStandard Client Only
JOHNAXJGW9Fixed an issue with the Client startup in Windows 7
JACQAVQV8NFixed an issue where the replication and sync icon change after the first shutdown of the Notes Client
EPORB3HQ6KFixed a Security Issue.

Please see this TN: Security Bulletin: Privilege Escalation in Notes System Diagnostic Service of both IBM Notes and Domino (CVE-2018-1171)

Download Link IBM Fix Central: IBM Notes 9.0.1 Feature Pack 10 Interim Fix 6

This technote contains download links and fix lists for Interim Fixes for 9.0.1.x versions of Notes, Domino, and iNotes. Also included are Interim Fixes for ICAA and Verse On-Premises. Interim Fixes are cumulative and contain all of the fixes from previous versions.

How to Download IBM Notes 10.0.1 - IBM Domino 10.0.1 from Passport Advantage

$
0
0

Today IBM / HCL released IBM Notes 10.0.1 and IBM Domino 10.0.1. Below the IBM Documents on how to download IBM Notes 10.0.1 and IBM Domino 10.0.1 from Passport Advantage including the Part Numbers.

How to download IBM Domino 10.0.1 from Passport Advantage

Part NoDescription
CNXL7ENIBM Domino 10.0.1 64 bit for Windows English
CNXL8ENIBM Domino 10.0.1 64 bit for AIX English
CNXL9ENIBM Domino 10.0.1 64 bit for Linux English
CNXK0ENIBM Domino Community Server for Non-Production 10.0.1 Windows English
CNXK1ENIBM Domino Community Server for Non-Production 10.0.1 Linux English

How to download IBM Notes 10.0.1 from Passport Advantage

Part NoDescription
CNXK5ENIBM Notes 10.0.1 Basic Configuration for Windows English
CNXK6ENIBM Notes 10.0.1 for Windows English
CNXK7ENIBM Notes 10.0.1 Mac 64 bit English
CNXL1ENIBM Notes, Domino Designer and Admin 10.0.1 for Windows English
CNY0UENIBM Notes Community Client for Non-Production 10.0.1 Windows English
CNXL0ENIBM Client Application Access 2.0.1 Windows English
CNY0HENIBM Client Application Access 2.0.1 Mac English

IBM 10.0.1 is a full release and includes:
IBM Domino 10.0.1
IBM Domino Designer 10.0.1
IBM Notes 10.0.1
IBM Traveler 10.0.1
IBM XWork Server 10.0.1
IBM Mail Add-in 2.0.2.8 (IMSMO Client)
IBM Client Application Access 2.0.1
IBM Domino AppDev Pack 1.0
IBM Verse On-Premises V1.0.6
IBM Domino Community Server Non-Production
IBM Notes Community Client Non-Production

For more information: IBM Domino 10.0.1 delivers new features to accelerate modern application development and deployment

How to get the most out of the new Domino 10 Administration Features

$
0
0

A short blog post at the end of the year. First of all, I want to thank everyone in the Notes Domino community for a great year. The year in which Notes Domino has been revived again and in which Notes Domino has a great future again. The next two weeks I will enjoy the holiday season. I wish everyone a great time.

Nonetheless, there is already a first event on my agenda for 2019. On 16 January 2019 a very interesting webinar will be organized by Ytria, How to get the most out of the new Domino 10 administration features using the Ytria tools. In my daily work as Domino Administrator (and Developer) I have the privilege to use the Ytria EZSuite. The description of the webinar is very promising: Domino 10 shipped jam packed with awesome new features you'll love. And in this webinar, you'll learn how to bring the best out of them with the Ytria tools. We'll talk about deletion logging, replication and synch-up, Domino On Disk Structures (ODS) and what they mean. You'll also learn how you can enable and enhance these features using our upcoming EZ Suite tools version 19.
Registration for the webinar is already open.


Finally I hope that the IBM Champions 2019 will be announced before Christmas. That would be a nice ending to a great IBM Notes and IBM Domino year.

IBM Champion for IBM Collaboration Solutions (ICS) 2019

$
0
0

Today IBM announced the IBM 2019 Champions for IBM Collaboration Solutions (ICS). There is no official announcement and overview from IBM yet but the overview of the IBM Champions 2019 will eventually be published here.
I want to congratulate all IBM Champions heartily. I would also like to thank everyone who nominated me for IBM Champion 2019. Thank you very much!
This year I am selected for the fourth consecutive year as IBM Champion for IBM Collaboration Solutions. Thank you IBM! I am humbled and grateful to be belong again to this very special group of IBM Champions.

The IBM Champion program recognizes innovative thought leaders in the technical community -- and rewards these contributors by amplifying their voice and increasing their sphere of influence. An IBM Champion is an IT professional, business leader, developer, or educator who influences and mentors others to help them make best use of IBM software, solutions, and services.
IBM Champions are eligible to accept IBM Champion badges for use in social and networking sites as part of their IBM Champion benefits. The IBM Champion badge is an IBM-issued open badge acknowledging the IBM Champion achievement. The badge can be shared on social and networking sites and indicates that the holder is a proven innovative thought leader in the technical community who has demonstrated exceptional expertise and contribution in helping others derive greater value from IBM software, solutions and services.
The badge recognizes the IBM Champion's skills not only in the Champion's area of technical expertise, but also as one who influences and mentors others through blogging, speaking at conferences, moderating forums, leading user groups, and authoring books or articles. The badge is earned as part of the selection as an IBM Champion.


For more information about the IBM Champion Program and badges see the IBM developerWork website IBM Championsand the IBM Community website IBM Champion Program News and Views.

Quick Tip: Prevent Access Through Web Browser Using Don't Allow URL Open

$
0
0
A test post for testing my new blog layout. In my daily work as an Domino Administrator I needed a possibility to prevent certain Notes client users from accessing their mail databases through a Web browser. In basic there are three possibilities to prevent certain users from accessing their mail database via a web browser. Below a short description.

Internet Password
As a first option Administrators can change the Internet password in the user's Person document. If the internet password change does not take affect immediately administrators can execute a load updall -R names.nsf from the Domino server console. In many cases, as in our case, the internet password is also be used for other Notes XPages application as a result of which this option will not be applied much in daily practice.

Maximum Internet Name and Password
A second option for Administrators is to set the Maximum Internet Name and Password setting in the Database Access Control List - Advanced section to No Access.
In our case we are using Notes Traveler (iPhone's). If the Maximum Internet Name and Password is set to No Acces or the following error message is generated in relation to Notes Traveler or the synchronization on the iPhone's is no longer working.

28-11-2018 16:11:42   Traveler: WARNING NAME. An exception occurred when opening database CN=servername!!mail/username.nsf using user shortname CN=username in order to retrieve changed documents. Exception information: Throw: TASK_PROFILE_OPEN_DB
*** Content Adapter Exception ***
ERROR 23 (ERR_DATABASE_ERROR)
--- Debug Info ------------:
Database cannot be opened with status of 0x4ac.  Server=servername database=m

Remark: Setting the Maximum Internet Name and Password in the Database Access Control List - Advanced section to No Access will not prevent access to public documents such as the Calendar.

Don't Allow URL Open
Another option for Administrators is to enable the Don't Allow URL Open setting in Database Properties - Basics tab. Given the above two options which we could not use in our situation, we used the Don't Allow URL Open database property for certain Notes users. This works without any problems.
When this database property is set the following error is displayed when a user tries to open the database in a web browser:
"Error 500
HTTP Web Server Lotus Notes Exception - You are not authorized to access that database".

Only users with a minimum of Designer Access to their mail database will have the ability to modify this setting.
For more information see the IBM Technote How to prevent Notes users from accessing their mail databases through a Web browser.

Quick Tip: Can Not Delete A Repeated Appointment If Parent Document is Missing

$
0
0
Another blog post to test my new blog layout :) Today I ran again into an age-old Notes problem concerning the deletion of a repeated calendar entries. When deleting repeated calendar entries it still occurs that the parent document can not be opened or no longer exists if the entries are deleted from the Calendar View. The error messages below are displayed. A suggested repair, as shown in the second message, does not solve the problem. It is remarkable that these types of problems still occur in the current Notes releases. In this case the error occurred in release Notes 9.0.1 Feature Pack 9 Interim Fix 1.
In these situations the only option to delete the repeated calendar entries is to execute the deletion from the All Documents view in the mail database. When creating repeated calendar entries, a document is created in the All Documents view in which all dates are displayed. Below a short description.

First I created a repeated calendar entry for 5 days.
In the All Documents view in the mail database a document with all repeated dates has been created. By deleting the document in the All Documents View, all repeated calendar entries in the Calendar View are deleted. In the Dialog select the option Delete Forever.
So in this case the problem was solved by deleting the corresponding document in the All Documents View in the mail database. Unfortunately in this case there is no choice on which instance is deleted. All the appointments contained in the document will be deleted. For me personally a point of attention for V11 to solve these kind of problems once and for all.

View Replication and Save Conflicts Including Differences Main Conflict Agent (3)

$
0
0
In my previous blog post View Replication and Save Conflicts Including Differences Main Conflict Agent (1) we started with the design for monitoring and managing the Replication and Save Conflict documents in Notes databases. Initially, the Agent for sending an email to the Administrator Group when Replication and Save Conflict documents are created in specific Notes databases and the View including the Replication and Save Conflict documents are created in the Notes Databases. Before the comparison between the Replication or Save Conflict document and the Main document can be made a number of additions are needed in the databases. Below a short description
A. Action Button
At first create a new Action Button 'Comparison Main Conflict' in the View MonitorConflicts. In the OnClick Event enter the @Formula: @Command([ToolsRunMacro]; "CheckMain")
B. Agent and Script Library
Next create a new Agent in the specific Notes Databases 'CheckMain'. This Agent uses the Script Library ReplicationSaveConflict which can be found on GitHubGist. Copy the code from GitHubGist to a new Script Library ReplicationSaveConflict in the Notes database.
Copy the script below to the Agent Check Main.

Options
Option Public
Use "ReplicationSaveConflict"

Initialize
Sub Initialize
Set session = New notessession
Set db = session.currentdatabase
Set coll = db.unprocesseddocuments

If coll.count<>1 Then
Msgbox "Please select just one Replication or Save Conflict Document."  ,  16 , "Select Replication or Save Conflict Document."
Else
Set loser =coll.getfirstdocument
If Not(loser.hasItem("$conflict")) Then
Msgbox "The selected document is no Replication or Save Conflict Document."  ,  16  , "Select Replication or Save Conflict Document."
Exit Sub
End If
tmp = loser.GetItemValue( "$Ref")
Set winner = db.GetDocumentByUNID(tmp(0))

'Check if winner/main exist
If winner.size = 0 Then
Msgbox "Error, no main document found."  ,  16  , "Error, no main document found."
Exit Sub
End If

'Check all fields - winner and sort into alphabetical order
fill_item_arrays winner,winneritems
sort_items winneritems

'Check all fields - loser and sort into alphabetical order
fill_item_arrays loser,loseritems
sort_items loseritems

'Combined both field lists into one and then check if equivalent
combine winneritems,loseritems,combineditems
For x = 0 To Ubound(combineditems)
processitem combineditems(x)
Next x

'Create document and report back to user
Set doc = db.createdocument()
filldocumentproperties winner,loser
writereport combineditems
End If
End Sub

The Runtime for the Agent is On Event - Action menu selection with Target All selected documents.
C. Result
By selecting a Replication or Save Conflict document in the View MonitorConflicts and next selecting the Action Button Difference Main Conflict the final result is a comparison Dialog Box as shown below between the differences in the Main Document and the Conflict Document. Based on the comparison the Conflict Document can be deleted or the values from the conflict document can be overwritten into the Main Document. Also a comparison of the Document Properties can be viewed in the Tab Document Properties.
In my next blog another approach to manage Replication or Save Conflict Documents in Notes databases.
Viewing all 628 articles
Browse latest View live