反馈已提交

网络繁忙

Administrator Operation Guide

  • Last update:  2024-04-02
  • Overview

    Version


    FineBI Server VersionFunctional Change

    6.0

    -


    Application Scenario

    Administrators in the FineBI system are divided into super admins and subordinate admins, and the corresponding responsibilities are shown in the following table.

    Administrator TypeScope  Description

    Super admin

    FineBI System

    It is the administrator account set on the Initialization Setting page. Usually, this role is undertaken by IT personnel in an enterprise who are responsible for coordinating the entire system, configuring users, roles, permissions, etc.

    Subordinate admin

    Sub-data/Sub-system

    Usually, this role is undertaken by administrators of a branch of an enterprise, to whom the super admin assigns certain permission for managing the data, users, roles, permissions, etc. of the corresponding branch/department.

    Super admin can assign some of the system permissions to subordinate admins as needed, such as assigning permissions on departmental business packages to subordinate admins of the corresponding department. Subordinate admins can assign permissions to business personnel/analysts in their department, reducing the workload and the communication pressure on IT personnel at the headquarter. This article introduces the functions and relevant knowledge that administrators need to master.

    Public Data Management

    Data Connection Management

    Before conducting analysis, the administrator (usually the IT personnel) shall prepare the data by defining data connections.

    Log in to the FineBI system as the admin, and click System Management > Data Connection > Data Connection Management. You can add new data connections and edit existing ones, as shown in the following figure.

    The configuration methods of different types of databases differ slightly. For details, see Entry-Level Data Connection Configuration.

    iconNote:

    1. Do not modify the data connection name arbitrarily as an error may occur if the database table fails to find the database. Determine the data connection name in advance. 

    2. If the name of a data connection is changed, you need to reselect the data connection for SQL datasets. You are advised to add basic tables rather than database tables through SQL statements.


    Folder Management

    You need to build a folder hierarchy for public data to group and categorize tables in BI, so that users even those without data analysis backgrounds can quickly access data based on the analysis dimensions and indicators, reducing the obstacle to data analysis and facilitating data update and subsequent permission assignment.

    • Folder hierarchy: The folder hierarchy could include raw data (which can be absent), basic data, and analysis data, and can be further refined by system, business type, user department, and responsible person.

    • Folder naming: Business/System/User Department + Business Package/Table Hierarchy + Data Information (Table Meaning) + Business Package/Table Owner. 

    You can rename, move, update, and delete existing folders in Public Data, and view the update progress of folders promptly.

    Adding Basic Dataset

    You can add tables to these business packages.

    • Data in database tables and SQL datasets are retrieved from the connected database.

    • Data in Excel datasets are retrieved from local Excel files.

    You can help business personnel who cannot write SQL statements process and merge the data in the above three types of tables in My Analysis, and then publish the table to Public Data.

    Data Retrieval Method

    You can switch the table attribute to control the type of datasets created by users, as shown in the following figure.

    Direct-Connected Data

    Direct-connected data refer to the data directly retrieved from the connected database. You no longer need to update data to local if the basic table uses direct-connected data, as all the data are real-time data fetched from the connected database through SQL statements.

    You are advised to fetch direct-connected data through the SQL dataset to reduce the subsequent data processing in FineBI.

    Extracted Data

    Data update in FineBI refers to extracting data from the database and storing them in the engine or a local disk if the local mode is enabled. 

    The data are stored in the %FineBI\webapps\webroot\spider directory.

      Operation
    Notes and Results 

    Table A originates from a database table, and a self-service dataset originates from Table A

    Modify the field name of the database table

    Updating Table A results in an error, and the table is marked as abnormal in red. Table A can be successfully updated after being edited while the self-service dataset cannot be updated. Manually modify the field in the self-service dataset.

    The analysis table B originates from the basic table A. 

    Update the basic table A, then cancel a field without updating table A.

    Table B can be updated normally as Table A is not updated and the configuration remains unchanged. Editing Table B triggers a prompt indicating a lack of permission for unticked fields because permissions are obtained in real time from Table A.

    View the update information of the analysis table.

    The displayed information is about the basic table, and the progress shows the update process of the current table.

    Obtain field types on the table editing page.

    There is no need to retrieve the field types from the database once the table is saved.

       Upload Excel files.

    Temporary files are stored in the path %FineBI\webapps\webroot\WEB-INF\assets\temp_attach and cannot be deleted.

       New fields are added to the database after Table A is updated.

    The newly added fields are visible on the table editing page and are not ticked by default. There is no need to update the table. To obtain corresponding data, tick the field and update the table.

       Escape characters automatically.

    It can be realized only when tables are added for the first time through business packages/databases. Escaping is achieved by identifying remarks of the table names and field names.

       The basic table is updated successfully, but the association fails to be updated.

    In this case, you will not be notified of update failure.

       The basic table is updated successfully, but the analysis table fails to be updated

    In this case, you will be notified of update failure.

       Delete a table or an association.

    The corresponding data storage file will be deleted after an update.

       Set Execute Frequency on Scheduled Update page to Execute Repeatedly, and execute update once every 1 day.

    The update is executed every 24 hours. If you want to perform updates every other day, set the update to be executed every 2 days (48 hours).

       All basic tables of an analysis table fail to be updated

    No update is available for the analysis table. An update failure prompt is displayed on the global update page.

        Update incremental data.

    The SQL statement for incremental updates cannot be empty.

       Change the start day of a week in system management.

    A global update is triggered after you restart the system.

       Update tables with similar update times together.

    Tables that have already been updated are not updated repeatedly.

       -

    Global updates with a frequency of once a day at night are preferred.

       A long interval between updates is preferred.

    If the update content (including associated tables) is relatively little, the update interval can be set to one hour. Otherwise, execute an update every several hours or every day at night.

    Association Between Tables

    Usually, tables in a database are associated. The system automatically reads the association between tables when database tables are added to the business package. You can also manually associate tables if there is no association.

    Setting rules:

    • Values in the 1-end field are not allowed to be duplicated or empty.

    • Avoid using the 1:1 relationship. Use 1:N or N:1 instead.

    • Associating data is not supported in My Analysis. Publish the analysis subject to Public Data where you can associate data.

    • The left and right fields shall correspond one by one.

    • After configuring the field association, click Confirm and Update if you want to extract data. The table will be automatically updated. 

    For details, see Data Lineage.

     

    User Analysis Management

    How do you manage and maintain subjects, data, components, or dashboards created by designers in My Analysis if issues such as errors or excessive disk space usage occur?

    FineBI provides the User Analysis function to super admins for managing all the subjects, data, components, and dashboards created by designers in My Analysis

    Log in to the FineBI system as the admin, click the    icon beside My Analysis, and click User Analysis to view all the subjects created by designers in My Analysis, as shown in the following figure.

    You can perform operations such as Edit, Rename, Delete, Save as Subject, and Export on these subjects, as shown in the following figure.

    iconNote:

    1. You cannot use the data in User Analysis to create components and dashboards, nor can you assign permissions on them.

    2. The analysis created by a deleted designer will be displayed as an analysis of an unknown user.


    You can also view the update progress, data lineage, update content, and set permission inheritance.

    System Management

    Directory Management

    Application Scenario

    You can add, delete, modify, and perform other operations on the directory tree of the system, and can freely adjust the position of directories

    You can mount finished templates onto the directory for viewers to view.

    Function Introduction

    Log in to the FineBI system as the admin, and click System Management > Directory Management. You can add, delete, and modify directories within the scope of permissions, as shown in the following figure.  

    For details, see Directory Management.

    User Management

    Application Scenario

    You can manage the information of platform users, including adding, deleting, and modifying user accounts, and setting the departmental structure, user roles, and user types.

    Function Introduction

    Log in to the FineBI system as the admin, and click System Management > User Management. You can set the name, department, position, and role of users, as shown in the following figure. 

    For details, see User Management.



    Tab

    Explanation

     

    All Users

    Managing users by Synchronize Users in the official version is preferred.

    If a dataset is synchronized, once data in the database change, the user information in the decision-making platform will also change accordingly.

    For details, see Synchronizing Users.

     

    Department

    Users' department and position information is imported during user synchronization and import. 

    You can create departments and positions, and assign positions to users.

    Department hierarchy setting is supported.

     

    Role

    Users' role information is imported during user synchronization and import. 

    You can create roles and assign roles to users.

    Department hierarchy setting is not supported.

     

    Platform User

    To limit the number of concurrent views and edits and the amount of data used in the analysis, and speed up the calculation and presentation, divide users into viewers and designers.

    Viewer: Can view dashboards, but cannot edit or process data.

    Designer: Can view, call, edit, and publish data, components, and dashboards.

    For details, see Platform Users.

    Permission Management

    Application Scenario

    It contains the security rules and policies of the system to ensure that users can only access authorized resources.

    Function Introduction

    Log in to FineBI as the admin, and click System Management > Permission Management. You can set all permissions of this

    system, as shown in the following figure.

    • Permission carrier: The object to which permissions are assigned, including departments, roles, and users.

    • Permission entity: The assigned permission item, including personnel management, directory management, system management, data connection, task schedule, data permission, and sharing permission. 

    • Permission type: The type of permissions assigned to users/subordinate admins, including view, export, use, edit, management, and authorization.

    For details, see Permission.


    Publication Management

    Application Scenario

    If a dashboard is finished, it needs to be published in the directory for others to use.

    Function Introduction

    Log in to the FineBI system as the admin, and click System Management > Publication Management. You can quickly publish the template applied for publication within the scope of permission to the authorized directory.

    For details, see Publication Management.

    Registration Management

    You can view the version information of the decision-making platform and the list of purchased functions. 

    For details, see Registration Management.

    Intelligent O&M

    This module introduces solutions for common O&M and monitoring scenarios to help users in operating, maintaining, and monitoring FineReport and FineBI.

    The solution applies to FanRuan systems that have been deployed. It introduces the daily maintenance, management, and monitoring methods of FanRuan applications in detail. 


    附件列表


    主题: System Management
    Previous
    Next
    • Helpful
    • Not helpful
    • Only read

    feedback

    鼠标选中内容,快速反馈问题

    鼠标选中存在疑惑的内容,即可快速反馈问题,我们将会跟进处理。

    不再提示

    10s后关闭