Usage > Migrations > Migration process 

This function makes it possible to describe and schedule the different unit operations (named hereafter "procedures") relating to the optimized migration process implemented in the SAFE platform, from version 6.4. A standard migration process is supplied from version 6.4.

Each record created in this table represents a unit migration process. The scheduling rules of these processes are described in a dedicated appendix.

Here, it is possible to add specific migration procedures, or to change (with restrictions) some scheduling rules.

It is recommended, however, to be careful while changing the standard content of the table, for several reasons:

  • this table is common to all the folders, its modification will impact all the folders to migrate.
  • the careless modification of this table can lead to the migration procedure resulting incomplete or, worse, inoperative.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

The screen makes it possible to describe the various procedures which are assigned to a stage, a phase, a module and a rank. The standard procedures are identified by a checkbox. The information provided in the lower part of the screen is purely informative. It makes it possible to know, for documentary purposes, which tables in the data base are impacted by the migration procedure.

Entry screen

Fields

The following fields are present on this tab :

Identification

  • Code (field CODE)

This code identifies the created records in a unique manner.

  • field AINTIT

 

  • Active (field ACTIF)

This checkbox is used to activate or deactivate the migration procedure.

A deactivated procedure will not be used during the migration processing.

  • Standard (field STANDARD)

When this box is checked, the procedure is a standard procedure: it is impossible to change the stage, the phase, the module.
By contrast, the rank can be changed.

Running order

  • Step (field RANGMOD)

The stage is the highest scheduling level of migration procedures. The stages are named via a local menu. These are the following:

  • Currently, the initializing stage is not used in standard operations but it makes it possible to trigger various preliminary control procedures and processings.
  • the common stage is carried out afterwards. It is supposed to process all the tables common to several modules, for which migration is a prerequisite to any other module data procedure.
  • the module stage makes it possible to launch the functional migration procedures (in the order of the stages, then the modules). A module is linked to each of this stage procedure.
  • the post-migration stage is a mandatory stage to have the migrated folder operate normally, but whose procedures can be deferred with resulting limitations upon using the migrated folder. To define such stages and defer their launching during migration makes it possible for users to restart operations as fast as possible in a degraded mode, and to finish migrating later, for instance in the next inactivity period, so as to recover the overall functionalities of the migrated software.

  • Phase (field PHASE)

The phase is a number likely to vary from 1 to 9. It enables the strict scheduling of the migration procedures. The next phases cannot be launched as long as all the procedures of a phase are not completed.
The phase cannot be modified for a standard procedure.

  • Module (field MODULE)

[object Object]

  • Sequence (field RANG)

The rank represents a number likely to vary from 1 to 99. It provides a preferential order to launch a migration procedure in a phase and for a given module. This rank can be modified for the standard procedures.

  • Global index (field INDICEM)

This field, only displayed, is a global index calculated according to the stage, the phase, the module and the rank (in this order). This index defines the order in which the migration procedures are launched, knowing that parallezation is only possible on procedures located in the same stage and in the same phase, and that, in addition, launching a phase in a stage is impossible unless the preceding phases and stages have all been correctly completed.

Description

  • field ADESCRIP

 

  • field ADESCRIP1

 

  • field ADESCRIP2

 

Informative data

The table described herein is the main table migrated by the procedure.
This information is indicative and supplied for documentation purposes.

Grid

The tables described in this list are annex tables implemented by the migration procedure. This is an indicative list supplied for documentation purposes.

  • Update (field TABTYP)

When this box is checked, the corresponding annex table is supposed to be updated by the migration procedure. This information is indicative and supplied for documentation purposes.

Close

 

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation