Move the Business Analytics repository to PostGres
1. If you are using your LDAP Directory as the Business Analytics User Repository, make sure that at least one user in your LDAP Directory has administrator privileges for Business Analytics before you move the Business Analytics Repository. See Grant User Access to
Business Analytics
with Built-in Groups for instructions. When the Business Analytics User Repository is your LDAP Directory, the default administrator account (Administrator user) is disabled.
2. If you are hosting the Business Analytics Repository or MashZone Repository in a new database, create the database following PostGreSQL documentation. Keep the following points in mind: 
If you want
Business Analytics 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
Business Analytics Repository.
When you initialize the PostGres database that will host the
Business Analytics 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 Business Analytics Repository, if it is not already up.
4. Using the SQL tool for the database that will be host, add Business Analytics 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 Business Analytics Repository tables in these folders, if needed.
5. Update snapshot scheduler configuration for the Business Analytics 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 Business Analytics Server.
b. Find the org.springframework.scheduling.quartz.SchedulerFactoryBean bean.
c. Update the org.quartz.jobStore.driverDelegateClass property to the org.quartz.impl.jdbcjobstore.PostgreSQLDelegate delegate.
The configuration would now look like:
d. Save this change.
e. If this is a clustered environment, copy the updated applicationContext-scheduler.xml configuration file to each Business Analytics Server in the cluster.
6. Copy the JAR file for the JDBC driver for your database to the following folder for each Business Analytics Server that uses this Business Analytics Repository: MashZoneNG-install/apache-tomee-jaxrs/lib.
7. Open rdsApplicationContext.xml under MashZoneNG-install/apache-tomee-jaxrs/classes and add the following keys to:
<property name="jdoProperties">
...
<map>
...
<entry key="javax.jdo.mapping.Schema" value="public"/>
<entry key="datanucleus.identifier.case" value="LowerCase"/>
...
</map>
</property>
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-tomee-jaxrs/conf/tomee.xml configuration file in the text editor of your choice.
10. For the Business Analytics Repository, edit the <Resource> element with an ID of MashzoneNextGenRepository and:
a. Update the JDBC driver, URL and credential properties:
<Resource id="MashzoneNextGenRepository" type="DataSource">
JdbcDriver org.Postgresql.Driver
JdbcUrl jdbc:postgresql://host-name:port/databasename
UserName username
Password password
JtaManaged = false
</Resource>
The JTA managed property must be false.
b. If needed, update optional properties. See TomEE 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 11. Save your changes to this file.
If the
Business Analytics Server does not start up successfully, see
Troubleshooting Connections to the
Business Analytics
Repository for suggestions.
12. Open the rdsJDBC.properties configuration file, from the web-apps-home/mashzone/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 PostGres and update these properties to match the JNDI configuration your previously updated for TomEE.
c. Save your changes to this file.
You must keep JDBC and JNDI configuration synchronized for the Business Analytics Repository. The application server is using JNDI to connect to the Business Analytics Repository, but some components still use JDBC information.
13. Restart the Business Analytics Server to apply these changes. This also restarts the MashZone Server.
If the
Business Analytics Server wedoes not start up successfully, see
Troubleshooting Connections to the
Business Analytics
Repository for suggestions.
14. Update connection information for the Snapshots Repository:
a. Open Business Analytics 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.
15. Restart the Business Analytics Server to apply these changes.
16. Load macros required for the Snapshot feature in Business Analytics:
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 |
