CN109885779B - Subsystem management method, device, computer device and storage medium - Google Patents
Subsystem management method, device, computer device and storage medium Download PDFInfo
- Publication number
- CN109885779B CN109885779B CN201910018373.4A CN201910018373A CN109885779B CN 109885779 B CN109885779 B CN 109885779B CN 201910018373 A CN201910018373 A CN 201910018373A CN 109885779 B CN109885779 B CN 109885779B
- Authority
- CN
- China
- Prior art keywords
- subsystem
- request
- interface
- related request
- portal system
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 58
- 210000004258 portal system Anatomy 0.000 claims abstract description 66
- 238000012546 transfer Methods 0.000 claims abstract description 24
- 238000012795 verification Methods 0.000 claims description 17
- 238000000034 method Methods 0.000 claims description 9
- 241000700605 Viruses Species 0.000 claims description 4
- 238000011161 development Methods 0.000 abstract description 9
- 230000006870 function Effects 0.000 description 12
- 230000005540 biological transmission Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 6
- 230000007774 longterm Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a subsystem management method, which comprises the following steps: configuring a transit interface for the portal system; wherein the portal system receives a related request sent by at least one subsystem from the transit interface; the portal system analyzes the related request and acquires a return value corresponding to the related request; and the portal system calls the transfer interface to return the acquired return value to the at least one subsystem in a preset format. The invention also provides a device, a computer device and a storage medium for realizing the subsystem management method. The invention can realize a plurality of URL transfer requests by using one transfer interface, reduces the repeated development of subsystems and shortens the development period.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a subsystem management method, a device, a computer device, and a storage medium.
Background
Currently, developers need to develop and configure each subsystem in an enterprise respectively so that the multiple subsystems can access an interface service. However, such a configuration scheme may lead to repetitive development work. In addition, a plurality of architecture review and wall opening processes are required, and the process is complicated.
Disclosure of Invention
In view of the foregoing, there is a need for a subsystem management method, device, computer device and storage medium, which are used for solving the technical problem that the subsystem needs to be repeatedly developed.
A first aspect of the present invention provides a subsystem management method applied to a first computer device including a portal system, the method comprising:
configuring a transit interface for the portal system, wherein the portal system receives related requests sent by at least one subsystem from the transit interface, the at least one subsystem is installed in a second computer device, and the transit interface is an API interface;
the portal system analyzes the related request and acquires a return value corresponding to the related request; and
And the portal system calls the transfer interface to return the acquired return value to the at least one subsystem in a preset format.
Preferably, after the portal system receives the related request sent by the at least one subsystem from the transit interface, and before analyzing the related request and acquiring a return value corresponding to the related request, the portal system further includes:
when the related request is received, displaying a login page to the at least one subsystem, wherein the login page is used for the at least one subsystem to submit identity verification information;
receiving the identity verification information, verifying the identity of the at least one subsystem according to the received identity verification information, and determining whether the at least one subsystem passes the identity verification;
wherein when the at least one subsystem passes the authentication, resolving the related request; and
And when the at least one subsystem fails to pass the identity verification, continuing to display the login page to the at least one subsystem.
Preferably, the related request carries a URL address and a URL parameter of an interface to be accessed, where the parsing the related request and obtaining a return value corresponding to the related request include:
analyzing the received related request, and acquiring the URL of an interface to be accessed from the related request; and
And accessing the URL of the interface to be accessed, and acquiring a return value from the interface to be accessed according to the URL parameter in the related request.
Preferably, the related request carries a URL address of an interface to be accessed, but does not carry a URL parameter, where the parsing the related request and obtaining a return value corresponding to the related request includes:
sending a notification to the at least one subsystem to feed back the URL parameters;
receiving the URL parameter sent by the at least one subsystem; and
And accessing the URL of the interface to be accessed, and acquiring a return value from the interface to be accessed according to the received URL parameter.
Preferably, the at least one subsystem is a plurality of application systems respectively developed by different vendors at different times, the plurality of application systems being independent of each other.
Preferably, the types of the related requests include a POST request for updating resource information, a GET request for acquiring/querying resource information, a PUT request for adding resource information, and a DELETE request for deleting resource information.
Preferably, after the portal system returns the acquired return value to the at least one subsystem, the portal system further includes:
creating a request record for the at least one subsystem, wherein the request record includes a time at which the at least one subsystem sent the relevant request;
periodically acquiring the request record, and calculating the frequency of the at least one subsystem for sending the related request in preset time according to the request record; and
When the calculated frequency is larger than a preset value, a warning is sent out according to a preset warning mode.
A second aspect of the present invention provides a computer apparatus comprising a memory for storing at least one instruction and a processor for executing the at least one instruction to implement the subsystem management method.
A third aspect of the invention provides a computer readable storage medium storing at least one instruction that when executed by a processor implements the subsystem management method.
A fourth aspect of the present invention provides a subsystem management device, the device comprising:
the configuration module is used for configuring a transfer interface for a portal system of a first computer device, wherein the portal system receives related requests sent by at least one subsystem from the transfer interface, the at least one subsystem is installed in a second computer device, and the transfer interface is an API interface;
the execution module is used for triggering the portal system to analyze the related request and acquiring a return value corresponding to the related request; and
The execution module is further configured to trigger the portal system to call the transfer interface to return the acquired return value to the at least one subsystem in a preset format.
The subsystem management method, the device, the computer device and the storage medium are characterized in that a transit interface is configured for a portal system, wherein the portal system receives related requests sent by at least one subsystem from the transit interface; the portal system analyzes the related request and acquires a return value corresponding to the related request; and the portal system calls the transfer interface to return the acquired return value to the at least one subsystem in a preset format. The invention can realize a plurality of URL transfer requests by using one transfer interface, reduces the repeated development of subsystems and shortens the development period.
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 an application environment architecture diagram of a subsystem management method according to an embodiment of the present invention.
Fig. 2 is a flowchart of a subsystem management method according to a second embodiment of the present invention.
Fig. 3 is a block diagram of a subsystem management device according to a third embodiment of the present invention.
Fig. 4 is a schematic diagram of a first computer device according to a fourth embodiment of the present invention.
The invention will be further described in the following detailed description in conjunction with the above-described figures.
Detailed Description
In order that the above-recited objects, features and advantages of the present invention will be more clearly understood, a more particular description of the invention will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. It should be noted that, without conflict, the embodiments of the present invention and features in the embodiments may be combined with each other.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention, and the described embodiments are merely some, rather than all, embodiments of the present invention. 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.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used herein in the description of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.
Example 1
Referring to fig. 1, an application environment architecture diagram of a subsystem management method according to a first embodiment of the present invention is shown.
The subsystem management method is applied in an environment formed by a first computer device and one or more second computer devices. For example, in an environment constituted by a first computer device 3 and at least one second computer device 4.
The first computer device 3 may be communicatively coupled to the second computer device 4 via any conventional wired and/or wireless network. The wired network may be of any type of conventional wired communication, such as the internet, a local area network. The wireless network may be of any type of conventional wireless communication, such as radio, wireless fidelity (Wireless Fidelity, WIFI), cellular, satellite, broadcast, etc. The wireless communication technologies may include, but are not limited to, global system for mobile communications (Global System for Mobile Communications, GSM), general packet radio service (General Packet Radio Service, GPRS), code Division multiple access (Code Division Multiple Access, CDMA), wideband code Division multiple access (W-CDMA), CDMA2000, IMT single carrier (IMT Single Carrier), enhanced data rates for GSM Evolution (Enhanced Data Rates for GSM Evolution, EDGE), long Term Evolution (Long Term Evolution, LTE), long Term Evolution advanced (LTE), time Division Long Term Evolution (Time Division LTE, TD-LTE), high performance radio local area network (High Performance Radio Local Area Network, hiperLAN), high performance radio wide area network (High Performance Radio Wide Area Network, hiperWAN), local multipoint distribution service (Local Multipoint Distribution Service, LMDS), worldwide interoperability for all microwave access (Worldwide Interoperability for Microwave Access, wiMAX), zigBee), bluetooth, orthogonal frequency Division multiplexing (Flash Orthogonal Frequency-Division Multiplexing, flash-OFDM), high capacity space Division multiple access (High Capacity Spatial Division Multiple Access, HC-a), universal mobile telecommunication system (Universal Mobile Telecommunications System, UMTS), universal mobile telecommunication system Time Division duplex (UMTS Time-Division Duplexing, hspd), high speed packet access (Time Division Synchronous Code Division Multiple Access, UMTS), high speed Division multiple access (Evolved High Speed Packet Access, CDMA) and synchronous code Division multiple access (3567+) Evolution-Data Optimized (EV-DO), digital enhanced cordless telecommunications (Digital Enhanced Cordless Telecommunications, DECT), and others.
In this embodiment, the first computer device 3 may be a portal server. The second computer means 4 may be a server commonly used in the art.
Example two
Fig. 2 is a flowchart of a subsystem management method according to a second embodiment of the present invention.
In this embodiment, the subsystem management method may be applied to a first computer device, and for the first computer device that needs to perform subsystem management, the function for subsystem management provided by the method of the present invention may be directly integrated on the first computer device, or may be executed on the first computer device in the form of a software development kit (Software Development Kit, SDK).
As shown in fig. 2, the subsystem management method specifically includes the following steps, the order of the steps in the flowchart may be changed according to different requirements, and some steps may be omitted.
S1, the first computer device configures a transit interface for the portal system. The portal system receives the related request sent by at least one subsystem in the second computer device through the transit interface.
In one embodiment, the transit interface is an API interface (Application Programming Interface ).
In one embodiment, the at least one subsystem may be a plurality of application systems developed by different vendors at different times, respectively. The plurality of application systems are independent of each other. In one embodiment, the plurality of application systems may be installed in the same second computer device or in different second computer devices, respectively.
In one embodiment, each of the at least one subsystem has its own user identity verification module and rights management policy. In this embodiment, the portal system may perform unified management on the user of each subsystem in the at least one subsystem, so as to achieve the purposes of single sign-on and unified identity verification.
In one embodiment, the at least one subsystem may be a business system within an enterprise. For example, the at least one subsystem includes, but is not limited to, an enterprise's human resource management system, a mailing system, a financial system, and the like.
The human resource management system can be used for managing incumbent staff, off-staff, staff off-staff rate and the like of an enterprise.
The mail receiving and sending system is used for enabling employees of the enterprise to receive and send mails among each other to realize information transmission and the like.
The financial system is used for managing salary, company operation cost, profit and other data of enterprise staff.
In one embodiment, the type of related request sent by the at least one subsystem includes, but is not limited to, a POST request, a GET request, a PUT request, a DELETE request, and the like. The POST request may be used to update resource information, the GET request may be used to obtain/query resource information, the PUT request may be used to add resource information, and the DELETE request may be used to DELETE resource information. In general, the operations of adding, deleting, modifying and checking the resource can be completed through a POST request or a GET request, i.e. the PUT request and the DELETE request are not needed.
In a first embodiment, the related request carries a URL (Uniform Resource Locator ) address, URL parameters of the interface to be accessed.
In a second embodiment, the related request carries the URL (Uniform Resource Locator ) address of the interface to be accessed, but does not carry the URL parameter.
S2, the portal system receives the related request sent by the at least one subsystem from the transit interface.
In one embodiment, the type of related request may be a POST request, a GET request, a PUT request, or other types of requests such as a DELETE request.
And S3, when the portal system receives the related request, displaying a login page to the at least one subsystem, wherein the login page is used for submitting authentication information (such as a user name and a password) to the at least one subsystem.
S4, the portal system receives the identity verification information submitted by the at least one subsystem from the login page, verifies the identity of the at least one subsystem according to the received identity verification information, and determines whether the at least one subsystem passes the identity verification.
If the at least one subsystem passes the authentication, step S5 is executed. If the at least one subsystem fails to pass the authentication, returning to step S3, and continuing to display the login page to the at least one subsystem by the portal system.
In other embodiments, step S5 may be directly performed after step S2 is performed. I.e. steps S3-S4 are not included, the identity of the at least one subsystem is not verified.
S5, the portal system analyzes the related request and acquires a return value corresponding to the related request.
In a first embodiment, when the related request carries a URL (UniformResource Locator ) address and URL parameters of an interface to be accessed, the parsing the related request and obtaining a return value corresponding to the related request includes:
(a1) Analyzing the received related request, and acquiring the URL of the interface to be accessed from the related request.
(a2) And accessing the URL of the interface to be accessed, and acquiring a return value from the interface to be accessed according to the URL parameter in the related request.
In a second embodiment, when the related request carries a URL address of an interface to be accessed, but does not carry a URL parameter, the parsing the related request and obtaining a return value corresponding to the related request includes:
(b1) And sending a notification feeding back the URL parameter to the at least one subsystem.
And the at least one subsystem sends the URL parameter to the portal system when receiving the notification.
(b2) And receiving the URL parameter sent by the at least one subsystem.
(b3) And accessing the URL of the interface to be accessed, and acquiring a return value from the interface to be accessed according to the received URL parameter.
S6, the portal system calls the transfer interface to return the acquired return value to the at least one subsystem in a preset format. Thus, the at least one subsystem may obtain a return value corresponding to the related request.
In one embodiment, the preset format is JSON format.
It should be noted that, because the JSON format is compressed and occupies a small bandwidth, server resources can be better saved, network transmission time is reduced, and network transmission speed is increased.
In other embodiments, the portal system further:
(c1) When the acquired return value is returned to the at least one subsystem, a request record is created for the at least one subsystem.
In one embodiment, the request records include, but are not limited to, a time at which the at least one subsystem sent the relevant request, a time at which a return value was returned to the at least one subsystem. In other embodiments, the request record may further include a related request sent by the at least one subsystem, and the acquired return value corresponding to the related request.
In particular, the time at which the at least one subsystem sends the relevant request may refer to a system time of the first computer device when the relevant request is received, and the time at which the return value is returned to the at least one subsystem may refer to a system time of the first computer device when the return value is returned to the at least one subsystem.
(c2) The request records are periodically obtained and the frequency with which the at least one subsystem transmits the relevant requests within a preset time (e.g., 1 minute, 1 hour, half a day, or one day) is calculated from the request records.
(c3) And judging whether the calculated frequency is larger than a preset value. And when the calculated frequency is larger than the preset value, sending out an alarm according to a preset alarm mode. And when the calculated frequency is smaller than or equal to the preset value, not giving out the warning.
It should be noted that, when the calculated frequency is greater than the preset value, an alarm is sent, and the user may be prompted by the alarm to detect whether the at least one subsystem is infected with a virus, so that the frequency of the at least one subsystem sending the related request in the preset time is greater than the preset value.
In one embodiment, the preset warning mode includes, but is not limited to, displaying preset warning information on a display screen of the first computer device, and sending the warning information to a preset terminal device. In summary, in the subsystem management method described in the embodiment of the present invention, a transit interface is configured for a portal system; the portal system receives the related request sent by at least one subsystem from the transfer interface, analyzes the related request and acquires a return value corresponding to the related request; and the portal system calls the transfer interface to return the acquired return value to the at least one subsystem in a preset format, so that a plurality of URL transfer requests can be realized by using one transfer interface, the repeated development of the subsystem is reduced, and the development period is shortened.
The above-mentioned fig. 2 describes the subsystem management method of the present invention in detail, and the following describes, with reference to fig. 3 to 4, the functional modules of the software device implementing the subsystem management method and the hardware device architecture implementing the subsystem management method.
It should be understood that the embodiments described are for illustrative purposes only and are not limited to this configuration in the scope of the patent application.
Example III
Referring to fig. 3, a block diagram of a subsystem management device according to a third embodiment of the present invention is shown.
In some embodiments, the subsystem management device 30 is running in a first computer device. The first computer device is connected with a second computer device through a network. The subsystem management device 30 may include a plurality of functional modules that are comprised of program code segments. Program code for each program segment in the subsystem management device 30 may be stored in a memory of a first computer device and executed by at least one processor of the first computer device to implement the subsystem management functions (described in detail with respect to fig. 2).
In this embodiment, the subsystem management device 30 may be divided into a plurality of functional modules according to the functions performed by the subsystem management device. The functional module may include: configuration module 301, execution module 302. The module referred to in the present invention refers to a series of computer program segments capable of being executed by at least one processor and of performing a fixed function, stored in a memory. In the present embodiment, the functions of the respective modules will be described in detail in the following embodiments. It should be noted that, the subsystem management device 30 may be integrated with the portal system of the first computer device into one system.
The configuration module 301 configures a transit interface for the portal system of the first computer device. The portal system receives the related request sent by at least one subsystem in the second computer device through the transit interface.
In one embodiment, the transit interface is an API interface (Application Programming Interface ).
In one embodiment, the at least one subsystem may be a plurality of application systems developed by different vendors at different times, respectively. The plurality of application systems are independent of each other. In one embodiment, the plurality of application systems may be installed in the same second computer device or in different second computer devices, respectively.
In one embodiment, each of the at least one subsystem has its own user identity verification module and rights management policy. In this embodiment, the portal system may perform unified management on the user of each subsystem in the at least one subsystem, so as to achieve the purposes of single sign-on and unified identity verification.
In one embodiment, the at least one subsystem may be a business system within an enterprise. For example, the at least one subsystem includes, but is not limited to, an enterprise's human resource management system, a mailing system, a financial system, and the like.
The human resource management system can be used for managing incumbent staff, off-staff, staff off-staff rate and the like of an enterprise.
The mail receiving and sending system is used for enabling employees of the enterprise to receive and send mails among each other to realize information transmission and the like.
The financial system is used for managing salary, company operation cost, profit and other data of enterprise staff.
In one embodiment, the type of related request sent by the at least one subsystem includes, but is not limited to, a POST request, a GET request, a PUT request, a DELETE request, and the like. The POST request may be used to update resource information, the GET request may be used to obtain/query resource information, the PUT request may be used to add resource information, and the DELETE request may be used to DELETE resource information. In general, the operations of adding, deleting, modifying and checking the resource can be completed through a POST request or a GET request, i.e. the PUT request and the DELETE request are not needed.
In a first embodiment, the related request carries a URL (Uniform Resource Locator ) address, URL parameters of the interface to be accessed.
In a second embodiment, the related request carries the URL (Uniform Resource Locator ) address of the interface to be accessed, but does not carry the URL parameter.
The portal system receives from the transit interface the related requests sent by the at least one subsystem.
In one embodiment, the type of related request may be a POST request, a GET request, a PUT request, or other types of requests such as a DELETE request.
The execution module 302 triggers the portal system to present a login page to the at least one subsystem when the portal system receives the related request, wherein the login page is used for the at least one subsystem to submit authentication information (such as a user name and a password).
The execution module 302 triggers the portal system to receive the authentication information and to verify the identity of the at least one subsystem based on the received authentication information, determining whether the at least one subsystem passes the authentication.
If the at least one subsystem passes the authentication, the execution module 302 triggers the portal system to analyze the related request, and obtains a return value corresponding to the related request. If the at least one subsystem fails the authentication, the execution module 302 triggers the portal system to continue displaying the log-in page to the at least one subsystem.
It should be noted that, in other embodiments, the execution module 302 may trigger the portal system to parse the related request and obtain a return value corresponding to the related request after the portal system receives the related request sent by the at least one subsystem from the transit interface. I.e. without verifying the identity of the at least one subsystem.
The execution module 302 triggers the portal system to parse the related request, and obtains a return value corresponding to the related request.
In a first embodiment, when the related request carries a URL (Uniform Resource Locator ) address and URL parameters of an interface to be accessed, the parsing the related request and obtaining a return value corresponding to the related request includes:
(a1) Analyzing the received related request, and acquiring the URL of the interface to be accessed from the related request.
(a2) And accessing the URL of the interface to be accessed, and acquiring a return value from the interface to be accessed according to the URL parameter in the related request.
In a second embodiment, when the related request carries a URL address of an interface to be accessed, but does not carry a URL parameter, the parsing the related request and obtaining a return value corresponding to the related request includes:
(b1) And sending a notification feeding back the URL parameter to the at least one subsystem.
And the at least one subsystem sends the URL parameter to the portal system when receiving the notification.
(b2) And receiving the URL parameter sent by the at least one subsystem.
(b3) And accessing the URL of the interface to be accessed, and acquiring a return value from the interface to be accessed according to the received URL parameter.
The execution module 302 triggers the portal system to call the transit interface to return the acquired return value to the at least one subsystem in a preset format. Thus, the at least one subsystem may obtain a return value corresponding to the related request.
In one embodiment, the preset format is JSON format.
It should be noted that, because the JSON format is compressed and occupies a small bandwidth, server resources can be better saved, network transmission time is reduced, and network transmission speed is increased.
In other embodiments, the execution module 302 also triggers the portal system to further:
(c1) When the acquired return value is returned to the at least one subsystem, a request record is created for the at least one subsystem.
In one embodiment, the request records include, but are not limited to, a time at which the at least one subsystem sent the relevant request, a time at which a return value was returned to the at least one subsystem. In other embodiments, the request record may further include a related request sent by the at least one subsystem, and the acquired return value corresponding to the related request.
In particular, the time at which the at least one subsystem sends the relevant request may refer to a system time of the first computer device when the relevant request is received, and the time at which the return value is returned to the at least one subsystem may refer to a system time of the first computer device when the return value is returned to the at least one subsystem.
(c2) The request records are periodically obtained and the frequency with which the at least one subsystem transmits the relevant requests within a preset time (e.g., 1 minute, 1 hour, half a day, or one day) is calculated from the request records.
(c3) And judging whether the calculated frequency is larger than a preset value. And when the calculated frequency is larger than the preset value, sending out an alarm according to a preset alarm mode. And when the calculated frequency is smaller than or equal to the preset value, not giving out the warning.
It should be noted that, when the calculated frequency is greater than the preset value, an alarm is sent, and the user may be prompted by the alarm to detect whether the at least one subsystem is infected with a virus, so that the frequency of the at least one subsystem sending the related request in the preset time is greater than the preset value.
In one embodiment, the preset warning mode includes, but is not limited to, displaying preset warning information on a display screen of the first computer device, and sending the warning information to a preset terminal device.
In summary, in the subsystem management device according to the embodiment of the present invention, a transit interface is configured for a portal system, where the portal system receives, from the transit interface, a related request sent by at least one subsystem; analyzing the related request and acquiring a return value corresponding to the related request; and triggering the portal system to call the transfer interface to return the acquired return value to the at least one subsystem in a preset format, so that a plurality of URL transfer requests can be realized by using one transfer interface, the repeated development of the subsystem is reduced, and the development period is shortened.
Example IV
Fig. 4 is a schematic structural diagram of a first computer device according to a fourth embodiment of the invention. In the preferred embodiment of the present invention, the first computer device 3 includes a memory 31, at least one processor 32, at least one communication bus 33, and a portal system 34. It will be appreciated by those skilled in the art that the configuration of the first computer device shown in fig. 3 is not limiting of the embodiments of the present invention, and that it may be a bus type configuration or a star type configuration, and that the first computer device 3 may also include more or less other hardware or software than illustrated, or a different arrangement of components.
In some embodiments, the first computer device 3 includes a terminal capable of automatically performing numerical calculation and/or information processing according to a preset or stored instruction, and its hardware includes, but is not limited to, a microprocessor, an application specific integrated circuit, a programmable gate array, a digital processor, an embedded device, and the like.
It should be noted that the first computer device 3 is only used as an example, and other electronic products that may be present in the present invention or may be present in the future are also included in the scope of the present invention by way of reference.
In some embodiments, the memory 31 is used to store program codes and various data, such as a subsystem management device 30 installed in the first computer device 3, and to implement high-speed, automatic access to programs or data during operation of the first computer device 3. The Memory 31 includes Read-Only Memory (ROM), random-access Memory (Random Access Memory, RAM), programmable Read-Only Memory (Programmable Read-Only Memory, PROM), erasable programmable Read-Only Memory (EPROM), one-time programmable Read-Only Memory (OTPROM), electrically erasable rewritable Read-Only Memory (EEPROM), compact disc Read-Only Memory (Compact Disc Read-Only Memory, CD-ROM) or other optical disc Memory, magnetic disk Memory, magnetic tape Memory, or any other medium that can be used for carrying or storing data.
In some embodiments, the at least one processor 32 may be comprised of an integrated circuit, for example, a single packaged integrated circuit, or may be comprised of multiple integrated circuits packaged with the same or different functions, including one or more central processing units (Central Processing unit, CPU), microprocessors, digital processing chips, graphics processors, combinations of various control chips, and the like. The at least one processor 32 is a Control Unit (Control Unit) of the first computer device 3, connects the respective components of the entire first computer device 3 using various interfaces and lines, and performs various functions of the first computer device 3 and processes data, such as performing functions of management of subsystems in the second computer device 4, by running or executing programs or modules stored in the memory 31, and calling data stored in the memory 31.
In some embodiments, the at least one communication bus 33 is arranged to enable connected communication between the memory 31 and the at least one processor 32 or the like.
Although not shown, the first computer means 3 may further comprise a power source (such as a battery) for powering the various components, preferably the power source may be logically connected to the at least one processor 32 by power management means, whereby the functions of managing charging, discharging, and power consumption are performed by the power management means. The power supply may also include one or more of any of a direct current or alternating current power supply, recharging device, power failure detection circuit, power converter or inverter, power status indicator, etc. The first computer device 3 may further include various sensors, bluetooth modules, wi-Fi modules, etc., which will not be described herein.
It should be understood that the embodiments described are for illustrative purposes only and are not limited to this configuration in the scope of the patent application.
The integrated units implemented in the form of software functional modules described above may be stored in a computer readable storage medium. The software functional modules described above are stored in a storage medium and include instructions for causing a computer device (which may be a server, a personal computer, etc.) or a processor (processor) to perform portions of the methods described in the various embodiments of the invention.
In a further embodiment, in connection with fig. 3, the at least one processor 32 may execute the operating device of the first computer device 3 and various installed applications (such as the subsystem management device 30), program code, etc., such as the various modules described above.
The memory 31 has program code stored therein, and the at least one processor 32 can invoke the program code stored in the memory 31 to perform related functions. For example, each of the modules depicted in fig. 3 is a program code stored in the memory 31 and executed by the at least one processor 32 to perform the functions of the respective module for the purpose of managing the subsystem 41 of the second computer device 4.
In one embodiment of the invention, the memory 31 stores a plurality of instructions that are executed by the at least one processor 32 for the purpose of managing the subsystem 41 of the second computer device 4.
Specifically, the specific implementation method of the above instruction by the at least one processor 32 may refer to the description of the relevant steps in the corresponding embodiment of fig. 2, which is not repeated herein.
In the several embodiments provided in the present invention, it should be understood that the disclosed apparatus, device and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is merely a logical function division, and there may be other manners of division when actually implemented.
The modules described as separate components may or may not be physically separate, and components shown as modules may or may not be physical units, may be located in one place, or may be distributed over multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional module in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units can be realized in a form of hardware or a form of hardware and a form of software functional modules.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it will be obvious that the term "comprising" does not exclude other elements or that the singular does not exclude a plurality. A plurality of units or means recited in the apparatus claims can also be implemented by means of one unit or means in software or hardware. The terms first, second, etc. are used to denote a name, but not any particular order.
Finally, it should be noted that the above-mentioned embodiments are merely for illustrating the technical solution of the present invention and not for limiting the same, and although the present invention has been described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that modifications and equivalents may be made to the technical solution of the present invention without departing from the spirit and scope of the technical solution of the present invention.
Claims (10)
1. A sub-system management method applied to a first computer device comprising a portal system, the method comprising:
configuring a transit interface for the portal system, wherein the portal system receives related requests sent by at least one subsystem from the transit interface, the at least one subsystem is installed in a second computer device, and the transit interface is an API interface;
the portal system analyzes the related request and acquires a return value corresponding to the related request;
the portal system calls the transfer interface to return the acquired return value to the at least one subsystem in a preset format;
creating a request record for the at least one subsystem, wherein the request record includes a time at which the at least one subsystem sent the relevant request;
periodically acquiring the request record, and calculating the frequency of the at least one subsystem for sending the related request in preset time according to the request record; and
When the calculated frequency is larger than a preset value, sending out an alarm according to a preset alarm mode to prompt a user to detect whether viruses exist in the at least one subsystem.
2. The subsystem management method according to claim 1, wherein after the portal system receives the related request sent by the at least one subsystem from the transit interface, and before parsing the related request and acquiring the return value corresponding to the related request, the portal system further includes:
when the related request is received, displaying a login page to the at least one subsystem, wherein the login page is used for the at least one subsystem to submit identity verification information;
receiving the identity verification information, verifying the identity of the at least one subsystem according to the received identity verification information, and determining whether the at least one subsystem passes the identity verification;
wherein when the at least one subsystem passes the authentication, resolving the related request; and
And when the at least one subsystem fails to pass the identity verification, continuing to display the login page to the at least one subsystem.
3. The subsystem management method according to claim 1, wherein the related request carries a URL address and a URL parameter of an interface to be accessed, and wherein the parsing the related request and obtaining a return value corresponding to the related request includes:
analyzing the received related request, and acquiring the URL of an interface to be accessed from the related request; and
And accessing the URL of the interface to be accessed, and acquiring a return value from the interface to be accessed according to the URL parameter in the related request.
4. The subsystem management method according to claim 1, wherein the related request carries a URL address of an interface to be accessed but does not carry a URL parameter, and wherein the parsing the related request and obtaining a return value corresponding to the related request includes:
sending a notification to the at least one subsystem to feed back the URL parameters;
receiving the URL parameter sent by the at least one subsystem; and
And accessing the URL of the interface to be accessed, and acquiring a return value from the interface to be accessed according to the received URL parameter.
5. The subsystem management method of claim 1, wherein the at least one subsystem is a plurality of application systems developed by different vendors at different times, respectively, the plurality of application systems being independent of each other.
6. The subsystem management method of claim 1, wherein the types of related requests include a POST request for updating resource information, a GET request for retrieving/querying resource information, a PUT request for adding resource information, a PUT request for deleting resource information, a DELETE request.
7. The subsystem management method of claim 1, wherein the user authentication module and the rights management policy of each of the at least one subsystem are different from each other.
8. A computer device, characterized in that it comprises a memory for storing at least one instruction and a processor for executing said at least one instruction to implement the subsystem management method according to any one of claims 1 to 7.
9. A computer readable storage medium storing at least one instruction which when executed by a processor implements the subsystem management method of any one of claims 1 to 7.
10. A subsystem management device, the device comprising:
the configuration module is used for configuring a transfer interface for a portal system of a first computer device, wherein the portal system receives related requests sent by at least one subsystem from the transfer interface, the at least one subsystem is installed in a second computer device, and the transfer interface is an API interface;
the execution module is used for triggering the portal system to analyze the related request and acquiring a return value corresponding to the related request;
the execution module is further configured to trigger the portal system to call the transfer interface to return the acquired return value to the at least one subsystem in a preset format;
the execution module is further configured to create a request record for the at least one subsystem, where the request record includes a time when the at least one subsystem sent the related request; periodically acquiring the request record, and calculating the frequency of the at least one subsystem for sending the related request in preset time according to the request record; and when the calculated frequency is greater than a preset value, sending out an alarm according to a preset alarm mode to prompt a user to detect whether the at least one subsystem is virus or not.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910018373.4A CN109885779B (en) | 2019-01-09 | 2019-01-09 | Subsystem management method, device, computer device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910018373.4A CN109885779B (en) | 2019-01-09 | 2019-01-09 | Subsystem management method, device, computer device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109885779A CN109885779A (en) | 2019-06-14 |
| CN109885779B true CN109885779B (en) | 2024-04-02 |
Family
ID=66925771
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910018373.4A Active CN109885779B (en) | 2019-01-09 | 2019-01-09 | Subsystem management method, device, computer device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109885779B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111324780A (en) * | 2020-02-28 | 2020-06-23 | 北京三快在线科技有限公司 | Storage method, transmission method, device and storage medium of product data |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2005033351A (en) * | 2003-07-09 | 2005-02-03 | Hitachi Information Technology Co Ltd | Packet relaying apparatus |
| US7111086B1 (en) * | 2002-02-22 | 2006-09-19 | Vmware, Inc. | High-speed packet transfer in computer systems with multiple interfaces |
| CN101931715A (en) * | 2009-06-19 | 2010-12-29 | 中兴通讯股份有限公司 | Customer service system and cross-platform monitoring method therein |
| CN106210099A (en) * | 2016-07-18 | 2016-12-07 | 珠海格力电器股份有限公司 | Data handling system and method |
| CN108243183A (en) * | 2017-12-20 | 2018-07-03 | 北京车和家信息技术有限公司 | Integrated control method, system and the computer equipment of gate system |
| CN108717435A (en) * | 2018-05-16 | 2018-10-30 | 腾讯科技（深圳）有限公司 | Webpage loading method, information processing method, computer equipment and storage medium |
-
2019
- 2019-01-09 CN CN201910018373.4A patent/CN109885779B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7111086B1 (en) * | 2002-02-22 | 2006-09-19 | Vmware, Inc. | High-speed packet transfer in computer systems with multiple interfaces |
| JP2005033351A (en) * | 2003-07-09 | 2005-02-03 | Hitachi Information Technology Co Ltd | Packet relaying apparatus |
| CN101931715A (en) * | 2009-06-19 | 2010-12-29 | 中兴通讯股份有限公司 | Customer service system and cross-platform monitoring method therein |
| CN106210099A (en) * | 2016-07-18 | 2016-12-07 | 珠海格力电器股份有限公司 | Data handling system and method |
| CN108243183A (en) * | 2017-12-20 | 2018-07-03 | 北京车和家信息技术有限公司 | Integrated control method, system and the computer equipment of gate system |
| CN108717435A (en) * | 2018-05-16 | 2018-10-30 | 腾讯科技（深圳）有限公司 | Webpage loading method, information processing method, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109885779A (en) | 2019-06-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11750444B2 (en) | Implementation of compliance settings by a mobile device for compliance with a configuration scenario | |
| EP2437524A1 (en) | M2m service platform and work method thereof | |
| CN109327490B (en) | Method and server for deploying cloud service component | |
| CN110505162B (en) | Message transmission method and device and electronic equipment | |
| CN109150904A (en) | Interface service call method and terminal device | |
| US20120131135A1 (en) | Nonconforming web service policy functions | |
| CN111177112A (en) | Database blocking method and device based on operation and maintenance management system and electronic equipment | |
| CN111355622A (en) | Container traffic monitoring method, system and computer readable storage medium | |
| CN112395107A (en) | Tax control equipment control method and device, storage medium and electronic equipment | |
| CN110704131B (en) | Method and device for calling native application by HTML5 application | |
| CN109885779B (en) | Subsystem management method, device, computer device and storage medium | |
| US10701073B2 (en) | Terminal authentication method and device | |
| CN113885971A (en) | State management method and device based on self-adaptive platform system | |
| WO2015003570A1 (en) | Data downloading method,device and system thereof | |
| CN116302561A (en) | State control method, device, equipment and storage medium for application instance | |
| CN114449030B (en) | Internet service system, method, electronic equipment and storage medium | |
| CN113360172B (en) | Application deployment method, device, computer equipment and storage medium | |
| CN114170700A (en) | Attendance checking method and device | |
| CN110286907B (en) | Display method and device of public button assembly | |
| CN112632192A (en) | Node maintenance method and device, computer equipment and medium | |
| CN112199078A (en) | Toast message pushing method and device based on android fragment component and computer equipment | |
| US20140201839A1 (en) | Identification and alerting of network devices requiring special handling maintenance procedures | |
| CN109413647B (en) | Data sharing method and device, electronic equipment and computer readable storage medium | |
| CN114721740B (en) | Message triggering method, device, equipment and storage medium | |
| US20230319559A1 (en) | Enrollment of enrollee devices to a wireless network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |