CN111767117B - Mobile end BI middleware technology based on application container - Google Patents
Mobile end BI middleware technology based on application container Download PDFInfo
- Publication number
- CN111767117B CN111767117B CN202010575744.1A CN202010575744A CN111767117B CN 111767117 B CN111767117 B CN 111767117B CN 202010575744 A CN202010575744 A CN 202010575744A CN 111767117 B CN111767117 B CN 111767117B
- Authority
- CN
- China
- Prior art keywords
- report
- user
- data
- middleware
- setting
- 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
- 238000013507 mapping Methods 0.000 claims abstract description 37
- 238000012546 transfer Methods 0.000 claims abstract description 7
- 238000001514 detection method Methods 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 claims description 3
- 238000012986 modification Methods 0.000 claims description 3
- 230000004048 modification Effects 0.000 claims description 3
- 238000004806 packaging method and process Methods 0.000 claims description 3
- 230000006978 adaptation Effects 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000010485 coping Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000000034 method Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/26—Visual data mining; Browsing structured data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/604—Tools and structures for managing or administering access control systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- General Health & Medical Sciences (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Bioethics (AREA)
- Health & Medical Sciences (AREA)
- Automation & Control Theory (AREA)
- Information Transfer Between Computers (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to the technical field of BIs, in particular to a mobile terminal BI middleware technology based on an application container, which comprises middleware, wherein the middleware builds bridging between the application container and a report server; checking user data in the report through bridging; setting a user mapping module; one-to-one correspondence between the group and the report user is carried out; setting a report request transfer module; setting a browsing history interface; setting a report collection interface, wherein a user is interested in a certain workbook or report, and can click the collection identification of the workbook or report page; clicking the collected report forms to display the report forms; setting a background management function, which is used for maintaining the mapping between the users and the groups, and maintaining the mapping aspects of the groups and the report users; the invention can be integrated with the report conveniently, can directly check report data of the report through a mobile phone, is convenient for customers to move and work, and has targeted pushing effect on customer preference and history.
Description
Technical Field
The invention relates to the technical field of BI (business information technology), in particular to a mobile terminal BI middleware technology based on an application container.
Background
With the popularity of smartphones, mobile offices are emerging. For convenience of people's office, various micro-applications for office have been developed. The portable office is convenient, and the portable office becomes an office mode expected by various industries, wherein the report forms are common office modes and are mainly used for reflecting data, so that the operations of statistics, viewing, calculation and the like of people are facilitated.
When the traditional report is checked, the access is carried out by using a PC end most of the time, and the access mode is not portable and inflexible. In order to solve the problems, the report view of the mobile terminal is developed, and various problems of the view of the PC terminal can be solved; however, the existing mobile terminal is not perfect enough to view the report, so that the user experience is poor, meanwhile, the viewing efficiency of the report is low, and the report cannot adapt to the large environment of the existing intelligent data coping, so that middleware is designed between the server and the mobile terminal to view the report, and more functions are set in the middleware, so that the report viewing becomes easy and convenient.
Disclosure of Invention
The invention aims to provide a mobile terminal BI middleware technology based on an application container.
To achieve the purpose, the invention adopts the following technical scheme:
providing a mobile terminal BI middleware technology based on an application container, wherein the middleware comprises middleware, and bridging is built between the application container and a report server; checking user data in the report form through bridging, synchronizing the user data of the report form into a local project library, and mapping the third party application user and the report form user;
setting a user mapping module, acquiring logged-in user information through an interface provided by an application container, distributing the logged-in user to a default group, and mapping the default group with report users in a report Server to realize mapping between the logged-in user and the users in the report Server;
the group and the report users are in one-to-one correspondence, different users are distributed into different groups, the authorities of the different groups are set, the same group corresponds to the same report user, and the authorities are the same;
setting a report request transfer module, after a user logs in, taking report user data according to the mapping, and splicing the URL of the accessed report through the function of accessing the report by the bill of the report to realize the function of checking the report;
setting a browsing history interface, after a user successfully accesses one report, storing accessed report data into history data of the user, wherein a database adopts an independent database, and when clicking a report in a history list, the report can be correspondingly displayed;
setting a report collection interface, wherein a user is interested in a certain workbook or report, clicking collection identification of the workbook or report page, and storing the workbook or report in a collection library of the user; clicking the collected report forms to display the report forms;
and setting a background management function for maintaining the mapping between the users and the groups, and maintaining the mapping aspects of the groups and the report users.
Further, the step of setting the user mapping module is as follows:
step one: logging in the user information and identifying through big data, recording the comparison information characteristics of the user information after comparison as a, setting x default groups, and endowing the x default groups with specific characteristics;
step two: comparing the characteristics of the comparison information a with the specific characteristics of the x default groups one by one, and displaying the comparison matching percentage;
step three: comparing the x percentages, taking out the maximum value, and corresponding the comparison information a with a default group n of the percentages;
step four: assigning the user information to a default group n;
step five: and respectively assigning rights to the x default groups, and respectively assigning corresponding rights to users in the x default groups.
Further, the step of setting the report request transfer module is as follows:
step one: after the report Server modifies the configuration of the report checked by the bill, a report request needs to be called to acquire the bill;
step two: splicing the acquired bill with the report server address and parameters to splice a URL;
step three: and giving the URL to a front-end page, accessing the front-end page by using the page, and displaying a report.
Further, when the report is displayed, the report is determined by calling a RestAPI of the report, when the RestAPI is called, a user name of the report is used, a password firstly acquires a token, the token is transmitted in a parameter form, and the workbook and the report data are acquired in a stream form; acquiring XML format data, analyzing the data through XML, finally packaging the data into classes, and returning to a front-end display page; each call needs to be taken from the report Server to the data, so that the real-time property of the data is ensured.
Further, the step of setting the browsing history interface is as follows:
step one: setting up a corresponding small database g1 for user information when a user logs in;
step two: when a user clicks and accesses a report, the accessed report data is set as n (n=1, 2, n) and is input into a small database g1;
step three: the report is endowed with marks m (m=1, 2, m), corresponding links are carried out on the report m and the report data n, the accessed report m data is input into a small database g1, and a history list is formed and displayed at the front end.
Further, in the user mapping module, a first login detection module is set, if the user does not exist in the middleware database during login, the user is allocated to a group x1 by default, x1 is a default report user, and the api of the report is called according to the user name password of the default report, the workbook data is taken, and the workbook data is displayed on a foreground page.
Furthermore, the background management is divided into 3 modules, namely 'report user management', 'group management', 'view management', and 'view management', wherein the view names can be modified, and the modified contents are local view names and display names.
Further, the report user management module maintains the password of the report user in a local library, when an API (application program interface) is used or the report library is queried, the report user name can be obtained, the password can not be obtained, the user name password of the report can be taken to a token when the view and the workbook list are displayed, and the related data of the report can be queried by calling a RestAPI after the password is transmitted to the token;
the group management module is used as an intermediate bridge for mapping the users and the report users, mainly maintains the user names and the report user names in the group management, and report user options in the group are displayed by inquiring the report user names and cannot be modified at will;
the view management module starts the aliases from the view names acquired from the report server and displays the aliases of the report when the page is displayed; the thumbnail of the report is obtained from the report server by default, and is uploaded to the local thumbnail through view management to replace the original view thumbnail.
Further, after the view data is displayed to the foreground, when a user clicks a certain Zhang Shitu, the user firstly obtains a corresponding bill according to the name of the report user, after the bill is obtained, the data such as IP of the bill and the report Server are added, some parameters needing to control the style are spliced, and the path after splicing is returned to the front-end page.
Furthermore, the middleware is matched with a third party application, and user data is transmitted to the middleware so as to carry out mapping maintenance with the report; in the code of the middleware, parameters are received, and user data is captured.
The invention has the beneficial effects that:
through the mobile terminal report middleware, the mobile terminal report middleware can be integrated with a report conveniently, report data of the report can be directly checked through a mobile phone, and mobile office of a client is facilitated.
1. The method overcomes the defect of mobile BI products in an open platform (or third party application).
2. And integrating the report service into the mobile micro-application ecology, and improving the ecology of report service users.
3. And opening the micro application or applet mobile entry of the original report server enterprise user, and unifying the entry.
4. And seamlessly integrating the user rights of the third-party application user and the report server, and improving user experience without secondary authentication for user access.
5. Perfect mobile terminal adaptation, original report interaction function is reserved, and horizontal screen mode report browsing is supported.
6. The multi-terminal access requirements of the private cloud and the public cloud of the report user are supported, and the non-sensing cloud access can be realized.
7. And (3) moving: and the user directly checks the report forms through the mobile phone.
8. Real-time: providing more realistic data in a shorter time
9. Self-help: time and cost are saved
10. Expanding: the middleware is a report and intermediate service, has strong expansibility, can change the report and the thumbnail, and then is displayed on the mobile terminal, and can change the name of the report and then is displayed on the mobile terminal.
Drawings
In order to more clearly illustrate the technical solution of the embodiments of the present invention, the drawings that are required to be used in the embodiments of the present invention will be briefly described below.
FIG. 1 is a mapping diagram of the present invention;
FIG. 2 is a report accessing flowchart of the present invention.
Detailed Description
The technical scheme of the invention is further described below by the specific embodiments with reference to the accompanying drawings.
Wherein the drawings are for illustrative purposes only and are shown in schematic, non-physical, and not intended to be limiting of the present patent; for the purpose of better illustrating embodiments of the invention, certain elements of the drawings may be omitted, enlarged or reduced in size and do not represent the actual product dimensions.
Referring to FIG. 1 and FIG. 2, the application container-based mobile end BI middleware technology includes middleware that bridges between the application container and the report server; checking user data in the report form through bridging, synchronizing the user data of the report form into a local project library, and mapping the third party user and the report form user;
setting a user mapping module, acquiring logged-in user information through an interface provided by an application container, distributing the logged-in user to a default group, and mapping the default group with report users in a report Server to realize mapping between the logged-in user and the users in the report Server;
the group and the report users are in one-to-one correspondence, different users are distributed into different groups, the authorities of the different groups are set, the same group corresponds to the same report user, and the authorities are the same;
setting a report request transfer module, after a user logs in, taking report user data according to the mapping, and splicing the URL of the accessed report through the function of accessing the report by the bill of the report to realize the function of checking the report;
setting a browsing history interface, after a user successfully accesses a report, storing accessed report data into history data of the user, wherein a database adopts an independent database, and when clicking a report in a history list, the report can be correspondingly displayed;
setting a report collection interface, wherein a user is interested in a certain workbook or report, clicking collection identification of a workbook or report page, storing the workbook or report in a collection library of the user, and when the user is in the same state as a history list, clicking the collected workbook in a display page collected by the user, and entering the workbook to list all reports under the workbook; clicking the collected report forms to display the report forms;
and setting a background management function for maintaining the mapping between the users and the groups, and maintaining the mapping aspects of the groups and the report users.
The step of setting the user mapping module is as follows:
step one: logging in the user information and identifying through big data, recording the comparison information characteristics of the user information after comparison as a, setting x default groups, and endowing the x default groups with specific characteristics;
step two: comparing the characteristics of the comparison information a with the specific characteristics of the x default groups one by one, and displaying the comparison matching percentage;
step three: comparing the x percentages, taking out the maximum value, and corresponding the comparison information a with a default group n of the percentages;
step four: assigning the user information to a default group n;
step five: and respectively assigning rights to the x default groups, and respectively assigning corresponding rights to users in the x default groups.
The report request transfer module is set as follows:
step one: after the report Server modifies the configuration of the report checked by the bill, a report request needs to be called to acquire the bill;
step two: splicing the acquired bill with the report server address and parameters to splice a URL;
step three: and giving the URL to a front-end page, accessing the front-end page by using the page, and displaying a report.
When the report is displayed, the report is decided by calling a RestAPI of the report, when the RestAPI is called, a user name of the report is used, a password firstly acquires a token, the token is transmitted in a parameter form, and the workbook and report data are acquired in a stream form; acquiring XML format data, analyzing the data through XML, finally packaging the data into classes, and returning to a front-end display page; each call needs to be taken from the report Server to the data, so that the real-time property of the data is ensured.
The steps of setting the browsing history interface are as follows:
step one: setting up a corresponding small database g1 for user information when a user logs in;
step two: when a user clicks and accesses a report, the accessed report data is set as n (n=1, 2, n) and is input into a small database g1;
step three: the report is endowed with marks m (m=1, 2, m), corresponding links are carried out on the report m and the report data n, the accessed report m data is input into a small database g1, and a history list is formed and displayed at the front end.
In the user mapping module, a first login detection module is set, if the user does not exist in the middleware database during login, the user is distributed to a group x1 by default, x1 is a default report user, and the api of the report is called according to a user name password of the default report, the workbook data is taken, and the workbook data is displayed on a foreground page.
The background management is divided into 3 modules, namely 'report user management', 'group management', 'view management', and 'view management' can modify view names, and the modification content is local view names and display names.
The report user management module is used for maintaining the passwords of the report user in a local library, acquiring the report user name when using an API or inquiring the report library, acquiring no passwords, taking a token only by the user name passwords of the report when displaying the view and the workbook list, calling a RestAPI after the passwords are transmitted into the token, and inquiring related data of the report;
the group management module is used as an intermediate bridge for mapping the users and the report users, mainly maintains the user names and the report user names in the group management, and report user options in the group are displayed by inquiring the report user names and cannot be modified at will;
the view management module starts the aliases from the view names acquired from the report server and displays the aliases of the report when the page is displayed; the thumbnail of the report is obtained from the report server by default, and is uploaded to the local thumbnail through view management to replace the original view thumbnail.
After the view data are displayed on the foreground, when a user clicks a certain Zhang Shitu, the user firstly takes a corresponding bill according to the name of the report user, after the bill is obtained, the bill, IP (Internet protocol) and other data of the report Server are added, some parameters needing to control the style are spliced, and the path after splicing is returned to the front-end page.
The middleware is matched with a third party application, user data is transmitted to the middleware, and mapping maintenance can be carried out on the user data and the report; in the code of the middleware, parameters are received, and user data is captured
The foregoing is merely illustrative of the structures of this invention and various modifications, additions and substitutions for those skilled in the art can be made to the described embodiments without departing from the scope of the invention or from the scope of the invention as defined in the accompanying claims.
Claims (10)
1. The mobile terminal BI middleware technology based on the application container is characterized by comprising middleware, wherein the middleware builds bridging between the application container and a report server; checking user data in the report form through bridging, synchronizing the user data of the report form into a local project library, and mapping the third party application user and the report form user;
setting a user mapping module, acquiring logged-in user information through an interface provided by an application container, distributing the logged-in user to a default group, and mapping the default group with report users in a report Server to realize mapping between the logged-in user and the users in the report Server;
the group and the report users are in one-to-one correspondence, different users are distributed into different groups, the authorities of the different groups are set, the same group corresponds to the same report user, and the authorities are the same;
setting a report request transfer module, after a user logs in, taking report user data according to the mapping, and splicing the URL of the accessed report through the function of accessing the report by the bill of the report to realize the function of checking the report;
setting a browsing history interface, after a user successfully accesses one report, storing accessed report data into history data of the user, wherein a database adopts an independent database, and when clicking a report in a history list, the report can be correspondingly displayed;
setting a report collection interface, wherein a user is interested in a certain workbook or report, clicking collection identification of the workbook or report page, and storing the workbook or report in a collection library of the user; clicking the collected report forms to display the report forms;
and setting a background management function for maintaining the mapping between the users and the groups, and maintaining the mapping aspects of the groups and the report users.
2. The application container-based mobile terminal BI middleware technology according to claim 1, wherein the step of setting the user mapping module is as follows:
step one: logging in the user information and identifying through big data, recording the comparison information characteristics of the user information after comparison as a, setting x default groups, and endowing the x default groups with specific characteristics;
step two: comparing the characteristics of the comparison information a with the specific characteristics of the x default groups one by one, and displaying the comparison matching percentage;
step three: comparing the x percentages, taking out the maximum value, and corresponding the comparison information a with a default group n of the percentages;
step four: assigning the user information to a default group n;
step five: and respectively assigning rights to the x default groups, and respectively assigning corresponding rights to users in the x default groups.
3. The application container-based mobile terminal BI middleware technology according to claim 1, wherein the step of setting a report request transfer module is as follows:
step one: after the report Server modifies the configuration of the report checked by the bill, a report request needs to be called to acquire the bill;
step two: splicing the acquired bill with the report server address and parameters to splice a URL;
step three: and giving the URL to a front-end page, accessing the front-end page by using the page, and displaying a report.
4. The application container-based mobile terminal BI middleware technology according to claim 3, wherein the report is decided by calling a RestAPI of the report when the report is presented, a user name of the report is used when the RestAPI is called, a password firstly acquires a token, the token is transmitted in a parameter form, and the workbook and the report data are acquired in a stream form; acquiring XML format data, analyzing the data through XML, finally packaging the data into classes, and returning to a front-end display page; each call needs to be taken from the report Server to the data, so that the real-time property of the data is ensured.
5. The application container-based mobile terminal BI middleware technology according to claim 1, wherein the step of setting a browsing history interface is as follows:
step one: setting up a corresponding small database g1 for user information when a user logs in;
step two: when a user clicks and accesses a report, the accessed report data is set as n (n=1, 2, n) and is input into a small database g1;
step three: the report is endowed with marks m (m=1, 2, m), corresponding links are carried out on the report m and the report data n, the accessed report m data is input into a small database g1, and a history list is formed and displayed at the front end.
6. The application container-based mobile terminal BI middleware technology according to claim 1, wherein the user mapping module is configured with a first login detection module, if the user does not exist in the middleware database during login, the default is allocated to a group x1, x1 is a default report user, and according to a user name password of the default report, an api of the report is called, and the workbook data is taken and displayed on a foreground page.
7. The application container-based mobile BI middleware technology according to claim 1, wherein the background management is divided into 3 modules, namely "report user management", "group management", "view management", and "view management", which can modify view names, and the modification content is a local view name and a presentation name.
8. The mobile terminal BI middleware technology based on an application container according to claim 7, wherein the report user management module maintains a report user password in a local library, can acquire a report user name when using an API or querying the report library, can not acquire the password, can take a token only by the user name password of the report when displaying a view and a workbook list, can call a RestAPI after entering the token, and queries related data of the report;
the group management module is used as an intermediate bridge for mapping the users and the report users, mainly maintains the user names and the report user names in the group management, and report user options in the group are displayed by inquiring the report user names and cannot be modified at will;
the view management module starts the aliases from the view names acquired from the report server and displays the aliases of the report when the page is displayed; the thumbnail of the report is obtained from the report server by default, and is uploaded to the local thumbnail through view management to replace the original view thumbnail.
9. The application container-based mobile terminal BI middleware technology according to claim 8, wherein after the view data is displayed to the foreground, when a user clicks a certain Zhang Shitu, the user first obtains a corresponding bill according to the name of the report user, obtains the data such as the IP of the bill and the report Server after the bill is obtained, applies url of the view, and some parameters requiring control patterns to splice, and returns the path after splicing to the front page.
10. The application container-based mobile terminal BI middleware technology according to claim 1, wherein the middleware is configured with a third party application, and user data is transferred to the middleware so as to perform mapping maintenance with a report; in the code of the middleware, parameters are received, and user data is captured.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010575744.1A CN111767117B (en) | 2020-06-22 | 2020-06-22 | Mobile end BI middleware technology based on application container |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010575744.1A CN111767117B (en) | 2020-06-22 | 2020-06-22 | Mobile end BI middleware technology based on application container |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111767117A CN111767117A (en) | 2020-10-13 |
| CN111767117B true CN111767117B (en) | 2024-02-20 |
Family
ID=72721493
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010575744.1A Active CN111767117B (en) | 2020-06-22 | 2020-06-22 | Mobile end BI middleware technology based on application container |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111767117B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112367328B (en) * | 2020-11-13 | 2022-01-04 | 四川长虹电器股份有限公司 | Method for entering Kubernetes cluster container based on websocket |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1588369A (en) * | 2004-09-06 | 2005-03-02 | 杭州恒生电子股份有限公司 | Relation type data base system and its search and report method |
| CN101216817A (en) * | 2007-12-29 | 2008-07-09 | 中国建设银行股份有限公司 | Heterogeneous report form integration and centralized management device and system |
| CN101710336A (en) * | 2009-12-14 | 2010-05-19 | 浪潮通信信息系统有限公司 | Method for accelerating data processing by using relational middleware |
| CN104200402A (en) * | 2014-09-11 | 2014-12-10 | 国家电网公司 | Publishing method and system of source data of multiple data sources in power grid |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20010034679A1 (en) * | 2000-01-21 | 2001-10-25 | Wrigley Mark L. | Platform independent and non-invasive financial report mark-up |
-
2020
- 2020-06-22 CN CN202010575744.1A patent/CN111767117B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1588369A (en) * | 2004-09-06 | 2005-03-02 | 杭州恒生电子股份有限公司 | Relation type data base system and its search and report method |
| CN101216817A (en) * | 2007-12-29 | 2008-07-09 | 中国建设银行股份有限公司 | Heterogeneous report form integration and centralized management device and system |
| CN101710336A (en) * | 2009-12-14 | 2010-05-19 | 浪潮通信信息系统有限公司 | Method for accelerating data processing by using relational middleware |
| CN104200402A (en) * | 2014-09-11 | 2014-12-10 | 国家电网公司 | Publishing method and system of source data of multiple data sources in power grid |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111767117A (en) | 2020-10-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103559040B (en) | A kind of system and method based on SDK rapid build mobile Internet application module | |
| US9230257B2 (en) | Systems and methods for customer relationship management | |
| KR102504075B1 (en) | Matching and attributes of user device events | |
| CN103475577B (en) | Method, device and network equipment for obtaining characteristic information | |
| WO2010095867A2 (en) | Customized intellectual system for searching internet information using symbols and icons through a mobile communication terminal and an ip-based information terminal | |
| US20160162470A1 (en) | Semantic Application Logging and Analytics | |
| AU2014400621B2 (en) | System and method for providing contextual analytics data | |
| US8271435B2 (en) | Predictive categorization | |
| CN101606371A (en) | Content distribution management device, communication terminal, program and content delivering system | |
| US11882154B2 (en) | Template representation of security resources | |
| CN109241384B (en) | Scientific research information visualization method and device | |
| CN102265297A (en) | Techniques to manage and display related communications | |
| CN111427613A (en) | Application program interface API management method and device | |
| US20220067092A1 (en) | Integration of video conferencing applications with on-demand database services | |
| CN102394866A (en) | Methods for sharing data and applications in near-field communication network and near-field communication network | |
| CN111767117B (en) | Mobile end BI middleware technology based on application container | |
| GB2581634A (en) | Providing reporting and analysis for campaign-driven messages and websites | |
| CN105592352A (en) | File-sharing method and system based on smart TV | |
| US11689757B2 (en) | Method and apparatus for providing video streams | |
| CN113569089A (en) | Information processing method, device, server, equipment, system and storage medium | |
| CN114995717B (en) | Multi-front-end middle station management method and system | |
| CN111045928A (en) | Interface data testing method, device, terminal and storage medium | |
| CN112351420B (en) | Networking identity creation method and equipment of terminal equipment and readable storage medium | |
| KR100392195B1 (en) | System for network-based resource common service | |
| CN107453950A (en) | A kind of information processing method and monitoring system |
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 | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: Room 305-1, Building 16, Yard 16, Yingcai North 3rd Street, Future Science City, Changping District, Beijing 102211 Applicant after: ZTE Wisdom (Beijing) Technology Co.,Ltd. Address before: Room 305-1, Building 16, No. 16, Yingcai North Third Street, Future Science City, Changping District, Beijing, 102209 Applicant before: Bo Yi Chih soft (Beijing) Technology Co.,Ltd. |
|
| CB03 | Change of inventor or designer information | ||
| CB03 | Change of inventor or designer information |
Inventor after: Yan Jinwen Inventor after: Hu Bo Inventor after: Gong Yiling Inventor before: Yan Jinwen Inventor before: Hu Bo |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |