Progressive migration

Updating, in Pacbase, instances that have already been migrated is not advised. However, in some cases, you must keep on working in Pacbase. You will then have to migrate your modifications.

Before you begin

You must comply with the following use conditions:
  • You are strongly advised against working simultaneously on the same instances in Pacbase and Rational® Programming Patterns because these updates create conflicts.
  • In a multi-session migration, to migrate the updates on a Pacbase session that has already been migrated, you must target the corresponding Rational Team Concert™ stream, which was created by the duplication of the migration stream.
  • The use of the progressive migration must be as time-limited as possible to avoid complex update conflicts. During this time, if several streams (development stream and production stream for example) are each updated from a specific Pacbase session, you can manually carry over the updates to the streams but you must not promote these streams.

Procedure

  1. Complete the initial migration of the Pacbase repository, as it is explained in Extracting and migrating Pacbase data.
  2. Complete the necessary updates in Pacbase.
  3. Extract the updates with the MIBJ procedure. This procedure produces the following elements:
    • The journal transactions since the previous migration,
    • The list of the Macros to be generated with the MIMA procedure,
    • The input to the MIA1MIA2, MIA3, and MIA4 procedures.

    Run the MIMA procedure, and, depending on the databases, the MIA2, MIA3, and MIA4 procedures.

  4. Transfer the files to the workstation where the client parts of Rational Programming Patterns and of the required products are installed. You must transfer the files that are produced from the various procedures to the same directory.
    Warning: The .ta2 file that receives the journal transactions since the previous migration must not be named MIBR.ta2. For example, you can name it MIBJ.ta2 to differentiate it from the result of an initial migration.
  5. Run the automatic migration command: rpp --automaticMigration.

    This command creates the command file that is used to import the journal transactions, dispatch the Macros, and run the migration help.

    The rpp --importJournal command is automatically run instead of the rpp --import command because the import directory does not contain any MIBR.ta2 file.

  6. Run the resulting command file on the workspace that was used for the initial migration.

    The local workspace is then updated.


Feedback