CN113741879B

CN113741879B - Visual development platform, method, medium and equipment

Info

Publication number: CN113741879B
Application number: CN202111005799.XA
Authority: CN
Inventors: 邓承志; 郭原; 江继欢
Original assignee: Beijing Yusys Technologies Group Co ltd
Current assignee: Beijing Yusys Technologies Group Co ltd
Priority date: 2021-08-30
Filing date: 2021-08-30
Publication date: 2022-03-22
Anticipated expiration: 2041-08-30
Also published as: CN113741879A

Abstract

The invention provides a visual development platform, a method, a medium and equipment, wherein the platform comprises: the engineering view designer is used for generating an engineering view; the engineering view comprises: the system comprises at least one access module and at least one take-off module, wherein each access module and each take-off module are provided with resource definition files; the module editor is used for responding to triggering operation on the resource definition file and generating the resource definition file into a first visual interface; and performing visual configuration on at least one of resource configuration, protocol configuration and component configuration corresponding to the access module or the access module according to the editing operation of a user on the first visual interface. The invention provides a unified engineering view, and a development mode facing to the assembly can quickly set up a service system facing to the requirement, reduce the technical requirement of implementers, shorten the project period and ensure the project quality, thereby reducing the project implementation cost.

Description

Visual development platform, method, medium and equipment

Technical Field

The invention relates to the technical field of information, is mainly used in the fields of finance and general finance, and particularly relates to a visual development platform, a method, a medium and equipment.

Background

Various specific service systems in the current market are not interacted with peripheral systems to process communication and messages uniformly through a universal platform, or the universal platform is not accumulated enough, and the service systems need to write non-service codes to adapt to communication and message to be in butt joint with the peripheral systems to different degrees.

In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art: in the prior art, a demand-oriented service system cannot be built quickly.

Disclosure of Invention

In view of this, embodiments of the present invention provide a visualization development platform, a method, a medium, and a device, so as to quickly build a demand-oriented business system.

In a first aspect, an embodiment of the present invention provides a visualization development platform, which includes:

the engineering view designer is used for generating an engineering view; the engineering view comprises: the system comprises at least one access module and at least one take-off module, wherein each access module and each take-off module are provided with resource definition files;

the module editor is used for responding to triggering operation on the resource definition file and generating the resource definition file into a first visual interface; and performing visual configuration on at least one of resource configuration, protocol configuration and component configuration corresponding to the access module or the access module according to the editing operation of a user on the first visual interface.

In some possible embodiments, the engineering view designer may be specifically configured to:

generating a first engineering view, the first engineering view comprising: an application project name at a first level; application development and communication configuration at a second level; the communication access and communication exit which is positioned at the third level and corresponds to the communication configuration; an access module corresponding to the communication access and an exit module corresponding to the communication exit are positioned at a fourth level; the first resource definition file is positioned at the fifth level and corresponds to the access module, and the second resource definition file is positioned at the fifth level and corresponds to the access module; alternatively, the first and second electrodes may be,

generating a second engineering view, the second engineering view comprising: an application project name at a first level; application development and communication configuration at a second level; the communication access and communication exit which is positioned at the third level and corresponds to the communication configuration; an access module corresponding to the communication access and an exit module corresponding to the communication exit are positioned at a fourth level; the first resource definition file and the first message definition file which are positioned at the fifth level and correspond to the access module, and the second resource definition file and the second message definition file which are positioned at the fifth level and correspond to the access module; alternatively, the first and second electrodes may be,

generating a third engineering view, the third engineering view comprising: an application project name at a first level; application development and communication configuration at a second level; the communication access and communication exit which is positioned at the third level and corresponds to the communication configuration; an access module corresponding to the communication access and an exit module corresponding to the communication exit are positioned at a fourth level; the first resource definition file and the first transaction group which are positioned at the fifth level and correspond to the access module, and the second resource definition file and the second transaction group which are positioned at the fifth level and correspond to the access module; a first message definition file corresponding to the first transaction packet at a sixth level, and a second message definition file corresponding to the second transaction packet at a sixth level.

In some possible implementations, the module editor may include:

a first interface generating unit, configured to generate the resource definition file into a first visual interface in response to a trigger operation on the resource definition file, and display a configuration list interface in a first predetermined area of the first visual interface, where a thread pool of a next-level directory of a resource configuration is displayed;

the second interface generation unit is used for responding to the selection operation of the thread pool and displaying the configuration interface of the thread pool in a second preset area of the first visual interface; the configuration interface of the thread pool comprises: the name of the thread pool and the attribute information of the thread pool; the attribute information of the thread pool includes: the configuration item corresponding to the maximum thread number and the configuration item corresponding to the minimum thread number.

In some possible embodiments, the first interface generating unit is further configured to display a distributor of a next-level catalog of resource configurations in the configuration list interface;

the second interface generation unit is further used for responding to the selected operation of the distributor, and displaying the configuration interface of the distributor in a second preset area of the first visual interface; the configuration interface of the distributor comprises: name of the distributor and attribute information of the distributor; wherein the attribute information of the distributor includes any plurality of: the method comprises the following steps that configuration items corresponding to log hexadecimal systems, detection configuration items of load balancing equipment, detection request message configuration items of the load balancing equipment and detection response message configuration items of the load balancing equipment are obtained; the load balancing equipment is load balancing equipment.

In some possible embodiments, the first interface generating unit is further configured to display a workflow of a next-level directory of resource configurations in the configuration list interface;

the second interface generation unit is further used for responding to the selected operation of the workflow and displaying a configuration interface of the workflow in a second preset area of the first visual interface; the configuration interface of the workflow comprises: name of the workflow and attribute information of the workflow;

wherein the attribute information of the workflow comprises: a request process configuration item, a response process configuration item and an error response process configuration item; the request flow configuration item is used for receiving one or more names of request flows input by a user; the response flow configuration item is used for receiving one or more names of response flows input by a user; the error response flow configuration item is used for receiving one or more names of error response flows input by a user.

In some possible embodiments, the first interface generating unit is further configured to display at least one protocol of the protocol configuration in the configuration list interface;

the second interface generating unit is further configured to, in response to a selection operation on any one of the protocols, display a configuration interface corresponding to the selected protocol in a second predetermined area of the first visual interface, where the configuration interface corresponding to the selected protocol includes: name of the selected protocol and attribute information of the selected protocol.

In some possible embodiments, the first interface generation unit is further configured to display a next-level catalog dataFormat of a basic component configuration in the configuration list interface;

the second interface generating unit is further configured to respond to the operation of selecting the dataFormat, and display a message configuration interface in a second predetermined area of the first visual interface; the message configuration interface comprises: configuring a sub-interface by the name of the message and configuring a sub-interface by the attribute information of the message; wherein, the attribute information configuration sub-interface of the message comprises any more than one of the following: exception handling strategy configuration items, error code configuration items, action type configuration items, use message configuration items, message type configuration items, message coding configuration items, Map variable configuration items, message configuration items, unpacking variable configuration items and packing variable configuration items.

In some possible embodiments, the first interface generating unit is further configured to display a next-level directory of communication component configurations in the configuration list interface, where the next-level directory of communication component configurations includes: fixCommRecv and fixcomsend;

the second interface generation unit is further used for responding to the selected operation of the fixcomRecv and displaying a socket fixed-length configuration interface in a second preset area of the first visual interface; the socket fixed-length configuration interface comprises a socket fixed-length name and a socket fixed-length configuration information sub-interface; the socket fixed-length configuration information sub-interface comprises any more than one of the following components: exception handling strategy configuration item, error code configuration item, error information configuration item, action configuration item, sending variable name configuration item, receiving variable name configuration item, overtime configuration item, packet header type configuration item, packet header length configuration item and self-contained length configuration item; the configuration value corresponding to the exception handling strategy configuration item is selected from the following configuration values: exception throwing and ignoring; the configuration value corresponding to the packet header type configuration item is selected from a plurality of configuration values as follows: character type, byte type, short integer, integer.

In some possible embodiments, the first interface generating unit is further configured to display a next-level directory modelinvoke for invoking component configuration in the configuration list interface;

the second interface generating unit is further used for responding to the selected operation of the modeleinvoke, and displaying a module calling configuration interface in a second preset area of the first visual interface; the module calling configuration interface comprises: configuring a sub-interface by the name of module calling and attribute information of module calling; the attribute information configuration sub-interface called by the module comprises any more than one of the following components: exception handling strategy configuration item, error code configuration item, error information configuration item, module name configuration item and transaction code configuration item; wherein, the configuration value corresponding to the exception handling policy configuration item includes one of the following: throw exception, ignore.

In some possible embodiments, each of the access module and the egress module is provided with a message definition file; the visualization development platform may further include:

the visual message editor is used for responding to the triggering operation of the message definition file and generating the message definition file into a second visual interface; and visually configuring the message corresponding to the access module or the access module according to the editing operation of the user on the second visual interface.

In some possible embodiments, the visual message editor may include:

the third interface generation unit is used for responding to the triggering operation of the message definition file, generating the message definition file into a second visual interface, and displaying the structural hierarchy of the message in a first preset area of the second visual interface;

the fourth interface generating unit is used for responding to the selection operation of the message displayed in the first preset area of the second visual interface and displaying the configuration interface of the message in the second preset area of the second visual interface; the configuration interface of the message comprises any more of the following configuration items: message type configuration items, message coding configuration items, packet splicing parameter configuration items, unpacking method configuration items and packet splicing method configuration items.

In some possible embodiments, the configuration value of the packet type configuration item is selected from any one of the following: 1-JSON, 2-simple XML, 3-SOAP, 4-key-value pair separator, 5-KVXML, 6-fixed length, 7-separator, 8-ISO8583, 9-XML, 10-type fixed length, 11-domain fixed length, 12-Map; the configuration value of the message coding configuration item is selected from any one of the following items: UTF-8, GBK, GBK2312, GBK 18030; the grouping parameter configuration items comprise: automatic bag splicing and sub-configuring items, automatic bag splicing and sub-configuring items and filtering empty string configuring items; the configuration value of the automatic sub-packet-splicing configuration item is true or false; the configuration value of the filter empty string sub-configuration item is false or true; the unpacking parameter configuration item comprises: the method comprises the following steps of automatically unpacking a sub-configuration item, reserving an automatically unpacking data sub-configuration item and an automatically unpacking variable sub-configuration item; the configuration value of the automatic unpacking child configuration item is true or false; and the configuration value of the reserved automatic unpacking data sub-configuration item is false or true.

In some possible embodiments, the module editor is specifically configured to visually configure a protocol, and specifically includes: displaying a configuration list interface on a left side interface of the module editor, displaying a next-level directory of protocol configuration in the configuration list interface, wherein the next-level directory is tcp short connection, and displaying a configuration interface of the tcp short connection in a right side interface of the module editor in response to a selection operation of the tcp short connection, wherein the configuration interface of the tcp short connection comprises: the name of the tcp short connection and attribute information of the tcp short connection; wherein the attribute information of the tcp short connection comprises: a host configuration item, a port configuration item and a timeout configuration item; the host configuration item is used for receiving the IP address of the host input or configured by a user; the port configuration item is used for receiving a port number input or configured by a user; the timeout configuration item is used for receiving communication timeout parameters input or configured by a user.

In a second aspect, an embodiment of the present invention provides a visualization development method, which includes the following steps:

generating an engineering view, the engineering view comprising: the system comprises at least one access module and at least one take-off module, wherein each access module and each take-off module are provided with resource definition files;

generating the resource definition file into a first visual interface in response to a triggering operation on the resource definition file; and performing visual configuration on at least one of resource configuration, protocol configuration and component configuration corresponding to the access module or the access module according to the editing operation of a user on the first visual interface.

In a third aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the computer program implements:

In a fourth aspect, an embodiment of the present invention provides a computer device, including:

one or more processors;

storage means for storing one or more programs;

the one or more programs, when executed by the one or more processors, cause the one or more processors to implement:

The technical scheme has the following beneficial effects: the embodiment of the invention provides a visual development platform (tool), which provides a uniform engineering view, adopts a component-oriented development mode, can quickly build a demand-oriented business system, reduces the technical requirements of implementers, shortens the project cycle, and ensures the project quality, thereby achieving the purposes of reducing the project implementation cost, quickly meeting the business requirements of enterprises and improving the enterprise competitiveness.

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. 1A is a functional block diagram of a visualization development platform according to an embodiment of the present invention;

FIG. 1B is a functional block diagram of another visualization development platform of an embodiment of the present invention;

FIG. 2A is a structural design drawing of an engineering view according to an embodiment of the present invention;

FIG. 2B is a structural design drawing of another engineering view according to an embodiment of the present invention;

FIG. 2C is a structural design drawing of yet another engineering view according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of a module editor and a thread pool visualization configuration interface thereof according to an embodiment of the present invention;

FIG. 4 is a schematic view of a module editor and its distributor visualization configuration interface according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a module editor and its workflow visualization configuration interface according to an embodiment of the invention;

FIG. 6 is a schematic diagram of a module editor and its protocol visualization configuration interface according to an embodiment of the invention;

FIG. 7 is a schematic diagram of a module editor and its basic component visualization configuration interface according to an embodiment of the invention;

FIG. 8 is a schematic diagram of a receiving configuration visualization configuration interface of a module editor and its communication components according to an embodiment of the invention;

FIG. 9 is a schematic diagram of a module editor and a configuration interface for transmitting a configuration visualization of a communication component thereof according to an embodiment of the invention;

FIG. 10 is a schematic view of a visual configuration interface of a module editor and its calling components according to an embodiment of the invention;

fig. 11 is an interface diagram of a visual message editor according to an embodiment of the present invention;

FIG. 12 is a schematic diagram of another interface of a visual message editor, according to an embodiment of the invention;

FIG. 13 is a flow chart of a visualization development method of an embodiment of the present invention;

FIG. 14 is a functional block diagram of a computer-readable storage medium of an embodiment of the present invention;

FIG. 15 is a functional block diagram of a computer device of an embodiment 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 embodiment of the invention provides a visual development platform, which provides a uniform engineering view, is a component-oriented development mode, can quickly build a demand-oriented business system, reduces the technical requirements of implementers, shortens the project cycle, and ensures the project quality, thereby achieving the purposes of reducing the project implementation cost, quickly meeting the business requirements of enterprises and improving the enterprise competitiveness.

Professional matters are given to professional systems, service system developers pay more attention to service development, requirements for non-service system development technology stacks are reduced, communication and message processing related to external interaction can be developed in a configuration mode of the visual development platform of the embodiment of the invention, the number of used doorways is reduced, the method can be popularized to other service systems with similar requirements, reusability is high, and overall development efficiency is improved finally.

Example one

Fig. 1A is a functional block diagram of a visualization development platform according to an embodiment of the present invention. As shown in fig. 1A, the platform 100 includes:

an engineering view designer 110 for generating an engineering view; the engineering view comprises: the system comprises at least one access module and at least one take-off module, wherein each access module and each take-off module are provided with resource definition files. Specifically, the project view has an application project name, and the next level of the application project name includes an application code (application development) part and a communication configuration part. The next level of communication configuration comprises communication access and communication access, and corresponds to different access scenes. The communication access comprises one or more access modules, the communication output comprises one or more output modules, each access module and each output module are provided with resource definition files, and the next level of each access module and each output module can establish transaction groups and/or message definition files according to actual needs to carry out reasonable classification management. Some of the files in the engineering view may be visually edited. Fig. 2A is a structural design diagram of an engineering view according to an embodiment of the present invention. As shown in fig. 2A, the access module and the drop module may be distinguished from each other, and may include N (> < 0) access modules and drop modules. Resource definition files are arranged below the access module and the access module, and the resource definition files are modules. In some embodiments, as shown in fig. 2C, the access module or the drop module supports multi-layer grouping according to transaction types, and the message names under all the groupings cannot be repeated, and the grouping names cannot be chinese. Specifically, the engineering view designer 110 may be specifically configured to generate an engineering view, for example, similar to the engineering view illustrated in fig. 2A, fig. 2B, and fig. 2C, in response to receiving an operation instruction of a user to create a new engineering. In one example, a user performs a new project operation in the integrated development environment IDE to generate a preliminary project view with a preset structural hierarchy similar to that shown, for example, in FIG. 2A, including: and the application project name, the application development and the application development input by the user develop the next-level communication configuration, and the communication configuration is the next-level communication access and the communication access. When a user mouse selects communication access, a right button can establish an access module 1, and a default or preset resource definition file module.mrd is generated at the next stage of the access module 1; when a user mouse selects a right button for communication connection, a new connection module 1 can be established, and a default or preset resource definition file module. This forms the final engineering view.

And triggering the resource definition file module in the final engineering view to realize the visual editing of the resource definition file module. In a further embodiment, as shown in fig. 2B, after the access module 1 or the egress module 1 is established, the access module 1 or the egress module 2 is selected, and a right button is clicked to create a new message or a new message group, so as to generate a message definition file, where the suffix is mfd.

Referring again to FIG. 2A, in some embodiments, the engineering view designer 110 may be specifically configured to: generating a first engineering view, the first engineering view comprising: an application project name at a first level; application development and communication configuration at a second level; the communication access and communication exit which is positioned at the third level and corresponds to the communication configuration; an access module corresponding to the communication access and an exit module corresponding to the communication exit are positioned at a fourth level; the first resource definition file is positioned at the fifth level and corresponds to the access module, and the second resource definition file is positioned at the fifth level and corresponds to the access module; alternatively, the first and second electrodes may be,

referring again to FIG. 2B, in some embodiments, the engineering view designer 110 may be specifically configured to: generating a second engineering view, the second engineering view comprising: an application project name at a first level; application development and communication configuration at a second level; the communication access and communication exit which is positioned at the third level and corresponds to the communication configuration; an access module corresponding to the communication access and an exit module corresponding to the communication exit are positioned at a fourth level; the first resource definition file and the first message definition file which are positioned at the fifth level and correspond to the access module, and the second resource definition file and the second message definition file which are positioned at the fifth level and correspond to the access module; alternatively, the first and second electrodes may be,

referring again to FIG. 2C, in some embodiments, the engineering view designer 110 may be specifically configured to: generating a third engineering view, the third engineering view comprising: an application project name at a first level; application development and communication configuration at a second level; the communication access and communication exit which is positioned at the third level and corresponds to the communication configuration; an access module corresponding to the communication access and an exit module corresponding to the communication exit are positioned at a fourth level; the first resource definition file and the first transaction group which are positioned at the fifth level and correspond to the access module, and the second resource definition file and the second transaction group which are positioned at the fifth level and correspond to the access module; a first message definition file corresponding to the first transaction packet at a sixth level, and a second message definition file corresponding to the second transaction packet at a sixth level.

A module editor 120, configured to generate a resource definition file as a first visual interface in response to a trigger operation on the resource definition file; and performing visual configuration on at least one of resource configuration, protocol configuration and component configuration corresponding to the access module or the output module according to the editing operation of the user on the first visual interface. The triggering operation may be that the user clicks or double clicks on the resource definition file through a left mouse button, or clicks a right mouse button, or the user directly touches the resource definition file on the touch screen with a finger, or the triggering operation is a voice instruction sent by the user. By triggering the opening of a resource definition file suffixed with mrd in the engineering view, a visual editing interface similar to that shown, for example, in FIG. 5, is generated and displayed to the user. This translates or converts the resource definition file in the engineering view into a module configuration interface.

The following is a detailed description:

designing a module editor:

the embodiment of the invention can carry out visual configuration development on resources, protocols and components (basic components, communication components and calling components). As shown in fig. 3-5, the resource configuration may include, but is not limited to, thread pool, dispatcher, workflow, and so on.

Referring to FIG. 3, in one example, module editor 120 includes:

the first interface generation unit is used for responding to a trigger operation on the resource definition file, generating the resource definition file into a first visual interface, displaying a configuration list interface in a first preset area (for example, a left interface area) of the first visual interface, and displaying a thread pool of a next-level directory of the resource configuration in the configuration list interface. In an alternative embodiment, the thread pool, dispatcher, and workflow of the next level directory of resource configurations are displayed in a configuration list interface.

The second interface generation unit is used for responding to the selection operation of the thread pool, and displaying the configuration interface of the thread pool in a second preset area (such as a right side interface) of the first visual interface; the configuration interface of the thread pool comprises: the name of the thread pool and the attribute information of the thread pool; the attribute information of the thread pool includes: the configuration item corresponding to the maximum thread number and the configuration item corresponding to the minimum thread number. The configuration item corresponding to the maximum thread number is used for receiving the maximum thread number input by a user, and the configuration item corresponding to the minimum thread number is used for receiving the minimum thread number input by the user. The first predetermined area and the second predetermined area are not limited to the left interface or the right interface, that is, the layout manner is not limited to a left-right layout structure, but may also be an up-down layout structure, or an inside-outside layout structure, or a surrounding type, surrounding type layout structure, or other interface layout structures that divide the interface of the visual message editor into the first predetermined area and the second predetermined area that do not overlap.

Referring to fig. 4, in an example, the first interface generating unit is further configured to display a distributor of a next-level directory of resource configurations in the configuration list interface. Or, the first interface generating unit is further configured to generate the resource definition file into the first visual interface in response to a triggering operation on the resource definition file, display a configuration list interface in a first predetermined area (for example, a left interface area) of the first visual interface, and display a thread pool, a distributor, and a workflow of a next-level directory of the resource configuration in the configuration list interface.

The second interface generation unit is also used for responding to the selected operation of the distributor, and displaying the configuration interface of the distributor in a second preset area (for example, a right side interface) of the first visual interface; the configuration interface of the distributor comprises: name of the distributor and attribute information of the distributor. Wherein the attribute information of the distributor includes any plurality of: configuration items (whether the log printing format is 16-system format or not) corresponding to the log hexadecimal, F5 detection configuration items (whether F5 detection is performed or not), F5 detection request message configuration items (F5 detection probe messages) and F5 detection response message configuration items (F5 detection response messages). Wherein, F5 is a load balancing device, and F5 detects some parameters interacting with F5 device heartbeat mainly through visual development platform configuration.

Referring to fig. 5, in an example, the first interface generating unit is further configured to display the workflow of the next level directory of the resource configuration or the thread pool, the dispatcher and the workflow of the next level directory in the configuration list interface (e.g., the left side interface).

The second interface generation unit is further used for responding to the selected operation of the workflow, and displaying the configuration interface of the workflow in a second preset area (such as a right interface) of the first visual interface; the configuration interface of the workflow comprises: the name of the workflow and attribute information of the workflow.

Wherein the attribute information of the workflow comprises: a request flow configuration item, a response flow configuration item, and an error response flow configuration item. The request flow configuration item is used for receiving one or more names of request flows input by a user; the response flow configuration item is used for receiving one or more names of response flows input by a user; the error response flow configuration item is used for receiving one or more names of error response flows input by a user.

Further, a plurality of editing keys are further arranged on the right side of the request process configuration item, the response process configuration item and the error response process configuration item, and the editing keys comprise any plurality of the following keys: an add button, a delete button, an up button, a down button. A first adding button corresponding to the request process configuration item is used for adding one or more request processes to the request process configuration item; the first deleting button corresponding to the request process configuration item is used for deleting one or more existing request processes in the request process configuration item; the upward movement button corresponding to the request process configuration item is used for controlling the selected request process in the request process configuration item to move upwards so as to change the arrangement sequence of the request process configuration item; and the downward movement control corresponding to the request flow configuration items is used for controlling the selected request flows in the request flow configuration items to move downwards so as to change the arrangement sequence of the request flows.

Referring to the protocol configuration interface shown in fig. 6, the first interface generating unit is further configured to display at least one protocol corresponding to the protocol configuration in the configuration list interface;

the second interface generating unit is further configured to display, in response to a selection operation on any one of the protocols, a configuration interface corresponding to the selected protocol in a second predetermined area of the first visual interface, where the configuration interface corresponding to the selected protocol includes: name of the selected protocol and attribute information of the selected protocol.

In one example, in an interface of the module editor, a left side interface is a configuration list interface, a next-level directory shortServerInAdapter (tcp short connection) of the Protocol configuration is displayed in the configuration list interface, and in response to a selection operation on the shortServerInAdapter in the directory, a configuration interface of a tcp (Transmission Control Protocol) short connection is displayed in the right side interface of the module editor, where the configuration interface of the tcp short connection includes: name of tcp short connection and attribute information of tcp short connection. Wherein, the attribute information of tcp short connection includes: a host configuration item, a port configuration item, and a timeout configuration item. The host configuration item is used for receiving the IP address of the host input or configured by a user; the port configuration item is used for receiving a port number input or configured by a user; the timeout configuration item is used to receive user input or configured timeout values (communication timeout parameters) in milliseconds. In other examples, not limited to tcp short connections, other protocol types may be configured for visualization. Such as but not limited to: tcp long connections, SSL (Secure Sockets Layer), short connections, timing scheduling, IBMMQ, RabbitMQ, etc. Wherein MQ refers to a Message Queue (Message Queue). The RabbitMQ is an open source implementation of AMQP (Advanced Message Queue protocol) developed by Erlang language. IBM MQ (IBM Message Queue) is a commercial Message intermediate product of IBM, and is suitable for use in distributed computing environments or heterogeneous systems. With each new protocol type, a visualization interface can be added accordingly. And drawing and generating a corresponding visual configuration interface according to the attribute parameter configuration information by acquiring the attribute parameter configuration information corresponding to any one protocol type.

Referring to the visual configuration interface of the basic component shown in fig. 7, the first interface generating unit is further configured to display a next-level directory dataFormat of the basic component configuration in a configuration list interface (e.g., a left side interface), where the name is merely an exemplary default name and may be modified into other names, which represent message format processing, that is, related operations for messages, such as unpacking, grouping, and the like;

and the second interface generating unit is further configured to, in response to the selection operation of the dataFormat, display a message configuration interface in a second predetermined area (for example, a right-side interface) of the first visualization interface corresponding to the module editor. The message configuration interface comprises: configuring a sub-interface by the name of the message and configuring a sub-interface by the attribute information of the message; the attribute information configuration sub-interface of the message comprises any more than one of the following components: exception handling strategy configuration items, error code configuration items, action type configuration items, use message configuration items, message type configuration items, message coding configuration items, Map variable configuration items, message configuration items, unpacking variable configuration items and packing variable configuration items.

The Map variable configuration item, the message configuration item and the unpacking variable configuration item are necessary configuration items or mandatory configuration items, and the rest configuration items are optional configuration items. The configuration value corresponding to the exception handling policy configuration item can be selected from the following configuration values: throw exception, ignore. The configuration value corresponding to the action type configuration item can be selected from a plurality of configuration values as follows: unpacking and splicing. The configuration value corresponding to the message type configuration item can be selected from a plurality of configuration values as follows: 1-JSON, 2-simple XML, 3-SOAP, 4-key-value pair separator, 5-KVXML, 6-fixed length, 7-separator, 8-ISO8583, 9-XML, 10-type fixed length, 11-domain fixed length, 12-Map. The configuration value corresponding to the message coding configuration item can be selected from the following configuration values: UTF-8, GBK, GBK2312, GBK 18030. The Map variable configuration item corresponds to a default configuration value tradeDataMap (transaction data Map structure variable). The default configuration values corresponding to the unpacking variable configuration items are as follows: recv.

Referring to fig. 8 to 9, the communication assembly includes: receiving configuration and sending configuration. Referring to fig. 8, in a visual configuration interface of a communication component, in an example, in an interface of a module editor, a left side interface is a configuration list interface, and a first interface generating unit is further configured to display a next-level directory of a configuration of the communication component in the configuration list interface, where the next-level directory of the configuration of the communication component includes: a fixed-length general reception process and a fixed-length general transmission process, respectively;

and the second interface generation unit is also used for responding to the selection operation of the fixCommRecv, and displaying the socket fixed-length configuration interface in a second preset area (such as a right interface) of the first visual interface. The socket fixed-length configuration interface comprises a socket fixed-length name (fixcomRecv) and a socket fixed-length configuration information sub-interface. The socket fixed-length configuration information sub-interface comprises any more than one of the following components: exception handling policy configuration item, error code configuration item, error information configuration item, action configuration item, sending variable name configuration item, receiving variable name configuration item, timeout configuration item, packet header type configuration item, packet header length configuration item, and inclusion length configuration item. The configuration value corresponding to the exception handling strategy configuration item is selected from the following configuration values: throw exception, ignore. The configuration value corresponding to the packet header type configuration item is selected from a plurality of configuration values as follows: character type, byte type, short integer, integer. Sending a variable name configuration item and a packet header length configuration item as indispensable items, and selecting and filling other items; the configuration item containing the length indicates that the length of the packet header contains the length of the message and the length of the packet header.

Referring to fig. 9, in a visual configuration interface of a communication component, in an example, in an interface of a module editor, a left side interface is a configuration list interface, and the first interface generating unit is further configured to display a next level directory of the communication component configuration in the configuration list interface, where the next level directory of the communication component configuration includes: fixCommRecv and fixcomsend; and the second resource display and editing module is also used for responding to the selected operation of the fixCommSend and displaying the socket fixed-length configuration interface in a second preset area (such as a right side interface) of the first visual interface. The socket fixed-length configuration interface comprises a socket fixed-length name (fixcomSend) and a socket fixed-length configuration information sub-interface. The socket fixed-length configuration information sub-interface comprises any more than one of the following components: exception handling policy configuration, error code configuration, error information configuration, action configuration (e.g., unpack), send variable name configuration, receive variable name configuration, timeout configuration, packet header type configuration, packet header length configuration, containment length configuration itself. The configuration value corresponding to the exception handling strategy configuration item is selected from the following configuration values: throw exception, ignore. The configuration value corresponding to the packet header type configuration item is selected from a plurality of configuration values as follows: character type, byte type, short integer, integer. Wherein, the sending variable name configuration item and the packet header length configuration item are indispensable items, and the others are optional items.

Referring to the configuration interface of the calling component shown in fig. 10, in an example, in a first predetermined area of the interface of the module editor, for example, the left side interface is a configuration list interface, the first interface generating unit is further configured to display a next-level directory modeleinvoke of the calling component configuration, which represents the call-out module, in the configuration list interface;

and the second interface generating unit is also used for presenting the module calling configuration interface in a second preset area (such as a right side interface) of the first visual interface in response to the selection operation of the moduleInvoke. The module calling configuration interface comprises: and configuring the sub-interface by the name of the module call and the attribute information of the module call. The attribute information configuration sub-interface called by the module comprises any number of the following: exception handling policy configuration item, error code configuration item, error information configuration item, module name configuration item, transaction code configuration item. The configuration value corresponding to the exception handling policy configuration item includes one of the following: exception is thrown (exception information is thrown in the processing flow), ignored (no processing is done for exception information, and flow processing is kept uninterrupted). The module name configuration items are indispensable items, and the other configuration items are optional configuration items. The component executes the error code and error information configuration of the custom configuration, can select not to configure, and is used as the universal error code and the universal error information returned to the platform when not configured.

Fig. 1B is a functional block diagram of another visualization development platform provided in the embodiment of the present invention. In a further embodiment, each access module and each output module in the engineering view are provided with a message definition file; as shown in fig. 1B, the visualization development platform may further include: the visual message editor 130 is used for responding to the triggering operation of the message definition file and generating the message definition file into a second visual interface; and carrying out visual configuration on the message corresponding to the access module or the output module according to the editing operation of the user on the second visual interface. As shown in fig. 2B, the file with the suffix mfd in the engineering view is a message definition file, which corresponds to a visual message editor, and when a user triggers (e.g., clicks a left mouse button, double clicks a left mouse button, right mouse button, finger touch, voice command, etc.) the message definition file, a second visual interface is generated in response to receiving a trigger command of the user to the message definition file, as shown in fig. 3. The messages used for different types of transactions are not the same.

In the example shown in fig. 11, the visual message editor 130 may include: the third interface generation unit is used for responding to the triggering operation of the message definition file, generating the message definition file into a second visual interface, and displaying the structural hierarchy of the message in a first preset area of the second visual interface; the fourth interface generating unit is used for responding to the selection operation of the message displayed in the first preset area of the second visual interface and displaying the configuration interface of the message in the second preset area of the second visual interface; the configuration interface of the message comprises any more of the following configuration items: message type configuration items, message coding configuration items, packet splicing parameter configuration items, unpacking method configuration items and packet splicing method configuration items.

Specifically, the directory of the message, the header of the message, and the body of the message is displayed in a first predetermined area, for example, a left interface area, of the interface after the visual message editor is started; and responding to the selected operation of the message in the directory, and displaying a configuration interface of the message in a second preset area of the interface, such as a right-side interface, of the started visual message editor. The configuration interface of the message includes any more than one of the following: message type configuration items, message coding configuration items, packet splicing parameter configuration items, unpacking method configuration items and packet splicing method configuration items.

The configuration value of the message type configuration item may be selected from any one of the following: 1-JSON (JavaScript Object Notation, JS Object Notation), 2-Simple XML, 3-SOAP (Simple Object Access Protocol), 4-key-value pair separator, 5-KVXML, 6-fixed length, 7-separator, 8-ISO8583, 9-XML, 10-type fixed length, 11-domain fixed length, 12-Map; the configuration value of the message coding configuration item may be selected from any one of the following: UTF-8, GBK, GBK2312, GBK 18030. The grouping parameter configuration items can include: automatic bag splicing configuration items, automatic bag splicing variable quantum configuration items and filtering empty string configuration items. The configuration value of the automatic sub-spelling configuration item is true or false. The configuration value of the filter empty string sub-configuration item is false or true. Wherein, the unpacking parameter configuration item can comprise: the method comprises the following steps of automatically unpacking a sub-configuration item, reserving an automatically unpacking data sub-configuration item and automatically unpacking a variable sub-configuration item. The configuration value of the automatic unpacking child configuration item is true or false; and keeping the configuration value of the automatic unpacking data sub-configuration item as false or true.

The first predetermined area and the second predetermined area are not limited to the left interface or the right interface, that is, the layout manner is not limited to a left-right layout structure, but may also be an up-down layout structure, or an inside-outside layout structure, or a surrounding type, surrounding type layout structure, or other interface layout structures that divide the interface of the visual message editor into the first predetermined area and the second predetermined area that do not overlap.

As shown in fig. 11 and 12, in the visual message editor:

each type of message can define a header (message attribute) of the message and a default formatting method of the whole message.

As shown in fig. 12, the body of the message supports grouping (Group), field (Item), loop (While), branch (Switch), and reference message (dataformat ref).

The field (Item) can define the attribute and the sub-message (namely the reference message in the figure), the field (Item) is divided according to the sub-message, and the field (Item) supports the processing of the formatting method.

And supporting quick message configuration:

the embodiment of the invention supports the import and export of the message configuration excel. For example, an import and export button is arranged on a corresponding configuration interface, and the excel file is imported or exported by clicking the corresponding button.

The embodiment of the invention supports the import, generation and configuration of the original message, such as: and generating message configuration through self-description messages such as json message, xml message and the like.

Secondary development and design:

the user-defined component, the adapter code and the configuration file are independent from the visual Development platform, wherein the configuration file is placed in an IDE (Integrated Development Environment) specified directory, the IDE is combined when displayed, and the application-defined configuration is not updated when the platform version configuration is updated;

the custom configuration files are distinguished by naming specifications, for example, the platform resource definition file is ModuleDefinition _ in.xbd, the custom resource definition file is ModuleDefinition _ in _ custom name xbd, and the message is: dataformat definition _ custom name xdd, other similar rules;

the name and class name of the bean in the user-defined configuration file cannot be renamed with the platform, and if the name and class name are renamed, the name and class name are ignored and are not displayed.

The component public attribute self-defining component does not need configuration, such as error codes, error information, exception handling modes and the like, and the parentname is designated as the baseComponent.

Taking fig. 7 as an example, when the user wishes to further perform the custom secondary development design, a new configuration item of the attribute may be added to the right interface of the interface shown in fig. 9, and the configuration value of the attribute may be added/extended. That is, the configuration interface shown in fig. 9 is not fixed, but can be personalized and customized according to the secondary development requirement of the user, and the configuration interface is changed. In one example, a module editor of the visualization development platform obtains a message in a target suffix format and displays a new configuration interface corresponding to the message in the target suffix format according to the message in the target suffix format. The message in the target suffix format includes the user-defined secondary development design file, and the target suffix format may be xdd. And the secondary development design is beneficial to realizing customized visual development or extensible visual design.

The beneficial technical effects of the scheme of the embodiment of the invention comprise:

the visual development configuration development enables each business system not to repeatedly do the development work of communication and messages any more, thereby greatly improving the development efficiency of the business systems and reducing the cost.

The embodiment of the invention can realize IDE visual operation, communication and message processing zero code configuration development.

Example two

FIG. 13 is a flow chart of a visualization development method of an embodiment of the present invention. As shown in fig. 13, the method includes the steps of:

s210: generating an engineering view, the engineering view comprising: the system comprises at least one access module and at least one take-off module, wherein each access module and each take-off module are provided with resource definition files;

s220: generating the resource definition file into a first visual interface in response to a triggering operation on the resource definition file; and performing visual configuration on at least one of resource configuration, protocol configuration and component configuration corresponding to the access module or the access module according to the editing operation of a user on the first visual interface.

In some embodiments, step S220 may specifically include the following steps:

in response to a triggering operation on the resource definition file, generating the resource definition file into a first visual interface, displaying a configuration list interface in a first preset area of the first visual interface, and displaying a thread pool of a next-level directory of resource configuration or a thread pool, a distributor and a workflow of the next-level directory in the configuration list interface;

in response to the selection operation of the thread pool, displaying a configuration interface of the thread pool in a second preset area of the first visual interface; the configuration interface of the thread pool comprises: the name of the thread pool and the attribute information of the thread pool; the attribute information of the thread pool includes: the configuration item corresponding to the maximum thread number and the configuration item corresponding to the minimum thread number.

In some embodiments, step S220 may specifically include the following steps:

displaying a distributor of a next-level directory of resource configuration in the configuration list interface, or displaying a thread pool, a distributor and a workflow of the next-level directory;

in response to a selected operation on the dispenser, displaying a configuration interface of the dispenser in a second predetermined area of the first visual interface; the configuration interface of the distributor comprises: name of the distributor and attribute information of the distributor; wherein the attribute information of the distributor includes any plurality of: configuration items corresponding to the hexadecimal log, F5 detection configuration items, F5 detection request message configuration items and F5 detection response message configuration items.

In some embodiments, step S220 may specifically include the following steps:

displaying a configuration list interface in a first preset area of the first visual interface, wherein the configuration list interface displays workflow of a next-level directory of resource configuration, or a thread pool, a distributor and the workflow of the next-level directory;

in response to the selected operation on the workflow, displaying a configuration interface of the workflow in a second preset area of the first visual interface; the configuration interface of the workflow comprises: name of the workflow and attribute information of the workflow;

In some embodiments, step S220 may specifically include the following steps:

displaying at least one protocol corresponding to the protocol configuration in the configuration list interface; the system comprises a protocol configuration unit, a first-level directory and a second-level directory, wherein the protocol configuration unit is used for configuring a first-level directory of a protocol, and the first-level directory is at least one protocol;

responding to the selection operation of any one protocol, and displaying a configuration interface corresponding to the selected protocol in a second preset area of the first visual interface, wherein the configuration interface corresponding to the selected protocol comprises: name of the selected protocol and attribute information of the selected protocol.

In one example, the steps may specifically include:

displaying a configuration list interface in a first predetermined area (for example, a left side interface) of an interface of the module editor, and displaying a next-level directory of protocol configuration in the configuration list interface, wherein the next-level directory is a tcp short connection;

in response to the selected operation of the tcp short connection, displaying a configuration interface of the tcp short connection in a second predetermined area (for example, a right side interface) of the interface of the module editor, wherein the configuration interface of the tcp short connection comprises: the name of the tcp short connection and attribute information of the tcp short connection; wherein the attribute information of the tcp short connection comprises: a host configuration item, a port configuration item and a timeout configuration item; the host configuration item is used for receiving the IP address of the host input or configured by a user; the port configuration item is used for receiving a port number input or configured by a user; the timeout configuration item is used for receiving communication timeout parameters input or configured by a user.

In some embodiments, step S220 may specifically include the following steps:

displaying a next-level directory dataFormat of basic component configuration in the configuration list interface;

responding to the selected operation of the dataFormat, and displaying a message configuration interface in a second preset area of the first visual interface;

the message configuration interface comprises: configuring a sub-interface by the name of the message and configuring a sub-interface by the attribute information of the message; wherein, the attribute information configuration sub-interface of the message comprises any more than one of the following: exception handling strategy configuration items, error code configuration items, action type configuration items, use message configuration items, message type configuration items, message coding configuration items, Map variable configuration items, message configuration items, unpacking variable configuration items and packing variable configuration items.

In some embodiments, step S220 may specifically include the following steps:

displaying a next-level directory of communication component configuration in the configuration list interface, wherein the next-level directory of communication component configuration comprises: fixCommRecv and fixcomsend;

in response to the selected operation of the fixCommRecv, displaying a socket fixed-length configuration interface in a second preset area of the first visual interface;

the socket fixed-length configuration interface comprises a socket fixed-length name and a socket fixed-length configuration information sub-interface; the socket fixed-length configuration information sub-interface comprises any more than one of the following components: exception handling strategy configuration item, error code configuration item, error information configuration item, action configuration item, sending variable name configuration item, receiving variable name configuration item, overtime configuration item, packet header type configuration item, packet header length configuration item and self-contained length configuration item; the configuration value corresponding to the exception handling strategy configuration item is selected from the following configuration values: exception throwing and ignoring; the configuration value corresponding to the packet header type configuration item is selected from a plurality of configuration values as follows: character type, byte type, short integer, integer.

In some embodiments, step S220 may specifically include the following steps:

displaying a next-level directory modelenvoke for calling component configuration in the configuration list interface;

responding to the selected operation of the modelelnvoke, and calling a configuration interface by a display module in a second preset area of the first visual interface;

the module calling configuration interface comprises: configuring a sub-interface by the name of module calling and attribute information of module calling; the attribute information configuration sub-interface called by the module comprises any more than one of the following components: exception handling strategy configuration item, error code configuration item, error information configuration item, module name configuration item and transaction code configuration item; wherein, the configuration value corresponding to the exception handling policy configuration item includes one of the following: throw exception, ignore.

In some embodiments, each of the access module and the egress module is provided with a message definition file; the method further comprises step S230:

responding to the triggering operation of the message definition file, and generating the message definition file into a second visual interface; and visually configuring the message corresponding to the access module or the access module according to the editing operation of the user on the second visual interface.

In some embodiments, step S230 may specifically include:

responding to the triggering operation of the message definition file, generating the message definition file into a second visual interface, and displaying the structural hierarchy of the message in a first preset area of the second visual interface;

responding to the selection operation of the message displayed in the first preset area of the second visual interface, and displaying a configuration interface of the message in a second preset area of the second visual interface;

the configuration interface of the message comprises any more than one of the following components: message type configuration items, message coding configuration items, packet splicing parameter configuration items, unpacking method configuration items and packet splicing method configuration items;

the configuration value of the message type configuration item may be selected from any one of the following: 1-JSON, 2-simple XML, 3-SOAP, 4-key-value pair separator, 5-KVXML, 6-fixed length, 7-separator, 8-ISO8583, 9-XML, 10-type fixed length, 11-domain fixed length, 12-Map; the configuration value of the message coding configuration item may be selected from any one of the following: UTF-8, GBK, GBK2312, GBK 18030; the grouping parameter configuration items comprise: automatic bag splicing and sub-configuring items, automatic bag splicing and sub-configuring items and filtering empty string configuring items; the configuration value of the automatic sub-packet-splicing configuration item is true or false; the configuration value of the filter empty string sub-configuration item is false or true; the unpacking parameter configuration item comprises: the method comprises the following steps of automatically unpacking a sub-configuration item, reserving an automatically unpacking data sub-configuration item and an automatically unpacking variable sub-configuration item; the configuration value of the automatic unpacking child configuration item is true or false; and the configuration value of the reserved automatic unpacking data sub-configuration item is false or true.

The embodiment of the invention provides a visual development platform, which provides a uniform engineering view, is a component-oriented development mode, can quickly build a demand-oriented business system, reduces the technical requirements of implementers, shortens the project cycle, and ensures the project quality, thereby achieving the purposes of reducing the project implementation cost, quickly meeting the business requirements of enterprises and improving the enterprise competitiveness. The communication and message processing related to external interaction can be developed in a configuration mode of the visual development platform, the number of used doorways is reduced, the method can be popularized to other service systems with the same requirements, the reusability is high, and the overall development efficiency is finally improved.

EXAMPLE III

An embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored, and when executed by a processor, the computer program implements:

The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow of the method according to the embodiments of the present invention may also be implemented by a computer program, which may be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method embodiments may be implemented. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. Of course, there are other ways of storing media that can be read, such as quantum memory, graphene memory, and so forth. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.

Example four

An embodiment of the present invention further provides an electronic device, as shown in fig. 15, including one or more processors 301, a communication interface 302, a memory 303, and a communication bus 304, where the processors 301, the communication interface 302, and the memory 303 complete communication with each other through the communication bus 304.

A memory 303 for storing a computer program;

the processor 301 is configured to implement, when executing the program stored in the memory 303:

The communication bus mentioned in the electronic device may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus. The communication interface is used for communication between the electronic equipment and other equipment.

The bus 304 includes hardware, software, or both to couple the above-described components to one another. For example, a bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an infiniband interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a video electronics standards association local (VLB) bus, or other suitable bus or a combination of two or more of these. A bus may include one or more buses, where appropriate. Although specific buses have been described and shown in the embodiments of the invention, any suitable buses or interconnects are contemplated by the invention.

The Memory may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.

Memory 303 may include mass storage for data or instructions. By way of example, and not limitation, memory 303 may include a Hard Disk Drive (HDD), a floppy Disk Drive, flash memory, an optical Disk, a magneto-optical Disk, tape, or a Universal Serial Bus (USB) Drive or a combination of two or more of these. Storage 303 may include removable or non-removable (or fixed) media, where appropriate. In a particular embodiment, the memory 303 is a non-volatile solid-state memory. In a particular embodiment, the memory 303 includes Read Only Memory (ROM). Where appropriate, the ROM may be mask-programmed ROM, Programmable ROM (PROM), Erasable PROM (EPROM), Electrically Erasable PROM (EEPROM), electrically rewritable ROM (EAROM), or flash memory or a combination of two or more of these.

The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

Although the present application provides method steps as described in an embodiment or flowchart, more or fewer steps may be included based on conventional or non-inventive means. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or end product executes, it may execute sequentially or in parallel (e.g., parallel processors or multi-threaded environments, or even distributed data processing environments) according to the method shown in the embodiment or the figures.

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 flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

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

It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, 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 the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the device, the electronic device and the readable storage medium embodiments, since they are substantially similar to the method embodiments, the description is simple, and the relevant points can be referred to the partial description of the method embodiments.

The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.

Claims

1. A visualization development platform, comprising:

the module editor is used for responding to triggering operation on the resource definition file and generating the resource definition file into a first visual interface; performing visual configuration on at least one of resource configuration, protocol configuration and component configuration corresponding to the access module or the access module according to the editing operation of a user on the first visual interface;

the engineering view designer is specifically configured to:

2. A visualization development platform as recited in claim 1, wherein the module editor comprises:

3. The visualization development platform of claim 2,

the first interface generating unit is further configured to display a distributor of a next-level catalog of resource configuration in the configuration list interface;

the second interface generation unit is further used for responding to the selected operation of the distributor, and displaying the configuration interface of the distributor in a second preset area of the first visual interface; the configuration interface of the distributor comprises: name of the distributor and attribute information of the distributor; wherein the attribute information of the distributor includes any plurality of: the log configuration items correspond to hexadecimal system of the log, the detection configuration items of the load balancing equipment, the detection request message configuration items of the load balancing equipment and the detection response message configuration items of the load balancing equipment.

4. The visualization development platform of claim 2 or 3,

the first interface generating unit is further configured to display a workflow of a next-level directory of resource configuration in the configuration list interface;

5. The visualization development platform of claim 2,

the first interface generating unit is further configured to display at least one protocol corresponding to the protocol configuration in the configuration list interface;

6. The visualization development platform of claim 2,

the first interface generating unit is further configured to display a next-level directory dataFormat of the basic component configuration in the configuration list interface;

7. The visualization development platform of claim 2,

the first interface generating unit is further configured to display a next-level directory configured by the communication component in the configuration list interface, where the next-level directory configured by the communication component includes: fixCommRecv and fixcommend;

the second interface generation unit is further used for responding to the selected operation of the fixcomRecv and displaying a first socket fixed-length configuration interface in a second preset area of the first visual interface; the first socket fixed-length configuration interface comprises a socket fixed-length name and a socket fixed-length configuration information sub-interface; the socket fixed-length configuration information sub-interface comprises any more than one of the following components: exception handling strategy configuration item, error code configuration item, error information configuration item, action configuration item, sending variable name configuration item, receiving variable name configuration item, overtime configuration item, packet header type configuration item, packet header length configuration item and self-contained length configuration item; the configuration value corresponding to the exception handling strategy configuration item is selected from the following configuration values: exception throwing and ignoring; the configuration value corresponding to the packet header type configuration item is selected from a plurality of configuration values as follows: character type, byte type, short integer, integer; the packet header length including the length self configuration item indication comprises a message length and a self length;

the second interface generating unit is further configured to respond to a selection operation of the fixcomSend and display a second socket fixed-length configuration interface in a second predetermined area of the first visual interface; the second socket fixed-length configuration interface comprises a socket fixed-length name and a socket fixed-length configuration information sub-interface; the socket fixed-length configuration information sub-interface comprises any more than one of the following components: exception handling strategy configuration item, error code configuration item, error information configuration item, action configuration item, sending variable name configuration item, receiving variable name configuration item, overtime configuration item, packet header type configuration item, packet header length configuration item and self-contained length configuration item; the configuration value corresponding to the exception handling strategy configuration item is selected from the following configuration values: exception throwing and ignoring; the configuration value corresponding to the packet header type configuration item is selected from a plurality of configuration values as follows: character type, byte type, short integer, integer; the configuration item containing the length indicates that the length of the packet header contains the length of the message and the length of the packet header.

8. The visualization development platform of claim 2,

the first interface generating unit is further used for displaying a next-level directory modelinvoke for calling component configuration in the configuration list interface;

9. A visual development platform according to claim 1, wherein each of the access module and the egress module is provided with a message definition file; the visualization development platform further comprises:

10. A visualization development platform as recited in claim 9, wherein the visualization message editor comprises:

11. A visualization development method is characterized by comprising the following steps:

generating the resource definition file into a first visual interface in response to a triggering operation on the resource definition file; performing visual configuration on at least one of resource configuration, protocol configuration and component configuration corresponding to the access module or the access module according to the editing operation of a user on the first visual interface;

wherein the generating of the engineering view comprises:

12. The method according to claim 11, wherein the resource definition file is generated as a first visual interface in response to a trigger operation on the resource definition file; performing visual configuration on at least one of resource configuration, protocol configuration and component configuration corresponding to the access module or the access module according to the editing operation of a user on the first visual interface; the method specifically comprises the following steps:

in response to a trigger operation on the resource definition file, generating the resource definition file into a first visual interface, displaying a configuration list interface in a first preset area of the first visual interface, and displaying a thread pool of a next-level directory of resource configuration in the configuration list interface;

13. The method according to claim 12, wherein the resource definition file is generated as a first visual interface in response to a trigger operation on the resource definition file; performing visual configuration on at least one of resource configuration, protocol configuration and component configuration corresponding to the access module or the access module according to the editing operation of a user on the first visual interface; the method specifically comprises the following steps:

in response to a trigger operation on the resource definition file, generating the resource definition file into a first visual interface, displaying a configuration list interface in a first preset area of the first visual interface, and displaying a distributor of a next-level catalog of resource configuration in the configuration list interface;

in response to a selected operation on the dispenser, displaying a configuration interface of the dispenser in a second predetermined area of the first visual interface; the configuration interface of the distributor comprises: name of the distributor and attribute information of the distributor; wherein the attribute information of the distributor includes any plurality of: the log configuration items correspond to hexadecimal system of the log, the detection configuration items of the load balancing equipment, the detection request message configuration items of the load balancing equipment and the detection response message configuration items of the load balancing equipment.

14. The method according to claim 12, wherein the resource definition file is generated as a first visual interface in response to a trigger operation on the resource definition file; performing visual configuration on at least one of resource configuration, protocol configuration and component configuration corresponding to the access module or the access module according to the editing operation of a user on the first visual interface; the method specifically comprises the following steps:

in response to a trigger operation on the resource definition file, generating the resource definition file into a first visual interface, displaying a configuration list interface in a first preset area of the first visual interface, and displaying a workflow of a next-level directory of resource configuration in the configuration list interface;

15. The method according to claim 12, wherein the resource definition file is generated as a first visual interface in response to a trigger operation on the resource definition file; performing visual configuration on at least one of resource configuration, protocol configuration and component configuration corresponding to the access module or the access module according to the editing operation of a user on the first visual interface; the method specifically comprises the following steps:

in response to a trigger operation on the resource definition file, generating the resource definition file into a first visual interface, displaying a configuration list interface in a first preset area of the first visual interface, and displaying at least one protocol corresponding to a protocol configuration in the configuration list interface;

16. The method according to claim 12, wherein the resource definition file is generated as a first visual interface in response to a trigger operation on the resource definition file; performing visual configuration on at least one of resource configuration, protocol configuration and component configuration corresponding to the access module or the access module according to the editing operation of a user on the first visual interface; the method specifically comprises the following steps:

in response to a trigger operation on the resource definition file, generating the resource definition file into a first visual interface, displaying a configuration list interface in a first preset area of the first visual interface, and displaying a next-level directory dataFormat of basic component configuration in the configuration list interface;

responding to the selected operation of the dataFormat, and displaying a message configuration interface in a second preset area of the first visual interface; the message configuration interface comprises: configuring a sub-interface by the name of the message and configuring a sub-interface by the attribute information of the message; wherein, the attribute information configuration sub-interface of the message comprises any more than one of the following: exception handling strategy configuration items, error code configuration items, action type configuration items, use message configuration items, message type configuration items, message coding configuration items, Map variable configuration items, message configuration items, unpacking variable configuration items and packing variable configuration items.

17. The method according to claim 12, wherein the resource definition file is generated as a first visual interface in response to a trigger operation on the resource definition file; performing visual configuration on at least one of resource configuration, protocol configuration and component configuration corresponding to the access module or the access module according to the editing operation of a user on the first visual interface; the method specifically comprises the following steps:

in response to a trigger operation on the resource definition file, generating the resource definition file into a first visual interface, and displaying a configuration list interface in a first predetermined area of the first visual interface, wherein a next-level directory of communication component configurations is displayed in the configuration list interface, and the next-level directory of the communication component configurations comprises: fixCommRecv and fixcommend;

in response to the selected operation of the fixcomRecv, displaying a first socket fixed-length configuration interface in a second preset area of the first visual interface; the first socket fixed-length configuration interface comprises a socket fixed-length name and a socket fixed-length configuration information sub-interface; the socket fixed-length configuration information sub-interface comprises any more than one of the following components: exception handling strategy configuration item, error code configuration item, error information configuration item, action configuration item, sending variable name configuration item, receiving variable name configuration item, overtime configuration item, packet header type configuration item, packet header length configuration item and self-contained length configuration item; the configuration value corresponding to the exception handling strategy configuration item is selected from the following configuration values: exception throwing and ignoring; the configuration value corresponding to the packet header type configuration item is selected from a plurality of configuration values as follows: character type, byte type, short integer, integer; the packet header length including the length self configuration item indication comprises a message length and a self length;

responding to the selected operation of the fixcomSend, and displaying a second socket fixed-length configuration interface in a second preset area of the first visual interface; the second socket fixed-length configuration interface comprises a socket fixed-length name and a socket fixed-length configuration information sub-interface; the socket fixed-length configuration information sub-interface comprises any more than one of the following components: exception handling strategy configuration item, error code configuration item, error information configuration item, action configuration item, sending variable name configuration item, receiving variable name configuration item, overtime configuration item, packet header type configuration item, packet header length configuration item and self-contained length configuration item; the configuration value corresponding to the exception handling strategy configuration item is selected from the following configuration values: exception throwing and ignoring; the configuration value corresponding to the packet header type configuration item is selected from a plurality of configuration values as follows: character type, byte type, short integer, integer; the configuration item containing the length indicates that the length of the packet header contains the length of the message and the length of the packet header.

18. The method according to claim 12, wherein the resource definition file is generated as a first visual interface in response to a trigger operation on the resource definition file; performing visual configuration on at least one of resource configuration, protocol configuration and component configuration corresponding to the access module or the access module according to the editing operation of a user on the first visual interface; the method specifically comprises the following steps:

in response to a trigger operation on the resource definition file, generating the resource definition file into a first visual interface, displaying a configuration list interface in a first preset area of the first visual interface, and displaying a next-level directory modelinvoke for calling component configuration in the configuration list interface;

responding to the selected operation of the modelelnvoke, and calling a configuration interface by a display module in a second preset area of the first visual interface; the module calling configuration interface comprises: configuring a sub-interface by the name of module calling and attribute information of module calling; the attribute information configuration sub-interface called by the module comprises any more than one of the following components: exception handling strategy configuration item, error code configuration item, error information configuration item, module name configuration item and transaction code configuration item; wherein, the configuration value corresponding to the exception handling policy configuration item includes one of the following: throw exception, ignore.

19. The method according to claim 11, wherein each of the access module and the egress module is provided with a message definition file; the method further comprises the following steps:

20. The method of claim 19, wherein the message definition file is generated as a second visual interface in response to a triggering operation on the message definition file; visually configuring the message corresponding to the access module or the access module according to the editing operation of the user on the second visual interface; the method specifically comprises the following steps:

responding to the selection operation of the message displayed in the first preset area of the second visual interface, and displaying a configuration interface of the message in a second preset area of the second visual interface; the configuration interface of the message comprises any more of the following configuration items: message type configuration items, message coding configuration items, packet splicing parameter configuration items, unpacking method configuration items and packet splicing method configuration items.

21. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the visualization development method of any one of claims 11 to 20.

22. A computer device, comprising:

one or more processors;

storage means for storing one or more programs;

the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the visualization development method of any of claims 11-20.