1.4.3. Configuration General Steps

1. DataBase Creation

Create only the database on the chosen DBMS; The schema set (tables, primary keys, triggers ...) will be created automatically later on a first deployment, at a time when the application recognizes that it does not exist. The process will vary slightly:

• For Oracle: In this case the access and creation of the schema is per user. So it will be sufficient to create a user for this purpose with sufficient privileges. This user will be indicated in the Tomcat server.xml configuration file. For example, in case the user is DashboardSII:

CREATE USER DASHBOARDSII IDENTIFIED BY DASHBOARDSII;

• For SqlServer: A schema with the database name defined in the connection will be created. For example, in the event that the database is called sii:

CREATE DATABASE sii […];

• For MySql: Just as in the case of Sql Server will create a scheme with the name DashboardSII:

CREATE SCHEMA DashboardSII;

2. Configuration of the SIIDashboard.properties property file

It copies the properties file used by the dashboard in the desired path.

A good choice would be the server's configuration folder; In the case of Apache Tomcat, the '/ conf' folder. Although it could be anywhere else. The path where it is saved will be used later to give value to an environment variable that the application will use to retrieve the identifier of the tenant.

Therefore, this property file will basically have a single property.

3. Configuring the connection to the database

The configuration of the connection to the database (url, user, password, driver...), can be done either through the web container itself or through the properties file of the application. 

• Inside the Web container

Although the specific way to do this configuration will depend on the chosen server, we will use as a reference example the Apache Tomcat server, because it is the server on which the solution has been developed and tested.

The specific configuration will depend on the database engine used (Oracle, SqlServer or MySql). For each of them, a separate connection pool will be defined; one for the web appliance and SOAP services, and another for the alarm engine.

• Oracle 

Name of the exclusive JNDI resource for the web part and the SOAP services: jdbc/SIIOracle

Exclusive JNDI resource name for the alarm engine: jdbc/SIIOracleScheduler

For Apache Tomcat, in the file 'server.xml', within the <GlobalNamingResources> block, a new <Resource> tag is added with the connection data to the database. 

For Apache Tomcat, in the 'context.xml' file we create a new <ResourceLink> entry inside the <Context> block to reference the connection to the database previously declared in the file 'server.xml'.

If we set the value for the attributes "global" and "name" match the name given to the resource we created earlier.

Copy in the '/ lib' directory, if it does not exist, the Java connection library to Oracle: ojdbc7.jar

• Sql Server 

Name of the exclusive JNDI resource for the web part and the SOAP services: jdbc/SIISqlserver

Exclusive JNDI resource name for the alarm engine: jdbc/SIISqlserverScheduler

For Apache Tomcat, in the'server.xml' file, within the <GlobalNamingResources> block, a new <Resource> tag is added with the connection data to the.er database.

For Apache Tomcat, in the 'context.xml' file we create a new <ResourceLink> entry inside the <Context> block to reference the connection to the database previously declared in the file 'server.xml'.

If we set the value for the attributes "global" and "name" match the name given to the resource we created earlier.

We copy in the directory '/lib', in case it does not exist, the Java library of connection to SqlServer: sqljdbc4-6.0.jar

• MySql

Name of the exclusive JNDI resource for the web part and the SOAP services: jdbc/SIIMySQL

Exclusive JNDI resource name for the alarm engine: jdbc/SIIMySQLScheduler

For Apache Tomcat, a new <GlobalNamingResources> tag with the database connection data is added to the <GlobalNamingResources> block in the'server.xml' file.

For Apache Tomcat, in the 'context.xml' file we create a new <ResourceLink> entry inside the <Context> block to reference the connection to the database previously declared in the file 'server.xml'.

If we set the value for the attributes "global" and "name" match the name given to the resource we created earlier.

Copy to the '/ lib' folder, if it does not exist, the Java library connecting to SqlServer: mysql-connector-java-5.1.42.jar

• Through the properties file

Alternatively, you can define the database connection data via the 'SII-Dashboard.properties' property file. In this case the properties to be specified are:

• datasource.url: Url of connection to the BD
• datasource.username: User name of access to the BD
• datasource.password: Password to access the BD
• sii. datasource.driver-class-name: Name of the driver used for the connection (depending on the database engine used)

4. Declaration of the path to the properties file

We create an environment variable with the path where the 'SII-Dashboard.properties' property file we have copied previously.

For Apache Tomcat, the context.xml file defines a new <Environment> entry within the <Context>

The full path where the property file is specified as value of the attribute "value"

5. BD's profile statement

In the configuration file 'context.xml' of Apache Tomcat, a new variable is defined to indicate the profile used according to the database.

• For Oracle:

• For SqlServer:

• For MySql:

 6. Set Java configurations at startup of the application server

• Windows:

• Unix: