CN113805958B - Third party service access method and system based on OSB API specification - Google Patents
Third party service access method and system based on OSB API specification Download PDFInfo
- Publication number
- CN113805958B CN113805958B CN202110948311.0A CN202110948311A CN113805958B CN 113805958 B CN113805958 B CN 113805958B CN 202110948311 A CN202110948311 A CN 202110948311A CN 113805958 B CN113805958 B CN 113805958B
- Authority
- CN
- China
- Prior art keywords
- service
- osb
- plug
- party
- access
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 34
- 238000012545 processing Methods 0.000 claims description 15
- 230000008569 process Effects 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 12
- 238000004590 computer program Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 6
- 230000004048 modification Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 5
- 230000006978 adaptation Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention discloses a third party service access method and a system based on OSB API specification, wherein the third party service access method based on OSB API specification comprises the following steps: an OSB plug-in is additionally arranged in the SaaS platform; and accessing a third party service according to OSB API specifications by using the OSB plug-in. The technical scheme of the invention can solve the problems of low flexibility of interface access and poor expandability of a plug-in layer caused by correspondingly modifying the plug-in layer code of the cloud platform when the third party service is newly added each time due to the third party service access mode in the prior art.
Description
Technical Field
The invention relates to the technical field of open service agents, in particular to a third party service access method and system based on OSB API specifications.
Background
The SaaS (Software-as-a-Service) is one way to provide a Software Service through a network, and as a SaaS layer provider-SaaS platform, it is able to provide various types of services including a Service package, an off-line Service, and a third party Service.
In the service implementation, the SaaS platform encapsulates various operations of the service instance through an SDK layer of the abstract software development kit, and develops corresponding plug-ins for different types of services, wherein the plug-ins perform the operations of the service instance through an interface of an inherited SDK layer. In the service operation process, the adaptation layer of the SaaS platform calls the realization of the corresponding plug-in layer according to different service types. For the third party service, we need to set up a third party service plug-in, and in the third party service plug-in, access to the third party service is according to the logic of each service provider. Such as: the newly increased data cluster service needs the newly increased data implementation class and calls the interface of the big data service provider; the newly added kubernetes cluster service needs to newly add an implementation class for realizing kubernetes and call an interface of a kubernetes service provider.
The access of the third party service can be realized by expanding the third party plug-in realization logic, and the method has high expansibility, however, because the method needs to correspondingly modify the codes of the SaaS platform plug-in layer every time the third party service is newly added, so as to re-adapt to interfaces of different service providers. This not only results in reduced flexibility of interface access, but also reduces the scalability of the plug-in layer.
Disclosure of Invention
The invention provides a third party service access method and system based on OSB API specification, aiming at solving the problems of reduced flexibility of interface access and reduced expandability of plug-in layers caused by correspondingly modifying a plug-in layer code of a cloud platform when a third party service is newly added each time caused by a third party service access mode in the prior art.
According to a first aspect of the present invention, there is provided a third party service access method based on OSB API specification, comprising:
an OSB plug-in is additionally arranged in the SaaS platform;
and accessing the third party service according to the OSB API specification by using the OSB plug-in.
Preferably, the step of accessing the third party service according to the OSB API specification by using the OSB plugin includes:
creating a service agent in the SaaS platform, and establishing connection between the service agent and the OSB plug-in;
accessing the third party service by using a corresponding service agent in the SaaS platform according to the service type of the third party service;
and accessing the third party service into the OSB plugin through the connection of the service agent and the OSB plugin.
Preferably, the step of accessing the third party service according to the OSB API specification by using the OSB plugin includes:
acquiring a service address of a service agent by using an OSB plug-in;
controlling an OSB plug-in to splice a service address according to OSB API specifications to obtain a URL;
and controlling the OSB plug-in to access the third-party service of the service agent to the SaaS platform through the URL.
Preferably, the step of controlling the OSB plugin to splice the service address according to OSB API specification to obtain the URL includes:
the OSB plug-in is controlled to acquire a creation interface address defined by the OSB API specification;
and controlling the OSB plug-in to splice the creation interface address and the service address defined by the OSB API specification to obtain the URL.
Preferably, the third party service access method further includes:
according to the front-end requirement of the SaaS platform, a service access unified interface is additionally arranged on a software development tool layer of the SaaS platform, wherein the service access unified interface comprises a service instance;
using OSB plug-in inheritance service to access the unified interface;
when the OSB plug-in accesses the third party service, the service instance of the unified interface is used for processing the third party service.
Preferably, the step of processing the third party service by using the service instance of the service access unified interface includes:
establishing an instance corresponding relation between a service access unified interface and a creation interface defined by OSB API specifications;
and controlling the OSB plug-in to operate the third-party service according to the corresponding relation of the examples.
According to a second aspect of the present invention, there is also provided a third party service access system based on OSB API specification, comprising:
the plug-in creation module is used for adding an OSB plug-in the SaaS platform;
and the service access module is used for accessing the third party service by using the OSB plug-in according to the OSB API specification.
Preferably, the service access module includes:
the connection establishment sub-module is used for establishing a service agent in the SaaS platform and establishing connection between the service agent and the OSB plug-in;
the service access sub-module is used for accessing the third party service by using a corresponding service agent in the SaaS platform according to the service type of the third party service;
and the plug-in access submodule is used for accessing the third-party service into the OSB plug-in through the connection of the service agent and the OSB plug-in.
Preferably, the service access module comprises:
an address acquisition sub-module for acquiring a service address of the service agent using the OSB plug-in;
the address splicing sub-module is used for controlling the OSB plug-in to splice the service address according to the OSB API specification to obtain the URL;
and the platform access sub-module is used for controlling the OSB plug-in to access the third party service of the service agent to the SaaS platform through the URL.
Preferably, the third party service access system further comprises:
the interface creation module is used for adding a service access unified interface to a software development tool layer of the SaaS platform according to the front-end requirement of the SaaS platform, wherein the service access unified interface comprises a service instance;
the interface inheritance module is used for using the OSB plug-in inheritance service to access the unified interface;
and the service processing module is used for controlling the OSB plug-in to process the third party service by using the service instance of the service access unified interface when the OSB plug-in is accessed to the third party service.
According to the third party service access scheme based on the OSB API specification, the OSB plug-in is additionally arranged on the SaaS platform, and then the OSB plug-in is used for accessing the third party service according to the OSB API specification. The OSB API is known as Open Service Broker API, which is an open service proxy API, through which independent software vendors, saaS providers, and developers can integrate and run their services onto SaaS platforms, such as cloud computing platforms and Kubernetes platforms, with great convenience. Such API specifications have been adopted by more and more platforms or service providers. Service items such as generating service, accessing service, managing service and the like can be realized through a group of API endpoints. The SaaS platform realizes the OSB plug-in of the service agent access, the third party service provider realizes the own service agent according to the OSB API specification, and the SaaS platform can conveniently access the third party service, such as kubernetes cluster service, big data cluster service and the like, by accessing the service agent of the corresponding manufacturer through the plug-in.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to the structures shown in these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of an OSB API service architecture according to an embodiment of the present invention;
FIG. 2 is a flow chart of a first method for third party service access based on OSB API specifications according to an embodiment of the present invention;
FIG. 3 is a flow chart of a first third party service access method provided by the embodiment of FIG. 2;
FIG. 4 is a flow chart of a second third party service access method provided by the embodiment of FIG. 2;
FIG. 5 is a flow chart of a second method for third party service access based on OSB API specifications according to an embodiment of the present invention;
FIG. 6 is a flowchart of a third party service processing method according to the embodiment shown in FIG. 5;
FIG. 7 is a schematic structural diagram of a first third party service access system based on OSB API specifications according to an embodiment of the present invention;
FIG. 8 is a schematic structural diagram of a first service access module provided by the embodiment shown in FIG. 7;
FIG. 9 is a schematic diagram of a second service access module provided by the embodiment of FIG. 7;
fig. 10 is a schematic structural diagram of a second third party service access system based on OSB API specification according to an embodiment of the present invention.
The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
The main technical problems of the embodiment of the invention are as follows:
in the service implementation, the SaaS platform encapsulates various operations of the service instance through the SDK layer, and develops corresponding plug-ins for different types of services, where the plug-ins perform the operations of the service instance through inheriting the interfaces of the SDK layer. The adaptation layer of the SaaS platform calls the realization of the corresponding plug-in layer according to different service types. For the third party service, we need to set up a third party service plug-in, and in the third party service plug-in, access to the third party service is according to the logic of each service provider. The access of the third party service can be realized by expanding the third party plug-in, and the mode has high expansibility. However, since this approach requires corresponding modification of the code of the SaaS platform plug-in layer each time a third party service is added, the third party plug-in is accessed to re-adapt the interfaces of different service providers. This not only results in reduced flexibility of interface access, but also reduces the scalability of the plug-in layer.
In order to solve the above problem, referring specifically to fig. 1, in the technical solutions provided in the following embodiments of the present application, the present application provides an OSB API service architecture. In this service architecture, an OSB plug-in 105 is added in a plug-in layer 109 in the service factory 100 of the SaaS platform, and the OSB plug-in 105 can implement OSB API specification, through which different service agents, such as the big data agent 106 and the k8s agent 107 in fig. 1, can be accessed, so that multiple third party services can be accessed without the need for a corresponding service plug-in. In addition, the service factory 100 includes an API server 101, a directory service 102, a service adapter 103 disposed within a service unifying access layer 108, and an SDK defining service unifying interface.
Referring specifically to fig. 2, fig. 2 is a schematic flow chart of a third party service access method based on OSB API specification according to an embodiment of the present invention. As shown in fig. 2, the third party service access method based on OSB API specification includes:
s110: and an OSB plug-in is additionally arranged in the SaaS platform. The OSB plug-in can realize OSB API specification and inherits relevant interfaces in the SaaS platform, thereby realizing the access of third party services.
S120: and accessing the third party service according to the OSB API specification by using the OSB plug-in. The OSB API specification is in the form of the following table, and includes interface addresses of various interfaces, and its functions include creating a service instance, deleting a service instance, querying details of the service instance, and obtaining service information (name, description and specification) by service instance expansion mailing.
OSB API specification table
According to the third party service access method based on the OSB API specification, the OSB plug-in is additionally arranged on the SaaS platform, and then the OSB plug-in is used for accessing the third party service according to the OSB API specification. The OSB API is known as Open Service Broker API, which is an open service proxy API, through which independent software vendors, saaS providers, and developers can integrate and run their services onto SaaS platforms, such as cloud computing platforms and Kubernetes platforms, with great convenience. Such API specifications have been adopted by more and more platforms or service providers. Service items such as generating service, accessing service, managing service and the like can be realized through a group of API endpoints. The SaaS platform realizes the OSB plug-in of the service agent access, the third party service provider realizes the own service agent according to the OSB API specification, and the SaaS platform can conveniently access the third party service, such as kubernetes cluster service, big data cluster service and the like, by accessing the service agent of the corresponding manufacturer through the plug-in.
As a preferred embodiment, as shown in fig. 3, step S120 described above: the step of accessing the third party service according to the OSB API specification using the OSB plug-in comprises:
s121: and creating a service agent in the SaaS platform, and establishing connection between the service agent and the OSB plug-in. According to the embodiment of the application, the service agents, such as the big data agent and the k8s agent, are created in the SaaS platform, and the connection with the OSB plug-in can be established through the service agents, so that the SaaS platform can access different third party services, and the different third party services can be uniformly accessed and managed through the OSB plug-in.
S122: and accessing the third party service by using a corresponding service agent in the SaaS platform according to the service type of the third party service. The service types of the third party service comprise big data service, artificial intelligence service, k8s service and the like, corresponding service agents are provided in the SaaS platform, and different services are respectively accessed, so that the different service agents can transmit different services to the OSB plug-in.
S123: and accessing the third party service into the OSB plugin through the connection of the service agent and the OSB plugin.
In the embodiment of the application, all the service agents establish connection with the OSB plugin, so that different third party services can be accessed into the SaaS platform only by using one type of plugin of the OSB plugin in the SaaS platform.
As a preferred embodiment, as shown in fig. 4, step S120 described above: the step of accessing the third party service in accordance with the OSB API specification using the OSB plug-in comprises:
s124: the OSB plug-in is used to obtain the service address of the service agent. The service address of the service agent is obtained by using the OSB plug-in, and then the connection between the OSB plug-in and the service agent can be established by using the service address, so that when the service agent obtains the relevant third party service, the third party service can be accessed into the OSB plug-in through the service address.
S125: and controlling the OSB plug-in to splice the service address according to the OSB API specification to obtain the URL. The URL connects the service agent with the created interface address defined by the OSB API specification so that the OSB plug-in can connect to different service agents and access different third party services through the URL.
The step of splicing the service address by the control OSB plug-in according to the OSB API specification to obtain the URL comprises the following steps: the OSB plug-in is controlled to acquire a creation interface address defined by the OSB API specification; and controlling the OSB plug-in to splice the creation interface address and the service address defined by the OSB API specification to obtain the URL. Specifically, for example, the ServiceBroker address of the shared big data service is http:// bigdata-ServiceBroker 32100; the OSB API defines a creation interface of/v 2/service_instances/{ instance Id }; then the complete URL address is: http:// bigdata-servicemaker 32100/v2/service_instances/{ instance id }.
S126: and controlling the OSB plug-in to access the third-party service of the service agent to the SaaS platform through the URL. Because the OSB plug-in obtains the URL through the service address, the OSB can access the third party service of the service agent into the SaaS platform through the URL in an HTTP manner.
As a preferred embodiment, as shown in fig. 5, the third party service access method provided in the embodiment of the present application further includes the following steps in addition to the above steps:
s210: and adding a service access unified interface in a software development tool layer of the SaaS platform according to the front-end requirement of the SaaS platform, wherein the service access unified interface comprises a service instance. According to the front-end requirement of the SaaS platform, a service access unified interface is additionally arranged on the SDK layer of the SaaS platform, so that the OSB plug-in can be controlled to realize the function of the interface according to the user requirement, and external third-party services can be further accessed and processed through the interface.
S220: and using the OSB plugin to inherit services to access the unified interface.
S230: when the OSB plug-in accesses the third party service, the service instance of the unified interface is used for processing the third party service.
According to the technical scheme provided by the embodiment of the application, the OSB plug-in is used for inheriting the service access unified interface, so that the service access unified interface can be used for processing the third party service according to service examples contained in various user-defined interface methods.
As a preferred embodiment, as shown in fig. 6, the step of processing a third party service using a service instance of a service access unified interface includes:
s231: and establishing an instance corresponding relation between the service access unified interface and the creation interface defined by the OSB API specification.
S232: and controlling the OSB plug-in to operate the third-party service according to the corresponding relation of the examples. The operation method comprises the steps of carrying out data interaction, information display and the like with the third party service.
Specifically, as shown in the OSB API specification table, the service instance of the creation interface defined by the OSB API specification corresponds to the instance of the service access unified interface, so that the specific third party service can be operated according to the corresponding relationship with the instance of the creation interface defined by the OSB API specification by using the service access unified interface, and the processing of different types of third party services can be realized by adopting the above manner.
In addition, based on the same concept of the above method embodiment, the embodiment of the present invention further provides a third party service access system based on OSB API specification, for implementing the above method of the present invention, and because the principle of solving the problem of the system embodiment is similar to that of the above method, the system embodiment at least has all the beneficial effects brought by the technical solution of the above embodiment, which is not described herein in detail.
Referring to fig. 7, fig. 7 is a schematic structural diagram of a third party service access system based on OSB API specification according to an embodiment of the present invention, as shown in fig. 7, the third party service access system includes:
a plug-in creation module 110, configured to add an OSB plug-in the SaaS platform;
the service access module 120 is configured to access a third party service according to OSB API specification using OSB plugins.
In the third party service access system based on OSB API specification, OSB plug-in is added to the SaaS platform through the plug-in creation module 110, and then the service access module 120 uses the OSB plug-in to access the third party service according to OSB API specification. The OSB API is known as Open Service Broker API, which is an open service proxy API, through which independent software vendors, saaS providers, and developers can integrate and run their services onto SaaS platforms, such as cloud computing platforms and Kubernetes platforms, with great convenience. Such API specifications have been adopted by more and more platforms or service providers. Service items such as generating service, accessing service, managing service and the like can be realized through a group of API endpoints. The SaaS platform realizes the OSB plug-in of the service agent access, the third party service provider realizes the own service agent according to the OSB API specification, and the SaaS platform can conveniently access the third party service, such as kubernetes cluster service, big data cluster service and the like, by accessing the service agent of the corresponding manufacturer through the plug-in.
As a preferred embodiment, as shown in fig. 8, the service access module 120 includes:
a connection establishment sub-module 121, configured to create a service agent in the SaaS platform, and establish a connection between the service agent and the OSB plug-in;
the service access sub-module 122 is configured to access the third party service by using a corresponding service agent in the SaaS platform according to the service type of the third party service;
and the plug-in access submodule 123 is used for accessing the third party service into the OSB plug-in through the connection between the service agent and the OSB plug-in.
As a preferred embodiment, as shown in fig. 9, the service access module 120 includes:
an address acquisition sub-module 124, configured to acquire a service address of the service agent using the OSB plugin;
an address splicing sub-module 125, configured to control the OSB plug-in to splice the service address according to the OSB API specification, to obtain a URL;
the platform access sub-module 126 is configured to control the OSB plug-in to access the third party service of the service agent to the SaaS platform through the URL.
As a preferred embodiment, as shown in fig. 10, the third party service access system further includes:
the interface creation module 210 is configured to add a service access unified interface to a software development tool layer of the SaaS platform according to a front end requirement of the SaaS platform, where the service access unified interface includes a service instance;
an interface inheritance module 220, configured to use OSB plugin inheritance services to access a unified interface;
the service processing module 230 is configured to control the OSB plug-in to process the third party service by using the service instance of the service access unified interface when accessing the third party service.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It should be noted that in the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, third, etc. do not denote any order. These words may be interpreted as names.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.
Claims (6)
1. A third party service access method based on OSB API specification, comprising:
an OSB plug-in is additionally arranged in the SaaS platform;
accessing a third party service according to OSB API specifications by using the OSB plug-in;
according to the front-end requirement of the SaaS platform, a service access unified interface is additionally arranged on a software development tool layer of the SaaS platform, wherein the service access unified interface comprises a service instance;
inheriting the service access unified interface by using the OSB plug-in;
when the OSB plug-in accesses the third party service, the service instance of the service access unified interface is used for processing the third party service;
the step of accessing the third party service by using the OSB plugin according to the OSB API specification comprises the following steps:
creating a service agent in the SaaS platform, and establishing connection between the service agent and the OSB plug-in;
accessing the third party service by using a corresponding service agent in the SaaS platform according to the service type of the third party service;
and accessing the third party service into the OSB plug-in through the connection of the service agent and the OSB plug-in.
2. The third party service access method according to claim 1, wherein the step of accessing the third party service according to OSB API specification using OSB plugins comprises:
acquiring a service address of the service agent by using the OSB plug-in;
controlling the OSB plug-in to splice the service address according to OSB API specifications to obtain a URL;
and controlling the OSB plug-in to access the third party service of the service agent to the SaaS platform through the URL.
3. The third party service access method according to claim 2, wherein the step of controlling the OSB plug-in to splice the service address according to OSB API specification to obtain URL includes:
controlling the OSB plug-in to acquire a creation interface address defined by OSB API specification;
and controlling the OSB plug-in to splice the creation interface address and the service address defined by the OSB API specification to obtain the URL.
4. The third party service access method according to claim 1, wherein the step of processing the third party service using service instances of a service access unified interface comprises:
establishing an instance corresponding relation between the service access unified interface and a creation interface defined by the OSB API specification;
and controlling the OSB plug-in to operate the third party service according to the corresponding relation of the examples.
5. A third party service access system based on OSB API specification, comprising:
the plug-in creation module is used for adding an OSB plug-in the SaaS platform;
the service access module is used for accessing the third party service by using the OSB plug-in according to OSB API specification;
the interface creation module is used for adding a service access unified interface to a software development tool layer of the SaaS platform according to the front-end requirement of the SaaS platform, wherein the service access unified interface comprises a service instance;
the interface inheritance module is used for inheriting the service access unified interface by using the OSB plug-in;
the service processing module is used for controlling the OSB plug-in to process the third party service by using the service instance of the service access unified interface when the OSB plug-in is accessed to the third party service;
the service access module comprises:
the connection establishment sub-module is used for establishing a service agent in the SaaS platform and establishing the connection between the service agent and the OSB plug-in;
the service access sub-module is used for accessing the third party service by using a corresponding service agent in the SaaS platform according to the service type of the third party service;
and the plug-in access submodule is used for accessing the third party service into the OSB plug-in through the connection between the service agent and the OSB plug-in.
6. The third party service access system according to claim 5, wherein the service access module comprises:
an address acquisition sub-module, configured to acquire a service address of the service agent using the OSB plug-in;
the address splicing sub-module is used for controlling the OSB plug-in to splice the service address according to the OSB API specification to obtain a URL;
and the platform access sub-module is used for controlling the OSB plug-in to access the third party service of the service agent to the SaaS platform through the URL.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110948311.0A CN113805958B (en) | 2021-08-18 | 2021-08-18 | Third party service access method and system based on OSB API specification |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110948311.0A CN113805958B (en) | 2021-08-18 | 2021-08-18 | Third party service access method and system based on OSB API specification |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113805958A CN113805958A (en) | 2021-12-17 |
| CN113805958B true CN113805958B (en) | 2023-12-22 |
Family
ID=78893766
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110948311.0A Active CN113805958B (en) | 2021-08-18 | 2021-08-18 | Third party service access method and system based on OSB API specification |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113805958B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102025765A (en) * | 2010-06-04 | 2011-04-20 | 西本新干线股份有限公司 | Service integration platform and agent management method |
| CN104700193A (en) * | 2014-11-17 | 2015-06-10 | 国家电网公司 | Cloud platform service integrated device and system |
| US10445223B1 (en) * | 2018-10-25 | 2019-10-15 | Capital One Services, Llc | Service virtualization platform |
| CN111176633A (en) * | 2020-01-15 | 2020-05-19 | 山东健康医疗大数据有限公司 | Open terminal based on modular service and third party access method thereof |
| CN112698840A (en) * | 2021-01-12 | 2021-04-23 | 江苏苏州农村商业银行股份有限公司 | Architecture system for realizing bank cloud platform service |
| CN112966833A (en) * | 2021-04-07 | 2021-06-15 | 福州大学 | Machine learning model platform based on Kubernetes cluster |
| CN113064627A (en) * | 2021-03-23 | 2021-07-02 | 支付宝(杭州)信息技术有限公司 | Service access data processing method, platform, terminal, equipment and system |
| CN113157339A (en) * | 2021-04-23 | 2021-07-23 | 东云睿连(武汉)计算技术有限公司 | Application service expansion method, system, storage medium and device based on OSB |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101132405A (en) * | 2006-08-21 | 2008-02-27 | 华为技术有限公司 | Communication network system and method for providing business proxy function and business proxy device thereof |
| US20120047568A1 (en) * | 2010-08-17 | 2012-02-23 | MyWeboo Inc. | Digital Asset Management on the Internet |
| US9189304B2 (en) * | 2011-09-09 | 2015-11-17 | Oracle International Corporation | System and method for providing a dynamic invocation and service interface for use in a middleware or other environment |
-
2021
- 2021-08-18 CN CN202110948311.0A patent/CN113805958B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102025765A (en) * | 2010-06-04 | 2011-04-20 | 西本新干线股份有限公司 | Service integration platform and agent management method |
| CN104700193A (en) * | 2014-11-17 | 2015-06-10 | 国家电网公司 | Cloud platform service integrated device and system |
| US10445223B1 (en) * | 2018-10-25 | 2019-10-15 | Capital One Services, Llc | Service virtualization platform |
| CN111176633A (en) * | 2020-01-15 | 2020-05-19 | 山东健康医疗大数据有限公司 | Open terminal based on modular service and third party access method thereof |
| CN112698840A (en) * | 2021-01-12 | 2021-04-23 | 江苏苏州农村商业银行股份有限公司 | Architecture system for realizing bank cloud platform service |
| CN113064627A (en) * | 2021-03-23 | 2021-07-02 | 支付宝(杭州)信息技术有限公司 | Service access data processing method, platform, terminal, equipment and system |
| CN112966833A (en) * | 2021-04-07 | 2021-06-15 | 福州大学 | Machine learning model platform based on Kubernetes cluster |
| CN113157339A (en) * | 2021-04-23 | 2021-07-23 | 东云睿连(武汉)计算技术有限公司 | Application service expansion method, system, storage medium and device based on OSB |
Non-Patent Citations (3)
| Title |
|---|
| 基于ESB的应用系统集成方法初探;蔡芳;;电脑知识与技术(19);238-239+248 * |
| 基于服务总线的应用集成平台设计与开发;柳吉庆;徐礼祥;张军;;智能制造(11);31-34 * |
| 基于服务集成管理的SaaS解决方案;丁文定;;计算机与现代化(01);63-66 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113805958A (en) | 2021-12-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10838769B2 (en) | Application program interface based service lookup in a service architecture | |
| US8032588B2 (en) | System and method for hosting one or more versions of a service using a service proxy | |
| US11422777B2 (en) | System and methods with reduced complexity in the integration of exposed information models with applications | |
| CN106569880B (en) | Method and system for dynamically sharing resources between Android applications | |
| CN111897539A (en) | Method and device for deploying applications according to service roles | |
| CN111399840B (en) | Module development method and device | |
| CN110221840B (en) | Function implementation method and device of application program, equipment and storage medium | |
| CN109343970B (en) | Application program-based operation method and device, electronic equipment and computer medium | |
| CN112506681B (en) | Parameter calling method and device, electronic equipment and storage medium | |
| CN113448570A (en) | Data processing method and device, electronic equipment and storage medium | |
| US20170237687A1 (en) | Resource trees by management controller | |
| CN116233217B (en) | Page jump method and device based on route, electronic equipment and storage medium | |
| CN113805958B (en) | Third party service access method and system based on OSB API specification | |
| US11071151B2 (en) | Methods and apparatuses for connecting a wireless access point through an application in a user equipment | |
| CN116755788A (en) | On-line rule modification method, device, equipment and storage medium | |
| CN113612643B (en) | Network configuration method, device and equipment of cloud mobile phone and storage medium | |
| CN109918147B (en) | Expansion method and device for drive under OpenStack and electronic equipment | |
| CN109669679B (en) | Service detection and processing method and device and electronic equipment | |
| CN115857878A (en) | Development framework generation method and application method | |
| CN114090127A (en) | Electronic device, loading method and medium of configuration file of electronic device | |
| CN113709171A (en) | Method and device for cross-component state communication | |
| US10402454B1 (en) | Obtaining platform-specific information in a firmware execution environment | |
| CN110780864A (en) | Control method and device for class method replacement, storage medium and electronic equipment | |
| CN113626007B (en) | Application method and device of connector model and server | |
| US10884832B2 (en) | Aggregation messaging within an integration environment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |