A service deployment method and a service deployment system for system applications

Abstract

The present invention relates to a service deployment method and a service deployment system for system applications. The method of the present invention includes: starting the application to stop the service, randomly generating a release password and hot zone information, pushing a unified service stop interface to all clients accessing the application, and feeding back the release password and hot zone information to the personnel responsible for the application service. The hot zone information includes the hot zone positions and hot zone trigger rules on the service stop interface. The service stop interface is a static picture for external users, while the personnel responsible for the application service can operate according to the hot zone trigger rules at the hot zone positions on the service stop interface to obtain the login interface and use the release password to log in and start the application service. The present invention can simplify and standardize the start / stop service management and control of applications, unify the access technical standards, reduce the access cost, improve the user experience, and at the same time flexibly manage all applications of different platforms and different types.

Description

Technical Field

[0001] The present invention relates to an enterprise computer system, and particularly to a service deployment method and a service deployment system. Background Art

[0002] The computer systems of modern enterprises often involve various applications on the internal and external networks, and each application often needs to run in different forms on different types of platforms (such as mini-programs, APPs on Android or IOS, and Web terminals).

[0003] When service changes (such as application release or upgrade) are required, it usually has a great impact on external users using various types of platforms. Therefore, it is necessary to temporarily stop the service of the application and then enable the service after the change is completed. At present, due to the scattered management of different applications or different platforms with inconsistent standards, starting and stopping maintenance is not convenient enough, and the integration and control of multiple platforms and multiple applications cannot be achieved. When enterprise IT internal test users perform service changes, the workload is large, and at the same time, it also affects the use of applications by external users.

[0004] Therefore, it is necessary to simplify and standardize the start / stop service management and control of all internal and external network applications, unify the access technology standards, reduce the access cost, improve the user experience, and at the same time, flexibly manage all different platforms and different types of applications according to the application characteristics of each system. Summary of the Invention

[0005] The Summary of the Invention is provided to introduce some concepts that will be further described in detail below in a simplified form. The Summary of the Invention is not intended to identify the key features or essential features of the claimed subject matter; nor is it intended to be used to determine or limit the scope of the claimed subject matter.

[0006] The service deployment method and service deployment system of the present invention can achieve unified and complete plug-in management of start / stop services for application services. The service deployment system provides a set of plug-ins that are business-insensitive and non-intrusive. In this way, as long as the application to be controlled is connected to the service deployment system, the application will be hosted by the service deployment system, and when service changes are required, flexible configuration can be performed according to the situation. This helps to improve the management ability of enterprise IT systems, improve the convenience of starting and stopping maintenance of different applications, and ensure the user experience.

[0007] A service deployment method for system applications according to the present invention includes: starting the application outage, changing the outage status information, randomly generating a release password and hot zone information. The application outage is independently performed for a certain or certain platforms, and only affects the clients accessing the application through the outage platforms during the outage period; pushing a unified outage interface to all clients accessing the application; feeding back the release password and hot zone information to the internal testers responsible for the application service. The hot zone information includes the invisible hot zone positions and hot zone trigger rules on the outage interface; wherein the outage interface is a static picture for external users, while the personnel responsible for the application service can operate at the hot zone positions on the outage interface according to the hot zone trigger rules to obtain the login interface and log in using the release password to start work such as application upgrade and release. After the application outage, automatically poll and query the outage status, detect whether the application service is completed, and return the outage status information.

[0008] Among them, the outage status information, release password and hot zone information are stored in the buffer. When an external user accesses the application through the client, the cached outage status information in the buffer is called to query the service status to determine whether it is in the outage state. At the same time, it is checked whether there is a release password in the buffer. The external user can only obtain the feedback of whether there is a release password or not. When the internal testers responsible for the application service access the application through the client, they check whether there is a release password in the buffer. If there is, they obtain the release password and at the same time obtain the hot zone information. The hot zone trigger rule is a gesture operation performed at the hot zone position on the outage interface within a specified time, which is used to activate the login interface for the personnel responsible for the application service to input the release password.

[0009] A service deployment system for system applications according to the present invention includes: a buffer, an interface control module, a password configuration interaction module, a password generator, and a polling module built in the client. Among them:

[0010] The buffer is used to store the outage status information, release password, and hot zone information;

[0011] The interface control module is used to receive the requests of all clients accessing the application, retrieve the outage status information, release password, and hot zone information stored in the buffer, and when it is confirmed that it is in the outage state, feedback the outage interface to the clients requesting to access the application. If the client is the client of the internal testers responsible for the application service, further feedback the release password and hot zone information to the client of the internal testers responsible for the application service. When the internal testers responsible for the application service operate at the hot zone positions on the outage interface according to the hot zone trigger rules, provide the login interface for the internal testers responsible for the application service to log in using the release password;

[0012] The password configuration interaction module is used for the administrator to edit the outage configuration;

[0013] A password generator for generating a service suspension password and hot zone information;

[0014] A polling module for automatically polling the service suspension status after the application is suspended, detecting whether the application service is completed, and returning the service suspension status information.

[0015] These and other features and advantages will become apparent by reading the following detailed description and referring to the associated drawings. It should be understood that the foregoing general description and the following detailed description are illustrative only and do not limit the various aspects claimed. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The present invention will be described more specifically below by reference to specific embodiments shown in the drawings.

[0017] Figure 1 is a schematic diagram of the service deployment process of the service deployment system of the present invention;

[0018] Figure 2 is an example of a service suspension maintenance page;

[0019] Figure 3 Virtually shows Figure 2 the hot zones in the service suspension maintenance page of

[0020] Figure 4 is an example of the login interface when internal testers perform application maintenance.

[0021] The drawings show the possible architectures, functions, and operations of a system and method according to an embodiment of the present application. In this regard, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code that contains one or more executable instructions for implementing a specified logical function. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0022] The present invention will be described more specifically below by reference to specific embodiments shown in the drawings. By reading the detailed description of the following specific embodiments, various advantages and benefits of the present invention will become clear to those of ordinary skill in the art. However, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. The following embodiments are provided to enable a more thorough understanding of the present invention. Unless otherwise specified, the technical terms or scientific terms used in this application should have the ordinary meaning understood by those skilled in the art to which this application belongs.

[0023] The service deployment system of the present invention is a business-insensitive and non-invasive plug-in that is deployed at the system entrance. Requests (whether from external users or from enterprise IT internal testers) are first received by the service deployment system. In the out-of-service state, both external users and enterprise IT internal testers receive the same " Figure 2 shown 'Out-of-service Maintenance Page' (out-of-service interface). The difference is that external users can only wait for the maintenance to complete, while enterprise IT employees log in through the 'Out-of-service Maintenance Page' in a pre-set manner and then perform maintenance work.

[0024] As Figure 1 shown, the service deployment system of the present invention includes an interface control module, a password configuration interaction module, a password generator, a buffer at the system end, and a polling module (not shown) embedded in the client.

[0025] The following combines Figure 1 to describe the service deployment process of the present invention from three perspectives starting from the respective clients of external users, enterprise IT administrators, and enterprise IT internal testers.

[0026] 1. External users: Use a certain application via the Internet through a platform (such as a small program, APP, Web).

[0027] External users initiate a request to use the application through the client platform.

[0028] The interface module of the service deployment system receives this request in step S11.

[0029] In step S12, the message cached in the buffer is called to query the service status to determine whether the platform is in the out-of-service state. At the same time, the cached message is called to verify the release password to check whether there is a release password.

[0030] Here, through the query of the out-of-service state and the release password double-cached messages, the accuracy of the judgment result can be ensured. Although Figure 1 not shown in [reference], the inventor also envisions that in order to prevent misjudgment in the case of cache errors, when neither the out-of-service state nor the release password is queried, mongoDB can also be queried for a fallback confirmation.

[0031] If it is determined that the platform service status is not out of service and there is no release password, that is, the service status is the business state and the application can be used normally, then in step S13, the request of the external user for the application is processed normally, the application is called normally and the result is returned to the client.

[0032] If the platform is in a shutdown state and there is a release password, indicating that the service status is the release state, then in step S14, the requests of external users are intercepted, and a 'Shutdown and Maintenance Page' as shown in, for example, Figure 2 is popped up through the client of the external user to inform the application of the current shutdown and release message, Figure 2 and the name of the shutdown application is illustrated by the 'Application' icon in.

[0033] For external users, Figure 2 the interface of is a static picture. The static picture supports dynamic switching and CDN cache acceleration, but external users cannot perform any operations and can only wait until the maintenance is over to use the application. At this time, external users can also manually refresh the page to initiate a request again, and then return to step S11 to re-judge the service status.

[0034] 2. Enterprise IT administrators: Use the system for the internal management background to interact with the password configuration interaction module of the service deployment system to manage the start and stop of applications.

[0035] By default, none of the platforms are selected, indicating that all platforms are in the service status.

[0036] When an enterprise IT administrator starts the shutdown of an application on one or more platforms in step S21, they interact with the password configuration interaction module of the service deployment system.

[0037] In step S22, the start / stop service configuration is edited through the page, and the platforms to be shut down are selected. The selection can be single or multiple. For example, assume that this application upgrade is only for the application under IOS, then only IOS is selected. If it is for the mini-program and Android platforms, then the mini-program and Android are selected.

[0038] Each time the shutdown is started, the password generator in the service deployment system will randomly generate a release password in step S23. The release password can be eight pure digits, and it can be required that the repeated digits of the password do not exceed 3 digits. Each time the shutdown is started, a hot zone is also randomly defined and a hot zone trigger rule (collectively referred to as hot zone information) is formulated. As shown in the interface of, for example, the exemplary hot zone is on the right side of the application icon (please note that Figure 3 the area is colored and framed to show the position of the hot zone, but it cannot be seen by the human eye actually), and the trigger rule can be set, for example, to click 3 times within 2 seconds (this is just an example, and other click times or gestures can be imagined). The shutdown configuration is saved in mongoDB (an exemplary shutdown configuration table is shown below, involving tables, data field information). The application enters the shutdown state on the corresponding platform. Figure 3 Shutdown Configuration Table - mongo (osc.stopServiceConfig)

[0039] Shutdown Configuration Table - mongo (osc.stopServiceConfig)

[0040]

[0041] In step S24, information such as the service suspension status and release password in the buffer is updated, which can be used for query in the aforementioned step S12 and can also be called by the following steps S32 and S42.

[0042] 3. Enterprise IT internal testers: Responsible for the specific work of service changes (such as application release and upgrade, etc.).

[0043] After the enterprise IT administrator starts the service suspension, the enterprise IT internal testers request the release password and hot zone information (including hot zone location and hot zone trigger rules) in step S31.

[0044] After receiving the request from the internal testers in step S32, the interface control module of the service deployment system calls the message in the buffer, queries the current release password and the last update time, queries the current hot zone location and hot zone trigger rules, and returns them to the IT internal testers.

[0045] Although the interface shown to the internal testers is the 'Service Suspension Maintenance Page' as shown in Figure 2 and the appearance of this page is exactly the same as the static picture seen by the aforementioned external users. However, because the internal testers also know the hot zone location and hot zone trigger rules, therefore, the internal testers seem to see Figure 3 like that (please note that Figure 3 the coloring and framing of the hot zone location are virtual and are only for explaining the present invention).

[0046] At this time, taking the previous example, the internal testers can quickly click the screen 3 times (within 2 seconds) in the hot zone on the right side of the application icon, for example, on the 'Service Suspension Maintenance Page', and a login page as shown in Figure 4 will pop up. After the internal testers input the release password obtained in the aforementioned step S32 into the login page, they can perform operations such as application upgrade.

[0047] In addition, the present invention also includes a service suspension polling mechanism.

[0048] After the service suspension state is started, the polling module in the client automatically polls every few seconds (the interval time can be configured) in step S41 to query the service suspension state and detect whether the application upgrade has been completed. In step S42, the service suspension state information is returned. Once the service is restarted after the upgrade is completed (at this time, the returned message shows that the non-service suspension state is restored and the release password is emptied), such a polling mechanism can automatically detect that the application has been upgraded, and external users can access the application normally without having to judge again whether the upgrade has been completed.

[0049] The automatic polling mechanism is enabled only when the system is in the shutdown state to avoid putting pressure on the system.

[0050] The service deployment method and service deployment system of the present invention provide a friendly unified access, which can eliminate the technical differences of different applications on different platforms, achieve unified management of multiple platforms and multiple applications, effectively solve the problem of internal IT user authentication, and at the same time give a friendly experience to external users.

[0051] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements on some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application, and they should all be covered by the scope of the claims and the description of the present application.

Claims

1. A service deployment method for a system application, comprising: Start application shutdown, change shutdown status information, and randomly generate release passwords and hot zone information; Push a unified service shutdown interface to all clients accessing the application; Feedback the release password and the hot zone information to the internal tester responsible for the application service, the hot zone information including the hot zone location invisible to the naked eye on the service suspension interface and the hot zone triggering rules, the hot zone triggering rules being used to activate the login interface for the internal tester to enter the release password; The out-of-service interface is displayed as the same static image for external users and the internal testers. The out-of-service interface includes a hot zone that can be operated. After the internal tester operates at the hot zone position on the out-of-service interface according to the hot zone triggering rules, the login interface is activated for the internal tester to enter the release password to log in.

2. The method according to claim 1, wherein: It also includes automatically polling and querying the service stop status after the application is stopped, detecting whether the application service is completed, and returning the service stop status information.

3. The method according to claim 1, wherein: Application suspension is performed independently on one or more platforms, and only clients accessing the application through the suspended platform are affected during the suspension period.

4. The method according to claim 1, wherein: The outage status information and the release password are stored in a cache. When the external user accesses the application through the client, the outage status information cached in the cache is called to query the service status to determine whether it is in an outage state, and at the same time, check whether there is a release password in the cache. The external user can only obtain feedback on whether there is a release password or not.

5. The method according to claim 4, wherein: When the internal tester accesses the application through the client, he checks whether there is a release password in the cache, and if so, obtains the release password.

6. The method according to claim 5, wherein: The hot zone information is stored in a cache, and the internal tester obtains the hot zone information when accessing the application through the client.

7. The method according to claim 1, wherein: The hot zone triggering rule is a gesture operation performed at the hot zone position of the service outage interface within a specified time.

8. A service deployment system for implementing the service deployment method for system applications according to claim 1, comprising: Cache, used to store service suspension status information, release passwords, and hot zone information; an interface control module, configured to receive all client requests for accessing the application, retrieve the service suspension status information, release password, and hot zone information stored in the cache, and, upon confirming that the service suspension status is confirmed, return a service suspension interface to the client requesting access to the application; and, if the client is a client of an internal tester responsible for the application service, further return the release password and hot zone information to the client of the internal tester; Password configuration interaction module, used for administrators to edit service shutdown configuration; as well as A password generator is used to generate the release password and the hot zone information.

9. The service deployment system according to claim 8, wherein: The hot zone information includes the hot zone position and hot zone triggering rules on the out-of-service interface. The interface control module is further configured to provide a login interface for the internal tester to log in using the release password when the internal tester operates according to the hot zone triggering rules at the hot zone position on the out-of-service interface.

10. The service deployment system according to claim 8, wherein: It further includes a polling module built into the client, which automatically polls and queries the service suspension status after the application is stopped, detects whether the application service is completed, and returns the service suspension status information.

Images