# US 11,907,687 B2 · Re-usable integration component configuration in a microservice based integration service > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,907,687 B2 - Document ID: US11907687B2 - Status: Granted - Kind: B2 - Application number: 17/457,492 - Filed: 2021-12-03 - Published: 2023-06-08 - Granted: 2024-02-20 - Earliest claimed: 2021-12-03 - Assignees: Sap SE - Applicants: Sap SE - Inventors: Gopalkrishna Kulkarni; Mrutyunjay Padmasali Sidda - Web page: https://patentgrep.com/patent/US11907687B2 ## CPC - G06F 8/36: Software reuse - G06F 8/38: for implementing user interfaces - G06F 8/60: Software deployment - G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract According to some embodiments, methods and systems may be associated with a cloud computing environment having an integration service (e.g., associated with a Software-as-a-Service or a Platform-as-a-Service). A design microservice may have a User Interface (“UI”) framework and UI components for a first integration developer. A configuration framework may determine a set of configuration values for an integration component of an integration scenario defined by the first integration developer. The configuration framework may then receive, from the first integration developer, a publication indication associated with the integration component. Responsive to the publication indication, the configuration framework may arrange for the set of configuration values for the integration component to be made available to a second integration developer (e.g., via a marketplace platform). ## Claims ### Claim 1 A system associated with a cloud computing environment having an integration service, comprising: a design microservice having a User Interface (“UP”) framework and UI components for a first integration developer associated with a first tenant, including: a UI to configuration contract establisher to extract user configurations; and a configuration framework associated with a multi-tenant microservice, including: a version management component to provide lifecycle management, a computer processor, and a computer memory storing instructions that when executed by the computer processor cause the configuration framework to: receive, from the UI to configuration contract establisher, a set of configuration values for integration components of an integration scenario, the integration scenario including adapter and custom script integration components, defined by the first integration developer, receive, from the first integration developer, a publication indication associated with the integration components, and responsive to the publication indication, arrange for the set of configuration values for the integration components to be made available to a second integration developer associated with a second tenant. ### Claim 2 (depends on 1) The system of claim 1, wherein the integration scenario further includes flow step and mapping step components. ### Claim 3 (depends on 1) The system of claim 1, wherein at least one configuration value from the set of the configuration values is associated with at least one of: (i) an authentication type, (ii) a query, (iii) a retry configuration, (iv) a time-out, (v) a big query string, (vi) a page initiation configuration, (vii) a security configuration, and (viii) a schedule. ### Claim 4 (depends on 1) The system of claim 1, wherein said arranging for the set of configuration values for the integration components to be made available to the second integration developer is associated with an open Application Programming Interface (“API”) specification. ### Claim 5 (depends on 4) The system of claim 4, wherein said arranging for the set of configuration values for the integration components to be made available to the second integration developer is associated with JavaScript Object Notation (“JSON”). ### Claim 6 (depends on 1) The system of claim 1, wherein sets of configuration values for a plurality of integration scenarios are made available to the second integration developer. ### Claim 7 (depends on 1) The system of claim 1, wherein the configuration framework further includes: a configuration registry associated with types for at least one of: (i) a component configuration, and (ii) an iFlow configuration. ### Claim 8 (depends on 1) The system of claim 1, wherein the configuration framework further includes: a configuration injector to match an appropriate configuration for the integration components. ### Claim 9 (depends on 1) The system of claim 1, wherein the configuration framework further includes: a browse configuration component and a publish configuration component to make the integration component available via a marketplace platform. ### Claim 10 (depends on 1) The system of claim 1, wherein the configuration framework further includes: a commercialization component to provide commercialization of the integration components. ### Claim 11 (depends on 1) The system of claim 1, wherein the integration service is associated with at least one of: (i) a Software-as-a-Service, and (ii) a Platform-as-a-Service. ### Claim 12 A non-transitory, computer-readable medium having executable instructions stored therein, the medium comprising: instructions to receive from a User Interface (“UI”) to configuration contract establisher, by a computer processor of a configuration framework associated with a multi-tenant microservice, a set of extracted configuration values for integration components of an integration scenario, the integration scenario including adapter and custom script integration components, defined by a first integration developer associated with a first tenant via a design microservice having a UI framework and UI components, including the UI to configuration contract establisher and a version management component to provide lifecycle management; instructions to receive, from the first integration developer, a publication indication associated with the integration components; and responsive to the publication indication, instructions to arrange for the set of extracted configuration values for the integration components to be made available to a second integration developer associated with a second tenant. ### Claim 13 (depends on 12) The medium of claim 12, wherein the integration scenario further includes flow step and mapping step components. ### Claim 14 (depends on 12) The medium of claim 12, wherein at least one configuration value from the set of the extracted configuration values is associated with at least one of: (i) an authentication type, (ii) a query, (iii) a retry configuration, (iv) a time-out, (v) a big query string, (vi) a page initiation configuration, (vii) a security configuration, and (viii) a schedule. ### Claim 15 A computer-implemented method associated with a cloud computing environment having an integration service, comprising: receiving from a User Interface (“UI”) to configuration contract establisher, by a computer processor of a configuration framework associated with a multi-tenant microservice, a set of extracted configuration values for integration components of an integration scenario, the integration scenario including adapter and custom script integration components, defined by a first integration developer associated with a first tenant via a design microservice having a UI framework and UI components, including the UI to configuration contract establisher and a version management component to provide lifecycle management; receiving, from the first integration developer, a publication indication associated with the integration components; and responsive to the publication indication, arranging for the set of extracted configuration values for the integration components to be made available to a second integration developer associated with a second tenant. ### Claim 16 (depends on 15) The method of claim 15, wherein said arranging for the set of extracted configuration values for the integration components to be made available to the second integration developer is associated with an open Application Programming Interface (“API”) specification. ### Claim 17 (depends on 16) The method of claim 16, wherein said arranging for the set of extracted configuration values for the integration components to be made available to the second integration developer is associated with JavaScript Object Notation (“JSON”). ### Claim 18 (depends on 15) The method of claim 15, wherein sets of configuration values for a plurality of integration scenarios are made available to the second integration developer.