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.
- fluig running on its own servers: the TOTVS Infra Services team must be activated through [email protected]
- fluig 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 fluig on their own servers.
Usage of fluig
| 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 fluig 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 fluig - 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 fluig, 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 fluig, 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 fluig to use repositories in other Datacenters.
Database server
Recomendações dos fabricantes
| Banco de dados | Descrição | Link das documentações oficiais | Data da consulta |
| Oracle | Recomendações de hardware | https://docs.oracle.com/database/121/NTDBI/reqs.htm#NTDBI2689 | 15/08/2016 |
| Recomendações de software | https://docs.oracle.com/database/121/NTDBI/reqs.htm#NTDBI2698 | 15/08/2016 | |
| SQL Server | Recomendações de hardware e software | https://msdn.microsoft.com/en-us/library/ms143506(v=sql.120).aspx | 15/08/2016 |
| MySQL 5.6 | Sistemas operacionais suportados | http://www.mysql.com/support/supportedplatforms/database.html | 15/08/2016 |
Recomendação do time fluig
| Banco de dados | Descrição |
| Oracle | Requisitos mínimo para executar os bancos de dados homologados pelo fluig |
| SQL Server | |
| MySQL 5.6 |
O servidor de aplicação deve ser separado do servidor de banco de dados, sendo 2 servidores no mínimo.
Para garantir a performance do fluig os servidores devem ser dedicados:
- O servidor de aplicação deve conter somente o sistema operacional e a instalação do fluig;
- O servidor de banco de dados deve conter somente o sistema operacional e a instalação do banco de dados utilizado pelo cliente;
Servidor fluig Viewer
O fluig Viewer é o novo visualizador de documentos que foi desenvolvido em parceria com a americana Accusoft. Ele pode ser utilizado da seguinte forma:
Utilizando o fluig Viewer em servidores próprios
Deve ser seguida a recomendação mínima, definida pelo nosso parceiro, disponível (em inglês) neste link.
Atenção
Deve ser adicionado um terceiro servidor 100% dedicado ao fluig Viewer, conforme recomendações da Accusoft.
Utilizando o fluig Viewer
Para utilizar o fluig Viewer Cloud basta fazer a configuração conforme o documento Benefícios do fluig Viewer Cloud
Desenho lógico
Este desenho tem como objetivo mostrar como o ambiente virtual será estruturado.
Este desenho representa fielmente o ambiente que deverá montado no cliente. Se o ambiente do cliente estiver construído num modelo inferior ao exibido neste documento, ele será considerado fora do padrão fluig, e em desacordo com o escopo de atendimento e suporte do produto.
Visão Geral
Import HTML Content
Conteúdo das Ferramentas
Tarefas