Connection to DBAccess via Connection String

Protheus now has a more agile connection to the Database, with an uncomplicated configuration. If, before, you needed to configure the connection in the appserver.ini file, alias in the DBAccess and OBDC in the Operational System, now you need a initial configuration through a wizard screen and all necessary information is automatically saved only in the appserver.ini file.
Important:

• The appserver.ini file can neither have section \[DBAccess\] nor the lines DBAlias, DBServer, DBDatabase and DBPort in the \[Environment\] section.

• The improvement is available only for database Oracle, MSSQL and Postgres, in the homologated versions and in the lifecycle.
  To configure, follow these steps:
  1. Remove the configuration lines of DBAccess of the appserver.ini file, according to the notification above; 2. Access Protheus entering any module; 3. A screen of Communication with Database displayed.
  
  • DNS of the DBAccess server: IP address of the server where the Dbaccess is • Port of DBAccess server: Port the DBAccess is starting • Owner Database: Database being used • Driver: Driver to be used for database (Oracle does not have driver, leave it blank) • Schema or database: Database name • DNS of database server: IP address of the server where the database is - For Oracle, it is the address of the server+port+Service Name, found in tnsname.ora: P11A= (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = VMFW66213.sp01.local)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = orcl)
  In the example above, the DNS will be: VMFW66213.sp01.local:1521/orcl - For MSSQLServer, add the address name/address of the server+port Ex.: SPON010114158\SQLEXPRESS:1433 - For Postgres, enter address with port. Example: localhost:5433
  • Login of database: Database user (dbo) accessing the system. Important: The user must have the minimum permissions necessary to access the system and the creation of users • Database password: User password above
  4. After configuring, click Validate connection to test whether configuration is correct. If positive, the window Connection successfully executed is displayed.
  
  5. Click Save to confirm configuration
  6. From this moment on, the system is already configured and ready to use. Connection data saved in appserver.ini file. This configuration screen is not displayed.
  The connection wizard screen is displayed for each environment that is accessed, without DB configuration lines in the appserver.ini file.
  Notice:
  The dbo user and password are saved in the database on a specific screen. Data are cryptographically saved and its access is only allowed by a specific user created by Protheus (sysdba). He is the only one to read the table and decrypt data saved. With user and password of the database, the ERP connections are made.
  Availability:
  From LIB version 20180820 and DBAccess version 20171117-20180412
  Note:
  If necessary, enter any information after this initial configuration, edit it directly in the appserver.ini file