To deploy this release of Genesys Info Mart, do one of the following, depending on your current release:
- If you are currently using Genesys Info Mart 7.0.2, use the procedure described in "Migrating Genesys Info Mart from 7.0.2 to 7.6.x" in the Genesys 7 Migration Guide to upgrade to Genesys Info Mart 7.6.002.03.
- If you are currently using Genesys Info Mart 7.2, use the procedure described in "Migrating Genesys Info Mart from 7.2.x to 7.6.x" in the Genesys 7 Migration Guide to upgrade to Genesys Info Mart 7.6.002.03.
- If you are currently using Genesys Info Mart 7.5, use the procedure described in "Migrating Genesys Info Mart from 7.5.x to 7.6.x" in the Genesys 7 Migration Guide to upgrade to Genesys Info Mart 7.6.002.03.
- If this is a new installation of Genesys Info Mart, use the installation procedures in the Genesys Info Mart 7.6 Deployment Guide.
- To install this release of Genesys Info Mart over a prior 7.6 release, use this Deployment Procedure.
Note: Review all the steps before performing any of them.
Plan a time when you can complete the installation in one continuous session. Several steps can take significant time to complete, and this potentially affects the availability of Info Mart data.
Pre-Installation Steps
Set the run-scheduler configuration option to FALSE in the schedule section of the Genesys Info Mart Application object to temporarily stop Genesys Info Mart Server from launching ETL jobs.
Wait for any currently running jobs to finish. Use the Genesys Info Mart Administration Console to monitor the completion of the jobs.
Stop the Genesys Info Mart Server.
Create backup copies of both your Staging Area and Info Mart databases.
Create backup copies of the Genesys Info Mart deployment SQL scripts that you modified and ran when you last deployed Genesys Info Mart. These scripts perform the following tasks:
Create or modify the source Stat Server databases.
Create indexes in the source IDBs (Interaction Databases) to be used by Genesys Info Mart.
Create the target Staging Area and Info Mart databases.
Create the Info Mart database read-only views.
The new Genesys Info Mart installation program overwrites these SQL scripts, and does not preserve your modifications.
To locate these SQL scripts, navigate to the Genesys Info Mart installation directory, then navigate to its sql_scripts directory. The SQL scripts are in the RDBMS-specific subdirectories: db2, mssql, and oracle .
Make a note of the application startup arguments if you customized them. The installation process will overwrite these arguments and you will lose any changes you made.
If you are running Genesys Info Mart Server as a Windows service, you should have modified the startup arguments in the gim_etl_update_service_arguments.bat file. If you modified the gim_etl_update_service_arguments.bat file, back up a copy of your .bat file that is located in your gim-etl home folder.
If you are not running Genesys Info Mart Server as a Windows service, but rather use Genesys Solution Control Interface to start and stop Genesys Info Mart Server, note the command-line arguments on the Start Info tab of the Genesys Info Mart Application object in Configuration Manager.
If you are using the gim_etl_server.bat file to start Genesys Info Mart Server, back up a copy of your gim_etl_server.bat file that is located in your gim-etl home folder.
Installation Steps
Install the new Genesys Info Mart installation package:
On a Microsoft Windows operating system, uninstall the current Genesys Info Mart installation package using the Windows Control Panel > Add/Remove Programs . Then run setup to install the new Genesys Info Mart installation package.
On a UNIX operating system, run the new Genesys Info Mart installation script. When prompted, select the appropriate action to overwrite existing files (for example, Overwrite only the files contained in this package ).
Update the 7.6 application startup arguments if you previously customized them.
If you are running Genesys Info Mart Server as a Windows service, open the General tab of the Genesys Info Mart 7.6 Windows service Properties window. Copy the arguments for the 7.6 application from the Path to executable text box to the gim_etl_update_service_arguments.bat file located in your 7.6 gim-etl home folder. Update the arguments per the backup copy of the .bat file that you created in Pre-Installation Step 6 above, but preserve the path to the 7.6 executable. Once you update the 7.6 .bat file, execute it in order for the changes to take effect. Genesys recommends that you make the same changes to the Genesys Info Mart Application object in the Configuration Manager.
If you are using Genesys Solution Control Interface to start and stop Genesys Info Mart Server, modify the command-line arguments on the Start Info tab of the Genesys Info Mart Application object in Configuration Manager, as noted in Pre-Installation Step 6 above. Preserve the path to the 7.6 executable.
If you are using the gim_etl_server.bat file to start Genesys Info Mart Server, use the content of the backup gim_etl_server.bat file to update the command-line arguments in the 7.6 copy of the gim_etl_server.bat file that the installation placed into your gim-etl home folder. Preserve the path to the 7.6 executable.
If you are installing over release 7.6.001.07, examine the following SQL statements and issue them against each Interaction Concentrator IDB with Database Access Point role ICON_CORE if you have not previously done so
(ER# 206504724):
-
Click to show/hide SQL statements for Oracle
DROP INDEX GIM_IDX_ASRC_SEQ;
CREATE INDEX GIM_IDX_ASRC_SEQ on G_AGENT_STATE_RC (
GSYS_SEQ ASC,
CREATED_TS ASC
);
-
Click to show/hide SQL statements for Microsoft SQL Server
DROP INDEX G_AGENT_STATE_RC.GIM_IDX_ASRC_SEQ
go
CREATE INDEX GIM_IDX_ASRC_SEQ on G_AGENT_STATE_RC (
GSYS_SEQ ASC,
CREATED_TS ASC
)
go
-
Click to show/hide SQL statements for DB2
DROP INDEX GIM_IDX_ASRC_SEQ;
CREATE INDEX GIM_IDX_ASRC_SEQ on G_AGENT_STATE_RC (
GSYS_SEQ ASC,
CREATED_TS ASC
);
If you are installing over release 7.6.001.07, issue the following SQL statements against each Interaction Concentrator IDB with Database Access Point role ICON_CORE (ER# 207130586):
If you are installing over release 7.6.001.07, examine the following SQL statements and issue them against the Staging Area database if you have not previously done so (ER# 206504501):
-
Click to show/hide SQL statements for Oracle
CREATE INDEX IDX_IR1_DB on STG_IR_1 (
DBSOURCE_KEY,
IRID
);
CREATE INDEX IDX_IR2_DB on STG_IR_2 (
DBSOURCE_KEY,
IRID
);
DROP INDEX SE_PEND_LOGINSESS_IDX;
DROP INDEX SE_IDX_DB;
CREATE INDEX SE_IDX_DB on STG_GX_SESSION_ENDPOINT_PEND (
DBSOURCE_KEY,
LOGINSESSIONID,
ENDPOINTID,
QUEUEID
);
DROP INDEX AS_EVENTSEQ_PEND_IDX;
DROP INDEX AS_LOGINSESS_PEND_IDX;
DROP INDEX AS_EVENTSEQ_PEND_DB;
CREATE INDEX AS_EVENTSEQ_PEND_DB on STG_G_AGENT_STATE_HISTORY_PEND (
DBSOURCE_KEY,
LOGINSESSIONID,
EVENTSEQ,
ENDPOINTID,
QUEUEID,
TYPE
);
DROP INDEX AR_EVENTSEQ_PEND_IDX;
DROP INDEX AR_LOGINSESS_PEND_IDX;
DROP INDEX AR_EVENTSEQ_PEND_DB;
CREATE INDEX AR_EVENTSEQ_PEND_DB on STG_G_AGENT_STATE_RC_PEND (
DBSOURCE_KEY,
SESSIONID,
EVENTSEQ,
ENDPOINTID
);
DROP INDEX IDX_STG_G_LSESS_LSID_PEND;
DROP INDEX IDX_STG_G_LSESS_LSDB_PEND;
CREATE INDEX IDX_STG_G_LSESS_LSDB_PEND on STG_G_LOGIN_SESSION_PEND (
DBSOURCE_KEY,
LOGINSESSIONID
);
DROP INDEX EVENTSEQ_IDX_PEND;
DROP INDEX LOGINSESS_IDX_PEND;
DROP INDEX EVENTSEQ_DB_PEND;
CREATE INDEX EVENTSEQ_DB_PEND on STG_G_DND_HISTORY_PEND (
DBSOURCE_KEY,
LOGINSESSIONID,
EVENTSEQ
);
-
Click to show/hide SQL statements for Microsoft SQL Server
CREATE INDEX IDX_IR1_DB on STG_IR_1 (
DBSOURCE_KEY,
IRID
)
go
CREATE INDEX IDX_IR2_DB on STG_IR_2 (
DBSOURCE_KEY,
IRID
)
go
DROP INDEX STG_GX_SESSION_ENDPOINT_PEND.SE_PEND_LOGINSESS_IDX
go
DROP INDEX STG_GX_SESSION_ENDPOINT_PEND.SE_PEND_IDX_DB
go
CREATE INDEX SE_PEND_IDX_DB on STG_GX_SESSION_ENDPOINT_PEND (
DBSOURCE_KEY,
LOGINSESSIONID,
ENDPOINTID,
QUEUEID
)
go
DROP INDEX STG_G_AGENT_STATE_HISTORY_PEND.AS_EVENTSEQ_PEND_IDX
go
DROP INDEX STG_G_AGENT_STATE_HISTORY_PEND.AS_LOGINSESS_PEND_IDX
go
DROP INDEX STG_G_AGENT_STATE_HISTORY_PEND.AS_EVENTSEQ_PEND_DB
go
CREATE INDEX AS_EVENTSEQ_PEND_DB on STG_G_AGENT_STATE_HISTORY_PEND (
DBSOURCE_KEY,
LOGINSESSIONID,
EVENTSEQ,
ENDPOINTID,
QUEUEID,
TYPE
)
go
DROP INDEX STG_G_AGENT_STATE_RC_PEND.AR_EVENTSEQ_PEND_IDX
go
DROP INDEX STG_G_AGENT_STATE_RC_PEND.AR_LOGINSESS_PEND_IDX
go
DROP INDEX STG_G_AGENT_STATE_RC_PEND.AR_EVENTSEQ_PEND_DB
go
CREATE INDEX AR_EVENTSEQ_PEND_DB on STG_G_AGENT_STATE_RC_PEND (
DBSOURCE_KEY,
SESSIONID,
EVENTSEQ,
ENDPOINTID
)
go
DROP INDEX STG_G_LOGIN_SESSION_PEND.IDX_STG_G_LSESS_LSID_PEND
go
DROP INDEX STG_G_LOGIN_SESSION_PEND.IDX_STG_G_LSESS_LSDB_PEND
go
CREATE INDEX IDX_STG_G_LSESS_LSDB_PEND on STG_G_LOGIN_SESSION_PEND (
DBSOURCE_KEY,
LOGINSESSIONID
)
go
DROP INDEX STG_G_DND_HISTORY_PEND.EVENTSEQ_IDX_PEND
go
DROP INDEX STG_G_DND_HISTORY_PEND.LOGINSESS_IDX_PEND
go
DROP INDEX STG_G_DND_HISTORY_PEND.EVENTSEQ_DB_PEND
go
CREATE INDEX EVENTSEQ_DB_PEND on STG_G_DND_HISTORY_PEND (
DBSOURCE_KEY,
LOGINSESSIONID,
EVENTSEQ
)
go
-
Click to show/hide SQL statements for DB2
CREATE INDEX IDX_IR1_DB on STG_IR_1 (
DBSOURCE_KEY,
IRID
);
CREATE INDEX IDX_IR2_DB on STG_IR_2 (
DBSOURCE_KEY,
IRID
);
DROP INDEX SE_PNDLOGSES_IDX;
DROP INDEX SE_PEND_IDX_DB;
CREATE INDEX SE_PEND_IDX_DB on STG_GX_SESSION_ENDPOINT_PEND (
DBSOURCE_KEY,
LOGINSESSIONID,
ENDPOINTID,
QUEUEID
);
DROP INDEX GASPND_EVSEQ_IDX;
DROP INDEX GASPND_LOGIID_IDX;
DROP INDEX GASPND_DBKEY_IDX;
CREATE INDEX GASPND_DBKEY_IDX on STG_G_AGENT_STATE_HISTORY_PEND (
DBSOURCE_KEY,
LOGINSESSIONID,
EVENTSEQ,
ENDPOINTID,
QUEUEID,
TYPE
);
DROP INDEX ARPND_EVSEQ_IDX;
DROP INDEX ARPND_SESSID_IDX;
DROP INDEX ARPND_DBKEY_IDX;
CREATE INDEX ARPND_DBKEY_IDX on STG_G_AGENT_STATE_RC_PEND (
DBSOURCE_KEY,
SESSIONID,
EVENTSEQ,
ENDPOINTID
);
DROP INDEX IDX_PNDGLSESS_LID;
DROP INDEX IDX_PNDGLSESS_DB;
CREATE INDEX IDX_PNDGLSESS_DB on STG_G_LOGIN_SESSION_PEND (
DBSOURCE_KEY,
LOGINSESSIONID
);
DROP INDEX IDX_PNDGDND_EVS;
DROP INDEX IDX_PNDGDND_LID;
DROP INDEX IDX_PNDGDND_DB;
CREATE INDEX IDX_PNDGDND_DB on STG_G_DND_HISTORY_PEND (
DBSOURCE_KEY,
LOGINSESSIONID,
EVENTSEQ
);
If you are installing over release 7.6.001.07, issue the following SQL statements against the Staging Area database (ER# 207130586):
-
Click to show/hide SQL statements for Oracle
ALTER TABLE STG_EXTRACT_THROTTLE ADD (
UNFINISHED NUMBER(1)
);
UPDATE STG_SCHEMA_INFO SET SCHEMA_VERSION = '7.6.000.14';
COMMIT;
-
Click to show/hide SQL statements for Microsoft SQL Server
ALTER TABLE STG_EXTRACT_THROTTLE
ADD UNFINISHED NUMERIC(1) NULL
go
BEGIN TRANSACTION
go
UPDATE STG_SCHEMA_INFO SET SCHEMA_VERSION = '7.6.000.14'
go
COMMIT
go
-
Click to show/hide SQL statements for DB2
ALTER TABLE STG_EXTRACT_THROTTLE
ADD UNFINISHED NUMERIC(1);
UPDATE STG_SCHEMA_INFO SET SCHEMA_VERSION = '7.6.000.14';
COMMIT;
If you are installing over release 7.6.001.07, examine the following SQL statements and issue them against the Info Mart database if you have not previously done so (ER# 206620229):
If you are installing over release 7.6.001.07, examine the following SQL commands and issue them against the Info Mart database if you have not previously done so (ER# 206112053):
-
Click to show/hide SQL commands for Oracle
ALTER TABLE AG2_INB_V_QUEUE_ABN_DAY
DROP constraint PK_AG2_INB_V_QUEUE_ABN_DAY;
ALTER TABLE AG2_INB_V_QUEUE_ABN_HOUR
DROP constraint PK_AG2_INB_V_QUEUE_ABN_HOUR;
ALTER TABLE AG2_INB_V_QUEUE_ABN_MONTH
DROP constraint PK_AG2_INB_V_QUEUE_ABN_MONTH;
ALTER TABLE AG2_INB_V_QUEUE_ANS_DAY
DROP constraint PK_AG2_INB_V_QUEUE_ANS_DAY;
ALTER TABLE AG2_INB_V_QUEUE_ANS_HOUR
DROP constraint PK_AG2_INB_V_QUEUE_ANS_HOUR;
ALTER TABLE AG2_INB_V_QUEUE_ANS_MONTH
DROP constraint PK_AG2_INB_V_QUEUE_ANS_MONTH;
ALTER TABLE AG2_INB_V_QUEUE_ABN_DAY
ADD constraint PK_AG2_INB_V_QUEUE_ABN_DAY primary key
(STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
ALTER TABLE AG2_INB_V_QUEUE_ABN_HOUR
ADD constraint PK_AG2_INB_V_QUEUE_ABN_HOUR primary key
(STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
ALTER TABLE AG2_INB_V_QUEUE_ABN_MONTH
ADD constraint PK_AG2_INB_V_QUEUE_ABN_MONTH primary key
(STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
ALTER TABLE AG2_INB_V_QUEUE_ANS_DAY
ADD constraint PK_AG2_INB_V_QUEUE_ANS_DAY primary key
(STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
ALTER TABLE AG2_INB_V_QUEUE_ANS_HOUR
ADD constraint PK_AG2_INB_V_QUEUE_ANS_HOUR primary key
(STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
ALTER TABLE AG2_INB_V_QUEUE_ANS_MONTH
ADD constraint PK_AG2_INB_V_QUEUE_ANS_MONTH primary key
(STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
-
Click to show/hide SQL commands for Microsoft SQL Server
ALTER TABLE AG2_INB_V_QUEUE_ABN_DAY
DROP constraint PK_AG2_INB_V_QUEUE_ABN_DAY
go
ALTER TABLE AG2_INB_V_QUEUE_ABN_HOUR
DROP constraint PK_AG2_INB_V_QUEUE_ABN_HOUR
go
ALTER TABLE AG2_INB_V_QUEUE_ABN_MONTH
DROP constraint PK_AG2_INB_V_QUEUE_ABN_MONTH
go
ALTER TABLE AG2_INB_V_QUEUE_ANS_DAY
DROP constraint PK_AG2_INB_V_QUEUE_ANS_DAY
go
ALTER TABLE AG2_INB_V_QUEUE_ANS_HOUR
DROP constraint PK_AG2_INB_V_QUEUE_ANS_HOUR
go
ALTER TABLE AG2_INB_V_QUEUE_ANS_MONTH
DROP constraint PK_AG2_INB_V_QUEUE_ANS_MONTH
go
ALTER TABLE AG2_INB_V_QUEUE_ABN_DAY
ADD constraint PK_AG2_INB_V_QUEUE_ABN_DAY primary key
(STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
GROUP_COMBINATION_KEY,TIME_RANGE_KEY)
go
ALTER TABLE AG2_INB_V_QUEUE_ABN_HOUR
ADD constraint PK_AG2_INB_V_QUEUE_ABN_HOUR primary key
(STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
GROUP_COMBINATION_KEY,TIME_RANGE_KEY)
go
ALTER TABLE AG2_INB_V_QUEUE_ABN_MONTH
ADD constraint PK_AG2_INB_V_QUEUE_ABN_MONTH primary key
(STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
GROUP_COMBINATION_KEY,TIME_RANGE_KEY)
go
ALTER TABLE AG2_INB_V_QUEUE_ANS_DAY
ADD constraint PK_AG2_INB_V_QUEUE_ANS_DAY primary key
(STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
GROUP_COMBINATION_KEY,TIME_RANGE_KEY)
go
ALTER TABLE AG2_INB_V_QUEUE_ANS_HOUR
ADD constraint PK_AG2_INB_V_QUEUE_ANS_HOUR primary key
(STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
GROUP_COMBINATION_KEY,TIME_RANGE_KEY)
go
ALTER TABLE AG2_INB_V_QUEUE_ANS_MONTH
ADD constraint PK_AG2_INB_V_QUEUE_ANS_MONTH primary key
(STD_TENANT_DATE_TIME_KEY, TENANT_KEY, RESOURCE_KEY,
GROUP_COMBINATION_KEY,TIME_RANGE_KEY)
go
-
Click to show/hide SQL commands for DB2
ALTER TABLE AG2_INB_V_QUEUE_ABN_DAY
DROP constraint "P_Key_1";
ALTER TABLE AG2_INB_V_QUEUE_ABN_HOUR
DROP constraint "P_Key_1";
ALTER TABLE AG2_INB_V_QUEUE_ABN_MONTH
DROP constraint "P_Key_1";
ALTER TABLE AG2_INB_V_QUEUE_ANS_DAY
DROP constraint "P_Key_1";
ALTER TABLE AG2_INB_V_QUEUE_ANS_HOUR
DROP constraint "P_Key_1";
ALTER TABLE AG2_INB_V_QUEUE_ANS_MONTH
DROP constraint "P_Key_1";
ALTER TABLE AG2_INB_V_QUEUE_ABN_DAY
ADD constraint "P_Key_1" primary key (STD_TENANT_DATE_TIME_KEY,
TENANT_KEY, RESOURCE_KEY,
GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
ALTER TABLE AG2_INB_V_QUEUE_ABN_HOUR
ADD constraint "P_Key_1" primary key (STD_TENANT_DATE_TIME_KEY,
TENANT_KEY, RESOURCE_KEY,
GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
ALTER TABLE AG2_INB_V_QUEUE_ABN_MONTH
ADD constraint "P_Key_1" primary key (STD_TENANT_DATE_TIME_KEY,
TENANT_KEY, RESOURCE_KEY,
GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
ALTER TABLE AG2_INB_V_QUEUE_ANS_DAY
ADD constraint "P_Key_1" primary key (STD_TENANT_DATE_TIME_KEY,
TENANT_KEY, RESOURCE_KEY,
GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
ALTER TABLE AG2_INB_V_QUEUE_ANS_HOUR
ADD constraint "P_Key_1" primary key (STD_TENANT_DATE_TIME_KEY,
TENANT_KEY, RESOURCE_KEY,
GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
ALTER TABLE AG2_INB_V_QUEUE_ANS_MONTH
ADD constraint "P_Key_1" primary key (STD_TENANT_DATE_TIME_KEY,
TENANT_KEY, RESOURCE_KEY,
GROUP_COMBINATION_KEY,TIME_RANGE_KEY);
If you are installing over release 7.6.001.07, examine the following SQL statement and issue it against the Info Mart database if you have not previously done so (ER# 205563115):
If you are installing over release 7.6.001.07, examine the following SQL statements and issue them against the Info Mart database if you have not previously done so (ER# 204783401):
Restart the Genesys Info Mart Server.
-
Set the
run-scheduler configuration option to TRUE in the schedule section of the Genesys Info Mart Application object to resume the Genesys Info Mart Server schedule.
Top
of Page
|