Customers are often challenged by migrating Web content from one content management system to another. This article describes an approach for migrating to IBM Web Content Manager V7, based on customer experiences, addressing topics including process, tooling, and mapping concepts.
Tag: migration
Tips for moving from Microsoft Outlook to IBM Lotus Notes 8.5.2
Have you just moved away from Microsoft® Outlook to IBM® Lotus® Notes® 8.5.2? This article discusses some key tips on what preferences to set and ways to configure Lotus Notes to be compatible with the functionalities you were accustomed to in Microsoft Outlook. It addresses tips for mail, calendar, and contacts, along with general tips for across the Notes client.
via Tips for moving from Microsoft Outlook to IBM Lotus Notes 8.5.2.
Using the new IBM Lotus Connections 2.5 migration tool
Migrating artifacts is a key task when you are migrating your existing Lotus Connections version. Using the migration tool in version 2.0.1, you were able to accomplish this task to some extent; for example, you could migrate some configuration and all data files. You still had to customize many configurations manually, which is one of the most painful tasks in the migration process.
The newly added features in Lotus Connections 2.5 mean that many more configurations must be migrated. The latest migration tool, which is based on XSLT technology, provides a simple and effective way to migrate all necessary configurations and data files. With its help, you don’t need to manually reapply all configurations.
This article explains how to use the Lotus Connections 2.5 migration tool, including how to troubleshoot errors and perform a recovery, so that you can understand the migration tool and correctly migrate the artifacts of your existing Lotus Connections environment.
It is assumed that you have a good understanding of IBM WebSphere® Application Server and a general understanding of XSLT and XML Path Language (XPath) technology.
IBM – Knowledge Collection: Migration planning for WebSphere Application Server
The primary purpose of this material is to provide information required to plan and execute a successful migration between different versions of WebSphere Application Server. The goal is to provide a central set of information and references to enable customers of WebSphere Application Server to do this migration themselves without requiring assistance. There has been significant improvement over time in the area of WebSphere Application Server migration, but there are still some technical aspects involved in any migration scenario. These technical aspects can be addressed easier, and with reduced risk, if understood and addressed early. The overall process will always need careful planning and execution no matter how trivial the technical aspects might become for compatibility of applications themselves.
There are different migration scenarios. Migration scenarios are defined based on what combination of WebSphere Application Server versions are being migrated. There are different factors to consider based on what the “from” and “to” versions are that are being migrated. Each migration scenario is unique.
via IBM – Knowledge Collection: Migration planning for WebSphere Application Server.
IBM – Steps for upgrading to Notes/Domino 8 from versions 6.5 and 7
Abstract
This document contains the recommended procedure for upgrading to Lotus Notes/Lotus Domino 8.x from versions 6.5 and 7.
Content
This document is written to be platform-independent. Additional information to run the specific commands for each operating system can be found in the following online documents.
via IBM – Steps for upgrading to Notes/Domino 8 from versions 6.5 and 7.
IBM – Step-by-step Migration Guide for IBM WebSphere Portal and Lotus Web Content Management version 6.1
Abstract
Whether you are migrating an IBM® WebSphere® Portal or Workplace Web Content Management™ 6.0 server to version 6.1, these guides are designed to aid you through the process.
Content
The first paper describes the steps and best practices for migrating an existing standalone WebSphere Portal 6.0 environment to a standalone WebSphere Portal V6.1 and should be followed by the majority of customers, even those in a Web Content Management environment.
The purpose of the second document is to provide a step-by-step guide for migrating IBM Workplace Web Content Management (WCM) version 6.0 to WebSphere Portal v6.1 – Content Build for Lotus® Web Content Management (also WCM). The foundation for this document is the initial release of the V6.1 Information Center with additional information based on the outcome and experiences of our pre-release testing. With this document, we provide a more comprehensive guide and highlight some of the common pitfalls and mistakes when migrating.
Additional interim fixes are also required on the 6.1 system. You can retrieve these fixes using the links below.
IBM – Steps for upgrading to Notes/Domino 8 from versions 6.5 and 7
Abstract
This technote provides information on migrating to Lotus Notes and Lotus Domino 8 from versions 6.5 and 7.
Content
This document contains the recommended procedure for upgrading
to Lotus Notes/Domino 8.x from versions 6.5 and 7.
NOTE: This document is written to be platform independent; additional information to run the specific commands for each operating system can be found in the following online documents.
via IBM – Steps for upgrading to Notes/Domino 8 from versions 6.5 and 7.
Migrating from Microsoft Exchange to IBM Lotus Notes and Domino 8
By using the straightforward steps outlined in this white paper, an administrator can easily migrate data and users from Microsoft® Exchange to IBM® Notes® and Domino® 8. Included are tips and instructions for troubleshooting some common issues.
In this article
* Introduction
* Server-to-server migration steps
* Client-to-client migration steps
* Conclusion
* Resources
* About the author
via Migrating from Microsoft Exchange to IBM Lotus Notes and Domino 8.
IBM – Steps for migrating to Notes/Domino 8 from versions 6.5 and 7
Thinking or planning to migrate to Notes/Domino 8? If you are, here’s a MUST READ that covers the recommended steps for migration. As always, don’t wait too long to involve IBM support when you run into issues.
Abstract
This technote provides information on migrating to Lotus Notes and Lotus Domino 8 from versions 6.5 and 7.
Content
This document contains the recommended procedure for migrating
to Lotus Notes/Domino 8.x from versions 6.5 and 7.
via IBM – Steps for migrating to Notes/Domino 8 from versions 6.5 and 7.
Migrating from PDF forms to IBM Lotus Forms
In the world of e-forms, IBM® Lotus® Forms and PDF forms are the most two popular products. A Lotus Forms project can be categorized as two distinct tasks: migrating from existing e-forms and creating e-forms from scratch. We have found in our experience with IBM Software Services for Lotus that most forms projects involve migrating from PDF forms to Lotus Forms.
The PDF form is a type of e-form that is different from Lotus Forms. It can be a static binary file with no interactive fields or a dynamic XML-embedded XML Forms Architecture (XFA) form. Lotus Forms Conversion Tool 3.0 is a plug-in for Lotus Forms Designer that can convert PDF forms to Lotus Forms 3.0 automatically. It supports both static PDF files and dynamic XFA forms. It also includes a number of customized rules and optimizers that can be applied to the conversion process. After the automatic conversion, the plug-in is needed to manually update the converted forms for the presentation layer, XForms instances, and business logic.
This article gives a brief introduction to the PDF migration project, with a detailed description of the Lotus Forms 3.0 conversion tool. It also includes a detailed list of manual effort and requirements, which is an important list for project sizing and estimation. You should be familiar with the IBM Lotus Forms product. Users of IBM Lotus Forms are all welcome to learn and share the project experience with the forms service project.