Upgrade SAP BO 4.0 SP 05 to SAP BO 4.2 SP 03

[Former Member]

Hello,

My colleague and I are trying to upgrade SAP Business Objects from Version 4.0 Service Pack 5 to SAP Business Objects Version 4.2 Service Pack 3 on a test server. Our CMS database is on Oracle and our data warehouse is built in teradata.

Attached are all the steps we followed to do the upgrade. Can you please look through them and tell us if we are doing anything wrong? You time and effort is greatly apprecaited.

---------------------------------------------------------------------------------------------------------------------------------------------- 

SERVER CONFIGURATION
WINDOWS SERVER 2008 R2 ENTERPRISE
RAM 32 GB
SYSTEM TYPE 64-bit Operating system
Intel Xeon(R) CPU X5670 @ 2.93GHz 2.93 GHz (2 processors) 

----------------------------------------------------------------------------------------------------------------------------------------------
From Previous Installation
a) Backup of Central Management Server (CMS) & Audit metadata and detach the Central Management Server (CMS) and Auditing database

1) exp userid=<username>/<password> owner=<DATABASE_TO_BACKUP> indexes=Y rows=Y TRIGGERS=Y constraints=Y file=CbackupBO_DEV.dmp log=CbackupBO_DEV.log statistics=NONE

b) Backup of Following Configuration Files available at Tomcat (Web Tier) & BOBJ Layer (Management Tier & Processing Tier)

1)  Pick up the files at the path SAP BusinessObjectstomcatconf
a) web.xml
b) server.xml

2)Pick up the files at the path  [\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps\BOE\WEB-INF\config\default\]
a) BILaunchpad.properties
b) Global.properties (If you have done any changes)

3) Backup the entire FRS Folder (filestore) [\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\]

4) Retrieve existing cluster keys [\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\dbinfo\]

5) Retrieve existing credentials below
PRODUCTION
10.16.5.166
a) Server Intelligence Agent (SIA) Node name: TPPBO06
b) Server Intelligence Agent (SIA) Port: 6410
c) Central Management Server (CMS) Name: ?
d) Central Management Server (CMS) Port: 6400
e) User: Administrator
f) Password: prod@346
g) Cluster Key: [[g0482n4j7UHoj316S.uIkg]]
h) Central Management Server (CMS) Database Name:
i) Auditing Database Name:

PRODUCTION
10.16.5.167
a) Server Intelligence Agent (SIA) Node name: TPPBO07_Clust
b) Server Intelligence Agent (SIA) Port: 6410
c) Central Management Server (CMS) Name: ?
d) Central Management Server (CMS) Port: 7400
e) User: Administrator
f) Password: prod@346
g) Cluster Key: [[g0482n4j7UHoj316S.uIkg]]
h) Central Management Server (CMS) Database Name:
i) Auditing Database Name:
----------------------------------------------------------------------------------------------------------------------------------------------

Pre-Requists
1) Install WinRaR

2) Install Microsoft .NET Framework 3.5 or above

3) Install Oracle on the local system.
a) Run Setup and use custom installation.
b) Select all the languages needed
c) Browse to the location where oracle should be installed
d) Select all components.

4) Place the file tnsnames at the path [C:\app\Administrator\product\11.2.0\client_1\NETWORK\ADMIN]

5) Make Environmental Variable TNS_ADMIN and give the path of the tnsnames file in the value.
a) Go to Properties of My Computer
b) Advanced System Settings
c) Environment Variable
d) New System Variable

6) Go to the path [C:\WindowsSystem32\drivers\etc\hosts\] enter the ip and name of the machine separated by tab so that they can communicate

7) Install Teradata Tools and Utilities

8) Create all the ODBC connections from the existing environment

9) Install JRE 6

10) Data Execution Prevention (DEP):
Windows Server 2008
1) Start -> Right-click on My Computer -> Properties.
2) Advanced System Settings
3) Click on Settings under "Performance" category.
4) Open the Data Execution Prevention tab and select the first option: "Turn on DEP for essential Windows programs and services only".
5) User Account Control (UAC):

11) Launch Control Panel.
1) User Accounts -> "Turn User Account Control on or off".
2) Disable UAC.

12) Enable 8-dot-3 filename support:
The BI platform requires 8-dot-3 support to be enabled. Verify that your Windows server has 8-dot-3 filenames enabled:
1) From the Windows Start menu, select Run....The Run dialog window is displayed.
2) Type regedit into the Open field. The Registry Editor program runs.
3) Browse the registry tree to HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Control -> FileSystem
4) Double-click <NtfsDisable8dot3NameCreation> and ensure that its value is set to 0. When set to 0, Windows 8-dot-3 filename support is enabled.

13) Kill all JAVA.EXE processes that may still be running and taking up CPU / RAM (using task manager: right click, end process tree on each java process; or use process explorer)

14) ONLY IF YOU ARE USING A SHARED DRIVE TO HOUSE THE FRS then do the below:
1) Go to Control Panel
2) Go to User Account
3) Go to Manage you Credentials
4) Fully qualify the credentials of the shared drive with the ip of the shared drive (\\10.16.5.184\data\BO UPGRADE\Prod\FileStore)
----------------------------------------------------------------------------------------------------------------------------------------------
Server 1 - Install SAP BO 4.0
a) Place all the SAP BO 4.0 installation files in one folder and then run 51043404_part1 as administrator (SBOP BI PLAT 4.0 SP4 SERVER WIN 64B 1 of 5)

b)Folder 51051282
1) Go to the path [\51043404\DATA_UNITS\BusinessObjectsServer_win\] and run the file "setup" as administrator

2) Follow the steps from https://wiki.scn.sap.com/wiki/display/BOBJ/Configuring+and+installing+BI+platform+on+server+1

3) Select English and click next

4) Check all pre-requisites are completed

5) Press Next on home screen

6) Accept the license agreement and press next

7) Provide product key

8) Select Language

9) Select Custom/Expand

10) Provide Path where BO should be installed

12) Deselect Sybase database in platform server as we want to use Oracle as our Central Management Server (CMS) database

13) Start New

14) Central Management Server (CMS) database type: Oracle

15) Auditing Database type: None

16) Server Intelligence Agent (SIA) Node name: TPBIBOTMP21

17) Server Intelligence Agent (SIA) Port: 6410

18) Central Management Server (CMS) Port: 6400

19) Central Management Server (CMS) User: Administrator

20) Central Management Server (CMS) Password: Teradata#123

21) Central Management Server (CMS) Cluster Key: Teradata#123

22) ORACLE_TNSNAME: SAPHOST --> as per the "tnsnames" file in step 4 of the Pre-Requists

23) ORACLE_USERNAME: BO_TMPCMS --> Oracle empty user or which can be emptied

24) ORACLE_PASSWORD: telenor123

25) check Reset existing Database

26) Connection Port: 8080

27) Shutdown Port: 8005

28) Redirect Port: 8443

29) HTTP Listening Port: 6405

30) Do not configure connectivity to SMD Agent

31) Do not configure connectivity to Introscope Enterprise Manger

32) Start Installation.


----------------------------------------------------------------------------------------------------------------------------------------------

Server 2 Cluster - Install SAP BO 4.2

a) Place all the SAP BO 4.2 installation files in one folder and then run 51050786 as administrator (SBOP BI PLAT 4.2 SP3 SERVER WIN 64B 1 of 5)

b)Folder 51050786

1) Go to the path [\51051282\DATA_UNITS\BusinessObjectsServer_win] and run the file "setup" as administrator

2) Follow the steps from https://wiki.scn.sap.com/wiki/display/BOBJ/Configuring+and+installing+BI+platform+on+server+1

3) Select English and click next

4) Check all pre-requisites are completed

5) Press Next on home screen

6) Accept the license agreement and press next

7) Provide product key

8) Select Language

9) Select Custom/Expand

10) Provide Path where BO should be installed

12) Deselect Sybase database in platform server as we want to use Oracle as our Central Management Server (CMS) database

13) Start New

14) Central Management Server (CMS) database type: Oracle

15) Auditing Database type: None

16) Server Intelligence Agent (SIA) Node name: TPBIBOTMP22

17) Server Intelligence Agent (SIA) Port: 6410

18) Central Management Server (CMS) Port: 6400

19) Central Management Server (CMS) User: Administrator

20) Central Management Server (CMS) Password: Teradata#123

21) Central Management Server (CMS) Cluster Key: Teradata#123

22) ORACLE_TNSNAME: SAPHOST --> as per the "tnsnames" file in step 4 of the Pre-Requists

23) ORACLE_USERNAME: BO_TMPCMS --> Oracle empty user or which can be emptied

24) ORACLE_PASSWORD: telenor123

25) check Reset existing Database

26) Connection Port: 8080

27) Shutdown Port: 8005

28) Redirect Port: 8443

29) HTTP Listening Port: 6405

30) Do not configure connectivity to SMD Agent

31) Do not configure connectivity to Introscope Enterprise Manger

32) Start Installation.


----------------------------------------------------------------------------------------------------------------------------------------------

AFTER INSTALLATION OF 4.0 on Server 1

33) After installation is complete successfully go to the Central Configuration Manager (CCM) and stop the Server Intelligence Agent (SIA) and Apache Tomcat.

34) Restore the Central Management Server (CMS) database backup onto the Central Management Server (CMS) database installed with the SAP BO installation.
a) imp <username>/<password> fromuser=<NAME_OF_DATABASE_BACKEDUP> touser=<NAME_OF_DATABASE_TO_RESTORE_ON> indexes=Y rows=Y constraints=Y file=CbackupBO_DEV.dmp log=CbackupBO_DEV.log statistics=NONE

35) Delete references to the original server from the restored Central Management Server (CMS) database as follows:
a) SELECT * FROM cms_infoobjects7 WHERE parentid=16 OR parentid=59;
b) DELETE FROM cms_infoobjects7 WHERE parentid=16 OR parentid=59;
c) Commit the delete

36) Go to the Central Configuration Manager (CCM) and press “Add Node” or “Add Server Intelligent Agent”
a) Press Next on the Welcome Screen
b) Node Name: TPBIBOTMP02 --> Node name should be the same as name originally used while setting up the new environment.
c) Server Intelligence Agent (SIA) Port: 6410 --> SIA Port should be the same as name originally used while setting up the new environment.
d) Select “Add node with default services”
e) Press Next
f) Select "Start a New Temporary CMS"
g) New CMS Port: 6400
h) Click Specify
i) ORACLE_TNSNAME: SAPHOST --> as per the "tnsnames" file in step 4 of the Pre-Requists
j) ORACLE_USERNAME: BO_PROD --> Oracle empty user or which can be emptied
k) ORACLE_PASSWORD: telenor123
l) Cluster Key: [[g0482n4j7UHoj316S.uIkg]] --> This cluster key should be the same as the cluster key used from where the backup was taken
m) User: Administrator
n) Password: prod#346 --> The password should be the same as the password from the backup taken

37) Right click on the previous Server Intelligence Agent (SIA) in the Central Configuration Manager (CCM) and go to properties and do the following:
a) In the properties tab set the “Startup Type” to “Disabled”

38) When the Server Intelligence Agent (SIA) is created, do the below:
a) go to SIA > Properties > Configuration and modify the ClusterName of the restored environment to be different from the production environment
b) go to SIA > properties and log in as the administrator of that machine.

39) After all the services have stopped go to the location where the SAP Server was installed and follow the path “\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\”. Here rename the existing FRS (filestore) folder and place the backed-up FRS folder.
a) OPEN CMC > Servers > Core Servers
b) STOP InputFileRepository and OutputFileRepository of the server (Primary)
c) Go to Properties
d) Then under the Output Filestore Service header edit the location of the FRS (\\10.16.5.184\data\BO UPGRADE\Prod\FileStore)

40) Start the newly created Server Intelligence Agent (SIA)

41) Start the Apache Tomcat

42) If in the launch pad/CMC [http://localhost:8080/BOE/BI || http://localhost:8080/BOE/CMC ] if the default system name is incorrect then do the flowing:
a) Go to the directory <BusinessObjects Installation>\tomcat\webapps\BOE\WEB-INF\config\default
b) Copy the 2 files to <BusinessObjects Installation>\tomcat\webapps\BOE\WEB-INF\config\custom
1) BIlaunchpad.properties
2) CmcApp.properties
c) In both the file edit the below:
1) cms.default=<set to your appropriate CMS server and port>
d) Restart the tomcat server from the Central Configuration Manager (CCM)

----------------------------------------------------------------------------------------------------------------------------------------------

AFTER INSTALLATION OF 4.0 IS DONE PROD IS RESTORED

a) Follow the pre-requisites in the pre-requisites section

b) Install the upgrade of SAP BO 4.2 using the package "BIPLATS4203_0-80001044_P1"

c) Once the installation is complete go to CMC and Change licence key

d) Go to the path [C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java] and replace the lib folder with the lib folder from a running 4.2 environment.

e) Login to CMC and click on System Configuration Wizard
1) Make sure all the services are enabled and running.
2) Click next on the welcome screen
3) Uncheck "Keep existing configuration" and enable all the products then click next
4) Uncheck "Keep existing configuration" and move the scroll bar to small.
5) If the FRS folder location is correct in the services "OutputFileRepository" and "InputFileRepository" then click next and do not uncheck "Keep existing configuration"  otherwise uncheck "Keep existing configuration" and correct the paths
6) Review the changes and apply

f) Login to CMC and go to Servers --> Server List
1) Stop the services WebApplicationContainerServer and AdaptiveProcessingServer
2) Make sure the entry "-Dbusinessobjects.connectivity.directory=C:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0//dataAccess/connectionServer" (with the quotes) is part of the Command Line Parameters 
3) Make sure the value of ~ is greater than 1 in the parameter "-Xmx~g"

g) If the status of the WebApplicationContainerServer is still "Running with error" then
1) Go to CMC > Servers > Server List
2) Create a server and add the services of WebApplicationContainerServer

----------------------------------------------------------------------------------------------------------------------------------------------


AFTER INSTALLATION OF 4.2 on Server 2 - Clustered

1) Go to the Central Configuration Manager (CCM) and press “Add Node” or “Add Server Intelligent Agent”
a) Press Next on the Welcome Screen
b) Node Name: TPBIBOTMP02 --> Node name should be the same as name originally used while setting up the new environment.
c) Server Intelligence Agent (SIA) Port: 6410 --> SIA Port should be the same as name originally used while setting up the new environment.
d) Select “Add node with default services”
e) Press Next
f) Select "Start a New Temporary CMS"
g) New CMS Port: 6400
h) Click Specify
i) ORACLE_TNSNAME: SAPHOST --> as per the "tnsnames" file in step 4 of the Pre-Requists
j) ORACLE_USERNAME: BO_PROD --> Oracle empty user or which can be emptied
k) ORACLE_PASSWORD: telenor123
l) Cluster Key: [[g0482n4j7UHoj316S.uIkg]] --> This cluster key should be the same as the cluster key used from where the backup was taken
m) User: Administrator
n) Password: prod#346 --> The password should be the same as the password from the backup taken

2) Login to CMC and click on System Configuration Wizard
a) Make sure all the services are enabled and running.
b) Click next on the welcome screen
c) Uncheck "Keep existing configuration" and enable all the products then click next
d) Uncheck "Keep existing configuration" and move the scroll bar to small.
e) If the FRS folder location is correct in the services "OutputFileRepository" and "InputFileRepository" then click next and do not uncheck "Keep existing configuration"  otherwise uncheck "Keep existing configuration" and correct the paths
f) Review the changes and apply

[denis_konovalov]

That is a huge amount of reading.

Can you summarize in short paragraph what are you trying to do ?
Are you simply upgrading from 4.0 Sp5 to 4.2 Sp3 on the same server ?
Or are you moving from one machine to another and changing CMS DB's ?