System and method for connector development and integration channel development
View Patent ↗Independent Software Vendors ISVs develop, support, execute, and sell cloud applications. Cloud Service Broker Platforms (CSBs) provide partially-automated delivery of integrated cloud applications from different ISVs. Integration of ISV software requires special integration components such as connector packages and connector backends. Development of such components can be time consuming and expensive. The present disclosure relates to a system and method for allowing connector developers to decrease the cost of developing connector package and connector backends by allowing deployment and configuration of web services automatically and also allows support for scalability and zero-downtime upgrades out of the box, by the use of an automated authoring tool that generates connector packages from archetypes created by the CSB.
1. A method for connector development of software services, using a cloud service broker (CSB) platform, the method comprising:
receiving at a developer tool, a request for creation of a connector package, the developer tool operably connected to the CSB platform;
creating a copy at the developer tool, of an archetype connector package to create a base connector package;
compiling, at the developer tool, business logic code for the software services, and generating the connector package based at least in part on the base connector package;
creating, at the developer tool, a resource model schema, the resource model schema further packaged into a connector archive;
creating, at the developer tool, a connector backend deployment unit, the connector backend deployment unit further combined into a server image;
creating, at the developer tool, a container orchestrator package, the container orchestrator package comprising a set of container orchestrator resources, the container orchestrator package then pushed into a packages repository;
pushing, at the developer tool, the server image to a server repository;
assembling, at the developer tool, the server image, the resource model schema from the connector archive, and container orchestrator package to create an archive connector package; and
delivering the archive connector package to the CSB platform.
2. The method of claim 1 , wherein creating a base connector package further comprises:
requesting an application name and a persistence condition;
downloading additional components selected from a group consisting of libraries, drivers, and log appenders;
generating connector package sources; and
creating a development directory.
3. The method of claim 1 , further including the step of testing the connector package.
4. The method of claim 1 , wherein the archive connector package further includes an assembly of user interface code, resource model, navigation descriptions, and deployment descriptors.
5. The method of claim 1 , wherein the server image comprises a plurality of instruction set layers.
6. The method of claim 5 , wherein the plurality of instruction set layers forms a base image.
7. The method of claim 5 , wherein a last layer of the plurality of instruction set layers includes a developer layer.
8. A method for integration channel development of software services, using a cloud service broker (CSB) platform, the method comprising:
installing an archive connector package to the CSB platform via the CSB platform application programming interface (API);
receiving at the CSB platform, a container orchestrator package;
generating, at a developer tool, authentication credentials, the authentication credentials further built into a deployment descriptor;
running, via a container orchestrator, a connector backend obtained from the container orchestrator package;
generating, at the developer tool, a backend endpoint uniform resource locator (URL);
and
registering the endpoint URL at the CSB platform.
9. The method of claim 8 further comprising a check for a persistence requirement.
10. The method of claim 9 wherein a database connection is specified and the database connection is further written into the deployment descriptor.