Migration Steps - tomcat bundle

1. Stop
2. Create a folder named <frevvo-home>\config i.e. c:\frevvo\config. Copy your configuration.xml to this location
3. Locate & Delete your previous database resource definition(s)
   1. Edit configuration.xml
   2. Delete all lines between and including <resource-def></resource-def> for all querysets
      

      To help locate this, here is a example of a Datasource definition in configuration.xml

      <resource-def>
          <url>YOUR database Url HERE</url>   
          <driver>YOUR driver HERE</driver>
          <user>YOUR database user HERE</user>
          <password>YOUR password HERE</password>
      </resource-def>

   3. Delete all lines between and including <resource-ref></resource-ref>. You would have <resource-ref> definitions in your configuration.xml if you chose to define the database connection in the application container (Tomcat if you are using the frevvo-tomcat bundle) instead of inside the database connector.
      
      To help locate this, here is an example of a Datasource definition using <resource-ref>.

      <resource-ref>
          <description>MySQL Customers</description>
          <res-ref-name>jdbc/mystore_ds</res-ref-name>
          <res-type>javax.sql.DataSource</res-type>
          <res-auth>Container</res-auth>
      </resource-ref>

4. Setup your v2.5.3+ database resource definition(s)
   1. Create <frevvo-home>\tomcat\conf\frevvo-config.properties (if it does not already exist in your v7.3.2 frevvo server)

   2. For each deleted <resource-def> lines, Add these lines

      dbconnector.queryset@<your queryset name>.resource-def.url=<the url to your database>
      dbconnector.queryset@<your queryset name>.resource-def.user=<your database username>
      dbconnector.queryset@<your queryset name>.resource-def.password=<your database password>

   3. For each deleted <resource-ref> lines, Add this line

      dbconnector.queryset@mystore.resource-ref.name=jdbc/<name of your resource>

5. Start Live Forms
6. Browse  http://localhost:8082/database/status. Verify that the query validation page is loaded with status Passed
7.  Log into your tenant  and test your forms and flows that interact with your database.

Migration Steps - Standalone

1. Stop the Standalone Database Connector.  You can do this by closing the window if you started the DB Connector with the java command or by executing the Stop-DB Connector.(sh,bat) file if you installed it as a service.
2. Locate & Delete your previous database resource definition(s)
   1. Edit configuration.xml
   2. Delete all lines between and including <resource-def></resource-def> for all querysets
      

      To help locate this, here is a example of a Datasource definition in configuration.xml

      <resource-def>
          <url>YOUR database Url HERE</url>   
          <driver>YOUR driver HERE</driver>
          <user>YOUR database user HERE</user>
          <password>YOUR password HERE</password>
      </resource-def>

      The use of <resource-ref> definitions is NOT supported when running the Database Connector in standalone mode

3. Copy the modified configuration.xml file to the <db-home>\database-connector-2.5.x\config .

4. Copy the JDBC driver for your database into <db-home>\database-connector-2.5.x\lib. Remember the MSSQL driver is included in the standalone database war

5. Setup your v2.5.3+ database resource definition(s)
   1. Edit the <db-home>\database-connector-2.5.x\conf\dbconnector.properties file

   2. For each deleted <resource-def> lines, Add these lines

      dbconnector.queryset@<your queryset name>.resource-def.url=<the url to your database>
      dbconnector.queryset@<your queryset name>.resource-def.user=<your database username>
      dbconnector.queryset@<your queryset name>.resource-def.password=<your database password>

6. Restart the connector
   
   1. Open a command prompt and navigate to the <db-home>\database-connector-2.5.x directory
      
      1. Type java -jar database.war or click the Restart-DBConnector-Service.bat,sh files if you installed it as a service/daemon
7. Browse  http://localhost:8081/database/status page. Verify that query validation page is loaded with status Passed
8.  Log into your tenant  and test your forms and flows that interact with your database.