PPI - PIUPGRADE

8/3/2019 PPI - PIUPGRADE

http://slidepdf.com/reader/full/ppi-piupgrade 1/168

Solution Manager key- 35E9922CA1

Keyword – 20356441

J2ee_admin - DxPr0dPPI

Preparation:

1)

2)

3)



4)



5)

http://dsgpidbp101:50300/rep/support/CheckService

Logon as PIDIRUSER/DxPr0dPPI






If check - "missing key in admin data" for application "dir" fails please refer to another note - 1172942 to correct it.

Please note that the inconsistent objects will not cause problems if you are going to upgrade to

NetWeaver 7.10 SP07 patch 2, 7.10 SP08 onwards, 7.11 SP01 patch 1, 7.11 SP02 onwards.

We will be upgrading to 7.11 SP04, so we are ok.



6)



7)



dsgpidbp101:ppiadm 3> pwd

/usr/sap/PPI/DVEBMGS03/SDM/program

dsgpidbp101:ppiadm 5> StopServer.sh

Starting '/opt/IBMJava2-amd64-142/bin/java' '-Xmx256M' -jar

'/usr/sap/PPI/DVEBMGS03/SDM/program/bin/SDM.jar' shutdown 'sdmguiport=50318'

'sdmhome=/usr/sap/PPI/DVEBMGS03/SDM/program'

Sending shutdown request on Port 50318

Successfully sent shutdown request to the server at 'localhost:50318'.

Waiting 5 seconds for SDM server to shut down...

SDM server successfully shut down.

Successfully executed. Return code: 0

START UPGRADE PROGRAM


/oracle/SPI/sapdata6/PI7.1EHP1UPGRADE/51036470_MASTER

dsgpidbp101:ppiadm 21> STARTUP

"jce_policy_zip=/oracle/SPI/sapdata6/PI7.1EHP1UPGRADE/jce_policy-1_5_0.zip"

* Checking if C++ runtime is installed ...

* Running MIDBOOT to unpack and startup...

** Determined SAP system ID as 'PPI'

** Starting upgrade to SAP Netweaver 7.11

** Using upgrade directory /usr/sap/PPI/upg

** Locating SAPCAR

** Extracting SAP-JVM

** Extracting SL-Controller

** Unpacking /oracle/SPI/sapdata6/PI7.1EHP1UPGRADE/jce_policy-1_5_0.zip to SAP-JVM

** Starting SL-Controller...



** Checking username "ppiadm" for compliance...

Jul 15, 2010 2:33:03 AM [Info]: *************************

Jul 15, 2010 2:33:03 AM [Info]: Starting Server

Jul 15, 2010 2:33:03 AM [Info]: Reading server configuration.

Jul 15, 2010 2:33:03 AM [Info]: Reading service configuration DSUService.

Jul 15, 2010 2:33:03 AM [Info]: Configuring LogManager ...

Jul 15, 2010 2:33:03 AM [Info]: *************************************************

Jul 15, 2010 2:33:03 AM [Info]: Starting SL Controller listening on port 4241 ...

Jul 15, 2010 2:33:03 AM [Info]: Starting StorageService ...

Jul 15, 2010 2:33:03 AM [Info]: Initializing SecurityManager ...

Jul 15, 2010 2:33:04 AM [Info]: Server certificate fingerprint is C4 8F E7 00 0B BD 27 D2 7B DD 25 8A F3

9A EE F6

Jul 15, 2010 2:33:04 AM [Info]: Configuring HTTPManager ...

Jul 15, 2010 2:33:04 AM [Info]: Starting WebstartService ...

Jul 15, 2010 2:33:04 AM [Info]: RoleService switched off.

Jul 15, 2010 2:33:04 AM [Info]: AlertService switched off.

Jul 15, 2010 2:33:04 AM [Info]: Starting NotesService ...

Jul 15, 2010 2:33:04 AM [Info]: Starting ProcessService ...

Jul 15, 2010 2:33:04 AM [Info]: Starting MIDService ...

Jul 15, 2010 2:33:04 AM [Info]: Starting FileService ...

Jul 15, 2010 2:33:04 AM [Info]: LogService switched off.

Jul 15, 2010 2:33:04 AM [Info]: Starting MailService ...

Jul 15, 2010 2:33:04 AM [Info]: Starting services ...

Jul 15, 2010 2:33:04 AM [Info]: Starting service "DSUService" ...

Jul 15, 2010 2:33:05 AM [Info]: Service "DSUService" started

Jul 15, 2010 2:33:05 AM [Info]: Services started.



Jul 15, 2010 2:33:05 AM [Info]: Starting HTTP server listening on port 4239 ...

Jul 15, 2010 2:33:05 AM [Info]: HTTP server started.

Jul 15, 2010 2:33:05 AM [Info]: SL Controller started.



Added the last tp and R3trans to abap/exe and abap/exenew.




/usr/sap/PPI/DVEBMGS03/SDM/program

dsgpidbp101:ppiadm 39> StartServer.sh

Starting SDM - Software Deployment Manager...

tc/SL/SDM/SDM/sap.com/SAP AG/7.0018.20081020090558.0000

JStartupFramework is active



Operation mode of SDM in JStartupFramework is "Integrated".

Check if Server is running already.

OK server is not running. Enable SDM Process in JStartupFramework.

Successfully enabled SDM Process in JStartupFramework.

+--------------------------------------------------------------+

+ The SDM server will be started by the JStartupFramework now. +

+--------------------------------------------------------------+

Waiting 5 seconds for SDM server to start...

SDM started successfully.

Redirecting output to the two files "/usr/sap/PPI/DVEBMGS03/SDM/program/log/sdm_server.out" and

"/usr/sap/PPI/DVEBMGS03/SDM/program/log/sdm_server.err" respectively.



brspace -function tsextend -tablespace PSAPSR3 -size 20000 -autoextend no


brspace -function tsextend -tablespace SYSTEM -size 46 -autoextend no

brspace -function tsextend -tablespace PSAPSR3USR -size 18 -autoextend no

brspace -function tscreate -tablespace PSAPSR3711 -owner SAPSR3 -data both -size 20000 -autoex

tend no




Shutdown DI, CI, ASCS, and SCS.

STOP and DISABLE CRS on Node 2.

Startsap ASCS00

Startsap SCS01

Startsap DVEBMGS03



Stop ASCS00 and SCS01



Downtime Phase errors encountered:

RUN_APPLICATION_MIGRATION = check the server0. Logs due to tablespace issue.

RUN_OFFLINE_MIGRATION in JAVA

The problem you are experiencing is a known issue. The workaround is

to skip the migration of the log configuration.

please proceed as follows:

1. Exit Upgrade tool + SL Controller



more ./java/data/mig/MIGRATIONAUSF.LST

2. Edit your MIGRATIONAUSF.LST file

and delete the line containing the following line:

DEPLOYARCHIVES/sap.com~tc~je~log~configurator~migration.sda

3. Save the file and restart SL Controller + upgrade

4. Repeat the failing phase from point of failure



Activate the lock object ENQBADIIMPL_ENH ( package

SEEF_REDEFINITION_BADI).

Activate again this object using transaction SE11 to re-generate

ENQUEUE and DEQUEUE objects.



Copy the old SAP cluster files to the new exe folder.

sapwrapsap2crs

sapctl

sapctl.pl

crssapactions.pl

startsap - SAP script but modified for cluster

stopsap - SAP script but modified for cluster



The new startsap script by SAP wont work with Oracle clusterware.

START ASCS and SCS



Restarted CI.



Run BTCTRANS2 as ddic



Actions Before Restarting Production Operation

- Perform the follow-up activities for user root.

su – root

cd <upgrade directory>/abap/exenew

./oraroot.sh <SAPSID>

[root@dsgpidbp101 exenew]# ./oraroot.sh PPI



Preparing /usr/sap/PPI/SYS/exe/uc/linuxx86_64/brbackup ...

Preparing /usr/sap/PPI/SYS/exe/uc/linuxx86_64/brarchive ...

Preparing /usr/sap/PPI/SYS/exe/uc/linuxx86_64/brconnect ...

Preparing /usr/sap/PPI/SYS/exe/run/brbackup ...

Preparing /usr/sap/PPI/SYS/exe/run/brarchive ...

Preparing /usr/sap/PPI/SYS/exe/run/brconnect ...

done

You have new mail in /var/spool/mail/root

[root@dsgpidbp101 exenew]# pwd

/oracle/SPI/sapdata6/upg/abap/exenew

cd /sapmnt/<SAPSID>/exe/(n)uc/<platform>

cp -p ./icmbnd.new ./icmbnd

chown root:sapsys icmbnd

chmod 4750 icmbnd

[root@dsgpidbp101 linuxx86_64]# cp -p icmbnd.new icmbnd

[root@dsgpidbp101 linuxx86_64]# chown root:sapsys icmbnd

[root@dsgpidbp101 linuxx86_64]# chmod 4750 icmbnd

[root@dsgpidbp101 linuxx86_64]# ls -l icmb*

-rwsr-x--- 1 root sapsys 1335233 Jan 19 19:51 icmbnd

-rwxr-xr-x 1 ppiadm sapsys 1335233 Jan 19 19:51 icmbnd.new

[root@dsgpidbp101 linuxx86_64]# pwd

/sapmnt/PPI/exe/uc/linuxx86_64



RZ70



