For Information on supported versions of MS SQL Server please see Supported Platforms


Deployment

  • During the Install, choose Use Existing MS SQL server option to deploy the MSSQL files.
    • In case database is not created successfully, SQL file can be found in C:\Ephesoft\Dependencies\MsSQLSetup\ephesoft-mssql-config.sql file.
    • Have DBA Run this SQL script as Sysadmin
Note: If allocation of space is required the following is recommended:

– Ephesoft DB: Minimum of 10GB
– Ephesoft Report DB: Minimum of 20GB.

Configuration – MS JDBC Driver

 

  • Ephesoft will be configured automatically based on the information given during the Installation.

If any of the settings needs to changed, locate configuration files in following locations:

v4.0.2.0 or Lower:

  • C:\Ephesoft\Application\WEB-INF\classes\META-INF\dcma-data-access
  • C:\Ephesoft\Application\WEB-INF\classes\META-INF\dcma-performance-reporting
  • C:\Ephesoft\Report\ephesoft-reporting\META-INF\dcma-performance-reporting

v4.0.3.0 or Higher:

  • C:\Ephesoft\JavaAppServer\conf\server.xml

 

Windows Authentication

Please follow instructions here


Server Configuration Changes

Open the MS SQL server configuration manager

  1. Enable “TCP/IP” for the server instance.
  2. For the TCP/IP properties, disable the “Dynamic Ports” and set the port number to 1433.
  3. Enable SQL Server Browser in SQL Server services.

 


Configuration – JTDS Driver

  • Locate dcma-db.properties in C:\Ephesoft\Application\WEB-INF\classes\META-INF\dcma-data-access folder and change following properties based on your SQL server connection needs.
  • dataSource.driverClassName=net.sourceforge.jtds.jdbc.Driver
  • dataSource.url=jdbc\:jtds\:sqlserver\://localhost;user\=ephesoft;password\=ephesoft;databaseName\=ephesoft2

Configuration – JTDS Driver Using Named Instance (MSSQL)

There are two possible methods for connecting to a Database using a Named Instance:

jdbc\:jtds\:sqlserver\://${dataSource.serverName}\:<port>;databaseName\=${dataSource.databaseName};instance=<instance_name>;user\=${dataSource.username};password\=${dataSource.password}

jdbc\:jtds\:sqlserver\://${dataSource.serverName}\:<instance_port>];databaseName\=${dataSource.databaseName};user\=${dataSource.username};password\=${dataSource.password}


Performance

Ephesoft recommends JDTS for hi-volume production systems as our tests showed considerable performance gains over MS driver.


Reporting

Update the database name in the standalone installer in the following files:-

  1. ReportingUpdates\MSSQL\installer\Report\ephesoft-reporting\META-INF\dcma-performance-reporting\source.hbm.xml
    This should point to dcma database, currently it is pointing to “dcma”.
    If the database name needs to be changed, please replace all occurrences of “dcma” with the updated db name.
  2. ReportingUpdates\MSSQL\installer\Report\ephesoft-reporting\META-INF\dcma-performance-reporting\target.hbm.xml
    This should point to reports database, currently it is pointing to “reports”.
    If the database name needs to be changed, please replace all occurrences of “reports” with the updated db name.
    1. Update the connection URL for the database name in the standalone installer in the following file:
      ReportingUpdates\MSSQL\installer\Report\ephesoft-reporting\META-INF\dcma-performance-reporting\hibernate.cfg.xml
      <property name=”connection.url”>jdbc:sqlserver://localhost;database=reports;integratedSecurity=true;</property>
    2. Update the connection URL for the database name in the standalone installer in the following file:
      ReportingUpdates\MSSQL\installer\Report\ephesoft-reporting\META-INF\dcma-performance-reporting\hibernate-dcma.cfg.xml
      <property name=”connection.url”>jdbc:sqlserver://localhost;database=dcma;integratedSecurity\=true;</property>
      All the other set up steps are same as previous releases.

Please check the username, password and database name in the following property file in ephesoft application folder: {ephesoft-home}\WEB-INF\classes\META-INF\dcma–performance-reporting\dcma-report-db.properties.


How to monitor database activity on MSSQL?

Open Activity Monitor in SQL Server Management Studio by pressing Ctrl+Alt+A

Was this article helpful to you?

Walter Lee

Comments are closed.