EASA Help Pages

User Tools

Site Tools

You are here: EASA 6.1 » Administrator Guide » Setup a new EASA 6.1 installation to use a remote database

Sidebar

About EASA | Contact

Contents

Setup a new EASA 6.1 installation to use a remote database

Follow these steps to configure a remote EASA database.

1→ Follow Setup EASA 6.1 on Windows with a local database to configure an EASA Server only the following steps will be different.

Skip 'Downloading MySQL…', step A.6 (insure there is not a mysql-5.7.17-win32.zip file in the same folder as the installer).

Click No at step B.8 (pictured here).

At the next popup, click Ignore (pictured here).

After the installation has concluded do not start the EASA Tomcat8 service in step B.9

2→ Remove the folder <EASAROOT>\db

3→ Install a database on a remote machine, EASA currently supports MySQL, SQL Server and Postgres.

4→ As root or an equivalent high-privilege user, run the relevant script or backups to create the EASA database schema.

  • the EASA schema consists of four required databases,
    • easa
    • excel
    • excelTesting
    • signer
  • stockdata is provided with the default MySQL installation to show how an external database is connected by an Administrator and accessed by an EASAP in the Stock Screener Tool (Database Tutorial). We provide Postgres and SQL Server scripts and backup files.

5→ We need to configure EASA machines to connect to each database via the following files,

  • <SERVERDATA>\easa-share\admin\config\
    • easa.cfg.xml
    • excel.cfg.xml
    • excelTesting.cfg.xml
    • signer.cfg.xml
  • for each file above update
    • hibernate.connection.username with the actual username
    • hibernate.connection.password with the actual password
    • hibernate.dialect with the correct path,
      • org.hibernate.dialect.MySQLDialect
      • org.hibernate.dialect.SQLServerDialect
      • org.hibernate.dialect.PostgreSQLDialect
    • hibernate.connection.url with the actual IP address, port number, and database name in the required format,
      • jdbc:mysql://localhost:3306/db-name?autoReconnect=true
      • jdbc:sqlserver://localhost:1433;DatabaseName=db-name
      • jdbc:postgresql://localhost:5432/db-name
    • hibernate.connection.driver_class with the correct driver class
      • com.mysql.jdbc.Driver
      • com.microsoft.sqlserver.jdbc.SQLServerDriver
      • org.postgresql.Driver
      • see Database drivers in EASA then download and copy driver to <EASAROOT>\tomcat\lib

Below is an example of a portion of a modified .cfg.xml config file. 

<property name="hibernate.connection.driver_class">com.mysql.jdbc.Driver</property>
<property name="hibernate.connection.url">jdbc:mysql://192.168.12.56:3306/signer?autoReconnect=true</property>
<property name="hibernate.connection.username">user</property>
<property name="hibernate.connection.password">password</property>
<property name="hibernate.dialect">org.hibernate.dialect.MySQLDialect</property>
  • SQL Server requires modifications to hibernate.default_schema property
    • for easa database comment out hibernate.default_schema ​(ie. <​!-- I'​ve-been-commented-out -->​ )
    • for excel database set hibernate.default_schema to excel.dbo
    • do the same for exceltesting and signer
      • (ie. set hibernate.default_schema to exceltesting.dbo and signer.dbo, respectively)
    • additionally to use Windows Authentication instead of SQL Server Authentication do the following
      1. copy both the driver sqljdbc42.jar and library sqljdbc_auth.dll (from the linked .zip) to <EASAROOT>\jre\bin
      2. append integratedSecurity=true to the database connection URL in each .cfg.xml file above
        • ie. jdbc:sqlserver://localhost:1433;DatabaseName=easa;integratedSecurity=true

6→ Start the EASA Tomcat8 service, test the database.

  • login as admin
  • run a test query for each database from
    • EASA→Configure→Databases→Configure Databases→Query tester

Page Tools