JP2014013446A - Installation information generation method, installation information generation program and installation information generation device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To generate installation information to be needed when transiting software between different platforms.SOLUTION: A computer to be a transition destination acquires association data representing a correspondence relation of information of a function of software associated with version information of software used in another computer, information of a function of software associated with the version information, and version information of personally used software, selects a function corresponding to information of a function of software associated with the version information of the software used by the another computer among functions of the software associated with the version information of the personally used software on the basis of the acquired association data, and generates installation information for installing a software module for providing the selected function.

Description

  The present invention relates to an installation information generation method, an installation information generation program, and an installation information generation apparatus that generate installation information necessary for transferring software from one computer to another computer.

  A technique for determining the software to be installed by examining the environment of a device for installing software is known (Patent Document 1 and Patent Document 2).

JP 2002-318694 A JP-A-9-212341

  However, the above-mentioned technology does not consider transferring software between different platforms. In one aspect, the present invention is to generate installation information that is required when software is transferred between different platforms.

  In one aspect of the installation information generation method, a computer that migrates software used by another computer to itself is associated with version information of the software used by the other computer and the version information. Information on the function of the software being used, version information on the software used on the other computer, information on the function of the software associated with the version information, and version information on the software used by itself Acquires correspondence data representing the correspondence relationship of the information on the function of the associated software, and based on the acquired correspondence data, from among the software functions associated with the software version information used by itself, Used on the other computer Select the function corresponding to the information of the function of the software associated with the software version information that are to produce the installation information for installing the software module providing the selected said function.

  According to one aspect, it is possible to generate installation information for easily transferring software between different platforms.

1 is a configuration diagram illustrating an example of a computer system according to a first embodiment. It is explanatory drawing which shows an example of the record layout of the provision function data table classified by product. It is explanatory drawing which shows an example of the record layout of a use function conversion table. It is explanatory drawing which shows an example of the record layout of an installation information table. It is explanatory drawing which shows an example of the record layout of a function utilization performance log table. It is explanatory drawing which shows an example of the record layout of a migration source data table. It is explanatory drawing which shows an example of the record layout of a transfer destination platform data table. It is explanatory drawing which shows an example of the record layout of the data table for transfer. It is explanatory drawing which shows an example of arrangement | positioning of each table. It is a flowchart which shows the outline | summary of the process sequence of a system transfer. It is a flowchart which shows the process sequence of the acquisition process of transfer source information. It is a flowchart which shows the process sequence of the acquisition process of transfer destination information. It is a flowchart which shows the process sequence of the data creation process for transfer. It is a flowchart which shows the process sequence of the data creation process for transfer. It is explanatory drawing which shows an example of the result display screen of the data creation process for transfer. It is a block diagram which shows an example of the data preparation apparatus for software transfer. It is a functional block diagram of a data creation device for software migration. It is a block diagram which shows the other example of the data preparation apparatus for software transfer.

Embodiment 1
FIG. 1 is a configuration diagram illustrating an example of a computer system according to the first embodiment. Migration server computer 1 (hereinafter referred to as “migration source server 1”), migration destination server computer 2 (hereinafter referred to as “migration destination server 2”), and public server computer 3 (hereinafter referred to as “public server 3”). And the network N is included. The network N is a LAN (Local Area Network), a WAN (Wide Area Network), or the like.

The migration source server 1 (another computer) is a migration source server that attempts to migrate application software and middleware that are already used to another server, the migration destination server 2 (the computer to be migrated). The migration source server 1 includes a central processing unit (CPU) 11, a random access memory (RAM) 12, a read only memory (ROM) 13, a database 14, an input unit 15, an output unit 16, and a communication unit 17. The CPU 11 is connected to each part of the hardware via a bus. The CPU 11 controls each part of the hardware according to the control program stored in the ROM 13. The RAM 12 is, for example, SRAM (Static RAM), DRAM (Dynamic RAM), flash memory, or the like. The RAM 12 temporarily stores various data generated when the CPU 11 executes the program. The database 14 stores information about the platform of the migration source server 1, information about installed middleware, application software, and the like.
Note that the platform indicates a basic part of a computer such as an OS (Operating System) and hardware, but here, it mainly indicates the OS.

  The input unit 15 is a keyboard, a mouse, a touch panel, or the like, and a user inputs data, commands, and the like. The output unit 16 outputs image data to be displayed on a display device (not shown). The communication unit 17 has a function of communicating with the migration destination server 2, the public server 3, and other computers via the network N.

  The migration destination server 2 is a server that takes over the functions provided by the migration source server 1 in response to migration of application software and middleware used in the migration source server 1. The migration destination server 2 includes a CPU 21, a RAM 22, a ROM 23, a database 24, an input unit 25, an output unit 26, and a communication unit 27. Since the function of each part is the same as that of the migration source server 1, description thereof is omitted.

  The public server 3 stores information about application software and middleware, and plays a role of providing information to other servers. The public server 3 includes a CPU 31, a RAM 32, a ROM 33, a database 34, an input unit 35, an output unit 36, and a communication unit 37. Since the function of each part is the same as that of the migration source server 1, description thereof is omitted.

Next, the data table used in this embodiment will be described. FIG. 2 is an explanatory diagram showing an example of the record layout of the product-specific provided function data table T1. Assume that each product has the provided function data table T1 shown in FIG. The product-specific provision information data table T1 includes two sections, a platform section T1P and a function section T1F. The platform section T1P includes an OS column, an APS VL (Application Server Version Level) column, and an APS Edition column. The OS column stores the OS type, for example, values such as Windows (registered trademark) 32, Linux (registered trademark) 32, and the like. The APS VL column stores the version level of the application server, for example, values such as V1.0, V1.1, V2.0. The APS Edition field stores application server edition information, for example, values such as EE (Enterprise Edition) and SE (Standard Edition). The function section T1F includes a function ID column, a function column, a setting item column, and an attribute column. The function ID column is an ID that represents the function of the product and is unique within the same product. When a function is integrated with other functions by version upgrade, a new number is assigned when the function is divided into a plurality of functions. The function column stores a function name corresponding to the function ID. The setting item column stores the name of the setting item for each function. The attribute column stores information about what value the setting item takes.
In FIG. 2, the correspondence between the platform section T1P and the function section T1F is conceptually indicated by arrows. In the case of realizing the actual data structure, a column for indicating the correspondence relationship may be provided in both the platform section T1P and the function section T1F, and the same ID may be stored in both corresponding records. In addition, a data table may be provided in which pointers pointing to the respective records of the corresponding platform section T1P and function section T1F are set.

FIG. 3 is an explanatory diagram showing an example of the record layout of the used function conversion table T2. The used function conversion table T2 includes an APS VL column, a function ID column, an attribute 1 column, an attribute 2 column, and an attribute 3 column. The APS VL column further includes a From column and a To column. The function ID column further includes a From column and a To column. For each function shown in the above-mentioned provided function data table for each product, the function configuration may differ depending on the version level. Even if they are different, the functions provided in the latest version level may be provided by dividing, integrating, or partially changing the functions provided in the previous version level. The used function conversion table T2 (association data) indicates the correspondence between such functions. In the APS VL column, information of two version levels indicating the correspondence is stored. The From column stores information on the previous version level of the two version levels. The To column stores information on the later version level of the two version levels. In the function ID column, information on two functions indicating the correspondence is stored. The From column stores an ID of a function included in the previous version level among the two functions. The To column stores the ID of the function provided in the later version level among the two functions. By referring to the two columns of the APS VL column and the function ID column, it is possible to indicate the correspondence relationship between the functions provided in different version levels. In the attribute 1 column, the attribute 2 column, and the attribute 3 column, information for specifically indicating the relationship between the two corresponding functions is stored. The attribute field 1 stores a value of “compatible” when the function of the previous version level is not provided as it is, but is provided as a compatible function at the later version level. The attribute 2 column stores a value of “divided” when one function at the previous version level is divided into a plurality of different functions at the later version level. The attribute 3 column stores “no function” when the function of the previous version level is not provided as any function in the later version level. In the attribute 1 column, the attribute 2 column, and the attribute 3 column, values are not entered in two columns at the same time, and a value is stored in any one column, or none of the columns has a value. In the example shown in FIG. 3, it is indicated that the function whose function ID is 1 at version level V1.0 is compatible with the function whose function ID is 7 at version level V2.0. It is shown that the function having the function ID 3 in the version level V1.0 is divided in the version level V2.0, and the functions ID 8 and 9 are obtained. A function whose function ID is 6 in the version level V1.0 indicates that there is no corresponding function in the version level V2.0.
The attribute 1 column, attribute 2 column, and attribute 3 column may be expressed as flags. 1 may be stored in the corresponding column, and 0 may be stored in the other columns. For example, in the case of compatibility, 1 is stored in the attribute 1 column, 0 is stored in each of the attribute 2 column and the attribute 3 column.

  FIG. 4 is an explanatory diagram showing an example of a record layout of the installation information table T3. The installation information table T3 stores information about middleware, application software, and the like installed in the migration source server 1. The installation information table T3 includes a link section T3L, a platform section T3P, and a function section T3F. The link section T3L includes a platform information column and a used function information column. The link section T3L indicates the correspondence between the platform section T3P and the function section T3F. The platform information column stores a pointer to the platform section T3P, and the used function information column stores a pointer to the function section T3F. By storing two points in pairs, the correspondence between the two sections is stored. The platform section T3P includes an OS column, an APS VL column, and an APS Edition column. The OS column stores the OS type, for example, values such as Windows 32 and Linux 32. The APS VL column stores the version level of the application server, for example, values such as V1.0, V1.1, V2.0. The APS Edition field stores edition information of the application server, for example, values such as EE and SE. In the example of FIG. 4, the OS is Windows 32, the version level of the application server is V1.0, and the edition is EE. The function section T3F includes a function ID column, a function column, a setting item column, and an attribute column. The function ID column stores the ID of the installed function. The function column stores the name of the installed function. The setting item column stores the name of the setting item corresponding to the function. The attribute field stores what value is actually set as a setting representing a setting item. In the example of FIG. 4, the installed functions are Java (registered trademark) 1.4 with a function ID of 1, J2EE (Java2 Enterprise Edition) with a function ID of 2, SSO (Single Sign On) with a function ID of 3, The function ID is SOAP (Simple Object Access Protocol), and the function ID is 12 OD (Object Director). The setting items of J2EE include a common resource directory and a port number, and setting values (attributes) are c: ¥ Interstage and 3333, respectively.

  FIG. 5 is an explanatory diagram showing an example of a record layout of the function usage record log table T4. The function usage record log table T4 is a table that stores the use record of the functions installed in the migration source server 1. The function usage record log table T4 includes a function ID column, a function name column, and a final operation date / time column. The function ID column stores an ID of a function installed in the migration source server 1. The function column stores the name of the function corresponding to the function ID. The last operation date / time column stores the date / time information when the function last operated.

  FIG. 6 is an explanatory diagram showing an example of the record layout of the migration source data table T5. The migration source data table T5 stores information about middleware, application software, and the like installed in the migration source server 1, and information about the actual use of these. The migration source data table T5 includes a link section T5L, a platform section T5P, and a function section T5F. The link section T5L includes a platform information column and a used function information column. The link section T5L indicates the correspondence between the platform section T5P and the function section T5F. The platform information column stores a pointer to the platform section T5P, and the used function information column stores a pointer to the function section T5F. By storing the two pointers in pairs, the correspondence between the two sections is stored. The platform section T5P includes an OS column, an APS VL column, and an APS Edition column. The OS column stores the type of OS. The value of the version level of the application server is stored in the APS VL column. The value of edition information of the application server is stored in the APS Edition field. In the example of FIG. 6, the OS is Windows 32, the version level of the application server is V1.0, and the edition is EE. The function section T5F includes a function ID column, a function column, a usage status column, a setting item column, and an attribute column. The function ID column stores the ID of the installed function. The function column stores the name of the installed function. The usage status column stores the usage status of each function. The setting item column stores the name of the setting item corresponding to the function. The attribute field stores what value is actually set as a setting representing a setting item. In the example of FIG. 6, the installed function is Java 1.4 with function ID 1, J2EE with function ID 2, SSO with function ID 3, SOAP with function ID 4, and OD with function ID 6. is there. The setting items of J2EE include a common resource directory and a port number, and setting values (attributes) are c: ¥ Interstage and 3333, respectively. For functions other than the OD whose function ID is 6, the usage status has been proven.

  FIG. 7 is an explanatory diagram showing an example of the record layout of the migration destination platform data table T6. The migration destination platform data table T6 is a table in which information regarding the platform of the migration destination server 2 is stored. The migration destination platform data table T6 includes an OS column. The OS column stores the type of OS.

  FIG. 8 is an explanatory diagram showing an example of the record layout of the migration data table T7. The migration data table T7 stores information about middleware and application software to be installed in the migration destination server 2. The migration data table T7 includes a function ID column, a function column, a setting item column, an attribute column, and a migration unnecessary flag column. The function ID column stores the ID of the function to be installed. The function column stores a function name corresponding to the function ID. As the setting item, the name of the setting item corresponding to each function is stored. The attribute column stores a value specifically set for the setting item. 0 or 1 is stored in the migration unnecessary flag column, and 1 indicates that the migration is not necessary for the migration destination server 2. 0 indicates that migration is necessary. In the example of FIG. 8, the functions to be installed are Java SE5 with ID 7, J2EE with ID 2, SSO (business SV) with ID 8, and SSO (authentication SV) with ID 9. . An OD with an ID of 6 indicates that migration is not necessary. In addition, as setting items of J2EE, it is indicated that the common resource directory should be set to / user / local / Interstage and the XXX port should be set to 5555.

  Next, it will be described whether each table shown in FIGS. 2 to 8 is stored in the migration source server 1, the migration destination server 2, or the public server 3. FIG. 9 is an explanatory diagram showing an example of the arrangement of each table. Only the data table is shown, and other configurations are omitted. The migration source server 1 stores an installation information table T3, a function usage record log table T4, and a migration source data table T5. The migration destination server 2 stores a migration destination platform data table T6 and a migration data table T7. The public server 3 stores a product-specific provided function data table T1 and a used function conversion table T2.

Next, system migration processing will be described. FIG. 10 is a flowchart showing an outline of a processing procedure for system migration. First, the migration source server 1 acquires migration source information (step S1). The migration source information is data about the migration source server 1, that is, data to be stored in the installation information table T3 and the function usage record log table T4. These data are collected and stored in the respective tables. Next, the migration destination server 2 acquires migration destination information (step S2). The migration destination information is information about the migration destination server 2, that is, data to be stored in the migration destination platform data table T6, and is stored in the migration destination platform data table T6. The migration destination server 2 selects a function to be installed in the migration destination server 2 based on the migration source information and the migration destination information (step S3). Upon selection, the product-specific provided function data table T1 and the used function conversion table T2 are referred to. The migration destination server 2 generates migration data from the selected function (step S4). The migration data is data about functions to be installed in the migration destination server 2, and is stored in the migration data table T7. The migration destination server 2 installs necessary functions of middleware and application software by the installer based on the migration data stored in the migration data table T7 (step S5).
In the above description, the transfer destination information is acquired after acquiring the transfer source information. However, these processes are out of order, and the transfer source information may be acquired after acquiring the transfer destination information.

  FIG. 11 is a flowchart showing a processing procedure of migration source information acquisition processing. The process shown in FIG. 11 corresponds to the process of step S1 shown in FIG. It is assumed that the acquisition process of the migration source information illustrated in FIG. The CPU 11 of the migration source server 1 acquires platform information (step S11). The OS type, application server version level, and edition are acquired. The OS type is acquired using a command provided in the OS. Alternatively, it is obtained from a file output by the installer during OS installation. The version level and edition of the application server are the same, and are acquired by the management command provided in the application server. Alternatively, obtain it from the file output by the installer when installing the application server. The CPU 11 acquires function information (step S12). What is acquired is the name of the function, the setting item corresponding to it, and the value (attribute) for that item. The function information is acquired from a file in which the installation result output by the installer when middleware or application software is installed is written. The CPU 11 acquires a function ID corresponding to the acquired function (step S13). Based on the name of the function acquired in step S12, the function ID is acquired by referring to the provided function data table for each product stored in the public server 3. The CPU 11 installs the platform information (OS type, application server version level, edition) acquired in step S11, and the function information (function ID, function name, setting item, attribute) acquired in steps S12 and S13. Store in T3 (step S14).

  The CPU 11 acquires function usage record log information (step S15). The CPU 11 acquires the name of the function installed in the migration source server 1 and its final operation date / time. These pieces of information are acquired from log information output by middleware and application software. The function ID corresponding to the function name is acquired in step S13. The CPU 11 stores the acquired function use result log information (function ID, function name, last operation date and time) in the function use result log table T4 (step S16). Note that software that outputs function usage record log information to the function use record log table T4 each time a function is used may be operated as a background process in the migration source server 1. In this case, it is not necessary to perform the process of step S15 and step S16 anew.

  The CPU 11 generates migration source data based on the platform information, function information, and function usage history log information stored in the installation information table T3 and the function usage history log table T4, and stores them in T5 in the migration source data table (step S17). ). The CPU 11 ends the process. The platform information included in the migration source data is the same as the platform information stored in the installation information table T3. For the function information included in the migration source data, usage status data is added to the used function information stored in the installation information table T3.

  The usage status data is information indicating whether or not each function is actually used in the migration source server 1. Even functions selected when middleware and application software are installed may not be used during operation. In addition, even functions that were used at the start of operation may become unusable due to subsequent changes in operation. A function that is no longer used is stored as no usage data. Whether or not each function is used is determined using the last operation date and time stored in the function usage record log table. When the period from the last operation date and time to the processing time exceeds a preset predetermined period, there is no record. For example, the predetermined period is uniformly 3 months regardless of the function. This period may be shortened to one month or extended to six months according to the user's business operation mode. Moreover, it is good also as setting a different period for every function.

  FIG. 12 is a flowchart showing a processing procedure of migration destination information acquisition processing. The process shown in FIG. 12 corresponds to the process of step S2 shown in FIG. The migration destination information acquisition process shown in FIG. The CPU 21 of the migration destination server 2 acquires the OS type (step S21). The OS type is acquired using a command provided in the OS. Alternatively, it is obtained from a file output by the installer during OS installation. The CPU 21 stores the OS type in the migration destination platform data table T6 (step S22).

  13 and 14 are flowcharts showing the processing procedure of the migration data creation processing. The processes shown in FIGS. 13 and 14 correspond to steps S3 and S4 shown in FIG. It is assumed that the migration data creation process shown in FIGS. 13 and 14 is performed by the migration destination server 2. The CPU 21 of the migration destination server 2 acquires the OS type (step S31). The CPU 21 acquires the OS type from the migration destination platform data table T6. CPU21 acquires APS information (step S32). The CPU 21 stores the information about the APS information corresponding to the OS type acquired in step S32, that is, the version level (APS VL, APS Edition) and edition of the application server corresponding to the OS type, for each product stored in the public server 3. Obtained from the platform information section T1P of the provided function data table T1. The CPU 21 acquires function information corresponding to the OS type (step S33). The CPU 21 acquires the function information, that is, the function ID, the function name, the setting item, and the attribute from the function information section T1F of the provided function data table T1 for each product stored in the public server 3.

  The CPU 21 acquires migration source data from the migration source server 1 (step S34). The CPU 21 acquires platform information T5P and function information T5F of the migration source server 1 stored in the migration source data table T5 of the migration source server 1. The CPU 21 acquires the version level (APS VL) of the application server from the platform information of the migration source server 1 (step S35). The CPU 21 determines whether the migration source server 1 can use the function whose usage status is proven among the functions included in the acquired function information T5F (step S36).

  The determination as to whether or not it can be used is performed using the used function conversion table T2 stored in the public server 3. The CPU 21 extracts the functions in order from the function information T5F of the migration source server 1, and acquires the function ID corresponding to the functions. The CPU 21 searches the used function conversion table T2 to check which of the functions provided in the version level corresponding to the migration destination server 2 the acquired function corresponds to. Specifically, the APS VL From value is the APS VL value of the migration source server 1, the APS VL To value is the APS VL value of the migration destination server 2, and the function ID acquired by the function ID From The CPU 21 searches for records that are. The CPU 21 refers to the values of attribute 1 to attribute 3 of the record hit in the search.

  If any column of attribute 1 to attribute 3 is NULL, it is determined that the function is continued. If attribute 1 is compatible, it is determined that there is an alternative function. If attribute 2 is division, it is determined as division. When attribute 3 has no function, it is determined to be impossible.

  When the CPU 21 determines that the operation is to be continued (continuation in step S36), the function ID written in the To column or From column of the function ID is added to the list (step S37). The list stores function IDs to be installed in the migration destination server 2. If the CPU 21 determines that it is an alternative (substitution in step S36), it adds the function ID written in the To column of the function ID to the list (step S38). If the CPU 21 determines to divide (division in step S36), the function ID written in the To column of the function ID is added to the list for all records that have been searched for hit (step S38). If the CPU 21 determines that it is not possible (not possible in step S36), the process proceeds to step S39.

  Moving to FIG. 14, the CPU 21 refers to the usage record in the migration source server 1 of the function to be processed (step S <b> 39). If there is a track record of use (YES in step S39), the CPU 21 advances the process to step S41. If there is no usage record (NO in step S39), it is stored in the list that the migration unnecessary flag is on (1) (step S40).

The CPU 21 determines whether or not the availability determination has been performed for all the functions of the migration source server 1 acquired in step S34 (step S41). If determination has not been made for all functions (NO in step S41), CPU 21 returns the process to step S36. If all functions have been determined (YES in step S41), the CPU 21 generates migration data based on the created list (step S42). The CPU 21 extracts the function that matches the function ID written in the list from the function information acquired in step S33, and sets the function, setting item, and attribute as data for transfer. If the list indicates that the migration unnecessary flag corresponding to the function ID is on, the migration flag is turned on, that is, 1 is set. Otherwise, it is turned off, that is, 0 is set. Next, the CPU 21 stores the migration data in the migration data table T7. Thus, the CPU 21 completes the migration data creation process.
Note that the attribute of the migration data may be a value obtained from the environment variable of the migration destination server 2 or a predetermined default value.

  The CPU 21 starts the installer with the migration data stored in the migration data table T7 as an input, and installs middleware and application software. This completes the migration. Since the migration data includes setting items and corresponding values (attributes), silent installation is possible. In addition, the CPU 21 performs the installation following the creation of the migration data, but the installation may be performed after the user confirms the migration data.

  Next, the migration data creation process shown in FIG. 13 will be described using a specific example. The OS type of the migration source server 1 is Windows 32, the version level of the application server is V1.0, the functions used are Java 1.4 (ID = 1), J2EE (ID = 2), SSO (ID = 3), SOAP (ID = 4) OD (ID = 12). The OS type of the migration destination server 2 is assumed to be Linux32.

  In step S31 of FIG. 13, the CPU 21 acquires Linux 32 as the OS type. When the product-specific provided function data table T1 shown in FIG. 2 is searched, the version level corresponding to Linux 32 is V2.0 and the edition is SE. In step S32, the CPU 21 acquires V2.0 and SE as APS information. Moreover, Java SE5 (ID = 7), J2EE (ID = 7), SSO (business SV) (ID = 8), etc. are obtained as function information.

  It is assumed that the migration source data obtained by the CPU 21 in S34 is as shown in FIG. The availability determination is made for each function described in the function section T5F in FIG.

  The CPU 21 determines whether or not Java 1.4 with ID = 1 can be used (step S36). The CPU 21 searches the used function conversion table T2 for a record in which the APS VL From is V1.0, To is V2.0, and the Function ID From is 1. One record is hit, the function ID To is 7, and the attribute 1 is compatible. The CPU 21 determines that there is an alternative function (substitute in step S36), and adds the ID value 7 to the list (step S37).

  The CPU 21 checks whether there is a use record for the function having the function ID 1 (step S39). Since Java 1.4 with ID = 1 has a record of use (YES in step S39), the CPU 21 advances the process to step S41. Since the determination for all functions has not been completed (NO in step S41), the CPU 21 returns the process to step S36 and determines the next function (step S36). The next function is J2EE with ID = 2. When the used function conversion table T2 is searched, records whose attribute ID To value is 2 and attributes 1 to 3 are NULL are hit. That is, the same function is provided for J2EE. The CPU 21 determines to continue (continue in step S36), and adds an ID value of 2. It is determined that there is also a usage record.

  Through similar processing, the CPU 21 determines that the SSO with ID = 3 is divided into two functions with ID = 8 and ID = 9. The CPU 21 determines that the SOAP with ID = 4 does not correspond to the migration destination server 2. The CPU 21 determines that the same function is provided for the OD with ID = 6.

  Since the OD with ID = 6 has not been used (NO in step S39), the CPU 21 stores ON in the transition unnecessary flag in the list (step S40).

From the above results, 7, 2, 8, 9, 6 are stored as function IDs in the list, and functions other than the function ID 6 among the functions corresponding to these IDs are installed in the migration destination server 2. It becomes.

  The CPU 21 generates migration data based on the ID stored in the list and the function information acquired in step S33 (step S42). Store in the migration data table T7. The transfer data is as shown in FIG.

  The result of the migration data creation process may be displayed on a screen of a display device or the like. FIG. 15 is an explanatory diagram showing an example of a result display screen of the migration data creation process. FIG. 15A is a display of the result, and FIG. 15B displays a notice regarding the result.

  In the present embodiment, the function of the software to be installed on the migration destination server 2 is selected from the correspondence between the function used by the migration source server 1 and the function available on the migration destination server 2, and based on that Data for migration is created. By using the created migration data (installation information for installing the software module), software migration can be easily performed even if the migration source server 1 and the migration destination server 2 are different platforms.

Embodiment 2
In the first embodiment, the migration data creation process is performed by the migration destination server 2, but the present invention is not limited thereto, and may be performed by other devices such as the migration source server 1 and the public server 3. In the present embodiment, a case will be described in which migration data creation processing is performed by a device other than the migration source server 1, the migration destination server 2, and the public server 3.

  FIG. 16 is a configuration diagram showing an example of the software migration data creation device 4. The software migration data creation device 4 (installation information generation device) includes a CPU 41, a RAM 42, a ROM 43, a database 44, an input unit 45, an output unit 46, and a communication unit 47. The CPU 41 is connected to each part of hardware via a bus. The CPU 41 controls each part of the hardware according to the control program stored in the ROM 43. The RAM 42 is, for example, SRAM, DRAM, flash memory or the like. The RAM 42 temporarily stores various data generated when the CPU 41 executes the program. The database 44 stores various data used when creating the migration data. For example, the provided function data table T1 and the used function conversion table T2 stored in the public server 3 are mirrored in the database 44. In this case, the software migration data creation device 4 can perform migration data creation processing even when the network N is faulty or the public server 3 is stopped for maintenance. In addition, if the installation information table T3 and the function usage record log table T4 of the operating server are stored in the database 44, software migration data creation is possible regardless of which operating server is the migration source server. The device 4 can quickly create the data for migration.

  The input unit 45 is a keyboard, mouse, touch panel, or the like, and the user inputs data, commands, and the like. The output unit 46 outputs image data to be displayed on a display device (not shown). The communication unit 47 has a function of communicating with the migration source server 1, the migration destination server 2, the public server 3, and other computers via the network N.

  The processing performed by the software migration data creation device 4 is the same as the processing shown in the flowcharts of FIGS. Using the migration data created by the software migration data device 4, middleware and application software are installed on the migration destination server 2. Thereby, it is possible to perform software migration from the migration source server 1 to the migration destination server 2.

  FIG. 17 is a functional block diagram of the software migration data creation device 4. When the CPU 41 executes a control program or the like, the software migration data creation device 4 operates as follows. The first obtaining unit 41a obtains version information of software used in one computer and information on software functions associated with the version information. The second acquisition unit 41b acquires version information of software used on the other computer. The third acquisition unit 41c associates the version information of the software used in the one computer, the function information of the software associated with the version information, and the version information of the software used in the other computer The association data representing the correspondence relationship of the function information of the software being acquired is acquired. Based on the acquired association data, the selection unit 41d selects the software version information used in the one computer from the software functions associated with the software version information used in the other computer. Select the function corresponding to the function information of the associated software. The generation unit 41e generates installation information for installing a software module that provides the function of the software selected by the selection unit 41d.

  FIG. 18 is a configuration diagram showing another example of the software migration data creation device 4. Components that are the same as those in FIG. 16 are given the same reference numerals, and descriptions thereof are omitted. The software migration data creation device 4 shown in FIG. 18 reads a program for executing the various software processes described above from the portable recording medium 4A by the reading unit 48, from the semiconductor memory 4B, or via a communication network. Download from another server computer (not shown). The program is installed as a control program, loaded into the RAM 42 and executed. Thereby, it functions as the software migration data creation device 4 described above. The software migration data creation device 4 shown in FIGS. 17 and 18 may be realized by the migration source server 1, the migration destination server 2, and the public server 3.

  Further, the above-described embodiment is an example in all respects, and should be considered not restrictive. The scope of the present invention is defined by the terms of the claims, rather than the meanings described above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims.

  Regarding the above embodiment, the following additional notes are disclosed.

(Appendix 1)
A computer that migrates software used on another computer to itself
Obtaining the version information of the software used in the other computer and the function information of the software associated with the version information;
Correspondence between software version information used in the other computer, software function information associated with the version information, and software function information associated with the software version information used by itself Get the matching data that represents the relationship,
Of the software functions associated with the version information of the software used by itself based on the acquired association data, the software associated with the version information of the software used in the other computer Select the function corresponding to the function information,
An installation information generation method for generating installation information for installing a software module that provides the selected function.

(Appendix 2)
The method according to claim 1, wherein the other computer and the migrating computer are different platforms.

(Appendix 3)
The installation information includes a variable to be set by the user at the time of installation and a setting value for the variable,
The computer to be migrated is
The method according to appendix 1 or appendix 2, wherein the software module is silently installed.

(Appendix 4)
Obtaining information on the function of the software associated with the version information of the software used on the other computer and the date and time when the function was last used;
Information indicating that the software module providing the software function associated with the version information of the software used in the other computer corresponding to the function whose last use date has passed for a predetermined period of time does not need to be installed in the computer to be migrated, The method according to any one of appendix 1 to appendix 3, which is included in the installation information.

(Appendix 5)
A computer that performs processing for transferring software used on one computer to the other computer,
Obtaining the version information of the software used in the one computer and the function information of the software associated with the version information;
Obtaining software version information for use on the other computer;
Software version information used in the one computer, software function information associated with the version information, and software function information associated with the software version information used in the other computer Get correspondence data that represents the correspondence of information,
Software associated with the version information of the software used in the one computer out of the software functions associated with the version information of the software used in the other computer based on the acquired association data Select the function corresponding to the function information of
An installation information generation method for generating installation information for installing a software module that provides a function of the selected software.

(Appendix 6)
The method according to appendix 5, wherein one computer and the other computer are different platforms.

(Appendix 7)
The installation information includes a variable to be set by the user at the time of installation and a setting value for the variable,
The other computer is
The method according to appendix 5 or appendix 6, wherein the software module is silently installed.

(Appendix 8)
Obtaining information on the function of the software associated with the version information of the software used on the one computer and the date and time when the function was last used;
Information indicating that the software module providing the function of the software associated with the version information of the software used on the other computer corresponding to the function whose last use date has passed for a predetermined period does not need to be installed on the other computer, The method according to any one of appendix 5 to appendix 7, which is included in the installation information.

(Appendix 9)
Obtain the version information of the software used on one computer and the function information of the software associated with the version information,
Get the version information of the software used on the other computer,
Software version information used in the one computer, software function information associated with the version information, and software function information associated with the software version information used in the other computer Get correspondence data that represents the correspondence of information,
Software associated with the version information of the software used in the one computer out of the software functions associated with the version information of the software used in the other computer based on the acquired association data Select the function corresponding to the function information of
An installation information generation program that causes a computer to execute processing for generating installation information for installing a software module that provides a function of selected software.

(Appendix 10)
A first acquisition unit that acquires software version information used in one computer and software function information associated with the version information;
A second acquisition unit that acquires version information of software used in the other computer;
Software version information used in the one computer, software function information associated with the version information, and software function information associated with the software version information used in the other computer A third acquisition unit for acquiring association data representing a correspondence relationship of information;
Software associated with the version information of the software used in the one computer out of the software functions associated with the version information of the software used in the other computer based on the acquired association data A selection unit for selecting a function corresponding to the function information of
An installation information generation apparatus including a generation unit that generates installation information for installing a software module that provides a function of software selected by the selection unit.

1 Migration source server 11 CPU
12 RAM
13 ROM
14 database 15 input unit 16 output unit 17 communication unit 2 destination server 21 CPU
22 RAM
23 ROM
24 database 25 input unit 26 output unit 27 communication unit 3 public server 31 CPU
32 RAM
33 ROM
34 Database 35 Input Unit 36 Output Unit 37 Communication Unit 4 Software Migration Data Creation Device 41 CPU
41a First acquisition unit 41b Second acquisition unit 41c Third acquisition unit 41d Selection unit 41e Generation unit 42 RAM
43 ROM
44 database 45 input unit 46 output unit 47 communication unit 48 reading unit 4A portable recording medium 4B semiconductor memory N network

Claims (6)

A computer that migrates software used on another computer to itself
Obtaining the version information of the software used in the other computer and the function information of the software associated with the version information;
Correspondence between software version information used in the other computer, software function information associated with the version information, and software function information associated with the software version information used by itself Get the matching data that represents the relationship,
Of the software functions associated with the version information of the software used by itself based on the acquired association data, the software associated with the version information of the software used in the other computer Select the function corresponding to the function information,
An installation information generation method for generating installation information for installing a software module that provides the selected function. The method according to claim 1, wherein the other computer and the migrating computer are different platforms. The installation information includes a variable to be set by the user at the time of installation and a setting value for the variable,
The computer to be migrated is
The method according to claim 1, wherein the software module is silently installed. A computer that performs processing for transferring software used on one computer to the other computer,
Obtaining the version information of the software used in the one computer and the function information of the software associated with the version information;
Obtaining software version information for use on the other computer;
Software version information used in the one computer, software function information associated with the version information, and software function information associated with the software version information used in the other computer Get correspondence data that represents the correspondence of information,
Software associated with the version information of the software used in the one computer out of the software functions associated with the version information of the software used in the other computer based on the acquired association data Select the function corresponding to the function information of
An installation information generation method for generating installation information for installing a software module that provides a function of the selected software. Obtain the version information of the software used on one computer and the function information of the software associated with the version information,
Get the version information of the software used on the other computer,
Software version information used in the one computer, software function information associated with the version information, and software function information associated with the software version information used in the other computer Get correspondence data that represents the correspondence of information,
Software associated with the version information of the software used in the one computer out of the software functions associated with the version information of the software used in the other computer based on the acquired association data Select the function corresponding to the function information of
An installation information generation program that causes a computer to execute processing for generating installation information for installing a software module that provides a function of selected software. A first acquisition unit that acquires software version information used in one computer and software function information associated with the version information;
A second acquisition unit that acquires version information of software used in the other computer;
Software version information used in the one computer, software function information associated with the version information, and software function information associated with the software version information used in the other computer A third acquisition unit for acquiring association data representing a correspondence relationship of information;
Software associated with the version information of the software used in the one computer out of the software functions associated with the version information of the software used in the other computer based on the acquired association data A selection unit for selecting a function corresponding to the function information of
An installation information generation apparatus including a generation unit that generates installation information for installing a software module that provides a function of software selected by the selection unit.

Images