Accessing FineBI Through the HTML5 Terminal

Version

Application Scenario

This document introduces how to view FineBI dashboards or projects on the HTML5 terminal such as the browser.

Plugin Installation

To access FineBI on the HTML5 terminal, you need to install the HTML5 Mobile-Terminal Display plugin and the BI6.0 Mobile-Terminal Layout and Editing Page H5 plugin.

Choose System Management > Plugin Management as the admin, search and install the above two plugins, and upgrade them to the latest version.

Accessing FineBI Through the Mobile Terminal

Note:

When accessing the corresponding link on the mobile terminal, ensure that the mobile terminal is in the same network as the PC.

The following table describes the link format when you access FineBI on a mobile device.

The following sections show some examples.

1. Login Page

The link for FineBI on PC is http://localhost:37799/webroot/decision.

When accessing FineBI on the mobile terminal, you need to modify the link to http://172.16.2.134:37799/webroot/decision.

2. Directory Page

The directory link for FineBI on PC is http://localhost:37799/webroot/decision#management/directory.

When accessing FineBI on the mobile terminal, you need to modify the link to http://172.16.2.134:37799/webroot/decision/url/mobile#/directory.

Note:

When accessing the directory page for the first time, you need to log in to the system. If the token exists in the cache, you can directly go to the directory page.

3. Single Dashboard

You can also directly access a single dashboard through a link, which can be obtained on PC through the preview link and the public link.

The link obtained through the above two ways needs to be modified to the specified format before you access a single template on the mobile terminal.

Preview Link

When previewing a dashboard on PC, you can directly obtain the preview link (for example, http://localhost:37799/webroot/decision#/analysis/own/subject/e5c58a91c26143299551ba73d856242f/report/c2594718581f493f951f055b0f3122f6) of the dashboard on the browser address bar.

Note:

c2594718581f493f951f055b0f3122f6 at the end of the link represents the dashboard ID, which will be used in the link for the mobile terminal.

When accessing the dashboard on the mobile terminal, you need to modify the link to http://192.168.43.102:37799//webroot/decision/url/mobile/bi/view?id=c2594718581f493f951f055b0f3122f6, which includes the dashboard ID.

Public Link

You can also share the dashboard with others through the generated public link, as shown in the following figure.

For example, the generated public link on PC is http://localhost:37799/webroot/decision/link/pUHK.

When accessing the dashboard on the mobile device, you need to modify the link to http://192.168.43.102:37799/webroot/decision/link/pUHK.

When accessing a dashboard or a project on the HTML5 terminal, you can add parameters at the end of the URL to achieve some special effects. The following table describes the writing syntax and functions of parameters.

Left Arrow Appearing Below the Dashboard

Since the browser window is too wide, the system displays the template in horizontal mode. Therefore, a left arrow appears below the template when you preview a template on the HTML5 terminal.

You can change the size of the browser window to solve this problem.

Disabling the Developer Program

You can disable the developer program on the HTML5 terminal. You can manually disable the product improvement program joining option to further protect your privacy security.

The super admin can disable the product improvement program joining option through the FINE_CONF_ENTITY Visual Configuration plugin. After completion, restart the server for the setting to take effect.

Note:

For details about how to modify common table parameters, see "Parameter configuration" in FINE_CONF_ENTITY Visualization Configuration.

Viewing the Dashboard Failure

Problem

The dashboard created on PC cannot be viewed on the mobile terminal. An error indicating that the template has already been deleted appears.

Cause

The license is not registered.

Solution

You can refer to the document Local Machine Information Authentication to register the license.