CN115118776A - Application access method, local connector deployment method and device - Google Patents

Application access method, local connector deployment method and device Download PDF

Info

Publication number
CN115118776A
CN115118776A CN202210720127.5A CN202210720127A CN115118776A CN 115118776 A CN115118776 A CN 115118776A CN 202210720127 A CN202210720127 A CN 202210720127A CN 115118776 A CN115118776 A CN 115118776A
Authority
CN
China
Prior art keywords
data
application
server
access request
local connector
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.)
Pending
Application number
CN202210720127.5A
Other languages
Chinese (zh)
Inventor
王登临
陶鑫
胡逸峤
赵璇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Zitiao Network Technology Co Ltd
Original Assignee
Beijing Zitiao Network Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Zitiao Network Technology Co Ltd filed Critical Beijing Zitiao Network Technology Co Ltd
Priority to CN202210720127.5A priority Critical patent/CN115118776A/en
Publication of CN115118776A publication Critical patent/CN115118776A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08Protocols for interworking; Protocol conversion

Abstract

The application discloses an application access method.A local connector can receive a first data access request from an external network, the first data access request is used for requesting to access application data of a first application program deployed in the internal network, and a data protocol adopted by the first data access request is a first general data protocol. And then, processing the first data access request to obtain a second data processing request adopting a private data protocol supported by the first application program, and further sending the second data processing request to the first application program. Therefore, according to the scheme, even if the data protocol supported by the first application program is a private data protocol, the first data access request adopting the first general data protocol from the external network can be converted into the second data access request adopting the first data protocol through the local connector, so that the application data of the first application program deployed in the internal network can be accessed through the external network.

Description

Application access method, local connector deployment method and device
Technical Field
The present application relates to the field of computer technologies, and in particular, to an application access method, a local connector deployment method, and an apparatus.
Background
In some scenarios, there may be a need to access applications running in an intranet environment in an extranet environment. For example, a user accesses an application running in an intranet environment through an integrated platform deployed on an extranet.
Therefore, a solution is urgently needed to meet the requirement of accessing the application running in the intranet environment in the extranet environment.
Disclosure of Invention
In order to solve or at least partially solve the above problems, embodiments of the present application provide an application access method, a local connector deployment method, and an apparatus.
In a first aspect, an embodiment of the present application provides an application access method, which is applied to a local connector deployed in an intranet, and the method includes:
receiving a first data access request from an external network, wherein the first data access request is used for requesting to access application data of a first application program deployed in the internal network, and the first data access request adopts a first general data protocol;
processing the first data access request to obtain a second data processing request, wherein the second data processing request adopts a private data protocol supported by the first application program;
and sending the second data processing request to the first application program.
Optionally, the receiving a first data access request from an external network includes:
receiving, by a host agent, the first data access request.
Optionally, the host agent is further configured to:
receiving a third data access request from the external network, wherein the third data access request is used for requesting to access application data of a second application program deployed in the internal network, and the third data access request adopts the second universal data protocol;
sending the third data access request to the second application program, the second application program supporting the second universal data protocol.
Optionally, the local connector runs on a server in the intranet.
Optionally, the local connector is deployed on the server in the following manner:
responding to local connector deployment operation triggered by a user in a first page corresponding to a host agent running on the server, and automatically acquiring an installation file corresponding to the local connector, wherein the local connector is used for converting a message adopting a first general data protocol into a message adopting a private data protocol and converting the message adopting the private protocol into a message adopting the first general data protocol;
automatically installing the local connector onto the server using the installation file.
Optionally, the host agent is deployed on the server in the following manner:
responding to host agent creating operation triggered by a user on a second page displayed by the server, and acquiring an installation script for installing the host agent;
installing the host agent onto the server based on the installation script.
Optionally, the receiving a first data access request from an external network includes:
and receiving a first data access request sent by a server corresponding to an integration platform deployed in an external network, wherein the first data access request is generated by the server in response to an operation of accessing application data of a first application deployed in the internal network, which is triggered by a user on the integration platform.
Optionally, the method further includes:
receiving a first response message for the second data access request sent by the first application, the first response message being the private data protocol;
processing the first response message to obtain a second response message, wherein the second response message requests to adopt the first universal data protocol;
and sending the second response message to the server.
Optionally, the second response message is a desensitized message.
In a second aspect, an embodiment of the present application provides a method for deploying a local connector, where the method includes:
responding to local connector deployment operation triggered by a user in a first page corresponding to a host agent running on a server, and automatically acquiring an installation file corresponding to a local connector, wherein the local connector is used for converting a message adopting a first general data protocol into a message adopting a private data protocol and converting the message adopting the private protocol into a message adopting the first general data protocol;
automatically installing the local connector onto the server using the installation file.
Optionally, the host agent is deployed on the server in the following manner:
responding to host agent creating operation triggered by a user on a second page displayed by the server, and acquiring an installation script for installing the host agent;
installing the host agent onto the server based on the installation script.
Optionally, the server is deployed in an intranet.
In a third aspect, an embodiment of the present application provides an application access apparatus, which is applied to a local connector deployed in an intranet, where the apparatus includes:
a first receiving unit, configured to receive a first data access request from an external network, where the first data access request is used to request access to application data of a first application deployed in the internal network, and the first data access request employs a first general data protocol;
a first processing unit, configured to process the first data access request to obtain a second data processing request, where the second data processing request uses a private data protocol supported by the first application;
and the first sending unit is used for sending the second data processing request to the first application program.
Optionally, the first receiving unit is configured to:
receiving, by a host agent, the first data access request.
Optionally, the host agent is further configured to:
receiving a third data access request from the external network, wherein the third data access request is used for requesting to access application data of a second application program deployed in the internal network, and the third data access request adopts the second universal data protocol;
sending the third data access request to the second application program, the second application program supporting the second universal data protocol.
Optionally, the local connector runs on a server in the intranet.
Optionally, the local connector is deployed on the server in the following manner:
responding to local connector deployment operation triggered by a user in a first page corresponding to a host agent running on the server, and automatically acquiring an installation file corresponding to the local connector, wherein the local connector is used for converting a message adopting a first general data protocol into a message adopting a private data protocol and converting the message adopting the private protocol into a message adopting the first general data protocol;
automatically installing the local connector onto the server using the installation file.
Optionally, the host agent is deployed on the server in the following manner:
responding to host agent creating operation triggered by a user on a second page displayed by the server, and acquiring an installation script for installing the host agent;
installing the host agent onto the server based on the installation script.
Optionally, the first receiving unit is configured to:
and receiving a first data access request sent by a server corresponding to an integration platform deployed in an external network, wherein the first data access request is generated by the server in response to an operation of accessing application data of a first application deployed in the internal network, which is triggered by a user on the integration platform.
Optionally, the apparatus further comprises:
a second receiving unit, configured to receive a first response message for the second data access request sent by the first application, where the first response message is the private data protocol;
a second processing unit, configured to process the first response message to obtain a second response message, where the second response message requests to use the first generic data protocol;
and the second sending unit is used for sending the second response message to the server.
Optionally, the second response message is a desensitized message.
In a fourth aspect, an embodiment of the present application provides a deployment apparatus for a local connector, where the deployment apparatus includes:
an obtaining unit, configured to automatically obtain an installation file corresponding to a local connector in response to a local connector deployment operation triggered in a first page corresponding to a host agent running on a server by a user, where the local connector is configured to convert a packet using a first general data protocol into a packet using a private data protocol, and to convert a packet using the private protocol into a packet using the first general data protocol;
and the installation unit is used for automatically installing the local connector to the server by using the installation file.
Optionally, the host agent is deployed on the server in the following manner:
responding to host agent creating operation triggered by a user on a second page displayed by the server, and acquiring an installation script for installing the host agent;
installing the host agent onto the server based on the installation script.
Optionally, the server is deployed in an intranet.
In a fifth aspect, an embodiment of the present application provides an apparatus, which includes a processor and a memory;
the processor is configured to execute instructions stored in the memory to cause the apparatus to perform the method of any of the above first aspects or to cause the apparatus to perform the method of any of the above second aspects.
In a sixth aspect, embodiments of the present application provide a computer-readable storage medium, including instructions that instruct a device to perform the method of any one of the above first aspects, or instruct a device to perform the method of any one of the above second aspects.
In a seventh aspect, the present application provides a computer program product, which when run on a computer causes the computer to execute the method of any one of the above first aspects, or causes the computer to execute the method of any one of the above second aspects.
Compared with the prior art, the embodiment of the application has the following advantages:
the embodiment of the application provides an application access method which can be applied to a local connector deployed in an intranet. In one example, the local connector may receive a first data access request from the external network, where the first data access request is for requesting access to application data of a first application program deployed in the internal network, and a data protocol adopted by the first data access request is a first general data protocol. After receiving the first data access request, the local connector may process the first data access request to obtain a second data processing request using a private data protocol supported by the first application, and further send the second data processing request to the first application. Therefore, according to the scheme, even if the data protocol supported by the first application program is a private data protocol, the first data access request adopting the first general data protocol from the external network can be converted into the second data access request adopting the first data protocol through the local connector, so that the application data of the first application program deployed in the internal network can be accessed through the external network.
The embodiment of the application also provides a deployment method of the local connector, wherein the local connector is used for converting the message adopting the first general data protocol into the message adopting the private data protocol. The method may be applied to a host agent, for example. In one example, the host agent may run on a server deployed on an intranet. The user can trigger a local connector deployment operation in a first page corresponding to the host agent, and correspondingly, the host agent can respond to the local connector deployment operation, automatically acquire an installation file corresponding to the local connector, and automatically install the local connector on the server by using the installation file. Therefore, by the aid of the scheme, a user does not need to execute a series of operations of downloading the installation file, decompressing the installation file, inputting installation configuration information and the like, the user only needs to trigger the local connector deployment operation, the host computer agent can automatically install the local connector on the server, user operation is simplified, and user experience is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be 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 described in the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a schematic flowchart of an application access method according to an embodiment of the present application;
fig. 2 is an architecture diagram of an application access system according to an embodiment of the present application;
fig. 3 is a schematic flowchart of a deployment method of a local connector according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an application access device according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a deployment apparatus for a local connector according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions of the present application better understood, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Through research, the inventor of the application finds that in some scenarios, a user can access an application running in an intranet through an integration platform deployed in the extranet. For example, a user queries application data of an application running in an intranet environment through an integration platform deployed in an extranet.
With regard to the integrated platform, it should be noted that:
the integration platform is formed by combining the integration of an application system and an integration framework, and the problems of high integration cost and low efficiency of an enterprise are solved through lower construction cost and higher integration capability. In this embodiment, the integration platform may integrate a plurality of systems corresponding to an enterprise, and provide a unified operation entry, so that a user may complete a corresponding operation through the operation entry without entering each system for operation, thereby improving the service processing efficiency.
In an example, the unified operation entry may be an operation entry for accessing an application program in an intranet, and a user may trigger a corresponding operation through the operation entry, so as to access the application program in the intranet. By way of example:
the web page corresponding to the integration platform may include an access entry for accessing an application a in an intranet, and a user may trigger an operation for accessing the application a through the access entry, and accordingly, after the user triggers an operation for accessing the application a, the integration platform may display an associated page of the application a, and the user may input information (for example, a keyword) of data that specifically needs to be accessed in the associated page, and after the user inputs the information and triggers a determination operation for the information, a server corresponding to the integration platform may generate a corresponding data access request based on the information input by the user, and send the data access request to the application a.
Currently, integrated platforms support a common data protocol. In one example, after a user triggers an operation on the integration platform to access a certain application (e.g., application a) deployed on the intranet, the integration platform may generate a data access request using a generic data protocol. The application program deployed in the intranet may be developed by using a private data protocol or may be developed by using a general data protocol. If the application program A is developed by adopting a private data protocol, the protocol supported by the application program A is the private data protocol. Therefore, for this case, even if the application a receives the data access request using the generic data protocol, the data access request cannot be correctly parsed, and accordingly, the access to the application a fails. In the embodiments of the present application, an "application program" may also be referred to as an "application", and the two may be used alternately.
In this embodiment, the intranet may be a local area network of an enterprise. The outer network may be a network other than an inner network, and in one example, the outer network may be a public network.
In order to solve the foregoing problem, an application access method is provided in an embodiment of the present application, and the method may be applied to a local connector deployed in an intranet.
Various non-limiting embodiments of the present application are described in detail below with reference to the accompanying drawings.
Exemplary method
Referring to fig. 1, the figure is a schematic flowchart of an application access method provided in an embodiment of the present application. The method shown in fig. 1 may be applied to a local connector deployed in an intranet, where the local connector mentioned herein may be an application program. In one example, the local connector may run on a server of the intranet.
In this embodiment, the method shown in fig. 1 may include the following steps, for example: S101-S103.
S101: receiving a first data access request from an external network, wherein the first data access request is used for requesting to access application data of a first application program deployed in the internal network, and the first data access request adopts a first general data protocol.
In this embodiment of the application, for example, a user may trigger an operation for accessing the first application on an integration platform deployed in an extranet, and accordingly, a server corresponding to the integration platform may generate the first data access request in response to the operation, and send the first data access request to the local connector. In other words, in one example, the local connector may receive the first data access request sent by a server corresponding to the integration platform.
The first application program is not particularly limited in the embodiments of the present application, and the first application program may be an application program for managing and/or storing corresponding data. For example, the first application may be an Office Automation (OA) related application.
The first generic data protocol is not specifically limited in the embodiments of the present application, and the first generic data protocol may be a generic protocol adopted in developing the first application.
In one example, the local connector may receive the first data access request directly. In yet another example, the local connector may receive the first data access request through another application. For example, the local connector may receive the first data access request through a host agent, in other words, the first data access request is received by the host agent first and then sent to the local connector by the host agent.
In one example, the host agent may be deployed on a server in an intranet.
S102: and processing the first data access request to obtain a second data processing request, wherein the second data processing request adopts a private data protocol supported by the first application program.
S103: and sending the second data processing request to the first application program.
After receiving the first data access request, the local connector may process the first data access request, and convert the first data access request into a second data access request using a private data protocol supported by the first application. For example. The local connector may obtain valid information in the first data access request, and then encapsulate the valid information using the private data protocol, thereby obtaining the second data access request.
After obtaining the second data processing request, the local connector may send the second data processing request to the first application. Because the second data processing request adopts the private data protocol supported by the first application program, the first application program can analyze the second data processing request, and accordingly, the application data of the first application program deployed in the intranet can be accessed through the extranet.
The private data protocol is not specifically limited in the embodiments of the present application, and the private data protocol may be any data protocol different from the first general data protocol.
In one example, after the first application parses the second data access request, a first response message for the second data access request may be generated, where the first response message employs the aforementioned private data protocol. Correspondingly, the first application program may send the first response message to the local connector, and the local connector obtains a second response message using the first generic data protocol according to the first response message and sends the second response message to the external network. In an example, if the first data access request is sent to the local connector by a server corresponding to an integration platform deployed in an external network, the local connector may send the second response message to the server, and accordingly, the server may display valid data included in the second response message.
In this embodiment, the local connector may send the second response message to the server through the host agent, for example.
In an example, when the local connector obtains the second response message according to the first response message, in a specific implementation, the local connector may obtain the valid information in the first response message, and then encapsulate the valid information in the first response message by using the first generic data protocol, so as to obtain the second response message.
In one example, considering that the first response message may include information that needs to be kept secret, for this case, the second response message may be a desensitized message, and in this way, the desensitized message may be desensitized in the intranet, so as to avoid the foregoing information that needs to be kept secret from leaking into the extranet environment. In an example, the local connector may perform desensitization processing on the valid information in the first response message to obtain valid information after desensitization processing, and further encapsulate the desensitized valid information by using the first generic data protocol to obtain the second response message.
In one example, in addition to forwarding the first data access request, the host agent may also enable the user to access an application supporting a universal data protocol in the intranet through the host agent. In one example, a user may access a second application supporting a second universal data protocol in the intranet through the host agent. As an example, the host agent may receive a third data access request from the extranet, the third data access request requesting access to application data of a second application deployed within the intranet, the third data access request employing the second universal data protocol. After receiving the third data access request, the host agent may send the third data access request directly to the second application. Since the second application program supports the second universal data protocol, the second application program can analyze the third data processing request, and accordingly, access to the application data of the second application program deployed in the intranet through the extranet is achieved.
The second application program is not particularly limited in the embodiments of the present application, and the second application program may be an application program for managing and/or storing corresponding data. For example, the second application may be an OA-related application.
The second universal data protocol is not specifically limited in the embodiment of the present application, and the second universal data protocol may be a universal protocol used for developing the second application program.
As can be seen, in the embodiment of the present application, by means of the "host agent + local connector", it is possible to implement both an application supporting a general data protocol (for example, the second application) and an application supporting a private data protocol (for example, the first application) through an external network. For this case, in one example, whether the data protocol supported by the application deployed in the intranet is a generic data protocol or a proprietary data protocol, the user may trigger an operation of accessing the application on the integrated platform, so as to realize access to the application deployed in the intranet.
Next, the scheme provided by the embodiment of the present application will be briefly described with reference to the architecture diagram shown in fig. 2. Referring to fig. 2, fig. 2 is an architecture diagram of an application access system according to an embodiment of the present application.
In one example, an access portal for a first application 301 accessing the intranet and an access portal for a second application 302 accessing the intranet may be included in the integrated platform. Correspondingly, the server 200 deployed in the extranet and corresponding to the integration platform may include a data processing module 201 corresponding to the first application 301 and a data processing module 202 corresponding to the second application 301.
The data processing module 201 is configured to process data related to a first application, and the data processing module 202 is configured to process data related to a second application. In one example, the data processing module 201 may generate, for example, the aforementioned first data access request, and the data processing module 202 may generate the aforementioned third data access request.
Wherein:
the data processing module 201 and the first application 301 can communicate through a host agent 310 deployed in the intranet and a local connector 320 corresponding to the first application.
The data processing module 202 and the second application 302 may communicate through the host agent 310.
It should be noted that fig. 2 is only shown for convenience of understanding the scheme provided by the embodiment of the present application, and does not limit the embodiment of the present application. For example, a local connector corresponding to a third application supporting a private data protocol may also be deployed in the intranet 300, and the server 200 corresponding to the integrated platform may also include a data processing module corresponding to the third application, and the data processing module corresponding to the third application and the third application may communicate through the host agent 310 and the local connector corresponding to the third application. For another example, the server 200 corresponding to the integrated platform may further communicate with a fourth application program supporting a third general data protocol in the intranet through the host agent 310.
As described above, the local connector may be operated on a server of an intranet, and at present, if the local connector is to be installed on the server, a user needs to perform a series of operations, which is cumbersome for the user. For example: the user first downloads the installation file corresponding to the local connector, further decompresses the installation file, and then needs to perform a series of operations such as selecting an installation path, inputting installation configuration information, and the like. In order to simplify a user operation of installing the local connector on the server, an embodiment of the present application provides a deployment method of a local connector. Next, the method will be described with reference to fig. 3.
Fig. 3 is a schematic flowchart of a deployment method of a local connector according to an embodiment of the present application. The method shown in fig. 3, which may be performed by a host agent, may include, for example, the following S201-S202.
S201: and responding to local connector deployment operation triggered by a user in a first page corresponding to a host agent running on the server, and automatically acquiring an installation file corresponding to the local connector, wherein the local connector is used for converting a message adopting a first general data protocol into a message adopting a private data protocol and converting the message adopting the private protocol into a message adopting the first general data protocol.
In this embodiment, the first page may include a first control for triggering creation of the local connector, for example, and the user may trigger the local connector deployment operation through the first control. For example, the user may click on the first control, thereby triggering the local connector deployment operation.
Regarding the local connector deployment operation triggered by the user in the first page, it should be noted that, in an example, the host agent may be configured to quickly deploy local connectors corresponding to a plurality of applications, and for this case, the local connector deployment operation may include two operations, a first operation may be an operation of selecting a local connector corresponding to the first application, and a second operation may be an operation of confirming deployment of the selected local connector. That is, in one example, the user may first trigger an operation of selecting a local connector corresponding to the first application in the first page, and further trigger a deployment operation based on the selected local connector.
In one example, the first page may include a list of local connectors corresponding to a plurality of applications, and the user may trigger an operation of selecting a local connector corresponding to the first application from the list. Wherein the list may be presented in a drop down menu.
After the user triggers the local connector deployment operation, the host agent may automatically acquire an installation file corresponding to the local connector corresponding to the first application program in response to the local connector deployment operation. In one example, the host agent may pre-store an installation file download address corresponding to a local connector corresponding to the first application, and further download the installation file through the download address.
S202: automatically installing the local connector onto the server using the installation file.
After the host agent obtains the installation file, the local connector may be automatically installed on the server using the installation file. For example, the host agent may automatically decompress the installation file, automatically select an installation path, and automatically input installation configuration information, so as to automatically install the local connector corresponding to the first application program on the server.
Therefore, by using the scheme provided by the embodiment of the application, a user does not need to execute a series of operations such as downloading the installation file, decompressing the installation file, inputting the installation configuration information and the like, the user only needs to trigger the deployment operation of the local connector, and the host agent can automatically install the local connector on the server, so that the user operation is simplified, and the user experience is improved. As previously described, in one example, the host agent may be deployed on the server. At present, if a host agent is deployed on a server, a user needs to input a plurality of commands on a corresponding page, and for a user who is not familiar with the host agent deployment or has no programming basis, a situation of command input error is very likely to occur, so that the user operation threshold is higher, and accordingly, the efficiency of deploying the host agent is lower. In order to solve this problem, the embodiment of the present application provides a solution that can quickly deploy a host agent.
In one example, a shortcut deployment host agent may be implemented by the following steps A1-A2. In one example, the following steps A1-A2 may be performed by a server corresponding to the host agent.
A1: and responding to a host agent creating operation triggered by a user on a second page displayed by the server, and acquiring an installation script for installing the host agent.
A2: installing the host agent onto the server based on the installation script.
In one example, the second page may include a second control for triggering creation of the host agent, for example, through which the user may trigger the host agent creation operation. For example, the user may click on the second control, thereby triggering the host agent creation operation.
After the user triggers the host agent creation operation, the server may obtain an installation script for installing the host agent in response to the host agent creation operation. In one example, the installation script may include a plurality of commands to install the host agent.
After the installation script is obtained, the server corresponding to the host agent may install the host agent on the server based on the installation script. For example, a server corresponding to the host agent may execute a command in the installation script, so as to install the host agent on the server.
By adopting the steps A1-A2, the user can deploy the host agent on the server by triggering the host agent creation operation without inputting a plurality of commands by the user, so that the user operation threshold is reduced, and correspondingly, the efficiency of deploying the host agent is improved.
It should be noted that, in the case of no conflict, the contents of the application access method shown in fig. 1 and the local connector deployment method shown in fig. 2 may be referred to each other.
Exemplary device
Based on the method provided by the above embodiment, the embodiment of the present application further provides an apparatus, which is described below with reference to the accompanying drawings.
Referring to fig. 4, this figure is a schematic structural diagram of an application access device according to an embodiment of the present application. The apparatus 400 shown in fig. 4 can be applied to a local connector deployed in an intranet, and the apparatus 400 includes: a first receiving unit 401, a first processing unit 402 and a first transmitting unit 403.
A first receiving unit 401, configured to receive a first data access request from an external network, where the first data access request is used to request to access application data of a first application deployed in the internal network, and the first data access request employs a first general data protocol;
a first processing unit 402, configured to process the first data access request to obtain a second data processing request, where the second data processing request adopts a private data protocol supported by the first application;
a first sending unit 403, configured to send the second data processing request to the first application.
Optionally, the first receiving unit 401 is configured to:
receiving, by a host agent, the first data access request.
Optionally, the host agent is further configured to:
receiving a third data access request from the external network, wherein the third data access request is used for requesting to access application data of a second application program deployed in the internal network, and the third data access request adopts the second universal data protocol;
sending the third data access request to the second application program, the second application program supporting the second universal data protocol.
Optionally, the local connector runs on a server in the intranet.
Optionally, the local connector is deployed on the server in the following manner:
responding to local connector deployment operation triggered by a user in a first page corresponding to a host agent running on the server, and automatically acquiring an installation file corresponding to the local connector, wherein the local connector is used for converting a message adopting a first general data protocol into a message adopting a private data protocol and converting the message adopting the private protocol into a message adopting the first general data protocol;
automatically installing the local connector onto the server using the installation file.
Optionally, the host agent is deployed on the server in the following manner:
responding to host agent creating operation triggered by a user on a second page displayed by the server, and acquiring an installation script for installing the host agent;
installing the host agent onto the server based on the installation script.
Optionally, the first receiving unit 401 is configured to:
and receiving a first data access request sent by a server corresponding to an integration platform deployed in an external network, wherein the first data access request is generated by the server in response to an operation of accessing application data of a first application deployed in the internal network, which is triggered by a user on the integration platform.
Optionally, the apparatus further comprises:
a second receiving unit, configured to receive a first response message for the second data access request sent by the first application, where the first response message is the private data protocol;
a second processing unit, configured to process the first response message to obtain a second response message, where the second response message requests to use the first generic data protocol;
and the second sending unit is used for sending the second response message to the server.
Optionally, the second response message is a desensitized message.
Since the apparatus 400 is an apparatus corresponding to the application access method provided in the above method embodiment, and the specific implementation of each unit of the apparatus 400 is the same as that of the above method embodiment, for the specific implementation of each unit of the apparatus 400, reference may be made to the relevant description part of the above method embodiment, and details are not repeated here.
Referring to fig. 5, the drawing is a schematic structural diagram of a deployment apparatus for a local connector according to an embodiment of the present application. The apparatus 500 shown in fig. 5 may include: an acquisition unit 501 and a mounting unit 502.
An obtaining unit 501, configured to automatically obtain an installation file corresponding to a local connector in response to a local connector deployment operation triggered in a first page corresponding to a host agent running on a server by a user, where the local connector is configured to convert a packet using a first general data protocol into a packet using a private data protocol, and is configured to convert a packet using the private protocol into a packet using the first general data protocol;
an installation unit 502, configured to automatically install the local connector on the server by using the installation file.
Optionally, the host agent is deployed on the server in the following manner:
responding to host agent creating operation triggered by a user on a second page displayed by the server, and acquiring an installation script for installing the host agent;
installing the host agent onto the server based on the installation script.
Optionally, the server is deployed in an intranet.
Since the apparatus 500 is a device corresponding to the deployment method of the local connector provided in the above method embodiment, and the specific implementation of each unit of the apparatus 500 is the same concept as that of the above method embodiment, for the specific implementation of each unit of the apparatus 500, reference may be made to the relevant description part of the above method embodiment, and details are not repeated here.
An embodiment of the present application further provides an apparatus, which includes a processor and a memory;
the processor is configured to execute the instructions stored in the memory to cause the apparatus to perform the application access method of any of the above method embodiments or to cause the apparatus to perform the deployment method of the local connector of any of the above method embodiments.
The embodiment of the present application provides a computer-readable storage medium, which includes instructions for instructing a device to execute an application access method described in any one of the above method embodiments, or instructing a device to execute a deployment method of a local connector described in any one of the above method embodiments.
The present application provides a computer program product, when the computer program product runs on a computer, the computer is caused to execute the application access method described in any one of the above method embodiments, or the computer is caused to execute the deployment method of the local connector described in any one of the above method embodiments.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice in the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims (16)

1. An application access method, applied to a local connector deployed in an intranet, the method comprising:
receiving a first data access request from an external network, wherein the first data access request is used for requesting to access application data of a first application program deployed in the internal network, and the first data access request adopts a first general data protocol;
processing the first data access request to obtain a second data processing request, wherein the second data processing request adopts a private data protocol supported by the first application program;
and sending the second data processing request to the first application program.
2. The method of claim 1, wherein receiving the first data access request from the external network comprises:
receiving, by a host agent, the first data access request.
3. The method of claim 2, wherein the host agent is further configured to:
receiving a third data access request from the external network, wherein the third data access request is used for requesting to access application data of a second application program deployed by the internal network, and the third data access request adopts the second universal data protocol;
sending the third data access request to the second application program, the second application program supporting the second universal data protocol.
4. The method according to claim 1, wherein the local connector runs on a server in the intranet.
5. The method of claim 4, wherein the local connector is deployed on the server by:
responding to local connector deployment operation triggered by a user in a first page corresponding to a host agent running on the server, and automatically acquiring an installation file corresponding to the local connector, wherein the local connector is used for converting a message adopting a first general data protocol into a message adopting a private data protocol and converting the message adopting the private protocol into a message adopting the first general data protocol;
automatically installing the local connector onto the server using the installation file.
6. The method of claim 5, wherein the host agent is deployed on the server by:
responding to host agent creating operation triggered by a user on a second page displayed by the server, and acquiring an installation script for installing the host agent;
installing the host agent onto the server based on the installation script.
7. The method of claim 1, wherein receiving the first data access request from the external network comprises:
and receiving a first data access request sent by a server corresponding to an integration platform deployed in an external network, wherein the first data access request is generated by the server in response to an operation of accessing application data of a first application deployed in the internal network, which is triggered by a user on the integration platform.
8. The method of claim 7, further comprising:
receiving a first response message for the second data access request sent by the first application, the first response message being the private data protocol;
processing the first response message to obtain a second response message, wherein the second response message requests to adopt the first universal data protocol;
and sending the second response message to the server.
9. The method of claim 8, wherein the second response message is a desensitized message.
10. A method for deploying a local connector, the method comprising:
responding to local connector deployment operation triggered by a user in a first page corresponding to a host agent running on a server, and automatically acquiring an installation file corresponding to a local connector, wherein the local connector is used for converting a message adopting a first general data protocol into a message adopting a private data protocol and converting the message adopting the private protocol into a message adopting the first general data protocol;
automatically installing the local connector onto the server using the installation file.
11. The method of claim 10, wherein the host agent is deployed on the server by:
responding to host agent creating operation triggered by a user on a second page displayed by the server, and acquiring an installation script for installing the host agent;
installing the host agent onto the server based on the installation script.
12. The method according to claim 10, wherein the server is deployed within an intranet.
13. An application access apparatus for a local connector deployed in an intranet, the apparatus comprising:
a first receiving unit, configured to receive a first data access request from an external network, where the first data access request is used to request access to application data of a first application deployed in the internal network, and the first data access request employs a first general data protocol;
a first processing unit, configured to process the first data access request to obtain a second data processing request, where the second data processing request uses a private data protocol supported by the first application;
a first sending unit, configured to send the second data processing request to the first application.
14. A local connector deployment apparatus, the apparatus comprising:
an obtaining unit, configured to automatically obtain an installation file corresponding to a local connector in response to a local connector deployment operation triggered in a first page corresponding to a host agent running on a server by a user, where the local connector is configured to convert a packet using a first general data protocol into a packet using a private data protocol, and to convert a packet using the private protocol into a packet using the first general data protocol;
and the installation unit is used for automatically installing the local connector to the server by using the installation file.
15. An apparatus, comprising a processor and a memory;
the processor is to execute instructions stored in the memory to cause the device to perform the method of any of claims 1 to 12.
16. A computer-readable storage medium comprising instructions that direct a device to perform the method of any of claims 1-12.
CN202210720127.5A 2022-06-23 2022-06-23 Application access method, local connector deployment method and device Pending CN115118776A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210720127.5A CN115118776A (en) 2022-06-23 2022-06-23 Application access method, local connector deployment method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210720127.5A CN115118776A (en) 2022-06-23 2022-06-23 Application access method, local connector deployment method and device

Publications (1)

Publication Number Publication Date
CN115118776A true CN115118776A (en) 2022-09-27

Family

ID=83327868

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210720127.5A Pending CN115118776A (en) 2022-06-23 2022-06-23 Application access method, local connector deployment method and device

Country Status (1)

Country Link
CN (1) CN115118776A (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014145238A2 (en) * 2013-03-15 2014-09-18 Blue Jeans Network Provision of video conferencing services using a micropop to extend media processing into enterprise networks
CN106230870A (en) * 2016-10-13 2016-12-14 成都东方盛行电子有限责任公司 Proprietary protocol document transmission system and method
CN111064694A (en) * 2018-10-16 2020-04-24 深圳市云帆加速科技有限公司 Method and device for realizing protocol gateway
CN111131143A (en) * 2019-10-24 2020-05-08 天地融科技股份有限公司 Network access control method, device and system
CN113824791A (en) * 2021-09-23 2021-12-21 深信服科技股份有限公司 Access control method, device, equipment and readable storage medium

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014145238A2 (en) * 2013-03-15 2014-09-18 Blue Jeans Network Provision of video conferencing services using a micropop to extend media processing into enterprise networks
CN106230870A (en) * 2016-10-13 2016-12-14 成都东方盛行电子有限责任公司 Proprietary protocol document transmission system and method
CN111064694A (en) * 2018-10-16 2020-04-24 深圳市云帆加速科技有限公司 Method and device for realizing protocol gateway
CN111131143A (en) * 2019-10-24 2020-05-08 天地融科技股份有限公司 Network access control method, device and system
CN113824791A (en) * 2021-09-23 2021-12-21 深信服科技股份有限公司 Access control method, device, equipment and readable storage medium

Similar Documents

Publication Publication Date Title
CN101571809B (en) Implementation method of plug-in registration and device thereof
CN107635027B (en) Domain name resolution method, medium, device and computing equipment
US20130019236A1 (en) Communication device, update method, and computer-readable storage medium
US10282185B2 (en) Method and apparatus for firmware virtualization
US20120227032A1 (en) Method, apparatus, and system for invoking widget
CN107193609B (en) Function module calling method and device in application and electronic equipment
EP2863281A2 (en) System and method to configure a field device
US10404568B2 (en) Agent manager for distributed transaction monitoring system
CN113141405B (en) Service access method, middleware system, electronic device, and storage medium
CN110968331A (en) Method and device for running application program
CN103324537A (en) Resource sharing method and device
CN103634393A (en) IVR (interactive voice response) and realization method thereof
CN113778477A (en) File processing method and device, computer readable storage medium and electronic device
JP6358063B2 (en) Request transmission method, information processing apparatus, and program
US9160878B2 (en) Server apparatus that enables easy use of image input apparatus, information processing apparatus, methods of controlling the apparatuses, control program, and storage medium
CN113342419B (en) Push system loading method and device, electronic equipment and storage medium
US9164817B2 (en) Mobile communication terminal to provide widget expansion function using message communication, and operation method of the mobile communication terminal
CN112688811B (en) Wireless local area network management method, device, equipment and storage medium
CN115118776A (en) Application access method, local connector deployment method and device
CN114726905B (en) Method, device, equipment and storage medium for accessing Tbox network into Android system
CN115118587A (en) Method and device for creating connector
CN103608771B (en) Share and access to local device
CN113422791B (en) Cloud service configuration method and device, electronic equipment and computer readable storage medium
CN112104513B (en) Visual software load method, device, equipment and storage medium
US20080256614A1 (en) Network terminal management apparatus, method and program

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