Contents
- 1 Objective
- 2 Conversion
to Fluig
- 2.1 Backup copy
- 2.2 Before conversion
- 2.3 Starting Fluig
- 2.4 Conversion
- 2.5 Post conversion or migration
Objective
The goal of this guide is to instruct system administrators who wish to perform the conversion of TOTVS ECM to the Fluig platform.
Conversion to Fluig
See the following steps and procedures necessary for the conversion of TOTVS ECM to Fluig.
Backup copy
Before 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 Fluig 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;
When you finish these procedures, disconnect and stop the TOTVS ECM service.
From this point on, the installation of Fluig can be executed according to the instructions in the guideFluig installation (Installer) -Windows or Fluig installation (Installer) -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.
Check the startup modes below and choose the one you want to use to start Fluig:
Run the file <<FLUIG_HOME_PATH>> \jboss\bin\standalone.bat. With this a command prompt window opens displaying the startup information and messages of the JBoss server. When it is necessary to stop the execution of the system, press the CTRL + C keys.
Access Windows Services through Control Panel and Administrative Tools group, or execute the services.msc command in Command prompt. Locate the Fluig service and click the Start the service button, on the menu bar, or Start in the pop-up menu displayed by right-clicking on the service.
Figure 3 - Windows Services window. Fluig service selected and initialized.
The Fluig startup conference can be observed through the log file in <<FLUIG_HOME_PATH>> \jboss\standalone\log\server.log, when it has about 1.0 MB and contains the inscription:
HH:MM:SS,mmm INFO
[com.fluig.startup.service.FluigStartupBean] (EJB default - x)
===============================================
HH:MM:SS,mmm INFO
[com.fluig.startup.service.FluigStartupBean] (EJB default - x) ==
Fluig is up and running right now. ==
HH:MM:SS,mmm INFO
[com.fluig.startup.service.FluigStartupBean] (EJB default - x)
===============================================
The time for service startup may vary according to the capabilities of the server on which Fluig will be executed.
Run the file <<FLUIG_HOME_PATH>>\jboss\bin\standalone.sh. With this the boot log is displayed in the terminal, with the boot information and messages of the JBoss server. When it is necessary to stop the execution of the system, press the CTRL + C keys.
Conversion
At this point, you can start the conversion process.
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.
Figure 6 - Fluig login screen.
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.
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:
<?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>
- 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.