The Integration - PureEngage service needs to be configured, and then started. This service collects the required information from Genesys to support Scripting's side of the integration, including the campaign names and attached fields, and stores the information in the Scripting database.
As the collected information is stored in the Scripting database, after the service has run at least once then the integration will continue to function even if the service is disabled. However, if any changes are made to the campaign etc. in Genesys, then the changes won't be brought into Scripting until the service next runs. Similarly, any changes made to campaigns etc. within Genesys won't be reflected within Scripting until the service next runs. This is covered further in the Linking Campaigns article.
Note: if running a multi-webserver environment, the service only needs to be running on one of the instances of Scripting.
How To
1) Click on the menu button, select the Admin module, and then Services. Select the Integration - PureEngage item:
2) Click the Install button to install the service. Once the service has been installed, the following settings need to be configured (mandatory fields will be highlighted if incomplete). Once the configuration is complete, click Start and wait a few seconds to confirm that the service starts successfully.
Service Status Bar
When the Start button is clicked, the credentials will be checked and if the poll is successful the Scripting database will be updated. If this service fails, an error message will display, and further information will be recorded to the logs.
The name to be used for the service created by the Genesys application service. This name will appear in the logs if there are any service errors. There is no defined format for this field, it can be set to whatever name will be most useful when troubleshooting.
