JP2009140072A - Server system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problem that it is not possible to share any file between actions in continuously processing several actions defined at the server side in a server/client type system. <P>SOLUTION: In a server system, a file to be shared by a certain action is temporarily stored in a place where it is accessible from the other action, and the information of the storage place of the file is stored in a session so that the file can be shared between actions. ID or operating circumstances unique to the file as well as the storage place of the file are stored in the session. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a file sharing method between actions in a server / client type system.

  In a server / client type system, there is a mechanism for continuously processing several actions defined on the server side. The actions were executed continuously according to the request from the client side, and the information of the previously processed actions could be passed on to the next action.

Further, as a session management apparatus including a monitoring unit that monitors the state of a session and an update unit that updates a session management method, a technique described in Patent Document 1 below is known.
JP 2000-222353 A

  However, each action is implemented as an independent component, and no interface is provided for the actions to pass files to each other. Therefore, it was not possible to implement a means that required sharing files between actions.

  An action temporarily stores a file to be shared in a location that can be accessed by other actions, stores information on the storage location of the file in a session, and shares it between actions. In addition to the file storage location, the session also stores a unique ID and work status for the file.

  By referring to the information stored in the session, you can access the same file from different actions, so you can share the file between actions. Even if requests are received from a plurality of users at the same time, they can be managed separately by IDs assigned to files. In addition, the information stored in the session can be used to manage the working status of the file, and to delete the temporary file when the process is interrupted.

  Next, details of the present invention will be described in accordance with the description of the embodiments.

  FIG. 1 is a configuration diagram of an information content browsing system according to an embodiment of the present invention.

  This information content browsing system includes client PCs 101, 102, and 103, an HTTP server (Web server) 108, and a Web application server (WAS) 109 on a network.

  The client PCs 101, 102, and 103 are computers that communicate using HTTP using a Web browser. For example, a system administrator performs a maintenance operation of contents or a system maintenance process such as correction of user management information. A computer used to do.

  LANs (local area networks) 105 and 107 and the Internet 106 represent network forms used in the system, and the devices 101 to 102 connected to the LAN 105 exchange data with other devices via the LAN 105. . The client PC 103 is directly connected to the Internet 106.

  An HTTP server (Web server) 108 is a server that receives a request transmitted from the client PCs 101, 102, and 103 by the HTTP protocol via a network. Several Web application servers are registered in the HTTP server 108, and the HTTP server 108 allocates processing to an appropriate Web application server in accordance with the request contents from the client PCs 101, 102, and 103. In addition, for example, the Web application server 109 that has received the request executes processing and returns the processing result to the client PCs 101, 102, and 103.

  A database 110 is connected to the web application server 109. The database 110 records content data, data associated with the content, operation history, information such as processing status, and system information such as user / group information. The HTTP server 108, the web application server 109, and the database 110 are organically combined to function as a web database system.

  The Web application server 109 is connected to a back-end system (customer management system) 111 such as a company via the LAN 107, for example, and realizes a form in which content data is used in this back-end system. Note that the back-end system 111 may be configured to be directly connected to the application server 109.

  FIG. 2 is a block diagram showing the configuration of the client PCs 101, 102, 103, HTTP server 108, and Web application server 109 shown in FIG.

  Reference numeral 201 in the figure denotes a system bus. The system bus 201 includes a CPU (Central Processing Unit) 202, a program memory (PMEM) 203, a communication control unit 204, an external storage device control unit 208, an input control unit 211, and a video. An image memory (VRAM) 214, a display output control unit 215, a printer control unit 217, an external device control unit 219, and an image reading device control unit 220 are connected. The communication control unit 204 controls input / output data at the communication port 205, and a signal output from the communication port 205 is transmitted to a communication port of another device 206 on the network via a communication line. The external storage device control unit 208 controls access to, for example, the USB memory 209 or the hard disk (HD) 210 as a data file disk.

  Input devices such as a keyboard 212 and a mouse 213 are connected to the input control unit 211. The operator issues a system operation command and the like by operating the input device. A display 216 is connected to the video image memory (VRAM) 214 via the display output control unit 215, and data displayed on the display 216 is expanded as bitmap data on the VRAM 14. A mouse 213 which is a pointing device for instructing to process image information on the display 216 moves the cursor on the display 216 arbitrarily in the X and Y directions, selects a command icon on the command menu, and instructs processing. In addition to the above, an edit target instruction, a drawing position instruction, and the like are also provided.

  The PMEM 203 appropriately selects and reads a program for executing the processing according to the present embodiment from the hard disk 210 and uses it for execution by the CPU 202. Data input from the keyboard 212 is stored as code information in the PMEM 203 which is also a text memory. The printer control unit 217 controls data output to the connected printer 218. The image reading device control unit 220 is connected to the image reading device 221 and controls the connected device. The external device control unit 219 is for controlling external devices such as a printer and a scanner. In the client PCs 101, 102, and 103 according to the present embodiment, components such as the printer 218 and the printer control unit 217, the image reading device control unit 220, and the image reading device 221 that are directly connected to the client PC are not necessarily required.

  Although the present embodiment describes a network such as a LAN, it goes without saying that the present invention is applicable even if the communication port 205 and the communication line connected to the communication control unit 204 are general public lines. . In addition, even if the image reading device control unit 220 and the image reading device 221 are physically separate components, even if the image reading device control unit 220 is a single component including the image reading device 221, the same means can be used. I will have it. The program stored in the PMEM 203 is stored in a storage medium such as a hard disk (HD) or USB memory that is directly connected to the apparatus, or is stored on another apparatus connected via a network. Also good.

  In the client PCs 101, 102, and 103, a general-purpose Web browser is stored in a storage medium. The CPU 202 reads and executes the Web browser program, and the user interface of the present invention is realized on the Web browser.

  3 and 4 are flowcharts showing the processing of the first embodiment.

  The processing flow will be described with reference to the flowchart of FIG.

  A session is started (S302), a request from the user is received by the action (S302), the action starts processing (S303), a temporary file is stored in a temporary folder (S304), and a temporary file such as an identifier or a file path Information is stored in the session (S305), it is determined whether a temporary file needs to be passed to the next action (S306), and if necessary, the action ends processing (S307), and the next action is processed. Is started (S308), temporary file information is acquired from the session (S309), a temporary file is acquired from the temporary folder based on the temporary file information (S310), and the processing result of the action is reflected in the temporary file (S311). , S312, and in S305, it is necessary to pass the temporary file to the next action. If the no action returns the processing result to the user (S312), the action is terminated the process (S313), and disconnects the session (S314), and terminates this flow.

  The flow of session disconnection processing will be described with reference to the flowchart of FIG.

  When the session is disconnected, the temporary file is deleted from the temporary folder according to the temporary file information (S401), the temporary file information is deleted from the session (S402), and this flow ends.

  5 and 6 are diagrams illustrating sharing of a temporary file between a PDF output action for outputting a PDF document and a PDF overlay action for overlaying a PDF document in the first embodiment.

  FIG. 5 is an overall view of an example in which a temporary file is shared between a PDF output action for outputting PDF and a PDF overlay action for overlaying PDF in the first embodiment.

  In FIG. 5, reference numeral 501 denotes a client user who is a user who uses the system of this embodiment on the client side, 502 denotes a PDF output action for outputting a PDF document, and 503 denotes a plurality of PDF documents. 504 is a temporary folder for storing a temporary file, 505 is a session for managing a series of processes caused by a client user request, and 506 is a PDF output A PDF file which is a temporary file stored in the temporary folder by the action, and 507 is temporary file information necessary for handling the temporary file stored in the session.

  FIG. 6 is a diagram showing the contents of temporary file information necessary for handling a temporary file stored in a session.

  In FIG. 6, 601 is an ID for identifying each temporary file, 602 is a file path indicating the location where each temporary file is stored, and 603 is a working state indicating the state of each temporary file.

  Hereinafter, the sharing of the temporary file shown in FIGS. 5 and 6 will be described with reference to the flowcharts shown in FIGS.

  In S301 of FIG. 3, the session 505 is started. In S302, the PDF output action 502 receives a request from the client user 501, and in S303, the PDF output action 502 starts processing and outputs a PDF document. In step S305, the PDF output action 502 stores the output PDF document in the temporary folder 504 as the PDF file 506. In step S305, the temporary file information 507 that is information on the PDF file 506 is stored in the session 505. Generates and records a unique number, records the location where the PDF file 506 is stored for the file path 602, and subsequently processes the PDF overlay action 503 for the work state 603. In step S306, since the PDF output action 502 needs to pass the PDF file 506 to the PDF overlay action 503, the process proceeds to step 307. In step S307, the PDF output action 502 performs processing. In step S308, the PDF overlay action 503 starts processing. In step S309, the PDF overlay action 503 acquires the temporary file information 507 from the session 505. In step S310, the PDF overlay action 503 receives the temporary file information. The PDF file 506 is acquired based on the information of 507, the PDF document is superimposed, the processing result is reflected in the PDF file 506 in S311, and the process returns to S306. Since there is no action to be processed subsequent to the application 503, the process proceeds to S312. In S312, the PDF overlay action 503 returns the superimposed PDF file 506 to the client user 501, and in S313, the PDF overlay action In step S314, the session 505 is disconnected. In step S401, the PDF file 506 is deleted from the temporary folder 504 according to the temporary file information 507. In step S402, the session 505 is temporarily deleted. The file information 507 is deleted, the processing in FIG. 4 ends, the processing returns to FIG. 3 and the processing ends.

  If the session is cut off during the above process, the temporary file and the temporary file information are deleted according to the process of FIG.

  When returning control to the client user 501 once, in S305, the work state 603 records that the request is waiting, returns a PDF file 506 as a temporary processing result to the client user 501, and returns a PDF merge action. 502 is terminated, a request for execution of the PDF overlay action 503 is prompted, the request is waited, and when a request for continuation processing is received, the process proceeds to S308 to start processing of the PDF overlay action 503, and a request is received from the client user 501 If there is a cancel request, the session is disconnected, the temporary file and the temporary file information are deleted according to the process of FIG. 4, and the process is terminated.

  In this way, by sharing the information of the temporary file on the session, the file can be shared and handled between actions. Even if requests are received from a plurality of users at the same time, they can be managed separately by IDs assigned to files. In addition, the information stored in the session can be used to manage the working status of the file, or to delete the temporary file when processing is interrupted.

  Note that content described in this specification refers to document data, image data, text data, music data, video data, and other electronic data that can be handled by an information processing apparatus. The content handled varies depending on the actual system. In the music distribution system, main contents are music files and accompanying document data, and in the catalog creation system, image data and text data are contents.

  Next, it is assumed that the Web page is described in HTML. However, the present invention can be easily realized even when a markup language that can describe the Web page and a similar language such as XML HTML that conforms to XML are used. The present invention is effective regardless of the description language of the Web page. Similarly, the advantage of the present invention is maintained when a dynamic page generation means is used.

  An action refers to a means defined on the server side and provided in response to an instruction from the client side in a server / client type system.

  Further, in the embodiment of the present invention, the storage medium storing the program code of the software that realizes the means described in the embodiment is read by the computer (or CPU or MPU) of the system or apparatus reading the program code stored in the storage medium. Including cases achieved by executing.

It is a block diagram of the information content browsing system which concerns on embodiment of this invention. FIG. 2 is a block diagram illustrating configurations of client PCs 101, 102, and 103, an HTTP server 108, and a Web application server 109 illustrated in FIG. It is a flowchart which shows the flow of the cutting process of a session. It is a flowchart explaining the flow of a process of combined action. FIG. 10 is an overall view of an example in which a temporary file is shared between a PDF output action and a PDF overlay action. It is the figure which showed the contents of temporary file information.

Explanation of symbols

501 Client user using the system on the client side 502 PDF output action for outputting a PDF document 503 PDF overlay action for overlaying a plurality of PDF documents into one 504 Temporary folder for storing temporary files 505 Caused by a client user request Session 506 for managing a series of processes PDF file 507 which is a temporary file stored in a temporary folder by a PDF output action 507 Temporary file information necessary for handling the temporary file stored in the session

Claims (4)

A server system that performs processing in response to a request from a client,
A presentation layer that accepts user requests,
It consists of a business logic layer that processes user requests received via the presentation layer,
Means for executing a combination of a plurality of processes in the business logic layer,
Means for generating processing result data as a temporary file when executing the combination processing;
Means for passing processing information on the processing result data as processing session information between processing;
Each process of the business logic that has received the above session information, according to the process information,
A server system comprising means for processing the processing result data. The server system according to claim 1,
A server system comprising means for managing a flow of processing by including a work state in processing information for processing result data. In the server system according to claim 1 or 2,
What is claimed is: 1. A server system comprising means for managing allocation of temporary files for processing when processing is simultaneously executed for requests from a plurality of clients. In the server system according to any one of claims 1 to 3,
A server system comprising means for deleting processing information for the processing result data when a client requests interruption of processing.

Images