JP2005190193A - Information processor, information processing system, information processing method, program, and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To output corresponding respective output data in the receiving order of the data, to maintain also the multiplicity of output data generation processing and to avoid also the reduction of processing efficiency concerned with output data generation. <P>SOLUTION: At the time of receiving a document data file from a user terminal 11 through a LAN, a document server 12 generates a document preview file 17 for each received document data file, transmits the document preview file 17 to a print server 13 and sends an output request of the document preview file 17 to the print server 13 in accordance with data output order managed by a job management part 124 for managing the output order of data. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to an information processing apparatus, an information processing method, a program, and a recording medium for managing form data received from a user terminal via a communication network and outputting the data in a printing apparatus, for example.

  Usually, when printing a form, an operator inputs form data from a user terminal to a form server. Conventionally, a form server monitors form data input from a user terminal, performs form generation processing when the form data acquisition is completed, and issues a print instruction to the print server after the generation process is completed.

  Here, the form generation process in the form server is a system that performs parallel processing in order to improve processing efficiency, so form data is generated unless a large amount of form data is input in a short time to prevent parallel processing. There is no waiting state.

  Therefore, even if a plurality of form data are input almost simultaneously by the same or a plurality of operators, the form generation process is performed in parallel in the form server. In such a case, since print instructions are issued to the print server in order from the completion of the process, the print order does not necessarily match the order in which the operator inputs the form data.

  This is because if the file size of the form data that is first input to the form server is larger than the file size of the form data that is input next, the form data with a large file size takes longer to generate the form than the form data with a small file size. This is because the print instruction to the print server may be slower than the form data input later.

  However, in the case of a job that prints a form from the printer in a range that is intended by the operator or in a certain unit (for example, an invoice issuance work or an invoice issuance work), the forms are printed from the printer in the order of the entered form data. It is desirable. This is because it is necessary to check that the number of forms corresponding to the number of input form data are printed from the printer by comparing the instruction contents with the print results.

  However, as described above, depending on the file size of the form data, the order in which the form generation processing is executed is not guaranteed, and there is a problem that the matching work is very time-consuming.

  By the way, in order to satisfy this demand, it can be easily conceived that the multiplicity of the form generation processing is set to 1 and only one is executed at a time. However, if the form generation process is processed one by one in the order in which the input data is input, if the file size entered earlier is extremely large, the form data entered later waits for that process before the form is entered. Since the generation process is executed, the processing efficiency is extremely deteriorated. Patent Document 1 discloses a technique for providing a printing apparatus that processes a plurality of print jobs in an optimal order.

Japanese Patent Laid-Open No. 10-67146

  However, this is a technique for performing print processing in an optimal order by adopting a method of printing in the order of a job for which print data transfer from the host has been completed or a job for which intermediate code accumulation has been completed in the printing apparatus, It does not guarantee the printing order in the order in which form data is input from the user terminal to the form server.

  Accordingly, an object of the present invention is to enable output data corresponding to each in the order of data reception, maintain the multiplicity of output data generation processing, and reduce processing efficiency related to output data generation. It is another object of the present invention to provide an information processing apparatus, an information processing system, an information processing method, a program, and a recording medium that can be avoided.

  In order to achieve such an object, an information processing apparatus according to the present invention includes a data receiving unit that receives data from an external device via a communication network, and a job management that manages an output order of the data received by the data receiving unit. Means, output data generating means for generating output data for each data received in the data receiving means, output data transmitting means for transmitting output data generated by the output data generating means to an output device, Output request means for requesting the output device to output output data stored in the output device in accordance with the data output order managed by the job management means.

  An information processing system of the present invention is an information processing system in which at least an information processing device, an external device, and an output device are connected via a communication network, and the information processing device is connected to the external device via the communication network. Data receiving means for receiving data; job management means for managing the output order of data received by the data receiving means; output data generating means for generating output data for each data received by the data receiving means; Output data transmission means for transmitting output data generated by the output data generation means to the output device, and output of output data stored in the output device in accordance with the output order of data managed by the job management means Output request means for making a request to the output device To.

  An information processing method of the present invention is an information processing method by an information processing device, and includes a data reception step of receiving data from an external device via a communication network, and generating output data for each data received in the data reception step Output data generation step, output data transmission step for transmitting the output data generated by the output data generation step to the output device, and data output order managed by job management means for managing the data output order And an output requesting step of making an output request for output data stored in the output device to the output device.

  A program according to the present invention causes a computer to execute the information processing method. The computer-readable recording medium of the present invention is characterized in that the program is recorded.

  According to the present invention, the output order is managed in the job management means for each received data and the output request for the output data is made in accordance with the management contents. For example, the job management means responds to the data reception order. If the output order is managed, it becomes possible to output corresponding output data in the data reception order. Further, according to this method, since the multiplicity of the output data generation process can be maintained, it is possible to avoid a decrease in output data generation process efficiency.

  DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, preferred embodiments to which the invention is applied will be described in detail with reference to the accompanying drawings.

  In the form output system according to an embodiment of the present invention described below, in particular, a plurality of form data input from a user application (form application) in a user terminal is monitored by a form server, and based on the form data. After the form is generated, when the form preview file is transmitted to the print server and output to the printer, the order input from the user application in the user terminal is guaranteed.

  Also, it is possible to guarantee only the final output order regardless of the input order from the user terminal. In this case, the data can be output in the order designated by the user, or can be automatically output in the preset order.

<First Embodiment>
First, a first embodiment of the present invention will be described.
FIG. 1 is a diagram illustrating a configuration of a form output system according to the present embodiment. Note that the connection configuration of various servers on the network in FIG. 1 is merely an example, and it goes without saying that various configurations can be adopted according to applications and purposes.

  The form server 12 receives a form data file 15 input from the user application 111 in the user terminal 11 through a network such as a LAN, thereby accepting a print job and requesting a request for creating a form from the request management unit 122.

  The form generation unit 123 includes a plurality of form generation processes for processing the form generation in parallel, and the request management unit 122 requests an executable form generation process in the form generation unit 123 to generate a form. The form generation unit 123 generates the form preview file 17 in response to the request and transmits it to the print server 13.

  The print server 13 receives the form preview file 17 created by the form server 12 via the network. Furthermore, when the print server 13 receives a form instruction request from the print instruction unit 125 in the form server 12, the print server 13 instructs the printer 14 to output the stored form preview file 18.

  Next, the hardware configuration of the form server 12 and the print server 13 in FIG. 1 will be described with reference to FIG. FIG. 2 is a diagram illustrating a hardware configuration of the form server 12 or the print server 13 according to the present embodiment.

  The form server 12 or the print server 13 includes a CPU 21, a RAM (memory) 22, a ROM 23, a hard disk drive (HDD) 24, a recording medium drive 25, a network interface card (NIC) 29, a pointing device (P / D) 28, a keyboard ( K / B) 27 and a video adapter 26, which are connected to each other via a system bus.

  The CPU 21 controls various operations such as four arithmetic operations and comparison operations and hardware based on an operating system (OS) program and application programs.

  The RAM 22 temporarily stores an OS, application programs, and the like recorded in a storage device such as a hard disk drive (HDD) 24, a ROM 23, and other recording media (for example, CD-ROM, DVD, FD). The programs stored in the RAM 22 are executed under the control of the CPU 21.

  The ROM 23 stores a so-called BIOS or the like that controls input / output to / from an external storage device in cooperation with the OS. The hard disk drive (HDD) 24 stores an OS, a program for executing a customer charge arrangement method, and the like.

  The recording medium drive 25 is used for reading data from an application program or the like recorded on a recording medium such as a CD-ROM, DVD-ROM, or CD-R.

  A network interface card (NIC) 29 communicates with the outside through a network in cooperation with an OS communication program controlled by the CPU 21.

  A keyboard (K / B) 27 and a pointing device (P / D (for example, mouse)) 28 are used to input instructions to the information processing apparatus. The video adapter 26 is used to form an image to be displayed on the image display device.

  The file monitoring unit 121, the request management unit 122, the form generation unit 123, the job management unit 124, the print instruction unit 125, and the print data creation processing unit 131 and the storage processing unit 132 of the print server 13 in FIG. A functional configuration is such that a program is loaded into the RAM 22 as needed from the HDD 23, the ROM 23, another recording medium, and the like, and executed by the CPU 21. The form data file 15, the form execution file 16, and the form preview files 17 and 18 are recorded on a recording medium such as the HDD 24 of the form server 12 or the print server 13, respectively. This recording medium may be connected to the outside of the form server 12 and the print server 13.

Next, a basic processing flow of the form output system that guarantees the output order will be described with reference to FIG.
As described above, the user terminal 11, the form server 12, and the print server 13 are connected via a network such as a LAN. The form server 12 monitors the form data file 15 input from the user application 111 in the user terminal 11. When the form data file 15 is received, the form server 12 generates a form preview file 17 and transmits the generation result to the print server 13. The form server 12 manages the received job, and issues a form output instruction to the print server 13 in the order of input from the user terminal 11. The print server 13 accepts the request and instructs the printer 14 to output a form. One example will be described below.

  First, the form server 12 receives the form data file 15 transmitted from the user application 111 and stores it in the spool directory ((1) in FIG. 3). In FIG. 3, the spool directory is shown outside the form server 12, but may be configured inside.

  The file monitoring unit 121 monitors the spool directory at regular time intervals. When the form data file is stored in the spool directory, the file monitoring unit 121 acquires the file size ((2) in FIG. 3).

  When the form data file 15 is stored in the spool directory, the job management unit 124 receives a job reception notification from the file monitoring unit 121 ((3) in FIG. 3), and each form data file stored in the spool directory. A job number is assigned to 15 and a job list is created.

  When the file transfer from the user application 111 is completed, the file monitoring unit 121 moves the form data file 15 to a data directory (not shown) and issues a request for form generation to the request management unit 122 ((4 in FIG. 3). )).

  The request management unit 122 distributes processing to a form generation process that can be executed from the form generation unit 123 ((5) in FIG. 3).

  The form generation unit 123 creates a form preview file 17 from the form execution file 16 and the form data file 15 ((6) in FIG. 3). Subsequently, the form generation unit 123 transfers the created form preview file 17 to the print server 13 ((7) in FIG. 3).

  The print server 13 stores the transferred form preview file 18 by the storage processing unit 132 ((8) in FIG. 3).

  In response to the transfer of the form preview file 17 from the form generation part 123 to the print server 13, the job management part 124 of the form server 12 updates the status of the job list to “waiting for printing” (in FIG. 3). (12)).

  Based on the notification from the print server 13, the job management unit 124 determines a form data file to be printed from the job list, and requests the print data creation processing unit 131 to output a form (in FIG. 10)).

  The print data creation processing unit 131 instructs the printer 14 to output a form based on the output instruction from the form server 12 with the corresponding form preview file 18 as an input file ((11) in FIG. 3). The completion of output is notified to the job management unit 124 of the form server 12. The job management unit 124 outputs the output completion result to the log ((12) in FIG. 3).

FIG. 4 is a flowchart showing the operation of the file monitoring unit 121 in this embodiment.
The file monitoring unit 121 periodically monitors whether the form data file 15 exists in the spool directory (for example, once every 10 seconds). If the form data file 15 exists in the spool directory, the file name and file size are acquired (step 401). If the file name acquired here does not exist in the spool setting file shown in FIG. 17, an error is assumed.

  Next, the acquired file name is compared with the file name in the file list (FIG. 15) stored in the memory (step 402). If the file names do not match, the file name and file size are newly added to the memory file list (steps 403 and 404), and information necessary for the job list shown in FIG. (File name, status, etc.) are added (steps 405 and 406).

  Subsequently, the file monitoring unit 121 waits for a predetermined interval (step 415), and then repeats the spool directory monitoring process.

  If the file names match in step 403, the file size in the file list stored in the memory is compared with the acquired file size (step 407). If the file sizes are equal, the file management unit 121 considers that the transfer of the form data file 15 has been completed, and moves the form data file 15 from the spool directory to the data directory (steps 405 and 409).

  Then, the file monitoring unit 121 deletes the corresponding file list from the memory (step 410). Next, the spool setting file shown in FIG. 17 is searched using the form data file name as a key, and the matched form name is acquired from the spool setting file (step 411).

  Subsequently, the file monitoring unit 121 requests the request management unit 122 for a form generation request (step 412). At this time, the spool information data is passed to the request management unit 122, and the contents of the spool information data here are a form data file name and a form name. Finally, the status of the job list is updated from “Reception” to “Form creation requested” (Steps 413 and 414).

FIG. 15 is a diagram conceptually showing the processing operation of the file monitoring unit 121.
The file monitoring unit 121 compares the file name (nouhin20030826180201) of the form data file existing in the spool directory with the file name in the file list stored in the memory. Here, the file name corresponding to the file list It is assumed that there was no. Therefore, the file monitoring unit 121 newly registers the file name and data size in the file list. However, after 10 seconds, the data size of the form data file acquired from the spool directory by the file monitoring unit 121 has changed from 2,048 bytes to 38,921 bytes. Accordingly, the size item in the file list also changes from 2,048 bytes. Update to 38,921 bytes.

  Further, after 10 seconds, when the file monitoring unit 121 acquires the data size of the form data file from the spool directory, the acquired data size (38,921 bytes) matches the data size registered in the size item in the file list. The file management unit 121 considers that the transfer of the form data file has been completed, moves the form data file from the spool directory to the data directory, and deletes the corresponding file list.

  The file monitoring unit 121 ends the process when receiving an end notification from the OS (step 416). The termination notification here is, for example, when the operator issues a process termination command from the console.

FIG. 5 is a flowchart showing the operation of the request management unit 122.
The request management unit 122 waits for a request from the file monitoring unit 121, and if there is a request, acquires the spool information data from the file monitoring unit 121 (steps 501 and 502).

  Then, the request management unit 122 determines whether there is an executable form generation process in the form generation unit 123 (steps 503 and 504). If there is an executable process, the request generation unit 123 determines the form generation process with respect to the form generation process. Generation is requested (step 505). At that time, the request management unit 122 passes spool information data (form data file name and form name) to the form generation unit 123 (step 505). Whether there is a form generation process that can be executed from among a plurality of form generation processes is determined by inquiring each form generation process.

  Next, the request management unit 122 updates the status of the job list from “Creating Form” to “Creating Form” (Steps 506 and 507). If the form generation process is not free, after waiting for a certain interval (step 508), it is determined again whether the process is free. The request management unit 122 ends the process when receiving an end notification from the OS. The termination notification here is, for example, when the operator issues a process termination command from the console.

FIG. 6 is a flowchart illustrating operations of the form generation unit 123 of the form server 12 and the storage processing unit 132 of the print server 13.
The form generation unit 123 of the form server 12 waits for a form creation request from the request management unit 122. When there is a request, the form generation unit 123 obtains a spool setting file (form data file name and form name) from the request management unit 122. Obtain (steps 601, 602).

  The form setting file (FIG. 17) is read using the form name in the spool setting file as a key, and the form execution file name corresponding to the form setting file is acquired (step 603). The form execution file referred to here stores information such as form definition information, layout information, and field editing information for generating a form, as shown in FIG.

  The form generation unit 123 generates and outputs a form preview file (FIG. 23) from the input form data file based on the form execution file corresponding to the acquired form execution file name (step 604). Then, the form generation unit 123 transmits the generated form preview file to the storage processing unit 132 operating on the print server 13 (step 605). At this time, the communication process between the form server 12 and the print server 13 performs a synchronization process using socket communication, for example.

  Subsequently, the form generation unit 123 waits for a response notification of the processing result from the storage processing unit 132 of the print server 13 thereafter. By doing so, the form server 12 can specify which job the notification from the print server 13 is.

  The storage processing unit 132 waits for a request from the form generation unit 123 of the form server 12, and when there is a transfer request, receives the form preview file (steps 610 and 611), and stores the received form preview file 18. Save in the directory (step 612).

  As the name of the file to be saved here, the form preview file name received from the form generation unit 123 may be used as it is. However, since it is necessary to make it unique, for example, a name for adding a time stamp to the form preview file name, etc. You may change to The print server 13 notifies the form generation unit 123 of the name of the saved form preview file (step 613). When the print server 13 changes the file name to a unique file name, the unique file name is notified.

  The form generation unit 123 changes the status of the job list from “printing in progress” to “waiting for printing” for the job for which the notification from the storage processing unit 132 has been acquired, and sets the form preview file name acquired from the storage processing unit 132 to the corresponding record. And the job list is updated (steps 606 and 607).

  Then, the form generation unit 123 deletes the form data file used when generating the form preview file from the data directory (step 608). Note that the form generation unit 123 in the form server 12 ends the process when receiving an end notification from the OS (step 609). The termination notification here is, for example, when an operator issues a process termination command from the console. The same applies to the storage processing unit 132 in the print server 13 (step 614).

  If the form server 12 and the print server 13 are not performing synchronization processing, the job cannot be specified. For example, when the form preview file is saved in the save directory in the print server 13, the form preview file name is changed. When changed, it may be possible to notify the form server 12 of the form preview file name before and after the change. By doing so, the form server 12 can identify which form preview file the notification is for. In addition, since it is only necessary to be able to specify which form preview file the form server 12 is notified of, it may be specified by other methods such as using a unique number instead of the file name.

7 and 8 are flowcharts showing the operation of the job management unit 124 in the form server 12.
The job management unit 124 in the form server 12 reads the first record of the job list (FIG. 16) (step 701), and determines whether the status is “waiting for printing” (step 702). If the status is “Waiting for printing”, the job management unit 124 performs a print request process (step 703).

  In the print request process, the job management unit 124 requests the print instruction unit 125 for a print request (step 801). At that time, the job management unit 124 passes storage file information (for example, “seikyu20030826180201.rcl” in FIG. 16) related to the job to be printed from the job list to the print instruction unit 125. Then, the job management unit 124 updates the status of the job list from “waiting for printing” to “printing” (steps 802 and 803).

  The job management unit 124 reads the next record in the job list (step 704), and repeats the determination process whether the status of the corresponding record is “waiting for printing”. If the status is not “waiting for printing”, the job management unit 124 determines whether the status is “printing” (step 705). If the status is “printing”, the job management unit 124 reads the next record (step 704), and repeats the process of determining whether the status is “waiting for printing”. If the status is not “printing”, after waiting for a certain interval (step 706), the determination process of “waiting for printing” is repeated again.

  If the job list record is completed in the process of reading the next record (step 704), the job management unit 124 waits for a certain interval (step 706) and repeats the print wait determination process again. Note that the job management function ends the process upon receiving an end notification from the OS (step 707). The termination notification here is, for example, when an operator issues a process termination command from the console.

FIG. 9 is a flowchart showing the operations of the print instruction unit 125 on the form server 12 and the print data creation processing unit 131 on the print server 13.
The print instruction unit 125 in the form server 12 waits for a form print request from the job management unit 124 (step 901), and when requested, requests the print data creation processing unit 131 on the print server 13 for a print request. . At this time, the print instruction unit 125 passes the storage file information acquired from the job management unit 124 to the print data creation processing unit 131 of the print server 13. The print instruction unit 125 in the form server 12 waits for a processing result from the print data creation processing unit 131 at this time.

  The print data creation processing unit 131 of the print server 13 waits for a print request from the print instruction unit 125 of the form server 12 (step 906), and if there is a print request, acquires storage file information (step 907). .

  The print data creation processing unit 131 reads the form preview file 18 with the file name of the acquired storage file information as the input file name, and outputs the form preview file 18 to the printer 14 (step 908). Subsequently, the print data creation processing unit 131 acquires the print result information output to the printer 14 from the printer 14 (step 909), and then deletes the form preview file 18 (step 910).

  The print instruction unit 125 in the form server 12 acquires the print result from the print data creation processing unit 131 in the print server 13 and deletes the corresponding job list (step 903). Also, the print result is added to the print log (FIG. 18).

  As a method for the print server 13 to acquire the print result, for example, it is conceivable to inquire the printer 14 about the print status and acquire the corresponding print result. The print result here includes not only normal termination but also information of an abnormality of the printer 14 (for example, out of paper or paper jam). Note that the print status can be confirmed on the screen using the information of the job list and the print log (FIG. 24).

  As a result, if there is a file that ends abnormally, the user knows that the printing order of the output form is not guaranteed and can specify the file that ended abnormally. There is an advantage that it is sufficient to print again.

  Note that the print instruction unit 125 in the form server 12 ends the process when receiving an end notification from the OS (step 905). The termination notification here is, for example, when an operator issues a process termination command from the console. The same applies to the print data creation processing unit 131 in the print server 13 (step 911).

<Second Embodiment>
Next, a second embodiment of the present invention will be described. In the present embodiment, the order of output based on information specified by the user can be guaranteed regardless of the order of input from the user application 111. Hereinafter, the specific method is demonstrated, referring the flowchart of FIG.

  When the user application 111 inputs the form data file 15 to the spool directory, a control file is also input separately. In the control file, as shown in FIG. 19, the groups and the printing order for each group are described. The form server 12 also stores the groups in the acquired control file and the printing order for each group in the job list as shown in FIG. In this example, the print order for each group is given as an example. However, the form for giving the print order is not limited to this, and any print order is assigned to each form data file 15 without being caught by the concept of the group. Is possible.

  In FIG. 10, the job management unit 124 acquires a group described in the control file subsequent to the “printing waiting” status determination process (step 1102), and determines whether the group is a space (step 1003). ).

  If the group is other than a space, the job management unit 124 performs a user-specified print order determination process (step 1005). If the group is a space, print request processing (step 1104) is performed. Note that steps 1001, 1006, 1007, 1008, and 1009 in FIG. 10 are the same processes as steps 701, 704, 705, 706, and 707 in FIG.

  In the user-designated printing order determination process, as shown in FIG. 11, the job management unit 124 first extracts a job list that matches the acquired group as the same group (step 1101). Then, as shown in FIG. 20, the extracted job list is sorted in ascending order of printing order (step 1102). Next, the job management unit 124 performs a printing order determination process (step 1103).

  In the print order determination process, as shown in FIG. 12, the job management unit 124 reads one record of the sorted job list (step 1201), and determines whether the status is “waiting for printing” (step 1202). If the status is “Waiting for printing”, the job management unit 124 performs the print request process (step 1203), reads the next record (step 1204), and repeats the process until the record ends. In step S1203, the print request process shown in FIG. 8 is executed.

  If the status is other than “waiting for printing”, the job management unit 124 determines whether the status is “printing” (step 1205). If the status is other than “printing”, the job management unit 124 waits for a certain interval (step 1206) and then repeats the print wait determination process again. If the status is “printing”, the job management unit 124 reads the next record (step 1204), and then repeats the print waiting determination process.

  In addition to the group in the control file and the printing order for each group, the number of files in the group may be described. In this way, for example, in the situation where the form server 12 has only acquired five form data files of the group A even though the group A has six form data files, You may make it wait for one form data.

  Specifically, a column for storing the number of group files is provided in the job list, the number of group files is extracted from the control file and stored, and when the same group is extracted in FIG. 11 (step 1101), all The number of group files is used when determining whether or not all the files are available. If the number of group files is complete, the process proceeds to the next stage. If not, the process waits until reception or the next process may be performed first.

  For the last file, a code that can be identified as the last file may be added to the control file. For example, if the fourth file is the last file, it may be possible to add a symbol such as “print order = 4 *”. Until the last file is received, the process for the group is waited.

  When the last file is received, the total value of the group file is extracted from the “print order” value of the control file. If the number of files is complete, the process proceeds to the next step. It is possible to wait until receiving or to perform the next processing first.

<Third Embodiment>
Next, a third embodiment of the present invention will be described.
In the present embodiment, the print order can be defined in the header information of the form execution file (FIG. 22), and the output order can be guaranteed. Hereinafter, the specific method will be described in detail with reference to the flowchart of FIG. Note that steps 1301, 1302, 1305, 1307, 1308, 1309, and 1310 in FIG. 13 are the same as steps 701, 702, 703, 704, 705, 706, and 707 in FIG. Is omitted.

  The form server 12 extracts the form name from the control file received from the user terminal 11 and stores the form name in the job list (FIG. 21). Then, a form execution file is extracted from the stored form name, and automatic designation information (FIG. 22) is acquired from the form execution file (step 1303).

  If the automatic designation category is other than a space, automatic printing order determination processing (steps 1304 and 1306) is performed. If the automatic designation category is a space, a print request process (step 1305) is performed.

  In the automatic print order determination process, as shown in FIG. 14, the form server 12 first extracts a job that matches the form name in the acquired automatic designation information from the job list (step 1401). Then, the extracted job list is rearranged in the printing order designated in the automatic designation information (step 1402). If the designated printing order is “nouhin”, “seikyu”, and “uriage”, they are rearranged as shown in FIG. Next, a printing order determination process is performed (step 1403). Note that step 1403 is the same process as in FIG.

  If only a part of the job matching the form name in the automatic designation information can be extracted, the standby or the next process may be performed first until all jobs can be extracted.

  As described above, according to the embodiment, the printing order can be guaranteed. In particular, since the form output can be performed for each order of the form data input by the user application, consistency between the input order and the output order can be ensured. As a result, it is possible to easily confirm that the input form data is output from the printer.

  In addition, since only the output order of the forms can be guaranteed regardless of the order of input of the form data, there is an effect that the forms are output in the output order intended by the user.

  In addition, since the forms can be output based on the printing order specified in advance, the arrangement order of the forms that must be output in advance during routine operations can be automatically output. There is an effect.

  Another object of the present invention is to supply a storage medium storing software program codes for realizing the functions of the above-described embodiments to a system or apparatus, and the computer (or CPU or MPU) of the system or apparatus stores the storage medium. Needless to say, this can also be achieved by reading and executing the program code stored in.

  In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code itself and the storage medium storing the program code constitute the present invention.

  As a storage medium for supplying the program code, for example, a flexible disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a magnetic tape, a nonvolatile memory card, a ROM, or the like can be used.

  Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (basic system or operating system) running on the computer based on the instruction of the program code. Needless to say, a case where the functions of the above-described embodiment are realized by performing part or all of the actual processing and the processing is included.

  Further, after the program code read from the storage medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, the function is determined based on the instruction of the program code. It goes without saying that the CPU or the like provided in the expansion board or function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

