Deploying Interaction Server

This section describes how to install Interaction Server.

Create Host

If you plan on installing eServices on the same computer as Genesys Framework, you should already have a Host object created and available for your eServices deployment. However, if you have not already done so, or if you want to install eServices on a different computer than Framework, create the Host object in the Configuration Layer for the machine that will host your model environment.

Create the Databases

Create a database in your SQL Server RDBMS. This database will handle Interaction Server's one table for tracking transient data. You will use the name of this database during your creation of Interaction Server Database Access Point (DAP). After configuration and installation, you will run scripts against this database to make it available to Genesys servers.

Install and Start Interaction Workflow Samples

Install and run this component first to create various configuration objects that you will need when installing the rest of eServices.

Post Deployment Steps

Finishing the Interaction Server Deployment

Creating Database and Running Script

If you have not already done so, create the database for Interaction Server.

Running the Database Scripts

1. At the starting directory for Interaction Server, locate the SQL script folder:
   • Interaction Server—Script
2. Run the database script for Interaction Server.

Verifying Connections

At this point in the eServices installation process, you must update the configuration settings for some components before continuing. See the Connections Table for a list of connections that must be set in the Configuration Layer. Refer to the eServices Options Reference for information on option settings.

1. In Configuration Manager or Genesys Administrator, verify that the required connections have been made in the eServices Application objects.
2. Add a connection from Stat Server to Interaction Server, or to Interaction Server Proxy (see the next section "Interaction Server Proxy as Reporting Bus").
3. Add a connection from Universal Routing Server to Interaction Server.

Interaction Server Proxy as Reporting Bus

You can connect Stat Server to Interaction Server Proxy rather than directly to Interaction Server. This can be advantageous if you are running multiple Stat Servers. To do this:

• Deploy Interaction Server Proxy.
• Wherever this Guide speaks of connecting Stat Server to Interaction Server, instead make the connection to Interaction Server Proxy.