CN115964054A

CN115964054A - Application service deployment method and device

Info

Publication number: CN115964054A
Application number: CN202211674096.0A
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: 2022-12-26
Filing date: 2022-12-26
Publication date: 2023-04-14

Abstract

The invention provides an application service deployment method and device, and particularly relates to the field of big data, wherein the method comprises the following steps: determining field type information and field configuration information of a plurality of original fields in original communication area information of original service, and forming a target communication area file based on an original service name of the original service, a preset program file type, the field type information and the field configuration information; forming a target calling configuration file based on a preset calling configuration file type, the original service name, field type information and field configuration information; and correspondingly deploying the target communication area file and the corresponding preset target service execution logic file to a corresponding target program file address based on the original service type in the original service name, and correspondingly deploying the target calling configuration file to a corresponding target configuration file address. The invention can improve the accuracy and the speed of the application service deployment, thereby improving the efficiency of the application service deployment.

Description

Application service deployment method and device

Technical Field

The invention relates to the technical field of application development, in particular to the field of big data, and particularly relates to an application service deployment method and device.

Background

After the application is actually put into operation, the architecture, the platform, or the development language on which the application-related service is based may be changed or adjusted according to related business requirements, system adjustment, operation and maintenance requirements, and the like (in this scenario, it is acquiescent that the function of the application service is not modified basically), and at this time, in order to make the application service correspondingly compatible with the change or adjustment, the application service often needs to be redeployed. In the above deployment process, the original service corresponding to the old architecture, the old platform, the old development language, or the like is adjusted or redeveloped to form the target service corresponding to the new architecture, the new platform, the new development language, or the like, and the related file of the target service is deployed to the corresponding address. When a new target service is formed, the process of readjusting or constructing the communication area file and the call configuration file for forming the target service and the process of deploying the communication area file and the call configuration file to the appropriate positions are often involved.

However, in the prior art, the process of forming a new communication area file and calling a configuration file mainly includes operations of manually writing, adjusting, and checking related developers with reference to old communication area information of an original service, and often requires the developers to manually store the new communication area file and the calling configuration file to corresponding addresses after the new communication area file and the calling configuration file are formed. The interface fields related to the communication area and the calling configuration file are numerous and the related contents are complicated, so that when developers form the communication area file and call the configuration file, mistakes in the formed communication area file and the calling configuration file cannot be avoided, the accuracy of forming the communication area file and the calling configuration file of the target service is low, the workload involved in the process of manually forming the file is huge, the time consumption is long, and the speed of forming the communication area file and the calling configuration file of the target service is low. In addition, when storing and deploying the corresponding files, because the address system and the architecture of the related application project are also complicated, depending on a manual manner, deployment errors such as that the communication area files and the calling configuration files are not stored to correct addresses may also be caused, so that the accuracy of storing the communication area files and the calling configuration files of the target service is low, and the time consumption is also long, so that the speed of storing the communication area files and the calling configuration files of the target service is slow. Obviously, the accuracy and the speed of the related links are not ideal, so that the accuracy and the speed of the overall application service deployment are lower naturally.

In summary, in the prior art, the accuracy and the speed of application service deployment are low, which is not beneficial to improving the efficiency of application service deployment.

Disclosure of Invention

An object of the present invention is to provide an application service deployment method, so as to solve the problem that the accuracy and speed of application service deployment in the prior art are low, which is not favorable for improving the efficiency of application service deployment. Another object of the present invention is to provide an application service deployment apparatus. It is a further object of this invention to provide such a computer apparatus. It is a further object of this invention to provide such a readable medium.

In order to achieve the above object, an aspect of the present invention discloses an application service deployment method, including:

determining field type information and field configuration information of a plurality of original fields in original communication area information of original service, and forming a target communication area file based on an original service name of the original service, a preset program file type, the field type information and the field configuration information;

forming a target calling configuration file based on a preset calling configuration file type, the original service name, field type information and field configuration information;

and correspondingly deploying the target communication area file and the corresponding preset target service execution logic file to a corresponding target program file address based on the original service type in the original service name, and correspondingly deploying the target calling configuration file to a corresponding target configuration file address.

Optionally, the determining field type information and field configuration information of multiple original fields in original communication area information of an original service includes:

and determining the field type information and the field configuration information corresponding to a plurality of original fields based on a preset communication area information template and the original communication area information.

Optionally, the forming a target communication area file based on the original service name of the original service, the preset program file type, the field type information, and the field configuration information includes:

forming first target file content information based on a preset communication area file template, a field data type and a field input and output type in the field type information, and a field name, a field length, a field comment and a field input-necessary type in the field configuration information;

forming a first target file name based on the original service name and the program file type;

and forming the corresponding target communication area file based on the first target file content information and the first target file name.

Optionally, the forming of the first target file content information based on the preset communication area file template, the field data type and the field input/output type in the field type information, and the field name, the field length, the field comment, and the field entry type in the field configuration information includes:

obtaining a corresponding target field data type based on the field data type and preset field data type mapping information;

forming a corresponding target input and output field class based on the target field data type, the field input and output type, the field name, the field length, the field annotation, the field requisite input item type and the communication area file template;

and forming corresponding first target file content information based on the target input and output field class and the communication area file template.

Optionally, further comprising:

after forming the corresponding target input-output field class,

judging whether the corresponding original field comprises a subfield; if yes, determining a corresponding sub-field name, a sub-field length, a sub-field comment, a sub-field required entry type and a sub-field data type based on the original field;

obtaining a corresponding target sub-field data type based on the sub-field data type and preset field data type mapping information;

correspondingly forming a static inner class in the target input-output field class based on the field input-output type, the sub-field name, the sub-field length, the sub-field comment, the sub-field required entry type, and the target sub-field data type.

Optionally, the forming a target calling configuration file based on the preset calling configuration file type, the original service name, the field type information, and the field configuration information includes:

forming second target file content information based on a preset calling configuration file template, the field data type and the field input and output type in the field type information, and the field name, the field length, the field comment, the field required input type and the original service name in the field configuration information;

forming a second target file name based on the original service name and the calling configuration file type;

and forming a corresponding target calling configuration file based on the second target file content information and the second target file name.

Optionally, further comprising:

before the target communication area file and the corresponding preset target service execution logic file are correspondingly deployed to the corresponding target program file address based on the original service type in the original service name,

and determining a corresponding service execution logic base class based on the current service grouping information, so that a worker writes and inputs the target service execution logic file based on the service execution logic base class and the target communication area file.

Optionally, further comprising:

before correspondingly deploying the target communication area file and the corresponding preset target service execution logic file to the corresponding target program file address based on the original service type in the original service name,

judging whether the current file type in the current file name of the current target file is the program file type or the calling configuration file type;

if the program file type is the program file type, correspondingly deploying the current target file to a corresponding current target program file address based on the current service type in the current file name;

if the type of the calling configuration file is the type of the calling configuration file, the current target file is correspondingly deployed to the corresponding current target configuration file address based on the current service type in the current file name.

Optionally, the correspondingly deploying, based on the original service type in the original service name, the target communication area file and the corresponding preset target service execution logic file to the corresponding target program file address, and correspondingly deploying the target call configuration file to the corresponding target configuration file address, includes:

determining a project address of a current target project, and determining a corresponding first upper layer address based on the project address and a program file type corresponding to the target communication area file;

determining a corresponding target program file address based on the first upper layer address and the original service type, and deploying the target communication area file and the target service execution logic file to the target program file address;

determining a corresponding second upper layer address based on the item address and the calling configuration file type corresponding to the target calling configuration file;

and determining a corresponding target configuration file address based on the second upper layer address and the original service type, and deploying the target calling configuration file to the target configuration file address.

determining a corresponding first intermediate address based on the first upper layer address and the original service type;

determining a corresponding target program file address based on the current service grouping information and the first intermediate address, and deploying the target communication area file and the target service execution logic file to the target program file address;

determining a corresponding second intermediate address based on the second upper layer address and the original service type;

and determining a corresponding target configuration file address based on the current service grouping information and the second intermediate address, and deploying the target calling configuration file to the target configuration file address.

Optionally, further comprising:

forming a corresponding target input and output document based on the field data type and the field input and output type in the field type information and the field name, the field length, the field annotation and the field input and output type in the field configuration information;

and forming a corresponding target interface document based on the target input and output document and preset target service configuration information.

Optionally, the forming a corresponding target input/output document based on the field data type and the field input/output type in the field type information, and the field name, the field length, the field comment, and the field input/output type in the field configuration information includes:

forming a target input document in the target input and output document based on a field input and output type, a target field data type, a field name, a field length, a field comment, a field input and output item type and a preset first document template of an original field of which the corresponding field input and output type is the input type;

and forming a target output document in the target input and output document based on the field input and output type, the target field data type, the field name, the field length, the field annotation, the field required input item type and a preset second document template of the original field with the corresponding field input and output type as the output type.

In order to achieve the above object, another aspect of the present invention discloses an application service deployment apparatus, comprising:

the system comprises a communication area file forming module, a communication area file generating module and a communication area file generating module, wherein the communication area file forming module is used for determining field type information and field configuration information of a plurality of original fields in original communication area information of original services and forming a target communication area file based on an original service name of the original services, a preset program file type, the field type information and the field configuration information;

the calling configuration file forming module is used for forming a target calling configuration file based on a preset calling configuration file type, the original service name, field type information and field configuration information;

and the deployment module is used for correspondingly deploying the target communication area file and the corresponding preset target service execution logic file to a corresponding target program file address based on the original service type in the original service name, and correspondingly deploying the target calling configuration file to a corresponding target configuration file address.

The invention also discloses a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method when executing the program.

The invention also discloses a computer-readable medium, on which a computer program is stored which, when executed by a processor, implements a method as described above.

The application service deployment method and the device provided by the invention form a target communication area file by determining the field type information and the field configuration information of a plurality of original fields in the original communication area information of the original service and based on the original service name, the preset program file type, the field type information and the field configuration information of the original service, can take the field information of various specific properties related to the communication area information of the actual original service as the basis, fully considers the characteristics of the service to which the file belongs and the corresponding file type and the classification, inquiry and call rules when the file is deployed and used in the later period, forms a new service target communication area file which is exactly consistent with the relevant field conditions of the original service, ensures that the target communication area file is more complete, can facilitate the relevant classification, inquiry and call, can realize automatic execution, greatly reduces the dependence on manpower, greatly reduces the omission and mistake making and other conditions caused by manual operation when the communication area file is formed, reduces the workload related to manpower and reduces the forming time consumption of the communication area file, thereby greatly improving the accuracy of the application area and the overall speed;

the method forms a target calling configuration file based on the preset calling configuration file type, the original service name, the field type information and the field configuration information, can form a new service target calling configuration file which is exactly consistent with the relevant field condition of the original service by taking the specific multi-property field information in the communication area information of the actual original service as the basis and fully considering the characteristic of the service and the corresponding file type and the closely related rules of classification, inquiry and calling in the deployment process and later use, and makes the target calling configuration file more complete, and can facilitate the relevant classification, inquiry and calling.

The target communication area file and the corresponding preset target service execution logic file are correspondingly deployed to the corresponding target program file address based on the original service type in the original service name, the target calling configuration file is correspondingly deployed to the corresponding target configuration file address, the rules that the hierarchical structure, the branch, the grading, the classification and the like of the address in the related application project are closely related to the corresponding service type can be fully considered, the target communication area file and the target calling configuration file which apply the new service are respectively stored to the reasonable address in the related file address which the application belongs to, the rule that the related specific execution logic file needs to directly and frequently call the communication area file representing the interface frame is further fully considered, the specific execution logic file and the communication area file are stored together for calling the specific execution logic file, the related deployment requirements are met, the steps can be automatically executed, the dependence on manpower is greatly reduced, the occurrence of deployment errors such as the fact that the communication area file and the calling configuration file are not stored to the correct address is greatly reduced, the deployment related deployment is reduced, the time consumption is greatly increased, the storage speed of the communication area file and the calling configuration file is increased, and the accuracy of the application file is improved, and the overall application speed is increased.

In conclusion, the application service deployment method and the application service deployment device provided by the invention can improve the accuracy and the speed of application service deployment, thereby improving the efficiency of application service deployment.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a flowchart illustrating an application service deployment method according to an embodiment of the present invention;

FIG. 2 is a diagram illustrating an optional step of determining field type information and field configuration information according to an embodiment of the present invention;

FIG. 3 is a schematic diagram illustrating an alternative step of forming a target communication zone file according to an embodiment of the present invention;

FIG. 4 is a schematic diagram illustrating an alternative step of forming a target call profile according to an embodiment of the present invention;

FIG. 5 is a schematic step diagram illustrating an alternative stowage deployment of an embodiment of the present invention;

FIG. 6 is a block diagram of an application service deployment apparatus according to an embodiment of the present invention;

FIG. 7 illustrates a schematic block diagram of a computer device suitable for use in implementing embodiments of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the 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 invention.

The terms "first," "second," "8230," "8230," and the like as used herein do not particularly denote any order or sequence, nor are they intended to limit the invention, but rather are used to distinguish one element from another or from another element described in the same technical term.

As used herein, the terms "comprising," "including," "having," "containing," and the like are open-ended terms that mean including but not limited to.

As used herein, "and/or" includes any and all combinations of the described items.

It should be noted that, in the technical solution of the present invention, the acquisition, storage, use, processing, etc. of the data all conform to the relevant regulations of the national laws and regulations.

It should be noted that the application service deployment method and apparatus disclosed in the present application may be used in the field of big data, and may also be used in any field other than the field of big data.

The embodiment of the invention discloses an application service deployment method, which specifically comprises the following steps as shown in figure 1:

s101: determining field type information and field configuration information of a plurality of original fields in original communication area information of original service, and forming a target communication area file based on an original service name of the original service, a preset program file type, the field type information and the field configuration information.

S102: and forming a target calling configuration file based on a preset calling configuration file type, the original service name, the field type information and the field configuration information.

S103: and correspondingly deploying the target communication area file and the corresponding preset target service execution logic file to a corresponding target program file address based on the original service type in the original service name, and correspondingly deploying the target calling configuration file to a corresponding target configuration file address.

For example, the service in the embodiment of the present invention may be, but is not limited to, a platform service or a host service, and is preferably a platform service. Among them, platform services are usually developed based on Java language, and host services are usually developed based on EGL language or COBOL language. It should be noted that the specific nature of the service can be determined by those skilled in the art according to practical situations, and the above description is only an example and should not be construed as a limitation.

For example, the communication area in the embodiment of the present invention may be understood as, but not limited to, data structure content representing various input and output fields of a service and specific information thereof, and may also be specifically understood as, but not limited to, an input and output field interface framework for being called by a related execution logic, and the like. Generally, one communication area may correspond to one service. It should be noted that the specific meaning and nature of the communication area can be determined by those skilled in the art according to practical situations, and the above description is only for example and is not limiting.

For example, the call configuration file in the embodiment of the present invention may be understood as, but not limited to, a file required when a service call (for example, a current service calls another service) is implemented, a communication structure of a communication area is embodied, and functions such as data conversion, data transmission, and related transmission configuration and interface call configuration may be implemented by using the call configuration file correspondingly. It should be noted that the specific meaning and nature of the calling configuration file can be determined by those skilled in the art according to the actual situation, and the above description is only an example and is not limiting.

The target communication area file and the corresponding preset target service execution logic file are correspondingly deployed to the corresponding target program file address based on the original service type in the original service name, the target calling configuration file is correspondingly deployed to the corresponding target configuration file address, the laws, such as the hierarchy, the branch, the grading and the classification of the address in the related application project, which are often closely related to the corresponding service type can be fully considered, the target communication area file and the target calling configuration file applying the new service are respectively stored to the reasonable addresses in the related file address belonging to the application, the laws, such as the fact that the related specific execution logic file needs to directly and frequently call the communication area file representing the interface frame, are further fully considered, the specific execution logic file and the communication area file are stored together so as to be convenient for calling, the related requirements are met, moreover, the steps can be automatically executed, the dependence on manpower is greatly reduced, the occurrence of deployment errors, such as the fact that the communication area file and the calling configuration file are not stored to the correct address is greatly reduced, the time consumption of the deployment and the overall deployment speed and the accuracy of the calling of the communication area are greatly improved.

In summary, the application service deployment method and device provided by the invention can improve the accuracy and speed of application service deployment, thereby improving the efficiency of application service deployment.

In an alternative embodiment, as shown in fig. 2, the determining field type information and field configuration information of a plurality of original fields in original cell information of an original service includes the following steps:

s201: and determining the field type information and the field configuration information corresponding to a plurality of original fields based on a preset communication area information template and the original communication area information.

For example, the original communication area information may be in a specific form, but is not limited to, an originally served communication area file or an originally served interface document in which relevant field information is recorded, and correspondingly, the communication area information template may be, but is not limited to, a corresponding communication area file template or an original served interface document template corresponding to the original served interface document. The communication area file corresponding to the original service may also record communication area contents corresponding to other services besides the original service, that is, one communication area file may correspond to a plurality of communication areas of a plurality of services, and preferably one communication area file corresponds to one communication area of one service.

For example, the step S201 may be, but is not limited to, determining a corresponding content start identifier (or content start address) and a corresponding content end identifier (or content end address) based on the communication area information template, so that the field type information and the field configuration information in the field information corresponding to the multiple original fields may be determined based on the content start identifier, the content end identifier and the original communication area information. It should be noted that, for the specific implementation manner of step S201, it can be determined by those skilled in the art according to practical situations, and the above description is only an example, and is not limited thereto.

An exemplary original communication area information may be as follows:

Record xxx_xxxxx_xxx type basicRecord

{

TextLiteralDefaultIsString＝no

}

3ROLLBACK _FLAGchar (1); //1 (1-input, 2-output, 3-input/output)/2 (must input, 2-select input, 3-fail input)

…

end

Wherein, the content start identifier can be, but is not limited to, "Record xxx _ xxxxx _ xxx type basic Record" or "Record" etc., "3ROLLBACK _FLAGchar (1); the result of this is that "// 1 (1-input, 2-output, 3-input/output)/2 (must input, 2-select input, 3-no input)" is the field information of a field "ROLLBACK _ FLAG".

It should be noted that, the specific content of the original communication area information can be determined by those skilled in the art according to practical situations, and the above description is only an example and is not limited thereto.

Through the steps, the corresponding various detailed field information in the communication area information can be accurately positioned and analyzed, so that the accuracy of integrally forming a new communication area file is improved, and the accuracy of integrally applying service deployment is improved.

In an optional embodiment, as shown in fig. 3, the forming a target communication area file based on the original service name of the original service, the preset program file type, the field type information, and the field configuration information includes the following steps:

s301: and forming first target file content information based on a preset communication area file template, the field data type and the field input and output type in the field type information, and the field name, the field length, the field annotation and the field input and output type in the field configuration information.

S302: and forming a first target file name based on the original service name and the program file type.

S303: and forming the corresponding target communication area file based on the content information of the first target file and the name of the first target file.

For example, the step S302 may be, but not limited to, forming the first target file name by using the original service name as the main name content of the first target file name and using a suffix name corresponding to the program file type as the suffix of the first target file name. For example, if the original service name is "atsxxabc" and the program file type is java file, the first target file name may be, but is not limited to, "atsxxabc. The program file type may be, but is not limited to, a java file, a python file, a c file, or the like. It should be noted that, the specific implementation manner and the type of the program file of step S302 can be determined by those skilled in the art according to practical situations, and the above description is only an example, and is not limited thereto.

For example, in step S303, but not limited to, the content information of the first target file is used as the substantial content of the target communication area file, and the name of the first target file is used as the file name of the target communication area file, so that the corresponding target communication area file can be directly formed. It should be noted that, for the specific implementation manner of step S303, it can be determined by those skilled in the art according to practical situations, and the foregoing description is only an example, and is not limited thereto.

Through the steps, the content of the field information in the target communication area file is more detailed, the granularity is more detailed, and the field information accurately accords with the characteristic property of the related field in the original service, the communication area file template corresponding to the new service is used for standard processing, so that the compatibility is stronger when the related calling and processing operation is carried out on the communication area file when the new service is subsequently used, the error probability is reduced, the related execution speed is improved, the corresponding requirement and requirement of the new service are better met, the name of the communication area file is favorable to be detailed and clear, the identification function can be realized, and the accuracy, convenience and coordination of the calling and operation of the communication area file when the subsequent new service is executed are improved. Therefore, the accuracy of forming the new service communication area file is improved through the steps, and the overall deployment efficiency is greatly improved.

In an optional implementation manner, the forming of the first target file content information based on the preset communication area file template, the field data type and the field input/output type in the field type information, and the field name, the field length, the field comment, and the field requisite entry type in the field configuration information includes:

Illustratively, in a certain field information "ROLLBACK _ FLAG char (1); a field name "ROLLBACK _ FLAG", a field length of 1 (which can be determined by 1 in char (1)), a field comment of "/1 (1-input, 2-output, 3-input-output)/2 (must input, 2-output, 3-input-output)" (located by "/////" sign), a field data type of "char" (character), a field input-output type of "input" (determined by "/1 (1-input, 2-output, 3-input-output)" in the comment, or a specific called case of a field in a logical code or the like by related development software or the like), a field must input type of "select input" (determined by "/2 (must input, 2-output, 3-input-output)" in the comment, or a specific called case of a field in a logical code or the like by related development software or the like), or a specific called case of a field in a logical code or the like. Further, the field information may further include an operation flag (representing an operation type) and a rollback flag (representing a rollback type) according to actual requirements. It should be noted that, for the positioning and determining manner of the specific field detail information such as the field data type, the field input and output type, the field name, the field length, the field comment, and the field required entry type, and the content that the field information may further include, etc., may be determined by those skilled in the art according to the actual situation, and the above description is only an example, and does not limit this.

For example, the field data type mapping information may be, but is not limited to, mapping information that characterizes a corresponding field data type in the old service and a corresponding field data type under a new service condition (e.g., a condition of architecture, code language, or architecture), for example, if the old service is a java-based service and the new service is a go-based service and a certain field data type of the old service is char, the mapping information records mapping information that maps "char" to var (the field data type char in the java language may be partially equivalent to the field data type var in the go language). It should be noted that the specific content and nature of the field data type mapping information can be determined by those skilled in the art according to practical situations, and the above description is only an example and is not limiting.

For example, the corresponding target field data type is obtained based on the field data type and preset field data type mapping information, which may be, but is not limited to, using the field data type to perform a query in the field data type mapping information to obtain the corresponding target field data type. It should be noted that, for a specific implementation manner of obtaining a corresponding target field data type based on the field data type and preset field data type mapping information, the specific implementation manner may be determined by a person skilled in the art according to an actual situation, and the foregoing description is only an example, and does not limit the present invention.

Illustratively, the corresponding target input/output field class is formed based on the target field data type, field input/output type, field name, field length, field comment, field requisite input type, and communication area file template, which may be, but is not limited to, determining a field information format corresponding to a new service based on the communication area file template, and then performing corresponding integration and adjustment to form the corresponding target input/output field class based on the field information format, class architecture format, the target field data type, field input/output type, field name, field length, field comment, and field requisite input type corresponding to the new service. It should be noted that, for the specific implementation manner of forming the corresponding target input/output field class based on the target field data type, the field input/output type, the field name, the field length, the field comment, the field entry type, and the communication area file template, a person skilled in the art can determine the specific implementation manner according to the actual situation, and the above description is only an example, and does not limit the specific implementation manner.

For example, the forming of the corresponding first target file content information based on the target i/o field class and the communication area file template may be, but is not limited to, obtaining a communication area frame, a communication area prefix, a communication area suffix, and the like corresponding to the new service based on the communication area file template, and then correspondingly integrating and adjusting the target i/o field class based on the communication area frame, the communication area prefix, the communication area suffix, and the like to form the corresponding first target file content information. It should be noted that, for a specific implementation manner for forming corresponding first target file content information based on the target input/output field class and the communication area file template, the specific implementation manner may be determined by a person skilled in the art according to actual situations, and the foregoing description is only an example, and does not limit this.

Preferably, after determining the field type information and the field configuration information of the plurality of original fields in the original communication area information of the original service, the field type information and the field configuration information corresponding to the original fields may be stored in an intermediate data structure, for example, in a Map data structure (Map set, which may be expressed in the form of, but not limited to, "Map < String, < Map < String, > Object >" or the like, and the Map data structure includes many Map nodes and may correspondingly store information of different fields), and then, when forming the first target file content information based on a preset communication area file template, the field data type and the field input and output type in the field type information, and the field name, the field length, the field comment and the field input item type in the field configuration information, the field type information and the field configuration information may be correspondingly extracted from the intermediate data structure, so that the flexibility of the overall application service deployment may be improved, the parsing and the formation of the corresponding communication area file may be achieved, and the requirements for asynchronous development and processing may be better satisfied.

Through the steps, specific field information can be adjusted, organized and architected more accurately and more finely on the basis of accurately mapping the data field type, so that more-accurate first target file content information which is more compatible and corresponding to new service requirements is formed, and by organizing the field type form, related variable definition content can be called more conveniently when a subsequent new service is actually used by virtue of the universality of the type. Therefore, the accuracy of forming the new service communication area file can be improved, and the overall deployment efficiency is greatly improved.

In an optional embodiment, further comprising:

after the corresponding target input-output field class is formed,

obtaining a corresponding target subfield data type based on the subfield data type and preset field data type mapping information;

For example, determining whether the corresponding primitive field includes a subfield is a conventional technical means in the art and is not described herein again. For example, a field is a data structure, and the data structure specifically includes a plurality of internal fields, and the internal fields are sub-fields relative to the data structure field.

For example, the determining, based on the original field, a corresponding sub-field name, a sub-field length, a sub-field comment, a sub-field required entry type, and a sub-field data type may be, but is not limited to, performing structure parsing, positioning, and the like on a sub-field in the original field, and obtaining a corresponding sub-field name, a sub-field length, a sub-field comment, a sub-field required entry type, and a sub-field data type. It should be noted that, for the specific implementation manner of determining the corresponding sub-field name, the sub-field length, the sub-field comment, the sub-field required entry type and the sub-field data type based on the original field, the foregoing description is only an example, and is not limited thereto, which can be determined by those skilled in the art according to practical situations.

Illustratively, the corresponding target sub-field data type is obtained based on the sub-field data type and the preset mapping information of the field data type, and the corresponding target sub-field data type may be obtained by, but not limited to, using the sub-field data type to perform a query in the mapping information of the field data type. It should be noted that, for a specific implementation manner of obtaining a corresponding target subfield data type based on the subfield data type and preset field data type mapping information, the specific implementation manner may be determined by a person skilled in the art according to practical situations, and the above description is only an example, and does not limit the present invention.

Illustratively, the static inner class formed in the target input/output field class based on the field input/output type, the sub-field name, the sub-field length, the sub-field comment, the sub-field requisite type, and the target sub-field data type may be formed by, but not limited to, performing field definition, adjustment, comment, arrangement and integration according to a corresponding class architecture format, and the like based on the field input/output type, the sub-field name, the sub-field length, the sub-field comment, the sub-field requisite type, and the target sub-field data type, forming an inner class, and then performing static definition on the inner class, and forming the static inner class accordingly. It should be noted that, for the specific implementation of the corresponding static internal class formed in the target input/output field class based on the field input/output type, the sub-field name, the sub-field length, the sub-field comment, the sub-field required input item type and the target sub-field data type, the above description is only an example, and is not limited thereto, and can be determined by those skilled in the art according to practical situations.

Preferably, whether the corresponding original field includes the sub-field may also be determined based on node affiliation and the like of an associated intermediate storage structure (e.g., a Map storage structure), and a corresponding sub-field name, a sub-field length, a sub-field comment, a sub-field required entry type, a sub-field data type, and the like may be parsed based on internal node data in the intermediate storage structure.

Through the steps, the fields of the lower level can be analyzed, extracted and integrated into the communication area files corresponding to the new service, so that the content of the communication area files is more comprehensive, and the accuracy of forming the communication area files is improved. In addition, the lower field is set to be in a static form, so that the lower field can be managed conveniently, the loading speed of acquiring the lower field during the subsequent new service commissioning can be increased, and the efficiency of overall application service deployment is improved.

In an optional embodiment, as shown in fig. 4, the forming a target call configuration file based on a preset call configuration file type, the original service name, field type information, and field configuration information includes the following steps:

s401: and forming second target file content information based on a preset calling configuration file template, the field data type and the field input and output type in the field type information, and the field name, the field length, the field comment, the field required input type and the original service name in the field configuration information.

S402: and forming a second target file name based on the original service name and the calling configuration file type.

S403: and forming a corresponding target calling configuration file based on the second target file content information and the second target file name.

For example, the step S401 may be, but is not limited to:

inquiring configuration mapping information corresponding to the calling configuration file template based on the field data type to obtain a target data type identifier corresponding to the field data type; inquiring configuration mapping information corresponding to the calling configuration file template based on the input and output type to obtain a target input and output type identifier corresponding to the input and output type; inquiring configuration mapping information corresponding to the calling configuration file template based on the field name to obtain a target sequence number corresponding to the field name; integrating auxiliary information such as field input item types and field comments to obtain corresponding configuration file comments; and then correspondingly adjusting and integrating the target sequence number, the target input and output type identifier, the target data type identifier, the field length, the communication area identifier (which can be directly obtained) corresponding to the service and the configuration file annotation based on the field record format corresponding to the calling configuration file template to obtain field records corresponding to a plurality of original fields, adjusting the field records according to the sequence of the target sequence number, and adding the original service name before the first field record to form the second target file content information. Wherein the configuration file annotation may further include the field properties previously annotated by the staff. One exemplary field record is as follows:

001 3 4 3RECORD1 xxxxx (the details of the annotation are omitted here)

Wherein, "001" represents a target serial number, "3" sequentially represents a target input/output type identifier, a target data type identifier and a field length, respectively, and "RECORD1" represents a communication area identifier.

It should be noted that, for the specific implementation manner of step S401, it can be determined by those skilled in the art according to practical situations, and the above description is only an example, and is not limited thereto.

Preferably, the service configuration information corresponding to the new service (the service configuration information includes but is not limited to a calling configuration version number, a public-to-private flag, a calling configuration file joining type, and a calling configuration file check code) can be obtained by analyzing or querying based on the calling configuration file template, and the service configuration information is adjusted, integrated, and processed according to a prefix format of the calling configuration file template to obtain a target service configuration prefix content; correspondingly, the prefix content of the target service configuration can be added to the initial part of the content information of the second target file, so that the subsequent target calling configuration file can be more comprehensive and accurate and is convenient to call and correspond.

For example, in step S402, the original service name may be, but is not limited to, the main name content of the second target file name, and a suffix name corresponding to the calling profile type may be used as a suffix of the second target file name, so as to form the second target file name. The type of the calling configuration file may be, but is not limited to, a dsr file, etc. It should be noted that, the specific implementation manner and the type of the program file of step S402 can be determined by those skilled in the art according to practical situations, and the above description is only an example, and is not limited thereto.

For example, in step S403, the second target file content information may be, but is not limited to, the substance content of the target call profile, and the second target file name may be a file name of the target call profile, so that the corresponding target call profile may be directly formed. It should be noted that, for the specific implementation manner of step S403, it can be determined by those skilled in the art according to practical situations, and the above description is only an example, and is not limited thereto.

Preferably, the template of the communication area file may also be a template similar to an xml format, that is, the content of the formed target communication area file may also be selected as an xml code, so that an xml operation package may be called. For example, a portion of an exemplary xml-type target address file is as follows:

<？xml version＝"1.0"encoding＝"utf-8"？>

<ETxxx>

< field id = "abcdefg" type = "Str" ioType = "3" mark = "process control variable" >)

…

Where, "ETxxx" may be, but is not limited to, an original service name or a host program name, etc., "trases" is a framework fixed tag, "? xml version = "1.0" encoding = "utf-8"? "is xml header information," dsrName "may represent dsr file name," COMMSTAT "may represent communication area representation, etc.," abcdefg "may represent field name of corresponding field, etc.," Str "may represent corresponding field data type," 3 "may represent input/output type identifier, and" process control variable "may represent corresponding configuration file annotation (here, field property of staff annotation).

It should be noted that, the specific form of the content of the target communication area file can be determined by those skilled in the art according to practical situations, and the above description is only an example and is not limited thereto.

Through the steps, the content of the field information in the target calling configuration file is more detailed, the granularity is more detailed, and the field information accurately accords with the characteristic property of the related field in the original service, the calling configuration file template corresponding to the new service is used for standard processing, so that the compatibility is stronger when the related calling and processing operations are carried out on the target calling configuration file when the new service is subsequently used, the error probability is reduced, the related execution speed is improved, the corresponding requirements and requirements of the new service are better met, the calling configuration file name is detailed and clear, the identification function can be achieved, and the accuracy, convenience and coordination of calling and operating the configuration file when the subsequent new service is executed are improved. Therefore, the accuracy of forming the new service calling configuration file is improved through the steps, and the overall deployment efficiency is greatly improved.

In an optional embodiment, further comprising:

For example, the service grouping information, which may also be referred to as but not limited to service group information, includes but is not limited to information about a specific grouping situation of services in an item, wherein corresponding groupings may be divided according to attributes or other dimensional situations of the services (e.g., service properties or service types, etc.). The services corresponding to different service groups can be stored in different packages. It should be noted that the specific nature of the service group information can be determined by those skilled in the art according to practical situations, and the above description is only an example and is not limiting.

Illustratively, one service grouping information may correspond to one service grouping, and one service grouping may perform the logical base class for a set (one or more) of services. The service execution logic base class may include, but is not limited to, a series of defined basic variables, basic methods (or frameworks of basic methods), or basic functions (or frameworks of basic functions), which are related to the execution logic. These base classes require the architecture, language, environment, and architecture, etc., to which the new service corresponds to be consistent. It should be noted that, the correspondence relation related to the base class, the specific content of the service execution logic base class, and the like can be determined by those skilled in the art according to actual situations, and the above description is only an example, and is not limited thereto.

For example, since the service grouping information itself is the corresponding service execution logic base class, the corresponding service execution logic base class can be determined directly based on the current service grouping information.

Illustratively, the worker writes the target service execution logic file based on the service execution logic base class and the target communication area file, which may be, but is not limited to, that the worker inherits or implements operations by using the corresponding service execution logic base class as a parent class, further writes, adjusts, sets, and supplements specific contents related to functions, methods, variables, and the like, and correspondingly and associatively calls, introduces, matches, and sets related variables of the execution logic based on the target communication area file, so that the worker can write a code to obtain the target service execution logic file. It should be noted that, the specific way for the worker to write the code to form the target service execution logic file can be determined by those skilled in the art according to the actual situation, and the above description is only an example, and is not limited thereto.

Through the steps, the target service execution logic file corresponding to the service property and the requirement can be formed beneficially, and time consumption for forming the target service execution logic file can be reduced to a great extent by determining the corresponding base class, so that the accuracy and the speed for determining the target service execution logic file are improved, and the accuracy and the speed for deploying the whole application service are improved.

In an optional embodiment, further comprising:

and if so, correspondingly deploying the current target file to the corresponding current target configuration file address based on the current service type in the current file name.

Illustratively, the current target file may be a randomly available or currently located application service file associated with the new service. It should be noted that the specific source of the current object file can be determined by those skilled in the art according to practical situations, and the above description is only an example and is not limiting.

Illustratively, the service types in the embodiments of the present invention may correspond to, but are not limited to, relevant application levels, for example, including, but not limited to, ACS (access control service), ATS (address translation service), EI, ET, and the like. Where EI and ET may represent different type identifications that invoke the host program property service. It should be noted that the specific nature and desirable range of the service type can be determined by those skilled in the art based on the actual circumstances, and the above description is only an example and is not intended to be limiting.

For example, the address in the embodiment of the present invention may be embodied in a form of, but not limited to, a path, a home folder, a home packet, or a home directory. It should be noted that the concrete embodiment of the address can be determined by those skilled in the art according to the actual situation, and the above description is only an example, and is not limited thereto.

For example, the determining whether the current file type in the current file name of the current target file is the program file type or the calling configuration file type may be, but is not limited to, determining the current file type based on a current suffix in the current file name of the current target file, and determining whether the current file type is the program file type or the calling configuration file type based on a preset file type corresponding relationship. In which, it can be easily determined from the file type correspondence which file types are program file types (for example, java file type, c file type, and the like are program file types), and which file types are calling configuration file types (for example, dsr file type, and the like are calling configuration file types). It should be noted that, for a specific implementation manner of determining whether the current file type in the current file name of the current target file is the program file type or the call configuration file type, a person skilled in the art may determine the specific implementation manner according to an actual situation, and the above description is only an example, and does not limit this.

Illustratively, the deploying the current target file to the corresponding current target program file address based on the current service type in the current file name includes, but is not limited to:

determining an item address of a current target item, and determining a corresponding file type hierarchy address based on the item address and the current file type;

and determining the corresponding current target program file address based on the file type hierarchy address and the current service type, and deploying the current target file to the current target program file address.

The item address of the current target item can be directly determined and obtained from the relevant background information or system information and the like. The determining of the corresponding file type hierarchical address based on the Project address and the current file type may be, but is not limited to, forming a lower address relative to the Project address based on the identifier corresponding to the current file type, and joining the Project address and the lower address to determine the corresponding file type hierarchical address, for example, if the Project address is "\8230 \ Project", and the identifier corresponding to the current file type is "java", then the determining of the file type hierarchical address may be, but is not limited to, "\8230 \ Project \ java". The determining of the corresponding current target program file address based on the file type hierarchy address and the current service type may be, but is not limited to, forming a lower address relative to the file type hierarchy address based on an identifier corresponding to the current service type, and determining the corresponding current target configuration file address by linking the file type hierarchy address and the lower address. For example, if the file type hierarchy address is "\8230 \ Project \ java" and the identifier corresponding to the current service type is "ACS", the determined current target program file address may be, but is not limited to "\8230 \ Project \ java \ ACS".

It should be noted that, for a specific implementation manner of correspondingly deploying the current object file to the corresponding current object program file address based on the current service type in the current file name, the specific implementation manner may be determined by a person skilled in the art according to an actual situation, and the foregoing description is only an example, and does not limit this.

For example, the correspondingly deploying the current target file to the corresponding current target program file address based on the current service type in the current file name may further include but is not limited to:

determining a corresponding current target upper layer address based on the file type hierarchy address and the current service type;

and determining the corresponding current target program file address based on the current service grouping information and the current target upper layer address, and deploying the current target file to the current target program file address.

The item address of the current target item can be directly determined and obtained from the relevant background information or system information and the like. The determining of the corresponding file type hierarchical address based on the Project address and the current file type may be, but is not limited to, forming a lower address relative to the Project address based on the identifier corresponding to the current file type, and joining the Project address and the lower address to determine the corresponding file type hierarchical address, for example, if the Project address is "\8230 \ Project", and the identifier corresponding to the current file type is "java", then the determining of the file type hierarchical address may be, but is not limited to, "\8230 \ Project \ java". The determining of the corresponding current target upper address based on the file type hierarchical address and the current service type may be, but is not limited to, forming a lower address relative to the file type hierarchical address based on an identifier corresponding to the current service type, and determining the corresponding current target upper address by linking the file type hierarchical address and the lower address. For example, if the file type hierarchy address is "\8230 \ Project \ java" and the identifier corresponding to the current service type is "ACS", the determined current target upper layer address may be, but is not limited to "\8230 \ Project \ java \ ACS". The determining of the corresponding current target program file address based on the current service grouping information and the current target upper layer address may be, but is not limited to, forming a lower address relative to the current target upper layer address based on an identifier corresponding to the current service grouping information, and determining the corresponding current target program file address by joining the current target upper layer address and the lower address. For example, if the current target upper layer address is "\8230 \ Project \ java \ ACS", and the identifier corresponding to the current service grouping information is "medium", the determined current target program file address may be, but is not limited to "\8230 \ Project \ java \ ACS \ medium".

It should be noted that, for a specific implementation manner that the current target file is deployed to the corresponding current target program file address based on the current service type in the current file name, the specific implementation manner may be determined by a person skilled in the art according to an actual situation, and the foregoing description is only an example, and does not limit this.

Illustratively, the deploying the current target file to the corresponding current target configuration file address based on the current service type in the current file name includes, but is not limited to:

and determining the corresponding current target configuration file address based on the file type hierarchy address and the current service type, and deploying the current target file to the current target configuration file address.

But may also include, but is not limited to:

determining a corresponding current target upper layer address based on the file type hierarchical address and the current service type;

and determining the corresponding current target configuration file address based on the current service grouping information and the current target upper layer address, and deploying the current target file to the current target configuration file address.

The specific principle is the same as the principle of correspondingly deploying the current target file to the corresponding current target program file address based on the current service type in the current file name, and details are not repeated here.

It should be noted that, for a specific implementation manner of correspondingly deploying the current target file to the corresponding current target configuration file address based on the current service type in the current file name, the specific implementation manner may be determined by a person skilled in the art according to an actual situation, and the foregoing description is only an example, and does not limit this.

Through the steps, asynchronous processing of forming the corresponding service file and storing and deploying the corresponding file can be favorably realized, relevant characteristics of the current target file (service file) can be fully analyzed to determine a detailed and proper deployment address, the accuracy of storing and deploying the file is greatly improved, relevant development requirements are better met, the flexibility is improved, and the efficiency of overall application service deployment is improved.

In an optional implementation manner, as shown in fig. 5, the correspondingly deploying the target communication area file and the corresponding preset target service execution logic file to the corresponding target program file address and the correspondingly deploying the target call configuration file to the corresponding target configuration file address based on the original service type in the original service name includes the following steps:

s501: and determining the project address of the current target project, and determining a corresponding first upper layer address based on the project address and the program file type corresponding to the target communication area file.

S502: and determining a corresponding target program file address based on the first upper layer address and the original service type, and deploying the target communication area file and the target service execution logic file to the target program file address.

S503: and determining a corresponding second upper layer address based on the item address and the calling configuration file type corresponding to the target calling configuration file.

S504: and determining a corresponding target configuration file address based on the second upper layer address and the original service type, and deploying the target calling configuration file to the target configuration file address.

For example, a specific principle of step S501 may refer to a description of the step of determining the item address of the current target item and determining the corresponding file type hierarchy address based on the item address and the current file type in the embodiment of the present invention, which is not described herein again.

For example, the specific principle of step S502 may refer to the description of the step of determining the corresponding current target program file address based on the file type hierarchy address and the current service type in the embodiment of the present invention, and details are not repeated here.

For example, the original service type may also be directly obtained from a direct query about background information or system information.

For example, the specific principle of step S503 may refer to the description of the step of determining the item address of the current target item and determining the corresponding file type hierarchy address based on the item address and the current file type in the embodiment of the present invention, and is not described herein again.

For example, a specific principle of the step S504 may refer to a description of the step of determining the corresponding file address of the current target program based on the file type hierarchy address and the current service type in the embodiment of the present invention, and details are not repeated here.

Through the steps, the characteristics of the target communication area file and the target calling configuration file, such as the related file type, the service type and the like, can be fully analyzed to respectively determine the deployment and storage addresses corresponding to the target communication area file, the target service execution logic file and the target calling configuration file, so that the deployment and storage accuracy of the service file related to the new service is comprehensively improved, and the deployment efficiency of the whole application service is greatly improved.

In an optional implementation manner, the deploying, based on the original service type in the original service name, the target communication area file and the corresponding preset target service execution logic file to the corresponding target program file address, and correspondingly deploying the target call configuration file to the corresponding target configuration file address includes:

determining a corresponding second upper layer address based on the item address and a calling configuration file type corresponding to the target calling configuration file;

For example, the specific principle of determining the item address of the current target item and determining the corresponding first upper layer address based on the item address and the program file type corresponding to the target communication area file may refer to the description of the step of determining the item address of the current target item and determining the corresponding file type hierarchical address based on the item address and the current file type in the embodiment of the present invention, and details are not repeated here.

For example, the specific principle of determining the corresponding first intermediate address based on the first upper layer address and the original service type may refer to the description of the step of determining the corresponding current target upper layer address based on the file type hierarchical address and the current service type in the embodiment of the present invention, and is not described herein again.

For example, the specific principle of determining a corresponding target program file address based on the current service grouping information and the first intermediate address, and deploying the target communication area file and the target service execution logic file to the target program file address may refer to the description of the step of determining the corresponding current target program file address based on the current service grouping information and the current target upper layer address, and deploying the current target file to the current target program file address in the embodiment of the present invention, which is not described herein again.

For example, the specific principle of determining the corresponding second upper layer address based on the item address and the calling configuration file type corresponding to the target calling configuration file may refer to the description of the step of determining the item address of the current target item and determining the corresponding file type hierarchical address based on the item address and the current file type in the embodiment of the present invention, which is not described herein again.

For example, the specific principle of determining the corresponding second intermediate address based on the second upper layer address and the original service type may refer to the description of the step of determining the corresponding current target upper layer address based on the file type hierarchical address and the current service type in the embodiment of the present invention, and is not described herein again.

For example, the specific principle of determining a corresponding target configuration file address based on the current service grouping information and the second intermediate address, and deploying the target call configuration file to the target configuration file address may refer to the description of the step of determining the corresponding current target program file address based on the current service grouping information and the current target upper layer address, and deploying the current target file to the current target program file address in the embodiment of the present invention, which is not described herein again.

Through the steps, the characteristics of the target communication area file and the target calling configuration file, such as the related file types, the service types and the like, can be fully analyzed, and service groups closely related to the service characteristics are further analyzed in a simultaneous mode to respectively determine the deployment and storage addresses corresponding to the target communication area file, the target service execution logic file and the target calling configuration file, so that the deployment and storage accuracy of the service files related to the new service is further comprehensively improved, and the overall application service deployment efficiency is further greatly improved.

In an optional embodiment, further comprising:

forming a corresponding target input and output document based on the field data type and the field input and output type in the field type information and the field name, the field length, the field comment and the field input and output type in the field configuration information;

Illustratively, the target service configuration information includes, but is not limited to, a service interface identifier (e.g., a service interface name, etc.), a service version identifier (e.g., a service version number, etc.), a service secondary identifier (e.g., a service alias, etc.), a timeout time of a service call, a retry number of the service call, load balancing policy information (e.g., a load balancing identifier, etc., where a specific policy may be, but is not limited to, a random, polling, or minimum activity priority policy, etc.), and an identifier of whether to expose an HTTP call out of the DSF through a service route, etc. The specific form of the target service configuration information may be, but is not limited to, the form of table information, and may include attributes, attribute values, description information, and the like of various pieces of sub information. It should be noted that, the specific content and form of the target service configuration information can be determined by those skilled in the art according to the actual situation, and the above description is only an example, and is not limited thereto.

For example, the corresponding target interface document is formed based on the target input and output document and preset target service configuration information, and the target interface document may be formed by, but not limited to, integrating or linking the target service configuration information and the target input and output document. For example, a target input output document may be concatenated after the target service configuration information to form the target interface document. It should be noted that, for a specific implementation manner of forming a corresponding target interface document based on the target input/output document and preset target service configuration information, the specific implementation manner may be determined by a person skilled in the art according to actual situations, and the above description is only an example, and does not limit this.

Preferably, the field data type and the field input/output type in the field type information, and the field name, the field length, the field comment, and the field entry type in the field configuration information may also be obtained by traversing a previously formed intermediate data structure (e.g., a Map data structure).

Through the steps, the interface document of the new service can be further correspondingly formed, so that the improvement of the application service deployment is facilitated, the development work such as inquiry, check, tracing and the like based on the interface document of the new service is facilitated, and the overall relevant efficiency is improved.

In an optional embodiment, the forming a corresponding target input/output document based on the field data type and the field input/output type in the field type information, and the field name, the field length, the field comment, and the field required entry type in the field configuration information includes:

forming a target input document in the target input and output document based on a field input and output type, a target field data type, a field name, a field length, a field annotation, a field required input item type and a preset first document template of an original field of which the corresponding field input and output type is an input type;

For example, the target input and output document may be, but is not limited to, an integrated or spliced whole of the target input document and the target output document.

For example, the obtaining of the corresponding target field data type based on the field data type and the preset field data type mapping information may be, but is not limited to, obtaining the corresponding target field data type by querying in the field data type mapping information using the field data type. It should be noted that, for a specific implementation manner of obtaining the corresponding target field data type based on the field data type and the preset field data type mapping information, the specific implementation manner may be determined by a person skilled in the art according to an actual situation, and the above description is only an example, and does not limit the present invention.

For example, the target input document in the target input/output document is formed based on the field input/output type, the target field data type, the field name, the field length, the field comment, the field required input type of the original field whose corresponding field input/output type is the input type, and a preset first document template, and the target input document may be formed by, but not limited to, filling the field input/output type, the target field data type, the field name, the field length, the field comment, and the field required input type of the original field whose corresponding field input/output type is the input type into a document column of corresponding attributes in the first document template (for example, filling the target field data type into a field data type document column, and the like), and filling the communication zone type and the communication zone name into a communication zone type document column and a communication zone name document column corresponding to the first document template (which may be directly obtained or obtained by query), respectively. It should be noted that, for the field input/output type, the target field data type, the field name, the field length, the field comment, the field required entry type, and the preset first document template of the original field whose corresponding field input/output type is the input type, a specific implementation manner of the target input document in the target input/output document is formed, which can be determined by those skilled in the art according to actual situations, and the above description is only an example, and does not limit this.

For example, the target output document in the target input/output document is formed based on the field input/output type, the target field data type, the field name, the field length, the field comment, the field required input type of the original field whose corresponding field input/output type is the output type, and a preset second document template, and the target output document may be formed by, but not limited to, filling the field input/output type, the target field data type, the field name, the field length, the field comment, and the field required input type of the original field whose corresponding field input/output type is the input type into a document column of corresponding attributes in the second document template (for example, filling the target field data type into a field data type document column, and the like), and filling the communication zone type and the communication zone name into a communication zone type document column and a communication zone name document column corresponding to the second document template (which can be directly obtained or obtained by query), respectively. It should be noted that, for the field input and output type, the target field data type, the field name, the field length, the field comment, the field required entry type, and the preset second document template of the original field whose corresponding field input and output type is the output type, a specific implementation manner of forming the target output document in the target input and output document may be determined by those skilled in the art according to actual situations, and the above description is only an example, and does not limit the present invention.

Through the steps, the information of the related specific fields of the target interface document of the new service can be more comprehensive, detailed and clear, so that the integrity and the usability of the target interface document are improved, further, the follow-up related work based on the target interface document is facilitated, and the overall efficiency is improved.

Preferably, the target input/output document may further include related message style content corresponding to the new service, and specifically, the message style content may also be obtained by processing and integrating information based on a field input/output type, a target field data type, a field name, a field length, a field comment, a field entry type, and the like, and then converting the information into JSON data and performing operations such as line changing and the like according to a structure.

Preferably, if the relevant fields are specifically classified into levels (considering that there may be multiple levels in the related communication architecture, and the levels correspond to the levels of the levels in the architecture), only the field of the highest level in the old service may be concerned, and based on this, the subsequent operations related to forming and deploying the file may be performed, and the fields of the non-highest levels may be ignored. For example, in field information "3ROLLBACK _FLAGchar (1); the result of this is that///1 (1-input, 2-output, 3-input/output)/2 (must input, 2-output, 3-no input) "is a field" ROLLBACK _ FLAG ", which is identified by the first" 3 "and is a field level identifier, and" 3 "indicates that this field is the highest level, and if a lower level identifier, such as the first" 4 "and" 5", appears, it indicates that the field corresponding to this field information is not the highest level field, and it is sufficient to ignore this field information.

Preferably, for a peptide like "3 timestap; the field definition of// timestamp ", etc. (similar to the variable reference)," timestap "itself can be understood as a variable, not the host base datatype, which would have a definition on itself (defined by the base host datatype). Definitions similar to timestap are usually stored in a communication area file (which is very common and used for unified specification), and the corresponding host basic data types can be added to the configuration file by a program, and related personnel can also manually add some unreported types.

Based on the same principle, the embodiment of the present invention discloses an application service deployment apparatus 600, as shown in fig. 6, the application service deployment apparatus 600 includes:

a communication area file forming module 601, configured to determine field type information and field configuration information of a plurality of original fields in original communication area information of an original service, and form a target communication area file based on an original service name of the original service, a preset program file type, the field type information, and the field configuration information;

a calling configuration file forming module 602, configured to form a target calling configuration file based on a preset calling configuration file type, the original service name, field type information, and field configuration information;

the deployment module 603 is configured to correspondingly deploy the target communication area file and the corresponding preset target service execution logic file to a corresponding target program file address based on the original service type in the original service name, and correspondingly deploy the target call configuration file to a corresponding target configuration file address.

In an optional embodiment, the communication area file forming module 601 is configured to:

forming first target file content information based on a preset communication area file template, a field data type and a field input/output type in the field type information, and a field name, a field length, a field comment and a field input/output type in the field configuration information;

and forming the corresponding target communication area file based on the content information of the first target file and the name of the first target file.

In an alternative embodiment, further comprising an internal class forming module for:

after the corresponding target input-output field class is formed,

In an optional embodiment, the calling configuration file forming module 602 is configured to:

In an optional embodiment, the method further comprises executing a logic base class determination module, configured to:

In an alternative embodiment, the system further comprises an asynchronous storage module for:

In an optional embodiment, the deployment module 603 is configured to:

In an optional embodiment, the method further comprises a new interface document forming module, configured to:

In an optional embodiment, the new interface document forming module is configured to:

Since the principle of the application service deployment apparatus 600 for solving the problem is similar to the above method, the implementation of the application service deployment apparatus 600 can refer to the implementation of the above method, and is not described herein again.

The systems, apparatuses, modules or units described in the above embodiments may be specifically implemented by a computer chip or an entity, or implemented by a product with certain functions. A typical implementation device is a computer device, which may be, for example, a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.

In a typical example, the computer device comprises in particular a memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor implements the method as described above.

Referring now to FIG. 7, shown is a schematic block diagram of a computer device 700 suitable for use in implementing embodiments of the present application.

As shown in fig. 7, the computer apparatus 700 includes a Central Processing Unit (CPU) 701, which can perform various appropriate works and processes according to a program stored in a Read Only Memory (ROM) 702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM703, various programs and data necessary for the operation of the system 700 are also stored. The CPU701, the ROM702, and the RAM703 are connected to each other via a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.

The following components are connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output section 707 including components such as a Cathode Ray Tube (CRT), a liquid crystal feedback (LCD), and a speaker; a storage section 708 including a hard disk and the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. A drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read out therefrom is mounted as necessary in the storage section 708.

In particular, according to an embodiment of the present invention, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the invention include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 709, and/or installed from the removable medium 711.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the various elements may be implemented in the same one or more pieces of software and/or hardware in the practice of the present application.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by a record "comprising one of 8230 \8230;" does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application 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 application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

All the embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement or the like made within the spirit and principle of the present application shall be included in the scope of the claims of the present application.

Claims

1. An application service deployment method, comprising:

2. The method of claim 1, wherein determining field type information and field configuration information of a plurality of original fields in original cell information of an original service comprises:

3. The method of claim 1, wherein forming a target cell file based on the original service name of the original service, the preset program file type, the field type information, and the field configuration information comprises:

4. The method of claim 3, wherein the forming of the first target file content information based on the preset communication area file template, the field data type and the field input/output type in the field type information, and the field name, the field length, the field comment and the field requisite entry type in the field configuration information comprises:

and forming corresponding first target file content 5 information based on the target input and output field class and the communication area file template.

5. The method of claim 4, further comprising:

after the corresponding target input-output field class is formed,

0, obtaining a corresponding target subfield data type based on the subfield data type and preset field data type mapping information;

6. The method according to claim 1, wherein the forming a target call configuration file based on the preset call configuration file type 5, the original service name, the field type information and the field configuration information comprises:

and 0, forming a corresponding target calling configuration file based on the second target file content information and the second target file name.

7. The method of claim 1, further comprising:

and 5, determining a corresponding service execution logic base class based on the current service grouping information, so that a worker writes and inputs the target service execution logic file based on the service execution logic base class and the target communication area file.

8. The method of claim 1, further comprising:

9. The method according to claim 1, wherein the correspondingly deploying the target communication area file and the corresponding preset target service execution logic file to a corresponding target program file address and the correspondingly deploying the target call configuration file to a corresponding target configuration file address based on the original service type in the original service name comprises:

10. The method according to claim 1, wherein the correspondingly deploying the target communication area file and the corresponding preset target service execution logic file to a corresponding target program file address and the correspondingly deploying the target call configuration file to a corresponding target configuration file address based on the original service type in the original service name comprises:

11. The method of claim 1, further comprising:

12. The method of claim 11, wherein forming a corresponding target input-output document based on the field data type and the field input-output type in the field type information, and the field name, the field length, the field comment, and the field must-enter type in the field configuration information comprises:

13. An application service deployment apparatus, comprising:

the calling configuration file forming module is used for forming a target calling configuration file based on a preset calling configuration file type, the original service name, the field type information and the field configuration information;

14. A computer arrangement comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1-12 when executing the program.

15. A computer-readable medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-12.