Installation and Configuration Datasul 12.1.

TOTVS S.A.
 2 Installation and Configuration Datasul 12.1.7

Sumário

Capítulo 1 - Installation Datasul 12 4

1 Purpose
................................................................................................................................... 4
Target Audience
.......................................................................................................................................................... 4
This Guide..........................................................................................................................................................
Organization 4
Im portant Docum
..........................................................................................................................................................
ents 4
2 Introdução
................................................................................................................................... 5
Product Distributed
..........................................................................................................................................................
Architecture 5
Installation..........................................................................................................................................................
Types 6
Notification
.........................................................................................................................................................
during installation 7
3 Minimum
...................................................................................................................................
Requirements 7
General View..........................................................................................................................................................
of Requirem ents 8
Hardw are Requirem
..........................................................................................................................................................
ents 9
Customer .........................................................................................................................................................
Station Requirements 9
Requirements
.........................................................................................................................................................
for Server 10
Softw are ..........................................................................................................................................................
Requirem ents 10
Operational
.........................................................................................................................................................
system 11
Progress
......................................................................................................................................................... 11
Java ......................................................................................................................................................... 11
Flash .........................................................................................................................................................
Player and Brow ser 12
Remote .........................................................................................................................................................
Access Tools 12
Requirements
.........................................................................................................................................................
for Oracle Databases 12
Requirements
.........................................................................................................................................................
for SQL Server databases 13
User Requirem
..........................................................................................................................................................
ents (Server) 13
4 Installation
................................................................................................................................... 13
Installation..........................................................................................................................................................
Media Details 13
Planning the..........................................................................................................................................................
Installation 14
Industrial
.........................................................................................................................................................
Multi-Company / Security by Site 14
Installation.......................................................................................................................................................... 14
Program s..........................................................................................................................................................
Installation 15
Database ..........................................................................................................................................................
Installation 17
Progress..........................................................................................................................................................
Database 17
Configuration
.........................................................................................................................................................
of Progress Explorer Tool 19
Objects.........................................................................................................................................................
created in the installation of Progress Database 19
Unix / .........................................................................................................................................................
Linux Operational Systems 19
Base creation
.........................................................................................................................................................
w ith SQL access 20
Oracle Database
.......................................................................................................................................................... 21
Objects.........................................................................................................................................................
created in the installation of Oracle Database 21
Creation
.........................................................................................................................................................
of Objects in Oracle Database 22
SQL Server ..........................................................................................................................................................
Database 22
Objects.........................................................................................................................................................
created in the installation of SQL Server Database 23
Creation
.........................................................................................................................................................
of Objects in SQL Server Database 23
SQL Server
.........................................................................................................................................................
Connection 23
Installation..........................................................................................................................................................
of Application Server 24
Objects.........................................................................................................................................................
created in the installation of the Application Server 27
Docum ent..........................................................................................................................................................
Installation 27
Initializing..........................................................................................................................................................
Datasul 12 27
Access to..........................................................................................................................................................
Datasul 12 29
Rem ote Access
.......................................................................................................................................................... 29
Adjust after..........................................................................................................................................................
Installation 29
Sequences
.........................................................................................................................................................
Permission 29

TOTVS S.A.
 Contents 3

Configuration
.........................................................................................................................................................
for Progress programs access 30
Configuration
.........................................................................................................................................................
for Plan Management access 30
Delivery
.........................................................................................................................................................
configuration of authentication e-mail 30
Translation
.........................................................................................................................................................
Matrix in EMS 5 31
Installation
.........................................................................................................................................................
of Plug-in CRM Outlook 31
Checking
.........................................................................................................................................................
environment after installation 32
5 Update
................................................................................................................................... 32
6 Reinstallation
................................................................................................................................... 32
7 Uninstallation
................................................................................................................................... 33

Capítulo 2 - Datasul 12 Configuration 33

1 Purpose
................................................................................................................................... 34
Target Audience
.......................................................................................................................................................... 34
Im portant..........................................................................................................................................................
Docum ents 34
How to use..........................................................................................................................................................
this guide 34
2 Configuration
...................................................................................................................................
file 34
Database .......................................................................................................................................................... 35
AppServer .......................................................................................................................................................... 35
Log .......................................................................................................................................................... 37
License Server
.......................................................................................................................................................... 38
License.........................................................................................................................................................
File Adjust 39
Jboss Service
..........................................................................................................................................................
Configuration 39
Linux ......................................................................................................................................................... 40
JBOSS .........................................................................................................................................................
Security 40
Mem ory Param
..........................................................................................................................................................
eters 43
Tim e Out ..........................................................................................................................................................
Flex 44
Josso .......................................................................................................................................................... 44
Configuration
.........................................................................................................................................................
of external access 45
Ports .......................................................................................................................................................... 45
Progress..........................................................................................................................................................
Session 45
Menu .......................................................................................................................................................... 46
RFI – Quotation
..........................................................................................................................................................
Portal 47
Mail Service
......................................................................................................................................................... 47
Files Location
.......................................................................................................................................................... 47
3 DataSource
...................................................................................................................................
Progress Connection 48
4 Configuration
...................................................................................................................................
of Datasul 12 with HTTPS 50
5 Datasul
...................................................................................................................................
Product Database List 50

Capítulo 3 - Remote Access Configuration 54

1 Introduction
................................................................................................................................... 55
2 Remote
...................................................................................................................................
access with TS 55
3 Remote
...................................................................................................................................
access with Citrix 63
Purpose .......................................................................................................................................................... 63
Requirem..........................................................................................................................................................
ents 63
Supported ..........................................................................................................................................................
versions 63
Citrix Configuration
.......................................................................................................................................................... 63
Datasul Configuration
.......................................................................................................................................................... 72
4 Remote
...................................................................................................................................
access with GoGlobal 77
GoGlobal ..........................................................................................................................................................
4 Adjusts 81

TOTVS S.A.

3
 4 Installation and Configuration Datasul 12.1.7

1 Installation Datasul 12

1.1 Purpose
This guide aims at describing the necessary procedures to install Datasul 11 product, as well as, setting
the product in the supported platforms. Installation media can also be used to update programs.

1.1.1 Target Audience

As it is a complex process of installation, it requires people that have knowledge of Datasul 11 product

architecture, database (Progress/Oracle/SQL Server), Java, Flex, Jboss and net environment.

1.1.2 This Guide Organization

Introduction
This chapter displays a general view of the distributed architecture, installation types and examples
of topologies in product use.
Requirements
This chapter displays the minimum requirements list of hardware and software demanded in
installation and product configuration.

Installation
This chapter describes the procedures that must be run for product installation. It covers since the
installation planning, that is, choosing the proper installation type, until necessary configuration for remote
access.
Update
This chapter describes the product update procedure.
Reinstallation
This chapter describes the procedures to be run for re-installation of each Datasul 11 component,
as well as, the necessary precautions for this routine run.
Uninstallation
This chapter describers the necessary procedures for Datasul 11 uninstallation.

1.1.3 Important Documents

Progress Guides
Getting Started – Installation and Configuration;

TOTVS S.A.
 Installation Datasul 12 5

Getting Started – Preinstallation Checklist for Windows;

Getting Started – Preinstallation Checklist for Unix;

Getting Started – Database Essentials;
Data Management – Database Administration;
Application Server – Administration.
Get these and other documents in Progress site.

Jboss Guides
Installation Guide;
Getting Started Guide;
Server Configuration Guide.
Get these and other documents at Jboss AS Documentation and Jboss Wiki.

Datasul Connection for Web (GoGlobal) Guides

Administrator Guide;
License Agreement;
Quick Start Guide.
Get these and other documents in Graphon and GoGlobal.

Datasul 11 Guides, Upgrade/Update Guide.

1.2 Introdução

1.2.1 Product Distributed Architecture

Distributed architecture consists of separating the components in independent platforms that
interact among them, enabling the resources to be shared while the maximum benefit of each device is
obtained. It works as follows: the machines of the users are connected to serves through the net; each
server provides different resources so the programs are run from the user machine.
The figure below displays the four basic components used by product.

TOTVS S.A.
 6 Installation and Configuration Datasul 12.1.7

1.2.2 Installation Types

For the product to work, run the installation of Programs, Database and Application Server:
Programs
It installs programs to use the product, as well as, other necessary files for its run.

Database
It installs and configures the database used by the product, as well as, the scripts to load and drop
these databases.
Application Server
It installs and configures Jboss, as well as, the Datasul Interactive, and these components are
essential for product work.
Document
It installs the product document guides.

NOTIFICATION: This media is prepared for installation of several instances of Datasul 11

product in the same server. This procedure consists of installing multiple copies of

TOTVS S.A.
 Installation Datasul 12 7

Database, Application Server and Document options, following the maximum limit of six

instances. Each installed instance is named based on the main port used by Jboss, following
the sequence 8080, 8180, 8280, 8380, 8480 e 8580. The folders, scripts and services used in the
first installation of the options mentioned are named after the identifier 8080. To install a
second instance of these options, open the media installer and run these same options
again. At each new run, a new copy is installed and named based on the sequence described

above. The programs area is the same in the environment and shared by all instances.

1.2.2.1 Notification during installation

During Datasul products installation, a notification is displayed for customers using determining
antivirus, accusing the virus identification in the “OCX” and “Interfac” directory files. It happens as files run
routines that some antivirus identify as virus. However, they do not characterize instructions of this type.
Therefore, the message displayed is disregarded.

1.3 Minimum Requirements

This chapter aims at promoting recommendation on the user of hardware and software related to
Datasul 11 and some information on their configuration. These recommendations aims at helping the
customers in the environment configuration, using it at its maximum, getting a better cost/benefit relation.
However, it does not represent commitments with technologies or some supplier in special on the part of
TOTVS. The decision on technology and supplier is responsibility of the customer, as well as, the service,

security and reliability level, the customer desires from the environment. This guide positions are also
changed due to the progress of technologies and our products;
Remember the Web environment used by Datasul 11 has greater complexity than an environment
of standard client/server, as for instance, EMS 2, EMS 5, etc. The proper configuration and tuning of
environment (servers, nets, clients, database, etc.) are important for Datasul 11 working, as in case part of
the environment is improperly configured, the product performance as a whole is affected.
The recommendation and examples mentioned below only take in consideration the softwares
related to Datasul 11 and generic use softwares, such as Office and e-mail. If other softwares are installed
in the same environment, they must be be taken in consideration, wherein the requirements described are
probably not enough for all routines run.
The Infra Structure (DMZ, net etc) and third party softwares (Operational Systems, Java etc)

TOTVS S.A.
 8 Installation and Configuration Datasul 12.1.7

configurations necessary for product work are responsibility of the customer. If you need the support of the

Infra Structure team, contact TOTVS Infra Services through e-mail [email protected] or contact
through phone number 4003-0015 in the options 3, 4, 2 - TIS Scheduling Central.

1.3.1 General View of Requirements

Servidor
30 us ers (whi thout cons i deri ng DCFW, Ci tri x a nd others )

Hardware

Disk 120 GB
Memory 4 GB
Processor Intel Xeon Dual 2.00 GHz
Software

Operational System ¹ Windows Server

Linux
Java JRE 1.6 and JRE 1.7
OpenEdge 10.2B08

OpenEdge ² 11.3.3.017 and supports higher versions

¹ The load and Jboss shutdown scripts are sent to the mentioned operational systems for customer
convenience. For these scripts configuration in other operational systems, contact Jboss support in its
location or access TOTVS phone consultancy for monitoring.
² From version 12.1.1, media is released for Progress 10.2B and another one for Progress 11.3.3, where
the customer must download, as environment migration planning.
In Progress 11.3 was released the implementation of programs with 64-bit client (prowin.exe), but Datasul
12.1.1 is approved to run only with 32-bit client (prowin32.exe).
Customers using Progress 11.3 should apply service pack 3 and FIX 017 (11.3.3.017).
Customers using Progress 11.5 should apply service pack 1 and FIX 005 (11.5.1.005).

Client Station
Wi ndows

Hardware

Memory (Architecture 32-bit) 1 GB Minimum (2GB Recommended)

TOTVS S.A.
 Installation Datasul 12 9

Memory (Architecture 64-bit) 2 GB Minimum

Processor Intel Pentium IV 2.80 GHz (Pentium Dual-
Core Recommended)
Screen Resolution 1024 x 768 or higher
Software

Flash Flash Player 10

Browsers Internet Explorer 9
Internet Explorer 10
Internet Explorer 11
Firefox 3.5 e 7
Chrome ²
Java Latest JRE 1.7

¹ For the season the same client that having 64-bit operating system is recommended to be done 32-bit
JRE installation, this due to the applications used by Datasul be 32-bits.

² The Chrome browser can be used only to environments that use MenuHTML

1.3.2 Hardware Requirements

1.3.2.1 Customer Station Requirements

We do not recommend the usage of stations smaller than the minimum mentioned above, as the
performance does not meet the user needs. If the company has several stations with less configurations

than the minimum amount recommended, we suggest you use the Graphic Terminal Servers resources
using the existing hardware.
The configuration recommended meets the majority of the users, but, for the most demanding
users, maybe there is the need of a better configuration. We understand a 'most demanding user' as the
one using heavier processes (the need of a better CPU and a faster network card and/or connected to a
switch port dedicated to it) or a user with several simultaneous application (need of more memory to run
process as Office, e-mail, CAD, EIS etc., at the same time).
We recommend the minimum configuration above mentioned for new equipment, if the company
purchases new stations and want to use them for a long time without the need of upgrade and without
becoming obsolete. Configurations the hardware suppliers are currently offering and that have a new
relation cost/benefit are also taken in consideration.

TOTVS S.A.
 10 Installation and Configuration Datasul 12.1.7

For all cases, we recommend the update of network card of first line suppliers.

1.3.2.2 Requirements for Server

For other types of installations, such as Application Server, Database and Programs, we
recommend the user of Dimensioning service that can be requested through the contacts below:

Complementary Hardware and Software - C&O - 2013

Architec
t Flávia Wiliam Victor Antonio Alinne
flavia. wiliam. victor. antonio.
polido@totvs. abreu@totvs. janusz@totvs. rodrigues@totvs. alinne.ciancio@totvs.
E-Mail com.br com.br com.br com.br com.br
Landlin
e phone 11-2099-7520 11-2099-7307 11-2099-7188 11-2099-7398 11-2099-7870
Mobile 11-98853-1479 11-97677-4305 11-98899-4684 11-99953-8025 11-99198-2681
Acre ABM Argentina Brasília Amapá
Centro-Oeste Centro-Norte de
Paulista Jurídica Minas Curitiba Amazonas
Centro-Oeste de
IP São Paulo Minas Goiás Bahia
Mato Grosso Espírito Santo Metropolitana Ceará
Mato Grosso do
Sul Leste de Minas Paulistana Maranhão
Rio de Janeiro México Private Para
Service Roraima Minas Gerais Triah Paraíba
São José do Rio
Preto Nordeste Vale do Paraíba Paraná Central
Norte
Sul Fluminense Fluminense Piauí
Tocantins Sul de Minas Rio Grande do Norte
Triangulo
Mineiro Rio Grande do Sul
Zona da Mata Santa Catarina
Sergipe

1.3.3 Software Requirements

TOTVS S.A.
 Installation Datasul 12 11

1.3.3.1 Operational system

The station client must have Windows operational system installed, as Datasul 11 uses language

Progress in architecture 32-bit (Win32). Additional information in relation to operational platforms and
systems validated can be obtained in Progress site (Product Availability Guide).

1.3.3.2 Progress

The Progress licenses in Datasul 11 product are:

License Operational System Comment

Openedge Windows Server It is installed in the database server for Progress base
Enterprise administration routines run.
RDBMS Unix
Openedge Windows Server Only used with Oracle database. As it is installed in
DataServer for clients (DataServer Local) or in server (Remote
Oracle Unix DataServer)
OpenEdge Only used with SQL Server database. As it is installed in
DataServer for Windows Server clients (DataServer Local) or in server (Remote
Microsoft SQL DataServer)
Openedge Windows It is installed in application server for configuration of
Application Server services as AppServer, Webspeed, WebServices etc.
Enterprise Unix

Windows It is installed in client station or in files server (Shared

Client Networking Progress). It is also necessary in the database server for
Unix routines run through RPW.
Windows Server It is installed in client stations or in files server (Shared
Query / Results Progress) for reports run and compilation.
Unix

NOTIFICATION: Only one type of license related to database is released (Openedge Enterprise
RDBMS, Openedge DataServer for Oracle or Openedge DataServer for Microsoft SQL) according
to database managerial system used in its company.

1.3.3.3 Java

The JBOSS when configured in an Operational System 64-bit, install Java 64-bit (JRE) in the same
version 7.
For workstations, use version 32-bit of JAVA 8.

TOTVS S.A.
 12 Installation and Configuration Datasul 12.1.7

1.3.3.4 Flash Player and Browser

To run Datasul 11 in client stations, you need the Flash Player. If it is not installed, the Flash Player can be

downloaded from Adobe site (minimum version: 9r124).

1.3.3.5 Remote Access Tools

To run Progress programs through Internet, use third party remote access tools. Program Datasul
11 is validated and has remote access configurations for GoGlobal version 4, Citrix (Citrix Presentation
Server Version 4.5) and Terminal Server. To use Server Terminal, the server must have an operational

system Window 2008 or later, with service RemoteAPP enabled.

Further details, query remote access configuration.

1.3.3.6 Requirements for Oracle Databases

If you use an existing instance, the following recommendations must prevail against other non
TOTVS products. To check the values of existing base parameters, proceed with the following queries
and analyses the results:
select parameter, value
from nls_database_parameters
where parameter = 'NLS_CHARACTERSET'

NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CHARACTERSET WE8ISO8859P1 OU WE8MSWIN1252
NLS_NCHAR_CHARACTERSET AL16UTF16

Select name, value from v$parameter where name = 'db_block_size';

Select name, value from v$parameter where name = 'open_cursors';
CHARACTERSET: The database page code must have value WE8ISO8859P1 or
WE8MSWIN1252. If this parameter value is not this one, the instance must be recreated. This parameter is
only entered during creation of the database, so there is no way to change it without recreating the
instance.
Block size of Oracle instance: If the database has block value smaller than 8k (8192 bytes) observed

TOTVS S.A.
 Installation Datasul 12 13

by initialization parameter (db_block_size), it must be recreated. If possible, create a new database for

Datasul products
Cursors Availability: We recommend administrate a value higher than the instance installation
standard in the initialization parameter (open_cursors) Start with value 32000 or higher.
Workstations: Install Oracle Net Service in each station. Never install this product with language
other than English. The NLS_LANG must have the database CharacterSet ( AMERICAN_AMERICA.

WE8ISO8859P1 or AMERICAN_AMERICA.WE8MSWIN1252) in record keys (regedit) of the station or

application servers. This configuration returns better performance to products with relationship Client/
Server.

1.3.3.7 Requirements for SQL Server databases

The product was validated to be run with SQL Server 2012 and the hardware and software requirements

are queried in manufacturer site SQL Server 2012 Requirements.

Confirm the TCP/IP protocol is enabled for SQL Server instance used. SQl Server Express
instances do not have this protocol enabled by standard.
For these workstations, install SQL Server Native Client 10.0, so access to Datasul 11 product is

configured in the server.

1.3.4 User Requirements (Server)

We recommend you install Datasul products as "administrator" user, or as a user added in server

administrator group.

1.4 Installation

1.4.1 Installation Media Details

The installation media of Datasul 11 is available in DVD through Totvs Support Portal in Downloads
area.
In these media, you can find available:
Product Installation Guide;
Customer Support Guide;
Java;
Setup and files needed for product installation.

TOTVS S.A.
 14 Installation and Configuration Datasul 12.1.7

1.4.2 Planning the Installation

We will show some stages that must be followed for Datasul 11 configuration and installation,

according to types of installation available in media (Programs, Database and Application Server).
Define environment topology. In this stage, define where each component is installed. Choose
hardware used as database server, files server, application server and the machines that are
available to users as well. For each of theses components, check if hardware and software
requirements are met;

Install the programs in files server;

Install database;
Install application server;
Load database using the scripts by Openedge Explorer application;
Initialize the product by using the shortcut created in “Initialize > Programs > TOTVS Datasul >
Administration > Product Initializer” during application server installation;
Start Jboss through “TOTVS Datasul - <ID>” server through “Services” of Windows.
After the conclusion of these stages, the product is ready for use.

1.4.2.1 Industrial Multi-Company / Security by Site

Datasul 11 has the Security by Site functionality, aiming at defining whether each user can view
information of a determined site.
This feature enables the Industrial databases to be used as Multi-Company with information

separated by Sites. The Security by Site can be applied both in Unified Databases (Multi-Company) and
separated.
This functionality has some features and rules that must be clarified and assessed before its application.

Further details on rules and programs, click here.

1.4.3 Installation
NOTIFICATION: If you receive media in DVD, before starting installation, copy all DVD2 content
for DVD1. Without this, installation is interrupted in the middle of the process. When media
download is performed through the Support Portal, all zip files must be unzipped in the same
directory.

TOTVS S.A.
 Installation Datasul 12 15

The stages below are common for all types of Datasul 11 installation:

Enter ID screen for this installation

An identifier (ID) must be entered for this installation. As the product installation directory is default, this ID is
necessary to avoid overlapping of files when there is more than one product installation in the same server.
User Record Screen
Enter the “User Name” and the “Company Name” using Datasul 11. Select “Next” to continue.

Special characters are not allowed in this field, as errors may occur in product access.
Drive Screen available
Drives available for product installation are displayed on this screen. Select a drive, then click Next.
Remember only local drives are displayed (mapped units are not displayed).
After clicking Next, a screen indicating whether space in disk is enough for media installation is displayed.
If there is space, only an information screen is displayed, indicating space is enough. If there is space,
installation questions whether you want to select another drive. If negative, installation is not proceeded. In
this case, release space in disk and start installer again.
Installation type screen
Select the installation type run this moment. Remember the displayed order must be followed:
Programs
Database
Application Server

Document
Select “Next” to continue.
Next chapters describe procedures that must be run for each installation type.

1.4.4 Programs Installation

When selecting option "Programs", Progress used by Datasul 11 are installed. Programs area are
installed in structure <Drive>:\Totvs\Datasul\<ID>\ERP. Directory “ERP” must be accessible to all users
using Datasul 11, due to Progress programs run. Programs area installation is a requirement for
installation of other installation media components.
Installer OpenEdege 10.2B has binaries compiled both for 32-bit and 64-bit. Define through menu
options the binaries that are installed. If any option is selected for Character 32 or Character 64, a directory
named "char32" or "char64" is created, respectively inside product directories.

TOTVS S.A.
16 Installation and Configuration Datasul 12.1.7

Installer OpenEdege 11.3 has binaries compiled for both 32-bit and 64-bit. Select option "Progress
11.3" for environment using Windows or Linux, 32-bit or 64-bit. Option TTY serves for character
environments and for Web, 32-bit or 64-bit applications.

TOTVS S.A.
 Installation Datasul 12 17

To continue this process, select "Next". In this moment, programs start to be installed. At the end of
the process, the installer returns to Installation Type selection screen.

1.4.5 Database Installation

When selecting option "Database", bases used by Datasul 11 are installed and configured.

1.4.6 Progress Database

ID Selection Screen
If installation of Database is performed in the same server where programs area installation is, this
screen is displayed. In this case, "Yes" to use ID previously created. If there is more than 1 ID registered, the
ID you want to use is requested.
Services change screen
Enter start number of TCP/IP port to be configured to load databases. TCP/IP ports are configured
in a sequence. In this case, before entering the port start number, we recommend you to check whether
the next subsequent 60 TCP/IP ports are free.
Select “Next” to continue.
Progress Explorer Tool configuration screen

TOTVS S.A.
18 Installation and Configuration Datasul 12.1.7

This screen defines if Progress “conmgr.properties” file is configured. This is a file responsible by

the configuration of databases that are managed by Progress Explorer Tool.

Enabling InstallShield to change conmgr.properties file
When selecting this option, “conmgr.properties” file below directory Progress installation
“properties” is changed.
In this case, after starting the AdminService service, you can view the databases by Progress

Explorer Tool.
With this installation, a “conmgr.properties” file is also created below the “scripts” directory of
database installation with databases configuration used by Datasul 11.
Save necessary changes for conmgr.properties.new file
When selecting this option, “conmgr.properties.new” file is created below “properties” directory of
Progress installation and Progress original “conmgr.properties” is not changed.
In this case, before starting the AdminService service, rename “conmgr.properties.new” file for
“conmgr.properties” and then, you can view databases by Progress Explorer Tool.
With this installation, a “conmgr.properties” file is also created below the “scripts” directory of
database installation with bases configuration used by Datasul 11.
Do not change
When selecting this option, “conmgr.properties” file is created below database installation “scripts”
directory, with database configuration used by Datasul 11 and “conmgr.properties” file below

Progress installation “properties” directory is not changed.

In this case, before starting the AdminService service, copy “conmgr.properties” file below “scripts”
directory for Progress “properties” directory, and then, you can view databases by Progress Explorer
Tool.
Select “Next” to continue.
Screen for Installation Information
This screen has a summary of entered information on previous screen. If any information is
incorrect, select option “Back” to perform proper corrections.
When selecting “Next”, databases are installed and configured.

TOTVS S.A.
 Installation Datasul 12 19

1.4.6.1 Configuration of Progress Explorer Tool

Bases used by product are configured to be started by Progress Explorer Tool (proexp). This

application Progress is a graphic tool enabling you to create, configure, start and stop services managed
by local or remote AdminService as, for instance, database, Webspeed, AppServer, among others.
The administration of databases and services configured in Progress Explorer Tool can also be
run through command line.
The configuration performed in Progress Explorer Tool during database installation is basic, that

is, enough to start databases and run access test to product. After finalizing Datasul 11 installation and
configuration, the parameterization of databases and sessions (.pf) must be revised, adjusting them
according to resources available in database server and connections/processes volume with the purpose
of meeting requirements with better performance.
The analysis of environment and adjustment of parameterization can be performed together to the
Database consultancy by phone number 4003-0015, options "02" Software > "03" Technical Consultancy
> "04" Datasul > "08" Technology > "03" Database. Additional information on this service can be obtained
in phone support by phone number 4003-0015, options "02" Software > "02" Technical Support > "04"
Datasul > "08" Technology > "03" Database.

1.4.6.2 Objects created in the installation of Progress Database

Seguem os objetos importantes para administração do ambiente, criados na instalação de

banco de dados em ambiente Windows.

Localization Object Description

<Dir Instal Bancos>\scripts ReparaBancos.bat Script to adjust database structure.
Script to drop databases manually
datasulDescargaBancos.
<Dir Instal Bancos>\scripts started (proserve or _mprosrv) or started
bat
by script “datasulCargaBancos.bat”.
Script to start base. When starting
<Dir Instal Bancos>\scripts datasulCargaBancos.bat database by this script, bases are not
managed by Progress Explorer Tool.
File responsible by the configuration of
<Dir Instal Bancos>\scripts conmgr.properties databases that are managed by Progress
Explorer Tool.

1.4.6.3 Unix / Linux Operational Systems

Installation media does not automatically create database for these operational systems (Linux, AIX,

TOTVS S.A.
 20 Installation and Configuration Datasul 12.1.7

HP-UX, HP-UX Itanium, Solaris, etc.). Therefore, database media must be installed in Windows

environment and the database must be manually created.

1.4.6.4 Base creation with SQL access

Bases “emsdev”, “emsfnd”, “payroll2”, “finance”, “ems2sor”, “mdtfrw”, “mdmerge”, “mdtcrm” e "eai2"
have SQL access and must be created according to procedures described below (for operational system
that are not Windows or for databases manually created). Definitions (.df e .dfsql) can be obtained below

from “<Dir Instal Bancos>\database\definitions” structure.

Access database server console;
Define Progress variable
export DLC=<Dir Instal Progress>
export PATH=<Dir Instal Progress>/Bin:$PATH
Create database
prodb <database name> <Dir Instal Progress>/empty8
Access the Data Administration from Progress by connecting the database in user mono mode

pro -Mm 4096 -cpstream ibm850 -d dmy -E -rx -db <database> -1 -p _admin.p
Run definitions (.df) load by “Admin > Load Data and Definitions > Data Definitions (.df file)” for
databases “emsfnd”, “ems2uni” e "eai2";
Create “sysprogress” user, “sysprogress” password and “pub” user, “pub” password by “Admin > Security >
Edit User List”;
Close session Progress and load database with broker SQL
proserve <database> -S <port> -N TCP -H <database server name> <parameters>
proserve <database> -S <port> -N TCP -H <database server name> -m3 –ServerType SQL
<parameters>
Access a client Windows with installed Progress;
Access the “proenv” from Progress in “Start > Programs > Progress > Proenv”;
Run load of definition (.dfsql) for databases “emsdev”, “finance” e “payroll2”;
sqlexp –user sysprogress –password sysprogress -url jdbc:datadirect:openedge://<database server
name>:<port of broker SQL>;databaseName=<database> -infile <file.dfsql>

TIP: The broker port is the one defined for parameter "-Y" when loading the database with

TOTVS S.A.
 Installation Datasul 12 21

parameter “-ServerType SQL”.

Connect through SQL Explorer the “mdtfrw” database and give permissions of DBA for “pub” user,
through commands below:
sqlexp –user sysprogress –password sysprogress -url jdbc:datadirect:openedge://<database server
name>:<port of broker SQL>;databaseName=<database>

Grant dba to pub;

Commit;
After running these procedures, the databases used by Datasul 11 are installed and configured.
Important to check the document on conexão DataSource configuration for Progress database that
must be performed according to quantity of users using Datasul 12.

1.4.7 Oracle Database

NOTIFICATION: For the use of product in Oracle, the value “NLS_LANG” must be configure
according to CharacterSet used in database (AMERICAN_AMERICA.WE8ISO8859P1 or
AMERICAN_AMERICA.WE8MSWIN1252).

Oracle Instance Screen

Enter the name of Oracle instance used to store this installation objects.

Configuration Screen of Oracle Server

Enter the name of the server and Listener port for this instance on this screen. This information is used to
create the objects in Oracle database.
Location Screen of Datafiles
Enter directory where you want to store the Datafiles of tablespaces that are used for Datasul 11 product.
Screen for Installation Information
This screen has a summary of entered information on previous screen. If any information is
incorrect, select option “Back” to perform proper corrections.
When selecting option “Next”, the scripts for creation of objects in Oracle databases are created
and the Schema Holder are copied.

1.4.7.1 Objects created in the installation of Oracle Database

Below, the files for creation of objects and administration of environment created for installation of
Oracle database.

TOTVS S.A.
 22 Installation and Configuration Datasul 12.1.7

Localization Object Description

Script to create objects (tables, indexes
<Dir Instal Bancos>\scripts criaObjetoOracle.sql
etc.) in Oracle database.
Script to create tablespaces for Datasul
<Dir Instal Bancos>\scripts criaTablespaceOracle.sql
11 product in Oracle database.
Script to create tablespaces for Datasul
<Dir Instal Bancos>\scripts criaUsuarioOracle.sql
11 product in Oracle database.
Script that manages the call of other
Oracle scripts. This file must be run so
<Dir Instal Bancos>\scripts gerenciadorScripts.sql
the objects are created in Oracle
database.
Script to adjust Schema Holder database
<Dir Instal Bancos>\scripts ReparaBancos.bat
structure.

1.4.7.2 Creation of Objects in Oracle Database

The installation media does not automatically create objects in Oracle database. To create these
objects, the “gerenciadorScripts.sql” script must be manually run according to procedures below:
Access the Sql Plus with the “System” user in instance where the objects are created;
Run the command “@<Dir Instal Bancos>\scripts\gerenciadorScripts.sql”;
Check whether errors were created in log files at the end of the process in “<Dir Instal
Bancos>\spool” directory.

1.4.8 SQL Server Database

SQL Server Configurations Screen

Enter user of SQL Serverdatas database.

Password Screen
Enter user password.
SQL Server Configurations Screen
Enter server name and the SQL Server instance and the location for Database datafiles, directory in SQL
Server server.
Screen for Installation Information
This screen has a summary of entered information on previous screen. If any information is
incorrect, select option “Back” to perform proper corrections.
When selecting option “Next”, the scripts for creation of objects in SQL Server database and
Schema Holder are also copied.

TOTVS S.A.
 Installation Datasul 12 23

1.4.8.1 Objects created in the installation of SQL Server Database

Below, the files for creation of objects and administration of environment created for installation of

SQL Server database.

Localization Object Description

Script to create the objects (tables,
<Dir Instal Bancos>\scripts criaObjetoSQLServer.bat
indexes etc.) in SQL Server database.
Script to create databases for Datasul 11
<Dir Instal Bancos>\scripts criaDatabaseSQLServer.sql
product in SQL Server..
Script to create user and associate to
<Dir Instal Bancos>\scripts criaUsuarioSQLServer.sql
databases in SQL Server.
Script that manages the call of other SQL
Server scripts. This file must be run so
<Dir Instal Bancos>\scripts gerenciadorScripts.bat
the objects are created in SQL Server
database..
Script to adjust Schema Holder database
<Dir Instal Bancos>\scripts ReparaBancos.bat
structure.

1.4.8.2 Creation of Objects in SQL Server Database

The installation media does not automatically created the objects in SQL Server database. To
create these objects, the “gerenciadorScripts.bat” script must be manually run according to procedures
below:
Enter directory “<Dir Instal Bancos>\script”;
Run the script “gerenciadorScripts.bat”;

Check whether errors were created in log files at the end of the process in “<Dir Instal
Bancos>\spool” directory.

1.4.8.3 SQL Server Connection

The new connection with SQL Server database does not need to be performed in each station,
ensuring information to be centralized in configuration file.
In this case, the better method is to enter all connection parameters in the command line or in
parameters file (file .pf), method also know as DSN-less.
A DN-less (Data Source Name-less, or connection without database) enabling the application to
specify all parameters directly in the connection line to the database, without the need to configure a
ODBC data source.
A line for DSN-less connection with SQL Server driver is:

TOTVS S.A.
 24 Installation and Configuration Datasul 12.1.7

Driver={<driver>}; Server=<server>; DatabaseName=<database>; Uid=<user>; Pwd=<password>;

1.4.9 Installation of Application Server

When selecting option “Application Server”, Jboss and Datasul Interactive services are installed and
configured for Datasul 11 run.
Below, stages to run this process:

Target Local screen

Enter the directory where the Application Server is installed in the server. We recommend the default
directory suggested by installation media.
Integration Screen with ECM
Enter whether the product is integrated with ECM. In case of questions, select the option “No”, as
this information can be changed at any moment through the configuration file.
Screen of remote run
If remote connections are performed for Datasul 11 access through Datasul Connection for Web

(GoGlobal), Citrix or Terminal Server, option “Yes” must be selected. Otherwise, option “No” must be
selected to proceed with the installation. When selecting option “Yes”, the selection screen of remote
access type is displayed. Select the installation type and fill out as requested:
Datasul Connection for Web
URL: URL that has libs of Datasul Connection for Web (GoGlobal);
Server: Enter the server where the Datasul Connection for Web is installed;
Port: Enter a port available in server for communication between the Jboss and
Datasul Connection for Web.

Terminal Server
Port: Enter a port available in server for communication between the Jboss and
Terminal Server;
Server: Enter the server where the application published in Terminal Server;
Metaframe Port: Enter port used by Terminal Server.

Citrix
URL: URL in which the DatasulCtxWI is published (check configuration Citrix in this

TOTVS S.A.
 Installation Datasul 12 25

Guide);

Server: Enter server where application is published in Citrix;

Port: Enter a port available in server for communication between the Jboss and
Citrix.
Select “Next” to continue.
Machine name screen

Enter server name where database are installed of Datasul 11 product. Select “Next” to continue.
Single Sign On Screen
The Single Sign On (Josso) is installed and configured in the Jboss. Therefore, enter the hostname
of the application server where the Jboss is installed and the communication port with Jboss.
Select “Next” to continue.
Nameserver Screen
Enter the machine name and Nameserver port number of Progress. If not changed, standard port is
5162. This information is used for connection with AppServer created during installation. Select “Next” to
continue.

TIP: This information can be obtained in “ubroker.properties” file located below of Progress
“properties” directory. Parameter defining the communication port with Nameserver is the
“portNumber”, below the structure [Nameserver] or [Nameserver.XXX]. As default, the

Nameserver used is the NS1 with port UDP 5162.

Configurations Screen of Jboss

Enter the access port number to Jboss. We recommend using the default port (8080)
Progress Explorer Tool configuration screen
This screen defines how the “ubroker.properties” file is configured. This is the file responsible by the
configuration of AppServer “Datasul” server that is managed by Progress Explorer Tool.
Enabling InstallShield change the ubroker.properties file
When selecting this option, “ubroker.properties” file below directory Progress installation “properties”
is changed.
In this case, after starting the AdminService service, you can view the bases by Progress Explorer

TOTVS S.A.
26 Installation and Configuration Datasul 12.1.7

Tool.

Save necessary changes for ubroker.properties.new file

When selecting this option, “ubroker.properties.new” file is created below “properties” directory of
Progress installation and Progress original “ubroker.properties.new” is not changed.
In this case, before starting the AdminService service, rename “ubroker.properties.new” file for

“ubroker.properties” and then, you can view “Datasul” AppServer by Progress Explorer Tool.

Do not change
When selecting this option, “ubroker.properties” file is created below database installation “scripts”
directory, with AppServer service configuration used by product and “ubroker.properties” file below
Progress installation “properties” directory is not changed.
In this case, before starting the AdminService service, copy “ubroker.properties” file below “scripts”
directory for Progress “properties” directory, and then, you can view AppServer services by Progress
Explorer Tool.
Screen of License Server Configuration
Enter the License Server and port.
Information screen of installation
This screen has a summary of entered information on previous screen. If any information is

incorrect, select option “Back” to perform proper corrections.

When selecting option “Next”, the services are installed and configured.
When finalizing the configurations, a question on whether you want to enter LDAP configurations is
displayed. This information is used for product integrated login. Without this configuration, even if the SO
user is properly entered with external access type, you are not able to access product by using integrated
login. If option “yes” is chosen, a user and net password is required for configuration with Active Directory
(AD). After configuration with Active Directory, a screen of the conclusion of Application Server installation is
displayed.

NOTIFICATION: The user password entered cannot have character "&", wherein it causes
failure in Jboss initialization. Enter user and password valid in AD without domain and
extension, otherwise, you cannot configure the authentication file used by Josso.

TOTVS S.A.
 Installation Datasul 12 27

1.4.9.1 Objects created in the installation of the Application Server

These are important objects for management of environment, created in the application server

installation.

Localization Object Description

<Dir Instal File responsible for configuration of product
Programs>\scripts- config.xml access shortcut.
[instance]
<Dir Instal Session initialization file with environment
Programs>\scripts- datasul-progress.ini configurations, such as, sources, colors,
[instance] PROPATH, others.
<Dir Instal Script of alias used for product access.
Programs>\scripts- datasul-configxml-alias.p
[instance]
<Dir Instal Script of alias used by "datasul" AppServer
Programs>\scripts- datasul-appserver-alias.p service.
[instance]
<Dir Instal Program used for product initialization.
Programs>\scripts- datasul-aliasIni.p
[instance]
<Dir Instal File with session parameters and connection
Programs>\scripts- datasul.pf parameters with databases.
[instance]
<Dir Instal File responsible by the configuration of
Programs>\scripts- ubroker.properties AppServer “datasul” server that is managed
[instance] by Progress Explorer Tool.

1.4.10 Document Installation

When selecting option “Document”, technical guidelines, functional differences guidelines and
Release Notes are installed. When selecting this option, a question on whether the installation directory of
application server is the one indicated on screen is displayed. If positive, select YES. If negative, select NO
and change this directory.

1.4.11 Initializing Datasul 12

During the Application Server installation, a shortcut for product initialization is created > “Start >
Programs > TOTVS Datasul > Administration > Product Initialization”. In this stage, databases must be
loaded.
Below, stages to run this routine:
Screen for company configuration, country and language
Enter the company name using Datasul 11, CNPJ (only numbers), the country and state of company

TOTVS S.A.
28 Installation and Configuration Datasul 12.1.7

location, as well as the language for use. Select ">" to continue.

Menu Import Groups screen

Tell whether to import the groups * (All) and SUP (Suitable for new INSTALLATION) and must
import SUP group (Suitable for CONVERSION the EMS2, EMS5 And HCM210 to Datasul 12).
Select ">" to continue.
Screen of strings, messages and literais

Enter external strings files location (<Dir Instal Programs>\univdata\pt.d), messages (<Dir Instal
Programs>\univdata\msg.d) and literais (<Dir Instal Programs>\univdata\liter.d). Select u to continue.
Also tell whether to ignore the import of the lyrics in English and Spanish. Select ">" to continue.
Initialization screen of “emsdev” database
On this screen, enter parameters file location (<Dir Instal Programs>\fnd\men\importer\parameters-
[instance].properties), according to the instance being initialized. Enter location directory “.jar” files (<Dir
Instal Programs>\fnd\men). Select ">" to continue.
Configuration Screen Database X Company
Database displayed on screen are the same ones configured for “.pf” file connection below the
structure “<Dir Instal Programs>\scripts”. Select “Start” to continue. This screen is only informative, and you
cannot change connection data through it.
Performance Optimizer
This function improves the environment performance to which the dictionary triggers refers. With

this program run, the triggers with codes are enabled, and triggers not being used are disabled. We
recommend the performance optimizer run in initialization (option “Yes”).
In this moment, the product initialization is run.
The last initialization process stage is the database import for “emsdev” database. During this stage,
the initialization screen is locked. At the end, “btb907za.txt” file is displayed on screen generated below the
programs installation root directory. This file is a run procedures log. The initialization screen is released
after closing log file.

After checking the generated log, close file and select finishing the process.

ATENÇÃO: Verifique a existência NOTIFICATION: Check the existence of “StringTable”

table records. If table is empty, run through the Command Prompt, the “importacaoByYou.bat”

TOTVS S.A.
 Installation Datasul 12 29

script below the root directory of programs installation. After running this script, check the

number of records on screen again.

After product initialization, you must configure business so information is displayed according to
desired in Datasul 12 desktop.

1.4.12 Access to Datasul 12

During the Application Server installation, a shortcut is created > “Start > Programs > TOTVS
Datasul”.

But, before accessing the product, the following procedures must be run:
Start database;
You can start the Progress database through OpenEdge Explorer or script “datasulCargaBancos.
bat”.
Start AppServer “datasul-[ID]-[instance]” service;
You can start the AppServer through OpenEdge Explorer or through the command line by “asbman”.
Start Jboss “TOTVS Datasul” in “Control Panel > Management Tools > Services”;
Start TOTVS License Server service;

1.4.13 Remote Access

Datasul 11 can have a remote access by using the Datasul Connection for Web (GoGlobal), Citrix
Metaframe or Terminal Server (all with installation media separated from product).

1.4.14 Adjust after Installation

The adjusts in this chapter are needed after Datasul 11 installation.

1.4.14.1 Sequences Permission

When the databases automatically created by installation media are not used, you must permit
select and update for user pub in sequences seq_configur and seq_propried. This permission directly
affects the user configuration persistence. If there are no permissions for Sequences, no user configuration
is saved with several errors on screen.
Access the SQL Explorer through the Proenv, connecting the emsfnd database;
Sqlexp –db emsfnd –H <hostname> -S <service> -user sysprogress –password
sysprogress

TOTVS S.A.
 30 Installation and Configuration Datasul 12.1.7

Use the commands below for permissions in the sequence:

Grant select, update on sequence pub.seq_configur to pub;

Grant select, update on sequence pub.seq_propried to pub;
Commit;

1.4.14.2 Configuration for Progress programs access

At the end of installation, Progress programs are available for access only through server where
installation is made. For the access to these programs to be available to all net stations, follow the

procedures listed below:

Share “ERP” directory, attributing reading permission to all users accessing the product.
E.g. \\servidor\ERP
Edit “ERP\scripts-8x80\datasul-progress.ini” file by changing all Propath input for previously
created sharing;
E.g. PROPATH=\\servidor\ERP, \\servidor\ERP\ems2, \\servidor\ERP\ems5, etc
Edit “ERP\scripts-8x80\config.xml” file, changing “.ini”, “.pf” and alias files address for previously
created sharing.

1.4.14.3 Configuration for Plan Management access

If Plans Management is used, create a shortcut specifically to access it in the product. In this case,
the steps below must be followed:

Create a shortcut in config.xml, pointing to a .INI file where the v6Keys value is = Yes. The Plan
Management programs must be run at this shortcut;
Create a shortcut in config.xml, pointing to .INI file where the v6Keys value is = No. This shortcut is
used to run programs of EMS 2/ EMS 5/ HCM.

1.4.14.4 Delivery configuration of authentication e-mail

When the customer e-mail server demands authentication for e-mail delivery, create an e-mail
specific account for Datasul product and configure it in mail-service.xml file in Jboss.
Check if in mail-service.xml file (located in <Jboss>\server\<instance>\deploy), there is a
configuration below to allow e-mail messages to be sent to external e-mails with user authentication:
<property name="mail.smtp.auth" value="true"/>
If positive, it is configure to use authentication of user, so whenever an e-mail is sent, the recipient is

TOTVS S.A.
 Installation Datasul 12 31

the one defined in mail-service.xml file. The a-mail used in "replyTo", that is, for e-mail answer, it will also

be the one configured in mail-service.xml.

Removing the mail.smtp.auth configuration, when trying to send an e-mail for external recipient, if
the e-mail server is configured to demand authentication for e-mail delivery is not possible to continue this
process. If it is sent to internal e-mail, the sender on the e-mail must be the one entered, and not the one
configured in mail-service.xml.

1.4.14.5 Translation Matrix in EMS 5

After a new installation of Datasul 11 product, a Translation Matrix is created for External
Organization in EMS 5 (prgint/utb/utb118aa), if it does not exist.
The matrix is used to identify the organizational unit of EMS 5 corresponding to organizational unit
of EMS 2 related to the user. It is also used when the user changes company in Datasul system (procedure
“Exchange Company User”).
There must be at least one relationship record between the company of EMS 2 with company of
EMS 5.
The External Organization Translation Matrix must have the name “EMS2” and the “Organization
Origin” must be EMS. If there already is a matrix called “EMS2”, it is the official used in the integration
between EMS 2 and EMS 5.
In the matrix, all companies and sites used in EMS 2 must be registered as below:

Organizational Unit Type: company/site used in EMS2.

External Organizational Unit: EMS 2 Organizational Unit.
Organizational Unit: EMS 5 Organizational Unit.
Other information (accounts matrix, cost center matrix and others) do not need to be identified in
this moment.

1.4.14.6 Installation of Plug-in CRM Outlook

To install the plugin, copy the 2 files located in the folder 'crm-outlook' of Datasul 11 product
installation media for a temporary folder in user station.
Run file 'setup.exe', then follow the installation steps. To use the plugin, you must have the Microsoft
Outlook 2010 installed in the station.

TOTVS S.A.
 32 Installation and Configuration Datasul 12.1.7

1.4.14.7 Checking environment after installation

A check-list of the environment enabling the installation and detection of installation failures is

available.
Below the environment check-list:
Check if the items displayed in the requirements chapter were met;
Check if AdminService service is started;
Check if database are loaded

Check if ports used in database load are the same ones defined for their connection;
Check if AdminService service is started;
Check if the Jboss service started without errors in log;
Check if “config.xml” file located below in the structure “<Dir Instal Programs>\scripts-8080” is
properly configured wherein it is the responsible for Progress programs run. If there is any empty tab,
it must be commented or removed;
Check if datasources (“progress-ds.xml” or “oracle-ds.xml” or “mssql-ds.xml”) located in “deploy”
directory of Jboss instance wherein it is responsible for the communication with database. For
Progress environments, this file must point to the ports corresponding to SQL brokers;
Check the existence of “datasul_framework.properties” file located below the structure
“jboss_home\server\instance-8080\conf\datasul” wherein it is responsible for the run of integrated
services with Jboss such as AppServer, Totvs License Server, Flex, among others;

Check if “di.properties” file located below the structure “jboss_home\server\instance-8080

\conf\datasul” is properly configure wherein it is the responsible for the location of “config.xml” file;
Check if “hcm.properties” file located below the structure “jboss_home\server\instance-8080\deploy\
datasul-byyou-XX.X.X-SNAPSHOT.ear\payroll-config-X.X.X.jar” is properly configure wherein “hcmpayroll.
appserverconnection” parameter must be pointed to AppServer service;

1.5 Update
The product update process is performed through the Update Console. The Update Console
Guidelines are available in “D@ - CAT” Community Documents area in Fluig.

1.6 Reinstallation
Reinstallation is run for any of the product components (programs, database and application

TOTVS S.A.
 Installation Datasul 12 33

server), running the installation media setup again. But, before running this process, some verification must

be performed.
NOTIFICATION: It is extremely important to backup current environment before the
reinstallation of any component.
Programs
If the product is operational, select a different programs area from the one used by production

environment. Reinstallation can be used to install programs compiled in Character 32-bit or Character 64-
bit environment for example.
Database
If the product is operational, select a different database server or area from the one used by
production environment. If the same area is entered for reinstallation, all data added until present time are
deleted. Only overlap files if you are sure about your needs. Besides, when reinstalling database, run
initialization run of product again. In Oracle and SQL Server environment, it is recommendable a backup of
Schema Holder before reinstallation to avoid synchronism problems.
Application Server
In Application Server reinstallation, not existing objects are created and existing objects are
substituted. Installation media perform all configurations again.

1.7 Uninstallation
Run uninstallation process only when you do not need components installed in each server wherein this
routine must be run from the server where each component is installed.
To uninstall product in Window environment, select option “delete” from “Datasul 11” in “Start >
Configurations > Control Panel > Add or Delete Programs”. During this process, a deletion confirmation is
requested and a screen of process conclusion is displayed.
This procedure does not delete all files created in the installation process as logs and temporary
files. In this case, check the directories used for installation of components and delete the remaining
objects as necessary.

2 Datasul 12 Configuration

TOTVS S.A.
 34 Installation and Configuration Datasul 12.1.7

2.1 Purpose
The purpose of this Guide is to describe Datasul 12 product configurations displaying the file

where each configuration is performed. Additional information can be located in chapter “Important
Documents”.

2.1.1 Target Audience

The process complexity requires professionals with knowledge of Datasul 11, Progress, Java,
Flex, Jboss and net environment product architecture.

2.1.2 Important Documents

Jboss Guides
Installation Guide;
Getting Started Guide;
Server Configuration Guide.
Get these and other documents at Jboss AS Documentation and Jboss Wiki.
Totvs Guides

Installation Datasul 12.1.7;

Entity and Relationship Model (M.E.R)
The Datasul_11-MER.zip file has artifacts for Datasul 11 product M.E.R query. Document "Datasul
11 - MER.docx" explains how all relationship structure from database to each of the attributes and
indexes are queried.
APIs Programs
In Datasul_11-APIs.zip you can find procedures to use API programs released along with Datasul 11
product and procedures on how to generate Weberservices WSDL.

2.1.3 How to use this guide

Configurations in this guide are capitulated by functionality. Throughout this guide, only the file
name where the configuration is performed is mentioned. In the chapter “Files Localization”, the paths for
files location are listed.

2.2 Configuration file

In this chapter, files and configuration for Datasul 12 product are mentioned.

TOTVS S.A.
 Datasul 12 Configuration 35

2.2.1 Database
Database “emsdev”, “emsfnd”, “mdmerge”, “mdtfrw”, “finance”, “payroll2”, “ems2sor”, “ems2cad”

and "eai2" are directly accessed by Jboss. For this access, datasources are created through progress-ds.
xml file (Progress environment) or oracle-ds.xml (Oracle environment).
List the most important attributes and respective functions:

jndi-name: Datasource Name (You cannot change it);

username: User for connection to database;

password: Password for connection to database;
connection-url: String of JDBC connection to database. E.g.
jdbc:datadirect:openedge://JAGUARIBE:23618;databaseName=emsdev
min-pool-size: Minimum number of active connections to database;
max-pool-size: Maximum number of active connections to database;

There may be more than one connection for the same database, but with different JNDI. If you
need to change the file, be careful about changes in correct place and for all necessary datasources.
For Progress environment, username must be “PUB”, as tables are created below this user.

2.2.2 AppServer
AppServer configuration is performed in datasul_framework.properties file.

progress.server.name=JAGUARIBE
progress.server.port=5162
progress.server.application=datasul-1151-progress-8080
progress.server.maxconnections=5

Description:
progress.server.name: Server where broker AppServer is configured;
progress.server.port: NameServer Port;
progress.server.application: Broker AppServer Name;
progress.server.maxconnections: Maximum quantity of agents that Jboss uses.

If message “Error connecting” during Flex program run, check if AppServer broker configured in
this file is active and properly configured. AppServer broker log file also helps in problems correction.

TOTVS S.A.
36 Installation and Configuration Datasul 12.1.7

Proprieties described below can be configured for AppServer Progress. Check the configuration

that better suits production scenario. As default, all proprieties are disabled and the system works as state-
reset.

progress.server.mode=1
progress.server.statereset.controlpoolcompanyid=false
progress.server.statereset.numberreqconnsclear=-1
progress.server.statereset.evictionthreadrun=120000
progress.server.statereset.mintimeidleobjects=180000

Description:

Propriety Definition Default Comment

value
progress.server.mode Integer {1,2} 1 (state- AppServer broker must
reset/ be configure with the
state- same operational mode
aware) for proper work
(stateless, state-reset or
state-aware).
progress.server.statereset. Logic {true,false} false Controls the impact of
controlpoolcompanyid company change
generating the database
connect and disconnect
in VM Java pool.
(Use only with state-rest
and state-aware)
progress.server.statereset. Integer {-1-200} -1 Used to indicate to VM
numberreqconnsclear Java pool the number of
times a connection with
AppServer can be
reused. Reaching the
limit, it is invalidated
and Pool creates a new
one.
(Use only with state-rest
and state-aware)
progress.server.statereset. Milliseconds 120000ms Controls Thread start
evictionthreadrun (2minutes) time for Idle objects
cleanse in Pool Java.
Applying -1 in propriety
ignores work.
(Use only with state-rest
and state-aware)
progress.server.statereset. Milliseconds 180000ms If propriety

TOTVS S.A.
 Datasul 12 Configuration 37

mintimeidleobjects (3minutes) evictionthreadrun > 0,

defines time an object
remains in Idle status in
the VM Java.
(Use only with state-rest
and state-aware)

2.2.3 Log
In JBoss, logs generation is controlled by “jboss-log4j.xml” file. This file defines a group of
"appenders" basically are log output. As default, JBoss is configured with output for console and log file

(server.log).
The log level to be configured depends on the type of information you need. Datasul 11 product is
configured with log for "ERROR" which means only error messages are displayed in file. This is the proper
configuration for a production environment, so informative messages are not saved in log, making the file
bigger and difficult to be read.
There are six log levels: TRACE, DEBUG, INFO, WARN, ERROR and FATAL. When one of these
levels is defined in the file, all messages above the chosen level are also registered. That is, if level "INFO"
is chosen, all equal messages or superior to this level are written in log (INFO, WARN, ERROR and
FATAL).

The example below is of an appender with output for file, configured as "INFO":

<appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppender">

<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
<param name="File" value="${jboss.server.log.dir}/server.log"/>
<param name="Append" value="false"/>
<param name="Threshold" value="INFO"/>
<param name="DatePattern" value="'.'yyyy-MM-dd-HH"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
</layout>
</appender>

To change the log level, change “Threshold” from "INFO" to desired value. After changing, you do
not need to restart the instance. The jboss-log4j.xml is the only configuration file of JBoss that does not
demand instance restart. The change becomes effective in 60 seconds maximum after saving the file.
In standard configuration of product, the log rotate is performed at each hour. At the beginning of
each hour, the log current log is renamed and log is generated in another file with the same name.

TOTVS S.A.
 38 Installation and Configuration Datasul 12.1.7

Configure log according to its need, aiming at not generating huge size files. You can configure a log rotate

by: month, week, day, midday, hour and minute. To change it, edit the value of option “DatePattern” as table
below:

DatePattern Period
'.'yyyy-MM Rotates log at each month
'.'yyyy-ww Rotates log at each week
'.'yyyy-MM-dd Rotates log at each day
'.'yyyy-MM-dd-a Rotates log at midnight and midday at each day
'.'yyyy-MM-dd-HH Rotates log at each hour
'.'yyyy-MM-dd-HH-mm Rotates log at each minute

Besides Appenders, you can create categories The categories have specific configuration for
determined applications. For example, you can keep the log level as “INFO” and configure another
category for messages of determined application as “WARN”. The example below is of a category of
component “org.jgroups” (cluster) configured as “WARN”:

<category name="org.jgroups">
<priority value="WARN"/>
</category>

Therefore, for all applications, only the messages with “ERROR” level are displayed, but “org.jgroups”
application messages with “WARN” log level.
Get information on log levels here.

2.2.4 License Server

License Server (LS) configuration is performed in “datasul_framework.properties” file in
parameters below:
license.server=calixto
license.port=7777
license.timeout=20
license.showlog=none

Description:
license.server: IP address or LS name;
license.port: Port configured for LS (default 5555);
license.timeout: Time (seconds) for connection with LS. If this time is reached without receiving LS
answer, the emergency key is requested;
license.showlog: Log level for LS messages. Types allowed are: none, all, error, debug, info (default:

TOTVS S.A.
 Datasul 12 Configuration 39

none).

If there is no communication with LS or license is expired, the emergency key is requested.

2.2.4.1 License File Adjust

From Datasul 12.1.1, the validation of product licenses were modified to improve control and
ensure proper use of licenses. This configuration is valid for an installation and updating (Update) of
Datasul 12 where basically it consists of automatic copy of file for work stations.

In this case, when Datasul 12 is accessed by a work station, it automatically copies the dll
for directory c:\windows\, it if does not try to copy for another directory defined in Window PATH
variable due to lack of permission.
When user is not allowed to make copies in any of the directories defined in Window
PATH variable, the administrator must make a manual copy or map the server directory to add the
Windows PATH.
1st suggestion:
Copy file license_client.dll of directory...\ERP\fnd\config\

Glue in directory c:\windows of each work station accessing the Datasul 11

2nd suggestion:

Map the path \\servidor\dts12\ERP\fnd\ as t:\

Add directory t:\config\ in the environment variable of Windows PATH.

Important:
If you use remote access (Citrix, GoGlobal, TS), the license_client.dll file must be copied for directory c:

\windows of tools server.

2.2.5 Jboss Service Configuration

The service “TOTVS Datasul - <ID> - 8x80”, responsible by Jboss load, is created in product
standard installation (Windows environment). When the service starts, the “service-8x80.bat” is run. It
manages the service, besides calling Jboss run line.
In “run.bat” file, the variable “JAVA_OPTS” is configured. This is the standard environment variable
for Java parameters configuration. Noting “service-8x80.bat” and “run.bat” files, we can check this variable
is defined several times, generally concatenating the former value and adding other parameters and

TOTVS S.A.
 40 Installation and Configuration Datasul 12.1.7

values. If you need to add a new parameter, you can add one of these files in any one. The basic difference

is that “run.bat” file is used for all instances wherein the parameters defined in this file are the same for all
instances. The “service-8x80.bat” file is used by instance, enabling yo to defined different values for each of
the instances.

2.2.5.1 Linux

Jboss is installed through the media only for Windows environment. For environments where
Jboss is configured in a Linux server, the Jboss load is performed through the “run.sh” script wherein the

configurations of JAVA_OPTS variable must be performed in “run.conf” file.

For Jboss configuration in Linux server, we recommend you read this kbase.

2.2.5.2 JBOSS Security

Consoles “jmx-console” and “web-console” are used for administrative tasks. All users with
access to the environment also access these consoles and get administrative access in the process of
Datasul 11 product JBOSS.
Some instructions below to configure the authentication for these two JBoss monitors:
1) In ..\deploy\management\console-mgr.sar\web-console.war\WEB-INF\jboss-web.xml file, enable a
security domains removing the tag “<security-domain>” comments as example below:

<?xml version='1.0' encoding='UTF-8' ?>

<jboss-web>
<!-- Uncomment the security-domain to enable security. You willneed to edit the htmladaptor login
configuration to setup the
login modules used to authentication users. -->

<security-domain>java:/jaas/jmx-console</security-domain>

<!-- The war depends on the -->

<depends>jboss.admin:service=PluginManager</depends>
</jboss-web>

2) In ..\deploy\management\console-mgr.sar\web-console.war\WEB-INF\web.xml file, enabling a security

restriction, removing the tag “<security-constraint>” comments, changing the tag “<real-name>” for “jmx-
console”, changing the tags “<role-name>” for “*” as well, as example below:

<security-constraint>

<web-resource-collection>

TOTVS S.A.
 Datasul 12 Configuration 41

<web-resource-name>HtmlAdaptor</web-resource-name>
<description>An example security config that only allows users with the role JBossAdmin to access the
HTML JMX console web application </description>
<url-pattern>/*</url-pattern>
</web-resource-collection>

<auth-constraint>
<role-name>*</role-name>
</auth-constraint>

</security-constraint>

<login-config>
<auth-method>BASIC</auth-method>
<realm-name>jmx-console</realm-name>
</login-config>

<security-role>
<role-name>*</role-name>
</security-role>

3) In ..\deploy\jmx-console.war\WEB-INF\jboss-web.xml file, enable a security domain, removing the tag

“<security-domain>” comments as example below:

<?xml version='1.0' encoding='UTF-8' ?>

<jboss-web>

<!-- Uncomment the security-domain to enable security. You will need to edit the htmladaptor login
configuration to setup the
login modules used to authentication users. -->

<security-domain>java:/jaas/jmx-console</security-domain>

</jboss-web>

4) In ..\deploy\jmx-console.war\WEB-INF\web.xml file, enable a security restriction, removing the tag

“<security-constraint>” comments, changing the tag “<real-name>” for “jmx-console”, changing tags
“<role-name>” for “*” as well, as example below:

<security-constraint>

<web-resource-collection>
<web-resource-name>HtmlAdaptor</web-resource-name>
<description>An example security config that only allows users with the role JBossAdmin to access the

TOTVS S.A.
42 Installation and Configuration Datasul 12.1.7

HTML JMX console web application</description>

<url-pattern>/*</url-pattern>
</web-resource-collection>

<auth-constraint>
<role-name>*</role-name>
</auth-constraint>

</security-constraint>

<login-config>
<auth-method>BASIC</auth-method>
<realm-name>jmx-console</realm-name>
</login-config>

<security-role>
<role-name>*</role-name>
</security-role>

5) Create the files ..\deploy\management\console-mgr.sar\web-console.war\WEB-INF\context.xml and ..

\deploy\jmx-console.war\WEB-INF\context.xml as example below:

<Context>
<Realm className="org.apache.catalina.realm.JAASRealm"
appName="jmx-console"
allRolesMode="authOnly"
debug="1" />
</Context>

6) Change the user password admin in the file ..\conf\props\ jmx-console-users.properties, that are
effective for two monitors as example below:

admin=novasenha

7) In ...\deploy\http-invoker.sar\invoker.war\WEB-INF\web.xml file, add JNDIFactory, EJBInvokerServlet and

JMXInvokerServlet in security domain as example below:

<security-constraint>
<web-resource-collection>
<web-resource-name>HttpInvokers</web-resource-name>
<description>An example security config that only allows users with the role HttpInvoker to access the HTTP
invoker servlets </description>
<url-pattern>/restricted/*</url-pattern>
<url-pattern>/JNDIFactory/*</url-pattern>
<url-pattern>/EJBInvokerServlet/*</url-pattern>

TOTVS S.A.
 Datasul 12 Configuration 43

<url-pattern>/JMXInvokerServlet/*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<role-name>HttpInvoker</role-name>
</auth-constraint>
</security-constraint>

8) In the same file ...\deploy\http-invoker.sar\invoker.war\WEB-INF\web.xml define the security domains by

adding the rows below:

<jboss-web>
<security-domain>java:/jaas/jmx-console</security-domain>
</jboss-web>

9) For JBoss instance that was adjusted.

10) Delete directories date, farm, log, tmp and work of path ...\ServidorAplicacao\jboss-4.2.3.
GA\server\instance-xxxx\
11) Start JBoss and test access to monitors “jmx-console” and “web-console”.

2.2.6 Memory Parameters

To have the ideal performance in the use of this product, properly configure the JVM memory
parameters. These configurations are defined in variable “JAVA_OPTS” previously mentioned. In the
standard installed by the media, the memory parameters are defined in “run.bat” indicating the values

changed are for all instances. We recommend you remove this file configuration and put it in “service-
8x80.bat” (according to instance), so the memory configuration is different for each instance.
Below, a row example with Java memory parameters (installation media standard):

set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx768m -Xss128k -XX:MaxPermSize=512m -XX:

+UseParallelGC -XX:ParallelGCThreads=10

Below, a brief description of each of these parameters:

Xms: Memory parameter defining the minimum of memory for application;

Xmx: Memory parameter defining the maximum of memory for application;
Xss: Size of pile reserved for each thread;
XX:MaxPermSize: Maximum size of permanent objects area in memory;
-XX:+UseParallelGC: Enables the Garbage Collector to open several thread and act in parallel;
-XX:ParallelGCThreads: Number of thread opened for GC. By default, a Thread is opened for
each processor.

TOTVS S.A.
 44 Installation and Configuration Datasul 12.1.7

In a production environment, the ideal is the Xms and Xmx equal value. Upon this configuration,

the Garbage Collector is run with less frequency. To get the ideal value of memory, you need a JVM
monitoring.

2.2.7 Time Out Flex

The Time Out Flex configuration that, until the earlier versions, had only action on flex routines,
from release 11.5.7, acquires the same functionality on progress routines. The configuration is performed
through the “datasul_framework.properties” file, according to standard configurations below:

session.timeout=30
session.timeout.message=2

Description:
session.timeout: Time (minutes) the Web session is active without any user interaction with the system. If
time provided is 0 (zero), the Time Out is turned off.
session.timeout.message: Indicates how long (minutes) before the session.timeout the user message
about session being about to expire is displayed.
The users related to the exception group related to “btb927aa” (TimeOut Basic Parameters) are NOT

disconnected even if these users idleness time exceeds period determined in parameter “session.
timeout”. To disable the TimeOut, change the “session.timeout” parameter value to “0” (zero).
Important: For Progress database, adjust load parameters by adding the following parameters: -basetable
1 –tablerangesize 2500. Time Out Flex is available for Progress and Oracle environment.

2.2.8 Josso
Josso, or Java Open Single Sign-On, is an opensource infrastructure providing a centralized
solution of authentication and authorization of users. It is a component used for users login in Datasul 11
product.
Connection information to Josso are in “josso-agent-config.xml” file. In this file, three inputs are
found with server and port name. If you need to change the server name, this input must be changed.
The authentication configurations are in “josso-gateway-config.xml” file in Ldap. Upon editing the
file, the user to locate information in Ldap is used as well as the password in clear text. If the password is
changed, you can edit the file and manually change it. You can also run the “Domain.vbs” script requesting
information on screen and generating a file (LogDomain.txt) with necessary information to be added in the

TOTVS S.A.
 Datasul 12 Configuration 45

file.

2.2.8.1 Configuration of external access

The configurations below can be used when you need to access Datasul 11 product through an external
IP (out of local net).
Change in “josso-agent-config.xml” file the tags “gatewayLoginUrl” and “gatewayLogoutUrl”, indicating the

external IP address, according to example:

<gatewayLoginUrl>http://189.100.100.100:8080/josso/signon/login.do</gatewayLoginUrl>
<gatewayLogoutUrl>http://189.100.100.100:8080/josso/signon/logout.do</gatewayLogoutUrl>

For this configuration to work properly, parameter “-b” (run.bat file) has “0.0.0.0” value indicating the
instance answers the requirements of all IP address that are configured for server.

2.2.9 Ports
The group of ports to be used by instance in “Jboss-service.xml” file. In example below, the
“ServerName” attribute is pointing to group of ports “ports-8080”:

<mbean code="org.jboss.services.binding.ServiceBindingManager" name="jboss.system:

service=ServiceBindingManager">
<attribute name="ServerName">ports-8080</attribute>
<attribute name="StoreURL">${jboss.home.url}/binding/ports-bindings.xml</attribute>
<attribute name="StoreFactoryClassName"> org.jboss.services.binding.
XMLServicesStoreFactory</attribute>
</mbean>

The “StoreURL” attribute points to “ports-bindings.xml” file that is the file where the group of ports to
be used are found. By the standard installed by media, there are six groups of ports defined in the file: ports-
8080, ports-8180, ports-8280, ports-8380, ports-8480 and ports-8580. The recommendation is to change
these configurations only for Linux environment (as media does not configure the instance for Linux) and in
case you need more instances than the ports configured in “ports-bindings.xml” allow.
If you need to change any port, check if there also is any reference to this same port in the
“datasul_framework.properties” and “jboss-service.xml” files as if there are some ports configured in these
files. The logic is to sum 100 ports for instance 8180, 200 for instance 8280 etc.

2.2.10 Progress Session

In the first run of a Progress program in Datasul 11 in each station, the "Access Configuration"

TOTVS S.A.
 46 Installation and Configuration Datasul 12.1.7

screen is displayed. In the "Run Shortcut" field, you can select the shortcut to run Progress programs.

Information on this screen is stored in “config.xml” file. In this file, you can change the standard shortcut or
even create other shortcuts (for clientlog run, for instance).
To create a new tag <Shortcut>, inside tag <LocalShortcuts>. Change some desired information
in the new line created (Description, Ini, Pf and Alias) and save file. After the change, restart Jboss so the
change works.

In this file, information for remote access to product (Citrix, GoGlobal or Terminal Server) is
located. Further information on this configuration, check Installation Guide, chapter "Remote Access".
The reference for “config.xml” file location is in “di.properties” file. Upon opening the file, “config.
path” attribute is located. It has as value the full path for “config.xml” file location.
In case of slowness in Progress programs load, you can pre load Progress during Datasul 11
initialization. To activate resource to user, select option "Pre load Progress in Initialization". Note: This
resource works only for stations with progress locally installed.
The access preferences can be defined in global level it the user does not know how to configure
or if configuration is not needed, there some tags in "datasul_framework.properties" that serve as
"standard" for all users. These standard values only are ignored when the user defines the own access
preferences.

# indicates the "description" of progress shortcut that must be used as default to load the progress

# this "description" is defined in the file "config.xml" menu.default.shortcut=c:\\dlc102b

# indicates the type of access to progress used, local=false or remote=true menu.default.
remoteaccess=false

2.2.11 Menu
In case of slowness in the programs load in product menu, use the menu consolidation solution.
Enter in datasul_framework.properties the propriety "use.menu.key=true". This propriety is not dispatched
in media standard and is not recommended for environment in which slowness is not identified, as to
reflect changes performed in menu structure (program, module, security group, new users), run the update
program in user menu (mer010aa). If menu structure was changed, but this program is not run, accesses
remain the same.

TOTVS S.A.
 Datasul 12 Configuration 47

2.2.12 RFI – Quotation Portal

Datasul Quotation Portal enables the Supplier to enter quotation directly in the system; therefore,

external access must be allowed for proper work. For further security, parameters below have been
created in datasul_framework.properties file where a server and a port allowing external access are
allowed. This server and port make the link that is sent through e-mail to Supplier when Purchaser
requests quotation.
Configurations of RFI - Request for Information - are also used in other functionalities needing to

request information to external users.

rfi.server=moitas
rfi.port=8080
2.2.12.1 Mail Service

Enter e-mail account of company server (Exchange, Lotus) to enable e-mail delivery through
functions such as Quotation Request used by Purchaser. This account is not used to receive e-mails, only
for delivery.
Example:
<attribute name="User">purchases_company</attribute>
<attribute name="Password">s3nh4_3m4i1</attribute>
2.2.13 Files Location

Ports-bindings.xml* Jboss_home\binding\ports-bindings.xml
Service-8x80.bat* Jboss_home\bin\service-8x80.bat
Run.bat* Jboss_home\bin\run.bat
Run.sh* Jboss_home\bin\run.sh
Run.conf* Jboss_home\bin\run.conf
Jboss-log4j.xml Jboss_home\server\instance-8x80\conf\jboss-log4j.xml
Jboss-service.xml* Jboss_home\server\instance-8x80\conf\jboss-service.xml
Josso-agent-config.xml* Jboss_home\server\instance-8x80\conf\josso-agent-config.xml
Josso-gateway-config.xml* Jboss_home\server\instance-8x80\conf\josso-gateway-config.xml
Datasul_framework. Jboss_home\server\instance-8x80\conf\datasul\datasul_framework.
properties* properties
Di.properties* Jboss_home\server\instance-8x80\conf\datasul\di.properties
Progress-ds.xml* Jboss_home\server\instance-8x80\deploy\progress-ds.xml
Oracle-ds.xml* Jboss_home\server\instance-8x80\deploy\oracle-ds.xml

TOTVS S.A.
 48 Installation and Configuration Datasul 12.1.7

Mail-service.xml* Jboss_home\server\instance-8x80\deploy\mail-service.xml
Config.xml* <Dir installation>\ERP\scripts-8x80\config.xml

* You must restart Jboss so changes work.

2.3 DataSource Progress Connection

Datasul 12 media for Progress database by standard configures some databases with JBDC
access where this configuration involves load script (.bat) and JDBC connection script (.xml).
The load script is assembled based on information provided on screen during Datasul 12

installation with media, when database need to connect JDBC, two rows are added as example below:

call C:\dlc102b\bin\proserve "C:\datasul\ERP\database-8x80\emsfnd" -B

1000 -spin 4000 -L 200000 -Mm 4096 -N tcp -S 27620 -n 101 -Ma 15 -Mn 9 -
Mpb 4
call C:\dlc102b\bin\proserve "C:\datasul\ERP\database-8x80\emsfnd" -
ServerType SQL -m3 -S 27621 -Ma 10 -Mpb 4

The first row loads the broker 4GL by using a port defined by parameter -S and other start
parameters, this port is used by Progress programs
The second row loads the broker SQL by using another port defined by parameter -S, defines

parameter -ServerType SQL and other start parameters, this port is used by JAVA programs.
Below, a Progress database list that, as default, is configured with JDBC access in script progress-
ds.xml:

emsdev
emsfnd
mdmerge
finance
ems2sor
payroll2
mdtfrw
ems2cad
eai2

These databases by default are configured in progress-ds.xml file by using the port defined of

parameter -S of load script row .

Example:

<connection-url>jdbc:datadirect:openedge://server:27621;databaseName=emsfnd</connection-url>

TOTVS S.A.
 Datasul 12 Configuration 49

The Jboss service when started uses this file connect the databases opening a connection pool,

so for some databases, there is more than a pool, as in case of EMSFND.

If the JBoss tries to open a connection and receives an error because the database rejected it,
due to parameters configured, the user receives an error and something does not properly work in Datasul.
Soon, it is important all JBoss pool connections are dimensioned in database load.

How this connection pool works?

When any program needs to access a database, it requires a "borrowed" connection for
corresponding pool. If any connection is opened and nobody is using it, this connection is borrowed to
program. If there is no connection opened and the pool has not reached the limit size (max-pool-size), the
JBoss opens a new connection with database.

If the pool is in the limit, the program waits a while indicated by parameter "blocking-timeout-
millis" in progress-ds.xml file. If a connection is released, the program takes this one borrowed and
continues; otherwise, the program receives an error.

After the program used and released the connection, it returns to pool to be reused.

How many connections are needed?

It depends on the number of users, the users activity, the programs each user runs, the order and

how long each program remains with the "borrowed" connection before returning it to pool.

In order to follow and dimension this number, use /jmx-console, as article How to define the value of field

<max-pool-size> in progress-ds.xml.

What is the minimum configuration recommended for Datasul 12 to work?

In progress-ds.xml file, the max-pool-size parameters comes with standard value 30 measured for
environment with 300 users, because the following calculation is used: 1 connection for 10 users. This
number used as calculation is an average calculation, it may vary according to environment.

This parameter can be adjusted by defining a value corresponding to the number of users using
Datasul 12. EMSFND database needs the minimum of 6 connections to start JBoss, find below the values
that must be used for file configuration.

TOTVS S.A.
 50 Installation and Configuration Datasul 12.1.7

emsFnd
<min-pool-size>1</min-pool-size>
<max-pool-size>1</max-pool-size>

no_tx_emsFnd
<min-pool-size>1</min-pool-size>
<max-pool-size>1</max-pool-size>

ems_josso
<min-pool-size>4</min-pool-size>
<max-pool-size>4</max-pool-size>

It is important to highlight the parameters above are about the minimum connection to be
configured in EMSFND, where for each configured database in file progress-ds.xml, a monitoring of
connections to identify the max-pool-size parameter ideal configuration.
Further details of max-pool-size parameter configuration can be viewed in article How to define
the value of field <max-pool-size> in progress-ds.xml.

2.4 Configuration of Datasul 12 with HTTPS

Information for configuration of Datasul 11 product with HTTPS are described in this document (
HTTPS Configuration).

2.5 Datasul Product Database List

A list of Datasul product databases is shown below.
Mono-company: This structure meets the needs of companies that control only one company.
Multi-company: Due to Datasul-EMS characteristics, only administrative databases address the
multi-company structure and the capacity to store data from multiple companies in a single
database. Thus, customers who wish to control several companies must use the multi-company
database solution, in which the multi-company databases are shared among all companies and
the mono-company databases are duplicated to each specific company. Hence, all companies
share the multi-company databases and each company has its mono-company databases. You
can configure the connection to the databases you need in the connection parameter files. In this
configuration, the number of databases depends on the number of companies. Each company
has a different connection pathway.
Database Records: You can use this database structure to store historical data in separate

TOTVS S.A.
 Datasul 12 Configuration 51

databases that you can access whenever you wish. The transaction data are regularly transfered

from the daily transactions to the historical databases. The transaction databases are thus
constantly accessed in the daily processes, becoming "leaner", significantly improving system
performance as a result. You can also use these databases in a multi-company environment. For
EMS 5, you can only use history databases from release 5.06 onwards.
Specific Databases: you can create databases to contain specific tables from customers. Such

databases should not be merged with the default databases of the product. It's up to the customer
to choose the best way to merge his/her specific databases, as long as these databases remain
separate from Datasul default databases.
ScreenOptimizer: you can merge the mgsop database with the product register databases;
however, you cannot merge the mgsor database, which must remain distinct.
International: databases used by the product by customers outside Brazil.
EAI: this database cannot be merged.
Datasul Transportation(TMS): this product has three databases: mgtrp, movtrp and comtrp (all
mono-company). You can merge all three in a single database.
Database MGAPS: available in EMS 2 from release 2.06B onwards.
Database MGADT: database mgadt is mono-company and cannot be merged. It must remain as
a distinct database.
Database MGMP: this database cannot be merged.

Plans Management 1.00: You can merge the databases of this product, which are mono-
company.
DBR (APS): The databases of this product are mono-company. You can merge them with the
other EMS2 mono-company databases.
Fleet: The databases of this product (mgfro and movfro) are mono-company and you can merge
them with the other EMS2 mono-company databases.
TOTVS Generic: Use the TOTVSGEN database to create new product feature tables, initially
found in Ekanban tables.

Database Description Type Product

mgadt Audit Trail Mono-company ERP

TOTVS S.A.
52 Installation and Configuration Datasul 12.1.7

Database Description Type Product

mgadm Administrative Multi-company ERP

mgaps APS Mono-company ERP

mgcex Foreign trade Mono-company ERP

mgcld Data Collector Mono-company ERP

mgdis Distribution Mono-company ERP

mgfis Tax Mono-company ERP

mgind Industrial Mono-company ERP

mginv Investments Multi-company ERP

mgmfg Manufacturing Mono-company ERP

mgmnt Industrial Maintenance Mono-company ERP

mgmp Multi-plant Mono-company ERP

mgmrp Planning Mono-company ERP

mgrac Representative checking account Multi-company ERP

mgscm Freight/Warehouse Mono-company ERP

mgsop Screen Optimizer Multi-company ERP

mgsor Screen Optimizer Multi-company ERP

mgtmp Temp Multi-company ERP

mguni Universal Multi-company ERP

mgven Vendor Multi-company ERP

mgdbr APS Mono-company APS

movadm Administrative Transaction Multi-company ERP

movdis Distribution Transaction Mono-company ERP

movfis Tax Transaction Mono-company ERP

movind Industrial Transaction Mono-company ERP

movmfg Manufacturing Transaction Mono-company ERP

movmnt Industrial Maintenance Transaction Mono-company ERP

TOTVS S.A.
 Datasul 12 Configuration 53

Database Description Type Product

Representative Checking Account

movrac Multi-company ERP
Transaction

movdbr APS Transaction Mono-company APS

neogrid Neogrid E-collaboration Multi-company ERP

wmovdis Temporary Distribution Mono-company ERP

eai EAI Integration Queue Mono-company ERP

emsinc Business Analytics Mono-company Datasul BA

mgfro Fleet Mono-company ERP

movfro Fleet Transaction Mono-company ERP

emsfnd Foundation Multi-company ERP

emsbas Basic Tables Multi-company ERP

emsfin Financial Registers Multi-company ERP

emsuni Universal Tables Multi-company ERP

emsedi EDI_ Multi-company ERP

movfin Financial Transactions Multi-company ERP

dthrpmg Organizational Development Multi-company ERP

dthrpyc Pay Office Multi-company ERP

dthrcpj Project Control Multi-company ERP

dthrtma Frequency Control Multi-company ERP

dthrgst Personnel Management Multi-company ERP

srcadger General Registers Mono-company Health

srmovben Beneficiaries Transaction Mono-company Health

srmovcon Accounts Transaction Mono-company Health

srmovfi1 Financial Transaction I Mono-company Health

srmovfin Financial Transaction Mono-company Health

srweb WEB Registers/Transaction Mono-company Health

emsdev Framework Multi-company ERP

TOTVS S.A.
 54 Installation and Configuration Datasul 12.1.7

Database Description Type Product

Finance Invest and loans Multi-company ERP

payroll2 HCM Portal Multi-company ERP

emsdca Datasul Accessory Components Mono-company ERP

comtrp TMS Mono-company TMS

mgtrp TMS Mono-company TMS

movtrp TMS Mono-company TMS

emsven Vendor Multi-company ERP

emsgra Grain Multi-company ERP

mdtcrm CRM Mono-company CRM

mdtfrw Metadata Multi-company Metadata

mdmerge Metadata Multi-company Metadata

eai2 EAI2 Multi-company ERP
totvsgen TOTVS Generic Multi-company ERP
cad2loc International Register EMS2 Mono-company ERP
mov2loc International Movement EMS2 Mono-company ERP
cad5loc International Register EMS5 Mono-company ERP

mov5loc International Movement EMS5 Mono-company ERP

Notes:
The restriction to not merge EMS2 product databases with EMS5 databases or with HCM
databases continues, since tables with the same nomenclature exist.
Databases EMSDEV, EMSFND, MDMERGE, FINANCE, EMS2SOR, PAYROLL2, MDTFRW:
Databases accessed via JDBC via SQL port. Merger not recommended.

3 Remote Access Configuration

TOTVS S.A.
 Remote Access Configuration 55

3.1 Introduction
The purpose of this Guide is to describe Datasul 11 product configurations displaying the file

where each configuration is performed.

Important:
According to tools version, some screens can displayed in a different manner from what was
displayed in the guide.
The configuration and installation of GoGlobal, TS and Citrix is customer responsibility. In

case of questions, contact manufacturer support.

3.2 Remote access with TS

The Terminal Server is installed in the server where the remote access is performed.
Below, procedures to be performed for remote access through Terminal Server:

Install Progress Client Networking license in Terminal Server.

Install Java.

Open the RemoteApp Manager of server in ...\Control Panel\Administrative Tools\Terminal

Services\

In RemoteApp Programs, click the right button and add “Add RemoteApp Programs” program

TOTVS S.A.
56 Installation and Configuration Datasul 12.1.7

Click “Next”

TOTVS S.A.
 Remote Access Configuration 57

Click “Browse...” to search Progress executable

Enter Progress\bin + prowin32.exe path

TOTVS S.A.
58 Installation and Configuration Datasul 12.1.7

Click “Finish” to finish creation

Click with right button the row created, go to “Properties”

Change name (RemoteApp program name:), in the example used in Datasul 11, but any name

later used in config.xml file configuration is possible.

TOTVS S.A.
 Remote Access Configuration 59

Create program in TS server that must be with these proprieties

After the creation, config.xml file of Datasul 11 is configured to access TS, important backup
file before changes.
Configure “config.xml” file below structure “<Dir Instal Programs>\scripts”. Below, items to be
configured in this file, so tags not mentioned are not changed.
RemoteConnectionType

TOTVS S.A.
60 Installation and Configuration Datasul 12.1.7

Enter remote connection type (Terminal Server).

E.g. <RemoteConnectionType>TerminalServer</RemoteConnectionType>

RemoteServerPort
Enter a port for communication between the Jboss and Terminal Server;
E.g. <RemoteServerPort>8085</RemoteServerPort>

MetaframeServer
Enter IP of Terminal Server address or name.
E.g. <MetaframeServer>jaguaribe</MetaframeServer>

MetaframeServerPort
Enter access port to Terminal Server.
E.g. <MetaframeServerPort>3389</MetaframeServerPort>

MetaframeServerId
Enter application name created in TS server according to examples above.
E.g. <MetaframeServerId>Datasul11</MetaframeServerId>

RemoteShortcut Description

Enter parameters for Progress session run.

E.g. <RemoteShortcut Description="TS" Path=" -pf &quot;C:

\totvs\datasul\dts1159pgs\ERP\scripts-8080\datasul.pf&quot; -ininame &quot;C:
\totvs\datasul\dts1159pgs\ERP\scripts-8080\datasul-progress.ini&quot; -p &quot;C:
\totvs\datasul\dts1159pgs\ERP\scripts-8080\datasul-configxml-alias.p&quot;" />

Comments:
After changing JBOSS file, restart it.
In the example, the TS is installed in the same Datasul 11 serve, but it can be configured in
another server available in the company. But, you must have Progress installed and updated with
available services packs.

TOTVS S.A.
 Remote Access Configuration 61

Below, an example of file changed with information for access to TS.

Upon accessing Datasul 11, go to Tools\Access Preferences. where information registered in config.

xml file are displayed.

TOTVS S.A.
62 Installation and Configuration Datasul 12.1.7

Upon opening the Progress program, it requests TS server .rdp to be opened.

After this, enter user and net password to validate access to server and open Datasul Interactive.

TOTVS S.A.
 Remote Access Configuration 63

3.3 Remote access with Citrix

3.3.1 Purpose
This content aims at helping the configuration of an environment of Datasul product execution by
using the Citrix execution platform. Necessary steps are approached for Citrix (XenApp and Web Interface)
products configuration and the parameterization needed to Datasul product for proper integration.

3.3.2 Requirements
Some requirements are needed to use this material in Citrix configuration process along with
Datasul product:

Datasul – Version / Release later than 11.5.7 installed.

Citrix – Installed (check supported versions) – Web Interface version 5.x is needed.
Framework .NET 3.5 installed.

J# 2.0 (Redistributable Package) installed.

Progress Client Networking Leave.
Java equal to or later than version 1.6.

3.3.3 Supported versions

XenApp 5.0
XenApp 5.0 FP
XenApp for Windows Server 2008 5.0
XenApp for Windows Server 2008 5.0
XenApp for Windows Server 2008R2 6.0
XenApp for Windows Server 2008R2 6.5
XenApp 7.x
Web Interface 5.x
3.3.4 Citrix Configuration
The installation of Citrix is divided in some application, and each one is responsible by a part of the
configuration execution, as follows:

o Citrix AppCenter: Access in Administrative Tools – Citrix - Management

Consoles. This a the tool responsible by the creation of the application that

TOTVS S.A.
64 Installation and Configuration Datasul 12.1.7

are later published through Web Interface tool.

o Citrix Web Interface Management: Access in Programs – Citrix -

Management Consoles. This is the tool responsible to execute the
publication of the application along with Microsoft IIS.

The first step is the creation of the folder with Citrix execution application: Copy files citrix.
properties, citrix.bat and datasul-framework-citrixproxy-java-1.0.2.jar,
the directory is located in folder scripts below where Datasul application server is installed for a folder in
Citrix server, example: C:\Datasul12.
In the citrix.properties file, indicate:

path=: the path of installation of Progress, example: c:/dlc102b/bin/prowin32.exe

pf=: File .PF with Progress connection data to database, for example: C:/Datasul12/
datasul.pf
ini=: File .INI with data starting Progress, example: C:/Datasul12/datasul-progress.ini.
p=: Alias file for the connection to Progress banks, example: C:/Datasul12/datasul-
alias.p

After the creation of the folder, the next step is the creation of an application in Citrix AppCenter

tool. For this, browse the tree on the left, to the option XenApp (Citrix AppCenter – Citrix Resources –
XenApp) and with right button go to option Run discovery. After executing this option, new knots are
displayed below in the structure.
By clicking with right button in the knot below, the option New - Publish application displayed,
according to picture below:

TOTVS S.A.
 Remote Access Configuration 65

In this option of creation of a new application, enter in the first step name and description of the
application that is executed through Citrix, according to the picture below:

TOTVS S.A.
66 Installation and Configuration Datasul 12.1.7

In the next step, enter the application type that is used. In this case, keep the standard options
suggested (Installed application).

TOTVS S.A.
 Remote Access Configuration 67

In the next step, enter the line of application execution command and the work directory. The

command line must point to citrix.bat file, followed by characters %**, example: “C:\Datasul12\citrix.bat" %
**. The work directory, enter the application folder, example C:\Datasul12. As picture below:

The next step is the server information that executes the application. Enter server before option
Add, according to picture below:

TOTVS S.A.
68 Installation and Configuration Datasul 12.1.7

The next step is related to the configuration of user permissions. Enter option Allow only
configured users and Citrix User Selector. In the option Add, enter users with access to application.
Example of the picture below:

TOTVS S.A.
 Remote Access Configuration 69

As a last step, visual configurations of application, such as icon are applied. No need to change
default options on this screen, as picture below:

TOTVS S.A.
70 Installation and Configuration Datasul 12.1.7

As the application created, the next step is to execute the publication in IIS through the tool Citrix
Web Interface Management. By accessing the tool, in option XenApp Web Site, click option on the right
Create Site.
A screen of configuration is displayed and the first step is to enter IIS site name, publication name
and path. In the field IIS Site, you can keep option suggested Default Web Site. In option Path, enter the
application publication name, this value is repeated in option Name without bars, according to example:

TOTVS S.A.
 Remote Access Configuration 71

The next steps of configuration, default information must be kept.

When finishing the steps, after creating the site, Farm name is requested. In option Farm Name, enter the
same application name, according to picture of example * The other options can be kept according to
suggested standard:

TOTVS S.A.
 72 Installation and Configuration Datasul 12.1.7

At the end, you can test the publication by accessing the address - as example:

https://<servidor>/Datasul12/

3.3.5 Datasul Configuration

To execute the communication between Datasul product and application published from
Citrix in IIS, another application that must be configured and published also in IIS is needed. Along with

TOTVS S.A.
 Remote Access Configuration 73

the default installation of the product, within the application server folder (Jboss), there is a folder name

DatasulCtxWI that must be copied for the server where the Citrix is installed, in the folder previously
created for the Citrix application, example C:\Datasul12. After copied, the full path is C:\Datasul12
\DatasulCtxWI\.

To publish the application DatasulCtxWI access Internet Information Services (IIS)

Manager (Administrative Tools - Internet Information Services (IIS) Manager).

The first necessary step is the creation of an Application Pool, by clicking this option in the
tree displayed on the left. With the right-click button, go to option Add Application Pool. Add a name
to the application pool, indicate version 2.x from framework .NET (.NET 3.5) and use of the Classic
mode, according to picture below:

TOTVS S.A.
74 Installation and Configuration Datasul 12.1.7

After the creation of a new Application Pool, execute change. For this, click the new record in the list and
with the right-click button in option Advanced Settings. In this option, exchange the value of the field
Enable 32-Bit Application for True, according to picture below:

As the following step, create a new application, going to IIS tool on the right, in knot Sites -> Default Web
Site, clicking with right-click button in option Add Virtual Directory.
On screen, enter Alias, with the value of DatasulCtxWI and the local path of the copied folder,
according to example C:\Datasul12\DatasulCtxWI:

TOTVS S.A.
 Remote Access Configuration 75

The next step is the transformation of the virtual directory in an application. For this, click in the knot of the
virtual directory in the tree with the right-click button in option Convert to Application. On screen, select
Application pool previously created, add user and password in option Connect as and execute
functioning test in option Test Settings.

Finished the creation of the application, change the file Web.Config of folder DatasulCtxWI.
In this file, the following variable are changed:

CtxWIConfigFile: It must have the path for WebInterface.conf file of application created by
Citrix. In the example the file C:\inetpub\wwwroot\Datasul12\conf\WebInterface.conf

TOTVS S.A.
76 Installation and Configuration Datasul 12.1.7

CtxFarmName: Name of Farm previously created along with the application Citrix. In the

example the name Datasul12.

As a final step, configure along with Datasul, the access to Citrix, in file config.xml, located below the
structure “<Dir Instal Programas>\scripts”. Below, items to be configured in this file, so tags not
mentioned are not changed.

• RemoteConnectionType
Enter remote connection type (CITRIX).
Ex: <RemoteConnectionType>Citrix</RemoteConnectionType>

• RemoteServerPort
Enter a port for communication between the Jboss and Citrix.
Ex: <RemoteServerPort>8085</RemoteServerPort>

• RemoteShortcut Description
Enter description for connection. The value Path item can be blank,
Ex: <RemoteShortcut Description="Citrix" Path="" />

• MetaframeServer

Enter Citrix server IP address or name.

Ex: <MetaframeServer>citrixserver</MetaframeServer>

• ASPHttpServer
Enter the URL for virtual directory previously published:
Ex: <ASPHttpServer>http://citrixserver/DatasulCtxWI</ASPHttpServer>

• MetaframeServerId
Enter application name created in Citrix server.
Ex: <MetaframeServerId>Datasul12</MetaframeServerId>

TOTVS S.A.
 Remote Access Configuration 77

3.4 Remote access with GoGlobal

For Datasul Connection for Web (GoGlobal) to properly work, point path of “.jar” and “.cab”, and

scripts Java available in installation.

Below, procedures to be run for remote access to be properly run:
Install Progress Client Networking license in Datasul Connection for Web (GoGlobal) server.
Install Java.
Create an application in “GoGlobal Cluster Manager > Applications > Add”.

Display Name – It is the name of the application is run (for this configuration to work properly, this
field value must be “DI”);
Executable Path – It must point to “java.exe”, below the structure “<Dir Instal Java>\ bin\java.exe”;
Start Directory – Temporary directory for the session;
Startup State – Regular.

TOTVS S.A.
78 Installation and Configuration Datasul 12.1.7

Configure log of “GoGlobal 3” in “Tools > Server Options > Log”. We recommend log level 6, so
all events are displayed.
Configure log of “GoGlobal 4” in “Tools > Host Options > Log”. We recommend log level 6, so all
events are displayed.

TOTVS S.A.
 Remote Access Configuration 79

NOTIFICATION: All operational system users must have access and permission to directories

and programs defined in PROPATH of the session, as well as, to files “.ini”, “.pf”, “datasul-
framework-citrixproxy-java-1.0.2.jar” and Progress. If the users are not allowed, access errors are
registered in GoGlobal log.

Configure “config.xml” file below structure “<Dir Instal Programs>\scripts”. Below, items to be

configured in this file, so tags not mentioned are not changed:

RemoteConnectionType
Informar o tipo de conexão remota (GOGLOBAL).
E.g. <RemoteConnectionType>GOGLOBAL</RemoteConnectionType>

RemoteServerPort
Enter a communication port with Datasul Connection for Web (GoGlobal).
E.g. <RemoteServerPort>8085</RemoteServerPort>

RemoteShortcut Description
Enter parameters for Progress session run.
E.g. < RemoteShortcut Description=" GOGLOBAL" Path="-jar &quot;C:\Datasul11\datasul-
framework-citrixproxy-java-1.0.2.jar&quot; &quot;c:\dlc102b\bin\prowin32.exe&quot;
&quot;C:\Datasul11\datasul.pf&quot; &quot;C:\Datasul11\datasul-progress.ini&quot;

&quot;C:\Datasul11\datasul-alias.p&quot; " />

Important: files entered above must be in server of GoGlobal, in the example above, directory C:
\Datasul was created in the server.

MetaframeServer
Enter IP or name of GoGlobal server.
E.g. <MetaframeServer>legacy2</MetaframeServer>

MetaframeServerLibURL
Enter URL where the GoGlobal components (this virtual directory must be published in Web server).

TOTVS S.A.
80 Installation and Configuration Datasul 12.1.7

Ex:<MetaframeServerLibUrl>http://legacy2/goglobal</MetaframeServerLibUrl>

NOTIFICATION: If any of the parameters described above are not properly configured, the
programs are not run. If there is any blank tab, we recommend it to be removed from file
(previously backup file).

Below, an example file changed with information for access to GoGlobal

Upon accessing Datasul 11, go to Tools\Access Preferences. where information registered in

config.xml file are displayed.

TOTVS S.A.
 Remote Access Configuration 81

After this, enter user and net password to validate access to server and open Datasul Interactive.

3.4.1 GoGlobal 4 Adjusts

GoGlobal 4 becomes supported from Datasul 11.5.7. The adjusts are necessary so the connection
with GoGlobal properly works.
RemoteConnectionType
Enter the remote connection type and the full version of GOGLOBAL. The “version_full” can be
located in GoGlobal installation release:
E.g. <RemoteConnectionType>GOGLOBAL#4,7,0,17377</RemoteConnectionType>

RemoteServerPort
Enter a communication port with Datasul Connection for Web (GoGlobal). Add a free port in the

TOTVS S.A.
82 Installation and Configuration Datasul 12.1.7

operational system to avoid ports conflict

E.g. <RemoteServerPort>48085</RemoteServerPort>
Upon installing GoGlobal, check if the machine has a valid domain of product execution, as it
already automatically integrates to LDAP. After installed, configure the type of authentication for the
GoGlobal to transfer user and password information indicated by Datasul product.

For proper work, we select option “Standard authentication” in “GoGlobal -> Host Options ->
Secury”, so GoGlobal requests user and password when opening a session (the user does not need to
enter, as Datasul automatically enters GoGlobal).

Details:
1. When activating the cache option, the user password is stored in cache for some time, however,
when the user changes the password in the domain, the modification of cache in GoGlobal takes
time generating errors (not recommended).
2. When activating “Integrated Windows Authentication”, authentication to open session is not
requested, automatically authenticating user logged in Windows. With this option activated, the
server does not access net resources, not running mappings or scripts. GoGlobal (for the
moment) does not transmit the desktop credentials for server through net. So, you cannot
authenticate the user sessions out for the server (net or other users), disabling programs run.

Below, an example file changed with information for access to GoGlobal

TOTVS S.A.
 Remote Access Configuration 83

Upon accessing Datasul 11, go to Tools\Access Preferences. where information

registered in config.xml file are displayed.

After this, enter user and net password to validate access to server and open Datasul

TOTVS S.A.
84 Installation and Configuration Datasul 12.1.7

Interactive.

TOTVS S.A.