fast track to deploying or migrating to d6.5

1© Copyright 2009 EMC Corporation. All rights reserved.

Fast Track to Deploying or Migrating to D6.5


AGENDA

IntroductionsPlanning Your 6.5 MigrationDeveloping Your 6.5 SolutionRolling Out Your 6.5 SolutionQuestions


Introduction: Deployability Charter

Collect and Analyze Results

Identify High Priority/Payback Items

Drive Corrective Actions

Lead Deployment Initiatives

Design Partner

Beta

PREPP

Initial Deployment

Controlled Release

Rapid Success

Customer/ Partner

Programs

Deployment Solutions

Enhance Customer Success and Accelerate Customer Deployments by Running “Pre- and Post-release customer programs”, Product Advisory Forums and Driving Deployability Product Requirements to Speed Deployment of EMC Documentum Products by Our Global Customers.

Product Advisory

Forums (PAFs)

Facilitate Idea and Information Exchange, Product Plans Between Customers and Product Management


What type of D6.5 deployment are you planning?

0 10 20 30 40 50 60

None Planned

New

Migration

Upgrade

Upgrade = Move to 6.5 Version, with minimal changes to existing deployment

Migration = Move to 6.5 Version and make substantial changes to deployment

New = Roll out a new application on 6.5


Where are you in your 6.5 deployment?

Requirements/DesignRequirements/Design DevelopmentDevelopment

TestTest

User Acceptance/PilotUser Acceptance/PilotInitial Production Live

Initial Production Live

Complete 6.5 Roll-Out


Most are in early stages of 6.5 deployment and coming from 5.3




TestTest






Ready! Set! Preparing for your 6.5 Deployment

Align with EMC roadmap

Plan your infrastructure

Understand supported migration path

Know the 6.5 benefits

Assess your deployment risk

Planning tips for deployment success


Align with EMC Roadmap EMC Release Types and Support Durations

Release Type External Name

Internal Name Characteristics

Major A.0 A.0

Architectural ChangesRevolutionary ChangesAs requiredEOS: 4 years + Extended Support

Minor A.B A.B

Feature EnhancementsRollup and Regression QA of HFMinimum 9 – 12 months after MajorEOS: Sync with Major (3 years minimum)

Service Pack A.B SPx A.B.x

Rollup and QA of HFAs needed - Typically

Release + 4 mo = SP1, + 6 mo = SP2, + 8 mo = SP3

EOS: Sync with Major/Minor

Hot Fix/Patch A.B SPx HFy A.B.x.yyyyBug fix(es) for urgent customer issuesReleased on current Service Pack


Model Enhancements

Enhanced TCO & deployment planning horizon– Release supported for 6 years (4 yrs standard plus 2 yrs extended)– Predictable Service Packs

– Release frequency: Major +4; Minor +4, +6, +8– NEW: Guaranteed support overlap of 24 months from last SP to next major release

Improved Service Pack quality and reduced upgrade Impact– Limited features in Service Packs; – All feature inclusions undergo high scrutiny and require executive approval

Timely feature enhancements in a predictable release model– NEW: Major/Minor release every 9 – 12 months


Documentum 6.x Content Server is backward compatible

Documentum 5.3 client applications supported with Documentum 6.x Content Server include Webtop, DAMtop, Custom 5.3 and D6.x DFC and WDK apps

5.3 Client D6.x Content Server


Limited # of D6.x clients are backwards compatible

D6.x Client5.3 Content

Server


Migration fine print

Except for Webtop, custom DFC and custom WDK apps you will need to migrate your Content Server first, then your client applications

In a mixed environment i.e. using 5.3 & 6.x clients against the same D6.x Server

Certain 5.3 SBO & TBO restrictions might apply (details in migration guide)

Separate 5.3 and D6.x/D6.x.5 Global Registries are required

Full functionality may not be accessible through 5.3 clients

Following D6.x applications require all other clients accessing the same D6.x Server be also D6.x and therefore that the clients be upgraded at the same time

– Records Manager– Retention Policy Services– Documentum Collaborative Edition

BPM and DCM suite of products should be upgraded to D6.x in groups


Full Text migration

Upgrading from 5.3 SP2 or SP3 with Get Well Fixes

– NO Full-text Rebuild

Upgrading from 5.3, 5.3 SP1

– Rebuild Indexes

Upgrading from 5.2.5 -> 5.3 -> D6.x.x

– Rebuild Index – Only Once


Global Registry enhanced capabilities

In Documentum 6.x, the global registry is required for all clients

The global registry stores objects such as:– User preferences– Location information– Server-based Objects– Presets

It is necessary to have a D6.x global registry for D6.x clients

It is necessary to have a 5.3 global registry for 5.3 clients that require it

The global registry is a significant consideration during migration


Migration decision tree

Did you have a single server/repository (departmental solution)

OR

a distributed server/repository configuration (enterprise solution)?


Departmental solution with a 5.3 global registry

If you had a 5.3 global registry:

1. Upgrade the server, repository and clients all at once

Or

1. Create a second repository dedicated to 5.3 global registry2. Upgrade the Content Server and repository to D6.x3. Create the D6.x global registry4. Use utility to move global registry objects from 5.3 to D6.x5. Decommission the 5.3 global registry repository


5.3 Departmental solution with no global registry

If you had no 5.3 global registry1. Upgrade the 5.3 Content Server and repository to D6.x2. Designate the repository as the D6.x global registry3. Upgrade client applications to D6.x


Enterprise Solution using 5.3 global registry

1. Leave your 5.3 global registry repository in place2. Create a new Documentum 6.x global registry repository3. Use utility to migrate 5.3 global registry objects to the Documentum 6.x global

registry repository4. Upgrade content server(s) to Documentum 6.x5. Upgrade application server(s) and clients to Documentum 6.x6. Decommission your 5.3 global registry repository


New Infrastructure for 6.x

Java 5 Support

JMS – using JBOSS (6.5 +)

Eclipse, Composer and DARS

IPV6

Kerberos (coming SP2)

Presets

DFS


DMCL functionality now Java Based D6.x using Java 5

Content ServerDMCLC++

JNI

DFCJava

Content Server

DFC

J-DMCL Java

5.3

D6.x


WAR file Deployment

Java based DMCL Enables WAR File Deployment for WDK Apps

Allow IT personnel to deploy WebApps using App Server tools

Simplify Clustered and HA deployments

Accelerate support for new App Server versions

Allow “non-exploded” WAR file deployment for better performance

Sandbox DFC per Application to avoid application conflicts

Simplify troubleshooting by removing transition from Java to C++


D6.x WDK based deployment scenario

Developer – Download WAR – Deploy WAR to Dev Application Server (in expanded mode)– Configure Web Application – Add Customizations, Language Packs and Patches– Create deployable WAR

Production Machine Admin– Deploy Production WAR -> Application is up and ready to use!


RAD: DocApps vs. Composer Projects

DocApps Composer Projects

Development Mode

Online - requires connectivity to Documentum repository

Offline – Configuration stored locally as xml metadata

Deployable Package DocApp Archive DAR

Package Installer DAI DAR Installer or Headless Composer

Source Control Management

Check-in and version entire DocApp Archive

Check-in and version individual Composer Artifact files


Deprecations

Deprecations with Available Alternatives– Routers replaced by Workflows – CTA replaced by UCF– DMCL replaced by Java API– BOF1 replaced by BOF2– DAB/DAI replaced by Composer

Removals– DFC no longer supports Linked Store– DFC no longer Optical Storage Devices


Deployment Benefits in 6.5

Preset Benefits– Reduce customized config xmls – Makes easy migration to future releases – Presets can be defined and applied during runtime

Compared to customizations which is done in pre-deployment stage.

Allows users to roll out features as they have end-user training available– Presets can be defined by users having preset coordinator role

DFS Benefits– Allows you freedom to use any development environment

.NET Productivity Layer– Makes easy migration to future releases – More scalable, available


Documentum ECM 6.5 - Faster and Easier

37% fewer mouse clicks for average user

Cut review/approval time by 90%

High volume ingestion—10’s of million objects per day

Design and test new processes up to 50% faster

Up to 55% faster file transfer time

Offline bulk loading for data migration is 61x faster

EMC Documentum Platform

Record-breaking benchmark demonstrates massive scalability of EMC Documentum 6.5 – 100,000 concurrent users is 10x larger than any other

published benchmarking study in the ECM industry


Risk Assessment and Mitigation Plans

Changes to the products– That are new and you wish to use– That affect areas you might have customized– Consider a Consulting Risk assessment

Changes to your infrastructure– That affect the sizing and performance of the system– That require new interoperability testing– Consider an Architecture Review

Changes affecting your end users– Changes affecting User Experience may require training– Consider 6.5 delta training– http://software.emc.com/services/education


Planning Tips for a Successful Deployment

Well Defined Plan CreatedClear Goals SetDeployment is Business CriticalExecutive Sponsor SelectedVendor Roadmaps ResearchedYour People Prepared Your Technical Infrastructure PlannedYour Hardware ProcuredEarly Risk Identification and EliminationChange Management is a Priority




TestTest






Go! Advantages to Help You Win the Race

Use a Migration tool

Consider VMware

Train your team

Use provided references– Migration Guides– What’s New Documents

Join the 6.5 communities!


Migration Tool

Determine all sources of datas– Legacy systems– File servers– Paper based servers– Other EMC Documentum repositories

Determine frequency

Usually a tool investment will bring great ROI– Crown Software’s Buldoser is on EMC’s Price List


Optimize Your Deployment with VMware

Create Development Sandboxes

Create “Crash and Burn” Test Boxes

Create “Golden” Environments

Provision New Systems in Minutes using Templates


Useful References

White Papers

Performance Improvements of D6.5 over D5.3

D6.5 Sizing Tool

Deployment Strategy for Directory Services (LDAP)

Support for IPV6

UCF Content Transfer Tuning Guide

High Volume Server Tuning Guide

High Volume Server Performance & Scalability

SourceOne for Email Sizing Guide Benchmarks

100,000 User Webtop

TaskSpace

SourceOne for Email

Captiva Input Accel (Coming in SP!!)


Development Tips for a Successful Deployment

Verify performanceTackle riskiest development firstEnsure your test environment mimics productionDon’t wait to get your user’s involved




TestTest






Approaching the Finish

Handle deployment issues– Keeping dev/test servers around

Real time scaling

Handling changing HA requirements

Disaster Recovery planning

Upgrades and Service Packs


Get Involved with EMC CMA Communities

Why should you join?

Collaborate and share best practices

Shape the direction of future EMC products

Network with innovators across the globe, 24/7

Join now by going to: community.EMC.com/go/Documentumcommunity.EMC.com/go/SourceOnedeveloper.EMC.com/Documentumdeveloper.EMC.com/XMLtechcommunity.EMC.com/community/labs/d65

fast track to deploying or migrating to d6.5

Technology