Webcast Q&A: Best Practices for Deploying Verse On-Premises

In the recent webcast “Best Practices for Deploying Verse On-Premises,” we showed how you can give your users the power of Verse without the migration effort. You can watch the replay here and quickly get up to speed with helpful tips from our Verse and Notes technical experts.

As promised, we have answered the questions that we were not able to cover in the session:


Q: In which version will Verse On-Premises be on the same level as iNotes when it comes to Contacts & To Do’s

A: We’re aware there are a few remaining functions in iNotes that aren’t yet in Verse On-Premises (VOP). “Contacts” are in scope for 2019 along with other enhancements. To Do’s are not currently in our backlog.

Beyond a modernized UI, VOP already includes a number of functions that are not available in iNotes. Over the next couple of quarters we will ensure that all features of iNotes are available in VOP. Click here for information on the last release, VOP 1.0.7.


Q: Do i need to install the Connections part for drag and drop files? If yes, when will that be integrated in the standard installation?

A: Yes, you do. Regarding a simplified install, it’s in the backlog. No date yet on its availability.


Q: Can you please provide a comparison of iNotes and VOP?

A: iNotes V11 will be the last release, as we are moving iNotes clients to Verse On-Premises. Traveler is fully supported and moving forward with the Verse Mobile clients on iOS and Android. We’re happy to provide a comparison of iNotes and Verse On-Premises functionality in the future.


Q: What about mail history in VOP? In iNotes I have access to complete mail history and I wonder if that will be included in future releases of VOP?

A: Verse does not limit the number of messages that can be loaded into the message list.  If you try to load a lot of messages, the performance of the client will slow.  Faceted search can be used to find old messages.


Q: Can VOP and iNotes co-exist on the same server?

A: Yes they can.


Q: Does VOP go on its own box?

A: No. Unless you want a more granular deployment, VOP can be installed on top of your prod mail servers.


Q: We have only Domino/Notes. What would Verse On-Premises add to our environment?

A: VOP is a new web interface for Mail and Calendar that is lighter, easier to customize and extend using existing web technologies and its design was heavily influenced by IBM Design Thinking.

iNotes will no longer be supported after Domino 11.0 and Verse will be the primary web interface for mail and calendar on a browser. However, the traditional Notes client will of course be also supported.

Please refer to the V11 webcast for our intention to combine the Verse and mobile apps experience into a new Windows and Mac desktop client.


Q: What is better to deploy first: Connections Files & Profiles or VOP? Can VOP work without Connections?

A: VOP can work without Connections but you won’t be able to see Files inside the VOP UI. For Profile Pics, there are ways where you can customize VOP to pull the pics from another service.


Q: Why do iwaredir.ntf and vopdesign.nsf have to be copied at each new version of VOP even if the files haven’t changed?

A: Both of these files can be ignored if doing an upgrade. Only the initial setup of VOP should make use of these files. See this documentation for more information.


Q: Will it be possible to use external services in Verse On-Premises?

A: Yes, the extensibility capabilities of VOP make accessing any REST API very straight-forward.

The links to the documentation are here:

Verse Developer site: documentation on all of the extensions along with detailed samples and deployment details.

New IBM Verse Developer organization – hosts the files for the sample implementations:

Provide feedback.


Q: If I have two mail servers clustered, should I (or can I) install VOP on both servers?

A: That depends on whether you have a web load balancer for those servers. If you do and users could hit either server, then I would advise that you do. If it’s not clustered at the web level, then it’s not needed.


Q: Do you think it will be possible to add a link to the archive file (on server) of the user in the future?

A:  This functionality is in the roadmap for a future release.


Q: We have no web load balancer, but users have two links for iNotes login: https://server1 and https://server2. If one server is not responding, they try to reach other. Is this case suitable for VOP too?

A: Sure, that would work for VOP too. You would need to install the code on both servers.


Q: Can we review a one URL approach for all mail servers in a Domain?

A: If this question refers to web mail redirects, we suggest you explore the functionality iNotes Redirect. You can read more about how to set up iNotes Redirect here. We have updated this for VOP as well.


Q: Doesn’t FTI all your mail files add a huge burden on the server?

A: It’s true that Full Text Indexing all your mail files adds more load to your server, both disk space and the indexer task will be utilized more. However, we believe that the benefits of the VOP search functions outweigh this increased utilization.


Q: Would you be able to explain the architecture a bit more? For example, we have three different home mail servers — where would you put VOP? If you put it on its own server, does it sort of act like a proxy? Meaning, there would not be any ‘mail data’ on the VOP server?

A:  VOP is designed to be installed on your existing mail servers. If you install it on a separate mail server, then it would need the mail files to be replicated to that server to be able to serve them via VOP. We would recommend the mail files be added to the cluster replicator so that they stay as up to date as possible.


Q: Is there a method to provide a link to open other user mail files?

A: We already support delegated mail file (e.g. admin who can open an executive’s mail).


Q: Is there a VOP cheat sheet for users?

A: Take a look at our extensive user documentation. Then, if you add customizations of your own, you can add your customizations to the cheat sheet.


Q: Can we review the use of IDVault (already implemented) and the ability to no longer have the Notes ID on the user’s desktop?

A: Absolutely. VOP doesn’t require the id file store in the personal computer.


Q: Is there a method to provide a link to the users archive mail file?

A:  This is in the roadmap for a future release.


Q: Is it true that I can connect both VOP’s to one Connection server?

A: Yes, it is possible to point multiple VOP servers to a single Connections environment.


Q: When will Verse in the Cloud catch up with the functionality of VOP?

A: Good question. For background, we published a roadmap for SCN/Verse on Cloud on the March 14 webinar and there will be a separate communication about the roadmap going out very soon. By the end of 2019, we intend to have delivered the majority of the user experience improvements in VOP to the Cloud. In the 2H-2019, you will start to see the latest innovations from VOP 1.0.7 starting to appear on Verse on Cloud. Thereafter, we will be synchronizing Verse functionality across both platforms within weeks of a new release.


Q: When will the contacts interface be changed from the iNotes interface to a Verse interface?

A: This work is in our roadmap. We are in the early stages of development.


Q: Are there any screens or views of VOP on a mobile device, such as a mobile phone?

A: There is a preview of Verse Web for a mobile browser available in the VOP 1.0.7 release. This is intended to replace the Notes Ultralight solution. The intention is to make this new experience available in VOP 1.0.8. This offering is complementary to the existing Verse Mobile for iOS and Android applications.

Disclaimer: IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.