Distribution Artifacts
|
Contents
|
Notes
|
advisors-platform-installer- <version>.jar
|
The installation file for Advisors Platform.
|
In release 8.5.2, you use the Advisors Platform installation wizard to install the Advisors Web services and to configure available integration with Genesys Pulse. For detailed information about the Advisors Platform installation wizard, see Deploying Advisors Platform.
|
baseweb-<version>-static-web.zip
|
A copy of the static files that can be served by Apache.
|
|
supplement/
advisors-migration-wizard-<version>.jar
user-migration-util-<version>.zip
|
The Advisors migration utilities.
|
See User Migration Utility and Object Migration Utility in the Genesys Performance Management Advisors Migration Guide.
|
platform-database-sql/mssql/
advisors-platform-new-database-<version>.sql
advisors-platform-migrateSchema_<from-versions>_<to-version>.sql
Readme-advisors-platform-migrate_<from-versions>_<to-version>.txt
|
- ...-new-database-8.5.202.09.sql
- Creates database objects for the MS SQL Platform database after the Platform database is created.
- ...-migrateSchema_8.5.101(102)_8.5.202.09.sql
- The scripts to update an existing MS SQL Platform database. The scripts are applicable to Advisors release 8.5.102 and to the release immediately preceding 8.5.102 (that is, release 8.5.101.21).
|
For additional details, see the ReadMe file, if present. The Readme-advisors-platform-migrate_8.5.101(102)_8.5.202.09.txt file is applicable to Advisors release 8.5.102 and to the release immediately preceding 8.5.102 (that is, release 8.5.101.21). Also see the Release Notes.
To create an MS SQL database for Advisors, see instructions on the Creating a SQL Server Database page in this Guide.
To migrate an Advisors Platform database, see instructions on the Migrating Databases to Advisors Release 8.5.2 page in the Genesys Performance Management Advisors Migration Guide.
|
platform-database-sql/oracle/
advisors-platform-<version>_INMEMORY.sql
advisors-platform-<version>_NO_INMEMORY.sql
advisors-platform-<version>_ObjectsCustom.sql
advisors-platform-<version>_ObjectsDefault.sql
advisors-platform-<version>_ObjectsPlus.sql
advisors-platform-<version>_Schema.sql
advisors-platform-<version>_TBS.sql
advisors-platform-<version>_User.sql
advisors-platform-migrateSchema_<from-versions>_<to-version>.sql
Readme-advisors-platform-migrate_<from-versions>_<to-version>.txt
Any additional files in the folder are not to be executed manually. They are called automatically within the sql*Plus script during runtime.
|
The creation scripts for the Platform database for Oracle.
- ..._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 alternate 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 alternate 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 alternate script that replaces, and has the same purpose as ...User.sql and ...ObjectsPlus.sql combined.
- ..._INMEMORY.sql
- You use this script if you run the Oracle 12C In-Memory option. For information about using this script, see Migrating Databases to Advisors Release 8.5.2 in the Genesys Performance Management Advisors Migration Guide.
- ..._NO_INMEMORY.sql
- You use this script to revert the changes to the metrics schema if you previously executed the ..._INMEMORY.sql script. For information about using this script, see Migrating Databases to Advisors Release 8.5.2 in the Genesys Performance Management Advisors Migration Guide.
- advisors-platform-migrateSchema_8.5.101(102)_8.5.202.09.sql
- The scripts to update an existing Oracle Platform database. The scripts are applicable to Advisors release 8.5.102 and to the release immediately preceding 8.5.102 (that is, release 8.5.101.21).
|
The distribution contains several folders:
- The files contained in the platform-database-sql\oracle folder are for deployment/migration with an Oracle database that has Java Virtual Machine JServer installed.
- The files contained in the platform-database-sql\oracle\oracleNoJServer are for deployment/migration with an Oracle database that does not have the Java Virtual Machine JServer installed.
- The CISCO folder contains a script that must be applied in installations with a CISCO data source, in addition to the regular deployment or migration script.
For additional details, see the following:
- Readme-advisors-platform-<version>.txt, if present. Otherwise, see the Release Notes.
- Readme-advisors-platform-migrate_8.5.101(102)_8.5.202.09.txt, if present. The ReadMe file is applicable to Advisors release 8.5.102 and to the release immediately preceding 8.5.102 (that is, release 8.5.101.21). Otherwise, see the Release Notes.
|
.../bulkconfig/independent/ccadvbulkload/
|
The CCAdv bulk configuration tool for deployments in which you have specified the independent configuration mode for CCAdv (and WA, if you deploy it).
|
To use the CCAdv bulk configuration tool, see instructions on the CCAdv Bulk Configuration – Independent Mode page in this Guide.
|
.../bulkconfig/independent/wa-bulkload/
|
The WA bulk configuration tool for deployments in which you have specified the independent configuration mode for CCAdv and WA.
|
To use the WA bulk configuration tool, see instructions on the WA Bulk Configuration – Independent Mode page in this Guide.
|
.../bulkconfig/integrated/ccadv-wa-bulkload/
|
The CCAdv/WA bulk configuration tool for deployments in which you have specified the integrated configuration mode for CCAdv and WA.
|
To use the CCAdv/WA bulk configuration tool, see instructions on the CCAdv/WA Bulk Configuration – Integrated Mode page in this Guide.
|
metric-graphing-database-sql/mssql-...
mg-new-database-<version>.sql
|
The creation script for the metric graphing database on MS SQL.
This script is located in the metric-graphing-database-sql directory.
The IP includes the following folders:
- mssql-standard (for installations that use MS SQL Standard Edition)
- mssql-enterprise (for installations that use MS SQL Enterprise Edition)
Ensure you use the files from the folder that corresponds to your edition of Microsoft SQL Server.
|
|
metric-graphing-database-sql/oracle-...
mg-<version>_INMEMORY.sql
mg-<version>_NO_INMEMORY.sql
mg-<version>_ObjectsCustom.sql
mg-<version>_ObjectsDefault.sql
mg-<version>_ObjectsPlus.sql
mg-<version>_Schema.sql
mg-<version>_TBS.sql
mg-<version>_User.sql
migrate_mg_<from-version>_<to-version>.sql
|
The creation scripts for the metric graphing database on Oracle.
The scripts are located in the metric-graphing-database-sql directory.
The IP includes 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)
Ensure you use the files from the folder that corresponds to your edition of Oracle.
- _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 alternate script that replaces, and has the same purpose as ...User.sql and ...ObjectsPlus.sql combined.
- ..._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 alternate 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 alternate 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.
- ..._INMEMORY.sql
- You use this script if you run the Oracle 12C In-Memory option. For information about using this script, see Migrating Databases to Advisors Release 8.5.2 in the Genesys Performance Management Advisors Migration Guide.
- ..._NO_INMEMORY.sql
- You use this script to revert the changes to the metrics schema if you previously executed the ..._INMEMORY.sql script. For information about using this script, see Migrating Databases to Advisors Release 8.5.2 in the Genesys Performance Management Advisors Migration Guide.
- migrate_mg_8.5.101.15_8.5.202.09.sql
- A metric graphing migration script applicable to any release between 8.5.101.15 and 8.5.102.
|
For additional details, see the Readme file, if present. Otherwise, see the Release Notes.
|