CN111984372B - Data processing method and system - Google Patents
Data processing method and system Download PDFInfo
- Publication number
- CN111984372B CN111984372B CN202010837544.9A CN202010837544A CN111984372B CN 111984372 B CN111984372 B CN 111984372B CN 202010837544 A CN202010837544 A CN 202010837544A CN 111984372 B CN111984372 B CN 111984372B
- Authority
- CN
- China
- Prior art keywords
- service
- host
- managed
- configuration
- domain
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000003672 processing method Methods 0.000 title abstract description 23
- 238000013515 script Methods 0.000 claims abstract description 62
- 238000000034 method Methods 0.000 claims abstract description 56
- 238000012545 processing Methods 0.000 claims abstract description 15
- 230000007613 environmental effect Effects 0.000 claims abstract description 12
- 238000012544 monitoring process Methods 0.000 claims description 35
- 230000002159 abnormal effect Effects 0.000 claims description 14
- 230000006835 compression Effects 0.000 claims description 6
- 238000007906 compression Methods 0.000 claims description 6
- 238000012856 packing Methods 0.000 claims description 2
- 238000004806 packaging method and process Methods 0.000 claims 1
- 230000008569 process Effects 0.000 abstract description 30
- 238000004519 manufacturing process Methods 0.000 description 17
- 238000010586 diagram Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 208000019585 progressive encephalomyelitis with rigidity and myoclonus Diseases 0.000 description 2
- 230000004913 activation Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000009849 deactivation Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
- G06F9/45508—Runtime interpretation or emulation, e g. emulator loops, bytecode interpretation
- G06F9/45512—Command shells
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a data processing method and a data processing system, wherein configuration parameters matched with environmental parameters of a first host are obtained; creating a domain, a management service, a first node manager and a first device managed by the first node manager on a first host according to the configuration parameters, and creating a first managed service corresponding to the first device; configuring management service and first managed service according to preset service parameter configuration conditions; configuring Java virtual machine parameters of a first host and a first node manager; the method comprises the steps of respectively creating a management service, a start script and a stop script of a first managed service to finish the creation of the management service and the first managed service, so that parameters of each management service and each first managed service are consistent, the purpose of quickly creating uniform standard service is achieved, the consumption of manpower and time is reduced, the creation efficiency is improved, and errors in the creation process are reduced.
Description
Technical Field
The present invention relates to the field of computer networks, and in particular, to a data processing method and system.
Background
WebLogic is an application server manufactured by Oracle corporation, is one of the main Java (J2 EE) application server software in the commercial market, and is precisely a middleware based on JAVAEE architecture, and services can be created in equipment through WebLogic, so that the equipment can provide services, wherein the process of creating services in the equipment by WebLogic is as follows:
The user manually logs in the host computer where the management server is located, manually clicks and runs config. Sh under the Weblogic product installation directory, and starts the domain creation guide. The user creates a domain by gradually performing the following operations according to the prompt: selecting a component or a template of a domain, setting a name of the domain, setting a directory in which the domain is located, setting a user name and a password, setting an operation mode of the domain, setting a java development kit (Java Development kit, JDK) path, setting a monitoring address and a port of a management server, and the like.
In summary, the steps of the existing service creation process require user participation, increase the manpower and time consumption, and have the problems of low efficiency and easy error.
Disclosure of Invention
In view of the above, embodiments of the present invention provide a data processing method and system, so as to reduce the consumption of manpower and time, improve the creation efficiency, and reduce the errors occurring in the creation process.
To achieve the above object, an aspect of an embodiment of the present invention provides a data processing method, including:
Acquiring a first configuration parameter, a second configuration parameter, a third configuration parameter and a fourth configuration parameter which are matched with the environmental parameter of the first host;
Creating a domain and a management service on the first host according to the first configuration parameters, wherein the management service operates in the domain;
creating a first node manager on the first host according to the second configuration parameters;
Creating a first device managed by the first node manager according to the third configuration parameters, and creating a first managed service corresponding to the first device;
Configuring the management service and the first managed service according to preset service parameter configuration conditions;
Configuring Java virtual machine parameters of the first host and the first node manager according to the fourth configuration parameters so as to enable the running environment of the first host to be matched with the running environments required by the management service and the first managed service, wherein the first node manager is configured to be started up and self-started, and is used for restarting the first managed service when the first managed service is monitored to be abnormally stopped through the self-started first node manager;
creating a start script and a stop script of the management service, and a start script and a stop script of the first managed service, respectively, to complete creation of the management service and the first managed service.
Another aspect of an embodiment of the present invention provides a data processing system, including:
the acquisition unit is used for acquiring a first configuration parameter, a second configuration parameter, a third configuration parameter and a fourth configuration parameter which are matched with the environment parameter of the first host;
a first creation unit, configured to create a domain and a management service on the first host according to the first configuration parameter, where the management service runs in the domain;
A second creating unit, configured to create a first node manager on the first host according to the second configuration parameter;
A third creating unit, configured to create a first device managed by the first node manager according to the third configuration parameter, and create a first managed service corresponding to the first device;
The first configuration unit is used for configuring the management service and the first managed service according to preset service parameter configuration conditions;
The second configuration unit is configured to configure the Java virtual machine parameters of the first host and the first node manager according to the fourth configuration parameters so as to enable the running environment of the first host to be matched with the running environments required by the management service and the first managed service, and the first node manager is configured to be started up and self-started, and is used for restarting the first managed service when the first managed service is monitored to be abnormally stopped through the self-started first node manager;
and a fourth creation unit configured to create a start script and a stop script of the management service, and a start script and a stop script of the first managed service, respectively, so as to complete creation of the management service and the first managed service.
According to the technical scheme, the first configuration parameter, the second configuration parameter, the third configuration parameter and the fourth configuration parameter which are matched with the environment parameter of the first host are obtained; creating a domain and management service on the first host according to the first configuration parameters; creating a first node manager on the first host according to the second configuration parameters; creating a first device managed by the first node manager according to the third configuration parameters, and creating a first managed service corresponding to the first device; configuring management service and first managed service according to preset service parameter configuration conditions; configuring Java virtual machine parameters of the first host and a first node manager according to the fourth configuration parameters so as to enable the running environment of the first host to be matched with the running environments required by the management service and the first managed service, wherein the first node manager is configured to be started up and self-started, and is used for restarting the first managed service when the first managed service is monitored to be abnormally stopped through the self-started first node manager; the method comprises the steps of respectively creating a start script and a stop script of a management service and a start script and a stop script of a first managed service to finish creation of the management service and the first managed service, automatically creating a domain, the management service running in the domain, a first node manager, a first device managed by the first node manager and the first managed service corresponding to the first device according to each configuration parameter, finishing automatic creation of the domain, various services, the node manager and the device, configuring the management service and the first managed service according to preset service parameter configuration conditions, enabling parameters of each management service and each first managed service to be consistent, achieving the purpose of quickly creating unified standard service, thereby realizing reduction of manpower and time consumption, improving creation efficiency and reducing errors in the creation process.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present invention, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a data processing method disclosed in an embodiment of the present invention;
FIG. 2 is a flow chart of one implementation of step S102 in FIG. 1;
FIG. 3 is a flowchart of a data processing method according to another embodiment of the present invention;
FIG. 4 is a flowchart of a data processing method according to another embodiment of the present invention;
FIG. 5 is a block diagram of a data processing system according to an embodiment of the present invention;
FIG. 6 is a block diagram of a data processing system according to another embodiment of the present invention;
FIG. 7 is a block diagram of a data processing system according to another embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
In the present disclosure, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
Before describing the data processing method and system provided by the present invention, the terms involved will be described:
node Manager (NM) may be followed by an identification, such as e.g. NM1, NM2, etc., representing different Node managers within a cluster.
WebLogic scripting tool (WebLogic Script Tools, WLST), WLST is a command line scripting interface for monitoring and managing WebLogic Server (WebLogic services) instances and domains.
Managed services (MANAGED SERVER, MS) may be followed by an identification, such as number MS1, MS2, etc., representing different managed services within a cluster.
A management service (ADMIN SERVER, AS).
Java development kit (Java Development kit, JDK).
Java virtual machine (Java Virtual Machine, JVM), a specification for computing devices, is an imaginary computer that emulates the various functions of a Java computer by emulating it on an actual computer (also called a physical machine).
Referring to fig. 1, a flowchart of a data processing method disclosed in an embodiment of the present invention is shown, processing logic of the data processing method of the embodiment is written by a code script, and the data processing method provided in the embodiment is implemented by running the code script, where the data processing method may include the following steps:
S101, acquiring a first configuration parameter, a second configuration parameter, a third configuration parameter and a fourth configuration parameter which are matched with the environment parameter of the first host.
In this embodiment, the first host is a designated physical machine/virtual machine. The environmental parameters of the first host include at least one of: software parameters such as an operating system installed on the first host, and hardware parameters such as a memory size of the first host. The first configuration parameter, the second configuration parameter, the third configuration parameter and the fourth configuration parameter are preset configuration parameters of WebLogic, and the configuration parameters can be set in a configuration file so as to be read from the configuration file; or the user inputs the configuration parameters by setting the parameter input interface, and the configuration parameters input in the parameter input interface are automatically imported in the process of implementing the data processing method of the embodiment.
Configuration parameters may include, but are not limited to: domain name, address of management service, IP address and port of managed service, user name, user password, JVM parameters, etc. The first configuration parameter includes at least one parameter of the configuration parameters, and the second configuration parameter, the third configuration parameter and the fourth configuration parameter may also include at least one parameter of the configuration parameters, such as a part of or all of the first configuration parameter, the second configuration parameter, the third configuration parameter and the fourth configuration parameter. The relationship of the four configuration parameters is as follows: the first configuration parameter, the second configuration parameter, the third configuration parameter, and the fourth configuration parameter may or may not include the same parameter or parameters.
In this embodiment, matching with the environment parameters of the first host refers to that the parameter values of the configuration parameters are compliant in the operating environment of the first host, in other words, meet the operating system requirements of the first host. For example, assuming that the operating system of the first host is Linux, if the configuration parameter is a parameter adapted to the windows system, the configuration parameter is not suitable for the Linux system, which indicates that the configuration parameter is not compliant, and the configuration parameter is not matched with the environmental parameter of the first host; if the configuration parameters are parameters which are suitable for the Linux system, the configuration parameters are suitable for the Linux system, the compliance of the configuration parameters is explained, and the configuration parameters are matched with the environment parameters of the first host.
The judging time for judging whether the configuration parameters are matched with the environment parameters of the first host machine may be: and judging whether the configuration parameters are matched with the environment parameters of the first host or not in the process of reading the configuration parameters into the memory. Implementation mode for judging whether configuration parameters are matched with environment parameters of first host computer or not: except that it is checked whether the parameter values of these configuration parameters are compatible with the environmental parameters according to the environmental parameters of the first host; it is also possible to check whether the format or content of the parameter values of the respective configuration parameters is legal, for example, whether the IP address of the AS or MS belongs to a legal IP address, and whether the format is correct.
S102, creating a domain and an AS on the first host according to the first configuration parameters.
The domains comprise a WebLogic single-machine domain and a WebLogic multi-machine domain, and all services (servers, including AS and MS) contained in the WebLogic single-machine domain are deployed on a virtual machine or a physical machine; all services contained by WebLogic multiple machine domains can be deployed on different virtual machines or physical machines. In this embodiment, the created domain is a WebLogic single domain, and both the AS and the MS in the domain are deployed on the first host.
The AS is a management service that operates within a domain. The AS is a service instance on the first host, and WebLogic carries an application, which is also called a management console (simple for short), and can manage MSs in the whole domain and the domain through the application, and is a central management controller of the whole domain. The MS is provided with an application system required by the running program, which is an actual running environment of the running program and resources in the domain.
Referring to fig. 2, a flowchart of one implementation of step S102 is shown:
s201, creating a domain and an AS on the first host according to the preset domain template file and the first configuration parameters.
The preset domain template file is a domain template file manufactured based on a simple domain. When creating a domain, a simple domain can be built according to a preset domain template file, and then the configuration of the domain (such as changing an ip address) is changed or increased according to the first configuration parameter and/or the preset service parameter configuration condition, so that the parameter value of the domain is more optimized. The first configuration parameters and the preset service parameter configuration conditions are customized in advance according to specific requirements of users. The configuration of changing or adding the domain according to the first configuration parameter and/or the configuration of changing or adding the domain according to the preset service parameter configuration condition is performed after the domain creation is similar to the process of configuring the AS, and in particular, see the following description of step S105.
And creating the AS according to the first configuration parameters, and starting the created AS. The AS operates within a domain, which is an instance of the domain. The first configuration parameters may include, but are not limited to: domain name, address of AS, username of WebLogic, and user password. The address of the AS is an IP address of an accessible AS configured for the first host, including at least one IP address.
In this embodiment, to ensure the security isolation of the production environment, two IP addresses may be configured on the first host, one for production access, referred to as a production address; the other is used for daily operation and management, called a hosting address, the AS is accessed through networks corresponding to the two IP addresses, the network corresponding to the production address is called a production network, and the network corresponding to the hosting address is called a hosting network. The production network is used for service access, and the data flow of the production network needs to be ensured for high requirements of service instantaneity and the like. The production address is only used for service access and is not used for other administrative operations, so that the large-flow operation can be prevented from occupying the data flow of the service access. The hosting network is used for some administrative operations, configuration modifications, and may manage all MSs through the AS or access the AS with an operator/manager identity, such AS through a hosting address.
Taking AS addresses AS two IP addresses AS an example, a configuration format of the first configuration parameter when creating WebLogic single domain is given below, where HOST1 is the hostname of the first HOST, and NM1 is the first node manager on the first HOST (for description of NM1, see S103):
Domain_name= 'DOMAIN NAME';
MACHINE_ ADDRS = 'HOST1 production address: NM1 snoop port';
ADMINSERVER _addr= 'HOST1: AS snoop port';
admin_manage_addr= ' AS's hosting address ';
Wls_username= 'WebLogic', the USERNAME of WebLogic control defaults to WebLogic;
Wls_password= 'PASSWORD', PASSWORD of user of WebLogic control.
It should be noted that in other embodiments, the address of the AS may be changed, for example, only one IP address may be configured.
S202, setting a domain password.
In this embodiment, the domain password is used to verify whether the access right of the AS and/or the MS in the activation and deactivation domain is provided, the domain password may be set according to the user password in the first configuration parameter, the domain password corresponds to the password for connecting the AS, and is applicable to the domain corresponding to the domain password.
The verification process may be as follows: determining the authority of the user according to the user name and the user password by acquiring the user name and the user password filled in the login page, for example, judging whether the user is a designated user capable of connecting with the AS according to the user name; if the user is the designated user, judging whether the user password is matched with the domain password; if the user password matches the domain password, the user has the right to start and shut down the AS and/or MS within the domain.
S203, creating and configuring a monitoring user.
In this embodiment, the monitoring user is configured to view the first configuration parameter in the domain and monitor the service running condition in the domain. The functions provided by the monitoring user for the WebLogic product are created, and the related monitoring permission can be configured for the monitoring user but the modification permission is not configured, so that unexpected changes of the domain caused by the modification of the monitoring user are avoided. It should be noted that, the monitoring user may be used to view not only the first configuration parameter in the domain, but also the second configuration parameter, the third configuration parameter, and the fourth configuration parameter in the domain. If new configuration parameters appear in the subsequent domain, the configuration parameters can also be checked by monitoring the user.
The monitoring user can also be used as an interface of other external monitoring products, and the external monitoring products can monitor the whole domain through the monitoring user, so that the domain is convenient to maintain and manage. It should be noted that, in other embodiments, the creation step of the monitoring user may be omitted if there is no monitoring need.
The above is one implementation of step S102.
S103, a first node manager (hereinafter referred to as NM 1) is created on the first host according to the second configuration parameters.
In this embodiment, the second configuration parameters include, but are not limited to: the snoop port of NM1, the address of AS and the snoop port. One configuration format of the second configuration parameter is as follows:
MACHINE_ ADDRS = 'HOST1 production address: NM1 snoop port';
ADMINSERVER _addr= 'HOST1: AS snoop port'.
To facilitate the management of service instances, such AS WebLogic service instances, a first node manager (NM 1 for short) is created, where NM1 is not associated with a particular domain, and is associated with a first host, for starting and stopping service instances (AS and MS 1) on the first host. The NM1 is equivalent to a daemon process (also called proxy process) of the AS and the MS1, and when the process of the AS or the MS1 exits or is turned off due to an exception, the NM1 can automatically start the turned-off AS or MS1, thereby improving the availability of the first host. In other embodiments, the relevant step of creating the first node manager may be omitted if the availability requirements for the first node are not high.
S104, creating a first device managed by NM1 according to the third configuration parameter, and creating a first managed service (MS 1 for short) corresponding to the first device.
A device (machine) is a logical concept in WebLogic products, one device corresponds to one physical machine or virtual machine, and the two belong to a one-to-one relationship. It can be understood that: the device is a physical or virtual machine associated with the node manager. In this embodiment, NM1 is associated with a first host, and the first device corresponds to the first host, and then the first device is a physical machine or a virtual machine associated with NM 1.
Creating the first device may be creating a device with the same physical parameters as the first host. One implementation is that the first device binds the IP address of the first host, such that NM1 determines the physical machine or virtual machine associated with it (i.e., NM1 is associated with the first host) from the IP address of the first device binding, such that NM1 can manage all service instances on the first device from the IP address of the first device binding.
In this embodiment, MS1 is a service instance on the first host. Applications for providing business services to the outside can be deployed on a Managed Service (MS), a plurality of applications can be deployed on one machine, and one or a plurality of applications can be deployed on a plurality of machines under the condition of multiple machine domains. Third configuration parameters include, but are not limited to: the monitor port of NM1, the address and monitor port of AS and the monitor port of MS 1. One configuration format of the third configuration parameter is:
MACHINE_ ADDRS = 'HOST1 production address: NM1 snoop port';
ADMINSERVER _addr= 'HOST1: AS snoop port';
MSERVER _ ADDRS = 'MS1: HOST1: MS1 listening port'.
And configuring the first equipment through the third configuration parameters.
S105, configuring AS and MS1 according to preset service parameter configuration conditions.
The preset service parameter configuration conditions can be preset in the code script; the method can also be recorded in a configuration file, and if the preset service parameter configuration conditions are not preset in the code script, the preset service parameter configuration conditions are read from the configuration file when the code script runs. In the actual use process, preset service parameter configuration conditions can be formulated according to the practical experience of the WebLogic product and the product standard specification in the enterprise. Preset service parameter configuration conditions include, but are not limited to: to facilitate analysis of faults, the AS and MS1 are configured to generate detailed garbage collection logs during operation; configuring execution thread viscous timeout time for improving high availability of an application system; to facilitate third parties or self-research monitoring products, webogic application domain monitoring users are provided. In other embodiments, two sets of preset service parameter configuration conditions may be set according to different requirements, one set is used for configuring the AS and one set is used for configuring the MS1, which is not limited herein.
Optionally, this step may further configure AS and MS1 according to the weblog NUMBER (LOGFILES _number), the minimum value (POOLSIZE _min) and the maximum value (POOLSIZE _max) of the service instance thread pool in the configuration parameters.
S106, configuring JVM parameters and NM1 of the first host according to the fourth configuration parameters so AS to enable the running environment of the first host to be matched with the running environments required by the AS and the MS1, wherein the NM1 is configured to be started up and restarted, and is used for restarting the MS1 when the abnormal stop of the MS1 is monitored through the self-started NM 1.
In this embodiment, the JVM refers to a JVM process, which is 1 java process from the operating system level. JVM parameters include, but are not limited to: parameters of the PERM memory area and parameters of the HEAP memory area. One configuration format of the configuration parameters used to configure JVM parameters in the fourth configuration parameters may be:
AS_PERM_MAX＝'256'；MS1_PERM_MAX＝'512'；
AS_HEAP_MIN＝'512'；AS_HEAP_MAX＝'512'；
MS1_HEAP_MIN＝'1024'；MS1_HEAP_MAX＝'1024'。
Wherein AS_PERM_MAX and MS1_PERM_MAX are the maximum values of PERM memory areas of AS and MS1 respectively; AS_HEAP_MIN and AS_HEAP_MAX are respectively the minimum value and the maximum value of the HEAP memory area of the AS; the MS1_HEAP_MIN and MS1_HEAP_MAX are the minimum and maximum values of the HEAP memory area of MS 1.
In this embodiment, the configuration NM1 includes two aspects: on the one hand, configuring the name of the domain managed by NM1 on NM1 (the name of the domain managed by NM1 at least comprises one); on the other hand, NM1 is configured with a listening address and a listening port of NM1, so that the AS can access NM1 through the listening address and the listening port of NM1. As can be seen, the fourth configuration parameters further include: the DOMAIN NAME corresponding to NM1 (domain_name= 'DOMAIN NAME'), the listening address of NM1 and the listening port (machine_ ADDRS = 'HOST1: HOST1 production address: NM1 listening port'; ADMINSERVER _addr= 'HOST1: AS listening port').
In this embodiment, the implementation manner in which NM1 is configured to be booted may be: putting the starting script of NM1 under the appointed directory of the operating system, and realizing that NM1 is also automatically started when the operating system is started.
In other embodiments, two configuration files may be pre-stored on the first host, the first node manager may be configured according to the two configuration files, one configuration file is a name for configuring the domain to the first node manager, and one first node manager may manage a plurality of domains. The other configuration file is used for configuring the characteristics of the monitoring address, the monitoring port and the like of the first node manager; another configuration file is also used to configure some of the personalization parameters managed by the first node manager, e.g., how many seconds after the MS failed to start up? The MS is not successfully restarted after a few times and no further attempt is made to start. It should be noted that the configuration of all nodes in one domain is the same.
S107, respectively creating a start script and a stop script of the AS and a start script and a stop script of the MS1 to finish the creation of the AS and the MS 1. The NM1 can manage start and stop of the AS and the MS1 through the start script and the stop script of the AS and the start script and the stop script of the MS 1.
According to the technical scheme, according to the configuration parameters, the domain, the AS, the NM1, the first equipment and the MS1 running in the domain are automatically created, and the domain, various service instances, the node manager and the equipment are automatically created, if the domain and the service are related to WebLogic, the WebLogic domain and the service instance can be created by one key, and the AS and the MS1 can be configured according to the preset service parameter configuration conditions, so that the parameters of the AS and the MS1 are consistent, and the purpose of quickly creating the service with unified standard is achieved, thereby reducing the consumption of manpower and time, improving the creation efficiency and reducing errors in the creation process. The data processing method can be executed on the first host in the form of a code script (for example, using shell script and WLST language) to realize one-click creation of WebLogic domain and service instance; the script can be remotely invoked through a unified operation and maintenance management platform.
In practical applications, most business systems generally provide application services in the form of application clusters, and WebLogic single-machine domain (i.e. a server) cannot meet the application requirements of most business systems. For this reason, another embodiment of the present invention provides a data processing method, which implements automatic creation of WebLogic application clusters (i.e., multiple machine domains). An application cluster is understood to mean that WebLogic is installed on the application cluster and a set of hosts is created, where the hosts may be physical machines or virtual machines, and an application cluster includes at least two hosts.
Taking an application cluster including two hosts (e.g., a first host and a second host) as an example, a data processing method for creating an application cluster is described below, referring to fig. 3, which shows a flowchart of the data processing method, including the following steps:
s301, acquiring a first configuration parameter, a second configuration parameter, a third configuration parameter and a fourth configuration parameter which are matched with the environment parameter of the first host.
S302, creating a domain and an AS on the first host according to the first configuration parameters.
Steps S301 to S302 are similar to steps S101 to S102 in the above embodiments, and the description of the working procedure of steps S301 to S302 is referred to steps S101 to S102, which are not repeated here.
S303, setting a node manager on each host of the application cluster according to the second configuration parameters.
In this embodiment, the application cluster includes two hosts, a first host and a second host. The method comprises the following steps: creating NM1 on the first host according to the second configuration parameters; and creating a second node manager (hereinafter, abbreviated as NM 2) on the second host according to the second configuration parameters. It should be noted that, in other embodiments, more than two hosts may be created in the application cluster, and this step creates a corresponding number of node managers according to the number of hosts in the application cluster, which is not limited herein. For example, the application cluster includes four hosts, namely, a first host, a second host, a third host, and a fourth host, respectively, then NM1 is created on the first host, NM2 is created on the second host, NM2 is created on the third host, and NM4 is created on the fourth host.
For the second configuration parameter, please refer to step S103, and the description thereof is omitted. In this embodiment, one configuration format of the second configuration parameter may be:
MACHINE_ ADDRS =' HOST1 production address NM1 snoop port; HOST2 production address NM2 snoop port'; HOST2 is the hostname of the second HOST;
ADMINSERVER _addr= 'HOST1: AS snoop port'.
For the explanation of NM1, please refer to step S103, and the description is omitted here. Because the WebLogic service instance is deployed on multiple hosts (i.e., on physical machines), NM2 is created on the second host for facilitating remote management of the WebLogic service instance on the second host. In the case of multiple domains, the remote management of service instances refers to the remote management from the AS (or confole) to all MSs on different hosts; in this embodiment, remote management from AS (or control) to MS2 is referred to. And the NM2 is instructed through the AS (or a con), and the NM2 remotely realizes the instruction to realize the remote management of the WebLogic service instance. NM2 is not associated with a particular domain, and is associated with a second host, a service instance deployed in any one of the WebLogic domains on the second host may be started and stopped from the AS (or confole) through NM2. NM2 is equivalent to a daemon/proxy process of MS2, and a service instance started by NM2 (namely, a second managed service MS 2) is automatically restarted after being abnormally exited, so that the usability of the system is improved.
S304, equipment managed by the node manager is created according to the third configuration parameters, and managed services corresponding to the domain equipment are created.
In this embodiment, step S304 includes: creating a first device managed by the NM1 according to the third configuration parameter, and creating an MS1 corresponding to the first device; and creating a second device managed by the NM2 according to the third configuration parameter, and creating the MS2 corresponding to the second device. The creation device may be understood as a device that creates a room with the same parameters as the first host. In this embodiment, the first device corresponds to a first host, and the second device corresponds to a second host. In the implementation manner of creating the first device, please refer to step S104, and the creation of the second device is similar to the creation of the first device, and will not be repeated here. It should be noted that, in other embodiments, the number of node managers in the application cluster is not necessarily 2, and may be greater than 2, and this step creates a corresponding number of devices according to the number of node managers in the application cluster, which is not limited herein specifically. For example, the application cluster includes four node managers, NM1, NM2, NM3, and NM4, respectively, a first device managed by NM1, a second device managed by NM2, a third device managed by NM3, and a fourth device managed by NM4, respectively. Similarly, in other embodiments, an appropriate number of MSs may be created based on the number of devices in the application cluster, not limited herein.
In this embodiment, the third configuration parameters include, but are not limited to: the monitor ports of NM1 and NM2, the addresses and monitor ports of AS, the monitor port of MS1 and the monitor port of MS 2. One configuration format of the third configuration parameter is:
MACHINE_ ADDRS =' HOST1 production address NM1 snoop port; HOST2 production address NM2 snoop port';
ADMINSERVER _addr= 'HOST1: AS snoop port';
MSERVER _ ADDRS =' MS1: HOST1: MS1 listening port; MS2 HOST2 MS2 listens to port'.
S305, configuring all service instances in the condition configuration domain according to preset service parameters.
In this embodiment, the service instance created in the domain includes: AS, MS1 and MS2. The step comprises: configuring AS and MS1 according to preset service parameter configuration conditions; and configuring the MS2 according to the preset service parameter configuration conditions. For the description of the preset service parameter configuration conditions and the description of the process of configuring the AS and MS1, please refer to the description related to step S105; in addition, the configuration MS2 is similar to the configuration MS1, and will not be described here again.
It should be noted that, in other embodiments, the configuration may also be performed by the host, for example, the AS, MS1, NM1, and the first device of the first host may be created and configured first, and then the MS2, NM2, and the second device of the second host may be created and configured. The execution sequence of the first host AS, MS1, NM1, and the first device, and the second host MS2, NM2, and the second device are not limited herein.
S306, packing and compressing files in a first directory on the first host into a compressed package.
The first directory includes a domain directory and a NM1 directory on the first host. The domain catalogue is a catalogue which is generated after the creation and configuration of the domain are completed on the first host and is related to the domain, and various files related to the operation of the domain are stored in the domain catalogue; similarly, the NM1 directory is a directory related to NM1 generated after the creation of NM1 is completed on the first host, and various files related to the running of NM1 are stored in the NM1 directory.
S307, a second catalog corresponding to the first catalog is created on the second host.
The second directory includes a domain directory and a NM2 directory on the second host. The second directory corresponding to the first directory means that the location of the second host pointed to by the second directory corresponds to the location of the first host pointed to by the first directory, and is the same location on a different host. That is, the storage path of the domain directory created on the second host is identical to the storage path of the domain directory on the first host; the storage path of the NM2 directory created on the second host is identical to the storage path of the NM1 directory of the first host.
It should be noted that, in other embodiments, if the application cluster includes a plurality of hosts, the directories (including the domain directory and the node manager directory) corresponding to the first directory of the domain first host are created on the other hosts, and the second directory is not created on the second host, which is not limited herein.
And S308, sending the compressed package to a second host, and decompressing the compressed package to a second catalog to enable the files in the second catalog to be identical with the files in the first catalog.
In this embodiment, the compressed package obtained in step S306 is sent to the second host, and the files decompressed by the compressed package are respectively stored in the designated positions of the second directory. The decompressed files of the compression package comprise domain building scripts, and the storage positions of the decompressed files in the second catalogue are determined according to the storage positions of the files in the first catalogue, so that the files in the second catalogue are identical to the files in the first catalogue. It should be noted that, in other embodiments, if the application cluster includes multiple hosts, this step sends a compressed packet to each host (except for the host where the AS is located), and decompresses the compressed packet to the designated directory in the other hosts, so that the files in the domain directory and the node manager directory in the other hosts are the same AS the files in the domain directory and the node manager directory of the host where the AS is located. The listening address and listening port of the MS on the other host are then configured on the AS.
S309, configuring JVM parameters and NM1 of the first host according to the fourth configuration parameters. The operation of step S309 is described in step S106, and will not be described herein.
S310, obtaining a fifth configuration parameter matched with the environmental parameter of the second host; the JVM parameters and NM2 of the second host are configured according to the fifth configuration parameters.
By the configuration of this step, the running environment of the second host is matched with that of the first host, and the NM2 is configured to be booted up for restarting the MS2 when the abnormal stop of the MS2 is monitored by the booted up NM 2. In this embodiment, the fifth configuration parameter is the same as the fourth configuration parameter, and reference is made to the description of the fourth configuration parameter in step S106. Fifth configuration parameters one configuration format may be:
AS_PERM_MAX＝'256'；MS2_PERM_MAX＝'512'；
AS_HEAP_MIN＝'512'；AS_HEAP_MAX＝'512'；
MS2_HEAP_MIN＝'1024'；MS2_HEAP_MAX＝'1024'；
Domain_name= 'DOMAIN NAME';
MACHINE_ ADDRS = 'HOST2 production address: NM2 snoop port'.
The configuration procedures of NM2 and NM1 are the same, and the description of the configuration of NM2 in this step is referred to as the configuration description of NM1 in step S106, and is not repeated here. It should be noted that, in other embodiments, the configuration process of the JVM parameters and the configuration process of the corresponding node manager in all hosts may be implemented with reference to step S106.
S311, respectively creating a start script and a stop script of the AS, and a start script and a stop script of the MS1 and the MS2 to finish the creation of the application cluster.
The NM1 can manage the start and stop of the AS and the MS1 through the start script and the stop script of the AS and the start script and the stop script of the MS1 and the MS 2; NM2 may manage the start-stop of MS2 to complete the creation of the application cluster.
According to the technical scheme, the domain, various service instances, the node manager and the equipment can be automatically built according to the configuration parameters, and the service instances in the domain can be configured according to the preset service parameter configuration conditions, so that the parameters of all the service instances are consistent, the purpose of quickly building the service with unified standards is achieved, the consumption of manpower and time is reduced, the building efficiency is improved, and errors in the building process are reduced. Through actual timing, 60 minutes are needed for manually creating and configuring a multi-machine domain containing 3 MSs according to a certain standard specification (wherein 3 managed services are distributed on 3 virtual machines), and only 6 minutes are needed for automatic creation and automatic configuration by using the embodiment, so that 90% of time is saved, the efficiency is greatly improved, and the standard, specification and accuracy are ensured.
Further, in order to ensure that the application clusters delivered to the user are more reliable, a further embodiment of the present invention provides a data processing method, where a flowchart of the data processing method is shown in fig. 4, and compared with fig. 3, the data processing method of the present embodiment further includes the following steps:
S312, NM1, NM2, MS1 and MS2 are started and the AS is restarted.
Because the AS is configured with parameters after the AS is turned on, the AS is restarted in order to validate the configured parameters.
S313, monitoring the operation conditions of the AS, the MS1 and the MS2 through the NM1 and the NM 2.
S314, if the running conditions of the AS, the MS1 and the MS2 indicate that the AS, the MS1 and the MS2 run normally, ending the creation flow of the AS, the MS1 and the MS 2.
S315, if the running conditions of the AS, the MS1 and the MS2 indicate that the running abnormal services exist in the AS, the MS1 and the MS2, the running abnormal services are rebuilt.
In the embodiment, whether the service implementation in the application cluster operates normally or not is judged by monitoring the running conditions of the AS, the MS1 and the MS2 through the NM1 and the NM2, and the abnormal service is rebuilt, so that the reliability of the created application cluster is further ensured.
Based on the above method embodiment, the embodiment of the present invention correspondingly discloses a data processing system, please refer to fig. 5, which shows a structure diagram of the data processing system, including: an acquisition unit 101, a first creation unit 102, a second creation unit 103, a third creation unit 104, a first configuration unit 105, a second configuration unit 106, and a fourth creation unit 107.
An obtaining unit 101, configured to obtain a first configuration parameter, a second configuration parameter, a third configuration parameter, and a fourth configuration parameter that match an environmental parameter of the first host.
A first creation unit 102, configured to create a domain and an AS on the first host according to the first configuration parameter. Wherein the AS operates within the domain.
The first creation unit 102 is specifically configured to: creating a domain and an AS on a first host according to a preset domain template file and a first configuration parameter; setting a domain password for verifying whether the domain password has the authority to start and close the AS and/or MS in the domain; a monitoring user is created and configured for viewing a first configuration parameter in the domain and monitoring service operation in the domain.
A second creating unit 103, configured to create NM1 on the first host according to the second configuration parameter.
A third creating unit 104, configured to create a first device managed by NM1 according to a third configuration parameter, and create an MS1 corresponding to the first device.
A first configuration unit 105, configured to configure the AS and the MS1 according to preset service parameter configuration conditions.
The second configuration unit 106 is configured to configure the Java virtual machine parameters and NM1 of the first host according to the fourth configuration parameters, so that the running environment of the first host matches with the running environments required by the AS and the MS1, and the NM1 is configured to be booted up and booted up, and is configured to restart the MS1 when the MS1 is monitored to be abnormally stopped by the booted up NM 1.
A fourth creation unit 107, configured to create a start script and a stop script of the AS, and a start script and a stop script of the MS1, respectively, so AS to complete creation of the AS and the MS 1.
For the description of the working process of each unit, please refer to the descriptions of steps S101 to S107 in the method embodiment, and the description is omitted here.
According to the technical scheme, according to the configuration parameters, the domain, the AS, the NM1, the first equipment and the MS1 running in the domain are automatically created, and the domain, various service instances, the node manager and the equipment are automatically created, if the domain and the service are related to WebLogic, the WebLogic domain and the service instance can be created by one key, and the AS and the MS1 can be configured according to the preset service parameter configuration conditions, so that the parameters of the AS and the MS1 are consistent, and the purpose of quickly creating the service with unified standard is achieved, thereby reducing the consumption of manpower and time, improving the creation efficiency and reducing errors in the creation process. The data processing method can be executed on the first host in the form of a code script (for example, using shell script and WLST language) to realize one-click creation of WebLogic domain and service instance; the script can be remotely invoked through a unified operation and maintenance management platform.
In practical applications, most business systems generally provide application services in the form of application clusters, and WebLogic single-machine domain (i.e. a server) cannot meet the application requirements of most business systems. To this end, another embodiment of the present invention provides a data processing system that enables automatic creation of WebLogic application clusters (i.e., multiple machine domains). Taking an application cluster comprising two hosts (e.g., a first host and a second host) as an example, a data processing system for creating an application cluster is described below, referring to fig. 6, which shows a block diagram of the data processing system, and further includes, compared to fig. 5: a compression unit 108, a catalog creation unit 109, and a transmission unit 110.
The compression unit 108 is configured to package and compress files in the first directory on the first host into a compressed package.
A directory creation unit 109 for creating a second directory corresponding to the first directory on the second host.
The sending unit 110 is configured to send the compressed packet to the second host, and decompress the compressed packet to the second directory, so that the files in the second directory are the same as the files in the first directory.
For a description of the working procedures of the compression unit 108, the catalog creation unit 109 and the transmission unit 110, please refer to the description of steps S306 to S308 of the above method embodiment, which is not repeated here.
The second creating unit 103 is further configured to create NM2 on the second host according to the second configuration parameter. The second creation unit 103 creates the NM2, please refer to the description of step S303 in the above method embodiment, which is not described herein.
The third creating unit 104 is further configured to create a second device managed by NM2 according to the third configuration parameter, and create MS2 corresponding to NM 2. The third creation unit 104 creates a procedure description of the second device and the MS2, please refer to the description of step S304 in the above method embodiment, which is not described herein.
The first configuration unit 105 is further configured to configure NM2 according to a preset service parameter configuration condition. For the description of the process of configuring NM2 by the first configuration unit 105, please refer to the description of step S305 in the above method embodiment, which is not repeated here.
The obtaining unit 101 is further configured to obtain a fifth configuration parameter that matches the environmental parameter of the second host.
The second configuration unit 106 is further configured to configure the Java virtual machine parameters and NM2 of the second host according to the fifth configuration parameters, so that the running environment of the second host matches the running environment of the first host, and NM2 is configured to be booted up and booted, and is configured to restart the MS2 when the MS2 is monitored to be abnormally stopped by the booted up NM 2. The obtaining unit 101 obtains the fifth configuration parameter, and the process description of the second configuration unit 106 configuring the Java virtual machine parameter and NM2, please refer to the description of step S310 in the above method embodiment, which is not described herein.
The fourth creation unit 107 is further configured to create a start script and a stop script of the MS 2. The process is described in step S311 of the above method embodiment, and is not repeated here.
According to the technical scheme, the domain, various service instances, the node manager and the equipment can be automatically built according to the configuration parameters, and the service instances in the domain can be configured according to the preset service parameter configuration conditions, so that the parameters of all the service instances are consistent, the purpose of quickly building the service with unified standards is achieved, the consumption of manpower and time is reduced, the building efficiency is improved, and errors in the building process are reduced. Through actual timing, 60 minutes are needed for manually creating and configuring a multi-machine domain containing 3 MSs according to a certain standard specification (wherein 3 managed services are distributed on 3 virtual machines), and only 6 minutes are needed for automatic creation and automatic configuration by using the embodiment, so that 90% of time is saved, the efficiency is greatly improved, and the standard, specification and accuracy are ensured.
Further, in order to ensure that the application clusters delivered to the users are more reliable, a further embodiment of the present invention proposes a data processing system, the structure of which is shown in fig. 7, and compared with fig. 6, the data processing system of this embodiment further includes: a starting unit 201, a monitoring unit 202 and a control unit 203.
A startup unit 201 for starting up NM1, NM2, MS1 and MS2 and restarting the AS.
A monitoring unit 202 for monitoring the operation of the AS, MS1 and MS2 by means of NM1 and NM 2.
A control unit 203, configured to instruct the first creation unit 102 to end the creation flow of the AS and instruct the third creation unit 104 to end the creation flow of the MS1 and the MS2 if the operation conditions of the AS, the MS1 and the MS2 indicate that the AS, the MS1 and the MS2 are operating normally; if the running conditions of the AS, the MS1 and the MS2 indicate that the running abnormal services exist in the AS, the MS1 and the MS2, the creation unit corresponding to the running abnormal services is indicated to reconstruct the running abnormal services.
In the embodiment, whether the service implementation in the application cluster operates normally or not is judged by monitoring the running conditions of the AS, the MS1 and the MS2 through the NM1 and the NM2, and the abnormal service is rebuilt, so that the reliability of the created application cluster is further ensured.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for a system or system embodiment, since it is substantially similar to a method embodiment, the description is relatively simple, with reference to the description of the method embodiment being made in part. The systems and system embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative elements and steps are described above generally in terms of functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method of data processing, comprising:
Acquiring a first configuration parameter, a second configuration parameter, a third configuration parameter and a fourth configuration parameter which are matched with the environmental parameter of the first host;
Creating a domain and a management service on the first host according to the first configuration parameters, wherein the management service operates in the domain;
creating a first node manager on the first host according to the second configuration parameters;
Creating a first device managed by the first node manager according to the third configuration parameters, and creating a first managed service corresponding to the first device;
Configuring the management service and the first managed service according to preset service parameter configuration conditions;
Configuring Java virtual machine parameters of the first host and the first node manager according to the fourth configuration parameters so as to enable the running environment of the first host to be matched with the running environments required by the management service and the first managed service, wherein the first node manager is configured to be started up and self-started, and is used for restarting the first managed service when the first managed service is monitored to be abnormally stopped through the self-started first node manager;
creating a start script and a stop script of the management service, and a start script and a stop script of the first managed service, respectively, to complete creation of the management service and the first managed service.
2. The method of claim 1, wherein the creating a domain and management service on the first host according to the first configuration parameters comprises:
Creating a domain and management service on the first host according to a preset domain template file and the first configuration parameters;
Setting a domain password for verifying whether the domain password has the authority to start and close the management service and/or managed service in the domain;
A monitoring user is created and configured for viewing a first configuration parameter in the domain and service operation in the monitoring domain.
3. The method of claim 1, further comprising, after said configuring said management service and said managed service according to preset service parameter configuration conditions, and before said configuring Java virtual machine parameters of said first host according to said fourth configuration parameters:
Packaging and compressing files in a first directory on the first host into a compressed package;
creating a second directory corresponding to the first directory on a second host;
And sending the compressed package to the second host, and decompressing the compressed package to the second catalog so that the files in the second catalog are the same as the files in the first catalog.
4. A method according to claim 3, further comprising:
Creating a second node manager on the second host according to the second configuration parameters;
Creating a second device managed by the second node manager according to the third configuration parameters, and creating a second managed service corresponding to the second device;
configuring the second managed service according to a preset service parameter configuration condition;
Obtaining a fifth configuration parameter matched with the environmental parameter of the second host;
Configuring Java virtual machine parameters of the second host and the second node manager according to the fifth configuration parameters so as to enable the running environment of the second host to be matched with the running environment of the first host, wherein the second node manager is configured to be started up and self-started, and is used for restarting the second managed service when the second managed service is monitored to be abnormally stopped through the self-started second node manager;
creating a start script and a stop script for the second managed service.
5. The method as recited in claim 4, further comprising:
Starting the first node manager, the second node manager, the first managed service and the second managed service, and restarting the management service;
Monitoring, by the first node manager and the second node manager, the operation of the management service, the first managed service, and the second managed service;
if the running conditions of the management service, the first managed service and the second managed service indicate that the management service, the first managed service and the second managed service normally run, ending the creation flow of the management service, the first managed service and the second managed service;
And if the running conditions of the management service, the first managed service and the second managed service indicate that the running abnormal service exists in the management service, the first managed service and the second managed service, reconstructing the running abnormal service.
6. A data processing system, comprising:
the acquisition unit is used for acquiring a first configuration parameter, a second configuration parameter, a third configuration parameter and a fourth configuration parameter which are matched with the environment parameter of the first host;
a first creation unit, configured to create a domain and a management service on the first host according to the first configuration parameter, where the management service runs in the domain;
A second creating unit, configured to create a first node manager on the first host according to the second configuration parameter;
A third creating unit, configured to create a first device managed by the first node manager according to the third configuration parameter, and create a first managed service corresponding to the first device;
The first configuration unit is used for configuring the management service and the first managed service according to preset service parameter configuration conditions;
The second configuration unit is configured to configure the Java virtual machine parameters of the first host and the first node manager according to the fourth configuration parameters so as to enable the running environment of the first host to be matched with the running environments required by the management service and the first managed service, and the first node manager is configured to be started up and self-started, and is used for restarting the first managed service when the first managed service is monitored to be abnormally stopped through the self-started first node manager;
and a fourth creation unit configured to create a start script and a stop script of the management service, and a start script and a stop script of the first managed service, respectively, so as to complete creation of the management service and the first managed service.
7. The system according to claim 6, wherein the first creation unit is specifically configured to:
Creating a domain and management service on the first host according to a preset domain template file and the first configuration parameters;
Setting a domain password for verifying whether the domain password has the authority to start and close the management service and/or managed service in the domain;
A monitoring user is created and configured for viewing a first configuration parameter in the domain and service operation in the monitoring domain.
8. The system of claim 6, further comprising:
the compression unit is used for packing and compressing files in a first catalog on the first host into a compression packet;
A catalog creation unit for creating a second catalog corresponding to the first catalog on a second host;
and the sending unit is used for sending the compressed packet to the second host and decompressing the compressed packet to the second directory so that the files in the second directory are the same as the files in the first directory.
9. The system of claim 8, wherein the system further comprises a controller configured to control the controller,
The second creating unit is further configured to create a second node manager on the second host according to the second configuration parameter;
The third creating unit is further configured to create a second device managed by the second node manager according to the third configuration parameter, and create a second managed service corresponding to the second device;
The first configuration unit is further configured to configure the second managed service according to a preset service parameter configuration condition;
the obtaining unit is further configured to obtain a fifth configuration parameter that is matched with the environmental parameter of the second host;
The second configuration unit is further configured to configure Java virtual machine parameters of the second host and the second node manager according to the fifth configuration parameters, so that an operating environment of the second host matches an operating environment of the first host, and the second node manager is configured to be booted and self-started, and is configured to restart the second managed service when the second managed service is monitored to be abnormally stopped through the self-started second node manager;
The fourth creation unit is further configured to create a start script and a stop script of the second managed service.
10. The system of claim 9, further comprising:
The starting unit is used for starting the first node manager, the second node manager, the first managed service and the second managed service and restarting the management service;
the monitoring unit is used for monitoring the running conditions of the management service, the first managed service and the second managed service through the first node manager and the second node manager;
The control unit is used for indicating the management service, the first managed service and the second managed service to normally operate if the running conditions of the management service, the first managed service and the second managed service indicate the first creation unit to end the creation flow of the management service and the third creation unit to end the creation flow of the first managed service and the second managed service; and if the running conditions of the management service, the first managed service and the second managed service indicate that the running abnormal service exists in the management service, the first managed service and the second managed service, a creation unit corresponding to the running abnormal service is indicated to reconstruct the running abnormal service.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010837544.9A CN111984372B (en) | 2020-08-19 | 2020-08-19 | Data processing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010837544.9A CN111984372B (en) | 2020-08-19 | 2020-08-19 | Data processing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111984372A CN111984372A (en) | 2020-11-24 |
| CN111984372B true CN111984372B (en) | 2024-06-18 |
Family
ID=73435569
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010837544.9A Active CN111984372B (en) | 2020-08-19 | 2020-08-19 | Data processing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111984372B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114024842B (en) * | 2021-11-02 | 2024-09-27 | 中国建设银行股份有限公司 | Weblogic domain building method and device, storage medium and electronic equipment |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105450735A (en) * | 2015-11-10 | 2016-03-30 | 中国建设银行股份有限公司 | Method and system for laterally expanding capacity |
| CN106325953A (en) * | 2016-08-30 | 2017-01-11 | 广西电网有限责任公司 | Weblogic cluster one-key automatic deployment method |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10417073B2 (en) * | 2017-04-12 | 2019-09-17 | Bank Of America Corporation | Application server deployment system for domain generation and testing with an administrative server virtual machine and managed server virtual machines |
-
2020
- 2020-08-19 CN CN202010837544.9A patent/CN111984372B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105450735A (en) * | 2015-11-10 | 2016-03-30 | 中国建设银行股份有限公司 | Method and system for laterally expanding capacity |
| CN106325953A (en) * | 2016-08-30 | 2017-01-11 | 广西电网有限责任公司 | Weblogic cluster one-key automatic deployment method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111984372A (en) | 2020-11-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10802906B2 (en) | Monitoring method and apparatus of server, and storage medium | |
| CN110879712B (en) | Cloud data center physical host installation method and related device | |
| US8290998B2 (en) | Systems and methods for generating cloud computing landscapes | |
| US6012100A (en) | System and method of configuring a remotely managed secure network interface | |
| US8713177B2 (en) | Remote management of networked systems using secure modular platform | |
| CN110224860B (en) | Load balancing application creation method and device, computer equipment and storage medium | |
| CN106325953A (en) | Weblogic cluster one-key automatic deployment method | |
| CN107222320A (en) | The method and apparatus that Cloud Server cluster sets up High Availabitity connection | |
| CN109725950B (en) | Method, device and storage medium for realizing single-instance operation of client | |
| CN113572862A (en) | Cluster deployment method and device, electronic equipment and storage medium | |
| CN113590169B (en) | Application deployment method, application deployment system, and computer-readable storage medium | |
| CN110928554A (en) | Deployment method, device, equipment and storage medium | |
| CN111984372B (en) | Data processing method and system | |
| CN111669293B (en) | SD-WAN system and remote management method and device for network terminal equipment | |
| Developers | Heat Documentation | |
| CN106372142A (en) | DM database and Weblogic combination one-key automatic deployment method | |
| CN110489134A (en) | A kind of dispositions method and system of PXE server and High-Performance Computing Cluster environment | |
| CN116627595A (en) | Virtual machine creation method and related components | |
| CN113328883B (en) | Terminal management method and device, storage medium and electronic equipment | |
| WO2002073438A1 (en) | Method and system for management of remote devices | |
| CN110808943B (en) | Client connection emergency management method, client and computer readable storage medium | |
| CN111966364A (en) | A method and system for building a Weblogic automation environment based on docker | |
| US20250088417A1 (en) | Architecture for remote delivery and application of datacenter management configurations | |
| CN116614323B (en) | Cloud storage enterprise network management method and system based on Rclone | |
| CN113868128B (en) | Method and device for testing PXE (PCI express) guide function and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |