JP2020135607A - Information processing program - Google Patents

Abstract

To provide an information processing program capable of appropriately executing a function even in the case that a common database does not exist.SOLUTION: A setting application 161 causes a PC 100 to execute: acquisition processing for acquiring a first device list showing identification information of a plurality of MFPs 200 from a common DB 155 if the common DB 155 is constructed by installing a management application 151 in the PC 100, and acquiring a second device list showing identification information of the plurality of MFPs 200 by retrieving the plurality of MFPs 200 through a communication IF 160 if the common DB 155 is not constructed in a storage part 150; first display processing for displaying the first device list or the second device list in a display part 120; and communication processing for transmitting or receiving setting data among two or more devices selected from the first device list or the second device list displayed by the first display processing.SELECTED DRAWING: Figure 2

Description

The present application relates to an information processing program that transmits or receives a setting file to and from a plurality of communication devices.

In Patent Document 1, when the common basic information (B) stored in the storage unit of the started application and the common basic information (A) stored in the common database do not match, the common basic information (B) is provided. A technique for overwriting the common basic information (A) and executing processing using the common basic information (A) is disclosed.

Japanese Unexamined Patent Publication No. 2013-164706

However, the technique described in Patent Document 1 is based on the premise that a common database has already been constructed when the second application is operated. Therefore, for example, how an application that uses a common database operates when a common database is not constructed is not considered in Patent Document 1.

Therefore, an object of the present application is to provide an information processing program capable of appropriately executing a function even when a common database does not exist.

In order to achieve the above object, the information processing program of the present application is a first information processing for a terminal device including a communication unit capable of communicating with a plurality of communication devices, an operation unit, a display unit, and a storage unit. The first information processing program is a program, and when a second information processing program different from the first information processing program is installed in the terminal device to construct a common database in the storage unit, the first information processing program is stored in the common database. In the stored first device list, when the first device list showing the identification information of a plurality of communication devices is acquired and the common database is not constructed in the storage unit, a plurality of communications are performed via the communication unit. An acquisition process for acquiring a second device list indicating identification information of a plurality of communication devices by searching for a device, a first display process for displaying the first device list or the second device list on a display unit, and a first display. The terminal device is made to execute the communication process of transmitting or receiving the setting data between the first device list or the two or more devices selected from the second device list displayed by the display process.

According to the information processing program of the present application, it is possible to appropriately execute a function even when a common database does not exist.

It is a schematic diagram which shows the personal computer which executes the information processing program which concerns on one Embodiment of this application, and the multifunction device which is connected to the personal computer in communication. It is a block diagram which shows a part of the configuration example of the information processing program which concerns on one Embodiment of this application, and is the figure which shows an example of the format of data stored in a database. It is a figure which shows each example of the main screen and the drop-down list which are displayed when the setting application is started. It is a figure which shows an example of each of the main screen when the "Backup Setting" function is selected, and the main screen when the "PJL Activation" function is selected. It is a figure which shows an example of "Add Devices" screen. It is a figure which shows an example of a communication setting screen. It is a figure which shows an example of a communication setting screen. It is a flowchart of cooperation processing. It is a flowchart of a device list display process. It is a flowchart of processing at the time of execution button selection. It is a flowchart of "PLJ Activation" map creation process.

Hereinafter, embodiments of the present application will be described in detail with reference to the drawings.
(System configuration)

FIG. 1 is a schematic view showing a personal computer 100 that executes an information processing program according to an embodiment of the present application, and a multifunction device 200 that is communicably connected to the personal computer 100. Hereinafter, the personal computer 100 is referred to as a PC 100, and the multifunction device 200 is referred to as an MFP 200. MFP is an abbreviation for multifunction peripheral.

The PC 100 includes an operation unit 110, a display unit 120, a voice I / O (input / output) 130, a CPU (central processing unit) 140, a storage unit 150, and a communication IF (interface) 160.

The operation unit 110 is typically composed of a keyboard and a mouse.

The display unit 120 is composed of a display device such as a liquid crystal display or an organic EL (electro-luminescence) display, a drive circuit for driving the display device, and the like. When a touch panel type display unit 120 is used, the user can perform an input operation by clicking an input button on the screen. Therefore, in this case, the display unit 120 also serves as the operation unit 110. Note that a click is a point-and-click, which means that an object is executed or opened (hereinafter, the same applies).

The voice I / O 130 is composed of a microphone, a speaker, a voice processing circuit, and the like.

The CPU 140 executes various application programs (hereinafter abbreviated as "applications") including the information processing program of the present embodiment, firmware, and the like.

The storage unit 150 includes a ROM (read only memory), a RAM (random access memory), an HDD (hard disk drive), an SSD (solid state drive), an optical disk drive, and the like. Firmware and various data are stored in the ROM. The RAM is used as a temporary storage unit for the CPU 140 to load an application and execute various processes.

The storage unit 150 stores an OS (operating system), an information processing program of the present embodiment, and various other applications and data.

Various applications including the information processing program of the present embodiment can be downloaded from an external server (not shown) via the communication IF160. In addition, various applications may be downloaded from an external device (not shown) via a USB (universal serial bus) interface (IF) provided on the PC 100.

The communication IF 160 connects the PC 100 to the communication network 300 and connects an external device to the PC 100. Since the communication network 300 assumes a wired or wireless LAN (local area network) in the present embodiment, the communication IF 160 is a LAN IF (local area network interface) or a WLAN IF (wireless LAN interface). Of course, a wired LAN and a wireless LAN may exist at the same time, and in this case, the communication IF 160 includes both a LAN IF and a WLAN IF. The IF that directly connects an external device to the PC 100 includes the above-mentioned USBIF, Bluetooth® IF, and the like.

In this embodiment, a plurality of MFPs 200 are connected to the communication network 300. In the present embodiment, each MFP 200 is the same model of the same manufacturer for convenience of explanation, but the present invention is not limited to this, and may be of different manufacturers or different models of the same manufacturer. Further, in the present embodiment, the MFP is mentioned as an example of the communication device, but the present invention is not limited to this, and a single printer, scanner, or copier may be used, or the MFP and the printer, scanner, and copier may be used. It may be a mode that exists at the same time.

A single MFP 200 is also directly connected to the PC 100 without going through the communication network 300. As the connection IF at this time, the USB IF is used in this embodiment.

A proxy server 250 is further connected to the communication network 300, and the proxy server 250 is connected to the Internet 350. The proxy server 250 plays a role of connecting a device connected to the communication network 300, that is, in the present embodiment, the PC 100 and each MFP 200 to the Internet 350 while maintaining security.

The management server 270 and the mail server 290 are connected to the Internet 350. The management server 270 manages the paid functions provided in each MFP 200, and the mail server 290 sends and receives mail. When the PC 100 accesses the management server 270 and the mail server 290, it accesses the proxy server 250. The MFP 200 can theoretically access the management server 270 and the mail server 290 via the proxy server 250, but in the present embodiment, the MFP 200 does not access the management server 270 and the mail server 290.
(Organization of information processing program)

As shown in FIG. 2A, the information processing program of the present embodiment is composed of a management application 151 and a setting application 161.

The management application 151 is an application that can display the status of the MFP 200 on the display unit 120 for each device and manage the status. The management application 151 is also a program for executing functions (“Send Files”, “Backup Settings”, “Send Log”, “Notification”) for transmitting or receiving setting files to and from the MFP 200. The management application 151 is installed in the storage unit 150 of the PC 100, for example, in the HDD by installation. The CPU 140 loads the contents of the management application 151 into the RAM of the storage unit 150 and executes the background service 153. Then, when the user clicks an icon (not shown) instructing the executable file of the installed management application 151, the program of the first user interface control layer (hereinafter abbreviated as "first UI control layer") 152 is executed. To.

FIG. 2A shows a part of the configuration example of the loaded management application 151 and the setting application 161. The management application 151 has a hierarchical structure as shown in FIG. 2A, and includes a first UI control layer 152, a background service 153, and a data service layer 154 from the uppermost layer to the lower layers. A database (DB) 155 is connected to the data service layer 154. Further, a business logic layer 156, a data control layer 157, a protocol layer 158, and a communication interface layer 159 are provided below the background service 153. The business logic layer 156 to the communication interface layer 159 are referred to as a platform (PF) 165. The business logic layer 156 is accessed by the first UI control layer 152 or the second user interface control layer (hereinafter, abbreviated as "second UI control layer") 162 described later through the background service 153, and the first. There are cases where the 2UI control layer 162 is performed without passing through the background service 153 (details of each case will be described later).

The management program 151 of the first UI control layer 152 is a program for providing a GUI (graphical user interface) to a user of the PC 100, accepting a user operation for the GUI, and setting and changing various parameters. Further, the data service layer 154 and the business logic layer 156 are accessed via the background service 153, various functions are executed with the MFP 200, and the result is displayed on the GUI.

The management program 151 of the background service 153 is a program that can be executed as a background service on the OS, and has a role of maintaining the data service layer 154 in response to a request from the first UI control layer 152. When updating the data of the data service layer 154, the business logic layer 156 of the PF 165 is called and the result is stored in the data service layer 154.

The management program 151 of the data service layer 154 is a program for providing an API (application programming interface) for reading / writing data to / from DB 155 (also, exclusive control at that time), and adding or deleting data. In addition to this, the management program 151 of the data service layer 154 manages the device action scenario executed by the background service 153, and between the first UI control layer 152 and the background service 153. It provides a notification mechanism. The device action scenario (hereinafter abbreviated as "scenario") is information that defines the order in which the functions provided by the management program 151 of the business logic layer 156 are executed.

The management program 151 of the business logic layer 156 is a program for accessing the data control layer 157 and providing a function for realizing a function executed by using the management application 151 and the setting application 161. The functions provided are, for example, the "Discovery" function, the "Send Files" function and the "Backup Settings" function.

The "Discovery" function is a function for searching the MFP 200 that is communicably connected to the PC 100. When the CPU 140 calls the "Discovery" function, it transmits a packet to the broadcast address via the communication IF 160, and transmits the information (for example, model name, IP address, and node name) output by the MFP 200 in response to the packet to the communication IF 160. Receive via. The CPU 140 assigns a device ID that uniquely identifies the MFP 200 to each responding MFP 200, and generates a device list shown in FIG. 2B based on the information received from each MFP 200. In the device list (b), information that is not received by the "Discovery" function, for example, "whether or not there is a paid function", is unicast by sending a packet to the IP address indicated by the device ID described in the device list. You can get it with. The information about the MFP 200 described in the device list of FIG. 2B is only an example, and may include a serial number, a MAC address (media access control address), and the like in addition to the above information. Any part of the above information may not be included.

The "Send Files" function is a function that sends a setting file to the MFP 200. When the CPU 140 calls the "Send Files" function by passing the device ID and the storage location of the setting file as arguments, the setting file is read from the storage location and the read setting file is transmitted to the MFP 200 indicated by the device ID.

The "Backup Settings" function is a function that saves the settings file of the MFP200 in a specified storage location. When the CPU 140 calls the "Backup Settings" function by passing the device ID, the storage location of the setting file, and the backup item as arguments, the settings corresponding to the backup items are extracted from the various settings of the MFP 200 indicated by the device ID and set file. And save the setting file in the save location.

Further, various functions other than these are provided, but since they are not necessary for explaining the present embodiment, further description will be omitted.

The management program 151 of the data control layer 157 inputs / outputs data to / from the MFP 200 by using MIB (management information base), PJL (printer job language), JSON (JavaScript (registered trademark) object notation), or the like. It is a program of.

The management program 151 of the protocol layer 158 provides input / output of data to the USB port of the designated MFP 200 and input / output of data to port 9100 of TCP (transmission control protocol). Further, the management program 151 of the protocol layer 158 inputs / outputs data using the specified MFP200's SNMP (simple network management protocol), and inputs / outputs data using the specified MFP200 and the service's HTTP (hypertext transfer protocol). I will provide a.

The management program 151 of the communication interface layer 159 is used when a printer driver, a USB driver, a socket, or an HTTP is used for data input / output.

The DB 155 stores various information related to the MFP 200, such as a list of the MFP 200 (that is, the device list), the status of each MFP 200, and a log.

On the other hand, the setting application 161 is an application that makes various settings for the MFP 200. The setting application 161 is also a program for executing functions (“Send Files” and “Backup Settings”) for transmitting or receiving a setting file with the MFP 200. It can be said that the setting application 161 is a simple application having fewer functions that can be executed than the management application 151. The setting application 161 is installed in the storage unit 150 of the PC 100, for example, in the HDD in the form of an executable file. That is, the setting application 161 is a program that does not need to be installed. Then, when the user clicks an icon (not shown) instructing the execution file of the setting application 161, the setting program 161 of the second UI control layer 162 is executed.

Similar to the first UI control layer 152, the setting program 161 of the second UI control layer 162 is a program for providing the GUI to the user of the PC 100, accepting user operations for the GUI, and setting and changing various parameters. Is. Further, the second UI control layer 162 belongs to the same upper layer as the first UI control layer 152, and the setting program 161 of the second UI control layer 162 is data through the background service 153 like the management program 151 of the first UI control layer 152. It is possible to execute each function of the service layer 154 and read data from the DB 155. Further, the setting program 161 of the second UI control layer 162 directly accesses the business logic layer 156 without going through the background service 153, executes various functions with the MFP 200, and displays the result on the GUI.

As described above, the second UI control layer 162 also has a hierarchical structure together with the layers of the plurality of layers included in the management application 151.
(Details of setting app)

Since the setting application 161 is a simple application having fewer functions that can be executed than the management application 151 as described above, at least a part of the functions of the setting application 161 is included in the functions of the management application 151. Specifically, the "Send Files" function and the "Backup Settings" function executed by the setting application 161 are also provided on the management application 151 side.

One of the features of the setting application 161 is that the setting application 161 can cooperate with the management application 151. Then, in the linked state, the setting application 161 can share and use the DB 155 constructed by the management application 151 with the management application 151.

The setting application 161 is an executable file format program as described above, and is a program that does not need to be installed. DB155 is not built by the setting app 161. On the other hand, the management application 151 is a program introduced into the PC 100 by installation as described above. Then, when the management application 151 is installed, the DB 155 is constructed. Therefore, the setting application 161 is set to execute using the DB 155 of the management application 151 when the setting application 161 is in a state of cooperation with the management application 151 when executing its own function or process.

One of the features of the setting application 161 is that the DB 155 of the management application 151 cannot be used when it cannot be linked with the management application 151, but it can still execute its own functions and processes.

One of the features of the setting application 161 is to execute the functions and processes of the setting application 161 by using a part of the program configuration of the management application 151. Specifically, the setting application 161 uses the above-mentioned PF165 of the management application 151 when executing its own function or process.
(Screen configuration of the main screen)

FIG. 3A shows an example of the main screen 800 displayed on the display unit 120 when the setting application 161 is started.

The main screen 800 is provided with a function selection combo box 801 for selecting and switching the function realized by the setting application 161. A drop-down button 802 is provided at the right end of the function selection combo box 801. When the user clicks the drop-down button 802, the drop-down list 830 is displayed as shown in FIG. 3 (b).

The functions presented in the drop-down list 830 are "Send Files", "Backup Settings" and "PJL Activation".

"Send Files" is a function of transmitting a setting file applied to the MFP 200 (for example, one described by JSON, PJL, etc.) to the MFP 200. "Backup Settings" is a function of receiving a setting file showing the settings of the MFP 200 from the MFP 200 and saving it. “PJL Activation” is a function for enabling / disabling a paid function of the MFP 200 (“Custom UI” function in this embodiment). The "Custom UI" function is a function for customizing the display contents of the display unit (not shown) of the MFP 200 to a special display different from the normal display.

Returning to FIG. 3A, the main screen 800 is in a state where the “Send Files” function is selected by the function selection combo box 801. The “Add Devices” icon 803 is clicked when adding a device, that is, an MFP 200, to the destination list area 810. The “Refresh” icon 804 is for refreshing the state of the MFP 200 displayed in the destination list area 810 to the latest state. The “Application Settings” icon 805 is for displaying the application setting screen (see FIG. 6) on the display unit 120.

The "Set Files" button 806 sets the setting file (location) for the selected MFP200 displayed in the destination list area 810. The “Set Device Password” button 807 sets a password for the selected MFP 200 displayed in the destination list area 810. The “Delete Devices” button 808 deletes the selected MFP 200 from the destination list area 810.

The destination list area 810 is an area for displaying a list of file destinations.

The "Save as Deploy Profile" button 820 stores the current setting state as a profile. The “Apply” button 821 instructs the application of the current setting state.

FIG. 4A shows the main screen 840 when the “Backup Settings” function is selected by the function selection combo box 801. The main screen 840 of FIG. 4A assigns different reference numerals to the main screen 800 of FIG. 3A only for different configurations. Therefore, the description of the configuration to which the same reference numerals are given will be omitted.

The backup target list area 850 is an area for displaying a list of MFP 200s to be backed up.

The “Set Device Password” button 841 sets a password for the selected MFP 200 displayed in the backup target list area 850. Area 843 is an area for designating a backup location. Area 844 is an area for designating items to be backed up.

The "Save as Deploy Profile" button 845 stores the current setting state as a profile. The “Backup” button 846 instructs the backup in the current setting state.

FIG. 4B shows the main screen 860 when the “PJL Activation” function is selected by the function selection combo box 801. The main screen 860 of FIG. 4B assigns different reference numerals to the main screen 800 of FIG. 3A and the main screen 840 of FIG. 4A only for different configurations. Therefore, the description of the configuration to which the same reference numerals are given will be omitted.

The “PJL Activation” target list area 870 is an area for displaying a list of MFP 200s that are the targets of the “PJL Activation” function.

Area 862 is an area for designating a “Solution File”. The area 863 is an area for displaying the “Solution Provider ID”. The "Solution Provider ID" is specified from the detailed setting area displayed in the right pane 953 by selecting "Solution" from the setting item list in the left pane 952 of the communication setting screen 950 of FIG. 6 (a).

The "Save as Deploy Profile" button 864 stores the current setting state as a profile. The "Activate" button 865 indicates "PJL Activation" in the current setting state.
(Screen configuration of "Add Devices" screen)

5 (a) and 5 (b) show "Add Devices" screens 900, 900'displayed on the display unit 120 when the "Add Devices" icon 803 in the main screen 800 of FIG. 3 (a) is clicked. This is an example.

In the “Add Devices” screen 900 of FIG. 5A, when the setting application 161 is linked with the management application 151 and the DB 155 is shared between the setting application 161 and the management application 151, the “Add Devices” icon 803 is displayed. The screen displayed on the display unit 120 when clicked is shown.

The “Add Devices” screen 900 includes a left pane 901 and a right pane 905 as shown in FIG. 5 (a). The left pane 901 is an area for selecting a device list stored in the DB 155. In the illustrated example, one device list is stored in the DB 155, and one of them is displayed in the left pane 901. The right pane 905 displays the MFP 200 presented in the device list selected in the left pane 901. That is, when the setting application 161 is linked with the management application 151 and the DB 155 is shared between the setting application 161 and the management application 151, the device list can be acquired from the DB 155. Therefore, the device list acquired from the DB 155 is used. The "Add Devices" screen 900 is displayed.

On the other hand, the "Add Devices" screen 900'in FIG. 5B shows "Add" when the setting application 161 and the management application 151 are not linked and the DB 155 cannot be shared between the setting application 161 and the management application 151. Shows the screen displayed on the display unit 120 when the "Devices" icon 803 is clicked. If the setting application 161 and the management application 151 are not linked, the DB 155 cannot be shared between the setting application 161 and the management application 151. Therefore, in this case, the CPU 140 that executes the setting application 161 cannot acquire the device list from the DB 155 and cannot display the device list in the right pane 905. Therefore, the CPU 140 that executes the setting application 161 can obtain the device list. Generate. The “Add Devices” screen 900 ′ is displayed on the display unit 120 based on the device list generated by the CPU 140 that executes the setting application 161.
(Screen configuration of communication setting screen)

FIG. 6A is a diagram showing an example of the communication setting screen 950 included in the application setting screen, and the communication setting screen 950 is displayed on the display unit 120. The application setting screen transitions from the main screen 840 when the "Application Settings" icon 805 in the main screen 840 of FIG. 4A is clicked. The communication setting screen 950 is displayed by selecting "Network" from the setting item list in the left pane 952 of the application setting screen.

The communication setting screen 950 provides a selection area 951 for selecting whether or not to link the setting application 161 and the management application 151, and detailed settings for the setting items selected in the left pane 901 and the left pane 901. It has a right pane 953 for doing so.

The selection area 951 is provided with a switching button 954 that switches between the setting application 161 and the management application 151 as either linked (= On) or non-linked (= Off). In the communication setting screen 950 of FIG. 6A, since the switching button 954 is in the “Off” state, the setting application 161 and the management application 151 are not linked.

The detailed setting area for the SNMP setting is displayed in the right pane 953, and the user can set the SNMP setting from the detailed setting area.

The right pane 953 on the communication setting screen 950 of FIG. 6A displays the detailed setting area for the SNMP setting, whereas the right pane 953'on the communication setting screen 950 of FIG. 6B displays the detailed setting area. The difference is that it displays the advanced settings area for proxy settings. To switch between the detailed setting area for SNMP settings and the detailed setting area for proxy settings, select either the "SNMP" tab where "SNMP" is displayed or the "Proxy" tab where "Proxy" is displayed. It is done by.

When the user wants to save the SNMP setting or proxy setting set by the right pane 953 of FIG. 6A or the right pane 953'of FIG. 6B as the setting on the setting application 161 side, the user presses the OK button 955. click. On the other hand, when the user wants to cancel the SNMP setting or the proxy setting, the user clicks the cancel button 956.

FIG. 7 shows an example of the communication setting screen 960 when the setting application 161 and the management application 151 are linked.

A switching button 954 is displayed in the selection area 961 for selecting whether or not to link the setting application 161 and the management application 151, and the switching button 954 is in the "On" state. When the switching button 954 is in the "On" state, the communication setting in the setting application 161 uses the communication setting stored in the DB 155, that is, the communication setting set on the management application 151 side as it is, so that the user of the management application 151 can use it. , It is prohibited to freely change the communication settings on the management application 151 side. Therefore, the detailed setting area for communication settings is not displayed in the right pane 963. Then, in the selection area 961, the message "If you want to change the setting, please cancel the cooperation" is displayed. At this time, when the user switches the switching button 954 from the "On" state to the "Off" state, the communication setting screen 960 of FIG. 7 transitions to the communication setting screen 950 of FIG. 6A or FIG. 6B. ..
(Collaboration processing)

FIG. 8 is a flowchart showing a procedure of cooperation processing, which is one function of the setting application 161. The cooperation process performs a process of automatically or manually switching the cooperation or non-cooperation between the setting application 161 and the management application 151, and a process corresponding to the switching. The cooperation process is started when the setting application 161 is started, and is executed by the PC 100, particularly the CPU 140.

In FIG. 8, first, the CPU 140 that executes the setting program 161 of the second UI control layer 162 determines the activation state of the background service 153 (step (hereinafter abbreviated as “S”) 1). The CPU 140 transmits a command including the service name of the background service 153 to the OS. The OS that receives the command transmits information indicating the startup state of the background service 153 to the CPU 140 that executes the setting program 161 of the second UI control layer 162. The CPU 140 that executes the setting program 161 of the second UI control layer 162 determines the activation state of the background service 153 based on the received information.

The startup state of the background service 153 is one of "running", "stopping", and "non-existing" of the background service 153. "Running" is a state in which the background service 153 is registered in the OS and started. "Stopped" is a state in which the background service 153 is registered in the OS, but the startup is stopped. "Non-existent" means that the background service 153 is not registered in the OS or is deleted after registration. Even if the management application 151 is not installed on the PC 100, the background service 153 is in the "non-existent" state, but in the present embodiment, the management application 151 is managed on the premise that it is installed. It is not considered when the application 151 is not installed.

In this way, the CPU 140 can determine which of the above three states the background service 153 is in the determination of S1.

When it is determined in S1 that the background service 153 is being executed, the CPU 140 that executes the setting program 161 of the second UI control layer 162 sets the cooperation parameter to "ON" (S2). The cooperation parameter is an operation mode of the setting application 161 and is a parameter indicating an operation mode according to the activation state of the background service 153, and is any of three types of modes, "ON", "OFF", and "NG". It is configured to be able to take. The cooperation parameters are stored in the storage unit 150, for example, RAM. The operation mode determined during the cooperative processing in this way is called the default operation mode. The operation mode in the cooperative processing is determined in S2 above and S10 and S20 described later.

Next, the CPU 140 that executes the setting program 161 of the second UI control layer 162 requests the background service 153 to set the communication settings stored in the DB 155 (S3). The communication settings include the SNMP settings and the proxy settings, and the communication settings are the settings received from the user by the CPU 140 that executes the management application 151 and registered in the DB 155.

The CPU 140 that executes the management program 151 of the background service 153 makes a communication setting request to the data service layer 154 in response to a communication setting request from the second UI control layer 162. In response to this, the CPU 140 that executes the management program 151 of the data service layer 154 reads the communication setting from the DB 155 and transmits it to the background service 153.

The CPU 140 that executes the management program 151 of the background service 153 receives the communication setting and transmits the received communication setting to the second UI control layer 162. The CPU 140 that executes the setting program 161 of the second UI control layer 162 acquires the communication setting from the background service 153 (S4). In the present embodiment, as described above, both the SNMP setting and the proxy setting are registered in the DB 155 as the communication setting, and both of the settings are acquired from the DB 155. However, the communication requested in S3 and acquired in S4. The setting may be either the SNMP setting or the proxy setting. In this case, the setting that is not acquired from the DB 155 may be accepted from the user via the communication setting screen 950 of FIGS. 6 (a) and 6 (b). Alternatively, both the SNMP setting and the proxy setting may be accepted from the user via the communication setting screen 950 of FIGS. 6 (a) and 6 (b) without being acquired from the DB 155.

Next, the CPU 140 that executes the setting program 161 of the second UI control layer 162 requests the background service 153 for the device list (S5). In response to this, the CPU 140 that executes the management program 151 of the background service 153 makes a device list request to the data service layer 154. The CPU 140 that executes the management program 151 of the data service layer 154 reads the device list from the DB 155 and transmits the device list to the background service 153.

The CPU 140 that executes the management program 151 of the background service 153 transmits the received device list to the second UI control layer 162. In response to this, the CPU 140 that executes the setting program 161 of the second UI control layer 162 acquires the device list from the background service 153 (S6).

Then, the CPU 140 that executes the setting program 161 of the second UI control layer 162 displays the communication setting screen on the display unit 120 based on the cooperation parameters (S7). FIG. 7 shows an example of the communication setting screen 960 displayed in S7. A switching button 954 is displayed in the selection area 961 of the communication setting screen 960, and the switching button 954 is in the "On" state indicating that the setting application 161 and the management application 151 are linked. Further, in the selection area 961, the message "If you want to change the setting, please cancel the cooperation" is displayed. Then, as described above, nothing is displayed on the right pane 963 of the communication setting screen 960, and the communication setting cannot be changed. In the present embodiment, the right pane 963 of the communication setting screen 960 is hidden, but the present invention is not limited to this, and is displayed in the right pane 953, 953'of the communication setting screen 950 of FIGS. 6A and 6B. The detailed settings made may be grayed out.

When the user clicks the OK button 965 or the cancel button 966 on the communication setting screen 960, the CPU 140 that executes the setting program 161 of the second UI control layer 162 displays the main screen (for example, the main screen 800 in FIG. 3A). It is displayed on the display unit 120 (S8).

On the other hand, when it is determined in S1 that the background service 153 is stopped, the CPU 140 that executes the setting program 161 of the second UI control layer 162 sets the cooperation parameter to "OFF" (S10) and sets the cooperation parameter to Based on this, the communication setting screen is displayed on the display unit 120 (S11). 6 (a) and 6 (b) show an example of the communication setting screen 950 displayed by S11. As described above, FIG. 6A shows an example in which the “SNMP” tab is selected and the detailed setting area for SNMP settings is displayed in the right pane 953, and FIG. 6B shows an example in which the “Proxy” tab is displayed. An example is shown in which the detailed setting area of the proxy setting is displayed in the right pane 953 after being selected.

Further, as described above, the switching button 954 is provided in the selection area 951 on the communication setting screen 950 of FIGS. 6A and 6B. On the communication setting screen 950, the switching button 954 is in the "Off" state. When the switching button 954 is in the "Off" state, the background service 153 is registered in the OS, but is in the "stopped" state. If the activation state of the background service 153 is the above-mentioned "non-existent" state, the switching button 954 is not displayed on the display unit 120.

When the switching button 954 is displayed, the user can switch the state of the switching button 954 from the "Off" state to the "On" state as described above.

Returning to FIG. 8, the CPU 140 that executes the setting program 161 of the second UI control layer 162 determines whether or not the cooperation ON operation has been accepted via the operation unit 110 (S12). This cooperation ON operation is an operation of switching the switching button 954 from the "Off" state to the "On" state. Specifically, the user uses the mouse of the operation unit 110 to move the cursor (not shown) to the knob (black circle in FIG. 6) of the switching button 954, drag it to the right end, and then drop it. Of course, this user operation is an example, and any operation method may be used as long as the switching button 954 can be switched from the "Off" state to the "On" state.

When it is determined in S12 that the cooperation ON operation has been accepted via the operation unit 110, the CPU 140 that executes the setting program 161 of the second UI control layer 162 sets the cooperation parameter to "ON" (S13) and sets the OS to the OS. Instructs the activation of the background service 153 (S14). As a result, the management program 151 of the background service 153 starts to start, and the background service 153 is being executed.

Then, the CPU 140 that executes the setting program 161 of the second UI control layer 162 advances the processing to the above S3. Since the processing after S3 has been described above, the description thereof will be omitted.

On the other hand, in S12, when it is determined that the cooperation ON operation has not been performed, the CPU 140 that executes the setting program 161 of the second UI control layer 162 is displayed by the user on the communication setting screens 950 of FIGS. 6A and 6B. Wait until the click of the OK button 955 or the cancel button 956 is accepted. When the background service 153 is stopped, the setting application 161 cannot acquire the communication setting from the background service 153, so that the user needs to manually set the communication setting. Therefore, the user sets the SNMP settings from the communication setting screen 950 of FIG. 6A, and sets the proxy from the communication setting screen 950 of FIG. 6B. Then, when the user clicks the OK button 955, the CPU 140 that executes the setting program 161 of the second UI control layer 162 stores the communication settings including the SNMP settings and the proxy settings in the storage unit 150, for example, RAM (S15). After that, the process proceeds to S8, and the main screen (for example, the main screen 800 in FIG. 3A) is displayed on the display unit 120.

When it is determined in the above S1 that the background service 153 does not exist, the CPU 140 that executes the setting program 161 of the second UI control layer 162 sets the cooperation parameter to "NG" (S20), and based on the cooperation parameter. The communication setting screen 950 is displayed on the display unit 120 (S21). The communication setting screen 950 displayed in S21 is a display of the selection area 951 hidden from the communication setting screens 950 of FIGS. 6A and 6B. Therefore, on the communication setting screen displayed in S21, the user manually sets the communication. The CPU 140 that executes the setting program 161 of the second UI control layer 162 waits until the OK button 955 or the cancel button 956 is accepted from the user on the communication setting screen 950. Then, when the SNMP setting and the proxy setting are accepted from the communication setting screen 950 and the OK button 955 is clicked, the CPU 140 that executes the setting program 161 of the second UI control layer 162 performs the SNMP setting and the SNMP setting in the same manner as in S15. The communication settings including the proxy settings are stored in the storage unit 150 (S22). Then, the CPU 140 that executes the setting program 161 of the second UI control layer 162 proceeds to the above S8 and displays the main screen (for example, the main screen 800 of FIG. 3A) on the display unit 120.

Since the communication settings stored in S14 and S22 are not stored in the DB 155, they are not used in the management application 151. The operation of the setting application 161 writing the communication setting to the DB 155 is prohibited. This is because the setting application 161 is a simple application having fewer functions than the management application 151, so that the setting application 161 overwrites the communication setting received by the setting application 161 with the communication setting stored in the DB 155. This is because there is a risk that the function of the management application 151 will not operate normally when the management application 151 is executed.
(Device list display processing)

FIG. 9 is a flowchart showing the procedure of the device list display process. The device list display process is started when the “Add Devices” icon 803 in the main screen 800 of FIG. 3 (a) is clicked, and the “Add Devices” screen 900 of FIG. 5 (a) and the above FIG. 5 This is a process of displaying any one of the “Add Devices” screen 900 ′ of (b) on the display unit 120. The device list display process is executed by the PC 100, particularly the CPU 140.

In FIG. 9, first, the CPU 140 that executes the setting program 161 of the second UI control layer 162 determines whether or not the cooperation parameter is set to “ON” (S31). In S31, when it is determined that the cooperation parameter is set to "ON", that is, the setting application 161 and the management application 151 are linked, and the DB 155 is set between the setting application 161 and the management application 151. If it can be shared, the CPU 140 that executes the setting program 161 of the second UI control layer 162 acquires the device list from the DB 155 (S32). In the process of S32, it is necessary to acquire the device list from the DB 155 according to the same procedure as the procedure described in S5 and S6 of FIG. 8, but the procedure for acquiring the device list from the DB 155 has already been described in detail. , The description is omitted.

Next, the CPU 140 that executes the setting program 161 of the second UI control layer 162 displays the “Add Devices” screen 900 of FIG. 5A on the display unit 120 based on the device list acquired in S32 (S33). ) After that, the device list display process is terminated.

On the other hand, in the above S31, when it is determined that the cooperation parameter is not set to "ON", that is, the setting application 161 and the management application 151 are not linked, and between the setting application 161 and the management application 151. If the DB 155 cannot be shared, the CPU 140 that executes the setting program 161 of the second UI control layer 162 cannot acquire the device list from the DB 155. Therefore, the CPU 140 that executes the setting program 161 of the second UI control layer 162 searches for the MFP 200 that is communicably connected to the PC 100 (S34). Specifically, the search for the MFP 200 is performed by the CPU 140 that executes the setting program 161 of the second UI control layer 162 by calling the above-mentioned "Discovery" function to the business logic layer 156. The details of the processing performed by calling the "Discovery" function have been described above, and the description thereof will be omitted.

Since the MFP 200 that is communicably connected to the PC 100 is searched by the process of S34, the CPU 140 that executes the setting program 161 of the second UI control layer 162 is, for example, based on the search result, for example, FIG. 2 (b). Create the device list shown in (S35). Then, the CPU 140 that executes the setting program 161 of the second UI control layer 162 displays the “Add Devices” screen 900 ′ of FIG. 5B on the display unit 120 based on the created device list (S36). , Ends the device list display process.

In this way, when the setting application 161 is linked with the management application 151 and shares the DB 155 with the management application 151, the device list generated on the management application 151 side and registered in the DB 155 is acquired from the DB 155. I try to use it. On the other hand, the setting application 161 is not linked with the management application 151, and when the DB 155 cannot be shared with the management application 151, the setting application 161 is set to generate a device list.

In the linked process of FIG. 8, the device list is not created when the background service 153 is stopped or does not exist. Therefore, in this case, the device list is created after the device list display process is executed, but the present invention is not limited to this, and the device list may be created in the linked process. Specifically, in the cooperative processing, for example, the processing of S34 and S35 is inserted immediately after S15 and immediately after S22.
(Processing when the execute button is selected)

FIG. 10 shows any of a screen for setting any function of the setting application 161 (main screen 800 in FIG. 3A, main screen 840 in FIG. 4A, and main screen 860 in FIG. 4B). Is a flowchart showing the procedure of the process executed when the execute button (any of the “Apply” button 821, the “Backup” button 846, and the “Activate” button 865) is clicked (selected). .. The process at the time of selecting the execute button is executed by the PC 100, particularly the CPU 140. The processing at the time of selecting the execute button includes the "Apply" button 821 in the main screen 800 of FIG. 3 (a), the "Backup" button 846 in the main screen 840 of FIG. 4 (a), and the main screen of FIG. 4 (b). It is started when any one of the "Activate" buttons 865 in 860 is clicked.

In FIG. 10, first, the CPU 140 that executes the setting program 161 of the second UI control layer 162 determines which function the displayed function is (S41). That is, in this determination, the CPU 140 determines which of the "Apply" button 821, the "Backup" button 846, and the "Activate" button 865 is clicked.

When it is determined that the "Apply" button 821 is clicked in S41, the CPU 140 that executes the setting program 161 of the second UI control layer 162 executes the "Send Files" map creation process that creates the "Send Files" map. (S42). The "Send Files" map is a map in which lines are provided for each MFP 200 selected by the user as the target for executing the function, and the "Send Files" command, the storage location of the configuration file, and the device ID are aligned on each line. .. Specifically, the "Send Files" command is a command instructing to call the "Send Files" function provided by the management program 151 of the data service layer 154. Then, the storage location of the setting file and the device ID are used as arguments of the "Send Files" function when calling the "Send Files" function.

Next, the CPU 140 that executes the setting program 161 of the second UI control layer 162 executes a command transmission process line by line for the created “Send Files” map (S46). In the command transmission process, the CPU 140 calls the "Send Files" function to the data service layer 154. In response to this, the CPU 140 that executes the management program 151 of the business logic layer 156 executes the called "Send Files" function, and uses the lower data control layer 157, the protocol layer 158, and the communication interface layer 159. , Perform a task that demonstrates the “Send Files” function.

Next, the CPU 140 that executes the setting program 161 of the second UI control layer 162 receives the execution result (S47), updates the progress status display (S48), and then moves to the next line to move to the next line, S46 to S48. Repeat the process.

Before the process proceeds from S42 to S45, the CPU 140 that executes the setting program 161 of the second UI control layer 162 determines the protocol (TCP / IP (9100) or HTTPS) that communicates with the MFP 200 by using the SNMP settings. To do.

Then, when the processing of S46 to S48 for all the lines of the "Send Files" map is completed, the CPU 140 displays the execution result on the display unit 120 (S49), and ends the processing when the execution button is selected.

On the main screen 800 of FIG. 3A, the user selects the MFP 200 to be the target of the “Send Files” function, specifies the setting file using the “Set Files” button 806, and if necessary, “Set Device”. When the password is set using the Password "button 807 and then the" Apply "button 821 is clicked, the process when the execute button is selected is executed, and the communication IF 160 sets the MFP 200 as the target of the" Send Files "function. Data including information indicating the application of the file and a configuration file is transmitted. The MFP 200 applies the configuration file based on the received data. For communication between the PC 100 and the MFP 200, for example, the SNMP setting is used.

When it is determined that the "Backup" button 846 is clicked in the above S41, the CPU 140 that executes the setting program 161 of the second UI control layer 162 executes the "Backup Settings" map creation process that creates the "Backup Settings" map. (S43). The "Backup Settings" map is mapped by providing a line for each MFP200 selected by the user as the target for executing the function, and aligning the "Backup Settings" command, the storage location of the setting file, the backup item, and the device ID on each line. It is a thing. Specifically, the "Backup Settings" command is a command instructing to call the "Backup Settings" function provided by the management program 151 of the data service layer 154. Then, the storage location of the setting file, the backup item, and the device ID are used as arguments of the "Backup Settings" function when calling the "Backup Settings" function.

In the subsequent processing of S46 to S48, only the map to be processed is different, and the processing content is almost the same between the “Send Files” map and the “Backup Settings” map. Therefore, the description of the processing of S46 to S48 will be omitted.

On the main screen 840 of FIG. 4A, the user selects the MFP200 to be the target of the "Backup Settings" function, specifies the location to back up from the area 843, and specifies the items to be backed up from the area 844. , When the "Backup" button 846 is clicked, the process when the execute button is selected is executed, and the information and backup instructing the MFP200, which is the target of the "Backup Settings" function, to read and send the setting file from the communication IF160. Data containing information indicating the target item is transmitted. The MFP 200 transmits data including a setting file generated by extracting the setting corresponding to the item to be backed up from the current setting based on the received data to the PC 100. When the PC 100 receives the data from the MFP 200, the CPU 140 that executes the management program 151 of the PF 165 transmits the setting file included in the received data from the business logic layer 156 to the second UI control layer 162. The CPU 140 that executes the setting program 161 of the second UI control layer 162 saves the received setting file in a designated backup location.

When it is determined that the "Activate" button 865 has been clicked in S41, the CPU 140 executes the "PJL Activation" map creation process (S44).

FIG. 11 is a flowchart showing the procedure of the “PJL Activation” map creation process.

In FIG. 11, first, the CPU 140 that executes the setting program 161 of the second UI control layer 162 sets the authentication ID (“Solution Provider ID”) displayed in the area 863 of the main screen 860 of FIG. 4B to the business of PF165. It is transmitted to the logic layer 156 (S51). The CPU 140 that executes the management program 151 of the business logic layer 156 uses the lower data control layer 157, the protocol layer 158, and the communication interface layer 159 to transmit the received authentication ID from the communication IF 160 via the proxy server 250. Send to the management server 270. The management server 270 performs authority authentication based on the received authentication ID, and transmits the authentication result to the PC 100.

The CPU 140 that executes the management program 151 of the business logic layer 156 acquires the authentication result received from the communication IF 160 by using the lower data control layer 157, the protocol layer 158, and the communication interface layer 159, and obtains the second UI control layer 162. Send to. The CPU 140 that executes the setting program 161 of the second UI control layer 162 determines whether or not the authentication result received from the business logic layer 156 is successful (S52).

When it is determined in S52 that the authentication result is unsuccessful (S52: NO), the CPU 140 that executes the setting program 161 of the second UI control layer 162 does not create the "PJL Activation" map, but "PJL Activation". End the map creation process. In this case, since there is no "PJL Activation" map, the CPU 140 that executes the setting program 161 of the second UI control layer 162 cannot release the execution restriction of the specific function for any MFP 200.

On the other hand, in S52, when it is determined that the authentication result is successful (S52: YES), the CPU 140 that executes the setting program 161 of the second UI control layer 162 expands the MFP 200 selected as the control target on the map (S53). ). Then, the CPU 140 that executes the setting program 161 of the second UI control layer 162 expands the setting change command with authentication (setting change command with "PJL Activation") to all the lines of the map developed in S53 (S54).

Next, the CPU 140 that executes the setting program 161 of the second UI control layer 162 maps the solution file (“Solution File”) downloaded from the storage location input from the area 862 of the main screen 860 of FIG. 4 (b). It is set in all lines (S55), and the file path input to the UI, that is, the information (= file path) indicating the storage location of the file including the authentication ID is expanded to all the commands of the map (S56). The CPU 140 that executes the setting program 161 of the second UI control layer 162 stores the map created in this manner in a storage unit 150, for example, a RAM (S56), and ends the “PJL Activation” map creation process.

In the subsequent processing of S46 to S48, the processing contents are almost the same between the "Send Files" map and the "PJL Activation" map except that the map to be processed is different. Therefore, the description of the processing of S46 to S48 will be omitted.

On the main screen 860 of FIG. 4B, the user selects the MFP 200 to be the target of the "PJL Activation" function, specifies "Solution File" from the area 862, and displays the "Solution Provider ID" in the area 863. After that, when the "Activate" button 865 is clicked, the process when the execute button is selected is executed, and the setting change information with "PJL Activation", "Solution", is executed for the MFP200 which is the target of the "PJL Activation" function from the communication IF160. Data including the file paths of "File" and "Solution Provider ID" is sent. The MFP 200 activates the above-mentioned "Custom UI" function based on the received data, and switches the display content of its own display unit to a special display.
(effect)

As described above, the information processing program of the present embodiment is a setting application for a PC 100 including a communication IF 160 capable of communicating with a plurality of MFPs 200, an operation unit 110, a display unit 120, and a storage unit 150. The setting application 161 is the first device stored in the common DB 155 when the common DB 155 is constructed in the storage unit 150 by installing the management application 151 different from the setting application 161 in the PC 100. In the list, the first device list showing the identification information of the plurality of MFPs 200 is acquired (S32), and when the common DB 155 is not constructed in the storage unit 150, the plurality of MFPs 200 are searched via the communication IF160. (S34), the acquisition process of acquiring the second device list indicating the identification information of the plurality of MFPs 200 (S35), and the first display process of displaying the first device list or the second device list on the display unit 120 (S33). , S36) and the communication process (S46) for transmitting or receiving the setting data between the first device list or two or more devices selected from the second device list displayed by the first display process. Is executed by the PC 100.

As described above, in the information processing program of the present embodiment, even when the common DB 155 does not exist, the second device list showing the identification information of the plurality of MFPs 200 by searching the plurality of MFPs 200 via the communication IF160. Is acquired, and the setting data is transmitted or received between the two or more devices selected from the second device list, so that the function can be appropriately executed.

By the way, in this embodiment, the MFP 200 is an example of a "communication device". The communication IF160 is an example of a "communication unit". The setting application 161 is an example of the "first information processing program". The management application 151 is an example of the "second information processing program".

Further, the setting application 161 further has a determination process (S1) for determining whether or not the common DB 155 is constructed in the storage unit 150, and an operation mode when it is determined by the determination process that the common DB 155 is constructed. If the default of is set to the first mode (“ON”) and it is determined by the judgment process that the common DB 155 has not been constructed, the default of the operation mode is the second mode (“OFF” or “NG”). The PC100 is made to execute the setting process (S2, S10, S20) set to. Then, in the acquisition process, when the operation mode is set to the first mode, the first device list is acquired (S6), and when the operation mode is set to the second mode, the second device list is acquired. To do.

This is convenient because the default operating mode is automatically set so that the user does not have to set the default operating mode himself.

Further, the management application 151 includes a program of the background service 153, which is a service that operates in the background, and the judgment process determines that the common DB 155 is constructed when the background service 153 is running. If the background service 153 does not exist, it is determined that the common DB 155 has not been constructed (S1), and the acquisition process requests the background service 153 for the first device list when the background service 153 is running. Is transmitted (S5), and the background service 153 acquires the first device list read from the common DB 155 in response to the transmission of the command (S6).

As a result, it is determined whether or not the common DB 155 is constructed depending on the presence or absence of the background service 153, so that this determination can be easily performed.

Further, in the setting process, when the background service 153 is stopped by the judgment process, the operation mode is set to the second mode (S10), and the setting application 161 further sets the default operation mode set by the setting process. A second display process for displaying the switching button 954 for changing on the display unit 120, a reception process for accepting an operation performed via the operation unit 110 on the switching button 954 displayed by the second display process, and reception. When the operation for changing the operation mode from the second mode to the first mode by the process is received for the switching button 954, the start instruction of the background service 153 is stored in the storage unit 150. The PC 100 is made to execute the transmission process (S14) to be transmitted to the operating system.

As a result, the first device list read from the common DB 155 by the background service 153 can be used as the device list, so that the setting application 161 does not have to acquire the second device list, and the setting application 161 does not have to acquire the second device list. The burden on the service can be reduced.

By the way, the changeover button 954 is an example of an "operator".

Further, the switching button 954 is not displayed on the display unit 120 when it is determined by the determination process that the common DB 155 is not constructed.

As a result, when the common DB 155 is not constructed, the mode change operation cannot be performed, so that a malfunction can be prevented.

Further, if the second information processing program is installed on the PC 100 after the second device list is acquired by the acquisition process, it is prohibited to register the second device list in the common DB 155.

As a result, it is possible to prevent rewriting of the device list in the common DB 155 against the intention of the user.

Further, the communication IF 160 can communicate with the proxy server 250, and in the acquisition process, when it is determined by the determination process that the common DB 155 is constructed, the first proxy for communicating with the proxy server 250 from the common DB 155. When the setting is acquired (S4) and it is determined by the determination process that the common DB 155 is not constructed, the setting is acquired by accepting the second proxy setting for communicating with the proxy server 250 from the user (S21). In the communication process, after communicating with the proxy server 250 using the first proxy setting or the second proxy setting acquired by the acquisition process, the setting data is transmitted or received between the two or more selected MFPs 200. ..

As a result, when the common DB 155 is constructed, the proxy settings can also be read from the common DB 155 and obtained, so that it is not necessary to perform troublesome proxy settings, which is convenient.

Further, in the acquisition process, when it is determined by the determination process that the common DB 155 is constructed, the first SNMP setting for communicating with a plurality of MFP 200s according to the SNMP (simple network management protocol) is acquired from the common DB 155 (S4). ), When it is determined by the determination process that the common DB 155 has not been constructed, the second SNMP setting for communicating with a plurality of MFPs 200 according to the SNMP is acquired from the user (S21), and the communication process is acquired. Setting data is transmitted or received between two or more MFPs 200 selected by using the first SNMP setting or the second SNMP setting acquired by the process.

As a result, when the common DB 155 is constructed, the SNMP settings can also be read from the common DB 155 and acquired, so that it is not necessary to perform troublesome SNMP settings, which is convenient.

The setting application 161 is a program that can be executed without being installed on the PC 100, and the management application 151 is a program that can be executed by being installed on the PC 100.

100 PC
110 Operation unit 120 Display unit 140 CPU
150 Storage unit 160 Communication IF
250 Proxy server 270 Management server 290 Mail server 151 Management application 152 1st UI control layer 153 Background service 154 Data service layer 155 DB
156 Business logic layer 157 Data control layer 158 Protocol layer 159 Interface layer 161 Setting application 162 Second UI control layer 165 PF
200 MFP

Claims (9)

A first information processing program for a terminal device including a communication unit capable of communicating with a plurality of communication devices, an operation unit, a display unit, and a storage unit.
The first information processing program is
When a common database is constructed in the storage unit by installing a second information processing program different from the first information processing program in the terminal device, the first device list stored in the common database is used. Therefore, the first device list showing the identification information of the plurality of communication devices is acquired, and when the common database is not constructed in the storage unit, the plurality of communication devices are searched through the communication unit. By doing so, the acquisition process of acquiring the second device list indicating the identification information of the plurality of communication devices, and
The first display process for displaying the first device list or the second device list on the display unit,
A communication process for transmitting or receiving setting data between the first device list displayed by the first display process or two or more communication devices selected from the second device list.
Is executed by the terminal device.
Information processing program. The first information processing program further
Judgment processing for determining whether or not the common database is constructed in the storage unit, and
When it is determined that the common database has been constructed by the determination process, the default operation mode is set to the first mode, and when it is determined that the common database has not been constructed by the determination process. Is a setting process that sets the default operation mode to the second mode,
Is executed by the terminal device,
The acquisition process acquires the first device list when the operation mode is set to the first mode, and the second device when the operation mode is set to the second mode. Get the list,
The information processing program according to claim 1. The second information processing program includes a background service program, which is a service that operates in the background.
The determination process determines that the common database has been constructed when the background service is running, and determines that the common database has not been constructed when the background service does not exist.
In the acquisition process, when the background service is being executed, a command requesting the first device list is transmitted to the background service, and the background service causes the common database in response to the transmission of the command. Obtain the first device list read from
The information processing program according to claim 2. In the setting process, when the background service is stopped by the determination process, the operation mode is set to the second mode.
The first information processing program further
A second display process for displaying an operator for changing the default operation mode set by the setting process on the display unit, and
A reception process for accepting an operation performed via the operation unit on the operator displayed by the second display process, and
When the operation for changing the operation mode from the second mode to the first mode is received by the operator by the reception process, the storage unit issues an instruction to start the background service. Send processing to send to the operating system stored in
Is executed by the terminal device.
The information processing program according to claim 3. The operator is not displayed on the display unit when it is determined by the determination process that the common database has not been constructed.
The information processing program according to claim 4. When the second information processing program is installed in the terminal device after the second device list is acquired by the acquisition process, it is prohibited to register the second device list in the common database.
The information processing program according to any one of claims 1 to 5. The communication unit can communicate with the server and
In the acquisition process, when it is determined by the determination process that the common database has been constructed, the first proxy setting for communicating with the server is acquired from the common database, and the common database is acquired by the determination process. If it is determined that the database has not been built, the second proxy setting for communicating with the server is acquired by accepting from the user, and the database is acquired.
In the communication process, after communicating with the server using the first proxy setting or the second proxy setting acquired by the acquisition process, the setting data is exchanged with the two or more selected communication devices. Send or receive,
The information processing program according to any one of claims 2 to 6. In the acquisition process, when it is determined by the determination process that the common database has been constructed, the common database sets the first SNMP setting for communicating with the plurality of communication devices according to the SNMP (simple network management protocol). When it is determined by the determination process that the common database has not been constructed, it is acquired by accepting from the user a second SNMP setting for communicating with the plurality of communication devices according to the SNMP.
The communication process transmits or receives the setting data to or from the two or more selected communication devices using the first SNMP setting or the second SNMP setting acquired by the acquisition process.
The information processing program according to any one of claims 2 to 7. The first information processing program is a program that can be executed without being installed in the terminal device.
The second information processing program is a program that can be executed by being installed in the terminal device.
The information processing program according to any one of claims 1 to 8.

Images