JP2020038606A - Management system, method, and program - Google Patents

Abstract

To reduce complicated work by an operator of a management system and appropriately distribute destination information to a plurality of network devices.SOLUTION: A management system comprises a plurality of network devices, a client that communicates with the plurality of network devices, and a manager for managing the client. The manager includes management means for managing a destination table set including a plurality of destination tables including one or more destinations and creation means for creating a task in which the destination table set and the network device to be distributed are set. The client includes first determination means for determining whether or not the network device to be distributed can manage the plurality of destination tables of the destination table set on the basis of the task created by the manager and second determination means for determining the number of destinations included in the plurality of destination tables of the destination table set is within the number of destinations that can be managed by the network device to be distributed.SELECTED DRAWING: Figure 9

Description

  The present invention relates to a technique for delivering destination information to different types of network devices.

2. Description of the Related Art Conventionally, there is a management system that distributes data including a destination such as a telephone number, a mail address and information indicating a file transfer destination to a network device to be managed. At the time of distribution, it may be distributed as a destination table in which one or more destinations are put together.
Patent Literature 1 discloses a technique in which a server distributes a conditional address book to a plurality of network devices, and a network device that meets the conditions stores the received address book.

JP-A-2007-110263

It is assumed that there are various types (models, functional configurations) of network devices to be distributed by the management system. Depending on the number of destinations distributed from the management system, the size and format of the destination table, etc., it may not be possible to properly manage the destination network device. Therefore, in the management system, it is necessary to generate distribution data in consideration of the device type of the distribution destination.
On the other hand, when it is desired to distribute a destination to a plurality of network devices at the same time, it is extremely troublesome for an operator of the management system to individually create distribution data according to the distribution destination.

  Therefore, an object of the present invention is to provide a mechanism capable of appropriately distributing destination information to a plurality of network devices while reducing complicated operations by an operator.

  To solve the above problem, a management system of the present invention is a management system including a plurality of network devices, a client that communicates with the plurality of network devices, and a manager that manages the client, wherein the manager is A management unit that manages a destination table set including a plurality of destination tables including one or more destinations, and a generation unit that generates a task in which the destination table set and a network device to be distributed are set, and A first determining unit configured to determine whether the network device to be distributed can manage a plurality of destination tables of the destination table set based on the task generated by the manager; The number of destinations included in the plurality of destination tables of the table set is managed by the network device to be distributed. A second determination unit that determines whether the number is within the number of possible destinations, and the network device to be distributed is determined to be capable of managing the plurality of destination tables by the first determination unit; (2) when the number of destinations included in the plurality of destination tables of the destination table set is determined to be within the manageable number of destinations, the distribution data including the plurality of destination tables of the destination table set is determined. A delivery unit that delivers to the delivery target, and the network device to be delivered is determined by the first determination unit to be unable to manage the plurality of destination tables, and the second determination unit determines that the destination table set When it is determined that the number of destinations included in the plurality of destination tables is within the manageable number of destinations, the network to be distributed is used by using the destinations included in the plurality of destination tables of the destination table set. A generating means for generating a destination table that can be managed by device, the said delivery means is characterized by distributing the distribution data including the destination table the generated in said distribution target.

  Advantageous Effects of Invention According to the present invention, it is possible to appropriately distribute destination information to a plurality of network devices while reducing complicated work by an operator of a management system.

1 is an overall view of a system. FIG. 3 is a block diagram illustrating an example of a hardware configuration of a management server and a client device. FIG. 3 is a block diagram illustrating an example of a software configuration of a management server. FIG. 8 is a diagram illustrating an example of destination table management information. It is a figure showing an example of task management information. It is a figure showing an example of task management information. It is a figure showing an example of task management information. FIG. 3 is a block diagram illustrating an example of a software configuration of a client device. 13 is a flowchart illustrating an example of operation processing of the management server. 6 is a flowchart illustrating an example of operation processing of a client device. 13 is a flowchart illustrating an example of operation processing of the management server. It is a figure showing an example of a task result list screen. It is a figure showing an example of a recovery task creation screen. 15 is a flowchart illustrating an example of operation processing of a client device according to a fourth embodiment.

The best mode for carrying out the present invention will be described with reference to the drawings.
However, the components described in the following embodiments are merely examples, and are not intended to limit the scope of the present invention thereto.

<System configuration>
FIG. 1 shows an overall view of the system.
The system according to the present embodiment is a device management system. The system includes a client device 102 that distributes one or more destination tables to one or more devices, and a management server 101 that manages the destination table distributed by the client device 102 and the client device 102 itself. Prepare.

  The management server (manager) 101 is connected to the client device 102 via the LAN 104. The plurality of network devices 103 are also connected to the LAN 104. The management server 101 centrally manages data of the client device 102 and the plurality of network devices 103. The plurality of network devices 103 are devices such as an LBP (Laser Beam Printer) and an MFP (Multi-Function Peripheral). The plurality of network devices 103 are monitored by the client device 102.

  The client device 102 manages a plurality of network devices 103 via the LAN 104. Further, the client device 102 communicates with the plurality of network devices 103 and performs distribution of a destination table to the plurality of network devices 103.

<Hardware configuration of client device and management server>
FIG. 2 is a block diagram illustrating an example of a hardware configuration of an information processing device such as the management server 101 and the client device 102.
The information processing apparatus includes a communication I / F unit 201, a storage device 202, a CPU 203, a memory 204, and an output I / F unit 205.

  The communication I / F unit 201 is a network interface for communicating with an external system or device. The storage device 202 stores an OS (Operating System), programs, management data, data collected from external systems and devices, and the like. The CPU 203 loads a program from the storage device 202 to the memory 204 and executes the program. The output I / F unit 205 connects an output device such as a display, and outputs an execution result of a program or the like. In the management server 103, a storage device 202 stores a management program for realizing a function described later with reference to FIG. In the client device 102, the storage device 202 stores a client program for implementing a function described later with reference to FIG.

  One information processing device can operate as the management server 101 and the client device 102. In this case, the management program and the client program are installed in the storage device 202 and executed by the CPU 203. . In the case where one information processing device operates as the management server 101 and the client device 102, the management server 101 communicates with the client device 102 in the own device.

<Software configuration of management server>
FIG. 3 is a block diagram illustrating an example of a software configuration of the management server 101.
The destination table management unit 301 manages destination table management information necessary for distributing the destination table to the network device 103, such as destination information and destination table information for managing a plurality of pieces of destination information collectively. Details of the destination table management information will be described later.

  The task management unit 302 manages task management information necessary for managing tasks, such as task information for distributing one or more destination tables and schedule information for executing tasks. Details of the task management information will be described later. The scheduler 303 manages the schedule of task execution, starts a task to be executed, and notifies the client device 102 of a task processing start. The task execution unit 304 registers information necessary for the client device 102 to execute a task in the storage device 202, and creates intermediate data of destination table information to be distributed. The intermediate data includes destination table information and destination information included in the destination table.

  The request processing unit 305 processes various requests (device information acquisition request, task information acquisition request, and the like) from the client device 102. The task result processing unit 306 receives the task result notified from the client device 102 and stores it in the storage device 202. The screen display unit 307 displays task results and the like. Since the recovery task creation unit 308 is not related to the present embodiment, the description is omitted here.

<Example of destination table management information managed by management server>
FIG. 4 is an example of destination table management information.
The destination table management information is information registered in advance by the user.

First, a destination management table for managing destination information will be described.
The destination information is a part of information constituting the destination table information, and the destination table information is information obtained by grouping the destination information.
Reference numeral 401 denotes a destination ID, which is information for identifying destination information.
Reference numeral 402 denotes a destination type, which is information indicating the type of the destination. For example, e-mail, FAX, etc.
Reference numeral 403 denotes a destination name, which is the name of the destination.
Reference numeral 404 denotes a mail address, which is information indicating destination information when the e-mail function is used.
Reference numeral 405 denotes a facsimile number, which is information indicating destination information when the facsimile function is used.

Next, a destination table information management table for managing destination table information will be described.
Reference numeral 406 denotes a destination table ID, which is information for uniquely identifying destination table information.
Reference numeral 407 denotes a destination table name, which is the name of the destination table.

Next, a destination table set management table for managing destination table set information will be described.
The destination table set information is information for grouping and managing the destination table information, and is information indicating which destination table of the device is to be applied to which destination table. The destination table set information includes a plurality of destination table information including one or more destinations. Also, there is only one type of destination table set regardless of the device type.
A destination table set ID 408 is information for uniquely identifying destination table set information.
Reference numeral 409 denotes a destination table set name, which is the name of the destination table set.

Next, a device management table for managing device information to be managed by the device management system will be described.
A device ID 410 is information for identifying a device.
A device name 411 is a device name.
Reference numeral 412 denotes a device type, which is information indicating device model information. This information may be input by the user when registering the device, or after device registration, the model may be determined based on information acquired from the device at some timing, and registered.

  Finally, a destination table and destination management table that links the destination table and the destination, a destination table set and a destination table management table that links the destination table set and the destination table, and a device and destination table set that links the device and the destination table set Management table table exists. These tables hold each other's ID information. Further, regarding the destination table set & destination table management table, the table holds a destination table type 413 in addition to the ID information. The destination table type 413 is information indicating to which destination table in the device the destination table should be delivered.

<Example of task management information managed by the management server>
FIGS. 5, 6, and 7 show examples of task management information.
FIG. 5 shows a task schedule management table for managing a task schedule and a task target management table for managing a target device of the task. This information is information registered in advance by the user.

First, the task schedule management table will be described.
Reference numeral 501 denotes a task ID, which is information for uniquely identifying a task.
Reference numeral 502 denotes a task type, which is information for specifying the type of the task.
Reference numeral 503 denotes a schedule, which is information indicating a schedule for executing a task. This information is information set by the user when creating a task. Schedules that can be set include execution immediately, designation of date and time, designation of a regular schedule, and the like.
Reference numeral 504 denotes the next start time of the task, which is information indicating the time at which the task should be executed next time. This information is calculated by the scheduler 303 based on the schedule set by the user at the time of task registration and execution.

Next, the task target management table will be described.
Reference numeral 501 is the same as that described in the task schedule management table.
Reference numeral 505 denotes a target ID, which is information for uniquely identifying a target device to execute a task.

  FIG. 6 shows a task instance management table for managing task instance information and a subtask instance management table for managing subtask instance information. The subtask is a task for each target device.

First, the task instance management table will be described.
Reference numeral 601 denotes an instance ID, which is information for uniquely identifying a task instance.
A task ID 602 is information for uniquely identifying a task.
Reference numeral 603 denotes a task type, which is information for specifying the type of the task.
Reference numeral 604 denotes content, which is detailed information necessary for executing the task.
Reference numeral 605 denotes the creation date and time, which is the date and time when the task instance was created.
Reference numeral 606 denotes the completion date and time, which is the date and time when the execution of the task has been completed.
Reference numeral 607 denotes status, which is information indicating a task execution result.

Next, the subtask instance management table will be described.
Reference numeral 601 is the same as that described in the task instance management table.
Reference numeral 608 denotes a client ID, which is information indicating identification information of a client device that executes a subtask.
A device ID 609 is information for identifying a target device of the subtask.
Reference numeral 610 is subtask content, which is detailed information necessary for executing the subtask. For example, it is destination table identification information of a distribution target, destination table type information indicating a destination table in a device to be distributed, and information on model identification information of a target device.
Reference numeral 611 denotes the subtask completion date and time, which is the date and time when the execution of the subtask is completed.
A subtask status 612 is information indicating the execution status of the subtask.
Reference numeral 613 denotes a result, which is information indicating an execution result of the subtask.

FIG. 7 shows a task execution notification table that manages task execution notification information (information indicating to which client a task execution notification should be sent).
Reference numeral 701 denotes a notification ID, which is information for uniquely identifying notification information.
Reference numeral 702 denotes a client ID, which is information for identifying a client to be notified of task execution.
Reference numeral 703 denotes a task type, which is information for indicating which task should be executed for the client.

<Software configuration of client device>
FIG. 8 is a block diagram illustrating an example of a software configuration of the client device 102.
The process start notification receiving unit 801 receives a task process start notification from the management server 101. The client task execution unit 802 acquires information on a task to be executed and device information, and creates a subtask as a task for each target device. The queue management unit 803 stores the subtask in the queue, takes out the subtask from the queue, and the like. The subtask execution unit 804 performs acquisition of intermediate data of device information and destination table information, creation of destination information for distribution, distribution of a destination table to the network device 103, notification of a task execution result to the management server 101, and the like.

<First embodiment>
Operation of Management Server FIG. 9 is a flowchart illustrating an example of operation of the management server 101.
FIG. 9A shows a main flow, and FIG. 9B shows a subroutine of S902 in FIG. 9A.

  First, in step S901, the scheduler 303 acquires information from the task management unit 302, and determines whether the task execution time is earlier than the current time. If the time is before the current time, it is determined that the task is to be executed, and the process proceeds to S902. On the other hand, if the task execution time is later than the current time, it is determined that it is not the task execution timing, and the process returns to S901.

Next, in S902, the task execution unit 304 executes a destination table distribution task.
That is, the task execution unit 304 creates a task instance and registers it in the storage device 202 via the task management unit 302 (S9021). Next, the task execution unit 304 creates an instance of the subtask and registers it in the storage device 202 via the task management unit 302 (S9022). Next, the task execution unit 304 acquires destination table information to be distributed from the destination table management unit 301, creates intermediate data for each destination table, and stores it in the storage device 202 (S9023). Finally, the task execution unit 304 registers task execution notification information for notifying the client device 102 of task execution in the storage device 202 via the task management unit 302 (S9024).

  Next, in step S903, the scheduler 303 notifies the client device 102 of a task execution. In step S904, the request processing unit 305 determines whether there is a request from the client device 102. If there is a request, the process proceeds to S905. On the other hand, if there is no request, the process returns to S904.

  Next, in S905, the request processing unit 305 determines whether the request content is a subtask result notification. If it is a subtask result notification, the process proceeds to S907. On the other hand, if it is not a subtask result notification, the process proceeds to S906. In step S906, the request processing unit 305 performs a process on the request. For example, in the case of a request to acquire information on a specified device, device information is acquired from the storage device 202 and a response is made.

  Next, in step S907, the task result processing unit 306 stores the result of the subtask received from the client device 102 in the storage device 202 via the task management unit 302. In step S908, the task result processing unit 306 determines whether all the subtasks related to the task have been completed based on the status of the subtask stored in the subtask instance management table. If it is determined that all the subtasks have been completed, the process proceeds to S909. If it is determined that all subtasks have not been completed, the process returns to S904.

  Next, in step S909, the task result processing unit 306 stores the result of the task in the storage device 202 via the task management unit 302. In step S910, the screen display unit 307 displays the task result and the subtask result stored in the storage device 202 on the screen.

Operation of Client Device FIG. 10 is a flowchart illustrating an example of an operation of the client device 102.
10A shows a main flow, FIG. 10B shows a subroutine of S1002 in FIG. 10A, and FIG. 10C shows a subroutine of S1003 in FIG. 10A.

  First, in step S1001, the process start notification receiving unit 801 receives a process start notification from the management server 101.

Next, in S1002, the client task execution unit 802 executes a destination table distribution task.
That is, the client task execution unit 802 acquires task information from the management server 101 (S10021). Next, the client task execution unit 802 acquires all the subtask information related to the task from the management server 101 (S10022). Finally, the queue management unit 803 creates a subtask in which the acquired task information and subtask information are described, and registers the created subtask in the queue (S10023).

Next, in S1003, the subtask execution unit 804 executes the destination table distribution subtask.
That is, if the information on the device to be distributed is cached in the corresponding client device 102, the subtask execution unit 804 acquires the information. If it is not cached, the distribution target device information is obtained from the management server 101 and cached in the client device 102 (S10031).

  That is, the device information is not obtained from the management server 101 every time the subtask is executed, but is obtained from the management server 101 only when the target device executes the first task after the client device 102 is started. Thus, network traffic between the client device 102 and the management server 101 is reduced.

  Next, if the intermediate data of the destination table information to be distributed is cached in the corresponding client device 102, the subtask execution unit 804 acquires the information. If not cached, intermediate data of the destination table information to be distributed is acquired from the management server 101 and cached in the client device 102 (S10032).

  In other words, the intermediate data of the destination table information is not obtained from the management server 101 every time the subtask is executed, and is managed only when the destination table to be distributed is not cached inside the client device 102 when each subtask is executed. Obtained from the server 101. Thus, the network traffic between the client device 102 and the management server 101 is reduced by sharing the destination table between the subtasks.

  Next, the subtask execution unit 804 determines whether the number of destination tables that can be managed by the device to be distributed is plural (S10033). The value of the number of destination tables that can be managed for each device type is stored in the client device in advance. If the number of destination tables that can be managed by the device to be distributed is plural, the subtask execution unit 804 determines that the total number of destinations included in all the destination tables to be distributed is the specification of the device to be distributed. It is determined whether it is within (S10034). That is, in S10034, the subtask execution unit 804 determines whether the total number of destinations included in all the destination tables to be distributed is within the number of destinations that can be managed by the distribution target device.

  The determination in S10034 is realized by holding the upper limit of the number of destinations that can be managed for each device type in the client device. In S10034, if the specification is within the device specification, the subtask execution unit 804 generates distribution data from a plurality of destination tables included in the destination table information and distributes the data to the distribution target device (S10035). Further, the subtask execution unit 804 notifies the management server 101 of the information of the distribution result (success) as the execution result of the subtask (S10036). On the other hand, if it is determined in step S10034 that it is not within the device specifications, in step S10036, the subtask execution unit 804 notifies the management server 101 of the execution result of the subtask indicating a distribution error.

  If it is determined in step S10033 that the number of destination tables manageable by the device to be distributed is not plural, the process advances to step S10037. As in S10034, the subtask execution unit 804 determines whether the total number of destinations included in each of the plurality of destination tables to be distributed is within the specifications of the device to be distributed (S10037). If it is within the specifications of the device, one destination table including all destinations included in each of the plurality of destination tables to be delivered is generated (S10038).

  After that, the subtask execution unit 804 distributes the distribution data including the generated one destination table to the distribution target network device (S10035). Then, information of the distribution result (success) is notified to the management server 101 as a subtask result (S10036). On the other hand, if it is determined in step S10037 that the content is not within the device specifications, in step S10036, the subtask execution unit 804 notifies the management server 101 of the execution result of the subtask indicating a distribution error.

  In step S10033, the subtask execution unit 804 determines whether the number of destination tables that can be managed by the device to be distributed is plural. However, a model is conceivable in which a certain number of destination tables, such as two or three devices to be distributed, can be managed, but ten or more destination tables cannot be managed. In such a case, in S10033, the subtask execution unit 804 may make a determination by comparing the upper limit of the number of destination tables that can be managed by the device to be distributed with the number of destination tables set by the task to be distributed. good. At that time, if the number of destination tables set in the task to be distributed is within the upper limit, the process transitions to S10034; otherwise, the process transits to S10037.

  After that, if YES is determined in S10037, at least one or more destination tables are generated within the maximum number of destination tables that can be managed by the distribution target device. For example, when the type of the destination table is different, such as personal or shared, it is conceivable to generate the destination tables for the number of types by combining the destinations included in the destination tables of the same type into one destination table. . The distribution data including the destination tables for the number of types created here is distributed to the distribution target network device in S10035.

  Next, in S1004, the client task execution unit 802 deletes the intermediate data of the destination table information cached inside the client device 102.

  Creating a destination table for distribution in the client device 102 leads to a reduction in load on the management server 101 side. It is more effective from the viewpoint of load distribution to create a distribution destination table for target devices for each client device 102 than to create a distribution destination table for all devices by the management server 101. It is obvious. Further, by caching device information and destination table information in the client device 102 and sharing the information between subtasks, network traffic between the management server 101 and the client device 102 can be reduced.

  As described above, in the first embodiment, the destination table is managed by one type of destination table set independent of the device type. Also, at the time of destination table distribution, the destination table to be distributed is created based on the information in the destination table set according to the type of the device to be distributed, so that the user can easily manage the destination table. Become. Furthermore, in the client device, the load on the management server can be reduced by creating a destination table for distribution based on the destination table intermediate data. In the client device, device information and destination table information are cached and shared between the subtasks, so that network traffic between the management server and the client device can be reduced.

<Second embodiment>
In the first embodiment, when distributing a destination table, if a plurality of destination tables are to be distributed to a device that can be managed with only one destination table, the destination table information is merged and distributed. I was At the time of merging, if the number of destinations to be distributed is larger than the number of destinations that can be managed by the corresponding distribution target device, an error is generated.

  However, it is troublesome for the user to create a task from the beginning to execute the task again for the device in which the error has occurred. Further, depending on the cause of the error, there is a case where the task fails even if the task is executed again. For example, a case where an attempt is made to distribute destination information exceeding the number of destinations that can be managed by the device as described above. Knowing that it will fail, doing the work is useless.

  In the second embodiment, a description will be given of a mechanism for allowing a user to easily re-create a task based on the above, and for selecting only a device that has a possibility of being successful when the process is performed again. .

-System configuration The overall view of the system is as shown in Fig. 1. Since this has already been described, the description here is omitted.

-Hardware configuration of management server The hardware configuration of the management server is as shown in FIG. Since this has already been described, the description here is omitted.

-Software configuration of management server The software configuration of the management server is as shown in FIG. The second embodiment differs from the already described software configuration in the following points. The other points are the same as those described with reference to FIG. 3, and the description thereof will be omitted.
The recovery task creation unit 308 automatically creates a recovery task targeting only the device for which the task is to be re-executed in response to a recovery instruction.

Operation of Management Server FIG. 11 is a flowchart illustrating an example of operation of the management server 1011.
FIG. 11A shows a main flow, and FIG. 11B shows a subroutine of S1103 in FIG. 11A.

  First, in step S1101, the screen display unit 307 outputs a task result list screen according to a user request.

Here, the task result list screen will be described.
FIG. 12 is an example of the task result list screen.
When the screen is displayed, the screen display unit 307 acquires information from the task instance management table described in the first embodiment and displays the content. For a task whose execution result has failed, a recovery button is arranged and a link to a recovery task creation screen is provided.

Return to the description of the flowchart.
Next, in step S1102, the screen display unit 307 determines whether the recovery button has been pressed by the user in the task result list screen and creation of a recovery task has been requested. If the recovery button has been pressed, the process proceeds to S1103. On the other hand, if the recovery button has not been pressed, the process returns to S1102.

Next, in step S1103, the screen display unit 307 displays a recovery task creation screen.
That is, the screen display unit 307 requests the recovery task creation unit 308 to create a recovery task, and acquires the information (S11031). Next, the recovery task creation unit 308 acquires the original information of the recovery target task from the task schedule management table, and creates a recovery task based on the information. Further, the recovery task creation unit 308 acquires information on the target device of the recovery task (S11032). The target device here is a device that failed in the processing of the task from the subtask instance management table and that excludes devices that attempted to deliver destination information exceeding the number of destinations that can be managed by the device. is there. Finally, the recovery task creation unit 308 displays a recovery task creation screen based on the obtained information.

Here, the recovery task creation screen will be described.
FIG. 13 is an example of a recovery task creation screen.
This screen includes a screen in which original information (schedule, task name, etc.) of the task to be recovered is input in advance, and a screen in which a list of target devices of the recovery task is output. A save button for registering the task information created on this screen in the storage device 202 is provided.

Return to the description of the flowchart.
Next, in step S1104, the screen display unit 307 determines whether the recovery task creation button has been pressed. If the user has pressed the recovery task creation button, the process advances to step S1105. On the other hand, if the recovery task creation button has not been pressed, the process returns to S1104.

  Finally, in S1105, the recovery task creation unit 308 registers the recovery task information in the storage device 202 based on the information input on the recovery task creation screen.

  As described above, according to the second embodiment, when creating a recovery task, the screen display unit 307 creates a recovery task creation screen in which the original task information of the recovery target task is input. Then, on this screen, among the devices for which the processing has failed, only those devices which are likely to succeed when the processing is performed again can be selected. Therefore, the user can easily create a recovery task.

<Third embodiment>
In the first embodiment, when distributing a destination table, if a plurality of destination tables are to be distributed to a device that can be managed with only one destination table, the destination table information is merged and distributed. I was At the time of merging, if the number of destinations to be distributed is larger than the number of destinations that can be managed by the corresponding distribution target device, an error is generated.

  However, in such a case, there is a case where it is desired to merge and distribute the destination tables to be distributed within a range not exceeding the number of destinations that can be managed by the device without causing an error. Therefore, if the number of destinations to be distributed is larger than the number of destinations that can be managed by the distribution target device, an error occurs, or the destination table of the distribution target is merged within the range that does not exceed the number of destinations that can be managed by the device. May be selected by the user in advance.

  Then, at the time of distribution of the destination table, the subsequent processing can be switched based on the selected information. When the destination tables to be distributed are merged and distributed within a range not exceeding the number of destinations that can be managed by the device, the user may be allowed to select in advance the priority of the destination table to be merged. In this case, when distributing the destination table, the order of the destination tables to be merged is controlled based on the priority information.

<Fourth embodiment>
In the first embodiment, when the destination table is distributed, it is determined whether the number of destinations included in the destination table to be distributed satisfies the device specifications. However, when distributing a destination table to a device that manages a plurality of destination tables, even if the number of destinations included in the destination table to be distributed satisfies the device specifications, as a result of distribution, the destination There are cases where the total number exceeds the device specifications. In this case, when distribution is performed for each destination table, only some of the destination tables are distributed, and appropriate destination table management cannot be performed. In addition, even if the total number of destinations of the distribution target device does not exceed the device specification in terms of calculation, even if the destination table of the distribution target is distributed, the result of distribution for each destination table may result in the There are cases where it exceeds. Here, a mechanism for dealing with these cases will be described.

-System configuration The overall view of the system is as shown in Fig. 1. Since this has already been described, the description here is omitted.

-Hardware configuration of management server The hardware configuration of the management server is as shown in FIG. Since this has already been described, the description here is omitted.

-Software configuration of management server The software configuration of the management server is as shown in FIG. Since this has already been described, the description here is omitted.

-Operation of the management server The description is omitted because it is the same as that of the first embodiment.

-Operation of Client Device Only the process of S1003 (destination table distribution subtask execution process) having a difference from the first embodiment will be described.
FIG. 14 shows the subroutine of S1003 in FIG. 10A described in the first embodiment.
Since steps S10031 to S10038 are the same as those described in the first embodiment, the description here is limited to the processing of steps S1401 to S1404 only.
The subtask execution unit 804 acquires the number of destinations for each destination table from the distribution target device (S1401). The number of destinations may be obtained by actually obtaining destination table data and analyzing the data.

  Next, when the destination table to be distributed is distributed, the subtask execution unit 804 determines whether the number exceeds the number of destinations that can be managed by the device (S1402). Specifically, first, from the number of destinations in the destination table to be distributed and the number of destinations for each destination table managed by the device acquired in S1401, the number of destinations in the destination table that is not to be distributed this time is acquired. Add them together. It is determined whether the result is larger than the value of the number of destination tables that can be managed by the device type of the distribution target device. If it is determined in step S1402 that the value will be exceeded, the flow shifts to step S10036. In S10036, the subtask execution unit 804 notifies the management server 101 of the execution result of the subtask indicating the distribution error. By doing so, it is possible to prevent only some of the destination tables from being distributed. On the other hand, if it is determined in step S1402 that the number does not exceed the value, the process advances to step S1403.

  Next, the subtask executing unit 804 determines, for each destination table to be distributed, the number of destinations included in the destination table and the number of destinations for each destination table managed by the device acquired in S1401, and includes the destination table in the corresponding destination table. The difference from the number of destinations is calculated (S1403). Here, the number of destinations included in the destination table to be distributed is subtracted from the number of destinations in the destination table managed by the device.

  Next, based on the value calculated in S1403, the subtask execution unit 804 determines that the number of destinations included in the destination table for distribution is smaller than the number of destinations set in the corresponding destination table on the device side, In addition, distribution is performed in order from the destination table having the largest difference (S1404). In terms of the value calculated in S1403, distribution is performed from a destination table having a large value. This makes it possible to distribute all destination tables without causing a distribution error in the middle.

  As described above, when distributing a destination table to a device that manages a plurality of destination tables, the total number of destinations currently managed by the device is acquired, and as a result of distribution, the total number of destinations of the distribution target device is the device. It is determined whether the specification is exceeded. As a result, only a part of the destination table is not distributed. In addition, at the time of distribution of the destination table, even if the total number of destinations of the device to be distributed does not exceed the device specification in calculation, there is a case where the specification exceeds the device specification in the middle depending on the distribution order. In this case, by controlling the order of the destination tables to be distributed, it is possible to distribute all the destination tables without causing a distribution error on the way.

<Other Examples>
According to the present invention, there is provided a process for supplying a program for realizing one or more functions of the above-described examples to a system or an apparatus via a network or a storage medium, and one or more processors in a computer of the system or the apparatus reading and executing the program. But it is feasible. Further, it can also be realized by a circuit (for example, an ASIC) that realizes one or more functions.

  As described above, the preferred embodiments of the present invention have been described, but the present invention is not limited to these embodiments, and various modifications and changes can be made within the scope of the gist.

101 management server 102 client device 103 network device

Claims (10)

A management system including a plurality of network devices, a client that communicates with the plurality of network devices, and a manager that manages the client,
The manager,
Management means for managing a destination table set including a plurality of destination tables including one or more destinations;
Creating means for creating a task in which the destination table set and a network device to be distributed are set, and
The client,
A first determination unit configured to determine whether the network device to be distributed can manage a plurality of destination tables of the destination table set based on the task created by the manager;
A second determination unit that determines whether the number of destinations included in the plurality of destination tables of the destination table set is within the number of destinations that can be managed by the distribution target network device,
The network device to be distributed is determined by the first determination unit to be capable of managing the plurality of destination tables, and the destination included in the plurality of destination tables of the destination table set by the second determination unit. When it is determined that the number of destinations is within the number of manageable destinations, distribution means for distributing distribution data including a plurality of destination tables of the destination table set to the distribution target,
The number of destinations included in the plurality of destination tables of the destination table set is determined by the first determination unit to be unable to manage the plurality of destination tables, and the second determination unit determines that the network device to be distributed cannot manage the plurality of destination tables. Is determined to be within the number of manageable destinations, generating a destination table that can be managed by the network device to be distributed using destinations included in the plurality of destination tables of the destination table set. Means,
The management system, wherein the distribution unit distributes distribution data including the generated destination table to the distribution target. The creating means of the manager further creates a subtask for a client corresponding to a network device to be distributed set in the task,
The management according to claim 1, wherein the client further includes a first acquisition unit that acquires the destination table set and information on the network device to be distributed from the manager according to the created subtask. system.   The client may further include a notification unit that notifies the manager of a distribution result indicating that distribution data has been successfully distributed to the network device to be distributed by the distribution unit. 3. The management system according to 1 or 2.   The notification unit is configured to determine whether the number of destinations included in a plurality of destination tables of the destination table set is determined by the second determination unit, regardless of a result of the determination by the first determination unit. 4. The management system according to claim 3, wherein when it is determined that the number is not within the number of manageable destinations, a delivery result indicating an error is notified to the manager. 5. The manager further includes a display unit that displays a distribution result based on the created task according to the notification from the client,
When receiving an instruction to recover a task corresponding to a distribution result indicating an error, the creation unit of the manager automatically sets a recovery task that is successfully distributed to at least a part of the distribution target set in the task. The management system according to claim 4, wherein the management system is created. A second acquisition unit that acquires the number of destinations for each destination table from the network device to be distributed;
In the case where a plurality of destination tables of the destination table set are distributed based on information on the number of destinations for each destination table managed by the distribution target network device acquired by the second acquisition unit, Third determining means for determining whether or not the number of destinations that can be managed by the network device to be distributed is exceeded;
In the case where the third determination means distributes a plurality of destination tables of the destination table set and determines that the number of destinations that can be managed by the distribution target network device is not exceeded, the destination table set is Calculation for calculating a difference between the number of destinations for each destination table included and the number of destinations for each destination table corresponding to the destination table and managed by the network device to be distributed acquired by the second acquisition unit. 2. The management system according to claim 1, further comprising: means.   The distribution means of the client may be configured such that, among the plurality of destination tables, the number of destinations included in the destination table is the number of destinations included in the destination table managed by the distribution target network device corresponding to the destination table. 7. The management system according to claim 6, wherein the distribution is performed in order from a destination table having a smaller number and a larger difference.   The management system according to any one of claims 1 to 7, wherein the manager and the client are installed in one information processing device. A method in a management system that includes a plurality of network devices, a client that communicates with the plurality of network devices, and a manager that manages the client,
The manager,
A management step of managing a destination table set including a plurality of destination tables including one or more destinations;
A creating step of creating a task in which the destination table set and a network device to be distributed are set, and
The client,
A first determination step of determining whether or not the network device to be distributed can manage a plurality of destination tables of the destination table set based on the task created by the manager;
A second determination step of determining whether the number of destinations included in the plurality of destination tables of the destination table set is within the number of destinations that can be managed by the distribution target network device;
The network device to be delivered is determined to be capable of managing the plurality of destination tables in the first determination step, and the destination included in the plurality of destination tables of the destination table set in the second determination step When it is determined that the number of destinations is within the number of manageable destinations, a distribution step of distributing distribution data including a plurality of destination tables of the destination table set to the distribution target,
The network device to be distributed is determined to be unable to manage the plurality of destination tables in the first determination step, and the number of destinations included in the plurality of destination tables of the destination table set in the second determination step Is determined to be within the number of manageable destinations, generating a destination table that can be managed by the network device to be distributed using destinations included in the plurality of destination tables of the destination table set. And a process,
In the method, the distribution step includes distributing distribution data including the generated destination table to the distribution target. Computer
Based on the task in which the destination table set created by the manager that manages the destination table set including a plurality of destination tables including one or more destinations and the network device to be distributed are set, the network device to be distributed is First determining means for determining whether or not a plurality of destination tables in the destination table set can be managed;
A second determination unit that determines whether the number of destinations included in the plurality of destination tables of the destination table set is within the number of destinations that can be managed by the distribution target network device,
The network device to be distributed is determined by the first determination unit to be capable of managing the plurality of destination tables, and the destination included in the plurality of destination tables of the destination table set by the second determination unit. When it is determined that the number of destinations is within the number of manageable destinations, distribution means for distributing distribution data including a plurality of destination tables of the destination table set to the distribution target,
The number of destinations included in the plurality of destination tables of the destination table set is determined by the first determination unit to be unable to manage the plurality of destination tables, and the second determination unit determines that the network device to be distributed cannot manage the plurality of destination tables. Is determined to be within the number of manageable destinations, generating a destination table that can be managed by the network device to be distributed using destinations included in the plurality of destination tables of the destination table set. Means,
The distribution means distributes distribution data including the generated destination table to the distribution target;
A program for functioning as a client.

Images