The Business Edition Premise eServices application allows you to install and configure the optional Email and Chat routing solutions. If you are not installing Email or Chat, you can ignore these steps.
For more information about eServices, see the eServices documentation page.
Before you start
The Genesys Deployment Agent (GDA) service must be manually enabled on the core and db VMs before you deploy the eServices application.
To do this:
- Find the GDA service in your list of Windows services. (It should be in a not started/disabled state.)
- In the Properties, change the startup type to Manual.
- Start the GDA service.
Do this for both the core and db VMs. The eServices deployment process will stop and disable the GDA service on both VMs after it is successfully deployed.
The following steps describe how to deploy the eServices application. Note that the deployment process can take up to ten minutes to complete.
WATCH: This video shows the eServices application deployment for BEP 8.5.000:
- In GAX, go to Administration > Solution Definitions and select Genesys eServices Single Host Deployment.
- Click Related (it's the gear icon) and select Install.
- Use the default values, except for the following:
- Check or uncheck Activate chat-media support, depending on whether or not you want to activate chat.
- Database Administrator Name: sa
- Database Administrator Password: G3n35y5!
For BEP 8.5.000: You also need to enter the following (otherwise, skip to the next step):
- Interaction Server Database User Name: genesys_ixn
- Interaction Server Database Password: Genesy$_0_ixn
- ICON Database User Name: genesys_icon_mm
- ICON Database User Password: Genesy$_0_icon_mm
- You will also need to set the POP Account Parameters. (You can add up to 20 POP accounts.)
ImportantFor BEP 8.5.000: The eServices application deployment requires separate user names and passwords for the Interaction Server and ICON databases. While you can choose to use any existing user names, the passwords for those accounts will be overwritten by the ones entered during deployment. Keep this in mind, as any differences in the passwords could impact an existing configuration.