>> Sierra HF01

Installation, Configuration, and Upgrade

The following sections provide information related to installation, configuration, and upgrade of the SummitAI application:

Important Notes About v4.1.4 Setup and Installation
Patch Update for .NET Framework
Security Best Practices for SummitAI Application Deployment
SummitAI Upgrade Steps
Installing PsExec Tool
Post Installation Steps
Oracle and IBM Client Configuration
Online Help Upgrade
BI Reports
Maximum File Size for Attachments

Important Notes About v4.1.4 Setup and Installation

Points to be Noted During v4.1.4 Installation

While installing the v4.1.4 Web setup on the SummitAI Server, ensure to install English OS and English supported DB only. Furthermore, the SummitAI Proxy Data Collector service needs to be installed on the English OS Server.
The Web URL created on English OS Server can be accessed through the Client Machines, which have another language OS, such as English, Chinese, Japanese, and so on. This enables the end users to use the Web URL created in the English OS Server and access SummitAI Suite applications for inputting data in different languages.
The SUMMIT Proxy can be installed on the Client Servers, which has other language OS, such as English, Chinese, Japanese, and so on.

Double-Byte Character Support for SummitAI IT Management Suite

To enable multi-language support for SummitAI IT Management Suite, a basic support for double-byte characters is activated. Now, the application accepts the inputs in any of the language it is typed in and stores it in the same language in the database tables. Whenever required, the data is retrieved and displayed in the respective languages on the GUI.

In the v4.1.4 release, the SummitAI application Graphical User Interface (GUI) is displayed in English. However, the end users can enter the input data or text in any of the languages, such as English, Chinese, Japanese, and so on in the text editable fields.

Note:

In v4.1.4 release, entering text in the E-mail Address and Password fields are supported only in English language. Hence, it is highly recommended to enter the data in the E-mail Address and Password fields on any of the pages for the application in English language only. While logging into the application or configuring the user details, or in any other pages within the application, wherever there is a need to enter the e-mail address and password details, ensure to enter the text in English language. If you enter the details in any other language, the Application throws an error.

Patch Update for .NET Framework

For .NET Framework 3.5 software, Microsoft has released a patch. It is recommended to apply the .NET Framework 3.5 Service Pack 1 (MS KB 958481, 958483, 958484 patches) after the successful installation of v4.1.4 SummitAI IT Management Suite setup on the SummitAI Server. This helps to avoid occurring of unforeseen errors in the application. You can download the patch from the http://support.microsoft.com/kb/959209 link.

Note:

After the successful deployment of the patches mentioned above, please restart the IIS on SummitAI Server.

SummitAI Upgrade Steps

To upgrade the database of the SummitAI Suite from the prior version v4.1.4 hotfix to Sierra, do the following:

Assumptions
Pre Upgrade Steps
Database Upgrade from v4.1.4 Hotfix To v5.1 SP7
Database Upgrade from v5.1 SP7 To v5.3
Database Upgrade from v5.3 To v5.4
Database Upgrade from v5.4 To v5.4 SP1
Database Upgrade from v5.4 SP1 to v5.4 SP2
Database Upgrade from v5.4 SP2 to v5.5
Database Upgrade from v5.5 to v5.5 SP1
Database Upgrade from v5.5 SP1 to v5.5 SP2
Database Upgrade from v5.5 SP2 to v5.6
Database Upgrade from v5.6 to v5.6 SP1
Database Upgrade from v5.6 SP1 to v5.7
Database Upgrade from v5.7 to v5.7 HF01
Database Upgrade from v5.7 HF01 to v5.7 SP1
Database Upgrade from v5.7 SP1 to v5.7 SP2
Database Upgrade from v5.7 SP2 to v5.7 SP3
Database Upgrade from v5.7 SP3 to v5.7 SP5
Database Upgrade from v5.7 SP5 to Alps
Database Upgrade from ALPS to ALPS HF01
Database Upgrade from ALPS HF01 to ALPS SP1
Database Upgrade from Alps SP1 to Sierra
Database Upgrade in BI Report and Global Search

Assumptions

Before executing the database upgrade scripts, it is assumed that you have successfully installed the SummitAI Suite base version 4.1.4 hotfix or above.

Pre Upgrade Steps

Before you start with the database upgrade of SummitAI, we recommend that you perform the following:

On the SummitAI Database Server, open the Microsoft SQL Server Management Studio tool. Connect to the SummitAI database Instance. Take the backup of the complete SummitAI database.
On the SummitAI Server, ensure that you take a backup of the folders where the attachment files are saved. In general, the attachment files are saved in the application root directory.

Application Root Directory: \\SummitWeb\<databasename>-ModuleCode-Attachments.

Example of the Attachment Files folder name is ‘summitDB-im-attachments’, where summitDB is the database name, im is the module code for Incident Management and attachments is the folder name.

Database Upgrade from v4.1.4 Hotfix To v5.1 SP7

To perform the database upgrade from v4.1.4 hotfix to v5.1 SP7, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
v4.1.4 HF	1.Summitupgrade_v4.1.4HF to v5.1dbscripts[Migration_back] 2.Summitupgrade_v4.1.4HF_B003_20140715 to v5.1_dbscripts[TableSchema] 3.Summitupgrade_v4.1.4HF_B003_20140715 to v5.1_dbscripts[ViewSchema] 4.Summitupgrade_v4.1.4HF_B003_20140715 to v5.1_dbscripts[FunctionSchema] 5.Summitupgrade_v4.1.4HF_B003_20140715 to v5.1_dbscripts[SPSchema] 6.Summitupgrade_v4.1.4HF_dbscripts[PostDeployment] 7.Summitupgrade_v5.1_dbscripts[PostDeployment] 8.Summitupgrade_v5.1_dbscripts[Roletemplate_Migration] 9.Summitupgrade_v5.1_dbscripts[InstanceMigration] 10.Summitupgrade_v5.1_dbscripts[License]	v5.1
v5.1	11.Summitupgrade_v5.1_HF01_24March_to_v5.1_STC_16June_dbscripts 12.Summitupgrade_v5.1_STC_16June_to_v5.1_HF02_01August 13.Summitupgrade_v5.1_HF02_B008_01Aug_to_v5.1_HF03_B015_08Dec 14.Summitupgrade_v5.1_HF03_B015 to v5.1HF02_27OCT 15.Summitupgrade_v5.1HF02_27OCT_to_v5.1SP1_11Dec	v5.1 SP1
v5.1 SP1	16.Summitupgrade_v5.1SP1_11Dec_to_v5.1SP2_B002_16Feb2016.sql 17.Summitupgrade_v5.1_dbscripts[Data_Migration_Modulewise]	v5.1 SP2
v5.1SP2	18.Summitupgrade_v5.1SP2_B002_17Feb2016_to_v5.1SP4_B006_04May2016	v5.1SP4
v5.1SP4	19.Summitupgrade_v5.1SP5_B001_04May2016_to_v5.1SP7_B003_04July	v5.1 SP7

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\Summitv5.1\UpgradeScripts\

Database Upgrade from v5.1 SP7 To v5.3

To perform the database upgrade from v5.1 SP7 to v5.3, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
v5.1SP7	20.Summitupgrade_v5.1SP7_B003_04July2016_to_v5.3_09thAugust2016	v5.3

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\Summitv5.3UpgradeScripts\

Note:

Execute the scripts (folder name: v5.3-AD_Related_Changes_SP) only if any AD-related changes are fixed between v5.1 to v5.3 and v5.3 to v5.4 upgrade.

Database Upgrade from v5.3 To v5.4

To perform the database upgrade from v5.3 to v5.4, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
v5.3	21.Summitupgrade_v5.3_9thAug2016_to_v5.4_06thJan2017	v5.4
v5.3 to v5.4 License migration related scripts	22.SummitMigrationScripts-for-v5.3tov5.4_License InsertInCustomerInfo.sql UpdateLicense.sql lm_ANALYSTMAPPING.sql Note: Read the SUMMIT License Admin Guide and pass the parameter before upgrading the scripts.	License upgrade

Schema Version

Upgrade Script

Upgraded Schema Version

v5.3

21.Summitupgrade_v5.3_9thAug2016_to_v5.4_06thJan2017

v5.4

v5.3 to v5.4 License migration related scripts

22.SummitMigrationScripts-for-v5.3tov5.4_License

InsertInCustomerInfo.sql

UpdateLicense.sql

lm_ANALYSTMAPPING.sql

Note: Read the SUMMIT License Admin Guide and pass the parameter before upgrading the scripts.

License upgrade

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\Summitv5.4UpgradeScripts\

Database Upgrade from v5.4 To v5.4 SP1

To perform the database upgrade from v54 to v54 SP1, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
v5.4	23.Summitupgrade_v5.4_06thJan2017_to_v5.4SP1_B006_14thFeb2017 Note: The upgrade step for v5.4HF01 is merged with this script.	v5.4SP1

Schema Version

Upgrade Script

Upgraded Schema Version

v5.4

23.Summitupgrade_v5.4_06thJan2017_to_v5.4SP1_B006_14thFeb2017

Note: The upgrade step for v5.4HF01 is merged with this script.

v5.4SP1

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\Summitv5.4SP1UpgradeScripts\

Database Upgrade from v5.4 SP1 to v5.4 SP2

To perform the database upgrade from v54 SP1 to v54 SP2, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
v5.4SP1	24.Summitupgrade_v5.4SP1_B006_14Feb2017_to_v5.4SP2_B009_27March2017 Note: The upgrade steps for v5.4SP1HF01 to v5.4SP1HF03 are merged with this script.	v5.4SP2

Schema Version

Upgrade Script

Upgraded Schema Version

v5.4SP1

24.Summitupgrade_v5.4SP1_B006_14Feb2017_to_v5.4SP2_B009_27March2017

Note: The upgrade steps for v5.4SP1HF01 to v5.4SP1HF03 are merged with this script.

v5.4SP2

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\Summitv5.4SP2UpgradeScripts\

Database Upgrade from v5.4 SP2 to v5.5

To perform the database upgrade from v54 SP2 to v5.5, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
v5.4SP2	25.Summitupgrade_v5.4SP2_B009_27March2017_to_v5.5_9thJune2017.	v5.5

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\Summitv5.5UpgradeScripts\

Database Upgrade from v5.5 to v5.5 SP1

To perform the database upgrade from v5.5 to v5.5 SP1, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
v5.5	26.Summitupgrade_v5.5_09June2017_to_v5.5SP1_23rdAug2017.sql Note: The upgrade steps for v5.5HF01 and HF02 are merged with this script.	v5.5 SP1

Schema Version

Upgrade Script

Upgraded Schema Version

v5.5

26.Summitupgrade_v5.5_09June2017_to_v5.5SP1_23rdAug2017.sql

Note: The upgrade steps for v5.5HF01 and HF02 are merged with this script.

v5.5 SP1

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\Summitv5.5SP1UpgradeScripts\

Database Upgrade from v5.5 SP1 to v5.5 SP2

To perform the database upgrade from v5.5 SP1 to v5.5 SP2, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
v5.5 SP1	27.Summitupgrade_v5.5SP1_23rdAug2017_to_v5.5SP2_2ndNov2017.sql Note: The upgrade step for v5.5SP1_ B005 is merged with this script.	v5.5 SP2

Schema Version

Upgrade Script

Upgraded Schema Version

v5.5 SP1

27.Summitupgrade_v5.5SP1_23rdAug2017_to_v5.5SP2_2ndNov2017.sql

Note: The upgrade step for v5.5SP1_ B005 is merged with this script.

v5.5 SP2

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\Summitv5.5SP2UpgradeScripts\

Database Upgrade from v5.5 SP2 to v5.6

To perform the database upgrade from v5.5 SP2 to v5.6, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
v5.5 SP2	28.Summitupgrade_v5.5SP2_2ndNov2017_to_v5.6_5thFeb2018.sql Note: The upgrade steps for v5.5SP2HF01 to HF03 are merged with this script.	v5.6

Schema Version

Upgrade Script

Upgraded Schema Version

v5.5 SP2

28.Summitupgrade_v5.5SP2_2ndNov2017_to_v5.6_5thFeb2018.sql

Note: The upgrade steps for v5.5SP2HF01 to HF03 are merged with this script.

v5.6

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\Summitv5.6UpgradeScripts\

Database Upgrade from v5.6 to v5.6 SP1

To perform the database upgrade from v5.6 to v5.6 SP1, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
v5.6	29.Summitupgrade_v5.6_05Feb2018_to_v5.6SP1_B003_20thFeb2018.sql Note: The upgrade step for v5.6HF01 is merged with this script.	v5.6 SP1

Schema Version

Upgrade Script

Upgraded Schema Version

v5.6

29.Summitupgrade_v5.6_05Feb2018_to_v5.6SP1_B003_20thFeb2018.sql

Note: The upgrade step for v5.6HF01 is merged with this script.

v5.6 SP1

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\Summitv5.6SP1UpgradeScripts\

Database Upgrade from v5.6 SP1 to v5.7

To perform the database upgrade from v5.6 SP1 to v5.7, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
v5.6 SP1	30.Summitupgrade_v5.6SP1_B003_20thFeb2018_to_v5.7_ 25thMay2018.sql Note: The upgrade steps for V5.6SP1 HF01 to V5.6SP1 HF03 and V5.6SP2 to V5.6SP2 HF02 are merged with this script.	v5.7

Schema Version

Upgrade Script

Upgraded Schema Version

v5.6 SP1

30.Summitupgrade_v5.6SP1_B003_20thFeb2018_to_v5.7_ 25thMay2018.sql

Note: The upgrade steps for V5.6SP1 HF01 to V5.6SP1 HF03 and V5.6SP2 to V5.6SP2 HF02 are merged with this script.

v5.7

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\Summitv5.7UpgradeScripts\

Database Upgrade from v5.7 to v5.7 HF01

To perform the database upgrade from v5.7 to v5.7 HF01, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
V5.7	31.Summitupgrade_v5.7_25thMay2018_to_v5.7HF01_B005_22^ndJune2018.sql.	v5.7 HF01

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\Summitv5.7 SP1UpgradeScripts\

Database Upgrade from v5.7 HF01 to v5.7 SP1

To perform the database upgrade from v5.7 HF01 to v5.7 SP1, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
V5.7 HF01	32.Summitupgrade_v5.7HF01_B005_22^ndJune2018.sql_to_v5.7SP1_B007_04thAugust2018.sql.	v5.7 SP1

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\Summitv5.7 SP1UpgradeScripts\

Database Upgrade from v5.7 SP1 to v5.7 SP2

To perform the database upgrade from v5.7 SP1 to v5.7 SP2, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
V5.7 SP1	33.Summitupgrade_v5.7SP1_B007_04thAug2018_to_v5.7SP2_B008_21stSep2018 Notes: The following versions are merged in v5.7 SP2: - v5.7 SP1 HF01 - v5.7 SP1 HF02 - V5.6SP2HF07 - V5.6SP2HF08 - V5.5SP2HF10 - V5.5SP2HF11 While altering the column type or length which is a part of full text search indexes, the DB script error is occurred. To resolve this issue, the user needs to follow the below steps: - Identify the full text index and take the backup - Drop the backup full text indexes - Alter the column type or length columns - Create the full text index (execute the full text index backup taken at the first step). While altering the table type columns, the DB script error is occurred. To resolve this issue, the user needs to follow the below steps: - Identify the procedures and take the backup - Drop the backup procedures - Alter the table type columns Create the procedure (execute the procedure backup taken at the first step). While updating the Scripts from the previous versions to v5.7 SP2, the DB script error “The index 'IX_Common_Master_X_X' is dependent on Column 'CM_Value” is occurred. To resolve this issue, user needs to follow the below steps: - Identify the index and take the backup - Drop the index - Alter the column - Create the index (execute the index backup taken at the first step) Example of error observed in v5.7 SP2: The index 'IX_User_Master_127892' is dependent on column 'EmpID'. This issue is observed in user master of the v5.7 SP2. It is recommended to follow the above steps if the same error occurs for any other table.	v5.7 SP2

Schema Version

Upgrade Script

Upgraded Schema Version

V5.7 SP1

33.Summitupgrade_v5.7SP1_B007_04thAug2018_to_v5.7SP2_B008_21stSep2018

Notes:

The following versions are merged in v5.7 SP2:

- v5.7 SP1 HF01

- v5.7 SP1 HF02

- V5.6SP2HF07

- V5.6SP2HF08

- V5.5SP2HF10

- V5.5SP2HF11

While altering the column type or length which is a part of full text search indexes, the DB script error is occurred. To resolve this issue, the user needs to follow the below steps:

- Identify the full text index and take the backup

- Drop the backup full text indexes

- Alter the column type or length columns

- Create the full text index (execute the full text index backup taken at the first step).

While altering the table type columns, the DB script error is occurred. To resolve this issue, the user needs to follow the below steps:

- Identify the procedures and take the backup

- Drop the backup procedures

- Alter the table type columns

Create the procedure (execute the procedure backup taken at the first step).
While updating the Scripts from the previous versions to v5.7 SP2, the DB script error “The index 'IX_Common_Master_X_X' is dependent on Column 'CM_Value” is occurred. To resolve this issue, user needs to follow the below steps:

- Identify the index and take the backup

- Drop the index

- Alter the column

- Create the index (execute the index backup taken at the first step)

Example of error observed in v5.7 SP2: The index 'IX_User_Master_127892' is dependent on column 'EmpID'.

This issue is observed in user master of the v5.7 SP2. It is recommended to follow the above steps if the same error occurs for any other table.

v5.7 SP2

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\Summitv5.7 SP2UpgradeScripts\

Database Upgrade from v5.7 SP2 to v5.7 SP3

To perform the database upgrade from v5.7 SP2 to v5.7 SP3, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
V5.7 SP2	34.Summitupgrade_v5.7SP2_B008_21stSep2018_to_v5.7SP3_B007_05Dec2018 Notes: The following versions are merged in v5.7 SP3: - v5.6 SP2 HF10 While altering the column type or length which is a part of full text search indexes, the DB script error is occurred. To resolve this issue, the user needs to follow the below steps: - Identify the full text index and take the backup - Drop the backup full text indexes - Alter the column type or length columns - Create the full text index (execute the full text index backup taken at the first step). While altering the table type columns, the DB script error is occurred. To resolve this issue, the user needs to follow the below steps: - Identify the procedures and take the backup - Drop the backup procedures - Alter the table type columns - Create the procedure (execute the procedure backup taken at the first step). This issue is observed in user master of the v5.7 SP3. It is recommended to follow the above steps if the same error occurs for any other table.	v5.7 SP3

Schema Version

Upgrade Script

Upgraded Schema Version

V5.7 SP2

34.Summitupgrade_v5.7SP2_B008_21stSep2018_to_v5.7SP3_B007_05Dec2018

Notes:

The following versions are merged in v5.7 SP3:

- v5.6 SP2 HF10

While altering the column type or length which is a part of full text search indexes, the DB script error is occurred. To resolve this issue, the user needs to follow the below steps:

- Identify the full text index and take the backup

- Drop the backup full text indexes

- Alter the column type or length columns

- Create the full text index (execute the full text index backup taken at the first step).

While altering the table type columns, the DB script error is occurred. To resolve this issue, the user needs to follow the below steps:

- Identify the procedures and take the backup

- Drop the backup procedures

- Alter the table type columns

- Create the procedure (execute the procedure backup taken at the first step).

This issue is observed in user master of the v5.7 SP3. It is recommended to follow the above steps if the same error occurs for any other table.

v5.7 SP3

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\Summitv5.7 SP3UpgradeScripts\

Database Upgrade from v5.7 SP3 to v5.7 SP5

To perform the database upgrade from v5.7 SP3 to v5.7 SP5, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
V5.7 SP3	35.Summitupgrade_v5.7SP3_B007_05Dec2018_to_v5.7SP5_B005_2^ndJanuary2019.sql. Note: The upgrade steps of v5.7 SP4 are merged with this script.	v5.7 SP5

Schema Version

Upgrade Script

Upgraded Schema Version

V5.7 SP3

35.Summitupgrade_v5.7SP3_B007_05Dec2018_to_v5.7SP5_B005_2^ndJanuary2019.sql.

Note: The upgrade steps of v5.7 SP4 are merged with this script.

v5.7 SP5

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\Summitv5.7 SP5UpgradeScripts\

Database Upgrade from v5.7 SP5 to Alps

To perform the database upgrade from v5.7 SP5 to Alps, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
V5.7 SP5	36.Summitupgrade_v5.7SP5_B005_2^ndJanuary2019_to_Alps_B016_31^stMarch2019.sql Note: The upgrade steps of v5.7 SP5 HF01 and v5.7 SP6 are merged with this script. The above upgrade step is applicable only for the SummitAI application instances that are not enabled for GDPR. These steps are already available in the migration tool for the SummitAI application instances, which are enabled for GDPR.	Alps

Schema Version

Upgrade Script

Upgraded Schema Version

V5.7 SP5

36.Summitupgrade_v5.7SP5_B005_2^ndJanuary2019_to_Alps_B016_31^stMarch2019.sql

Note:

The upgrade steps of v5.7 SP5 HF01 and v5.7 SP6 are merged with this script.
The above upgrade step is applicable only for the SummitAI application instances that are not enabled for GDPR. These steps are already available in the migration tool for the SummitAI application instances, which are enabled for GDPR.

Alps

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\SummitAIALPSUpgradeScripts\

Database Upgrade from ALPS to ALPS HF01

To perform the database upgrade from Alps to Alps HF01, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
Alps	37.Summitupgrade_ALPS_01Apr2019_to_ALPS_HF01_B006_6thMay2019	Alps HF01

Schema Version

Upgrade Script

Upgraded Schema Version

Alps

37.Summitupgrade_ALPS_01Apr2019_to_ALPS_HF01_B006_6thMay2019

Alps HF01

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\SummitvALPSUpgradeScripts\

Database Upgrade from ALPS HF01 to ALPS SP1

To perform the database upgrade from Alps HF01 to Alps SP1, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
Alps HF01	38.Summitupgrade_ALPS_HF01_B006_6thMay2019_to_ALPS_SP1_B006_3rdJune2019	Alps SP1

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\SummitvALPSUpgradeScripts\

Database Upgrade from Alps SP1 to Sierra

To perform the database upgrade from Alps SP1 to Sierra, do the following:

Schema Version

Upgrade Script

Upgraded Schema Version

Alps Sp1

39.Summitupgrade_ALPS_SP1_B006_3^rdJune2019_to_Sierra_21^stAugust2019.sql

Note:

The upgrade steps of ALPS SP1 HF01 B004 is merged with this script.
The above upgrade step is applicable only for the SummitAI application instances that are not enabled for GDPR. These steps are already available in the migration tool for the SummitAI application instances, which are enabled for GDPR.

Sierra

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\SummitAISIERRAUpgradeScripts\

Database Upgrade in BI Report and Global Search

To perform the database upgrade in BI Report and Global Search script, do the following:

Schema Version	Upgrade Script	Upgraded Schema Version
BI-Report and Global Search	40.SummitMigrationscripts_enable_BIReport_GlobalSearch DN_Scripts-ONLY_FOR_NEW_IMPLE_NotUpgrade Note: The DN_Scripts.sql is only executed for new implementation not for upgrade. 2. Upgrade_Scripts_Till_v57SP5 Execute the script from 5.3x till 5.7 SP5 Note: Drop the dependent index completely if there is an error while dropping the column. While altering the column type or length, take the backup of dependent index and drop. After executing the alter command, recreate the index. 3. Upgrade_scripts_v57SP5_to_ALPS SP1 HF01 Post 5.7 SP5, run this script. Note: Drop the dependent index completely if there is an error while dropping the column. While altering the column type or length, take the backup of dependent index and drop. After executing the alter command, recreate the index. 4. Upgrade_scripts_ALPS SP1 HF01_to_SIERRA Post ALPS SP1 HF01, you can run this script. Notes: Drop the dependent index completely if there is an error while dropping the column. While altering the column type or length, take the backup of dependent index and drop. After executing the alter command, recreate the index 5. DB_Server_Configuration_LoadData Follow mentioned steps, in case, change in DN configuration: 6. Views.sql 7. PostScripts.sql Note: To enable the BI Configuration, follow the steps given in DeNormalization Process Steps document. Denormalization: If the SR_RPT_DN_ServcieTicketMaster contains around 1.5 lacks records, the post-deployment script runs approximately 3 minutes to update old records for [Resolved Updated By ] columns. Based on the volume of the records and index, the actual execution time may vary. SummitAI Global Search (Mandatory) Global Search_Configuration_Linked Server Environment.docx SummitSearch_FullTextEnabledTable_Script_LinkedServer.sql Enable outbound transaction for Linked Server.docx BI Report-Emails & Scheduling (Pushreport).docx Note: The scripts written in the Global Search_Configuration_Linked Server Environment document are for the reference purpose only. Ensure that you execute SummitSearch_FullTextEnabledTable_Script_LinkedServer.sql. To enable the Summit global search, follow the steps given in Global Search_Configuration_Linked Server Environment document. To access BI report related pages, the user need to update the SummitAI license. For more details, see Enhancement on ROLE TEMPLATE feature in v5.5 SP1 B005 RN. WithGDPR_Enablescripts 01. DN_Enable_GDPRChanges.sql Run this script in case GDPR is enabled for the client Enable BI Reports (Sierra) 01. Execute EnableBI_Reports_SIERRA script Note: For installing BI Reports (Sierra), please contact SummitAI Support and Implementation team.

Schema Version

Upgrade Script

Upgraded Schema Version

BI-Report and Global Search

40.SummitMigrationscripts_enable_BIReport_GlobalSearch

DN_Scripts-ONLY_FOR_NEW_IMPLE_NotUpgrade

Note: The DN_Scripts.sql is only executed for new implementation not for upgrade.

2. Upgrade_Scripts_Till_v57SP5

Execute the script from 5.3x till 5.7 SP5

Note:

- Drop the dependent index completely if there is an error while dropping the column.
- While altering the column type or length, take the backup of dependent index and drop. After executing the alter command, recreate the index.

3. Upgrade_scripts_v57SP5_to_ALPS SP1 HF01

Post 5.7 SP5, run this script.

Note:

- Drop the dependent index completely if there is an error while dropping the column.
- While altering the column type or length, take the backup of dependent index and drop. After executing the alter command, recreate the index.

4. Upgrade_scripts_ALPS SP1 HF01_to_SIERRA

Post ALPS SP1 HF01, you can run this script.

Notes:

Drop the dependent index completely if there is an error while dropping the column.
While altering the column type or length, take the backup of dependent index and drop. After executing the alter command, recreate the index

5. DB_Server_Configuration_LoadData

Follow mentioned steps, in case, change in DN configuration:

6. Views.sql

7. PostScripts.sql

Note:

- To enable the BI Configuration, follow the steps given in DeNormalization Process Steps document.
- Denormalization: If the SR_RPT_DN_ServcieTicketMaster contains around 1.5 lacks records, the post-deployment script runs approximately 3 minutes to update old records for [Resolved Updated By ****] columns. Based on the volume of the records and index, the actual execution time may vary.

SummitAI Global Search (Mandatory)

Global Search_Configuration_Linked Server Environment.docx
SummitSearch_FullTextEnabledTable_Script_LinkedServer.sql
Enable outbound transaction for Linked Server.docx
BI Report-Emails & Scheduling (Pushreport).docx

Note:

The scripts written in the Global Search_Configuration_Linked Server Environment document are for the reference purpose only. Ensure that you execute SummitSearch_FullTextEnabledTable_Script_LinkedServer.sql.
To enable the Summit global search, follow the steps given in Global Search_Configuration_Linked Server Environment document.
To access BI report related pages, the user need to update the SummitAI license. For more details, see Enhancement on ROLE TEMPLATE feature in v5.5 SP1 B005 RN.

WithGDPR_Enablescripts

01. DN_Enable_GDPRChanges.sql

Run this script in case GDPR is enabled for the client

Enable BI Reports (Sierra)

01. Execute EnableBI_Reports_SIERRA script

Note: For installing BI Reports (Sierra), please contact SummitAI Support and Implementation team.

All the upgrade script files are available along with SummitAI installer files.

Upgrade Folder Path: <Summit installer CD>\Summit<version no>\UpgradeScripts\

Example: ..\\Summitv5.4UpgradeScripts\

Installing PsExec Tool

SummitAI uses Microsoft PsExec tool to perform the following activities:

SummitAI IT Operations Management: MS Exchange Monitoring
Asset Management: Remote Software Delivery
Incident Management: Service Assist

Ensure to install the PsExec tool on the SummitAI Server, if it does not already exist.

Download link: http://technet.microsoft.com/en-us/sysinternals/bb897553

Place the downloaded psexec.exe file under the following SummitAI installer folder:

..\\Bin\TOOLS\PS\psexec.exe

Example: c:\Inetpub\wwwroot\SummitWeb\Bin\TOOLS\PS\psexec.exe

Post Installation Steps

Post installation of the SummitAI application setup, Izenda API Physical Path manually configured to the proper path. Physical Path: <Installation Directory>\API\Izenda7\

Note:

The APIs for the various modules, Incident, IT Operations, Asset, and BI Reports (Sierra) are part of the SummitAI Application setup.

Oracle and IBM Client Configuration

The Oracle and IBM client configurations are done to monitor the Oracle and IBM databases, respectively.

Oracle Client Configuration

To configure Oracle client, perform the following:

Open the URL http://www.oracle.com/technetwork/database/windows/downloads/utilsoft-087491.html. Alternatively, you can open the URL http://symphonysummit.blob.core.windows.net/customer-build/ODAC1120320Xcopy_32bit.zip.
Download the ODAC component ODAC1120320Xcopy_32bit.zip.
Extract the .zip folder to the <<drive>>:\extracted folder.
Run the command, cd “C:\ SummitAI \ODAC1120320Xcopy_32bit”, to change directory to the extracted folder, cd <<drive>>:\extracted folder.
Run the command, install.bat odp.net20 c:\oracle\11.2\odac odac11, to install Oracle Data Access Components.
Add the following paths of the installed ODAC components in the Environment Variables of the system:

- C:\oracle\11.2\odac
- C:\oracle\11.2\odac\bin
To add these paths in the Environment Variables, perform the following:
1. Click Start, right-click Computer, and then click Properties.
2. On the left side of the Control Panel, click Advanced system settings. The System Properties pop-up page is displayed.
3. On the System Properties pop-up page, click the Environment Variables button under the Advanced tab. The Environment Variables pop-up page is displayed.
4. On the Environment Variables pop-up page, in the System variable section, double-click the variable, Path, to edit it.
5. On the Edit System Variable pop-up page, in the Variable value field, add the text, C:\oracle\11.2\odac;C:\oracle\11.2\odac\bin, at the beginning of the existing text, and then click OK.
6. Restart your system.

IBM Client Configuration

To configure the IBM client, perform the following steps:

Open the URL http://www-01.ibm.com/support/docview.wss?rs=4020&uid=swg21385217. Alternatively, you can open the URL https://symphonysummit.blob.core.windows.net/prerequisites/ibm_data_server_client_winx64_v11.1.zip.
On the following page, click IBM Data Server Client.
In the IBM Data Server Client section, select IBM Data Server Client (Windows AMD64 and Intel EM64T) option, and then click Continue.
Fill in the required details, and then click I confirm.
The .exe file is downloaded. You can install the file to connect to the IBM Database Server.

Online Help Upgrade

While upgrading from earlier version of SUMMIT to v5.7 SP1 HF01, perform the following steps for Online Help configuration:

Delete the existing Online Help folder (~/Webfiles/OnlineHelp) and add new Online Help folder from 5.7 SP1 HF01 upgrade files.

BI Reports

While upgrading from earlier version of SummitAI to v5.7 SP1 HF01, perform the following steps for BI report configuration:

Add the below tag in web.config file and remove the Izenda.config file from (~/Webfiles/) <add key="Izenda:LicenseKey" value="T370 Symphony Summit +DASH +MAPS +LANG +FORMS +VISION+FUSION|Enterprise|6.8|09/30/2016|0|0|0|M|YG6YSZE"/>

Delete the existing Reporting folder(~/Webfiles/Reporting) and add new Reporting folder from 5.7 SP1 HF01 upgrade files
Update the SMTP configuration details in web.config instead of izenda.config

Maximum File Size for Attachments

The default maximum file attachment size is 4 MB. This value can be configured using the following keys in the web.config file:

However, it is recommended to keep the maximum file size limit to 8 MB for best system performance.

Reference Documents

SummitAI IT Management Suite document library comprises the following list of documents:

For all other documents, please contact the SummitAI Support Team.

Support

If you need any technical assistance from the SummitAI Support Team, contact at https://support.symphonysummit.com/ or send an e-mail to summitsupport@symphonysummit.com

Browser not supported