JP2009140428A - Data transfer program, data transfer method and data transfer device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To perform data transfer among systems, without having to stop the systems. <P>SOLUTION: A processing request means 1b transmits a processing request A to a transfer destination data processing system 2. When data that is a processing object is absent in the transfer destination data processing system 2, a data request means 1c requests a transfer source data processing system 3 to provide the data. When the data is present in the transfer source data processing system 3, the data request means 1c acquires and outputs the data to a registration request means 1d. When the data is absent, a reprocessing request means 1e transmits the processing request A to the transfer destination data processing system 2. The registration request means 1d, when it acquires the data from the data request means 1c, requests the transfer destination data processing system 2 to register the data. When the data is already registered in the transfer destination data processing system 2, the reprocessing request means 1e transmits the processing request A to the transfer destination data processing system 2. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a data migration program, a data migration method, and a data migration device, and more particularly to a data migration program, a data migration method, and a data migration device that migrate data between systems.

  In recent years, SOA (Service Oriented Architecture) has become widespread as a form of computer data processing system. The SOA type data processing system is a loosely coupled distributed processing system that realizes a series of data processing by dynamically linking a plurality of services. By using the SOA type data processing system, it is possible to flexibly add, change, and delete services as constituent elements. Because of these advantages, SOA is being adopted in systems that require high reliability, such as enterprise mission-critical systems.

  By the way, in a data processing system that requires extremely high reliability, it is desired that the entire system be continuously operated for 24 hours and 365 days even during maintenance work such as migration from the old system to the new system. For example, in a core business system of a financial institution, there is a request that it is possible to move these data from an old database to a new database while operating a service for searching and updating customer account data and transaction record data.

In response to such a request, a system is known in which an old database and a new database are simultaneously operated, and data is sequentially transferred from the old database to the new database in response to the occurrence of an access request (for example, Patent Documents). 1). In this system, when there is an access request, the new database is first searched for the presence or absence of target data. If the target data does not exist in the new database, the target data is migrated from the old database to the new database.
JP 05-324420 A

  However, the data migration method described in Patent Document 1 has a problem that it does not consider access competition when a plurality of data processing requests targeting the same data are input. For example, in an SOA type data processing system, when a plurality of data processing requests are input, a plurality of processes are executed in parallel corresponding to the data processing requests.

  At this time, (1) the first process accesses the new system and determines that the target data has not been migrated, (2) the second process accesses the new system and determines that the symmetric data has not been migrated, ( 3) When two processes are executed in the order of the first process transferring the target data from the old system to the new system, and (4) the second process trying to transfer the target data from the old system to the new system. Can be considered. In this case, the second process determines that the target data does not exist in both the new and old systems as a result of the processes (2) and (4), and an error occurs. Such data processing failure due to access contention is a serious problem in a system that requires high reliability.

  The present invention has been made in view of such points, and when data migration is performed from an old system to a new system in response to a data processing request, the data processing can be continued normally even if an access conflict occurs. An object is to provide a data migration program, a data migration method, and a data migration apparatus.

  In order to solve the above problems, a data migration program is provided that causes a computer connected to the migration source data processing system and the migration destination data processing system to execute data migration from the migration source data processing system to the migration destination data processing system. Is done. The data migration program causes the computer to function as a process request unit, a data request unit, a registration request unit, a reprocessing request unit, and a deletion request unit. When receiving the data processing request, the processing request means transmits the data processing request to the migration destination data processing system. When the data requesting unit receives a processing target data non-existence response from the migration destination data processing system in response to the transmission by the processing request unit, the data requesting unit transmits a processing target data acquisition request to the migration source data processing system. The registration request unit transmits the received data registration request to the migration destination data processing system when the processing target data is received from the migration source data processing system in response to the acquisition request from the data request unit. The reprocessing request means receives the response to the acquisition request from the data request means when the non-existence response of the processing target data is received from the migration source data processing system, and when the registration request is transmitted by the registration request means. The transmitted data processing request is retransmitted to the migration destination data processing system. The deletion request means receives the registration completion response from the migration destination data processing system in response to the transmission by the registration request means, and receives the processing result response from the migration destination data processing system in response to the retransmission by the reprocessing request means. Send a request to delete data to be processed to the original data processing system.

  According to the computer that executes such a data migration program, when a data processing request is received, the data processing request is transmitted to the migration destination data processing system by the processing request unit. On the other hand, when the processing target data non-existence response is received from the migration destination data processing system, the data request means transmits a processing target data acquisition request to the migration source data processing system. Here, when the processing target data is received from the migration source data processing system, the registration request means transmits a processing target data registration request to the migration destination data processing system. When a response to the absence of processing target data is received from the migration source data processing system and when a registration request is transmitted to the migration destination data processing system, the data processing request is transferred to the migration destination data processing system by the reprocessing request means. Will be resent to After that, when a registration completion response is received from the migration destination data processing system and a processing result response is received from the migration destination data processing system, the deletion request means sends a deletion request for processing target data to the migration source data processing system. The

  In order to solve the above problems, a data migration method for performing the same processing as that of the computer for executing the data migration program, and a data migration apparatus having the same function as the computer for executing the data migration program are provided. The

  According to the data migration program, the data migration method, and the data migration device, when data migration from the migration source data processing system to the migration destination data processing system is performed in response to a data processing request, even if an access conflict occurs Data processing can be continued.

Hereinafter, embodiments will be described in detail with reference to the drawings. First, an outline of the present embodiment will be described, and then specific contents of the present embodiment will be described.
FIG. 1 is a conceptual diagram of the present embodiment. The computer 1 shown in FIG. 1 enables the migration of data from the migration source data processing system 3 to the migration destination data processing system 2 while the system is operating. Further, the computer 1 relays a request for business processing from the user to the migration destination data processing system 2. The computer 1 includes a system management information storage unit 1a, a processing request unit 1b, a data request unit 1c, a registration request unit 1d, a reprocessing request unit 1e, and a deletion request unit 1f.

  The system management information storage unit 1a stores system management information that defines the locations of computers and services that constitute the migration destination data processing system 2 and the migration source data processing system 3.

  The processing request unit 1b is a service group 2a that operates in the migration destination data processing system 2 to be processed based on the system management information stored in the system management information storage unit 1a when a request for business processing occurs. Request business processing. The business process request is transmitted to the computer 1 from, for example, a terminal of a user who intends to use the service group 2a of the migration destination data processing system 2 or another system that relays the user request.

  In response to the business processing request transmitted by the processing request unit 1b, the data request unit 1c sends the data to the migration source data processing system 3 when there is no data to be processed in the migration destination data processing system 2. Request to provide When the data request unit 1c acquires data corresponding to the request, the data request unit 1c outputs the acquired data to the registration request unit 1d. In addition, when the data requesting unit 1c receives a response from the source data processing system 3 that this data does not exist, the data requesting unit 1c transmits the business process request to the reprocessing request unit 1e again to the destination data processing system 2. Notify you.

  When the registration request unit 1d acquires data from the data request unit 1c, the registration request unit 1d requests the registered data processing system 2 to register the acquired data based on the system management information. The registration request unit 1d receives a registration completion response or a registered response from the migration destination data processing system 2. Then, the registration request unit 1d notifies the reprocessing request unit 1e to transmit the business processing request again to the migration destination data processing system 2.

  When receiving the notification from the data requesting unit 1c or the registration requesting unit 1d, the reprocessing requesting unit 1e requests the migration destination data processing system 2 again for business processing based on the system management information.

  When the registration request unit 1d receives a registration completion response from the migration destination data processing system 2 and receives a processing result response to the rerequest by the reprocessing request unit, the deletion request unit 1f migrates to the migration source data processing system 3 The migration source data processing system 3 is requested to delete the data.

The migration destination data processing system 2 has a service group 2a and data storage means 2b.
The service group 2a is a business service group that executes processing in response to a request from the computer 1 and responds with an execution result. The service group 2a includes the following services. The first service executes a business process in response to a processing request from the processing request unit 1b or the reprocessing request unit 1e, and transmits a processing result response or a data absence response to the processing request unit 1b or the reprocessing request unit 1e. This is a data processing execution service. The second service is a data registration service for registering data in the data storage unit 2b in response to a registration request from the registration request unit 1d.

The data storage unit 2b stores data handled by the service group 2a.
The migration source data processing system 3 includes a service group 3a and data storage means 3b.
The service group 3a is a business service group that executes processing in response to a request from the computer 1 and responds with an execution result. The service group 3a includes the following services. The first service is a data acquisition service that acquires corresponding data from the data storage unit 3b and transmits it to the data request unit 1c in response to a data request from the data request unit 1c. The second service is a data deletion service that deletes corresponding data registered in the data storage unit 3b in response to a data deletion request from the deletion request unit 1f.

The data storage means 3b stores data handled by the service group 3a.
With this configuration, when the computer 1 receives a business process request, a process request is transmitted to a service operating in the migration destination data processing system that is the target of the business process. When a response indicating that there is no data to be processed is received, the migration source data processing system is requested to provide data. When data is acquired by a data provision request, the data is registered in the migration destination data processing system, and when the data provision request is received, a response that the target data does not exist is received from the source data processing system In this case, the processing request is transmitted to the migration destination data processing system again. Furthermore, deletion of data registered in the migration source data processing system is requested based on the response of the processing result to this processing request.

  As a result, when data migration from the migration source data processing system 3 to the migration destination data processing system 2 is performed in response to a data processing request, it is possible to continue data processing normally even if access contention occurs.

Hereinafter, the present embodiment will be described in detail with reference to the drawings.
FIG. 2 is a diagram showing a system configuration of the present embodiment. The data processing system shown in FIG. 2 is an SOA type linkage system controlled by the data migration linkage server 100.

  In the linkage system according to the present embodiment, the data migration linkage server 100, the new system 200, and the old system 300 are connected to each other via the network 10. The terminal devices 21, 22, and 23 are connected to the data migration cooperation server 100 via the network 20.

  The data migration cooperation server 100 executes data migration between the new system 200 and the old system 300. In addition, the data migration cooperation server 100 receives business process requests from the terminal devices 21, 22, 23, identifies a server and a service that execute the business process, and transmits a business process request to the identified service. To do. That is, the server 100 for data migration cooperation can communicate with each other using a common data format, command, etc. when not only cooperation between systems for data migration but also a plurality of services are required to execute business processing. As an intermediary interface.

  The new system 200 includes servers 210a and 210b and a database (DB: DataBase) 220. The servers 210a and 210b provide business services to users. The database 220 is a database system connected to the servers 210a and 210b. The database 220 stores data used for services operating on the servers 210a and 210b. In the example of FIG. 2, the database 210 is shared by the servers 210a and 210b, but a database may be prepared separately for each server.

  The old system 300 includes servers 310a and 310b and a database 320. The servers 310a and 310b are servers in the old environment with respect to the servers 210a and 210b. The database 320 is a database system connected to the servers 310a and 310b. The database 320 stores data used in services that operate on the servers 310a and 310b. The database 320 is an old environment database for the database 220 and stores data that needs to be migrated to the database 220.

Next, the hardware configuration of the data migration cooperation server 100 will be described.
FIG. 3 is a diagram illustrating a hardware configuration of the data migration cooperation server. The entire data transfer cooperation server 100 is controlled by a CPU (Central Processing Unit) 101. A random access memory (RAM) 102, a hard disk drive (HDD) 103, a graphics processing device 104, an input interface 105, and communication interfaces 106 and 107 are connected to the CPU 101 via a bus 108.

  The RAM 102 temporarily stores at least part of an OS (Operating System) program and application programs to be executed by the CPU 101. The RAM 102 stores various data necessary for processing by the CPU 101.

The HDD 103 stores data handled by the OS and application programs on the data migration cooperation server 100.
A monitor 11 is connected to the graphic processing device 104. The graphic processing device 104 displays an image on the screen of the monitor 11 in accordance with a command from the CPU 101. A keyboard 12 and a mouse 13 are connected to the input interface 105. The input interface 105 transmits a signal sent from the keyboard 12 or the mouse 13 to the CPU 101 via the bus 108.

  The communication interface 106 is connected to the network 10. The communication interface 106 transmits / receives data to / from the terminal devices 21, 22, and 23 via the network 10.

  The communication interface 107 is connected to the network 20. The communication interface 107 transmits and receives data to and from the new system 200 and the old system 300 via the network 20.

The terminal devices 21, 22, 23 and the servers 210a, 210b, 310a, 310b can also be realized by the same hardware configuration.
With the hardware configuration as described above, the processing functions of the present embodiment can be realized.

