CN112738091B - Method and device for interaction between middleware console and middleware server - Google Patents
Method and device for interaction between middleware console and middleware server Download PDFInfo
- Publication number
- CN112738091B CN112738091B CN202011591587.XA CN202011591587A CN112738091B CN 112738091 B CN112738091 B CN 112738091B CN 202011591587 A CN202011591587 A CN 202011591587A CN 112738091 B CN112738091 B CN 112738091B
- Authority
- CN
- China
- Prior art keywords
- middleware
- console
- server
- interaction
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/288—Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer And Data Communications (AREA)
Abstract
The application discloses a middleware console and middleware server interaction method and device, and realizes a one-to-many interaction mode of the middleware console and the middleware server. The method for interaction between the middleware console and the middleware server comprises the following steps: receiving a first interaction request of a middleware console; checking whether the middleware console has access authority or not according to the first interaction request; when the middleware console has access authority, generating first response information; sending the first response information to the middleware console; selecting a remote interface according to the first interaction request to acquire the first instruction; checking whether the access terminal has the operation authority or not according to the first instruction; when the access terminal has the operation authority, executing the first instruction, and generating second response data according to an execution result; and sending the second response data to the middleware console so that the middleware console and the access terminal exchange information.
Description
Technical Field
The present application relates to the field of data interaction technologies, and in particular, to a method and an apparatus for interaction between a middleware console and a middleware server.
Background
With the development of electronic commerce in recent years, middleware technology has become more and more mature. The middleware of the prior art supports a visual deployment console. This reduces the learning cost and maintenance cost for the operator using the middleware.
And an operator deploys the middleware server by accessing the visual console. For the deployment operation, a visual console controls a middleware server.
The access terminal transmits the operation instruction of the operator to a middleware console deployed in the middleware. And the middleware console retrieves a specific middleware server by analyzing the operation instruction.
In the process of realizing the prior art, the inventor finds that:
the application middleware server must deploy a visualization console. The console can only deploy files to a particular directory by looking up the directory. The interaction method is not only rigid and inextensible, but also wastes server resources to a certain extent.
Therefore, it is desirable to provide a method and an apparatus for interaction between a middleware console and a middleware server, so as to solve the problem of extensibility caused by a single interaction mode between the middleware console and the server.
Disclosure of Invention
The embodiment of the application provides a method and a device for interaction between a middleware console and a middleware server, which are used for solving the problem of expansibility caused by single interaction mode of the middleware console and the server.
The application provides an interaction method of a middleware console and a middleware server, which comprises the following steps:
receiving a first interaction request of a middleware console;
checking whether the middleware console has access authority or not according to the first interaction request;
when the middleware console has access authority, generating first response information;
sending the first response information to the middleware console;
selecting a remote interface matched with a first instruction of a transfer access end of the middleware console according to the first interaction request, and acquiring the first instruction of the transfer access end of the middleware console;
according to the first instruction, whether the access terminal has the operation authority is checked;
when the access terminal has the operation authority, executing the first instruction, and generating second response data according to an execution result;
sending second response data to the middleware console so that the middleware console and the access terminal can exchange information;
the middleware console is used for transferring the interactive information of the access terminal and the middleware server.
Further, the middleware console is decoupled from the middleware server; the middleware console and the middleware server are not in the same device.
Further, the middleware console interacts with at least one middleware server.
Further, according to the first interactive request, checking whether the middleware console has an access right specifically includes:
and acquiring an account number or an IP address of the middleware console according to the first interaction request, and judging whether the middleware console has an access right.
Further, according to the first instruction, checking whether the access terminal has an operation right specifically includes:
and acquiring an account number or an IP address of the access terminal according to the first instruction, and judging whether the access terminal has an operation authority.
The application provides an interaction method of a middleware console and a middleware server, which comprises the following steps:
receiving a second interaction request and a first instruction of the access terminal;
selecting a first target middleware server to which an access terminal needs to be connected according to the first instruction;
sending a first interaction request to the first target middleware server;
when the first interaction request meets the release condition, acquiring first response information sent from a first target middleware server, and sending the first instruction to the first target middleware server;
and acquiring second response information sent from the first target middleware server, and sending the second response information to an access terminal.
Further, the middleware console is decoupled from the middleware server; the middleware console is not in the same device as the middleware server.
Further, the middleware console interacts with at least one middleware server.
Further, the first interaction request meeting the release condition specifically includes:
and when the middleware console has the authority of accessing the middleware server, the first interaction request meets the release condition.
The application provides a middleware console and middleware server interaction device, including:
middleware console unit: the system comprises a middleware server unit, a relay access end and a middleware server unit, wherein the middleware server unit is used for sending interaction information of the access end and the middleware server unit;
middleware server unit: the first instruction is used for executing the middleware console unit to forward the access end;
wherein the middleware server unit includes:
the first interaction module is used for receiving a first interaction request of the middleware console unit;
selecting a remote interface according to the first interaction request to acquire the first instruction;
the first checking module is used for checking whether the middleware console unit has the access right or not according to the first interaction request;
according to the first instruction, whether the access terminal has the operation authority is checked;
the first response module is used for generating first response information when the middleware console unit has access authority;
sending the first response information to the middleware console unit;
when the access terminal has the operation authority, executing the first instruction, and generating second response data according to an execution result;
sending second response data to the middleware console unit so that the middleware console unit and the access terminal exchange information;
the middleware console unit includes:
the second interaction module receives a second interaction request and a first instruction of the access terminal;
sending a first interaction request to the middleware server unit;
when the first interaction request meets the release condition, acquiring first response information returned from a first target middleware server unit, and sending the first instruction to the first target middleware server unit;
the matching module selects a first target middleware server to which the access terminal needs to be connected according to the first instruction;
and the second response module is used for acquiring second response information sent from the first target middleware server unit and sending the second response information to the access terminal.
The embodiment provided by the application has at least the following beneficial effects:
the application expands the single interaction module which is bound one to one between the traditional middleware console and the middleware server, realizes a one-to-many interaction mode, increases expansibility, and solves the hidden safety and performance problems caused by strong binding.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a flowchart of a method for implementing interaction between a middleware console and a middleware server based on the middleware server according to an embodiment of the present application.
Fig. 2 is a flowchart of a method for implementing interaction between a middleware console and a middleware server based on the middleware console according to an embodiment of the present application.
Fig. 3 is a block diagram schematically illustrating a structure of an apparatus for implementing interaction between a middleware console and a middleware server according to an embodiment of the present application.
Reference numerals are as follows:
100. middleware console and middleware server interaction device
11. Middleware console unit
111. Second interaction module
112. Matching module
113. Second response module
12. Middleware server unit
121. First interaction module
122. First checking module
123. First response module
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only a few embodiments of the present application, and not all 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.
Middleware is understood to be software that connects two separate applications or separate systems. One of the main uses of the middleware is therefore information transfer. Through middleware, applications can operate in a multi-platform or OS environment.
Most middleware supports visual deployment consoles, which reduces the learning cost and maintenance cost for operators using middleware.
And the operator performs deployment operation on the middleware server by accessing the visual console. For the deployment operation, a visual console controls a middleware server.
The access terminal transmits the operation instruction of the operator to a middleware console deployed in the middleware. And the middleware console retrieves a specific middleware server by analyzing the operation instruction.
However, the interaction between the middleware console and the middleware server is accompanied by a problem that an application middleware server must deploy a visual middleware console. The middleware console can only deploy files to a particular directory through the bound middleware server. The interaction method is not only rigid and inextensible, but also wastes server resources to a certain extent.
After the middleware console and the middleware server are arranged in a decoupling mode, the middleware console is installed on the first device, the middleware server is installed on the second device, and an operator can initiate access to the middleware console on the third device.
It should be noted that, because the middleware console and the middleware server are set in a decoupled manner, the middleware console can establish a connection relationship with a plurality of middleware servers, so that a situation that one console can control a plurality of middleware servers occurs.
Therefore, the device for installing the middleware server can be provided with a plurality of devices, and for the convenience of description, only the access end, the middleware console and the first target middleware server are described.
Specifically, the operator initiates an access request on the third device to the middleware console of the first device.
The middleware console of the first device gives permission after receiving an access request from the third device.
The operator can then operate the middleware console of the first device on the third device and generate operating instructions at the third device.
The operating instruction is to be transmitted by the third device to the middleware console of the first device.
After receiving the operation instruction from the third device, the middleware console of the first device may retrieve the second device attribute, i.e., the first target middleware server attribute, to which the operator needs to connect according to the operation instruction sent by the third device.
It should be noted that the first target middleware server attribute includes a connection address, a port, an account, and a password of the first target middleware server.
After the middleware console of the first device retrieves the connection information of the first target middleware server on the second device, the middleware console of the first device will send an interaction request to the first target middleware server of the second device for access.
After receiving the interactive request of the middleware console, the first target middleware server verifies the access right of the middleware console according to the interactive request of the middleware console.
After the verification is passed, the first target middleware server generates a response message. The first target middleware server sends the response information to the middleware console.
Meanwhile, the first target middleware server also selects a remote interface matched with the operation information to be transferred according to the interaction information sent by the middleware console, and receives the operation information transferred by the middleware console from the access end.
When the middleware console receives the response information sent by the first target middleware server, the middleware console transfers the operation information from the access terminal to the first target middleware server.
Then, the first target middleware server of the second device acquires the operation information of the operator at the third device.
And then the first target middleware server verifies the operation authority of the third equipment access terminal according to the operation information.
And if the verification is passed, the first target middleware server executes the operation information.
And after the first target middleware server executes the operation according to the operation information, the first target middleware server generates response data from the current processing result and sends the response data to the middleware console.
The middleware console receives the response data from the first target middleware server, and then forwards the response data to the third device access terminal.
And the third equipment access terminal displays the response state, namely the processing result of the current operation after receiving the response data of the first target middleware server transmitted by the middleware console.
So far, the operation performed by the operator on the third device is interacted with the middleware server through the middleware console, and is finally executed.
The interaction of the middleware console and the middleware server is realized as a one-to-many interaction mode in a specific scene. Thereby increasing the expansibility of interaction between the middleware console and the middleware server.
For operators who pay more attention to the safety of equipment, the traditional middleware not only has application but also has a console. Hackers can attack deployed applications or middleware consoles, both of which can pose certain security risks. The middleware console and middleware server interaction method solves the problem of hidden safety caused by strong binding of the middleware console and the middleware server, and therefore the probability that the middleware server is attacked is reduced.
The method for interaction between the middleware console and the middleware server provided by the present application will be described in detail below with reference to the middleware server.
Referring to fig. 1, the present application provides a method for a middleware console to interact with a middleware server, including the following steps:
s110: a first interactive request of a middleware console is received.
It is noted that the first interactive request may be understood as a handshake protocol issued by the middleware console to the middleware server, and is mainly used for the middleware server to confirm the identity of the middleware console.
After the middleware console and the middleware server are decoupled, the middleware console can be connected with a plurality of middleware servers. Similarly, a middleware server will appear to be accessible by multiple middleware consoles.
The first interactive request is indispensable based on security performance considerations.
S120: and checking whether the middleware console has the access right or not according to the first interactive request.
It should be noted that the first interaction request includes information such as an IP address of a device where the middleware console is located, and an account number for sending the first interaction request middleware console. So that the middleware server can verify whether the middleware console has access rights.
After the middleware server reads the first interaction request, whether the middleware console has the access right or not is judged according to the IP address of the device where the middleware console is located, the account number of the middleware console sending the first interaction request and other information.
S130: and when the middleware console has the access right, generating first response information.
S140: and sending the first response information to the middleware console.
It should be noted that, in consideration of information security performance, the operation information of the operator is stored in the middleware console and waits to be transferred to the middleware server. But the operation information is not sent to the middleware server along with the middleware console's handshake protocol.
The middleware console must transfer the operation information to the middleware server after the middleware server grants the middleware console access.
Therefore, only when the middleware console has the authority to access the middleware server, the middleware server generates the first response information and sends the first response information to the middleware console.
So that the middleware server acquires the operation information of the operator.
S150: and selecting a remote interface according to the first interaction request to acquire the first instruction.
Considering that the middleware server can be connected to different platforms, different environments, different systems, and different devices, the first interaction request sent by the middleware console further includes an interface identifier for receiving the operation information.
And the middleware server selects the matched remote interface according to the interface identifier.
And then the middleware server acquires the operation information of the middleware console transfer access end, namely the first instruction, through the matched remote interface.
S160: and checking whether the access terminal has the operation authority or not according to the first instruction.
It should be noted that the first instruction further includes information such as an IP address of the device where the access terminal is located, and an account number of the first instruction operator. So that the middleware server can verify whether the access terminal has the operation right.
After the middleware server reads the first instruction, whether the access terminal has the operation authority or not is judged according to information such as an IP address of equipment where the access terminal is located, an account number of a first instruction operator and the like.
S170: and when the access terminal has the operation authority, executing the first instruction, and generating second response data according to an execution result.
S180: and sending the second response data to the middleware console so that the middleware console and the access terminal exchange information.
It should be noted that the second response data is an execution result after the middleware server executes an operation according to the operation information.
And after the second response data is sent to the middleware console, the second response data is transferred to the access terminal through the middleware console.
The access terminal displays the second response data.
The middleware console and middleware server interaction method provided by the present application will be described in detail below with reference to the middleware console.
Referring to fig. 2, the present application provides a method for a middleware console to interact with a middleware server, including the following steps:
s210: and receiving a second interaction request and a first instruction of the access terminal.
It should be noted that the second interactive request may be understood as a handshake protocol issued by the access terminal to the middleware console, and is mainly used to let the middleware console confirm the identity of the access terminal.
The first instruction is an operation instruction generated when an operator operates at the access terminal and is used for being executed on the middleware server.
It is to be noted that the first instruction is also to be saved by the middleware console as a backup.
S220: and selecting a first target middleware server to which the access terminal needs to be connected according to the first instruction.
It should be noted that the first instruction at least includes information such as control instruction data, connection unique identifier, interface identifier, and IP address of the access terminal device.
The connection unique identifier comprises information such as a connection address, a port, an account number and a password of a first target middleware server which needs to be connected by the access terminal.
S230: and sending a first interaction request to the first target middleware server.
It should be noted that, after reading the first instruction, the middleware console sends a first interaction request to a first target middleware server that needs to be connected according to the connection unique identifier of the first instruction.
The first interactive request is indispensable based on security considerations.
S240: and when the first interaction request meets the release condition, acquiring first response information sent from a first target middleware server, and sending the first instruction to the first target middleware server.
It is noted that the first interactive request may be understood as a handshake protocol issued by the middleware console to the middleware server, and is mainly used for the middleware server to confirm the identity of the middleware console.
After the middleware console and the middleware server are arranged in a decoupling mode, the middleware console can be connected with the plurality of middleware servers. Similarly, a middleware server will appear to be accessible by multiple middleware consoles.
In one embodiment of the present application, the operation information of the operator is stored in the middleware console and is transferred to the middleware server in consideration of the information security performance. But the operation information is not sent to the middleware server along with the middleware console's handshake protocol.
After the middleware server grants the middleware console access, the middleware console will forward the operation information to the middleware server.
Therefore, when the middleware console has the right to access the middleware server, the first interaction request meets the release condition. The middleware server generates first response information and sends the first response information to the middleware console.
And after receiving the first response information sent by the first target middleware server, the middleware console forwards the first instruction to the first target middleware server.
S250: and acquiring second response information sent from the first target middleware server, and sending the second response information to an access terminal.
It should be noted that, after the first target middleware server executes the first instruction, the first target middleware server generates second response data according to an execution result.
And the second response data is sent to the middleware console from the first target middleware server and is transferred to the access terminal through the middleware console.
The access terminal displays the second response data.
In order to support the interaction method between the middleware console and the middleware server, the application provides an interaction device 100 between the middleware console and the middleware server.
And the middleware console unit 11 is used for relaying the interaction information between the access terminal and the middleware server unit 12.
It should be noted that, since the middleware console unit 11 and the middleware server unit 12 are provided separately from the middleware console and the middleware server, they may not be provided in the same device.
Therefore, the middleware console can establish connection relation with a plurality of middleware servers.
And the middleware console unit 11 is only used for relaying the interaction information of the access terminal and the middleware server unit 12.
The second interaction module 111 receives a second interaction request and a first instruction from the access terminal;
sending a first interaction request to the middleware server unit;
when the first interaction request meets the release condition, first response information returned from the first target middleware server unit 12 is acquired, and the first instruction is sent to the first target middleware server unit 12.
And the matching module 112 selects the first target middleware server 12 to which the access terminal needs to be connected according to the first instruction.
The second response module 113 is configured to obtain second response information sent from the first target middleware server unit, and send the second response information to the access terminal.
And a middleware server unit 12, configured to execute the first instruction of the forwarding access end of the middleware console unit 11.
It should be noted that, since the middleware console unit 11 and the middleware server unit 12 are not provided in the same device after being set separately from the middleware console and the middleware server.
The middleware server is thus accessible by multiple middleware consoles.
And the middleware server unit 12 is mainly used for executing the first instruction of the middleware console unit 11 for forwarding the access end.
A first interaction receiving module 121, configured to receive a first interaction request of the middleware console unit 11;
and selecting a remote interface according to the first interaction request to acquire the first instruction.
A first checking module 122, configured to check whether the middleware console unit 11 has an access right according to the first interaction request;
and checking whether the access terminal has the operation authority or not according to the first instruction.
A first response module 123, configured to generate first response information when the middleware console unit 11 has an access right;
sending the first response information to the middleware console unit;
when the access terminal has the operation authority, executing the first instruction, and generating second response data according to an execution result;
and sending the second response data to the middleware console unit so that the middleware console unit 11 exchanges information with the access terminal.
Specifically, in one embodiment provided in the present application, there are a device a, a device B, and a device C.
The middleware console unit 11 is disposed on the device B, and the middleware console unit 11 includes a second interaction module 111, a matching module 112, and a second response module 113.
The device C is provided with the middleware server unit 12, and the middleware server unit 12 includes a first receiving and interacting module 121, a first verifying module 122, and a first responding module 123.
The operation and maintenance personnel can operate remotely on device a and control the middleware server unit 12 on device C by accessing device B.
The operation of the middleware console and the middleware server interaction device during the remote operation of the operation and maintenance personnel will be described in detail below.
The operation and maintenance personnel initiates an access request, i.e. a second interaction request, on the device a to the middleware console unit 11 of the device B.
The device B middleware console unit 11 receives the second interaction request from the device a through the second interaction module 111, and then gives permission.
The operation and maintenance personnel can then operate the middleware console unit 11 of the equipment B on the equipment a. And generates an operation instruction, i.e., a first instruction, at the device a.
The first instruction will be transmitted by device a to the middleware console unit 11 of device B.
After receiving the first instruction from the device a through the second interaction module 111, the middleware console unit 11 of the device B reads the first instruction through the matching module 112. The matching module 112 may retrieve the attributes of the middleware server unit 12 on the device C to which the operation and maintenance staff needs to connect, that is, the connection address, the port, the account number, and the password of the device C.
After the middleware console unit 11 retrieves the connection information of the device C through the matching module 112, the middleware console unit 11 will send an interaction request, i.e. a first interaction request, to the middleware server unit 12 of the device C through the second interaction module 111, so that the middleware console unit 11 accesses the middleware server unit 12.
After the first interaction module 121 of the middleware server unit 12 on the device C receives the first interaction request of the middleware console unit 11, the first verification module 122 of the middleware server unit 12 verifies the access right of the middleware console unit 11 according to the first interaction request.
After the verification is passed, the middleware server unit 12 generates first response information. And transmits the first response information back to the middleware console unit 11 through the first response module 123.
Meanwhile, the first interaction module 121 of the middleware server unit 12 also selects a remote interface matched with the first instruction to be forwarded according to the first interaction request sent by the middleware console unit 11, and receives the first instruction of the middleware console unit 11 forwarding device a.
When the second interactive module 111 of the middleware console unit 11 receives the first response message from the middleware server unit 12, the second interactive module 111 forwards the first command from the device a to the middleware server unit 12.
Then, the first interaction module 121 of the middleware server unit 12 will obtain the first instruction of the operation and maintenance person on the device a.
The first checking module 122 of the middleware server unit 12 checks the operation authority of the device a according to the first instruction.
If the check passes, the middleware server unit 12 executes the first instruction.
After the middleware server unit 12 executes the operation according to the first instruction, the first response module 123 of the middleware server unit 12 generates second response data from the current execution result, and the second response data is sent to the middleware console unit 11 by the first response module 123.
After the second response module 113 of the middleware console unit 11 receives the second response data from the middleware server unit 12, the second response module 113 forwards the second response data from the middleware server unit 12 to the device a.
After receiving the second response data of the middleware server unit 12 forwarded by the middleware console unit 11, the device a displays the second response data, that is, the execution result of the middleware server unit 12 after the operation performed by the operation and maintenance personnel on the device a.
Up to this point, the operation performed by the operation and maintenance personnel on the device a is performed by the middleware console and the middleware server interaction device 100.
The middleware console and middleware server interaction device 100 is implemented as a one-to-many interaction mode in a specific scenario through the interaction of the middleware console unit 11 and the middleware server unit 12. Thereby increasing the expansibility of the interaction between the middleware console and the middleware server.
For an operator who attaches importance to the security of the device, the middleware console and middleware server interaction device 100 solves the hidden security caused by the strong binding between the middleware console and the middleware server, and therefore reduces the probability of the attack on the middleware server.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of other like elements in a process, method, article, or apparatus comprising the element.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application 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 above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (6)
1. A middleware console and middleware server interaction method is characterized in that the middleware server at least comprises a first target middleware server, and the middleware console and middleware server interaction method is applied to the interaction between the middleware console and the first target middleware server, so that the first target middleware server executes the following steps:
receiving a first interaction request of a middleware console;
checking whether the middleware console has access authority or not according to the first interaction request;
when the middleware console has access authority, generating first response information;
sending the first response information to the middleware console;
selecting a remote interface according to the first interaction request to acquire a first instruction;
checking whether the access terminal has the operation authority or not according to the first instruction;
when the access terminal has the operation authority, executing the first instruction, and generating second response data according to an execution result;
sending second response data to the middleware console so that the middleware console and the access terminal can exchange information;
the middleware console is used for transferring the interactive information of the access terminal and a first target middleware server;
after the middleware console and the first target middleware server are set in a decoupling mode, the middleware console is installed on the first equipment, the first target middleware server is installed on the second equipment, and an operator initiates access to the middleware console on the third equipment;
the first interactive request sent by the middleware console also comprises an interface identifier used for receiving the operation information;
the first target middleware server selects a matched remote interface according to the interface identifier;
and the first target middleware server acquires the operation information of the transfer access end of the middleware console through the matched remote interface.
2. The method for interaction between a middleware console and a middleware server as claimed in claim 1, wherein verifying whether the middleware console has an access right according to the first interaction request specifically comprises:
and acquiring an account number or an IP address of the middleware console according to the first interaction request, and judging whether the middleware console has an access right.
3. The method for interaction between a middleware console and a middleware server as claimed in claim 1, wherein verifying whether an access terminal has an operation right according to the first instruction specifically comprises:
and acquiring an account number or an IP address of an access terminal according to the first instruction, and judging whether the access terminal has an operation authority.
4. A method for interaction between a middleware console and a middleware server, the middleware server at least comprising a first target middleware server, the method for interaction between the middleware console and the middleware server being applied to the interaction between the middleware console and the first target middleware server, so that the middleware console performs the following steps in cooperation with the method of claim 1:
receiving a second interaction request and a first instruction of the access terminal;
selecting a first target middleware server to which an access terminal needs to be connected according to the first instruction;
sending a first interaction request to the first target middleware server;
when the first interaction request meets the release condition, acquiring first response information sent from a first target middleware server, and sending the first instruction to the first target middleware server;
and acquiring second response information sent from the first target middleware server, and sending the second response information to the access terminal.
5. The middleware console interacting method with the middleware server as claimed in claim 4, wherein the first interaction request satisfies a release condition, specifically comprising:
when the middleware console has the right to access the middleware server, the first interaction request meets the release condition.
6. A middleware console and middleware server interaction system, wherein the middleware server at least comprises a first target middleware server, and the middleware console and middleware server interaction system is applied to interaction between the middleware console and the first target middleware server, and comprises:
middleware console: the system comprises a first target middleware server, a second target middleware server and a server management server, wherein the first target middleware server is used for exchanging interaction information between an access terminal and the first target middleware server;
the first target middleware server: the first instruction is used for executing the middleware console to transfer the access end;
wherein the first target middleware server comprises:
the first interaction module is used for receiving a first interaction request of the middleware console;
selecting a remote interface according to the first interaction request to acquire a first instruction;
the first checking module is used for checking whether the middleware console has the access right or not according to the first interaction request;
checking whether the access terminal has the operation authority or not according to the first instruction;
the first response module is used for generating first response information when the middleware console has access authority;
sending the first response information to the middleware console;
when the access terminal has the operation authority, executing the first instruction, and generating second response data according to an execution result;
sending second response data to the middleware console so that the middleware console and the access terminal can exchange information;
the middleware console includes:
the second interaction module receives a second interaction request and a first instruction of the access terminal;
sending a first interaction request to the first target middleware server;
when the first interaction request meets the release condition, acquiring first response information returned from a first target middleware server, and sending the first instruction to the first target middleware server;
the matching module selects a first target middleware server to which the access terminal needs to be connected according to the first instruction;
the second response module is used for acquiring second response information sent from the first target middleware server and sending the second response information to the access terminal;
the middleware console is used for transferring the interactive information of the access terminal and a first target middleware server;
after the middleware console and the first target middleware server are set in a decoupling mode, the middleware console is installed on the first device, the first target middleware server is installed on the second device, and an operator initiates access to the middleware console on the third device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011591587.XA CN112738091B (en) | 2020-12-29 | 2020-12-29 | Method and device for interaction between middleware console and middleware server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011591587.XA CN112738091B (en) | 2020-12-29 | 2020-12-29 | Method and device for interaction between middleware console and middleware server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112738091A CN112738091A (en) | 2021-04-30 |
| CN112738091B true CN112738091B (en) | 2022-11-29 |
Family
ID=75607597
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011591587.XA Active CN112738091B (en) | 2020-12-29 | 2020-12-29 | Method and device for interaction between middleware console and middleware server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112738091B (en) |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2390348A1 (en) * | 2002-06-10 | 2003-12-10 | Ibm Canada Limited-Ibm Canada Limitee | Systems, methods and computer programs for implementing and accessing webservices |
| CN101959119A (en) * | 2009-07-21 | 2011-01-26 | 上海扣贝网络科技有限公司 | Agent-based mobile internet information exchange method |
| CN102457766B (en) * | 2010-10-18 | 2014-10-01 | Tcl集团股份有限公司 | Method for checking access authority of Internet protocol television |
| CN105635051B (en) * | 2014-10-29 | 2020-07-03 | 腾讯科技（深圳）有限公司 | Data interaction method, device and system |
| CN105897663A (en) * | 2015-01-26 | 2016-08-24 | 阿里巴巴集团控股有限公司 | Method for determining access authority, device and equipment |
| CN105022290A (en) * | 2015-05-19 | 2015-11-04 | 重庆大学 | Method for implementing multi-type oscilloscope centralized control system based on middleware |
| CN109327535B (en) * | 2018-11-09 | 2022-02-22 | 郑州云海信息技术有限公司 | Database access method, system, middleware equipment and medium |
| CN110309669B (en) * | 2019-06-12 | 2023-10-20 | 创新先进技术有限公司 | Data labeling method, device and equipment |
-
2020
- 2020-12-29 CN CN202011591587.XA patent/CN112738091B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN112738091A (en) | 2021-04-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110647580B (en) | Distributed container cluster mirror image management main node, slave node, system and method | |
| EP2058748A1 (en) | Network connected terminal device authenticating method, network connected terminal device authenticating program and network connected terminal device authenticating apparatus | |
| CN109379336A (en) | A kind of uniform authentication method, distributed system and computer readable storage medium | |
| CN111586021B (en) | Remote office business authorization method, terminal and system | |
| CN110557318B (en) | Method for realizing safe remote operation of IOT equipment | |
| CN112448956B (en) | Authority processing method and device of short message verification code and computer equipment | |
| CN112714158A (en) | Transaction processing method, relay network, cross-link gateway, system, medium, and device | |
| CN111371787B (en) | Login registration method, device, system, server and medium for middle station service | |
| CN110138753B (en) | Distributed message service system, method, apparatus, and computer-readable storage medium | |
| US11005709B2 (en) | Method and a system for the deterministic autoconfiguration of a device | |
| CN111966422A (en) | Localized plug-in service method and device, electronic equipment and storage medium | |
| CN102347939A (en) | Software management method, device and system | |
| CN112738091B (en) | Method and device for interaction between middleware console and middleware server | |
| CN115840937B (en) | Control method and device and electronic equipment | |
| CN101272250A (en) | Client terminal access authentication method, system and device thereof | |
| CN114650231B (en) | Visual containerized union link point deployment method and system | |
| CN112130932B (en) | Single-instance operation method and device and electronic equipment | |
| CN114238262A (en) | Image distribution method, image distribution device, electronic device, and storage medium | |
| CN109379383B (en) | Virtual private network VPN client and implementation method | |
| US10574516B2 (en) | Management apparatus and shared network system | |
| CN116016509B (en) | Private cloud data processing method, device, equipment and storage medium | |
| CN110445798B (en) | DNS anti-hijacking method and device and electronic equipment | |
| JP2014053754A (en) | Validity verification method of certificate, certificate verification server and program | |
| CN110650125B (en) | Host device and method for mutual communication operation based on Pexpect | |
| KR102482151B1 (en) | System and method for transmitting and receiving data based on bridgehead network |
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 |