Jump to: navigation, search

x-jsms-config-file

Section: channel-any_name_for_mms_mm7
Default Value: jsms-mm7.conf
Valid Values: The full name of the jSMS configuration file
Changes Take Effect: After restart


Specifies the name and location of the configuration file for the jSMS implementation. If a full path is not specified, SMS Server searches its current (working) folder for the file. This option applies to jSMS drivers. The parameters of the jSMS configuration file are described in the file located at SMSServerInstallationFolder\media-channel-drivers\channel-sms-mms\jsms\bin\jsms.conf and in the jSMS User's Guide located at SMSServerInstallationFolder\media-channel-drivers\channel-sms-mms\jsms\docs\users_guide.pdf (SMSServerInstallationFolder is a sample name).

more...

x-jsms-config-file

Section: channel-any_name_for_mms_mm7
Default Value: jsms-mm7.conf
Valid Values: The full name of the jSMS configuration file
Changes Take Effect: After restart


Specifies the name and location of the configuration file for the jSMS implementation. If a full path is not specified, SMS Server searches its current (working) folder for the file. This option applies to jSMS drivers. The parameters of the jSMS configuration file are described in the file located at SMSServerInstallationFolder\media-channel-drivers\channel-sms-mms\jsms\bin\jsms.conf and in the jSMS User's Guide located at SMSServerInstallationFolder\media-channel-drivers\channel-sms-mms\jsms\docs\users_guide.pdf (SMSServerInstallationFolder is a sample name).

more...

Manual Deployment for UCS Proxy, Interaction Server Proxy, and SMS Server

This section describes the manual deployment of UCS Proxy, Interaction Server Proxy, and SMS Server.

Introduction

Large numbers of custom desktop (ESP client) connections to Interaction Server and UCS may give rise to performance issues.

Important
  • UCS Proxy and Interaction Server Proxy support High Availability in Warm Standby mode.
  • UCS Proxy and Interaction Server Proxy are not supported with Genesys Agent Desktop and desktops that connect using Interaction SDK. A custom desktop that connects using Platform SDK Contact can use UCS Proxy and Interaction Server Proxy.

To mitigate the issues caused by a high load on the server, Genesys introduced Interaction Server Proxy and UCS Proxy in release 7.6.1. Desktop applications can be configured to connect to these Proxy servers instead of the main server, significantly reducing the load on the server. For example, it is easier for the server to handle 20,000 clients that operate through ten proxies (only ten connections) than to handle the same 20,000 clients that each connect separately.

Important
  • These Proxy components are not part of the eServices Configuration Wizards and must be installed manually.
  • UCS Proxy only supports connections from desktop applications; Interaction Server Proxy supports connections from desktop applications and from Stat Server.

Because of the many variables in deployment (choice of operating system, number of clients, details of architecture) is so broad, it is not possible to provide exact guidelines as to when deploying Proxy servers would be advantageous. However it may be stated that you can anticipate performance issues when the number of clients exceeds 10,000.

Requirements

These components work with Universal Contact Server and Interaction Server. In order for the respective Proxy servers to work properly, all components that are needed by Universal Contact Server and Interaction Server must be installed. This will depend on your environment and how you are using Universal Contact Server and Interaction Server. For more details, refer to the chapter that is applicable to you:

Deploying UCS Proxy, Interaction Server Proxy and SMS Server

This section describes how to manually install UCS Proxy, Interaction Server Proxy and SMS Server.


UCS Proxy Deployment

Prerequisites

  • The Interaction Management CD.
  1. Create an Application object for the Proxy if it does not already exist.
    1. Import the correct application template from the Interaction Management CD for the UCS Proxy.
    2. Create a new Application object based on the template.
  2. Open the Properties dialog box of the Application object.
  3. On the Server Info tab:
    • In the Host text box, enter the name of the desired host.
    • In the Communication Port text box, enter the port the UCS Proxy will use for listening.
  4. On the Start Info tab enter some characters in the Working Directory, Command Line, and Command Line Arguments fields. These characters will be over-written with the correct values during the installation, but they cannot be left blank at this point.
  5. On the Connections tab, add connections to:
    • The primary Universal Contact Server (for UCS Proxy). This connection is mandatory.
    • Message Server (optional)
  6. Click Apply.
  7. If you would like to configure your UCS Proxy for HA, repeat this procedure for the second instance.

Prerequisites

  • The UCS Proxy Application object has been configured.
  • The Interaction Management CD.
  1. Locate the Setup.exe for UCS Proxy (available on the Interaction Management CD).
  2. Double-click Setup.exe.
  3. Enter the login information for your Configuration Server:
    • Host
    • Port
    • User
    • Password
  4. Select the appropriate UCS Proxy Application object from the list.
  5. Click Install.

Prerequisites

  1. Locate the install.sh file for UCS Proxy.
  2. Start the installation script with the command install.sh.
  3. Press Enter to confirm the host name for the installation.
  4. Enter the login information for your Configuration Server:
    • Host
    • Port
    • User
    • Password
  5. From the list of applications, select one and enter its number in the list.
  6. Press Enter to confirm the suggested destination directory, or choose a desired one.
  7. Answer other questions, if required.
Important
On some Red Hat Linux platforms, eServices components might fail to start and produce the error ./cfgutility: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory. Refer to Compatibility Package for Red Hat Linux for information about correcting this issue.

Important
UCS Proxy is not supported with Genesys Agent Desktop and desktops that connect using Interaction SDK. A custom desktop that connects using Platform SDK Contact can use the Proxy server.

Prerequisites

  • Your desktop application is installed and configured.
  • The UCS Proxy is installed and configured.
  1. Login to Configuration Manager or Genesys Administrator.
  2. Locate the desktop Application object and open its Properties dialog box.
  3. On the Connections tab, remove the connection to the main Universal Contact Server.
  4. Add a connection to the UCS Proxy.
  5. Click Apply

Interaction Server Proxy Deployment

Prerequisites

  • The Interaction Management CD.

Procedure

  1. Create an Application object for the Proxy if it does not already exist.
    1. Import the correct application template from the Interaction Management CD for the Interaction Server Proxy.
    2. Create a new Application object based on the template.
  2. Open the Properties dialog box of the Application object.
  3. On the Server Info tab:
    • In the Host text box, enter the name of the desired host.
    • In the Communication Port text box, enter the port the Interaction Server Proxy will use for listening.
  4. On the Start Info tab enter some characters in the Working Directory, Command Line, and Command Line Arguments fields. These characters will be over-written with the correct values during the installation, but they cannot be left blank at this point.
  5. On the Connections tab, add connections to:
    • The primary Interaction Server. This connection is mandatory.
    • E-mail Server. This connection is required in order to send outbound e-mails from Workspace Desktop Edition.
    • Message Server (optional)
  6. Click Apply.
  7. If you would like to configure your Interaction Server Proxy for HA, repeat this procedure for the second instance.

Prerequisites

  • The Interaction ServerProxy Application object has been configured.
  • The Interaction Management CD.

Procedure

  1. Locate the Setup.exe for Interaction Server Proxy (available on the Interaction Management CD).
  2. Double-click Setup.exe.
  3. Enter the login information for your Configuration Server:
    • Host
    • Port
    • User
    • Password
  4. Select the appropriate Interaction Server Proxy Application object from the list.
  5. Click Install.

Prerequisites

Procedure

  1. Locate the install.sh file for Interaction Server Proxy.
  2. Start the installation script with the command install.sh.
  3. Press Enter to confirm the host name for the installation.
  4. Enter the login information for your Configuration Server:
    • Host
    • Port
    • User
    • Password
  5. From the list of applications, select one and enter its number in the list.
  6. Press Enter to confirm the suggested destination directory, or choose a desired one.
  7. Answer other questions, if required.
Important
On some Red Hat Linux platforms, eServices 8.1 components might fail to start and produce the error ./cfgutility: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory. Refer to Compatibility Package for Red Hat Linux for information about correcting this issue.

Important
Interaction Server Proxy is not supported with Genesys Agent Desktop and desktops that connect using Interaction SDK. A custom desktop that connects using Platform SDK Contact can use the Proxy server.

Prerequisites

  • Your desktop application is installed and configured.
  • The Interaction Server Proxy is installed and configured.

Procedure

  1. Login to Configuration Manager or Genesys Administrator.
  2. Locate the desktop Application object and open its Properties dialog box.
  3. On the Connections tab, remove the connection to the main Interaction Server.
  4. Add a connection to the Interaction Server Proxy.
  5. Click Apply

SMS Server Deployment

Prerequisites

  • The SMS Server CD.
  • The following Java versions:
    • In release 8.1.300.14 and later,
      • Windows: JDK 1.7
      • UNIX: JRE 1.7
    • In release 8.1.3 prior to 8.1.300.14,
      • Windows: JDK 1.6 or JDK 1.7
      • UNIX: JRE 1.6 or JRE 1.7
    • In releases prior to 8.1.3, JDK 1.6 on Windows and JRE 1.6 on UNIX
  1. Create an Application object for the SMS Server if it does not already exist.
    1. Import the correct application template from the SMS Server CD.
    2. Create a new Application object based on the template.
  2. Open the Properties dialog box of the Application object.
  3. On the Server Info tab:
    • In the Host text box, enter the name of the desired host.
    • In the Communication Port text box, enter the port the SMS Server will use for listening.
  4. On the Start Info tab enter some characters in the Working Directory, Command Line, and Command Line Arguments fields. These characters will be over-written with the correct values during the installation, but they cannot be left blank at this point.
  5. On the Connections tab, add connections to:
    • The primary Interaction Server. This connection is mandatory.
    • Message Server (optional)
  6. If this is for a multi-tenant environment, add the tenant(s) on the Tenants tab.
  7. Click Apply.

Prerequisites

  • The SMS Server Application object has been configured.
  • Java is installed on the host.
  • The SMS Server CD.
  1. Locate the Setup.exe for SMS Server (available on the SMS Server CD).
  2. Double-click Setup.exe.
  3. Select Java.
  4. Select Use Client Side Port if applicable.
  5. Enter the login information for your Configuration Server:
    • Host
    • Port
    • User
    • Password
  6. Select the appropriate SMS Server Application object from the list.
  7. Select the destination location.
  8. Select JDK.
  9. Click Install.
Important
Refer to the SMS Server Options Reference for additional information. You must properly configure the x-jsms-config-file option before using SMS Server.

Prerequisites

  • The SMS Server Application object has been configured.
  • JRE x64, or x32 (depending on Operating System version) is installed.
Important
  • For Oracle, Java version 1.6.0_26 or higher (within the 1.6 family) is supported. In release 8.1.3 and higher, JRE 1.7 is also supported.
  • For IBM, Java (OS AIX) version 1.6.0 build pap6460sr9fp2-20110627_03(SR9 FP2) for AIX or higher (within the 1.6 family) is supported. In release 8.1.3 and higher, Java 1.7 is also supported.
  • The SMS Server CD.
  • Review the section Compatibility Package for Red Hat Linux.
    1. Locate the install.sh file for SMS Server.
    2. Start the installation script with the command install.sh.
    3. Press Enter to confirm the host name for the installation.
    4. Enter the login information for your Configuration Server:
      • Host
      • Port
      • User
      • Password
    5. Choose whether the application will use Client Side Port.
    6. From the list of applications, select one and enter its number in the list.
    7. Press Enter to confirm the suggested destination directory, or choose another one inside the directory referred to by the GES_HOME_810 variable.
    8. Answer other questions, if required.
    Important
    On some Red Hat Linux platforms, eServices 8.1 components might fail to start and produce the error ./cfgutility: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory. Refer to Compatibility Package for Red Hat Linux for information about correcting this issue.
    Important
    Refer to the SMS Server Options Reference for additional information. You must properly configure the x-jsms-config-file option before using SMS Server. This option is required for MMS processing.

    SMS Server will work with Chat Server in session mode:

    1. Add a connection to Solution Control Server.
    2. Add a connection to one or more Chat Servers.

    Prerequisites

    • The SMS Server Application object exists.
    1. In Configuration Manager or Genesys Administrator, locate the Interaction Server Application object and open its properties.
    2. On the Connections tab, add a connection to SMS Server.
    3. Click Apply.

    Using the eServices Configuration Wizards

    For information about installing the eServices components using the wizards, see Using the eServices Configuration Wizards.

    Retrieved from "https://docs.genesys.com/Documentation:ES:Depl:Mdep02:8.5.1 (2019-07-16 04:08:52)"
    This page was last modified on February 15, 2019, at 12:36.

    Feedback

    Comment on this article:

    blog comments powered by Disqus