Embed Size (px)
DESCRIPTION
EMC’s Documentum platform is arguably one of the most complex, highly customized and challenging systems for IT professionals to manage. Gaining visibility into the performance of the various servers across the Documentum environment is challenging but crucial; and maintaining performance monitoring thresholds during customization projects is a severe headache. Furthermore, how do you ensure you are getting the true performance picture inside Documentum’s infrastructure? And how could you possible plan for complex integration and migration projects without it? Join Correlsense and Portford Solutions Group for an online seminar which will offer solutions to these key issues. During this session we will discuss: -Best practices for successful Documentum integration projects -Managing migration projects successfully with the right data -The best tools to gain visibility across the entire Documentum environment
Citation preview
New Strategies for Successful Documentum Integrations, Migrations and Performance Management
June 27, 2012
1. Documentum challenges2. Strategies for success3. Case study4. Summary/Q&A
Agenda
Housekeeping
• Presentation will last 30 minutes• Submit questions via the chat window• Slides will be made available tomorrow
Featured speakers
Bruce BoltonExec VP, Technology and ConsultingPortford Solutions Group
Tom BatchelorSenior Solutions ArchitectCorrelsense
DOCUMENTUM CHALLENGES
Two main challenges
• Low-level system monitoring
• System troubleshooting
Documentum architecture
• Multi-tiered and multi-server environments
• Small environment servers
• Large environment servers
Small environment servers
• Web• Transformation• Content server/
database server• Full-text server
Large environment servers• Have high availability build in • Multiple instances of servers
for load balancing
Configuration architecture
• Click from WebTop can travel through many tiers
• Several systems are customized - Java Methods and WebTop customization
- Type Based Object (TBO)
- Server Based Object (SBO)
Configuration features
• Customization methods provide hooks into document actions
• Action before and after the customizations
• Servers can call different parts of the customizations
Monitoring challenges
• Load balancing – production operation
• Temporary load balancing – document migrations
• Problem root-cause
• Analysis
• Request source
STRATEGIES FOR SUCCESS
1) Start with design
• Understand the nature of user requests• When sizing server, consider customizations• Impact of migrations• Implement roll-back
2) Ramp up vs normal production
• Work with business on ramp-up time• May differ from normal production• Ramp-up may include
-Additional usage
-large scale document migrations
• Identify areas/time requirements
3) Analyze results
• Bottlenecks do not always mean more server horse-power
• Look at customizations processing time• Refine configurations and customizations
4) Monitor continuously
• Once refinements made, continue monitoring• Analyze performance against user
requests….they may change!
CASE STUDY
• Documentum installed for 9 years • Systems updated several times • Performance was slow• Needed to migrate
Large transportation firm in UK
Challenges
• EMC offered only out of box support• Documentum used across business• Problem in the content server - hard to monitor
Solution - application performance management
• See inside DQL• Easy to implement – saw data immediately• Visibility into content server and WebLogic
SLA dashboard
All WebTop transactions are listed, along with response times and SLAs
Transaction model
Slide 23
Transaction Model shows the full breakdown of the different tiers involved
Drill down
Slide 24
Drill down to specific components, here we can see the SQL to Oracle from the Content Server
SLA analysis
SLA Analysis across all tiers in the Documentum application
Transaction instances
Slide 26
Individual Instances of transactions available for further investigation and drill down
Transaction sequence view
Slide 27
Here we can see just how busy a Documentum transaction is
Summary tier breakdown available for this specific request
Transaction tree view
Slide 28
All calls to the Documentum Content server API are visible
Where Documentum Query Language (DQL) is used, this is extracted and displayed in the transaction tree
The resulting SQL is shown in context
Issues shown in context
Slide 29
Here we can see there is some chattiness to the Oracle DB, in context with the DQL statement and the original transaction
Topology map
Slide 30
Topology Map shows connections among the application components
OLAP visibility
Slide 31
SharePath Business Intelligence view shows where time is spent within the application components
OLAP drill down
Slide 32
OLAP allows for drill down, in this case see the time for each type of SQL against the Oracle DB
Summary
• Architecture is complex• Monitoring performance is challenging• To succeed:
- Start with design
- Ramp up vs. normal production
- Analyze results
- Monitor continuously
• DocuNECT and SharePath provide answers
Portford Solutions Group
• Complete document mgmt. service provider for 12 years
• Deep experience in Documentum application development
• Developed migration app for Documentum - DocuNECT
• APM solutions for IT Operations• Supports Documentum, Oracle, SOA and more• Customers include:
Correlsense
Questions
Contact Portford Solutions Group:http://www.portfordsg.com/[email protected] [email protected]
Contact Correlsense:www.correlsense.com/[email protected]
.
