Jump to: navigation, search

Local Control Agent

Also known as LCA. A daemon component of the Management Layer that controls all daemon applications that are running within Genesys Framework. A Genesys-supplied software module that is loaded to each server platform that hosts one or more Genesys server modules. The purpose of LCA is to monitor the operating status of all locally running Genesys software modules, report errors, and restart modules if they stop operating.



Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Solution Control Interface

Also known as SCI. A Genesys Framework component that is used to administer Genesys solutions—for example, to start or stop the solution, view logs, configure event-triggered alarms, and provide real-time status information for all Genesys applications.



Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Preparing and Installing the Genesys Info Mart Server

This page provides detailed instructions for setting up the Genesys Info Mart Server host and installing the Genesys Info Mart Server application.

Preparing the Genesys Info Mart Server host

Review the Before You Proceed information and the high-level task summary on Installing Genesys Info Mart. Then:

  • If you want to use SCI to control the operation of the Genesys Info Mart Server, install, or verify the installation of, LCA. For more information, see Installing LCA.
  • Install the Java Development Kit (JDK) or Server Java Runtime Environment (JRE) and modify, or verify the content of, the PATH and the JAVA_HOME environment variables. For more information, see Installing Java.
  • Install, or verify the installation of, a Java Database Connectivity (JDBC) driver for each RDBMS that Genesys Info Mart Server will access (Microsoft SQL Server, Oracle, or PostgreSQL). Modify, or verify the content of, the CLASSPATH environment variable. For more information, see Installing JDBC Drivers.

Installing LCA

If you plan to monitor or control Genesys Info Mart through the Management Layer, you must also configure and install Management Layer components — in particular, LCA.

To monitor the status of Genesys Info Mart components through the Management Layer, you must load an LCA instance on every host that is running Info Mart instances. Without LCA, the Management Layer cannot monitor the status of components.

If you do not use the Management Layer, you do not need LCA.

You will need a Genesys Management Framework product CD in order to install the components of the Management Layer. For more information about these Framework components, including deployment instructions, see the Management Framework Deployment Guide and the Framework Management Layer User’s Guide for your release.

Installing Java

Install the JDK or Server JRE on the Genesys Info Mart Server host, according to instructions in the Java documentation. For the Java versions that Genesys Info Mart supports, see the Genesys Supported Operating Environment Reference Guide.

Then modify the PATH and the JAVA_HOME environment variables:

  • [+] Windows
  • [+] UNIX

Installing JDBC Drivers

JDBC Driver for Microsoft SQL Server

The Microsoft SQL Server Client is not shipped with a JDBC driver. Therefore, you must download and install the driver separately. The required driver is available from the Microsoft Download Center website by searching for “JDBC Driver.” Genesys Info Mart requires JDBC Driver 1.2 or higher.

Install the driver by following the installation instructions that are supplied with it. The name of the .jar file that contains the driver is sqljdbc4.jar. After the installation, you must update the CLASSPATH environment variable to include the path to the folder that contains this .jar file.

To modify the CLASSPATH environment variable, add <MSSQL-jdbc-driver-dir>\sqljdbc4.jar (where <MSSQL-jdbc-driver-dir> is the path where you installed the Microsoft SQL Server JDBC driver), so that it appears earlier in the class path than any other reference to Microsoft SQL Server JDBC driver.

JDBC Driver for Oracle

You must use Oracle Thin Driver version 11.2.0.1.0 or higher, regardless of the Oracle RDBMS version that you are using. The required Type 4 JDBC thin client driver ships with the Oracle client, or you can download it from the Oracle website.

Install the driver by following the installation instructions that are supplied with it. The class name of the driver that Genesys Info Mart uses for Oracle is oracle.jdbc.driver.OracleDriver. This class is from the ojdbc6.jar file. Install the driver by following the installation instructions that are supplied with it.

You must also modify your CLASSPATH environment variable, so that Genesys Info Mart can locate the JDBC driver. The specific CLASSPATH environment variable that you modify depends on the operating system and user account under which the Genesys Info Mart Server runs.

  • On Windows:

    • If you plan to use SCI to start and stop Genesys Info Mart Server, you must modify the CLASSPATH environment variable for either the system account or the user account under which you plan to start the LCA service.
    • If you plan to run Genesys Info Mart Server as a Windows service, you must modify the CLASSPATH environment variable for either the system account or the user account under which you plan to start the Genesys Info Mart Server Windows service.

    To modify the CLASSPATH environment variable on Windows, add <Oracle-jdbc-driver-dir>\ojdbc6.jar (where <Oracle-jdbc-driver-dir> is the path where you installed the Oracle JDBC driver), so that it appears earlier in the class path than any other reference to an Oracle JDBC driver.

  • On UNIX:

    • If you plan to use SCI to start and stop Genesys Info Mart Server, you must modify the CLASSPATH environment variable for the user account under which you plan to start LCA.
    • If you will not use SCI, you must modify the CLASSPATH environment variable for the user account under which you plan to start Genesys Info Mart Server.

    To modify the CLASSPATH environment variable on UNIX, add <Oracle-jdbc-driver-dir>/ojdbc6.jar (where <Oracle-jdbc-driver-dir> is the path where you installed the Oracle JDBC driver), so that it appears earlier in the class path than any other reference to an Oracle JDBC driver.

JDBC Driver for PostgreSQL

You must download and install the JDBC driver. The required driver is available from the PostgreSQL website by searching for “JDBC Driver.” Genesys Info Mart requires JDBC4.1 PostgreSQL Driver Version 9.4.1211.

Install the driver by following the installation instructions that are supplied with it. The name of the .jar file that contains the driver varies by version. For example, the minimum supported version is named postgresql-9.4.1211.jre7.jar. After the installation, you must update the CLASSPATH environment variable to include this .jar file.

To modify the CLASSPATH environment variable, add <PostgreSQL-jdbc-driver-dir>\<postgresql.jar> (where <PostgreSQL-jdbc-driver-dir> is the path where you installed the PostgreSQL JDBC driver and <postgresql.jar> is the name of the .jar file for the version), so that it appears earlier in the class path than any other reference to PostgreSQL JDBC driver.

Installing the Genesys Info Mart Application

You can install the Genesys Info Mart application on either a Windows or a UNIX operating system.

Installing the Genesys Info Mart application (Windows)

When you install Genesys Info Mart on a Windows operating system, Genesys Info Mart is also installed as a Windows service with a startup type of Automatic. This means that if the host machine is restarted, the Windows service will start Genesys Info Mart automatically.

The following procedure provides step-by-step instructions for installing Genesys Info Mart. You can install more than one Genesys Info Mart application that you have configured in the configuration interface you use.

Procedure: Installing the Genesys Info Mart application on Windows

Prerequisites

Steps

  1. Insert the Genesys Info Mart CD into the CD-ROM drive of the machine on which you want to install Genesys Info Mart.
  2. Navigate to, and open, the genesys-info-mart\windows directory.
  3. Double-click the setup.exe file, and then follow the directions in the installation wizard.
    Warning
    If you are installing on a 64-bit operating system, Genesys recommends that you specify an installation folder under /gcti/gim_etl/. There must not be any parentheses in the path name. For example, if you specify an installation folder under /Program Files (x86)/, the installation will fail.

    If you want to enable client-side port definition for the initial connection to Configuration Server, specify the required parameters on the Client Side Port Configuration page in the wizard. For more information, see the procedure about configuring a connection to Configuration Server on Windows in the chapter about client-side port definition in the Genesys Security Deployment Guide for your release.

    Tip
    The following error message might appear. If it does, you should ignore it:
    Unable to find configuration information. Either you have not used configuration wizards and the GCTISetup.ini file was not created or the file is corrupted.

Next Steps

Installing the Genesys Info Mart application (UNIX)

The following procedure provides step-by-step instructions for installing Genesys Info Mart. You can install more than one Genesys Info Mart application that you have configured in the configuration interface you use.

Procedure: Installing the Genesys Info Mart application on UNIX

Prerequisites

Steps

  1. Insert the Genesys Info Mart CD into the CD-ROM drive of the machine on which you want to install Genesys Info Mart.
  2. Locate the correct installation directory for your platform — for example, genesys_info_mart/gim_etl/solaris.
  3. Save the contents of this directory to a local folder.
  4. Locate and run the install.sh shell script. Enter requested information when you are prompted to do so.

    If you want to enable client-side port definition for the initial connection to Configuration Server, specify the required parameters when you get the Client Side Port Configuration prompt in the wizard. For more information, see the procedure about configuring a connection to Configuration Server on UNIX in the chapter about client-side port definition in the Genesys Security Deployment Guide for your release.

Next Steps

Verifying Host Requirements

As described in Preparing the Genesys Info Mart Server Host, Genesys Info Mart has specific requirements for supporting system software components and operational parameters, such as JDBC drivers and environment variables. This section describes important system information that you cannot verify or modify before installation.

gim_etl_paths.bat File

After the installation, verify that the path in the gim_etl_paths.bat file correctly points to the Java executable. For example:

set JAVACMD=java.exe

Update the path in the gim_etl_paths.bat file, if necessary.

For related information about modifying the PATH and JAVA_HOME environment variables, see Installing Java.

Modifying the Configuration Checkup Properties File

On startup, or whenever the configuration of the Genesys Info Mart application changes, the Genesys Info Mart Server automatically performs a configuration check, which includes verification that the correct JDBC driver version is available. If the available version is not as specified in a properties file (gim_cfg_checkup.properties), the configuration check logs an error, and the Genesys Info Mart Server will not run any jobs until the error has been fixed.

By default, the properties file specifies the required minimum version of Oracle Thin Driver (oracle.jdbc.driver.OracleDriver=11.2.0.1.0). For later Oracle versions, for Microsoft SQL Server deployments, or for PostgreSQL, you must modify the properties file to specify the installed version of the driver for Genesys Info Mart to use. After installation, the gim_cfg_checkup.properties file is available in the resources subfolder in the Genesys Info Mart installation folder.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on December 7, 2017, at 12:44.