Multi-portal system for configuration information differentiation processing and configuration differentiation processing method
By adopting public libraries and customized libraries in the computing power portal, intensive development deployment and differentiated processing of multi-portal systems are achieved, and the problem of large resource investment under traditional deployment methods is solved, reducing operation and maintenance costs and supporting differentiated configurations of operators.
Patent Information
- Application Number
- CN202411226013.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-02
- Publication Date
- 2025-02-28
AI Technical Summary
When implementing the deployment of computing power portals, the existing technology requires each to deploy a complete set of front and back-end systems, resulting in large investment in software development and hardware resources, making it difficult to achieve intensive development and deployment of the system.
It provides a multi-portal system for differentiated processing of information, adopts public libraries and customized libraries, and uses integrated support platforms, resource scheduling and opening platforms and peripheral business platforms to realize differentiated processing and intensive data storage of different operators.
It realizes that different operators use the same back-end support platform, unified deployment and intensive data storage, reduce operation and maintenance costs, and supports different operators to connect with different third-party computing power cooperation platforms according to their own situation.
Smart Images

Figure CN119537734A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of Internet technology, and in particular to a multi-portal system for differential processing of configuration information and a method for differential processing of configuration information. Background Art
[0002] With the booming development of the computing power industry, driven by AI applications such as ChatGTP and Sora, the demand for computing power has exploded. Users generally obtain various computing power applications through computing power portals. In order to better serve computing power users, governments and enterprises and institutions have planned to establish computing power portals.
[0003] The current mainstream portal website architecture is generally a front-end and back-end separated deployment architecture, that is, each website has a complete front-end and back-end system deployed. The front-end is used to accept user requests, and the back-end is used to process business logic, access data, and connect to third-party platforms. Take an exchange in City G and a government agency in City S as examples. Both units have similar computing portal deployment requirements. In the traditional deployment method, each needs to deploy a complete front-end and back-end system.
[0004] Although the traditional deployment method can meet the personalized business needs of each operator, the corresponding software development and hardware resource investment is large.
[0005] Therefore, how to achieve intensive development and deployment of the system becomes a problem that needs to be solved. Summary of the invention
[0006] The technical problem to be solved by the present application is to provide a multi-portal system for differential processing of configuration information and a method for differential processing of configuration information in order to solve the problems existing in the prior art.
[0007] In a first aspect, the present application provides a multi-portal system for differential processing of configuration information, the system comprising: N front-end portals, an integrated support platform, a resource scheduling and activation platform, and M peripheral business platforms, where M and N are both positive integers;
[0008] The integrated support platform includes a service layer, a data access layer, a data adaptation layer and a database, wherein the database includes a common library corresponding to all front-end portals and a customized library corresponding to each front-end portal;
[0009] The public library is used to store public service tables, and the customized library is used to store customized service tables;
[0010] The data access layer is used to support access to different databases based on tenant identifiers, the data adaptation layer is used to define the databases where each table is located and provide corresponding APIs, and the service layer accesses the public library and / or the customized library through the data access layer and the data adaptation layer to obtain business information corresponding to the front-end portal, and performs business processing for the front-end portal based on the obtained business information.
[0011] In some embodiments, the public library is specifically used to store at least one of a public business configuration table, a tenant table, a user table, a menu table, a product definition table, a product listing table, a process definition table, a product ordering process table, an order table, an operation data statistics table, a portal style configuration table, and a portal language configuration table.
[0012] In some embodiments, each business table in the public library isolates data for different front-end portals through a tenant ID.
[0013] In some embodiments, when the system is running, the data in the public library and / or the data in the custom library are loaded into the cache.
[0014] In some embodiments, the service layer accesses the public library and / or the custom library through the data access layer and the data adaptation layer, including:
[0015] The data access layer initializes access connections for all libraries and puts them into the connection pool;
[0016] The data adaptation layer determines the target library where the target table is located according to the target table that the service layer needs to access, and then searches the connection pool for the corresponding database connection according to the library name of the target table, so that the service layer accesses the database data based on the database connection.
[0017] In a second aspect, the present application provides a configuration information differentiation processing method, which is applied to the above-mentioned multi-portal system, and the method includes:
[0018] Preset a public service table and a customized service table, store the public service table in a public library, and store the customized service table in a customized library;
[0019] The business information corresponding to the front-end portal is obtained by accessing the public library and / or the customized library, and business processing is performed for the front-end portal according to the obtained business information.
[0020] In some embodiments, the public library is specifically used to store at least one of a public business configuration table, a tenant table, a user table, a menu table, a product definition table, a product listing table, a process definition table, a product ordering process table, an order table, an operation data statistics table, a portal style configuration table, and a portal language configuration table.
[0021] In some embodiments, each business table in the public library performs data isolation for different front-end portals through tenant IDs.
[0022] In some embodiments, when the system is running, the data in the public library and / or the data in the custom library are loaded into the cache.
[0023] In some embodiments, accessing the public library and / or the custom library includes:
[0024] Initialize access connections for all libraries and put them into the connection pool;
[0025] The target library where the target table is located is determined according to the target table that the service layer needs to access, and then the corresponding database connection is searched in the connection pool according to the library name of the target table, and the database data is accessed based on the database connection.
[0026] The present application provides a multi-portal system for differentiated processing of configuration information and a method for differentiated processing of configuration information. The system includes: N front-end portals, an integrated support platform, a resource scheduling and activation platform, and M peripheral business platforms, where M and N are both positive integers; wherein the integrated support platform includes a service layer, a data access layer, a data adaptation layer, and a database, wherein the database includes a common library corresponding to all front-end portals and a customized library corresponding to each front-end portal; wherein the common library is used to store common business tables, and the customized library is used to store customized business tables; the data access layer is used to support access to different databases based on tenant identifiers, and the data adaptation layer is used to define the databases where each table is located and provide corresponding APIs, and the service layer accesses the common library and / or the customized library through the data access layer and the data adaptation layer to obtain business information corresponding to the front-end portal, and performs business processing for the front-end portal based on the acquired business information. This application uses the public library + customized library method to realize a supporting platform to serve different operators on the basis of unified business processes, and realizes intensive data storage of different front-end portal operations and configuration data; the data of customized businesses is stored in the customized library, and the general business process provides a general warehousing method. The different fields of different operators are solved by reusing extended fields, and each business party organizes the warehousing and parsing by itself. BRIEF DESCRIPTION OF THE DRAWINGS
[0027] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0028] Figure 1 This is a traditional portal system architecture diagram in the prior art;
[0029] Figure 2An architecture diagram of a multi-portal system for differential processing of configuration information provided in an embodiment of the present application;
[0030] Figure 3 A schematic diagram of a configuration information differentiation processing method provided in an embodiment of the present application;
[0031] Figure 4 A schematic diagram of a product ordering process provided in an embodiment of the present application;
[0032] Figure 5 A schematic diagram of the order service process provided in an embodiment of the present application.
[0033] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION
[0034] In order to enable those skilled in the art to better understand the technical solution of the present application, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.
[0035] It should be understood that the specific embodiments and drawings described herein are only used to explain the present application, rather than to limit the present application.
[0036] It can be understood that, in the absence of conflict, the various embodiments in the present application and the various features in the embodiments can be combined with each other.
[0037] It can be understood that, for the convenience of description, the drawings of the present application only show the parts related to the present application, while the parts unrelated to the present application are not shown in the drawings.
[0038] It can be understood that each unit and module involved in the embodiments of the present application may correspond to only one physical structure, or may be composed of multiple physical structures, or multiple units and modules may be integrated into one physical structure.
[0039] It can be understood that the terms "first", "second", etc. in the embodiments of the present application are used to distinguish different objects, or to distinguish different processing of the same object, rather than to describe a specific order of objects.
[0040] It is understandable that, in the absence of conflict, the functions and steps marked in the flowcharts and block diagrams of the present application may occur in an order different from that marked in the drawings.
[0041] It is understood that the flowcharts and block diagrams of the present application illustrate the possible architectures, functions, and operations of the systems, devices, equipment, and methods according to the various embodiments of the present application. Among them, each box in the flowchart or block diagram may represent a unit, module, program segment, code, which contains executable instructions for implementing the specified functions. Moreover, each box or combination of boxes in the block diagram and flowchart may be implemented by a hardware-based system that implements the specified functions, or by a combination of hardware and computer instructions.
[0042] It can be understood that the units and modules involved in the embodiments of the present application can be implemented by software or hardware, for example, the units and modules can be located in a processor.
[0043] Figure 1 This is a traditional portal system architecture diagram in the prior art, such as Figure 1 As shown in the figure, the current mainstream portal website architecture is generally a deployment architecture with separated front-end and back-end, that is, a complete set of front-end and back-end systems are deployed on each website. Since each customer has different needs, each new system needs to be developed and launched, resulting in a long cycle. Each customer's portal system needs to maintain its own software version and data separately. Modifications to public business logic and the launch of new features will cause all portal systems to be re-released, and the operation and maintenance costs will increase exponentially. In addition, the number of docking interfaces between the portal and the peripheral platform has also doubled. Even if different portals are connected to the same peripheral platform, they need to be independently developed and debugged, and cannot share the same interface.
[0044] In view of the above shortcomings, the present invention aims to achieve the following objectives:
[0045] 1. Different operators use the same backend support platform to achieve unified system deployment and intensive data storage;
[0046] 2. Different operators can connect to different third-party computing power cooperation platforms according to their own situations;
[0047] 3. Different operators can achieve business customization through differentiation of business logic.
[0048] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.
[0049] Figure 2 The architecture diagram of a multi-portal system for differential processing of configuration information provided in an embodiment of the present application is as follows: Figure 2As shown, the present application provides a multi-portal system for differential processing of configuration information, the system comprising: N front-end portals, an integrated support platform, a resource scheduling and activation platform, and M peripheral business platforms, where M and N are both positive integers;
[0050] The front-end portal calls the integrated support platform through the API interface, and different operator tenants correspond to different front-end portals; specifically, in this application, each operator (in this application, the operator of each front-end portal is regarded as a tenant) independently manages and uses a front-end portal, and each operates independently. The front-end portal contacts can include different forms such as computer WEB terminals, mobile applets, H5, etc. Multiple front-end portals call and reuse the back-end integrated support platform through API interfaces.
[0051] Optionally, if multiple front-end portals use the same business process, different front-end portals all call the same API interface of the integrated support platform, but carry different tenant IDs in the API interface protocol to distinguish different operators.
[0052] The peripheral service platform is an entity that provides services to the front-end portal operator. When a user orders a product on the portal, if a third-party platform is required to provide services, the portal sends a service activation request to the third-party service platform through an API.
[0053] The integrated support platform is connected to the resource scheduling and activation platform and each of the peripheral business platforms respectively. The integrated support platform is used to configure products corresponding to the business needs for the front-end portal based on the resource scheduling and activation platform and each of the peripheral business platforms after obtaining the business needs of the front-end portal. In this application, the integrated support platform is connected to multiple front-end portals in the north, that is, a system architecture combining 1 back-end support platform and N front-end portals is adopted, and products or solutions are flexibly configured and released according to the business operation needs of each front-end portal to support the needs of different portal business display and expansion. In addition, the integrated support platform can be connected to multiple peripheral business platforms in the east-west direction to realize a closed loop of the entire business process, including but not limited to different payment platforms, different order platforms, different third-party partner business platforms, etc., and connected to the resource scheduling and activation platform in the south to realize a closed loop of business processes.
[0054] In this application, the integrated support platform processes the business requests of each tenant. The same business has different requirements and corresponding different implementations for different tenants. Correspondingly, different library tables or fields are required to store differentiated data. The present invention adopts public library + customized library to realize the storage of public library tables and customized library tables.
[0055] refer to Figure 2The integrated support platform includes a service layer, a data access layer, a data adaptation layer and a database. The database includes a common library corresponding to all front-end portals and a customized library corresponding to each front-end portal. Figure 2 Portal 1 Library, Portal 2 Library, etc.);
[0056] Among them, the public library is used to store public business tables, and the customized library is used to store customized business tables; the data access layer is used to support access to different databases according to tenant identifiers, and the data adaptation layer is used to define the database where each table is located and provide a corresponding API. The service layer accesses the public library and / or the customized library through the data access layer and the data adaptation layer to obtain the business information corresponding to the front-end portal, and performs business processing for the front-end portal based on the obtained business information.
[0057] Specifically, the integrated support platform service accesses the public library and the customized library through the cooperation of the data access layer and the data adaptation layer.
[0058] Optionally, according to business needs, some tables can be migrated from the custom library to the public library. For example, in the early stage, only a certain tenant is required to perform identity verification consistency comparison. Later, this functional process is popularized to multiple tenants and becomes a public process. The corresponding tables are migrated from the custom library to the public library (this is just an example, and it can also be other business functions).
[0059] In some embodiments, the public library is specifically used to store at least one of a public business configuration table, a tenant table, a user table, a menu table, a product definition table, a product listing table, a process definition table, a product ordering process table, an order table, an operation data statistics table, a portal style configuration table, and a portal language configuration table.
[0060] For example, the following table is an example of a public business table:
[0061]
[0062]
[0063] Table 1
[0064] As shown in Table 1, the public library is used to store tables used by all portals, and the customized library is used to store business customized tables unique to each tenant.
[0065] In some embodiments, each business table in the public library isolates data for different front-end portals through a tenant ID.
[0066] Specifically, the difference fields in each business table in the public library are solved by reusing extended fields: that is, for the same extended field, different portal front-ends can define and parse its meaning by themselves. When handling business, the front-end fills in the field by itself, and the corresponding data interface enters the field uniformly; when reading, it is read uniformly by the corresponding data interface, and different portal front-ends parse the field value and its meaning respectively.
[0067] In some embodiments, when the system is running, the data in the public library and / or the data in the custom library are loaded into the cache.
[0068] Specifically, in order to improve data access efficiency, the data in the public library and / or the data in the customized library may be loaded into a cache so as to improve processing efficiency.
[0069] Optionally, since the configuration table changes less and the business table changes more, in order to relieve cache pressure, only the "configuration table" in Table 1 can be added to the cache, and the data of the business table is not placed in the cache.
[0070] In some embodiments, the service layer accesses the public library and / or the custom library through the data access layer and the data adaptation layer, including:
[0071] The data access layer initializes access connections for all libraries and puts them into the connection pool;
[0072] The data adaptation layer determines the target library where the target table is located according to the target table that the service layer needs to access, and then searches the connection pool for the corresponding database connection according to the library name of the target table, so that the service layer accesses the database data based on the database connection.
[0073] Specifically, when the program starts, the data access layer first initializes the access connections of all libraries and puts them into the connection pool. When accessing a specific table, the data adaptation layer first reads the library where the table is located through Table 1, and then finds the corresponding database connection in the connection pool according to the library name to access the database. The public library contains common configuration tables and business tables such as business configuration table, tenant table, user table, menu table, product definition table, product listing table, process definition table, product ordering process table, order table, operation data statistics table, portal style configuration table, portal language configuration table, etc.; the tenant customization library stores the business tables customized by each tenant. In particular, for the same tenant, if the same table is configured as a public library and its own customization library at the same time, it will be stored in the customization library first (that is, customization takes priority). When the program starts, check whether the table configured in Table 1 actually exists. If it is detected that the table corresponding to a certain record does not exist, the system reports an error.
[0074] In some embodiments, each table configured in the public service table (Table 1) can be configured in addition to being configured in the database, or through a configuration file:
[0075] 1. Create 1 public library configuration file and N custom library configuration files (1 configuration file for each operator);
[0076] 2. Configure the table name used by all tenants in the public library configuration file;
[0077] Configure the table name used by the operator in the custom library configuration file. For the same operator, if the same table is configured in both the public library configuration file and its own custom library configuration file, it will be stored in the custom library first. When the program starts, check whether the tables configured in each configuration file actually exist. If it is detected that the table corresponding to a record does not exist, the system reports an error.
[0078] Compared with the prior art, the improvements of the system in this application mainly include:
[0079] 1. Data storage design includes data access layer, data adaptation layer and database. The data access layer is used to support data access requests of services, and the data adaptation layer allows users to define and identify the database where each table is located and provide relevant APIs;
[0080] 2. Under the mainstream mode, all data of different operators will be managed in separate libraries. The present invention adopts the public library + customized library method. The public library stores tables and data shared by all tenants (data is logically isolated by tenant ID), and N customized libraries store N characteristic business tables corresponding to tenants, thereby realizing intensive management of tables and data.
[0081] (1) Configure tables for the public library and tenant customized library in the public business configuration table;
[0082] (2) The public library includes common configuration tables and business tables such as business configuration table, tenant table, user table, menu table, product definition table, product listing table, process definition table, product ordering process table, order table, operation data statistics table, portal style configuration table, portal language configuration table, etc.;
[0083] (3) The tenant customization library stores the business tables customized by each tenant;
[0084] (4) As needed, tenant-customized business tables can be migrated from the customized library to the public library;
[0085] (5) Preferably, loading the public service configuration table into the cache can improve data access efficiency;
[0086] (6) Preferably, the table data of the configuration table type in the public business configuration table is loaded into the cache, which can further improve the data access efficiency;
[0087] (7) Preferably, for the same tenant, if the same table is configured as a public library and a customized library of the tenant at the same time, the table will be stored in the customized library first (i.e., customized library takes precedence);
[0088] (8) Preferably, when the program starts, it is checked whether the table configured in Table 1 actually exists. If it is detected that the table corresponding to a certain record does not exist, the system reports an error.
[0089] 3. The data access layer supports access to different databases based on tenant IDs, including the computing power portal public library and customized libraries for each tenant. By configuring the database where each business table is located in the data access layer, dynamic access to different databases can be achieved in one service.
[0090] (1) Preferably, when the program starts, the data access layer first initializes the access connections of all libraries and puts all accesses into the connection pool;
[0091] (2) Preferably, when accessing a specific table, the data access adapter layer first reads the library where the table is located through Table 1, and then finds the corresponding database connection in the connection pool according to the library name to access the database.
[0092] 4. The general business process provides a general warehousing method. The difference fields in the business tables of each tenant in the public library are solved by reusing extended fields: that is, for the same extended field, different portal front-ends can define and parse its meaning by themselves. When handling business, the front-end fills in the field by itself, and the corresponding data interface enters the data into the library uniformly; when reading, it is read uniformly by the corresponding data interface, and different portal front-ends parse the field value and its meaning respectively.
[0093] Based on the above-mentioned multi-portal system for differential processing of configuration information, the present application provides a method for differential processing of configuration information.
[0094] Figure 3 A schematic diagram of a configuration information differentiation processing method provided in an embodiment of the present application, such as Figure 3 As shown, the method includes:
[0095] S1. Preset a public service table and a customized service table, store the public service table in a public library, and store the customized service table in a customized library;
[0096] S2. Acquire the business information corresponding to the front-end portal by accessing the public library and / or the customized library, and perform business processing for the front-end portal according to the acquired business information.
[0097] In some embodiments, the public library is specifically used to store at least one of a public business configuration table, a tenant table, a user table, a menu table, a product definition table, a product listing table, a process definition table, a product ordering process table, an order table, an operation data statistics table, a portal style configuration table, and a portal language configuration table.
[0098] In some embodiments, each business table in the public library performs data isolation for different front-end portals through tenant IDs.
[0099] In some embodiments, when the system is running, the data in the public library and / or the data in the custom library are loaded into the cache.
[0100] In some embodiments, accessing the public library and / or the custom library includes:
[0101] Initialize access connections for all libraries and put them into the connection pool;
[0102] The target library where the target table is located is determined according to the target table that the service layer needs to access, and then the corresponding database connection is searched in the connection pool according to the library name of the target table, and the database data is accessed based on the database connection.
[0103] It should be understood that, although the various steps in the flowcharts in the above-described embodiments are sequentially displayed according to the indications of the arrows, these steps are not necessarily executed sequentially in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps is not strictly limited in order, and they can be executed in other orders. Moreover, at least a portion of the steps in the figure may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily to be carried out sequentially, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
[0104] To facilitate further understanding of the present application, the main process is described below using the example of a user registering at portal 1 to place a product order (the rest of the business processes are similar). This example is only used to explain the present invention and does not limit the scope of the present invention.
[0105] Figure 4 A schematic diagram of a product ordering process provided in an embodiment of the present application, such as Figure 4 As shown, the process includes:
[0106] 1. User a registers an account user1 on portal 1. The browser carries the tenant 1 identifier and submits the user registration information to the integrated support platform;
[0107] 2. The integrated platform queries the public library business configuration table and finds that the database where the user table is located is the public library. The data is recorded in the user information table, and the tenant ID is recorded as the tenant 1 identifier. The extended field 1 defaults to no (the extended field 1 is used as the real-name authentication identifier for tenant 1. After the real-name authentication, it will be updated to yes. The authentication information must be queried in the tenant 1 custom library. Other tenants can define the meaning and usage of this field according to actual needs).
[0108] For example, the following table is an example of a user information table:
[0109]
[0110]
[0111] Table 2
[0112] 3. User a opens the product zone page through account user1, and portal 1 queries the integrated support platform for a list of products that are available on this portal and all tenants;
[0113] 4. The integrated support platform reads the product whose tenant ID is tenant 1 from the product listing table of the public library, and then returns it to portal 1 for display in the product area;
[0114] 5. User A selects Product 1 to order, and Portal 1 submits the order to the integrated support platform;
[0115] 6. The integrated support platform records the order information and returns the order ID and order success message to portal 1;
[0116] 7. The integrated support platform background process calls the order service process.
[0117] Figure 5 A schematic diagram of the order service process provided in the embodiment of the present application, such as Figure 5 As shown, the process includes:
[0118] (1) Process step 1: According to the tenant 1 ID, perform the business verification of this business, including public verification and customized verification. For example: Tenant 1 requires users to do real-name authentication before ordering products, and the identity card must be consistent, but other tenants do not have this requirement. Therefore, in the customized verification, execute: perform real-name authentication verification on the user. If the user has not performed real-name authentication, return failure and require real-name authentication; otherwise, jump to step (4) to perform the general ordering process;
[0119] (2) Real-name authentication: Users perform real-name authentication, upload ID photos, take face photos, and send the collected ID photos and face photos to the integrated support platform for comparison. After the integrated platform completes the comparison:
[0120] a. Through the public library business configuration table, it is known that the certificate information table and the person-certificate comparison result table are in the tenant 1 custom library;
[0121] b. Upload the ID photo and face photo to the file server through the data access layer;
[0122] c. Then record the user ID, user name, certificate type and corresponding file identifier in the certificate information table of the customized library of tenant 1, and record the authentication comparison result in the person-certificate comparison result table of the customized library;
[0123] d. Update the extension field 1 of the public library user table (this field is used as a real-name authentication identifier for tenant 1) to yes.
[0124] (3) The user reorders Product 1 and the process returns to step (1);
[0125] (4) Process step 2: Create order information;
[0126] (5) Process step 3: Process the user's payment. Different tenants can choose different payment methods. Different users can choose from the payment methods supported by the tenants. The tenant configuration is read and matched with the user's selection in the conditional expression (for example, some tenants support deducting user's mobile phone bills or points through operators, and some tenants support bank deductions, and the user has selected one of these payment methods). When executing here, several mutually exclusive expressions Expression1 / Expression2 / Expression3 in step 3 of Table 2 are substituted into the tenant ID one by one for calculation. If one of the expressions is satisfied, one of the methods in paymentA / paymentB / paymentC is executed to deduct the corresponding fee, and then the process step 4 is continued;
[0127] Optional, this step verifies that paymentA / paymentB / paymentC must be executed and only one can be executed.
[0128] (6) Process step 4: Calculate the expression Expression4 in step 4 of Table 2. If the condition is met, call sycPlatformA to synchronize the order relationship to platform A;
[0129] (7) Process step 5: Calculate the expression Expression5 in step 5 of Table 2. If the condition is met, call sycPlatformB to synchronize the order relationship to platform B;
[0130] (8) Process step 6: Calculate the expression Expression6 of step 4 in Table 2. If the condition is met, call sycPlatformC to synchronize the order relationship to platform C;
[0131] (9) Execute updateOrder to update the order status.
[0132] It can be understood that the application examples mentioned in the present invention are merely examples and can be flexibly adjusted during actual implementation.
[0133] The system architecture and method provided by this application can achieve the following beneficial effects:
[0134] 1. Through the public library + customized library method, a support platform is implemented to serve different operators on the basis of unified business processes, and intensive data storage of different front-end portal operation and configuration data is realized;
[0135] 2. The data of customized business is stored in the customized library. The general business process provides a general warehousing method. The different fields of different operators are solved by reusing extended fields, and each business party organizes the warehousing and parsing by itself.
[0136] It is to be understood that the above embodiments are merely exemplary embodiments used to illustrate the principles of the present application, but the present application is not limited thereto. For those skilled in the art, various modifications and improvements can be made without departing from the spirit and substance of the present application, and these modifications and improvements are also considered to be within the scope of protection of the present application.
Claims
1. A multi-portal system for differential processing of configuration information, characterized in that: The system includes: N front-end portals, an integrated support platform, a resource scheduling and activation platform, and M peripheral business platforms, where M and N are both positive integers; The integrated support platform includes a service layer, a data access layer, a data adaptation layer and a database, wherein the database includes a common library corresponding to all front-end portals and a customized library corresponding to each front-end portal; The public library is used to store public service tables, and the customized library is used to store customized service tables; The data access layer is used to support access to different databases based on tenant identifiers, the data adaptation layer is used to define the databases where each table is located and provide corresponding APIs, and the service layer accesses the public library and / or the customized library through the data access layer and the data adaptation layer to obtain business information corresponding to the front-end portal, and performs business processing for the front-end portal based on the obtained business information.
2. The multi-portal system for differential processing of configuration information according to claim 1, characterized in that: The public library is specifically used to store at least one of a public business configuration table, a tenant table, a user table, a menu table, a product definition table, a product listing table, a process definition table, a product ordering process table, an order table, an operation data statistics table, a portal style configuration table, and a portal language configuration table.
3. The multi-portal system for differential processing of configuration information according to claim 2, characterized in that: Each business table in the public library performs data isolation for different front-end portals through tenant IDs.
4. The multi-portal system for differential processing of configuration information according to claim 1, characterized in that: When the system is running, the data in the public library and / or the data in the customized library are loaded into the cache.
5. The multi-portal system for differential processing of configuration information according to claim 4, characterized in that: The service layer accesses the public library and / or the custom library through the data access layer and the data adaptation layer, including: The data access layer initializes access connections for all libraries and puts them into the connection pool; The data adaptation layer determines the target library where the target table is located according to the target table that the service layer needs to access, and then searches the connection pool for the corresponding database connection according to the library name of the target table, so that the service layer accesses the database data based on the database connection.
6. A configuration information differentiation processing method, applied to the multi-portal system according to any one of claims 1 to 5, characterized in that: The method comprises: Preset a public service table and a customized service table, store the public service table in a public library, and store the customized service table in a customized library; The business information corresponding to the front-end portal is obtained by accessing the public library and / or the customized library, and business processing is performed for the front-end portal according to the obtained business information.
7. The configuration information differentiation processing method according to claim 6, characterized in that: The public library is specifically used to store at least one of a public business configuration table, a tenant table, a user table, a menu table, a product definition table, a product listing table, a process definition table, a product ordering process table, an order table, an operation data statistics table, a portal style configuration table, and a portal language configuration table.
8. The configuration information differentiation processing method according to claim 6, characterized in that: Each business table in the public library performs data isolation for different front-end portals through tenant IDs.
9. The configuration information differentiation processing method according to claim 6, characterized in that: When the system is running, the data in the public library and / or the data in the customized library are loaded into the cache.
10. The configuration information differentiation processing method according to claim 9, characterized in that: Accessing the public library and / or the custom library includes: Initialize access connections for all libraries and put them into the connection pool; The target library where the target table is located is determined according to the target table that the service layer needs to access, and then the corresponding database connection is searched in the connection pool according to the library name of the target table, and the database data is accessed based on the database connection.