Jul 4, 2013 | by Florian Piaszyk | 0 Comments

EMA is NOT an out-of-the-box product, it’s a tool set (framework) that ONLY the Documentum Professional Services Team uses. This tool is exclusively available through EMC IIG Services. Once the engagement is over, EMA leaves with the team and cannot be used for additional migrations. Partners and customers are not able to use EMA without IIG Consulting in a project because EMA bypasses the API (DFC).

The main use case for EMA is the high speed cloning from Oracle based on-premise Documentum installations to MS SQL Server based off-premise (EMC onDemand) installations. For this approach a simple dump&load is not feasible and a tool for cloning is needed. In addition EMC addressed some other use cases at EMC World 2013 like version upgrades (DCM to D2 life sciences and Webtop to D2 or xCP) and third-party migrations.

 

Speed vs. Business Requirements and methodology

Cloning or a 1:1 migration of all objects located in a repository without reorganization and clean-up has no additional business value, the result is just a new platform and/or version (garbage in, garbage out). With EMA, changes on business requirements can not be applied easily during the migration (e.g. new metadata, new object types, business logic etc.). The results of the actual migration can not be discussed with the business department before the content is imported in the target system. If needed, duplicates can not be dictated and managed. And furthermore it is not possible to apply changes during the project with just a few clicks of the mouse as you could with migration-center.

read more

Feb 10, 2010 | by admin | 0 Comments

Es geht wieder los. Die Themen SharePoint Migration und SharePoint Upgrade werden wieder aktuell. Obwohl die Begriffe häufig synonym verwendet werden, gibt es bei genauer Betrachtung einen entscheidenden Unterschied. Eine Migration ist ein Umzug der SharePoint Farm auf eine neue Hardware. Dies ist zum Beispiel dann notwendig, wenn eine SharePoint 2007 Umgebung auf SharePoint 2010 aktualisiert werden soll und die Server Hardware / Software des bestehenden Systems auf 32 Bit basiert. Bei einem Upgrade wird die bestehende SharePoint 2007 Umgebung auf SharePoint 2010 aktualisiert.

Möchte man beim Upgrade auf SharePoint 2010 auch gleichzeitig das Farm Sizing ändern, ist das nur beschränkt möglich. Weiterführende Informationen über die unterstützten Ziel-Topologien gibt es hier: http://technet.microsoft.com/de-de/library/cc262747%28office.14%29.aspx

read more