CN112667415B - Data calling method and device, readable storage medium and electronic equipment - Google Patents
Data calling method and device, readable storage medium and electronic equipment Download PDFInfo
- Publication number
- CN112667415B CN112667415B CN202011552890.9A CN202011552890A CN112667415B CN 112667415 B CN112667415 B CN 112667415B CN 202011552890 A CN202011552890 A CN 202011552890A CN 112667415 B CN112667415 B CN 112667415B
- Authority
- CN
- China
- Prior art keywords
- attribute information
- entity
- data
- virtual object
- virtual
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 40
- 238000013507 mapping Methods 0.000 claims abstract description 55
- 238000004590 computer program Methods 0.000 claims description 11
- 238000012545 processing Methods 0.000 claims description 8
- 238000010276 construction Methods 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 abstract description 3
- 238000004891 communication Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 8
- 230000007246 mechanism Effects 0.000 description 7
- 238000011161 development Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 5
- 230000008901 benefit Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 210000001503 joint Anatomy 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000003032 molecular docking Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Landscapes
- Stored Programmes (AREA)
Abstract
A data calling method, a device, a readable storage medium and an electronic device, wherein the data calling method comprises the following steps: acquiring an entity object engineering package of a user system imported by a user, and extracting attribute information of each entity in the entity object engineering package; determining virtual objects corresponding to the entity objects in the predefined multiple virtual objects one by one according to the attribute information of the entity objects; constructing an attribute information mapping configuration file according to the determined corresponding relation between each entity object and each virtual object; invoking data of each entity object in the user system through each predefined object operation interface; and mapping the data of each called entity object into the corresponding data of the virtual object according to the attribute information mapping configuration file. The application greatly reduces the workload of application system software developers, reduces the risk of developing unnecessary functional modules, and reduces the maintenance cost of client information.
Description
Technical Field
The present application relates to the field of electronic technologies, and in particular, to a data calling method and apparatus, a readable storage medium, and an electronic device.
Background
With the development of communication technology, more and more enterprises and units realize user management through a user management system. The user management system generally relates to application system software under a plurality of architectures, and user data among application systems usually need to be called mutually, for example, the A system needs to synchronously call and read heterogeneous B system user management related data.
At present, the user data of application system software is mostly called by a set of complete user management function modules built in, and then the user data is initialized by methods such as manual input or batch import when the system is deployed, and the method mainly has the following defects:
the application system software developer needs to additionally develop a whole set of user management function modules, so that project investment is increased, and unnecessary troubles and the like are brought due to the fact that the developed user management function modules are too simple or complex and are not approved by clients;
the customer units often have user management systems with unified standards, only corresponding business application function modules are needed to be purchased, but a user management function module additionally added is required to buy the list, and a new set of user data is required to be maintained directly or indirectly repeatedly, so that the use workload of the customer side is increased, and the rejection of the customer is improved;
if the client is forced to use the unified user management system, the application system developer needs to modify the code logic of the local user management module or modify the related logic of the service application call user data, so that the implementation workload is greatly increased, and the stability, the robustness, the expansibility and the like of the application system software are influenced.
Disclosure of Invention
In view of the foregoing, it is necessary to provide a data calling method, apparatus, readable storage medium and electronic device, which address the problems of high cost and large workload of calling user data by an application system in the prior art.
A data calling method, comprising:
acquiring an entity object engineering package of a user system imported by a user, and extracting attribute information of each entity in the entity object engineering package;
inquiring virtual objects corresponding to the entity objects one by one in a plurality of predefined virtual objects according to the attribute information of the entity objects;
constructing an attribute information mapping configuration file according to the determined corresponding relation between each entity object and each virtual object;
invoking data of each entity object in the user system through each predefined object operation interface;
and mapping the data of each called entity object into the corresponding data of the virtual object according to the attribute information mapping configuration file.
Further, in the above data calling method, the step of determining, according to attribute information of each entity object, a virtual object corresponding to each entity object in a predefined plurality of virtual objects one by one includes:
acquiring a keyword library corresponding to each predefined virtual object;
extracting keywords in the attribute information of each entity object, and matching the keywords with keyword libraries corresponding to each virtual object;
and when the extracted attribute information of the current entity object is successfully matched with the keyword library corresponding to the target virtual object, determining that the target virtual object is the virtual object corresponding to the current entity object.
Further, in the above data calling method, the step of extracting keywords in the attribute information of each entity object and matching the keywords corresponding to each virtual object includes:
when the current entity object is not matched with the corresponding virtual object, sending out prompt information to prompt a user to set the attribute information of a standby virtual object as the attribute information of the current entity object;
and when the attribute information of the standby virtual object is detected to be the attribute information of the current entity object, determining that the standby virtual object is the virtual object corresponding to the current entity object.
Further, in the above data calling method, the step of constructing an attribute information mapping configuration file according to the determined correspondence between each entity object and each virtual object includes:
acquiring an attribute information mapping configuration file template;
and acquiring attribute information of the virtual object corresponding to each entity object, and writing the attribute information of each entity object and the attribute information of the corresponding virtual object into the mapping configuration file template to obtain an attribute information mapping configuration file.
Further, the step of calling the data of each entity object in the user system through the predefined operation interfaces of each object includes:
the user management module is connected with the user system through the ESB service bus;
and calling the data of the entity object of the user system for each predefined object operation interface according to the service opened by the user management module of the user system.
The technical scheme of the application also provides a data calling device, which comprises:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring an entity object engineering package of a user system imported by a user and extracting attribute information of each entity in the entity object engineering package;
the determining module is used for inquiring virtual objects corresponding to the entity objects one by one in a plurality of predefined virtual objects according to the attribute information of the entity objects;
the construction module is used for constructing an attribute information mapping configuration file according to the determined corresponding relation between each entity object and each virtual object;
the calling module is used for calling the data of each entity object in the user system through each predefined object operation interface;
and the mapping module is used for mapping the data of each called entity object into the corresponding data of the virtual object according to the attribute information mapping configuration file.
Further, in the above data calling device, the step of determining, according to attribute information of each entity object, a virtual object corresponding to each entity object in a predefined plurality of virtual objects one by one includes:
acquiring a keyword library corresponding to each predefined virtual object;
extracting keywords in the attribute information of each entity object, and matching the keywords with keyword libraries corresponding to each virtual object;
and when the extracted attribute information of the current entity object is successfully matched with the keyword library corresponding to the target virtual object, determining that the target virtual object is the virtual object corresponding to the current entity object.
Further, the data calling device further includes:
the prompting module is used for sending out prompting information when the current entity object is not matched with the corresponding virtual object so as to prompt a user to set the attribute information of a standby virtual object as the attribute information of the current entity object;
the determining module is further configured to determine that the standby virtual object is a virtual object corresponding to the current entity object when the attribute information of the standby virtual object is detected to be the attribute information of the current entity object.
The technical scheme of the application also provides a readable storage medium, on which a computer program is stored, the program when being executed by a processor realizes the data calling method of any one of the above.
The technical scheme of the application also provides electronic equipment, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor realizes the data calling method of any one of the above when executing the computer program.
By constructing the standard extensible virtual object, the attribute information mapping configuration file and the object operation interface, the application ensures that the user data call of the application system software can be extended across applications and according to requirements, realizes free switching, keeps the stability and the robustness of the application system software and the like. The method not only saves the workload of application system software developers and reduces the risk of developing unnecessary functional modules, but also reduces the maintenance cost of clients, so that the clients are focused on the development of functional business.
Drawings
FIG. 1 is a flow chart of a data calling method in a first embodiment of the application;
FIG. 2 is a flow chart of a data calling method in a first embodiment of the application;
FIG. 3 is a block diagram showing a data calling device according to a third embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The present application will be described and illustrated with reference to the accompanying drawings and examples in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application. All other embodiments, which can be made by a person of ordinary skill in the art based on the embodiments provided by the present application without making any inventive effort, are intended to fall within the scope of the present application.
It is apparent that the drawings in the following description are only some examples or embodiments of the present application, and it is possible for those of ordinary skill in the art to apply the present application to other similar situations according to these drawings without inventive effort. Moreover, it should be appreciated that while such a development effort might be complex and lengthy, it would nevertheless be a routine undertaking of design, fabrication, or manufacture for those of ordinary skill having the benefit of this disclosure, and thus should not be construed as having the benefit of this disclosure.
Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the application. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is to be expressly and implicitly understood by those of ordinary skill in the art that the described embodiments of the application can be combined with other embodiments without conflict.
Unless defined otherwise, technical or scientific terms used herein should be given the ordinary meaning as understood by one of ordinary skill in the art to which this application belongs. The terms "a," "an," "the," and similar referents in the context of the application are not to be construed as limiting the quantity, but rather as singular or plural. The terms "comprising," "including," "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, article, or apparatus that comprises a list of steps or modules (elements) is not limited to only those steps or elements but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. The terms "connected," "coupled," and the like in connection with the present application are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The term "plurality" as used herein means two or more. "and/or" describes an association relationship of an association object, meaning that there may be three relationships, e.g., "a and/or B" may mean: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship. The terms "first," "second," "third," and the like, as used herein, are merely distinguishing between similar objects and not representing a particular ordering of objects.
Some embodiments of the present application are described in detail below with reference to the accompanying drawings. The following embodiments and features of the embodiments may be combined with each other without conflict.
Referring to fig. 1, a data calling method according to a first embodiment of the present application includes steps S11 to S15.
Step S11, obtaining an entity object engineering package of a user system imported by a user, and extracting attribute information of each entity in the entity object engineering package.
The data calling method in the embodiment is applied to electronic equipment, such as computer equipment, and is used for synchronizing and calling user data of other user systems to an application system of the electronic equipment. The user data is, for example, user data of users, institutions, posts, roles, rights, resources, and the like.
The respective entity objects are, for example, user ID information, user name information, real name information, password information, organization information set, post information set, default organization post information, character information set, type information, whether enable information, employee number information, mailbox information, telephone information, and the like in the user system. The attribute information of the implementation object is the attribute name of each data, such as "user ID", "user name", etc.
In the implementation, a user entity object set engineering package of the butt joint user system B is introduced into an application system A of the electronic equipment, wherein the user entity object set engineering package contains attribute information of all entity objects of the user system B. The subscriber management module of subscriber system B may be exposed to a by way of an ESB service bus or the like.
And step S12, inquiring virtual objects corresponding to the entity objects one by one in a plurality of predefined virtual objects according to the attribute information of the entity objects.
And S13, constructing an attribute information mapping configuration file according to the determined corresponding relation between each entity object and each virtual object.
A set of standard virtual objects are predefined in an application system of the electronic equipment, wherein the virtual objects are objects which are convenient for local program logic processing and do not have an actual database table corresponding to the virtual objects.
In specific operation, standard general user virtual objects can be defined for various user management functions, and the attribute information set of the defined virtual objects should cover various use fields Jing Xuqiu, and user data such as users, institutions, posts, roles, authorities, resources and the like operate related virtual objects. In addition, some custom attribute information or some standby attribute information can be predefined, so that the post-flexible application and expansion are facilitated. For example: the user virtual object attribute information defined in the application system software a includes: user ID, user name, real name, password, set of authorities, set of posts, default set of authorities, set of roles, type, whether enabled, employee number, mailbox, phone, cell phone, custom attribute information set, spare field one, spare field two, spare field three, etc.
And determining each corresponding virtual attribute information object according to the acquired attribute information of each entity object. For example, the virtual object identical to the attribute information of each entity object can be queried according to the attribute information of each entity object, and the virtual object is determined as the corresponding virtual object.
And establishing an attribute information mapping configuration file according to the corresponding relation between each entity object and each virtual object. And mapping and configuring the attribute information of the user virtual object and the entity object one by one through an object mapping tool. The attribute information mapping configuration file is, for example, an xml format file, maps and configures the attribute information of the virtual object defined above with the attribute information of the entity object to be docked, and no attribute information field can be left blank or annotated. Other virtual objects such as organizations, posts, roles, permissions, resources, etc. may be defined and mapped with reference to the user virtual object.
In this embodiment, the standard user virtual object and attribute information mapping is constructed, so that the application system software does not need to pay attention to other user systems or user management modules of other systems which need to be docked in the future, but only needs to program the virtual object in a concentrated manner.
Step S14, the data of each entity object in the user system is called through each predefined object operation interface.
The application system is pre-defined with object operation interfaces corresponding to the virtual objects one by one, and the defined object operation interfaces should cover various common and reasonable user data operations. The interface of the object operation defined in the application system a includes, for example: the method comprises the steps of obtaining current login user information, obtaining user information according to user IDs, obtaining user information sets according to user IDs, obtaining mechanism information sets of users, obtaining post information sets of users, obtaining module resource information sets of users, obtaining role information sets of users, obtaining default mechanism post information of users, obtaining mechanism information according to mechanism IDs, obtaining all sub-mechanism information sets, obtaining all user information sets under a mechanism, obtaining mechanism information sets according to mechanism IDs and the like.
A standard set of object operation interfaces is defined, and universal operation can be extracted for each virtual object and corresponding operation interfaces are defined, and the defined set of object operation interfaces should cover the user data operation requirements of various application scenes as much as possible and be easy to expand.
After defining the user data operation interface, a user data operation tool class can be built again, and all possible operations required or involved by a user management system are packaged or processed by programming the defined user data operation interface so as to facilitate the local service logic call of the application system software.
By predefining a set of standard object operation interfaces and corresponding operation tool classes, the application system software only needs to pay attention to the locally defined user data operation interfaces and program the interface or tool class-oriented method in the development period, and does not need to pay attention to other user systems or user management modules of other systems to be docked later, so that the development efficiency of the application core attention function can be greatly improved.
And step S15, mapping the data of each called entity object into the corresponding data of the virtual object according to the attribute information mapping configuration file.
And calling the services of the user system to realize one-to-one according to the defined object operation interface. And mapping and converting the data of the entity object returned by the remote user data calling operation into the data of the user virtual object defined locally through an object mapping tool. For interface implementation of non-homologous technology architecture, other third party docking libraries may be employed.
In this embodiment, a plurality of virtual objects are preset in an application system, and each virtual object is determined to match according to attribute information of each entity object of a user system, so as to determine a virtual object corresponding to each entity object one by one, and an attribute information mapping configuration file is constructed according to a correspondence between the entity object and the virtual object. And the object operation interface set is realized one by one according to the service opened by the service system, and the user entity object data returned by the user is mapped into the data of the virtual object predefined by the application system.
According to the embodiment, by constructing the standard extensible virtual object, the attribute information mapping configuration file and the object operation interface, the user data call of the application system software can be extended across applications and according to requirements, free switching is realized, the stability and the robustness of the application system software are maintained, and the like. The method not only saves the workload of application system software developers and reduces the risk of developing unnecessary functional modules, but also reduces the maintenance cost of clients, so that the clients are focused on the development of functional business.
Referring to fig. 2, a data calling method according to a second embodiment of the present application includes steps S21 to S29.
Step S21, obtaining a keyword library corresponding to each predefined virtual object, obtaining an entity object engineering package of a user system imported by a user, and extracting attribute information of each entity in the entity object engineering package.
Attribute information of each entity object in the user system includes, but is not limited to, attribute information of user data such as users, institutions, posts, roles, rights, resources, and the like.
And S22, extracting keywords in the attribute information of each entity object, and matching the keywords with keyword libraries corresponding to each virtual object.
Step S23, when the extracted attribute information of the current entity object is successfully matched with the keyword library corresponding to the target virtual object, determining that the target virtual object is the virtual object corresponding to the current entity object.
The definition of the attribute information of the real object is different in different user systems, for example, the application system a needs to acquire the user identity information in the B user system and the C user system, wherein the attribute information corresponding to the user identity information in the B user system is "user ID", and the attribute information corresponding to the user identity information in the C system is "user account". Accordingly, corresponding keyword libraries are respectively provided for each predefined virtual object in the application system a. Virtual objects corresponding to the entity objects one by one can be determined through a keyword matching algorithm.
Step S24, when the current entity object is not matched with the corresponding virtual object, a prompt message is sent out to prompt the user to set the attribute information of a standby virtual object as the attribute information of the current entity object.
Step S25, when it is detected that the attribute information of the spare virtual object is the attribute information of the current entity object, determining that the spare virtual object is a virtual object corresponding to the current entity object.
If the current entity object is not matched with the corresponding virtual object according to the keyword matching algorithm, a prompt message is sent. The prompt information is, for example, to pop up a prompt window on the display interface to prompt the user to set the attribute information of a standby virtual object as the attribute information of the current entity object. The application system is provided with a plurality of standby virtual objects, and after the user can set the attribute information of one standby virtual object as the attribute information of the current entity object, the application system determines that the standby virtual object corresponds to the current entity object when detecting that the attribute information of the standby virtual object is the attribute information of the current entity object.
In this embodiment, the predefined virtual object, object attribute mapping, and user data operation interface and implementation may be conveniently extended according to the requirements, so as to quickly respond to and implement expansion and adjustment of the user management related functions, and truly implement cross-application and extensible user data call. If an object attribute needs to be added, a new attribute needs to be defined only by adding a standby virtual object in the application system.
Step S26, obtaining an attribute information mapping configuration file template and obtaining attribute information of a virtual object corresponding to each entity object.
And step S27, writing the attribute information of each entity object and the attribute information of the corresponding virtual object into the mapping configuration file template to obtain an attribute information mapping configuration file.
The attribute information mapping configuration file template comprises a plurality of mapping files, and each mapping file comprises an attribute information filling area of a virtual object and an attribute information filling area of a physical object. And filling the attribute information of each entity object and the attribute information of the corresponding virtual object into the corresponding area according to the determined one-to-one correspondence between each entity object and each virtual object.
It can be understood that the number of mapping files set in the attribute information mapping configuration file template meets the number requirement of actual entity objects of each user system as much as possible.
Further, in the embodiment of the present application, the attribute information of each virtual object may be pre-filled into the corresponding area in each mapping file, and after determining the corresponding relationship between each entity object and the virtual object, the attribute information of each entity object is filled into the corresponding area.
Step S28, the data of each entity object in the user system is called through each predefined object operation interface.
And step S29, mapping the data of each called entity object into the corresponding data of the virtual object according to the attribute information mapping configuration file.
For example, by exposing the user management module services of user system B to application system a via an ESB service bus or the like. The application system A constructs an object attribute information mapping file according to the corresponding relation between the entity object and the virtual object so as to match the accessed entity object attribute, then implements the object operation interface set one by one according to the service opened by the user system B, and maps the user entity object data returned by the user system B into defined user virtual object data.
Furthermore, during the use of the application system, if the other user systems or the user management modules of the other systems need to be switched to be docked, only the user systems need to be docked again according to the method. For example: in the use of the system, if the docked user system B is required to be switched to the user system C, only the entity object set engineering package of the user system C is required to be reintroduced into the application system A, the user object attribute mapping file is remapped, and the defined standard user data operation interface is realized again through the service opened by the user system C. These operations do not affect the application system component a and the subject business logic of the interfacing user systems B or C, etc.
Referring to fig. 3, a data calling device according to a third embodiment of the present application includes:
an obtaining module 31, configured to obtain attribute information of each entity object of the user system;
a determining module 32, configured to determine virtual objects corresponding to the entity objects in a predefined plurality of virtual objects according to attribute information of the entity objects;
a construction module 33, configured to construct an attribute information mapping configuration file according to the determined correspondence between each of the entity objects and each of the virtual objects;
a retrieving module 34, configured to retrieve data of each entity object in the user system through predefined operation interfaces of each object;
and the mapping module 35 is configured to map the data of each invoked entity object into the corresponding data of the virtual object according to the attribute information mapping configuration file.
Further, in the above data calling device, the step of determining, according to attribute information of each entity object, a virtual object corresponding to each entity object in a predefined plurality of virtual objects one by one includes:
acquiring a keyword library corresponding to each predefined virtual object;
extracting keywords in the attribute information of each entity object, and matching the keywords with keyword libraries corresponding to each virtual object;
and when the extracted attribute information of the current entity object is successfully matched with the keyword library corresponding to the target virtual object, determining that the target virtual object is the virtual object corresponding to the current entity object.
Further, the data calling device further includes:
the prompting module is used for sending out prompting information when the current entity object is not matched with the corresponding virtual object so as to prompt a user to set the attribute information of a standby virtual object as the attribute information of the current entity object;
the determining module is further configured to determine that the standby virtual object is a virtual object corresponding to the current entity object when the attribute information of the standby virtual object is detected to be the attribute information of the current entity object.
The above-described respective modules may be functional modules or program modules, and may be implemented by software or hardware. For modules implemented in hardware, the various modules described above may be located in the same processor; or the above modules may be located in different processors in any combination.
The data calling device provided by the embodiment of the application has the same implementation principle and technical effects as those of the embodiment of the method, and for the sake of brevity, reference may be made to the corresponding contents of the embodiment of the method.
In addition, the data calling method of the embodiment of the present application described in connection with fig. 1 may be implemented by an electronic device, which may be a server. Fig. 4 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present application.
The electronic device may comprise a processor 11 and a memory 12 storing computer program instructions.
In particular, the processor 11 may comprise a Central Processing Unit (CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, abbreviated as ASIC), or may be configured as one or more integrated circuits that implement embodiments of the present application.
Memory 12 may include, among other things, mass storage for data or instructions. By way of example, and not limitation, memory 12 may comprise a Hard Disk Drive (HDD), floppy Disk Drive, solid state Drive (Solid State Drive, SSD), flash memory, optical Disk, magneto-optical Disk, tape, or universal serial bus (Universal Serial Bus, USB) Drive, or a combination of two or more of the foregoing. The memory 12 may include removable or non-removable (or fixed) media, where appropriate. The memory 12 may be internal or external to the data processing apparatus, where appropriate. In a particular embodiment, the memory 12 is a Non-Volatile (Non-Volatile) memory. In particular embodiments, memory 12 includes Read-Only Memory (ROM) and random access Memory (Random Access Memory, RAM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable ROM (Programmable Read-Only Memory, abbreviated PROM), an erasable PROM (Erasable Programmable Read-Only Memory, abbreviated EPROM), an electrically erasable PROM (Electrically Erasable Programmable Read-Only Memory, abbreviated EEPROM), an electrically rewritable ROM (Electrically Alterable Read-Only Memory, abbreviated EAROM), or a FLASH Memory (FLASH), or a combination of two or more of these. The RAM may be Static Random-Access Memory (SRAM) or dynamic Random-Access Memory (Dynamic Random Access Memory DRAM), where the DRAM may be a fast page mode dynamic Random-Access Memory (Fast Page Mode Dynamic Random Access Memory FPMDRAM), extended data output dynamic Random-Access Memory (Extended Date Out Dynamic Random Access Memory EDODRAM), synchronous dynamic Random-Access Memory (Synchronous Dynamic Random-Access Memory SDRAM), or the like, as appropriate.
Memory 12 may be used to store or cache various data files that need to be processed and/or communicated, as well as possible computer program instructions for execution by processor 11.
The processor 11 implements any of the data calling methods of the above embodiments by reading and executing computer program instructions stored in the memory 12.
In some of these embodiments, the electronic device may also include a communication interface 13 and a bus 10. As shown in fig. 4, the processor 11, the memory 12, and the communication interface 13 are connected via the bus 10 and communicate with each other.
The communication interface 13 is used to implement communications between modules, devices, units and/or units in embodiments of the application. The communication interface 13 may also enable communication with other components such as: and the external equipment, the image/data acquisition equipment, the database, the external storage, the image/data processing workstation and the like are used for data communication.
Bus 10 includes hardware, software, or both, that couple components of an electronic device to each other. Bus 10 includes, but is not limited to, at least one of: data Bus (Data Bus), address Bus (Address Bus), control Bus (Control Bus), expansion Bus (Expansion Bus), local Bus (Local Bus). By way of example, and not limitation, bus 10 may include a graphics acceleration interface (Accelerated Graphics Port), abbreviated AGP, or other graphics Bus, an enhanced industry standard architecture (Extended Industry Standard Architecture, abbreviated EISA) Bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an industry standard architecture (Industry Standard Architecture, ISA) Bus, a wireless bandwidth (InfiniBand) interconnect, a Low Pin Count (LPC) Bus, a memory Bus, a micro channel architecture (Micro Channel Architecture, abbreviated MCa) Bus, a peripheral component interconnect (Peripheral Component Interconnect, abbreviated PCI) Bus, a PCI-Express (PCI-X) Bus, a serial advanced technology attachment (Serial Advanced Technology Attachment, abbreviated SATA) Bus, a video electronics standards association local (Video Electronics Standards Association Local Bus, abbreviated VLB) Bus, or other suitable Bus, or a combination of two or more of the foregoing. Bus 10 may include one or more buses, where appropriate. Although embodiments of the application have been described and illustrated with respect to a particular bus, the application contemplates any suitable bus or interconnect.
In addition, in combination with the data calling method in the above embodiment, the embodiment of the application may be implemented by providing a computer readable storage medium. The computer readable storage medium has stored thereon computer program instructions; the computer program instructions, when executed by a processor, implement any of the data calling methods of the above embodiments.
The technical features of the above-described embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above-described embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples illustrate only a few embodiments of the application, which are described in detail and are not to be construed as limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of protection of the present application is to be determined by the appended claims.
Claims (8)
1. A data calling method, comprising:
acquiring an entity object engineering package of a user system imported by a user, and extracting attribute information of each entity in the entity object engineering package;
inquiring virtual objects corresponding to the entity objects one by one in a plurality of predefined virtual objects according to the attribute information of the entity objects;
constructing an attribute information mapping configuration file according to the determined corresponding relation between each entity object and each virtual object;
invoking data of each entity object in the user system through each predefined object operation interface;
mapping the data of each called entity object into the corresponding data of the virtual object according to the attribute information mapping configuration file;
the step of determining the virtual object corresponding to each entity object in the predefined plurality of virtual objects according to the attribute information of each entity object comprises the following steps:
acquiring a keyword library corresponding to each predefined virtual object;
extracting keywords in the attribute information of each entity object, and matching the keywords with keyword libraries corresponding to each virtual object;
and when the extracted attribute information of the current entity object is successfully matched with the keyword library corresponding to the target virtual object, determining that the target virtual object is the virtual object corresponding to the current entity object.
2. The data calling method as claimed in claim 1, wherein the step of extracting keywords in the attribute information of each of the entity objects and matching the keyword library corresponding to each of the virtual objects comprises:
when the current entity object is not matched with the corresponding virtual object, sending out prompt information to prompt a user to set the attribute information of a standby virtual object as the attribute information of the current entity object;
and when the attribute information of the standby virtual object is detected to be the attribute information of the current entity object, determining that the standby virtual object is the virtual object corresponding to the current entity object.
3. The data calling method of claim 1, wherein the constructing of the attribute information mapping profile according to the determined correspondence between each of the physical objects and each of the virtual objects comprises:
acquiring an attribute information mapping configuration file template;
and acquiring attribute information of the virtual object corresponding to each entity object, and writing the attribute information of each entity object and the attribute information of the corresponding virtual object into the mapping configuration file template to obtain an attribute information mapping configuration file.
4. The data calling method of claim 1, wherein the step of calling data of each entity object in the user system through a predefined each object operation interface comprises:
the user management module is connected with the user system through the ESB service bus;
and calling the data of the entity object of the user system for each predefined object operation interface according to the service opened by the user management module of the user system.
5. A data recall device, comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring an entity object engineering package of a user system imported by a user and extracting attribute information of each entity in the entity object engineering package;
the determining module is used for inquiring virtual objects corresponding to the entity objects one by one in a plurality of predefined virtual objects according to the attribute information of the entity objects;
the construction module is used for constructing an attribute information mapping configuration file according to the determined corresponding relation between each entity object and each virtual object;
the calling module is used for calling the data of each entity object in the user system through each predefined object operation interface;
the mapping module is used for mapping the data of each called entity object into the corresponding data of the virtual object according to the attribute information mapping configuration file;
the step of determining the virtual object corresponding to each entity object in the predefined plurality of virtual objects according to the attribute information of each entity object comprises the following steps:
acquiring a keyword library corresponding to each predefined virtual object;
extracting keywords in the attribute information of each entity object, and matching the keywords with keyword libraries corresponding to each virtual object;
and when the extracted attribute information of the current entity object is successfully matched with the keyword library corresponding to the target virtual object, determining that the target virtual object is the virtual object corresponding to the current entity object.
6. The data recall device of claim 5 further comprising:
the prompting module is used for sending out prompting information when the current entity object is not matched with the corresponding virtual object so as to prompt a user to set the attribute information of a standby virtual object as the attribute information of the current entity object;
the determining module is further configured to determine that the standby virtual object is a virtual object corresponding to the current entity object when the attribute information of the standby virtual object is detected to be the attribute information of the current entity object.
7. A readable storage medium having stored thereon a computer program, which when executed by a processor implements a data invoking method as claimed in any of claims 1 to 4.
8. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the data recall method of any one of claims 1 to 4 when the computer program is executed by the processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011552890.9A CN112667415B (en) | 2020-12-24 | 2020-12-24 | Data calling method and device, readable storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011552890.9A CN112667415B (en) | 2020-12-24 | 2020-12-24 | Data calling method and device, readable storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112667415A CN112667415A (en) | 2021-04-16 |
| CN112667415B true CN112667415B (en) | 2023-11-24 |
Family
ID=75408541
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011552890.9A Active CN112667415B (en) | 2020-12-24 | 2020-12-24 | Data calling method and device, readable storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112667415B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113327119B (en) * | 2021-06-25 | 2023-04-18 | 青岛森麒麟轮胎股份有限公司 | Virtual material coding method and system, electronic equipment and storage medium |
| CN114090525A (en) * | 2021-09-18 | 2022-02-25 | 统信软件技术有限公司 | File attribute adding method, computing device and storage medium |
| CN115617819B (en) * | 2022-12-19 | 2023-03-14 | 思创数码科技股份有限公司 | Data storage method, system, computer device and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102611705A (en) * | 2012-03-20 | 2012-07-25 | 广东电子工业研究院有限公司 | General calculation account management system and realization method thereof |
| CN104732310A (en) * | 2013-12-23 | 2015-06-24 | 北京索为高科***技术有限公司 | Data integration method based on unified data model |
| CN109840254A (en) * | 2018-12-14 | 2019-06-04 | 湖南亚信软件有限公司 | A kind of data virtualization and querying method, device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190334778A1 (en) * | 2016-11-30 | 2019-10-31 | Nutanix, Inc. | Generic access to heterogeneous virtualized entities |
-
2020
- 2020-12-24 CN CN202011552890.9A patent/CN112667415B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102611705A (en) * | 2012-03-20 | 2012-07-25 | 广东电子工业研究院有限公司 | General calculation account management system and realization method thereof |
| CN104732310A (en) * | 2013-12-23 | 2015-06-24 | 北京索为高科***技术有限公司 | Data integration method based on unified data model |
| CN109840254A (en) * | 2018-12-14 | 2019-06-04 | 湖南亚信软件有限公司 | A kind of data virtualization and querying method, device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112667415A (en) | 2021-04-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112667415B (en) | Data calling method and device, readable storage medium and electronic equipment | |
| US9619304B2 (en) | Automatic connections between application components | |
| WO2020086187A1 (en) | Data processing method, apparatus, and device | |
| WO2019136800A1 (en) | Service processing method, apparatus and device, and computer-readable storage medium | |
| CN111683066B (en) | Heterogeneous system integration method, heterogeneous system integration device, computer equipment and storage medium | |
| CN113435862B (en) | Bill processing method and device based on mailbox | |
| CN113806037A (en) | Service calling method and device, storage medium and electronic equipment | |
| CN110704833A (en) | Data permission configuration method, device, electronic device and storage medium | |
| US7937696B2 (en) | Method, system and program product for adapting software applications for client devices | |
| CN113626223A (en) | Interface calling method and device | |
| CN113076153A (en) | Interface calling method and device | |
| CN111142863A (en) | Page generation method and device | |
| CN114385382A (en) | Light application access method and device, computer equipment and storage medium | |
| CN109669678A (en) | Template engine integration method, device, electronic equipment and storage medium | |
| CN111488286B (en) | Method and device for independently developing Android modules | |
| CN112650804A (en) | Big data access method, device, system and storage medium | |
| CN112732547B (en) | Service testing method and device, storage medium and electronic equipment | |
| WO2023082813A1 (en) | Information sharing method and apparatus, electronic device and storage medium | |
| CN116069725A (en) | File migration method, device, apparatus, medium and program product | |
| CN110471708B (en) | Method and device for acquiring configuration items based on reusable components | |
| CN114090127A (en) | Electronic device, loading method and medium of configuration file of electronic device | |
| US20170364293A1 (en) | Method and apparatus for data processing | |
| CN114064712A (en) | Data access method and device, electronic equipment and computer readable storage medium | |
| CN115114280A (en) | Report generation processing method, device and equipment | |
| CN113761588A (en) | Data verification method and device, terminal equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |