CN113485742A

CN113485742A - Host application version registration method and device

Info

Publication number: CN113485742A
Application number: CN202110854824.5A
Authority: CN
Inventors: 杨一鸣; 孟伟; 朱婷婷; 於维华
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2021-07-28
Filing date: 2021-07-28
Publication date: 2021-10-08
Anticipated expiration: 2041-07-28

Abstract

The embodiment of the application provides a host application version registration method and a device, which can be used in the technical field of big data, and the method comprises the following steps: extracting attribute information of an update task corresponding to a current version of a host application from a host version list issued by a target delivery system according to host application information received by the currently grabbed target delivery system, wherein the update task comprises a modified or newly added program and/or operation; respectively acquiring installation information, execution sequence information and an execution flow chart of the update task based on the attribute information of the update task; and generating a registration document corresponding to the current version of the host application according to the attribute information, the installation information, the execution sequence information and the execution flow chart of the update task of the current version. The method and the device can effectively improve the efficiency and reliability of the registration of the application version of the host computer, and can effectively improve the accuracy, reliability and integrity of the registration content.

Description

Host application version registration method and device

Technical Field

The present application relates to the field of data processing technologies, and in particular, to the field of big data technologies, and in particular, to a method and an apparatus for registering a version of a host application.

Background

The use of delivery systems has grown mature, and not only can platform applications be approved and delivered through the delivery system, but host applications are gradually shifting to the system. However, the host application is different from the platform application, the platform application is processed by each application responsible person no matter the version, maintenance, execution batch, download log and the like, and the application responsible person is clear in the process of processing; the host application is clearly divided into different parts, and except for the process of maintaining the host application, other processes are all responsible for other professional personnel, such as plate making, environment maintenance, batch execution and the like. Each group of people only pay attention to the state of the content which is in charge of the people in the online delivery system.

At present, in the overall test process aiming at the host application, the problem of test failure is easily caused because different parts of host application documents, host version lists and the like are processed or transmitted asynchronously; the host version list can only be subjected to fuzzy comparison with the application document list and the host version list when independently delivered, so that the matching accuracy is poor; in addition, most of the host application lists of the daily online delivery system can only see the modified operation or program of the current version, so that the integrity of the overall test process of the host application is poor.

Disclosure of Invention

Aiming at the problems in the prior art, the application provides a host application version registration method and device, which can effectively improve the efficiency and reliability of host application version registration and can effectively improve the accuracy, reliability and integrity of registration contents.

In order to solve the technical problem, the application provides the following technical scheme:

in a first aspect, the present application provides a host application version registration method, including:

extracting attribute information of an update task corresponding to a current version of a host application from a host version list issued by a target delivery system according to host application information received by the currently grabbed target delivery system, wherein the update task comprises a modified or newly added program and/or operation;

respectively acquiring installation information, execution sequence information and an execution flow chart of the update task based on the attribute information of the update task;

and generating a registration document corresponding to the current version of the host application according to the attribute information, the installation information, the execution sequence information and the execution flow chart of the update task of the current version.

Further, before the extracting, according to the host application information received by the currently grabbed target delivery system, the attribute information of the update task corresponding to the current version of the host application from the host version list issued by the target delivery system, the method further includes:

capturing host application information input by a user from a host version registration foreground processing interface corresponding to the target delivery system by using a preset crawler tool according to a currently received trigger instruction or a preset periodic capturing rule;

wherein the host application information comprises: the version number of the host application, the identification of the application, the patch number range, and the document generation path.

Further, the extracting, according to the host application information received by the currently grabbed target delivery system, the attribute information of the update task corresponding to the current version of the host application from the host version list issued by the target delivery system includes:

judging whether a host version list corresponding to the host application is published in the target delivery system or not, if so, extracting attribute information of each update task corresponding to the current version of the host application from the host version list according to the version number of the host application, the application identification and the patch number range in the host application information;

wherein the attribute information of the update task includes: the corresponding relation among the task identification, the host application identification, the program type, the environment, the installation partition, the function description, the affiliated project and the development department.

Further, the obtaining of the installation information, the execution sequence information, and the execution flowchart of the update task based on the attribute information of the update task includes:

respectively acquiring the installation information of each update task from the delivery system according to the identification of each update task;

acquiring the execution sequence information of each update task from a resource management system corresponding to the delivery system according to the identification of each update task;

and generating an execution flow chart corresponding to the current version of the host application based on the execution sequence information of each updating task.

Further, the obtaining the installation information of each update task from the delivery system according to the identifier of each update task includes:

according to the identification of each updating task, extracting the arrival center time of each updating task to the test center and the expected installation center time to the test center from the delivery system;

judging whether each updating task is installed in the test center at present or not based on a comparison result of the installation center time and the current time corresponding to each updating task, and generating a corresponding installation identifier, wherein the installation identifier is used for indicating whether the corresponding updating task is installed in the test center at present or not;

and respectively generating the installation information of each updating task according to the corresponding relation among the identification, the arrival center time, the installation center time and the installation identification of each updating task.

Further, the acquiring, according to the identifier of each update task, the execution sequence information of each update task from the resource management system corresponding to the delivery system includes:

capturing execution sequence parameters input by a user from the host version registration foreground processing interface;

acquiring execution sequence information of each update task in a resource management system corresponding to the delivery system according to the identifier of each update task and the execution sequence parameter, wherein the execution sequence information includes: and executing the sequence identification and the corresponding batch processing relation information.

Further, the generating a registration document corresponding to the current version of the host application according to the attribute information, the installation information, the execution sequence information, and the execution flowchart of the update task of the current version includes:

generating a first page according to the corresponding relation among the task identifier, the host application identifier, the program type, the environment, the installation partition, the function description, the affiliated project and the development department;

generating a second page according to the corresponding relation among the identification, the arrival center time, the installation center time and the installation identification of each updating task;

generating a third page according to the corresponding relation among the identification of each update task, the execution sequence identification and the batch processing relation information and the execution flow chart;

generating a registered document containing the first page, the second page and the third page;

outputting the registration document.

In a second aspect, the present application provides a host application version registration apparatus, comprising:

the system comprises a grabbing matching module, a service module and a service module, wherein the grabbing matching module is used for extracting attribute information of an update task corresponding to a current version of a host application from a host version list issued by a target delivery system according to host application information received by the currently grabbed target delivery system, and the update task comprises a modified or newly added program and/or operation;

the flow acquisition module is used for respectively acquiring installation information, execution sequence information and an execution flow chart of the update task based on the attribute information of the update task;

and the document generating module is used for generating a registration document corresponding to the current version of the host application according to the attribute information, the installation information, the execution sequence information and the execution flow chart of the update task of the current version.

In a third aspect, the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the host application version registration method when executing the program.

In a fourth aspect, the present application provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the host application version registration method described herein.

According to the technical scheme, the host application version registration method and device provided by the application comprise the following steps: extracting attribute information of an update task corresponding to a current version of a host application from a host version list issued by a target delivery system according to host application information received by the currently grabbed target delivery system, wherein the update task comprises a modified or newly added program and/or operation; respectively acquiring installation information, execution sequence information and an execution flow chart of the update task based on the attribute information of the update task; according to the attribute information, the installation information, the execution sequence information and the execution flow chart of the update task of the current version, generating a registration document corresponding to the current version of the host application, and through the host application information received by the automatically-captured target delivery system, the attribute information of the update task of the current version of the host application can be effectively and accurately and efficiently acquired according to the registration conditions given by a user; by respectively acquiring the installation information, the execution sequence identification, the corresponding batch processing relationship information and the batch execution flow chart of the task with the updated current version, a complete registration document containing the relevant attributes and the flow contents of all newly added or modified tasks can be effectively generated, so that the efficiency and the reliability of the registration of the application version of the host computer can be effectively improved, the accuracy, the reliability and the integrity of the registration contents can be effectively improved, and the user experience of checking the registration situation of the application version of the host computer can be effectively improved.

Drawings

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

Fig. 1 is a schematic diagram of the relationship between a host application version registration apparatus and a target delivery system, an asset management system and a client device, respectively, in an embodiment of the present application.

Fig. 2 is a first flowchart illustrating a host application version registration method in an embodiment of the present application.

Fig. 3 is a second flowchart of a host application version registration method in the embodiment of the present application.

Fig. 4 is a third flowchart illustrating a host application version registration method in an embodiment of the present application.

Fig. 5 is a fourth flowchart illustrating a host application version registration method in an embodiment of the present application.

Fig. 6 is a fifth flowchart illustrating a host application version registration method in an embodiment of the present application.

Fig. 7 is a sixth flowchart illustrating a host application version registration method in an embodiment of the present application.

Fig. 8 is a seventh flowchart illustrating a host application version registration method in an embodiment of the present application.

Fig. 9 is a schematic structural diagram of a host application version registration apparatus in the embodiment of the present application.

Fig. 10 is a schematic overall flow chart of the crawler acquiring online delivery document content provided by the application example of the present application.

Fig. 11 is a schematic diagram of a host version registration foreground processing interface provided in an application example of the present application.

Fig. 12 is a schematic diagram of a specific manner of triggering a host version registration foreground processing interface provided in an application example of the present application.

Fig. 13 is a schematic diagram illustrating an example of the content of the first page of the registered document provided in the application example of the present application.

FIG. 14 is a diagram illustrating an example of the contents of the second page of the registered document provided in the application example of the present application.

FIG. 15 is a diagram illustrating an example of the contents of the third page of the registration document provided in the application example of the present application.

Fig. 16 is a schematic diagram of a crawler acquiring host TWS process and generating a TWS flowchart provided by an application example of the present application.

Fig. 17 is a schematic structural diagram of an electronic device in the embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

It should be noted that the method and apparatus for registering a host application version disclosed in the present application may be used in the field of big data technology, and may also be used in any field other than the field of big data technology.

During the overall test procedure for the host application, the following problems arise:

1. poor timeliness

In the whole testing process, the problems that the testing period of the small version is four weeks, the testing period of the large version is six weeks, the testing process is long, and the testing period is short enable the content of each version to be tested efficiently, so that the problems can be found and corrected timely. However, because the host application version is now delivered through the online delivery system, which contains different parts such as documents, host version lists (including job lists and program lists), and the like, and is separately distributed, the following situation may occur.

Case 1: the job list and the program list are not sent to the test center from the development center, and the host application document firstly arrives at the test center. After the host application responsible person sees the document, if the host application responsible person does not communicate with the person responsible for the installation of the host program, the test content in the document fails to be verified, and the document is rejected;

case 2: the operation list and the program list are sent to the test center, but the responsible personnel do not operate, and the responsible personnel test the operation and maintenance host application according to the document content, so that the content in the document cannot be realized, and the document is rejected.

In any case, a lot of time is consumed for rechecking, which is a meaningless error searching process and wastes time and cost.

2. The accuracy is poor:

because the program and the job list related in the host document content are sent to the online delivery system by independent packaging, the corresponding content in the application document list and the host version list cannot be directly matched, and only the version date and the item name are used for fuzzy comparison and the corresponding content is presumed. The condition of human matching errors possibly exists, so that not only is the waste of time and labor cost caused, but also the risk caused by incorrect operation of the host is increased.

3. Poor integrity:

the host plays an indispensable role in carrying hundreds of millions of user data and accounts in the industrial and commercial banks due to the special stability and high efficiency of the host. The integrity of the host application is an important factor for ensuring the host operation and the program to be called and executed. In the daily host application list of the online delivery system, most of the jobs or programs modified by the current version can only be seen, and whether the jobs have been subjected to batch job scheduling by the modified jobs in the active directory ad (active directory) where the jobs are located or not can not be seen as a whole. Moreover, some programs are common programs, and once changed, execution of many jobs is involved, and perhaps in the job scheduling process, a job can smoothly schedule the program, and B job conflicts and fails. Therefore, it is important to grasp the integrity of the job posting.

Based on this, aiming at the problems of low registration efficiency, poor accuracy and incompleteness of the registration content and the like of the existing host application version registration mode, the embodiment of the application provides a host application version registration method, according to the host application information received by the currently grabbed target delivery system, the attribute information of the update task corresponding to the current version of the host application is extracted from the host version list issued by the target delivery system, wherein the update task comprises a modified or newly added program and/or operation; respectively acquiring installation information, execution sequence information and an execution flow chart of the update task based on the attribute information of the update task; according to the attribute information, the installation information, the execution sequence information and the execution flow chart of the update task of the current version, generating a registration document corresponding to the current version of the host application, and through the host application information received by the automatically-captured target delivery system, the attribute information of the update task of the current version of the host application can be effectively and accurately and efficiently acquired according to the registration conditions given by a user; by respectively acquiring the installation information, the execution sequence identification, the corresponding batch processing relationship information and the batch execution flow chart of the task with the updated current version, a complete registration document containing the relevant attributes and the flow contents of all newly added or modified tasks can be effectively generated, so that the efficiency and the reliability of the registration of the application version of the host computer can be effectively improved, the accuracy, the reliability and the integrity of the registration contents can be effectively improved, and the user experience of checking the registration situation of the application version of the host computer can be effectively improved.

Based on the above, the present application further provides a host application version registration apparatus for implementing the host application version registration method provided in one or more embodiments of the present application, where the host application version registration apparatus may be a server, see fig. 1, the host application version registration apparatus may be in communication connection with a target delivery system, a resource management system, and each client device in turn, by itself or through a third-party server, and the host application version registration apparatus may receive a trigger instruction for host application version registration sent by a client device, and may also receive a trigger instruction sent by a user from a host version registration foreground processing interface, and extract attribute information of an update task corresponding to a current version of a host application from a host version list issued by the target delivery system according to host application information received by the currently grabbed target delivery system, wherein the update task comprises a modified or newly added program and/or job; respectively acquiring installation information, execution sequence information and an execution flow chart of the update task based on the attribute information of the update task; and generating a registered document corresponding to the current version of the host application according to the attribute information, the installation information, the execution sequence information and the execution flow chart of the update task of the current version, wherein the registered document can be sent to client equipment of a user by the host application version registration device.

In another practical application scenario, the aforementioned host application version registration part of the host application version registration apparatus may be executed in the server as described above, or all operations may be completed in the user end device. Specifically, the selection may be performed according to the processing capability of the user end device, the limitation of the user usage scenario, and the like. This is not a limitation of the present application. If all the operations are completed in the customer premise equipment, the customer premise equipment may further include a processor for performing specific processing of the host application version registration.

It is understood that the mobile terminal may include any mobile device capable of loading an application, such as a smart phone, a tablet electronic device, a network set-top box, a portable computer, a Personal Digital Assistant (PDA), a vehicle-mounted device, a smart wearable device, and the like. Wherein, intelligence wearing equipment can include intelligent glasses, intelligent wrist-watch, intelligent bracelet etc..

The mobile terminal may have a communication module (i.e., a communication unit), and may be communicatively connected to a remote server to implement data transmission with the server. The server may include a server on the task scheduling center side, and in other implementation scenarios, the server may also include a server on an intermediate platform, for example, a server on a third-party server platform that is communicatively linked to the task scheduling center server. The server may include a single computer device, or may include a server cluster formed by a plurality of servers, or a server structure of a distributed apparatus.

The server and the mobile terminal may communicate using any suitable network protocol, including network protocols not yet developed at the filing date of this application. The network protocol may include, for example, a TCP/IP protocol, a UDP/IP protocol, an HTTP protocol, an HTTPS protocol, or the like. Of course, the network Protocol may also include, for example, an RPC Protocol (Remote Procedure Call Protocol), a REST Protocol (Representational State Transfer Protocol), and the like used above the above Protocol.

The following embodiments and application examples are specifically and individually described in detail.

In order to solve the problems of low registration efficiency, poor accuracy of registered content, incompleteness and the like of the conventional host application version registration method, the present application provides an embodiment of a host application version registration method, and referring to fig. 2, the host application version registration method executed based on a host application version registration device specifically includes the following contents:

step 100: according to host application information received by a currently grabbed target delivery system, extracting attribute information of an update task corresponding to a current version of a host application from a host version list issued by the target delivery system, wherein the update task comprises a modified or newly added program and/or operation.

It is to be understood that the target delivery system may be an online delivery document system, and the host version list may include a program list and a job list.

In one or more embodiments of the present application, a job is composed of a plurality of programs.

Step 200: and respectively acquiring installation information, execution sequence information and an execution flow chart of the update task based on the attribute information of the update task.

In step 200, the execution flow chart may refer to a TWS relationship chart or a TWS flow chart.

Step 300: and generating a registration document corresponding to the current version of the host application according to the attribute information, the installation information, the execution sequence information and the execution flow chart of the update task of the current version.

As can be seen from the above description, according to the host application version registration method provided in the embodiment of the present application, the automatically captured host application information received by the target delivery system can effectively and accurately obtain the attribute information of the task of updating the current version of the host application according to the registration condition given by the user; by respectively acquiring the installation information, the execution sequence identification, the corresponding batch processing relationship information and the batch execution flow chart of the task with the updated current version, a complete registration document containing the relevant attributes and the flow contents of all newly added or modified tasks can be effectively generated, so that the efficiency and the reliability of the registration of the application version of the host computer can be effectively improved, the accuracy, the reliability and the integrity of the registration contents can be effectively improved, and the user experience of checking the registration situation of the application version of the host computer can be effectively improved.

In order to improve the efficiency and timeliness of extracting the update information of the current version of the host application, in an embodiment of the host application version registration method provided by the present application, referring to fig. 3, step 100 of the host application version registration method specifically includes the following steps:

step 010: capturing host application information input by a user from a host version registration foreground processing interface corresponding to the target delivery system by using a preset crawler tool according to a currently received trigger instruction or a preset periodic capturing rule; wherein the host application information comprises: the version number of the host application, the identification of the application, the patch number range, and the document generation path.

It is understood that the host version registration foreground processing interface is used for displaying input boxes corresponding to the version number of the host application, the identification of the application, the patch number range (the patch start number and the patch end number), the path of the application document, the document generation path and the registration date respectively.

The user can input the version number of the host application, the identification of the application, the patch number range (patch start number and patch end number), the path where the application document is located, the document generation path, and the registration date, respectively, in the respective input boxes.

The user can also input the environment set number and the checking batch in the host version registration foreground processing interface.

As can be seen from the above description, according to the host application version registration method provided in the embodiment of the present application, by setting a host version registration foreground processing interface and actively capturing data in the host version registration foreground processing interface by using a crawler tool, efficiency and timeliness of extracting update information of a current version of a host application can be effectively improved, comparison work such as operation, program, TWS relationship, patch version number and the like of the host application does not need to be manually performed, all processes are automated by using a crawler technology, modification information is acquired by using a page foreground button, and efficiency is improved; and further, the efficiency and timeliness of the host application version registration process can be further improved.

In order to improve the reliability and accuracy of extracting the attribute information of the update task of the current version of the host application from the host version list, in an embodiment of the host application version registration method provided by the present application, referring to fig. 4, step 100 of the host application version registration method specifically includes the following contents:

step 110: judging whether a host version list corresponding to the host application is published in the target delivery system or not, if so, executing the step 120;

step 120: extracting attribute information of each update task corresponding to the current version of the host application from the host version list according to the version number of the host application, the application identifier and the patch number range in the host application information; wherein the attribute information of the update task includes: the corresponding relation among the task identification, the host application identification, the program type, the environment, the installation partition, the function description, the affiliated project and the development department.

Specifically, the host application information is automatically captured from the host version registration foreground processing interface periodically, in real time or according to a received trigger instruction based on a preset crawler tool.

The host application information specifically includes a version number of the host application, an identifier of the application, a patch number range (a patch start number and a patch end number), a path where an application document is located, a document generation path, and specific data in input boxes corresponding to registration dates, where at least the version number of the host application, the identifier of the application, the patch number range (the patch start number and the patch end number), and the document generation path are to be captured.

And judging whether the current delivery system has a host version list, if so, executing the step S4, and if not, contacting personnel of the development center. The host version list comprises an operation list and a program list.

According to the captured host application information, obtaining attribute information of the current modified or newly added program or operation from the host version list, wherein the attribute information comprises: modification type (type of job or program), modification name (name of job or program), application (identification of host application), program type, environment, installation partition (for example: large row, Asia-Pacific, European and American, etc.), function description, corresponding relationship between the affiliated project and development department;

the modification type (type of job or program) and the modification name (name of job or program) are specific examples of the aforementioned identifier of the update task.

As can be seen from the above description, the host application version registration method provided in the embodiment of the present application can effectively improve the reliability and accuracy of extracting the attribute information of the update task of the current version of the host application from the host version list, and further can further improve the reliability and accuracy of the host application version registration process.

In order to improve the integrity, reliability and efficiency of generating the registration document corresponding to the current version of the host application, in an embodiment of the host application version registration method provided in the present application, referring to fig. 5, step 200 of the host application version registration method specifically includes the following contents:

step 210: and respectively acquiring the installation information of each updating task from the delivery system according to the identification of each updating task.

Step 220: and acquiring the execution sequence information of each updating task from a resource management system corresponding to the delivery system according to the identification of each updating task.

Step 230: and generating an execution flow chart corresponding to the current version of the host application based on the execution sequence information of each updating task.

As can be seen from the above description, the host application version registration method provided in the embodiment of the present application can effectively improve the integrity, reliability, and efficiency of generating the registration document corresponding to the current version of the host application by respectively obtaining the installation information of each update task from the delivery system, and compare the content in the document with the content developed and released on the resource management system in a crawler manner; the host version list is compared with the content of the host application document, and the accuracy of the issuing operation or program can be guaranteed through secondary comparison; therefore, the efficiency and reliability of registering the application version of the host computer can be effectively improved, and the accuracy, reliability and integrity of the registered content can be effectively improved.

In order to further improve the integrity of the generation of the registered document corresponding to the current version of the host application, in an embodiment of the host application version registration method provided by the present application, referring to fig. 6, step 210 of the host application version registration method specifically includes the following steps:

step 211: and extracting the arrival center time of each update task to the test center and the expected installation center time to the test center from the delivery system according to the identification of each update task.

Step 212: and judging whether each updating task is installed in the test center at present based on a comparison result of the installation center time and the current time corresponding to each updating task, and generating a corresponding installation identifier, wherein the installation identifier is used for indicating whether the corresponding updating task is installed in the test center at present.

Step 213: and respectively generating the installation information of each updating task according to the corresponding relation among the identification, the arrival center time, the installation center time and the installation identification of each updating task.

After step 213, it may also be performed: searching whether the current modified or newly added program or operation corresponds to modification time from a system such as metadata and a software information resource management system (SEAS) corresponding to the delivery system according to the modification type (operation or type of the program) and the modification name (operation or name of the program) of the current modified or newly added program or operation, if so, indicating that the current modified or newly added program or information corresponding to the operation is registered in the SEAS in advance, and performing TWS relation statistics of the AD where the operation or the program is located.

It is understood that the arrival center time of the current modification or new program or job at the test center and the center installation time expected to be installed in the test center are acquired from the delivery system based on the modification type (job or program type) and the modification name (job or program name) of the current modification or new program or job. Acquiring current time, judging whether the center installation time of the current modified or newly added program or operation predicted to be installed in the test center is earlier than the current time, and if so, determining that the current modified or newly added program or operation is installed in the delivery system; otherwise, the personnel of the development center are contacted.

As can be seen from the above description, in the host application version registration method provided in this embodiment of the present application, based on the comparison result between the installation center time and the current time corresponding to each update task, it is determined whether each update task has been installed in the test center at present, and a corresponding installation identifier is generated, so that the integrity of the registration document corresponding to the current version of the host application is generated, and the accuracy and integrity of the registration content are further improved.

In order to further improve the integrity of the generation of the registered document corresponding to the current version of the host application, in an embodiment of the host application version registration method provided by the present application, referring to fig. 7, step 220 in the host application version registration method specifically includes the following contents:

step 221: and capturing the execution sequence parameters input by the user from the host version registration foreground processing interface.

Step 222: acquiring execution sequence information of each update task in a resource management system corresponding to the delivery system according to the identifier of each update task and the execution sequence parameter, wherein the execution sequence information includes: and executing the sequence identification and the corresponding batch processing relation information.

It can be understood that, the environment set number and the check batch input by the user are determined in the foreground processing interface of the host version registration, where the environment set number and the check batch are specific examples of the foregoing execution sequence parameters; according to the environment suite number and the inspection batch, the TWS relationship of the AD where the job or program is located is found in the SEAS (the above specific example of the resource management system), and the following situations specifically exist:

1) if the modification type is the job, automatically acquiring AD (representing all the lots by $ due to different job lots) of the job and the position of the job in the batch job scheduling TWS relation (or TWS execution sequence) in the AD according to the environment set number and the checking lot, wherein the AD is an identifier for expressing the execution sequence (execution time and/or execution lot) of the corresponding job.

2) And if the modification type is a BATCH processing program (BATCH), traversing the host database, finding out the job where the program is located, and then automatically acquiring the AD where the job is located and the position of the job in the BATCH job scheduling TWS relationship (or TWS execution sequence) in the AD according to the environment set number and the checking BATCH.

And traversing the host database again to acquire the AD and TWS relations containing all the modified jobs, and generating a corresponding TWS flow chart according to the AD and TWS relations containing all the modified jobs.

In order to improve convenience and efficiency of viewing a registered document by a user, in an embodiment of the host application version registration method provided by the present application, referring to fig. 8, a step 300 in the host application version registration method specifically includes the following contents:

step 310: generating a first page according to the corresponding relation among the task identifier, the host application identifier, the program type, the environment, the installation partition, the function description, the affiliated project and the development department;

step 320: generating a second page according to the corresponding relation among the identification, the arrival center time, the installation center time and the installation identification of each updating task;

step 330: generating a third page according to the corresponding relation among the identification of each update task, the execution sequence identification and the batch processing relation information and the execution flow chart;

step 340: generating a registered document containing the first page, the second page and the third page;

step 350: outputting the registration document.

Specifically, the registered document containing the three pages of contents can be sent to a host application responsible person or the like in a mass mail manner, so as to complete the full-flow registration of the host version of the online delivery document; and transmitting the registration document in the form of excel with the 'application-registration date' as a title to a path which is filled in an input box of the document generation path in advance by a user so as to be convenient for the user to download.

As can be seen from the above description, according to the host application version registration method provided in the embodiment of the present application, by setting the attribute information, the installation information, the execution sequence information, and the like in different pages, convenience and efficiency for a user to check a registered document can be effectively improved, and a result of comparing host contents is displayed in a graph form, so that visual fatigue caused by only list display is compensated to a certain extent, and modification information of a program related to a patch version is displayed more intuitively, so that the user is more convenient in a use process.

In terms of software, in order to solve the problems of low registration efficiency, poor accuracy of registered content, incompleteness and the like of the conventional host application version registration method, the present application provides an embodiment of a host application version registration apparatus for executing all or part of the content in the host application version registration method, and referring to fig. 9, the host application version registration apparatus specifically includes the following contents:

the system comprises a grabbing matching module 10, a service module and a service module, wherein the grabbing matching module is used for extracting attribute information of an update task corresponding to a current version of a host application from a host version list issued by a target delivery system according to host application information received by the currently grabbed target delivery system, and the update task comprises a modified or newly added program and/or operation;

a flow obtaining module 20, configured to obtain installation information, execution sequence information, and an execution flow chart of the update task based on the attribute information of the update task;

and the document generating module 30 is configured to generate a registered document corresponding to the current version of the host application according to the attribute information, the installation information, the execution sequence information, and the execution flowchart of the update task of the current version.

The embodiment of the host application version registration apparatus provided in the present application may be specifically configured to execute the processing procedure of the embodiment of the host application version registration method in the foregoing embodiment, and the functions of the embodiment are not described herein again, and refer to the detailed description of the embodiment of the method.

As can be seen from the above description, the host application version registration apparatus provided in the embodiment of the present application, through automatically capturing host application information received by the target delivery system, can effectively and accurately obtain attribute information of a task of updating a current version of a host application according to a registration condition given by a user; by respectively acquiring the installation information, the execution sequence identification, the corresponding batch processing relationship information and the batch execution flow chart of the task with the updated current version, a complete registration document containing the relevant attributes and the flow contents of all newly added or modified tasks can be effectively generated, so that the efficiency and the reliability of the registration of the application version of the host computer can be effectively improved, the accuracy, the reliability and the integrity of the registration contents can be effectively improved, and the user experience of checking the registration situation of the application version of the host computer can be effectively improved.

In order to further explain the scheme, the application example provides a host application version registration method, relates to the field of webpage data acquisition by a crawler technology, and particularly relates to a full-flow registration process of daily versions of hosts.

Document online delivery systems have been widely used for their features of easy comparison of version differences and easy approval. However, the host application is different from the platform application, and its program installation, TWS relationship, job scheduling, and application maintenance are maintained separately. The host version registration technology based on the crawler technology can integrate the newly added or modified programs into a file by traversing a host application list, a host version list and a host system list sent by an online delivery system, so that the query is facilitated. Referring to fig. 10, the method for detecting the version of the host specifically includes the following steps:

s1: the online delivery document system (delivery system) receives the host application new content:

the user registers the host application information input by the foreground processing interface through the host version.

The host version registration foreground processing interface is constructed in advance, and as shown in fig. 11, the host version registration foreground processing interface is configured to display a version number of a host application, an identifier of the application, a patch number range (a patch start number and a patch end number), a path where an application document is located, a document generation path, and input boxes corresponding to registration dates, respectively.

S2: crawling the host application information by the crawler:

and automatically capturing the host application information from the host version registration foreground processing interface periodically, in real time or according to a received trigger instruction based on a preset crawler tool.

S3: whether the host version list is released:

and judging whether the current delivery system has a host version list, if so, executing the step S4, and if not, contacting personnel of the development center.

The host version list includes a job list and a program list, and it can be understood that the job may be composed of a plurality of programs.

S4: automatically matching the host version list with the host application information:

(1) according to the captured host application information, obtaining attribute information of the current modified or newly added program or operation from the host version list, wherein the attribute information comprises: modification type (type of job or program), modification name (name of job or program), application (identification of host application), program type, environment, installation partition (for example: large row, Asia-Pacific, European and American, etc.), function description, corresponding relationship between the affiliated project and development department;

(2) Storing the attribute information of the program or the operation which is modified or added at this time into a first page of a registered document.

S5: obtaining the center of arrival time and the center installation time:

acquiring the time of the current modified or newly added program or operation reaching the center of the test and the expected center installation time of installation in the test center from the delivery system according to the modified type (operation or type of program) and the modified name (operation or name of program) of the current modified or newly added program or operation;

s6: time matching is successful:

(1) acquiring current time, judging whether the center installation time of the current modified or newly added program or operation predicted to be installed in the test center is earlier than the current time, and if so, determining that the current modified or newly added program or operation is installed in the delivery system; otherwise, the personnel of the development center are contacted.

(2) The modification type (type of job or program), modification name (name of job or program), arrival center time, center install time, and installation flag (Y for installed, N for uninstall) are stored into the second page of the registration document.

S6: and (3) registration and verification:

searching whether the current modified or newly added program or operation corresponds to the modification time from a system such as a metadata and software information resource management system (SEAS) corresponding to the delivery system according to the modification type (operation or type of the program) and the modification name (operation or name of the program) of the current modified or newly added program or operation, if so, indicating that the information corresponding to the current modified or newly added program or operation is registered in the SEAS in advance, and executing S7, otherwise, contacting personnel of the development center.

S7: TWS relation statistics of AD where the operation or program is located:

(1) determining the environment set number and the checking batch input by a user on a host version registration foreground processing interface, wherein the environment set number and the checking batch are specific examples of the execution sequence parameters;

(2) determining the corresponding operation or program according to the current modification or newly added program or the modification type of the operation (the type of the operation or the program) and the modification name (the name of the operation or the program);

(3) according to the environment suite number and the inspection batch, the TWS relationship of the AD where the job or program is located is found in the SEAS (the above specific example of the resource management system), and the following situations specifically exist:

(4) And traversing the host database again, acquiring the AD and TWS relations containing all the modified jobs, and generating a corresponding TWS flow chart according to the AD and TWS relations containing all the modified jobs.

(5) The modification type (type of job or program), modification name (name of job or program), job in which program is located, correspondence between AD and TWS relationship in which all modified jobs are located, and TWS flowchart are stored in the third page of the registration document.

S8: outputting the registration document:

sending the registered document containing the three pages of contents to a host application responsible person in a group mode in the form of an email so as to complete the full-flow registration of the online delivery document host version;

and transmitting the registration document in the form of excel with the 'application-registration date' as a title to a path which is filled in an input box of the document generation path in advance by a user so as to be convenient for the user to download.

Referring to fig. 12, the specific manner of the host version registration foreground processing interface trigger is as follows:

1) the user clicks 'one-click trigger' or separate click trigger in the host version registration foreground processing interface, then automatically acquires the whole flow of online delivered document content based on the crawler shown in fig. 10 to generate a corresponding modified list (registered document), performs identification and comparison and acquires the TWS relationship, and can also display information such as environment suite number, inspection batch and the like.

2) The host version registration foreground processing interface will automatically list out the contents with the application modification in the selected patch number as required, and obtain the whole flow of online delivery document contents according to the crawler shown in fig. 10, and under the path filled in the input box of the document generation path, generate an excel document (registration document) with the 'application-registration date' as the title, i.e. the modification list in fig. 12;

on the first page of the registration document, all the jobs, programs and production partitions of the application in the patch (the current host application version or the host version) are registered, displayed and registered; on the second page of the document, the time of the job and the program in the patch arriving at the center and the time of the host job and the program installation in the service research and development management system are registered; on the third page of the document, the TWS relationship of the AD where the job is located in the host is registered, and a flowchart of TWS in the current version host library is generated.

The automatic acquisition and registration process of the content in the host version registration document comprises the following steps:

(1) integration of host application modification points: on the first page of the registered document, the version number, application and patch number range input by the user is automatically selected by crawler technology, and the host application, job, program, function, project, development department identification and the like sent to the online delivery system by the development center are automatically captured and matched, and the content of the first page of the registered document is exemplified by referring to fig. 13.

In fig. 13, the content captured from the first page of the registered document may specifically include: modification type (job or program), modification name (job or program name), application (host application identification), program type, environment, installation partition (e.g., large row, asia-pacific, european and american), functional description, correspondence between the subject project and the development department.

(2) Comparison of job or program release time with install time: capturing a first column and a second column in a second page of the document to register modification types and names by using a crawler technology on the second page of the registered document; the third column automatically captures jobs, the arrival time of the program to the center (test center) through the host application document and the host version list in the online delivery platform; and the fourth column automatically captures the central installation time of the predicted installation to the test center of the operation and program registration through the current patch number installation time list provided by the technical department. Comparing the central installation time with the current time, and if the central installation time is earlier than the current time, indicating that the corresponding program or operation is installed in the host environment and is expressed as 'Y'; if not, the corresponding program or the corresponding operation is not installed in the host environment, the operation is represented as 'N', and whether the issued operation or the program is installed in the host environment or not is visually seen. Referring to fig. 14 as an example of the contents of the second page of the crawl registration document, if the current time is 12:00 on 4/13 of 2013, the time is between 10:12 on 13 of 4/13 of 2013 and 18:21 on 13 of 4/13 of 2013, so that the "verifiable" flag of the program earlier than 12:00 on 13 of 4/13 of 2013 is "Y", and the "verifiable" flag of the program later than 12:00 on 13 of 4/13 of 2013 is "N".

In fig. 14, the content crawled by the crawler from the second page of the registered document may specifically include: a correspondence relationship between a modification type (job or program), a modification name (name of job or program), arrival time at center (test center), installation time at center (test center), and whether or not it is verifiable (Y stands for "yes", and N stands for "no").

(3) TWS relation statistics of AD where the operation or program is located: firstly, determining the environment suite number and the checking batch at a host version registration foreground, and automatically capturing the operation or program registered by a developer on the SEAS by utilizing a crawler technology on a third page of a document;

if the modification type is the job, automatically acquiring the AD (representing all batches by $ due to different batches of the job) of the job and the position in the TWS relationship;

if the modification type is a program and is a BATCH type, firstly traversing the host database, finding out the operation of the program, and repeating the registration process;

finally, the crawler traverses the host database again, automatically registers all ADs containing the modified job in the document, and integrates them into a TWS flowchart that is related to the job in its current version. Whether the developer has completely released the modified content involved in the job can be visually checked in the TWS flowchart.

An example of the crawler crawling the contents of the third page of the registration document is shown in fig. 15.

In fig. 15, the content crawled by the crawler from the third page of the registered document may specifically include: the modification type (job or program), the modification name (job or program name), the program job, the SEAS registration job AD, and the TWS location (TWS relationship location), and the right-most content in fig. 15 is the TWS flowchart.

After the registration of the above three pages of excel contents is completed, returning to the first page of a host version registration foreground processing interface, and clicking 'all save', namely saving the excel contents; clicking 'mail automatic release', informing a host responsible person of the file after the host version registration every day in a mail mode, and checking the result in time.

In addition, the specific process of the crawler acquiring the host TWS flow and generating the TWS flow chart is shown in fig. 16, which specifically includes the following contents:

s11: modifying the operation program by the crawler at the current time;

s12: the modification type is operation: judging whether the modification type is a job, if so, executing step S16; if not, go to S13;

s13: program type is BATCH: judging whether the modification type is a BATCH type program, if so, executing S14, otherwise, executing step S15;

s14: capturing all the jobs where the programs in the host library are located, and then executing step S16;

s15: and the TWS relation does not exist, and the current flow is ended.

S16: grabbing the AD where the operation is located on the SEAS;

s17: grabbing the operation of TWS relation in AD;

s18: find jobs in the host library: and judging whether the host library has the operation or not, if so, executing S19, and if not, executing S20.

S19: and generating an overall operation flow chart.

S20: the development colleague is contacted.

The host application version registration method provided by the application example has the following advantages:

1. host version statistics efficiency. The comparison work of the operation, the program, the TWS relation, the patch version number and the like of the host application is not required to be manually carried out, all the processes are automated through a crawler technology, the modification information is obtained through a page foreground button, and the efficiency is improved.

2. The accuracy of registering the host version is improved. Comparing the content in the document with the content developed and published on the SEAS in a crawler mode; the accuracy of the release job or program can be guaranteed by comparing the version list with the content of the host application document through secondary comparison.

3. And the user experience is improved. The result of the comparison of the host content is displayed in the form of a chart, so that the visual fatigue caused by only list display is compensated to a certain extent, and the modification information of the program related to the patch version is displayed more intuitively, so that a user can use the patch version more conveniently.

In terms of hardware, in order to solve the problems of low registration efficiency, poor accuracy of registered content, incompleteness and the like of the existing host application version registration method, the present application provides an embodiment of an electronic device for implementing all or part of the content in the host application version registration method, where the electronic device specifically includes the following contents:

fig. 17 is a schematic block diagram of a system configuration of an electronic device 9600 according to an embodiment of the present application. As shown in fig. 17, the electronic device 9600 can include a central processor 9100 and a memory 9140; the memory 9140 is coupled to the central processor 9100. Notably, this fig. 17 is exemplary; other types of structures may also be used in addition to or in place of the structure to implement telecommunications or other functions.

In one embodiment, the host application version registration functionality may be integrated into the central processor. Wherein the central processor may be configured to control:

As can be seen from the above description, according to the electronic device provided in the embodiment of the present application, the automatically captured host application information received by the target delivery system can effectively and accurately obtain the attribute information of the task updated by the current version of the host application according to the registration condition given by the user; by respectively acquiring the installation information, the execution sequence identification, the corresponding batch processing relationship information and the batch execution flow chart of the task with the updated current version, a complete registration document containing the relevant attributes and the flow contents of all newly added or modified tasks can be effectively generated, so that the efficiency and the reliability of the registration of the application version of the host computer can be effectively improved, the accuracy, the reliability and the integrity of the registration contents can be effectively improved, and the user experience of checking the registration situation of the application version of the host computer can be effectively improved.

In another embodiment, the host application version registration apparatus may be configured separately from the central processor 9100, for example, the host application version registration apparatus may be configured as a chip connected to the central processor 9100, and the host application version registration function is realized by the control of the central processor.

As shown in fig. 17, the electronic device 9600 may further include: a communication module 9110, an input unit 9120, an audio processor 9130, a display 9160, and a power supply 9170. It is noted that the electronic device 9600 also does not necessarily include all of the components shown in fig. 17; in addition, the electronic device 9600 may further include components not shown in fig. 17, which can be referred to in the related art.

As shown in fig. 17, a central processor 9100, sometimes referred to as a controller or operational control, can include a microprocessor or other processor device and/or logic device, which central processor 9100 receives input and controls the operation of the various components of the electronic device 9600.

The memory 9140 can be, for example, one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, or other suitable device. The information relating to the failure may be stored, and a program for executing the information may be stored. And the central processing unit 9100 can execute the program stored in the memory 9140 to realize information storage or processing, or the like.

The input unit 9120 provides input to the central processor 9100. The input unit 9120 is, for example, a key or a touch input device. Power supply 9170 is used to provide power to electronic device 9600. The display 9160 is used for displaying display objects such as images and characters. The display may be, for example, an LCD display, but is not limited thereto.

The memory 9140 can be a solid state memory, e.g., Read Only Memory (ROM), Random Access Memory (RAM), a SIM card, or the like. There may also be a memory that holds information even when power is off, can be selectively erased, and is provided with more data, an example of which is sometimes called an EPROM or the like. The memory 9140 could also be some other type of device. Memory 9140 includes a buffer memory 9141 (sometimes referred to as a buffer). The memory 9140 may include an application/function storage portion 9142, the application/function storage portion 9142 being used for storing application programs and function programs or for executing a flow of operations of the electronic device 9600 by the central processor 9100.

The memory 9140 can also include a data store 9143, the data store 9143 being used to store data, such as contacts, digital data, pictures, sounds, and/or any other data used by an electronic device. The driver storage portion 9144 of the memory 9140 may include various drivers for the electronic device for communication functions and/or for performing other functions of the electronic device (e.g., messaging applications, contact book applications, etc.).

The communication module 9110 is a transmitter/receiver 9110 that transmits and receives signals via an antenna 9111. The communication module (transmitter/receiver) 9110 is coupled to the central processor 9100 to provide input signals and receive output signals, which may be the same as in the case of a conventional mobile communication terminal.

Based on different communication technologies, a plurality of communication modules 9110, such as a cellular network module, a bluetooth module, and/or a wireless local area network module, may be provided in the same electronic device. The communication module (transmitter/receiver) 9110 is also coupled to a speaker 9131 and a microphone 9132 via an audio processor 9130 to provide audio output via the speaker 9131 and receive audio input from the microphone 9132, thereby implementing ordinary telecommunications functions. The audio processor 9130 may include any suitable buffers, decoders, amplifiers and so forth. In addition, the audio processor 9130 is also coupled to the central processor 9100, thereby enabling recording locally through the microphone 9132 and enabling locally stored sounds to be played through the speaker 9131.

Embodiments of the present application further provide a computer-readable storage medium capable of implementing all steps in the host application version registration method in the foregoing embodiments, where the computer-readable storage medium stores thereon a computer program, and when the computer program is executed by a processor, the computer program implements all steps of the host application version registration method in which an execution subject is a server or a client, for example, when the processor executes the computer program, the processor implements the following steps:

As can be seen from the above description, the computer-readable storage medium provided in the embodiment of the present application, through automatically capturing host application information received by the target delivery system, can effectively and accurately obtain attribute information of a task of updating a current version of a host application according to a registration condition given by a user; by respectively acquiring the installation information, the execution sequence identification, the corresponding batch processing relationship information and the batch execution flow chart of the task with the updated current version, a complete registration document containing the relevant attributes and the flow contents of all newly added or modified tasks can be effectively generated, so that the efficiency and the reliability of the registration of the application version of the host computer can be effectively improved, the accuracy, the reliability and the integrity of the registration contents can be effectively improved, and the user experience of checking the registration situation of the application version of the host computer can be effectively improved.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (devices), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The principle and the implementation mode of the invention are explained by applying specific embodiments in the invention, and the description of the embodiments is only used for helping to understand the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.

Claims

1. A host application version registration method, comprising:

2. The host application version registration method according to claim 1, wherein before extracting, according to the host application information received by the currently grabbed target delivery system, attribute information of an update task corresponding to the current version of the host application from a host version list issued by the target delivery system, the method further comprises:

3. The host application version registration method according to claim 2, wherein the extracting, according to the host application information received by the currently grabbed target delivery system, attribute information of the update task corresponding to the current version of the host application from a host version list issued by the target delivery system includes:

4. The host application version registration method according to claim 3, wherein the obtaining of the installation information, the execution sequence information, and the execution flowchart of the update task based on the attribute information of the update task, respectively, comprises:

5. The host application version registration method according to claim 4, wherein the obtaining installation information of each update task from the delivery system according to the identifier of each update task comprises:

6. The host application version registration method according to claim 5, wherein the acquiring, from the resource management system corresponding to the delivery system, the execution sequence information of each update task according to the identifier of each update task includes:

7. The method of claim 6, wherein generating the registration document corresponding to the current version of the host application according to the attribute information, installation information, execution sequence information, and execution flow chart of the update task of the current version comprises:

outputting the registration document.

8. A host application version registration apparatus, comprising:

9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the host application version registration method of any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium on which a computer program is stored, the computer program, when being executed by a processor, implementing the host application version registration method of any one of claims 1 to 7.