Installation, Configuration, and Upgrade Tahoe SP4 HF12
Previous Versions: << Sierra << Sierra HF01 << Sierra SP1 << Sierra SP1 HF01 << Sierra SP1 HF02 << Sierra SP1 HF03 << Denali << Denali HF01 << Denali HF02 << Denali HF03 << Denali SP1 << Denali SP1 HF01 << Tahoe << Tahoe SP1 << Tahoe SP3 HF01 << Tahoe SP3 HF01 V1 << Tahoe SP3 HF02<< Tahoe SP3 HF03 << Tahoe SP4 << Tahoe SP4 HF01 << Tahoe SP4 HF02 << Tahoe SP4 HF03 << Tahoe SP4 HF04 << Tahoe SP4 HF05 << Tahoe SP4 HF06 << Tahoe SP4 HF07 << Tahoe SP4 HF08 << Tahoe SP4 HF09 << Tahoe SP3 HF10 << Tahoe SP4 HF11
On this page:
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 Denali SP1, do the following:
All old configuration of the Auto Problem Record creation will be deleted when you upgrade from pre-Denali SP1 to Denali SP1 or a later release. Hence, the Administrator needs to do configurations based on CONDITION and TARGET fields again.
For more information, see Configuring Auto Create Problem Records.
- Assumptions
- Scripting
- Pre Upgrade Steps
- Database Upgrade from v4.1.4 Hotfix To v5.7SP5
- Database Upgrade from v5.7SP5 to ALPS
- Database Upgrade from ALPS to ALPS SP1
- Database Upgrade from ALPS SP1 to SIERRA
- Database Upgrade from SIERRA to SIERRA HF01
- Database Upgrade from SIERRA HF01 to SIERRA SP1 HF01
- Database Upgrade from SIERRA SP1 HF01 to Denali
- Database Upgrade from Denali to Denali SP1
- Database Upgrade from Denali SP1 to Denali SP3
- Database Upgrade from Denali SP3 to Tahoe
- Database Upgrade from Tahoe to Tahoe SP1
- Database Upgrade from Tahoe SP1 to Tahoe SP3
- Database Upgrade from Tahoe SP3 to Tahoe SP3 HF01
- Database Upgrade from Tahoe SP3 HF01 to Tahoe SP3 HF01 V1
- Database Upgrade from Tahoe SP3 HF01 v1 to Tahoe SP3 HF02
- Database Upgrade from Tahoe SP3 HF02 to Tahoe SP3 HF03
- Database Upgrade from Tahoe SP3 HF03 to Tahoe SP4
- Database Upgrade from Tahoe SP4 to Tahoe SP4 HF01
- Database Upgrade from Tahoe SP4 HF01 to Tahoe SP4 HF02
- Database Upgrade from Tahoe SP4 HF02 to Tahoe SP4 HF03
- Database Upgrade from Tahoe SP4 HF03 to Tahoe SP4 HF04
- Database Upgrade from Tahoe SP4 HF04 to Tahoe SP4 HF05
- Database Upgrade from Tahoe SP4 HF05 to Tahoe SP4 HF06
- Database Upgrade from Tahoe SP4 HF06 to Tahoe SP4 HF07
- Database Upgrade from Tahoe SP4 HF07 to Tahoe SP4 HF08
- Database Upgrade from Tahoe SP4 HF08 to Tahoe SP4 HF09
- Database Upgrade from Tahoe SP4 HF09 to Tahoe SP4 HF10
- Database Upgrade from Tahoe SP4 HF10 to Tahoe SP4 HF11
- Database Upgrade from Tahoe SP4 HF11 to Tahoe SP4 HF12
- 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.
Scripting
There is no impact to the JavaScript codes written using the Scripting functionality when the SummitAI application is upgraded to a later version. However, if there are changes on the Application interface in the later version where the fields referred in the JavaScript code are modified (fields removed, data type changed, etc.), there will be an impact on such JavaScript codes. Such JavaScript codes need to be validated and modified (as required).
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.7 SP5
To perform the database upgrade from v4.1.4 hotfix to v5.7 SP5, do the following:
Schema Version | Upgrade Script | Upgraded Schema Version |
V4.1.4 HF | Please download the scripts from below path which having the | v5.7 SP5 B005 |
Database Upgrade from v5.7SP5 to ALPS
To perform the database upgrade from v5.7SP5 to ALPS, do the following:
Schema Version | Upgrade Script | Upgraded Schema Version |
v5.7 SP5 | 1.Summitupgrade_v5.7SP5_B005_02Jan2019_to_ALPS_01Apr2019.sql | ALPS |
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 ALPS to ALPS SP1
To perform the database upgrade from ALPS to ALPS SP1, do the following:
Schema Version | Upgrade Script | Upgraded Schema Version |
ALPS | 2.Summitupgrade_ALPS_01Apr2019_to_ALPS_SP1_B006_4t |
Confluence Cloud Migration Alert: Please refer to known issues you may encounter in Confluence Cloud: https://eitdocs.atlassian.net/wiki/x/wDGwAQ