CN111767117A - Mobile-end BI middleware technology based on application container - Google Patents
Mobile-end BI middleware technology based on application container Download PDFInfo
- Publication number
- CN111767117A CN111767117A CN202010575744.1A CN202010575744A CN111767117A CN 111767117 A CN111767117 A CN 111767117A CN 202010575744 A CN202010575744 A CN 202010575744A CN 111767117 A CN111767117 A CN 111767117A
- 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.)
- Granted
Links
- 238000013507 mapping Methods 0.000 claims abstract description 35
- 230000005540 biological transmission Effects 0.000 claims abstract description 6
- 238000000034 method Methods 0.000 claims description 10
- 238000013461 design Methods 0.000 claims description 4
- 238000001514 detection method Methods 0.000 claims description 4
- 238000004806 packaging method and process Methods 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 claims 1
- 238000012546 transfer Methods 0.000 claims 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000001939 inductive effect Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
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 Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Security & Cryptography (AREA)
- Automation & Control Theory (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention relates to the technical field of BI (business intelligence) technology, in particular to a mobile end BI middleware technology based on an application container, which comprises a middleware, wherein the middleware builds bridging between the application container and a report server; checking user data in the report form through bridging; setting a user mapping module; the group and the report form users are in one-to-one correspondence; setting a report request transmission module; setting a browsing history interface; setting a report collection interface, wherein a user is interested in a certain workbook or a report and can click a collection identifier of a workbook or a report page; clicking the collected report to display the report; setting a background management function for maintaining the mapping between the user and the group, and maintaining the mapping between the group and the report user; the invention can be conveniently integrated with the report, can directly check report data through a mobile phone, is convenient for clients to carry out mobile office work, and has a targeted pushing effect according to the preferences and history of the clients.
Description
Technical Field
The invention relates to the technical field of BI, in particular to a mobile terminal BI middleware technology based on an application container.
Background
With the popularization of smart phones, mobile office work appears. In order to facilitate the office work of people, various micro applications applied to the office work are produced. The portable office is convenient and portable, and the report forms are increasingly expected by various industries, wherein the report forms are common office forms and are mainly used for embodying data, and are convenient for people to perform operations such as statistics, viewing and calculation on the data.
When the traditional report is checked, the PC terminal is used for accessing most of the time, and the access mode is inconvenient to carry and inflexible. In order to solve the problems, mobile terminal report form checking is developed, and various problems checked by a PC terminal can be solved; but present mobile terminal looks over the report and is not perfect enough now, leads to user experience relatively poor, and is lower to the efficiency of looking over of report simultaneously, can't adapt to the big environment that present intelligent data dealt with, consequently designs the middleware between server and mobile terminal and looks over the report, sets up more function in the middleware for it becomes light convenient to look over the report.
Disclosure of Invention
The invention aims to provide a mobile end BI middleware technology based on an application container.
In order to achieve the purpose, the invention adopts the following technical scheme:
the mobile terminal BI middleware technology based on the application container is provided and comprises a middleware, wherein the middleware builds a bridge between the application container and a report server; checking user data in the report through bridging, and synchronizing the user data of the report into a local project library for mapping a third-party application user and a report user;
setting a user mapping module, acquiring login user information through an interface provided by an application container, distributing the login user to a default group, mapping the default group with a report user in a report Server, and realizing mapping between the login user and the report user in the report Server;
the group and the report user are in one-to-one correspondence, different users are distributed to different groups, the authority of different groups is set, the same group corresponds to the same report user, and the owned authorities are the same;
setting a report request transmission module, obtaining report user data according to the mapping after a user logs in, accessing the report through the bill of the report, splicing and accessing the URL of the report, and realizing the function of viewing the report;
setting a browsing history interface, storing the accessed report data into the history data of a user after the user successfully accesses one report, wherein the database adopts an independent database, and when a certain report is clicked 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, can click a collection identifier of a workbook or a report page, and stores the workbook or the report into a collection library of the user, and the same as the history list is that the collected workbook is clicked in a display page collected by the user, so that the user can enter the workbook and list all reports under the workbook; clicking the collected report to display the report;
and setting a background management function for maintaining the mapping between the user and the group and maintaining the mapping between the group and the report user.
Further, the step of setting the user mapping module is as follows:
the method comprises the following steps: logging in user information, identifying the user information through big data, recording the compared information characteristic of the user information after comparison as a, setting x default groups, and giving specific characteristics to the x default groups;
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 coincidence percentage;
step three: comparing the x percentages, taking out the maximum value, and corresponding the comparison information a with the default group n of the percentages;
step four: assigning the user information to a default group n;
step five: and respectively endowing the x default groups with the authority, and respectively endowing the users in the x default groups with the corresponding authority.
Further, the step of setting the report request transmission module is as follows:
the method comprises the following steps: after the report Server end modifies the configuration of the report checked through the bill, the report request needs to be called to obtain the bill;
step two: splicing the obtained bill with the address and the parameters of the report server to form a URL;
step three: and giving the URL to a front-end page, using the page to access, and displaying the report.
Further, when the report is displayed, the statement is determined by calling RestAPI of the report, when the RestAPI is called, the user name of the report is used, the token is firstly obtained by the password, the token is passed in a parameter form, and the workbook and the report data are obtained in a stream form; acquiring XML-formatted data, analyzing the data through XML, finally packaging the data into classes, and returning to a front-end display page; and data is required to be taken from the report Server every time of calling, so that the real-time performance of the data is ensured.
Further, the step of setting the browsing history interface is as follows:
the method comprises the following steps: when a user logs in, a corresponding small database g1 is set for the user information;
step two: when a user clicks and accesses a report, setting n (n is 1, 2, n and n) of accessed report data to be recorded into the small database g 1;
step three: and (3) giving a mark m (m is 1, 2, the sum of m and m), carrying out correspondence and corresponding link design on the report m and the report data n, inputting the accessed data of the report m into a small database g1, and displaying a history list to the front end.
Furthermore, a first login detection module is arranged in the user mapping module, when logging in, if the user does not exist in the middleware database, the user is assigned to a group x1 by default, x1 is a default report user, the api of the report is called according to the user name and the password of the default report, the workbook data is taken, and the foreground page is displayed.
Further, the background management is divided into 3 modules, namely 'report user management', 'group management', 'view management', and the like, and the view name can be modified, and the modified content is the local view name and the display name.
Furthermore, the report user management module maintains the password of the report user in a local library, when an API is used or the report library is queried, the report user name can be obtained, the password cannot be obtained, the token can be taken only when the view and the workbook list are displayed, and the RestAPI can be called to query the related data of the report after the token is transmitted;
the group management module is used as a middle bridge for mapping the user and the report user, the user name and the report user name are mainly maintained in group management, and the report user option in the group is displayed by inquiring the report user name and cannot be modified randomly;
the view management module is used for giving an alias to the view name acquired from the report server and displaying the alias of the report when the page is displayed; the default of the thumbnail of the report is obtained from a report server, and the thumbnail is uploaded to a local thumbnail through view management to replace the original view thumbnail.
Furthermore, after the view data is displayed to the foreground, when a user clicks a certain view, the corresponding bill is taken according to the report user name, after the bill is obtained, the bill, the data of the report Server, such as IP (Internet protocol) and the like, are spliced together with the url of the view and some parameters needing to control the style, and the spliced path is returned to the front-end page.
Furthermore, the middleware is matched with a third-party application, and the user data is transmitted to the middleware so as to be mapped and maintained 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 this removal end report form middleware, can be convenient carry out integrated whole with the report form, can directly look over report form data through the cell-phone, make things convenient for customer's mobile office.
1. The lack of moving BI products in an open platform (or third party application) is compensated.
2. The report service is integrated into the mobile micro-application ecology, and the report service user ecology is improved.
3. And (4) opening the micro application or small program mobile entry of the enterprise user of the original report server, and unifying the entries.
4. The user permission of the third-party application user and the report server is seamlessly integrated, secondary authentication is not needed for user access, and user experience is improved.
5. The perfect mobile terminal adaptation keeps the original report interactive function and supports the browsing of the horizontal screen mode report.
6. The multi-end access requirements of the private cloud and the public cloud of the report user are supported, and the non-inductive cloud access can be realized.
7. Moving: and the user directly checks the report form through the mobile phone.
8. Real-time implementation: providing more realistic data in a shorter time
9. Self-help: saving time and cost
10. Expanding: the middleware is a report and a middle service, has strong expansibility, can be displayed on the mobile terminal after the report and the thumbnail are changed, and can be displayed on the mobile terminal after the report name is modified.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments of the present invention will be briefly described below.
FIG. 1 is a mapping relationship diagram of the present invention;
FIG. 2 is a flow chart of report access according to the present invention.
Detailed Description
The technical scheme of the invention is further explained by the specific implementation mode in combination with the attached drawings.
Wherein the showings are for the purpose of illustration only and are shown by way of illustration only and not in actual form, and are not to be construed as limiting the present patent; to better illustrate the embodiments of the present invention, some components of the drawings may be omitted, enlarged or reduced, and do not represent the size of an actual product.
The application container-based mobile end BI middleware technology shown in the figures 1 and 2 comprises a middleware which builds a bridge between an application container and a report server; checking user data in the report through bridging, and synchronizing the user data of the report into a local project library for mapping between a third-party user and a report user;
setting a user mapping module, acquiring login user information through an interface provided by an application container, distributing the login user to a default group, mapping the default group with a report user in a report Server, and realizing mapping between the login user and the report user in the report Server;
the group and the report user are in one-to-one correspondence, different users are distributed to different groups, the authority of different groups is set, the same group corresponds to the same report user, and the owned authorities are the same;
setting a report request transmission module, after a user logs in, obtaining report user data according to mapping, accessing the report through the bill of the report, splicing and accessing the URL of the report, and realizing the function of viewing the report;
setting a browsing history interface, storing accessed report data into the history data of a user after the user successfully accesses a report, wherein the database adopts an independent database, and the report can be correspondingly displayed when a certain report is clicked in a history list;
setting a report collection interface, wherein a user is interested in a certain workbook or report, can click a collection identifier of a workbook or a report page, and stores the workbook or the report into a collection library of the user, and the same as a history list is that the collected workbook is clicked in a display page collected by the user, and all reports under the workbook can be listed under the workbook; clicking the collected report to display the report;
and setting a background management function for maintaining the mapping between the user and the group and maintaining the mapping between the group and the report user.
The steps of setting the user mapping module are as follows:
the method comprises the following steps: logging in user information, identifying the user information through big data, recording the compared information characteristic of the user information after comparison as a, setting x default groups, and giving specific characteristics to the x default groups;
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 coincidence percentage;
step three: comparing the x percentages, taking out the maximum value, and corresponding the comparison information a with the default group n of the percentages;
step four: assigning the user information to a default group n;
step five: and respectively endowing the x default groups with the authority, and respectively endowing the users in the x default groups with the corresponding authority.
The steps of setting the report request transmission module are as follows:
the method comprises the following steps: after the report Server end modifies the configuration of the report checked through the bill, the report request needs to be called to obtain the bill;
step two: splicing the obtained bill with the address and the parameters of the report server to form a URL;
step three: and giving the URL to a front-end page, using the page to access, and displaying the report.
The method comprises the steps that a report is displayed according to the RestAPI of the report, the user name of the report is used when the RestAPI is called, a token is obtained through a password, the token is transmitted in a parameter mode, and a workbook and report data are obtained in a stream mode; acquiring XML-formatted data, analyzing the data through XML, finally packaging the data into classes, and returning to a front-end display page; and data is required to be taken from the report Server every time of calling, so that the real-time performance of the data is ensured.
The steps of setting the browsing history interface are as follows:
the method comprises the following steps: when a user logs in, a corresponding small database g1 is set for the user information;
step two: when a user clicks and accesses a report, setting n (n is 1, 2, n and n) of accessed report data to be recorded into the small database g 1;
step three: and (3) giving a mark m (m is 1, 2, the sum of m and m), carrying out correspondence and corresponding link design on the report m and the report data n, inputting the accessed data of the report m into a small database g1, and displaying a history list to the front end.
And a first login detection module is arranged in the user mapping module, if no user exists in the middleware database during login, the user is assigned to a group x1 by default, x1 is a default report user, the api of the report is called according to the user name and the password of the default report, the workbook data is taken, and the foreground page is displayed.
The background management is divided into 3 modules, namely 'report user management', 'group management', 'view management', and the like, and the view names can be modified, and the modified contents are the local view names and the display names.
The report user management module is used for maintaining the password of the report user in a local library, acquiring a report user name and not acquiring the password when an API is used or the report library is inquired, taking the token only when the user name and the password of the report are needed when a view and a workbook list are displayed, calling RestAPI after the token is transmitted, and inquiring related data of the report;
the group management module is used as a middle bridge for mapping the user and the report user, the user name and the report user name are mainly maintained in the group management, and the report user option in the group is displayed by inquiring the report user name and cannot be modified randomly;
the view management module is used for giving an alias to the view name acquired from the report server and displaying the alias of the report when the page is displayed; the default of the thumbnail of the report is obtained from a report server, and the thumbnail is uploaded to a local thumbnail through view management to replace the original view thumbnail.
After the view data is displayed to the foreground, when a user clicks a certain view, the user firstly takes a corresponding bill according to a report user name, and after the bill is obtained, the bill, the IP (Internet protocol) and other data of a report Server are spliced together with url of the view and parameters of patterns needing to be controlled, and the spliced path is returned to a front-end page.
The middleware is matched with the third-party application, and the user data is transmitted to the middleware so as to be mapped and maintained with the report; in the code of the middleware, parameters are received, user data is captured
The foregoing is merely exemplary and illustrative of the present invention and various modifications, additions and substitutions may be made by those skilled in the art to the specific embodiments described without departing from the scope of the invention as defined in the following claims.
Claims (10)
1. The mobile end BI middleware technology based on the application container is characterized by comprising a middleware, wherein the middleware builds bridging between the application container and a report server; checking user data in the report through bridging, and synchronizing the user data of the report into a local project library for mapping a third-party application user and a report user;
setting a user mapping module, acquiring login user information through an interface provided by an application container, distributing the login user to a default group, mapping the default group with a report user in a report Server, and realizing mapping between the login user and the report user in the report Server;
the group and the report user are in one-to-one correspondence, different users are distributed to different groups, the authority of different groups is set, the same group corresponds to the same report user, and the owned authorities are the same;
setting a report request transmission module, obtaining report user data according to the mapping after a user logs in, accessing the report through the bill of the report, splicing and accessing the URL of the report, and realizing the function of viewing the report;
setting a browsing history interface, storing the accessed report data into the history data of a user after the user successfully accesses one report, wherein the database adopts an independent database, and when a certain report is clicked 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, can click a collection identifier of a workbook or a report page, and stores the workbook or the report into a collection library of the user, and the same as the history list is that the collected workbook is clicked in a display page collected by the user, so that the user can enter the workbook and list all reports under the workbook; clicking the collected report to display the report;
and setting a background management function for maintaining the mapping between the user and the group and maintaining the mapping between the group and the report user.
2. The application container-based mobile-end BI middleware technology of claim 1, wherein the step of setting the user mapping module is as follows:
the method comprises the following steps: logging in user information, identifying the user information through big data, recording the compared information characteristic of the user information after comparison as a, setting x default groups, and giving specific characteristics to the x default groups;
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 coincidence percentage;
step three: comparing the x percentages, taking out the maximum value, and corresponding the comparison information a with the default group n of the percentages;
step four: assigning the user information to a default group n;
step five: and respectively endowing the x default groups with the authority, and respectively endowing the users in the x default groups with the corresponding authority.
3. The application container-based mobile-end BI middleware technology of claim 1, wherein the step of setting a report request transfer module is as follows:
the method comprises the following steps: after the report Server end modifies the configuration of the report checked through the bill, the report request needs to be called to obtain the bill;
step two: splicing the obtained bill with the address and the parameters of the report server to form a URL;
step three: and giving the URL to a front-end page, using the page to access, and displaying the report.
4. The application container-based mobile-end BI middleware technology of claim 3, wherein the statement is displayed by calling RestAPI of the statement, the user name of the statement is used when RestAPI is called, the password first obtains token, the token is passed in a parameter form, and the workbook and statement data are obtained in a stream form; acquiring XML-formatted data, analyzing the data through XML, finally packaging the data into classes, and returning to a front-end display page; and data is required to be taken from the report Server every time of calling, so that the real-time performance of the data is ensured.
5. The application container-based mobile-end BI middleware technology of claim 1, wherein the step of setting a browsing history interface is as follows:
the method comprises the following steps: when a user logs in, a corresponding small database g1 is set for the user information;
step two: when a user clicks and accesses a report, setting n (n is 1, 2, n and n) of accessed report data to be recorded into the small database g 1;
step three: and (3) giving a mark m (m is 1, 2, the sum of m and m), carrying out correspondence and corresponding link design on the report m and the report data n, inputting the accessed data of the report m into a small database g1, and displaying a history list to the front end.
6. The BI middleware technology of claim 1, wherein the user mapping module is configured with a first login detection module, and when the user is not present in the middleware database during login, the first login detection module is assigned to a group x1 by default, wherein x1 is a default report user, and the api of the report is called according to a username and a password of the default report, and the workbook data is fetched and displayed on a foreground page.
7. The application container-based mobile-end BI middleware technology of claim 1, wherein the background management is divided into 3 modules, which are respectively "report user management", "group management", "view management", and the view name can be modified, and the modified content is the local view name and display name.
8. The application container-based mobile-end BI middleware technology of claim 7, wherein the report user management module maintains a password of a report user in a local library, can acquire a report user name and cannot acquire the password when using an API or querying the report library, can take a token when a view and a workbook list are displayed by using the user name and the password of the report, and can call RestAPI to query related data of the report after the token is transmitted;
the group management module is used as a middle bridge for mapping the user and the report user, the user name and the report user name are mainly maintained in group management, and the report user option in the group is displayed by inquiring the report user name and cannot be modified randomly;
the view management module is used for giving an alias to the view name acquired from the report server and displaying the alias of the report when the page is displayed; the default of the thumbnail of the report is obtained from a report server, and the thumbnail is uploaded to a local thumbnail through view management to replace the original view thumbnail.
9. The BI middleware technology of a mobile terminal based on an application container as claimed in claim 8, wherein after the view data is displayed to the foreground, when a user clicks a view, the user first gets a corresponding bill according to a report user name, after the bill is obtained, splices the bill and data such as IP of a report Server, and additionally adds url of the view, some parameters needing to control a style, and returns the spliced path to the front-end page.
10. The application container-based mobile BI middleware technology of claim 1, wherein the middleware is adapted to a third party application, and the user data is transmitted to the middleware for mapping maintenance with the 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 true CN111767117A (en) | 2020-10-13 |
| CN111767117B 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) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112367328A (en) * | 2020-11-13 | 2021-02-12 | 四川长虹电器股份有限公司 | Method for entering Kubernetes cluster container based on websocket |
Citations (5)
| 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 |
| 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 |
-
2020
- 2020-06-22 CN CN202010575744.1A patent/CN111767117B/en active Active
Patent Citations (5)
| 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 |
| 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 |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112367328A (en) * | 2020-11-13 | 2021-02-12 | 四川长虹电器股份有限公司 | Method for entering Kubernetes cluster container based on websocket |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111767117B (en) | 2024-02-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11366686B1 (en) | Managing user data in a multitenant deployment | |
| CN1949763B (en) | Shared message server system | |
| US6990532B2 (en) | Context-sensitive help for thin client-based business operations platform | |
| US9009135B2 (en) | Method and apparatus for satisfying a search request using multiple search engines | |
| KR102504075B1 (en) | Matching and attributes of user device events | |
| US20030172127A1 (en) | Execution of process by references to directory service | |
| US20090174551A1 (en) | Internet activity evaluation system | |
| WO2010095867A2 (en) | Customized intellectual system for searching internet information using symbols and icons through a mobile communication terminal and an ip-based information terminal | |
| US8271435B2 (en) | Predictive categorization | |
| US8396941B2 (en) | Digital living network alliance (DLNA) server that serves contents from IVL services | |
| US20190394632A1 (en) | Method and system for storing contact information in a network contact database | |
| US8731151B2 (en) | Methods and apparatus for partially updating a web page using an embedded iFrame | |
| CN109241384B (en) | Scientific research information visualization method and device | |
| CN109600458B (en) | Website access method and device | |
| CN111427613A (en) | Application program interface API management method and device | |
| CN112256772A (en) | Data service method, device and readable storage medium | |
| US20030179870A1 (en) | Method for automatically generating a business proposal from an accessible electronic database | |
| CN108959294A (en) | A kind of method and apparatus accessing search engine | |
| CN111767117A (en) | Mobile-end BI middleware technology based on application container | |
| US20050243807A1 (en) | Method of searching a specific computer IP address using telephone number codes and an identification code | |
| CN116048517A (en) | API (application program interface) generating method, system and device based on B/S (browser/Server) architecture application system | |
| US20060129522A1 (en) | Subscription service for access to distributed cell-oriented data systems | |
| KR20020074236A (en) | System for providing Internet phone service by means for sending email including one click juncture icon and method there of | |
| CN104980329A (en) | Address book management method address book management device and mobile agent server | |
| US11144970B2 (en) | Information processing device 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 | ||
| 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. |
|
| CB02 | Change of applicant 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 |
|
| CB03 | Change of inventor or designer information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |