Chapter 3: Installation Interaction Server Databases log4j.appender.runtime.layout.ConversionPattern=%d{yyyy-MM-dd
HH:mm:ss}|%t|%p|%c|%m%n log4j.appender.runtime.MaxBackupIndex=7 log4j.appender.runtime.MaxFileSize=256MB
# if you enable centralized_node appender then make sure you change rootLogger to:
# log4j.rootLogger=INFO, runtime, centralized_node log4j.appender.centralized_node=com.genesyslab.iwd.log.Centraliz
edAppender log4j.appender.centralized_node.Threshold=INFO log4j.appender.centralized_node.layout=org.apache.log4j.PatternL
ayout log4j.appender.centralized_node.layout.ConversionPattern=%m log4j.appender.centralized_manager.MessageServerHost=MsgSrvrHost log4j.appender.centralized_manager.MessageServerPort=4050 log4j.appender.centralized_node.MessageServerClientName=iWD
Runtime Node
End of procedure
Interaction Server Databases
Once all iWD components have been installed, database update scripts have to be run on the Interaction Server databases and options need to be imported into your Event Log DAP.
Procedure:
Updating the Interaction Server databases
Purpose: To run the update scripts on the Interaction Server databases for compatibility with iWD 8.0, import configuration options for the Event Log
DAP, and configure the completed-queues
option for Interaction Server.
Prerequisites
•
Interaction Server is installed as described in Procedure: Installing
Interaction Server and its databases, on page 43
(also refer to the eServices
(Multimedia) 8.0 Deployment Guide).
Deployment Guide 85
Chapter 3: Installation Interaction Server Databases
•
The installation of iWD components as outlined in this chapter is completed up to this point. In particular, iWD Manager must be installed.
During iWD Manager installation, the database scripts that are required to update the Interaction Server databases are saved to the iWD Manager installation directory.
Note:
The procedure below is a general procedure. Please work with your enterprise’s database administrator to follow the specific procedure required by your database management system and your enterprise policies.
Start of procedure
1. Locate the eventlog_update.sql
script in the
<iWD Manager directory>/sql_scripts/<Database Type> directory and run it on the
Interaction Server Event Log database.
2. Locate the iwd_custom_fields.sql
script in the <iWD Manager directory>/sql_scripts/<Database Type> directory and run it on the
Interaction Server database.
3. In Configuration Manager or Genesys Administrator, open the properties for your Interaction Server
Application
. In the settings
section, locate the completed-queues
option. This option specifies a list of queues for completed interactions. The completed_at
timestamp in the Interaction
Server database is set for an interaction when it is placed in one of these queues. Add iWD_Completed
as a value. This is the name of the queue used for completed iWD interactions (the name of this queue is not configurable.
iWD_Completed
must be used). Save the changes.
4. In Configuration Manager or Genesys Administrator, open the properties for your Event Logger DAP Application . On the Properties tab, import evenlog_options.cfg
to update the DAP’s properties. The evenlog_options.cfg
file can be found in the config
directory after iWD
Manager is installed.
End of procedure
Next Steps
Now you should start configuring the mandatory and optional services for your
Solution. Jump ahead to “iWD Services” on page 146 for information about
the available services, their recommended order of configuration, and the properties that can be configured for each service. If you would like to review how to work with iWD Manager first, start at the beginning of
Chapter 4
.
86 intelligent Workload Distribution 8.0
