Compatibility issues may occur when you migrate a project not deployed via FineOps to a FineOps-deployed one.
You must first confirm the following compatibility considerations before proceeding with migration.
Description
FineOps-deployed projects are built upon standardized FanRuan products.
Custom JARs from secondary development are not guaranteed to function properly after migration.
Solution
1. If the customized JAR files are provided by FanRuan, contact FanRuan technical support personnel to assess the impact of migration on corresponding functions.
2. After migration, verify that the relevant custom JAR files have been uploaded to Project mounting directory/customlib/lib.
3. Confirm that the functions dependent on these JAR files are working as expected.
Plugins not downloaded from the FanRuan market (that is, obtained from third-party channels) are not guaranteed to function properly after migration.
1. If the customized plugins are provided by FanRuan, contact FanRuan technical support personnel to assess the impact of migration on corresponding functions.
2. After migration, confirm that the relevant plugins are installed and enabled under System Management > Plugin Management.
3. Confirm that the functions provided by these plugins are working as expected.
You may have modified the web.xml file in /webroot/WEB-INF/, such as the CAS-related configuration, before migration.
The target project of migration (which is a FineOps-deployed project) does not support the custom web.xml file.
Contact FanRuantechnical support personnel to assess the impact of migration on it.
A FanRuan application may contain custom resources such as CSS, JS, HTML, or image files that are required by the project.
For FineOps-deployed projects, these resource files must be uploaded to Project mounting directory/help.
If uploaded to a non-persistent directory instead of the mounting directory, they will be lost upon restart. Persistent mounting directories include:
Preparing the FineBI Mounting Directory
Preparing the FineReport Mounting Directory
Preparing the FineDataLink Mounting Directory
1. For custom resources (such as CSS, JS, HTML, and image files) required by the project:
Before migration, they might be stored anywhere in /webroot.
After migration, you must manually upload them to Project mounting directory/help, which can be done via File Management.
2. For templates that reference these resource files, you must manually update the resource paths within the templates.
For example, if you have uploaded an A.jsp file, the access path of this resource is http://IP address:Port number/webroot/help/A.jsp.
FineOps-deployed projects only support SSL certificates in the .crt or .pem format issued by official certificate authorities (CA) for the Nginx component. Self-signed certificates are not supported.
Affected functions include, but are not limited to:
Data storage service
LDAP synchronization
HTTPS access to the project
1. If you previously used self-signed certificates generated by the JDK keytool, they will not function after migration.
After migration, you must obtain a formal certificate from a CA to enable SSL.
2. When deploying a new project via FineOps, you must select a FanRuan internal gateway for deployment to install the certificate.
3. After successful migration, configure the certificate manually. For details, see Enabling SSL for O&M Projects.
Operation logs of projects not deployed via FineOps are stored in Tomcat installation deirectory/webapps/webroot/logs/cubes using the Swift engine by default.
For projects deployed via FineOps, if the Elasticsearch component is deployed and enabled, operation logs are stored in Elasticsearch by default.
If you migrate a project using the migration tool, historical log files will not be migrated by default.
Scenario:
For FineReport clusters and FineBI 6.1 deployed via FineOps, Elasticsearch is mandatorily enabled as the log storage service.
For standalone FineReport projects deployed via FineOps, you can enable Elasticsearch as the log storage service.
Description:
For historical operation logs: If backup is required, use the Syncing Platform Logs to Other Databases plugin to export historical logs to a self-prepared database before migration. For details, see Syncing Platform Logs to Other Databases Plugin.
For new operation logs: After migration, the project can no longer access operation logs via a data connection to LogDB. If you need to view project logs, contact FanRuan technical support personnel for assistance. For details about how to contact technical support, see Technical Support Channel Introduction.
For standalone FineReport projects deployed via FineOps, enabling Elasticsearch as the log storage service is optional.
For FineOps-deployed FineDataLink projects, Elasticsearch is not enabled as the log storage service.
If Elasticsearch is not enabled (in which case, LogDB continues to be used for log storage) and historical operation logs need to be retained, use the Syncing Platform Logs to Other Databases plugin to export historical logs to a self-prepared database before migration. For details, see Syncing Platform Logs to Other Databases Plugin.
The security strategies of certain browsers may cause SSO to fail.
For projects not deployed via FineOps, the built-in HTTPS_SameSite_Cross-Domain strategy can resolve this issue.
For FineOps-deployed projects, additional configuration is required for SSO to take effect.
1. First, ensure that SSL is enabled for the O&M project. For details, see Enabling SSL for O&M Projects.
2. Then, follow the steps in the "HTTPS Solution" section of Failed SSO on Chrome.
DingTalk/WeCom integration requires uploading a domain ownership verification file to the root directory of the domain.
The storage location of this file differs before and after migration.
After migration, upload the relevant domain ownership verification file(s) to Project mounting directory/ROOTmanually.
The default homepage built in the FineBI project uses certain custom resources, which may fail to render properly after migration.
1. Upload the Demo_files folder and the Demo.html file in Tomcat installation directory/webroot/ to Project mounting directory/help.
2. Modify the homepage address to help/Demo.html under System Management > Directory Management.
Before migration, you might have enabled access to the project with a short domain name or the IP address by modifying the configuration file.
However, the target project of migration (a FineOps-deployed project) does not support custom configuration files.
Custom modification to files such as web.xml to achieve access with a short domain or the IP address is no longer necessary.
After migration, the logo in the top-left corner of the project may display incorrectly and require manual reconfiguration.
Choose System Management > Appearance Configuration > Platform Style, and re-upload the logo in Platform Logo.
You can download the official default logos:
FineReport Platform Logo.zip
FineBI Platform Logo.zip
The SAP dataset function relies on the sapjco3.jar and sapjco3.dll files. The function only works if these files are correctly located and read.
The file storage path may differ before and after migration, which can cause the function to fail.
After migration, upload the sapjco3.jar and sapjco3.dll files to Project mounting directory/plugins/SAP plugin folder.
You can obtain files by referring to New SAP BW Dataset Plugin.
For details, see FAQs on Project Usage.
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy