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

• US 20070011209A1
• Filed: 11/21/2005
• Published: 01/11/2007
• 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
• Granted Patent: US 7,831,636 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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 previous system platform to a new system platform, wherein there is access to the host environment from a decentralised environment, comprising the steps:

providing at least one database of a first type on the previous system platform, wherein the first type of database is not migrated to the new 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 previous system platform, wherein on migration to the new 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 a first type of transaction, which on the previous 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 and not the second type of database and the third type of transaction accesses the second and not the first type of database; and

initiating transactions of the second and third type if a transaction of the first type is requested in the decentralised 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 of taking into operation at least one database of the third type of database which has arisen from the second type of database on the new system platform.

7. The method according to claim 6, comprising the further step of fanning out a requested transaction of the first type onto both platforms into an allocated transaction of the second type on the previous system platform and into an allocated transaction of a fourth type on the new system platform, wherein the fourth type of transaction accesses the third type of database.

8. The method according to claim 7, wherein the step of fanning out takes place in the decentralised environment.

9. The method according to claim 1, comprising the further step of administering at least one database of the second type on the previous system platform and the corresponding database of the third type on the new system platform by respective transactions of the third and fourth type.

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

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

determining whether an allocated transaction of the third type or 35 an allocated transaction of the fourth type is to be conducted for the requested transaction of the first type; and

initiating either a transaction of the third type or a transaction of the fourth type as a function of the result of the determination.

11. The method according to claim 10, 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.

12. 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 new system platform.

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

14. 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.

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

16. The method according to claim 15, wherein the functionalities of the plurality of parallel hosts on the previous system platform are taken on by a single logical host on the new system platform.

17. The method according to claim 14, 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 previous system platform or the allocated transaction of the fourth type on the new system platform as a function of the migration status of the allocated entity.

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

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

20. A computer program product with program code portions for performing the steps of claim 1 when the computer program product is run on one or more computers.

21. The computer program product according to claim 20, stored on a computer-readable data carrier.

22. A transaction control component for configuring a transaction-based host environment for migration from a previous system platform to a new system platform, with access to the host environment from a decentralised environment, comprising a control mechanism which initiates transactions of a second and a third type when a transaction of a first type is requested in the decentralised environment, wherein the first type of transaction accessed both a first type of database and a second type of database on the previous system platform and the second type of transaction accesses the first and not the second type of database and the third type of transaction accesses the second and not the first type of database, and wherein the first type of database and the second type of database have different migration behavior.

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

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