Scribd
Upload
39 views17 pages

Activities Checklist

This document outlines the steps for upgrading a SAP BusinessObjects platform from version 4.1 SP10 to version 4.2 SP6. It involves pre-upgrade tasks like backing up files, databases and configurations. It also involves securing licenses for the new version, downloading installers, checking for sufficient disk space and communicating the planned downtime. The upgrade process involves running a pre-requisite check, executing the setup file and providing information during installation like product keys, installation folders, server configurations and administrator account details. Post upgrade tasks include verifying the upgraded platform.

Uploaded by

nikhillchief
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
39 views17 pages

Activities Checklist

This document outlines the steps for upgrading a SAP BusinessObjects platform from version 4.1 SP10 to version 4.2 SP6. It involves pre-upgrade tasks like backing up files, databases and configurations. It also involves securing licenses for the new version, downloading installers, checking for sufficient disk space and communicating the planned downtime. The upgrade process involves running a pre-requisite check, executing the setup file and providing information during installation like product keys, installation folders, server configurations and administrator account details. Post upgrade tasks include verifying the upgraded platform.

Uploaded by

nikhillchief
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 17

Sl.

No Activity

1
2

3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Downtime
Start Date End Date Action Point Status
required
Yes/No
Comments
Sl. No Activity Start Date

Pre Upgrade
1 Collect the Service Account from BBC
2 Communicate the Plan with end Users
3 Run Platform Support tool for BO 4.1 SP10
4 Check the CCM (SIA and Services) and document the screens

5 Check the CMC and BI Launchpad logon

6 Check the services in CMC

7 Check the Connections, Authernication, User hirarchy

8 Run the Webi reports through the launchpad

9 Run the Dashboards (CCT and MTD)


10 Check the folders in BI Launchpad
11 Pause all the recurring schedules

12 Take the Database backup


13 Take the file repository backup(IFRS, OFRS and Promotions)
14 Backup server Configuration from CCM
15 Take the Image level Backup

16 Run the Repo scan

17 Secure the Licence for the BO 4.1 SP 10

18 Secure the .cert and keystore files for SSO

19 BackUp configuration settings from Tomcat server (Tomcat files)

20 secure the TNS.ora file

21 Secure Worker properties file for Apache

22 Ensure that there is sufficient disk space in the drives


Download and Secure the installers of 4.2 SP 6 Upgarde, BO 4.2 SP6
Client tools, Lumira 2.2, Crystal reports 2016, Crystal reports 4.2 for
22 Entterprise, Analysis for office 2.7 in the local system

23 Secure the Licence key for 4.2 SP 6

24 Communicate the Downtime with the Busisness

25
Upgrade

23 Open CMD and navigate to the software download location

Execute the command "setup.exe -pre_requisite_check <response file


path> <file path to store failed pre-requisite info>." like setup.exe
-pre_requisite_check C:\response.ini C:\logs\xyz_failedpc.txt
24
25 The result of this check will write a .txt file in setupengine.log

26
Downtime
End Date Action Point Status
required

No BBC Not Started


No IBM Not Started
No IBM Not Started
No IBM Not Started
No IBM Not Started
No IBM Not Started
No IBM Not Started
No IBM Not Started
No IBM Not Started
No IBM Not Started
No IBM Not Started
No BBC Not Started
No IBM Not Started
No IBM Not Started
No ATOS Not Started
No IBM Not Started
No IBM Not Started
No IBM Not Started
No IBM Not Started
No IBM Not Started
No IBM Not Started

No IBM Not Started

No BBC Not Started


No COMMS Not Started
Comments
The installation program prompts for the following information:
Product key.
Folder where the BI platform will be installed.
Web application server configuration, including type, connection, and authentication details.
Database server configuration, including type, connection, and authentication details.
CMS system and Auditing Data Store configuration information, including type, connection, and authentication details.
Central Management Server (CMS) administrator account password and cluster key.
CMS port number to receive incoming connections.
Server Intelligence Agent (SIA) name.
Server Intelligence Agent (SIA) port number for incoming connections.
SAP Solution Manager Diagnostics (SMD) configuration.
CA Wily Introscope Enterprise Manager configuration.
Subversion version control system configuration to store configuration files.
Promotion management configuration.
Installation type (Full, Custom / Expand, Web Tier).
uthentication details.
Sl. No Activity

1
2

3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Downtime
Start Date End Date Action Point Status
required
Yes/No
Comments
Sl. No Activity

1
2

3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Downtime
Start Date End Date Action Point Status
required
Yes/No
Comments

You might also like