Method for calling operation and maintenance tool by client-free remote desktop gateway

Abstract

The invention discloses a method for calling an operation and maintenance tool by a client-free remote desktop gateway, which belongs to the field of network operation and maintenance, and comprises the following steps of: calling operation and maintenance tool software through the client-free remote desktop gateway, after an account is automatically filled and configured on behalf, notifying the operation and maintenance tool software started by Apphome by the client-free remote desktop gateway, creating a user by an Apphome internal service, an operation and maintenance tool software calling program is placed in a created user directory, operation and maintenance tool software is called, a client-side-free remote desktop gateway serves as an intermediate proxy gateway, and a visual interaction interface of the operation and maintenance tool software is returned to a management platform; and the management platform returns the visual interface information of the operation and maintenance tool software to the user browser client and finally presents the visual interface information to the user, and the user can carry out operation and maintenance operation through a visual interface. The problems that operation and maintenance tool software must be installed on a local computer of a user, and when operation and maintenance are needed, the user opens a corresponding operation and maintenance tool and needs to manually input an account number and a password of a connection target at the same time are solved.

Description

Technical Field

[0001] The present invention relates to the field of network operation and maintenance, and in particular to a method for a clientless remote desktop gateway to call an operation and maintenance tool. Background Art

[0002] With the rapid development of information technology and the Internet, the degree of informatization is getting higher and higher, and the technologies used in enterprise systems and services are becoming more and more large and complex. Enterprises have higher and higher demands for operation and maintenance management, and the operation and maintenance team needs to use a variety of operation and maintenance management tools to manage and monitor its huge systems and services.

[0003] In the traditional operation and maintenance mode, each operation and maintenance method requires the installation of a dedicated operation and maintenance client tool. The installation and maintenance costs are high, resources are occupied, learning costs are high, and integration is difficult. In order to solve these problems, you can consider using a unified operation and maintenance management platform or tool to integrate various operation and maintenance functions and provide a unified operation interface to reduce the workload of administrators and improve efficiency.

[0004] In terms of security, under the traditional operation and maintenance model, the use of dedicated operation and maintenance client tools usually requires users to provide an account and password for identity authentication, which may lead to some security risks.

[0005] In summary, each operation and maintenance method under the traditional operation and maintenance model requires the installation of a dedicated client tool. The operation and maintenance tools do not have a unified management and maintenance method, account security services cannot be guaranteed, and log and video audits cannot be performed. The clientless remote desktop gateway operation and maintenance tool call can provide a browser-based client unified entrance, unified account management, centralized management of operation and maintenance tools through virtualized containers, password filling for tool calls, and audit logs and videos. Summary of the invention

[0006] In view of the above-mentioned deficiencies in the prior art, the present invention provides a method for a clientless remote desktop gateway to call an operation and maintenance tool.

[0007] In order to achieve the above-mentioned object of the invention, the technical solution adopted by the present invention is: A method for a clientless remote desktop gateway to call an operation and maintenance tool comprises the following steps: S1. Obtain access rights to the target operation and maintenance account and log in, connect to the account that needs operation and maintenance, and make an operation and maintenance connection request; S2. After receiving the connection request, the management platform calls the target operation and maintenance tool and sends the complete operation and maintenance account information to Apphouse; S3. Prepare the operation and maintenance tools. Based on the prepared operation and maintenance tools, the management platform communicates in real time through the clientless remote desktop gateway and performs operation and maintenance operations through command interaction. S4. Record user operation logs, actively call the management platform interface to push records, and the clientless desktop gateway records the operation video. After the operation and maintenance operation is completed, the connection is disconnected and the ongoing operation and maintenance status is updated to the historical behavior status.

[0008] Furthermore, the S2 specifically includes the following steps: S21. Modify the configuration data of the operation and maintenance tool software before calling the operation and maintenance tool, and set the account information to be filled in; S22. Based on the received configuration data, check whether the parameters are compliant and complete, and check whether the called tool has been installed and the version is correct. If it is not installed or the version is incorrect, Apphouse downloads the correct operation and maintenance tool software from the management platform through a request; S23, Apphouse always waits for client connection requests, and establishes a communication session with the client when there is a request; S24. Apphouse hides the system desktop in the graphical interface and displays the graphical screen that only exists in the operation and maintenance tool software to the user, and authorizes the user to only have the authority to operate the operation and maintenance tool software; S25. Do not record the user input instructions before they are executed. When the user executes a new instruction, the changes in the operation and maintenance tool software log file are monitored and the changed content is read. The read content is transmitted to the management platform for storage after secondary analysis. The Apphouse virtualization tool software container does not record and store data.

[0009] Furthermore, S3 specifically includes the following steps: S31. Based on the preparation of the operation and maintenance tool software, the clientless remote desktop gateway of the management platform communication uses a long connection protocol for real-time interactive communication; S32, the management platform uses the specified protocol instructions in the interaction, and the clientless remote desktop gateway listens to request a connection and parses the content of the protocol instructions; S33. Based on the parsed instruction content, the clientless remote desktop gateway draws the image interface sent back by Apphouse and transmits operation events, while monitoring the connection and data interaction between the clientless remote desktop gateway and the management platform; S34. Parse the command data passed by the management platform and connect to Apphouse as a client, acting as an intermediate layer to perform data parsing between protocol interactions.

[0010] Furthermore, each protocol instruction in the S32 is a comma-delimited data followed by a terminating semicolon, wherein the first element of the instruction is the instruction opcode, and all subsequent elements are parameters of the instruction. Each element in the list has a positive integer length prefix, and the element value and the prefix are separated by a period.

[0011] Furthermore, the management platform or clientless remote desktop gateway at either end of the real-time communication in S3 can terminate the connection at any time by using the "disconnect" command. If a problem occurs in the management platform or the clientless remote desktop gateway, the clientless remote desktop gateway will send an "error" command to notify the management platform. The present invention has the following beneficial effects: 1. Call the operation and maintenance tool software in Apphouse through the clientless remote desktop gateway.

[0012] 2. Unified management and installation of operation and maintenance tool software to achieve client-free installation of operation and maintenance tool software.

[0013] 3. Automatically fill in the operation and maintenance account number, and centralize the hosting to ensure that account information is not lost.

[0014] 4. Apphouse automatically installs supported operation and maintenance tools.

[0015] 5. The virtualization container tool automatically installs supported operation and maintenance tools. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 Flowchart of a method for invoking an operation and maintenance tool for a clientless remote desktop gateway. DETAILED DESCRIPTION

[0017] The specific implementation modes of the present invention are described below so that those skilled in the art can understand the present invention. However, it should be clear that the present invention is not limited to the scope of the specific implementation modes. For those of ordinary skill in the art, as long as various changes are within the spirit and scope of the present invention as defined and determined by the attached claims, these changes are obvious, and all inventions and creations utilizing the concept of the present invention are protected.

[0018] A method for calling an operation and maintenance tool by a clientless remote desktop gateway, such as Figure 1 As shown, the following steps are included: S1. Obtain access rights to the target operation and maintenance account and log in, connect to the account that needs operation and maintenance, and make an operation and maintenance connection request; The user logs in to the management platform through multi-factor security authentication and checks whether he has the corresponding access rights to the target operation and maintenance account. If he does not have the authority, he needs to apply for it through the management platform. The user enters the operation and maintenance interface, selects the account to be operated and maintenance, and makes an operation and maintenance connection request.

[0019] S2. After receiving the connection request, the management platform calls the target operation and maintenance tool and sends the complete operation and maintenance account information to Apphouse; In this embodiment, the following steps are specifically included: S21. Modify the configuration data of the operation and maintenance tool software before calling the operation and maintenance tool, and set the account information to be filled in; The clientless remote desktop gateway calls the operation and maintenance tool software. After the account is automatically filled in and configured, the clientless remote desktop gateway notifies Apphouse to start the operation and maintenance tool software. The Apphouse internal service creates a user, and calls up the operation and maintenance tool software by placing the operation and maintenance tool software call program in the created user directory. The clientless remote desktop gateway acts as an intermediate proxy gateway and returns the visual interactive interface of the operation and maintenance tool software to the management platform. The management platform returns the visual interface information of the operation and maintenance tool software to the user's browser client and finally presents it to the user. The user can perform operation and maintenance operations through the visual interface.

[0020] S22. Based on the received configuration data, check whether the parameters are compliant and complete, and check whether the called tool has been installed and the version is correct. If it is not installed or the version is incorrect, Apphouse downloads the correct operation and maintenance tool software from the management platform through a request; The Apphouse virtualization tool software container uses two types of protocols to achieve external interaction. One type of protocol is the graphical interface interaction, which enables users to interact with the target operation and maintenance tool software through the graphical interface. The other type of protocol exchanges data with the interface of the Apphouse virtualization tool software container through the management platform, including operation and maintenance account configuration, files, monitoring, logs and other interface interactions.

[0021] S23, Apphouse always waits for client connection requests, and establishes a communication session with the client when there is a request; S24. Apphouse hides the system desktop in the graphical interface and displays the graphical screen that only exists in the operation and maintenance tool software to the user, and authorizes the user to only have the authority to operate the operation and maintenance tool software; S25. Do not record the user input instructions before they are executed. When the user executes a new instruction, the changes in the operation and maintenance tool software log file are monitored and the changed content is read. The read content is transmitted to the management platform for storage after secondary analysis. The Apphouse virtualization tool software container does not record and store data.

[0022] S3. Prepare the operation and maintenance tools. Based on the prepared operation and maintenance tools, the management platform communicates in real time through the clientless remote desktop gateway and performs operation and maintenance operations through command interaction. In this embodiment, the following steps are specifically included: S31. Based on the preparation of the operation and maintenance tool software, the clientless remote desktop gateway of the management platform communication uses a long connection protocol for real-time interactive communication; S32, the management platform uses the specified protocol instructions in the interaction, and the clientless remote desktop gateway listens to request a connection and parses the content of the protocol instructions; S33. Based on the parsed instruction content, the clientless remote desktop gateway draws the image interface sent back by Apphouse and transmits operation events, while monitoring the connection and data interaction between the clientless remote desktop gateway and the management platform; S34. Parse the command data passed by the management platform and connect to Apphouse as a client, acting as an intermediate layer to perform data parsing between protocol interactions.

[0023] Based on the preparation of the operation and maintenance tool software, the management platform communicates with the clientless remote desktop gateway using a long connection protocol for real-time interactive communication. The management platform uses the specified protocol instructions in the interaction, and the clientless remote desktop gateway listens to request a connection. The clientless remote desktop gateway will parse the content of the protocol instructions to know what operations the user needs to do with the remote server. The clientless remote desktop gateway draws the screen and transmits operation events for the image interface sent back by Apphouse, and monitors the connection and data interaction with the management platform. Parse the command data passed by the management platform, and connect to Apphouse as a client, acting as an intermediate layer to perform data parsing between protocol interactions.

[0024] The command interaction of the clientless remote desktop gateway, each command is a comma-delimited data followed by a terminating semicolon, where the first element of the command is the command opcode, and all subsequent elements are the parameters of the command. Each element in the list has a positive integer length prefix, and the element value and the prefix are separated by a period. This length represents the number of characters in the element value. Any number of complete commands constitute a message, which is sent from the management platform to the clientless remote desktop gateway, or from the clientless remote desktop gateway to the management platform. The commands sent by the management platform are usually control commands and events. The commands from the clientless remote desktop gateway to the management platform are usually image drawing commands, using the browser client as the display. The length prefix in each command element means that the parser can quickly jump from one command to another without traversing each character. The protocol interaction phase begins immediately after the connection is established. It starts with a "select" command sent by the client. The command tells the clientless remote desktop gateway which protocol to load, and responds with a "return" command to its protocol version and acceptable parameter names. After receiving the parameters, the client needs to respond with a list of supported command types and the values ​​of the available parameters. The clientless remote desktop gateway marks the connection successfully and then sends a "ready" command to enter the actual interaction phase. The sending and receiving of command data in the actual interaction phase is sent by one end and confirmed by the other end. The content sent by the sender requires the receiver to return a "confirmation" command. Either end's management platform or clientless remote desktop gateway can end the connection at any time and can use the "disconnect" connection command. If there is a problem with the management platform or the clientless remote desktop gateway, the clientless remote desktop gateway will send an "error" command to notify the management platform. S4. Record user operation logs, actively call the management platform interface to push records, and the clientless desktop gateway records the operation video. After the operation and maintenance operation is completed, the connection is disconnected and the ongoing operation and maintenance status is updated to the historical behavior status.

[0025] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0026] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0027] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0028] The present invention uses specific embodiments to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. At the same time, for those skilled in the art, according to the idea of ​​the present invention, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

[0029] Those skilled in the art will appreciate that the embodiments described herein are intended to help readers understand the principles of the present invention, and should be understood that the protection scope of the present invention is not limited to such specific statements and embodiments. Those skilled in the art can make various other specific variations and combinations that do not deviate from the essence of the present invention based on the technical revelations disclosed by the present invention, and these variations and combinations are still within the protection scope of the present invention.

Claims

1. A method for calling an operation and maintenance tool by a clientless remote desktop gateway, characterized in that: The steps include: S1. Obtain access rights to the target operation and maintenance account and log in, connect to the account that needs operation and maintenance, and make an operation and maintenance connection request; S2. After receiving the connection request, the management platform calls the target operation and maintenance tool and sends the complete operation and maintenance account information to Apphouse; S3. Prepare the operation and maintenance tools. Based on the prepared operation and maintenance tools, the management platform communicates in real time through the clientless remote desktop gateway and performs operation and maintenance operations through command interaction. S4. Record user operation logs, actively call the management platform interface to push records, and the clientless desktop gateway records the operation video. After the operation and maintenance operation is completed, the connection is disconnected and the ongoing operation and maintenance status is updated to the historical behavior status.

2. The method for calling an operation and maintenance tool by a clientless remote desktop gateway according to claim 1, characterized in that: The S2 specifically includes the following steps: S21. Modify the configuration data of the operation and maintenance tool software before calling the operation and maintenance tool, and set the account information to be filled in; S22. Based on the received configuration data, check whether the parameters are compliant and complete, and check whether the called tool has been installed and the version is correct. If it is not installed or the version is incorrect, Apphouse downloads the correct operation and maintenance tool software from the management platform through a request; S23, Apphouse always waits for client connection requests, and establishes a communication session with the client when there is a request; S24. Apphouse hides the system desktop in the graphical interface and displays the graphical screen that only exists in the operation and maintenance tool software to the user, and authorizes the user to only have the authority to operate the operation and maintenance tool software; S25. Do not record the user input instructions before they are executed. When the user executes a new instruction, the changes in the operation and maintenance tool software log file are monitored and the changed content is read. The read content is transmitted to the management platform for storage after secondary analysis. The Apphouse virtualization tool software container does not record and store data.

3. The method for calling an operation and maintenance tool by a clientless remote desktop gateway according to claim 1, characterized in that: The S3 specifically includes the following steps: S31. Based on the preparation of the operation and maintenance tool software, the clientless remote desktop gateway of the management platform communication uses a long connection protocol for real-time interactive communication; S32, the management platform uses the specified protocol instructions in the interaction, and the clientless remote desktop gateway listens to request a connection and parses the content of the protocol instructions; S33. Based on the parsed instruction content, the clientless remote desktop gateway draws the image interface sent back by Apphouse and transmits operation events, while monitoring the connection and data interaction between the clientless remote desktop gateway and the management platform; S34. Parse the command data passed by the management platform and connect to Apphouse as a client, acting as an intermediate layer to perform data parsing between protocol interactions.

4. The method for calling an operation and maintenance tool by a clientless remote desktop gateway according to claim 3, characterized in that: Each protocol instruction in the S32 is a comma-delimited data followed by a terminating semicolon, wherein the first element of the instruction is the instruction opcode, and all subsequent elements are parameters of the instruction. Each element in the list has a positive integer length prefix, and the element value and the prefix are separated by a period.

5. The method for calling an operation and maintenance tool by a clientless remote desktop gateway according to claim 3, characterized in that: The management platform or clientless remote desktop gateway at either end of the real-time communication in the S3 can terminate the connection at any time using the "disconnect" connection command. If a problem occurs with the management platform or the clientless remote desktop gateway, the clientless remote desktop gateway will send an "error" command to notify the management platform.

Images