This document discusses preparing a Domino application landscape for migration to HCL Nomad Web. It recommends first consolidating the landscape by identifying unused databases that can be archived. Key questions to answer include which databases have few active users, incompatible code like hardcoded dependencies, and standard templates that are easier to migrate. Tools like iDNA and MarvelClient can help by analyzing application usage, detecting duplicate code, and finding code that is not supported in Nomad Web to speed up the migration process. The goal is to understand what applications can be modernized with Nomad Web versus left behind or re-written.

1. Make Your Data Work For You
#3 Dominoapplikationen im Wandel der Zeit
Alles neu mit HCL Nomad Web
8. Juni 2022

2. Katrin Pascher
Marketing Operations
& Content Manager
panagenda
Christoph Adler
Senior Consultant
panagenda
Join the conversation using #NomadWeb #MarvelClient & @panagenda
Speakers
Franz Walder
Product Manager
panagenda

3. Agenda
1. About our webinar series “The Path to HCL Nomad Web”
2. Consolidation as the foundation for transformation
3. Key questions and how to answer them
4. Design, source code and HCL Nomad Web

4. Make Your Data Work For You
1. About our webinar series
“The Path to HCL Nomad Web”

5. The Path to HCL Nomad Web
✓ ✓ ✓

6. The Path to HCL Nomad Web
!=
Nomad (mobile) Nomad Web
Official name
“HCL Nomad for web browser”

7. The Path to HCL Nomad Web
+ + +

8. The Path to HCL Nomad Web (cont.)

9. The Path to HCL Nomad Web (cont.)

10. The Path to HCL Nomad Web (cont.)

11. The Path to HCL Nomad Web (cont.)
License requirements
To use HCL Nomad for web browsers, you agree to obtain and
maintain an active subscription and Support for HCL Domino
Complete Collaboration (CCB). Please note, only CCB customers are
entitled to use HCL Nomad for web browsers.

12. Make Your Data Work For You
2. Consolidation as the foundation
for transformation

13. Consolidation as the foundation
Consolidation?
Not Nomad?!!

14. Whatever your challenge …
• Modernization
• Migration
– to the Cloud
– to a new use experience
… in the beginning you need answers to the same questions.

15. The Meta-Questions
• Which databases are unused and can be archived?
• For which applications do I have easy paths forward?
• What can be turned off asap? (license cost impact)

16. The Meta-Questions
• Which databases are unused and can be archived?
• For which applications do I have easy paths forward?
• What can be turned off asap? (license cost impact)

17. The Meta-Questions
• Which databases are unused and can be archived?
• For which applications do I have easy paths forward?
• What can be turned off asap? (license cost impact)

18. The ongoing process
Measure
Plan
Execute
Track

19. Make Your Data Work For You
3. Key questions and how to answer them

20. Application KPIs
• Which/How many DBs can be excluded from my project?

21. Application KPIs
• Which DBs are unused and can be decommissioned?

22. How iDNA can help
1%-5%
Original
Project
Scope

23. Application KPIs
• How many users are active per database?

24. Identify stakeholders

25. Identify stakeholders

26. Identify stakeholders
Consumers
Content Creators

27. User KPIs
• When were the users last active?

28. User KPIs
• How many applications do my users really work with?

29. User KPIs
• What happens to these numbers after a few iterations?
• Continuous monitoring is essential!

30. Application KPIs
• How many DBs have blockers in content?
Content
Age
Attachment
Types & Size
Rich-Text
Objects
Used
Design
Elements
Security &
Access
Restrictions

31. Make Your Data Work For You
4. Design, source code
and HCL Nomad Web

32. Design, Code and Nomad Web
How many DBs are based on standard templates?

33. Design, Code and Nomad Web
How many DBs have blockers in source code?
• Hard-coded names
IP addresses, server names, usernames, …
• External interfaces
File system, libraries/DLLs, interfaces to SAP, Fax, …
• Dependencies on other DBs

34. Design, Code and Nomad Web
Extensive list from HCL:
https://help.hcltechsw.com/nomad/1.0_web/nomad_web_limitations.html
• Unsupported: XPages / foreground JavaAgents
• Limitations: LotusScript / Formula
OLE, NotesHTTPRequest, LSXLC, LSXODBC, …

35. How iDNA can help
• Source code full-text search
– all Domino applications in a central location
– using regular expressions for maximum flexibility
– 60+ pre-defined patterns
36

36. Code Similarity Clusters
Source Code Duplication Detection
How iDNA can help

37. To sum it up!
• Find out what’s unused and what’s worth bringing along
• Detect applications with incompatible code
• Isolate affected code blocks and speed up remediation
• Get your application landscape ready for Nomad Web!

38. To sum it up!
• Find out what’s unused and what’s worth bringing along
• Detect applications with incompatible code
• Isolate affected code blocks and speed up remediation
• Get your application landscape ready for Nomad Web!

39. To sum it up!
• Find out what’s unused and what’s worth bringing along
• Detect applications with incompatible code
• Isolate affected code blocks and speed up remediation
• Get your application landscape ready for Nomad Web!

40. To sum it up!
• Find out what’s unused and what’s worth bringing along
• Detect applications with incompatible code
• Isolate affected code blocks and speed up remediation
• Get your application landscape ready for Nomad Web!

41. MarvelClient iDNA
Relational
Analytics
Inventory
Clean-up

42. What’s next?
• Try for yourself in our sandbox:
https://www.panagenda.com/contact/contact-sandbox-idna
• Get a trial installation in your own environment: sales@panagenda.com
• Follow our blog: https://www.panagenda.com/blog/idna
• Join the conversation on Twitter: #iDNAApplications & @panagenda

43. Webinar Survey – please give us your feedback!
https://tinyurl.com/20220608

44. Katrin Pascher
Marketing Operations
& Content Manager
panagenda
Christoph Adler
Senior Consultant
panagenda
Join the conversation using #NomadWeb #MarvelClient & @panagenda
Q & A
Franz Walder
Product Manager
panagenda