Advisors Software Distribution Contents

Click the links below to view the software contents that Genesys provides for each Performance Management Advisors product.

[+] Advisors Platform

Distribution Artifacts	Contents	Notes
advisors-platform-installer- <version>.jar		The installer for the Platform.
advisors-migration-wizard-<version>.jar user-migration-util-<version>.jar (See User Migration Utility)		Migration utilities located in supplement directory: ip\supplement
baseweb-<version>-static-web.zip		A copy of the static files that can be served by Apache.
SQL Server platform-new-database-<version>.sql	Creates DB objects for MS SQL Platform database after the Platform database is created. Refer to Creating a SQL Server Database for instructions about MS SQL Server database creation.	The creation and migration script for the Platform database for MSSQL. This script is located in the sql\mssql directory.
Oracle advisors-platform-migrate_<old version>_<new version>.sql advisors-platform-<version>_CUSTOM_ROUTINE.sql advisors-platform-<version>_INIT_DATA.sql advisors-platform-<version>_ObjectsCustom.sql advisors-platform-<version>_ObjectsDefault.sql advisors-platform-<version>_ObjectsPlus.sql advisors-platform-<version>_Readme.txt advisors-platform-<version>_ROUTINE.sql advisors-platform-<version>_Schema.sql advisors-platform-<version>_TBS.sql advisors-platform-<version>_User.sql	..._CUSTOM_ROUTINE.sql Not to be executed manually. Used by the scripts in runtime. ..._INIT_DATA.sql Not to be executed manually. Used by the scripts in runtime. ..._ROUTINE.sql Not to be executed manually. Used by the scripts in runtime. ..._TBS.sql To be executed by a database user who has permission to create tablespaces. The script generates a resulting script, runTbsCre.sql, based on the user dialog input. The script issues a prompt which allows you to postpone the execution of the resulting script. If necessary, the resulting script can be customized to meet your needs and environment and executed later. A minimum requirement is to create at least one user default tablespace and a separate user temporary tablespace exclusively for the platform user/schema. In most cases, tablespaces are created by your DBA. The file can be used for DBA information as it shows sizing and possible table distribution among multiple tablespaces. Note, the sizing must be adjusted before the script execution. If created by the DBA, the DBA provides the tablespaces information to the engineer who proceeds with the installation. ...User.sql Creates platform user and schema. To be executed by a database user who has permission to create other users. In most cases, users are created by your DBA. The file can be used as is or for DBA information as it shows user permission and tablespace requirements. If the user/schema is created by DBA, the DBA provides the relevant information to the engineer who proceeds with the installation. ...ObjectsPlus.sql An SQL*Plus script that creates all platform database objects. To be executed by the previously-created platform user and after all planned tablespaces are created. ...ObjectsCustom.sql An alternative script that has the same purpose as ...ObjectsPlus.sql, but can be executed from Oracle Sql Developer by the previously-created platform user and after all planned tablespaces are created. The script allows table and index distribution among multiple tablespaces by issuing pop-up prompts. ...ObjectsDefault.sql An alternative script similar to ...ObjectsCustom.sql that has the same purpose as ...ObjectsPlus.sql. To be executed from Oracle Sql Developer by the previously-created platform user. The script does not issue any pop-up prompts and creates all platform database objects in the platform user default tablespace assigned during platform user creation. ...Schema.sql Creates the platform user, schema, and all database objects. To be executed by a database user who has permission to create other users. An alternative script that replaces, and has the same purpose as, ...User.sql and ...ObjectsPlus.sql combined.	The creation scripts for the Platform database for Oracle. These scripts are located in the sql\oracle directory. For additional details, please refer to: migrate_plt_Readme.txt, if present. Otherwise, refer to the Release Notes. plt_Readme.txt, if present. Otherwise, refer to the Release Notes.

[+] Advisors Genesys Adapter

Distribution Artifacts	Contents	Notes
aga-installer-<version >.jar		The installer for Genesys Adapter.
SQL Server gc_metrics_newdb_<version>.sql		The creation and migration scripts for the Genesys Adapter database for MSSQL. These scripts are located in the configuration-schema\mssql directory.
Oracle gc_metrics_new_<version>_ObjectsCustom.sql gc_metrics_new_<version>_ObjectsDefault.sql gc_metrics_new_<version>_ObjectsPlus.sql gc_metrics_new_<version>_ROUTINE.sql gc_metrics_new_<version>_User.sql gc_metrics_new_<version>_TBS.sql gc_metrics_new_<version>_Schema.sql	..._ROUTINE.sql Not to be executed manually. Used by the scripts in runtime. ..._TBS.sql To be executed by a database user who has permission to create tablespaces. The script contains some sizing recommendations. The sizing must be adjusted before the script execution. The script issues a prompt that allows you to postpone the actual tablespace creation. Instead, a resulting script, runTbsCre.sql, is generated based on the user dialog input. If necessary, the resulting script can be customized to the needs of the environment and executed later. A minimum requirement is to create at least one user default tablespace and a separate user temporary tablespace exclusively for AGA metrics user/schema. In most cases, tablespaces are created by your DBA. If created by the DBA, the DBA provides the tablespaces information to the engineer who proceeds with the installation. ...User.sql Creates the AGA metrics user and schema. To be executed by a database user who has permission to create other users. In most cases, users are created by your DBA. The file can be used as is or for DBA information as it shows user permission and tablespace requirements. If the user/schema is created by the DBA, the DBA provides the relevant information to the engineer who proceeds with the installation. ...ObjectsPlus.sql An SQL*Plus script that creates all AGA metrics DB objects. To be executed by the previously-created AGA metrics user and after all the planned tablespaces are created. ...ObjectsCustom.sql An alternative script that has the same purpose as ...ObjectsPlus.sql, but can be executed from Oracle Sql Developer by the previously-created AGA metrics user and after all the planned tablespaces are created. The script allows table and index distribution among multiple tablespaces by issuing pop-up prompts. ...ObjectsDefault.sql An alternative script similar to ...ObjectsCustom.sql that has the same purpose as ...ObjectsPlus.sql. To be executed from Oracle Sql Developer by the previously-created platform user. The script does not issue any pop-up prompts and creates all AGA metrics database objects in the platform user default tablespace assigned during platform user creation. ...Schema.sql Creates the AGA metrics user, schema, and all database objects. To be executed by a database user who has permission to create other users. An alternative script that replaces, and has the same purpose as, ...User.sql and ...ObjectsPlus.sql combined.	The creation and migration scripts for the Genesys Adapter databases for Oracle. These scripts are located in the configuration-schema\oracle directory.

[+] Supervisor Desktop Service

Distribution Artifacts	Notes
sds-installer-<version >.jar	The installer for Supervisor Desktop Service

[+] Advisors Cisco Adapter

Distribution Artifacts	Contents	Notes
aca-installer-<version>.jar		The installer for Cisco Adapter
SQL aca-new-database-<version>.sql aca-migration-3.3-to-8.0.sql aca-migration-8.0-to-8.1.sql aca-migration-8.1-to-8.1.1.sql aca-migration-8.1.1-to-8.1.2.sql aca-migration-8.1.2-to-8.1.3.sql aca-migration-8.1.3-to-8.1.4.sql aca-migration-8.1.4-to-8.1.5.sql GeneratePermsStatements.sql		The creation and migration scripts for the Cisco Adapter databases for MSSQL. These scripts are located in the mssql directory.
Oracle aca-<version>_TBS.sql aca-<version>_Schema.sql aca-new-database-<version>.sql aca-migration-8.1-to-8.1.1.sql aca-migration-8.1.1-to-8.1.2.sql aca-migration-8.1.2-to-8.1.3.sql aca-migration-8.1.3-to-8.1.4.sql aca-migration-8.1.4-to-8.1.5.sql	aca_..._TBS.sql The script creates ACATBS_USER data tablespace and ACATBS_TMP temporary tablespace under the path specified on the prompt. To be executed by a database user who has permission to create tablespaces. If necessary, the sizing can be adjusted before the script execution. If it is necessary to change the suggested tablespace names, the script must be edited before execution as follows: ACATBS_USER must be replaced with another suitable tablespace name that must be used as the default FA user tablespace. ACATBS_TMP must be replaced with another suitable tablespace name that must be used as the temporary ACA user tablespace. The script generates a resulting script, runTbsCre.sql, based on user dialog input. If there is any error, the resulting script can be customized to the needs and environment and executed again. A minimum requirement is to create one user default tablespace and a separate user temporary tablespace exclusively for the ACA user/schema. In most cases, tablespaces are created by your DBA. If created by a DBA, the DBA provides the tablespaces information to the engineer who proceeds with the installation. faca-new-database-....sql Creates all ACA database objects. Executed by the previously-created ACA user. In most cases users are created by your DBA. The DBA can use aca_...Schema.sql (see the description below) for information about required user permissions and tablespace requirements. If the user/schema is created by the DBA, the DBA provides the relevant information to the engineer who proceeds with the database object creation and further installation. aca_...Schema.sql Creates the ACA user, schema, and all database objects. Replaces manual user creation and aca-new-database-....sql. To be executed by a database user who has permission to create other users. This is an alternative script normally used in non-production environments.	The creation and migration scripts for the Cisco Adapter databases for Oracle. These scripts are located in the oracle directory.

[+] Contact Center Advisor/Workforce Advisor

Distribution Artifacts	Contents	Notes
ccadv-wa-server-installer-<version>.jar		The installer for CCAdv and WA modules, as well as CCAdv–ME starting in Release 8.1.5.
SQL Server mg-new-database-<version>.sql		The creation and migration database script for Metric Graphing for MS SQL. This script is located in the sql\mssql directory. You have the following folders: mssql-standard (for installations that use MS SQL Standard Edition) mssql-enterprise (for installations that use MS SQL Enterprise Edition) Files within each folder use the same filename convention as previous releases. Ensure you use the files from the folder that corresponds to your edition of Microsoft SQL Server.
Oracle mg-<version>_User mg-<version>_TBS.sql mg-<version>_Schema.sql mg-<version>_ROUTINE.sql mg-<version>_ObjectsPlus mg-<version>_ObjectsDefault mg-<version>_ObjectsCustom mg-<version>_INIT_DATA.sql	..._CUSTOM_ROUTINE.sql Not to be executed manually. Used by the scripts in runtime. ..._INIT_DATA.sql Not to be executed manually. Used by the scripts in runtime. ..._ROUTINE.sql Not to be executed manually. Used by the scripts in runtime. ..._TBS.sql To be executed by a database user who has permission to create tablespaces. The script generates a resulting script, runTbsCre.sql, based on the user dialog input. The script issues a prompt that allows you to postpone execution of the generated resulting script. If necessary, the resulting script can be customized to meet your needs and environment and executed later. A minimum requirement is to create at least one user default tablespace and a separate user temporary tablespace exclusively for the CCA/WA metric graphing user/schema. Note, the sizing must be adjusted before the script execution. In most cases tablespaces are created by your DBA. The file can be used for DBA information as it shows sizing and possible table distribution among multiple tablespaces. If created by the DBA, the DBA provides the tablespaces information to the engineer who proceeds with the installation. ...User.sql Creates the CCAdv/WA metrics graphing user and schema. To be executed by a database user who has permission to create other users. In most cases, users are created by your DBA. The file can be used as is or for DBA information as it shows user permission and tablespace requirements. If the user/schema is created by the DBA, the DBA provides the relevant information to the engineer who proceeds with the installation. ...ObjectsPlus.sql An SQL*Plus script that creates all CCA/WA database objects necessary for metrics graphing. To be executed by the previously-created CCAdv/WA metric graphing user and after all planned tablespaces are created. ...ObjectsCustom.sql An alternative script that has the same purpose as ...ObjectsPlus.sql, but can be executed from Oracle Sql Developer by the previously-created CCAdv/WA metric graphing user and after all planned tablespaces are created. The script allows table and index distribution among multiple tablespaces by issuing pop-up prompts. ...ObjectsDefault.sql An alternative script similar to ...ObjectsCustom.sql that has the same purpose as ...ObjectsPlus.sql. To be executed from Oracle Sql Developer by the previously-created CCAdv/WA metric graphing user. The script does not issue any pop-up prompts and creates all platform database objects in the platform user default tablespace assigned during platform user creation.	The creation database scripts for Metric Graphing for Oracle. These scripts are located in the sql\oracle directory. You have the following folders: oracle-without-partitions (for installations that use Oracle without the partitioning option) oracle-with-partitions (for installations that use Oracle with the partitioning option) Files within each folder use the same filename convention as previous releases. Ensure you use the files from the folder that corresponds to your edition of Oracle. For additional details, refer to the migrate_mg_8.1_<version>Readme.txt file, if present. Otherwise, refer to Release Notes.

[+] Frontline Advisor/Agent Advisor

Distribution Artifacts	Contents	Notes
fa-server-installer-<version>.jar		The installer for FA/AA.
SQL Server fa-new-database-<version>.sql fa-database-migration-3.1-to-3.3.sql fa-database-migration-3.3-to-8.0.sql fa-database-migration-8.0-to-8.1.sql fa-database-migration-8.1-to-8.1.1.sql fa-database-migration-8.1.1-to-8.1.2.sql fa-database-migration-8.1.2-to-8.1.3.sql fa-database-migration-8.1.3-to-8.1.4.sql fa-database-migration-8.1.4-to-8.1.5.sql	Creates database objects for the MSSQL FA database after the FA database is created. Refer to Creating a SQL Server Database for instruction about MSSQL Server database creation.	The creation and migration scripts for the FA/AA database for MSSQL. These scripts are located in the mssql and mssql\migrations directories.
Oracle fa_<version>_TBS.sql fa_<version>_Schema.sql fa-new-database-<version>.sql fa-database-migration-8.1-to-8.1.1.sql fa-database-migration-8.1.1-to-8.1.2.sql fa-database-migration-8.1.2-to-8.1.3.sql fa-database-migration-8.1.3-to-8.1.4.sql fa-database-migration-8.1.4-to-8.1.5.sql	fa_..._TBS.sql The script creates the FATBS_USER data tablespace and FATBS_TMP temporary tablespace under the path specified on the prompt and appends frontline to this path sub-folder name. The script contains sizing recommendations. The sizing must be adjusted before the script execution. To be executed by a database user who has permission to create tablespaces. If it is necessary to change the suggested tablespace name and the file path, the script must be edited before its execution as follows: FATBS_USER must be replaced with another suitable tablespace name that needs to be used as the default FA user tablespace. FATBS_TMP must be replaced with another suitable tablespace name that must be used as the temporary FA user tablespace. Replace the line fapath := ''|| fapath || 'frontline' || osfs; with fapath := ''|| fapath || osfs; to prevent the script from appending a frontline sub-folder name to the specified path. In this case, the files are created under the path specified on the related prompt issued by the script when it is executed. The script generates a resulting script, runTbsCre.sql, based on user dialog input. If there is an error, the resulting script can be customized to the needs of the environment and executed again. A minimum requirement is to create at least one user default tablespace and a separate user temporary tablespace exclusively for FA user/schema. In most cases, tablespaces are created by your DBA. If created by the DBA, the DBA provides the tablespaces information to the engineer who proceeds with the installation. fa-new-database-....sql Creates all FA database objects. Executed by the previously-created FA user. In most cases, users are created by your DBA. The DBA can use fa_...Schema.sql for information about required user permissions and tablespace requirements. If the user/schema is created by the DBA, the DBA provides the relevant information to the engineer who proceeds with the database object creation and installation. fa_...Schema.sql Creates the FA user, schema, and all database objects. Replaces manual user creation and fa-new-database-....sql. To be executed by a database user who has permission to create other users. This is an alternative script normally used in non-production environments.	The creation and migration scripts for the FA/AA database for Oracle. These scripts are located in the oracle and oracle\migrations directories.
SQL Server fa-hierarchy-mssql-<version>.sql hierarchy-migration-3.1-to-3.3.sql hierarchy-migration-3.3-to-8.0.sql hierarchy-migration-8.0-to-8.1.sql		The creation and migration scripts for the FA/AA hierarchy database for MSSQL. These scripts are located in the mssql and mssql\migrations directories.
Oracle Not applicable.