Recording: http://pan.news/20201001 “Which applications are used and unused?” is a central question in nearly every Notes/Domino migration or modernization project. Getting that information just when you need it can make all the difference in successfully setting up and driving your project. There are various sources for usage numbers and they greatly differ in terms of accessibility, quality and thereby usefulness in your project. Join Franz Walder in this webinar to learn about their strengths, weaknesses and how to best utilize them to your advantage. Having accurate usage numbers will also be a powerful tool in determining consolidation potential and thereby license cost savings potential. Find out which users you do not need licenses for anymore, because they haven’t accessed Notes recently. Combining information on inactive users and unused applications will also enable you to realize where server licenses can be saved due to under-utilization. Speaker: Franz Walder

1. Make Your Data Work For You
How to find out
Which Notes/Domino
Applications are unused?
Franz Walder,
October 1st 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. The benefits of mastering (in)activity
II. Available data sources for Usage
III. Opportunities and risks
Agenda

4. I. The benefits of mastering (in)activity
II. Available data sources for Usage
III. Opportunities and risks
Agenda

5. I. The benefits of mastering (in)activity
II. Available data sources for Usage
III. Opportunities and risks
Agenda

6. Make Your Data Work For You
The benefits of
mastering (in)activity

7. Benefits
• Understanding user activity is essential for many topics
• These topics may have overlaps with each other
• We focus on three that are most valuable to our customers

8. Focus
Project Scope
& Efforts
Benefits
Identify
Application
Stakeholders
Reduce
Cost

9. Focus
Project Scope
& Efforts
Benefits
Identify
Application
Stakeholders
Reduce
Cost

10. Identify Unused Applications

11. Saving on Server
License Cost
11
Identify Unused
Applications
Consolidating Apps
on less Servers
Focus Project Scope
(Remove Clutter)
…

12. Discover Inactive Users

13. Saving on User
License Cost
13
Discover Inactive
Users
Replacing Apps
Makes Additional
Users Inactive

14. Reduce
Cost
Focus
Project Scope
& Efforts
Benefits
Identify
Application
Stakeholders

15. Identify Application Owners / Stakeholders

16. Reduce
Cost
Focus
Project Scope
& Efforts
Benefits
Identify
Application
Stakeholders

17. Automated Project Scope Reduction

18. Focus
Project Scope
& Efforts
Benefits
Identify
Application
Stakeholders
Reduce
Cost

19. Make Your Data Work For You
Available data sources
for Usage

20. Available Data Sources
User Sessions
in (dom)log.nsf
User Activity
in DB Properties
Document Editors
in DB Content
Activity Trends
in activity.nsf
Usage

21. Client Sessions in (dom)log.nsf
• log.nsf → Usage → By User, DB, Date …
21

22. Web Requests in (dom)log.nsf
• domlog.nsf → Requests By Date, Site, Content …
22

23. User Activity in DB Properties
• Database Properties → i → User Detail
23

24. Document Editors in DB Content
• DB Content → Document Properties
24

25. Activity Trends in activity.nsf
• activity.nsf → Databases → Inventory
25

26. Make Your Data Work For You
Opportunities and risks

27. Opportunities and Risks
27
Opportunity
RiskWeakness
Strength

28. Weighing Your Options
28
Opportunity Risk
?

29. Client Sessions in log.nsf
Strengths
• Available without additional configuration (per default)
• Very good granularity (user sessions per DB on server)
• Little server overhead / performance impact
• Extremely dependable and hassle free
Weaknesses
• Log file (views) can grow very large
• History usually limited to 7 days / needs ongoing collection
(no long-term history available in most cases)
• No web usage
• No differentiation for Agent or Replication activity
29

30. Client Sessions in log.nsf
30
Opportunity Risk
• Very reliable data source with great features makes an outstanding option
• Majority of weaknesses are mitigated by configuration options
?

31. Client Sessions in log.nsf
• Very reliable data source with great features makes an outstanding option
• Majority of weaknesses are mitigated by configuration options
31
Opportunity
Risk

32. Web Requests in domlog.nsf
Strengths
• Widely used option for web activity logging
• Very good granularity (web request per DB on server/site)
• Long-term history may be available
• Config options to minimize performance impact
• Config option to write files instead of Notes DB
Weaknesses
• Needs to be enabled manually
• Log and esp. views can grow very large
• A lot of clutter if not configured sensibly
• No grouping by session
32

33. Web Requests in domlog.nsf
33
Opportunity Risk
• Good data source with important features makes this a solid option
• Majority of weaknesses are mitigated by configuration options
?

34. Web Requests in domlog.nsf
34
Opportunity
Risk
• Good data source with important features makes this a solid option
• Majority of weaknesses are mitigated by configuration options

35. User Activity in DB Properties
Strengths
• Easy to enable (sometimes enabled per default)
• Very good granularity (user sessions per DB on server)
• Long-term history may be available
• Little server overhead / performance impact
• Easy to export
Weaknesses
• Not enabled per default
• DB history holds a maximum of ~1000 entries FIFO
• No web usage
• Long names are cut off
35

36. User Activity in DB Properties
36
Opportunity Risk
• Good data source to provide an instant foundation based on existing history
• Various issues with data quality and uncertainty of availability as an issue
?

37. User Activity in DB Properties
37
Opportunity
Risk
• Good data source to provide an instant foundation based on existing history
• Various issues with data quality and uncertainty of availability as an issue

38. Document Editors in DB Content
Strengths
• Available for every accessible database
• No server overhead / performance impact during collection
• Long-term history is available
• Unique data source for some information
Weaknesses
• Limited in granularity and available information
• Can be a lot of data to process depending on DB size
• Potential issues with access, encryption, reader fields …
• No read-only information (only r/w operations)
38

39. Document Editors in DB Content
39
Opportunity Risk
• Great data source to provide an instant foundation based on existing history
• Weaknesses are mainly limitations that can be less relevant if used correctly
?

40. Document Editors in DB Content
40
• Great data source to provide an instant foundation based on existing history
• Weaknesses are mainly limitations that can be less relevant if used correctly
Opportunity
Risk

41. Activity Trends in activity.nsf
Strengths
• Low entry barrier (easy to use)
• Differentiates between User/Agent/Replication traffic
• Long-term history may be available if previously enabled
Weaknesses
• Significant overhead / performance impact during collection
• Continuous collection required (low customer acceptance)
• Heavily pre-aggregated (parameters not configurable)
• Very limited drill-down capabilities
(No connection between user on database on server)
• Relies on log.nsf and catalog.nsf among others
41

42. Activity Trends in activity.nsf
42
Opportunity Risk
?
• Good data source for a quick comprehensive overview with known limitations
• Significant limitations and server impact lead to low customer acceptance

43. Activity Trends in activity.nsf
43
• Good data source for a quick comprehensive overview with known limitations
• Significant limitations and server impact lead to low customer acceptance
Opportunity
Risk

44. What does iDNA Applications use?
44
Usage
Client Sessions in log.nsf
&
Web Requests in domlog.nsf
User Activity
in DB Properties
Document Editors
in DB Content
Use existing long-term
history to provide
instant value
Use detailed editor info
to support search for
stakeholders

45. Make Your Data Work for You
Where to go from here

46. 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

47. Questions & Answers
Franz Walder
Product Manager
franz.walder@panagenda.com
Daniel Klas
Inbound Marketing Coordinator
@panagenda
Join the conversation using #iDNAApplications & @panagenda

48. Headquarters, Austria:
panagenda GmbH (Ltd.)
Schreyvogelgasse 3/10
AT 1010 Vienna
Phone: +43 1 89 012 89
Fax: +43 1 89 012 89-15
E-Mail: info@panagenda.com
Headquarters, Germany:
panagenda GmbH (Ltd.)
Lahnstraße 17
DE 64646 Heppenheim
Phone: +49 6252 67 939-00
Fax: +49 6252 67 939-16
E-Mail: info@panagenda.com
USA:
panagenda Inc.
60 State Street, Suite 700
MA 02109 Boston
Phone: +1 617 855 5961
Fax: +1 617 488 2292
E-Mail: info@panagenda.com
Germany:
panagenda Consulting GmbH (Ltd.)
Donnersbergstraße 1
DE 64646 Heppenheim
Phone: +49 6252 67 939-86
Fax: +49 6252 67 939-16
E-Mail: info@panagenda.com
The Netherlands:
Trust Factory B.V.
11th Floor,
Koningin Julianaplein 10
NL 2595 AA The Hague
Phone: +31 70 80 801 96
E-Mail: info@trust-factory.com
© 2007-2015 panagenda
Make Your Data Work for You