Deploying Genesys Adapter

You run a .jar installation file to deploy Advisors Genesys Adapter (AGA) and Resource Management Console (RMC). You use the same installation file to deploy both, although you can install only a single component (either the AGA core service or RMC) during a single installer run. The installer guides you through the deployment. The screens displayed during your deployment are dependent on the selections you make on the Install Type and Server Install Type screens. The procedures on this page are specific to AGA deployment. If you are deploying RMC, see Deploying SDS and RMC.

Roadmap

1. [+] Install the databases that correspond to the Advisors products you will deploy.
   1. Advisors Genesys Adapter metrics database
   2. Advisors Platform database
   3. Advisors Cisco Adapter database (if you use ACA)
   4. Metric Graphing database
2. Create the Advisors User and the Object Configuration User in Configuration Server.
3. [+] Install the Platform service (Geronimo) on all servers on which you will deploy one of the Advisors components.
   • Contact Center Advisor
   • Workforce Advisor
   • Frontline Advisor
   • Contact Center Advisor–Mobile Edition
   • Resource Management Console
4. Install each adapter you will use (AGA and ACA). See additional information for CCAdv/WA installations.
5. [+] Install the Advisors components for your enterprise.
   • Contact Center Advisor
   • Workforce Advisor
   • Contact Center Advisor – Mobile Edition
   • Frontline Advisor
   • SDS and Resource Management
6. Make any required configuration changes.

You can deploy AGA on a Red Hat Linux or a Windows platform, and with Oracle or MS SQL databases.

Starting in Release 8.1.5, source metric definitions and statistics templates that were previously stored in the Advisors Genesys Adapter (AGA) database move to Advisors Platform tables. Configured objects and filters that were previously stored in the Advisors Genesys Adapter database move to Genesys Configuration Server. If you are migrating to Advisors release 8.1.5 as part of a migration to release 8.5.x, you have the additional step of recreating the AGA metrics schema before migrating from 8.1.5 to 8.5.0. See the Genesys 8.1 Performance Management Advisors Deployment Guide.

<tabber>

Migration Notes=

If you are migrating to a new software release, and not installing Advisors Genesys Adapter (AGA) for the first time, there is an existing AGA entry in the Adapter_Instances table in the Platform database. You have two options when upgrading your AGA instance:

1. Install the new AGA instance with the same host name and port number as the previous installation. The previous adapter is updated with the new configuration. For this option, you must have information about the earlier adapter to ensure you overwrite it successfully: host and port number. Ensure you enter that information on the Adapter Port and Registration Option installation screen to match the previous entry exactly. If this information is unavailable, you can find it in the ADAPTER_INSTANCES database table on the Platform database.
2. Install the new AGA instance with a different adapter host name and port number; it is added as a second adapter in the Platform database. Use this option to install a new adapter instance, or if you need to move the adapter to a new host name or port number. If moving the adapter to a new host name or port number, you must manually remove the previous adapter entry from the Platform database.

35px|link= Migrating the AGA Metrics Database or Schema

In release 8.1.5, you dropped and recreated the metrics schema or database as part of migration. This is unnecessary for release 8.5.0. To migrate to release 8.5.0, you use scripts supplied by Genesys to simply remove old objects and then add new objects to the Advisors Genesys Adapter metrics database. Genesys provides two scripts for Oracle and one for MS SQL; see the following procedures. Review the Readme.txt file included with the scripts. The Readme file includes important information, including which tools Genesys recommends to execute the scripts.

Migration of AGA Oracle METRICS Schemas

1. Connect as the METRICS user.

2. Execute gc_metrics_<version>_ObjectsDrop.sql

3. Execute gc_metrics_new_<version>_ObjectsPlus.sql

Migration of AGA MS SQL Databases

1. Connect to the AGA metrics database.

2. Execute gc_metrics_newdb_<version>.sql

|-| MCR Extensions=

MCR extensions are required for your Stat Server only if Interaction Queue statistics are to be collected. Use the following procedure to deploy the extensions.

1. Install Stat Server.

2. Install the MCR extension package. The MCR version corresponding to the most recent Stat Server release can be obtained from the Genesys installation CD image.

3. Configure the JVM path options for the Stat Server in Configuration Manager using the Stat Server application Options tab. If you require more information about Stat Server configuration than is provided below, see Framework 8.0 Stat Server Deployment Guide. Configure Stat Server Java options, such as [java-config], [java-options], and [java-extensions]. Set the JVM Path to the jvm.dll file (for example: C:\Program Files\Java\jre5\bin\client\jvm.dll). Set the ext directory to the relative path of the extensions directory under the Stat Server installation (the default is ./java/ext). Set the lib directory to the relative path of the library directory under the Stat Server installation (the default is ./java/lib). Select the eServiceContactStat.jar and eServiceInteractionStat.jar Java Extension jar files to be loaded.

4. Ensure that the Stat Server has a connection to the Interaction Server. Double-click the Stat Server application, and add this connection on the Connections tab if it is not already present.

5. Under the Stat Server application Options table, set enable-java to true.

6. Under the Stat Server application Options tab, create a new section named common. Set the value of option rebind-delay to 0 (zero). If you previously loaded the statserverentries.cfg file, this option is already there. Ensure you verify it is correct.

7. Ensure that the corresponding connection from the Interaction Server back to the Stat Server is also present. Double-click the Interaction Server Application, and add the connection on the Connections tab if it is not already present.

8. Restart both the Interaction Server and the Stat Server.

|-| AGA Server for CCAdv/WA=

1. Place the aga-installer-<version>.jar file into the Advisors home directory. [+] Show additional information for Linux environments You can start the installer locally or from a remote desktop. To run the installer remotely, use SSH with X11 forwarding enabled: ssh -X root@<host> As root, place the aga-installer-<version>.jar file into the Advisors home directory.

2. Launch the AGA installation file. [+] Show Steps for Linux As root, navigate to the Advisors home directory: cd /home/advisors As root, run the AGA installer. The page format of this document might cause a line break in the following command, but you must enter it on one line in the command prompt window: ./jdk1.7.0_<version>/bin/java -jar aga-installer-<version>.jar [+] Show Steps for Windows Do one of the following: Open a command line window, and enter the following command: java -jar aga-installer-<version>.jar Double-click the aga-installer-<version>.jar file in the release bundle. Double-clicking might not work due to system settings, but using the command line terminal should always work. Genesys recommends using the command line window to launch the installer. For 64-bit systems, if double-clicking to launch the installer, please ensure that the Java instance associated with the jar file type is 64-bit. Running the installer with a 32-bit Java instance will create a Windows service with the wrong executable.

3. On the Install Type screen, select the Install Server radio button. You can install only a single component (either the core service or RMC) during a single installer run.

4. On the Server Install Type screen, select the Contact Center Advisor/Workforce Advisor radio button. After installation, you must install and start the AGA service.

5. On the Installation details screen, specify the installation directory and the directory in which the log files will appear. The default installation directory is C:\Program Files\GCTI\Advisors\Genesys\Adapter.

6. On the Java Development Kit screen, specify the location of the root directory of the Java installation.

7. On the Database Type screen, select either the SQL Server or the Oracle option – whichever you use for databases in your installation. The screens that follow are dependent on your selection: [+] Show Step for SQL Server On the CCAdv/WA Metrics Database Configuration screen, specify the parameters for the metrics database: Server hostname—The host name or IP address of the database server. When using numerical IPv6 addresses, enclose the literal in brackets. Database port—The database server’s port number. Database name/SID—The unique name of the database instance; for example, advisors_gametricsdb. Database user—The Advisors user that will be used by the Adapter to access the database. Database user password—The password associated with the Advisors user that will be used by the Adapter to access the database. Important The CCAdv/WA metrics database password is encrypted and saved in the ...\GCTI\Advisors\Genesys\Adapter\conf\ inf_genesys_importer.properties file by default. To change the password, see Change Encrypted Passwords. [+] Show Steps for Oracle On the Oracle setup type screen, select the Basic radio button. On the Oracle JDBC Driver screen, specify the location of the Oracle JBDC driver. The following Oracle JDBC drivers can be used: Oracle database 10g release 2 (10.2.0.4). The download file is ojdbc14.jar. Oracle database 11g release 2 (11.2.0.2.0). The download file is ojdbc6.jar. On the CCAdv/WA Metrics Database Configuration screen, specify the parameters for the metrics database: Server hostname—The host name or IP address of the machine where the CCAdv/WA metrics database is installed. When using numerical IP v6 addresses, enclose the literal in brackets. Database port—The database server’s port number. Database name/SID—The unique name of the database instance; for example, advisors_gametricsdb. Database user—The Advisors user that will be used by the Adapter to access the database. Database user password—The password associated with the Advisors user that will be used by the Adapter to access the database. Important The CCAdv/WA metrics database password is encrypted and saved in the ...\GCTI\Advisors\Genesys\Adapter\conf\ inf_genesys_importer.properties file by default. To change the password, see Change Encrypted Passwords. [+] Show Steps for Oracle RAC On the Oracle setup type screen, select the RAC connectivity setup option. On the Oracle JDBC Driver screen, specify the location of the Oracle JBDC driver. The following Oracle JDBC drivers can be used: Oracle database 10g release 2 (10.2.0.4). The download file is ojdbc14.jar. Oracle database 11g release 2 (11.2.0.2.0). The download file is ojdbc6.jar. On the CCAdv/WA Metrics Database Configuration - RAC screen, specify the parameters for the metrics database: Database user—The Advisors user that will be used by the Adapter to access the database. Database password—The password associated with the Advisors user that will be used by the Adapter to access the database. Important The CCAdv/WA metrics database password is encrypted and saved in the ...\GCTI\Advisors\Genesys\Adapter\conf\ inf_genesys_importer.properties file by default. To change the password, see Change Encrypted Passwords. Locate file—Enter the location of the file that contains the advanced database connection string. If you do not know how to correctly build the advanced database connection string, contact your database administrator. The installation wizard applies the specified advanced connection string when configuring the data sources.

8. On the Platform Database Configuration screen, specify connection information for the the Advisors Platform database with which this AGA will be registered. You must complete this screen for all database types (MS SQL, Oracle basic, or Oracle RAC). If you use Oracle RAC, you will be prompted for additional information about the Advisors Platform database at Step 11. [+] Show More Enter the following information about the Advisors platform database with which this adapter will register: server hostname or IP address SID port schema and corresponding password

9. On the Genesys Data Source – Configuration Server screen, configure the connection to the Genesys Configuration Server(s). [+] Show Steps To connect to the primary (mandatory) Configuration Server in the Genesys environment, enter information in the following text fields: Name – The name of the primary configuration server. The name is obtained from the Configuration Manager and is case sensitive. Host name – The name or IP address of the machine hosting the Configuration Server. When using numerical IPv6 addresses, enclose the literal in brackets. Port – The port that the configuration server is listening on. If you enter a port number in this field, and then enable a TLS connection, this port number is ignored. Client name – The name of the application that Advisors Platform will use to log in to the Configuration Server (for example, default). User name – The user name of the account the Adapter will use to connect to the Configuration Server. Password – The corresponding password of the account the Adapter will use to connect to the Configuration Server. Important The Genesys Configuration Server password is encrypted and saved in the <adapterhome>\conf\inf_genesys_adapter.properties file by default. To change the password, see Change Encrypted Passwords. Add backup server – Select this checkbox only if you plan to configure the connection to a backup Configuration Server. The backup Configuration Server can be, but does not need to be, configured in a high-availability pair in Genesys. If you use a TLS connection to the Configuration Server, also complete the following: Enable TLS connection – To configure a TLS connection to the Configuration Server, select this option on the installation screen. If you have a backup Configuration Server, AGA also connects to it using TLS if you enable a TLS connection to the primary Configuration Server. Config Server TLS Port Number – Enter the Configuration Server TLS port number. If you enable a TLS connection, the TLS port number is used for both the primary and backup Configuration Servers. The port number for an unsecured connection is ignored. The primary and backup Configuration Servers must use the same TLS port number. Locate TLS properties file – Identify the location of the TLS properties file. The TLS properties file contains all the properties required to connect successfully using TLS, as well as any other optional TLS attributes that you use. If you use a backup Configuration Server, the TLS properties for the primary server are also used for the backup server. Add backup server – Select this checkbox only if you have a backup Configuration Server. The backup Configuration Server can be, but does not need to be, configured in a high-availability pair in Genesys. If you opted to add a backup Configuration Server, enter the information required to connect to that server on the Genesys Data Source – Backup Configuration Server screen: Backup server name – The name of the backup configuration server. The name is obtained from the Configuration Manager and is case sensitive. Backup host – The name or IP address of the machine hosting the backup Configuration Server. When using numerical IPv6 addresses, enclose the literal in brackets. Backup server port – The port that the backup Configuration Server is listening on. If you enter a port number in this field, but enabled a TLS connection for the primary Configuration Server, this port number is ignored. If the primary server connection uses a TLS connection, then the backup server connection is also a TLS connection. When you enable the TLS connection, you must enter the Configuration Server TLS port number; Advisors uses that port for the connection for both the primary and backup Configuration Servers.

10. On the Genesys Data Source – Stat Server Configuration screen, configure the connection to the data source Stat Server(s). [+] Show Steps To connect to the primary (mandatory) Stat Server in the Genesys environment, enter information in the following text fields: Name – The name of the Stat Server server. The name is obtained from the Configuration Manager and is case sensitive. Host name – The name or IP address of the machine hosting the Stat Server. When using numerical IPv6 addresses, enclose the literal in brackets. Port – The port that the Stat Server is listening on. If you have a backup Stat Server, also complete the following: Backup server name – Name of the backup Stat Server. This is obtained from the Configuration Manager. Backup host – Name or IP address of the machine hosting the backup Stat Server. When using numerical IPv6 addresses, enclose the literal in brackets. Backup server port – The port on which the backup Stat Server listens. To configure a second or subsequent Stat Server (or Stat Server pair), select the Another Stat Server? checkbox. Repeat this step for each Stat Server (pair) you want to add. Up to four additional Stat Server pairs can be configured—that is, a total of 10 Stat Servers can be configured. On the Genesys Data Source - Stat Server (continued) screen, specify the types of statistics supported on the Stat Server pair you are associating with this Genesys Adapter instance. The default is the Core statistics type for the Stat Server pair if you do not make a selection from the options. After installation, the configuration option is unavailable in the Advisors user interface. If you require a change in the configuration after installation, you must update the Stat Server configuration table. If you make changes, you must restart the Genesys Adapter. The 3rd Party Media and Multimedia statistics options require you to install the corresponding Java extensions on the Stat Servers. For more information, see Adapter Stat Server Configuration.

11. On the Adapter Port and Registration Option screen, you enter information that the Advisors Platform database requires to register this adapter instance. If your enterprise has an Oracle RAC database installation, the Enter Advisor Platform Database information for Adapter Registration screen prompts you for additional information about the Platform database with which the adapter will register. [+] Show More You must enter the following information about your adapter: The port number on which the Genesys Adapter web services will run. You can use the default port, 7000, if no other application is using that port. The name, host IP address, and description of the AGA server. For an Oracle RAC installation, you must also enter the following information about the Advisors Platform database on the Enter Advisor Platform Database information for Adapter Registration screen: The database schema and corresponding password created and used for the platform database. Enter the location of the file that contains the advanced database connection string. If you do not know how to correctly build the advanced database connection string, contact your database administrator. The installation wizard applies the specified advanced connection string when configuring the data sources.

12. After installation is complete, click Show Details, and then click Install and verify that there were no errors reported during installation.

13. Configure AGA to run automatically as a system service. [+] Show Steps for Linux As root, create an /etc/init.d/advisors-aga file with the following contents; remember to replace <version> with the version number of your file and <Advisors directory> with your directory’s name: #!/bin/bash # description: Advisors Genesys Adapter Start Stop Restart # processname: advisors-aga # chkconfig: 235 20 80 # # This script should be edited and installed in /etc/init.d directory # # Before using please edit PATH and AGA_BIN. # export PATH=/<path to jdk>/jdk1.7.0_<version>/bin:$PATH #NOTE: if AGA is installed not in home/advisors, change this part of the path too AGA_BIN=/home/advisors/<AGA directory>/bin cd $AGA_BIN case $1 in start) /bin/su advisors ./startup.sh ;; stop) ./shutdown.sh ;; restart) ./shutdown.sh /bin/su advisors ./startup.sh ;; esac exit 0 As root, make the startup script executable: chmod 755 /etc/init.d/advisors As root, configure the system to start the Advisors process at boot time: chkconfig --add advisors chkconfig --level 235 advisors on As root, check that the configuration is correct: chkconfig --list advisors The output should be similar to the following: advisors 0:off 1:off 2:on 3:on 4:off 5:on 6:off As root, test the service starts correctly: service advisors-aga start Wait until startup is complete. Open the Advisors interface in your browser (http://<host>:8080/admin/) and log in; the page should be available. As root, test that the service stops correctly: service advisors-aga stop Wait until shutdown is complete. Open the Advisors interface in your browser (http://<host>:8080/admin/) and log in; the page should be unavailable. [+] Show steps for Windows To install the Windows service, do one of the following: Navigate to the \bin folder and double-click the Install-Adapter-NT.bat file. Open a command line window, navigate to the \bin folder, and execute the bat file.

14. For every Stat Server (primary and backup) that you specified as part of the AGA server deployment, open the Stat Server configuration through the Configuration Manager and import the Advisor metrics on the Options tab. The metrics are stored in a file named StatServerEntries.cfg, and the file is located in C:\Program Files\GCTI\advisors\Genesys\Adapter\CONF (or the location you specified in which to install the Advisors Genesys Adapter). This configuration file also contains settings for the Stat Server logging. The location of the log file can be changed by changing the following options in the Stat Server Options tab under the Log section: all=statserver.log standard=statserver.log

|-| AGA Server for FA=

1. Place the aga-installer-<version>.jar file into the Advisors home directory. [+] Show additional information for Linux environments You can start the installer locally or from a remote desktop. To run the installer remotely, use SSH with X11 forwarding enabled: ssh -X root@<host> As root, place the aga-installer-<version>.jar file into the Advisors home directory.

2. Launch the AGA installation file. [+] Show Steps for Linux As root, navigate to the Advisors home directory: cd /home/advisors As root, run the AGA installer. The page format of this document might cause a line break in the following command, but you must enter it on one line in the command prompt window: ./jdk1.7.0_<version>/bin/java -jar aga-installer-<version>.jar [+] Show Steps for Windows Do one of the following: Open a command line window, and enter the following command: java -jar aga-installer-<version>.jar Double-click the aga-installer-<version>.jar file in the release bundle. Double-clicking might not work due to system settings, but using the command line terminal should always work. Genesys recommends using the command line window to launch the installer. For 64-bit systems, if double-clicking to launch the installer, please ensure that the Java instance associated with the jar file type is 64-bit. Running the installer with a 32-bit Java instance will create a Windows service with the wrong executable.

3. On the Install Type screen, select the Install Server radio button. You can install only a single component (either the core service or RMC) during a single installer run.

4. On the Server Install Type screen, select the Frontline Advisor radio button. After installation, you must install and start the service.

5. On the Installation details screen, specify the installation directory and the directory in which the log files will appear. The default installation directory is C:\Program Files\GCTI\Advisors\Genesys\Adapter.

6. On the Java Development Kit screen, specify the location of the root directory of the Java installation.

7. On the Database Type screen, select either the SQL Server or the Oracle option – whichever you use for databases in your installation. If you select Oracle as your database type, you are prompted for additional information. [+] Show Steps for single-instance Oracle installations On the Oracle setup type screen, select the Basic radio button. On the Oracle JDBC Driver screen, specify the location of the Oracle JBDC driver. The following Oracle JDBC drivers can be used: Oracle database 10g release 2 (10.2.0.4). The download file is ojdbc14.jar. Oracle database 11g release 2 (11.2.0.2.0). The download file is ojdbc6.jar. [+] Show Steps for Oracle RAC installations On the Oracle setup type screen, select the RAC connectivity setup option. On the Oracle JDBC Driver screen, specify the location of the Oracle JBDC driver. The following Oracle JDBC drivers can be used: Oracle database 10g release 2 (10.2.0.4). The download file is ojdbc14.jar. Oracle database 11g release 2 (11.2.0.2.0). The download file is ojdbc6.jar.

8. On the Platform Database Configuration screen, specify connection information for the the Advisors Platform database with which this AGA will be registered. You must complete this screen for all database types (MS SQL, Oracle basic, or Oracle RAC). If you use Oracle RAC, you will be prompted for additional information about the Advisors Platform database at Step 11. [+] Show More Enter the following information about the Advisors platform database with which this adapter will register: server hostname or IP address SID port schema and corresponding password

9. On the Genesys Data Source – Configuration Server screen, configure the connection to the Genesys Configuration Server(s). [+] Show Steps To connect to the primary (mandatory) Configuration Server in the Genesys environment, enter information in the following text fields: Name – The name of the primary configuration server. The name is obtained from the Configuration Manager and is case sensitive. Host name – The name or IP address of the machine hosting the Configuration Server. When using numerical IPv6 addresses, enclose the literal in brackets. Port – The port that the configuration server is listening on. If you enter a port number in this field, and then enable a TLS connection, this port number is ignored. Client name – The name of the application that Advisors Platform will use to log in to the Configuration Server (for example, default). User name – The user name of the account the Adapter will use to connect to the Configuration Server. Password – The corresponding password of the account the Adapter will use to connect to the Configuration Server. Important The Genesys Configuration Server password is encrypted and saved in the <adapterhome>\conf\inf_genesys_adapter.properties file by default. To change the password, see Change Encrypted Passwords. Add backup server – Select this checkbox only if you plan to configure the connection to a backup Configuration Server. The backup Configuration Server can be, but does not need to be, configured in a high-availability pair in Genesys. If you use a TLS connection to the Configuration Server, also complete the following: Enable TLS connection – To configure a TLS connection to the Configuration Server, select this option on the installation screen. If you have a backup Configuration Server, AGA also connects to it using TLS if you enable a TLS connection to the primary Configuration Server. Config Server TLS Port Number – Enter the Configuration Server TLS port number. If you enable a TLS connection, the TLS port number is used for both the primary and backup Configuration Servers. The port number for an unsecured connection is ignored. The primary and backup Configuration Servers must use the same TLS port number. Locate TLS properties file – Identify the location of the TLS properties file. The TLS properties file contains all the properties required to connect successfully using TLS, as well as any other optional TLS attributes that you use. If you use a backup Configuration Server, the TLS properties for the primary server are also used for the backup server. Add backup server – Select this checkbox only if you have a backup Configuration Server. The backup Configuration Server can be, but does not need to be, configured in a high-availability pair in Genesys. If you opted to add a backup Configuration Server, enter the information required to connect to that server on the Genesys Data Source – Backup Configuration Server screen: Backup server name – The name of the backup configuration server. The name is obtained from the Configuration Manager and is case sensitive. Backup host – The name or IP address of the machine hosting the backup Configuration Server. When using numerical IPv6 addresses, enclose the literal in brackets. Backup server port – The port that the backup Configuration Server is listening on. If you enter a port number in this field, but enabled a TLS connection for the primary Configuration Server, this port number is ignored. If the primary server connection uses a TLS connection, then the backup server connection is also a TLS connection. When you enable the TLS connection, you must enter the Configuration Server TLS port number; Advisors uses that port for the connection for both the primary and backup Configuration Servers.

10. On the Genesys Data Source – Stat Server Configuration screen, configure the connection to the data source Stat Server(s). [+] Show Steps To connect to the primary (mandatory) Stat Server in the Genesys environment, enter information in the following text fields: Name – The name of the Stat Server server. The name is obtained from the Configuration Manager and is case sensitive. Host name – The name or IP address of the machine hosting the Stat Server. When using numerical IPv6 addresses, enclose the literal in brackets. Port – The port that the Stat Server is listening on. If you have a backup Stat Server, also complete the following: Backup server name – Name of the backup Stat Server. This is obtained from the Configuration Manager. Backup host – Name or IP address of the machine hosting the backup Stat Server. When using numerical IPv6 addresses, enclose the literal in brackets. Backup server port – The port on which the backup Stat Server listens. To configure a second or subsequent Stat Server (or Stat Server pair), select the Another Stat Server? checkbox. Repeat this step for each Stat Server (pair) you want to add. Up to four additional Stat Server pairs can be configured—that is, a total of 10 Stat Servers can be configured. On the Genesys Data Source - Stat Server (continued) screen, specify the types of statistics supported on the Stat Server pair you are associating with this Genesys Adapter instance. The default is the Core statistics type for the Stat Server pair if you do not make a selection from the options. After installation, the configuration option is unavailable in the Advisors user interface. If you require a change in the configuration after installation, you must update the Stat Server configuration table. If you make changes, you must restart the Genesys Adapter. The 3rd Party Media and Multimedia statistics options require you to install the corresponding Java extensions on the Stat Servers. For more information, see Adapter Stat Server Configuration.

11. On the Adapter Port and Registration Option screen, you enter information that the Advisors Platform database requires to register this adapter instance. If your enterprise has an Oracle RAC database installation, the Enter Advisor Platform Database information for Adapter Registration screen prompts you for additional information about the Platform database with which the adapter will register. [+] Show More You must enter the following information about your adapter: The port number on which the Genesys Adapter web services will run. You can use the default port, 7000, if no other application is using that port. The name, host IP address, and description of the AGA server. For an Oracle RAC installation, you must also enter the following information about the Advisors Platform database on the Enter Advisor Platform Database information for Adapter Registration screen: The database schema and corresponding password created and used for the platform database. Enter the location of the file that contains the advanced database connection string. If you do not know how to correctly build the advanced database connection string, contact your database administrator. The installation wizard applies the specified advanced connection string when configuring the data sources.

12. After installation is complete, click Show Details, and then click Install and verify that there were no errors reported during installation.

13. Configure AGA to run automatically as a system service. [+] Show Steps for Linux As root, create an /etc/init.d/advisors-aga file with the following contents; remember to replace <version> with the version number of your file and <Advisors directory> with your directory’s name: #!/bin/bash # description: Advisors Genesys Adapter Start Stop Restart # processname: advisors-aga # chkconfig: 235 20 80 # # This script should be edited and installed in /etc/init.d directory # # Before using please edit PATH and AGA_BIN. # export PATH=/<path to jdk>/jdk1.7.0_<version>/bin:$PATH #NOTE: if AGA is installed not in home/advisors, change this part of the path too AGA_BIN=/home/advisors/<AGA directory>/bin cd $AGA_BIN case $1 in start) /bin/su advisors ./startup.sh ;; stop) ./shutdown.sh ;; restart) ./shutdown.sh /bin/su advisors ./startup.sh ;; esac exit 0 As root, make the startup script executable: chmod 755 /etc/init.d/advisors As root, configure the system to start the Advisors process at boot time: chkconfig --add advisors chkconfig --level 235 advisors on As root, check that the configuration is correct: chkconfig --list advisors The output should be similar to the following: advisors 0:off 1:off 2:on 3:on 4:off 5:on 6:off As root, test the service starts correctly: service advisors-aga start Wait until startup is complete. Open the Advisors interface in your browser (http://<host>:8080/admin/) and log in; the page should be available. As root, test that the service stops correctly: service advisors-aga stop Wait until shutdown is complete. Open the Advisors interface in your browser (http://<host>:8080/admin/) and log in; the page should be unavailable.

14. For every Stat Server (primary and backup) that you specified as part of the AGA server deployment, open the Stat Server configuration through the Configuration Manager and import the Advisor metrics on the Options tab. The metrics are stored in a file named StatServerEntries.cfg, and the file is located in C:\Program Files\GCTI\advisors\Genesys\Adapter\CONF (or the location you specified in which to install the Advisors Genesys Adapter). This configuration file also contains settings for the Stat Server logging. The location of the log file can be changed by changing the following options in the Stat Server Options tab under the Log section: all=statserver.log standard=statserver.log

|-| Multiple instances on a server=

It is possible to deploy multiple instances of the Genesys Adapter core service on a single server. If you do use the same metrics database for more than one adapter, each adapter must monitor a completely distinct set of objects. For each installation, you should:

• Create the metrics database.
• Install and configure the AGA core service.

Deploy the second, and subsequent AGA instances, using the same procedure you use to deploy a single instance, and follow these rules:

• You must install each Genesys Adapter instance in a different directory. For example, the first instance could use the following location:
  C:\Program Files\GCTI\Advisors\Genesys\Adapter
  and the second instance could be located at:
  C:\Program Files\GCTI\Advisors\Genesys\Adapter2.
• You must specify a unique log directory for each Genesys Adapter instance.
• You must specify a unique port number for each Genesys Adapter instance.

You must also edit the configuration file for each additional AGA core service deployment. See the following procedure.

1. Once the additional adapter has been installed, navigate to the conf folder for this installation.

2. Locate the file wrapper.conf and edit it as follows: Search for the # Name of service string. Edit the parameter below it (wrapper.ntservice.name=) so that the service name is different from the original instance. For example, enter Advisors Genesys Adapter 2. Edit the next parameter (wrapper.ntservice.displayname=) so that it differs from the original instance. This is the name that will appear in the NT Services dialog. It need not match the name used in wrapper.ntservice.name= above, but it can.

3. Save and close the file.

4. Navigate to the bin folder for the second installation, and execute the Install-Adapter-NT.bat file. This installs the renamed service. After the installation is complete, you can then locate and start the service in the Services Control Panel applet.

|-| Troubleshooting=

The following Table shows parameter validation errors that you may encounter at the end of installation.

Installation Error Message	Cause
[java] Failed to connect to the database using connection URL: [java] jdbc:sqlserver://192.168.xx.yy:nnn;DatabaseName=ys_gadb;user=sa;password=very_secure_pwd; selectMethod=cursor [java] The following exception was thrown: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host 192.168.xx.yy, port nnn has failed. Error: "Connection refused. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.	Wrong database server name / IP address or port number
[java] Failed to connect to the database using connection URL: [java] jdbc:sqlserver://192.168.xx.yy:nnnn;DatabaseName=NotAPlatformDB;selectMethod=cursor;user=sa; password=very_secure_pwd [java] The following exception was thrown: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host 192.168.xx.yy, port nnnn has failed. Error: "connect timed out. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port."	Wrong database name
[java] Exception while connecting: Login failed for user 'badUserId'. [java] url used: jdbc:sqlserver://192.168.xx.yy:nnnn;DatabaseName=ys_gadb;selectMethod=cursor;user=badUserId; password=very_secure_password	Wrong database user name or password
[loadfile] Unable to load file: java.io.FileNotFoundException: C:\ (The system cannot find the path specified)	Produced in error and can be ignored.