Service deployment method and service deployment system for system application

Abstract

The invention relates to a service deployment method and a service deployment system for system application. The method comprises the steps of starting an application to stop service, randomly generating a version issuing password and hot area information, pushing a unified service stop interface to all clients accessing the application, feeding back the version issuing password and the hot area information to personnel responsible for application service, the hot area information comprising a hot area position and a hot area trigger rule on the service stop interface, and sending the hot area trigger rule to the personnel responsible for application service. Wherein the service stopping interface is a static picture for an external user, and a person responsible for the application service can operate at a hot area position on the service stopping interface according to a hot area triggering rule to obtain a login interface, log in by using a version issuing password and start the application service. According to the invention, the start-stop service management and control of the application can be simplified and standardized, the access technology standard is unified, the access cost is reduced, the user experience is improved, and meanwhile, all different platforms and different types of applications are flexibly managed.

Description

Technical Field

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

[0002] The computer systems of modern enterprises often involve multiple applications on 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 a service change is required (such as application release or upgrade), it usually has a significant impact on the use of external users of various types of platforms, so the application needs to be temporarily stopped and the service can be enabled again after the change is completed. At present, different applications or different platforms are managed separately, the standards are not unified, and the start and stop maintenance is not convenient enough, and the integration and control of multiple platforms and multiple applications cannot be achieved. Enterprise IT internal test users have a large workload when making service changes, which also affects the use of applications by external users.

[0004] Therefore, it is necessary to simplify and standardize the start and stop management and control of all internal and external network applications, unify access technology standards, reduce access costs, improve user experience, and flexibly manage all applications of different platforms and types based on the application characteristics of each system. Summary of the invention

[0005] This Summary is provided to introduce some concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify 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 realize unified and complete application service plug-in management of start-stop services. A set of business-insensitive and non-intrusive plug-ins is provided through the service deployment system. In this way, it is only necessary to connect the application to be managed to the service deployment system, and then the application will be hosted by the service deployment system. When the service needs to be changed, it can be flexibly configured according to the situation. It helps to improve the management capabilities of enterprise IT systems, improve the convenience of starting and stopping maintenance of different applications, and ensure user experience.

[0007] A service deployment method for system applications of the present invention includes: starting application shutdown, changing shutdown status information, randomly generating version release passwords and hot zone information, wherein application shutdown is independently performed for one or some platforms, and only clients accessing the application through the platform being shut down are affected during the shutdown period; a unified shutdown interface is pushed to all clients accessing the application; and the version release password and hot zone information are fed back to internal testers responsible for application services, wherein the hot zone information includes the hot zone position and hot zone triggering rules that are invisible to the naked eye on the shutdown interface; wherein the shutdown interface is a static image for external users, and the personnel responsible for application services can operate at the hot zone position on the shutdown interface according to the hot zone triggering rules, obtain a login interface, and use the version release password to log in, and start application upgrade and version release and other work. After the application is shut down, the shutdown status is automatically polled to detect whether the application service is completed, and the shutdown status information is returned.

[0008] The service downtime status information, release password and hot zone information are stored in the cache. When an external user accesses the application through the client, the service downtime status information cached in the cache is called to query the service status to determine whether it is in a service downtime state. At the same time, it checks whether there is a release password in the cache. External users can only get feedback on whether there is a release password or not. When the internal tester responsible for the application service accesses the application through the client, he checks whether there is a release password in the cache. If so, he obtains the release password and the hot zone information at the same time. The hot zone trigger rule is a gesture operation performed at the hot zone position of the service downtime interface within a specified time, which is used to activate the login interface for the person responsible for the application service to enter the release password.

[0009] The service deployment system for system applications of the present invention comprises: a cache, an interface control module, a password configuration interaction module, a password generator, and a polling module built into the client.

[0010] The cache is used to store service shutdown status information, release passwords, and hot zone information;

[0011] The interface control module is used to receive all client requests for accessing the application, retrieve the service stop status information, version release password, and hot zone information stored in the cache, and when the service stop status is confirmed, feedback the service stop interface to the client requesting to access the application, and if the client is a client of an internal tester responsible for the application service, feedback the version release password and hot zone information to the client of the internal tester responsible for the application service, and when the internal tester responsible for the application service operates according to the hot zone triggering rule at the hot zone position on the service stop interface, provide a login interface for the internal tester responsible for the application service to log in using the version release password;

[0012] Password configuration interaction module, used for administrators to edit the service shutdown configuration;

[0013] Password generator, used to generate shutdown passwords and hot zone information;

[0014] The polling module is used to automatically poll and query the service suspension status after the application is stopped, detect whether the application service is completed, and return the service suspension status information.

[0015] These and other features and advantages will become apparent by reading the following detailed description and by reference to the associated drawings.It is to be understood that the foregoing general description and the following detailed description are illustrative only and are not restrictive of the aspects of what is claimed. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0018] Figure 2 This is an example of a maintenance page.

[0019] Figure 3 Virtually shows Figure 2 Hotspots in the downtime maintenance page;

[0020] Figure 4 This is an example of the login interface used by internal testers for application maintenance.

[0021] The accompanying drawings show the system architecture, functions and operations that may be implemented according to the system and method of the embodiments of the present application. In this regard, each box in the flowchart or block diagram may represent a module, a program segment or a part of the code, which contains one or more executable instructions for implementing the specified logical functions. DETAILED DESCRIPTION

[0022] The present invention will be described in more detail below by referring to the specific embodiments shown in the accompanying drawings. By reading the detailed description of the specific embodiments below, 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 various embodiments set forth herein. The following embodiments are provided in order to be able to more thoroughly understand the present invention. Unless otherwise stated, the technical terms or scientific terms used in this application should be the common meanings 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, non-intrusive plug-in. It is deployed at the entrance of the system. 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 The 'outage maintenance page' (outage interface) shown is different in that external users can only wait for the maintenance to be completed, while the IT staff within the enterprise logs in through the 'outage maintenance page' in a pre-set manner to perform maintenance work.

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

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

[0026] 1. External users: use an application via the Internet through a platform (such as mini-programs, apps, and the Web).

[0027] External users initiate requests to use applications through the client platform.

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

[0029] In step S12, the cached message in the buffer is called to query the service status to determine whether the platform is in a suspended state, and at the same time, the cached message is called to verify the version release password to check whether the version release password exists.

[0030] Here, by querying the service shutdown status and the release password double cache message, the accuracy of the judgment result can be ensured. Figure 1 Not shown in the figure, the inventor has also conceived that, in order to prevent misjudgment in the event of a cache error, when neither the service downtime status nor the release password is found, a fallback confirmation can be performed by checking mongoDB.

[0031] If it is determined that the platform service status is not out of service and there is no version password, that is, the service status is in business operation and the application can be used normally, then in step S13, the external user's request 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 the service suspension state and there is a release password, indicating that the service state is the release state, then in step S14, the request of the external user is intercepted and a pop-up such as Figure 2 The 'Service Suspension and Maintenance Page' shown here informs you that the app is currently out of service. Figure 2 The name of the suspended application is illustrated by an “application” icon.

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

[0034] 2. Enterprise IT administrator: 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 the application.

[0035] By default, no platform is checked, indicating that all platforms are in service.

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

[0037] In step S22, edit the service start and stop configuration on the page and check the platforms that need to be stopped. The selection can be single or multiple. For example, if this application upgrade is only for applications under IOS, check IOS alone. If it is for mini-programs and Android platforms, check mini-programs and Android.

[0038] Each time a service is started or stopped, 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 the password can be repeated with no more than three digits. Each time a service is started or stopped, a hot zone is randomly demarcated and a hot zone trigger rule (collectively referred to as hot zone information) is formulated. Figure 3 As shown in the interface, the hotspot of the example is to the right of the application icon (note that Figure 3 In order to show the location of the hot zone, the area is colored and framed, which is actually not visible to the human eye). The trigger rule can be set to, for example, 3 clicks within 2 seconds (this is just an example, and other click times or gestures can be imagined). The outage configuration is saved in mongoDB (an exemplary outage configuration table is shown in the following table, involving table and data field information). The application enters the outage state on the corresponding platform.

[0039] Stop service configuration table - mongo (osc.stopServiceConfig)

[0040]

[0041] In step S24, the information such as the outage status and the version release password in the cache is updated and 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 (application release and upgrade, etc.).

[0043] After the enterprise IT administrator initiates the service suspension, the enterprise IT internal tester requests the release password and hot zone information (including hot zone location and hot zone triggering rules) at step S31.

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

[0045] Although the interface shown to internal testers is as follows Figure 2 The appearance of the 'Service Suspension Maintenance Page' is exactly the same as the static image seen by external users. However, because the internal testers also know the hot zone location and hot zone triggering rules, the internal testers seem to see Figure 3 That way (note that Figure 3 The coloring and framing of the hot zone positions are virtual and are only for explaining the present invention).

[0046] At this time, taking the previous example as an example, the internal tester can quickly (within 2 seconds) click the screen 3 times in the hot area on the right side of the application icon on the 'Service Suspension Maintenance Page' to pop up the following Figure 4 After the internal tester enters the release password obtained in the above step S32 into the login page, he can perform operations such as application upgrade.

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

[0048] When the service suspension state is started, the polling module in the client automatically polls every few seconds (configurable interval) in step S41 to check the service suspension state and detect whether the application upgrade has been completed. The service suspension state information is returned in step S42. Once the upgrade is completed and the service is restarted (at this time, the returned message shows that the service is restored to the non-service suspension state, and the release password is left blank), the polling mechanism can automatically find that the application has been upgraded, and external users can access the application normally without having to determine whether the upgrade has been completed again.

[0049] The automatic polling mechanism is only enabled when the service is down to avoid putting pressure on the system.

[0050] The service deployment method and service deployment system of the present invention provide friendly unified access, can eliminate the technical differences between different platforms and different applications, realize unified management of multiple platforms and multiple applications, effectively solve the problem of internal IT user authentication, and provide external users with a friendly experience.

[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 aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some or all of the technical features may be replaced by equivalents. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application, and they should all be included in the scope of the claims and specification 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, wherein the hot zone information includes the hot zone position and hot zone triggering rules that are invisible to the naked eye on the service shutdown interface; The out-of-service interface is a static picture for external users, but there is a hot zone that can be operated for the internal testers. After the internal testers operate at the hot zone position on the out-of-service interface according to the hot zone trigger rules, a login interface is provided to the internal testers for them to log in using the release password.

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

3. The method according to claim 1, characterized in that: 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, characterized in that: 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. At the same time, it is checked 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, characterized in that: When the internal tester accesses the application through the client, he checks whether there is a release password in the buffer, and if so, obtains the release password.

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

7. The method according to claim 1, characterized in that: The hot zone trigger rule is a gesture operation performed at the hot zone position of the service suspension interface within a specified time, which is used to activate a login interface for the internal tester to input the release password.

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

9. The service deployment system according to claim 8, characterized in that: The hot zone information includes the hot zone position and the 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, characterized in that: It further includes a polling module built into the client, which automatically polls and inquires about the service suspension status after the application is suspended, detects whether the application service is completed, and returns the service suspension status information.

Images