Revision as of 10:37, May 18, 2017 by Peter Chaplin (talk | contribs)
Jump to: navigation, search

Installing iWD History Node

Prerequisites

    • The environment meets the requirements that are described in Installation Prerequisites
    • The computer on which the iWD Manager is going to be installed has network access to the computer that is hosting Genesys Configuration Server. Users of iWD Manager will be authenticated through Genesys Configuration Server.
    • You have access rights to execute install.sh or setup.exe, depending on the operating system.
    • For upgrades from 8.5.1 to 9.0.0:
      • The servlet container (for example, Tomcat) is stopped.
      • The previous version of iWD Manager is uninstalled—the iwd_manager directory from the web server is removed.


On Windows

Prerequisites

  • Installation Packages have been installed.

Purpose

To install the iWD Manager application on the Windows platform.

Summary

Installation of iWD Manager saves the required database scripts in the working directory. These scripts must be run against the iWD Configuration database and the Interaction Server database. iWD Manager does this automatically after a user's successful login and authentication, when it detects a different database schema than expected. For Iteration Server synchronization, there is a dedicated option Configure Ixn Custom Properties in iWD Manager. The current procedure assumes that the application already exists in Configuration Server—the required steps are described in iWD Manager Application Definition.

Important
If you are upgrading, ensure that you have uninstalled the previous version and proceed with the current installation procedure. Also make sure not to skip the Application Definition step, because new versions might deliver new options.

Procedure

  1. Locate and double-click setup.exe in the iWD Manager directory eg. of the iWD DVD.
  2. The iWD Manager Installation Wizard opens. Click Next in the Welcome screen.
  3. Select the web container (for example, Tomcat or WebSphere) and click Next.
  4. If you selected WebSphere in Step 7, select the appropriate JDK from the list.
    Important
    This is not the JDK which will be used by WebSphere. This is necessary to properly configure the scripts which will be used to build the WAR archive.
  5. If you selected Apache Tomcat in Step 7, browse to the Home directory for your Apache Tomcat installation (for example, C:\ProgramFiles\Apache\Tomcat7\). The iWD Manager components will be installed in the selected directory, under the webapps/ subdirectory.
  6. Click Next.
  7. 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).
  8. From the list of available choices, choose the iWD Manager application that you want to install and click Next.
  9. Choose the destination location for iWD Manager. If you selected Websphere in Step 7, both supporting files and iWD Manager Java application part will be installed in that location. If you selected Tomcat in Step 7, only supporting files for iWD Manager will be installation in that location. The iWD Manager web application will be installed directly into the webapps folder under your Tomcat home directory.
  10. Click Next.
  11. Select the database type that will be used by the iWD Configuration database.
  12. Enter the parameters that are used to connect to the iWD Configuration database in the next screen. Enter the following information:
    • DB Server Host—The name of the computer on which the database is located.
    • Database Name—The name of the iWD Configuration database.
    • User Name—The name of the user that is used to connect to the database.
    • Password—The password that is used to connect to the database.
  13. Click Next.
  14. Enter the host name and port of the computer on which the backup Genesys Configuration Server is running. If there is no backup Configuration Server in your environment, specify the primary Configuration Server host and port. Click Next.
  15. In the Ready to Install screen, click Install to begin the installation of iWD Manager.
  16. When installation has been completed, click Finish.
  17. Perform any optional steps or install localization if needed.

For WebSphere configuration after installation of iWD Manager, build the WAR archive as described in Post-Installation Steps For WebSphere and install the generated WAR file by using the WebSphere Integrated Solutions Console.


End of procedure

Using GAX

Purpose

To install the iWD Manager 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 on it. Its details appear in a new panel.
  3. Verify the details of the IP, then click the Iwd install1.png 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 Manager
  • Application Port— Not applicable for iWD Manager
  • Primary Configuration Server
  • Backup Configuration Server
  • Click Next.
  • Complete the Installation Parameters. For assistance look at the tooltips near by field or see below:
    • IPCommon: InstallPath—The path where iWD Manager will be installed.
    • Database: Engine — Choose one of the supported Oracle or MSSQL databases.
    • Database: Host
    • Database: DataBaseName
    • Database: User
    • Database: Password
    • ConfigServer: Host
    • ConfigServer: Port
    • ConfigServer: BackUpHost
    • ConfigServer: BackUpPort
    • ConfigServer: ApplicationName
    • IPCommon: Container — Choose one of Apache Tomcat or IBM WebSphere Server.
    • IPCommon: TomcatPath— Applicable only for the Tomcat option. Provide the path to your Tomcat here.
    • IPCommon: JavaPath— Applicable only for WebSphere. Provide the path to your JDK; this Java will be used to build the .war package.
    • IPCommon: JavaVersion— Applicable only for WebSphere. Provide the WebSphere JRE version, making sure it is the minimum version required.
    • IPCommon: JavaPatchNumber— Applicable only for Websphere. Provide the WebSphere JRE patch version, making sure it is the minimum version required
  • Click Next.
    • Important
    For Tomcat, before you click Finish, confirm that the server is not running
  • On the Deployment tab, check all the parameters you have provided. Click Finish.
  • 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 Manager application on the UNIX platform.

    Summary

    Installation of iWD Manager saves the required database scripts in the working directory. These scripts must be run against the iWD Configuration database and the Interaction Server database. iWD Manager does this automatically after a user's successful authentication in the login every time that it detects a different database schema than expected. For Interation Server synchronization there is a dedicated option Configure Ixn Custom Properties. The current procedure assumes that the application already exists in Configuration Server—the required steps are described in iWD Manager Application Definition.


    Important
    If you are upgrading, ensure that you have uninstalled the previous version and proceed with the current installation procedure. Also make sure not to skip the Application Definition step, because new versions might deliver new options.

    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.
      Important
      In this procedure Websphere is selected for the servlet container. When asked to provide the destination directory, enter an arbitrary location. iWD Manager Java application and supporting files will be installed in this directory.

      Othercase you can select Tomcat option. Then you will be asked additionally for you tomcat installation path: Please enter the full path to your Tomcat installation

      And java application will be installed directly into Tomcat as iwd_manager and rest of supporting files in location that you provided.
      **************************************************
* Welcome to the Genesys 9.0 Installation Script *
**************************************************

Installing iWD Manager, version 9.X.XXX.XX

Please select your servlet container type by number:
1. Tomcat
2. WebSphere
=>1

Please specify the type of used Database Server:
1) MS SQL Server
2) Oracle Server
=>2

Please enter the Database Server hostname or IP address =>X.X.X.X

Please enter the Database name =>XE

Please enter the Database Server user name =>iWD

Please specify the Database Server user password =>

Please enter the Configuration Server Host Name =>X.X.X.X

Please enter the Configuration Server Port =>2020

Please enter the Configuration Server Backup Host Name =>X.X.X.X

Please enter the Configuration Server Backup Port =>2020

Please enter the Configuration Server Application Name =>iWD Manager

Please enter full path of the destination directory for installation =>/var/iwd90/manager

Extracting tarfile: data.tar.gz to directory: /var/iwd90/manager
...
webapp/
...
webapp/WEB-INF/
webapp/WEB-INF/application.properties
webapp/WEB-INF/web.xml
webapp/WEB-INF/faces-config.xml
webapp/WEB-INF/lib/
webapp/WEB-INF/lib/hibernate.jar
webapp/WEB-INF/lib/packagedstatisticsdeprecated.jar
webapp/WEB-INF/lib/commons-lang.jar
webapp/WEB-INF/lib/commons-logging.jar
...
webapp/META-INF/MANIFEST.MF

Installation of iWD Manager, version 9.X.XXX.XX has completed successfully.
    3. Perform any optional steps or install localization if needed.

    For WebSphere configuration after installation of iWD Manager, build the WAR archive as described in Post-Installation Steps For WebSphere and install the generated WAR file by using the WebSphere Integrated Solutions Console.

    Procedure

    1. Log into Genesys Administrator or GAX and import the iWD Manager Server and iWD Manager Application templates 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 Manager Server template.
      1. To begin create procedure navigate to Configuration > Environment > Applications and click New.
      2. On the General tab:
        1. Enter a name for the iWD Manager Server
        2. Select the application Template—This must be of type Third Party Server
        3. Version, Tenant and Is Application Server boxes are pre-selected according to the template type.
        4. State Enabled—If selected, indicates that the object is in regular operating condition and can be used without any restrictions.
      3. Click Save to save the Application object.
    3. Create a new Application object based on the iWD Manager Application template. For upgrades from 8.5.1 to 9.0.0 you can either create a new application in place of the previous one or simply update the application by using the new template. As for second option be careful with privileges part.
      Important
      The must be only one iWD Manager application on the Configuration Server. Additional ones will be ignored.
      1. To begin create procedure navigate to Configuration > Environment > Applications and click New.
      2. On the General tab:
        1. Enter a name for the iWD Manager.
        2. Select the application Template—This must of type iWD Manager.
        3. Version, Tenant and Is Application Server boxes are pre-selected according to the template type.
        4. 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 the connections to the Interaction Server and to Universal Contact Server (UCS) that your iWD Solution will use. If you need to:
        1. Add the Port ID on the Interaction Server that iWD Manager will connect to.
        2. Specify the Connection Protocol: simple or addp.
        3. Specify the Local Timeout and the Remote Timeout—These values are required only if you specified addp in Connection Protocol. This value specifies the heartbeat polling interval, measured in seconds, on a client side. This indicates how often the client application sends polling signals to the server application. To enable this functionality, specify any integer as the value.
        4. Specify a Trace Mode—The connection trace mode used between a server and its client.
          • Trace Is Turned Off—Select if you do not want either the client or the server application to print ADDP-related messages in its log.
          • Trace On Client Side—Select if you want the client application to print ADDP-related messages in its log.
          • Trace On Server Side—Select if you want the server application to print ADDP-related messages in its log.
          • Trace On Both Sides—Select if you want both the client and server applications to print ADDP-related messages in their log.
        5. Specify Transport Protocol Parameters—Any text, usually key=value pairs, separated by a semicolon (;). This property is application-specific.
        6. Specify Application Parameters—Any text, usually key=value pairs, separated by a semicolon (;). This property is application-specific.
      4. 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.
      5. Ignore the Options tab.
      6. Ignore the Application Options tab.
      7. Click Save to save the Application object.

    Additional Configuration for Oracle RAC and MS SQL

    After a standard installation of iWD Manager, you must do one of the following to correctly configure iWD Manager for either Oracle RAC or MS SQL clusters:

    • Edit the iwd.properties file
    1. Edit the iWD Manager configuration file (iwd.properties) and replace the iwd.configDatabase.url property value with a valid JDBC URL for either Oracle RAC or MS SQL.
    2. Start iWD Manager.

    See also here for differences between the Oracle RAC SCAN-on and SCAN-off URLs.

    Comments or questions about this documentation? Contact us for support!