JP2016194735A - Information acquisition device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information acquisition device that can flexibly cope with a change of an information acquisition destination and can easily obtain information needed by a user.SOLUTION: An information acquisition device is provided with: a data source setting file 1 for setting a relation between an information acquisition destination and a service; a mash-up template file 2 for setting a process specification corresponding to a service for information acquired by an information acquisition unit 4. A mash-up file for user transmission creation unit 5 processes information acquired from an information acquisition destination 9 by using information in the mash-up template file 2, and creates a mash-up file to reply to a terminal 10. The data source setting file 1 and the mash-up template file 2 are managed by a setting file management unit 7.SELECTED DRAWING: Figure 1

Description

  The present invention relates to an information acquisition device that acquires information via an information acquisition device such as a portable terminal or a server, and provides the user with a combination of such information.

  In recent years, services that create new information (hereinafter referred to as mashup) by combining information published on the Internet and local data have been widely provided. Information published on the Internet is published by API (Application Programming Interface) and libraries. These APIs and libraries are provided in different formats for each service. For example, there is an API that provides information provided by a restaurant search service or an accommodation facility search service in a data format such as XML (extensible Maskup Language) or JSON (Javascript (registered trademark) Object Notification). On the other hand, there is an API or library that provides an operation for displaying a feature on a map or an operation for changing a map type, such as Google Map (registered trademark).

  By combining these pieces of information, the user can easily create a unique WEB service or application. For example, it is possible to create a web service that mashups the map API provided by Google (registered trademark) and the flight status of the aircraft. The mashup app is also used for taxi dispatch services and for business.

  For example, Patent Document 1 discloses a technique related to individual information distribution when distributing information in a taxi dispatch service, and includes a device for storing a reference for distributing data to a user and a device for processing the reference. By using this, it is possible to provide only the information required by the user. Accordingly, it is possible to provide a vehicle allocation service that does not distribute unnecessary information (for example, information on a taxi on which another user has already been placed) to the user.

  Patent Document 2 discloses a technique for a fusion method in a Web application, and a Web application in which a display element that has not been accessed on the Web application is determined by communication with a user and the element is removed. It is realized to change to become. By combining these technologies, a mashup application and a mashup web application corresponding to each user are provided.

International Publication No. 2012-153362 JP 2010-282409 A

However, in the above-described conventional information acquisition apparatus, when adding / deleting information of an information acquisition destination such as a server, a part for analyzing information from each server has to be largely changed, which increases development cost. There was a problem.
Further, in the conventional information acquisition apparatus, the user cannot select acquisition information and can only acquire predetermined information, and thus it is difficult to acquire information required by the user. was there.

  The present invention has been made to solve the above-described problems, and provides an information acquisition device that can flexibly cope with a change in information acquisition destination and can easily acquire information required by a user. The purpose is to obtain.

  The information acquisition apparatus according to the present invention acquires information from an information acquisition destination in accordance with a service requested from a user terminal, performs information processing on the acquired information in response to the service, and responds to the user terminal A data source setting file that sets a relationship between an information acquisition destination and a service, an information acquisition unit that acquires information from the information acquisition destination using information in the data source setting file, and an information acquisition unit A mashup template file that sets the processing specifications corresponding to the information service and the information acquired from the information acquisition source using the information of the mashup template file, and creates a mashup file for responding to the user terminal And a mashup file creation unit.

  The information acquisition device of the present invention includes a data source setting file that sets a relationship between an information acquisition destination and a service, and a mashup template file that sets a processing specification corresponding to the information service acquired by the information acquisition unit, Since the mashup file for the user is created based on these files, it is possible to flexibly cope with the change of the information acquisition destination, and it is possible to easily obtain the information required by the user.

BRIEF DESCRIPTION OF THE DRAWINGS It is a block diagram which shows the information acquisition apparatus by Embodiment 1 of this invention. It is a block diagram of the information acquisition system to which the information acquisition apparatus by Embodiment 1 of this invention is applied. It is explanatory drawing which shows an example of the data source setting file of the information acquisition apparatus by Embodiment 1 of this invention. It is explanatory drawing which shows an example of the mashup template file of the information acquisition apparatus by Embodiment 1 of this invention. It is a flowchart which shows operation | movement of the information acquisition apparatus by Embodiment 1 of this invention. It is explanatory drawing which shows the user information of the information acquisition apparatus by Embodiment 1 of this invention. It is explanatory drawing which shows the user information management structure of the information acquisition apparatus by Embodiment 1 of this invention. It is explanatory drawing which shows the data source management structure of the information acquisition apparatus by Embodiment 1 of this invention. It is a flowchart which shows the addition / deletion process of the setting file of the information acquisition apparatus by Embodiment 1 of this invention. It is explanatory drawing which shows the mashup template file management structure of the information acquisition apparatus by Embodiment 1 of this invention. It is explanatory drawing which shows the example of deletion of the data source setting file and mashup template file of the information acquisition apparatus by Embodiment 1 of this invention, and the addition of user information.

Embodiment 1 FIG.
FIG. 1 is a block diagram showing an information acquisition apparatus according to Embodiment 1 of the present invention. FIG. 2 is a hardware configuration diagram of each unit in the information acquisition system to which the information acquisition apparatus of the present invention is applied.

  In FIG. 1, the information acquisition apparatus includes a data source setting file 1, a mashup template file 2, a setting file analysis unit 3, an information acquisition unit 4, a user transmission mashup file creation unit 5, a communication unit 6, and a setting file management unit. 7, a management structure file 8, an information acquisition destination 9, and a terminal 10.

The data source setting file 1 is a file for setting the relationship between the information acquisition destination 9 and the service requested by the user, and an example thereof is shown in FIG. In the data source setting file 1 shown in FIG. 3, the name of the service is described in the first column, and the ID corresponding to the information acquisition means described in the third column is described in the second column. . In the third and subsequent columns, information acquisition means corresponding to Service variables described in user information described later is described.
The mashup template file 2 is a file for setting processing specifications corresponding to the information service acquired by the information acquisition unit 4, and an example thereof is shown in FIG. The mashup template file 2 shown in FIG. 4 includes tag information enclosed by Get tags, store names, how to read store names, addresses, latitudes, longitudes, telephone numbers, holidays, business hours, store catches, points (total Evaluation), cooking / taste scores, and atmosphere scores. Information specified in the Get tag can be specified by the user or a third party, and the mashup template file 2 can be created.

  The setting file analysis unit 3 is a processing unit that analyzes the data source setting file 1 and the mashup template file 2 and extracts desired information. The information acquisition unit 4 is a processing unit that transmits an information acquisition request to the information acquisition destination 9 according to the request message format from the data source setting file 1 analyzed by the setting file analysis unit 3 and acquires information. The user transmission mashup file creation unit 5 is a processing unit that creates new information by processing the information acquired by the information acquisition unit 4 based on the processing specifications described in the mashup template file 2. The communication unit 6 is a processing unit that performs communication processing with the terminal 10. The setting file management unit 7 is a processing unit that manages the data source setting file 1 and the mashup template file 2 based on each management structure in the management structure file 8. The management structure file 8 stores various management structures such as a data source management structure for managing the data source setting file 1, a mashup template file management structure for managing the mashup template file 2, and a user information management structure for managing user information. It is a file to be. The information acquisition destination 9 is a device that holds various types of information corresponding to the service requested by the terminal 10. The terminal 10 is a terminal used by a user of the information acquisition device or a third party, and makes an information acquisition request to the information acquisition device and processes such as addition and deletion of the data source setting file 1 and the mashup template file 2 It is a terminal for performing.

Next, the information acquisition system shown in FIG. 2 will be described.
The information acquisition system illustrated in FIG. 2 includes a user terminal 100, an information acquisition device 200, servers 300a and 300b, and a network 400. The user terminal 100 corresponds to the terminal 10 in FIG. 1, and includes a mouse 101, a keyboard 102, a display unit 103, an input / output interface (I / F) 104, a CPU 105, a memory 106, an external storage device 107, a communication interface ( I / F) 108. The mouse 101 and the keyboard 102 are input devices in the user terminal 100, and the display unit 103 is a display device of the user terminal 100. The input / output interface 104 is an interface between the mouse 101 and the display unit 103. The CPU 105 is a processor that controls the user terminal 100, and the memory 106 is a storage unit that stores various data and includes a RAM that forms a work area of the CPU 105. The external storage device 107 is a storage device such as a hard disk device for storing user information and various information in the user terminal 100. The communication interface 108 is an interface for performing communication control for the user terminal 100 to connect to the network 400.

  The information acquisition device 200 is a device that constitutes the data source setting file 1 to the management structure file 8 in FIG. 1, and includes a CPU 201, a memory 202, an external storage device 203, a communication interface (I / F) 204, and an external device connection unit 205. It has. A CPU 201 is a processor that controls the information acquisition apparatus 200, and a memory 202 is a semiconductor memory such as a RAM. The external storage device 203 is a storage device such as a hard disk device, and stores the data source setting file 1 and the mashup template file 2 in FIG. The external storage device 203 stores programs corresponding to the setting file analysis unit 3, the information acquisition unit 4, and the setting file management unit 7 in FIG. 1, and these programs are read into the memory 202 and executed by the CPU 201. As a result, these functional units are realized. The communication interface 204 is an interface that performs communication control for connecting the information acquisition apparatus 200 to the network 400. The external device connection unit 205 is an interface for connecting an external device to the information acquisition apparatus 200 such as a USB connection or Bluetooth (registered trademark). The communication interface 204 and the external device connection unit 205 correspond to the communication unit 6 in FIG.

The servers 300a and 300b are devices corresponding to the information acquisition destination 9 in FIG. 1, and include CPUs 301a and 301b, memories 302a and 302b, external storage devices 303a and 303b, and communication interfaces (I / F) 304a and 304b. Yes. The CPUs 301a and 301b are processors that control the servers 300a and 300b, and the memories 302a and 302b are semiconductor memories such as a RAM. The external storage devices 303a and 303b are storage devices such as a hard disk device for storing various types of information. The communication interfaces 304 a and 304 b are communication control units that perform communication control for connecting the servers 300 a and 300 b to the network 400. In the information acquisition device 200 configured as described above, various types of information are stored in the external storage devices 303a and 303b, and when there is an information acquisition request from the information acquisition device 200, the CPUs 301a and 301b perform these external storage devices. Information is read from 303a and 303b and transmitted to the information acquisition apparatus 200 via the communication interfaces 304a and 304b.
The network 400 is a communication network for connecting the user terminal 100, the information acquisition device 200, and the servers 300a and 300b to each other.

Next, the operation of the information acquisition device will be described. FIG. 5 is a flowchart showing an operation from reception of a request from the user terminal 100 to creation of a user transmission mashup file.
The information acquisition apparatus 200 receives user information from the user terminal 100 via the network 400 (step ST101). The user information has information as shown in FIG. 6, for example. In the user information shown in FIG. 6, a variable name is described in the first column, a description of the variable is described in the second column, and an example of the value of the variable is described in the third column. User information is used when acquiring image data such as the myLatitude variable that indicates the latitude of the current user's position coordinates, the myLongitude variable that indicates the longitude, the Service variable that indicates the service that the user has requested to use, and the street view. Information such as a Rotation variable indicating a rotation method and a UserName variable indicating a user name.

In the user terminal 100, for example, the CPU 105 reads the user information stored in the external storage device 107 into the memory 106, and transmits the user information to the information acquisition device 200 using the communication interface 108.
The communication protocol between the user terminal 100 and the information acquisition device 200 uses, for example, SOAP / XML. With such a communication method, information (for example, an address, a search history, and the current time) that the user terminal 100 has can be transmitted.

  The information acquisition apparatus 200 receives user information transmitted from the user terminal 100 via the communication interface 204 (or external device connection unit 205). Accordingly, the setting file management unit 7 in FIG. 1 reads the user information management structure from the management structure file 8 and determines whether the user information has been used in the past. That is, the user information is compared with the past information, and the user information related to the user information is extracted from the user information registered in the user information management structure. If the user information is used in the past, the user information is already stored. If it is new and is new, the user information is registered in the user information management structure.

  FIG. 7 shows an example of a user information management structure. The first column describes the user name, the second column is the date and time of addition, the third column is the last use date and time, the fourth column is the last use service, and the fourth column is the position coordinate when last used. Is described. In FIG. 7, a user named guest is newly registered on 2013/01/01, the last service used is GourmetSearch (restaurant search service), the last use date is 2013/02/02, and the last use place is , Latitude 35.6785783 and longitude 139.7646844 are managed. These pieces of information are used for security and services used by users.

The setting file management unit 7 reads the data source management structure from the management structure file 8. FIG. 8 shows an example of the data source management structure. In the first column of FIG. 8, the data source setting file name is described, and in the second column, the ID of the service using the data source setting file described in the first column is described. The date and time of addition are described in the third column, and the file format of the data source setting file 1 is described in the fourth column.
The setting file management unit 7 extracts the service type acquired from the data source management structure and the user information, and reads the corresponding one from the data source setting file 1 (step ST102). The data source setting file 1 to be selected is determined by the Service variable of the user information shown in FIG. In step ST102, the setting file management unit 7 selects the mashup template file 2 based on the user information.

Next, the setting file analysis unit 3 analyzes the data source setting file 1 read by the setting file management unit 7, and extracts the request message format described in the data source setting file 1 (step ST103).
The information acquisition unit 4 supplements the parameter information of the request message format extracted by the setting file analysis unit 3 using user information and an acquisition information file (not shown) that has already been acquired, and creates a request message (step ST104). . The supplemental part of the parameter is defined in the data source setting file 1 in advance. The created request message is transmitted to the servers 300a and 300b as the information acquisition destination 9 (step ST105), and the information acquisition device 200 acquires information from each of the servers 300a and 300b (step ST106) and analyzes it (step ST107). ).
The setting file analysis unit 3 analyzes the mashup template file 2 read in step ST102, and determines the processing specifications in the user transmission mashup file creation unit 5 (step ST108). Note that. The process in step ST108 may be performed at an arbitrary timing such as being performed simultaneously with the analysis of the data source setting file 1 in step ST103.

  The information acquired by the information acquisition unit 4 is processed by the user transmission mashup file creation unit 5 (step ST109). The processing specifications are described in the mashup template file 2. In the processing specification, when the acquired information includes a predetermined tag, a process for extracting the information and a process for creating new information by combining the extracted information are described. The information acquisition device 200 stores the processed acquisition information file in the external storage device 203 and the memory 202.

  The user transmission mashup file creation unit 5 creates a user transmission mashup file according to the processed acquisition information file and the mashup template file 2 (step ST110). The created user transmission mashup file is transmitted to the terminal 10 by the communication unit 6.

  The data source setting file 1 and the mashup template file 2 can be changed regardless of the user / administrator. To change these files, a method of transferring and updating information using the communication interface 204 or the external device connection unit 205 of the information acquisition apparatus 200 is used.

  An example of processing when adding new information acquisition destination information will be described. First, the administrator or user of the information acquisition destination creates the data source setting file 1. For example, the data source setting file 1 as shown in FIG. 3 is created. The data source setting file creator transmits the data source setting file 1 to the information acquisition apparatus 200. In the example shown in FIG. 3, the service name is described in the first column, and the ID corresponding to the information acquisition means described in the third column is described in the second column. In the third and subsequent columns, information acquisition means corresponding to the Service variable described in FIG. 6 is described.

  The information acquisition device 200 receives the data source setting file 1 by the communication interface 204 (or the external device connection unit 205), and inputs the data source setting file 1 to the setting file management unit 7. The setting file management unit 7 reads the user information management structure and the data source management structure. From the data source management structure, it is determined whether the data source setting file 1 is the registered data source setting file 1 based on the data source setting file name and the creator name (not shown in FIG. 8). If so, the new registration of the data source design file 1 is stored in the user management structure and the data source management structure, and if it is an addition, the difference is taken and the additional part is written. FIG. 9 shows a flowchart for deleting / adding such a setting file.

  First, a setting file such as a data source setting file 1 to be added or a file in which a deletion instruction from the user is described is received (step ST201). Next, the setting file management unit 7 checks the presence / absence of the corresponding data source setting file 1 using the data source management structure, and if the data source setting file 1 already exists, selects the data source setting file 1. Processing is performed (step ST202). If there is a deletion request from the user and the corresponding data source setting file 1 does not exist, an error notification file describing the file name that did not exist is transmitted to the user.

When the data source setting file 1 is added, a difference from the existing data source setting file 1 is extracted. When deleting, the name and creator name of the data source setting file 1 are extracted (step ST203).
Next, the setting file management unit 7 adds / deletes the setting file based on the analysis result of step ST203 (step ST204). In the case of addition, when an existing data source setting file 1 exists, a difference is added to the data source setting file 1. If the existing data source setting file 1 does not exist, it is saved as it is. After the addition is completed, additional setting file information is added to the setting file management structure. In the case of deletion, the file is deleted from the data source management structure using the data source setting file 1 name and author name of the analysis result of step ST203, and the stored data source setting file 1 is also deleted.

  When the change processing of the target setting file is completed, it is determined whether the addition / deletion request from all users has been processed (step ST205). If the processing has been completed, the setting file is deleted / added. When the process is finished and the processes from all users have not been finished yet, the process returns to step ST202 to select the next setting file.

Next, an example of adding the mashup template file 2 will be described. The mashup template file 2 created by the user or a third party (administrator of the mashup template file 2) is transmitted to the information acquisition device 200. The information acquisition apparatus 200 inputs the mashup template file 2 to the setting file management unit 7 via the communication unit 6.
The setting file management unit 7 reads the user information management structure and the mashup template file management structure from the management structure file 8. FIG. 10 shows a mashup template file management structure. The mashup template file name is described in the first column. The manager name is described in the second column. The file name in the first column and the administrator name in the second column are search keys. The date and time of addition are described in the third column. In the fourth column, the file format of the mashup template file in the first column is described.

  The setting file management unit 7 determines whether or not the mashup template file 2 to be added exists in the mashup template file management structure based on the mashup template file name and the administrator name. Add the template file name and administrator name to the mashup template file management structure. Also, the received mashup template file 2 is stored. If a mashup template file to be added already exists in the mashup template file management structure, the difference from that file is taken and the difference is added to the already stored mashup template file 2.

  Next, an example of processing for deleting the mashup template file 2 will be described. The administrator of the mashup template file 2 transmits a file describing the name of the mashup template to be deleted to the information acquisition device 200. The information acquisition device 200 receives the information via the communication unit 6, and receives the setting file. Input to the management unit 7. Based on the information, the setting file management unit 7 deletes the information related to the mashup template file 2 specified from the mashup template file management structure, and also deletes the stored mashup template file 2. If the mashup template file 2 to be deleted does not exist, an error notification file in which the mashup template file 2 is described is transmitted to the user.

FIG. 11 shows an example of a request file for adding user information, deleting a mashup template file, and deleting a data source setting file. In the illustrated example, an instruction to delete the data source setting file and the mashup template file is issued. Various tags in the illustrated example will be described. The Request tag indicates the processing request sent from the user, NumberOfRequests indicates the number of processing requests, and the Remove tag indicates the deletion request. In the illustrated example, the mashup template file deletion request and the data source setting file It shows that two processing requests of the deletion request have been transmitted from the user. In addition, NumberOfFiles describes the number of files to be deleted. In the illustrated example, two files are designated. The part enclosed by the MashupTemplateFile tag is the setting file belonging to the mashup template file, DataSourceFile is the data source setting file, the part enclosed by the File tag describes the details of the setting file, the FileName tag is the setting file name, UserName indicates the user name. In the illustrated example, it is shown that deletion processing is performed on the mashup template file Template and the data source setting file DataSourceFile created by the user Guest.
The FileName tag and the UserName tag are used as search keys used when searching for a specified setting file from each management structure.

  As described above, in the information acquisition apparatus according to the first embodiment, the server 300a, 300b from which the information described in the mashup template file 2 is acquired on the user side by the mashup template file 2. It is possible to acquire information without being conscious of.

In addition, the user or the administrator of the servers 300a and 300b can add or delete information of the information acquisition destination 9 without making a large-scale change to the program by adding or deleting the data source setting file 1. Can do.
Furthermore, the developer of the information acquisition system can reduce development costs by not having to create functions corresponding to the servers 300a and 300b by the data source setting file 1 one by one.

  As described above, according to the information acquisition apparatus of the first embodiment, information is acquired from an information acquisition destination according to a service requested from a user terminal, and a processing process corresponding to the service is performed on the acquired information. An information acquisition device that performs a response to a user terminal and acquires information from an information acquisition destination using a data source setting file that sets a relationship between the information acquisition destination and a service, and information in the data source setting file Mashup template file that sets the processing specifications corresponding to the service of the information acquired by the information acquisition unit and the information acquisition unit, and the information acquired from the information acquisition destination using the information of the mashup template file, and responds to the user terminal Data source setting because it has a mashup file creation section to create a mashup file for Only to add, change, delete Airu, without performing a large-scale changes to the program, it is possible to add, modify or delete information acquisition source of information. Further, the user can use the data without determining changes such as the stop of distribution of information at the information acquisition destination and the distribution of new information. Further, the user can customize the information to be acquired by changing the mashup template file.

  In addition, according to the information acquisition apparatus of the first embodiment, the data source management structure for managing the data source setting file, and the setting file management unit for managing the data source setting file using the data source management structure are provided. When the configuration file management unit receives a request to add a data source configuration file, the configuration file management unit refers to the data source management structure to determine whether the data source configuration file that has received the addition request exists. Data source configuration file is registered in the data source management structure, and when a data source configuration file deletion request is received, the data source configuration file that received the deletion request is deleted from the data source management structure. Processing such as adding, changing, and deleting files can be reliably managed.

  Further, according to the information acquisition apparatus of the first embodiment, the mashup template file management structure for managing the mashup template file and the setting file management unit for managing the mashup template file using the mashup template file management structure When the configuration file management unit receives a request to add a mashup template file, the configuration file management unit refers to the mashup template file management structure to determine whether there is a mashup template file that has received the addition request, If it does not exist, register it in the mashup template file management structure as a new mashup template file. If you receive a mashup template file deletion request, the mashup template file that received the deletion request Since the plate files to be deleted from the mash-up template file management structure, it is possible to reliably manage the processing, such as add, change or delete a mash-up template file.

  Further, according to the information acquisition apparatus of the first embodiment, the setting file management unit manages the data source setting file for each administrator set corresponding to the data source setting file. Even a data source setting file created by the three parties can be used by managing the third party as an administrator.

  Further, according to the information acquisition apparatus of the first embodiment, the setting file management unit manages the mashup template file for each administrator set corresponding to the mashup template file. Even a mashup template file created by the three parties can be used by managing the third party as an administrator.

  Further, according to the information acquisition device of the first embodiment, the data source setting file and the mashup template file are made into a single setting file having the functions of the respective files. Management of mashup template files can be simplified.

  In the present invention, any constituent element of the embodiment can be modified or any constituent element of the embodiment can be omitted within the scope of the invention.

  1 data source setting file, 2 mashup template file, 3 setting file analysis unit, 4 information acquisition unit, 5 user transmission mashup file creation unit, 6 communication unit, 7 setting file management unit, 8 management structure file, 9 information Acquisition source: 10 terminals, 100 user terminals, 101 mouse, 102 keyboard, 103 display unit, 104 input / output interface (I / F), 105, 201, 301a, 301b CPU, 106, 202, 302a, 302b memory, 107, 203, 303a, 303b External storage device, 108, 204, 304a, 304b Communication interface (I / F), 200 Information acquisition device, 300a, 300b Server, 400 network.

Claims (6)

An information acquisition device that acquires information from an information acquisition destination according to a service requested from a user terminal, performs processing according to the service on the acquired information, and responds to the user terminal,
A data source setting file for setting a relationship between the information acquisition destination and the service;
An information acquisition unit that acquires information from the information acquisition destination using information of the data source setting file;
A mashup template file for setting processing specifications corresponding to the service of the information acquired by the information acquisition unit;
An information acquisition apparatus comprising: a mashup file creation unit that processes information obtained from the information acquisition destination using information of the mashup template file and creates a mashup file for responding to the user terminal. A data source management structure for managing the data source configuration file;
A configuration file management unit that manages the data source configuration file using the data source management structure;
When the configuration file management unit receives a request to add the data source configuration file, the configuration file management unit refers to the data source management structure to determine whether the data source configuration file that has received the addition request exists, and does not exist. In this case, the data source setting file is registered in the data source management structure as a new data source setting file, and when the deletion request for the data source setting file is received, the data source setting file that has received the deletion request is deleted from the data source management structure. The information acquisition apparatus according to claim 1. A mashup template file management structure for managing the mashup template file;
A configuration file management unit that manages the mashup template file using the mashup template file management structure;
When the setting file management unit receives a request to add the mashup template file, the setting file management unit determines whether there is a mashup template file that has received the addition request with reference to the mashup template file management structure. If it does not exist, it is registered in the mashup template file management structure as a new mashup template file. If a deletion request for the mashup template file is received, the mashup template file that has received the deletion request is registered in the mashup template file. 3. The information acquisition apparatus according to claim 1, wherein the information acquisition apparatus is deleted from the file management structure.   The information acquisition apparatus according to claim 2, wherein the setting file management unit manages the data source setting file for each administrator set corresponding to the data source setting file.   4. The information acquisition apparatus according to claim 3, wherein the setting file management unit manages the mashup template file for each administrator set corresponding to the mashup template file.   The information acquisition apparatus according to claim 1, wherein the data source setting file and the mashup template file are a single setting file having a function of each file.

Images