Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
7migrate:stages67gp [2018/11/07 11:37] – [Stages v6 to v7.2 program update - overview] vtbr7migrate:stages67gp [2024/02/15 00:00] (current) – external edit 127.0.0.1
Line 1: Line 1:
-===== Stages v6 to v7.2 program update - overview =====+====== Stages v6 to v7 program update - overview ======
  
-<font 14px/Verdana,Geneva,sans-serif;;inherit;;inherit>Update requirements: to upgrade to Stages v7.2 the following preliminary topics need to be clarified:</font>+Please contact your product consultant to work out a migration plan.
  
-  - __**<font 14px/Verdana,Geneva,sans-serif;;inherit;;inherit>Metamodel:</font>**__  A migration of your customer specific metamodel is required. This will be done by your Stages product consultant. You will receive a Stages v7.2 compatible metamodel file that can be installed to your Stages v7.2 instance. +Update requirements: to upgrade to Stages v7 the following preliminary topics need to be clarified:
-  - __<font 14px/Verdana,Geneva,sans-serif;;inherit;;inherit>**Database:**</font>__  Your Stages V6 data / database needs to be migrated to a Stages v7 compatible format. For this purpose we provide 3 ways of migration:+
  
-  <font 14px/Verdana,Geneva,sans-serif;;inherit;;inherit>**T****he database migration will be done by Method Park:**</font> You send a dump of your database to Method Park and we will send you a migrated database dumpWe will guide you in how to create dump and how to upload large files to Method Park+__**Metamodel**__  : A migration of your customer specific metamodel is required. This will be done by your Stages product consultantYou will receive Stages v7 compatible metamodel file that can be installed to your Stages v7 instance.\\ 
-  <font 14px/Verdana,Geneva,sans-serif;;inherit;;inherit>**Migrate the database on your own:**</font> In order to do this you need to install the latest Version of Stages v6 and perform a [[:7migrate:Database-Cleanup|database cleanup]]. Then we suggest to install a Stages v7.2 testing server and connect this Stages instance to a copy of your Stages 6 database. Please be aware that in case of any error this might be a longer lasting procedure. We strongly suggest to let Method Park migrate your database. +__**Database**__  : Your Stages V6 data database needs to be migrated to a Stages v7 compatible formatFor this purpose we provide two ways of migration:
-  * <font 14px/Verdana,Geneva,sans-serif;;inherit;;inherit>**Start with a plain Stages v7 database:**</font> In this case we will send you a Stages v7.2 starting database dump and you can migrate existing data by Stages ZIP import- and export functionality.+
  
 +**Migrate the full database**
  
-==== Stages v7 program update====+In order to do this you need to install the latest Version of Stages v6 and perform a [[:7migrate:database-cleanup|database cleanup]] (click link for details). If you are using Oracle please refer to this for the latest Oracle requirements. After that we suggest that you install a Stages v7 testing server and connect this Stages instance to a copy of your cleaned Stages 6 database. Please be aware that this step might take several hours depending on the datavolume in the database.\\ 
 +In case of any error (migration stops) please contact the customer care team providing the logfiles.
  
-Stages v6 must be deinstalled and v7 will be installed with database dump, metamodel and license. A dedicated guide is available [[:72:install|here]]. We strongly suggest to install a Stages 7.2 testing server first in order to allow you learn how to avoid possible upgrade errors and estimate the required time for a productive update.+**Start with a plain Stages v7 database**
  
 +In this case we will send you a Stages v7 starting database dump and you can migrate existing data by Stages ZIP import- and export functionality.
  
 ==== How to start your upgrade / How to continue: ==== ==== How to start your upgrade / How to continue: ====
  
-Please tell the [[stages-support@methodpark.com?subject=Stages upgrade V6 to V7|Stages Support Team]] how you would like to migrate the Stages 6 data/database and (if availablethe name of your Stages product consultant. Please also send us your Stages runtime information. We will then continue to guide you through your customer specific upgrade procedure.+Please contact the [[stages-support@ul.com?subject=Stages upgrade V6 to V7|Stages Support Team]] to initiate the migration (if available add the name of your Stages product consultant). Please provide your Stages runtime information of production server. We will then continue to guide you through your customer specific upgrade procedure
 + 
 + 
 +==== Stages v7 program update: ==== 
 + 
 +Stages v6 must be deinstalled and v7 will be installed with database dump, metamodel and license. A dedicated guide is available [[:72:install|here]]. We strongly suggest to install a Stages 7 testing server first in order to allow you to learn how to avoid possible upgrade errors and estimate the required time for a productive update.