JP5434654B2 - Application server, program for realizing the application server, and Web application system including the application server - Google Patents

Description

  The present invention receives an address data from one or more terminal devices connected via a network or the like, operates according to an application file specified by the address data, a program for realizing the application server, and The present invention relates to a Web application system including the application server.

  Conventionally, address data (hereinafter simply referred to as “URL”) such as a URL (Uniform Resource Locator) is received from one or more terminal devices connected via a network or the like, and a Web application file designated by the URL There are application servers that operate according to (hereinafter simply referred to as “application files”).

  The application server provides, for example, a screen that displays a list of operable application files (hereinafter referred to as “menu screen”) to the terminal device, and allows a user operating the terminal device to select an arbitrary application file. Each application file listed on the menu screen is associated with a URL for accessing the application file. When the user selects an arbitrary application file, the terminal device transmits a URL associated with the selected application file to the application server.

  When the application server receives the URL from the terminal device, the application server operates according to the application file stored in the storage area specified by the URL, thereby executing a job desired by the user operating the terminal device.

  In many cases, this application server is connected to a database server that registers various data and application files, and constitutes a Web application system together with the database server.

  In addition, as an application server, there is a device that downloads an application program to a terminal device and causes the terminal device to execute the application program, thereby sharing the task desired by the user with the terminal device (for example, Patent Document 1). reference). The application server disclosed in Patent Document 1 determines whether or not the application program has been downloaded when the terminal device has accessed, and if it is determined that the download has not been completed, the necessity for downloading is determined. Is notified to the terminal device.

JP-A-6-131163

  However, in the conventional application server, when there are a plurality of application file versions (versions), the user needs to consciously select and specify a different URL for each version of the application file corresponding to the terminal device. For this reason, there is a problem that the usability is bad and the user is burdened with operations.

  That is, in the conventional application server, for example, when an application file is upgraded, an old version application file registered in the application server is deleted by an administrator such as a central management center. The file is registered. Thereby, the application file is replaced in the conventional application server. However, this application file replacement takes time. Therefore, the conventional application server has registered multiple versions of application files with different file names. However, the application server can operate only one application file per URL. For this reason, different URLs are set in each version of the application file.

  Since the URL corresponding to each version of the application file is different, the user needs to consciously select and specify a different URL for each version of the application file corresponding to the terminal device operated by the user. For this reason, the conventional application server is not easy to use, and places a heavy operational burden on the user.

  Therefore, the user automatically (or accesses) the application file of a suitable version number automatically in accordance with the terminal device operated by the user without making the user aware of the version number of the application file. The provision of an application server has been desired.

  Further, the conventional application server has a problem that once a new version of an application file is registered, it cannot be immediately restored to the old version of the application file.

  That is, in the conventional application server, the new version application file is registered by replacing the old version application file. Therefore, in order for the conventional application server to return the new version of the application file provided to the terminal device to the old version of the application file, the administrator of the central management center or the like can change the new version of the application file registered in the application server. The application file is deleted and the old version of the application file needs to be re-registered instead. However, it takes time to re-register the old version of the application file. For this reason, once a new version of an application file is registered, the conventional application server cannot immediately return to the old version of the application file.

  Further, the conventional Web application system has a problem that when a failure occurs as a result of registering a new version of the application file in the application server, recovery from the failure is likely to be delayed.

  That is, the conventional Web application system has a version number of an application file corresponding to each terminal device and address data corresponding to each application when a failure occurs as a result of registering a new version of the application file in the application server. Therefore, the new version application file provided to the terminal device cannot be immediately returned to the old version application file. For this reason, in the conventional Web application system, recovery from a failure is easily delayed.

  In view of this, there has been a demand for a Web application system that can change the version number of the application file corresponding to each terminal device and the address data corresponding to each application.

The present invention has been made in order to solve the above-described problems, and automatically makes a suitable version number automatically corresponding to the terminal device operated by the user without making the user aware of the version number of the application file. It is a main object to provide an application server that operates (or accesses) according to the application file and a program that realizes the application server.
Another object of the present invention is to provide a Web application system that easily changes the version number of an application file corresponding to each terminal device and address data corresponding to each application.

  In order to achieve the above object, the first invention is the application server that receives address data from one or more terminal devices connected via a network and operates according to an application file specified by the address data. A storage unit that stores multiple versions of an application file corresponding to an item, a menu screen that allows the terminal device to display each job type in a selectable manner, and each job type corresponds to the address data A menu screen generating unit that generates a menu screen for transmitting the address data corresponding to the selected and designated business type to the application server when selecting and specifying an arbitrary business type, and for each terminal device The version number of the application file corresponding to each business line A specific version number designated by the address data transmitted from the terminal device from among the multiple version application files stored in the storage unit corresponding to each business type A job execution unit that operates according to the application file, and the menu screen generation unit sets the version number of the application file corresponding to each terminal device as the specific version number, and for each terminal device, the version The address data for accessing each business type and the specific version number of application files stored in the storage unit according to the version number of the application file corresponding to each business type managed by the number management unit The menu screen is generated in association with each other, and the generated menu screen is displayed on each of the terminals. A configuration to be sent to the location.

  In this application server, the menu screen generation unit sets the version number of the application file corresponding to each terminal device as a specific version number, and for each terminal device, the application corresponding to each business type managed by the version number management unit According to the version number of the file, a menu screen is generated by associating each job type with the address data for accessing the application file of a specific version number stored in the storage unit, and the generated menu screen is displayed on the terminal device. Send. For this reason, the terminal device automatically operates according to an application file having a suitable version number as appropriate simply by selecting and specifying an arbitrary job type from among the job types displayed on the menu screen so as to be selectable. Therefore, this application server does not require the user to consciously select and specify different URLs for each version of the application file corresponding to the terminal device, so that the usability is improved and the operational burden on the user is increased. Can be reduced.

  Further, since this application server registers a plurality of versions of application files, the old version of the application file and the new version of the application file are registered together instead of being replaced. Therefore, this application server can also solve the problem that once a new version of an application file is registered, it cannot be immediately restored to the old version of the application file.

  Further, the second invention receives address data from one or more terminal devices connected via a network, and corresponds to each business item in an application server that operates according to an application file determined by the address data. A storage unit that stores an application file of a plurality of versions, an access destination determination unit that determines an application file to be accessed by the terminal device when receiving the address data from the terminal device, and a task for each terminal device A version number management unit that manages the version number of the application file corresponding to the item, and the plurality of version application files stored in the storage unit corresponding to each business item, and transmitted from the terminal device. Specified version number specified by the address data A job execution unit that operates according to an application file, wherein the access destination determination unit sets the version number of the application file corresponding to each terminal device as the specific version number, and the version number is determined for each terminal device. The address data for accessing each business type and the specific version number of application files stored in the storage unit according to the version number of the application file corresponding to each business type managed by the number management unit To determine the access destination.

  In this application server, the access destination determination unit sets the version number of the application file corresponding to each terminal device as a specific version number, and for each terminal device, the application corresponding to each business type managed by the version number management unit In accordance with the version number of the file, an access destination is determined by associating each business type with address data for accessing a specific version number of application file stored in the storage unit. For this reason, the terminal device automatically accesses an application file having a suitable version number automatically when the user selects and designates an arbitrary business item. Therefore, this application server does not require the user to consciously select and specify different URLs for each version of the application file corresponding to the terminal device, so that the usability is improved and the operational burden on the user is increased. Can be reduced.

  In addition, since this application server registers multiple versions of the application file in the same manner as the application server according to the first aspect of the invention, the old version of the application file and the new version of the application file are registered together instead of being replaced. Is done. Therefore, this application server can also solve the problem that once a new version of an application file is registered, it cannot be immediately restored to the old version of the application file.

According to a third aspect of the present invention, a computer in which a plurality of versions of application files corresponding to each business item is stored in a storage unit receives address data from one or more terminal devices connected via a network, and A program that functions as an application server that operates in accordance with an application file specified by address data, the computer having a menu screen that allows the terminal device to display each job type in a selectable manner, and each job type And the address data are associated with each other, and when selecting and specifying an arbitrary business type, a menu screen generating unit that generates a menu screen for transmitting the address data corresponding to the selected business type to the application server And each business line for each terminal device The version number management unit that manages the version number of the corresponding application file, and the plurality of version number application files stored in the storage unit corresponding to each business type, and transmitted from the terminal device The menu screen generation unit functions as the specific version number of the application file corresponding to each terminal device, and functions as a business execution unit that operates according to the specific version number of application file specified by the address data. In accordance with the version number of the application file corresponding to each business type managed by the version number management unit for each terminal device, the application file of the specific version number stored in each business type and the storage unit The menu screen is generated in association with the address data for accessing And, a structure that transmits the generated the menu screen to each of the terminal device.
This program causes a computer to function as an application server according to the first invention.

According to a fourth aspect of the present invention, a computer in which a plurality of versions of application files corresponding to each business item is stored in a storage unit receives address data from one or more terminal devices connected via a network, and A program that functions as an application server that operates according to an application file specified by address data, the computer storing a plurality of versions of an application file corresponding to each business item, and the terminal device When receiving the address data, an access destination determining unit that determines an application file to be accessed by the terminal device, and a version number managing unit that manages the version number of the application file corresponding to each business type for each terminal device; Corresponding to each business line Function as a business execution unit that operates in accordance with a specific version number of application files specified by the address data transmitted from the terminal device from among the multiple version number of application files stored in the unit, and determines the access destination The section sets the version number of the application file corresponding to each terminal device as the specific version number, and for each terminal device, the version of the application file corresponding to each business type managed by the version number management unit According to the version number, each business type is associated with the address data for accessing the application file having the specific version number stored in the storage unit, and the access destination is determined.
This program causes a computer to function as an application server according to the second invention.

  The fifth invention is a Web application system for managing the version number indicating the correspondence between the application server according to the first invention or the second invention, each terminal device and the version number of the application file. A database in which a table, an application file of each version number, and a table for address data management representing a correspondence between the address data for accessing the application file are registered, and the version number management registered in the database And a setting device for performing a data change process on the address data management table and the address data management table.

  In this Web application system, application files of a plurality of versions are registered in the application server, and a version management table and an address data management table are registered in the database. The version number registered in the database Since the management table and the address data management table are changed by the setting device, the version number of the application file corresponding to each terminal device and the address data corresponding to each application can be easily changed.

According to the first aspect of the present invention, there is provided an application server that automatically operates according to a suitable version of an application file automatically in accordance with a terminal device operated by the user without making the user aware of the version of the application file. be able to.
In addition, according to the second invention, there is provided an application server that automatically accesses a suitable version of an application file automatically corresponding to a terminal device operated by the user without making the user aware of the version of the application file. Can be provided.
Moreover, according to the third invention, a program for realizing the application server according to the first invention can be provided.
According to the fourth invention, a program for realizing the application server according to the second invention can be provided.
In addition, according to the fifth aspect of the invention, it is possible to provide a Web application system that can easily change the version number of the application file corresponding to each terminal device and the address data corresponding to each application.

It is a figure (1) which shows the structure of the web application system containing the application server which concerns on embodiment. It is a figure (2) which shows the structure of the web application system containing the application server which concerns on embodiment. It is a figure which shows the structure of the application server which concerns on embodiment. It is a figure which shows the structure of the database server used by embodiment. It is a figure which shows the structure of the version number management master table used by embodiment. It is a figure which shows the structure of the menu table used by embodiment. It is a flowchart (1) which shows operation | movement of the web application system containing the application server which concerns on embodiment. It is a flowchart (2) which shows operation | movement of the web application system containing the application server which concerns on embodiment. It is a flowchart (3) which shows operation | movement of the web application system containing the application server which concerns on embodiment. It is a flowchart (4) which shows operation | movement of the web application system containing the application server which concerns on embodiment. It is a flowchart (5) which shows operation | movement of the web application system containing the application server which concerns on embodiment. It is a figure (1) which shows the example of a display screen of the version number setting apparatus used by embodiment. It is a figure (2) which shows the example of a display screen of the version number setting apparatus used by embodiment. It is a figure (3) which shows the example of a display screen of the version number setting device used by an embodiment. It is FIG. (4) which shows the example of a display screen of the version number setting apparatus used by embodiment. It is a figure (1) which shows the example of a display screen of the client terminal device used by embodiment. It is a figure (2) which shows the example of a display screen of the client terminal device used by embodiment.

  Hereinafter, an embodiment of the present invention (hereinafter referred to as “the present embodiment”) will be described in detail with reference to the drawings. Each figure is only schematically shown so that the present invention can be fully understood. Therefore, the present invention is not limited to the illustrated example. Moreover, in each figure, the same code | symbol is attached | subjected about the common component and the same component, and those overlapping description is abbreviate | omitted.

<Configuration of Web application system including application server>
Hereinafter, a configuration of a Web application system including an application server according to the present embodiment will be described with reference to FIGS. 1A and 1B. Here, for example, the Web application system 1 is a financial institution such as a bank or the like. ) Etc. are explained as being used to perform financial operations.

  1A and 1B are diagrams each showing a configuration of a Web application system including an application server according to the embodiment. In the example illustrated in FIG. 1A, the database 43 has a configuration independent of the application server 3 as a component of the database server 4. On the other hand, in the example shown in FIG. 1B, the database 43 has a configuration built in the application server 3 as a component of the application server 3. The Web application system 1 may be configured as shown in either one of FIGS. 1A and 1B, but here, it will be described as having the configuration shown in FIG. 1A.

  As shown in FIG. 1A, the Web application system 1 includes an application server 3, a database server 4, and a version number setting device 5 as devices on the central management center 2 side, and a branch (including a business trip store) 6 As a device on the side, one or a plurality of client terminal devices 7 are provided, and a device on the central management center 2 side and a device on the branch 6 side are connected via a wired or wireless network 8. In FIG. 1A, only one branch 6 is shown, but there are actually many branches 6.

  The application server 3 is a server in which application files (hereinafter sometimes referred to as “AP”) corresponding to each business are registered. Details of the application server 3 will be described later with reference to FIG. Here, the server is installed with a program (hereinafter referred to as an “application server construction program”) 9 a for causing the server to function as the application server 3 from the storage medium 9. It will be described as being realized. The storage medium 9 is, for example, a memory member such as a USB memory, an HDD device, an optical medium such as a CD-ROM or a DVD, a magnetic medium such as a flexible disk, or other forms.

  The database server 4 is a server having a database 43 in which various data are registered. Details of the database server 4 will be described later with reference to FIG. Here, an operation of storing data serving as a reference for data generation and data serving as a reference for determination processing in a recording unit is referred to as “registration”.

  The version number setting device 5 includes address data such as a URL (hereinafter simply referred to as “URL”) corresponding to each version of the application file, and an application file that operates in each job corresponding to each client terminal device 7. It is a device that sets the version number. Here, the version number setting device 5 will be described as a personal computer (PC) in which a control program for displaying a login screen 105 shown in FIG. 10 on a display unit (not shown), for example, is stored. The version number setting device 5 registers a menu table 42MN (see FIG. 5) to be described later in the database 43 of the database server 4 and a version number management master table 42VC (see FIG. 4) to be described later, or a registered menu table 42MN. Or by modifying the version number management master table 42VC, the URL corresponding to each version of the application file and the version number of the application file corresponding to each client terminal device 7 are set.

  The client terminal device 7 is a terminal device that is installed at a window of the branch 6 and executes various transaction processes. Here, the client terminal device 7 is a personal computer (PC) in which a control program for displaying an initial screen 205 including a menu screen acquisition icon 205a shown in FIG. 15 on a display unit (not shown), for example, is stored. It will be explained as being. The client terminal device 7 acquires the menu screen 210 (see FIG. 16) from the application server 3. The menu screen 210 displays a list of various business types, and each business type is associated with a URL for accessing an application file registered in the application server 3. The client terminal device 7 does not show an image generated as a result of the browser being activated and the application server 3 operating in accordance with the application file when the user selects an arbitrary business type from among the business types displayed in a list. Display on the display. Thereby, the client terminal device 7 executes a job desired by the user. Therefore, a bank employee who works at a branch 6 of a financial institution becomes a user of the client terminal device 7 and operates the client terminal device 7 to use, for example, an arbitrary application file registered in the application server 3 to perform seal verification. Can perform financial services such as processing and deposit / withdrawal processing.

<Application server configuration>
Hereinafter, the configuration of the application server 3 according to the present embodiment will be described with reference to FIG. FIG. 2 is a diagram illustrating a configuration of the application server according to the embodiment. Here, the Web application system 1 will be described as having the configuration shown in FIG. 1A. However, if the Web application system 1 has the configuration shown in FIG. 1B, the application server 3 is shown in FIG. The database 43 shown in FIG.

  As shown in FIG. 2, the application server 3 includes a control unit 31, a storage unit 32, and a communication unit 35. The control unit 31 includes a CPU, and functions as a main control unit 31A, a menu screen generation unit 31B, a version number management unit 31C, a job execution unit 31D, and a communication control unit 31E. The storage unit 32 includes a RAM, a ROM, an HDD, and the like, and is divided into a menu screen generation AP storage unit 32A, a version number management AP storage unit 32B, and a business AP storage unit 33. The communication unit 35 performs communication with external devices (here, the database server 4, the version number setting device 5, and the client terminal device 7) via the network 8.

The main control unit 31A is a functional unit that controls the operation of each unit.
The menu screen generation unit 31B is a functional unit that generates a menu screen 210 (see FIG. 16) to be displayed on the client terminal device 7. The menu screen 210 is a screen that can be selected and specified for each business type. In the menu screen 210, each business item is associated with address data. In the client terminal device 7, when the menu screen acquisition screen 205a is designated by the user, the menu screen generation unit 31B determines the version number of the application file corresponding to the client terminal device 7 from the database server 4 for each business item. A menu screen 210 (see FIG. 16) that represents the business line that is acquired and associated with the version number of the application file corresponding to the client terminal device 7 is dynamically generated.

  The version number management unit 31 </ b> C is a functional unit that manages the version number of the application file corresponding to each business type for each client terminal device 7. The version number management unit 31C stores table data (hereinafter referred to as “menu table 42MN (see FIG. 5)”) representing the relationship between the application file of each version number and the corresponding address data (URL) for each business type. And registering it in the database 43 of the database server 4. Further, the version number management unit 31C stores table data (hereinafter referred to as “version number management master table 42VC (see FIG. 4)”) representing the relationship between each client terminal device 7 and the version number of the application file corresponding thereto. And registering it in the database 43 of the database server 4. The menu table 42MN and the version number management master table 42VC are appropriately registered and modified by the version number setting device 5.

The business execution unit 31D is a functional unit that operates according to the application files 32CAP and 32DAP stored in the business AP storage unit 33.
The communication control unit 31E is a functional unit that controls the communication unit 35.

The menu screen generation AP storage unit 32A is a storage unit that stores an application file (hereinafter referred to as “menu screen generation AP”) that causes the CPU to function as the menu screen generation unit 31B.
The version number management AP storage unit 32B is a storage unit that stores an application file (hereinafter referred to as “version number management AP”) that causes the CPU to function as the version number management unit 31C.

  The business AP storage unit 33 is a storage unit that stores a plurality of versions of application files (AP) corresponding to each business. Here, the business AP storage unit 33 includes an application file (hereinafter referred to as a “seal verification AP”) 32CAP for executing a seal verification process, and an application file (32) for executing a deposit / withdrawal process. Hereinafter, description will be made on the assumption that it is divided into a deposit / withdrawal AP storage unit 32D for storing 32DAP. The stamp verification AP storage unit 32C stores a plurality of versions of the stamp verification APs 32Ca, 32Cb, 32Cc,. The deposit / withdrawal AP storage unit 32D stores a plurality of versions of deposit / withdrawal APs 32Da, 32Db, 32Dc,.

<Configuration of database server>
Hereinafter, the configuration of the database server 4 used in this embodiment will be described with reference to FIG. FIG. 3 is a diagram illustrating a configuration of a database server used in the embodiment.

  As shown in FIG. 3, the database server 4 includes a control unit 41, a storage unit 42, and a communication unit 45. The control unit 41 is configured by a CPU and functions as a main control unit 41A, a data management unit 41B, and a communication control unit 41E. The storage unit 42 includes a RAM, a ROM, an HDD, and the like, and is divided into a version number management master table storage unit 42A and a menu table storage unit 42B. The version number management master table storage unit 42A and the menu table storage unit 42B function as the database 43. The communication unit 45 performs communication with external devices (here, the application server 3 and the version number setting device 5) via the network 8.

The main control unit 41A is a functional unit that controls the operation of each unit.
The data management unit 41B is a functional unit that registers data in the database 43 and manages registered data.
The communication control unit 41E is a functional unit that controls the communication unit 45.
The version number management master table storage unit 42A is a storage unit that stores a version number management master table 42VC (see FIG. 4). Details of the version number management master table 42VC will be described later with reference to FIG.
The menu table storage unit 42B is a storage unit that stores the menu table 42MN (see FIG. 5). Details of the menu table 42MN will be described later with reference to FIG.

<Configuration of tables registered in the database server>
The configuration of the table registered in the database server will be described below with reference to FIG. 4 and FIG.

(Configuration of version management master table)
FIG. 4 is a diagram illustrating a configuration of a version number management master table used in the embodiment. The version number management master table 42VC shown in FIG. 4 is table data for version number management, and represents the correspondence between each client terminal device 7 and the version number of each application file. In the example shown in FIG. 4, the version number management master table 42VC includes items such as “store number”, “terminal number”, and “version number”. In FIG. 4, the store number “ZZZ” means the number of all stores, and the terminal number “ZZZZZ” means the number of all terminals.

  Here, in the version number management master table 42VC, the version numbers of all the terminals in all stores (that is, the client terminal device 7 in which the store number is “ZZZ” and the terminal number is “ZZZZZ”) are set in advance as standard. The version number (here, “normal version”) is registered in the version number management master table storage unit 42A (see FIG. 3) of the database server 4, and then the central management center 2 (see FIG. 1A) of the financial institution. ) Will be described as the version number of each client terminal device 7 being individually registered (set) by operating the version number setting device 5 (see FIG. 1A) as a data manager.

  4A shows the configuration of the version management master table 42VC before the change, and FIG. 4B shows the configuration of the version management master table 42VC after the change. Hereinafter, when the version number management master table 42VC is distinguished between before and after the change, they are referred to as a “version number management master table 42VCA before change” and a “version number management master table 42VCB after change”, respectively. The post-change version management master table 42VCB is compared with the pre-change version management master table 42VCA as the version number of the application file corresponding to the client terminal device 7 having the terminal number “ABCD” installed in the store number “3456”. Data representing “trial version” is registered for correction (set).

For example, FIG. 4A shows that all the client terminal devices 7 (“ZZZZZ”) of the store whose store number is “1234” use the old version of the application and other stores (“ZZZ”). This means that all client terminal devices 7 (“ZZZZZZZ”) use the normal version application file. That is, FIG. 4A shows that the default version number in the client terminal device 7 of all stores is the normal version, and the default version number is the old version only for the store number “1234”. Represents.
On the other hand, FIG. 4B shows that the trial version is specified to be used only for a specific terminal.

(Menu table configuration)
FIG. 5 is a diagram illustrating a configuration of a menu table used in the embodiment. A menu table 42MN shown in FIG. 5 is a URL management table, and represents the correspondence between each version of the application file and the URL for accessing the application file. In the example illustrated in FIG. 5, the menu table 42MN includes items such as “version number”, “business name”, and “URL”. In FIG. 5, each URL designates each application file 32CAP, 32DAP stored in the storage unit 32 (see FIG. 2) of the application server 3 corresponding to each version number.

  Here, “innkann” such as URL “http: //...innkannV1” means “seal verification” processing, and “money” such as URL “http: // moneyV1” is “payment / withdrawal”. In the following description, it is assumed that the processing work is performed, and the code “V1” at the end of each URL represents a version number. When the application server 3 receives a URL such as “http: //...innkannV1” or “http: // ... moneyV1” from the client terminal device 7, the storage unit 32 (specified by the URL using the HTTP protocol) (See FIG. 2) and the stamp verification application files 32Ca, 32Cb, 32Cc,... (See FIG. 2) and deposit / withdrawal application files 32Da, 32Db, 32Dc,.

  Further, here, the menu table 42MN has “http: //...innkann” in the “seal verification” processing business and “http: in the deposit / withdrawal” processing business in which the last code is “V1” or “V2” in advance. // money ”is registered in the menu table storage unit 42B (see FIG. 3) of the database server 4, and then a bank employee who works at the central management center 2 (see FIG. 1A) of the financial institution is the version of the data manager. By operating the number setting device 5 (refer to FIG. 1A), “http: //...innkann” of the “seal verification” processing business in which the last sign is “V3” and “http: of the deposit / withdrawal” processing business The description will be made on the assumption that “/...

  FIG. 5A shows the configuration of the menu table 42MN before the change, and FIG. 5B shows the configuration of the menu table 42MN after the change. Hereinafter, when the menu table 42MN is distinguished between before change and after change, they are referred to as “before-change menu table 42MNA” and “after-change menu table 42MNB”, respectively. Compared with the pre-change menu table 42MNA, the post-change menu table 42MNB includes “http: //” as the URL of the business name “seal verification” and the URL of the business name “payment / withdrawal” corresponding to the version number “trial version”. /...InnkannV3 "and" http: // ... moneyV3 "are additionally registered (set).

<Operation of Web Application System Including Application Server>
The operation of the Web application system 1 including the application server 3 according to this embodiment will be described below with reference to FIGS. 6 to 10 are flowcharts showing the operation of the Web application system 1 including the application server 3 according to the embodiment. Moreover, FIGS. 11-14 is a figure which shows the example of a display screen of the version number setting apparatus used by embodiment, respectively. FIGS. 15 and 16 are diagrams showing examples of display screens of the client terminal device used in the embodiment.

  Each device operates based on the time measured by a timer (not shown). The operation of each device is defined by a program stored in a readable manner in the storage unit of each device, and is realized by the control unit of each device. Further, communication between devices is performed by temporarily storing data received by the receiving device in the storage unit and then reading the data from the storage unit. In addition, each data is temporarily stored in a storage unit so as to be readable, and then output to a required component that performs subsequent processing. Hereinafter, since these points are conventional means in data processing, detailed description thereof is omitted.

(Management process of version number of application file corresponding to store number and terminal number)
First, with reference to FIGS. 6 and 7, the management process of the version number of the application file corresponding to the store number and the terminal number will be described. Here, a bank employee who works at the central management center 2 (see FIG. 1A) of a financial institution operates the version number setting device 5 (see FIG. 1A) as a data manager to the database server 4 (see FIG. 3). Access the version number management master table 42VC (see FIG. 4) registered in the version number management master table storage unit 42A (see FIG. 3) of the database server 4 and store number “3456” and terminal number “ABCD”. As an example, the case of additionally registering data of the version number “trial version” corresponding to “” will be described.

  The Web application system 1 starts processing when an administrator who works at the central management center 2 (see FIG. 1A) of the financial institution activates the version number setting device 5 (see FIG. 1A). Here, it is assumed that the application server 3 and the database server 4 are already activated.

  First, as shown in FIG. 6, the version number setting device 5 displays a login screen 105 (see FIG. 11) (S105). In the example illustrated in FIG. 11, the login screen 105 includes an input field for an administrator identification number (hereinafter referred to as “ID”) and a password (hereinafter referred to as “PASS”), and “Login”. A button and a “Cancel” button are provided.

  The version number setting device 5 accepts the input of the administrator's ID and PASS when the administrator inputs the ID and PASS into the input field of the login screen 105 and further presses the “Login” button. (For example, stored in a storage unit (not shown)) (S110), and transmits a maintenance screen transmission request (hereinafter referred to as "maintenance screen request") including the administrator ID and PASS to the application server 3 (S115). .

  After S115, when the application server 3 receives a maintenance screen request from the version number setting device 5 (S120), the version number management unit 31C (see FIG. 2) stores the version number management AP storage unit 32B (see FIG. 2). In accordance with the stored version number management AP, it is determined whether the ID and PASS included in the received maintenance screen request have the authority to manage the version number (hereinafter simply referred to as “management authority”). (S125).

  If it is determined in S125 that management authority exists (in the case of “Yes”), the process proceeds to S130. On the other hand, if it is determined that there is no management authority (in the case of “No”), the process is performed. ,finish.

  When it is determined in S125 that the management authority exists (in the case of “Yes”), the version number management unit 31C of the application server 3 transmits the maintenance screen 110 (see FIG. 12) to the version number setting device 5. (S130). In the example illustrated in FIG. 12, the maintenance screen 110 is provided with a “version number management screen” button and a “URL management screen” button. The “version management screen” button is a management screen (hereinafter referred to as “version management screen”) for performing data correction registration, additional registration, deletion, etc., to the version management master table 42VC (see FIG. 4). This is a button for acquiring from the application server 3. On the other hand, the “URL management screen” button is a management screen (hereinafter referred to as “URL management screen”) for performing data correction registration, additional registration, deletion, and the like with respect to the menu table 42MN (see FIG. 5). This is a button for obtaining from the application server 3.

  After S130, the version number setting device 5 receives the maintenance screen 110 from the application server 3 (S135), and displays the maintenance screen 110 (see FIG. 12) on a display unit (not shown) (S140).

  After S140, the administrator who operates the version number setting device 5 selects and presses either the “version number management screen” button or the “URL management screen” button included in the maintenance screen 110. Here, the administrator selects and presses the “version number management screen” button to instruct the version number setting device 5 to acquire the “version number management screen”. In this case, as shown in FIG. 7, the version number setting device 5 accepts the acquisition of the version number management screen (S145), and sends a version number management screen transmission request (hereinafter referred to as “version number management screen request”). Is transmitted to the application server 3 (S150).

  After S150, when the application server 3 receives a version number management screen request from the version number setting device 5 (S155), the version number management unit 31C (see FIG. 2), the version number management AP storage unit 32B (see FIG. 2). The version management screen 115a (see FIG. 13A) is generated and transmitted to the version number setting device 5 in accordance with the version management AP stored in (). At this time, the version management unit 31C of the application server 3 obtains the version management master table 42VCA before change from the database server 4 (see FIG. 4A), and based on the version management master table 42VCA before change. The version number management screen 115a (see FIG. 13A) is generated. The application server 3 stores the version management master table 42VCA before change in a storage area (not shown) in the storage unit 32 (see FIG. 2) of the application server 3 (or a version management AP storage unit 32B (see FIG. 2)). The version management master table 42VCA before change stored in the storage unit 32 may be used when generating the version management screen 115a in S160.

  After S160, when the version number setting device 5 receives the version number management screen 115a from the application server 3 (S165), the version number management screen 115a is displayed on a display unit (not shown) (S170).

  After S170, the administrator who operates the version number setting device 5 may change the data displayed on the version number management screen 115a (hereinafter referred to as “version number data”) with respect to the version number data. Change processing such as addition, correction, and deletion is performed. Here, the administrator performs the third step on the version number data displayed on the version number management screen 115a (see FIG. 13A) as in the version number management screen 115b shown in FIG. (That is, data having the store number “3456”, the terminal number “ABCD”, and the version number “trial version”) is additionally registered.

  The “add” process is executed, for example, when the administrator presses the “add” button displayed on the version number management screen 115a and adds the third-stage data. The “correction” process is executed, for example, when the administrator corrects a part of the version number data displayed on the version number management screen 115a. In the “deletion” process, for example, after the administrator designates a part of the version number data displayed on the version number management screen 115a, the “deletion” button displayed on the version number management screen 115a is pressed. Is executed.

  When all the change processes to be executed are completed, the administrator presses the “Register” button displayed on the version number management screen 115a. In response to this, the version number setting device 5 receives input of the changed version number data (S175) and includes the version data (hereinafter referred to as “input version number data”) that has been received. The registration request for the input version number data is transmitted to the application server 3 (S180).

  After S180, when the application server 3 receives a registration request for the input version number data from the version number setting device 5 (S185), the version number management unit 31C (see FIG. 2), the version number management AP storage unit 32B (see FIG. 2). 2), the database server 4 is instructed to register the input version number data (S190).

  After S190, in the database server 4, the data management unit 41B (see FIG. 3) registers the input version number data in the version management master table storage unit 42A (see FIG. 3) of the database 43 (S195). As a result, the version number management master table 42VCA (see FIG. 4A) registered in the version number management master table storage unit 42A has the store number “3456”, the terminal number “ABCD”, and The updated version number management master table 42VCB (see FIG. 4B) including version number data whose version number is “trial version” is updated. At this time, if the version number data whose store number is “3456” and the terminal number is “ABCD” is already registered in the version number management master table 42VCA, the data management of the database server 4 is performed. The unit 41B overwrites the input version number data on the already registered version number data.

  After S195, the data management unit 41B of the database server 4 transmits a signal indicating that data registration is completed (hereinafter referred to as “registration completion signal”) to the application server 3 (S200).

  After S200, when the application server 3 receives the registration completion signal from the database server 4 (S205), the version number management unit 31C (see FIG. 2) displays a message indicating that the data registration is completed (hereinafter, “registration”). Is generated and transmitted to the version number setting device 5 (S210).

  After S210, upon receiving a registration completion message from the application server 3 (S215), the version number setting device 5 displays the registration completion message on a display unit (not shown) (S220). As a result, a series of processing ends.

(URL management processing corresponding to version number and business name)
Next, URL management processing corresponding to the version number and the business name will be described with reference to FIGS. Here, an administrator who works at the central management center 2 (see FIG. 1A) of a financial institution operates the version number setting device 5 (see FIG. 1A) to access the database server 4 (see FIG. 3). 4 for the menu table 42MN (see FIG. 5) registered in the menu table storage unit 42B (see FIG. 3), the URL of the business name “seal verification” corresponding to the version number “trial version” and the business name “in / out” An example of the case of additionally registering a URL of “gold” will be described as an example.

  The Web application system 1 starts processing when an administrator who works at the central management center 2 (see FIG. 1A) of the financial institution activates the version number setting device 5 (see FIG. 1A). Here, it is assumed that the application server 3 and the database server 4 are already activated.

  First, as shown in FIG. 6, the version number setting device 5 displays a login screen 105 (see FIG. 11) (S105). Hereinafter, the version number setting device 5 performs the process as described above over S105 to S140.

  After S140, the administrator who operates the version number setting device 5 selects and presses either the “version number management screen” button or the “URL management screen” button included in the maintenance screen 110. Here, it is assumed that the administrator selects and presses the “URL management screen” button and instructs the version number setting device 5 to acquire the “URL management screen”. In this case, as shown in FIG. 8, the version number setting device 5 accepts the URL management screen acquisition (S145a), and sends a URL management screen transmission request (hereinafter referred to as “URL management screen request”). It transmits to the application server 3 (S150a).

  After S150a, when the application server 3 receives the URL management screen request from the version number setting device 5 (S155a), the version number management unit 31C (see FIG. 2), the version number management AP storage unit 32B (see FIG. 2). The URL management screen 120a (see FIG. 14A) is generated and transmitted to the version number setting device 5 in accordance with the version number management AP stored in (S160a). At this time, the version number management unit 31C of the application server 3 acquires the pre-change menu table 42MNA (see FIG. 5A) from the database server 4, and displays the URL management screen 120a based on the pre-change menu table 42MNA. Generate. The application server 3 stores the pre-change menu table 42MNA in advance in a storage area (or version management AP storage unit 32B (see FIG. 2)) (not shown) of the storage unit 32 (see FIG. 2) of the application server 3. In addition, when the URL management screen 120a is generated in S160a, the pre-change menu table 42MNA stored in the storage unit 32 may be used.

  After S160a, upon receiving the URL management screen 120a from the application server 3 (S165a), the version number setting device 5 displays the URL management screen 120a on a display unit (not shown) (S170a).

  After S170a, the administrator who operates the version number setting device 5 adds or corrects URL data if there is a point to be changed in data included in the URL management screen 120a (hereinafter referred to as “URL data”). , Change processing such as deletion. Here, as shown in the URL management screen 120b shown in FIG. 14B, the administrator uses the fifth level data (see FIG. 14A) with respect to the URL data displayed on the URL management screen 120a (see FIG. 14A). That is, the version number is “trial version”, the business name is “seal verification”, and the URL is “http: // innkannV3”) and the sixth stage data (ie, the version number is “trial”). Version ”, business name“ pay-in / out ”, and URL“ http: // moneyV3 ”) are additionally registered.

  When all the change processes to be executed are completed, the administrator presses the “Register” button displayed on the URL management screen 120a. In response to this, the version number setting device 5 accepts the input of the changed URL data (S175a), and the input URL including the accepted URL data (hereinafter referred to as “input URL data”). A data registration request is transmitted to the application server 3 (S180a).

  After S180a, when the application server 3 receives the input URL data registration request from the version number setting device 5 (S185a), the version number management unit 31C (see FIG. 2), the version number management AP storage unit 32B (FIG. 2). In accordance with the version number management AP stored in (Ref.), The database server 4 is instructed to register the input URL data (S190a).

  After S190a, in the database server 4, the data management unit 41B (see FIG. 3) registers the input URL data in the menu table storage unit 42B (see FIG. 3) of the database 43 (S195a). As a result, the menu table 42MNA (see FIG. 5A) registered in the menu table storage unit 42B has the version number “trial version”, the business name “seal verification”, and the URL “http”. URL data with “: //...innkannV3”, URL data with version number “trial”, business name “pay-in / out”, and URL “http: // moneyV3” The updated menu table 42MNB (see FIG. 5B) is updated. At this time, the URL data whose version number is “trial version” and the business name is “seal verification”, the version number is “trial version”, and the business name is “payment / withdrawal”. When the URL data is registered in the menu table 42MNA, the data management unit 41B of the database server 4 overwrites the input URL data on the already registered URL data.

  After S195a, the data management unit 41B of the database server 4 transmits a signal indicating that data registration is completed (hereinafter referred to as “registration completion signal”) to the application server 3 (S200). Thereafter, the application server 3 and the version number setting device 5 execute the processes of S205 to S220, similarly to the flow shown in FIG. As a result, a series of processing ends.

(Business execution processing)
Next, business execution processing will be described with reference to FIGS. Here, a bank employee who works at the branch 6 (see FIG. 1A) with the store number “3456” becomes the user of the client terminal device 7 (see FIG. 1A) with the terminal number “ABCD” and accesses the application server 3. A description will be given assuming that the application server 3 operates in accordance with various application files 32CAP and 32DAP stored in the business AP storage unit 33 (see FIG. 2).

Here, as a precondition, it is assumed that a store number and a terminal number are uniquely assigned to each client terminal device 7.
An icon for acquiring a menu screen from the application server 3 (hereinafter referred to as “menu screen acquisition icon 205a”) is displayed on the initial screen 205 (see FIG. 15) of each client terminal device 7. And

  The Web application system 1 starts processing when a user working at the branch 6 (see FIG. 1A) with the store number “3456” activates the client terminal device 7 (see FIG. 1A). Here, it is assumed that the application server 3 and the database server 4 are already activated.

  First, as shown in FIG. 9, the client terminal device 7 displays an initial screen 205 (see FIG. 15) (S505). At this time, the client terminal device 7 displays a screen including the menu screen acquisition icon 205a as the initial screen 205 (see FIG. 15).

  When the user presses the menu screen acquisition icon 205a (see FIG. 15), the client terminal device 7 starts an application program for accepting the menu screen acquisition (S510), and stores the store number “3456” and the terminal as terminal data. A menu screen transmission request (hereinafter referred to as “menu screen request”) including the machine number “ABCD” is transmitted to the application server 3 (S515).

  After S515, when the application server 3 receives a menu screen request from the client terminal device 7 (S520), the menu screen generation unit 31B (see FIG. 2) stores it in the menu screen generation AP storage unit 32A (see FIG. 2). In accordance with the generated menu screen generation AP, the store number “3456” and the terminal number “ABCD” included in the received menu screen request as terminal data are transmitted to the database server 4, and the terminal data is transmitted to the database server 4. Is instructed to search for the version number of each application file corresponding to (S525).

  After S525, the database server 4 causes the data management unit 41B (see FIG. 3) to manage the version number of the database 43 using the store number “3456” and the terminal number “ABCD” included in the terminal data as keys. The version data of the corresponding application file is obtained from the version management master table 42VC (here, the version management master table 42VCB shown in FIG. 4B) registered in the master table storage unit 42A (see FIG. 3). Search is performed (S530), and it is determined whether there is version number data in which both the store number and the terminal number match (S535).

  If it is determined in S535 that there is version data that matches both the store number and the terminal number (in the case of “Yes”), the process proceeds to S540, while the store number and the terminal number. If it is determined that there is no version number data that coincides with each other (in the case of “No”), the process proceeds to S545.

  If it is determined in S535 that there is version data that matches both the store number and the terminal number (in the case of “Yes”), the data management unit 41B of the database server 4 determines the store number and the terminal number. The version data of the application file corresponding to both of the numbers is transmitted to the application server 3 (S540). Here, the data management unit 41B of the database server 4 transmits to the application server 3 data representing “trial version”, which is the version of the application file corresponding to both the store number “3456” and the terminal number “ABCD”. To do.

  On the other hand, if it is determined in S535 that there is no version number data that matches both the store number and the terminal number (in the case of “No”), the data management unit 41B of the database server 4 has the store number. It is determined whether there is version number data that matches and the terminal number is “ZZZZZZZ” (S545).

  If it is determined in S545 that there is corresponding version data (in the case of “Yes”), the data management unit 41B of the database server 4 sets the version data of the corresponding application file to the default of the store. The version number data is transmitted to the application server 3 (S545). In this case, the data management unit 41 </ b> B of the database server 4 transmits data representing the version number of the application file corresponding to the store number “3456” to the application server 3.

  On the other hand, if it is determined in S545 that there is no version number data with the same store number (in the case of “No”), the data management unit 41B of the database server 4 determines the standard version number data of the application file. Is transmitted to the application server 3 (S555). In this case, the data management unit 41B of the database server 4 represents data representing “normal version” which is the version number corresponding to the store number “ZZZ” and the terminal number “ZZZZZ” shown in FIG. 4B of the application file. Is transmitted to the application server 3 as default version number data of all stores.

  Note that the processes of S540, S550, and S555 are performed for all business types. Here, the database server 4 executes the processing of S540, thereby displaying the data representing “trial version” as the version data of the “seal verification” application file, and the version of the application file of “deposit / withdrawal”. It is assumed that data representing “trial version” is transmitted as data.

  After any of the processes of S540, S550, and S555, as shown in FIG. 10, the application server 3 receives the version data of the application file from the database server 4 (S560). Here, the application server 3 receives data representing “trial version” from the database server 4 as version data of the application file of “seal verification”, and “trial” as version data of the application file of “deposit / withdrawal”. It is assumed that data representing “version” has been received.

  After S560, in the application server 3, the menu screen generation unit 31B (see FIG. 2) causes the application file 3 version data (in accordance with the menu screen generation AP stored in the menu screen generation AP storage unit 32A (see FIG. 2)) Here, the version data representing the “trial version” corresponding to the “seal verification” application file and the version data representing the “trial version” corresponding to the “payment / withdrawal” application file are transmitted to the database server 4. Then, the database server 4 is instructed to search the URL of each application file corresponding to the version number data of the application file (S565).

  After S565, in the database server 4, the menu registered in the menu table storage unit 42B (see FIG. 3) of the database 43 by the data management unit 41B (see FIG. 3) using the version number data of the application file as a key. The URL data of the corresponding application file is searched from the table 42MN (here, the menu table 42MNB shown in FIG. 5B) (S570), and each application corresponding to the version number data for each business type (business name). The URL data of the file is transmitted to the application server 3 (S575). Here, the data management unit 41B of the database server 4 uses “http: // innkannV3” corresponding to the version number “trial version” and the business name “payment / withdrawal” as URL data of the business name “seal verification”. As the URL data, “http: // moneyV3” corresponding to the version number “trial version” is transmitted to the application server 3.

  After S575, when the application server 3 receives the URL data of each application file from the database server 4 (S580), the menu screen generation unit 31B (see FIG. 2) displays the menu screen generation AP storage unit 32A (see FIG. 2). The HTML data of the menu screen 210 (see FIG. 16) is dynamically generated based on the URL data of the application file in accordance with the menu screen generation AP stored in (S585). At this time, the URL data received from the database server 4 is associated (linked) with each business type (business name) included in the menu screen 210 formed based on the HTML data.

  When the menu screen generation unit 31B of the application server 3 generates the HTML data of the menu screen 210, the menu screen generation unit 31B transmits the generated HTML data of the menu screen 210 to the client terminal device 7 that has transmitted the menu screen request in S515 (S590). .

  After S590, when the client terminal device 7 receives the HTML data of the menu screen 210 from the application server 3 (S595), the menu screen 210 (see FIG. 16) formed based on the HTML data is displayed on a display unit (not shown). Display (S600).

  When the user selects and presses an arbitrary business item from the business items (business names) included in the menu screen 210, the client terminal device 7 accepts the execution of the selected business item (S605). . In this case, the client terminal device 7 accesses the address specified by the URL associated with the selected and pressed business type. The user operates the client terminal device 7 to execute a desired job. As a result, a series of processing ends.

  As described above, according to the application server 3 according to the present embodiment, a suitable version number is automatically and appropriately adapted to the client terminal device 7 operated by the user without making the user aware of the version number of the application file. Can work according to the application file.

Also, since the application server 3 registers a plurality of versions of application files, the old version of the application file and the new version of the application file are registered together rather than being replaced.
Therefore, the application server 3 can solve the problem of the conventional application server that once a new version of an application file is registered, it cannot be immediately restored to the old version of the application file.

In the Web application system 1 according to the present embodiment, the version number of the application file provided by the database 43 to each client terminal device 7 is registered as the version number management master table 42VC. 5 can be appropriately performed on the version number of the application file registered in the database 43 by performing a change process such as addition, correction, or deletion.
Therefore, according to the Web application system 1, the version number of the application file corresponding to each client terminal apparatus 7 can be easily changed.

In the Web application system 1, the old version application file and the new version application file are registered in the application server 3, not replaced. In the Web application system 1, since the database 43 registers URLs corresponding to the application files of each version as the menu table 42MN, the administrator operates the version setting device 5 to register the URL in the database 43. Change processing such as addition, correction, and deletion can be appropriately performed on the URL.
Therefore, according to the Web application system 1, the URL corresponding to each application file can be easily changed.

  When the Web application system 1 provides the client terminal device 7 with the menu screen 210 (see FIG. 16), the URL data associated with each business type included in the menu screen 210 is updated from the new version. It can be easily changed to the old version. Therefore, according to the Web application system 1, even if a new version application file is provided to the client terminal device 7, the new version application file provided to the client terminal device 7 is sent to the user by the old version application file. You can get the file back immediately.

  Further, according to the Web application system 1, the user can immediately return the new version application file provided to the client terminal device 7 to the old version application file. Even if a failure occurs as a result of registration in the application server 3, the failure can be recovered early.

  Further, according to the Web application system 1, version data of application files corresponding to all client terminal devices 7 can be registered in the database server 4, and the data can be easily changed by the version number setting device 5. Therefore, it is possible to realize data management for operating according to a different version of the application file for each client terminal device 7 at a low cost.

The present invention is not limited to the above-described embodiment, and various changes and modifications can be made without departing from the gist of the present invention.
For example, the menu screen 210 shown in FIG. 16 does not display URL data corresponding to each business type, but may display URL data corresponding to each business type.

  Further, for example, in the application server 3, the application file is configured as a program file, and the menu screen generation unit 31B causes the menu screen 210 (FIG. 16) to download the specific version number of the program file to the client terminal device 7. The job execution unit 31D may provide the client terminal device 7 with a specific version program file specified by the address data (URL) transmitted from the client terminal device 7. In the case of this configuration, the specific version program file is downloaded by the client terminal device 7 and executed by the client terminal device 7.

  In the above-described embodiment, the version number is determined for each client terminal device 7, but the version number is managed for each operator by using an operator ID instead of the “terminal number”. It may be. In this way, even when the operator freely selects the terminal to be used, the operator can perform work with the application of the version number suitable for the operator.

  In the above embodiment, the menu screen is generated by HTML data in which the link destination (URL) for each version number is changed. However, the URL is fixed and the store number and the terminal number are used as URL parameters. When the application file is accessed from the client terminal device 7, the version number to be used is identified based on the store number and the terminal number, and the URL of the application file corresponding to the identified version number It may be determined and transferred. In this case, instead of (or in addition to) the menu screen generation unit 31B, an access destination determination unit that performs the processing described above may be provided. The mechanism for determining the version number used for each terminal by the access destination determination unit and the mechanism for determining the access destination for each version may be the same as those of the menu screen generation unit 31B. A menu screen including a fixed link destination may be prepared in advance, or may be generated by a menu screen generation unit. By distributing the access destinations according to the specified version numbers in this way, it is possible to achieve the same effects as in the above embodiment.

DESCRIPTION OF SYMBOLS 1 Web application system 2 Central management center 3 Application server 4 Database server 5 Version number setting apparatus (PC)
6 Branches 7 Client terminal equipment (PC)
8 Network 9 Storage media (memory, CD-ROM, DVD, etc.)
9a Application server control program 31, 41 Control unit (CPU)
31A, 41A Main control unit 31B Menu screen generation unit 31C Version number management unit 31D Business execution unit 31DA Seal verification unit 31DB Deposit / withdrawal unit 31E, 41E Communication control unit 32, 42 Storage unit (RAM, ROM, HDD, etc.)
32A menu screen generation AP storage unit 32AAP menu screen generation AP
32B version management AP storage unit 32BAP version management AP
32C Seal verification AP storage unit 32CAP (32Ca, 32Cb, 32Cc) Seal verification AP
32D Deposit / withdrawal AP storage unit 32DAP (32Da, 32Db, 32Dc) Deposit / withdrawal AP
33 Business AP storage unit 41B Data management unit 42A Menu table storage unit 42B Version management master table storage unit 42VC Version management master table 42MN Menu table 43 Database

Claims (15)

In an application server that receives address data from one or more terminal devices connected via a network and operates according to an application file specified by the address data,
A storage unit for storing multiple versions of an application file corresponding to each business line;
A menu screen for displaying each job type on the terminal device so that the job can be selected and designated, and each job type and the address data are associated with each other. A menu screen generator for generating a menu screen for transmitting the address data corresponding to the event to the application server;
A version number management unit for managing the version number of the application file corresponding to each business type for each terminal device;
Business execution that operates according to a specific version number of application files specified by the address data transmitted from the terminal device from among the plurality of version application files stored in the storage unit corresponding to each business type And
The menu screen generation unit
The version number of the application file corresponding to each terminal device is set as the specific version number, and the version number of the application file corresponding to each business type managed by the version number management unit for each terminal device. Accordingly, the menu screen is generated by associating each business type with the address data for accessing the application file of the specific version number stored in the storage unit, and the generated menu screen is displayed on the respective menu items. An application server that transmits to a terminal device. The application server according to claim 1,
The application file is configured as an HTML file,
The application server, wherein the address data is URL data. In the application server according to claim 1 or 2,
The application file is configured as a program file,
The menu screen generation unit
As a screen for causing the terminal device to download a program file of a specific version number, the menu screen is generated,
The business execution unit
The specific specified by the address data transmitted from any of the terminal devices by selecting a specific item from the one or more business items included in the menu screen displayed on the terminal device An application server that transmits a program file of a version number to the terminal device that has transmitted the address data. In the application server according to any one of claims 1 to 3,
It is connected to a database server that stores various data,
The version number management unit
An application server, wherein a version number management master table for managing a version number of the application file corresponding to each business type is stored in the database server for each terminal device. In the application server according to claim 4,
The version number management unit
An application server, wherein a menu table for managing the address data is stored in the database server for each version of the application file. In the application server according to claim 5,
The version number management unit
Based on the version management master table stored in the database server, the version number of the application file corresponding to each terminal device is identified as the specific version number,
The menu screen generation unit
Based on the menu table stored in the database server, for each terminal device, each business item is associated with the address data for accessing the specific version of the application file stored in the storage unit. And generating the menu screen. In the application server according to any one of claims 1 to 3,
In addition, it has a database that stores various data,
The version number management unit
An application server, wherein a version number management master table for managing the version number of the application file corresponding to each business type is stored in the database for each terminal device. In the application server according to claim 7,
The version number management unit
A menu table for managing the address data is stored in the database for each version number of the application file. The application server according to claim 8,
The version number management unit
Based on the version number management master table stored in the database, the version number of the application file corresponding to each terminal device is identified as the specific version number,
The menu screen generation unit
Based on the menu table stored in the database, for each terminal device, each business type is associated with the address data for accessing the application file of the specific version number stored in the storage unit. An application server for generating the menu screen. In the application server according to any one of claims 1 to 9,
Connected to a version number setting device for setting the version number of the application file,
The version number management unit
A version number management screen on which the specific version number of the application file corresponding to each terminal device is displayed is generated, and the generated version number management screen is transmitted to the version number setting device. Application server. The application server according to any one of claims 1 to 10,
Connected to a version number setting device for setting the version number of the application file,
The version number management unit
Generating an address management screen on which the plurality of versions of the application file and the address data corresponding to each of the application files are displayed, and transmitting the generated address management screen to the version number setting device; Application server. In an application server that receives address data from one or more terminal devices connected via a network and operates according to an application file determined by the address data,
A storage unit for storing multiple versions of an application file corresponding to each business line;
When receiving the address data from the terminal device, an access destination determination unit that determines an application file to be accessed by the terminal device;
A version number management unit for managing the version number of the application file corresponding to each business type for each terminal device;
Business execution that operates according to a specific version number of application files specified by the address data transmitted from the terminal device from among the plurality of version application files stored in the storage unit corresponding to each business type And
The access destination determination unit
The version number of the application file corresponding to each terminal device is set as the specific version number, and the version number of the application file corresponding to each business type managed by the version number management unit for each terminal device. In response, the application server determines an access destination by associating each business type with the address data for accessing the specific version of the application file stored in the storage unit. An application that receives address data from one or more terminal devices connected via a network to a computer in which a plurality of versions of application files corresponding to each business line is stored in the storage unit, and is designated by the address data A program that functions as an application server that operates according to a file,
The computer,
A menu screen for displaying each job type on the terminal device so that the job can be selected and designated, and each job type and the address data are associated with each other. A menu screen generator for generating a menu screen for transmitting the address data corresponding to the event to the application server;
A version number management unit for managing the version number of the application file corresponding to each business type for each terminal device;
Business execution that operates according to a specific version number of application files specified by the address data transmitted from the terminal device from among the plurality of version application files stored in the storage unit corresponding to each business type Function as a part,
The menu screen generation unit
The version number of the application file corresponding to each terminal device is set as the specific version number, and the version number of the application file corresponding to each business type managed by the version number management unit for each terminal device. Accordingly, the menu screen is generated by associating each business type with the address data for accessing the application file of the specific version number stored in the storage unit, and the generated menu screen is displayed on the respective menu items. A program characterized by being transmitted to a terminal device. An application that receives address data from one or more terminal devices connected via a network to a computer in which a plurality of versions of application files corresponding to each business line is stored in the storage unit, and is designated by the address data A program that functions as an application server that operates according to a file,
The computer,
A storage unit for storing multiple versions of an application file corresponding to each business line;
When receiving the address data from the terminal device, an access destination determination unit that determines an application file to be accessed by the terminal device;
A version number management unit for managing the version number of the application file corresponding to each business type for each terminal device;
Business execution that operates according to a specific version number of application files specified by the address data transmitted from the terminal device from among the plurality of version application files stored in the storage unit corresponding to each business type Function as a part,
The access destination determination unit
The version number of the application file corresponding to each terminal device is set as the specific version number, and the version number of the application file corresponding to each business type managed by the version number management unit for each terminal device. Accordingly, a program for determining an access destination by associating each business type with the address data for accessing the application file of the specific version number stored in the storage unit. An application server according to any one of claims 1 to 12,
Address indicating the correspondence between each version of the terminal device and the version number of the application file, and the correspondence between the version of the application file and the address data for accessing the application file A database in which data management tables are registered, and
A Web application system comprising: a setting device that performs data change processing on the version number management table and the address data management table registered in the database.

Images