Metadata object association configuration method and device based on paas platform

Abstract

The application provides a metadata object association configuration method and device based on a paas platform, wherein the method comprises the following steps: configuring an application scene in an application table, creating metadata objects corresponding to the application scene and configuring the metadata objects in an available object relationship table, configuring common processing modes of the metadata objects in a general table, and configuring application fields of the metadata objects except the common processing modes in an application field table; obtaining an application package corresponding to the application scene, and configuring the application package in each management page of the metadata objects in the available object relationship table; installing the application package in the management page, obtaining attribute data which is actually set in the management page based on the general table and the application field table, assembling an instance table together with a corresponding page component and a current metadata object identifier, isolating the metadata objects in the instance table through a metadata object relationship table, and making the association configuration under the application scene effective. The application does not need to manually configure the common processing modes under different application scenes each time.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of platform design, and in particular to a metadata object association configuration method and device based on a paas platform. BACKGROUND

[0002] Paas is a cloud computing service mode platform, which can provide a complete application development environment for developers in a configurable manner, and has abstracting and dynamic generalization capabilities compared with the traditional platform fixed configuration mode.

[0003] In the related art, metadata objects in the paas platform are isolated from each other, and different metadata objects are independent in storage and behavior, have different storage spaces, fields and operations, but in some business scenarios, different metadata objects need to have some same behaviors, such as inserting the same field or the same button when configuring, which requires repeated manual addition each time the configuration is performed, but the above defects are difficult for the metadata business scenario because the business application scenario is independent and needs to be implemented across objects, and the metadata tenants are also isolated from each other.

[0004] In summary, the above analysis of the development status of the technical field shows that there is a lack of a configuration expansion table structure to associate to a specific metadata object in the existing technology. SUMMARY

[0005] The present application relates to the technical field of platform design, and in particular to a metadata object association configuration method and device based on a paas platform.

[0006] According to a first aspect of an embodiment of the present application, a metadata object association configuration method based on a paas platform is provided, comprising:

[0007] Configuring an application scenario in an application table, creating metadata objects corresponding to the application scenario and configuring them in an available object relationship table, configuring common processing modes of the metadata objects in a general table, and configuring application fields of the metadata objects except the common processing modes in an application field table;

[0008] Obtaining an application package corresponding to the application scenario, and configuring the application package in each management page of the metadata objects corresponding to the available object relationship table;

[0009] Installing the application package in the management page, obtaining attribute data set in the management page based on the general table and the application field table, assembling an instance table together with a corresponding page component and a current metadata object identifier, isolating metadata objects in the instance table through the metadata object relationship table, and making the association configuration under the application scenario effective.

[0010] According to a second aspect of the embodiment of the present application, a metadata object association configuration device based on a paas platform is provided, comprising:

[0011] An initialization module is configured to configure an application scenario in an application table, create metadata objects corresponding to the application scenario and configure in an available object relationship table, configure common processing modes of the metadata objects in a general table, and configure application fields of the metadata objects except the common processing modes in an application field table.

[0012] An installation package configuration module is configured to obtain an application package corresponding to the application scenario and configure the application package in each management page of the metadata objects in the available object relationship table.

[0013] An association configuration module is configured to install the application package in the management page, obtain attribute data set based on the general table and the application field table in the management page, assemble an instance table together with a corresponding page component and a current metadata object identifier, isolate the metadata objects in the instance table through the metadata object relationship table, and make the association configuration under the application scenario effective.

[0014] According to a third aspect of the embodiment of the present application, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is executed by the processor to implement the steps of the metadata object association configuration method based on the paas platform provided in the first aspect of the present application.

[0015] According to a fourth aspect of the embodiment of the present application, a computer readable storage medium is provided, which stores an information transmission implementation program, wherein the program is executed by a processor to implement the steps of the metadata object association configuration method based on the paas platform provided in the first aspect of the present application.

[0016] The technical solution provided by the embodiment of the present application has the following beneficial effects: a general configuration scheme based on a paas platform is provided, and it is not necessary to manually configure common processing modes under different application scenarios each time, a general template is formed by customizing configuration of various table structures, which is used as a basis for instantiation of metadata objects, and the paas flexible abstraction feature is used to make the metadata objects not affect each other even in the case of not being completely isolated during configuration.

[0017] It should be understood that the foregoing general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0018] In order to make one or more embodiments or the technical solutions of the prior art in the specification clearer, the drawings needed in the embodiment or prior art description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments described in the specification, and other drawings can be obtained by those skilled in the art without creative labor under the premise of the drawings.

[0019] Figure 1 is a flowchart of a metadata object association configuration method based on a paas platform according to an embodiment of the present application;

[0020] Figure 2 is a schematic diagram of a general template configuration according to an embodiment of the present application;

[0021] Figure 3 is a schematic diagram of a management page not installed according to an embodiment of the present application;

[0022] Figure 4 is a schematic diagram of a page application field table setting according to an embodiment of the present application;

[0023] Figure 5 is a schematic diagram of a page operation table setting according to an embodiment of the present application;

[0024] Figure 6 is a schematic diagram of a page button table setting according to an embodiment of the present application;

[0025] Figure 7 is a schematic diagram of an instance table assembly according to an embodiment of the present application;

[0026] Figure 8 is a schematic diagram of metadata object isolation according to an embodiment of the present application;

[0027] Figure 9 is a schematic diagram of a management page installed according to an embodiment of the present application;

[0028] Figure 10 is a schematic diagram of an application effect according to an embodiment of the present application;

[0029] Figure 11 is a schematic diagram of a metadata object association configuration device based on a paas platform according to an embodiment of the present application;

[0030] Figure 12 is a schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0031] In order to make the person skilled in the art better understand the technical solutions in the one or more embodiments of the present specification, the technical solutions in the one or more embodiments of the present specification will be clearly and completely described in the following with reference to the drawings in the one or more embodiments of the present specification. Obviously, the described embodiments are only a part of the embodiments of the present specification, rather than all the embodiments. Based on the one or more embodiments of the present specification, all other embodiments obtained by the person skilled in the art without creative labor should belong to the protection scope of the present document.

[0032] Method embodiment one

[0033] According to the embodiments of the present application, a metadata object association configuration method based on a paas platform is provided, Figure 1 is the flow chart of the metadata object association configuration method based on the paas platform of the embodiments of the present application, as Figure 1 shown, the metadata object association configuration method based on the paas platform according to the embodiments of the present application specifically includes:

[0034] In step S110, the application scenario is configured in the application table, the metadata object corresponding to the application scenario is created and configured in the available object relationship table, the common processing mode of each metadata object is configured in the general table, and the application field of each metadata object except the common processing mode is configured in an application field table, specifically including:

[0035] In the available object relationship table, the application scenario field and the corresponding metadata object field are inserted as an available relationship.

[0036] The general table composed of the operation table and the button table is obtained, wherein the operation table is used to store the same business operation between each metadata object, and the button table is used to store the same button operation between each metadata object; the scene field, the operation field, the state field and the corresponding configuration action are inserted in the operation table; the scene field, the button field, the state field and the corresponding configuration action are inserted in the button table.

[0037] It should be noted that on the basis of the above metadata field, other fields can be added according to actual application conditions, which is also within the protection scope of the present application.

[0038] In step S120, the application package corresponding to the application scenario is obtained, and the application package is configured in each management page of the metadata object in the available object relationship table, specifically including:

[0039] The application package in each application scenario is built-in the same processing logic, which is only displayed in different management pages, and the processing logic refers to the complete implementation logic of the metadata object configuration and assembly based on the paas platform of the embodiments of the present application.

[0040] In step S130, the application package is installed in the management page, the attribute data set in the management page based on the general table and the application field table is obtained, the instance table is assembled together with the corresponding page component and the current metadata object identifier, the metadata objects in the instance table are isolated through the metadata object relationship table, the associated configuration in the application scenario is effective, and the specific operations include the following steps.

[0041] The attribute data set in the application field table, the operation table and the button table through the scene field is extracted, and is assembled with the current metadata object identifier corresponding to the management page to obtain the first instance table, the second instance table and the third instance table respectively.

[0042] Since the UI page component itself exists and does not need to be set in advance in step S110, the UI page component corresponding to the current metadata object is directly obtained, and the fourth instance table is assembled with the current metadata object identifier.

[0043] The first instance table, the second instance table, the third instance table and the fourth instance table are combined to form an instance table including all metadata objects, and the current metadata object identifier is used as a primary key to organize the instance tables.

[0044] The isolation of the metadata objects is realized through the metadata object identifier.

[0045] Method embodiment two

[0046] In the embodiment of the application, an effective application needs to be developed to support the installation and uninstallation of payment application (paymentApp3X) and current payment (currentPayment3X);

[0047] The table structure is defined as follows:

[0048] The application table p_app;

[0049] The available object relationship table p_app_avl_object;

[0050] The operation table p_app_action;

[0051] The button table p_app_button;

[0052] The application field table p_app_meta_field;

[0053] The page component table p_app_ui_component;

[0054] The metadata object relationship table p_meta_app_ref;

[0055] The background configuration process is as follows, and the following configuration is used for tenant upgrade:

[0056] Insert data in the application table p_app, the field name is effect, which means configuring the application scenario "effective application";

[0057] Insert data in the available object relationship table p_app_avl_object, the app_name is effect, which means the scenario field, and the avl_obj_name is paymentApp3X, which means the metadata object, that is, configuring the available metadata object as "payment application"; insert data in the available object relationship table p_app_avl_object, the app_name is effect, and the avl_obj_name is currentPayment3X, which means configuring the available metadata object as "current payment";

[0058] Insert data in the operation table p_app_action, the app_name is effect, which means the scenario field, the action is tackEffect, which means the operation is payment effective, and the label is effective, which means the state, corresponding to configuring the operation as modifying the effective state field to be effective; insert data in the operation table p_app_action, the app_name is effect, which means the scenario field, the action is cancelEffect, which means the operation is payment ineffective, and the label is cancelEffect, which means the state, corresponding to configuring the operation as modifying the effective state field to be ineffective;

[0059] Insert data in the button table p_app_button, the app_name is effect, which means the scenario field, the name is tackEffect, which means the button is payment effective, and the label is effective, which means the state, corresponding to configuring the operation as modifying the effective state field to be effective; insert data in the button table p_app_button, the app_name is effect, which means the scenario field, the name is cancelEffect, which means the button is payment ineffective, and the label is effective, which means the state, corresponding to configuring the operation as modifying the effective state field to be ineffective;

[0060] Configure all the required fields used by the two metadata objects "payment application" and "current payment" in the application field table p_app_meta_field, in each piece of data, the app_name is effect, which means the scenario field, the name is effectiveStatus, which means the field name, and the label is effective state, which means the field effective.

[0061] Figure 2 is a schematic diagram of the general template configuration of the embodiment of the application, as Figure 2As shown, the table structure required for defining the general template is shown, and since the metadata object relationship table p_meta_app_ref is used in data isolation, it is not shown Figure 2 In the present embodiment, preferably, additional custom fields are allowed in each table, such as ent_code, which are conventional fields used in actual applications.

[0062] Obtain the application package corresponding to the application scenario, and set metadata object association configuration logic in the application installation package;

[0063] At this time, the active application scenario in the object relationship table maintains two metadata objects, namely paymentApp3X and currentPayment3X, so in the uninstalled application of the two management pages of paymentApp3X and currentPayment3X, there is an active application installation package, Figure 3 is a schematic diagram of the management page uninstalled in the present embodiment, as Figure 3 shown, the interface when uninstalled is shown.

[0064] On the basis of the general configuration, link with the metadata object instantiation, and generate data in the management page based on the specific business settings of the metadata object, the data in each table needs to be extracted and assembled to form the configuration mode corresponding to the metadata object, and this step is executed in the process of installing the application package;

[0065] Extract the data in the application field table p_app_meta_field according to app_name, and assemble the first instance table p_meta_field according to app_name, name, label, and the current metadata object identifier meta_id; Figure 4 is a schematic diagram of the page application field table setting in the present embodiment, as Figure 4 shown, the setting of the management page corresponding to paymentApp3X is shown;

[0066] Extract the data in the operation table p_app_action according to app_name, and assemble the second instance table p_action according to app_name, name, label, and the current metadata object identifier meta_id; Figure 5 is a schematic diagram of the page operation table setting in the present embodiment, as Figure 5 shown, the operation settings of canceling activation and activation are shown;

[0067] Extract the data in the button table p_app_button according to app_name, and assemble the third instance table p_meta_button according to app_name, name, label, and the current metadata object identifier meta_id; Figure 6is a schematic diagram of the page button table setting of the embodiment of the present application, as shown in Figure 6 The button settings for showing, canceling and enabling are shown.

[0068] The UI page component corresponding to the current metadata object is obtained, and the fourth instance table p_meta_ui_component is assembled with the metadata object identifier meta_id.

[0069] The first instance table, the second instance table, the third instance table and the fourth instance table are combined to form the instance table p_meta including all metadata objects, Figure 7 is a schematic diagram of the assembly of the instance table of the embodiment of the present application, as shown in Figure 7 The process of maintaining the data in each table in the instance table through the primary key meta_id is shown.

[0070] The isolation of each metadata object is realized through the metadata object identifier, that is, in the metadata object relationship table p_meta_app_ref, each metadata object is distinguished by the meta_id identifier, which is used for subsequent user use. Figure 8 is a schematic diagram of the metadata object isolation of the embodiment of the present application, as shown in Figure 8 The isolation through the metadata object relationship table p_meta_app_ref is shown, and preferably, when the form data volume is large, a partition strategy is used for storage, and the data hotness of the metadata object task application is checked regularly, and the data that is not accessed for more than a preset time is marked as cold data and migrated.

[0071] When the application package is installed, Figure 9 is a schematic diagram of the management page of the embodiment of the present application, as shown in Figure 9 The enabled application is shown in the installed application of the management page, Figure 10 is a schematic diagram of the application effect of the embodiment of the present application, as shown in Figure 10 The enable and cancel enable buttons appear on the payment application document detail page, and the buttons are clicked to modify the enable state to enabled or not enabled, respectively.

[0072] Subsequently, the application can be uninstalled, and the specific process is to extract the p_meta_field, p_action, p_meta_button and p_meta_app_ref data for deletion according to the current metadata object meta_id.

[0073] In summary, in view of the existing problems, the metadata object association configuration method based on the paas platform is proposed, a general configuration scheme based on the paas platform is proposed, without manual configuration of common processing methods in different application scenarios each time, for example, the same operation or button, a general template is formed by customizing various table structures, which is used as the basis for metadata object instantiation link, and the flexible abstraction characteristics of paas are used, so that each metadata object can achieve the effect of not affecting each other even in the case of not completely isolated configuration.

[0074] Device embodiment

[0075] According to the embodiment of the application, a metadata object association configuration device based on a paas platform is provided, Figure 11 is a schematic diagram of the metadata object association configuration device based on the paas platform of the embodiment of the application, as Figure 11 shown, the metadata object association configuration device based on the paas platform according to the embodiment of the application specifically includes:

[0076] The initialization module 110 is configured to configure an application scenario in an application table, create a metadata object corresponding to the application scenario and configure it in an available object relationship table, configure common processing methods of each metadata object in a general table, and configure application fields of each metadata object except the common processing methods in an application field table, and is specifically configured to:

[0077] In the available object relationship table, insert the application scenario field and the corresponding metadata object field as an available relationship.

[0078] Obtain a general table composed of an operation table and a button table, wherein the operation table is used to store the same business operation between each metadata object, and the button table is used to store the same button operation between each metadata object.

[0079] Insert the scene field, operation field, state field and corresponding configuration actions in the operation table; insert the scene field, button field, state field and corresponding configuration actions in the button table.

[0080] The installation package configuration module 112 is configured to obtain an application package corresponding to the application scenario, and configure the application package in each management page of the metadata object corresponding to the available object relationship table.

[0081] The association configuration module 114 is configured to install the application package in the management page, obtain the attribute data set in the management page based on the general table and the application field table, assemble an instance table with the corresponding page component and the current metadata object identifier, isolate the metadata objects in the instance table through the metadata object relationship table, and the association configuration in the application scenario takes effect, and is specifically configured to:

[0082] The attribute data actually set in the application field table, the operation table and the button table are extracted through the scene field respectively, and are assembled with the current metadata object identification corresponding to the management page to obtain a first instance table, a second instance table and a third instance table respectively.

[0083] The UI page component corresponding to the current metadata object is acquired, and the fourth instance table is obtained by assembling the current metadata object identification.

[0084] The first instance table, the second instance table, the third instance table and the fourth instance table are combined to form the instance table including all metadata objects.

[0085] The isolation of each metadata object is realized through the metadata object identification.

[0086] In summary, in view of the existing problems, the metadata object association configuration device based on the paas platform is proposed, a general configuration scheme based on the paas platform is proposed, without manual configuration of common processing methods in different application scenarios each time, for example, the same operation or button, the general template is formed by customizing various table structures, which is used as the basis for metadata object instantiation link, and the flexible abstraction characteristics of paas are used, so that each metadata object can achieve the effect of not affecting each other even in the case of not completely isolated configuration.

[0087] Electronic device embodiment

[0088] Figure 12 is a schematic diagram of an electronic device according to an embodiment of the present application. The electronic device 1200 can include at least one processor 1210 and a memory 1220. The processor 1210 can execute instructions stored in the memory 1220. The processor 1210 is communicatively connected to the memory 1220 through a data bus. In addition to the memory 1220, the processor 1210 can also be communicatively connected to an input device 1230, an output device 1240 and a communication device 1250 through the data bus.

[0089] The processor 1210 can be any conventional processor, such as a commercially available CPU. The processor can also include, for example, a graphic processing unit (GPU), a field programmable gate array (FPGA), a system on chip (SOC), an application specific integrated circuit (ASIC), or a combination thereof.

[0090] The memory 1220 can be implemented by any type of volatile or nonvolatile storage devices or a combination thereof such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable programmable read only memory (EPROM), programmable read only memory (PROM), read only memory (ROM), magnetic storage, flash memory, magnetic or optical disk.

[0091] In the embodiments of the present disclosure, executable instructions are stored in the memory 1220, and the processor 1210 can read the executable instructions from the memory 1220 and execute the instructions to implement all or part of the steps of the paas platform-based metadata object association configuration method of any of the above example embodiments.

[0092] Computer-readable storage medium embodiment

[0093] In addition to the above method and device, the example embodiments of the present disclosure can also be a computer program product or a computer readable storage medium storing the computer program product, the computer program product including computer program instructions executable by a processor to implement all or part of the steps described in the paas platform-based metadata object association configuration method of any of the above example embodiments.

[0094] The computer program product can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++, etc., as well as conventional procedural programming languages, such as the "C" programming language or similar programming languages and scripting languages (e.g., Python). The program code can execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device or entirely on the remote computing device or server.

[0095] The computer readable storage medium can be any combination of one or more non-transitory computer readable media. The non-transitory computer readable medium can be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium can include, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or any suitable combination of the above. More specific examples of the computer readable storage medium include a static random access memory (SRAM), an electrically erasable programmable read only memory (EEPROM), an erasable programmable read only memory (EPROM), a programmable read only memory (PROM), a read only memory (ROM), a magnetic storage, a flash memory, a magnetic or optical disk, or any suitable combination of the above.

