Technique for the migration of a host environment to a new system platform

• US 7,831,636 B2
• Filed: 11/21/2005
• Issued: 11/09/2010
• Est. Priority Date: 07/06/2005
• Status: Active Grant

• Current Assignee: UBS Business Solutions AG (UBS Ag)
• Original Assignee: UBS Ag
• Inventors: Loacker, Hansbeat, Wietlisbach, Markus
• Primary Examiner(s): Wassum; Luke S
• Application Number:
  US11/282,700
• Publication Number:
  US 20070011209A1
• Time in Patent Office: 1,814 Days
• Field of Search: 707/104.1, 707/101, 707/803, 707/809, 707/944, 707/999.101
• US Class Current: 707/803
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: Y10S 707/944 Business related

Abstract

A method for configuring a transaction-based host environment for migration to a new system platform is described. The method comprises the steps of providing at least one database of a first type and at least one database of a second type, which have different migration behaviour, on the previous system platform. Further provided is a first type of transaction which accesses both the first type of database and the second type of database on the previous system platform. For preparing the migration, the first type of transaction is replaced in the host environment by a second type of transaction and a third type of transaction, wherein the second type of transaction accesses only the first type of database and the third type of transaction only the second type of database. The method additionally comprises initiating transactions of the second and third type on request for a transaction of the first type from a decentralised environment.

Claims

1. A method for configuring a transaction-based host environment for the migration from a first system platform to a second system platform, wherein access to the host environment from a decentralised environment is maintained during the migration, comprising the steps:

providing at least one database of a first type on the first system platform, wherein the first type of database is not migrated to the second system platform or is migrated at least one of unchanged in content and with an unchanged logical data model;

providing at least one database of a second type on the first system platform, wherein on migration to the second system platform the second type of database is transformed into a third type of database that is at least one of changed in content and changed in relation to a logical data model;

replacing, during the migration a first type of transaction, which on the first system platform accessed both the first type of database and the second type of database, by a second type of transaction and a third type of transaction in the host environment, wherein the second type of transaction accesses the first type of database and not the second type of database, and the third type of transaction accesses the second type of database and not the first type of database;

receiving a request for a transaction of the first type from the decentralized environment;

in response to receipt of the request during the migration, initiating transactions of the second and third type in the host environment; and

upon completion of the migration of the second type of database to the third type of database the method further comprising the steps of;

replacing the first type of transaction with a first post migration type of transaction and a second post migration type of transaction, wherein the first post migration type of transaction accesses the first type of database and not the second or third types of databases, and the second post migration type of transaction accesses the third type of database and not the first or second types of databases;

in response to receipt of the request after the migration, initiating transactions of the first and second post migrations types in the host environment; and

disabling the second type of database from the host environment.

2. The method according to claim 1, comprising the further step of generating an allocation between a requested transaction of the first type and one each of an initiated transaction of the second and the third type.

3. The method according to claim 2, comprising the further steps:

receiving results of transactions of the second and third type allocated to one another; and

converting the received results into a pre-defined result format of the requested transaction of the first type.

4. The method according to claim 3, comprising the further steps:

requesting the transaction of the first type by a client in the decentralised environment; and

passing the converted result to the requesting client.

5. The method according to claim 3, wherein at least one of the steps of generating the allocation, receiving results and converting the results is performed the decentralised environment.

6. The method according to claim 1, comprising the further-step:

determining a status of the migration.

7. The method according to claim 6, wherein migration of the content of the database of the second type is done tranche by tranche;

and wherein in the step of determining a check is made as to whether the requested transaction of the first type relates to an already migrated tranche.

8. The method according to claim 1, comprising the further step of taking into operation at least one database of a fourth type of database which has arisen from the first type of database on the second system platform.

9. The method according to claim 8, comprising the further step of taking into operation an application accessing the fourth type of database on the second system platform, wherein the application has been obtained by code translation from an application running on the first system platform and there accessing the first type of database.

10. The method according to claim 1, wherein the transactions relate to data sets, allocated in each case to an entity, and migration is conducted entity by entity.

11. The method according to claim 10, comprising the further step of providing a plurality of parallel hosts with similar transaction behavior on the first system platform, wherein a subset of the entities is allocated to each host.

12. The method according to claim 11, wherein the functionalities of the plurality of parallel hosts on the first system platform are taken on by a single logical host on the second system platform.

13. The method according to claim 10, comprising the further steps:

determining the entity allocated to a requested transaction of the first type;

determining the migration status of the allocated entity;

conducting the allocated transaction of the third type on the first system platform or the allocated transaction of a fourth type on the second system platform as a function of the migration status of the allocated entity.

14. The method according to claim 13, wherein the determining steps are conducted in the decentralised environment.

15. The method according to claim 13, wherein the migration status is determined using a table.

16. A transaction control component in a terminal controller in a decentralized computer environment for configuring a transaction-based host environment for migration from a first system platform to a second system platform, with access to the host environment from the decentralised environment, comprising:

a memory for storing computer executable instructions;

a processing unit for accessing the memory and executing computer executable instructions; and

a control mechanism having computer executable instructions stored in memory that when executed, are configured to;

initiate transactions of a second and a third type during the migration in response to receiving a request for a transaction of a first type from the decentralised environment, wherein the first type of transaction accessed both a first type of database and a second type of database on the first system platform and the second type of transaction accesses the first type of database and not the second type of database, and the third type of transaction accesses the second type of database and not the first type of database, and wherein the first type of database and the second type of database have different migration behavior;

upon completion of the migration of the second type of database to a third type of database on the second platform, initiate transactions of a first and second post migration types in response to receiving a request for a transaction of the first type from the decentralised environment, wherein the first post migration type of transaction accesses the first type of database and not the second type of database or the third type of database, and the second type of transaction accesses the third type of database and not the first type of database or the second type of database, and wherein the third type of database corresponds to the second database transformed with at least one of changed content and a changed relation to a logical model; and

disabling the second database from the host environment.

17. A decentralised client system with access to a host environment and containing the transaction control component according to claim 16, wherein access to the host environment is done via the transaction control component.

18. The client system according to claim 17, wherein transactions of the first type are requested by the client system irrespective of the migration status of the host environment.