Way #5 Don’t end up in a ditch because you weren’t aware of roadblocks in your source code
0 likes85 views
The document discusses mastering application migration challenges for Domino applications by emphasizing the importance of understanding code complexity and roadblocks. It outlines three common use cases for migrating applications, including cloud migration, mail migration, and compatibility with Nomad, highlighting potential issues such as hard-coded references and external dependencies. Additionally, it suggests tools and methods for analyzing code, like DXL, Regex, and third-party solutions, to facilitate a smoother migration process.
![Just because you don’t have enough headaches already
25
And here is what that regular expression could look like:
(?iw)
@db(column|lookup)s*?
((s*??"notes?"|s*??"?")[^;]*;
(?!(?!s*??".+??"|s*?S+s*?:s*??".+??")|
s*??"?"(s*?:s*??"?")?s*?;|s*?@dbnames*?;|
s*?@subsets*?(s*?@dbnames*?;s*?1s*?)s*?:
s*?@subsets*?(s*?@dbnames*?;s*?-1s*?))
[^;]*;[^;]*;[^)]*)](https://image.slidesharecdn.com/20200312enifa5dontendupinaditchbecauseyouwerentawareofroadblocksinyoursourcecode-200312104937/85/Way-5-Don-t-end-up-in-a-ditch-because-you-weren-t-aware-of-roadblocks-in-your-source-code-25-320.jpg)
Way #5 Don’t end up in a ditch because you weren’t aware of roadblocks in your source code
- 1. Make Your Data Work For You Don’t end up in a ditch because you weren’t aware of roadblocks in your source code Way #5 of 7 new ways to master your Domino application migration challenges Franz Walder, March 11, 2020
- 2. Speakers Daniel Klas Inbound Marketing Coordinator @panagenda Join the conversation using #iDNAApplications & @panagenda Franz Walder Product Manager franz.walder@panagenda.com
- 3. I. Why you should care II. The technical foundation III. Three common use cases Agenda
- 4. I. Why you should care II. The technical foundation III. Three common use cases Agenda
- 5. I. Why you should care II. The technical foundation III. Three common use cases Agenda
- 6. Make Your Data Work For You Why you should care
- 7. Why you should care
- 8. Why you should care clean up → low-hanging → analyze complexity / unused DBs fruit re-develop apps / change platforms
- 9. Why you should care clean up → low-hanging → analyze complexity / unused DBs fruit re-develop apps / change platforms
- 10. Why you should care clean up → low-hanging → source code unused DBs fruit matters
- 11. Why you should care clean up → low-hanging → analyze complexity unused DBs fruit re-develop apps change platforms ...
- 12. Questions we hear a lot • What is complex and what is not? – How complex is my special database? – How does the complexity of applications compare? • What are roadblocks for my target scenario? – Are there hard-coded references in my code? – Are there design or code elements that may cause issues? • What will it cost to migrate or modernize an application? – Are there standard transformation paths? – What kind of developer resources will I need?
- 13. Shout-out to … … Code Similarity! – Only 5-10% of your source code might be unique! – Webinar #2 of this series
- 14. Why you should care What Code Similarity can do for you: • Drastically reduce effort of (re-)development • Change profile of development resources you need • Uncover lost template inheritance – Open standard transformation paths
- 15. Make Your Data Work For You The technical foundation
- 16. Technical foundation Two ugly truths: • Two DBs with the Same Design Template will not necessarily have the same design • Two databases with the Same Replica ID will not necessarily have the same design → You want to make a very conscious decision on what you analyze
- 17. Technical foundation How do you analyze your code? • Domino Designer is a place to start • Lacks flexibility • Lacks enterprise capabilities
- 18. DXL: Domino XML Language 18
- 19. Why DXL? 19 • You will need flexibility that only very few approaches can provide – Regex is one of them – Having a text file is a start • You typically want to analyze more than one database – (if not all) • You do not only want to search for code, but e.g., count – Forms, views, actions, agents … – Lines of code (per programming language) – …
- 20. How DXL? 20 • Use notepad or similar to take a first look – (Yes, that might be painful) • Use XSLT → HTML – (e.g. Comprehensive XSLT for DB design @OpenNTF) • Tools like e.g. LotusScript Manager or Source Sniffer from OpenNTF – Stay away from Lotus Analyzer
- 21. 21 Just because you don’t have enough Headaches already …
- 22. Just because you don’t have enough headaches already 22 Having to deal with Remarks in code: – %REM … %ENDREM – (no)code ‘(apostrophe) – REM – (no)code : REM – REM "comments"; – REM "comments“ ; – REM {comments} ;
- 23. Just because you don’t have enough headaches already 23 It’s great what kind of Flexibility we have (to deal with): – Var = “123“ – Var = “123“ – Var=“123“ – Var=‘123‘ – Var=_ “123“ – Var=FullTrim(| 123 |)
- 24. Just because you don’t have enough headaches already 24 @DbLookup(class:cache; server:db; view; key; fieldName; keywords) @DbLookup(class:cache; server:db; view; key; columnNumber; keywords) Challenge and Opportunity: • Find all @DbLookups (and @DbColumns, …) • Only flag the ones pointing to “other” databases
- 25. Just because you don’t have enough headaches already 25 And here is what that regular expression could look like: (?iw) @db(column|lookup)s*? ((s*??"notes?"|s*??"?")[^;]*; (?!(?!s*??".+??"|s*?S+s*?:s*??".+??")| s*??"?"(s*?:s*??"?")?s*?;|s*?@dbnames*?;| s*?@subsets*?(s*?@dbnames*?;s*?1s*?)s*?: s*?@subsets*?(s*?@dbnames*?;s*?-1s*?)) [^;]*;[^;]*;[^)]*)
- 26. 26 Enough! • Follow our blog for more details (if you‘re into stuff like that) • 3rd party solutions that help are available!
- 27. Make Your Data Work For You Three common use cases
- 28. Three common use cases • Moving your Domino applications from on-prem to the Cloud • Migrating mail from Notes/Domino to a new platform • Checking application compatibility with Nomad
- 29. Three common use cases Cloud Migration • Hard-coded names – IP addresses, server names, user names, … • External interfaces – File system, libraries/DLLs, interfaces to SAP, Fax, … • Dependencies on other DBs • …
- 30. Three common use cases Mail Migration • Signed and/or encrypted mails – IP addresses, server names, user names, … • Address book fields • Accessing the mail file – Mails, Calendar, Todo, … • Special mail content – Document links, embedded views, … • …
- 31. Three common use cases Nomad Compatibility • Java / XPages Code • C-API calls without platform-specific “Declare” • ODBC not supported • 3rd party client extensions – e.g. Adobe for PDF creation • …
- 32. Three common use cases Nomad Compatibility • Java / XPages Code • C-API calls without platform-specific “Declare” • ODBC not supported • 3rd party client extensions – e.g. Adobe for PDF creation • … Shout-out to MarvelClient! Analyze and Manage Notes Clients Check out Free Essentials offering for this use case!
- 33. There are a lot more use cases! • Check out our sandbox for examples – Dozens of rulesets, insights and regex patterns
- 34. Make Your Data Work For You Where to go from here
- 35. Try iDNA Applications for yourself • Try for yourself in our sandbox: https://www.panagenda.com/products/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
- 36. Questions & Answers Franz Walder Product Manager franz.walder@panagenda.com Daniel Klas Inbound Marketing Coordinator @panagenda Join the conversation using #iDNAApplications & @panagenda
- 37. Join us in our next webinar!