US2018300115A1PendingUtilityA1

Technologies for creating and distributing integration connectors in a cloud service brokerage system

47
Assignee: INGRAM MICRO INCPriority: Apr 14, 2017Filed: Apr 13, 2018Published: Oct 18, 2018
Est. expiryApr 14, 2037(~10.8 yrs left)· nominal 20-yr term from priority
G06F 2209/5015G06F 9/5072G06Q 30/0641G06F 9/547G06F 8/60
47
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Technologies for creating and distributing integration connectors in cloud service brokerage systems include a developer portal computing device communicatively coupled to a connector hub of a marketplace computing. The developer portal computing device is configured to receive information from a developer via a developer UI portal of a developer portal computing device. Such information includes connector descriptor information for a connector associated with a cloud service and one or more resource types of the connector. The developer portal computing device is further configured to build, via a connector builder of the developer portal computing device, the connector as a function of the connector descriptor information and the one or more resource types, generate a connector package for the built connector, and transmit the generated connector package to a connector hub of a cloud service marketplace computing device, wherein the connector package is usable to create one or more instances of the connector. Additional embodiments are described herein.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A method for creating and distributing cloud service integration connectors in a cloud service brokerage system, the method comprising:
 receiving, from a developer via a developer UI portal of a developer portal computing device, connector descriptor information for a connector associated with a cloud service;   receiving, from the developer via the developer UI portal, one or more resource types of a model of the connector;   building, via a connector builder of the developer portal computing device, the connector as a function of the connector descriptor information and the one or more resource types;   generating, by the connector builder, a connector package for the built connector; and   transmitting, by the connector builder, the generated connector package to a connector hub of a cloud service marketplace computing device, wherein the connector package is usable to create one or more instances of the connector.   
     
     
         2 . The method of  claim 1 , further comprising:
 analyzing, by an expert system of the developer portal computing device, whether a previous version of the connector associated with the cloud service has been published;   determining, by the expert system and subsequent to a determination that the previous version of the connector has been published, a coincidence level between the connector and the previous version of the connector;   comparing, by the expert system, the coincidence level against a coincidence level threshold; and   relating, by the expert system, the connector with the previous version of the connector as a new version of the previous version of the connector.   
     
     
         3 . The method of  claim 1 , further comprising:
 analyzing, via the expert system of the developer portal computing device, whether another service should be related to the connector;   identifying, by the expert system, whether one or more other services could be related to the connector; and   relating, by the expert system and subsequent to having identified the one or more other services could be related to the connector, the one or more other services.   
     
     
         4 . The method of  claim 1 , further comprising receiving, from the developer via the developer UI portal, an identifier associated with a connector skeleton from a connector skeleton database of the developer portal computing device, wherein the connector skeleton is usable to generate a framework for creating the connector, and wherein receiving the one or more resource types of the connector comprises receiving the one or more resource types of the connector based on the connector skeleton. 
     
     
         5 . The method of  claim 1 , wherein receiving the connector descriptor information includes receiving a title of the service, a type of the service, an icon associated with the service, and one or more service provider instructions. 
     
     
         6 . The method of  claim 1 , further comprising:
 determining, by the connector builder, one or more differences between the connector and the previous version of the connector; and   generating, by the connector builder, one or more upgrade instructions as a function of the determined one or more differences,   wherein generating the connector package comprises generating the connector package as a function of the one or more upgrade instructions.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.