What do you know about your Documentum system? Learn how to prevent Documentum downtime with deep visibility and with three key insights. First though, do you know: - Your processor load, memory usage & disk space? - Your overall server health? - If your Documentum system is available? - How many users are on it? - What transactions are they executing? - If your system is operating at peak performance? - How long it takes to check out a document? - If you are meeting your SLAs? Without Deep Documentum Insight... - Firefighting & lengthy troubleshooting becomes the norm - Users become disenchanted due to missed SLA’s & productivity suffers - App support is stuck in reactive mode & planning is difficult In a Reveille survey of Documentum users at EMC World 2014, preventing downtime was cited as a top concern - 50+%! 3 Metrics to Prevent Downtime 1. Server Health Metrics - Repository space available - CPU Usage - Memory Consumption Managing underlying server metrics ensures a solid physical/virtual foundation for your Documentum environment Note: Reveille Scorecards show server health over time – watch for upward trends to prevent downtime 2. System Usage Metrics Understand all end user activity & system processing, such as: - Content Server Active/Total Sessions - Content Server App Activity Count - ACS Requests - BAM Job Counts - BOCS Request Counts - CTS Queued & Total Task Counts - xPLORE Pending & Processing Counts - JVM Session Counts Note: Understand distribution & peak times for both users & processes to ensure system availability 3. Response Time Metrics - End User Response Times for your key client apps such as D2, xCP, WebTop, Mobile - API Performance - Database Query Response Times - Repository Transaction Performance - Document Transformation Times Understand expected response times for both user transactions & common processes Note: Investigating the cause of slowing response times can prevent larger system down situations Take a Product Tour: http://reveillesoftware.com/product-tour/

1. What Do You Know
About Your
Documentum
System?

2. Do You Know….
2
•Your processor load, memory
usage & disk space?
•Your overall server health?

3. Do You Know….
3
•If your Documentum system
is available?
•How many users are on it?
•What transactions are they
executing?

4. •If your system is operating at
peak performance?
•How long it takes to check out
a document?
•If you are meeting your
SLAs?
Do You Know….
4

5. Without Deep Documentum Insight...
5
Firefighting & lengthy troubleshooting
becomes the norm
Users become disenchanted due to
missed SLA’s & productivity suffers
App support is stuck in reactive mode
& planning is difficult

6. Preventing Downtime a Top Concern
* “Content Management Environment” Survey, Reveille Software at EMC World 2014
6
Improving/reporting
service levels
Performance tuning
Preventing
downtime
Increasing end-user
experience visibility
Regulatory/audit
compliance
Reducing support
tickets/Ops costs
Protecting docs
against theft/
unauthorized use
In a Reveille survey of Documentum users at EMC World 2014, preventing
downtime was cited as a top concern

7. 3 Metrics to Prevent Downtime
Deep application insight

8. Critical Metrics to Monitor
Ensure Documentum
Availability
3
Response
Times
1 Server
Health
2 System
Usage
8
Peak Documentum Availability

9. Server Health Metrics
• Repository space available
• CPU Usage
• Memory Consumption
9
Managing underlying server metrics ensures a solid
physical/virtual foundation for your Documentum environment

10. 1Server Health Metrics
10

11. System Usage Metrics
Understand all end user activity & system processing,
such as:
• Content Server Active/Total Sessions
• Content Server App Activity Count
• ACS Requests
• BAM Job Counts
• BOCS Request Counts
• CTS Queued & Total Task Counts
• xPLORE Pending & Processing Counts
• JVM Session Counts
11

12. 2System Usage Metrics
12

13. Response Time Metrics
• End User Response Times for your key client
apps such as D2, xCP, WebTop, Mobile
• API Performance
• Database Query Response Times
• Repository Transaction Performance
• Document Transformation Times
13
Understand expected response times for both user
transactions & common processes

14. 3Response Time Metrics
14

15. Thank You
Take a Product Tour:
http://reveillesoftware.com/product-tour/
15
user/ReveilleSoftware
@ReveilleSoftwre
company/Reveille-Software
/ReveilleSoftware