Overview
Function Description
Local machine info authentication is the most common authentication method, allowing you to complete the authentication easily and conveniently.
The physical information of the server where the FineDataLink project is deployed is fixed. You can export the RIF file to obtain the MAC address and machine code, which are used to generate a license file with a unique identifier.
Notes
1. Local machine info authentication requires the physical information of the server where the FineDataLink project is deployed to be fixed. If the physical information is not fixed, this registration method is not applicable.
For example, if the FineDataLink project is deployed on a virtual machine, the physical information may change, causing the registration to fail. In this case, you need to use other registration methods.
2. A formal license file can be registered only once on a single machine. If you want to register multiple projects on the same machine, you need to purchase multiple licenses.
3. A formal license file is valid for only one server. If you want to change the server, you need to migrate the registration information.
4. Ensure that the project uses JDK 1.8 with the minor version of JDK 8u200 or later.
5. The MAC address cannot be left empty or set to unlimited, as the formal license file mandates MAC address verification. If the MAC address is left empty, registration will fail.
Registration Procedure
Confirming the Project Name
Go to the webapps directory of the Tomcat server where the FineDataLink project is deployed to confirm the project name of FineDataLink Web (which defaults to webroot).
You can modify the project name as needed before registration. After successful registration, the project name cannot be modified.
Note:Modifying the project name may affect settings such as template hyperlinks. Proceed with caution.
You can modify the project name by modifying the name of the webroot folder. After modification, the address for accessing the project becomes http://IP address:Port number/Project name/decision.
Exporting Registration Information
Log in to FineDataLink as the admin, choose System Management > Registration Management, and click Register Now, as shown in the following figure.
Select Local Machine Info as Authentication Method, and click Export Registration Information, as shown in the following figure.
The exported file name is RegistrationInformation.rif, and the file stores the version information of the FineDataLink project.
Emailing Business Personnel
Use the email address specified in the contract and send the registration information to FineDataLink business personnel (business@fanruan.com). The email format is shown as follows.
| Necessary Information | Content | Notes |
|---|---|---|
Primary contact | Contact FanRuan sales personnel in advance to confirm relevant matters and sign the contract. | / |
Sender | Use the email address specified in the contract. | Otherwise, the registration will be rejected. |
Recipient | business@fanruan.com | / |
Title | Company Name Registration for FineDataLink Official Authorization Document | If you do not specify the company name in the email, the registration will be rejected. |
Body | Company name: Company Name Project name: Project Name Contract signing date: YYYY/MM/DD Registration method: local machine info authentication Project version: Specify the minor project version and the JAR package information, which can be found under System Management > Registration Management > Version Information. | Other information like concurrency and the number of users will be registered according to the signed contract. |
Attachment | The aforementioned exported RIF file | Do not open the generated RegistrationInformation.rif file, otherwise, the file will be damaged and cannot be used for registration. |
Obtaining the License File for Registration
After verifying the received email, business personnel will generate a FanRuan.lic file and email it to you.
Choose System Management > Registration Management > Version Information, click Upload License, and import the FanRuan.lic authorization file, as shown in the following figure.
The following figure shows the effect after successful authentication.
Note:
Registration Cancellation
1. Go to the resources directory in the /webroot/WEB-INF path of the FineDataLink project and delete the FanRuan.lic file, as shown in the following figure.
2. Restart the FineDataLink project.
Registration Failure Troubleshooting
If the registration fails, a prompt window pops up with the specific failure reason, helping you troubleshoot problems.
Standalone Project
If the registration fails, a prompt window pops up with the specific failure reason. You can click Details for troubleshooting, as shown in the following figure.
You can click Back to return to the Registration Management page. In the Registration Information area, information about the registration failure and the reasons is displayed. You can click View Error Details for troubleshooting, as shown in the following figure.
Cluster Project
If the registration fails, the reasons may vary across different nodes. A prompt window pops up with the specific failure reason for each node. You can click Details for troubleshooting, as shown in the following figure.
You can click Back to return to the Registration Management page. In the Registration Information area, failure reasons for all nodes are displayed in a list. You can click View Error Details for troubleshooting.
Failure Reason Summary
You can click Details to view the reason for the registration failure and troubleshoot accordingly.
Note:The error message of all other errors not mentioned in the following table is "Incorrect License Format".
If the registration fails for multiple reasons, only the reason for the initial failure will be displayed.
| Failure Type | Failure Reason |
|---|---|
License File Issue | Licence File Corruption or Version Error |
| License Expired on YYYY/MM/DD | |
| License File Destroyed | |
License Upload Issue | License Upload Failure |
| Failed to Upload the License Appendix | |
| Failed to Verify the License File for Upload | |
Hardware Issue | MAC Address Mismatch Local MAC address: MAC Address Authentication MAC address: MAC Address |
Machine Code Mismatch Local Machine Code: Machine Code Authentication Machine Code: Machine Code | |
Environment Issue | There is a conflict in the license-used port Port number. The maximum number of nodes for which licenses can be assigned has been reached. |
Previous：Local Container Authentication
