IMPORTANT NOTICE: Sugar 6.3.2+ and 6.4.0 / 6.4.1 (all editions) are supported by Riva Cloud but require adjustments be made to the Sugar servers. For additional instructions, see Sugar 6.3.2+: Resolve "Access Denied" errors.
Riva On-Premise supports data integration with Sugar 4.5 and higher versions (Community Edition, Professional, and Enterprise) and Sugar On-Demand. This article describes how to prepare a Sugar server and the Riva server, to support a Riva impersonation CRM connection to Sugar.
To prepare Sugar for Riva:
Riva server can be installed on any Windows system that meets the system requirements.
IMPORTANT NOTE: Installing Riva on the Windows server that hosts the Sugar server is not recommended.
Confirm that you can log in to the Sugar application through a web browser by using an administrator-level account.
The following Sugar server versions have been tested for Riva On-Premise:
Up to six preparations and performance tuning improvements may be required for on-premises and independent Sugar service providers:
Riva requires "Use Impersonation" access through an administrator level-account to access the target user CRM accounts. All versions of Sugar Professional and Enterprise versions natively support “Use Impersonation”. Sugar Community Edition does not install this support by default; see How to configure "Use Impersonation" support for Sugar Community Edition.
When the Riva server attempts to sync multiple target users concurrently, it can create many Apache instances on the Sugar host server that use most of the available memory. For six tips that can greatly reduce the impact of memory usage, see Sugar performance tuning.
Another best practice on host Apache servers is to adjust the maximum number of worker processes to match the amount of memory available on the server. For more information, see Recommendations for performance tuning and resource planning for CRM hosted on LAMP/WAMP.
Sugar Development added a fix to the web services for Sugar 6.3.2 (and higher) and 6.4.0 (and higher) servers to protect against SQL injection attacks. That Sugar fix prevented the Riva CRM connection from permitting data sync. Sugar Development included a fix in the 6.4.2 release that works with Riva. To apply a patch to enable 6.3.2+, 6.4.0, and 6.4.1 Sugar servers to work with Riva, see Sugar 6.3.2+: Resolve "Access Denied" errors.
Not all versions of Sugar Web Services APIs support PHP 5.3. For versions of Sugar prior to 6.0.1, the options are to apply a bug fix or to downgrade PHP to 5.2.x on the Sugar server. For more information, see Sugar: PHP compatibility issue with PHP 5.3.
Sugar version 6.1 introduced a change to the logic for handling appointments:
The Riva connection to the target CRM must be configured to use the credentials of an administrator-level account. For Sugar, choose one of the following options:
The administrator account provides the privileges required to impersonate each target user and make the necessary changes to records in the CRM for each target user.
Two configurations must be confirmed to enable the target users:
4.1: Configure the correct primary email address value
The Riva server attempts to match the primary SMTP email address of the target users in their email account to the primary email address value of the corresponding target user in Sugar. Ensure that for each user, the email address values in the email system and Sugar are identical.
4.2: Enable sufficient access permissions
The Riva connection to Sugar uses the Enterprise Impersonation Model: When Riva creates new items in the CRM, it assigns ownership to the "target user". Since Riva is now acting on behalf of the target user, all audit fields in the CRM record the target user as the user that created and modified the item. Riva uses the permissions of the CRM target user to create and modify items and data in the CRM.
If the access permissions defined for the target user are not sufficient, the Riva server displays Access denied errors for each data change it tries to synchronize. Ensure that for each target user, permissions are assigned to create, modify, delete, import, and export datatypes that Riva will attempt to sync for that user. For more information, see Sugar Access Denied errors explained.
Gather the following information:
That information will be required when you create the Riva connection to the Sugar system: