Abstract: The disclosure generally describes methods, software, and systems for generation of a configurable and executable integration scenario. A request to generate a data sequence integration scenario is received. The request includes one or more textual requirements. The request is validated by processing the one or more textual requirements to determine inclusion of a minimal number of systems and actions. An intent and a context of the request are determined, using a first prediction engine, from the one or more textual requirements. The intent includes top-ranked systems and APIs matching the request. The intent and the context of the request are inputted as a prompt to a second prediction engine. The data sequence integration scenario is received, from the second prediction engine, responsive to the prompt. The data sequence integration scenario defines an order of the actions to be performed by the top-ranked systems and APIs matching the request.

Abstract: According to some embodiments, methods and systems may be associated with a cloud computing environment. A unified provisioning service may include a plan configuration data store that contains information associated with a combined service representing a plurality of multi-tenant cloud applications. A cloud platform provisioning framework may receive an indication of a subscription request for the combined service from a consumer via a Software as a Service (“SaaS”) marketplace and access, responsive to the received indication, a dependent service framework of the unified provisioning service. The cloud platform provisioning framework may then receive dependency subscription data from the unified provisioning service, and, based on the dependency subscription data, arrange for the consumer to be subscribed to each of the plurality of multi-tenant cloud applications.

Abstract: According to some embodiments, methods and systems may include a data storage device that contains user identifiers and associated entitlement values for a plurality of tenants of a cloud computing environment. A provisioning application platform processor may receive a user request for an integration service and access the data storage device. The provisioning application platform processor may then transmit at least one entitlement value to a platform resource manager processor to facilitate creation of a plurality of microservices resulting in implementation of the integration service for the user.

Abstract: The disclosure generally describes methods, software, and systems for handling integration flows. A set of flows is initially deployed to a single worker set. A load balancing issue is identified that is associated with initial runtime interactions by workers with the single worker set. In response to identifying the load balancing issue, the load balancing issue is analyzed to determine whether to autoscale or generate a new worker set. Load balancing is performed to initiate at least one new worker set. At least one flow to be moved to the at least one new worker set is identified. Movement of the identified at least one flow from a current worker set to a new worker set is performed.

Abstract: According to some embodiments, methods and systems may include a data storage device that contains user identifiers and associated entitlement values for a plurality of tenants of a cloud computing environment. A provisioning application platform processor may receive a user request for an integration service and access the data storage device. The provisioning application platform processor may then transmit at least one entitlement value to a platform resource manager processor to facilitate creation of a plurality of microservices resulting in implementation of the integration service for the user.

Abstract: According to some embodiments, methods and systems may be associated with a cloud computing environment. A unified provisioning service may include a plan configuration data store that contains information associated with a combined service representing a plurality of multi-tenant cloud applications. A cloud platform provisioning framework may receive an indication of a subscription request for the combined service from a consumer via a Software as a Service (“SaaS”) marketplace and access, responsive to the received indication, a dependent service framework of the unified provisioning service. The cloud platform provisioning framework may then receive dependency subscription data from the unified provisioning service, and, based on the dependency subscription data, arrange for the consumer to be subscribed to each of the plurality of multi-tenant cloud applications.

Abstract: According to some embodiments, methods and systems may include a data storage device that contains user identifiers and associated entitlement values for a plurality of tenants of a cloud computing environment. A provisioning application platform processor may receive a user request for an integration service and access the data storage device. The provisioning application platform processor may then transmit at least one entitlement value to a platform resource manager processor to facilitate creation of a plurality of microservices resulting in implementation of the integration service for the user.

Abstract: The disclosure generally describes methods, software, and systems for handling integration flows. A set of flows is initially deployed to a single worker set. A load balancing issue is identified that is associated with initial runtime interactions by workers with the single worker set. In response to identifying the load balancing issue, the load balancing issue is analyzed to determine whether to autoscale or generate a new worker set. Load balancing is performed to initiate at least one new worker set. At least one flow to be moved to the at least one new worker set is identified. Movement of the identified at least one flow from a current worker set to a new worker set is performed.

Abstract: The disclosure generally describes methods, software, and systems for handling integration flows. A set of flows is initially deployed to a single worker set. A load balancing issue is identified that is associated with initial runtime interactions by workers with the single worker set. In response to identifying the load balancing issue, the load balancing issue is analyzed to determine whether to autoscale or generate a new worker set. Load balancing is performed to initiate at least one new worker set. At least one flow to be moved to the at least one new worker set is identified. Movement of the identified at least one flow from a current worker set to a new worker set is performed.

Abstract: The disclosure generally describes methods, software, and systems for handling integration flows. A set of flows is initially deployed to a single worker set. A load balancing issue is identified that is associated with initial runtime interactions by workers with the single worker set. In response to identifying the load balancing issue, the load balancing issue is analyzed to determine whether to autoscale or generate a new worker set. Load balancing is performed to initiate at least one new worker set. At least one flow to be moved to the at least one new worker set is identified. Movement of the identified at least one flow from a current worker set to a new worker set is performed.