Navigation:  Installation activities > Service configuration >

Adding/Updating databases

Previous  Top  Next

If you need to add a new database or update the existing database(s) after the installation is finished (for example, add a test database), follow the procedure below:

 

During the database configuration process, the system will request the configuration of the e-mail and password to the administrator user, which must follow the following password strength rules:

Must have numbers;

Must have alphabetic character;

Must have uppercase and lowercase characters;

At least 6 characters;

The administrator's e-mail configuration is not mandatory, but it is highly recommended. In case of forgotten passwords, use the "Forgot password?" option to reset it. If the user does not have access to the e-mail registered for the administrator, contact Softexpert support.

 

1.Open the database_config.xml file for editing:

# vi /usr/local/se/conf/database_config.xml

 

2.Add in the file the new database, that is, repeat the entire structure of the <database> tag changing the highlighted values with $:

<?xml version='1.0' ?>

<database>

   <databaseList>

       <database>

           <autoCreate>MANUAL</autoCreate>

           <connectionName>$connection_name</connectionName>

           <databasePassword>$password</databasePassword>

           <databaseUser>$user</databaseUser>

           <db>$database_name</db>

           <domain>$domain</domain>

           <driver>$driver</driver>

           <enable>true</enable>

           <encrypted>false</encrypted>

           <instance/>

           <oraHome>$oracle_home</oraHome>

           <port>$port</port>

           <server>$server</server>

           <synom>false</synom>

           <tableSpaceData>$tablespace_data</tableSpaceData>

         <tableSpaceIndexes>$tablespace_indexes</tableSpaceIndexes>

           <tns>$tns</tns>

           <allowedHosts>

             <host>$host.softexpert.com</host>

           </allowedHosts>

       </database>

   </databaseList>

</database>

 

3.Acceptable parameters for the database_config.xml file, used to connect to the database:

Parameters

Acceptable parameters

Definition and usability

<autoCreate>        

MANUAL

This parameter may not be modified.

<connectionName>

name

Name to be defined by the user, only to name the database in the file.

<databasePassword>

password

Password to access the database data.

<databaseUser>

user

User name to access the database data.

<db>

database_name

Database name, if existent.

<charset>

iso-8859-1

or

"Unicode"

Define whether the database will be iso or unicode. Unicode should only be used for oracle and postgres databases. The standard is iso-8859-1, and the database configurator validates this information.

<domain>

domain

Name of the domain where SE Suite was installed.

<driver>

net.sourceforge.jtds.jdbc.Driver

or

oracle.jdbc.driver.OracleDriver

or

org.postgresql.Driver

Use:

net.sourceforge.jtds.jdbc.Driver to MSSQLServer;

oracle.jdbc.driver.OracleDriver to Oracle; and        

org.postgresql.Driver for Postgresql

<enable>

true

Leave it always as "true".

<encrypted>

false        

For files written manually, always set the value of this parameter as "false". The configurator encrypts this file and changes this value.

<instance/>

 

Used for SQL Server database, when it contains instances. It is left empty by default.

<oraHome>

oracle_home        

If using Oracle, add the oracle 64 bits installation location.

<port>        

5432

or

1521

or

1433

By default, the ports are:

1433 for MSSQLServer;

5432 for Postgresql;

1521 for Oracle.

However, if the connection port is another one, add the correct port.

<server>

server

Name of the database server.

<tableSpaceData>

tablespace_data

Postgresql and Oracle use tableSpaceData, check for it in the database.

<tableSpaceIndexes>

tablespace_indexes

Postgresql and Oracle use tableSpaceData, check for it in the database.

<tns>

tnsName

Enter the tns if the database is Oracle. Oracle Net Services is the tnsnames.ora file. In it, verify the tns name for connection with the database.

<allowedHosts>

host

Fill out the tag when it is necessary to limit the hosts with access permission in the SE Suite requests. If it is not entered, the requests will not be blocked.

 

4.Save and close the file:

:wq!

 

5.Access the SEConfigurator directory:

$ cd /usr/local/se/tools/configurator

 

6.Execute the following command to create and update the added database:

# bash run.sh

 

7.Execute the following command to encrypt the database data of the database_config.xml file:

# java -jar se-configurator.jar -installDirectory="/usr/local/se" -action="0"

 

The options for the action parameter, highlighted in the command above, may be:

0: Encrypts the database information.

1: Decrypts the database information.

2: Creates/updates the database(s).

 

Configuration to avoid Host Header Attack

 

To disable host identification by the header of the request, avoiding the Host Header Attack, it is necessary to add the record below into the ADPARAMS table of each database:

CDISOSYSTEM = 0

CDPARAM = 750

NMPARAM = '<sesuite.company.com>'

 

To add the record, use the following command, updating the example with the host that must be used:

INSERT INTO ADPARAMS (CDISOSYSTEM, CDPARAM, NMPARAM) VALUES (0, 750, '<sesuite.company.com>');

 

This configuration may be undone by deleting this record, for example:

DELETE FROM ADPARAMS WHERE CDISOSYSTEM = 0 AND CDPARAM = 750;