JP2009217353A - Printing system, management program for printing system, and storage medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To update a cache of printer information held by a print server without reducing print performance. <P>SOLUTION: A printer information update situation of the print server in printer information cache update processing of the print server is held as update status in an update management table concerned by the print server and a printer, and the print server refers to the update status to perform the printer information cache update processing with minimum information acquisition. When adding or deleting the printer, or adding or deleting the print server, arrangement of the update management table is performed to suppress size of the update management table to the minimum. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a printer information update management method in a printing system.

  As shown in Patent Document 1, a technique for managing job information using a DataBase (hereinafter referred to as DB) for reducing the load on a print server is known.

  According to Patent Document 1, the client can acquire job information from the DB, and can reduce the load on the print server.

Also, as disclosed in Patent Document 2, each component compares the print information cached with the latest print information centrally managed in the DB, thereby acquiring only necessary information and updating the cache. It has been known. According to this patent document 2, the print information cache can be updated with the minimum necessary data acquisition.
Japanese Patent Laid-Open No. 9-325868 JP 2001-265540 A

  In a print server that distributes printing to thousands of printers located in offices throughout the country, if a large number of print jobs are controlled by a single print server, the print server will be heavily loaded and each job will be ejected significantly. Takes a long time. In order to avoid this, it is necessary to cluster and load balance (load balancing) multiple print servers. Since printing systems are distributed in a cluster configuration, print information such as job information and printer information common among print servers is centrally managed on a common disk (hereinafter referred to as DB).

  In a large-scale printing system, it is necessary to monitor thousands of printers. In a print server environment that is distributed by a cluster configuration and centrally manages print information in a DB, such as adding, deleting, changing, and moving printers Printer information update processing is frequently performed. Accordingly, in order to cope with the printer information update, the print server must acquire the latest printer information from the DB for printing. However, in a large-scale environment where hundreds of thousands of jobs are input in one hour, it takes time to acquire the latest printer information from the DB every time printing is performed. Furthermore, since access to the DB is concentrated, the performance of the entire printing system may be degraded, and it may take time to print. Therefore, the print server caches the printer information, periodically acquires the latest printer information from the DB, and updates the cache. When the print server periodically acquires printer information, the printer information acquisition timing is shifted among the print servers, and the access load to the DB can be distributed.

  When each print server periodically obtains the latest printer information from the DB for updating the printer information cache, the printer information cache is inconsistent between the print servers because the timing of obtaining the printer information differs for each print server. Occur. In order to avoid the management of the printer information update status in the print server, it may be possible to acquire as many as thousands of printer information each time from the DB that holds the latest information, but this takes time. By comparing the latest printer information held in the DB with the printer information cache held in the print server and acquiring only unupdated information, the amount of acquired information can be suppressed. However, it is necessary to search unupdated printer information from a large amount of printer information in the DB, and the disk access load in the DB for searching becomes high. If the disk access of the DB is concentrated, data acquisition from the DB is awaited, and as a result, it takes time to acquire printer information, which is not an effective means. As described above, the printer information update process of the print server increases the load and causes a problem of deteriorating the performance of the printing system. In addition, when the load of updating printer information by the print server is increased, when several tens of print servers are clustered, the print performance is remarkably reduced, which limits the scalability of the cluster configuration.

  In the method disclosed in Patent Document 1, the print server registers job information in the DB, and the client acquires job information from the DB, thereby reducing the load on the print server. However, the access load to the DB and the disk access load in the DB as described above cannot be reduced.

  In the method of Patent Document 2 described above, when the print server updates the printer information cache, the amount of acquired information can be minimized by performing comparison with the latest printer information held in the DB. . However, it is necessary to retrieve unupdated information from a large amount of printer information in the DB, and the disk access load on the DB cannot be reduced.

  The present invention has been made in view of such problems, and an object thereof is to update a cache of printer information held by a print server without degrading print performance.

  In the present invention, in the printer information cache update process of the print server, the printer server update status and printer deletion status of the print server are held in the update management table related to the print server and printer. The update status of the printer information cache of the print server is managed using an update management table.

  The present invention may be a program and a storage medium.

  According to the present invention, it is possible to update the cache of printer information held by the print server without degrading print performance.

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

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

<Embodiment 1>
(System configuration)
FIG. 1 is a diagram illustrating an example of a system configuration of a printing system.

  In the printing system, a server system and the like that control the printing system, a printing device, and a client (client computer) are connected over a wide area via a wide area network 110 (hereinafter referred to as WAN).

  The DBMS 104 is a DataBase Management System, and manages data such as document data, print jobs, and device information stored in the storage 105. The DBMS 104 is software installed on a server computer or the like, and the CPU or the like of the server computer performs processing based on the DBMS 104. However, in the present embodiment, for the sake of simplification of description, the description will be made assuming that the DBMS 104 performs processing. The DBMS 104 accepts operations such as update, acquisition, addition, and deletion of various data from other servers, and executes processing in accordance with the accepted operations.

  The storage 105 may be directly connected to the DBMS 104 as a DAS (Direct Attached Storage), or may be connected via a network as a SAN (Storage Area Network). In the case of a large-scale printing system, in order to distribute the load, the DBMS 104 (or the server computer on which the DBMS 104 is installed) may be configured in a cluster configuration, or may be configured in a redundant manner in case a failure occurs. .

  The print server system 101 is a system configured by a server computer that manages monitoring and management of a print device, control and monitoring of a print job, and transfer of a print job to the print device in the printing system. Note that in the case of a large-scale printing system, the print server system 101 may have a cluster configuration or a configuration with redundancy in preparation for failure occurrence in order to distribute the load.

  Further, the print server system 101 is connected to the DBMS 104 and the Web server system 102 via a local area network 109A (hereinafter referred to as LAN), and exchanges print job data, print control instructions, information on managed print jobs, and the like. To do.

  The Web server system 102 transmits print job information managed by the print server system 101 and document information managed by the DBMS 104 to each front-end client 108 connected via the WAN. The Web server system 102 is a system composed of server computers. In order to distribute the load, the Web server system 102 may have a cluster configuration or a configuration with redundancy in preparation for failure occurrence.

  The Web server system 102 receives a print instruction and print job operation from the client 108 and the print device 107, and transfers the instruction to the print server system 101. In addition, the Web server system 102 performs login authentication management from the client 108 and the print device 107 in cooperation with a directory server 103 described later. The Web server system 102 holds user authority information set in advance by a system designer or a document creator. The authority information includes, for example, document reference, printing, deletion authority, printing authority for a certain device, and print job deletion authority. The user authority information may be stored and managed by the Web server system 102 or may be stored and managed by the DBMS 104.

  The directory server 103 is a server computer that performs user authentication management using, for example, a combination of a user name and a password. Each user may be configured to participate in a domain group. For example, the Web server system 102 or the DBMS 104 can set the authority of the domain group in the authority information of the domain group in a range different from the authority of a single user. Further, for example, the web server system 102 may set user information, group information, or the like so that the user can participate in a plurality of domain groups.

  The print devices 107A, 107B, 107C, and 107D are printing devices (hereinafter referred to as the print device 107). Each print device is connected to the LAN 109B or LAN 109C via a network interface (not shown). The LAN 109B or LAN 109C is connected to the WAN 110, and the print device 107 can communicate with the print server system 101 and the Web server system 102 via the LAN and WAN. As the print device 107, an image processing apparatus such as a laser beam printer adopting an electrophotographic method or an ink jet printer adopting an ink jet method can be appropriately applied.

  Clients 108A, 108B, 108C and 108D are client computers (hereinafter referred to as clients 108) for performing information processing. Each client 108 is connected to the LAN 109B or the LAN 109C via a network interface (not shown). The LAN 109B or LAN 109C is connected to the WAN 110, and the client 108 can communicate with various server systems via the LAN and WAN. Each of the clients 108 may be a computer to which a permanent storage device is connected, or may be a computer with a Thin Client configuration configured only by a temporary storage device.

(Hardware configuration of server computer and client computer)
FIG. 2 is a diagram illustrating an example of a hardware configuration of a server computer or a client computer.

  The CPU 203 controls each process on this apparatus (server computer or client computer) by reading a program stored in the HDD 206 into the RAM 205 and executing a process based on this program. The ROM 204 stores programs and data related to each process of the present apparatus and cannot be rewritten. The RAM 205 can electrically store temporary data related to each process of the apparatus and can be rewritten. Programs and data related to each process of the apparatus, temporary data, and the like are stored in the HDD 206. The input device 207 is a keyboard or a pointing device that receives an instruction input to the apparatus. The display device 208 displays the operation status of the apparatus and information output by each program operating on the apparatus. A network I / F 202 connects to a LAN and the Internet via a network and exchanges information with the outside. The external device I / F 201 connects an external storage device or the like.

(Hardware configuration of print device)
FIG. 3 is a diagram illustrating an example of a hardware configuration of the print device.

  The image reader 302 reads a document with the document feeding unit 301. The image reader 302 and the image forming unit 303 convert the read original and data received via the network into a print image and print out the print image. A paper discharge unit 304 discharges the printed paper and performs processing such as sorting and stapling. A network I / F 305 connects to a LAN and the Internet via a network and exchanges information with the outside. The CPU 306 controls each process on the apparatus (print device) by reading a program stored in the ROM 307 or the HDD 309 into the RAM 308 and executing a process based on the program. A ROM 307 serving as a nonvolatile storage unit stores programs and data related to each process of the apparatus. A rewritable RAM 308 electrically stores temporary data related to each process of the apparatus. The HDD 309 stores programs and data related to each process of the apparatus, temporary data, and the like. The operation unit 310 displays a screen to be described later, and receives a user operation instruction via the screen.

(Print device)
FIG. 4 is a diagram hierarchically showing a part of the software configuration and hardware configuration of the print device. In FIG. 4, an image forming unit 413 corresponds to the image forming unit 303 in FIG. Form. The image forming unit 413 includes, for example, an ink jet printer or an electrophotographic image forming unit.

  The image reading unit 417 corresponds to the image reader 302 in FIG. 3 and includes a scanner or the like, and optically reads a document image and converts it into digital image information. Further, the image reading unit 417 outputs digital image information to the image forming unit 413 to form an image, or passes the digital image information to the fax unit 412, the network interface unit 414 or the like and transmits the digital image information via a line.

  The device controller 410 controls the operations of the image forming unit 413 and the image reading unit 417, for example, controls the image forming unit 413 to copy the document information read by the image reading unit 417. The device controller 410 also includes a network interface unit 414, a print processing unit 415, a fax unit 412, and an operation unit control unit 411, and also controls the exchange of information between these units. The device controller 410 corresponds to the CPU 306, the ROM 307, the RAM 308, the HDD 309, and the like in FIG.

  The fax unit 412 transmits / receives facsimile images, that is, transmits digital image information read by the image reading unit 417, and conversely decodes received facsimile signals and records them by the image forming unit 413. Execute the process.

  The operation unit control unit 411 generates a signal corresponding to a user operation using the operation panel of the operation unit 310, and displays various data, messages, and the like on the operation unit 310 (or display unit). Control.

  The print processing unit 415 performs control such as processing print data input via the network interface unit 414, outputting the processed data to the image forming unit 413, and printing. The network interface unit 414 controls data transmission / reception with other communication terminals via a communication line.

  A virtual machine (Virtual Machine) 405 is positioned above the device controller 410 and is configured to be able to control the device controller 410 from the virtual machine 405.

  The network interface unit 414 can be directly used by both the device controller 410 and the virtual machine 405, and is configured to be able to access an external network independently.

  Furthermore, an application described in a programming language corresponding to an API (Application Programming Interface) provided by the virtual machine 405 exists above the virtual machine 405. These applications (401, 402, 403) can indirectly act on the device controller 410 via the virtual machine 405, and can operate the image forming unit 413 and the image reading unit 417. Further, the application virtual machine 405 can be uninstalled or further installed as an application 404.

  Moreover, although the application mentioned above was demonstrated as an application installed in the print device 107 as this embodiment, you may be provided as hardware. Further, it may be provided as an application on a computer that is communicably connected to the print device 107 as an external device.

  The external storage device control unit 416 converts the image read by the image reading unit 417 into a data format that can be stored in the external storage device by the image forming unit 413, and stores the converted image in the external storage device. The external storage device control unit 416 reads data stored in the external storage device, performs print processing via the image forming unit 413, and transmits the data to the outside via the network interface unit 414.

  In this embodiment, an IC card reader 418 is communicably connected as a log-in means to the print device 107, and user account information can be notified to the authentication application 403 via the IC card reader 418. It is. The login means may be other means, for example, a means for inputting from an operation unit (device panel) managed by the operation unit control unit 411.

(Web server system)
As described above, the Web server system 102 typically has a cluster configuration for load distribution, and includes a plurality of Web server computers. A Web server installed in the Web server computer is a server that performs information communication in a WWW (World Wide Web) system, and is software.

  The Web server system 102 has the following functions.

  User account information (user name) and password are obtained by login from the front-end client 108, and the directory server 103 is authenticated. If login authentication is successful, the user's permission to view documents is approved. Document information is acquired from the DBMS 104 according to the approved reference authority, and the information is transmitted to the logged-in client 108. Also, a document print instruction from the client 108 is obtained, and a print instruction to which a document ID is assigned is transmitted to the print server system 101.

  As the above-mentioned approval policy for the reference authority, there are, for example, a policy that can refer to documents of users in all the domains to which the user belongs, a policy that can refer only to the user's own documents, and the like. Moreover, they can be designed flexibly according to the policy of the user who introduces the printing system. Further, the Web server system 102 can set not only the document reference but also authority settings such as document print authority, print job deletion authority, and promote authority for this approval.

  The client that accesses the Web server may be an authentication application installed in the virtual machine 405 on the print device 107 and a pull print application. In that case, the Web server accepts login from the authentication application, performs authentication and approval, the approved document information is received by the pull print application, and a print instruction is issued from the pull print application to the Web server.

(DBMS)
The DBMS 104 can employ various data management methods such as a card type, a relational type, and an object type. In the present embodiment, the DBMS 104 will be described as the most widespread relational type. The DBMS 104 holds document information, device information, device information update management information, and print server activation status management information as table information.

  The document table includes a document ID, which is a document identifier, a document name, a user name of a document registrant, and the like. The job table includes a document ID, a job ID, the name of the user who issued the print instruction, the status of the print job, and the like.

  FIG. 5 is a diagram illustrating an example of the device information 500. The device information 500 includes a device name 501, a device communication destination address 502, a communication port number 503, a print data transfer method 504, a device status 505, and the like. The print data transfer method 504 includes, for example, a RAW, LPR (Line Printer Demonstration Protocol), which continuously transmits data as a stream by TCP / IP, and a method of transmitting by HTTP.

  FIG. 6 is a diagram illustrating an example of the device information update management table 600. The device information update management information includes a device name 601, a deletion flag 602, a print server name 603, and an updated flag 604. The device name 601 contains the name of the device whose device information has been changed. The deletion flag 602 is a flag for determining whether the device information change is a device deletion. The deletion flag 602 is set to TRUE when the device information is deleted, and FALSE is stored when the device information is changed or the device information is added. The print server name 603 contains the name of the print server that needs to update the device information cache described later. An updated flag 604 is a flag indicating whether or not the print server has acquired changed device information. If the print server acquires the changed device information and updates a device information cache described later, TRUE is stored. If not updated, FALSE is stored.

  The values that can be taken by the deletion flag 602 and the updated flag 604 are two values of TRUE / FALSE in this embodiment. However, the status of the deletion status or the change status may be held as multiple values such as numbers and character strings. It doesn't matter how you hold it.

  FIG. 7 is a diagram illustrating an example of the print server activation status management table 700. The print server activation status management information includes a print server name 701 and an operation flag 702. The operation flag 702 is a flag indicating whether or not the print server is operating, and stores TRUE when the print server is operating, and FALSE when it is stopped.

  In this embodiment, the values that the operation flag 702 can take are set to TRUE / FALSE. However, the status of the operation status may be held as multiple values such as numbers and character strings, and the data holding method is not limited.

(Print server system)
FIG. 8 is a diagram illustrating an example of the system configuration of the print server system 101.

  As shown in FIG. 8, the print server system 101 of this embodiment is connected to a plurality of print servers (print server computers) 801 via a load balancer 802 that is a switch mechanism for load distribution with the LAN 109A. Yes. The load balancer 802 grasps the load status of a plurality of print servers 801, issues a request (request) preferentially to the print server 801 that is not loaded, and distributes the load. As a method for grasping the load status, a round robin method in which requests are sequentially sent to each print server 801 or a predetermined request is periodically sent to each print server 801, and the time taken until a reply is used as a load. There are methods to judge.

  A functional configuration of the print server 801 will be described.

  The print server 801 includes an API 803, a DB driver 804, a job manager 805, and a device manager 806 as functional configurations.

  API 803 is an Application Program Interface. The API 803 accepts document registration, document print requests, and print job control requests from the Web server system 102 or other servers that generate printable documents. Other servers that generate printable documents include, for example, a form server that creates a fixed form, a document management server that collectively manages user documents, and the like.

  The DB driver 804 is a module that communicates with the DBMS 104 when receiving a document registration request and registering a document in the DBMS 104 or when receiving a print request and acquiring print data from the DBMS 104.

  The job manager 805 has the following functions.

  The document received by the API 803 is registered in the DBMS 104 via the DB driver 804. When the API 803 receives a print request, the document data to be printed is acquired from the DBMS 104 via the DB driver 804 and managed as a print job. Further, the device manager 806 described later is instructed to print the acquired document on the print device 107 to be printed.

  The device manager 806 periodically acquires the device information 500 held by the DBMS 104 using the DB driver 804 and holds it as a device information cache. In this embodiment, the device information cache is the same as the device information 500 held in the DBMS 104, but it may be limited to information required by the device manager 806.

  Upon receiving a print data transmission request from the job manager 805, the device manager 806 starts printing to the print device 107 based on the device information cache.

(Device information cache update flow)
FIG. 9 shows an update flow of the device information cache held in the print server 801. The device information cache held by the print server 801 acquires and caches the latest device information 500 from the DBMS 104 when the print server 801 is activated. During startup, the device information cache is periodically updated in consideration of the load on the DB and printing performance.

  When it is time to update the device information cache, the print server 801 first obtains all records registered with its own print server name from the device information update management table 600 held in the DBMS 104 (F901). Then, all records acquired in F902 to F908 are processed one record at a time. First, in F903, the updated flag 604 is confirmed. If the updated flag 604 is TRUE, the device information cache is already updated and the process moves to the next record process. When the updated flag 604 is FALSE, the device information cache is updated. In the device information cache update process, the deletion flag 602 is confirmed (F904), and in the case of TRUE, the device information cache is deleted (F905). When the deletion flag 602 is FALSE, the latest device information 500 is acquired from the DBMS 104 (F906), and the device information cache is updated (F907).

  This is only the device information 500 that has a record change added to the device information update management table 600. Therefore, by referring to the device information update management table 600, the print server 801 can acquire only the necessary device information 500 and update the device information cache.

(System management server)
FIG. 10 is a diagram showing a functional configuration of the system management server 106.

  The system management server 106 includes a DB driver 1001, a print server manager 1002, a device information change receiving unit 1003, and a device information update management manager 1004 as functional configurations.

  The DB driver 1001 is a module that communicates with the DBMS 104 when operating (acquiring, updating, adding, deleting, etc.) information held in the DBMS 104 by the system management server 106.

  The print server manager 1002 confirms the activation status of the print server 801. If the print server manager 1002 is stopped, the operation flag 702 corresponding to the corresponding print server name 701 in the print server activation status management table 700 is set to FALSE. Confirmation of the activation status of the print server 801 is generally performed at regular time intervals. Means for confirming the activation status includes the presence or absence of a Ping response or the presence or absence of an ACK response in TCP / IP, but the means is not limited. Further, when the print server 801 is newly added to the printing system, the print server name 701 and the operation flag 702 added to the print server activation status management table 700 add a record of TRUE. When the print server 801 is deleted from the printing system, the corresponding record is deleted from the print server activation status management table 700 and the device information update management table 600. As means for changing the number of print servers 801 managed by the system management server 106, a tool is prepared and read from a file. As a means for changing the number of print servers 801, a method in which the Web server system 102 accepts a user operation and notifies the system management server 106 or a method in which an initialization file is changed and restarted can be considered.

  The device information change receiving unit 1003 receives a device information change and updates the device information 500 held by the DBMS 104. The Web server system 102 notifies the system management server 106 as means for accepting device information change. Device information changing means may be a method of reading from a file by a tool or a method of changing an initialization file and restarting, but any means may be used. When the device information change accepting unit accepts the change of the device information 500, it notifies the device information update management manager 1004 described later. Information to be notified includes the device name in which the device information 500 has been changed and the operation of changing, adding, or deleting device information.

  The device information update management manager 1004 performs a table operation of the device information update management table 600 held by the DBMS 104. When device information update is notified by the device information change receiving unit 1003, the DB driver 1001 is used to operate the device information update management table 1004. In addition, the device information update management table 600 is periodically accessed to delete unnecessary records.

(Operation of Device Information Update Management Table 600 when Updating Device Information)
FIG. 11 shows a flowchart when the device information update management manager 1004 receives a notification of change of the device information 500 from the device information change accepting unit 1003. First, when a device information change notification is received from the device information change accepting unit 1003 in F1101, a record in which the operation flag 702 is TRUE is acquired from the print server activation status management table 700 (F1102, F1103). The records in F1102 and F1103 may be obtained by acquiring all records and confirming the operation flag 702 in the system management server 106, or by using the search function of the DBMS 104 and only records for which the operation flag 702 is TRUE. You may get it. Next, in F1104 to F1112, processing is performed for all active print servers 801 whose operation flag 702 is TRUE. First, in F1105, the device information update management table 600 is searched for the name of the active print server and the device name in which the device information has been changed, and the corresponding record is acquired. If the corresponding record does not exist as a result of the search in F1106, the record to be added to the device information change management table 600 differs depending on the operation in the device information change acceptance process F1101. If the device information 500 is changed or added, a device name, delete flag 602 is added to FALSE, a print server name, and an updated flag 604 is added to a FALSE record (F1108). On the other hand, if the device information 500 is deleted, a device name, delete flag 602 is TRUE, print server name, and updated flag 604 is a FALSE record (F1109). If the corresponding record exists in the device information update management table 600 in F1105 and F1106, the updated flag 604 of the record is confirmed (F1110). If the updated flag 604 is TRUE in F1110, the updated flag 604 is changed to FALSE (F1111). If the updated flag 604 is FALSE, the device information change management table 600 is not updated, and the process proceeds to the next process in F1112. Processing for all the print servers 801 in operation in F1104 to F1112 is performed, and the device information update table 600 update processing at the time of device information update is terminated.

(Regular organization of device information update management table 600)
FIG. 12 shows a flowchart when the device information update management manager 1004 periodically organizes the device information update management table 600.

  First, all records are acquired from the print server activation status management table 700 (F1201). Next, the processing of F1203 to F1205 is performed for all the print servers 801 in which the operation flag 702 is FALSE in F1202. In F1204, the inactive print server 801 whose operation flag 702 is FALSE is searched from the device information update management table 600 by the print server name 601 and the corresponding record is deleted. When processing for all print servers not operating in F1203 to F1205 is completed, the processing proceeds to the next processing.

  As a next procedure, a record in which the updated flag 604 is TRUE is acquired from the device information update management table 600 (F1206, F1207). Records in F1206 and F1207 may be obtained by acquiring all records and checking the updated flag 604 in the system management server 106, or by using the search function of the DBMS 104 and a record in which the updated flag 604 is TRUE. You may get only. For all the records for which the updated flag 604 is TRUE, the records are deleted from the device information update management table 600 (F1209). In F1210, when the deletion of all the records for which the updated flag 604 is TRUE is completed, the regular organization of the device information update management table 600 of the device information update management manager 1004 is terminated.

<Other embodiments>
The object of the present invention is achieved by the following. That is, a storage medium (or recording medium) in which a program code of software that realizes the functions of the above-described embodiments is recorded is supplied to the system or apparatus. Then, the central processing means (CPU or MPU) of the system or apparatus reads and executes the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiment, and the storage medium recording the program code constitutes the present invention.

  In addition, by executing the program code read by the central processing means of the system or apparatus, an operating system (OS) or the like operating on the system or apparatus performs actual processing based on the instruction of the program code. Do some or all. The case where the function of the above-described embodiment is realized by the processing is also included.

  Further, it is assumed that the program code read from the storage medium is written in a memory provided in a function expansion card inserted into the system or apparatus or a function expansion unit connected thereto. After that, based on the instruction of the program code, the CPU of the function expansion card or function expansion unit performs part or all of the actual processing, and the function of the above-described embodiment is realized by the processing. It is.

  When the present invention is applied to the storage medium, the program code corresponding to the flowchart described above is stored in the storage medium.

  As described above, according to the above-described embodiment, it is possible to update the cache of device information held by the print server without degrading the print performance.

  The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to such specific embodiments, and various modifications can be made within the scope of the gist of the present invention described in the claims.・ Change is possible.

1 is a diagram illustrating an example of a system configuration of a printing system. It is a figure which shows an example of the hardware constitutions of a server computer or a client computer. FIG. 3 is a diagram illustrating an example of a hardware configuration of a print device. FIG. 2 is a diagram hierarchically showing a part of a software configuration and a hardware configuration of a print device. 5 is a diagram illustrating an example of device information 500. FIG. 5 is a diagram illustrating an example of a device information update management table 600. FIG. 6 is a diagram illustrating an example of a print server activation status management table 700. FIG. 1 is a diagram illustrating an example of a system configuration of a print server system 101. FIG. 10 is a flowchart illustrating an example of a process for updating a cache of device information 500 held by the print server 801. 2 is a diagram illustrating an example of a system configuration of a system management server 106. FIG. 12 is a flowchart illustrating an example of processing in which the system management server 106 updates a device information update management table 600 when there is a change in device information 500. 12 is a flowchart illustrating an example of processing in which the system management server 106 organizes a device information update management table 600.

Explanation of symbols

101 Print Server System 102 Web Server System 103 Directory Server 104 DBMS
105 Storage 106 System Management Server 107 Print Device 108 Client 109 LAN
110 WAN
600 Device information update management table 700 Print server activation status management table 801 Print server

Claims (6)

Regarding the printer information necessary for printing, the print server has printer information update means for acquiring the latest printer information held in the external storage device and updating the printer information cache held in the own storage device,
Means for holding update information related to a print server and a printer in the printer information update process;
Means for holding the update information in a print server and printer update management table;
Means for holding a printer server printer information update status in the update management table;
Means for holding a printer deletion status relating to printer deletion which is a special case of printer information update in the update management table;
Have
A printing system for managing an update status of a printer information cache of a print server by the update management table. A system management server having printer information change accepting means for accepting a change in printer information and a print server operating status grasping means for grasping the operating status of the print server;
When the printer information change acceptance unit accepts a change in printer information, the update management table is updated in claim 1.
Regarding update processing of the update management table,
When the system management server receives the printer information change by the printer information change accepting unit, the operating server status identified by the print server operating status grasping unit identifies the operating print server,
Means for acquiring a printer information update status and a printer deletion status related to an active print server and a printer that has received a change from the update management table;
Means for updating the printer information update status related to the active print server and the printer that received the change to unupdated when the acquired printer information update status has been updated;
If the printer information update status and printer deletion status related to the active print server and the printer that received the change cannot be obtained,
If the printer information change acceptance by the printer information change acceptance means is a printer deletion, the printer information update status related to the active print server and the deleted printer is not updated, and the printer deletion status is updated as deleted. Add update information to the table,
If the printer information change acceptance by the printer information change acceptance means is a change or addition instead of printer deletion, the printer information update status related to the active print server and the changed / added printer is not updated, and the printer is deleted. The printing system according to claim 1, further comprising means for adding update information to the update management table with the status as undeleted. The system management server organizes the update management table,
Regarding organization of update management table by system management server,
From the operating status of the print server grasped by the print server operating status grasping means, the system management server identifies the stopped print server,
Means for deleting update information relating to a stopped print server from the update management table;
3. The printing system according to claim 2, further comprising means for deleting update information whose printer information update status has been updated in the update management table. The system management server includes a print server addition / deletion reception unit for the printing system,
3. The apparatus according to claim 2, further comprising means for deleting update information related to the print server deleted from the update management table when the print server is deleted from the printing system by the print server adding / deleting means. The printing system described. Regarding the printer information necessary for printing, the print server has printer information update means for acquiring the latest printer information held in the external storage device and updating the printer information cache held in the own storage device,
Means for holding update information related to a print server and a printer in the printer information update process;
Means for holding the update information in a print server and printer update management table;
Means for holding a printer server printer information update status in the update management table;
Means for holding a printer deletion status relating to printer deletion which is a special case of printer information update in the update management table;
Have
A printing system management program that manages the update status of a printer information cache of a print server using the update management table.   A computer-readable storage medium storing the management program according to claim 5.

Images