JP2006091960A - Program update system and program update method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a program update process system for automatically updating a program at a source-code level. <P>SOLUTION: The program update system includes a vendor information downloading function 100 for obtaining new program update information including version information, a program name, conversion category, and character-string information from a new information delivery server located on a vendor homepage 050; a data file 101 for storing the new program update information obtained by means of the vendor information downloading function 100; a file 102 for storing old program update information; and a processing function 200 for comparing the version information, the program name, the conversion category, and the character-string information included in the file 101 with those included in the file 102, then changing, according to the result of this comparison, the version information included in the old program update information into the version information included in the new program update information, and then converting, according to the category included in the new program update information, the character-string information into a character string included in the new program update information. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a program update system and a program update method capable of automatically updating a program by taking in program update information provided by a vendor, and in particular, without creating source data such as a program source. The present invention relates to a program update system and a program update method capable of automatically performing update processing of addition, correction, and deletion of the information and managing update history of acquired change information.

  In general, a core business integration type application system package is such that a vendor's product sales homepage is registered in a vendor information providing server and registered in a business management server connected to the server via an Internet communication network. However, the programs on the homepage are often updated as the various legal systems are revised / requested by customers / market changes, so the version of the program that has been used so far has been changed and used so far. It is assumed that the program on the business management server that has been used can no longer be used.

  For this reason, it is necessary for the core business integration type application system package to check for any changes to all existing programs provided by the vendor, and to update the programs to be changed such as addition, change, and deletion. is there.

As one of the update management methods of this program, there is a version management method. For example, as described in Patent Document 1 below, in a client / server LAN system, client software version upgrade data is centrally managed on the server. Some versions of the client software are upgraded. Specifically, when registering new version update data created by including previous version update data in the server, the version update data corresponding to the included version is deleted from the server, and the new version update data is also stored in the server. And registering the version update data again.
JP 2002-91776 A

  The above-described program update method according to the prior art requires a large amount of man-hours and costs and adds / changes / deletes the program to be changed as well as checking whether all existing programs provided by the vendor are changed. There was a problem that if there was a mistake in the creation of source data or a change / deletion, it would cause a system failure.

  Especially for programs that are individually customized for each user company, such as integrated business packages, even if they are the same version, there are differences at the source code level. There was also a problem that it was not possible to perform up.

  The technique described in Patent Document 1 is used to centrally manage the upgrade data of the client computer on the server, but the upgrade management for the individually customized programs as described above is not considered at all. There was a problem.

  An object of the present invention is to eliminate the above-mentioned problems caused by the prior art, and extracts only necessary information from the version change information provided from the vendor side, and updates each program based on the extracted information. To provide a program update system and a program update method that can be automatically performed at a code level.

  In order to achieve the above object, the present invention provides a program update system having an information capture function, an information comparison function, and an information update function, from an information providing server on a vendor homepage, and version information, a program name, a conversion category, A capture data file that acquires and stores program update information including character string information, a program information file that stores program information including version information, a program name, a conversion category, and character string information, and the capture data file The version information, the program name, the conversion classification, and the character string information included in the stored program update information and the program information stored in the program information file are compared, and the version information included in the program information is determined based on the comparison result. Versions included in program update information With change in the information, the first, comprising a processing unit for performing updating processing including add, correct or delete the character string information included in the program information in accordance with categories contained in the program update information.

  Furthermore, the present invention provides a program update method having an information fetch function, an information comparison function, and an information update function, and includes version information, a program name, a conversion category, and character string information from an information providing server on a vendor homepage. Comparing version information, program name, conversion classification, and character string information included in the first step of acquiring program update information and the program update information acquired in the first step and the program information stored in the program information file Then, based on the comparison result, the version information included in the program information is changed to the version information included in the program update information, and addition / correction of character string information included in the program information is performed according to the classification included in the program update information. Including a second step of performing the deletion And butterflies.

  The program update system and the update method according to the present invention change the version information included in the old program update information to the version information included in the new program update information, and update the character string information according to the classification included in the new program update information. By converting to a character string included in the update information, a program update process including addition, correction, and deletion of the program can be performed.

  Hereinafter, an embodiment of a program update system and a program update method according to the present invention will be described in detail with reference to the drawings. FIG. 1 is an overall configuration diagram of a program update system according to the present embodiment, FIG. 2 is a flowchart of vendor information fetching processing according to the present embodiment, FIG. 3 is a diagram showing an image of vendor information fetching processing according to the present embodiment, and FIG. FIG. 5 is a diagram showing a vendor information fetching data file according to this embodiment, FIG. 5 is a flowchart of vendor information and user information matching and conversion processing according to this embodiment, and FIG. 6 is a diagram showing an outline of error checking according to this embodiment. FIG. 8 is a diagram of a new addition process according to this embodiment, FIG. 8 is a diagram of an insertion process according to this embodiment, FIG. 9 is a diagram of a change and deletion process according to this embodiment, and FIG. 10 is a chart of a change and deletion process according to this embodiment.

<Description of configuration>
As shown in FIG. 1, the program update system according to the present embodiment is connected to a vendor information providing server 050 including a vendor home page, and the vendor information providing server 050 via a network such as an Internet network, and version change compatible program conversion. The version change compatible program conversion system includes a vendor information capture processing function 100, a vendor information capture data file 101, a current program information (before conversion) file 102, and vendor information. A user information matching conversion processing function 200 and a development machine program information (after conversion) file 201 are provided.

  The program update system executes the vendor information fetch processing function 100 to acquire vendor information from the vendor information providing server 050 on the vendor home page and create a vendor information fetch data file 101. The fetched vendor information By executing the vendor information / user information matching & conversion processing function 200 for the data file 101 and the current program information (before conversion) file 102, change information from the vendor information capture data file 101 is obtained, and the version and program It operates to update and create a program information (after conversion) file 201.

  As shown in FIG. 2, the vendor information import processing function 100 extracts the version change information from the vendor information providing server 110 (step 111), and the “version” of the fetched version change information is shown in FIG. Information ”is detected, and a character string (version number or the like) starting with 6-byte alphanumeric characters following the data is set as version information of the vendor information fetch data file 120 (step 112).

  Next, this system detects the “program name” character string of the imported version change information, and converts the character string (program name) beginning with the 8-byte alphanumeric character following the character string to the vendor information capture data file. Set as a program name (step 113), detect the "classification" character string of the imported version change information, and indicate the conversion classification of 1-byte alphanumeric characters (A, I, R, D, etc.) following the character string (Character) is set in the conversion category of the vendor information capture data file (step 114), and the "character string information 1" character string of the captured version change information is detected, and the characters starting with alphanumeric characters in the character string A column is set in each item of the vendor information capture data file according to the contents of the conversion category (step 115). The conversion category “A” in step 115 means “set to program data”, the conversion category “I” means “set to general-purpose module”, and the conversion category “R” is set to “old character string”. The conversion classification “D” means “set to old character string”.

  Furthermore, this system detects the “character string information 2” character string of the imported version change information, and converts the character string starting with alphanumeric characters of the character string into each item of the vendor information import data file according to the contents of the conversion classification. (Step 116). The conversion category “A” in step 116 means “not set”, the conversion category “I” means “set to program data”, and the conversion category “R” means “set to new character string”. The conversion category “D” means “no setting”.

  Next, the system repeats the processing described in steps 114 to 116 until the version change information is completed, and stores it in the vendor information capture data file 120 (step 117), and ends the processing.

  That is, the program update system according to the present embodiment uses an item name included in the version change information from the vendor on the right side of FIG. 2, for example, a character string representing an item name such as “version information” / “program name” / “category”. The data of a predetermined number of bytes following the detected item name is extracted as the content corresponding to the item name and stored in the vendor information capture data file 120.

  As shown in FIG. 3, the stored vendor information capture data file 120, when the version change information 300 includes data indicated by symbols a to g in the figure, captures the vendor information capture that has read these data a to g. Embedded data file 450 is created. That is, the program update system takes in the version change information shown in FIG. 3 and includes each item of version / section / general module name / old character string / new character string / program data for each of the data a to g. A data file 450 for capturing vendor information is created.

The data file format of the import vendor information import data file 450 is as follows. The version information is 6 alphanumeric characters, the change classification is 1 alphanumeric character, the program name is 8 alphanumeric characters, and the general module name is English. This is a format for storing contents such as 30 digits, an old character string of 30 alphanumeric characters, a new character string of 30 alphanumeric characters, and program data of 80 alphanumeric characters.
<Description of operation>

  Now, as shown in FIG. 5, the vendor information: user information matching & conversion process of the program update system configured as described above performs an initialization process to turn off the process first flag / READ flag / clear the SPACE area. (Step 201), one record is read from the vendor information file (Step 202), it is determined whether or not the data of the vendor information file is completed (Step 203). The contents of the First flag are confirmed. When the flag is OFF, since no case is processed, “0 case error” is output and the program is terminated (steps 204 to 205).

  If it is determined in step 203 that the data in the vendor information file is continued (not finished), it is determined whether or not the processing first flag is on (step 206). If the processing first flag is off, the read data In response to the required item check (step 207), it is determined whether or not an error has occurred based on the result of the required item check in step 207 (step 208). Is output and the program is terminated. The error check items in step 207 are, as shown in FIG. 6, an essential item check 601 for determining whether each information is blank, and a segment value check 602 for determining whether the conversion category is a predetermined alphabetic character. And 0 item check 604 for determining whether data is not registered in the vendor information import data file, and a conversion category association check 605 for checking the mutual relationship of the conversion category values.

  If no error occurs in step 208, the process checks the content of the READ flag (step 209). If the READ flag is OFF, the process corresponds to the program name set in the vendor information file. Then, the file is acquired from the file before conversion (step 210), the related check is performed when acquiring the previous item (step 211), and the presence or absence of an error is determined (step 212). This association check is each item shown in FIG.

  If a related error occurs in step 212, a “data related error” is output and the program is terminated. If no related error occurs, this process copies all the contents of the acquired pre-conversion file to the WORK area. Perform (step 213).

  In step 208, when the READ flag is on, this process determines whether or not the conversion category is “A” (step 214), and when the category is “A” (new addition), “classification related error”. Is output and the program is terminated. As described above, in the present embodiment, when the READ flag is determined to be ON in the step 209, the same program is being continuously processed, so that the newly added process is performed when insertion / change / deletion is performed. In addition, when new additions are made, the version is different, so the same processing cannot be performed.

  Subsequently, following the step 213, the program update system saves the version, the program name, and the contents of the change classification in the vendor information file and turns on the processing first flag (steps 215 to 216).

  On the other hand, when it is determined in step 206 that the processing first flag is on, the system determines whether the read vendor information version and program name match the saved value (step 217), and the version and program name match. If so, a conversion classification related check is performed on the read data (step 218). If a related check error occurs, a "classification related error" is output and the program is terminated (step 219). The contents of the check in step 218 are as shown in FIG.

  If the version of the vendor information does not match the saved value, version, or program name in step 217, the system sets the contents of the WORK area in the converted file, and writes (step 220). The processing first flag is turned off (step 221), and it is further determined whether the read vendor information program name matches the saved value (step 222). If the program name matches, the READ flag is turned on (step 223). If they do not match, the READ flag is turned OFF (step 224), the WORK area is also cleared in SPACE (step), and the operation returns to step 206 described above.

  If there is no error in step 219, or following step 216, the system determines whether the conversion category on the vendor information file is 'R' (change) or 'D' (delete) (step 225). ) If the conversion category is 'R' (change) or 'D' (delete), a character string that matches the old character string information in the vendor information file is searched from the WORK area (step 226). As a result of the search, it is determined whether or not there is a matching character string (step 227). If there is matching data, it is determined again whether the conversion category is 'R' (change) (step 228). ) If the conversion category is' R '(change), the new character string information in the vendor information file is replaced with the character string matched on the WORK area (step 229). In step 228, the conversion category is' If it is not R '(change), the line containing the matched character string on the WORK area is deleted (step 230).

  In addition, when it is determined in step 225 that the conversion category is not “R” (change) or “D” (deletion), the system next determines whether the conversion category is “A” (addition). When the determination is made (step 231) and the conversion classification is 'A' (addition), the program data (one line) of the vendor information file is sequentially added from the first line on the WORK area (step 232).

  When the conversion category is not “A” (addition) in the step 231, the system determines whether or not the conversion category is “I” (insertion) (step 233), and the conversion category is “I” (insertion). ), The program data (one line) of the vendor information file is sequentially added (inserted) to the last line on the WORK area (step 234), and when the conversion classification is not 'I' (insertion), "Error" is output and the program is terminated.

  When the addition process in step 232 is the vendor information import file shown in FIG. 7, all the data in the program data 707 is newly added as a new program like the pre-change file 710 is the post-change file 720.

  In the case of the vendor information import file shown in FIG. 8, the insertion process in step 234 adds the additional program after the pre-change program as in the post-change file 820 using the pre-change file 810. That is, this insertion processing is performed as a program in which a general-purpose module is inserted into the last line of the existing program of the file before conversion from the version information 801 of the vendor information capture data file, the classification 802, the program name 803, the general-purpose module 804, and the program data 807. Create a new program.

  As shown in FIG. 9, the replacement process of the new character string information in step 229 and the deletion process in step 230 are performed when the vendor information import data file has changed in the data ac shown in FIG. This is done by changing the data abc of 910 as the changed file 920. That is, this deletion processing is performed for the existing program of the file before conversion based on the version information 901, the category 902, the program name 903, the old character string 905, and the new character string 906 of the data a to c of the vendor information capture data file. Thus, a new program is created as the changed and deleted program.

  Also, vendor information: user information matching & conversion change & deletion processing is performed as shown in FIG. 10 from the conventional program version (1.0) to the next program version (1.1) and the latest version (1.2). ), Processing is performed when changes between versions are made. The reason for performing the processing when changes between versions are made is that the user can select the number of versions to be upgraded in the core business integrated application system. This is because the version to be used becomes the version of the program to be used. That is, this process changes the version information 1001 of the df information of the vendor information capture data file, the category 1002, the program name 1003, the old character string 1005, and the new character string 1006 from the existing program of the file before conversion. A new program is created as the deleted program. In this way, a new program is created across the versions from the program version (1.0) to the next program version (1.1) and then to the next version (1.2).

  As described above, the program update system and the update method according to the present invention change the version information included in the program update information to the version information included in the program information, and change the character string information into the program information according to the classification included in the program update information. By converting to a character string included in the program, it is possible to perform program update processing including addition, correction, and deletion of programs.

1 is an overall configuration diagram of a program update system according to an embodiment of the present invention. The flowchart figure of the vendor information taking-in process by this embodiment. The figure which shows the vendor information taking-in image by this embodiment. The figure which shows the vendor information taking-in data file by this embodiment. The flowchart figure of vendor information and user information matching and conversion processing by this embodiment. The figure which shows the outline | summary of the error check by this embodiment. The new addition process image figure by this embodiment. The insertion process image figure by this embodiment. The change and deletion process image figure by this embodiment. The change and deletion process image figure by this embodiment.

Explanation of symbols

  050: Vendor information providing server, 100: Vendor information import processing function, 101: Vendor information data file, 102: Program information (before change) file, 110: Vendor information providing server, 120: Vendor information import data file, 200: Conversion processing function, 300: Version change information, 450: Vendor information import data file, 601: Mandatory item check, 602: Category value check, 604: 0 item check, 605: Conversion category related check, 707: Program data, 710 : File before change, 720: File after change, 801: Version information, 802: Classification, 803: Program name, 804: Function module, 807: Program data, 810: File before change, 820: File after change, 901: Version 902: Category, 903: Program name, 905: Old character string, 906: New character string, 910: File before change, 920: File after change, 1001: Version information, 1002: Category, 1003: Program name, 1005 : Old string.

Claims (2)

A program update system having an information capture function, an information comparison function, and an information update function,
Captured data file for acquiring and storing program update information including version information, program name, conversion classification, and character string information from the information providing server on the vendor homepage, version information, program name, conversion classification, and character string information Version information, program name, conversion classification, and character string information included in a program information file that stores program information including: program update information stored in the capture data file and program information stored in the program information file Based on the comparison result, the version information included in the program information is changed to the version information included in the program update information, and the character string information included in the program information is added according to the classification included in the program update information. Includes corrections and deletions Program update system, comprising a processing unit for performing new processing. A program update method having an information capture function, an information comparison function, and an information update function,
A first step of acquiring program update information including version information, a program name, a conversion classification, and character string information from an information providing server on the vendor homepage, and the program update information and the program information file acquired by the first step Compares the version information, program name, conversion classification, and character string information included in the stored program information, and changes the version information included in the program information to version information included in the program update information based on the comparison result. And a second step of adding, correcting, and deleting the character string information included in the program information according to the classification included in the program update information.

Images