I. Overview
Fanruan provides FineReport software free of charge, and users can use this software for functional testing and trial.
The directly downloaded FineReport software contains all the functions, but the number of concurrency is limited. There will be trial information signs when using some functions.
Users can contact FanRuan Business, purchase function points and register according to their own needs. The registered function points can be used, but the unpurchased function points cannot be used.
Note 1: In order to ensure normal use, users are recommended to purchase and register. For FineReport registration steps, please refer to: Local Machine Info AUTH
Note 2: Registration is distinguished by function points. Even if you register, if you do not purchase the corresponding function points, the relevant functions cannot be used. If necessary, you can contact sales for additional purchases.
II. Check whether to register
The administrator logs in to the data decision system and clicks Manage>Registration . If FineReport is not registered, it will display Not Registered when viewing the registration information. As shown below:
III. Impact of unregistered
1. Copyright information
If FineReport is not registered or the registration license has expired, and the user accesses the report or data analysis through the IP or domain name, the copyright information will be displayed at the bottom of the report: Select Fanruan for BI and focus on BI for 15 years. Powered by Fan Ruan. As shown below:
Note 1: Only the JAR package of version 2019-12-05 and later will display the report copyright information.
Note 2: Users access reports or data analysis through localhost, regardless of whether they are registered or not, the copyright information will not be displayed.
2. Concurrency
Concurrent number refers to the number of IPs that are allowed to access the report server at the same time
The number of unregistered concurrency is fixed at 2, that is, only 2 different IPs can access the server at the same time. As shown below:
If the number of IPs accessing the server has reached the maximum concurrent number, users who log in later will not be able to access it.
An error was reported when accessing the project: System is unregistered or number of visitors exceeds limit.
3. Web Application Server
The web application server of the unregistered version will be suspended every seven days, and the report cannot be accessed normally. At this time, the web Application server such as Tomcat needs to be restarted.
If your project is in progress, the above-mentioned unregistered suspension of operation may have a relatively large impact on the project, and even cause unnecessary losses.
Therefore, we recommend that you purchase the FineReport software and use it after registration.
4. Template preview
If the project is not registered, the error message appears randomly when previewing the template: Error Code: 12400002 Need a registration code or the number of users exceeds the limit.
IV. Registration method
It is recommended that users use the simplest and fastest registration method: local Container AUTH.
| Sort | Document | Introduction | Advantages | Disadvantages |
|---|---|---|---|---|
| Server registration | Local Container AUTH | Local container authentication is an authorization method designed for private cloud, virtual server and other non-fixed servers or frequently changing server environments | 1) The physical information of the report project server can be changed 2) There is no need to provide an additional fixed physical information server as an authorization server 3) The client report server can be in the internal network environment without opening the external network port | 1) An official lic file is only applicable to one report project 2) If you need to replace the authorized project, you need to contact the business for registration migration |
| Public Cloud AUTH | Users need to register multiple projects, it is very troublesome to export project information multiple times, and they don't want to build an authorization server locally. Fanruan has built a public cloud authentication server. The client initiates an authorization request by filling in the authentication information and sends it to the public cloud authentication server to verify authorization uniformly. | 1) The physical information of the report project server can be changed 2) There is no need to provide an additional fixed physical information server as an authorization server 3) If the report server IP is not restricted when applying for authorization, you can register on any report server, which is more flexible 4) If the authorized project needs to be replaced, the user does not need to contact the business, and can operate the migration by himself | The client report server must be connected to the Fanruan authorization server through the public network, and customers who are not allowed to open the external network cannot use this registration method. | |
| Local Machine Info AUTH | Obtain the Mac address and machine code of the machine where the report engineering server is located by exporting the rif file Register by binding the Mac address and machine code of the machine where the report engineering server is located | The client report server can be in the intranet environment without opening the extranet port | 1) The physical information of the server where the report project is located must be fixed 2) An official lic file is only applicable to one report project 3) If you need to replace the authorized project, you need to contact the business for registration migration | |
| Private cloud AUTH | When the report project is deployed on a virtual machine or cloud platform, the physical information of the server is not fixed At this time, you can find a server with fixed physical information as the authorization server Bind the report project registration to the server address | 1) The physical information of the report project server can be changed 2) Within the range allowed by the number of authorizations, one authorization server can authorize multiple report servers 3) In the case of clusters, private cloud authentication is used, without each node sending registration information to the business 4) When the report server is migrated, there is no need to reapply for the authorization file, just make sure that the machine where the report server is located and the network of the authorization server can be connected. | 1) The operation is cumbersome 2) Need to provide an additional server with fixed physical information as an authorization server 3) The report server must be able to access the authorized server 4) The authorization server needs to be turned on all the time, otherwise the registration will fail. If Server.exe is closed and reopened, it is unregistered and needs to be operated again | |
| Encryption lock AUTH | For some large projects, the same report project may be published on multiple servers Or users are inconvenient to provide the physical information of the machine where the report project is located, and at the same time they don’t want to build an authorization server locally At this time, you can use the encryption lock to register, and realize the authorization by binding the report application name | The client report server can be in the intranet environment without opening the extranet port | 1) The operation is cumbersome 2) The dongle must always be plugged into the server, once it is unplugged, the registration will become invalid 3) Relying on the specific carrier encryption lock (similar to U disk), which is not conducive to storage 4) This authentication method does not support clusters | |
| Plugin registration | Authorized registration of plugins | Register through plug-ins to reap the benefits for developers Therefore, users can devote more energy to improve the plug-in, and users can also use better and more refined plug-ins, forming a good ecosystem 1) No need to register plug-ins for unregistered projects, all plug-ins are free 2) The plug-in in the registration project can be tried for free for 90 days, after 90 days, plug-in registration is required to use | - | - |
| Cluster registration | Cluster registration- | Based on the registration of "Local Machine Information Authentication", it supports exporting cluster rif files with spliced machine code and MAC address for registration | - | - |
| Register License Migration | Authorized migration plugin | 1) Replace the report server with a server that supports "local machine information authentication" 2) Servers that support the "local machine information authentication" version 10.0 and above can be upgraded across major versions | - | - |
| Local machine information authentication migration | Servers that support "local machine information authentication" versions below 10.0, upgrade across major versions | - | - |
