V2.11.0
FineOps Basic Edition supported the deployment of FineBI6.1 Basic Edition only.
Some users' servers are short of resources and cannot support the deployment of FineOps Standard Edition.
FanRuan has launched FineOps Basic Edition to address the O&M demands extensively.
This article details the differences between FineOps Basic Edition and FineOps Standard Edition.
FineOps Basic Edition is usually deployed on a server with insufficient resources.
Therefore, FineOps limits the number and type of projects that can be connected to or deployed via FineOps to prevent project crashes due to insufficient resources.
When you deploy a FineBI 6.1 project via FineOps Basic Edition, note that:
App Service Quantity: Only the 1 BI Application(s) + 1 BI Engine(s) option is available. You can deploy no more nodes or engines.
FanRuan Internal Gateway: You can deploy the single-node internal gateway only. The dual-node internal gateway is unsupported.
Node Configuration: You can deploy all components on one main application server with at least 8 CPU cores, 64 GB of available memory, and 100 GB of free disk space.
Deployment List: The default port number of the file service component minio is changed from 9001 to 9005.
Single Table Update: The number of cells with changed data in a single table cannot exceed one billion (calculated by Number of rows * Number of columns), or the update fails.
When you deploy a FineReport/FineDataLink project via FineOps Basic Edition, note that:
App Service Quantity: You can deploy one application only.
FineOps Basic Edition does not support the deployment of clusters.
FineOps Basic Edition supports the connection of one project only.
By default, FineOps Basic Edition does not include the elasticsearch and skywalking_oap components, which renders some functions unavailable. These functions are detailed in the following table.
You can observe the stability status and performance of the system as well as the efficiency of O&M personnel.
You can locate the object (such as dashboards and templates) where a problematic request resides through observation.
You can understand the request traffic between projects and components, which helps troubleshoot issues of performance, connectivity, node balancing, and others.
The performance of each template in the project is summarized and displayed for easier performance management.
The admin can help users collect and analyze the link details in the query request in case of dashboard/report lagging without passively waiting for the users' feedback.
It allows for filtering requests by ID, time, etc., to facilitate further analysis and pinpointing of slow requests and precise identification of issues such as network fluctuations, database performance, abnormal configuration database, complex resources, and resource shortages.
The requirement on the FineOps server configuration is different, as shown in the following table.
Converting FineOps Basic Edition to FineOps Standard Edition cannot be achieved via upgrades or other methods and requires a reinstallation. Determine which edition to be installed carefully before deployment.