CN113805958A - 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 specificationDownload PDFInfo
- Publication number
- CN113805958A CN113805958ACN202110948311.0ACN202110948311ACN113805958ACN 113805958 ACN113805958 ACN 113805958ACN 202110948311 ACN202110948311 ACN 202110948311ACN 113805958 ACN113805958 ACN 113805958A
- Authority
- CN
- China
- Prior art keywords
- service
- osb
- plug
- party service
- 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.)
- Granted
Links
Images
Classifications
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
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 specification.
Background
SaaS (Software-as-a-Service) is a way of providing Software services through a network, and as a SaaS layer provider-SaaS platform, it is capable of providing various types of services including a Service package, an offline Service, and a third party Service.
In the aspect of service implementation, the SaaS platform develops corresponding plug-ins for different types of services by abstracting various operations of a Software Development Kit (SDK) layer encapsulated service instance, and the plug-ins carry out the operations of the service instance by inheriting an interface of the SDK layer. In the service operation process, the adaptation layer of the SaaS platform calls the corresponding plug-in layer according to different service types. For a third-party service, a third-party service plug-in needs to be set, and in the third-party service plug-in, the third-party service is accessed according to the logic of each service provider. Such as: newly increasing data cluster service requires newly increasing data implementation class and calling an interface of a big data service provider; if the kubernets cluster service is newly added, an implementation class for realizing the kubernets needs to be newly added, and an interface of a kubernets service provider is called.
The access of the third-party service can be realized by expanding the third-party plug-in realization logic, and the mode has high expansibility, however, when the third-party service is newly added, the mode needs to correspondingly modify the code of the SaaS platform plug-in layer so as to adapt to the interfaces of different service providers again. This not only results in reduced interface access flexibility, but also reduces the scalability of the plug-in layer.
Disclosure of Invention
The invention provides a third-party service access method and a third-party service access system based on OSB API specification, and aims to solve the problems that in the prior art, due to a third-party service access mode, the interface access flexibility is reduced and the expandability of a plug-in layer is reduced because the plug-in layer codes of a cloud platform need to be correspondingly modified every time a third-party service is newly added.
According to a first aspect of the present invention, the present invention provides a third party service access method based on OSB API specification, including:
adding an OSB plug-in the SaaS platform;
and accessing the third-party service by using the OSB plug-in according to the OSB API specification.
Preferably, the step of accessing the third party service by using the OSB plug-in according to the OSB API specification includes:
establishing a service agent in the SaaS platform, and establishing the connection between the service agent and the OSB plug-in;
according to the service type of the third-party service, accessing the third-party service by using a corresponding service agent in the SaaS platform;
and accessing the third-party service to the OSB plug-in through the connection of the service agent and the OSB plug-in.
Preferably, the step of accessing the third party service by using the OSB plug-in according to the OSB API specification includes:
using an OSB plug-in to obtain a service address of a service agent;
controlling the OSB plug-in to splice the service address according to the OSB API specification 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 plug-in to splice the service address according to the OSB API specification to obtain the URL includes:
controlling an OSB plug-in to obtain a creation interface address defined by an 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 the OSB plug-in to inherit the service to access the uniform interface;
and when the OSB plug-in is accessed to the third-party service, the service instance of the service access 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 created interface defined by OSB API specification;
and controlling the OSB plug-in to operate the third-party service according to the corresponding relation of the instances.
According to a second aspect of the present invention, the present invention further provides a third party service access system based on OSB API specification, including:
the plug-in creating module is used for additionally arranging 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 comprises:
the connection establishing 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 sub-module is used for accessing the third-party service to the OSB plug-in through the connection of the service agent and the OSB plug-in.
Preferably, the service access module comprises:
the address acquisition submodule is used for acquiring the service address of the service agent by using the OSB plug-in;
the address splicing submodule 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 submodule 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 includes:
the software development system comprises an interface creation module, a service access unified interface and a service access module, wherein the interface creation module is used for additionally arranging the service access unified interface on a software development tool layer of the SaaS platform according to the front-end requirement of the SaaS platform, and 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;
and the service processing module is used for controlling the OSB plug-in to use the service instance of the service access unified interface to process the third-party service 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 called an Open Service Broker API, that is, an Open Service agent API, through which independent software vendors, SaaS providers and developers can integrate and run their services on SaaS platforms, such as cloud computing platforms and kubernets platforms, very conveniently. Such API specifications have been adopted by an increasing number of platforms or service providers. Service items such as generating services, accessing services and managing services can be realized through a group of API endpoints. The SaaS platform realizes the OSB plug-in of service agent access, a third-party service provider realizes the service agent of the third-party service provider according to the OSB API specification, and the SaaS platform can conveniently access the third-party service such as kubernets cluster service, big data cluster service and the like by accessing the service agent of a 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 used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the structures shown in the drawings without creative efforts.
FIG. 1 is a schematic structural diagram of an OSB API service architecture according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a first third-party service access method based on OSB API specification according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of a first third-party service access method provided by the embodiment shown in fig. 2;
fig. 4 is a flowchart illustrating a second third-party service access method provided by the embodiment shown in fig. 2;
fig. 5 is a flowchart illustrating a second third-party service access method based on OSB API specification according to an embodiment of the present invention;
FIG. 6 is a flow chart illustrating a third-party service processing method provided by 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 specification according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a first service access module provided in the embodiment shown in fig. 7;
fig. 9 is a schematic structural diagram of a second service access module provided in the embodiment shown in 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 implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The main technical problems of the embodiment of the invention are as follows:
in the aspect of service implementation, the SaaS platform encapsulates various operations of service instances through the SDK layer, develops corresponding plug-ins for different types of services, and the plug-ins perform the operations of the service instances by inheriting the interfaces of the SDK layer. And the adaptation layer of the SaaS platform calls the realization of the corresponding plug-in layer according to different service types. For a third-party service, a third-party service plug-in needs to be set, and in the third-party service plug-in, the third-party service is accessed 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, in this way, when a third-party service is newly added, the code of the SaaS platform plug-in layer needs to be modified correspondingly, and a third-party plug-in is accessed to adapt to interfaces of different service providers again. This not only results in reduced interface access flexibility, but also reduces the scalability of the plug-in layer.
In order to solve the above problem, referring to fig. 1 specifically, in a technical solution provided by the following embodiments of the present application, the present application provides an OSB API service architecture. In the service architecture, an OSB plug-in 105 is added to a plug-inlayer 109 in aservice factory 100 of the SaaS platform, the OSB plug-in 105 can implement an OSB API specification, and different service agents, such as thebig data agent 106 and thek8s agent 107 in fig. 1, can be accessed through the OSB plug-in 105, so that a variety of third party services can be accessed without the corresponding service plug-in. In addition, theservice factory 100 further includes anAPI server 101, adirectory service 102, aservice adapter 103 provided in a service unifiedaccess layer 108, and an SDK definition service unified interface.
Referring to fig. 2 in particular, fig. 2 is a schematic flowchart 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 the OSB API specification includes:
s110: and adding an OSB plug-in the SaaS platform. The OSB plug-in can realize OSB API specification and inherit a related interface in the SaaS platform, so that the access of third-party service is realized.
S120: and accessing the third-party service by using the OSB plug-in according to the OSB API specification. The format of the OSB API specification is shown in the following table, and includes interface addresses of various interfaces, and the functions of the OSB API specification include creating a service instance, deleting the service instance, querying details of the service instance, expanding the service instance, and mailing to obtain service information (name, description, and specification).
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 called an Open Service Broker API, that is, an Open Service agent API, through which independent software vendors, SaaS providers and developers can integrate and run their services on SaaS platforms, such as cloud computing platforms and kubernets platforms, very conveniently. Such API specifications have been adopted by an increasing number of platforms or service providers. Service items such as generating services, accessing services and managing services can be realized through a group of API endpoints. The SaaS platform realizes the OSB plug-in of service agent access, a third-party service provider realizes the service agent of the third-party service provider according to the OSB API specification, and the SaaS platform can conveniently access the third-party service such as kubernets cluster service, big data cluster service and the like by accessing the service agent of a corresponding manufacturer through the plug-in.
As a preferred embodiment, as shown in fig. 3, the step S120: the step of using the OSB plug-in to access the third party service according to the OSB API specification comprises the following steps:
s121: and establishing a service agent in the SaaS platform, and establishing the connection between the service agent and the OSB plug-in. According to the method and the device, the service agents such as the big data agent and the k8s agent are created in the SaaS platform, and the service agents can establish connection with the OSB plug-in, so that the SaaS platform can access different third-party services, and the different third-party services can be accessed and managed uniformly through the OSB plug-in.
S122: and according to the service type of the third-party service, accessing the third-party service by using a corresponding service agent in the SaaS platform. The service types of the third-party services comprise big data services, artificial intelligence services, k8s services and the like, corresponding service agents are provided in the SaaS platform, and different services are respectively accessed, so that different service agents can transmit different services to the OSB plug-in.
S123: and accessing the third-party service to the OSB plug-in through the connection of the service agent and the OSB plug-in.
In the embodiment of the application, all service agents are connected with the OSB plug-in, so that different third-party services can be accessed into the SaaS platform only by using one type of plug-in of the OSB plug-in the SaaS platform.
As a preferred embodiment, as shown in fig. 4, the step S120: the step of using the OSB plug-in to access the third party service according to the OSB API specification comprises the following steps:
s124: the service address of the service agent is obtained using the OSB plug-in. The service address of the service agent is obtained by using the OSB plug-in, then the connection between the OSB plug-in and the service agent can be established by using the service address, and when the service agent obtains the related 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 creation interface address defined by the OSB API specification so that the OSB plug-in can connect different service agents through the URL to access different third party services.
The step of obtaining the URL by splicing the service address by the control OSB plug-in according to the OSB API specification comprises the following steps: controlling an OSB plug-in to obtain a creation interface address defined by an 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 address of the ServiceBroker dedicated to the big data service is http:// bigdata-ServiceBroker: 32100; the creation interface defined by the OSB API is/v 2/service _ instances/{ instance Id }; then the complete URL address is: http:// bigdata-servicebrowser: 32100/v2/service _ instances/{ instanceId }.
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 uniform resource locator 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, in addition to the above steps:
s210: 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. According to the front-end requirement of the SaaS platform, a service access unified interface is additionally arranged on an SDK layer of the SaaS platform, an OSB plug-in can be controlled to realize the function of the interface according to the user requirement, and external third-party services are further accessed and processed through the interface.
S220: the OSB plug-in is used to inherit the service access unified interface.
S230: and when the OSB plug-in is accessed to the third-party service, the service instance of the service access 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 third-party service can be processed according to the service examples contained in various interface methods defined by a user by using the service access unified interface.
As a preferred embodiment, as shown in fig. 6, the step of processing the third-party service by using the service instance of the service access unified interface includes:
s231: and establishing an instance corresponding relation between the service access unified interface and a creating 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 instances. The operation method comprises the steps of carrying out data interaction, information display and the like with a 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 correspondence relationship between the service access unified interface and the instance of the creation interface defined by the OSB API specification, and processing of different types of third-party services can be realized by the above manner.
In addition, based on the same concept of the embodiment of the method, the embodiment of the present invention further provides a third party service access system based on the OSB API specification, for implementing the method of the present invention, because the principle of solving the problem of the embodiment of the system is similar to that of the method, the embodiment of the present invention at least has all the beneficial effects brought by the technical solution of the embodiment, and details are not repeated herein.
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, and as shown in fig. 7, the third-party service access system includes:
the plug-in creatingmodule 110 is used for adding an OSB plug-in the SaaS platform;
and theservice access module 120 is configured to access a third-party service according to the OSB API specification by using an OSB plug-in.
In the third-party service access system based on the OSB API specification, the OSB plug-in is added to the SaaS platform through the plug-increation module 110, and then theservice access module 120 accesses the third-party service using the OSB plug-in according to the OSB API specification. The OSB API is called an Open Service Broker API, that is, an Open Service agent API, through which independent software vendors, SaaS providers and developers can integrate and run their services on SaaS platforms, such as cloud computing platforms and kubernets platforms, very conveniently. Such API specifications have been adopted by an increasing number of platforms or service providers. Service items such as generating services, accessing services and managing services can be realized through a group of API endpoints. The SaaS platform realizes the OSB plug-in of service agent access, a third-party service provider realizes the service agent of the third-party service provider according to the OSB API specification, and the SaaS platform can conveniently access the third-party service such as kubernets cluster service, big data cluster service and the like by accessing the service agent of a corresponding manufacturer through the plug-in.
As a preferred embodiment, as shown in fig. 8, theservice access module 120 includes:
the connection establishing sub-module 121 is configured to establish 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 a third-party service by using a corresponding service agent in the SaaS platform according to a service type of the third-party service;
and the plug-in access sub-module 123 is configured to access the third-party service to 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, theservice access module 120 includes:
anaddress obtaining submodule 124 for obtaining a service address of the service agent by using the OSB plug-in;
theaddress splicing submodule 125 is used for controlling the OSB plug-in to splice the service addresses according to the OSB API specification to obtain the URL;
and the platform access sub-module 126 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.
As a preferred embodiment, as shown in fig. 10, the third-party service access system further includes:
theinterface creating module 210 is configured to add a service access unified interface on 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;
aninterface inheritance module 220 for inheriting the service access unified interface using the OSB plug-in;
and theservice 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.
As will be appreciated by one skilled in the art, 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 flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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 usage of the words first, second and third, etcetera do not indicate any ordering. 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. Therefore, it is intended that the appended claims be interpreted as including 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 changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (10)
1. A third party service access method based on OSB API specification is characterized by comprising the following steps:
adding an OSB plug-in the SaaS platform;
and accessing the third-party service by using the OSB plug-in according to the OSB API specification.
2. The third party service access method of claim 1, wherein the step of using an OSB plug-in to access the third party service according to the OSB API specification comprises:
establishing a service agent in the SaaS platform, and establishing the connection between the service agent and the OSB plug-in;
according to the service type of the third-party service, accessing the third-party service by using a corresponding service agent in the SaaS platform;
and accessing the third-party service to the OSB plug-in through the connection between the service agent and the OSB plug-in.
3. The third party service access method of claim 2, wherein the step of using an OSB plug-in to access the third party service according to the OSB API specification comprises:
using the OSB plug-in to obtain a service address of the service agent;
controlling the OSB plug-in to splice the service address according to OSB API specification to obtain URL;
and controlling the OSB plug-in to access the third-party service of the service agent to the SaaS platform through the URL.
4. The third-party service access method according to claim 3, 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 defined by the OSB API specification and the service address to obtain the URL.
5. The third-party service access method of claim 1, further comprising:
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;
and when the OSB plug-in is accessed to the third-party service, the service instance of the service access unified interface is used for processing the third-party service.
6. The third-party service access method of claim 5, wherein the step of processing the third-party service using the service instance of the service access unified interface comprises:
establishing an instance corresponding relation between the service access unified interface and a created 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 instances.
7. A third party service access system based on OSB API specification, comprising:
the plug-in creating module is used for additionally arranging 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.
8. The third party service access system of claim 7, wherein the service access module comprises:
the connection establishing 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 sub-module is used for accessing the third-party service to the OSB plug-in through the connection between the service agent and the OSB plug-in.
9. The third party service access system of claim 8, wherein the service access module comprises:
the address acquisition submodule is used for acquiring the service address of the service agent by using the OSB plug-in;
the address splicing submodule is used for controlling the OSB plug-in to splice the service address according to OSB API specification to obtain URL;
and the platform access submodule 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.
10. The third party service access system of claim 7, further comprising:
the software development system comprises an interface creation module, a service access unified interface and a service access unified interface, wherein the interface creation module is used for additionally arranging the service access unified interface on a software development tool layer of the SaaS platform according to the front-end requirement of the SaaS platform, and 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;
and the service processing module is used for controlling the OSB plug-in to use the service instance of the service access unified interface to process the third-party service when accessing the third-party service.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110948311.0ACN113805958B (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.0ACN113805958B (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 |
|---|---|
| CN113805958Atrue CN113805958A (en) | 2021-12-17 |
| CN113805958B CN113805958B (en) | 2023-12-22 |
Family
ID=78893766
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110948311.0AActiveCN113805958B (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) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116346894A (en)* | 2023-03-01 | 2023-06-27 | 浪潮软件科技有限公司 | A method to solve the problem of rapid integration of third-party middleware in the industry cloud platform |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090193131A1 (en)* | 2006-08-21 | 2009-07-30 | Huawei Technologies Co., Ltd. | Communication network system and method for providing a service broker function, and service broker apparatus |
| CN102025765A (en)* | 2010-06-04 | 2011-04-20 | 西本新干线股份有限公司 | Service integration platform and agent management method |
| US20120047568A1 (en)* | 2010-08-17 | 2012-02-23 | MyWeboo Inc. | Digital Asset Management on the Internet |
| US20130066946A1 (en)* | 2011-09-09 | 2013-03-14 | Oracle International Corporation | System and method for providing a dynamic invocation and service interface for use in a middleware or other environment |
| 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 |
- 2021
- 2021-08-18CNCN202110948311.0Apatent/CN113805958B/enactiveActive
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090193131A1 (en)* | 2006-08-21 | 2009-07-30 | Huawei Technologies Co., Ltd. | Communication network system and method for providing a service broker function, and service broker apparatus |
| CN102025765A (en)* | 2010-06-04 | 2011-04-20 | 西本新干线股份有限公司 | Service integration platform and agent management method |
| US20120047568A1 (en)* | 2010-08-17 | 2012-02-23 | MyWeboo Inc. | Digital Asset Management on the Internet |
| US20130066946A1 (en)* | 2011-09-09 | 2013-03-14 | Oracle International Corporation | System and method for providing a dynamic invocation and service interface for use in a middleware or other environment |
| 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 |
|---|
| 丁文定;: "基于服务集成管理的SaaS解决方案", 计算机与现代化, no. 01, pages 63 - 66* |
| 柳吉庆;徐礼祥;张军;: "基于服务总线的应用集成平台设计与开发", 智能制造, no. 11, pages 31 - 34* |
| 蔡芳;: "基于ESB的应用系统集成方法初探", 电脑知识与技术, no. 19, pages 238 - 239* |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116346894A (en)* | 2023-03-01 | 2023-06-27 | 浪潮软件科技有限公司 | A method to solve the problem of rapid integration of third-party middleware in the industry cloud platform |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113805958B (en) | 2023-12-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109002362B (en) | Service method, device and system and electronic equipment | |
| CN114077462B (en) | Method, device, equipment and medium for software operating system to call Android HIDL interface | |
| US20040158577A1 (en) | System and method for cross platform and configuration build system | |
| US8032588B2 (en) | System and method for hosting one or more versions of a service using a service proxy | |
| US20200167713A1 (en) | Business processing method, apparatus, device and system using the same, and readable storage medium of the same | |
| CN111399840B (en) | Module development method and device | |
| US20170048331A1 (en) | Platform runtime abstraction | |
| US10346160B2 (en) | Melding of mediation flow service component architecture (SCA) components | |
| CN115061717B (en) | Application management method, application subscription method and related equipment | |
| CN109104368B (en) | A method, device, server and computer-readable storage medium for requesting connection | |
| CN113626007A (en) | Method and device for creating and applying connector model and server | |
| CN116755788A (en) | On-line rule modification method, device, equipment and storage medium | |
| CN112612460A (en) | Interface packaging and calling method, electronic device and storage medium | |
| CN109343970B (en) | Application program-based operation method and device, electronic equipment and computer medium | |
| CN114217845B (en) | Application configuration method, device, equipment and storage medium | |
| CN113805958B (en) | Third party service access method and system based on OSB API specification | |
| CN111176641A (en) | Flow node execution method, device, medium and electronic equipment | |
| CN106982131A (en) | Initiate method, the apparatus and system of VNF instantiations | |
| WO2024002217A1 (en) | Application management method and related device | |
| CN112579212A (en) | Cross-language calling method, calling party device and called party device | |
| CN116684494A (en) | Resource processing method, device and storage medium based on distributed cloud platform | |
| CN116225403A (en) | Domain-specific language data processing method and device, computing device and storage medium | |
| CN115857878A (en) | Development framework generation method and application method | |
| CN109669679B (en) | Service detection and processing method and device and electronic equipment | |
| CN113709171A (en) | Method and device for cross-component state communication |
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 |