Ran's World

  Upgrading and Migrating Migration overview The goal of migration is to allow you to continue to work in the current version or the product with projects that you developed in previous versions. Projects that you created in V6.0.x or V7.0.x can be migrated to this version. Projects from   version 6.0.x   or   version 7.0.x   are migrated using the Workspace Migration wizard. When projects from   version 6.0.x   or version 7.0.x   are detected in the current version, the Workspace Migration wizard starts automatically and selects the projects to migrate.   Backward compatibility of migrated projects and workspaces Backward compatibility   of a project (or other artifact) refers to its ability to work with earlier version of the product. Projects migrated from V6.0.x to this version are not backward compatible with V6.0.X. Projects migrated from V7.0.x to this version are backward compatible with V7.0.x. Note:   If you migrate a workspace from   version 6.0.x   or

Upgrading and migrating, when we say upgrading it refers to the replacement of a product with a newer version of the same product. When we say migrating, it refers to go from one place or software to another one. Every software has a limit, that’s why they do some upgrade and updates to the software having it more efficient than older versions.          Backward compatibility is a relationship between two components, rather than being an attribute of just one of them. IBM RAD is designed to be backward- compatible. Files that came from the other older versions can be use on the newer versions in a way that the upgrade and update of the software is not that far from each other. The goal of migration is to allow you to continue to work in the current version or the product with projects that you developed in previous versions. OBJECTIVES OF THE STUDY The General objective of the study is to show how Upgrading and migrating works. These are the fol