This document provides an overview of analyzing an IT infrastructure in preparation for moving workloads to the cloud. It discusses: - Understanding user activity through database logs to identify high impact users, applications, and server loads. - Analyzing application design dependencies, features, interfaces to assess complexity and feasibility of moving applications. - Combining usage and design analysis with organizational data to understand the full infrastructure picture and identify critical applications and areas for a successful transition.

1. Cloud Readiness 101:
Analyzing and Visualizing Your
IT Infrastructure
Francie Tanner - panagenda
1

2. Agenda
• Getting started
• Introduction
• What can you expect from this session?
• What is The Cloud and why are companies “moving there”?
• Making your infrastructure transformation a success
• Key factors identified and explained
• User activity analysis - who uses what and how?
• Application design analysis - identifying scope and feasibility constraints
• Summary: Infrastructure as a whole
2

3. Introduction
• Francie Tanner, Director, Americas
• Over 17 years experience in IBM Lotus consulting
• Managing, architecting, and supporting
10 – 100'000 user environments
• Experienced Lotus instructor and speaker
• CH -> US -> AI -> US -> ?
3
| © 2012 IBM Corporation

4. What can you expect from this session?
• Managing Infrastructure changes as a whole
• Understanding how moving to the cloud is best approached
in an IBM ICS environment
• Ways to identify and measure critical success factors
involved, in order to be able to calculate expected effort
• Samples of environment and application analysis
4

5. What is cloud
= someone else’s computer
5
XPages
IBM Connections
HTML5
IBM Notes

6. • What exactly is the cloud and why are companies
moving there?
• Why?
• Costs – CAPEX vs OPEX
• Flexibility, Integration, Scalability
• Easier Upgrades
• Speed (?)
• How?
• That is what this session is all about
• There is no “Move to cloud”–button …
• “Adapting a Cloud strategy” is a key driving factor for many
6
Getting started

7. Getting started
Evolution of IT projects: From static projects …
7

8. Getting started
Evolution of IT: Classic 18 – 24 month upgrade project
8
Project
Stable StableChange

9. Getting started
Evolution of IT projects: … to ongoing agile transformation!
9

10. Getting started
Agility is the key to success
10
Continuous Change

11. One goal?
More like many moving targets!
XPages
IBM Connections
HTML5
IBM Notes

12. 12
Continuous Change
Getting started
Agility is the key to sucess

13. Agenda
Making Your Move a Success
Key factors identified and explained
13

14. 14
Key factors identified and explained
• Clarifying why you do it and for whom
• Understand the motivators of your stakeholders
Management / Governance, Technical, Business
• Why you do it has a big influence on setting your goal
and how you measure success
• User Activity Analysis
• Demand Characteristics
• Usage - Reads, Writes, Users
• Load - Transactions, CPU, Memory, …
• Availability / Reliability / Performance
• Geographies / Topologies
• Bandwidth - demand vs. availability

15. 15
• Application Design Analysis
• Cross Linkage of Mail, Apps and Business Processes
• Dependencies
• Features & Functions e.g. Telephony integration, Archiving, …
• Interfaces -Fax, Files, Printers, data in a text file on some server …
• Tying those findings to organizational structures
• Has its foundation in user activity
• Evaluate infrastructure utilization by cost center rather than technical by user
or DB
• Identify areas with special significance
• e.g. databases which are mainly used by VIPs
• activity benchmarks across departments
Key factors identified and explained

16. 16
Increasing
Consulting
Demand
Decreasing
Risk for
Customer & IBM
Making Your Move a Success

17. User Activity Analysis
Who uses what and how
17

18. User Activity Analysis
What can user activity tell you?
• Read vs. Write traffic
• Mail vs. Apps
• Transactions - Server load
• High impact users & apps
• Excessive usage
18

19. What happens when moving to the cloud ...
19

20. What happens when moving to the cloud ...
20
On premise
?
?
?
?

21. What happens when moving...
21
Off premise
?
?
?
?
?

22. What happens when moving...
22
Off premise
?
?
?
?
?

23. Traffic jam
23

24. 24
User Activity Analysis
• Users
• How many, where are they – session concurrency
• When do they use resources – data center location
• What kind of connectivity do they have
• How much do they read vs write
• Resources – Servers, Clients, Apps
• Rich clients, iNotes, plugins, browser
• How many Apps, where are they
• Server power consumed and required
• Bandwidth to/from servers

25. 25
User Activity Analysis
How to get the data without 3rd party tools
• DB Activity: LOG.NSF –
documents with form type “Activity”
• View selection formula: SELECT FORM = "Activity"
• Add columns that are interesting in your scenario

26. 26
• DB Activity: LOG.NSF – database activity details
• Note there is a 1400 activity entry maximum per database (FIFO)
• There is also a 64K size limit for the user activity
• More details in IBM Technote #1086245
User Activity Analysis
How to get the data without 3rd party tools

27. 27
• DB Activity: CATALOG.NSF
– related information, different focus
– Full text index details
– Replication information
– ACL overview
Note: Domino does not distinguish
between user, server or
maintenance tasks activity at this level
User Activity Analysis
How to get the data without 3rd party tools

28. 28
• User Activity: LOG.NSF
basic information is easy to extract
• File → Export → Comma Separated Value
• Combine results of multiple servers in spreadsheet calculation
software
User Activity Analysis
How to get the data without 3rd party tools

29. 29
User Activity Analysis
DEMO: Activity analysis example

30. Application Design Analysis
Scope and feasibility constraints
30

31. 31
Application Design Analysis
• Why does application design analysis matter
• Dependencies on hardware (e.g. dongle, mobile phone, etc.) or
software (e.g. DLL on windows machine)
• Standard applications (Mail, Teamrooms) often migratable with
very low effort
• Design complexity and code type may make
transformation extremely complex

32. 32
Application Design Analysis
• Geography and Topology considerations

33. 33
Application Design Analysis
• Possible destinations
• Web application (e.g. XPages)
• Mobile application
• Notes browser plugin
• Hybrid
• ...

34. Infrastructure as a Whole
Understanding the big picture
34

35. 35
Understanding the big Picture
• Combining usage and design analysis is essential
• Organizational considerations
• Who owns and “will pay” for migrating an application?
• Combination with HR data
• Compare efficiency of infrastructure consolidation vs transformation
• Hard numbers are much easier to deal with than guesstimates
• IBM Domino Doublecheck is a great foundation

36. 6
Questions?