Histórico da Página
Índice
| Índice | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Objective
The goal of this guide is to instruct system administrators who wish to perform the conversion of TOTVS ECM to the TOTVS Fluig platformPlatform.
Conversion
...
to platform
See the following steps and procedures necessary for the conversion of TOTVS ECM to TOTVS Fluig Platform.
Backup copy
| Nota |
|---|
In order to preserve the resources and data from TOTVS ECM in case there is an error during the conversion process, it is important to run a backup of the following items:
|
Before conversion
| Nota | ||
|---|---|---|
| ||
In order to carry out the conversion process successfully, it is necessary that TOTVS ECM is in its most current version update package, available in the Customer Portal. If the environment is outdated it is recommended to update it and then proceed with the steps for conversion. |
...
Run backups described in the previous item and, if a new database is used, restore the backup copy of the database on this new one.
Before executing the conversion, it is necessary to follow some procedures:
- Make sure that TOTVS Fluig Platform will respond on the same IP address and HTTP/HTTPS port as the current version of TOTVS ECM. If you do not use these same access criteria, start the TOTVS ECM service for this new database, if applicable. When you start the TOTVS ECM service, access the TOTVS ECM companies registers and change access settings, i.e. the Web server and Web port fields, as shown in Figure 1.
Figure 1- Company's parameters in the ECM.
- If you wish to change the location of the volumes, it is important that you execute the action before the conversion so access the Volume tab and make the necessary changes.
Figure 2 - Data volume of TOTVS ECM.
- The number of registered users in TOTVS ECM cannot exceed the number of available users in the License Service.
- Make sure that all the users that are registered in TOTVS ECM meet the following requirements:
- The user cannot possess duplicate login, email or registration;
- The user's login must have only alphanumeric characters, period (.), hyphen (-) and underscore (_);
- The name of the user cannot exceed the maximum limit of 255 characters;
- The user's email must be a valid email address;
- The user's password cannot be blank;
- Remove any global event or other customization that handles the posting of documents or other features of TOTVS ECM. For example: a global event beforeDocumentPublisher that does not allow posting in the root folder;
- Remove all scheduled tasks registered in TOTVS ECM;
...
From this point on, the installation of Fluig can be executed according to the instructions in the guideFluig the guide Platform installation (Installer) -Windows or Fluig installation (Installer) - or Linux
Starting Fluig
For the migration process, when Fluig is initialized on a database used by TOTVS ECM, table structures belonging to the latter remain the same. However, Fluig will create its tables separately.
| Informações | ||
|---|---|---|
| ||
In the case of a new service initialization or failure on reboot, it may be necessary to terminate processes with Image name equal to soffice.bin and the location of the file is for the Fluig installation directory in the Windows Task Manager. This is accessible through the CTRL + SHIFT + ESC shortcut keys or by right-clicking on the task bar and in the pop-up menu selecting the Start the Task Manager option. If these processes exist, they should be terminated. |
...
| Deck of Cards | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||
|
Conversão
Neste momento, pode ser iniciado o processo de conversão.
| Nota | ||
|---|---|---|
| ||
|
Pay attention to the following steps to start the conversion:
- After initializing Fluig, it is necessary to login using the user name wcmadmin and password adm;
- Once you've logged in, access the Control Panelmenu item and click on the ECM tab, in that tab access the Base converter option;
- With this, the base validation to verify that the conversion can be started will be executed. Figure 4 illustrates this process;
Figure 4 - Process of conversion of ECM base to Fluig.
- If non-conformities are not found, click Convert;
- When you click Convert, a message is displayed, as shown in Figure 5, indicating the beginning of the conversion;
Figure 5 - Conversion process started.
- To track the conversion process, access the file: <<FLUIG_HOME_PATH>> \jboss\standalone\log\conversion.log;
- The phrase "Conversion completed successfully" appears at the end of the log file and indicates the end of the conversion process;
- From this moment, it is possible to connect Fluig with users and passwords that existed in TOTVS ECM. To manage companies, the user wcmadmin is used and not wdkAdmin any longer.
Post conversion or migration
When a conversion process is executed, some procedures are necessary so that Fluig services can present its features properly. The following steps are recommended:
- Indexation of volume.
- Data services update for TOTVS ECM. This is the modification of these services for the recreation of stubs, in case of changes in the webservice URLs used.
For migration and where TOTVS ECM was integrated with TOTVS ECM/HCM, see if the folder <<FLUIG_HOME_PATH>> \jboss\modules\com contains the directories progress\main with libraries (JAR) of their Progress.
Nota title Attention This is not the JAR generated by ProxyGen (Proxy Generator), they are the old environment libraries registered in TOTVS ECM. This procedure is necessary, because in this version of the product such register of environments and indication of libraries no longer exist. The JBoss AS 7, requires that access to these common JAVA classes of Progress are initialized as a module of JBoss.
Inside this folder next to libraries there must be a file called "module.xml." Within its contents, all these libraries must be related. Remember that the file must be saved with UTF-8 code (without BOM). The file follows the standard:
Bloco de código language html/xml <?xml version="1.0" encoding="UTF-8"?> <module xmlns="urn:jboss:module:1.1" name="com.progress"> <properties> <property name="jboss.api" value="private"/> </properties> <resources> <resource-root path="o4glrt.jar"/> <resource-root path="common.jar"/> <resource-root path="commonj.sdo.jar"/> <resource-root path="ecore.change.jar"/> <resource-root path="ecore.jar"/> <resource-root path="ecore.resources.jar"/> <resource-root path="ecore.sdo.jar"/> <resource-root path="ecore.xmi.jar"/> <resource-root path="openedge.jar"/> <resource-root path="progress.jar"/> </resources> </module>Informações title Observação After this setting the restart of Fluig is mandatory so that these libraries are loaded into the classpath of JBoss AS 7. Until this is executed, the operations will return an error like: JavaException: java.lang.ClassNotFoundException: com.progress.open4gl.ProDataGraphHolder. Or another class in an attempt to create an object in the package com.progress.*.
Nota title Alternative Treatment A way to enable the use of these classes by the proxy generated is to add the contents of these libraries within the package of this proxy, that is, the files of type and extension JAR are compressed files like ZIP, each of these libraries can be opened by your preferred file compression application (WinZIP, WinRAR, 7-ZIP, among others) and their contents copied into the .JAR file of the proxy. Only the folders and their "META-INF" contents should be ignored, not copied.
- Re-add the global events or other customizations that have been removed before starting the conversion;
- Re-register the task schedules that were removed before starting the conversion, if they are still needed;
- If, when accessing Fluig, targeting occurs to the address <host>:<port> which belonged to TOTVS ECM, that means the address of access was not changed before the conversion (as mentioned in the session Before conversion) and therefore it will be necessary to change the access address in Fluig, entering as wcmadmin and going to the ControlPanel tab, WCM tab, System settingsitem.
Visão Geral
Import HTML Content
Conteúdo das Ferramentas
Tarefas