Procedure
When the MashZone NextGen User Repository is your LDAP Directory, the default administrator account (Administrator user) is disabled.
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 and collation to UTF-8 when you create the database. See documentation for your database for specific instructions.
For medium or larger MySQL databases that will host the MashZone NextGen Repository, you should increase the maximum allowed packet size, which defaults to 1MB, for the database.
MashZoneNG-install/prestorepository/jackbe-presto-rds-oracle-mysql-mssql.jar
To the web-apps-home/mashzone/WEB-INF/lib folder.
name="MashzoneNextGenRepository" auth="Container" type="javax.sql.DataSource" maxTotal="200" maxIdle="30" maxWaitMillis="10000" username="app" password="app" driverClassName="com.mysql.jdbc.Driver" url="jdbc:mysql://host-name/databasename" />
For MySQL databases, it is recommended including the database name in data source URLs. If this information is omitted, testing the data source fails and may also cause errors with access to stored procedures.
The JTA managed property must be false.
Some common properties you may need to set include:
validationQuery = select 1 from dual
Common tuning properties for connections pools. See Tuning the MashZone NextGen Repository Connection Pool.
If the MashZone NextGen Server does not start up successfully, see Troubleshooting Connections to the MashZone NextGen Repository for suggestions.
Note
Depending on your local MySQL settings, MashZone NextGen may display an error message, such as "Error: Packet for query is too large (xxx > yyy)". In this case, a file (for example, the JDBC driver library) was uploaded to MashZone NextGen that exceeds the size of the max_allowd_packet parameter in the MySQL configuration. After setting an appropriate value in the mysql.cnf file, this error should no longer occur. For details, please refer the corresponding MySQL documentation.