FineBI Version
JAR Package Version
6.0
2019/05/20
Local machine information authentication is the most common authentication method, with simple operations and great convenience.
The physical information of the FineBI's server is fixed. You can export the RIF file to obtain a MAC address and machine code and generate a LICENSE file with unique identification.
You are advised to use the simplest and fastest registration method: Local Container Authentication.
1. Local machine information authentication requires the physical information of the FineBI's server to be fixed. If it is not fixed, this registration method cannot be used.
For example, if you deploy FineBI in a virtual machine environment, the physical information in the virtual machine environment may change, causing registration failure. You need to use other registration methods.
2. A formal LICENSE file can only be registered once on a machine. If you want to register multiple projects on the same machine, you need to purchase multiple LICENSE files.
3. A formal LICENSE file is only applicable to one server. If you want to change the server, you need to conduct registration migration.
4. After update under major version is performed on the same server (such as from V 5.0 to V 5.1), you need to conduct registration migration.
5. You need to ensure that the project uses JDK 1.8 and the minor version needs to be JDK 8u200 or later.
6. The Mac address cannot be set to empty or unlimited, as the official LICENSE file enforces the validation of the MAC address and registration will fail if it is empty.
Open the path %Tomcat_HOME%\webapps\ in FineBI's server and confirm the project name of FineBI Web. The default name is webroot.
You can modify the project name as needed before registration. It cannot be modified after registration.
Modify the project name with caution, as changing it may affect the settings such as hyperlinks of a template.
To change the project name is to change the name of this folder. After modification, the address for accessing the project becomes http://IP address:port/project name/decision.
Log into FineBI as the admin and choose Manage > Registration > Register Now.
Select Local Machine Info as AUTH Method and click Export registration Information.
The exported file name is RegistrationInformation.rif, which stores the version information of the FineBI project.
Use the email address specified in the contract to send the registration information to FineBI business personnel (business@fanruan.com). The email format is as follows.
Indicate the special circumstances (if any) in the email.
List
Content
Note
Priority contact
Contact FanRuan business personnel in advance to confirm relevant matters and sign the contract.
/
Sender
Use the email specified in the contract.
If you do not use the email specified in the contract to send registration information, the registration will not be allowed.
Recipient
business@fanruan.com
Title
Document of Company Name's Registration for FineBI Official Authorization
If you do not mark the company name in the email, the registration will not be allowed.
Body
Company name: {Company Name}
Project name: {Project Name}
Contract signing date: YYYY-MM-DD
Registration method: Local Machine Info
Other information like concurrency and user number will be registered according to the signed contract.
Attachment
The aforementioned exported RIF files
Opening the generated RegistrationInformation.rif file will damage it. If you send the damaged file to FanRuan business personnel, the registration will fail.
Business personnel will generate a FanRuan.lic authorization file for you and email it to you after verification.
Choose Manage > Registration > Version Information, click Upload lic, and import the FanRuan.lic authorization file.
The effect of successful uploading is as follows.
Go to the path %FineBI_HOME%/webroot/WEB-INF/resources and delete the FanRuan.lic file.
Restart FineBI server.
If registration fails, a prompt will pop up:
Click Details to view causes for registration failure. You can troubleshoot according to the specific cause.
Cause
Specific Prompt
Certificate is expired.
Expired Time: 2019/02/22
Version is mismatched
Certified Application Version: 9.0
Local Application Version: 10.0
MAC address is mismatched.
Authenticate MAC address: {address}
Local MAC address: {address}
Machine code is mismatched.
Authentication machine code: {code}
Local machine code: {code}
Application name is mismatched.
Authentication application name: {Application name}
Local application name: {Application name}
The maximum number of authorizations is reached.
The certificate has been used by other projects on the same server.
Engineering content is mismatched.
Authentication project content: {Content}
Local project content: {Content}
In addition to the above causes for failure, other errors will be reported uniformly: The certificate content is incorrect.
When there are multiple causes for failure, all of them will be displayed in the platform.
滑鼠選中內容,快速回饋問題
滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy