...
- Copy jackrabbit-bundle-mysql-search.xml from the empty webapp overlay, rename it to jackrabbit-bundle-azure-search.xml and place it in WEB-INF/config/repo-conf/.
The configuration file for mysql can be easily adapted to work for Azure DB. - Use the PersistanceManager class for MSSQL: org.apache.jackrabbit.core.persistence.pool.MSSqlPersistenceManager.
Since Azure DB is based on Microsoft SQL Server the classes for MSSQL may be used. - Change the schema type from 'mssql' to 'azure'.
There is a special set of schema DDL files available for Azure DB. The main difference is that it creates clustered indexes, instead of non-clustered indexes. - Configure a JNDI datasource or specify your the driver class and connection parameters directly in the jackrabbit bundle configuration file.
| Info | ||
|---|---|---|
| ||
Using the schema type 'mssql' instead of 'azure' on Azure DB should be considered as a mis-configuration. It works but comes with a huge performance penalty, causing all sorts of buggy behavior in Magnolia CMS that can be traced back to timeouts on database queries. It is important for clustered indexes to be created, as these drastically improve the performance of the JackRabbit (2.3+) repositories that are stored in Azure DB. Use 'azure' as schema type! |
...