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.

Abstract: The present disclosure relates to a system and method of digital product onboarding and distribution using a cloud service brokerage (CSB) infrastructure, whereby the method includes creating a product model at a vendor portal computing device, the product model based at least in part on a first product, storing the product model at a marketplace product catalog, exporting the product model to a third-party CSB platform, exporting the product model to an ordering system, configuring an application programming interface (API) to receive a request for integration of the first product, receiving, at the order system, the request for the first product, wherein the request includes a request product model payload, and fulfilling, at the order system, the request for the first product, based at least in part on a product attribute.

Abstract: Technologies for securely extending cloud service application programming interfaces (APIs) in a cloud service marketplace include a connector hub of a marketplace computing device communicatively coupled to a cloud service provider interface of a cloud service provider and a cloud service broker interface of a cloud service broker. The connector hub is configured to deploy an API connector instance in a connection factory of the marketplace computing device, transmit provider provisioning channel credentials to the API connector instance and the cloud service provider interface and transmit broker provisioning channel credentials to the API connector instance and the cloud service broker interface. The connector hub is additionally configured establish a provisioning channel between the cloud service provider interface and the cloud service broker interface. Additional embodiments are described herein.

Abstract: An Application Packaging Standard (APS) is a specification defining application's life cycle in a cloud. The application's life cycle includes packaging, delivering to the cloud, verification of package, integrating (and unpacking) into the cloud, distributing to clients, licensing, functionality, updates and deletion. The APS has its own Application Programming Interface (API) for accessing the APS functions from a program code or by http/https requests. The APS provides for efficient integration of SaaS web applications into the cloud.

Abstract: A method for integrating cloud applications into a cloud service broker (CSB) platform using an automated, universal connector, the method includes receiving at a connector hub, a connector package for a software from an independent software vendor device, creating a connector instance for the connector package for integration with the CSB platform, the CSB platform further configured to provide licenses for the software, receiving at the cloud service broker computing device via a CSB platform interface, a subscription request for the software, the subscription request comprising an activity selected from a group consisting of a creation, change and deletion, transmitting to a universal connector device by a CSB platform controller, the subscription request, processing, at the universal connector device, the subscription request, notifying a customer relationship management (CRM) device, by the universal connector device, of the subscription request, storing the subscription request in a CRM database, obtain

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.

Abstract: A system and method for multi-tenant single sign-on (SSO) identity management with dynamic attribute retrieval, the system includes at least one service provider, at least one service provider plug-in, and a service automation platform. A method for multi-tenant SSO identity management with dynamic attribute retrieval, includes the steps of receiving a link to a service provider at an SSO dispatcher, the SSO dispatcher identifying a service, requesting at the SSO dispatcher, user attributes for the at least one service provider, assembling at a service provider handler implementation, a response query, retrieving identity provider credentials from the service automation platform, signing at the SSO dispatcher, a package for a user's authentication, and redirecting the package to the service provider.

Abstract: The present disclosure relates to a system and method of digital product onboarding and distribution using a cloud service brokerage (CSB) infrastructure, whereby the method includes creating a product model at a vendor portal computing device, the product model based at least in part on a first product, storing the product model at a marketplace product catalog, exporting the product model to a third-party CSB platform, exporting the product model to an ordering system, configuring an application programming interface (API) to receive a request for integration of the first product, receiving, at the order system, the request for the first product, wherein the request includes a request product model payload, and fulfilling, at the order system, the request for the first product, based at least in part on a product attribute.

Abstract: A method for integrating cloud applications into a cloud service broker (CSB) platform using an automated, universal connector, the method includes receiving at a connector hub, a connector package for a software from an independent software vendor device, creating a connector instance for the connector package for integration with the CSB platform, the CSB platform further configured to provide licenses for the software, receiving at the cloud service broker computing device via a CSB platform interface, a subscription request for the software, the subscription request comprising an activity selected from a group consisting of a creation, change and deletion, transmitting to a universal connector device by a CSB platform controller, the subscription request, processing, at the universal connector device, the subscription request, notifying a customer relationship management (CRM) device, by the universal connector device, of the subscription request, storing the subscription request in a CRM database, obtain

Abstract: A system for provisioning applications using a Connectors Hub service is provided. At least one Service Automation module is connected to the single Connectors Hub service, which receives service APIs from a service cloud via an independent software vendor (ISV) connector. This architecture improves upon the conventional system, where a number of services are provisioned using multiple connectors located on each of the Service Automation modules. The Connectors Hub service includes a service module coupled to the statistics database. A service connector provides a service API from the ISV service cloud. This API can be directed to proxies within the Connectors Hub service, because the same service API can be used for the same service from different service providers. The proxies collect analytics data for each service provider and pass this data to the service module for generating bills for the providers based on service usage.

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.

Abstract: Many software vendors offer their software via online service platforms. In one embodiment of a software services distribution system, a cloud services broker is used. A cloud services broker is an organization that acts as an intermediary between subscribers/end users and SaaS vendors. Billing in a cloud services broker system is managed through the cloud services broker because the cloud services broker is the only entity capable of managing the many relationships in such a software distribution system. However, revenue matching and settlement may be problematic. For example, the complexities of billing in a cloud broker system arise because of the intermingling of the types of SaaS vendors, the influence of resellers, and the various billing schemes offered by each of these entities. Implementing such a billing scheme must account for the variations in billing rules and billing schemes from the entities throughout the hierarchy (i.e. SaaS vendors, resellers, sub-resellers, etc.).

Abstract: A system for multi-layered billing in a cloud service brokerage is provided, including at least one service vendor configured to provide software services, a cloud service broker, at least one transaction mediator, at least one downstream subscriber, where the cloud service broker receives service vendor pricing rules, service vendor billing rules, downstream subscriber pricing rules, and downstream subscriber billing rules, the cloud service broker further configured to apply the service vendor pricing rules and the service vendor billing rules, and to calculate settlements and perform reconciliations.

Abstract: Technologies for securely extending cloud service application programming interfaces (APIs) in a cloud service marketplace include a connector hub of a marketplace computing device communicatively coupled to a cloud service provider interface of a cloud service provider and a cloud service broker interface of a cloud service broker. The connector hub is configured to deploy an API connector instance in a connection factory of the marketplace computing device, transmit provider provisioning channel credentials to the API connector instance and the cloud service provider interface and transmit broker provisioning channel credentials to the API connector instance and the cloud service broker interface. The connector hub is additionally configured establish a provisioning channel between the cloud service provider interface and the cloud service broker interface. Additional embodiments are described herein.

Abstract: A system and method for multi-tenant single sign-on (SSO) identity management with dynamic attribute retrieval, the system includes at least one service provider, at least one service provider plug-in, and a service automation platform. A method for multi-tenant SSO identity management with dynamic attribute retrieval, includes the steps of receiving a link to a service provider at an SSO dispatcher, the SSO dispatcher identifying a service, requesting at the SSO dispatcher, user attributes for the at least one service provider, assembling at a service provider handler implementation, a response query, retrieving identity provider credentials from the service automation platform, signing at the SSO dispatcher, a package for a user's authentication, and redirecting the package to the service provider.

Abstract: A method for provisioning application resources using semantic links is provided. Each application is divided into a set of separate resources corresponding to business logic linked to each other by semantic links. The application is configured based on user requirements. The provider assembles an application provisioning package, including creating a Virtual Environment (e.g., VM) on a customer site and launching an application instance on the VM based on required configuration determined by application resources and the semantic links required by these resources. A provisioning algorithm is implemented as a hierarchical tree. A root tree resource (object) is created. All relationships (semantic links) are determined. Existing linked objects are found and not yet existing ones are determined. The tree branch is created not further than one a link from a non-existent object. The leaf nodes of the tree are existing objects or objects that do not have the required links.

Abstract: Method for web-based management of resources. On a cloud computing system, for groups of user resources, defining commonly managed subgroups. Accessing cloud-based control procedures of one subgroup using a dedicated communication channel. Control procedures reside on a server, and are visible with a single specified domain ID unique for the subgroup. Multiple domain IDs are used in one communication session. On the client, isolated windows for each domain ID contain graphical representation of local applications, and where applications of one window share local data and are connected to control procedures using the same domain ID. Managing user resources through control procedures that are controlled by the applications. Only one of the isolated windows is activated at any one time on the user's computer.

Abstract: An Application Packaging Standard (APS) is a specification defining application's life cycle in a cloud. The application's life cycle includes packaging, delivering to the cloud, verification of package, integrating (and unpacking) into the cloud, distributing to clients, licensing, functionality, updates and deletion. The APS has its own Application Programming Interface (API) for accessing the APS functions from a program code or by http/https requests. The APS provides for efficient integration of SaaS web applications into the cloud.

Abstract: Method for web-based management of resources. On a cloud computing system, for groups of user resources, defining commonly managed subgroups. Accessing cloud-based control procedures of one subgroup using a dedicated communication channel. Control procedures reside on a server, and are visible with a single specified domain ID unique for the subgroup. Multiple domain IDs are used in one communication session. On the client, isolated windows for each domain ID contain graphical representation of local applications, and where applications of one window share local data and are connected to control procedures using the same domain ID. Managing user resources through control procedures that are controlled by the applications. Only one of the isolated windows is activated at any one time on the user's computer.

Abstract: A system and method for implementing direct attachment of VMs, implemented on a computer system, to hardware devices attached to the computer system. Direct attachment architecture is implemented. The direct attachment is an exclusive dedication of a hardware device to a VM, where a particular hardware device is assigned to a particular VM. When the VM is not activated, the hardware device can be re-assigned to another VM. At system start up, hardware devices are masked from a host OS of a computer system and are automatically attached to the assigned VMs.