Performance improvement through parallelizing

It may be that the groupware jobs mentioned here are not listed in the job administration of the application server. To ensure good performance of the Groupware Connector, it is helpful to "outsource" the group­ware jobs to parallel servers in cluster mode.

Due to the exclusively sequential synchronization of the activities of internal employees, the response times of the groupware server are relatively high. The parallelization of synchronization tasks improves performance.

To this end, all Groupware configurations have an ID that is assigned to them automatically when they are upgraded. All Group­ware services (whose method is provided by the GwcSynJob class) now expect as method parameter the ID of the Groupware configuration to be used for a job run (Example: IDN:=GWC01). If you want to synchronize several Groupware servers in parallel, set up one job (record) per Groupware configuration, and set the ID parameter accordingly. The jobs can run in different intervals as needed, and if it makes sense (e.g., with a remote Groupware server with high latency or low bandwidth).

Move the groupware coupling (and possibly other groupware-relevant jobs as well as “silent” jobs such as index updating of the full-text search) to a parallel server process. This means setting up a second JustRelate CRM service that is connected to the same database as the “normal” server. Only the aforementioned jobs then run on this second process, while the users log in to the previous system as usual.

Vorteil: Die Last (Speicher, I/O), die der Groupware-Job produziert, beeinträchtigt die interaktive Arbeit spürbar weniger.
Nachteil: Ein zweiter Prozess benötigt ebenso Ressourcen (RAM) und darf bei Softwareaktualisierun­gen nicht vergessen werden, wobei sich hier noch ein Vorteil ergibt: Korrekturen, die ausschließlich die Synchronisation betreffen, können direkt eingespielt werden, ohne den laufenden Betrieb unter­brechen zu müssen.

Advantage: The load (memory, I/O) produced by the groupware job affects the interactive work noticeably less.

Disadvantage: A second process also requires resources (RAM) and must not be forgotten when updating software, although there is another advantage here: Corrections that only affect synchronization can be applied directly without having to interrupt ongoing operations.