Move the MashZone NextGen repository to PostGres

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

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

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

Make sure this database is supported by MashZone NextGen. See Additional MashZone NextGen System and Software Requirements for details.

If you want MashZone NextGen to support international characters in meta-data for artifacts, set the character encoding to UTF8 when you create the database. See documentation for your database for specific instructions.

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

When you initialize the PostGres database that will host the MashZone NextGen Repository, you may need to specifically set the locale used by the database to ensure case-insensitive sorting.

3. Start the database that will become host to the MashZone NextGen Repository, if it is not already up.

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

createDBTables.txt for MetaData and the default User Repository

createSnapsTables.sql for Snapshots

createSchedulerTables.sql for Scheduler

There are also scripts to drop the corresponding MashZone NextGen Repository tables in these folders, if needed.

5. Update snapshot scheduler configuration for the MashZone NextGen Server:

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

b. Find the bean for org.springframework.scheduling.quartz.SchedulerFactoryBean in default profile.

c. Update the org.quartz.jobStore.driverDelegateClass property to the org.quartz.impl.jdbcjobstore.PostgreSQLDelegate delegate.

The configuration would now look like:

...
<bean id="scheduler"

>
<property name="applicationContextSchedulerContextKey">
<value>applicationContext</value>
</property>
<property name="quartzProperties">
<props>
<prop key="org.quartz.scheduler.instanceId">AUTO</prop>
<prop key="org.quartz.jobStore.class"> org.quartz.impl
.jdbcjobstore.JobStoreTX</prop>
<prop key="org.quartz.jobStore.tablePrefix">QRTZ_</prop>
<prop key="org.quartz.jobStore.driverDelegateClass"> org.quartz
.impl.jdbcjobstore.PostgreSQLDelegate</prop>
<prop key="org.quartz.jobStore.dataSource">schedulerDS</prop>
...
</props>
</property>
</bean>
...

d. Save this change.

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

6. Copy the JAR file for the JDBC driver for your database to the following folder for each MashZone NextGen Server that uses this MashZone NextGen Repository: MashZoneNG-install/apache-tomcat/lib.

7. Open rdsApplicationContext.xml under MashZoneNG-install/apache-tomcat/classes and add the following keys to:

8. If you are using PostgreSQL version 9.x please open postgresql.conf under PostgreSQL-install/9.x/data and un-comment the following property and make sure it is set to off: standard_conforming_strings = off.

9. Open the MashZoneNG-install/apache-tomcat/conf/context.xml configuration file in the text editor of your choice.

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

a. Update the JDBC driver, URL and credential properties:

name="MashzoneNextGenRepository" auth="Container"
type="javax.sql.DataSource"
maxTotal="200" maxIdle="30" maxWaitMillis="10000"
username="app" password="app"
driverClassName="org.postgresql.Driver"
url="jdbc:postgresql://host-name:port/databasename"
/>

The JTA managed property must be false.

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

Some common properties you may need to set include:

validationQuery = select 1

Common tuning properties for connections pools. See Tuning the MashZone NextGen Repository Connection Pool.

11. Save your changes to this file.

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

12. Restart the MashZone NextGen Server to apply these changes. This also restarts the MashZone Server.

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

13. Update connection information for the Snapshots Repository:

a. Open MashZone NextGen Hub and login.

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.

d. Select SnapshotDatasource and click

Edit.

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

f. Click Save.

14. Restart the MashZone NextGen Server to apply these changes.

15. Load macros required for the Snapshot feature in MashZone NextGen:

a. Open a command or terminal window and move to the MashZoneNG-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/mashzone/edge/api	./publish-global-macros -u Administrator -p manage -url http://app-server:port/mashzone/edge/api