JP6440571B2 - SaaS data linkage support system and SaaS data linkage support method - Google Patents

Description

  The present invention relates to an inter-SaaS data collaboration support system and an inter-SaaS data collaboration support method, and more specifically to a technique for efficiently cooperating between SaaS without a development burden on the user side.

With the spread of cloud computing, the use of systems provided in the form of SaaS (Software as a Service) is expanding. Such SaaS users are freed from operations such as installation and management related to IT resources for the system.

  On the other hand, regardless of whether or not the SaaS format is used, a system for intersystem cooperation that absorbs the difference in data model and data format is required for a plurality of systems having a data usage relationship with each other. As in the past, when the system is in the form of so-called on-premise, which is constructed and operated at a user facility or the like, a system for intersystem cooperation has been constructed on the user side.

  On the other hand, when the system is provided as SaaS, it is necessary to prepare a mechanism for cooperation between SaaS in order to achieve cooperation between systems. As a conventional technique corresponding to such a mechanism, a technique for realizing cooperation between SaaS by connecting an API provided by SaaS (see Patent Document 1) has been proposed.

  By the way, SaaS described above is an object that feels the merit of being quick and easy to install and use from the user's point of view. From the viewpoint of the SaaS provider, this leads to the need to quickly provide, modify and abolish various SaaS according to the needs of users and to carry out a very efficient business development. Therefore, in recent years, a base provider (see Non-Patent Document 1) that provides a SaaS provider with a base for the SaaS business has appeared (hereinafter, SaaS base provider). This SaaS platform provider provides various infrastructure functions necessary for the SaaS project, such as IT resources for application execution, charging for collecting usage charges from users, user management, and user authentication. The SaaS platform provider also provides a marketplace on the network that introduces the SaaS provider, which is a user of the SaaS platform, to the user. In this case, the user searches for SaaS in the marketplace, specifies a desired SaaS according to his / her business, and concludes a usage contract with the provider.

US2013 / 0275265

"Putting the Cloud Within Reach - How Service Provider Can Succeed with Business Application Marketplaces" (http://info.appdirect.com/resources/how-service-providers-can-succeed-with-business-application-marketplaces, 2015 / 03/26)

  In some cases, SaaS that has been widely spread or is well-known is linked via an API. However, which SaaS is to be linked is a matter to be determined by the SaaS infrastructure provider or SaaS provider, and does not necessarily reflect the wishes and intentions of each user. Therefore, in many cases, in order to establish the cooperation between the SaaS desired by the user, it is necessary to develop a system for absorbing the difference in the data format and the like between the corresponding SaaS. Such system development is generally complicated and costly, which places a heavy burden on the user.

  In addition, when the user searches for a desired SaaS in the SaaS marketplace described above, information that is useful for the cooperation between SaaS, that is, the consistency of the data format, is not presented. Accordingly, the SaaS selection can be advanced without considering the cost and labor when the cooperation between SaaS is attempted. In that case, the cost and labor of the above-described system development increase more and the burden on the user may become excessive.

  Therefore, an object of the present invention is to provide a technique for efficiently cooperating between SaaS without a development burden on the user side.

  The SaaS data cooperation support system of the present invention that solves the above problems includes a set of a storage device that holds an interface DB that stores information related to a data input / output interface in each SaaS, and a SaaS that has a common data format in the interface. A specific algorithm corresponding to the data linkage processing between SaaS when specified based on the interface DB and outputting information on the set to a predetermined device and receiving a request for linkage setting from the user for the set from the predetermined device And an arithmetic unit that executes processing for assigning predetermined information defining the set as a SaaS group to be linked to the API and acquiring the group as a linkage API and storing the result in the storage device.

  In addition, the SaaS data linkage support method according to the present invention provides a computer system including a storage device that holds an interface DB that stores information related to a data input / output interface in each SaaS. When a set is specified based on the interface DB, information on the set is output to a predetermined device, and a request for cooperation setting from the user is received for the set from the predetermined device, data linkage processing between SaaS is supported. It is characterized in that predetermined information defining the set as a SaaS group to be linked is assigned to an API that acquires an execution result of a predetermined algorithm, and a process of storing in a storage device as a linked API is executed.

  According to the present invention, cooperation between SaaS can be efficiently achieved without a development burden on the user side.

It is a figure which shows the network structural example containing the data cooperation assistance system between SaaS of 1st Embodiment. It is a figure which shows the hardware structural example of the information processing apparatus in 1st Embodiment. It is a figure which shows the example of a data structure of contract DB in 1st Embodiment. It is a figure which shows the example of a data structure of SaaS information DB in 1st Embodiment. It is a figure which shows the example of a data structure of SaaS interface DB in 1st Embodiment. It is a figure which shows the example of a data structure of cooperation DB in 1st Embodiment. It is a flowchart which shows the process procedure example 1 of the data cooperation support method between SaaS in 1st Embodiment. It is a figure which shows the example 1 of a screen in 1st Embodiment. It is a flowchart which shows the process procedure example 2 of the data cooperation assistance method between SaaS in 1st Embodiment. It is a flowchart which shows process sequence example 3 of the data cooperation assistance method between SaaS in 1st Embodiment. It is a flowchart which shows process sequence example 4 of the data cooperation assistance method between SaaS in 1st Embodiment. It is a flowchart which shows process sequence example 5 of the data cooperation assistance method between SaaS in 2nd Embodiment. It is a figure which shows the example of a network structure containing the data cooperation assistance system between SaaS in 3rd Embodiment. It is a figure which shows the example of a data structure of gateway DB in 3rd Embodiment. It is a figure which shows the example of a data structure of cooperation DB in 4th Embodiment.

--- First Embodiment ---
A first embodiment of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a network configuration diagram including an inter-SaaS data cooperation support system 1 according to the first embodiment. The inter-SaaS data cooperation support system 1 shown in FIG. 1 is a computer system that efficiently promotes cooperation between SaaS without a development burden on the user side.

  The inter-SaaS data collaboration support system 1 exemplified in the first embodiment is configured from the collaboration gateway 100, the SaaS collaboration marketplace server 130, and the server collaboration management server 150 in the network configuration in FIG. However, the minimum configuration is the cooperation gateway 100 and the server cooperation management server 150. In addition, although the system is configured by such a server group, the function of each server may be implemented in an integrated server device, and the form is not limited.

  Among such SaaS inter-data collaboration support system 1, the collaboration gateway 100, SaaS marketplace server 130, server collaboration management server in which the objects to be operated and managed by the SaaS infrastructure provider, that is, the infrastructure environment, are connected to each other via the network 30. 150 and SaaS server 170. On the other hand, the terminal used by the SaaS user is the user terminal 200. Both environments are connected by a network 20 such as the Internet.

  The SaaS marketplace server 130 existing in the infrastructure side environment stores a contract DB 131 that holds information related to a contract with a user and a SaaS information DB 133 that holds various information related to each SaaS in its storage device. In addition, the SaaS marketplace server 130 receives a request for SaaS search by the user terminal 200 via the network 20, the cooperative gateway 100, and the network 30, and specifies and returns information related to the user's desired SaaS from the SaaS information DB 133. The portal function unit 132 is held. Note that the above-described contract DB 131 includes authentication information necessary for using the contracted SaaS for each user, that is, a contractor, and billing information associated with the use of the corresponding server.

In addition, the SaaS cooperation management server 150 uses the SaaS interface DB 151 that holds information regarding the interface of each SaaS provided to the user terminal 200 using the infrastructure side environment, and the information regarding the combination of the SaaS that performs data cooperation and the information regarding the interface. The cooperation DB 152 to be held is stored in the storage device. Further, the SaaS cooperation management server 150 includes an interface registration unit 153 that registers interface information of each SaaS in the SaaS interface DB 151, a cooperative SaaS discovery unit 154 that discovers a combination of SaaS that can be cooperated, and a SaaS specified by the user. The cooperation registration part 155 which registers the information regarding cooperation into cooperation DB152 is hold | maintained.

  The SaaS server 170 is a server device that actually executes an application provided in the SaaS form to the user terminal 200 via the network 30, the cooperative gateway 100, and the network 20. In the SaaS server 170 illustrated in FIG. 1, SaaS1 (171), SaaS2 (172), and SaaS3 (173) are shown as examples. In FIG. 1, the SaaS server 170 is illustrated as one server device, but may be configured by a plurality of server devices.

  In addition, the cooperation gateway 100 provides a cooperation API for starting an algorithm (data cooperation unit 112) for executing the cooperation processing between SaaS, and performs data cooperation processing between the corresponding SaaS and acquisition processing of the result through the cooperation API. Server device. In response to an instruction from the cooperation registration unit 155 of the SaaS cooperation management server 150, the API creation unit 111 held by the cooperation gateway 100 creates a cooperation API for calling the data cooperation unit 112, and creates the cooperation API 152 (SaaS cooperation). Storage processing is performed in the management server 150). On the other hand, the data linkage unit 112 is called via the created linkage API, acquires information held in the linkage DB 152 of the SaaS linkage management server 150, and executes data acquisition and transmission processing between SaaS for data linkage. To do. Note that the above-described cooperation API is assumed to be a Web API. This Web API is an API that uses HTTP to execute predetermined processing over a network and receives the result. The cooperation API, which is a Web API in the embodiment, is a URL where the data cooperation unit 112 is located, specifically, a URL indicating an address in which the activation program of the data cooperation unit 112 in the cooperation gateway 100 is stored (for example, “http: //www.abcdefg.com/api/l/C1.json ”), which is accompanied by identification information (“ C1 ”in the above example) that uniquely identifies the SaaS group to be linked with data. This identification information uniquely indicates a SaaS group that is a target of data cooperation, and becomes a request code in the cooperation API.

  On the other hand, a user terminal 200 used by a user who is a SaaS user is a general PC, and includes a browser 210 for accessing SaaS to be used, and a business program 211 that calls and executes a cooperation API of the cooperation gateway 100. Yes.

--- Hardware configuration--
Next, an example of a hardware configuration of each device configuring the above-described SaaS data cooperation support system 1 will be described. This apparatus is the above-described user terminal 200, cooperative gateway 100, SaaS marketplace server 130, SaaS cooperative management server 150, and SaaS server 170. FIG. 2 is a diagram illustrating a hardware configuration example of the information processing apparatus according to the first embodiment. The information processing apparatus according to the present embodiment includes a storage device 11 including an appropriate nonvolatile storage element such as an SSD (Solid State Drive) or a hard disk drive, a memory 13 including a volatile storage element such as a RAM, and the storage device 11. An execution device 14 such as a CPU for performing various determinations, operations and control processes, an input / output device 15 for data input / output, A communication device 16 connected to the network and responsible for communication processing with other devices. In addition, when the arithmetic device 14 executes the program 12 provided in the storage device 11, a functional unit necessary for each corresponding device is mounted.

--- Data structure example ---
Next, an example of a data structure in a table used by the inter-SaaS data cooperation support system 1 of the present embodiment will be described. FIG. 3 is a diagram showing an example of the data structure of the contract DB 131 in the first embodiment. The contract DB 131 illustrated in FIG. 3 is a database that holds SaaS contract information for each user. The contractor ID 211 for identifying the organization (eg, company) to which the user belongs is used as a key. The contract SaaS name 212 that uniquely indicates the contracted SaaS, the authentication information 213 (eg, set of ID and password) required for the authentication process when the contractor uses the contracted SaaS, and the contracted SaaS This is a set of records associated with values such as a billing amount 214 relating to the corresponding contractor according to the usage status of each. In the contract DB 131 of FIG. 3, the SaaS under contract by the organization with the contractor ID “Company 1” is “SaaS1” and “SaaS2”, and the monthly charges related to “SaaS1” are “¥ 185,380”, “SaaS2”. The monthly billing amount for “SaaS1” for the organization with the contractor ID “Campanii 2” is “SaaS1”, and the monthly billing amount for “SaaS1” is “¥ 70,200”. 570 ".

  FIG. 4 is a diagram showing an example of the data structure of the SaaS information DB 133 in the first embodiment. The SaaS interface DB 151 illustrated in FIG. 4 is a database that holds various types of information related to SaaS that can be provided by the SaaS platform provider, provided to the user terminal 200 by the portal function unit 132 of the SaaS marketplace server 130. This SaaS information DB 133 uses a SaaS name 215 as a key and records associated with values such as a corresponding service 216 that uniquely indicates a service provided by the SaaS and a unit charge 217 that is charged according to the use of the corresponding SaaS. It is an aggregate of.

  FIG. 5 is a diagram showing an example of the data structure of the SaaS interface DB 151 in the first embodiment. The SaaS interface DB 151 is a database that holds interface information related to data linkage of SaaS executed on a SaaS platform operator base. Here, the interface related to data linkage is URL corresponding to two types of acquisition (export) of data held in SaaS and registration (import) of data from outside (that is, for data input / output in the corresponding SaaS) Address = interface).

  The SaaS interface DB 151 illustrated in FIG. 5 is a set of records in which values such as the interface type 312, the interface URL 313, and the data format 314 are associated with each other using the SaaS name 311 as a key.

  Of these, the interface type 312 is a value indicating the distinction between export and import. The data format 314 is a format of a file output by the interface when the interface type is “export”, and an input file format acceptable by the interface when the interface type is “import”. Specifically, the data format 314 corresponds to the name of a famous application. Note that the interface URL 313 illustrated in FIG. 5 is simplified as “URL11” or the like for simplification of description, but in actuality “http://www.abcdefg.com/s-serv/saas1/exp”. It is such a value.

  FIG. 6 is a diagram illustrating a data structure example of the cooperation DB 152 in the first embodiment. The cooperation DB 152 illustrated in FIG. 6 is a database that stores combinations of SaaS interfaces designated to cooperate with the user and information on the cooperation API that starts the data cooperation processing.

The cooperation DB 152 illustrated in FIG. 6 includes a company name 321 that uniquely indicates an organization that is a user who has instructed the setting of data cooperation between SaaS, a cooperation API 322 that indicates identification information of a cooperation API that activates a function of data cooperation processing, and the like. Export SaaS 323 that uniquely indicates SaaS to be acquired from SaaS to be acquired, Export API 324 that indicates URL that is API for acquiring data from this Export SaaS, and Import that uniquely indicates SaaS that is the transmission destination of data acquired from Export SaaS This is an aggregate of records in which the values of SaaS 325 and import API 325 indicating the URL that is an API for importing data into this import SaaS are associated with each other.

  Among these values, the value of the linkage API 322 includes “C1” as information defining the export SaaS “SaaS S1” and the import SaaS “SaaS S2” as the SaaS group to be linked. In other words, “C1” is a request code corresponding to the data linkage processing related to the SaaS group including “SaaS1” and “SaaS2”.

--- Flow example 1 ---
Hereinafter, the actual procedure of the SaaS data linkage support method in the present embodiment will be described with reference to the drawings. Various operations corresponding to the inter-SaaS data collaboration support method described below are realized by programs that are read and executed by the respective information processing devices of the inter-SaaS data collaboration support system 1 in a memory or the like. And this program is comprised from the code | cord | chord for performing the various operation | movement demonstrated below.

  FIG. 7 is a flowchart showing a processing procedure example 1 of the inter-SaaS data cooperation support method in the present embodiment. Here, first, the process of registering the interface of each SaaS managed by the SaaS platform operator in the SaaS interface DB 151 will be described. Such a process is a process executed by the interface registration unit 153 of the SaaS cooperation management server 150.

  Here, for example, it is assumed that a SaaS provider accesses the SaaS marketplace server 130 via a predetermined information processing apparatus and requests information registration regarding SaaS. In this case, the portal function unit 132 of the SaaS marketplace server 130 returns the interface registration screen 410 (FIG. 8) to the information processing apparatus described above, and accepts information input regarding a predetermined SaaS via this screen. Become.

  The SaaS provider browses this screen 410 using the information processing apparatus, and inputs each value such as the URL of each SaaS export / import interface and the data format supported by the interface on the screen 410. Then, the registration button 411 is pressed. Receiving this, the information processing apparatus returns the input value on the screen 410 to the SaaS marketplace server 130.

  On the other hand, the portal function unit 132 of the SaaS marketplace server 130 activates the interface registration unit 153 of the SaaS cooperation management server 150 when the registration button 411 is pressed. The interface registration unit 153 acquires each value (SaaS name, interface type, URL, data format) input by the above-described SaaS provider on the screen 410 (step 401), and registers it in the SaaS interface DB 151. (Step 402). It is assumed that a plurality of interfaces can be registered for one SaaS.

As described above, the SaaS interface DB 151 in FIG. 3 is related to “SaaS1”, the export API having the interface URL “URL11” and the data format “format1”, the interface URL “URL12”, and the data format “format”. 1 ”indicates that the import API is registered. Similarly, with respect to “SaaS2”, an export API having an interface URL “URL21” and a data format “format 1”, and an interface U
It also shows that an import API with RL “URL22” and data format “format 1” has been registered. These two SaaS, that is, “SaaS1” and “SaaS2” indicate that both data formats are common to “format 1” and data can be linked via the export API and the import API.

--- Flow example 2 ---
Next, processing for finding a combination of SaaS that can be linked to data among SaaS provided by a SaaS platform operator will be described with reference to the drawings. FIG. 9 is a flowchart showing a processing procedure example 2 of the inter-SaaS data cooperation support method according to this embodiment. The processing of this flow is assumed to be executed by the cooperative SaaS discovery unit 154 in the SaaS cooperative management server 150. In addition, for example, when the SaaS user operates the user terminal 200 and logs in to the portal function unit 132 of the SaaS marketplace server 130, the cooperation SaaS discovery unit 154 causes the portal function unit 132 to the user terminal 200. It is called to display a combination of SaaS that can be linked to data on the screen to be provided.

  In this flow, the linked SaaS discovery unit 154 first clears a linked candidate list that holds information regarding combinations of SaaS that can be linked to data (step 501). This process is a process for avoiding confusion with the cooperation candidate list obtained for the flow performed previously. In addition, the cooperation candidate list is held in a predetermined storage device or memory in the SaaS cooperation management server 150, for example.

  Next, the cooperative SaaS discovery unit 154 acquires the company ID of the user who is calling the flow through the portal function unit 132 from the session information at the time of login held by the portal function unit 132, and this company ID. A list of SaaS contracted in step S1 is acquired from the contract DB 131 (step 502).

  Subsequently, the cooperative SaaS discovery unit 154 executes the following steps 503 to 508 for each SaaS acquired in step 502 described above. That is, the cooperative SaaS discovery unit 154 determines whether or not the export API is registered for the SaaS selected in accordance with a predetermined standard such as the ascending order of ID from the list obtained in step 502 (here, SaaSS_X), and the corresponding SaaS of the SaaS interface DB 151. A check is made on the record relating to (Step 504). Specifically, the check can be executed by determining whether there is a record whose interface type 312 is “export” among the records of the corresponding SaaS.

  As a result of the determination, if the export API is not registered (step 503: NO), the cooperative SaaS discovery unit 154 selects another SaaS in the above list based on the above-described predetermined criteria, and relates to the selected SaaS A similar step 503 is executed.

  On the other hand, if the export API has been registered as a result of the above determination (step 503: YES), the cooperative SaaS discovery unit 154 determines the other SaaS in the list obtained in the above step 502 (in this case, other than SaaS_X) For SaaS), the following steps are performed:

In other words, the linked SaaS discovery unit 154 searches the other SaaS described above (for example, SaaS_Y) whether the data format of the import API is the same as the data format of the export API in SaaS_X (step 505). That is, in step 505, it is checked whether SaaS_X and SaaS_Y are compatible with data export and import in the same format.

  As a result of the above determination, if there is no other SaaS (for example, SaaS_Y) whose import API data format is the same as the export API data format in SaaS_X (step 505: NO) The SaaS discovery unit 154 returns the process to step 505, and re-executes the same process for another SaaS import API.

  On the other hand, as a result of the above-described determination, among the above-described other SaaS (for example, SaaS_Y), if the data format of the import API is the same as the data format of the export API in SaaS_X (step 505: YES), cooperation The SaaS discovery unit 154 determines whether the combination of the above SaaS_X and SaaS_Y and the combination of the export API and the import API discovered in step 505 are already registered in the cooperation DB 152 (step 506).

  As a result of this determination, if the corresponding combination has already been registered in the cooperation DB 152 (step 506: NO), the cooperation SaaS discovery unit 154 returns the process to step 505 and re-executes the same process for another SaaS. To do.

  On the other hand, as a result of the above-described determination, if the corresponding combination has not already been registered in the cooperation DB 152 (step 506: YES), the cooperation SaaS discovery unit 154 indicates that the above-mentioned user's belonging organization is not used. Recognize that a combination of data linkages has been found, add each found combination of SaaS and API to the linkage candidate list, and return to the above-described step 503 to execute the same processing for another SaaS in the list (Step 507).

  Through the above processing, the cooperation candidate list holds combinations of data linkages between SaaS that are not used at that time among SaaS used by the organization to which the user belongs. For example, when the SaaS collaborative discovery unit 154 is executed under the authority of the user with the company name “company 1” when the SaaS interface DB 151 is in the state of FIG. 3, the export of “SaaSS1” and the import of “SaaSS2”, “ It is output to the cooperation candidate list that the export of “SaaS2” and the import of “SaaS1” can be linked. Further, when the linkage DB 152 is in the state of FIG. 3, the export of “SaaS” and the import of “SaaS” have already been linked, and therefore, the export of “SaaS” and the import of “SaaS” are output to the linkage candidate list. The The calling side of the linked SaaS discovery unit 154 can prompt the user to use data linkage between SaaS by providing this information to the user terminal 200 of the user by the portal function unit 132 or the like.

--- Flow example 3 ---
Next, a process of generating a cooperation API for a combination of SaaS discovered in the above-described flow example 2, that is, a combination designated by the user on the user terminal 200 from the cooperation candidate list will be described. FIG. 10 is a flowchart showing a processing procedure example 3 of the inter-SaaS data cooperation support method according to this embodiment. Each process of this flow shall be performed by the cooperation registration part 155 in the SaaS cooperation management server 150. The cooperation registration unit 155 is called from the portal function unit 132 of the SaaS marketplace server 130.

At the start of this flow, the cooperation registration unit 155, based on the above-described cooperation candidate list, designates the SaaS group that is a data cooperation target in the user terminal 200, and the SaaS name that outputs data and the URL that is the API thereof, It is assumed that each information of the SaaS name that receives the output data and the URL that is the reception API is received as input.

  Here, the cooperation registration unit 155 first generates a URL as an API for executing data cooperation between two SaaS received from the user terminal 200 (step 601). This URL generation is, for example, a process of giving predetermined information defining a SaaS group designated as a cooperation target from the user terminal 200 to a URL where the activation program of the data cooperation unit 112 that executes the data cooperation process is located. Become.

  Next, the cooperation registration unit 155 registers each information of the SaaS group designated from the user terminal 200 and the URL (ID of the cooperation URL) generated in Step 601 in the cooperation DB 152 as described above (Step 602). ).

  Finally, the cooperation registration unit 155 acquires the ID of the generated cooperation URL and the name of the organization (company name) to which the user who has called the cooperation registration unit 155 belongs from the authentication information, and creates the API of the cooperation gateway 100. This is notified to the unit 111 to instruct the creation of a linked URL (step 603). It is assumed that the above authentication information can be acquired from the SaaS marketplace server 130 or the like. The API creation unit 111 that receives the request receives the above-described creation instruction of the cooperation URL from the cooperation registration unit 155, and from the process that is authenticated as the user of the designated company name for the designated cooperation URL. When there is an access, the Web API in the cooperative gateway 100 is configured with a predetermined algorithm so that the cooperation registration unit 155 is executed. In this case, as already described, a URL (for example, “http://www.abcdefg.com/api/l/***) indicating the address where the activation program of the data linkage unit 112 in the linkage gateway 100 is stored. ") Is accompanied by identification information (" C1 "in the above example) that uniquely identifies the SaaS group to be linked. This cooperative API (for example, “http://www.abcdefg.com/api/l/C1”) has an ID “URL_C1”.

  The cooperation DB 152 of FIG. 3 uses the cooperation process in which the organization of the company name “campani 1” exports the data “SaaS1” and imports it into “SaaS2”, and the ID of the cooperation process, that is, the ID of the cooperation API is “URL_C1” is indicated.

--- Flow example 4 ---
Next, the data cooperation process between SaaS by the cooperation gateway 100 is demonstrated based on figures. FIG. 11 is a flowchart showing a processing procedure example 4 of the inter-SaaS data cooperation support method according to the present embodiment. The processing in this flow is executed by the data linkage unit 112 in the linkage gateway 100.

  In this case, the data linkage unit 112 of the linkage gateway 100 is activated when the linkage API is called. Note that the cooperation API is called from the browser 210 or the business program 211 of the user terminal 200.

  In this flow, the data linkage unit 112 is called when there is an access to the URL of the above-described linkage API, and acquires the URL as a parameter. It is assumed that a parameter for the export API may be given to the URL (for example, HTTP GET format).

  First, the data linkage unit 112 obtains from the authentication information the user name of the user who has accessed the above URL, and further obtains the URL that is the linkage API that caused the above call (step 701).

  Next, the data linkage unit 112 refers to the linkage DB 152 to obtain linkage information corresponding to the URL obtained above, specifically, the values of the export SaaS 323, the export API 324, the import SaaS 325, and the import API 326 (step 702). ).

  Next, the data linkage unit 112 performs an authentication process using the authentication information obtained in step 701 on the export SaaS obtained in step 702 described above, and further calls the export API, Data is acquired from the export SaaS (step 703). When a parameter is given to the data linkage unit 112, this parameter is given to the export API. In addition, the data linkage unit 112 performs authentication processing on the import SaaS as described above, calls the import API, and transmits the data acquired in step 703 (step 704).

  According to the above embodiment, a combination of SaaS having the same input / output data format is found, a cooperation API for starting a process for transferring data between them is defined, and the user calls the cooperation API to perform SaaS. Data can be exchanged between them. The user does not need to prepare a system for data linkage, and the SaaS provider can also automate linkage with SaaS that can be linked only by registering the API.

--- Second Embodiment ---
Next, a second embodiment of the present invention will be described. In the first embodiment, SaaS that can be linked to data is found out from SaaS contracted by a certain organization and presented to the user. On the other hand, in the second embodiment, for a user who is searching for contracted SaaS, SaaS that can be linked to data is extracted from the SaaS information that the user is currently subscribed to, and the search result of SaaS can be linked to data. And a method of modification using the extracted SaaS information.

  FIG. 12 is a flowchart illustrating a processing procedure example 5 of the inter-SaaS data cooperation support method according to the second embodiment. This flow shows processing for determining whether or not SaaS designated by a certain user can be linked with data of SaaS under contract of the corresponding user. Each process in this flow is executed by, for example, the authority of a specific authenticated user by the cooperation SaaS discovery unit 154 of the SaaS cooperation management server 150. In addition, the trigger of such a flow is, for example, an operation in which a user accesses the SaaS marketplace server 130 using the user terminal 200 and searches for SaaS under a desired condition using a function or screen provided by the portal function unit 132. Can be assumed.

  First, the linked SaaS discovery unit 154 clears a recommended SaaS list, which is a list of SaaS that can be recommended as a data linkage target, specified as a result of this flow in a predetermined storage device that stores the list (step 801). ).

  Next, the linked SaaS discovery unit 154 searches the SaaS interface DB 151 using the SaaS name of a specific SaaS specified in the SaaS search conditions as described above as a key, and an export or import interface is set for the corresponding SaaS. It is determined whether it is defined (step 802).

  As a result of the determination, if the export or import interface is not defined (step 802: NO), the cooperative SaaS discovery unit 154 specifies that there is no SaaS that can be cooperated, and ends the flow.

