The updating of the product may have manual procedures, which are prior to or after the updating run by the Management Console of Environments. Before starting the updating process, we recommend you to read this document.
*** ATTENTION - UPDATING 12.1.18 ***
--> CREATION OF NEW INDEXES FOR THE TABLE "MOVTO-ESTOQ".
--> TAF (CONSOLIDATOR): IMPORTANT INFORMATION ON ESOCIAL IN A TAF RELEASED PACKAGE.
-------------------------------------------------------
NEW INDEXES FOR TABLE "MOVTO_ESTOQ"
-------------------------------------------------------
We inform that in the 12.1.18 release updating, the creation of new indexes for the table "movto-estoq" will be issued. Depending on the number of records in this table, the updating process can take longer than usual. In this case, we recommend a better planning in the updating window.
When indexes are created in tables with a great volume of data, it is advisable to create them as inactive, then reactive them through command 'PROUTIL <banco> -C IDXBUILD'.
For such, edit files .df from 'dfprep' directory by adding the word 'INACTIVE' in the definition of the indexes, according to the example below:
ADD INDEX "Comments" ON "Customer"
AREA "Customer Index Area"
INACTIVE
WORD
INDEX-FIELD "Comments" ASCENDING
Importing these settings is faster, because the indexes will not be created, they will only be cataloged in the data dictionary.
After this import is completed, use the 'PROUTIL' command to re-create the inactive indexes. Here is a brief example:
proutil sports -C Idxbuild <performance parameters>
- select the option 'v' = Rebuild selected active or inactive indexes
- select option '2' = Choose inactive indexes
- then answer the other questions inherent in re-indexing
-----------------------------------------------
ATENÇÃO PARA A LIBERAÇÃO DO TAF
-----------------------------------------------
Below, we reinforce some important information about the Layout 2.3 of eSocial
Government: According to the publication of competent authorities, the provision of Layout 2.3 as the official environment for the submission of eSocial information is 10/09/2017.
HR Solutions: The Layout 2.3 is made available along with Release 12.1.18 (10/06/2017).
TAF (Consolidator): Our package with the updating of Layout 2.3 of eSocial will be available on 10/27/2017.
Follow the information at:
http://tdn.totvs.com/pages/viewpage.action''pageId=301203218
From release 12.1.18, only the updating packages will only be available in OpenEdge11 version.
==============
PRE-UPDATE STAGES
==============
-------------------------------------------------- -----
1. Progress OpenEdge version
-------------------------------------------------- -----
Progress OpenEdge versions certified for Datasul product:
- Customers using Progress 11.6 must apply Service Pack 3 and FIX 26 (11.6.3.026).
Therefore, customers willing to migrate to Progress 11 must request Progress 11.6 version with the TOTVS Service Center (CST) team.
Note: From this Datasul 12.1.18 release, the issue of programs will be only in the OpenEdge 11.6.3 version, no issuance will take place in 10.2B.
-------------------------------------------------------
2. Enable Progress 64Bit Sequences
-------------------------------------------------------
The database, when created with a version below Progress 10.2B, lacks a feature called '64 Bit Sequences', so you can only create 32 bit sequences.
To meet the needs of Datasul 12 sequence settings, you must enable this feature to avoid errors while creating objects.
With the command below, you can check whether the enabled feature is found in the database, using the PROENV of Progress.
proutil nome-banco -C describe
To enable the feature, run the command below in the database, using the PROENV of Progress.
proutil nome-banco -C enableseq64
When you check it again, the feature must appear as enabled.
-------------------------------------------------------
3. Replacing database in target system
-------------------------------------------------------
WARNING: Failure to use all databases suggested by the product installation media may cause unexpected system performance. Only stop using any database if it is explicitly recommended by the Datasul technical support.
Datasul 12 consists of updated databases, plus the databases corresponding to new features, provided by the program media. The following Datasul system files must be checked as well to include the converted databases:
- Database connection .pf file: check whether the converted databases are included in the connection, as well as specific databases brought in the process;
- File progress-ds.xml in JBoss: database with 'EMS2UNI' data is required to run the Flex environment. This file contains the connection parameters of this database, which can be united with source databases.
- Alias program, if your databases are unified.
In addition to changing these files, check the 'Company Database' and 'Company X User relationship' registers in the Datasul system.
The Environment Management Console converts a system in each execution. It is recommended that you complete the conversion of all source products before using Datasul 12 in production.
-------------------------------------------------------
4. Oracle database
-------------------------------------------------------
If you do not use the default owners TOTVS has defined, change the '_for-owner' property of the Schemas-image objects.
-------------------------------------------------------
5. SQL Server database
-------------------------------------------------------
If you do not use the DSN-less connection standard for SQL Server database, then change it to update the environment.
Basically, a DSN-less connection (Data Source Name-less or connection without data source) allows the application to specify all parameters directly on the connection line to the database, without the need to set up an ODBC data source, however the ODBC driver is still required for connection and must be installed in the machine that will access.
-------------------------------------------------------
6. Upgrade and update historical databases
-------------------------------------------------------
Customers using history databases who wish to carry out the update process for this set of databases must use a backup of the databases in the source format, along with the history databases connected in the session with the logical names of their respective databases of movement. This setting is similar to the history database shortcut for querying data.
Currently, the history databases approved for the TOTVS Datasul product are:
- (EMS5) MOVFIN – Financial (multi-database)
- (EMS2) MOVADM – Administrative (multi-database)
- (EMS2) MOVRAC – Representative commission (multi-database)
- (EMS2) MOVIND – Industrial (single-database)
- (EMS2) MOVDIS – Distribution (single-database)
- (EMS2) MOVMNT – Industrial maintenance (single-database)
- (EMS2) MOVMFG – Shop floor (single-database)
- (EMS2) MOVFIS – Fiscal (single-database)
===============
POST-UPDATE STAGES
===============
It is recommended that you perform all post-update tasks that apply to your environment at the end of the update process.
You can delete the directories below when the update process finishes. These directories are backups of the product's previous version.
Location\File
JBOSS_HOME\server\instance-8080\deploy\datasul-byyou-12.1.1X-SNAPSHOT.rej
JBOSS_HOME\server\instance-8080\deploy\datasul-sso-ear-12.1.1X-SNAPSHOT.rej
Check the following items as well:
-------------------------------------------------------
1. JBoss parameters
-------------------------------------------------------
With the release of the new Portal (Sales, MLA and CRM) in Datasul to display the menu, you need to adjust parameter -Xss of JBOSS.
The environment administrator must execute the procedure below:
- Stop JBOSS.
- Edit file ...\ServidorAplicacao\jboss-4.2.3.GA\bin\run.bat
- Find parameter -Xss.
- Edit parameter found for -Xss256k.
- Start JBOSS.
-------------------------------------------------------
2. Propath verification
-------------------------------------------------------
You need to perform a validation in the PROPATH defined for Datasul. Basically, you need to check whether all the directories defined exist physically. If they no longer exist, you need to delete them from PROPATH. This significantly impacts performance, because when it seeks the directory, it waits for the operating system to provide feedback notifying that they do not exist and only then it moves on to the next directory.
-------------------------------------------------------
3.Java version
-------------------------------------------------------
WARNING: to perform the JBOSS load, use the JAVA VM issued by Oracle.
The minimum JAVA version to load the JBOSS service is 1.7.0_80, as some implementations only work with this version or above, for as long as you stay in version 1.7 of JAVA.
If the server has a 64 bit operating system, you can use a 64 bit version of JAVA to use the available server resources.
Workstations can use JAVA version 1.8.
-------------------------------------------------------
4. Oracle and SQL Server database
-------------------------------------------------------
The Environment Management Console changes the connection parameters to import deltas, but when using Oracle or SQL Server database, the following procedure has to be done after the conversion.
After the process is finished, quit the Console and truncate the before-image areas with the following before-image truncate command:
proutil nome-do-schemaholder –C truncate bi
This is necessary because the console uses -1 to connect to the schema-holder to make dictionary changes. Usually the -RO parameter is used to connect to the schema-holder; in case the truncate is not done, the message below is displayed at each access.
WARNING: Before image file of database is not truncated. (1552)
When executing the schema-holder truncate, this message is no longer displayed, allowing the connection in read-only (-RO) mode for schema-holders (Oracle and SQL Server).
WARNING: If you do not use the default owners TOTVS has defined, change the '_for-owner' property of the Schemas-image objects for environments using Oracle database.
-------------------------------------------------------
5. Oracle user permissions
-------------------------------------------------------
Some programs, such as TimeOut, when configured for an environment with the Oracle database, access the control tables (v$session) and, depending on user permission level, may display the message "table or view does not exist".
Thus we recommend you create a ROLE, to grant the needed permissions to all Oracle users configured for Datasul.
CREATE ROLE "DATASUL";
GRANT ALTER SYSTEM TO "DATASUL";
GRANT CREATE SEQUENCE TO "DATASUL";
GRANT CREATE SESSION TO "DATASUL";
GRANT CREATE TABLE TO "DATASUL";
GRANT SELECT ANY DICTIONARY TO "DATASUL";
GRANT SELECT ANY TABLE TO "DATASUL";
GRANT SELECT ANY SEQUENCE TO "DATASUL";
GRANT SELECT ON "SYS"."ARGUMENT$" TO "DATASUL";
GRANT SELECT ON "SYS"."COL$" TO "DATASUL";
GRANT SELECT ON "SYS"."COM$" TO "DATASUL";
GRANT SELECT ON "SYS"."CON$" TO "DATASUL";
GRANT SELECT ON "SYS"."DUAL" TO "DATASUL";
GRANT SELECT ON "SYS"."ICOL$" TO "DATASUL";
GRANT SELECT ON "SYS"."IND$" TO "DATASUL";
GRANT SELECT ON "SYS"."LINK$" TO "DATASUL";
GRANT SELECT ON "SYS"."OBJ$" TO "DATASUL";
GRANT SELECT ON "SYS"."PROCEDURE$" TO "DATASUL";
GRANT SELECT ON "SYS"."SEQ$" TO "DATASUL";
GRANT SELECT ON "SYS"."SYN$" TO "DATASUL";
GRANT SELECT ON "SYS"."TAB$" TO "DATASUL";
GRANT SELECT ON "SYS"."TS$" TO "DATASUL";
GRANT SELECT ON "SYS"."USER$" TO "DATASUL";
GRANT SELECT ON "SYS"."VIEW$" TO "DATASUL";
GRANT "CONNECT" TO "DATASUL";
GRANT "RESOURCE" TO "DATASUL";
Once the creation is done, you must grant users the ROLE created. For example:
GRANT DATASUL TO EMS2CAD;
IMPORTANT: you need to grant permissions to all users configured in Datasul, basically all who were registered in program databases by company (btb\btb962aa.r).
-------------------------------------------------------
6. Srcadger connection
-------------------------------------------------------
For a client using Plan Management, you need to identify whether the JBOSS configuration file has the SRCADGER database connection, to avoid errors while using Plan Management.
Find this configuration file in the directory of the JBOSS instance in ...\ServidorAplicacao\jboss-4.2.3.GA\server\instance-8x80\deploy\ named in accordance with the environment database.
Example:
- progress-ds.xml - Progress database
- oracle-ds.xml - Oracle database
- mssql-ds.xml - SQL Server database
--> Progress database content:
<local-tx-datasource>
<jndi-name>srcadger</jndi-name>
<connection-url>jdbc:datadirect:openedge://<SERVIDOR-BANCO>:<PORTA-SQL>;databaseName=srcadger</connection-url>
<driver-class>com.ddtek.jdbc.openedge.OpenEdgeDriver</driver-class>
<user-name>pub</user-name>
<password>pub</password>
<metadata>
<type-mapping>PostgreSQL 7.2</type-mapping>
</metadata>
<min-pool-size>1</min-pool-size>
<max-pool-size>30</max-pool-size>
</local-tx-datasource>
<local-tx-datasource>
<jndi-name>ErpDS</jndi-name>
<connection-url>jdbc:datadirect:openedge://<SERVIDOR-BANCO>:<PORTA-SQL>;databaseName=srcadger</connection-url>
<driver-class>com.ddtek.jdbc.openedge.OpenEdgeDriver</driver-class>
<user-name>pub</user-name>
<password>pub</password>
<metadata>
<type-mapping>PostgreSQL 7.2</type-mapping>
</metadata>
<min-pool-size>1</min-pool-size>
<max-pool-size>30</max-pool-size>
</local-tx-datasource>
- Replace value <SERVIDOR-BANCO> with the IP or server name of the SRCADGER database.
- Replace value <PORTA-SQL> with the SQL port loaded for the SRCADGER database.
--> Oracle database content:
<local-tx-datasource>
<jndi-name>srcadger</jndi-name>
<connection-url>jdbc:oracle:thin:@<SERVIDOR-ORACLE>:1521:<INSTANCIA-ORACLE></connection-url>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<user-name>srcadger</user-name>
<password>srcadger</password>
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
<metadata>
<type-mapping>Oracle10g</type-mapping>
</metadata>
<min-pool-size>1</min-pool-size>
<max-pool-size>8</max-pool-size>
</local-tx-datasource>
<local-tx-datasource>
<jndi-name>ErpDS</jndi-name>
<connection-url>jdbc:oracle:thin:@ <SERVIDOR-ORACLE>:1521:<INSTANCIA-ORACLE></connection-url>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<user-name>srcadger</user-name>
<password>srcadger</password>
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
<metadata>
<type-mapping>Oracle10g</type-mapping>
</metadata>
<min-pool-size>1</min-pool-size>
<max-pool-size>8</max-pool-size>
</local-tx-datasource>
- Substitute value <SERVIDOR-ORACLE> by the IP or name of server in which the Oracle instance is installed.
- Substitute value <INSTANCIA-ORACLE> by the name of Oracle instance in which the SRCADGER was created.
--> SQL Server database content:
<local-tx-datasource>
<jndi-name>srcadger</jndi-name>
<connection-url>jdbc:sqlserver://<SERVIDOR-SQLSERVER>;instanceName=<NOME-BANCO>;databaseName=srcadger</connection-url>
<driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
<user-name>totvs</user-name>
<password>totvs</password>
<metadata>
<type-mapping>MS SQLSERVER2008</type-mapping>
</metadata>
<min-pool-size>1</min-pool-size>
<max-pool-size>8</max-pool-size>
</local-tx-datasource>
<local-tx-datasource>
<jndi-name>ErpDS</jndi-name>
<connection-url>jdbc:sqlserver://<SERVIDOR-SQLSERVER>;instanceName=<NOME-BANCO>;databaseName=srcadger</connection-url>
<driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
<user-name>totvs</user-name>
<password>totvs</password>
<metadata>
<type-mapping>MS SQLSERVER2008</type-mapping>
</metadata>
<min-pool-size>1</min-pool-size>
<max-pool-size>8</max-pool-size>
</local-tx-datasource>
- Substitute value <SERVIDOR-SQLSERVER> by the IP or name of server in which the SQL Server was installed.
- Substitute value <NOME-BANCO> by the name of the database created for the SRCADGER.