JP5808484B2 - Program, information processing apparatus and data providing method - Google Patents

Description

  The present invention relates to a program, an information processing apparatus, and a data providing method.

  Currently, an information processing system in which a client device is connected to a server device via a network is used. In some information processing systems, a client device acquires screen information provided by a server device, and a GUI (Graphical User Interface) based on the screen information can be used on the client device. For example, a client device equipped with a Web browser communicates with a server device equipped with a Web server function using HTTP (HyperText Transfer Protocol), and acquires an HTML (HyperText Markup Language) file. The client device presents a GUI corresponding to the HTML file to the user using a Web browser.

  As the client device, for example, an electronic device such as a portable type or a tablet type may be used. There are various electronic devices having different specifications. For example, there are various screen sizes. For this reason, if the GUI provided by the server device is used as it is in the electronic device, the operability may be poor. In addition, the GUI may not be used as it is.

  Therefore, there is a proposal to provide a content conversion device between the client device and the server device (see, for example, Patent Document 1). By using the content conversion device, the content provided by the server device is converted according to the type of the client device, so that one content can be used by various client devices.

JP 2003-16001 A

  When converting screen information, it is conceivable to perform conversion by giving a common rule to a plurality of screen information. However, the method of converting according to a common rule has a problem that it is not easy to make flexible adjustments corresponding to individual screen information.

  For example, the common rule may be changed to a rule suitable for a certain business screen. However, the rule change is not necessarily suitable for other business screens. The rule change may worsen the usability of other business screens.

  SUMMARY An advantage of some aspects of the invention is that it provides a program, an information processing apparatus, and a data providing method capable of easily flexibly adjusting screen information.

In order to solve the above problems, a program executed by a computer is provided. This program generates a setting change for each tag for the second screen information including the tag, which is generated based on the first screen information including the tag and the first rule for changing the first screen information. Is received, the second rule including the information indicating the first screen information and the content of the setting change for each tag is generated and stored in the storage unit, and the first rule acquired from the first device is stored. When the screen information is provided to the second device, the storage unit is referred to search for a second rule including information indicating the first screen information, and the first screen information and the first rule are searched. generating a third screen information based on the second rule retrieved and, the place of the first screen information, and providing a third screen information to the second device, the first device If the acquired first screen information is not acquired, the first screen information is stored in the storage means. Ri and held, as a generation source of the information of the second screen information when generating the second rule, using the first screen information held in the storage means, to execute the processing to the computer.

Moreover, in order to solve the said subject, an information processing apparatus is provided. This information processing apparatus includes a storage unit and a calculation unit. The storage unit stores first screen information including a tag. For each tag for the second screen information including a tag generated based on the first screen information stored in the storage unit and the first rule for changing the first screen information. When an input for setting change is received, a second rule including information indicating the first screen information and the content of the setting change for each tag is generated, stored in the storage unit, and acquired from the first device. When providing the first screen information to the second device, the storage unit is referred to search for a second rule including information indicating the first screen information, and the first screen information and Third screen information is generated based on the first rule and the searched second rule, and the third screen information is provided to the second device instead of the first screen information. When the first screen information acquired from the first device is not acquired, the arithmetic unit holds the first screen information in the storage unit and generates second rule information when generating the second rule. As the generation source information, the first screen information held by the storage unit is used.

Moreover, in order to solve the said subject, the data provision method performed by information processing apparatus is provided. In this data providing method, the information processing apparatus generates a second screen including a tag generated based on the first screen information including a tag and the first rule for changing the first screen information. When an input of setting change for each tag with respect to information is received, a second rule including information indicating the first screen information and the content of setting change for each tag is generated and stored in the storage unit, and the first device When providing the first screen information acquired from the second device to the second device, the second rule including the information indicating the first screen information is searched with reference to the storage means, Third screen information is generated based on the screen information, the first rule, and the searched second rule, and the third screen information is provided to the second device instead of the first screen information. If the first screen information acquired from the first device is not acquired, the first The screen information is held by the storage means, as a generation source of the information of the second screen information when generating the second rule, using the first screen information held by the storage means.

Adjustment of screen information can be easily made flexible.
These and other objects, features and advantages of the present invention will become apparent from the following description taken in conjunction with the accompanying drawings which illustrate preferred embodiments by way of example of the present invention.

It is a figure which shows the information processing apparatus of 1st Embodiment. It is a figure which shows the information processing system of 2nd Embodiment. It is a figure which shows the hardware example of a conversion server. It is a figure which shows the software example of a conversion server. It is a figure which shows the example of the HTTP request which a client transmits. It is a figure which shows the example of data memorize | stored in a memory | storage part. It is a figure which shows the example of a former HTML table. It is a figure which shows the example of a screen conversion rule table. It is a figure which shows the example of a components conversion rule table. It is a figure which shows the example of an original HTML file. It is a figure which shows the example of the HTML file after default conversion. It is a figure which shows the example of the HTML file after individual conversion. It is a figure which shows the example of an individual conversion rule registration screen. It is a figure which shows the example of a screen conversion rule setting screen. It is a figure which shows the example of a components conversion rule setting screen. It is a flowchart which shows the example of the process between clients. It is a flowchart which shows the example in the case of accessing a Web server. It is a flowchart which shows the example of HTML conversion. It is a flowchart which shows the example of preparation of an individual conversion rule.

Hereinafter, the present embodiment will be described with reference to the drawings.
[First Embodiment]
FIG. 1 is a diagram illustrating the information processing apparatus according to the first embodiment. The information processing device 1 is connected to the first device 2 and the second device 3 via a network.

  The information processing apparatus 1 may include a processor such as a CPU (Central Processing Unit) and a memory such as a RAM (Random Access Memory), or may be a computer that executes a program stored in the memory. The information processing apparatus 1 may include an electronic circuit such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the function of the information processing apparatus 1 may be realized by the electronic circuit. Similarly to the information processing apparatus 1, the first apparatus 2 and the second apparatus 3 may be a computer or an electronic apparatus that includes a processor and a memory (or includes an FPGA, an ASIC, or the like).

The first device 2 distributes screen information. The screen information includes a tag indicating a component (hereinafter referred to as a screen component) to be displayed on the screen. The screen information is, for example, an HTML file.
The second device 3 displays a screen based on the screen information on a display device built in the second device 3 or a display device externally attached to the second device 3. For example, the second device 3 includes a web browser. The Web browser generates a screen based on the HTML file and displays it on the display device.

The information processing apparatus 1 includes a storage unit 1a and a calculation unit 1b.
The storage unit 1a stores various data used by the calculation unit 1b. For example, the storage unit 1 a stores first screen information acquired from the first device 2. The first screen information is original screen information. For example, the first screen (not shown) can be generated based on the first screen information using a predetermined browser.

  The computing unit 1b allows input of setting change for each tag with respect to the second screen information 4 including the tag generated based on the first screen information and the first rule for changing the screen information. . The first rule is a rule commonly used for a plurality of screen information. The first rule may be stored in advance in the storage unit 1a. The calculation unit 1b may generate the second screen information 4 from the first screen information using the first rule. For example, the computing unit 1b adds a predetermined tag indicating a screen component to the first screen information based on the first rule. Further, for example, the computing unit 1b changes the attribute set in the tag included in the first screen information based on the first rule.

  For example, it is assumed that tags A, B, and C are included in the first screen information. For example, the tag Z is added based on the first rule. The tag Z reads an external definition file (for example, a style sheet) and adjusts the shape and arrangement of the screen components included in the first screen. In this way, the second screen information 4 is generated based on the first screen information. This process can also be referred to as a process for generating the second screen information 4 by performing a default conversion on the first screen information according to the first rule.

  The second screen 5 is an example of a screen generated by a predetermined browser based on the second screen information 4. The second screen 5 includes screen components 5a, 5b, and 5c. The screen component 5 a corresponds to the tag A in the second screen information 4. The screen component 5 b corresponds to the tag B in the second screen information 4. The screen component 5 c corresponds to the tag C in the second screen information 4.

  For example, the computing unit 1b may display a GUI for supporting input of setting changes for each tag on a display device connected to the information processing device 1. For example, a screen based on the first screen information (original screen information) and the second screen 5 are displayed side by side, selection input of each screen component, and attributes (size, color, font, arrangement, etc.) of each screen component You may support the setting change. The computing unit 1b may be capable of previewing the second screen 5 by reflecting the contents of the setting change. This is to support an efficient operation by the user who changes the setting.

  When accepting the setting change for each tag with respect to the second screen information 4, the calculation unit 1b generates a second rule including information indicating the first screen information and the contents of the setting change for each tag, and the storage unit 1a. To store. The information indicating the first screen information is identification information for uniquely identifying the first screen information. For example, it is conceivable to use a title or a predetermined identifier described in the HTML file as the identification information.

  For example, when accepting a setting change to be deleted for the tag B included in the second screen information 4, the calculation unit 1 b sets a second rule including information indicating the first screen information and the content of the setting change. Generated and stored in the storage unit 1a. Further, when accepting a setting change for adding the setting C1 to the tag C included in the second screen information 4, the computing unit 1b receives information indicating the first screen information and the content of the setting change. Are generated and stored in the storage unit 1a.

  When the computing unit 1b provides the first screen information acquired from the first device 2 to the second device 3, the computing unit 1b refers to the storage unit 1a and includes information indicating the first screen information. Search for the second rule. For example, when the calculation unit 1b receives a predetermined request for the first screen information from the second device 3, the computing unit 1b accesses the first device 2 on behalf and obtains the first screen information from the first device 2. Get from.

  And the information which shows 1st screen information is acquired from the said 1st screen information, The 2nd rule containing the said information is searched. In the above example, there is a second rule including information indicating the first screen information and the content of setting change (deletion) for the tag B. Further, there is a second rule including information indicating the first screen information and setting change contents (addition of attributes) to the tag C. Therefore, the computing unit 1b searches for and extracts these second rules.

  The computing unit 1b generates the third screen information 6 based on the first screen information acquired from the first device 2, the first rule, and the searched second rule. In the above example, there is a second rule that deletes the tag B included in the second screen information 4. Therefore, the calculation unit 1b deletes the tag B in the second screen information 4. As a second rule, there is a rule that adds a setting C1 to a tag C included in the second screen information 4. Therefore, the calculation unit 1b adds the setting C1 to the tag C in the second screen information 4. However, the tag having the second rule may be controlled so as not to apply the first rule. This is because the conversion process can be made more efficient. In this way, the calculation unit 1b generates the third screen information 6. In the above example, there is no second rule regarding the tag A.

  The calculation unit 1b first applies the second rule to the first screen information (after adding / changing the attribute of each tag by the second rule), and then the second rule. The first rule may be applied to tags that are not applicable. The third screen information 6 can also be generated by such a procedure.

  The third screen 7 is an example of a screen generated by a predetermined browser based on the third screen information 6. The third screen 7 includes screen components 7a and 7b. The screen component 7 a corresponds to the tag A in the third screen information 6. The screen component 7 b corresponds to the tag C in the third screen information 6. Since the tag B is deleted, there is no screen component corresponding to the screen component 5b on the third screen 7.

  For example, the screen parts 5a and 7a have the same display because there is no setting change for the tag A. Further, the screen component 7b is enlarged in size in the vertical and horizontal directions than the screen component 5c due to the setting change to the tag C (addition of the setting C1).

  According to the information processing apparatus 1, the calculation unit 1b accepts an input of a setting change for each tag for the second screen information 4 including the tag, which is generated based on the first screen information and the first rule. It is done. Then, a second rule including information indicating the first screen information and the contents of the setting change for each tag is generated by the calculation unit 1b and stored in the storage unit 1a. When the first screen information acquired from the first device 2 is provided to the second device 3 by the computing unit 1b, the storage unit 1a is referred to and information indicating the first screen information is displayed. The second rule that contains it is searched. The calculation unit 1b generates the third screen information 6 based on the first screen information, the first rule, and the searched second rule. Instead of the first screen information, the calculation unit 1b provides the third screen information 6 to the second device 3.

  Thereby, adjustment of screen information can be made flexible easily. Specifically, in addition to the first rule that is commonly applied to a plurality of screen information (a plurality of first screen information) acquired from the first device 2, a second for each screen information Since the rule is created, the screen components and the like can be adjusted for each screen information without changing the first rule. For this reason, for example, it is possible to flexibly perform rule setting suitable for a certain business screen while suppressing the influence on other business screens.

  At this time, control may be performed so that the first rule is not applied to the screen component to which the second rule is applied. As a result, the rule application process can be made more efficient. For example, if a rule is applied twice, the first applied rule is updated with the next applied rule, and the process of applying the first rule becomes useless and inefficient.

[Second Embodiment]
FIG. 2 illustrates an information processing system according to the second embodiment. The information processing system according to the second embodiment includes clients 30 and 40, a conversion server 100, a Web server 200, and a management terminal device 300. The clients 30 and 40 and the conversion server 100 are connected via the network 10 and the relay device 20. The conversion server 100, the web server 200, and the management terminal device 300 are connected via the network 10.

The network 10 may be a LAN (Local Area Network). The network 10 may be a wide area network such as the Internet or a WAN (Wide Area Network).
The relay device 20 is a router that relays wireless or wired communication between the clients 30 and 40 and the network 10. The relay device 20 may be a radio base station that connects the mobile communication network included in the network 10 and the clients 30 and 40.

  The clients 30 and 40 are electronic devices used by users. The client 30 is, for example, a portable electronic device that includes a wireless or wired communication interface. The client 40 is a tablet electronic device having a wireless or wired communication interface. The clients 30 and 40 may function as mobile phones. The clients 30 and 40 may be client computers. The clients 30 and 40 may incorporate a display. An external display may be connected to the clients 30 and 40.

  The clients 30 and 40 have a web browser. The Web browser displays a GUI corresponding to the HTML file provided by the Web server 200 on the built-in (or external) display and presents it to the user. The user operates the displayed GUI to input data related to a predetermined job, or cause an AP (APplication) server (not shown) existing under the Web server 200 to execute a job process. can do.

  The conversion server 100 is a server computer provided between the clients 30 and 40 and the Web server 200. The conversion server 100 receives an HTTP request from the clients 30 and 40. The conversion server 100 accesses the Web server 200 by proxy, and acquires an HTML file corresponding to the HTTP request from the Web server 200. The conversion server 100 performs predetermined conversion on the HTML file and responds to the clients 30 and 40. For example, the conversion server 100 performs the conversion using different rules according to the models of the clients 30 and 40. The conversion server 100 may function as a reverse proxy server for the Web server 200 by caching the content distributed by the Web server 200.

  The web server 200 is a server computer having a web server function. The Web server 200 distributes an HTML file indicating a GUI related to a predetermined business. For example, the Web server 200 may be connected to an AP server that executes processing according to business. The Web server 200 may cause the AP server to execute processing according to data input using the GUI. For example, a DB (DataBase) server (not shown) for storing business data can be provided under the AP server, and the processing result of the AP server can be registered in the DB server. The HTML file distributed by the Web server 200 may be a prepared (static) HTML file or an HTML file dynamically generated by Servlet or the like.

  The management terminal device 300 is a client computer operated by an administrator of the information processing system. For example, the administrator can register a new conversion rule in the conversion server 100 by operating the management terminal device 300.

  FIG. 3 is a diagram illustrating a hardware example of the conversion server. The conversion server 100 includes a CPU 101, a RAM 102, an HDD (Hard Disk Drive) 103, an image signal processing unit 104, an input signal processing unit 105, a disk drive 106 and a communication unit 107. Each unit is connected to the bus of the conversion server 100. The clients 30 and 40, the Web server 200, and the management terminal device 300 can also be implemented using the same hardware as the conversion server 100.

  The CPU 101 is a processor that controls information processing of the conversion server 100. The CPU 101 reads out at least a part of the program and data stored in the HDD 103, expands it in the RAM 102, and executes the program. The conversion server 100 may be provided with a plurality of processors to execute the program in a distributed manner.

  The RAM 102 is a volatile memory that temporarily stores programs executed by the CPU 101 and data used for processing. Note that the conversion server 100 may include a type of memory other than the RAM, or may include a plurality of memories.

  The HDD 103 is a non-volatile storage device that stores programs such as an OS (Operating System) program and application programs and data. The HDD 103 reads / writes data from / to the built-in magnetic disk in accordance with instructions from the CPU 101. Note that the conversion server 100 may include a nonvolatile storage device of a type other than the HDD (for example, an SSD (Solid State Drive)) or a plurality of storage devices.

  The image signal processing unit 104 outputs an image to the display 11 connected to the conversion server 100 in accordance with an instruction from the CPU 101. As the display 11, for example, a CRT (Cathode Ray Tube) display or a liquid crystal display can be used.

  The input signal processing unit 105 acquires an input signal from the input device 12 connected to the conversion server 100 and outputs it to the CPU 101. As the input device 12, for example, a pointing device such as a mouse or a touch panel, a keyboard, or the like can be used.

  The disk drive 106 is a drive device that reads programs and data recorded on the recording medium 13. As the recording medium 13, for example, a magnetic recording device, an optical disk, a magneto-optical recording medium, or a semiconductor memory can be used. Examples of the magnetic recording device include an HDD, a flexible disk (FD), and a magnetic tape. Optical disks include CD (Compact Disc), CD-R (Recordable) / RW (ReWritable), DVD (Digital Versatile Disc), DVD-R / RW / RAM, and the like. Magneto-optical recording media include MO (Magneto-Optical disk). Semiconductor memory includes flash memory such as USB (Universal Serial Bus) memory. For example, the disk drive 106 stores the program and data read from the recording medium 13 in the RAM 102 or the HDD 103 in accordance with an instruction from the CPU 101.

  The communication unit 107 is a communication interface that communicates with the clients 30 and 40, the Web server 200, and the management terminal device 300 via the network 10. The communication unit 107 may be a wired communication interface or a wireless communication interface.

In the following description, a case where the client 30 accesses the Web server 200 via the conversion server 100 is illustrated, but the same applies to the case where the client 40 is used.
FIG. 4 is a diagram illustrating a software example of the conversion server. 4 may be a module of a program executed by the conversion server 100. Also, some or all of the units shown in FIG. 4 may be electronic circuits such as FPGA and ASIC. The conversion server 100 includes a storage unit 110, an access control unit 120, and a rule generation unit 130.

  The storage unit 110 stores an HTML file acquired from the Web server 200 by the access control unit 120. In addition, the storage unit 110 stores the conversion rules generated by the rule generation unit 130 based on the HTML file. The storage unit 110 stores the conversion rule in association with information indicating an HTML file.

  When receiving an HTTP request from the client 30, the access control unit 120 accesses the Web server 200 based on the HTTP request, and acquires an HTML file corresponding to the HTTP request from the Web server 200. The access control unit 120 applies conversion according to the client 30 to the HTML file acquired from the Web server 200 and transmits the converted HTML file to the client 30. The Web browser of the client 30 generates a GUI based on the converted HTML file and presents it to the user.

  The rule generation unit 130 generates a conversion rule for each HTML file stored in the storage unit 110 and stores the conversion rule in the storage unit 110. The rule generation unit 130 provides the management terminal device 300 with a GUI for supporting input of conversion rules. An administrator of the information processing system can input a conversion rule for each HTML file by operating the management terminal device 300.

  FIG. 5 is a diagram illustrating an example of an HTTP request transmitted by a client. FIG. 5A illustrates a URL (Uniform Resource Locator) 51. The URL 51 is an example of a URL that is designated as an access destination on the Web browser of the client 30. “Aaa.bbb.co.jp” is designated as the host name. The host name is an FQDN (Fully Qualified Domain Name) of the conversion server 100. As a path name, “http://xxx.yyy.co.jp/index.html” is specified. Among the path names, “xxx.yyy.co.jp” following the character string “http: //” is the FQDN of the Web server 200.

  FIG. 5B illustrates an HTTP request 52. The HTTP request 52 is an HTTP request issued by the Web browser when the URL 51 is input. Hereinafter, the contents will be described using a line number attached to the HTTP request 52 for convenience.

  The description “GET / xxx.yyy.co.jp / index.html HTTP / 1.1” of the line number “1” specifies the path name of the URL 51. However, the path name includes the FQDN “xxx.yyy.co.jp” of the Web server 200. For example, the access control unit 120 can determine that the access is an HTTP request for proxy access by detecting the second “http: //” included in the path name.

The description “Host: aaa.bbb.co.jp” of the line number “2” specifies the FQDN of the conversion server 100 that the client 30 is to access.
The description “USER-AGENT: mobile” in the line number “3” specifies identification information (client type) for identifying the model of the client 30. Here, since a portable electronic device is assumed as the client 30, information “mobile” indicating it is set. In the case of the client 40 that is a tablet-type electronic device, information that can identify the model, such as “tablet”, is set. Note that the size of the screen, the browser used, the OS, the user, and the like can be identified by information set in “USER-AGENT”.

  FIG. 6 is a diagram illustrating an example of data stored in the storage unit. The data stored in the storage unit 110 includes an original HTML table 111, default conversion rule information 112, individual conversion rule information 113, and a shared cache 114.

The original HTML table 111 is a table for storing an original HTML file acquired by the access control unit 120 from the Web server 200.
The default conversion rule information 112 is data defining rules that are commonly applied to a plurality of HTML files. The rule may be referred to as a default conversion rule. In addition, conversion of an HTML file based on a default conversion rule may be referred to as default conversion. The default conversion rule information 112 may be incorporated in a module for HTML conversion in the access control unit 120. For example, the default conversion rule information 112 is information specifying a style sheet to be applied or a JAVASCRIPT (registered trademark) file. The default conversion rule information 112 can be registered for each client type.

  The individual conversion rule information 113 is obtained by registering a conversion rule for each original HTML file. The individual conversion rule information 113 can be registered for each client type. The individual conversion rule information 113 includes a screen conversion rule table 113a and a component conversion rule table 113b.

The screen conversion rule table 113a defines conversion rules for each screen corresponding to one HTML file.
The component conversion rule table 113b defines conversion rules for each screen component included in one HTML file.

  The shared cache 114 is a set of content such as images distributed by the Web server 200, and files such as style sheets and JAVASCRIPT. Each file is managed for each URL of the Web server, for example. When the conversion server 100 receives a request for the Web server 200 from the client 30, the conversion server 100 acquires data from the shared cache 114 instead of the Web server 200 and responds on behalf of the server, thereby shortening the response time.

FIG. 7 is a diagram illustrating an example of the original HTML table. The original HTML table 111 includes items of content ID (IDentifier) and HTML file.
In the content ID item, identification information for identifying an HTML file is registered. In the HTML file item, the data body of the HTML file is registered. In FIG. 7, the data body is indicated by the file name of the HTML file (enclosed in parentheses).

For example, in the original HTML table 111, information that the content ID is “content X1” and the HTML file is “(search.html)” is registered.
FIG. 8 is a diagram illustrating an example of the screen conversion rule table. The screen conversion rule table 113a includes items of terminal type, content ID, default conversion target, theme, screen skip, and skip request.

  In the terminal type item, information indicating the type of client device is registered. In the content ID item, identification information for identifying an HTML file is registered. In the default conversion target item, a flag indicating whether or not to perform default conversion is registered. If the flag is “true”, it is a default conversion target. If the flag is “false”, it is not subject to default conversion. In the theme item, information for designating a theme such as a predetermined color tone is registered. In the screen skip item, a flag indicating whether to skip the screen corresponding to the HTML file is registered. If the flag is “true”, skip. If the flag is “false”, it is not skipped. In the item of request at the time of skip, a request for accessing the next screen is registered when the screen is skipped. If no screen is skipped, there is no setting.

  For example, in the screen conversion rule table 113a, the terminal type is “mobile”, the content ID is “content X1”, the default conversion target is “true”, the theme is “theme 1”, the screen skip is “false”, and the request at the time of skip Is registered as information “−”.

  When providing an HTML file indicated by “content X1” to a client device of terminal type “mobile”, the default conversion is performed, the theme specified by “theme 1” is applied, and the screen is skipped. It shows no. It should be noted that specific contents (such as a style sheet) of a theme corresponding to a character string such as “Theme 1” are given to the conversion server 100 in advance.

  Further, for example, in the screen conversion rule table 113a, the terminal type is “tablet”, the content ID is “content X1”, the default conversion target is “false”, the theme is not set “−” (hyphen), and the screen skip is “ “true”, information that the request at the time of skip is “POST menu_id = 0002” is registered.

  This is because when an HTML file indicated by “content X1” is provided to a client device of terminal type “tablet”, default conversion is not performed, there is no theme to apply, screen skip is performed, and then the Web server This indicates that a request to be transmitted to 200 is a POST request including “menu_id = 0002”.

  When screen skip is performed, the HTML file is not provided to the client device. For this reason, when the screen skip is “true”, the default conversion target and theme settings are invalid.

  FIG. 9 is a diagram illustrating an example of a component conversion rule table. The component conversion rule table 113b includes items of terminal type, content ID, tag ID, tag type, rule type, attribute, attribute value, pre-change character string, post-change character string, and conversion flag.

  In the terminal type item, information indicating the type of client device is registered. In the content ID item, identification information for identifying an HTML file is registered. In the tag ID item, a tag ID of a tag included in the HTML file is registered. The tag ID can be used as information for identifying the screen component to be converted. In the tag type item, information indicating what form the screen component indicated by the tag is is registered.

  Information indicating the type of conversion rule indicated by the record is registered in the rule type item. The rule type is represented by a numerical value such as “0”, “4”, “6”, for example. For example, rule type “0” is tab deletion. Rule type “4” is an attribute change. Rule type “6” is replacement of a character string registered in the form. In addition to this, a rule type indicating no change in form layout or conversion (no action) is included.

  In the attribute item, information indicating an attribute to be changed when the rule type is “4” is registered. In the attribute value item, when the rule type is “4”, the attribute value to be set to the attribute to be changed is registered.

  In the item of the character string before change, the character string before change is registered when the rule type is “6”. In the item of changed character string, the changed character string is registered when the rule type is “6”. In the conversion flag item, a flag indicating whether or not to perform individual conversion for each component is set. When the flag is “true”, individual conversion is performed in units of parts. When the flag is “false”, individual conversion for each part is not performed.

  For example, in the part conversion rule table 113b, the terminal type is “mobile”, the content ID is “content X1”, the tag ID is “in1”, the tag type is “input”, the rule type is “4”, and the attribute is “style”. ", The attribute value is" font-size: 25px; color: blue; ", the pre-change character string is"-", the post-change character string is"-", and the conversion flag is" true ".

  This indicates an individual conversion rule for each component applied to the tag indicated by the tag ID “in1” when the HTML file indicated by the “content X1” is provided to the client device whose terminal type is “mobile”. The tag type “input” indicates that the tag is an input form. The rule type “4”, the attribute “style”, and the attribute value “font-size: 25 px; color: blue;” indicate that the attribute value is set in the attribute “style” included in the tag. In the rule type “4”, the pre-change character string and the post-change character string are “−” without setting. Further, the conversion flag is “true”, individual conversion based on the record is valid, and the screen component is set to perform individual conversion.

  For example, in the component conversion rule table 113b, an attribute “clear” and an attribute value “true” are set for the record with the tag ID “in1”. This indicates that the clear attribute is set in addition to the style attribute. As described above, it is also possible to specify a plurality of attributes for one tag and define the setting contents of the attribute value for each attribute.

  Also, for example, in the component conversion rule table 113b, the rule type “0” is set for the record with the tag ID “in2”. This indicates that the tag indicated by the tag ID “in2” is deleted.

  Further, for example, the conversion flag “false” is registered in the component conversion rule table 113b for the record with the tag ID “bt1”. This is a setting in which individual conversion based on the record is invalid and individual conversion is not performed for the screen component.

  Further, for example, in the component conversion rule table 113b, for the record with the tag ID “se1”, the tag type is “selection”, the rule type is “6”, the pre-change character string is “long character string selection item”, Information that the post-change character string is “item” is registered. The tag type “selection” indicates that the tag is a form for selecting an item value. The rule type “6”, the pre-change character string “long character string selection item” and the post-change character string “item” replace the selection item value “long character string selection item” included in the tag with “item”. Indicates to do.

  FIG. 10 is a diagram illustrating an example of an original HTML file. FIG. 10A illustrates an HTML file 60. The HTML file 60 is an original HTML file distributed by the Web server 200. Hereinafter, the contents will be described using line numbers assigned to the HTML file 60 for convenience.

Line numbers “1” to “16” are portions surrounded by html tags and indicate the definition content of the HTML document.
Line numbers “2” to “4” are portions surrounded by head tags and indicate the definition content of the header of the HTML document. In the line number “3”, a title (a portion surrounded by a title tag) “content X1” is described. The title can be used as identification information of the HTML file 60. For example, information specified by a div tag may be used as identification information.

  Line numbers “5” to “15” are portions surrounded by body tags, and indicate the definition content of the text of the HTML document. Line numbers “6” to “8” define a text box for inputting text using an input tag (type = “text”). For example, in the case of the line number “6”, “set value 1” is set as the initial value (value), and “in1” is set as the tag ID (id). The line number “9” defines a button for receiving an input of a pressing operation using an input tag (type = “button”).

  Further, line numbers “10” to “14” define a selection form for selecting and inputting item values by pull-down using a select tag (type = “select”). “Se1” is set as the tag ID (id), and “1” is set as the item value (value) to be selected. Further, “long character string selection item 1” and the like are defined as display of item values.

  FIG. 10B illustrates a screen 70 corresponding to the HTML file 60. The screen 70 includes text boxes 71, 72, 73, buttons 74, and a selection form 75. The correspondence between each screen component and the HTML file 60 is as follows. The text box 71 is a screen component corresponding to the line number “6”. The text box 72 is a screen component corresponding to the line number “7”. The text box 73 is a screen component corresponding to the line number “8”. The button 74 is a screen component corresponding to the line number “9”. The selection form 75 is a screen component corresponding to the line numbers “10” to “14”.

  FIG. 11 is a diagram illustrating an example of an HTML file after default conversion. FIG. 11A illustrates an HTML file 61. The HTML file 61 is an HTML file after default conversion (first stage conversion) for the HTML file 60. Hereinafter, the contents will be described using line numbers given for convenience in the HTML file.

Line numbers “1” to “19” are portions surrounded by html tags, and indicate the definition content of the HTML document.
Line numbers “2” to “7” are portions surrounded by head tags, and indicate the definition contents of the header of the HTML document. Line number “3” defines meta information to be given to the Web browser. The line number “4” defines the title “content X1” of the HTML file 61. The title is the same as the HTML file 60. Line numbers “5” and “6” specify the default conversion rule to be applied. “Bsc.css” and “bsc.js” specified here are examples of the default conversion rule information 112.

Line numbers “8” to “18” are the same as line numbers “5” to “15” of the HTML file 60.
FIG. 11B illustrates a screen 80 corresponding to the HTML file 61. Screen 80 includes text boxes 81, 82, 83, buttons 84, and selection form 85. The correspondence between each screen component and the HTML file 61 is as follows. The text box 81 is a screen component corresponding to the line number “9”. The text box 82 is a screen component corresponding to the line number “10”. The text box 83 is a screen component corresponding to the line number “11”. The button 84 is a screen component corresponding to the line number “12”. The selection form 85 is a screen component corresponding to the line numbers “13” to “17”.

  Here, when the screens 70 and 80 are compared, the screen width of each screen component of the screen 80 is reduced compared to the screen components of the screen 70, and the vertical width is increased. Further, each screen component of the screen 80 has a rounded shape as compared with each screen component of the screen 70. Further, the button 84 and the selection form 85 are changed from the design of the button 74 and the selection form 75.

These changes reflect the changes made by the default conversion rules described above.
FIG. 12 is a diagram illustrating an example of an HTML file after individual conversion. FIG. 12A illustrates an HTML file 62. The HTML file 62 is an HTML file after individual conversion (second stage conversion) with respect to the HTML file 61. Hereinafter, the contents will be described using line numbers given for convenience in the HTML file.

Line numbers “1” to “18” are portions surrounded by html tags, and indicate the definition content of the HTML document.
The line numbers “2” to “7” are the same as the line numbers “2” to “7” of the HTML file 61.

  Line numbers “8” to “17” are parts surrounded by the body tag, and indicate the definition content of the body of the HTML document. Line numbers “9” to “11” define a text box for inputting text using an input tag (type = “text”). For example, in the case of the line number “9”, “set value 1” is set as the initial value (value), and “in1” is set as the tag ID (id). Further, “font-size: 25 px; color: blue;” is set as a style attribute (style). Furthermore, “true” is set as the clear attribute.

  Line numbers “12” to “16” define a selection form for selecting and inputting item values by pull-down using a select tag. Compared with the line numbers “10” to “14” of the HTML file 60, the display of the item value is shortened to “item 1” or the like.

  FIG. 12B illustrates a screen 90 corresponding to the HTML file 62. The screen 90 includes a text box 91, a button 92, and a selection form 93. The correspondence between each screen component and the HTML file 62 is as follows. The text box 91 is a screen component corresponding to the line number “9”. The button 92 is a screen component corresponding to the line number “11”. The selection form 93 is a screen component corresponding to the line numbers “12” to “16”.

  Here, when the text boxes 81 and 91 are compared, the text box 91 has a larger vertical width than the text box 81 and has a larger font size to be displayed. In addition, a clear icon 91a for deleting the displayed input value is added to the text box 91. For example, the user can delete the input displayed in the text box 91 by selecting the clear icon 91a with a pointer or the like.

  When the buttons 84 and 92 are compared, a check icon 92 a is added to the button 92. The check icon 92a can attract the user's attention, and the button 92 can make an impression that the input value can be confirmed.

  Further, when the selection forms 85 and 93 are compared, a short character string is displayed as a selection item on the selection form 93. In this way, even on a small screen, the selection items can be accommodated in one screen, and the visibility can be improved as compared with the case where a long selection item is displayed.

  The screen 90 does not include screen parts corresponding to the text boxes 82 and 83. This is because the tag corresponding to the text box 82 has been deleted from the HTML file 62. This is also because the screen part corresponding to the text box 83 is set to non-display in the line number “10” of the HTML file 62.

  FIG. 13 is a diagram illustrating an example of an individual conversion rule registration screen. The individual conversion rule registration screen 400 is displayed on a display (or a display connected to the management terminal device 300) built in the management terminal device 300.

  For example, based on the original HTML table 111 stored in the storage unit 110, the rule generation unit 130 provides the management terminal device 300 with a list of contents (original HTML files) for which conversion rules can be set. For example, if the list is provided in the HTML file format, the list can be displayed on a display (for example, externally attached) of the management terminal device 300 using a Web browser included in the management terminal device 300. When the management terminal device 300 receives selection of any content from the list by the administrator, the management terminal device 300 transmits the selection content to the rule generation unit 130.

  Then, the rule generation unit 130 provides the management terminal device 300 with an HTML file for generating the individual conversion rule registration screen 400 for the selected content. The Web browser included in the management terminal device 300 can display the individual conversion rule registration screen 400 on a display or the like built in the management terminal device 300 based on the HTML file.

  The individual conversion rule registration screen 400 includes a screen conversion button 401, a component conversion button 402, a delete button 403, a restore button 404, a non-target button 405, a target button 406, a target list button 407, a preview button 408, an apply button 409, and a reset. A button 410, a close button 411, an original screen display area 420, and a screen display area 430 after individual conversion. The administrator can operate the pointer P using an input device connected to the management terminal device 300 to press each button or select a specific item in the area. The management terminal device 300 transmits the operation content for the individual conversion rule registration screen 400 to the rule generation unit 130.

  A screen conversion button 401 is a button for displaying a screen unit conversion rule setting screen. The screen unit conversion rule setting screen is a screen that supports the setting of the screen unit conversion rule for the HTML file being displayed in the original screen display area 420. For example, when the rule generation unit 130 receives a press input of the screen conversion button 401, the rule generation unit 130 provides the management terminal device 300 with an HTML file for generating a screen unit conversion rule setting screen for the content displayed in the original screen display area 420. To do.

  The component conversion button 402 is a button for displaying a component unit conversion rule setting screen. The part unit conversion rule setting screen is a screen that supports the setting of the part unit conversion rule for the screen part selected in the original screen display area 420. For example, when a part conversion button 402 is pressed after a screen part to be set is selected in the original screen display area 420, a part unit conversion rule setting screen for the selected screen part can be displayed. For example, when receiving the pressing input of the component conversion button 402, the rule generation unit 130 provides the management terminal device 300 with an HTML file for generating a component unit conversion rule setting screen.

  The delete button 403 is a button for registering a rule for deleting the screen part selected in the original screen display area 420. When the rule generation unit 130 receives an input of pressing the delete button 403, the rule generation unit 130 provisionally registers the rule type “0” (delete) for the tag ID corresponding to the screen component in the component conversion rule table 113b.

  Here, provisional registration refers to recording only changes to the corresponding record of the component conversion rule table 113b in a predetermined storage area of the storage unit 110 without directly rewriting the component conversion rule table 113b. Meaning (hereinafter the same).

  The restore button 404 is a button for canceling (restoring) the rule for deleting the screen part selected in the original screen display area 420. When the rule generation unit 130 receives a pressing input of the restoration button 404, the rule generation unit 130 temporarily registers a rule type (eg, “1”) indicating that no conversion is performed for the tag ID in the component conversion rule table 113b.

  The non-target button 405 is a button for setting so that the component unit conversion rule is not applied to the screen component selected in the original screen display area 420. When the rule generation unit 130 receives a pressing input of the non-target button 405, the rule generation unit 130 provisionally registers the conversion flag “false” for the tag ID corresponding to the screen component in the component conversion rule table 113b.

  The target button 406 cancels the setting when the screen part selected in the original screen display area 420 is set to be out of the application target of the part unit conversion rule, and becomes the application target of the part unit conversion rule. It is a button for. When the rule generation unit 130 receives an input of pressing the target button 406, the rule generation unit 130 temporarily registers a conversion flag “true” for the tag ID corresponding to the screen component in the component conversion rule table 113b.

  The target list button 407 is a button for displaying a list of screen components displayed in the original screen display area 420 that are subject to application of the component unit conversion rule.

  A preview button 408 is a button for displaying a screen when the currently effective conversion rule including the temporarily registered individual conversion rule is applied to the original HTML file in the screen display area 430 after individual conversion. It is. Details of the process of the rule generation unit 130 when the pressing operation of the preview button 408 is received will be described later.

  The apply button 409 is a button for reflecting the provisionally registered setting change contents in the component conversion rule table 113b. When the rule generation unit 130 receives an input of pressing the apply button 409, the rule generation unit 130 reflects the provisionally registered setting change content in the component conversion rule table 113b. Thereby, the component conversion rule table 113b is updated. Of the individual conversion rules that are provisionally registered, those that have already been reflected in the component conversion rule table 113 b are deleted from the temporary registration storage area of the storage unit 110.

  A reset button 410 is a button for deleting temporarily registered individual conversion rule data. When the rule generation unit 130 receives an input of pressing the reset button 410, the rule generation unit 130 deletes the temporarily registered individual conversion rule data.

The close button 411 is a button for closing the individual conversion rule registration screen 400 and ending creation of the individual conversion rule.
The original screen display area 420 is an area for displaying a screen corresponding to the original HTML file. In the individual conversion rule registration screen 400, a “personal information search” screen is displayed.

  The original screen display area 420 includes text boxes 421, 422, 425, a selection form 423, a check box 424, a search button 426, and a clear button 427.

  A text box 421 is a form for inputting a name as a search key. A text box 422 is a form for inputting an employee number as a search key. The selection form 423 is a form for selecting and inputting an affiliation as a search key. The check box 424 is a form for setting whether or not to include the subordinate organization to which the affiliation selected in the selection form 423 is included in the search target. A text box 425 is a form for inputting a contact as a search key.

  The search button 426 is a button (a button is also included in the form) for executing a search using a search key input to each form in the original screen display area 420. The clear button 427 is a button for erasing all contents input to each form in the original screen display area 420.

  However, these forms function when the original screen is operated by the Web browser on the client 30, and each form can only be selected on the individual conversion rule registration screen 400. Specifically, when any form is selected by the pointer P, the selected form is surrounded by the cursor C1. In the individual conversion rule registration screen 400, the case where the text box 425 is selected is illustrated. For example, an individual conversion rule that deletes the text box 425 can be created by pressing the delete button 403 while the text box 425 is selected.

  The post-individual screen display area 430 is an area for displaying the post-individual conversion screen when the currently effective conversion rule is applied to the original HTML file. In the individual conversion rule registration screen 400, a “personal information search” screen is displayed. This corresponds to the “personal information search” screen displayed in the original screen display area 420.

The post-conversion screen display area 430 includes text boxes 431 and 432, a selection form 433, and a search button 434.
A text box 431 is a form for inputting a name as a search key. A text box 422 is a form for inputting an employee number as a search key. The selection form 433 is a form for selecting and inputting an affiliation as a search key. The search button 434 is a button for executing a search by using a search key input to each form in the screen display area 430 after individual conversion.

  Like the original screen display area 420, these forms function when the individual converted screen is operated by the Web browser on the client 30, and each form is displayed on the individual conversion rule registration screen 400. It can only be viewed. However, it is possible to confirm items that can be selected by inputting text or pull-down.

  Here, in the screen display area 430 after individual conversion, there is no form corresponding to the text box 425 and the clear button 427. This is because these forms have been deleted by the individual conversion rules. In addition, the form corresponding to the check box 424 does not exist in the screen display area 430 after individual conversion. This is because the check box 424 is fixed to ON by the individual conversion rule. A message M indicating that effect (“* subordinate organization is not searched”) may be displayed on the screen after individual conversion.

  Note that the screen component to be converted is selected in the original screen display area 420, but the screen component to be converted can be selected by selecting the screen component displayed in the screen display area 430 after individual conversion. Also good.

  FIG. 14 is a diagram illustrating an example of a screen conversion rule setting screen. The screen conversion rule setting screen 500 is a window that is newly displayed when the screen conversion button 401 is pressed. The screen conversion rule setting screen 500 includes check boxes 501 and 503, a selection form 502, a text box 504, a determination button 505, and a return button 506.

  A check box 501 is a form for setting whether or not to be a target of default conversion. When a check mark is input, it indicates that it is a target for default conversion. If the check mark is not entered, it indicates that it is not subject to default conversion. When the determination button 505 is pressed and pressed while the check mark is input in the check box 501, the rule generation unit 130 temporarily registers “true” for the default conversion target item in the screen conversion rule table 113a. On the other hand, when the enter button 505 is pressed down without a check mark being input to the check box 501, “false” is temporarily registered for the item.

  The selection form 502 is a form for selecting a theme. When the determination button 505 is pressed and input in a state where any theme is selected, the rule generation unit 130 temporarily registers the theme item in the screen conversion rule table 113a as the selected theme.

  The check box 503 is a form for setting whether or not to make a screen skip target. When a check mark is input, it indicates that the screen is to be skipped. When no check mark is input, it indicates that the screen is not to be skipped. When the determination button 505 is pressed and pressed while a check mark is input in the check box 503, the rule generation unit 130 temporarily registers “true” for the item of screen skip in the screen conversion rule table 113a. On the other hand, when the enter button 505 is pressed down without a check mark being input to the check box 503, “false” is provisionally registered for the item.

  A text box 504 is a form for inputting the content of a request to be transmitted to the Web server 200 when the screen is to be skipped. When the rule generation unit 130 receives a press input of the determination button 505, the rule generation unit 130 provisionally registers the contents set in the text box 504 for the item of request at the time of skip in the screen conversion rule table 113a. In the item, contents of the above-described POST request, a URL to be accessed next, and the like can be set. The value to be set is determined according to the business system.

The determination button 505 is a button for temporarily registering the contents input in each form of the screen conversion rule setting screen 500.
The return button 506 is a button for returning the content input to each form of the screen conversion rule setting screen 500 to a state immediately after the state where the screen conversion button 401 was pressed last time.

  FIG. 15 is a diagram illustrating an example of a component conversion rule setting screen. The component conversion rule setting screen 600 includes check boxes 601, 602, 608, 609, 610, text boxes 603, 604, 605, 607, a selection form 606, a determination button 611, and a return button 612.

  The check box 601 is a form for setting whether or not the currently selected screen component is to be subject to individual conversion for each component. When a check mark is input, it indicates that it is a target for default conversion. If the check mark is not entered, it indicates that it is not subject to default conversion. For example, when the determination button 611 is pressed and pressed while a check mark is input in the check box 601, the rule generation unit 130 temporarily registers “true” for the item of the conversion flag in the component conversion rule table 113b. On the other hand, when the enter button 611 is pressed down without a check mark being input to the check box 601, “false” is temporarily registered for the item.

  The check box 602 is a button for setting whether or not to hide the selected screen component. When a check mark is input, it indicates that it is not displayed. If no check mark is entered, it indicates that it is not hidden. For example, when the determination button 611 is pressed and pressed while a check mark is input in the check box 602, the rule generation unit 130 sets “4” as the rule type and “style” as the attribute of the component conversion rule table 113b. , “Display: none” is provisionally registered in the attribute value. Other attributes / attribute values may be used to hide the form. On the other hand, when the determination button 611 is pressed and input without a check mark being input to the check box 602, the setting of the attribute value is temporarily registered.

  A text box 603 is a form for inputting the font size of the font displayed in the currently selected screen component. For example, when the determination button 611 is pressed and pressed while a numerical value is input in the text box 603, the rule generation unit 130 sets “4” as the rule type and “style” as the attribute of the component conversion rule table 113b. “Font-size: (input numerical value) px” is provisionally registered as a value. On the other hand, when the enter button 611 is pressed and entered without entering a numerical value in the text box 603, a temporary registration of clearing the setting of the attribute value is made. In this case, the default font size is used.

  Hereinafter, the processing of the rule generation unit 130 for the setting contents of each form is the same as the check boxes 601, 602, the text box 603, and the like (predetermined settings in HTML are performed according to the setting contents). For this reason, a description of specific attribute values and the like is omitted for the following forms.

  A text box 604 is a form for setting the width of the currently selected screen component. A text box 605 is a form for setting the height of the currently selected screen component. The selection form 606 is a form for setting the color of the currently selected screen component. A text box 607 is a form for setting a value to be input from the beginning to the currently selected screen component.

  The check box 608 is a form for setting whether or not the initial value set in the text box 607 is fixed (cannot be changed). When a check mark is input in the check box 608, it is fixed (cannot be changed). On the other hand, when no check mark is input, it indicates that the check mark is not fixed (can be changed).

  The check box 609 is a form for setting whether or not to display a check mark (corresponding to the check icon 92a) on the currently selected screen component. When a check mark is input in the check box 609, this indicates that the check mark is displayed in the screen part. On the other hand, when the check mark is not input, it indicates that the check mark is not displayed in the screen part.

  The check box 610 is a form for setting whether or not the clear function can be used for the currently selected screen component. The clear function is a function that enables the character string in the screen part to be collectively deleted using the above-described clear icon 91a. When a check mark is input in the check box 610, it indicates that the clear function is used. When no check mark is input in the check box 610, it indicates that the clear function is not used.

The decision button 611 is a button for temporarily registering the contents input in each form of the component conversion rule setting screen 600.
The return button 612 is a button for returning the content input to each form of the component conversion rule setting screen 600 to a state immediately after the state where the component conversion button 402 was pressed last time.

  In the component conversion rule setting screen 600, a form for inputting a setting value for a presettable attribute is prepared. However, an arbitrary attribute and an input of a setting value for the arbitrary attribute or the arbitrary value It may be permitted to input the deletion of the attribute. For example, a form for selecting or newly inputting an arbitrary attribute and a form for inputting a setting value for the arbitrary attribute may be provided. Further, a form for deleting an arbitrary attribute that has been set may be provided. In this way, any attribute can be added or deleted later, and the part conversion rule can be set more flexibly.

Next, a processing procedure of the conversion server 100 having the above configuration will be described. First, a processing procedure when the conversion server 100 receives an HTTP request from the client 30 will be described.
FIG. 16 is a flowchart illustrating an example of processing with a client. In the following, the process illustrated in FIG. 16 will be described in order of step number.

  (Step S <b> 11) The access control unit 120 receives an HTTP request from the client 30. Note that, in the HTTP request received in step S11, the conversion server 100 is designated as a direct access destination and the Web server 200 is the final access destination, as described in FIGS. 5A and 5B. Is specified.

  (Step S12) The access control unit 120 checks the client type of the client 30 with reference to the setting of “USER-AGENT” included in the HTTP request.

  (Step S13) The access control unit 120 replaces the destination of the HTTP request so as to access the Web server 200. In the example when the HTTP request 52 is received, the contents of the line number “1” are replaced with “GET / index.html HTTP / 1.1”, and the contents of the line number 2 are replaced with “HOST: xxx.yyy. co.jp ".

  (Step S14) When there is a transmission parameter to be set for the HTTP request after replacement, the access control unit 120 sets the transmission parameter. Transmission parameters to be set in the HTTP request after replacement are given in advance to the conversion server 100 for each destination Web server, for example.

  (Step S15) The access control unit 120 determines whether it is possible to respond to the HTTP request from the file stored in the shared cache 114. If it is possible to respond from the shared cache 114, the process proceeds to step S16. If a response cannot be made from the shared cache 114, the process proceeds to step S18. For example, whether or not it is possible to respond from a file stored in the shared cache 114 can be determined by referring to the file format specified by the HTTP request. Specifically, if the specified file format is a cache target file format (.jpg, .css, .jsp, etc.), it is determined that the shared cache 114 can respond. If it does not correspond to these file formats, it is determined that the shared cache 114 cannot respond.

  (Step S16) The access control unit 120 determines whether or not the data specified by the HTTP request is in the shared cache 114. If the data is in the shared cache 114, the process proceeds to step S17. If the data is not in the shared cache 114, the process proceeds to step S18.

  (Step S <b> 17) The access control unit 120 acquires data specified by the HTTP request from the shared cache 114 and responds to the client 30. Then, the process ends.

  (Step S18) The access control unit 120 accesses the Web server 200 by proxy, and responds to an HTTP request from the client 30 based on the access result to the Web server 200.

  In this way, when the conversion server 100 can make a cache response to the HTTP request received from the client 30, the conversion performance is obtained by making a cache response to the HTTP request without accessing the Web server 200. To improve. On the other hand, when the cache response is not made, the proxy access is made to the Web server 200. Next, the process of step S18 will be specifically described.

FIG. 17 is a flowchart illustrating an example of accessing a Web server. In the following, the process illustrated in FIG. 17 will be described in order of step number.
(Step S21) The access control unit 120 sets an HTTP request header to be transmitted to the Web server 200, and generates the HTTP request.

(Step S <b> 22) The access control unit 120 transmits the generated HTTP request to the Web server 200.
(Step S23) The access control unit 120 receives a response to the HTTP request transmitted in Step S22 from the Web server 200.

  (Step S <b> 24) When the data included in the received response includes the file format to be cached, the access control unit 120 stores the data in the shared cache 114 in association with the URL of the HTTP request. . If the file format to be cached is not included, step S24 is skipped and the process proceeds to step S25.

  (Step S25) The access control unit 120 determines whether or not the received response is an unacquired HTML file. If it is an unacquired HTML file, the process proceeds to step S26. If it is an acquired HTML file, the process proceeds to step S27. The access control unit 120 can determine whether the HTML file has not been acquired by acquiring the content ID of the HTML file from the setting content of the title tag of the HTML file acquired from the Web server 200. If the content ID has already been registered in the original HTML table 111, the HTML file has been acquired. If the content ID is not registered in the original HTML table 111, the HTML file has not been acquired.

(Step S26) The access control unit 120 registers the HTML file acquired from the Web server 200 in the original HTML table 111 in association with the content ID.
(Step S27) The access control unit 120 performs HTML conversion based on the default conversion rule information 112 and the individual conversion rule information 113. Details will be described later.

  (Step S28) The access control unit 120 generates a response to the HTTP request from the client 30 by replacing the address included in the response received from the Web server 200. The HTML file included in the response is an HTML file after the HTML conversion process in step S27.

(Step S29) The access control unit 120 transmits the response after the address replacement to the client 30.
In this way, the conversion server 100 accesses the Web server 200 by proxy, and responds to the client 30 based on the response from the Web server 200. Next, the process of step S27 will be specifically described.

FIG. 18 is a flowchart illustrating an example of HTML conversion. In the following, the process illustrated in FIG. 18 will be described in order of step number.
(Step S31) Based on the individual conversion rule information 113, the access control unit 120 determines whether there is an individual conversion rule corresponding to the client type included in the HTTP request and the HTML file acquired from the Web server 200. To do. If there is an individual conversion rule, the process proceeds to step S32. If there is no individual conversion rule, the process proceeds to step S36. The access control unit 120 can determine the presence / absence of an individual conversion rule corresponding to the HTML file with reference to the terminal type and content ID items of the screen conversion rule table 113a and the component conversion rule table 113b. Specifically, when a record including the client type and the content ID acquired from the HTML file is registered in at least one of the screen conversion rule table 113a and the component conversion rule table 113b, there is an individual conversion rule. judge. If the record is not registered in both tables, it is determined that there is no individual conversion rule.

  (Step S32) The access control unit 120 acquires the individual conversion rule corresponding to the content ID of the HTML file from the individual conversion rule information 113. For example, if the client type is “mobile” and the content ID is “content X1”, the screen conversion rule including these is acquired from the screen conversion rule table 113a. Similarly, a plurality of component conversion rules including these are acquired from the component conversion rule table 113b.

  (Step S33) The access control unit 120 performs individual conversion on the HTML file acquired from the Web server 200 based on the acquired individual conversion rule. The specific contents of the conversion are as described in FIG.

  (Step S34) The access control unit 120 refers to the screen conversion rule table 113a and determines whether or not the HTML file is a default conversion target. If it is the default conversion target, the process proceeds to step S35. If it is not the default conversion target, the process ends. If the item of the default conversion target in the screen conversion rule table 113a is “true”, the access control unit 120 determines that it is the target of default conversion. On the other hand, if the item is “false”, it is determined that the item is not a default conversion target.

  (Step S35) The access control unit 120 refers to the default conversion rule information 112 and performs default conversion on the HTML file after individual conversion. Here, when there is a default conversion rule that converts each screen component individually, the default conversion rule is applied only to screen components that are not subject to the individual conversion rule. This is to avoid overwriting the conversion contents in the individual conversion rule. For example, when both the individual conversion rule and the default conversion rule exist for the text box 71, the individual conversion rule is preferentially applied. Then, the process ends.

  (Step S36) The access control unit 120 determines whether or not to perform default conversion for the Web system provided by the Web server 200. When performing default conversion for the Web system, the process proceeds to step S37. If default conversion is not performed for the Web system, the process ends. Information indicating whether or not to perform default conversion for the Web system provided by the Web server 200 is given to the conversion server 100 in advance.

  (Step S37) The access control unit 120 refers to the default conversion rule information 112 and performs default conversion on the HTML file acquired from the Web server 200.

  In this way, the conversion server 100 applies the individual conversion rule and the default conversion rule to the HTML file. Note that steps S32 and S33 may be executed after steps S34 and S35 are executed. In step S34, it is also conceivable that the conversion rule for each screen corresponding to the HTML file acquired from the Web server 200 is not registered in the screen conversion rule table 113a. In that case, the access control unit 120 may perform control so as to determine that the HTML file is a target of default conversion.

Next, a procedure for creating an individual conversion rule will be described. The processing procedure shown below is executed as needed according to access from the management terminal device 300.
FIG. 19 is a flowchart illustrating an example of creating an individual conversion rule. In the following, the process illustrated in FIG. 19 will be described in order of step number.

  (Step S <b> 41) The rule generation unit 130 receives selection of a setting target screen for individual conversion rules from the management terminal device 300. For example, the management terminal device 300 presents a list of HTML files (content IDs) provided by the rule generation unit 130 to the system administrator. The administrator can operate the management terminal device 300 to select any content ID and cause the rule generation unit 130 to transmit the selected content. Note that the rule generation unit 130 accepts selection of a client type (terminal type) along with selection of a setting target screen.

  (Step S <b> 42) The rule generation unit 130 provides the individual conversion rule registration screen 400 to the management terminal device 300. At this time, the rule generation unit 130 acquires an HTML file corresponding to the content ID from the original HTML table 111, and transmits the HTML file to the management terminal device 300. The management terminal device 300 can display the original screen in the original screen display area 420 of the individual conversion rule registration screen 400 based on the HTML file.

  (Step S43) The rule generation unit 130 determines the request content received from the management terminal device 300. If designation of an individual conversion rule is accepted, the process proceeds to step S44. If the designation of preview is accepted, the process proceeds to step S45. If confirmation of the individual conversion rule is accepted, the process proceeds to step S47. If an end instruction is accepted, the process ends. Here, the case where the designation of the individual conversion rule is accepted is a case where the delete button 403, the restoration button 404, the non-target button 405, the target button 406, the decision buttons 505, 611, and the like are pressed. The case where the designation of preview is accepted is a case where the preview button 408 is pressed down. The case where the confirmation of the individual conversion rule is accepted is a case where the apply button 409 is pressed. The case where the end instruction is accepted is a case where the close button 411 is pressed.

(Step S44) The rule generation unit 130 provisionally registers the specified individual conversion rule. The method for selecting a screen component to be converted is as described with reference to FIGS.
(Step S45) The rule generation unit 130 performs conversion on the selected HTML file based on the default conversion rule information 112, the individual conversion rule information 113, and the temporarily registered individual conversion rule. The processing procedure is the same as the procedure described in FIG. However, if there is a provisionally registered individual conversion rule, the provisionally registered individual conversion rule is preferentially applied as the individual conversion rule. That is, the individual conversion rule registered in the screen conversion rule table 113a or the component conversion rule table 113b is not applied to the corresponding screen component. This is because the preview is a function for confirming how the display method changes according to the provisionally registered individual conversion rule.

  (Step S46) The rule generation unit 130 transmits the converted HTML file to the management terminal device 300. Based on the converted HTML file, the management terminal device 300 can display the converted screen in the individual conversion screen display area 430 of the individual conversion rule registration screen 400.

  (Step S47) The rule generating unit 130 reflects the contents of the temporarily registered individual conversion rule in the screen conversion rule table 113a and the component conversion rule table 113b. At this time, if a record including the selected terminal type, content ID, tag ID, tag type, and rule type already exists in each table, the rule generation unit 130 changes the setting of the record. That's fine. On the other hand, when there is no existing record, the rule generation unit 130 may add a new record.

In this way, the rule generation unit 130 provides the management terminal device 300 with the original screen and the screen after applying the individual conversion rule.
In step S43, a pressing input of the reset button 410 may be accepted. In that case, the rule generation unit 130 discards the temporarily registered individual conversion rule. Moreover, you may transmit the HTML file after applying an individual conversion rule at the timing of step S42.

  In this way, the conversion server 100 uses the individual conversion rule information 113 for each screen component (tag included in the HTML file) with respect to the default conversion rule information 112 in which common rules are registered for a plurality of HTML files. Allow registration. Thereby, adjustment of screen information can be made flexible easily. That is, the screen components and the like can be adjusted for each client type and HTML file without changing the default conversion rule information 112. For this reason, for example, it is possible to flexibly perform rule setting suitable for a certain business screen while suppressing the influence on other business screens.

  At this time, control is performed so that the default conversion rule is not applied to the screen component to which the individual conversion rule is applied. As a result, the rule application process can be made more efficient. For example, if a rule is applied twice, the first applied rule is updated with the next applied rule, and the process of applying the first rule becomes useless and inefficient. However, when applying an individual conversion rule after applying a default conversion rule, it does not prevent applying a default conversion rule to a screen component to which an individual conversion rule is applied.

  Conventionally, it has been necessary to check the actual operation and usability by incorporating the image after applying the rules into the business system. On the other hand, the conversion server 100 can generate the individual rule registration screen 400 using the HTML file by accumulating the pre-conversion HTML file, so that the converted screen can be displayed without operating the business system. It becomes possible to confirm.

  In addition, to write conversion rules, specialized knowledge is required for the administrator, but since it is possible to visually confirm before / after conversion from the screen, conversion is easy even without specialized knowledge. Rules can be registered.

  In addition, for example, it is conceivable that an HTML file acquired in the past is used for the current request, or an HTML file after individual conversion is created in advance from an HTML file acquired in the past. However, in this case, it is not easy to handle a Web page that is dynamically created by Servlet or the like. This is because the dynamically created Web page can change depending on the content of the request. Therefore, the conversion server 100 registers individual conversion rules for each client type and content ID, acquires an HTML file each time there is a request from the Web server 200, and performs individual conversion. For this reason, it is possible to easily cope with a Web page dynamically created by Servlet or the like.

  The client type may include at least one of the size of the display provided in the client, the Web browser, the OS, and the user ID, in addition to the type of terminal device. In this case, the default conversion rule information 112 and the individual conversion rule information 113 can be registered in more detail for each client Web browser and user ID. Then, it is possible to finely adjust each screen according to the client type.

  Also, the conversion server 100 allows the individual conversion rule registration screen 400 to display the original screen and the screen after the individual conversion simultaneously for confirmation. Thereby, the manager who operates management terminal device 300 can perform creation work of an individual conversion rule efficiently, contrasting both. In particular, each screen component can be selected by the GUI, and an individual conversion rule can be registered only by inputting into a check box, a selection form, and a text box. For this reason, it is possible to save labor for creating an individual conversion rule by the administrator.

  The functions described above can also be realized by causing a computer to execute a predetermined program. The program can be recorded in a computer-readable portable recording medium 13. In order to distribute the program, for example, the recording medium 13 on which the program is recorded is distributed. Alternatively, the program may be stored in a server computer and transferred to the computer via a network. For example, the computer stores the program recorded in the recording medium 13 or the program acquired from the network in the nonvolatile storage medium of its own device. Then, the program is read from the nonvolatile storage medium and executed. For example, the program of the present invention is executed by a calculation unit such as a CPU provided in a computer. However, it is also possible for the computer to execute the acquired program sequentially in the RAM without storing it in the nonvolatile storage medium.

  The above merely illustrates the principle of the present invention. In addition, many modifications and variations will be apparent to practitioners skilled in this art and the present invention is not limited to the precise configuration and application shown and described above, and all corresponding modifications and equivalents may be And the equivalents thereof are considered to be within the scope of the invention.

DESCRIPTION OF SYMBOLS 1 Information processing apparatus 1a Memory | storage part 1b Calculation part 2 1st apparatus 3 2nd apparatus 4 2nd screen information 5 2nd screen 5a, 5b, 5c, 7a, 7b Screen components 6 3rd screen information 7 3rd 3 screen

Claims (11)

When an input of a setting change for each tag with respect to the second screen information including the tag generated based on the first screen information including the tag and the first rule for changing the screen information is received, A second rule including information indicating the screen information and the contents of the setting change for each tag is generated and stored in the storage means,
When the first screen information acquired from the first device is provided to the second device, the second means including the information indicating the first screen information is searched with reference to the storage means. The third screen information is generated based on the first screen information, the first rule, and the searched second rule, and the third screen information is replaced with the first screen information. Providing to the second device;
If the first screen information acquired from the first device is not acquired, the first screen information is held by the storage means, and the second screen information is generated when generating the second rule. As the original information, the first screen information held by the storage means is used.
A program that causes a computer to execute processing. When the first screen information acquired from the first device is provided to the second device, among the tags included in the first screen information, the tag to which the second rule is applied The program according to claim 1 , wherein control is performed so as not to apply the first rule. When an input of a setting change for each tag with respect to the second screen information including the tag generated based on the first screen information including the tag and the first rule for changing the screen information is received, A second rule including information indicating the screen information and the contents of the setting change for each tag is generated and stored in the storage means,
When the first screen information acquired from the first device is provided to the second device, the second means including the information indicating the first screen information is searched with reference to the storage means. The third screen information is generated based on the first screen information, the first rule, and the searched second rule, and the third screen information is replaced with the first screen information. Providing to the second device;
A rule including first screen information and information on a converted screen after applying at least one of the first rule and the second rule for the first screen information when receiving the setting change input To enter the information on the registration screen, the font size, form size, initial value of the input value, whether the initial value is fixed, whether the initial value is fixed, and whether the specified function that can be used in the form of the converted screen is used Information on the rule setting screen including the input form is displayed on the management device, the rule registration screen and the rule setting screen are displayed on the management device, and the input form included in the rule setting screen is displayed . In response to an operation input, an input of the setting change for each tag included in the first screen information is received.
A program that causes a computer to execute processing. The program according to any one of claims 1 to 3 , wherein the content of the setting change for each tag includes setting change, addition and deletion of an attribute in the tag. In addition to the input of the setting change for each tag to allow the input of the setting change for each screen information to generate a second rule that contains the contents of the setting change of each said screen information, any one of claims 1 to 4 The program according to item 1. The program according to any one of claims 1 to 5 , wherein the setting change content for each tag includes at least one of addition and deletion of a tag. The program according to any one of claims 1 to 6 , wherein the first screen information is acquired from the first device every time an access request for the first screen information is received from the second device. The first rule and the second rule are stored in the storage means in association with the type of the second device, and the access request includes information indicating the type of the second device,
When searching for the second rule, the second rule associated with both the information indicating the first screen information acquired from the first device and the information indicating the type of the second device. The program according to claim 7 , wherein the program is searched. The program according to any one of claims 1 to 8 , wherein the first rule is a rule for making a common change to a plurality of pieces of screen information. A storage unit for storing first screen information including a tag;
An input of setting change for each tag with respect to the second screen information including the tag generated based on the first screen information stored in the storage unit and the first rule for changing the screen information is received. Second information including the information indicating the first screen information and the content of the setting change for each tag, stored in the storage unit, and acquired from the first device Is provided to the second device, the second rule including information indicating the first screen information is searched with reference to the storage unit, and the first screen information, the first rule, based on the second rule retrieved to generate a third screen information, instead of the first screen information, and a calculator for providing the third screen information to the second device Have
When the first screen information acquired from the first device has not been acquired, the arithmetic unit holds the first screen information in the storage unit and generates a second rule. The first screen information held by the storage unit is used as the generation information of the screen information.
Information processing device. A data providing method executed by an information processing apparatus,
When an input of a setting change for each tag with respect to the second screen information including the tag generated based on the first screen information including the tag and the first rule for changing the screen information is received, A second rule including information indicating the screen information and the contents of the setting change for each tag is generated and stored in the storage means,
When the first screen information acquired from the first device is provided to the second device, the second means including the information indicating the first screen information is searched with reference to the storage means. The third screen information is generated based on the first screen information, the first rule, and the searched second rule, and the third screen information is replaced with the first screen information. Providing to the second device;
If the first screen information acquired from the first device is not acquired, the first screen information is held by the storage means, and the second screen information is generated when generating the second rule. As the original information, the first screen information held by the storage means is used.
Data provision method.

Images