On the other hand, when the export or import interface is defined as a result of the above determination (step 802: YES), the cooperative SaaS discovery unit 154 displays the company of the organization to which the user executing the above SaaS search processing belongs. The name is appropriately acquired from authentication information, session information, or the like, or from the contract DB 131, and a list of SaaS contracted by the company name is acquired from the contract DB 131 (step 803). For each of the SaaS acquired here (hereinafter, SaaS_Z), the cooperative SaaS discovery unit 154 executes Steps 804 to 806.

  In other words, in step 804, the cooperative SaaS discovery unit 154 determines whether the data format of the import API of the SaaS_Z is the same as the data format of the SaaS export API specified in the above-described user's SaaS search or the like. The determination is made with reference to the SaaS interface DB 151.

  As a result of the above determination, when the same data format exists as SaaS_Z (step 804: YES), the cooperative SaaS discovery unit 154 adds the SaaS_Z to the recommended SaaS list (step 806), and step 804. The process is returned to and the process for another SaaS is executed.

  On the other hand, when the same data format does not exist as SaaS_Z (step 804: NO), the cooperative SaaS discovery unit 154 determines that the data format of the export API of the SaaS_Z is the above-described SaaS search of the user. It is determined with reference to the SaaS interface DB 151 whether the same data format as the specified SaaS import API exists (step 805).

  As a result of the above determination, when the same data format exists as SaaS_Z (step 805: YES), the cooperative SaaS discovery unit 154 adds the SaaS_Z to the recommended SaaS list (step 806), and step 804. The process is returned to and the process for another SaaS is executed.

  On the other hand, when the same data format does not exist as SaaS_Z (step 805: NO), the cooperative SaaS discovery unit 154 returns the process to step 804 and similarly executes the process for another SaaS.

  When all the processes related to SaaS (steps 804 to 806) acquired in step 803 are completed, the cooperative SaaS discovery unit 154 calls the recommended SaaS list, outputs it to the user terminal 200, and ends the process. .

  The portal function unit 132 of the SaaS marketplace server 130 incorporates each process of the flow of FIG. 12 into the search process of SaaS, and in addition to the information on the possibility of data collaboration with the SaaS that the user is contracting, SaaS Search results can be displayed. In this case, the portal function unit 132 receives the SaaS search condition from the user terminal 200, searches the SaaS information DB 133 for SaaS that matches the search condition, and for each SaaS included in this search result, the SaaS shown in FIG. Execute the process. As a result, for each SaaS included in the SaaS search result, it is possible to determine whether data can be linked to SaaS that the user has already contracted, and the result can be returned to the user terminal 200. The portal function unit 132 displays information on the possibility of data cooperation on the user terminal 200 together with the search result, thereby efficiently presenting information on SaaS that can be data-linked immediately with the SaaS used by the user. it can.

--- Third Embodiment ---
Next, a third embodiment of the present invention will be described. The embodiments so far have been described on the assumption that the cooperative gateway 100 is placed on the site of the SaaS platform operator. In this configuration, when the data cooperation unit 112 exports and acquires data from one SaaS, this data becomes accessible from the SaaS platform operator, and there is a concern that the security level is lowered. In the third embodiment, the SaaS platform operator provides a service for placing the cooperation gateway 100 at the user site and storing data in the middle of the cooperation, so that the burden of introducing the cooperation gateway 100 to the user site is secure. A method for realizing SaaS cooperation with a small amount of data will be described.

  FIG. 13 is a diagram illustrating a network configuration example including the inter-SaaS data cooperation support system 1 according to the third embodiment. Although the configuration is almost the same as the network configuration (FIG. 1) of the first embodiment, the SaaS linkage management server 150 has a linkage data storage unit 901 that receives the linkage data, and linkage data 902 that is an area for storing the linkage data. The gateway DB 904 that holds information on the cooperative gateway 100 placed on the user site is newly provided. The cooperative gateway 100 also includes an encryption unit 903 that executes data encryption / decryption when the cooperative data is stored in the cooperative data storage unit 901.

  In the case of such a configuration, it is assumed that the cooperative gateway 100 is provided to a user by a SaaS platform operator using package software or a VM (Virtual Machine) image. One user introduces the cooperation gateway 100 in the user site, and configures the network of the user site so as to be accessible from the SaaS cooperation management server 150 of the SaaS platform operator. Such a user notifies the SaaS platform operator of the network address for the SaaS cooperation management server 150 to access the cooperation gateway 100. On the other hand, the SaaS platform operator receives the above-mentioned contact from the user and records address information in the gateway DB 904. In addition, the cooperation gateway 100 becomes a structure arrange | positioned for every organization to which a user belongs.

  FIG. 14 is a diagram illustrating a data structure example of the gateway DB 904 in the third embodiment. In the gateway DB 904 illustrated in FIG. 14, values of a company name 1001 that uniquely indicates a user's affiliation and an interface URL 1002 that is address information for accessing the cooperative gateway 100 installed by the user are stored in association with each other. Database.

  The processing of the cooperation registration unit 155 of the SaaS cooperation management server 150 in such a configuration is basically the same as the flow of FIG. 10 of the first embodiment. However, in step 603 of the flow, the processing when instructing the cooperation gateway 100 to create a cooperation URL is different. Specifically, the cooperation registration unit 155 obtains the company name of the user who called the cooperation registration unit 155 from the authentication information, and obtains the interface URL 1002 of the cooperation gateway 100 corresponding to the company name with reference to the gateway DB 904. To do. Also, the cooperation registration unit 155 calls the API creation unit 111 of the cooperation gateway 100 with the URL.

  Next, processing of the data linkage unit 112 in the third embodiment will be described. This is almost the same as each process in the flow of FIG. 11 of the first embodiment, except that the data to be linked is temporarily stored in the SaaS base.

  Specifically, in step 703, the data linkage unit 112 passes the data to be linked between the corresponding SaaS, that is, the linkage data is encrypted to the encryption unit 903, and the encrypted linkage data is stored in the SaaS linkage management. A request is made to the cooperation data storage unit 901 of the server 130.

Upon receiving such a data storage request, the cooperation data storage unit 901 allocates a storage area corresponding to the data size in the cooperation data 902 (data storage file) in the storage device, and stores the corresponding cooperation data. At that time, the linkage data storage unit 901 returns a key for calling the linkage data to the data linkage unit 112.

  On the other hand, the data linkage unit 112 uses the key obtained from the linkage data storage unit 901 at the time of the data save request described above before calling the SaaS import API of the data linkage destination, and sends the corresponding linkage data from the linkage data storage unit 902. Obtaining and executing a decryption process by the encryption unit 903. In addition, the data cooperation unit 112 transmits the plaintext cooperation data obtained by the decryption process to the cooperation destination SaaS using the import API (step 704).

  In order to prevent the SaaS platform operator from accessing the cooperation data, it is only necessary to arrange the cooperation gateway 100 at the user site, but it is necessary to prepare an area in which the cooperation gateway 100 temporarily records data. When the cooperative gateway 100 is placed at the user site, there is a risk that the cost may be increased if the user site resources are allocated to this area. As in this third embodiment, by providing an area for data storage by the SaaS platform operator and storing the encrypted data at the user site, the user can reduce the risk of data leakage, The cost of allocating data storage areas can also be reduced.

--- Fourth Embodiment ---
In the fourth embodiment of the present invention, a mechanism for a SaaS infrastructure provider to charge a user or a SaaS provider for data linkage between SaaS will be described. As a result, the SaaS platform operator can obtain a compensation for mediating SaaS cooperation.

  FIG. 15 is a diagram illustrating an example of a data structure of the cooperation DB 152 in the fourth embodiment. Specifically, FIG. 15 is a diagram illustrating a DB that is an extension of the cooperation DB 152 of the first embodiment. This extension corresponds to providing a field for recording the number of executions 327 of each SaaS collaboration.

  In this case, when the data linkage unit 112 of the linkage gateway 100 completes the data linkage process, the value of the execution frequency field 327 in the linkage DB 152 is incremented, and how many times the data linkage between the respective SaaS is executed. Count what has been done. The predetermined function unit (for example, portal function unit 132) corresponding to the billing process of the SaaS marketplace server 130 periodically monitors the value of the execution number field 327 of the cooperation DB 152 and determines the number of cooperation processes within a certain period. Acquire and calculate the billing amount for each company name according to the value.

  This calculation process assumes that the value of the unit charge relating to the corresponding SaaS in the SaaS information DB 133 illustrated in FIG. Alternatively, when the value in the execution number field 327 is not the number of executions but the amount of transfer data, a unit charge value corresponding to the attribute is specified in the SaaS information DB 133 and multiplied. In any case, the charging amount calculated here is stored in a record related to the corresponding company in the contract DB 131 (FIG. 3) by the portal function unit 132 and the like, and then the predetermined charging process (registration of the corresponding company) is executed. It will be used for withdrawals from financial accounts).

  Although the best mode for carrying out the present invention has been specifically described above, the present invention is not limited to this, and various modifications can be made without departing from the scope of the invention.

  According to this embodiment, it is possible to efficiently achieve cooperation between SaaS without a development burden on the user side.

  At least the following will be clarified by the description of the present specification. That is, in the inter-SaaS data cooperation support system according to the present embodiment, the arithmetic device executes the predetermined algorithm in response to a request for calling a cooperation API from a predetermined device, and one of the SaaS groups defined by the corresponding cooperation API. It is also possible to further execute a process of acquiring predetermined data from the SaaS and transmitting the predetermined data to the other SaaS.

  According to this, it is possible to carry out the inter-SaaS data cooperation process itself with the inter-SaaS data cooperation support system, thereby further improving the efficiency of the process.

  Also, in the SaaS data linkage support system according to the present embodiment, the computing device includes, as information relating to the data input / output interface of each SaaS, a data input / output API and data format information that can be accepted by the API. May be acquired from a predetermined device and stored in the interface DB.

  According to this, for example, a SaaS platform provider or a SaaS provider can easily register SaaS information to be provided in the interface DB and set it as a target for subsequent SaaS data linkage processing. It becomes possible. As a result, management and data linkage without omission are achieved for each SaaS.

  Further, in the inter-SaaS data cooperation support system of the present embodiment, the storage device further holds a contract DB that stores information related to SaaS under contract for the SaaS user, and the arithmetic device is the SaaS When specifying a set of SaaS, a predetermined user specifies SaaS under contract in the contract DB, and among the specified SaaS under contract, a set of SaaS having a common data format in the interface is specified based on the interface DB. It may be a thing.

  According to this, what can be data-linked without any particular trouble between each SaaS under contract is clearly indicated to the user who is the subject of the contract, while the inter-SaaS data linkage support system performs data linkage between these SaaSs. It is possible to receive a user instruction for setting smoothly. As a result, cooperation between SaaS can be efficiently achieved without a development burden on the user side.

  Further, in the inter-SaaS data collaboration support system of the present embodiment, the storage device is contracting for a SaaS information DB storing information related to SaaS to be managed by the inter-SaaS data collaboration support system and a SaaS user. A contract DB storing information about SaaS, and the arithmetic unit executes a search in the SaaS information DB in response to a search request for SaaS received from a predetermined device, and the search result indicates It is determined based on the interface DB whether or not the data format in the interface can be shared in common with respect to the predetermined SaaS and the contracted SaaS specified in the contract DB with respect to the user who has made the search request, and the determination result Is further executed to output to the specified device. That may be.

  According to this, for example, for SaaS that the user is newly assumed to use, it is possible to identify SaaS that can be linked with data from SaaS under contract by the corresponding user and present it to the user. As the user can freely search for SaaS according to his / her needs, the possibility of data linkage with the contracted SaaS can be taken into consideration, so that SaaS search without waste can be performed in terms of data linkage. In addition, the SaaS-to-SaaS data cooperation support system also makes it possible to propose SaaS in a contract as appropriate from the viewpoint of data cooperation in accordance with SaaS search operations, and to further efficiently cooperate between SaaS without the development burden on the user side. It becomes possible to plan.

  Further, in the inter-SaaS data cooperation support system of the present embodiment, the arithmetic device holds the interface DB and a gateway DB that stores a network address of a second information processing device managed by each user, Is specified based on the interface DB, information related to the set is output to a predetermined device, and when a request for cooperation setting from the user is received from the predetermined device for the set, the second information regarding the user is stored in the gateway DB. A first information processing apparatus that identifies the network address of the processing apparatus and notifies the network API of the instruction to generate the cooperation API, holds the cooperation API, and responds to a request for calling the cooperation API from a predetermined apparatus. In response, the predetermined algorithm is executed, and the S defined by the corresponding cooperation API a second information processing apparatus disposed in a network environment on the user side, which executes processing for acquiring predetermined data from one SaaS in the aS group and transmitting the predetermined data to the other SaaS; It may be configured.

  According to this, so-called sensitive information such as business data in a company or the like can be reliably managed not on the SaaS platform operator side but on the user side, and secure data management can be realized at the time of data linkage between SaaS. As a result, secure cooperation between SaaS can be achieved more efficiently and reliably without a development burden on the user side.

  Further, in the inter-SaaS data cooperation support system of the present embodiment, when the second information processing apparatus acquires predetermined data from one SaaS of the SaaS group, the second data processing apparatus stores the predetermined data in the network environment on the user side. When temporarily storing in a predetermined storage device located outside and transmitting to the other SaaS, it may be read from the predetermined storage device and transmitted to the other SaaS.

  According to this, it becomes possible to easily manage business data and the like in a company with a storage service that can quickly and freely expand and reduce the data capacity, etc., and the cost and labor of data management as a user when data is linked between SaaS It can be greatly reduced. As a result, secure cooperation between SaaS can be achieved more efficiently and reliably without a development burden on the user side.

  Further, in the inter-SaaS data cooperation support system of the present embodiment, when the second information processing apparatus acquires predetermined data from one SaaS of the SaaS group, the second data processing apparatus encrypts the predetermined data with a predetermined algorithm, Encrypted data is temporarily stored in a predetermined storage device located outside the network environment on the user side, and when transmitted to the other SaaS, read from the predetermined storage device, decrypted, and then transmitted to the other SaaS It is good also as what to do.

  According to this, it is possible to manage so-called sensitive information such as business data in companies, etc. securely and surely on the user side, not on the SaaS platform operator side, and realize more secure data management when data is linked between SaaS I can do it. As a result, more secure cooperation between SaaS can be achieved more efficiently and reliably without a development burden on the user side.

  Further, in the inter-SaaS data cooperation support system according to the present embodiment, when the second information processing apparatus acquires predetermined data from one SaaS of the SaaS group, the inter-SaaS data cooperation support system manages. For the predetermined SaaS corresponding to the storage service, the acquired predetermined data is temporarily stored, and when it is transmitted to the other SaaS, it is read from the predetermined SaaS and transmitted to the other SaaS. Good.

According to this, it becomes possible to easily manage business data, etc. in companies, etc. with a storage service that can quickly and freely expand and reduce the data capacity, etc., greatly increasing the cost and labor of data management as a user when linking data between SaaS Can be reduced. As a result, secure cooperation between SaaS can be achieved more efficiently and reliably without a development burden on the user side.

  In the inter-SaaS data cooperation support system according to the present embodiment, the arithmetic device executes the predetermined algorithm in response to a cooperation API call request from the predetermined device, and the SaaS group defined by the corresponding cooperation API. The number of times that predetermined data is acquired from one SaaS, the process of transmitting the predetermined data to the other SaaS is executed for each user, and the accounting process corresponding to the counted number is executed for the user. It may be.

  According to this, efficient billing management can be performed without omission with respect to the charges to be collected from the user in the data linkage between SaaS. The user can easily estimate the cost to be borne by the user, and can efficiently manage funds with high accuracy. As a result, it is possible to achieve cooperation between SaaS without burden on development and the like on the user side.

  Further, in the inter-SaaS data cooperation support system of the present embodiment, the arithmetic device executes the predetermined algorithm in response to a request for calling a cooperation API from the predetermined device, and the SaaS group defined by the corresponding cooperation API. In the process of acquiring predetermined data from one SaaS and transmitting the predetermined data to the other SaaS, the amount of processed data is counted for each user, and charging processing corresponding to the counted data amount is executed for the corresponding user. It may be a thing to do.

  According to this, efficient billing management can be performed without omission with respect to the charges to be collected from the user in the data linkage between SaaS. The user can easily estimate the cost to be borne by the user, and can efficiently manage funds with high accuracy. As a result, it is possible to achieve cooperation between SaaS without burden on development and the like on the user side.

  Further, in the inter-SaaS data cooperation support method according to the present embodiment, the computer system executes the predetermined algorithm in response to a request for calling a cooperation API from a predetermined device, and one of the SaaS groups defined by the corresponding cooperation API. It is also possible to further execute a process of acquiring predetermined data from one SaaS and transmitting the predetermined data to the other SaaS.

  In the SaaS inter-data data support method according to the present embodiment, the computer system includes a data input / output API and information on a data format that can be accepted by the API as information on the data input / output interface of each SaaS. May be acquired from a predetermined device and stored in the interface DB.

  In the SaaS inter-data cooperation support method according to the present embodiment, the computer system further holds a contract DB storing information on SaaS under contract for the SaaS user in the storage device, When specifying, SaaS that a predetermined user is contracting is specified in the contract DB, and among the specified SaaS in contract, a set of SaaS having a common data format in the interface is specified based on the interface DB. Good.

In the SaaS inter-data collaboration support method according to the present embodiment, the computer system stores a SaaS information DB storing information on SaaS managed by the inter-SaaS inter-data collaboration support system in the storage device, and a SaaS user. And a contract DB storing information related to SaaS under contract, and an S received from a predetermined device.
A search is performed in the SaaS information DB in response to a search request for aaaS, and the interface between the predetermined SaaS indicated by the search result and the in-contract SaaS specified in the contract DB for the user who has made the search request. It may be determined based on the interface DB whether or not data formats can be shared in common with each other, and a process of outputting the determination result to a predetermined device may be further executed.

  Further, in the SaaS data collaboration support method of the present embodiment, the first information processing device constituting the computer system is a storage device, the interface DB, and a network of second information processing devices managed by each user. The gateway DB storing the address, specifying the set based on the interface DB, outputting information about the set to a predetermined device, and receiving a request for cooperation setting for the set from the user from the predetermined device In this case, the network address of the second information processing apparatus is specified in the gateway DB with respect to the user, the generation instruction of the cooperation API is notified to the network address, the computer system is configured, and the network on the user side A second information processing apparatus arranged in the environment is connected to the network; An API is held, the predetermined algorithm is executed in response to a request for calling a cooperative API from a predetermined device, predetermined data is acquired from one SaaS of the SaaS group defined by the corresponding cooperative API, and the predetermined data is transferred to the other The process of transmitting to SaaS may be executed.

  Further, in the inter-SaaS data cooperation support method of the present embodiment, when the second information processing apparatus acquires predetermined data from one SaaS of the SaaS group, the predetermined data is stored in the network environment on the user side. When temporarily storing in a predetermined storage device located outside and transmitting to the other SaaS, it may be read from the predetermined storage device and transmitted to the other SaaS.

  Further, in the inter-SaaS data cooperation support method of the present embodiment, when the second information processing apparatus acquires predetermined data from one SaaS of the SaaS group, the predetermined data is encrypted with a predetermined algorithm, Encrypted data is temporarily stored in a predetermined storage device located outside the network environment on the user side, and when transmitted to the other SaaS, read from the predetermined storage device, decrypted, and then transmitted to the other SaaS You may do it.

  Further, in the inter-SaaS data collaboration support method of the present embodiment, when the second information processing apparatus acquires predetermined data from one SaaS of the SaaS group, the inter-SaaS data collaboration support system manages. For the predetermined SaaS corresponding to the storage service, the acquired predetermined data may be temporarily stored and read from the predetermined SaaS and transmitted to the other SaaS when transmitted to the other SaaS.

  In the inter-SaaS data cooperation support method of the present embodiment, the computer system executes the predetermined algorithm in response to a request for calling a cooperation API from the predetermined device, and the SaaS group defined by the corresponding cooperation API. It is assumed that the number of times that the process of acquiring predetermined data from one SaaS and transmitting the predetermined data to the other SaaS is performed is counted for each user, and the charging process corresponding to the counted number is performed for the corresponding user. Also good.

Further, in the inter-SaaS data cooperation support method of the present embodiment, the computer system executes the predetermined algorithm in response to a cooperation API call request from the predetermined device, and the SaaS group defined by the corresponding cooperation API. In the process of acquiring predetermined data from one SaaS and transmitting the predetermined data to the other SaaS, the amount of processed data is counted for each user, and charging processing corresponding to the counted data amount is executed for the corresponding user. You may do that.

DESCRIPTION OF SYMBOLS 1 SaaS data cooperation support system 10 Information processing apparatus 11 Storage apparatus 12 Program 13 Memory 14 Calculation apparatus 15 Input / output apparatus 16 Communication apparatus 20, 30 Network 100 Cooperation gateway 111 API preparation part 112 Data cooperation part 130 SaaS Marketplace server 131 Contract DB
132 Portal Function Unit 133 SaaS Information DB
150 SaaS cooperation management server 151 SaaS interface DB (interface DB)
152 Cooperation DB
153 Interface registration unit 154 Cooperation SaaS discovery unit 155 Cooperation registration unit 170 SaaS server 171, 172, 173 SaaS
200 User terminal 210 Web browser 211 Business program 901 Cooperative data storage unit 902 Cooperative data storage area 903 Encryption unit 904 Gateway DB

Claims (18)

A storage device that holds an interface DB that stores information on data input / output interfaces in each SaaS;
When a set of SaaS having a common data format in the interface is specified based on the interface DB, information on the set is output to a predetermined device, and a request for cooperation setting from the user is received from the predetermined device for the set, Executes a process of assigning predetermined information defining the group as a SaaS group to be linked to an API that acquires an execution result of a predetermined algorithm corresponding to a data linkage process between SaaS, and storing it in a storage device as a linkage API An arithmetic unit;
The SaaS data cooperation support system characterized by including this. The arithmetic unit is
In response to a cooperation API call request from a predetermined device, the predetermined algorithm is executed, predetermined data is acquired from one SaaS of the SaaS group defined by the corresponding cooperation API, and the predetermined data is transmitted to the other SaaS. To perform further processing,
The inter-SaaS data collaboration support system according to claim 1. The arithmetic unit is
As information on the data input / output interface of each SaaS, a data input / output API and data format information that can be accepted by the API are acquired from a predetermined device and stored in the interface DB. Is,
The inter-SaaS data collaboration support system according to claim 1. The storage device
For SaaS users, it further holds a contract DB that stores information related to SaaS under contract,
The arithmetic unit is
When the SaaS group is specified, the contract user identifies SaaS under contract in the contract DB, and among the specified SaaS under contract, the SaaS group having a common data format in the interface is based on the interface DB. Is to identify
The inter-SaaS data collaboration support system according to claim 1. The storage device
A SaaS information DB that stores information related to SaaS to be managed by the inter-SaaS data linkage support system, and a contract DB that stores information related to SaaS under contract for a SaaS user,
The arithmetic unit is
A search is performed in the SaaS information DB in response to a SaaS search request received from a predetermined device, and the predetermined SaaS indicated by the search result and the contracted SaaS specified in the contract DB regarding the user who has made the search request In the meantime, it is determined on the basis of the interface DB whether the data format in the interface can be shared in common with each other, and the process of outputting the determination result to a predetermined device is further executed.
The inter-SaaS data collaboration support system according to claim 1. The arithmetic unit is
The interface DB and the gateway DB storing the network address of the second information processing device managed by each user are held, the set is specified based on the interface DB, and information on the set is output to a predetermined device When a request for cooperation setting from the user is received from the predetermined device for the group, the network address of the second information processing device is specified in the gateway DB for the user and the cooperation API is addressed to the network address. A first information processing apparatus for notifying a generation instruction;
The predetermined API is held, the predetermined algorithm is executed in response to a request for calling the cooperative API from a predetermined device, predetermined data is acquired from one SaaS of the SaaS groups defined by the corresponding cooperative API, and the predetermined data A second information processing apparatus disposed in a user-side network environment;
The SaaS inter-data cooperation support system according to claim 1, wherein the system is configured as follows. The second information processing apparatus
When the predetermined data is acquired from one SaaS of the SaaS group, the predetermined data is temporarily stored in a predetermined storage device located outside the network environment on the user side, and transmitted to the other SaaS. Read from the storage device and send to the other SaaS,
The inter-SaaS data collaboration support system according to claim 6. The second information processing apparatus
When obtaining predetermined data from one SaaS of the SaaS group, the predetermined data is encrypted with a predetermined algorithm, and the encrypted data is temporarily stored in a predetermined storage device located outside the network environment on the user side, When transmitting to the other SaaS, after reading from the predetermined storage device and decoding, it is transmitted to the other SaaS.
The inter-SaaS data collaboration support system according to claim 6. The second information processing apparatus
When the predetermined data is acquired from one SaaS of the SaaS group, the acquired predetermined data is temporarily stored for the predetermined SaaS corresponding to the storage service managed by the inter-SaaS data cooperation support system, When transmitting to the other SaaS, reading from the predetermined SaaS and transmitting to the other SaaS,
The inter-SaaS data collaboration support system according to claim 6. A computer system including a storage device that holds an interface DB that stores information related to data input / output interfaces in each SaaS,
When a set of SaaS having a common data format in the interface is specified based on the interface DB, information on the set is output to a predetermined device, and a request for cooperation setting from the user is received from the predetermined device for the set, Executes a process of assigning predetermined information defining the group as a SaaS group to be linked to an API that acquires an execution result of a predetermined algorithm corresponding to a data linkage process between SaaS, and storing it in a storage device as a linkage API ,
The SaaS inter-data cooperation support method characterized by the above. The computer system is
In response to a cooperation API call request from a predetermined device, the predetermined algorithm is executed, predetermined data is acquired from one SaaS of the SaaS group defined by the corresponding cooperation API, and the predetermined data is transmitted to the other SaaS. Perform further processing,
The inter-SaaS data linkage support method according to claim 10. The computer system is
As information on the data input / output interface of each SaaS, a data input / output API and data format information that can be accepted by the API are acquired from a predetermined device and stored in the interface DB. ,
The inter-SaaS data linkage support method according to claim 10. The computer system is
In the storage device, for the SaaS user, further holds a contract DB storing information on SaaS under contract,
When the SaaS group is specified, the contract user identifies SaaS under contract in the contract DB, and among the specified SaaS under contract, the SaaS group having a common data format in the interface is based on the interface DB. Identify,
The inter-SaaS data linkage support method according to claim 10. The computer system is
The storage device further holds a SaaS information DB storing information related to SaaS to be managed by the inter-SaaS data cooperation support system, and a contract DB storing information related to SaaS under contract for SaaS users. ,
A search is performed in the SaaS information DB in response to a SaaS search request received from a predetermined device, and the predetermined SaaS indicated by the search result and the contracted SaaS specified in the contract DB regarding the user who has made the search request For the interval, it is determined based on the interface DB whether the data format in the interface is common to each other, and the process of outputting the determination result to a predetermined device is further executed.
The inter-SaaS data linkage support method according to claim 10. A first information processing apparatus constituting the computer system;
In the storage device, the interface DB and the gateway DB storing the network address of the second information processing apparatus managed by each user are held.
When the group is specified based on the interface DB, information on the group is output to a predetermined device, and when a request for cooperation setting from the user is received from the predetermined device for the set, the gateway DB Specifying the network address of the information processing apparatus, and notifying the generation instruction of the cooperative API addressed to the network address,
A second information processing apparatus that constitutes the computer system and is arranged in a network environment on the user side,
The predetermined API is held, the predetermined algorithm is executed in response to a request for calling the cooperative API from a predetermined device, predetermined data is acquired from one SaaS of the SaaS groups defined by the corresponding cooperative API, and the predetermined data Execute the process of sending to the other SaaS,
The inter-SaaS data linkage support method according to claim 10. The second information processing apparatus is
When the predetermined data is acquired from one SaaS of the SaaS group, the predetermined data is temporarily stored in a predetermined storage device located outside the network environment on the user side, and transmitted to the other SaaS. Read from the storage device and send to the other SaaS,
The inter-SaaS data linkage support method according to claim 15. The second information processing apparatus is
When obtaining predetermined data from one SaaS of the SaaS group, the predetermined data is encrypted with a predetermined algorithm, and the encrypted data is temporarily stored in a predetermined storage device located outside the network environment on the user side, When transmitting to the other SaaS, after reading from the predetermined storage device and decrypting, transmitting to the other SaaS,
The inter-SaaS data linkage support method according to claim 15. The second information processing apparatus is
When the predetermined data is acquired from one SaaS of the SaaS group, the acquired predetermined data is temporarily stored for the predetermined SaaS corresponding to the storage service managed by the inter-SaaS data cooperation support system, When transmitting to the other SaaS, read from the predetermined SaaS and transmit to the other SaaS,
The inter-SaaS data linkage support method according to claim 15.

Images