CN108845808B

CN108845808B - Middleware installation method and device, computer equipment and storage medium

Info

Publication number: CN108845808B
Application number: CN201810650549.3A
Authority: CN
Inventors: 黄桂钦
Original assignee: Ping An Technology Shenzhen Co Ltd
Current assignee: Ping An Technology Shenzhen Co Ltd
Priority date: 2018-06-22
Filing date: 2018-06-22
Publication date: 2020-09-29
Anticipated expiration: 2038-06-22
Also published as: WO2019242162A1; CN108845808A

Abstract

The embodiment of the invention provides a middleware installation method, a middleware installation device, computer equipment and a storage medium. The method comprises the following steps: acquiring related information of a server needing to install the middleware; according to the operating system information in the server configuration information, determining a first type of middleware matched with the operating system information from prestored middleware related information; according to the environment information of the server, determining a target middleware matched with the environment information of the server from the first class middleware matched with the operating system; setting a port number of the target middleware on the server for providing a service; and if an installation instruction is received, installing the target middleware into the server according to the set port number and the IP address of the server. The embodiment of the invention can simplify the installation process of the middleware and achieve the customized configuration and installation of the middleware.

Description

Middleware installation method and device, computer equipment and storage medium

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a middleware installation method and apparatus, a computer device, and a storage medium.

Background

When an enterprise adds a server, middleware generally needs to be installed on the server so that the server can run an application program to perform the functions of the server. At present, many middleware on the servers are installed by manual participation, for example, operation and maintenance personnel install the corresponding middleware on each newly added server one by one. Although some enterprises already have the function of installing the middleware software, the enterprises only need to simply install the middleware software, and many limitations exist, such as manual intervention is needed in some steps, and customized configuration and installation of the middleware cannot be achieved.

Disclosure of Invention

The embodiment of the invention provides a middleware installation method, a device, computer equipment and a storage medium, which can achieve customized configuration and installation of a middleware.

In a first aspect, an embodiment of the present invention provides a middleware installation method, where the method includes:

and acquiring relevant information of a server needing to install the middleware. The relevant information of the server comprises environment information where the server is located, configuration information of the server and an IP address of the server;

according to the operating system information in the configuration information, determining a first type of middleware matched with the operating system information from prestored middleware related information;

determining a target middleware matched with the environment information of the server from the first type of middleware for recommendation according to the environment information of the server;

judging whether the user accepts the recommended target middleware or not;

if the user accepts the recommended target middleware, setting a port number of the target middleware on the server for providing service;

and if an installation instruction is received, installing the target middleware into the server according to the set port number and the IP address of the server.

In a second aspect, an embodiment of the present invention provides a middleware installation apparatus, which includes a unit for executing the middleware installation method according to the first aspect.

In a third aspect, an embodiment of the present invention provides a computer device, where the computer device includes a memory and a processor connected to the memory;

the memory is used for storing a computer program, and the processor is used for executing the computer program stored in the memory to execute the middleware installation method according to the first aspect.

In a fourth aspect, an embodiment of the present invention provides a storage medium, where a computer program is stored, where the computer program includes program instructions, and when the program instructions are executed by a processor, the middleware installation method described in the first aspect is implemented.

According to the embodiment of the invention, the related information of the server needing to be provided with the middleware is obtained, the target middleware matched with the related information of the server is determined from the pre-stored related information of the middleware, and if the user receives the target middleware, the target middleware is provided for being provided with the server. The embodiment can simplify the installation process and achieve the customized configuration and installation of the middleware.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a schematic diagram of an application scenario provided by an embodiment of the present invention;

FIG. 2 is a schematic flow chart illustrating a middleware installation method according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of a middleware installation configuration interface provided by an embodiment of the present invention;

FIG. 4 is a sub-flowchart of a middleware installation method according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a middleware installation schedule provided by an embodiment of the present invention;

FIG. 6 is a schematic view of another sub-flow of a middleware installation method according to an embodiment of the present invention;

fig. 7 is a schematic block diagram of a middleware installation apparatus provided by an embodiment of the present invention;

FIG. 8 is a schematic block diagram of a mounting unit provided by an embodiment of the present invention;

FIG. 9 is a schematic block diagram of an add unit provided by an embodiment of the present invention;

FIG. 10 is a schematic block diagram of a computer device provided by an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. 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 invention.

Middleware (middleware) mentioned in the embodiments of the present invention is a large class of basic software, belongs to the category of reusable software, and is intermediate between operating system software and application software of a user. The middleware is arranged on an operating system, a network and a database and on the lower layer of application software, and is generally used for providing an operation and development environment for the application software on the upper layer of the middleware, and helping a user to flexibly and efficiently develop and integrate the complex application software.

Fig. 1 is a schematic diagram of an application scenario provided in an embodiment of the present invention. In the application scenario shown in fig. 1, a middleware automation installation platform (corresponding to a web server) and a server are respectively included. The operating system of the server may be a liunx operating system, an OS operating system, or a windows operating system. In the automatic middleware installation platform, the related information of different middleware can be added according to the requirements of enterprises, and the related information of different middleware is taken as the pre-stored related information of the middleware. Wherein, different middleware comprises different versions of middleware. It is to be understood that there are a number of different types of middleware, and that there may be a number of different versions in each type of middleware. After relevant information of the middleware is added to the middleware automation installation platform, relevant information of a server needing to install the middleware is added, wherein the relevant information of the server comprises environment information where the server is located, configuration information of the server, IP address of the server and the like. In other embodiments, if the relevant information of the server to which the middleware needs to be installed already exists, the relevant information of the server is directly acquired. And determining a matched target middleware from the prestored middleware related information for recommendation according to the environment information of the server and the configuration information of the server. And judging whether the user accepts the recommended target middleware, if the user does not accept the recommended target middleware, receiving the middleware selected by the user, and taking the middleware selected by the user as the target middleware. Setting a port number of the target middleware on the server for providing the service. And finally, if an installation instruction is received, installing the target middleware into the server by one key according to the IP address of the server and the set port number. In the one-key installation process, if installation abnormity occurs and the like, error reporting information is fed back to a user, and meanwhile, the installation progress can be displayed for the user, so that the user can know the installation progress conveniently. The scheme determines a matched target middleware from the prestored middleware related information according to the server related information, and installs the target middleware into the server by one key, thereby simplifying the installation process, matching the installation version of the middleware according to the server related information, and achieving the customized configuration and installation of the middleware.

The following method embodiments provided by the present invention operate in a middleware automation installation platform.

Fig. 2 is a schematic flowchart of a middleware installation method according to an embodiment of the present invention. The method comprises the following steps S201-S207.

S201, acquiring relevant information of a server needing to install the middleware. The relevant information of the server comprises environment information where the server is located, configuration information of the server and an IP address of the server.

The environment information of the server comprises a network environment, an application environment and an application scene. The application environment includes a test environment, a development environment, a production environment (a docking external system), cluster information of servers corresponding to the test environment, the development environment, and the production environment, and the like. The network environment includes network architecture, requested instances, concurrency, etc. The application scenarios include https encryption transmission, proxy forwarding and the like, and are different according to different functions realized by different servers. The configuration information of the server includes an operating system of the server, a version of the operating system, and the like. The operating system includes a windows operating system, a liunx operating system, an OS operating system, and the like.

Specifically, the step S201 of acquiring the relevant information of the server to which the middleware needs to be installed includes: judging whether a server needing to install the middleware exists or not; if a server needing to install the middleware exists, acquiring related information of the server; and if the server needing to install the middleware does not exist, adding the related information of the server. Whether the server already exists may be determined based on the IP address of the server. If the IP address of the server is input in the input box, and if the input is detected to be finished (for example, the input cursor is not in the input box or the total number of input characters reaches the number of characters corresponding to the IP address), whether the server exists is determined according to the IP address of the server. The number of the servers to be installed with the middleware may be one or multiple, and then the related information of one or more servers is correspondingly acquired. It is to be understood that the middleware is installed on one or more different servers simultaneously. The middleware is installed on the servers in batches, so that the middleware does not need to be installed on each server needing to be installed, the time, the labor cost and the corresponding workload are greatly saved, and the efficiency of installing the middleware is improved.

S202, according to the operating system information in the server configuration information, determining a first type of middleware matched with the operating system information from the prestored middleware related information.

The related information of the middleware comprises middleware installation software, application environment matched with the middleware installation software, application scenes, an operating system and other information. The middleware installation software comprises a middleware installation package, a configuration file, a middleware monitoring package and the like. The middleware monitoring package is used for monitoring the middleware, such as monitoring the running state of the middleware, for example, detecting whether the middleware is available or not, whether the quantity of requested downloading of the middleware is abnormally increased or not, or whether the middleware is abnormally attacked by hackers and the like; the configuration file comprises a version, environment resources, optimized parameter configuration and the like corresponding to the middleware. The environment resource refers to some environment resources that need to be possessed by the operating system before the corresponding middleware is installed, for example, some function libraries that need to be possessed by the operating system, and the environment resource can enable the middleware to normally run on the operating system after being installed. For example, the environment resources corresponding to the nginx middleware include a gcc (gnu Compiler collection) Compiler, C + +, a pcre library, a zlib library, an OpenSSL library, and the like.

Specifically, according to the operating system information in the server configuration information, determining a first type of middleware matching the operating system information from the pre-stored middleware related information, that is, step S202, includes: judging whether the obtained operating systems of one or more servers are the same according to the operating system information in the server configuration information; if the servers are not the same operating system, deleting the servers corresponding to the different operating systems so as to enable the rest servers to have the same operating system; and if the operating systems are the same, selecting the first type of middleware matched with the operating systems from the prestored related information of the middleware. It can be understood that if only one server needs to install the middleware, the middleware matched with the server operating system is directly selected and installed from the pre-stored related information of the middleware, and if a plurality of servers need to be installed, the operating systems of the plurality of servers need to be the same, and the middleware of the same type can be installed in batch.

S203, according to the environment information of the server, determining a target middleware matched with the environment information of the server from the first type middleware for recommendation.

The target middleware is the middleware which is matched with the operating system information of the server and the environment information of the server.

Specifically, step S203 includes: finding out the middleware matched with the environment information of the server from the first type of middleware according to the environment information of the server; judging whether a plurality of middleware matched with the environment information of the server exist or not; if the number of the middleware is multiple, selecting one middleware from the multiple middleware according to a preset rule, and recommending the selected middleware serving as a target middleware matched with the environment information where the server is located; and if one middleware exists, the middleware is taken as a target middleware matched with the environment information where the server is located for recommendation. If there are multiple pieces of middleware matched with the environment information where the server is located, it can be understood that the middleware matched with the environment information where the server is located has multiple different versions, and the multiple different versions are all matched with the environment information where the server is located. Wherein, select a middleware from a plurality of middleware according to preset rule, include: selecting one middleware from a plurality of middleware according to the principle of the highest version; or selecting one middleware from the plurality of middleware according to the principle of highest installation rate; or randomly selecting one middleware from a plurality of middleware according to a random principle; or randomly selecting one middleware from a plurality of middleware according to the principle of combining versions and installation rates; or displaying a plurality of middleware, and receiving one middleware selected by a user from the plurality of middleware; or to select one from a plurality of middleware components according to other suitable principles. And the selected middleware is taken as target middleware matched with the environment information where the server is located.

And S204, judging whether the user accepts the recommended target middleware or not.

In this embodiment, the recommended target middleware is displayed in a web interface (e.g., an installation configuration interface) of the middleware automation installation platform, specifically, in an input box or a selection box corresponding to a middleware field displayed in the installation configuration interface. If the fact that the user edits the data in the input box or the selection box or deletes the data is detected, determining that the user does not accept the recommended target middleware; otherwise, determining that the user accepts the recommended target middleware. The editing may be understood as adding, deleting or modifying data in the input box or the selection box, and if only a cursor is placed in the input box or the selection box without causing any other operation, it is regarded that no editing is performed.

And S205, if the user does not accept the recommended target middleware, receiving the middleware selected by the user, and taking the middleware selected by the user as the target middleware.

The receiving of the middleware selected by the user, taking the middleware selected by the user as the target middleware, includes: receiving the middleware input by a user in an input box corresponding to the middleware field, and taking the middleware input by the user as target middleware; or displaying the middleware matched with the server related information in the selection frame corresponding to the middleware field for the user to select, receiving the middleware selected by the user in the selection frame corresponding to the middleware field, and taking the middleware selected by the user as the target middleware.

S206, setting the port number of the target middleware on the server for providing the service.

And if the user accepts the recommended target middleware or the user does not accept the recommended target middleware, setting a port number of the target middleware on the server for providing service after receiving the target middleware selected by the user. Port numbers refer to ports in the TCP/IP protocol, and range from 0 to 65535, such as 80 ports for browsing web services, 21 ports for FTP services, and so on. A terminal having an IP address can provide many network services such as Web service, FTP service, SMTP service, etc. These services can be implemented by 1 IP address, and the relationship of the IP address to the network service is a one-to-many relationship, so that different services are actually distinguished by "IP address + port number".

If there are multiple servers on which the target middleware needs to be installed, the step S206 of setting a port number of the target middleware on the server for providing a service includes: judging whether an identifier using different port numbers is received; if receiving the mark using different port numbers, calling an interface for setting a plurality of port numbers; respectively setting port numbers used for providing services on a plurality of servers through the interfaces; if the identifiers using different port numbers are not received, the port numbers of the servers for providing the service are set to be the same port number. If a relevant button of 'using different port numbers' is displayed on a web interface (such as an installation configuration interface) of the middleware automation installation platform, if the button is detected to be clicked by a user, and an identifier of using different port numbers is determined to be received, an interface for setting a plurality of port numbers is called, the interface can be represented by a plurality of input boxes, and data input in the plurality of input boxes corresponds to a plurality of servers one by one. And respectively setting port numbers of the target middleware for providing services on a plurality of servers by users through the interface. In general, the same port number is used by default, it being understood that servers that have installed the same target middleware are most likely to be servers in the same cluster, the port number of the target middleware for providing the servers generally using the same port number.

And S207, if the installation instruction is received, installing the target middleware into the server according to the set port number and the IP address of the server.

If the relevant buttons such as 'one-key installation', 'installation', and the like are displayed in the interface, if the situation that the user clicks the relevant buttons such as 'one-key installation', 'installation', and the like is detected, an installation instruction is received. And if the installation instruction is received, installing the target middleware into the server according to the set port number and the IP address of the server. The embodiment selects the middleware matched with the server according to the related information of the server, and realizes the customized configuration and installation of the middleware.

In an embodiment, if there are multiple servers that need to install the target middleware, each server corresponds to multiple different accounts, and different accounts correspond to different permissions. For example, the accounts administeror, user1, user2, etc. correspond to different rights respectively. Then, before receiving the installation instruction, the method further comprises: and setting an account of the server needing to install the target middleware. If receiving the installation instruction, installing the target middleware into the server according to the set port number and the IP address of the server, comprising: and if receiving an installation instruction, installing the target middleware under the account in the server according to the set port number and the IP address of the server.

Specifically, setting an account of the server on which the target middleware needs to be installed includes: judging whether an identifier for using different accounts is received; if receiving the identification of using different accounts, calling an interface for setting different accounts; setting accounts corresponding to a plurality of servers and needing to install the target middleware through the interfaces respectively; and if the identification of using different accounts is not received, setting the accounts, corresponding to the plurality of servers, of the target middleware to be installed as the same account or using a default account. If a related button of 'using different accounts' is displayed on a web interface (such as an installation configuration interface) of the middleware automation installation platform, if the button is detected to be clicked by a user, and an identifier of using different accounts is determined to be received, an interface for setting different accounts is called, the interface can be represented by a plurality of input boxes, and data input in the plurality of input boxes corresponds to a plurality of servers one by one. And setting accounts corresponding to the plurality of servers and needing to install the target middleware through the interface respectively. In most cases, a default account is used, e.g., the default account is an administeror. It should be noted that the account mentioned in this embodiment may include an account name and a password to indicate that the target middleware is installed under the account by entering the server through the account name and the password. In some cases, the password is considered null if it is not set.

FIG. 3 is a schematic diagram of a middleware installation configuration interface provided by an embodiment of the invention. The installation configuration interface includes information such as an IP address field, a recommended middleware field, a port number field, and a one-touch installation button of the corresponding server. Two pieces of IP address information, 10.20.123.98, 10.20.123.99, are displayed in the text boxes corresponding to the IP address fields of the servers. There is a recommended target middleware in the drop-down box corresponding to the recommended middleware field: nginx-1.12.1. Wherein nginx is the name of the target middleware, and 1.12.1 is the version corresponding to the target middleware. And an "x" number is correspondingly arranged in a text box corresponding to the IP address field of the server and a drop-down box corresponding to the recommended middleware field. Clicking on this "x" number may delete the corresponding entry, such as the nginx-1.12.1 target middleware. The nginx-1.12.1 target middleware is deleted, meaning that the user does not accept the recommended target middleware. After the nginx-1.12.1 target middleware is deleted, the corresponding middleware can be selected by clicking the drop-down box, and the selected middleware is taken as the target middleware. In a text box corresponding to the port number field, a port number, such as port number 6633, may be entered. Below the port number, there is a radio button that indicates: different port numbers are used. If it is detected that the radio button "use different port number" is clicked, an identification of using a different port number is received. After the setting is finished, the 'one-key installation' button is clicked, the target middleware corresponding to the middleware field is installed on the server corresponding to the two pieces of IP address information in a one-key mode, and the port number of the server for providing the service is set to 6633. It should be noted that fig. 3 is merely an example. It should be noted that all of the information shown in FIG. 3 is saved to the configuration file.

In other embodiments, host name information of the server may also be added in fig. 3 for easy memorization; other relevant information of the server, such as environment information where the server is located, configuration information of the server and the like, can also be added, so that a user can conveniently know the relevant information of the server, and further confirm the server needing to install the target middleware. In other embodiments, information such as a middleware administrator, middleware contacts, etc. may also be added. The middleware manager can understand the owner of the target middleware, namely the creator; the middleware contact can be understood as a worker who has the right to operate the target middleware, and the number of the middleware contact can be multiple. In other embodiments, account information of the target middleware to be installed corresponding to the server may also be added, so that the target middleware is installed to the account in the server according to the account information.

In one embodiment, as shown in FIG. 4, installing the target middleware into the server includes the following steps S401-S404.

S401, initializing the installation environment of the target middleware, and performing parameter verification on the installation environment of the target middleware.

The installation environment of the initialization target middleware comprises an account name and a password of an initialization server, environment resources for initializing the installation target middleware, configuration items in an initialization configuration file and the like. The account name and the password of the server are initialized, and it is understood that a plurality of accounts may be involved on one server, and the installation and use of the corresponding target middleware are specific authority of one account. Specifically, initializing the account name and password of the server includes: acquiring a pre-configured account name and a password; searching the pre-configured account name and password in the server; and if the preset configured account name and the preset configured password are found, entering a server according to the account name and the password. In most cases, a default account name and password are used, such as an administeror account name and a password of 123. The pre-configured account name and password may be a plurality of different account names and passwords pre-set on a web interface (such as an installation configuration interface) of the middleware automation installation platform, or may be default account names and passwords. Initializing the corresponding environment resource in the configuration file can be understood as that before installing each software, an operating system is required to have certain functions and environments, such as library functions required by the running of the target middleware. Initializing environment resources of the installation target middleware, comprising: acquiring a command required to be used for initializing environment resources, wherein if the command is a liunx system, the command required to be used is a liunx command; according to the command needed to be used, the preset environment resource is installed in the server, such as a system file library, a system package and the like involved by the environment resource. For example, during installation, some commands of the system, such as hostname, ping, etc., need to be used, so that the relevant system commands need to be initialized and prepared before installation, and system libraries and lib files need to be used for installing the software. Initializing the configuration items in the configuration file, namely initializing according to the configuration items in the configuration file.

The parameter verification of the installation environment of the target middleware comprises detecting whether the port number has conflict, such as whether the port number is occupied, detecting whether a system version meets requirements, allocating system resources for the installation of the target middleware, and the like. In which, detecting whether the system version meets the requirement may be understood as that some target middleware versions have requirements on the operating system of the server, and some software versions are based on higher operating system versions, such as redhat7 and centros 7. The system resources are allocated for the installation of the target middleware, and it can be understood that for the installation of any target middleware, the system resources of the relevant server, such as CPU, memory, IO, etc., need to be occupied, for example, how much memory is occupied, how many CPU cores are used, etc. For each target middleware, there is the lowest resource allocation data and the best resource allocation data for starting the target middleware, and if the server has insufficient resources left to start the target middleware, the target middleware should not be allowed to be installed on the server. Specifically, allocating system resources for the installation of the target middleware includes: acquiring minimum resource allocation data and optimal resource allocation data preset by a target middleware; judging whether the residual resource data of the server is larger than the lowest resource allocation data; if the resource allocation data is not larger than the lowest resource allocation data, sending a prompt to indicate that the server resources are insufficient, which means that the system resources are unsuccessfully allocated for the installation of the target middleware; if the resource allocation data is larger than the lowest resource allocation data, judging whether the resource allocation data is larger than the optimal resource allocation data; if the resource allocation data is larger than the optimal resource allocation data, allocating the corresponding resource in the optimal resource allocation data for the target middleware; and if the resource allocation data is not larger than the optimal resource allocation data, allocating the corresponding resource in the lowest resource allocation data for the target middleware. It should be noted that the above-mentioned contents of initializing the installation environment of the target middleware and performing parameter check on the installation environment of the target middleware are only examples, and other contents may be involved in other embodiments. Meanwhile, it should be noted that the above-mentioned contents involved in initializing the installation environment of the target middleware and performing parameter check on the installation environment of the target middleware do not limit the specific execution order. The specific execution order can be determined according to actual requirements.

S402, if the initialization of the installation environment of the target middleware is successful, the target middleware installation software is uploaded to the server through parameter inspection of the target middleware installation environment.

And S403, installing the target middleware installation package in the target middleware installation software in the server. Specifically, analyzing a target middleware installation package to generate a target middleware installation package script; and executing the target middleware installation package script.

S404, synchronizing the installation information to a configuration file corresponding to the target middleware.

The installation information includes installation completion time, relevant information of the server, the target middleware, the set port number of the target middleware for providing service, server resources occupied by the target middleware corresponding to the version, and the like. In other embodiments, the installation information further includes information such as the set account number, the middleware administrator, the middleware contact, and the like. It should be noted that the configuration file mentioned herein includes a configuration file in the server (the target middleware installation software is uploaded to the server, and the target middleware installation software includes the configuration file, so the configuration file is involved in the server), and also includes a configuration file included in the installation information table in the middleware automation installation platform. When the installation is completed, the contents of the configuration file included in the installation information table are consistent with the contents of the configuration file in the server.

The above steps S401 to S404 are procedures for installing the target middleware on the server. Therefore, the middleware is automatically installed, and the flow of installing the middleware is simplified.

In the process of installing the target middleware, the installation progress can be shown, so that a user can conveniently know the installation progress. FIG. 5 is a schematic diagram illustrating installation progress of the target middleware. The method comprises the following four steps: recording information, initializing, uploading target middleware installation software, installing target middleware (execution script) and a synchronous configuration file, wherein the recording information refers to information set in a record installation configuration interface, and the steps of initializing, uploading target middleware installation software, installing target middleware (execution script) and the synchronous configuration file correspond to the steps S401-S404. Displaying, behind the recorded information: finishing the execution; after initialization: in execution; and (3) displaying the installation software of the uploading target middleware, the installation target middleware (execution script) and the synchronous configuration file at the back: waiting for execution. It should be noted that this installation schedule is merely an example. In other embodiments, in "executing", the progress of step execution, such as executing 50% data, may also be included; the content of the specific execution can also be displayed according to the actual execution situation, for example, in the "execution", data such as "detecting whether the port conflicts" can be substituted. In other embodiments, only the steps that are specifically being executed may be displayed on the interface, and none of the other steps may be displayed.

During installation of the target middleware, anomalies are also captured. When any abnormity occurs in the installation process, prompt is carried out so as to improve the experience of the user.

After the target middleware is installed, the installation information is stored in an installation information table on the middleware automation installation platform. The target middleware for installation and related installation information can be queried on the middleware automation installation platform. The installation information obtained as a result of the query is shown in table 1. In table 1, there are data items of target middleware, server information, server IP, port number, installation status, cluster/configuration, and the like. For example, the first row of information respectively comprises: nginx-1.12.1, environment information of the server, 10.20.123.98, 6633, modification, successful installation, cluster information and configuration files. The underlined text in table 1 indicates that the relevant information can be viewed or edited after clicking. For example, clicking "the environment information of the server" can check the environment information of the server, "clicking" modify "can modify the port number information, clicking" the cluster information "can check the cluster to which the server belongs, clicking" the configuration file "can check the configuration file corresponding to the target middleware and modify the information in the corresponding configuration file, and checking the server resources and the like occupied by the target middleware corresponding to the version in the configuration file. In this embodiment, the queried information further includes information such as installation time, which is not shown in table 1. In other embodiments, the installation information may also include other content, such as a middleware administrator, middleware contacts, and the like.

Table 1 installation information obtained by query

In other embodiments, before step S202, the method further comprises: and adding relevant information of the middleware. As shown in fig. 6, adding relevant information of the middleware includes: the following steps S601-S605.

S601, under the same operating system and under the environment resource corresponding to the middleware, the middleware of different versions is subjected to pressure test under different parameter configurations and different application environments, wherein the different parameter configurations correspond to different application scenes.

S602, selecting a middleware with a better/optimal pressure test result according to different parameter configurations, different application environments, pressure test results corresponding to the middleware with different versions and demand information of the server, and adjusting parameters corresponding to the middleware according to the demand information of the server to obtain the optimized parameter configuration, wherein the demand information of the server comprises environment information where the server is located, namely the application environment, the application scene and the network environment. It can be understood that, according to different parameter configurations corresponding to the middleware and pressure test results in different application environments, a parameter collocation most suitable for the environment information where the server is located is selected to obtain the adjusted parameter configuration and the corresponding middleware, and the adjusted parameter configuration and the corresponding middleware are stored. The environment information which is most suitable for the server, the adjusted parameter configuration and the corresponding middleware may be one or more. The pressure test result is better, and the pressure test result corresponding to the preset number at the top of the rank from high to low is taken as the better pressure test result. And if only one pressure test result is available, selecting the pressure test result as a comparative pressure test result. The middleware corresponding to a better pressure test result is stable and has proper performance. The pressure test result comprises forwarding capacity, consumed server resources and the like corresponding to the middleware of different versions under the same concurrency. For parameter adjustment, for example, for nginx middleware, when an application scenario relates to https encrypted transmission, an SSL module in the nginx middleware parameters needs to be opened; the application scene is that the nginx is taken as a static state, and when uploading and downloading of a large number of files are involved, a file compression function of the nginx middleware parameter is opened; and if the application scene relates to proxy forwarding, opening a proxy forwarding function of the nginx middleware parameter, and the like. And if the application scene of the server comprises https encrypted transmission, proxy forwarding and the like, opening SSL module parameters and proxy forwarding parameters in the nginx middleware. According to the method, the middleware is subjected to pressure test under different parameter configurations and different application scenes under the environment resource, and then parameters are adjusted according to the pressure test result and the demand information of the server to obtain the optimized parameter configuration, so that the middleware meets the requirements of enterprises, and the customized configuration of the middleware and the performance optimization configuration of the middleware are achieved.

And S603, writing the adjusted parameter configuration into a configuration file corresponding to the version corresponding to the middleware.

S604, storing the configuration file, the middleware installation package with the corresponding version and the middleware monitoring package as corresponding middleware installation software.

S605, storing information of application environment, application scene, operating system and the like which correspond to the middleware installation software and are matched with the middleware installation software into related information of the middleware so as to complete adding and storing of the related information of the middleware under the operating system.

The above steps S601-S605 are executed to complete the addition and saving of the related information of different corresponding middleware under multiple operating systems, and the saved related information of the middleware is taken as the pre-stored related information of the middleware.

It can be understood that the middleware related information stored in the middleware automation installation platform is the middleware related information which is screened after the pressure test and is suitable for enterprise requirements. The middleware related information achieves customized configuration of the middleware and performance optimization configuration of the middleware. And selecting the middleware which accords with the related information of the current server from the middleware which achieves the customized configuration and the performance optimization configuration for installation, thereby achieving the customized installation of the middleware.

In the process of subsequent development, if new middleware or a new middleware version is involved, the new middleware or the new middleware version is saved into the relevant middleware information in the middleware automation installation platform for subsequent installation and use.

Fig. 7 is a schematic block diagram of a middleware installation apparatus according to an embodiment of the present invention. The device is applied to an automatic middleware installation platform. As shown in fig. 7, the apparatus 70 includes an acquisition unit 701, a system matching unit 702, an environment matching unit 703, a determination unit 704, a reception unit 705, a port setting unit 706, and an installation unit 707.

An obtaining unit 701, configured to obtain information about a server on which the middleware needs to be installed. The relevant information of the server comprises environment information where the server is located, configuration information of the server and an IP address of the server.

Specifically, the acquisition unit 701 includes: the server comprises an existence judging unit, a server obtaining unit and a server adding unit. The existence judging unit is used for judging whether a server needing to install the middleware exists or not, for example, the IP address of the server is input in the input box, and if the input is detected to be finished (for example, the input cursor is not in the input box or the total number of input characters reaches the number of characters corresponding to the IP address), whether the server exists or not is determined according to the IP address of the server. And the server acquisition unit is used for acquiring the relevant information of the server if the server needing to install the middleware exists. And the server adding unit is used for adding the relevant information of the server if the server needing to install the middleware does not exist. The number of the servers to be installed with the middleware may be one or multiple, and then the related information of one or more servers is correspondingly acquired.

A system matching unit 702, configured to determine, according to the operating system information in the server configuration information, a first type of middleware matching the operating system information from pre-stored middleware related information.

Specifically, the system matching unit 702 includes: the system comprises an operating system judging unit, a deleting unit and a system selection matching unit. The operating system judging unit is used for judging whether the acquired operating systems of the one or more servers are the same operating system or not according to the operating system information in the server configuration information. And the deleting unit is used for deleting the servers corresponding to the different operating systems if the acquired operating systems of one or more servers are not the same operating system, so that the rest servers have the same operating system. And the system selection matching unit is used for selecting the first type of middleware matched with the operating system from the prestored middleware related information if the operating systems of one or more servers are the same operating system.

An environment matching unit 703 is configured to determine, according to the environment information where the server is located, a target middleware that matches the environment information where the server is located from the first class middleware to recommend the target middleware.

Specifically, the environment matching unit 703 includes: the device comprises a matching search unit, a matching judgment unit and an environment selection matching unit. The matching search unit is used for searching the middleware matched with the environment information of the server from the first type of middleware according to the environment information of the server. And the matching judgment unit is used for judging whether a plurality of middleware matched with the environment information of the server exist. And the environment selection matching unit is used for selecting one middleware from the plurality of middleware according to a preset rule if the number of the middleware matched with the environment information of the server is multiple, and using the selected middleware as a target middleware matched with the environment information of the server for recommendation. And the environment selection matching unit is also used for recommending the middleware serving as a target middleware matched with the environment information of the server if one middleware matched with the environment information of the server exists.

A judging unit 704, configured to judge whether the user accepts the recommended target middleware.

The receiving unit 705 is configured to receive the middleware selected by the user and use the middleware selected by the user as the target middleware if the user does not accept the recommended target middleware.

A port setting unit 706, configured to set a port number used by the target middleware to provide a service on the server after receiving the target middleware selected by the user if the user accepts the recommended target middleware or the user does not accept the recommended target middleware.

Specifically, if there are a plurality of servers to which the target middleware needs to be installed, the port setting unit 706 includes: the device comprises a port identification judging unit, a port interface calling unit and a port number setting unit. The port identification judging unit is used for judging whether the identification using different port numbers is received. And the port interface calling unit is used for calling the interfaces with a plurality of port numbers if the identifiers using different port numbers are received. A port number setting unit, configured to set, through the interface, port numbers used for providing services on the multiple servers, respectively; and the port numbers used for providing services by the plurality of servers are set to be the same port number if the identifications using different port numbers are not received.

An installation unit 707, upon receiving the installation instruction, is configured to install the target middleware into the server according to the set port number and the IP address of the server.

In an embodiment, if there are multiple servers that need to install the target middleware, each server corresponds to multiple different accounts, and different accounts correspond to different permissions. For example, the accounts administeror, user1, user2, etc. correspond to different rights respectively. Then, the middleware mounting apparatus further includes: and the account setting unit is used for setting the account of the server needing to install the target middleware. And the installation unit is also used for installing the target middleware under the account in the server according to the set port number and the IP address of the server if the installation instruction is received.

Specifically, the account setting unit includes: the device comprises an account identification judging unit, an account interface calling unit and an installation account setting unit. The account identification judging unit is used for judging whether identifications using different accounts are received. And the account interface calling unit is used for calling the interfaces for setting different accounts if the identifiers for using different accounts are received. The installation account setting unit is used for respectively setting accounts which correspond to the plurality of servers and need to install the target middleware through the interfaces; and if the identification of using different accounts is not received, setting the accounts corresponding to the servers and needing to install the target middleware to be the same account or using a default account.

In one embodiment, as shown in fig. 8, the mounting unit 707 includes: an initialization unit 801, an upload unit 802, a middleware installation unit 803, and a synchronization unit 804.

An initialization unit 801 is configured to initialize an installation environment of the target middleware and perform parameter verification on the installation environment of the target middleware. The initialization unit 801 includes: the account initialization unit is used for initializing an account name and a password of the server; the environment resource initialization unit is used for initializing the environment resources of the installation target middleware; the configuration item initialization unit is used for initializing configuration items in the configuration file; a port number detection unit, configured to detect whether a conflict exists in a port number, such as whether the port number is occupied; the system version detection unit is used for detecting whether the system version meets the requirements or not; and the resource allocation unit is used for allocating system resources and the like for the installation of the target middleware.

Wherein, account initialization unit includes: the system comprises an account acquisition unit, an account searching unit and an account entering unit. The account acquisition unit is used for acquiring a pre-configured account name and a password. And the account searching unit is used for searching the pre-configured account name and the password in the server. And the account entering unit is used for entering the server according to the account name and the password if the preset configured account name and the password are found.

An environment resource initialization unit comprising: the device comprises a command acquisition unit and an environment resource installation unit. The command obtaining unit is configured to obtain a command that needs to be used to initialize an environment resource, where the command that needs to be used is a liunx command if the environment resource is a liunx system. And the environment resource installation unit is used for installing preset environment resources into the server according to the command required to be used, such as a system file library, a system package and the like.

A resource allocation unit comprising: the device comprises an allocation data acquisition unit, a resource judgment unit, a prompt unit, an optimal resource allocation unit and a lowest resource allocation unit. The allocation data acquisition unit is used for acquiring the lowest resource allocation data and the optimal resource allocation data preset by the target middleware. And the resource judging unit is used for judging whether the residual resource data of the server is larger than the lowest resource allocation data. And the prompting unit is used for sending out a prompt to indicate that the server resources are insufficient if the residual resource data of the server is not greater than the lowest resource allocation data. And the resource judging unit is further used for judging whether the residual resource data of the server is larger than the optimal resource allocation data or not if the residual resource data of the server is larger than the lowest resource allocation data. And the optimal resource allocation unit is used for allocating the corresponding resource in the optimal resource allocation data to the target middleware if the residual resource data of the server is greater than the optimal resource allocation data. And the lowest resource allocation unit is used for allocating the corresponding resource in the lowest resource allocation data to the target middleware if the remaining resource data of the server is larger than the lowest resource allocation data and is not larger than the optimal resource allocation data.

The uploading unit 802 is configured to upload the target middleware installation software to the server if the initialization of the installation environment of the target middleware is successful and the parameter inspection of the target middleware installation environment is passed.

A middleware installation unit 803, configured to install the target middleware installation package in the target middleware installation software in the server. Specifically, the target middleware installation package is analyzed, and a target middleware installation package script is generated; and executing the target middleware installation package script.

A synchronizing unit 804, configured to synchronize the installation information to the configuration file corresponding to the target middleware.

In other embodiments, the middleware installation apparatus further includes an adding unit. The adding unit is used for adding the relevant information of the middleware.

Specifically, as shown in fig. 9, the adding unit 90 includes: a pressure test unit 901, a version parameter tuning unit 902, a configuration writing unit 903, a middleware holding unit 904, and an information holding unit 905.

The stress testing unit 901 is configured to perform stress testing on different versions of the middleware under different parameter configurations and different application environments in the same operating system and under environment resources corresponding to the middleware, where the different parameter configurations correspond to different application scenarios.

The version parameter tuning unit 902 is configured to select a middleware with a better/optimal pressure test result according to different parameter configurations, different application environments, pressure test results corresponding to the middleware with different versions, and requirement information of the server, and adjust parameters corresponding to the middleware according to the requirement information of the server to obtain tuned parameter configurations, where the requirement information of the server includes environment information where the server is located, that is, an application environment, an application scenario, and a network environment.

A configuration writing unit 903, configured to write the adjusted parameter configuration into a configuration file corresponding to the version corresponding to the middleware.

A middleware saving unit 904, configured to save the configuration file, the middleware installation package of the corresponding version, and the middleware monitoring package as corresponding middleware installation software.

An information saving unit 905, configured to save, to the relevant information of the middleware, information such as an application environment, an application scenario, and an operating system that matches the middleware installation software, corresponding to the middleware installation software, to complete addition and saving of the relevant information of the middleware under the operating system.

Through the above pressure test unit 901, the version parameter tuning unit 902, the configuration writing unit 903, the middleware storage unit 904, and the information storage unit 905, addition and storage of related information of different middleware under a plurality of operating systems can be completed.

The implementation process and the achieved beneficial effects of the above device embodiments can be referred to the corresponding description of the corresponding method embodiments.

The above-described apparatus may be implemented in the form of a computer program which is executable on a computer device as shown in fig. 10.

Fig. 10 is a schematic block diagram of a computer device according to an embodiment of the present invention. The device 100 includes a processor 102, memory, and a network interface 103 connected by a system bus 101, where the memory may include a non-volatile storage medium 104 and an internal memory 105.

The non-volatile storage medium 104 may store an operating system 1041 and computer programs 1042. The computer program 1042, when executed, may cause the processor 102 to perform a middleware installation method. The processor 102 is used to provide computing and control capabilities that support the operation of the overall device 100. The internal memory 105 provides an environment for running a computer program in a non-volatile storage medium, which, when executed by the processor 102, causes the processor 102 to perform the middleware installation method. The network interface 103 is used for network communication, such as receiving messages. Those skilled in the art will appreciate that the configuration shown in fig. 10 is a block diagram of only a portion of the configuration associated with the present application and does not constitute a limitation of the device 100 to which the present application is applied, and that a particular device 100 may include more or less components than those shown, or combine certain components, or have a different arrangement of components.

Wherein the processor 102 is configured to run a computer program stored in a memory to implement the steps of:

acquiring relevant information of a server needing to install middleware, wherein the relevant information of the server comprises environment information where the server is located, configuration information of the server and an IP address of the server; according to the operating system information in the configuration information, determining a first type of middleware matched with the operating system information from prestored middleware related information; determining a target middleware matched with the environment information of the server from the first type of middleware for recommendation according to the environment information of the server; judging whether the user accepts the recommended target middleware or not; if the user accepts the recommended target middleware, setting a port number of the target middleware on the server for providing service; and if an installation instruction is received, installing the target middleware into the server according to the set port number and the IP address of the server.

In an embodiment, when executing the installing the target middleware into the server, the processor 102 specifically executes:

initializing the installation environment of the target middleware, and performing parameter verification on the installation environment of the target middleware; if the initialization of the installation environment of the target middleware is successful, uploading target middleware installation software to a server through parameter inspection of the installation environment of the target middleware; installing a target middleware installation package in the target middleware installation software in a server; and synchronizing the installation information to the configuration file corresponding to the target middleware.

In an embodiment, the initializing the installation environment of the target middleware includes initializing an environment resource of the installation target middleware, and the processor 102 specifically executes, when executing the environment resource of the initialization installation target middleware:

acquiring a command required to be used for initializing environment resources; and installing preset environment resources into the server according to the command required to be used.

In an embodiment, before uploading the target middleware installation software to the server, the processor 102 further specifically performs:

acquiring minimum resource allocation data and optimal resource allocation data preset by the target middleware; if the residual resource data of the server is not larger than the lowest resource allocation data, prompting to show that the server resources are insufficient; if the residual resource data of the server is larger than the lowest resource allocation data and is larger than the optimal resource allocation data, allocating corresponding resources in the optimal resource allocation data to the target middleware; and if the residual resource data of the server is larger than the lowest resource allocation data and not larger than the optimal resource allocation data, allocating the corresponding resource in the lowest resource allocation data to the target middleware.

In an embodiment, if there are a plurality of servers on which the target middleware needs to be installed, when the processor 102 performs the setting of the port number of the target middleware on the server for providing the service, specifically:

judging whether an identifier using different port numbers is received; if receiving the mark using different port numbers, calling an interface for setting a plurality of port numbers; respectively setting port numbers used for providing services on a plurality of servers through the interfaces; if the identifiers using different port numbers are not received, the port numbers of the servers for providing the service are set to be the same port number.

In an embodiment, if there are a plurality of servers to which the middleware needs to be installed, when the processor 102 executes the operating system information in the configuration information and determines a first type of middleware matching the operating system information from pre-stored middleware related information, specifically:

judging whether the obtained operating systems of the plurality of servers are the same operating system or not according to the operating system information in the configuration information; if the servers are not the same operating system, deleting the servers corresponding to the different operating systems so as to enable the rest servers to have the same operating system; and if the operating systems are the same, selecting the first type of middleware matched with the operating systems from the prestored related information of the middleware.

In an embodiment, when the processor 102 executes the acquiring of the related information of the server on which the middleware needs to be installed, specifically:

judging whether a server needing to install the middleware exists or not; if a server needing to install the middleware exists, acquiring related information of the server; and if the server needing to install the middleware does not exist, adding the related information of the server.

In an embodiment, before executing the step of receiving the installation instruction, the processor 102 further specifically executes: setting an account of the server needing to install the target middleware; when executing the installation instruction, and installing the target middleware into the server according to the set port number and the IP address of the server, the processor 102 specifically executes: and if an installation instruction is received, installing the target middleware under the account in the server according to the set port number and the IP address of the server.

It should be understood that, in the embodiment of the present invention, the Processor 102 may be a Central Processing Unit (CPU), and the Processor may also be other general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

In another embodiment of the present invention, a storage medium is provided, the storage medium storing a computer program comprising program instructions, which when executed by a processor, implement the steps of:

In an embodiment, when the processor executes the installation of the target middleware into the server, the following is specifically implemented:

In an embodiment, the initializing the installation environment of the target middleware includes initializing an environment resource for installing the target middleware, and the processor specifically implements, when executing the initializing the environment resource for installing the target middleware:

In an embodiment, before the uploading the target middleware installation software to the server, the processor further specifically implements:

In an embodiment, if there are a plurality of servers on which the target middleware needs to be installed, when the processor performs the setting of the port number of the target middleware on the server for providing the service, the following is specifically implemented:

In an embodiment, if there are a plurality of servers to which the middleware needs to be installed, when the processor executes the operating system information in the configuration information and determines a first type of middleware matched with the operating system information from pre-stored middleware related information, the following is specifically implemented:

In an embodiment, when the processor executes the acquiring of the related information of the server on which the middleware needs to be installed, the following is specifically implemented:

In an embodiment, before the processor executes the installation instruction, the following is further specifically implemented: setting an account of the server needing to install the target middleware; when the processor executes the installation instruction and installs the target middleware into the server according to the set port number and the IP address of the server if the installation instruction is received, the following concrete steps are implemented: and if an installation instruction is received, installing the target middleware under the account in the server according to the set port number and the IP address of the server.

The storage medium may be a computer-readable storage medium. The storage medium may be an internal storage unit of the terminal according to any of the foregoing embodiments, for example, a hard disk or a memory of the terminal. The storage medium may also be an external storage device of the terminal, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, and the like provided on the terminal. Further, the storage medium may also include both an internal storage unit and an external storage device of the terminal.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus, device and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and the division of the unit is only one logical function division, and other division manners may be available in actual implementation. It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the apparatuses, the devices, the units and the storage media described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again. While the invention has been described with reference to specific embodiments, the invention is not limited thereto, and various equivalent modifications and substitutions can be easily made by those skilled in the art within the technical scope of the invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A middleware installation method, comprising:

acquiring relevant information of a server needing to install middleware, wherein the relevant information of the server comprises environment information where the server is located, configuration information of the server and an IP address of the server;

judging whether the user accepts the recommended target middleware or not;

2. The method of claim 1, wherein installing the target middleware into the server comprises:

initializing the installation environment of the target middleware, and performing parameter verification on the installation environment of the target middleware;

if the initialization of the installation environment of the target middleware is successful, uploading target middleware installation software to a server through parameter inspection of the installation environment of the target middleware;

installing a target middleware installation package in the target middleware installation software in a server;

and synchronizing the installation information to the configuration file corresponding to the target middleware.

3. The method of claim 2, wherein initializing the installation environment of the target middleware comprises initializing environment resources of the target middleware, and wherein initializing environment resources of the target middleware comprises:

acquiring a command required to be used for initializing environment resources;

and installing preset environment resources into the server according to the command required to be used.

4. The method of claim 2, wherein prior to the uploading the target middleware installation software into the server, the method further comprises:

acquiring minimum resource allocation data and optimal resource allocation data preset by the target middleware; wherein the target middleware is configured with minimum resource allocation data and optimum resource allocation data to launch the target middleware;

if the residual resource data of the server is not larger than the lowest resource allocation data, prompting to show that the server resources are insufficient;

if the residual resource data of the server is larger than the lowest resource allocation data and is larger than the optimal resource allocation data, allocating corresponding resources in the optimal resource allocation data to the target middleware;

and if the residual resource data of the server is larger than the lowest resource allocation data and not larger than the optimal resource allocation data, allocating the corresponding resource in the lowest resource allocation data to the target middleware.

5. The method of claim 1, wherein if there are more servers on which the target middleware needs to be installed, the setting of the port number of the target middleware on the servers for providing services comprises:

judging whether an identifier using different port numbers is received;

if receiving the mark using different port numbers, calling an interface for setting a plurality of port numbers;

respectively setting port numbers used for providing services on a plurality of servers through the interfaces;

if the identifiers using different port numbers are not received, the port numbers of the servers for providing the service are set to be the same port number.

6. The method according to claim 1, wherein if there are a plurality of servers to which the middleware needs to be installed, determining a first type of middleware matching with the operating system information from pre-stored middleware related information according to the operating system information in the configuration information comprises:

judging whether the obtained operating systems of the plurality of servers are the same operating system or not according to the operating system information in the configuration information;

if the servers are not the same operating system, deleting the servers corresponding to the different operating systems so as to enable the rest servers to have the same operating system;

and if the operating systems are the same, selecting the first type of middleware matched with the operating systems from the prestored related information of the middleware.

7. The method of claim 1, wherein prior to receiving the installation instruction, the method further comprises:

setting an account of the server needing to install the target middleware;

if receiving an installation instruction, installing the target middleware into the server according to the set port number and the IP address of the server, including: and if an installation instruction is received, installing the target middleware under the account in the server according to the set port number and the IP address of the server.

8. A middleware installation arrangement comprising means for performing the method according to any one of claims 1-7.

9. A computer device, comprising a memory, and a processor coupled to the memory;

the memory is used for storing a computer program; the processor is configured to execute a computer program stored in the memory to perform the method of any of claims 1-7.

10. A storage medium, characterized in that the storage medium stores a computer program comprising program instructions which, when executed by a processor, implement the method according to any one of claims 1-7.