Move Presto and MashZone Repositories to Microsoft SQL Server

1. If you are using your LDAP Directory as the Presto User Repository, make sure that at least one user in your LDAP Directory has administrator privileges for Presto before you move the Presto Repository. See Grant User Access to Presto with Built-in Groups for instructions.

When the Presto User Repository is your LDAP Directory, the default administrator account (Administrator user) is disabled.

2. If you are hosting the Presto Repository or MashZone Repository in a new database, create the database following SQL Server documentation. Keep the following points in mind:

Make sure this database is supported by Presto or MashZone. See Presto and MashZone Database Compatibility for details.

Note:

The JTDS driver for SQL Server is the recommended driver for use with Presto or MashZone and SQL Server databases due to known issues with the default SQL Server JDBC driver.

If you want Presto to support international characters in meta-data for artifacts, make sure the database uses the UTF-16 character encoding and collation. See documentation for your database for specific instructions.

It is a best practice to require passwords for every database account that can access the Presto Repository.

3. Start the database(s) that will become host to the Presto Repository and/or the MashZone Repository, if they are not already up.

4. Using the SQL tool for the database that will be host, add Presto Repository tables with the scripts shown below from the corresponding folder in presto-install/prestorepository/mssqldb:

createDBTables.txt for MetaData and the default User Repository

This folder also contains scripts to drop the corresponding Presto Repository tables, if needed.

5. Copy the JAR file for the JDBC driver for your database to the following folder for each Presto Server that uses this Presto Repository or MashZone Server that uses this MashZone Repository:

a. Remove the web-apps-home/presto/WEB-INF/lib/jackbe-presto-rds-postgresql-derby.jar JAR file for each Presto Server that uses this Presto Repository. You can delete this JAR or simply move it to a folder that is not in the classpath for the application server that hosts Presto.

presto-install/prestorepository/jackbe-presto-rds-oracle-mysql-mssql.jar

7. Update snapshot scheduler configuration for the Presto Server:

a. In the text editor of your choice, open the applicationContext-scheduler.xml file in the webapps-home/presto/WEB-INF/classes/ folder for the Presto Server.

b. Find the bean for org.springframework.scheduling.quartz.SchedulerFactoryBean.

c. Update the org.quartz.jobStore.driverDelegateClass property to the org.quartz.impl.jdbcjobstore.MSSQLDelegate appropriate delegate for this database:

e. If this is a clustered environment, copy the updated applicationContext-scheduler.xml configuration file to each Presto Server in the cluster.

8. Open the presto-install/apache-tomee-jaxrs/conf/tomee.xml configuration file in the text editor of your choice.

9. For the Presto Repository, edit the <Resource> element with an ID of PrestoRepository and:

<Resource id="PrestoRepository" type="DataSource">
JdbcDriver net.sourceforge.jtds.jdbc.Driver
JdbcUrl jdbc:jtds:sqlserver://host-name:port/database
UserName username
Password password
JtaManaged = false
</Resource>

b. If needed, update optional properties. See TomEE Datasource Properties for a complete list of optional properties and information on defaults.

10. For the MashZone Repository, edit the <Resource> element with an ID of amzDatabase and:

<Resource id="amzDatabase" type="DataSource">
JdbcDriver net.sourceforge.jtds.jdbc.Driver
JdbcUrl jdbc:jtds:sqlserver://host-name:port/database
UserName username
Password password
defaultAutoCommit = true
maxActive = 200
maxIdle = 20
maxOpenPreparedStatements = 0
maxWaitTime = 5000
</Resource>

b. If needed, update optional properties. See TomEE Datasource Properties for a complete list of optional properties and information on defaults.

If the Presto Server does not start up successfully, see Troubleshooting Connections to the Presto Repository for suggestions.

12. Open the rdsJDBC.properties configuration file, from the web-apps-home/presto/WEB-INF/classes folder, in the text editor of your choice and:

a. Comment out the property definitions for the Derby database.

b. Uncomment the properties for MSSQL and update these properties to match the JNDI configuration your previously updated for TomEE.

You must keep JDBC and JNDI configuration synchronized for the Presto Repository. The application server is using JNDI to connect to the Presto Repository, but some components still use JDBC information.

13. Restart the Presto Server to apply these changes. This also restarts the MashZone Server.

If the Presto Server wedoes not start up successfully, see Troubleshooting Connections to the Presto Repository for suggestions.

14. Update connection information for the Snapshots Repository:

b. Add a JDBC driver for the new database that should host the Snapshots Repository. See Add or Manage JDBC Drivers for instructions on adding JDBC drivers.

c. Expand the JDBC Configuration menu, if needed, and select Datasources.

e. Update configuration to point to the new database. See Add a Data Source for information on specific configuration properties.

16. Load macros required for the Snapshot feature in Presto:

a. Open a command or terminal window and move to the presto-install/presto-cli/bin folder.

b. Enter the appropriate command, shown below, for your operating system:

For Windows	For Linux, OS/X or UNIX
publish-global-macros.bat -u Administrator -p manage -url http://app-server:port/presto/edge/api	./publish-global-macros -u Administrator -p manage -url http://app-server:port/presto/edge/api