Installation Guide - Fusion Server

Welcome to the Fusion Server Installation Guide!

This manual has been designed to guide you through all the necessary steps to configure and install the Fusion Server, ensuring it operates efficiently and securely. Whether you are an experienced IT administrator or new to the platform, you will find clear and detailed instructions to help you successfully complete the installation.

Throughout this guide, we will cover technical requirements, essential configurations, and best practices for server deployment. Additionally, we will include useful tips to avoid common issues and provide practical examples to tailor the installation to your specific needs.

Our goal is to provide a comprehensive and easy-to-reference resource to make the process as simple and straightforward as possible. If you need additional support, our team is available to assist you. Any questions related to this manual can be addressed by opening a ticket in our Customer Portal.

Get ready to start your setup and make the most of the benefits that Fusion has to offer!

Attention

For any application installation—whether related to server prerequisites, workstation requirements, or the Fusion solution—be sure to carefully read and review the notes.

Minimum Installation Requirements

For Fusion to be installed correctly, certain minimum hardware and software configurations must be met, both on the server and on user workstations.

Server

The minimum requirements described in this guide ensure that Fusion operates properly during the initial deployment, preventing issues such as slow performance or system crashes. However, the server where Fusion will be installed must be scaled according to the volume of files and data that will be stored over time.

The specifications listed here represent only the initial requirements. As platform usage increases, additional server resources may be required, since the accumulation of files and information can impact performance if resources are insufficient.

We recommend acquiring the sizing service to ensure proper resource allocation based on your specific needs. This service analyzes factors such as the number of users, data volume, and advanced functionalities to help ensure that the server can support the growth and operational demands of your environment.

Additionally, it is highly recommended that Production and Staging environments be configured on separate servers, along with their respective databases. The requirements listed below apply to a single environment. If you plan to install both environments on the same server, you will need to double the specified resources. However, the best practice is to maintain each environment on distinct servers.

Another important recommendation is to keep the database on a separate server from the Fusion server whenever possible to improve performance.

Attention

Make sure to install the version compatible with your operating system, as some applications provide different download options for 32-bit and 64-bit systems.

Components	Requirements
Disk	At least 8 GB of free disk space for installation.
RAM	8 GB (if the database is on the same server, 16 GB is recommended).
Processor	Quad-Core processor (preferably with 2 cores).
Operating System	Windows Server 2012 or later.
Database	SQL Server 2022 or later. Oracle 19c, 21c and 23ai. MySQL 8.0.x (any version within the 8.0 series).
Software	Java OpenJDK-21 (or a higher version within 21.X.X). Apache Tomcat 10.1 (or a higher version within 10.1.X). Microsoft Office 2013 or later. LibreOffice 7.3.7.2 (for Standard or Distributed Document Converter). GhostScript 10.05.1 (for Standard or Distributed Document Converter). Edrawings 2019 (for Distributed Document Converter).

Attention

Other databases, such as PostgreSQL or MariaDB, are not recommended, as they may experience performance issues over time.

Database

The approved databases are Microsoft SQL Server, Oracle, and MySQL. However, there are some necessary requirements to ensure that the Fusion database operates without errors.

• The database's collation must be Case Insensitive.
• For using Fusion in Portuguese, it is recommended to use an Accent Sensitive collation.

Information

If you wish to use Fusion in another language, consult the database documentation to check for the appropriate collation.

Attention

Do not create views or tables manually in the Fusion database. Modifying the structure may affect the platform's functionality and compromise future updates. If you need to store additional information, we recommend exploring other alternatives or contacting support for guidance.

Workstation

To ensure that Fusion operates correctly on user workstations, it is important to meet the minimum hardware and software requirements listed below. These requirements are designed to provide adequate performance and stability while using the system.

Components	Requirements
Disk	150 MB of free disk space.
RAM	2 GB.
Processor	Dual-Core or higher.
Operating System	Windows 10 or later.
Software	Microsoft Office 2013 or later. LibreOffice 7.3.7.2.
Resolutions	1024 x 768 or higher.
Browsers	Google Chrome 110.0 or later. Microsoft Edge 110.0 or later. Safari 15.4 or later.

Ensure that the workstations meet the requirements above to guarantee the best possible performance when using Fusion. Software compatibility and screen resolutions are also essential to avoid issues when using the system.

Fusion Mobile

To ensure that Fusion runs properly on mobile devices, users must meet the minimum operating system requirements, as outlined below. Support for the latest versions of Fusion Mobile provides an optimized experience and full functionality.

System	Requirements
Fusion	4.0.0 or later.
Android	7.0 to 16.0 (or later within version 16 (16.X.X)).
IOS	11.0 to 26.0 (or later within version 26 (26.X.X)).
Fusion Mobile	version 1.16.0

Attention

We recommend using more common devices and brands available on the market.

If you have a very specific model and encounter issues, even with the operating system versions certified by Fusion, please contact our support so we can arrange or your device to be sent for analysis, allowing a more detailed evaluation based on the specifics of your device.

Installing Fusion

This guide is intended for IT professionals and system technicians with experience in information technology, who will be responsible for installing the Fusion Platform. While some installation processes are standard, prior experience will be essential to ensure proper configuration and operation of the solution.

Our goal here is to describe, in a clear and step-by-step manner, all the procedures necessary to install the Fusion Platform. This guide covers everything from the initial steps to the final configuration of the platform on the various supported versions.

To install and update the solution, no complex procedures such as creating tables or fields in the database will be required. The application server will automatically update the database during the initial deployment of the application. The only essential requirement is that the database is already created, accessible, and that the user has the necessary permissions to alter the schema.

Standard Folder Structure

To ensure the correct operation and organization of files related to Fusion, it is highly recommended to create the following folder structure in the directory. This organization will help manage the files and contribute to system efficiency:

• Folder 1: C:\neomind
• Folder 2: C:\neomind\fusion
• Folder 3: C:\neomind\fusion\storage
• Folder 4: C:\neomind\fusion\WebContent
• Folder 5: C:\neomind\fusion\work

1. Folder neomind: This will be the main folder where all files related to Fusion Platform will be stored. It serves as the root directory for both the Fusion and Neomind structure. Inside this folder, we will organize the essential files needed for the system's operation.
2. Folder fusion: Within the neomind folder, create a subfolder called fusion, which will be the centralized location for all files and downloads related to Fusion. Example: installation packages, configuration files, etc. This folder will contain the following subfolders:
   • Folder storage: This folder will be used to store the Fusion database information. It is crucial for the platform's operation and must never be deleted. If removed, important data such as modeled process information or published documents will be lost.
   • Folder WebContent: The WebContent subfolder will be used to store the Fusion package (the necessary files to run the application) and the database configuration file. This facilitates the organization and quick access to the files needed to configure and maintain the application.
   • Folder work: The work folder will be used to store temporary files generated during the execution of Fusion. These files are used for temporary processes and can be deleted whenever necessary without affecting system operation. For example, log files or temporary files generated during data processing.

All files from downloads related to Fusion should be stored in the C:\neomind\fusion folder to ensure organization and proper system functionality.

Attention

It is essential that the installation and configuration of the requirements be performed by an administrator user of the server to ensure that all installations and adjustments are applied correctly.

Installing the Fusion Package

Fusion is provided as a .war file. This type of file works similarly to a .zip file, meaning it is a compressed file that contains the entire structure necessary for the application. However, unlike regular files that can be fully extracted, the .war file is designed to be deployed directly to an application server, such as Apache Tomcat.

⚠️ Important: The fusion.war package should not be fully extracted. The application server needs this format to manage the execution of Fusion correctly. Only one file inside it, the application.yml, should be extracted to allow database configuration.

The fusion.war file can be obtained from the Neomind Portal by accessing the Downloads > Versions menu.

Once downloaded, it is recommended that the file be stored in the WebContent folder, as directed in the section about the folder structure.

To configure the database, it is necessary to extract only the application.yml file from inside the .war package.

To do this, open the fusion.war file using an extraction software like WinRAR or 7-Zip, navigate to the path WEB-INF/classes/application.yml, select the application.yml file, and click "Extract To". Note that only the application.yml file should be extracted.

The file should be extracted to the same folder where the fusion.war file is located, i.e., inside the WebContent folder.

After selecting the correct location, press "OK" to complete the extraction.

Once this step is completed, the user can proceed with configuring the other components necessary for the proper functioning of Fusion.

Configuring the application.yml

The application.yml file contains essential configurations for Fusion to function correctly, such as the database connection and the file storage paths. Properly following these steps ensures that the application runs without errors.

Configuring the Database

For Fusion to store and access data properly, it is necessary to configure the connection to the database within the application.yml file.

To configure the database, open the application.yml file using a code editor with administrative privileges, locate the section corresponding to the database you will use, and configure the parameters correctly.

• url: Provide the IP address and the port used to connect to the database. By default, the value is 127.0.0.1:1433, meaning the database is running on the local server on port 1433. In databaseName, enter the name of your database.
• username: Define a user with administrative permissions on the database.
• password: Enter the password for the database user.

📌 Example of database configuration in application.yml.

Note

The user configured in the application.yml must have full permissions within the database. This is necessary for Fusion to create its tables and routines automatically.

💡 If you are using a database other than Microsoft SQL Server, remove the comment from the corresponding configuration and comment out the default configuration.

📌 If using MySQL, the configuration should follow this example:

📌 If using Oracle, the configuration should follow this example:

Attention

For the proper functioning of the OLAP server in Oracle databases, in the application.yml settings it is mandatory to configure the username and schema with the same value.

Configuring Storage Folders

In addition to the database configuration, it is necessary to define where Fusion files will be stored on the server.

For this, in the application.yml file, locate the configuration related to storage and define the folder path where the Fusion files will be saved.

Within the application.yml file, there is a configuration representing the folder where all the Fusion storage folders will be created.

If you followed the recommended folder structure in this guide, simply copy and paste the path:

C:\\neomind\\fusion\\storage

If you have changed the directory, adjust this path as needed.

Attention

Always use two backslashes (\) as folder separators.

📌 Example of the Configuration in the File:

After completing the configurations in application.yml, save the file and close the editor.

Now, your Fusion is ready to be connected to the database and store files correctly! 🚀

Customizing the Name Displayed in the Authenticator

If your environment uses the two-factor authentication feature, you can customize the name that appears in the authenticator app.

By default, the displayed name will be Fusion Platform, but you can change this to something more representative of your organization or environment.

To do this, add the appName property under the authentication.twoFactor key in the application.yml file, as shown in the example below:

authentication:
    twoFactor:
        appName: Desired Name

As a result, the name displayed in the authenticator app will be the value defined in appName.

Installing Java OpenJDK

For proper operation, Fusion requires Java OpenJDK 21 (or higher versions within the 21.0.X series). The OpenJDK is an essential runtime environment for Java applications, ensuring compatibility and expected performance for the platform.

Downloading OpenJDK 21

OpenJDK can be downloaded directly from the official Adoptium website by accessing the following link: Download OpenJDK 21.

When downloading, choose the version compatible with the server's operating system.

Note

For Windows, it is highly recommended to download the version with the .msi extension, as this format includes a graphical installer that makes the setup easier and avoids manual errors. If you download a .zip file, you will need to manually configure the Java environment, which can be more complex.

Installing OpenJDK

After downloading, run the .msi file to start the installation process. Follow the on-screen instructions to complete the installation. The installation wizard will automatically apply the recommended default settings. After completion, OpenJDK will be ready to use on the server.

With this, the Java environment will be properly configured, allowing for the seamless installation and operation of Fusion.

Installing Apache Tomcat

Fusion uses Apache Tomcat as the application server to process its requests. To ensure compatibility and stability, Fusion is certified for all 10.1.X versions of Tomcat.

We recommend always using the latest version within the 10.1 series to ensure security and better performance.

Downloading Apache Tomcat

To download the latest Tomcat 10.1 version, go to the official site: Download Apache Tomcat 10.1.

On the downloads page, select the "Windows Service Installer" option, as this version includes a graphical installer that simplifies the setup and avoids the need for manual adjustments.

Installing Apache Tomcat

After downloading the installer, run the file and follow the installation wizard instructions.

During installation, a screen will appear to configure the Java Virtual Machine (JVM). At this point, change the path to the folder where OpenJDK was installed, as per the instructions in this guide.

Configuring the Tomcat Server

Once Apache Tomcat is installed, you'll need to make adjustments to the configuration file to ensure the proper functioning of Fusion.

These configurations involve adjusting ports, permissions, and references to the directories where the Fusion files are stored.

Configuring the server.xml File

The server.xml file contains the main configurations for Tomcat and needs to be adjusted as follows.

Navigate to the Tomcat installation directory and go to the conf folder. Open the server.xml file using a code editor, such as Notepad++, in administrator mode. This is necessary for the changes to be saved correctly.

In the server.xml file, locate the Connector configuration. This section defines how Tomcat will receive HTTP requests. Add the following parameters inside the Connector tag:

maxPostSize="-1"
discardFacades="false"

• The maxPostSize="-1" parameter ensures there is no limit to the size of POST requests, preventing errors when sending large files to Fusion.

• The discardFacades="false" parameter is necessary to avoid connection failures with FusionBox.

📌 Example configuration inside the Connector:

Note

If another application is already using port 8080, you will need to change it to a free port. To do so, modify the port parameter with a free port, as this is where the Fusion server will run.

Attention

To ensure the proper functioning of features that involve sending large amounts of data in the HTTP header, it is necessary to include the following parameter in the Tomcat Connector(s):

maxHttpHeaderSize="10000000"

This adjustment increases Tomcat’s default header size limit, preventing errors during operations that require sending a high volume of information in the request header. If Tomcat has more than one Connector, the parameter must be added to all of them.

Note

To optimize your Fusion server's performance, you can enable HTTP compression or configure NGINX as a reverse proxy.

HTTP compression reduces the size of data transmitted between the server and clients, improving response time and bandwidth usage. To enable HTTP compression, add the following code snippet to the Connector attribute in the server.xml file of Tomcat:

compression="on"
compressionMinSize="2048"
noCompressionUserAgents="godzilla"
compressableMimeType="text/html,text/xml,text/plain,text/css,text/javascript,text/x-component"

📌 After the change, the Connector attribute should look like this:

HTTP compression will help reduce page loading times and optimize network usage in your Fusion environment.

Tomcat must be configured to correctly locate the Fusion files. To do this, within the Host tag, you'll need to add a Context configuration.

Add the following snippet inside the Host tag:

<Context crossContext="true" debug="0" 
         docBase="C:/neomind/fusion/WebContent/fusion.war" 
         path="/fusion" 
         reloadable="false" 
         workDir="C:/neomind/fusion/work" 
         previleged="true"/>

📌 Example configuration inside the Connector:

📌 Explanation of Parameters:

• docBase="C:/neomind/fusion/WebContent/fusion.war: Indicates the location of the fusion.war package. If you followed the recommended folder structure in this guide, simply copy and paste this line. If you changed the directory, adjust this path as needed.
• path="/fusion": Defines the URL for accessing the system. For example:
  • If set to /fusion, access will be made via *http://localhost:8080/*fusion.
  • If changed to /fusion_cliente, access will be *http://localhost:8080/*fusion_cliente.
• workDir="C:/neomind/fusion/work": Specifies the directory where Tomcat will store temporary files for the system. If you followed the recommended folder structure, this path is already correct.

After making all the changes, save the server.xml file and close the text editor.

Configuring Tomcatw

Navigate to the bin folder within the Tomcat directory and run the Tomcatw file.

In the configuration panel, select the Java tab and add the following parameters in the Java options field:

📌 Required Parameters:

• Define the external configuration file

-Dfusion.configuration=C:\neomind\fusion\WebContent\application.yml

This allows Fusion to load configurations from the application.yml file externally to the war file. If this parameter is not added, the file inside the project will be used.

• Define default UTF-8 Encoding

-Dfile.encoding=UTF-8

This ensures that the application uses UTF-8 as the default encoding to avoid accent and special character issues.

• Parameter to Disable Database Cache

-Dfusion.ignore.db.cache=true

This parameter is essential to prevent issues related to system freezing when creating or editing form fields. It temporarily disables the internal database cache used by Fusion, helping to avoid inconsistent behavior in specific scenarios.

• Access permissions to internal Java APIs (Reflection)

--add-opens=java.base/java.lang=ALL-UNNAMED
--add-opens=java.base/java.math=ALL-UNNAMED
--add-opens=java.base/java.util=ALL-UNNAMED
--add-opens=java.base/java.util.concurrent=ALL-UNNAMED
--add-opens=java.base/java.net=ALL-UNNAMED
--add-opens=java.base/java.text=ALL-UNNAMED
--add-opens=java.sql/java.sql=ALL-UNNAMED

These parameters allow Fusion to access internal parts of Java that are necessary for the operation of libraries such as FSTConfiguration. Without them, the system may fail when attempting to perform operations that depend on these accesses.

Attention

The FusionBox relies on internal Java accesses and reflection operations to function correctly. Starting from Java 9, these accesses are restricted by default for security and modularity reasons. If the parameters above are not configured, Java will block these accesses, preventing the FusionBox from starting.

🔐 Security Parameter (Optional):

• Force the use of HTTPS (If an SSL certificate is configured)

-Dfusion.strictTransportSecurityType=true

This automatically redirects all HTTP connections to HTTPS, enhancing the application's security.

• Keep the default without redirection to HTTPS

-Dfusion.strictTransportSecurityType=false

This keeps the default configuration without forcing HTTPS.

🎛 Optional Parameters for Customizations:

• Load external customization file

-Dfusion.custom=file:\C:\neomind\fusion\WEB-INF\classes\META-INF\customflags.properties

Allows defining customization files externally to the project's war file. If not configured, the internal default file will be used.

• Define external log file

-Dlog4j.configurationFile=file:\C:\neomind\fusion\WEB-INF\classes\log4j2.xml

This allows the log file to be managed externally to the project's war file. If not added, Fusion will use the internal log file.

• Enable process hierarchy search

-Dfusion.enable.hierarchy.search=true

This allows simple process queries to use inheritance to find related processes.

📄 Document Conversion Parameter: (Required if using Microsoft Office for conversion)

• Define auxiliary folder for document conversion

-Djava.io.tmpdir=C:\neomind\fusion\converter

Defines an auxiliary folder for document conversion, avoiding issues with folder names containing spaces.

Attention

Before adding this parameter, create the converter folder at the following path: C:\neomind\fusion\converter, following the folder structure outlined at the start of this guide.

🕒 Parameters to Improve Timer Performance (Optional – Recommended for environments with a high volume of processes)

These parameters allow timers to run in parallel, reducing delays when many events are scheduled at the same time. They are optional but can improve performance depending on the server’s capacity.

• Number of simultaneous timer executions

-Dfusion.scheduler.number-background-threads=6

Defines how many timers can run at the same time, allowing multiple scheduled actions to be processed simultaneously.

• Fusion default value: 2

• Allowed value: 1 to 20

• The higher the value, the more events can run in parallel — provided the server can handle it.

• Prioritize timers

-Dfusion.scheduler.prioritize-deadlines=true

When enabled, Fusion prioritizes executing timers before other internal system jobs (such as scheduler tasks).

• Default: false
• Recommended only when there are many accumulated timers or noticeable delays.

Attention

These parameters are optional and should be adjusted according to server performance. Using a very high number of threads on servers with limited CPU can cause overall slowness. Before applying in production, we recommend testing in a staging environment.

If Tomcat is configured as a service on Windows, add the following parameters in the Java 9 Options field to avoid compatibility issues:

--add-opens=java.base/java.lang=ALL-UNNAMED
--add-opens=java.base/java.math=ALL-UNNAMED
--add-opens=java.base/java.util=ALL-UNNAMED
--add-opens=java.base/java.util.concurrent=ALL-UNNAMED
--add-opens=java.base/java.net=ALL-UNNAMED
--add-opens=java.base/java.text=ALL-UNNAMED
--add-opens=java.sql/java.sql=ALL-UNNAMED
--add-opens=java.base/java.io=ALL-UNNAMED
--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.code=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.comp=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.main=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.model=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED
--add-opens=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED
--add-opens=java.base/java.lang.reflect=ALL-UNNAMED

These options ensure compatibility with newer versions of Java and prevent errors when starting the Tomcat service.

Memory Adjustment

To ensure proper performance for Fusion, adjust memory allocation in the Java tab:

• Initial memory pool: 512 MB
• Maximum memory pool: 4096 MB

This way, Apache Tomcat will start with 512MB of the server's memory, and its maximum memory usage will be 4096MB.

Attention

This is the recommended minimum configuration. If smaller values are used, the application may experience slowdowns or crashes.

Startup Adjustments

To ensure Tomcat starts correctly when the server is powered on, make the following adjustments:

In the Log on tab, select Local System Account.

In the General tab, change the Startup type field to Automatic.

This ensures that Tomcat starts automatically when the server is turned on.

Cleaning the webapps Folder

Navigate to the Tomcat installation folder, go to the webapps folder, and remove all content.

Removing this folder prevents conflicts between older versions or other applications and the new Fusion installation.

With these configurations, Tomcat will be ready to run Fusion optimally and securely! 🚀

Starting the Server

Now that Apache Tomcat is configured, it's time to start the server so that the Fusion Platform becomes available.

To do this, open the Start menu in Windows and search for Services. In the list of services, locate Apache Tomcat. Select it and click the Start option, as shown below:

This will start Tomcat, making the Fusion Platform accessible.

Accessing the Fusion Platform

Once the service has started, open your preferred browser and go to the following address:

http://<server>:port/fusion

Best Practice

We recommend setting up a task scheduler on the server to restart the Fusion service at least once a week. This is a good preventive maintenance practice that helps release any stuck threads or sessions, ensuring greater stability and performance of the environment.

If everything was configured correctly, you will see the Fusion Platform login screen! 🚀

🔑 Initial credentials:

• Username: adm
• Password: adm

When accessing the Fusion Platform for the first time, you will be required to reset the Administrator password. The new password must meet the platform's security requirements.

If you have any questions or encounter issues, review the previous steps to ensure that all configurations were applied correctly. If everything is set up correctly but the Fusion Platform still does not start, we recommend opening a support ticket in our Customer Portal, providing details of the actions taken and any errors encountered. Our team will be available to assist you in resolving the issue.

Installation of Components for Document Converter

The Fusion document viewers (Universal Viewer and PDF Viewer) convert all supported formats, including PDF, Word, and Excel documents, among others. The conversion is initially performed into an internal format and then into an external format, which is displayed directly on the screen through a Fusion page. To enable this functionality, the following components must be installed:

• LibreOffice installation as a converter for Office suite applications such as Word, Excel, PowerPoint, etc. It must be installed in both the standard and distributed conversion configurations.
• GhostScript installation as a converter for PDF and image files. Like LibreOffice, it must be installed in both configurations.
• eDrawings installation as a converter for AutoCAD files. This component is optional and should only be installed in the distributed converter configuration.

Note

If needed, it is also possible to convert .doc and .docx files by installing Microsoft Office.

Document Conversion Configuration

Fusion offers two configuration options for document conversion: Standard and Distributed.

• Distributed Conversion: Allows Fusion to use dedicated external servers to process document conversion, improving performance by offloading resources from the main Fusion environment. In this setup, Fusion is not responsible for document conversion; instead, an external converter handles the process, preserving resources specifically allocated for Fusion and enhancing overall performance. For more details on how to configure this option, refer to the Configuration Guide - Distributed Document Converter.
• Standard Conversion: Performs document conversion using the resources of the Fusion environment itself. In this configuration, eDrawings cannot be used, meaning that AutoCAD file conversion is not supported.

Installing LibreOffice

To download LibreOffice, visit: Download LibreOffice.

Once the download is complete, proceed with the standard installation by following the on-screen instructions.

Installing GhostScript

To install GhostScript, visit: Download GhostScript.

After downloading, follow the standard installation process as instructed on the screen.

Installing and Configuring Microsoft Office

If you choose to use Microsoft Office and have a valid license, follow the standard installation process and configure the settings below.

Attention

Using Microsoft Office as a document converter requires an additional parameter configuration in Tomcat. For more details, carefully read the instructions in the section Configuring Tomcatw of this guide.

Attention

When enabling document conversion with Microsoft Office, only .doc and .docx files will be converted using it. All other file formats will continue to be processed by LibreOffice.

Note

If you encounter any permission-related issues during the final configuration of Microsoft Office, we recommend reinstalling the Office package.

For Fusion to use Microsoft Office as a document converter, the Microsoft Word service must be configured with a specific user. Follow the DCOM configuration steps below:

In the Run menu on Windows, type dcomcnfg, and press Enter. In the "DCOM Config" folder, locate "Microsoft Word 97 - 2003 Document".

Right-click and select Properties. Then, go to the Identity tab and select This user. Enter the username and password that will be used by DCOM and the Fusion service.

Attention

The configured user must be a local administrator and must have logged in interactively to create the profile required by Word for document conversion.

In Microsoft Word, enable the option “Update fields before printing” by navigating to File > Options:

In the Display tab, select the indicated option:

Click "OK" to finalize.

In Fusion, enable the option “Use Microsoft Office” in the system settings.

Configuring Document Conversion in Fusion

After installing the required components, configure Fusion to use the converters according to your environment's needs.

Log in to Fusion and navigate to Administration > System.

The relevant document converter settings are:

• Distributed: Select Yes to allow conversion to be performed by external servers.
• Use Microsoft Office: Select Yes to use Microsoft Office as the default software for opening .doc and .docx files. Otherwise, the system will use LibreOffice to open these files.
• Conversion Threads: Specify the number of parallel conversions to be performed.
• Cache Folder: Specify the folder path where converted documents will be stored.
• PDF to Image Converter Command Line: Specify the GhostScript path pointing to the executable. If GhostScript was installed in the default location, it is likely found at:

C:\Program Files\gs\gs10.00.0\bin\gswin64c

• LibreOffice Path: Specify the LibreOffice path pointing to the executable. If LibreOffice was installed in the default location, you can find it at:

C:\Program Files\LibreOffice\program\soffice.exe

• Customization Adapter: Insert any custom configurations as needed.
• File Viewing DPI Quality: This option allows users to set the resolution at which files should be displayed. Users can choose a resolution between 100 and 150 DPI or select the Automatic option.
• Enable OCR* in Documents: Select Yes to enable image-based text recognition within documents, allowing searches for terms inside uploaded files. Selecting No will disable this feature.
• Distributed OCR: Select Yes to separate OCR from the File Converter, making it independent. This allows OCR to be distributed outside of Fusion. Selecting No will keep OCR integrated within the platform. If you select Yes, you must configure the server to ensure distributed OCR functions properly. For more details, refer to the official manual: Distributed OCR.

Attention

The accuracy of OCR searches depends on the document quality. The ideal recommendation is to use documents with a 300 DPI resolution, ensuring a 95% accuracy rate.

If the document quality is around 200 DPI, the accuracy drops to 82%. At 150 DPI, the accuracy falls to 49%. This indicates that the closer the document quality is to 300 DPI, the higher the search accuracy will be.

With these configurations, Fusion will be ready to efficiently handle document conversion. 🚀

Customizations

The Fusion Platform allows the implementation of customizations to meet your company's specific needs. However, to ensure these customizations work correctly, some additional configurations are required. Below, we detail the essential steps to properly configure the system's files and parameters.

Configuring customflags.properties

The customflags.properties file is essential for activating customizations within the Fusion Platform. To configure it correctly, follow the steps below:

Open the Fusion .war file and navigate to WEB-INF\classes\META-INF. Locate the customflags.properties file and extract it to the WebContent folder created earlier in this guide.

Edit the file using a code editor and enter your company's name, as defined during the customization development, followed by the true parameter.

After making the changes, save and close the file.

Attention

The customflags.properties file must remain outside the .war file, just like application.yml. Modifying the .war file is not recommended, as it may compromise the system’s integrity.

Configuring Tomcatw

In addition to setting up customflags.properties, you must adjust the Tomcat server parameters to ensure the proper functioning of customizations.

During the server configuration, access the Java Options section and review the parameters added. Some are mandatory, while others are optional.

If your Fusion Platform installation includes customizations, you must add the following parameter:

-Dfusion.custom=file:\C:\neomind\fusion\WEB-INF\classes\META-INF\customflags.properties

This parameter ensures that Tomcat correctly locates and loads the customization settings.

By following these steps, your customizations in the Fusion Platform will be properly configured and ready for use. Make sure the files are in the correct location and that Tomcat is set up correctly to avoid issues when applying customizations.

Final Steps

Once all configurations are completed, you must activate the Fusion Platform license to ensure its proper operation. Additionally, there are optional services that can be installed to enhance the platform's capabilities. Below, we detail the steps for license activation and the installation of complementary services.

Activating the License

After completing the configurations, Fusion must be activated. The activation key can be requested from our support team by opening a ticket on the Customer Portal.

To activate the license, navigate to: Administration > License Control.

Next, click on "Activate now" to open the activation screen.

Enter the CNPJ and the activation key provided by the support team. Once this step is completed, the environment will be fully activated and ready for use.

Installing Additional Services

Beyond the core configuration, you can install additional services to extend the Fusion Platform functionalities. The main optional services include:

• OLAP: OLAP enables data analysis within the Analytics module, handling the storage and processing of configured schemas in Fusion. For more details on OLAP installation, refer to the Installation Guide - OLAP Server.
• Fusion Developer: Fusion Developer allows the creation and editing of scripts, enabling the addition of Java Classes to Script activities in BPM Studio. It also includes a dedicated script editor. For more details on Fusion Developer installation, refer to the Installation Guide - Fusion Developer Server.

With the license activated and additional services installed, the Fusion Platform will be fully operational and ready to meet your environment’s needs. Be sure to follow the activation instructions carefully, and if you need assistance, contact our support team via the Customer Portal.