[0096] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, and are not intended to limit the present application; although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that the technical solutions recorded in the above embodiments can be modified, or some or all of the technical features can be replaced by equivalents; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A metadata object association configuration method based on a paas platform, characterized in that, The application comprises the following steps: In the application table, the application scene is configured, the metadata object corresponding to the application scene is created and configured in the available object relationship table, the common processing mode of each metadata object is configured in the general table, and the application field of each metadata object except the common processing mode is configured in an application field table, specifically comprising the following steps: In the available object relationship table, an application scene field and a corresponding metadata object field are inserted as a usable relationship; The general table composed of an operation table and a button table is obtained, wherein the operation table is used to store the same business operation between each metadata object, and the button table is used to store the same button operation between each metadata object; In the operation table, a scene field, an operation field, a state field and corresponding configuration actions are inserted; in the button table, a scene field, a button field, a state field and corresponding configuration actions are inserted; The application package corresponding to the application scene is obtained, and the application package is configured in each management page of the metadata object corresponding to the available object relationship table; In the management page, the application package is installed, the attribute data of the management page which is set based on the general table and the application field table is obtained, the instance table is assembled together with the corresponding page component and the current metadata object identifier, the metadata objects in the instance table are isolated through the metadata object relationship table, the associated configuration under the application scene is effective, and specifically comprising the following steps: The attribute data of the application field table, the operation table and the button table which is set in reality is extracted through the scene field, and the current metadata object identifier corresponding to the management page is assembled to obtain a first instance table, a second instance table and a third instance table respectively; The UI page component corresponding to the current metadata object is obtained, and the fourth instance table is assembled together with the current metadata object identifier; The first instance table, the second instance table, the third instance table and the fourth instance table are composed to form an instance table comprising all metadata objects; The isolation of each metadata object is realized through the metadata object identifier. 2.A metadata object association configuration device based on a paas platform, characterized in that, The application comprises the following steps: An initialization module is configured to configure an application scene in an application table, create a metadata object corresponding to the application scene and configure the metadata object in an available object relationship table, configure a common processing mode of each metadata object in a general table, and configure an application field of each metadata object except the common processing mode in an application field table, specifically for: In the available object relationship table, an application scene field and a corresponding metadata object field are inserted as a usable relationship; The general table composed of an operation table and a button table is obtained, wherein the operation table is used to store the same business operation between each metadata object, and the button table is used to store the same button operation between each metadata object; In the operation table, a scene field, an operation field, a state field and corresponding configuration actions are inserted; in the button table, a scene field, a button field, a state field and corresponding configuration actions are inserted; An installation package configuration module is configured to obtain an application package corresponding to the application scene, and configure the application package in each management page of the metadata object corresponding to the available object relationship table. The association configuration module is configured to install the application package in the management page, obtain attribute data set in the management page based on a general table and an application field table, assemble an instance table together with a corresponding page component and a current metadata object identifier, isolate metadata objects in the instance table through a metadata object relationship table, and make the association configuration in the application scenario effective. Attribute data set in the application field table, the operation table and the button table is extracted through a scene field, and is assembled with a current metadata object identifier corresponding to the management page to obtain a first instance table, a second instance table and a third instance table respectively. A UI page component corresponding to the current metadata object is obtained, and a fourth instance table is obtained by assembling the current metadata object identifier. The first instance table, the second instance table, the third instance table and the fourth instance table are combined to form an instance table including all metadata objects. Isolation of each metadata object is realized through the metadata object identifier.

3. An electronic device, comprising: The computer readable storage medium stores an implementation program of information transmission, and the program is executed by the processor to realize the steps of the metadata object association configuration method based on the paas platform as claimed in claim 1. The computer readable storage medium stores an implementation program of information transmission, and the program is executed by the processor to realize the steps of the metadata object association configuration method based on the paas platform as claimed in claim 1.

4. A computer-readable storage medium, characterized in that, ​

Images