Next, the functional configuration of the data migration cooperation server 100 will be described.
FIG. 4 is a block diagram showing the data migration function of the data migration cooperation server. When the business processing request from the terminal device 21, 22, 23 is generated, the data migration cooperation server 100 receives this data from the old system 300 when there is no data subject to the processing request in the new system 200. Transition to the new system 200. Data migration executed in response to a business process request in this way is referred to as sequential migration in the following description.

  In addition, the data migration cooperation server 100 adds a migration data list, which is a list of migration target data, to migrate data that is not subject to business processing, such as database logs, or data that has a low frequency of processing requests. Based on this, a transition is made without waiting for a processing request. Data migration based on the migration data list in this way is referred to as batch migration in the following description. The batch migration is executed by, for example, a schedule registration by an administrator or an immediate start request.

  The data migration cooperation server 100 includes a system management information storage unit 111, a business process request receiving unit 112, a business process request unit 113, a business data request unit 114, a registration request unit 115, a rework process request unit 116, and a deletion request unit 117. A business process result response unit 118, a migration data list reception unit 119, and a migration data list reading unit 120.

  The system management information storage unit 111 receives the system management information that defines the server and service location of the new system 200 and the old system 300, the list of data to be migrated, and the terminal devices 21, 22, and 23. Store business process requests.

  The business process request accepting unit 112 accepts business process requests transmitted from the terminal devices 21, 22, and 23. Then, a request ID is assigned to the business process request and stored in the system management information storage unit 111. In addition, by generating the progress of processing of each unit as a log for this request ID, it is possible to associate each request with the next process to be executed even when a plurality of requests are received.

  The business process request unit 113 transmits a business process execution request to the new system 200 in response to the received business process request. When the business process request unit 113 receives a response from the new system 200 that there is no data to be processed by the business process, the business process request unit 113 notifies the business data request unit 114 of this response. When the business process request unit 113 receives a business process result response from the new system 200, the business process request unit 113 notifies the business process result response unit 118 of the result.

  In the case of sequential migration, the business data request unit 114 receives a notification from the business process request unit 113 that the data to be processed does not exist in the new system 200. Then, the old system 300 is requested to provide the data to be processed. When the business data request unit 114 receives this data from the old system 300, the business data request unit 114 outputs this data to the registration request unit 115. When the business data request unit 114 receives a response indicating that the data does not exist in the old system 300, the business data request unit 114 notifies the re-business processing request unit 116 to transmit a processing request to the new system 200.

  In the case of batch migration, the business data request unit 114 requests the old system 300 to provide the data specified by the migration data list reading unit 120. When the business data request unit 114 receives this data from the old system 300, the business data request unit 114 outputs this data to the registration request unit 115. When the business data request unit 114 receives a response indicating that the requested data does not exist in the old system 300, the business data request unit 114 refers to the migration data list reading unit 120 for the next data specified in the migration data list. Notify me.

  The registration request unit 115 requests the new system 200 to register the data received from the business data request unit 114 based on the system management information stored in the system management information storage unit 111. The registration request unit 115 receives a registration completion response when data registration is normally completed in the new system 200. When this data already exists in the new system 200, the registration request unit 115 receives a data registration completion response from the new system 200. In the case of sequential migration, the registration request unit 115 notifies the re-operation processing request unit 116 to transmit a processing request to the new system 200.

  Upon receiving the notification from the business data request unit 114 or the registration request unit 115, the re-business process request unit 116 makes a business process request to the new system 200. Upon receiving a business process result response from the new system 200, the re-business process request unit 116 notifies the business process result response unit 118 of this result.

  When the registration request unit 115 receives the registration completion response from the new system 200 and the re-operation processing request unit 116 receives the response of the business processing result, the deletion request unit 117 registers the old system 300 in the new system 200. Request to delete the recorded data. In the case of batch migration, the deletion request unit 117 notifies the migration data list reading unit 120 to refer to the next data specified in the migration data list.

  When the business process result response unit 118 receives a response to the business process request from the business process request unit 113 or the re-business process request unit 116, the business process result response unit 118 returns the business process result to the terminal devices 21, 22, and 23 that are the business process request sources. .

  The migration data list receiving unit 119 receives a migration data list from the terminal devices 21, 22, and 23. Then, the migration data list reception unit 119 stores the migration data list in the system management information storage unit 111.

  The migration data list reading unit 120 reads one migration target data from the migration data list stored in the system management information storage unit 111, and transmits a data request to the old system 300 to the business data request unit 114. Instruct. When the migration data list reading unit 120 receives a response indicating that there is no data instructed from the business data request unit 114, the migration data list reading unit 120 reads the next one in the migration data list and transfers the data to the business data request unit 114. Instruct. When the migration data list reading unit 120 receives a notification from the deletion request unit 117 to refer to the next data, it reads the next one in the migration data list and instructs the business data request unit 114 to migrate the data. To do.

  The new system 200 includes a business service group 211 and a business data storage unit 221. The business service group 211 is a business service group that executes processing in response to a request from the data migration cooperation server 100 and responds to the execution result to the data migration cooperation server 100. The business service group 211 includes the following services. The first service executes a business process in response to a processing request from the business process request unit 113 or the re-business process request unit 116, and sends a processing result response or a data absence response to the business process request unit 113 or the re-business process request. A data processing execution service to be transmitted to the unit 116. The second service is a data registration service that registers data in the business data storage unit 221 in response to a registration request from the registration request unit 115.

The business data storage unit 221 stores data handled by the business service group 211.
The old system 300 includes a business service group 311 and a business data storage unit 321. The business service group 311 is a business service group that executes processing in response to a request from the data migration cooperation server 100 and responds to the execution result to the data migration cooperation server 100. The business service group 311 includes the following services. The first service is a data acquisition service that acquires corresponding data from the business data storage unit 321 and transmits it to the business data request unit 114 in response to a data request from the business data request unit 114. The second service is a data deletion service that deletes corresponding data registered in the business data storage unit 321 in response to a data deletion request from the deletion request unit 117.

The business data storage unit 321 stores data handled by the business service group 311.
Here, the new system 200 is a system in a new environment with respect to the old system 300, and the business service group 211 includes functions of services executed by the business service group 311. In the business data storage unit 221, the data stored in the business data storage unit 321 is migrated by the data migration cooperation server 100.

  When the data formats handled by the new system 200 and the old system 300 are different, the data migration linkage server 100 converts the data into a data format handled by the new system 200 by a data format conversion unit (not shown). Also good.

  FIG. 5 is a diagram illustrating an example of the data structure of the data migration linkage table. The data migration linkage table 111a is stored in the system management information storage unit 111 and is referred to when data is migrated from the old system 300 to the new system 200. In the data migration cooperation table 111a, an item indicating a service name and an item indicating the location of the cooperation destination service (host name, object name) are provided. Information arranged in the horizontal direction of each item is associated with each other to constitute information about one service.

  In the item indicating the service name, the name of the service used in the data migration cooperation server 100 is set. In the item indicating the location (host name) of the cooperation destination service, the identification information of the server that executes the business service corresponding to the service specified in the item indicating the service name is set. Here, in the example of the figure, the server identification information is the host name, but other identification information may be used as long as the information uniquely identifies the server on the network to which the data migration cooperation server 100 belongs. In the item indicating the cooperation destination service location (object name), the object name of the service of the cooperation destination server for the service set in the item indicating the service name is set.

  In the data migration linkage table 111a, for example, the service name is “withdrawal transaction processing request”, the linkage destination service location (host name) is “new server 1”, and the linkage destination service location (object name) is “withdrawal transaction”. Information “data processing object” is set. This indicates that the cooperation destination of the service “withdrawal transaction processing request” in the data migration coordination server 100 is the “withdrawal transaction data processing object” existing in “new server 1”.

  FIG. 6 is a diagram illustrating a data structure example of a business process request. The business process request 112a is transmitted to the data migration cooperation server 100 when the user operates the terminal devices 21, 22, and 23. The business process request 112a includes an item indicating a business process name, an item indicating an account number, and an item indicating an amount. Information arranged in the horizontal direction of each item is associated with each other to form information about one business process request.

  In the item indicating the business process name, the name of the business process requested by the user is set. In the item indicating the account number, the account number of the user is set. In the item indicating the amount, an amount such as deposit or withdrawal is set.

  In the business process request 112a, for example, information that the business process name is “withdrawal”, the account number is “0000005”, and the amount is “5000” is set. This indicates a business processing request for “withdrawing” the amount of “5000” yen from the account number “0000005” of the user.

  FIG. 7 is a diagram illustrating an example of the data structure of the business process request management table. In the business process request management table 111b, a business process request 112a is received by the business process request receiving unit 112, and a request ID is assigned to manage each business process request 112a. The business process request receiving unit 112 stores the business process request management table 111 b in the system management information storage unit 111.

  The business process request management table 111b includes an item indicating a request ID, an item indicating a business process name, an item indicating an account number, and an item indicating an amount. Information arranged in the horizontal direction of each item is associated with each other to form information about one business process request. In the item indicating the request ID, a number for uniquely identifying the business process request is set. For the item indicating the business process name, the item indicating the account number, and the item indicating the amount, the same information as the item having the same name in the business process request 112a is set.

  In the business process request management table 111b, for example, information that the request ID is “100”, the business process name is “withdrawal”, the account number is “0000005”, and the amount is “5000” is set. This indicates that the request ID “100” is assigned to the job processing request represented by the job processing request 112a and managed.

  FIG. 8 is a diagram illustrating an example of the data structure of the data migration log. The data migration log 111c is stored in the system management information storage unit 111, and data is added by the function of each unit of the data migration cooperation server 100. The data migration log 111c includes an item indicating a log ID, an item indicating a request ID, an item indicating a service name, and an item indicating a log content. Information arranged in the horizontal direction of each item is associated with each other to constitute log information related to one service.

  In the item indicating the log ID, a number for uniquely identifying the log is set. In the item indicating the request ID, the same information as the request ID of the business process request management table 111b is set. In the item indicating the service name, the name of the service that output the log is set. In the item indicating the log content, the processing result of the service that output the log is set.

  In the data migration log 111c, for example, information that the log ID is “10010”, the request ID is “100”, the service name is “withdrawal transaction processing request”, and the log content is “no processing target response received” is set. . This indicates that data migration is being executed according to the business process request identified by the request ID “100”. Then, in response to the execution result of the service “withdrawal business process request”, a log when “not-processed response received”, that is, a notification indicating that there is no business process target data in the new system 200 is received. Is shown.

Thus, the next process to be executed can be determined based on the request ID, service name, and log contents.
FIG. 9 is a diagram illustrating an example of the data structure of the migration data list. The migration data list 111d is created by the system administrator in the terminal devices 21, 22, 23, and the like. The migration data list 111d is received by the migration data list reception unit 119. Then, the migration data list reception unit 119 stores the received migration data list 111 d in the system management information storage unit 111.

  The migration data list 111d includes an item indicating an identification ID, an item indicating migration data, an item indicating a migration source server, an item indicating a migration source path, an item indicating a migration destination server, and an item indicating a migration destination path. Yes. Information arranged in the horizontal direction of each item is associated with each other to form information related to one piece of migration data. In the item indicating the identification ID, a number for uniquely identifying the migration data is set. In the item indicating the migration data, information (for example, a file name) for specifying the migration data is set. In the item indicating the migration source server, identification information (for example, host name) of the server that identifies the migration source server is set. In the item indicating the migration source path, a path indicating the location of the migration data in the migration source server is set. In the item indicating the migration destination server, identification information (for example, host name) of the server that identifies the migration destination server is set. In the item indicating the migration destination path, a path for storing migration data in the migration destination server is set.

  In the migration data list 111d, for example, the identification ID is “1”, the migration data is “data A”, the migration source server is “old server 1”, the migration source path is “/ var /”, and the migration destination server is “new”. Information that the server 1 ”and the migration destination path are“ / var / ”is set. This is because the migration data “data A” is set for the migration data identification ID “1”, and “data A” is stored in the path “/ var /” of “old server 1”. , “Migrating to the path“ / var / ”of“ new server 1 ”.

Although FIG. 9 shows an example in which data to be migrated is designated in units of data, a plurality of data related to the business processing may be migrated by designating in units of business processing.
FIG. 10 is a flowchart showing a sequential migration procedure by the data migration cooperation server. In the following, the process illustrated in FIG. 10 will be described in order of step number. The result of each procedure is output to the data migration log 111 c stored in the system management information storage unit 111 by each unit of the data migration cooperation server 100.

  [Step S11] The business process request accepting unit 112 accepts a business process request 112a from the terminal devices 21, 22, and 23. The business process request receiving unit 112 assigns an identification ID to each business process request 112a and stores it in the system management information storage unit 111 as a business process request management table 111b.

  [Step S12] The business process request unit 113 reads a business process request from the system management information storage unit 111 from the business process request management table 111b. The business process request unit 113 makes a process request to the business service group 211 based on the read business process request (this process request is referred to as process request A).

  [Step S13] The business process request unit 113 responds from the business service group 211 whether or not the target data of the process request A exists in the business data storage unit 221 (this data is referred to as data A). Accept. If the data A does not exist, the business process request unit 113 notifies the business data request unit 114 that the data A does not exist, and the process proceeds to step S14. When the data A exists, the business process request unit 113 acquires a process result response from the business service group 211, and the process proceeds to step S21.

[Step S14] The business data request unit 114 requests the business service group 311 to provide the data A based on the notification from the business process request unit 113.
[Step S <b> 15] The business data request unit 114 receives a response from the business service group 311 as to whether data A exists in the business data storage unit 321. If the data A exists, the business data request unit 114 acquires the data A from the business service group 311 and outputs the data A to the registration request unit 115, and the process proceeds to step S16. When the response indicating that the data A does not exist is received, the business data request unit 114 requests the business service group 211 to perform the processing request A again, and the process proceeds to step S18. It is.

  [Step S16] The registration request unit 115 acquires the data A from the business data request unit 114, and requests the business service group 211 to register the data A in the business data storage unit 221.

  [Step S17] The registration request unit 115 receives a response indicating that the data A has already been registered in the business data storage unit 221 from the business service group 211 or has been registered normally. Then, the registration request unit 115 requests the re-operation processing request unit 116 to perform the processing request A to the business service group 211 again.

  [Step S18] The re-operation processing request unit 116 makes a processing request A to the business service group 211 again. The re-business process request unit 116 acquires a process result response from the business service group 211.

  [Step S19] The registration request unit 115 refers to the data migration log 111c stored in the system management information storage unit 111, and receives a data A no response in step S15 or a data A registered response in step S17. It is determined whether or not. If either one is accepted, the process proceeds to step S21. If neither is accepted, the process proceeds to step S20.

[Step S20] The deletion request unit 117 requests the business service group 311 to delete the data A stored in the business data storage unit 321.
[Step S21] The business process result response unit 118 receives the result of the process request A from the business process request unit 113 or the re-work process request unit 116. Then, the business process result response unit 118 transmits the business process result to the terminal devices 21, 22, and 23.

  As described above, the data migration cooperation server 100 acquires this data from the old system 300 when the data to be processed is not registered in the new system 200 in response to the business process request 112a from the user. Then, a request is made to register in the new system 200. At this time, it is determined at each stage of migration whether or not there is target data in the new system 200 or the old system 300, and whether or not the data to be processed has already been registered in the new system 200 by data migration by another business processing request 112a. to decide. If it is determined that the system has already been migrated to the new system 200, a processing request is made to the new system 200 again.

FIG. 11 is a flowchart showing a batch migration procedure performed by the data migration cooperation server. In the following, the process illustrated in FIG. 11 will be described in order of step number.
[Step S31] The migration data list receiving unit 119 receives the migration data list 111d and stores it in the system management information storage unit 111.

[Step S32] The migration data list reading unit 120 reads one data to be migrated from the migration data list 111d stored in the system management information storage unit 111.
[Step S33] The migration data list reading unit 120 notifies the business data request unit 114 to acquire the corresponding data (this data will be referred to as data B). Then, the business data request unit 114 requests the business service group 311 to provide the data B.

  [Step S34] The business data request unit 114 requests the business service group 311 to provide data B. The business data request unit 114 determines whether or not there is data B from the business service group 311. When the response indicating that the data B exists is acquired, the business data request unit 114 acquires the data B from the business service group 311 and outputs the data B to the registration request unit 115, and the process proceeds to step S35. . If a response indicating that data B does not exist is acquired, the process proceeds to step S38.

  [Step S35] The registration request unit 115 acquires data B from the business data request unit 114. The registration request unit 115 requests the business service group 211 to register data B in the business data storage unit 221.

  [Step S <b> 36] The registration request unit 115 determines whether the data B is normally registered in the business data storage unit 221 from the business service group 211. If the data B is normally registered, the process proceeds to step S37. If the data B has already been registered in the business data storage unit 221 by another migration process, the process proceeds to step S38.

[Step S37] The deletion request unit 117 requests the business service group 311 to delete the data B stored in the business data storage unit 321.
[Step S38] The migration data list reading unit 120 refers to the migration data list 111d stored in the system management information storage unit 111, and confirms whether migration has been completed for all data. If not completed, the process proceeds to step S32. If completed, the bulk migration is complete.

  As described above, data that is not a target of business processing or data that is less frequently generated by the business processing request 112a is specified by the migration data list 111d, and sequentially shown in FIG. 10 based on the migration data list 111d. Migration takes place in parallel with the migration. At this time, at each stage of migration, the presence or absence of target data in the new system 200 or the old system 300 is determined, and it is determined whether the data to be processed has already been registered in the new system 200 by data migration by another migration process. . If it is determined that the data has already been transferred to the new system 200, the next data set in the transfer data list 111d is transferred.

  In this way, even when sequential migration and batch migration compete and an exceptional response such as data nonexistence or data registration has occurred, the data migration coordination server 100 responds to each business processing request 112a. Thus, the processing of the new system 200 can be executed again and the processing result can be returned. In addition, when it is confirmed that data has been registered in the new system 200 by another migration process at any timing, the deletion request unit 117 does not request the old system 300 to delete the corresponding data. Delete processing is not executed.

  FIG. 12 is a first schematic diagram showing the sequential transition. The example of FIG. 12 shows a case where a user makes a withdrawal request to the deposit and saving system of a financial institution. Here, in the deposit and saving system, the service name of the service that executes the withdrawal process is referred to as a withdrawal processing service. The data migration cooperation server 100 relays a request from the user to a new withdrawal processing service operating in the new system 200. The data migration cooperation server 100 is also connected to the old withdrawal processing service operating in the old system 300, and controls data migration between the old and new databases. In the following, the process illustrated in FIG. 12 will be described in order of step number.

  [Step ST1] The business process request receiving unit 112 receives a business process request 112a from the terminal devices 21, 22, and 23. In the business process request 112a, a business process name “withdrawal”, a user account number “0000005”, and an amount “5000” are set. The business process request accepting unit 112 assigns a request ID to the business process request 112 a and stores it in the business process request management table 111 b of the system management information storage unit 111.

  [Step ST2] When the business process request unit 113 refers to the business process request management table 111b stored in the system management information storage unit 111 and acquires the request indicated by the business process request 112a, the business process request unit 113 receives the new withdrawal processing service. On the other hand, a withdrawal process for the account number “0000005” is requested. The new withdrawal processing service inquires whether the account number “0000005” exists in the new account table 221a that is a table of the new DB. When it is confirmed that the target account number does not exist, a response to that effect is sent to the business process request unit 113. The business process request unit 113 receives a response from the new withdrawal processing service that there is no account number to be processed, and the business data request unit 114 sends the account number “0000005” to the old withdrawal processing service of the old system 300. Request for data on "." Then, the old withdrawal processing service inquires whether the account number “0000005” exists in the old account table 321a which is a table of the old DB. When the old withdrawal processing service confirms that the corresponding account number exists in the old account table 321a, the old withdrawal process service provides the data to the business data request unit 114. Then, the business data request unit 114 outputs the acquired data to the registration request unit 115.

  [Step ST3] Upon acquiring the data from the business data request unit 114, the registration request unit 115 requests the new withdrawal processing service to register the acquired data in the new account table 221a. Then, the new withdrawal processing service registers the account number “0000005” in the new account table 221a and creates a new account table 221b.

  FIG. 13 is a second schematic diagram showing the sequential transition. The transition of the table information shown in FIG. 13 continues from FIG. In the following, the process illustrated in FIG. 13 will be described in order of step number.

  [Step ST4] The registration request unit 115 receives a response to the effect that the data related to the account number has been registered in the new account table 221b by the new withdrawal processing service. Then, the registration request unit 115 requests the re-business processing request unit 116 again to request a business process for the account number to the new withdrawal processing service. Then, the withdrawal process of “5000” yen is executed by the new withdrawal processing service, and the balance of the account number “0000005” becomes “95000” yen as shown in the new account table 221c.

[Step ST5] The deletion request unit 117 deletes the data of the account number “0000005” registered in the old account table 321a and creates the old account table 321b.
Thus, in the sequential migration, every time the business process request 112a is received, the new system 200 is requested to perform business processes. Then, if there is no data to be processed in the new system 200, the data migration cooperation server 100 acquires the data to be processed from the old system 300 and registers it in the new system 200. To do.

  Next, the parallel execution of the sequential migration and the batch migration described above will be described. First, a case where there is no competition regarding data migration between sequential migration and batch migration will be described. Here, the contention regarding data migration means that sequential migration or sequential migration and batch migration try to migrate the same data almost simultaneously.

  FIG. 14 is a first sequence diagram illustrating a specific example of the flow of processing when sequential migration and batch migration do not conflict. In the data migration cooperation server 100, sequential migration and batch migration are executed. In the following description, in the configuration of the data migration cooperation server 100, a function for controlling sequential migration is referred to as a sequential migration cooperation service, and a function for controlling batch migration is referred to as a batch migration cooperation service. It is assumed that the sequential transfer cooperation service accepts a processing request for data A that is a target of business processing. In the following, the process illustrated in FIG. 14 will be described in order of step number.

[Step S101] The sequential transfer cooperation service transmits a processing request for data A to the business service group 211 of the new system 200.
[Step S102] The business service group 211 sequentially responds that the data A to be processed is not registered in the new system 200 in the migration cooperation service.

[Step S103] The sequential transfer cooperation service transmits a request to provide data A to the business service group 311 of the old system 300.
[Step S104] The business service group 311 acquires the data A stored in the business data storage unit 321 and sequentially transmits the data A to the migration cooperation service.

[Step S105] The sequential transfer cooperation service requests the business service group 211 to register the acquired data A in the new system 200.
[Step S106] The business service group 211 sequentially responds to the migration cooperation service that the registration of the data B has been normally completed.

[Step S <b> 107] The sequential transfer cooperation service transmits a processing request for data A to the business service group 211 of the new system 200 again.
[Step S108] The business service group 211 responds to the sequential transfer cooperation service that the processing related to the data A has been normally completed and the processing result.

[Step S109] The sequential transfer cooperation service transmits a deletion request of data A to the business service group 311 of the old system 300.
[Step S110] The business service group 311 deletes the data A stored in the business data storage unit 321 and sequentially responds to the migration cooperation service that the data has been deleted. When the sequential transfer cooperation service receives this response, it transmits a processing completion response in step S108 to the processing request source.

  [Step S111] The collective migration cooperation service reads data A as a migration target from the migration data list 111d. Then, the batch migration cooperation service transmits a data A provision request to the business service group 311 of the old system 300.

[Step S <b> 112] The business service group 311 transmits a response indicating that the data A does not exist in the business data storage unit 321 to the collective migration cooperation service.
FIG. 15 is a second sequence diagram illustrating a specific example of the flow of processing when sequential migration and batch migration do not conflict. FIG. 15 shows the flow of processing continued from FIG. In the following, the process illustrated in FIG. 15 will be described in order of step number.

  [Step S113] The batch migration cooperation service reads data B from the migration data list 111d as a migration target. Then, the batch migration cooperation service transmits a data B provision request to the business service group 311 of the old system 300.

[Step S114] The business service group 311 acquires the data B stored in the business data storage unit 321 and transmits the data B to the batch transfer cooperation service.
[Step S115] The batch migration cooperation service requests the business service group 211 to register the acquired data B in the new system 200.

[Step S116] The business service group 211 transmits a response to the effect that the registration of the data B has been normally completed to the collective migration cooperation service.
[Step S117] The batch migration cooperation service transmits a data B deletion request to the business service group 311 of the old system 300.

  [Step S118] The business service group 311 deletes the data B stored in the business data storage unit 321 and responds to the collective transfer cooperation service that the data has been deleted. This completes the migration process for the data B by batch migration.

  [Step S119] The sequential transfer cooperation service accepts a processing request for data B. Then, the sequential transfer cooperation service transmits a processing request regarding the data B to the business service group 211 of the new system 200.

  [Step S120] The business service group 211 responds to the sequential transfer cooperation service that the processing related to the data B has been normally completed and the processing result. Upon receiving this response, the sequential transfer cooperation service transmits a process completion response related to data B to the process request source.

  In this way, by performing sequential migration and batch migration at the same time, it is possible to reliably migrate log data that is not subject to processing in business processing requests and data related to business processing requests that occur less frequently. Furthermore, data migration can be performed quickly by executing sequential migration and batch migration at the same time.

Next, a case will be described in which the same data migration process competes between sequential migration and batch migration.
FIG. 16 is a first sequence diagram illustrating a specific example of the flow of processing when sequential migration and batch migration compete. In the following, the process illustrated in FIG. 16 will be described in order of step number.

  [Step S131] The batch migration cooperation service reads data A as a migration target from the migration data list 111d. Then, the batch migration cooperation service transmits a data A provision request to the business service group 311 of the old system 300.

[Step S132] The business service group 311 acquires the data A stored in the business data storage unit 321 and transmits the data A to the batch transfer cooperation service.
[Step S133] The sequential transfer cooperation service accepts a processing request for data A. Then, the sequential transfer cooperation service transmits a processing request regarding data A to the business service group 211 of the new system 200.

[Step S134] The business service group 211 sequentially responds that the data A to be processed is not registered in the new system 200 in the migration cooperation service.
[Step S135] The collective migration cooperation service requests the business service group 211 to register the acquired data A in the new system 200.

[Step S136] The business service group 211 responds to the collective transfer cooperation service that the registration of the data A has been normally completed.
[Step S137] The batch migration cooperation service transmits a data A deletion request to the business service group 311 of the old system 300.

[Step S138] The business service group 311 deletes the data A stored in the business data storage unit 321 and responds to the collective transfer cooperation service that the data has been deleted.
[Step S139] The service for sequential transfer cooperation transmits a request to provide data A to the business service group 311 of the old system 300.

[Step S140] The business service group 311 sequentially responds that the data A is not registered in the migration cooperation service.
[Step S141] The sequential migration cooperation service determines that the data A registered in the old system 300 has already been migrated to the new system 200 by another migration process (here, the batch migration is performed in Step S135). Already migrated). Then, the sequential transfer cooperation service resends the processing request regarding the data A to the business service group 211 of the new system 200.

  [Step S142] The business service group 211 responds to the sequential transfer cooperation service that the processing related to the data A has been normally completed and the processing result. Upon receiving this response, the sequential transfer cooperation service transmits a process completion response related to data A to the process request source.

  As described above, the migration is started by the sequential migration and the data provision request is transmitted to the old system 300. However, even when the target data is deleted from the old system 300 by the batch migration, the business process is interrupted. And can provide services normally.

FIG. 17 is a second sequence diagram illustrating a specific example of the flow of processing when sequential migration and batch migration compete. In the following, the process illustrated in FIG. 17 will be described in order of step number.
[Step S151] The sequential transfer cooperation service accepts a processing request for data A. Then, the sequential transfer cooperation service transmits a processing request regarding data A to the business service group 211 of the new system 200.

  [Step S152] The business service group 211 of the new system 200 sequentially responds that the data A to be processed is not registered in the new system 200 in the migration cooperation service.

  [Step S153] The batch migration cooperation service reads data A as a migration target from the migration data list 111d. Then, the batch migration cooperation service transmits a data A provision request to the business service group 311 of the old system 300.

[Step S154] The business service group 311 acquires the data A stored in the business data storage unit 321 and transmits the data A to the collective migration cooperation service.
[Step S155] The sequential transfer cooperation service transmits a request to provide data A to the business service group 311 of the old system 300.

[Step S156] The business service group 311 acquires the data A stored in the business data storage unit 321 and sequentially transmits the data A to the migration cooperation service.
[Step S157] The batch migration cooperation service requests the business service group 211 to register the acquired data A in the new system 200.

[Step S158] The business service group 211 responds to the collective migration cooperation service that the registration of the data A has been normally completed.
[Step S159] The batch migration cooperation service transmits a data A deletion request to the business service group 311 of the old system 300.

[Step S160] The business service group 311 deletes the data A stored in the business data storage unit 321 and responds to the collective transfer cooperation service that the data has been deleted.
[Step S161] The sequential transfer cooperation service requests the business service group 211 to register the acquired data A in the new system 200.

[Step S162] The business service group 211 sequentially responds that the data A has already been registered in the migration cooperation service.
[Step S163] The sequential migration cooperation service determines that the data A registered in the old system 300 has already been migrated to the new system 200 by another migration process (in this case, the batch migration is performed in Step S157). Already migrated). Then, the sequential transfer cooperation service resends the processing request regarding the data A to the business service group 211 of the new system 200.

  [Step S164] The business service group 211 responds to the sequential transfer cooperation service that the processing related to the data A has been normally completed and the processing result. Upon receiving this response, the sequential transfer cooperation service transmits a process completion response related to data A to the process request source.

  As described above, the migration is started by sequential migration, data is acquired from the old system 300, and the registration request is made to the new system 200. Even when the target data is registered in the new system 200 just before the batch migration, It is possible to respond normally without interrupting business processing.

Next, a case where data migration due to sequential migration competes will be described.
FIG. 18 is a first timing diagram showing a specific example in the case where sequential transitions compete. FIG. 18 shows a case where two processes (sequential migration # 1, 2) of the sequential migration cooperation service are executed at the same time, and migration of the same data competes. In the following, the process illustrated in FIG. 18 will be described in order of step number.

  [Step S171] Sequential migration # 1 transmits a processing request (this processing request will be referred to as processing request A) to the new system 200. Sequential migration # 1 receives a response from the new system 200 that there is no data A to be processed.

[Step S172] Sequential migration # 1 requests data A from the old system 300. Sequential migration # 1 acquires data A from the old system 300.
[Step S173] Sequential migration # 2 sends a processing request A to the new system 200. Sequential migration # 2 receives a response from the new system 200 that there is no data A to be processed.

[Step S174] Sequential migration # 1 requests the new system 200 to register data A. Sequential migration # 1 receives a normal end response of registration of data A from the new system 200.
[Step S175] The sequential migration # 1 retransmits the processing request A to the new system 200. The sequential migration # 1 receives a processing result response from the new system 200.

  [Step S176] Sequential migration # 1 requests the old system 300 to delete data A. The sequential migration # 1 receives a response indicating that the deletion of the data A is completed from the old system 300.

[Step S177] Sequential migration # 2 requests data A from the old system 300. The sequential migration # 2 receives a response indicating that the data A does not exist from the old system 300.
[Step S178] The sequential transition # 2 retransmits the processing request A to the new system 200. The sequential migration # 2 receives a processing result response from the new system 200.

  As described above, when the sequential migration # 2 requests data from the old system 300, even if the corresponding data has already been deleted by the sequential migration # 1, the sequential migration # 2 again sends a processing request to the new system 200. By sending it, the processing request can be completed normally.

  FIG. 19 is a second timing diagram illustrating a specific example in the case where sequential transitions compete. FIG. 19 shows a case where two processes (sequential migration # 1 and # 2) of the sequential migration cooperation service are executed at the same time and the migration of the same data competes. In the following, the process illustrated in FIG. 19 will be described in order of step number.

  [Step S181] Sequential migration # 1 transmits a processing request (this processing request will be referred to as processing request A) to the new system 200. Sequential migration # 1 receives a response from the new system 200 that there is no data A to be processed.

  [Step S182] The sequential migration # 2 transmits a processing request A to the new system 200. Sequential migration # 2 receives a response from the new system 200 that there is no data A to be processed.

[Step S183] Sequential migration # 1 requests data A from the old system 300. Sequential migration # 1 acquires data A from the old system 300.
[Step S184] Sequential migration # 2 requests data A from the old system 300. In the sequential migration # 2, data A is acquired from the old system 300.

[Step S185] Sequential migration # 1 requests the new system 200 to register data A. Sequential migration # 1 receives a normal end response of registration of data A from the new system 200.
[Step S186] Sequential migration # 2 requests the new system 200 to register data A. Sequential migration # 2 receives a response from the new system 200 that data A has already been registered.

[Step S187] The sequential migration # 1 retransmits the processing request A to the new system 200. The sequential migration # 1 receives a processing result response from the new system 200.
[Step S188] Sequential migration # 1 requests the old system 300 to delete data A. The sequential migration # 1 receives a response indicating that the deletion of the data A is completed from the old system 300.

[Step S189] The sequential migration # 2 retransmits the processing request A to the new system 200. The sequential migration # 2 receives a processing result response from the new system 200.
As described above, when the sequential migration # 2 requests the new system 200 to register data, even if the corresponding data has already been registered by the sequential migration # 1, the sequential migration # 2 requests the processing again. By transmitting to the new system 200, the processing request can be completed normally.

  As described above, the data migration cooperation server 100 quickly executes data migration from the old system 300 to the new system 200 by sequential migration and batch migration. Even when access to the same data conflicts due to sequential migration or batch migration, the data migration can be executed normally and a processing response can be made without interrupting the business process.

  As described above, the data migration program, the data migration method, and the data migration apparatus have been described based on the illustrated embodiments. However, the present invention is not limited to these, and the configuration of each unit is an arbitrary configuration having the same function. Can be replaced. Moreover, other arbitrary structures and processes may be added to these. These may be a combination of any two or more configurations (features) of the above-described embodiments.

  The above processing functions can be realized by a computer. In that case, a program describing the processing contents of the functions that the data migration cooperation server 100 should have is provided. By executing the program on a computer, the above processing functions are realized on the computer.

  The program describing the processing contents can be recorded on a computer-readable recording medium. Examples of the computer-readable recording medium include a magnetic recording device, an optical disk, a magneto-optical recording medium, and a semiconductor memory. Examples of the magnetic recording device include an HDD, a flexible disk (FD), and a magnetic tape (MT). Optical discs include DVD (Digital Versatile Disc), DVD-RAM, CD-ROM (Compact Disc-Read Only Memory), CD-R (Recordable) / RW (ReWritable), and the like. Magneto-optical recording media include MO (Magneto-Optical disk).

  When the program is distributed, for example, a portable recording medium such as a DVD or CD-ROM in which the program is recorded is sold. It is also possible to store the program in a server computer and transfer the program from the server computer to another computer via a network.

  The computer that executes the program stores, for example, the program recorded on the portable recording medium or the program transferred from the server computer in its own storage device. Then, the computer reads the program from its own storage device and executes processing according to the program. The computer can also read the program directly from the portable recording medium and execute processing according to the program. In addition, each time the program is transferred from the server computer, the computer can sequentially execute processing according to the received program.

It is a conceptual diagram of this Embodiment. It is a figure which shows the system configuration | structure of this Embodiment. It is a figure which shows the hardware constitutions of the server for data migration cooperation. It is a block diagram which shows the data migration function of the server for data migration cooperation. It is a figure which shows the example of a data structure of the table for data migration cooperation. It is a figure which shows the example of a data structure of a business process request. It is a figure which shows the example of a data structure of a business process request management table. It is a figure which shows the data structure example of a data migration log. It is a figure which shows the data structure example of a transfer data list. It is a flowchart which shows the procedure of the sequential transfer by the server for data transfer cooperation. It is a flowchart which shows the procedure of the batch transfer by the server for data transfer cooperation. It is a 1st schematic diagram showing sequential transfer. It is a 2nd schematic diagram showing sequential transfer. It is a 1st sequence diagram which shows the specific example of the flow of a process when sequential transfer and batch transfer do not compete. It is a 2nd sequence diagram which shows the specific example of the flow of a process when sequential transfer and batch transfer do not compete. It is a 1st sequence diagram which shows the specific example of the flow of a process when sequential transfer and batch transfer compete. It is a 2nd sequence diagram which shows the specific example of the flow of a process when sequential transfer and batch transfer compete. FIG. 11 is a first timing diagram illustrating a specific example when sequential transitions compete. FIG. 10 is a second timing diagram illustrating a specific example in the case where sequential transitions compete.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Computer 1a System management information storage means 1b Processing request means 1c Data request means 1d Registration request means 1e Reprocessing request means 1f Deletion request procedure 2 Migration destination data processing system 2a Service group 2b Data storage means 3 Migration source data processing system 3a service Group 3b Data storage means

Claims (3)

A computer connected to the migration source data processing system and the migration destination data processing system,
Processing request means for receiving the data processing request and transmitting the data processing request to the migration destination data processing system;
A data requesting means for transmitting an acquisition request for the processing target data to the source data processing system upon receiving a non-existence response of the processing target data from the migration destination data processing system in response to the transmission by the processing requesting means;
Registration request means for transmitting the received data registration request to the migration destination data processing system when the processing target data is received from the migration source data processing system in response to the acquisition request by the data request means;
In response to an acquisition request from the data requesting means, when a response to the absence of the processing target data is received from the migration source data processing system, and when a registration request is sent by the registration requesting means, the processing requesting means sends Reprocessing request means for retransmitting the data processing request to the migration destination data processing system;
When the registration completion response is received from the migration destination data processing system in response to the transmission by the registration request unit, and the processing result response is received from the migration destination data processing system in response to the retransmission by the reprocessing request unit, the migration A deletion request means for transmitting a deletion request for the processing target data to the original data processing system;
Data migration program characterized by functioning as A computer connected to the source data processing system and the destination data processing system
Upon receiving a data processing request, a processing request step for transmitting the data processing request to the migration destination data processing system;
A data requesting step of transmitting an acquisition request for the processing target data to the source data processing system upon receiving a non-existence response of the processing target data from the migration destination data processing system in response to the transmission by the processing request step;
A registration request step for transmitting a registration request for the received data to the migration destination data processing system when the processing target data is received from the migration source data processing system in response to the acquisition request by the data request step;
In response to the acquisition request in the data request step, when the non-existence response of the processing target data is received from the migration source data processing system, and when the registration request is transmitted in the registration request step, the processing request step transmits A reprocessing request step for re-sending the data processing request to the migration destination data processing system;
When the registration completion response is received from the migration destination data processing system in response to the transmission by the registration request step and the processing result response is received from the migration destination data processing system in response to the retransmission by the reprocessing request step, the migration A deletion request step for transmitting a deletion request for the processing target data to the original data processing system;
The data migration method characterized by performing. A data migration device connected to the migration source data processing system and the migration destination data processing system,
Upon receiving a data processing request, processing request means for transmitting the data processing request to the migration destination data processing system;
A data requesting means for sending an acquisition request for the processing target data to the source data processing system upon receiving a non-existence response of the processing target data from the migration destination data processing system in response to the transmission by the processing requesting means;
A registration request means for transmitting a registration request for the received data to the migration destination data processing system when the processing target data is received from the migration source data processing system in response to an acquisition request by the data request means;
In response to an acquisition request from the data requesting means, when a response to the absence of the processing target data is received from the migration source data processing system, and when a registration request is sent by the registration requesting means, the processing requesting means sends Reprocessing request means for retransmitting the data processing request to the migration destination data processing system;
When the registration completion response is received from the migration destination data processing system in response to the transmission by the registration request unit, and the processing result response is received from the migration destination data processing system in response to the retransmission by the reprocessing request unit, the migration A deletion request means for transmitting a deletion request for the processing target data to the original data processing system;
A data migration apparatus comprising:

Images