Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

 

The 7.10 and 7.11 Java upgrades are so called switched base. This means that during the upgrade procedure the upgrade tool installs from scratch 7.10/7.11 system. We call the new system - shadow system. The shadow systems tables are created in different schema (shadow schema).  The migration controllers migrates data from the source system to the shadow system.

Different types of Migration Controller .

The java upgrade supports the following migration controller types:

  • Database migration controllers
  • Configuration manager migration controllers
  • Delegation migration controllers 
  • Online engine migration controllers
  • Files system migration controllers
  • Data migration controllers

Database migration controllers

These migration controllers migrate data between the DB  tables of the source system and the DB tables of the shadow system. During their execution the DB migration controllers receive as recourses two OpenSQL connections, one to the source DB schema and one to the shadow DB schema. The upgrade starts these migration controllers when the upgrade is in downtime. The shadow and the source engines are stopped.

Configuration manager migration controllers

These migration controllers migrate configuration stored in the Configuration Manager (from the source 6.40/7.00 Configuration manager to the 7.10/7.11 configuration manager). These migration controllers use specific configuration manager API to read configurations from the source Configuration Manager and to store them in the shadow Configuration Manager. The upgrade starts these migration controllers when the upgrade is in downtime. The shadow and the source engines are stopped.

Delegation migration controllers 

these migration controllers migrate configuration stored in the Configuration Manager, but these migration controllers can invoke over Configuration Manager controllers in specific order. They can delegate migration work to other migration controllers.

Default migration controllers

These migration controllers migrate configuration stored in the Configuration Manager. They migrate default configuration. These migration controllers are properties files that are packed in SDA. Every property file describes group of configuration from the source Configuration Manager, which have to be migrated without changes to the shadow Configuration Manager. The upgrade starts these migration controllers when the upgrade is in downtime. The shadow and the source engines are stopped.

Online engine migration controllers

This migration controllers call application deployed on the source or the shadow system, which do some data migration. These migration controllers use InitialContext to call application and can be run when the source or the shadow engine is running.

Files system migration controllers

these migration controllers migrate files from the file system of the source engine to the file system of the shadow engine or modified SDA files deployed on the source system, which the upgrade deploy on the shadow system during deployment phase.

Data migration controllers

These migration controllers don’t receive any specific recourses during their execution. They can be describes as small programs plugged in upgrade procedure and generate some output file, which to be used by upgrade or from other migration controllers.

 

 

 

  • No labels