Attention
The models below must not undergo any kind of modification. If the customer wish to make any type of change, he / she has to request the ratification of the sizing by the responsible teams, contacting the Channels or fluig partners.
- TOTVS Fluig Platform running on its own servers: the TOTVS Infra Services team must be activated through [email protected]
- TOTVS Fluig Platform running on Cloud Technical Projects servers: the team must be activated through [email protected]
Indexndice
Purpose
The purpose of this guide is to show a pre-approved environment for customers who wish to install and run TOTVS Fluig Platform on their own servers.
Usage of platform
| S | M | L | ||
| Users | Maximum of users registered | 20 to 100 | 101 to 300 | 301 to 500 |
| Maximum of users connected | 6 to 35 | 36 to 60 | 61 to 100 | |
| Documents | Maximum number of daily publications | 300 | 500 | 600 |
| Processes | Maximum number of processes designed | 5 | 10 | 15 |
| Average of opening per hour of requests | 50 | 100 | 200 | |
Integration with ERP? | Sim | Sim | Sim | |
| ERP in the same network?* | Sim | Sim | Sim |
Hardware
This section lists the hardware settings for the application and database servers.
Application Server
| S | M | L | ||
| Memory RAM | Quantity of memory in GB | 8 GB ¹ | 12 GB ² | 16 GB ³ |
| Processor | Bits | 64 | 64 | 64 |
| Core (vCPU) | 2 | 4 | 4 | |
| Disk | Speed | SAS of 15.000/rpm | SAS of 15.000/rpm | SAS of 15.000/rpm |
| Rate of SAN net transfer | 1 GB/s | 1 GB/s | 1 GB/s | |
| Space required for installation | 12 GB | 12 GB | 12 GB | |
| Space required for repository | (Number of documents x Size of document x Number of versions) x 1,10 | |||
| Space required for cache directory ** | (Number of documents accessed on day x file size x 6) | |||
| Space required for database | Minimum of 5 GB of disk for platform - For the operating system and installation of the DBMS, check the Database server documentation | |||
| Linux Files System | ext4 | ext4 | ext4 | |
| Windows Files System | NTFS or ReFS | NTFS or ReFS | NTFS or ReFS | |
Notes
¹ Since the 8 GB of memory is dedicated to the TOTVS Fluig Platform, as follows:
- Java (5 GB) - Configuration made in host.xml, stored in [Instalação_fluig]\appserver\domain\configuration. Inside the host.xml file, locate the following tag:
<server auto-start="true" group="fluig" name="fluig1">
- Below this tag, change the following properties:
size="1g" - Initial amount of memory allocated
max-size="4g" - Maximum amount of allocated memory
-XX:MaxMetaspaceSize=1g
- Operating System (3 GB);
² Since the 12 GB of memory is dedicated to the TOTVS Fluig Platform, in the following way:
- Java (8 GB) – Configuration made in host.xml, stored in [Instalação_fluig]\appserver\domain\configuration. Inside the host.xml file, locate the following tag:
<server auto-start="true" group="fluig" name="fluig1">
- Below this tag, change the following properties:
size="2g" - Initial amount of memory allocated
max-size="7g" - Initial amount of memory allocated
-XX:MaxMetaspaceSize=1g
- Operating System (4 GB)
³ Since the 16 GB of memory is dedicated to the fluig, in the following way:
- Java (13 GB) – Configuration made in host.xml, stored in [Instalação_fluig]\appserver\domain\configuration. Inside the host.xml file, locate the following tag:
<server auto-start="true" group="fluig" name="fluig1">
- Below this tag, change the following properties:
size="4g" - Initial amount of memory allocated
max-size="12g" - Maximum amount of allocated memory
-XX:MaxMetaspaceSize=1g
- Operating System (3 GB)
* For external systems that are not in the same VLAN where fluig is, the latency between the networks must be taken into account, as it directly affects the performance of fluig.
** The cache expires and is deleted after 24 hours of access.
*** The attribute name="fluig1" of the <server> tag is platform default, but may have been changed by the environment administrator.
Repository / Storage
The entire company in fluig will have a volume, which will be where the document information will be saved, not only the ECM documents but also within BPM processes. Although we support the Storage systems, mapped in the operating system, you must observe the latency between the application server and the Storage. Any variation on this communication channel will cause the platform to slow down.
Notification
Because of large latencies, do not configure platform to use repositories in other Datacenters.
Database server
Recommendations of manufacturers
| Database | Description | Link of official documents | Inquiry Date |
| Oracle | Recommendations of hardware | https://docs.oracle.com/database/121/NTDBI/reqs.htm#NTDBI2689 | 8/15/2016 |
| Recommendations of software | https://docs.oracle.com/database/121/NTDBI/reqs.htm#NTDBI2698 | 8/15/2016 | |
| SQL Server | Recommendations of hardware and software | https://msdn.microsoft.com/en-us/library/ms143506(v=sql.120).aspx | 8/15/2016 |
| MySQL 5.6 | Supported operating systems | http://www.mysql.com/support/supportedplatforms/database.html | 8/15/2016 |
Recommendation of fluig team
| Database | Description |
| Oracle | Minimum requirements to run databases ratified by fluig |
| SQL Server | |
| MySQL 5.6 |
The application server must be separate from the database server, with at least 2 servers.
To ensure fluig performance, the servers must be dedicated:
- The application server must contain only the operating system and installation of fluig;
- The database server must contain only the operating system and database installation used by the customer;
Fluig Viewer Server
Fluig Viewer is the new viewer of documents that was developed in partnership with American Accusoft. It can be used as follows:
Using the fluig Viewer in own Servers
Deve ser seguida a recomendação mínima, definida pelo nosso parceiro, disponível (em inglês) neste link.
Attention
A third server 100% dedicated to the fluig Viewer must be added, as recommended by Accusoft.
Using fluig Viewer
To use the fluig Viewer Cloud, simply configure according to the document Benefits of fluig Viewer Cloud
Logical design
This design aims to show how the virtual environment will be structured.
This design faithfully represents the environment that should be set up in the customer. If the customer environment is built on a model version earlier than this one displayed in this document, it will be considered out of fluig's standards, and at odds with the product service and support scope.
Visão Geral
Import HTML Content
Conteúdo das Ferramentas
Tarefas