This is the fourth post of my series “Insights into the development of migration-center 4”. In the last post I showed you how to configure and run a scanner in order to read all the desired files and their metadata from the source system. In today’s post I will show you how to organize your scan runs into so called migration sets. All further processing in the migration-center, i.e. transformation, validation and import will be based on a migration set. So the definition of a migration set is an important step in the whole migration workflow.
When you press the Organize icon in the main navigation bar, the client shows you the list of existing migration sets. You can use the icons in the command bar above the list to create, edit, copy or delete a migration set.
IBM Notes has been around for so many years – yet still many companies use it. Some are heavily relying on it as it supports many different processes – it can be used as an email tool for communication, as a database with or without any kind of documents and even as a feature rich application for (critical) business processes and workflows.
Notes is flexible and supports all kinds of different and custom scenarios.
However, there are several reasons to replace it with other platforms, especially when it comes down to document management. I do not want to talk about them in detail because you might know those already and therefore are reading this right now.
I want to talk about the solution to move to other platforms and I want to clear up doubts about the possibility to lose any information during the migration.
The typical migration scenario with migration-center is to read – or scan, as we call it – documents and their metadata from the source system (1), do necessary transformations on those documents in order to fit the target system (2), and finally write – or import – them into the target system (3).
Migration is an ongoing IT topic and there are many good reasons for that: Switching platforms or architecture e.g. when changing an operating system or database, virtualization and moving to the cloud are some reasons to be considered. In addition, the integration or merger of systems and applications can make content migration a relevant topic, as cost efficiency is a big deal in these cases.
Are you currently facing a migration project? Especially any Documentum migration task? Have your colleagues given you any serious advice to handle Documentum object IDs very carefully? A common example for that: Published links in intranet or e-mails referencing important documents through object IDs. Have you been asked to keep these documents’ object IDs and all their links working?
In this blog post I want to share some thoughts, experiences and solutions on migration regarding Documentum object ID concerns with you.
The development of migration-center 4 is moving forward. In today’s post I would like to show you two of the new basic configuration screens that we have designed in migration-center 4.
(English version below)
Dies ist der erste Beitrag einer kleinen Artikelserie, die einen Einblick in die Entwicklung der nächsten Hauptversion unseres migration-centers (MC) geben soll. Ab sofort werden wir an dieser Stelle neue Funktionen, Funktionalitäten und Verbesserungen vorstellen, auf die Sie sich freuen können. Im ersten Teil der Serie geht es hier um die neue Benutzeroberfläche.
Why migration-center 4.0?
The new major version 4 of our proven migration product is currently being developed and will be released in 2017. Version 4 comes with a new and modern user interface, great new user experience and a lot of new functionality that will make your migration team even more productive. The motivation to develop a new major version of migration-center have been the architectural and technical constraints of version 3 that inhibited major improvements in the areas of usability, customization, performance, functionally and custom jobs support (pre & post processing.
New technologies used
The modernized migration-center job server’s architecture will allow multi-threading in all adapters, easier adapter deployment, and the integration of any kind of custom adapters or jobs – so you can expect faster migrations and support for new use cases. The job server and the client will use state-of-the-art REST web services for communication instead of proprietary protocols, making it even easier to implement custom adapters/jobs.
Use migration-center to keep your sales and marketing collateral up to date in SharePoint
The migration-center is an out-of-the-box product to migrate content automatically and easily from one location to another. It is designed for large volume content migrations, easy to use and works with high efficiency. The product offers a wide range of migration paths from a wide variety of source and target systems as well as a professionally documented developer API to build your own source and target system adapters. The migration-center is not only a tool to migrate your content from one system to another, but also provides possibilities to (re-)organize your content in different locations.
Use case: sales and marketing collateral
We are sometimes faced with the challenge to combine daily collaborative work on up-to-date sales and marketing collateral and filing them in a system of records like Documentum effectively. At the same time you want to establish your server as a public point of access for your partners or customers where all product information is stored, but without granting them access to your system of records with possibly confidential content. In this case you might consider separating your system of records (e.g. Documentum) and setting up a discrete server running SharePoint with public access for your partners and customers. During the last years Microsoft’s SharePoint platform has become more and more important and received increased interests due to useful collaborative capabilities. read more
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.
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