The Riva On-Premise server supports data integration to 1CRM, info@hand On-Premise, and info@hand Online. This article describes how to prepare a 1CRM or info@hand server and the Riva server, to support a Riva impersonation CRM connection.
To prepare 1CRM (info@hand) for Riva
From the Windows system that will host the Riva server, confirm that you can log in to the 1CRM or info@hand application through a web browser with an administrator level account.
The following CRM server versions have been tested for Riva On-Premise:
Two performance tuning improvements may be required for on-premise 1CRM or info@hand servers:
When Riva server attempts to sync multiple target users concurrently, it can create many Apache instances on the 1CRM or info@hand server that use most of the available memory. For six tips that can greatly reduce the impact of memory usage, see CRM performance tuning.
Another best practise 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.
The Riva connection to the target CRM must be configured to use the credentials of an administrator-level CRM user account. For 1CRM or info@hand, choose one of the following options:
The administrator account provides the privileges necessary 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:
The Riva server attempts to match the primary SMTP reply-to email address of the user's email account to the primary email address value of the corresponding target user in 1CRM or info@hand. Ensure that for each user, the email address values in the email system and the CRM are identical.
The Riva connection to 1CRM 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 in the target user's assigned role are not sufficient, Riva server displays "Access denied" errors for each data change it tries to synchronize. For more information, see SugarCRM access denied errors explained.
Ensure that for each target user, the assigned 1CRM or info@hand role provides sufficient permissions to create, modify, delete, import, and export datatypes that Riva will attempt to sync for that user.
Gather the following information, which will be required when you create the Riva connection to the 1CRM or info@hand system: