Home

Welcome to the openy_daxko_gxp_syncer wiki!

Deployment tutorial

https://github.com/open-y-subprojects/openy_daxko_gxp_syncer/wiki/Deployment-and-Backup-plans

How to configure and run Syncer

https://github.com/open-y-subprojects/openy_daxko_gxp_syncer/wiki/Enable-Daxko-GXP-v1-API-Syncer-and-run-it

Server requirements

After switching from openy_pef_gxp_sync to openy_daxko_gxp_syncer there is an important architecture change happened. GroupEx PRO API ( so called embed API, or public API, or GXP API v1 ) is a calendar-type entity view. Daxko API v1 ( GXP API v2 ) - is not a calendar-style view, it exposes all entities as is without any periodicity information included.

This change led to a significant increase in the number of Session entities, created during the sync process. Once you migrated - keep an eye on the server's performance. If you faced with PHP memory limit issues - increase PHP memory limit. For the 30000 session nodes, PHP memory limit should be 758Mb or more.