Installing iWD History Node

Prerequisites

• The environment meets the requirements that are described in Installation Prerequisites
• The computer on which the iWD History Node is going to be installed has network access to the computer that is hosting Genesys Configuration Server.
• You have access rights to execute install.sh or setup.exe, depending on the operating system.

Creating the Database Schema

To create the History Node database schema, perform the migration steps described in iWD History Node Migration. This ensures that the database schema is created automatically when History Node starts up.

On Windows

Prerequisites

• Installation Packages have been installed.

Purpose

To install the iWD History Node application on the Windows platform. The current procedure assumes that the application already exists in Configuration Server—the required steps are described in iWD History Node Application Definition.

Procedure

1. Locate and double-click setup.exe in the iWD History Node directory of the iWD DVD.
2. The iWD History Node Installation Wizard opens. Click Next in the Welcome screen.
3. In the Connection Parameters to the Configuration Server screen, enter the login details to connect to Genesys Configuration Server and then click Next:

• Host name—The host of Genesys Configuration Server.
• Port—The port that is used by Genesys Configuration Server.
• User name—The user name of the Person (or User) as defined in Genesys Configuration Manager or Genesys Administrator.
• Password—The password that is associated with the Person (or User).

4. From the list of available choices, choose the iWD History Node application that you want to install and click Next.
5. Choose the destination location for iWD History Node.
6. Click Next.
7. In the Ready to Install screen, click Install to begin the installation of iWD History Node.
8. When installation has been completed, click Finish.

End of procedure

Using GAX

Purpose

To install the iWD History Node application on either Windows or Linux platform by using the simplified GAX method. Genesys strongly recommends that you install using the GAX/GAX Plug-in process.

Summary

GAX allows you to upload Installation Packages (IPs) and then use them to initiate the installation process. The procedure supports both a fresh install or an upgrade. The upgrade option is only available when you have installed the previous version of the application by using GAX. The upgrade procedure is basically the same as installation except that you are not forced to create a new application but are given the option either to use the old one or to merge them. So the upgrade does not remove the previous version of the application before the new installation.

IP Upload Procedure

Click here (new document) for the GAX IP Upload Procedure.

Installation Procedure

1. Navigate to GAX > Administration > Installation Packages
2. Chose the appropriate IP from the list. To install it, click it. Its details appear in a new panel.
3. Verify the details of the IP, then click the menu button and select Install. The installation wizard then takes you through the following steps.
4. On the Welcome page, click Next.
5. On the Host selection page, select the host to deploy to and click Next.
6. Complete the application parameters:

• Application Name— If you provide the existing application here, it won't be updated in any way.
• Tenant—Not applicable for iWD History Node.
• Application Port
• Primary Configuration Server
• Backup Configuration Server

7. Click Next.
8. Complete the Installation Parameters. Tooltips will provide some on-screen assistance.

• IPCommon: InstallPath—The path where iWD History Node will be installed.

9. Click Next.
10. On the Deployment tab, check all the parameters you have provided. Click Finish.
11. The procedure then executes automatically, showing the progress bar. Its status (and other details) you can find on the GAX > Administration > Deployed IPs page. If the installation fails, re-initiate the process using the parameters that you already provided and/or make any necessary changes.

On UNIX

Prerequisites

• Installation Packages have been installed.

Purpose

To install the iWD History Node application on the UNIX platform.

Procedure

1. Locate the install directory and enter ./install.sh.
2. When the following output is displayed, enter the required information, as indicated at each prompt.




**************************************************
* Welcome to the Genesys 9.0 Installation Script *
**************************************************

Installing iWD History Node, version 9.0.000.xx

Please enter the hostname or press enter for "xx-yy-zzzzzz" =>

Please enter the following information about your Configuration Server:

Configuration Server Hostname =>xx-yy-zzzzzz
Network port =>8888
User name =>default
Password =>

Please choose which application to install:
1 : iwd_history_1
2 : iwd_mgr_1_server
=>1

Press ENTER to confirm /genesys/iwd_history_1 as
the destination directory or enter a new one =>

Extracting tarfile: data.tar.gz to directory: /genesys/iwd_history_1
config/
config/iwd_history.yaml
iwd_history.jar
iwd_history.sh
iwd_history_service.sh
lib/

Installation of iWD History Node, version 9.0.000.xx has completed successfully.

iWD History Node Application Definition

1. Log into Genesys Administrator or GAX and import the iWD History Node Application template from the iWD DVD. Double-check to see whether metadata were correctly imported. This is important for definition of roles in Genesys Administrator. For GAX, importing the IP automatically also imports privileges. In that case, metadata are options since you would manage roles using GAX in those circumstances.
2. Create a new Application object based on the iWD History Node Application template.
1. To begin the create procedure, navigate to Configuration > Environment > Applications and click New.
2. On the General tab:
1. Enter a name for the iWD History Node.
2. Select the application Template—This must of type Third Party Server.
3. Version and Is Application Server boxes are pre-selected according to the template type.
4. Enter the name of the Tenant for which History Node will be working.
5. State Enabled—If selected, indicates that the object is in regular operating condition and can be used without any restrictions.
3. On the Connections tab, add connections to:

• The History Node database's Database Access Point (DAP). This DAP must have a jdbc section in the configuration application options, with the following parameters:
  • driver-class = "com.microsoft.sqlserver.jdbc.SQLServerDriver"
  • url = "jdbc:sqlserver://<hostname>:<port>;databaseName=<history_node_DB>;"
  • validation-query = "select 1"
    

This example contains Microsoft SQL Server connection strings. Adjust them appropriately for the database you are using.

• The Event Logger JMS DAP. This must be the same DAP as is configured for Interaction Server. Refer to the Using a Message Queue with Event Logger topic in the eServices Administration Guide for more information. The following parameters (with sample values) from the [logger-settings] section in the Options tab are read in:
  • jms-initial-context-factory = org.apache.activemq.jndi.ActiveMQInitialContextFactory
  • jms-connection-factory-lookup-name = ConnectionFactory
  • reconnect-timeout = 10
  • jms-provider-url = tcp://localhost:61616
  • delivery-protocol = jms
  • delivery-queue-name = InxEventLogQueue
  • username
  • password

Important

JDBC and JMS drivers do not require any configuration, but they are not delivered in the IWD software distribution artifacts. However their .jar files must be put into the {HISTORY NODE INSTALLATION DIR}/lib directory.

3. In the Port ID field, add the port ID and its number.
4. Connection Protocol—Leave empty. This parameter is ignored.
5. Local Timeout and the Remote Timeout—Leave empty. This parameter is ignored.
6. Specify a Trace Mode—The connection trace mode used between a server and its client. This parameter is ignored.

• Trace Is Turned Off—This parameter is ignored.
• Trace On Client Side—This parameter is ignored.
• Trace On Server Side—This parameter is ignored.
• Trace On Both Sides—This parameter is ignored.

7. Specify Transport Protocol Parameters—Any text, usually key/value pairs, separated by a semicolon (;). This property is application-specific.
8. Specify Application Parameters—Any text, usually key/value pairs, separated by a semicolon (;). This property is application-specific.
9. The Ports tab lists communication ports used by the clients of an application to connect to a server. To support specific high-availability configurations, more than one server can be registered on the same port within the same host. Otherwise, do not assign the port number to any other server on the same host. Click Add to add a connection. You need to add two ports:

• default—Provides History Node's main functionality.
• admin—Provides administrative tasks.

10. In the Options tab in the [IWD] section, set the value of these two options:

• process-dm—true
• process-gtl—true

Important
See also the 'Configuring History Node to Process Single Event Type' section of the iWD History Node Configuration topic.
11. Ignore the Application Options tab.
12. Click Save to save the Application object.

Installing an iWD History Node Cluster

1. Create an application for every History Node application in the cluster as described in iWD History Node Application Definition.
2. Create a new Application object based on the Application Cluster template.
1. To begin the create procedure, navigate to Configuration > Environment > Applications and click New.
2. On the General tab:
1. Enter a name for the iWD History Node Cluster.
2. Select the application Template—This must of type Application Cluster.
3. On the Connections tab, add connections to all History Node applications working in this cluster.