It is a figure which shows the structure of the form output system which concerns on one Embodiment of this invention. It is a figure which shows the hardware constitutions of the various terminals which concern on one Embodiment of this invention. It is a figure which shows the basic processing flow of the form output system which concerns on one Embodiment of this invention. It is a flowchart which shows operation | movement of a file monitoring process part. It is a flowchart which shows operation | movement of a request | requirement management part. It is a flowchart which shows operation | movement of a form production | generation part and a preservation | save process part. It is a flowchart which shows operation | movement of a job management part. 6 is a flowchart illustrating an operation of a print request process by a job management unit. 5 is a flowchart illustrating print instruction processing in the form server and print data creation processing in the print server. It is a flowchart which shows the job management process (user specification) by a job management part. It is a flowchart which shows the user designation | designated printing order judgment process in a job management process. 6 is a flowchart illustrating a printing order determination process in a job management process. It is a flowchart which shows the job management process (automatic designation | designated) by a job management part. 6 is a flowchart illustrating automatic designated printing order determination processing in job management processing. It is a figure which shows an example of operation | movement of a file monitoring part typically. It is a figure which shows the example of 1 structure of a job list. It is a figure which shows the example of 1 structure of a spool setting file. It is a figure which shows the example of 1 structure of a print log file. It is a figure which shows the example of 1 structure of a control file. It is a figure which shows the example of 1 structure of a job list (user specification). It is a figure which shows the example of 1 structure of a job list (automatic designation | designated). It is a figure which shows the example of 1 structure of a form execution file (automatic designation | designated). It is a figure which shows the example of 1 structure of a form preview file. 6 is a diagram illustrating a configuration example of a printing status screen layout. FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 11 User terminal 12 Form server 13 Print server 14 Printer 15 Form data file 16 Form execution file 17, 18 Form preview file 111 User application 121 File monitoring part 122 Request management part 123 Form generation part 124 Job management part 125 Print instruction part 131 Print Data creation processing unit 132 Storage processing unit 21 CPU
22 RAM
23 ROM
24 HDD (Hard Disk Drive)
25 Recording media drive 26 Video adapter 27 K / B (keyboard)
28 P / D (pointing device)
29 NIC (network interface card)

Claims (10)

Data receiving means for receiving data from an external device via a communication network;
Job management means for managing the output order of data received by the data receiving means;
Output data generating means for generating output data for each data received in the data receiving means;
Output data transmitting means for transmitting the output data generated by the output data generating means to an output device;
An information processing apparatus comprising: an output request unit that requests the output device to output output data stored in the output device in accordance with an output order of data managed by the job management unit.   The information processing apparatus according to claim 1, wherein the job management unit manages a data output order according to a data reception order in the data reception unit. Further comprising monitoring means for monitoring the data reception status in the data receiving means;
When the data reception unit is notified of data reception by the monitoring unit, the job management unit assigns a job number corresponding to the notification order to the data, and sets the data output order based on the job number. The information processing apparatus according to claim 1, wherein the information processing apparatus is managed.   The data receiving means receives control data including information indicating the output order of the data together with data from an external device, and the job management means outputs data based on the information indicating the output order included in the control data. The information processing apparatus according to claim 1, wherein the order is managed.   5. The information processing according to claim 4, wherein the information indicating the output order includes group information of data, and the job management unit manages the output order of data for each group indicated in the group information. apparatus.   The information processing apparatus according to claim 1, wherein the job management unit manages an output order of data according to an output form. An information processing system in which at least an information processing device, an external device, and an output device are connected via a communication network,
The information processing apparatus includes:
Data receiving means for receiving data from the external device via the communication network;
Job management means for managing the output order of data received by the data receiving means;
Output data generating means for generating output data for each data received in the data receiving means;
Output data transmitting means for transmitting the output data generated by the output data generating means to the output device;
An information processing system comprising: an output request unit that requests the output device to output output data stored in the output device according to an output order of data managed by the job management unit. An information processing method by an information processing apparatus,
A data receiving step for receiving data from an external device via a communication network;
An output data generation step for generating output data for each data received in the data reception step;
An output data transmission step of transmitting the output data generated by the output data generation step to an output device;
And an output requesting step of requesting the output device to output output data stored in the output device in accordance with the data output order managed by the job management means for managing the data output order. Information processing method.   A program for causing a computer to execute the information processing method according to claim 8.   A computer-readable recording medium on which the program according to claim 9 is recorded.

Images