o Log on with your J2EE administrator user.

o Choose Configuration Management - Scenarios - Configuration Wizard.

o From Configuration View, choose All Configuration Tasks (dropdown box).

o Select PI Upgrade and choose Start.



You perform the database-specific actions: Amongst others, you create or update the SAPDBA role, check the

environment variables for BR*Tools, and back up the database.

o Log on as user orappi at the UNIX level.

o Start the SQL script with:

cd $ORACLE_HOME/dbs



cp /usr/sap/PPI/SYS/exe/run/sapdba_role.sql sapdba_role.sql

sqlplus /nolog @sapdba_role SR3

Call transaction se38 and execute the program: SRT_ADMIN_CHECK



SLDCHECK



Testing the HTTP services on the Integration Server

Start transaction SICF .Choose as Hierarchy Type: ServiceChoose default_host sap xi.

o All services should be active, particularly the services:

- cache- cache_ssl- engine (for pipeline processing)

- adapter_plain (for HTTP Adapter)- wsdl*



Run RSXMB_ACTIVATE_ICF_SERVICES in SE38



Choose sap -> bc -> srt for the Web Service Runtime



Start transaction SICF.Choose default_host - sap bc ping (connection test)and then choose Test service in the context menu of the entry.

A browser should then open, prompting a logon. If the browser does not open, this indicatesa possible problem with the HTTP service of the SAP system and needs to be examined.

AI_RUNTIME_JCOSERVER (TCP/IP connection)



INTEGRATION_DIRECTORY_HMI (HTTP connection, use the XIISUSER with XI3.0 and thePIISUSER with PI 7.0 and PI 7.1 to authenticate). Is the Path Prefix set to “/dir/CacheRefresh” as recommended since SP1 of XI 3.0?Note that a HTTP 500 response is a successful test for this connection.



Caches in PI

call transaction SXMB_IFR

Cache Connectivity Test in RWB

Cache Connectivity Test



SXI_CACHE

Procedure

Log into the client of the Integration Server and call transaction SXI_CACHE. Start a manual cacherefreshvia XI Runtime Cache Start Complete Cache Refresh (Shift + F6). This will trigger a background jobthatcan be seen in transaction SM58 (its name is SAI_CACHE3_REFRESH_BACKGROUND).



Adapter Engine CacheThe Adapter Engine Cache contains the URL of the Adapter Engine. The information is used when amessage is sent from the Integration Engine to the Adapter Engine.

Procedure:

Log into the client of the Integration Server and call transaction SXI_CACHE.Navigate to: GoTo -> Adapter Engine Cache



Testing the CPA Cache

The cache of the Adapter Engine is called CPA Cache. It contains configuration information as e.g.adapterIDs that run on the J2EE Engine. Thus, it is important that the refresh of this cache is working correctly.

Procedure :Open a browser window and call the URL: http://<host>:5<sysnr>00/CPACache/refresh?mode=delta. (ifyouuse a HTTP LoadBalancer replace Host an Port with the one of the LoadBalancer)A full CPA Cache Refresh is triggered by executing the following URL: URL:http://<host>:5<sysnr>00/CPACache/refresh?mode=full (if you use a HTTP LoadBalancer replace Hostan

Port with the one of the LoadBalancer)Attention: Be aware not triggering a full cache refresh during processing of messages in production as itwillimpact message processing.Use the PIDIRUSER to authenticate yourself, it is the only user that is allowed to carry out a CPA CacheRefresh.



Testing the connectivity between Enterprise Service Repository and SLD



Testing the connectivity between Integration Directory and Enterprise Service

RepositoryProcedure :

Start the Integration Directory. Go to „Tools‟ -> „Apply Model from ES Repository‟. Then use the Help for the Field „Name‟.

This test is successful if you can see a list of Integration Scenarios from the ES Repository. Cancelthe Transfer once you have made sure that the list can be displayed properly.



This test is successful if you can see a list of Integration Scenarios from the ES Repository. Cancelthe Transfer once you have made sure that the list can be displayed properly.

Che ck Runtime Workbench



In the J2EE engine a number of background jobs are scheduled during the installation process. It shouldbechecked if they run smoothly.

Procedure

Log into the client of the Integration Server and call transaction SXMB_IFR. This will bring up a browserwindow with a link to the RWB. Once logged in, go to the „Component Monitoring‟ choose „All‟ from the

dropdown menu of the field “Component with Status” and hit the “Display” button. Click on the Adapter Engine button to get the details.Choose the button “Background Processing”. A new window opens displaying the background processes being executed in your Java environment.

Check if a default deletion job is scheduled and in status greenCheck if a default Recover Job is scheduled and in status green

PPI - PIUPGRADE

Documents

Transcript of PPI - PIUPGRADE