Build-independent software framework for creating custom adapters

Patent metadata

Field	Value
Publication number	US-11740894-B2
Application number	US-202217690288-A
Country	US
Kind code	B2
Filing date	Mar 9, 2022
Priority date	Jan 25, 2022
Publication date	Aug 29, 2023
Grant date	Aug 29, 2023

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). The system may include a build automation tool and a build-independent software framework coupled to the build automation tool. The build-independent software framework may access, via an implementation registry, information from the build automation tool that represents a custom adapter for the integration service. The build-independent software framework may then automatically create the custom adapter via a build Application Programming Interface (“API”) and automatically validate the created custom adapter via a validation API. The system can then arrange to deploy a concrete implementation of the custom adapter in the cloud computing environment. According to some embodiments, the software framework is “build-independent” because it does not require that an adapter designer use a particular Integrated Development Environment (“IDE”).

First claim

The invention claimed is:

1. A system associated with a cloud computing environment having an integration service, comprising:
a build automation tool; and
a build-independent software framework, coupled to the build automation tool, including:
a computer processor, and
a computer memory storing instructions that, when executed by the computer processor, cause the build-independent software framework to:
access, via an implementation registry, information from the build automation tool representing a custom adapter for the integration service,
automatically create the custom adapter via a build Application Programming Interface (“API”),
automatically validate the created custom adapter via a validation API, and
arrange to deploy a concrete implementation of the custom adapter in the cloud computing environment.

2. The system of claim 1 , wherein the software framework is build-independent because it does not require that an adapter designer use a particular Integrated Development Environment (“IDE”).

3. The system of claim 1 , wherein the build automation tool includes build automation tool archetypes.

4. The system of claim 3 , wherein the build automation tool further includes a metadata generator to create metadata for the custom adapter required for User Interface (“UI”) integration.

5. The system of claim 4 , wherein the build automation tool further includes an adapter validator to analyze a custom adaptor project and the metadata for errors.

6. The system of claim 5 , wherein the build automation tool further includes a builder to create a final deployable system bundle.

7. The system of claim 6 , further comprising an integration platform with an integration bus for the final deployable system bundle.

8. The system of claim 1 , wherein the build-independent software framework further includes:
a create-project API,
a build API,
a validate API, and
a deploy API.

9. 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.

10. A computer-implemented method associated with a cloud computing environment having an integration service, comprising:
accessing, via an implementation registry and a computer processor of a build-independent software framework, information from a build automation tool representing a custom adapter for the integration service;
automatically creating the custom adapter via a build Application Programming Interface (“API”);
automatically validating the created custom adapter via a validation API; and
arranging to deploy a concrete implementation of the custom adapter in the cloud computing environment.

11. The method of claim 10 , wherein the software framework is build-independent because it does not require that an adapter designer use a particular Integrated Development Environment (“IDE”).

12. The method of claim 10 , wherein the build automation tool includes build automation tool archetypes.

13. The method of claim 12 , further comprising:
creating metadata for the custom adapter required for User Interface (“UI”) integration via a metadata generator in the build automation tool.

14. The method of claim 13 , further comprising:
analyzing a custom adaptor project and the metadata for errors via an adapter validator in the build automation tool.

15. The method of claim 14 , further comprising:
creating a final deployable system bundle via a builder in the build automation tool.

16. The method of claim 10 , wherein the build-independent software framework further includes: (i) a create-project API, (ii) a build API, (iii) a validate API, and (iv) a deploy API.

17. The method of claim 10 , wherein the integration service is associated with at least one of: (i) a Software-as-a-Service, and (ii) a Platform-as-a-Service.

18. A non-transitory, computer-readable medium storing instructions, that, when executed by a processor, cause the processor to perform a method associated with a cloud computing environment having an integration service, the method comprising:
accessing, via an implementation registry and a computer processor of a build-independent software framework, information from a build automation tool that represents a custom adapter for the integration service;
automatically creating the custom adapter via a build Application Programming Interface (“API”);
automatically validating the created custom adapter via a validation API; and
arranging to deploy a concrete implementation of the custom adapter in the cloud computing environment.

19. The medium of claim 18 , wherein the software framework is build-independent because it does not require that an adapter designer use a particular Integrated Development Environment (“IDE”).

20. The medium of claim 18 , wherein the build automation tool includes build automation tool archetypes.

Assignees

• Sap Se

Inventors

• K Shankara Prasad
• Kulkarni Gopalkrishna

Classifications

• G06F8/71 Primary

  Version control (security arrangements therefor G06F21/57); Configuration management · CPC title

• G06F8/33

  Intelligent editors · CPC title

• G06F8/60

  Software deployment · CPC title

• G06F9/44505

  Configuring for program initiating, e.g. using registry, configuration files · CPC title