sap refresh (2)

7/22/2019 Sap Refresh (2)

1/63

SAP

Document Revision History

Date Version

Author Change Description

1.01.1

SAP Refresh Master Document Page 1 of 63


2/63

Text Heading Legend

System Color

ECC

BW

CRM

XI

SRM

SCM

1. PRE-DATABASE/SAP REFRESH....................................................................................71.1Post a System Message about Scheduled Downtime....................................................................................................71.2Saplicense..........................................................................................................................................................................7

1.3 Confirm Passwords for Source/Target system with Security team................................................................ .........7

1.4 Stage Instance Specific Information before Volume Group is recreated................................................................8

1.5 Export User Master data.............................................................................................................................................8

1.6Transport Printer Definitions.........................................................................................................................................9

1.7Transport RFC Definitions.............................................................................................................................................9

1.8Logical System Definitions..............................................................................................................................................9

1.9Partner Profile.................................................................................................................................................................9

1.10 IDOC Port Definitions..................................................................................................................................................9

1.11 Client Definitions..........................................................................................................................................................9

1.12 Trusted Systems .........................................................................................................................................................10

1.13 Trust Manager Portals Certificates.......................................................................................................................10

1.14 Integration Engine Configuration.............................................................................................................................10

1.15 Maintain SLD Access data ........................................................................................................................................10



3/63

1.16 SLD Bridge Info ABAP/JAVA .......................................................................................................................... ...10

1.16.1 ABAP ...................................................................................................................................................................101.16.2 Java .....................................................................................................................................................................10

1.17 Port Maintenance IDOC Adapters...........................................................................................................................10

1.18 IDOC Adapter Metadata Overview..........................................................................................................................10

1.19 Distribution Model View............................................................................................................................................11

1.20 Maintain CRM RFC Parameter ...............................................................................................................................111.21 Validate HP OMS entry in SPAD ............................................................................................................................11

1.22 Display / Note Logon Group Definitions....................................................................................................... ......... .11

1.23 Check operation modes ....................................................................................................................................... .....11

1.24 Check for ITS..............................................................................................................................................................11

1.25 Verify DBA Planning Calendar.................................................................................................................................11

1.26 XI Specific Steps.......................................................................................................................................... .......... ....12

1.26.1 Export SLD Information.......................................................................................................................................121.26.2 Export the Repository server information............................................................................................................121.26.3 Export the Directory server information........................................................................................................... ...131.26.4 Configure CMS Setup................................................................................................................................. .........131.26.5 SLD DATA supplier and Bridge..........................................................................................................................131.26.6 SLD Business Systems.........................................................................................................................................13

1.26.8 XI Message Archiving & Deletion.......................................................................................................................141.27 BI Specific Steps.........................................................................................................................................................15

1.27.1 Conversion of Logical System Names......................................................................................................... ........151.27.2 UDC Connection Container Settings....................................................................................................................15

1.28 SCM Specific Steps.................................................................................................................................................. ..16

1.28.1 Document connections to liveCache.....................................................................................................................161.28.2 Configure UDC (* same step as BI **).................................................................................................................161.28.3 Document Business System Groups (BSG).................................................................................................... .....161.28.4 qRFC Monitor.......................................................................................................................................... ......... ...161.28.5 Stop/check CIF queue............................................................................................................................ .......... ....171.28.6 LiveCache consistency........................................................................................................................................ .171.28.7 Backup liveCache.................................................................................................................................................17

1.29 SRM Specific............................................................................................................................................................ ..17

1.29.1 Copy the SRM IPC parameter file .......................................................................................................................171.30 Display/Note Logical Ports.......................................................................................................................... .......... .18

2 DATABASE BACKUP.......................................................................................................192.1Oracle Database Backup Source System..................................................................................................................19

2.2SCM maxDB liveCache Backup - Source System......................................................................................................19

3. ORACLE DATABASE RESTORE TARGET SYSTEM............................................203.1 Reproduce Source System environment on Target System...................................................................................20

3.2 Add Source system in /etc/hosts file................................................................................................................ .........21

3.3 Start database as Source System..............................................................................................................................21

3.4 Create Control File.................................................................................................................................................. ..213.6 Copy back the pre-staged files from the staging Directory - /usr/sap/put_refresh................................ ......... ...22

3.7 Change the ownership of all files to target system........................................................................ .........23

3.7.1 To change the ownership we need to be the root......................................................................................... ..........233.7.2 Change the ownership.................................................................................................................................. .........233.7.3 Set the permission for the new kernel files.................................................................................................... .......233.7.4 Copy the files from /sapmnt//exe to /usr/sap//SYS/exe/run Directory...........................................233.7.5 Now run the saproot.sh script................................................................................................................................233.7.6 Now copy the files from /usr/sap//SYS/exe/run to /sapmnt//exe........................................... .........23

3.8 Recover Database as Target System...................................................................................................................... ..24

3.8.1 Recover the database on target system as ora ..................................................................................243.8.2 Restart the database to make sure that DB starts correctly.......................................................................... .........243.8.3 Create the ops$adm users and grant permission..............................................................................24

3.8.4 Test the connectivity to the database as user adm................................................................... ........253.9 Create the Oracle Password File (OPTIONAL).....................................................................................................25



4/63

4 DELETE TARGET JAVA INSTALLATION................................................................254.1 **Delete the currently installed JAVA Installation**............................................................................................25

4.2 Delete the following directories on Target DB server............................................................................... .......... .....254.3 Delete the following directories on each of the application server...................................................................... .....254.4 Delete the JAVA profile............................................................................................................................................264.5 Drop your j2ee schema..............................................................................................................................................26

4.6 Now drop the table spaces as they are empty.........................................................................................................264.7 Delete the data files of tablespace PSAPDB from the system ................................................ .......26

5.1 Install sap license............................................................................................................................................... .........28

5.2 Set Background Process as Zero ..................................................................................................................... .........28

5.3 Cleanup /sapmnt/SID/global......................................................................................................................................28

5.4 STARTSAP .................................................................................................................................................... ......... ...28

5.5 Reinitialize TMS after DB copy...............................................................................................................................28

5.6 Delete Jobs .................................................................................................................................................................29

5.7 Revert background processes to original......................................................................................................... .......29

5.7.1Edit instance profile..................................................................................................................................................295.7.2 Stop SAP server ....................................................................................................................................................295.7.3Start SAP..................................................................................................................................................................29

5.8 Re-initialize Jobs......................................................................................................................................................29

5.9 Schedule Standard Jobs...................................................................................................................................... ........29.............................................................................................................................................................................................29

5.10 Configure SAP Profile Parameter Files ................................................................................................................29

5.11 Configure Op Modes ................................................................................................................................... ......... ...30

5.12 Check System Logs................................................................................................................................................. .30

5.13 Fix Logon Group Names....................................................................................................................................... ..30

5.14 Fix Server Group Names.........................................................................................................................................31

5.15 Import User Master Data........................................................................................................................................31

5.16 Post user master import..........................................................................................................................................31

5.17 Import Printer, RFC Definitions............................................................................................................................31

5.18 Fix ITS Information.......................................................................................................................................... ......32

5.19 Delete Local CUA/Detach a Satellite Client..........................................................................................................32

5.20 Update HP OMS entry in SPAD ....................................................................................................................... ....32

5.21 Disconnect from previously connected P21 ...........................................................................................................32

5.22 Converting Logical Systems....................................................................................................................................32

5.23 Logical System Names..............................................................................................................................................33

5.24 IDOC Port Definitions.............................................................................................................................................33

5.25 Partner Profile.............................................................................................................................................. .......... ..33

5.26 Create Trusted System ......................................................................................................................................... ..33

5.27 Republish Services.................................................................................................................................................. .33

5.28 Trust Manager Portals Certificates........................................................................................................... .........34

5.29 Integration Engine Configuration..........................................................................................................................34

5.30 Port Maintenance IDOC Adapters............................................................................................................ ......... ...34

5.31 IDOC Adapter Metadata Overview.......................................................................................................................34

5.32 Verify Distribution Model View........................................................................................................................... ..34

5.33 Delete Workload Analysis Logs for Old Server....................................................................................................34

5.34 Reset the passwords for the following users .........................................................................................................35

5.35 Client Definition ......................................................................................................................................................35

5.36 Maintain DBA Planning Calendar.........................................................................................................................35

5.37 qRFC Monitor..........................................................................................................................................................35

SLD Specific........................................................................................................................................................................35

5.38 Maintain SLD connection parameters......................................................................................................................355.39 Schedule XML Messages Delete Jobs.................................................................................................................... ..36

5.40 Attach a Satellite Client to CUA.............................................................................................................................36

6. INSTALL J2EE AND APPLY JAVA PATCHES ON CI..................................................376.1 NW04S Java Install.................................................................................................................................... ......... ...37

6.2 NW04 Install(SRM/SCM Specific)...........................................................................................................................38

6.3 Java Patches on CI....................................................................................................................................................39

6.3.1 Update SDM...........................................................................................................................................................39



5/63

6.3.2 Update JSPM..........................................................................................................................................................406.3.3 Apply Java Patch on CI...................................................................................................................................... ....406.3.4 Troubleshoot Errors while applying support package using JSPM........................................................... .......... ..406.3.5 For Target systems (Eg: SRM, SCM) which have J2EE 640 (Oracle 9i) install on Oracle 10.2 Database............41

7.POST SAP SYSTEM SPECIFIC STEPS:..........................................................................427.1 XI Specific Steps.......................................................................................................................................... .......... ....427.1.1 Configure the SLD Bridge (XI) ...........................................................................................................................427.1.2 Configure CMS Setup................................................................................................................................. .........427.1.3 Run transaction SXMB_IFR....................................................................................................................... .........427.1.4 Activate XI related services ........................................................................................................................ .........427.1.5 Refresh XI Cache....................................................................................................................................... ......... .427.1.6 XI Message Archiving & Deletion.......................................................................................................................427.1.7 Configure JCo RFC provider using Visual Admin......................................................................................... ......43

7.2 BI Specific Steps..........................................................................................................................................................45

7.2.1 Restore the Logical system destinations............................................................................................... ......... .......457.2.2 Restore the Table RSBKDTP entries to Target SID........................................................................................ .....457.2.3 Restore Source System Connection..................................................................................................... ......... .......46

7.2.4 Maintain IDOC Sender/Receiver Systems....................................................................................................... ....467.2.5 RSA1 Check.........................................................................................................................................................467.2.6 BI Integration into the Portal................................................................................................................................467.2.7 Configure UDC.......................................................................................................................................... ......... .477.2.8 Modify Logical System conversion Table.................................................................................................... .......487.2.9Change BIA (BI Accelerator) RFC Destination.......................................................................................................48

7.3 SCM Specific Steps.................................................................................................................................................. ..49

7.3.1 Delete connections to liveCache.............................................................................................................. ......... ...497.3.2 Setup Logical Systems............................................................................................................................. ......... ...497.3.4 qRFC Monitor.......................................................................................................................................... ......... ...497.3.5 Start CIF queue....................................................................................................................................................497.3.6 liveCache Restore.................................................................................................................................................507.3.7 liveCache consistency................................................................................................................................ ......... .50

7.4 ECC Specific Steps...................................................................................................................................... .......... ....507.4.1 Update Custom tables..............................................................................................................................................507.4.2 ECC Adapter Ports..................................................................................................................................................50

7.5 SRM Specific Steps.................................................................................................................................................. ..51

7.5.1 Update Custom table : ZPCARDENCRYPT..........................................................................................................517.5.2 Update Custom table : ZZRFCDES............................................................................................................... ........517.5.3 Synchronize Encryption for SRM...........................................................................................................................517.5.4 IPC Settings.............................................................................................................................................................52

7.6 CRM Specific Steps......................................................................................................................................... ......... ...53

7.7 Control-M Specific Steps............................................................................................................................. ......... ......55

7.8 FireFighter Installation................................................................................................................................................55

8.BEFORE RELEASING SYSTEM TO BUSINESS (POST CHECKOUTS).....................568.1 General Check for All Systems..................................................................................................................................578.1.1 Valid license for PRD in DR-systems................................................................................................................. .578.1.2 SAP access PRD Cl..............................................................................................................................................578.1.3 Oracle Alert Log...................................................................................................................................................578.1.4 DB12 Backup Logs.................................................................................................................................. .........578.1.5 DB13 DBA Planning Calendar............................................................................................................. ......... ...578.1.6 OS07.....................................................................................................................................................................578.1.7 RZ70 -> Ensure successful transmission of data to SLD.....................................................................................578.1.8 RZ03 -> No Configuration Alerts.............................................................................................................. ..........578.1.9 SICK SAP Initial Consistency Check............................................................................................................ ...578.1.10 SMICM -- ICM Monitor........................................................................................................................ .......... ...578.1.11 SM12 Check Lock Entries......................................................................................................................... .......57

8.1.12 SM13 Check Update Requests..........................................................................................................................578.1.13 SM21 System Logs............................................................................................................................ ......... ......57



6/63

8.1.14 SM37 Batch Jobs...............................................................................................................................................578.1.15 SM51 Check SAP Servers.................................................................................................................................578.1.16 SM50 Check Work Processes............................................................................................................. .......... ....578.1.17 SM59 -> ABAP Connections -> Check connectivity to other SAP system in the landscape..............................578.1.18 SMLG Check SAP Logon Groups................................................................................................................. ...578.1.19 SPAD -> Print to any printer other than LOCL and validate successful printing using SP01.............................57

8.1.20 ST22 Check SAP Dumps............................................................................................................................... ...578.1.21 SM58 Check Transactional RFCs.................................................................................................................... .578.1.22 SMQ1 Monitor Outbound Queue......................................................................................................................578.1.23 SMQ2 Monitor Inbound Queue................................................................................................................. .......578.1.24 http://hostname:5xx00 -> Check system Information -- Check System Information and Patch levels....... ..... .57

8.2 ECC Specific...............................................................................................................................................................57

8.2.2 SM59......................................................................................................................................................................578.2.3 KGS......................................................................................................................................................................588.2.4 FAX......................................................................................................................................................................588.2.5 ITS Check.............................................................................................................................................................58

8.3 BW Specific....................................................................................................................................................... ........58

8.3.1 RSA1 -> Source System -> Right Click individual system and select Check.................................................... ...588.3.2 Check for BI UDC..................................................................................................................................................58

8.4 SRM Specific ......................................................................................................................................................... ...598.4.1 SM59 Tcode Check for Live Auction........................................................................................................ ........598.4.2 SMOKE TEST for Live Auction ..........................................................................................................................59

8.5 XI Specific .................................................................................................................................................................61

8.5.3 TIBCO SXMB_IFR.............................................................................................................................. .......... ....618.6 SCM Specific Checkouts..................................................................................................................................... .....61

8.6.1 LC10 - Check for LiveCache ......................................................................................................................... ......628.6.2 JDBC Check..........................................................................................................................................................628.6.3 Analyse LiveCache & LCA Objects ................................................................................................................. ...628.6.4 Optimizer Installation Tests ................................................................................................................ ......628.6.5 Check for BI UDC.................................................................................................................................................628.6.6 APO Consistency Check.............................................................................................................................. .........62

APPENDIX.............................................................................................................................62Steps to reset the SDM password......................................................................................................................................62

Steps to synchronize SDM Server ....................................................................................................................................63

To recreate PSAPTEMP table space................................................................................................................................63

Starting Java SDM server..................................................................................................................................................63

Stopping Java SDM server:...............................................................................................................................................63



7/63

1. Pre-Database/SAP RefreshMost of the steps under this section will be performed at least One week prior to

Refresh .

1.1 Post a System Message about Scheduled DowntimeUse SM02 T-code to Post a System Message and let users know about thescheduled downtime.

Example:IMPORTANT : System will be unavailable from 10-Oct-2007 at 5pmCST to 15-Oct-2007 at 10am CST for a System Refresh. Please, plan your workaccordingly.

1.2 SaplicenseLogon to as adm on Source SystemCheck your sap licensesaplicense show

Export the saplicense information to a file under adm home directory.cd /home/saplicense show > saplicense.SID

1.3 Confirm Passwords for Source/Target system with Security teamDDIC password in Client 000DDIC and BASIS-BATCH in default client.



8/63

1.4 Stage Instance Specific Information before Volume Group is

recreatedValidate staging File System is available. This should return a valid File Systementry.

bdf /usr/sap/put_refresh

Copy the required directories to the staging Directory - /usr/sap/put_refreshcd /usr/sap/put_refrersh

mkdir -p oracle/T_SIDmkdir -p usr/sap/T_SID/DVEBMSxx

mkdir -p sapmnt/T_SID

cd /oracle/tar -cvf /usr/sap/put_refresh/oracle/U11/102_64.tar 102_64

{Note: To check the tar file structure tar -tvf .tar}

cd /oracle/tar cvf /usr/sap/put_refresh/oracle/U11/dotastrik.tar .[a-z]*cd /sapmnt/

tar -cvf /usr/sap/put_refresh/sapmnt/U11/profile.tar profilecd /usr/sap//DVEBMGSxx

tar -cvf /usr/sap/put_refresh/usr/sap/DVEBMGSxx/igs.tar igs

cd /oracletar cvf /usr/sap/put_refresh/oracle/client.tar client

tar -cvf /usr/sap/put_refresh/oracle/oraInventory.tar oraInventoryTeam - Please add any other directories or files that you want to save off beforethe Volume Group is recopied with Target Volume Group.

1.5 Export User Master dataLog on to source client with SAP

Run Transaction SCC8.

Select profile SAP_USER

Select target system

start immediately

Make note of the SIDKTxxxxx transport number from the pop-up screen. The data and

cofiles will be created with this numbers.

Check the appropriate export log to validate if the export was successful.SCC3 exports check for the current export logsAlways, logon as adm at the OS level and validate the recent creation of cofiles & datafiles. cd /usr/sap/trans/cofiles

ls ltrThe KTxxxxx.SID file should have been created with recent time stamp. cd /usr/sap/trans/data

ls ltr

The RTxxxxx.SID file should have been created with recent time stamp.



9/63

1.6 Transport Printer DefinitionsRun Transaction SPAD

Output Devices Display

Go to Edit transport transport all

Note down the request number Release the Transport

1.7 Transport RFC DefinitionsCreate a workbench request in SE01Go to change mode of your request

Include the following object Name with Program ID : R3TR Object Type :TABU

RFCATTRIB

RFCDES

RFCDESSECU

RFCDOCNow double click on each of your RFC table entry and it will open another screenand click on Insert Row button.

Give*as input (i.e. all the keys corresponding to that table are taken)Now save the transport requestNote down your request numberRelease your request.

1.8 Logical System Definitions

Run Transaction BD54Take a screenshot of Logical Systems Definition

1.9 Partner ProfileRun Transaction WE20

Take a screenshot of Partner Profile, specifically all Partner Type LogicalSystems

1.10 IDOC Port DefinitionsRun Transaction WE21Drill Down on Transactional RFC, Take a screenshot of RFC Destination PortAssignment

1.11 Client DefinitionsRun Transaction SCC4.

Take a screenshot of clients overview to note the Client Description andsettings.



10/63

1.12 Trusted SystemsRun Transaction SMT1.Take a screenshot of trusted systems to note the Client Description.This needs to be reconfigured during post refresh activities.

1.13 Trust Manager Portals CertificatesRun Transaction STRUSTSSO2.Check the existing public-key certificate of Portal Servers in component system'scertificate list. This needs to be reconfigured during post refresh activities.

1.14 Integration Engine Configuration

Run transaction SXMB_ADMDouble Click on Integration engine configurationTake screenshot of configuration data

1.15 Maintain SLD Access dataRun transaction SLDAPICUST

Take a snapshot or make note of the entries.

1.16 SLD Bridge Info ABAP/JAVA

1.16.1 ABAPRun Transaction RZ70

Take screenshot or note the SLD Bridge Host and Service Info.

1.16.2 JavaLogon to Visual Admin

Go to services Select SLD Data Supplier Note SLD Data Collection SettingsNote CIM Client Generation Settings

1.17 Port Maintenance IDOC AdaptersRun transaction IDX1Note all the ports and corresponding RFC destinations or take a screenshot of thesame.

This needs to be reconfigured during post refresh.

1.18 IDOC Adapter Metadata OverviewRun transaction IDX2Note all the ports and corresponding RFC destinations or take a screenshot of thesame.

This needs to be reconfigured during post refresh.



11/63

1.19 Distribution Model ViewRun transaction BD64

Take a snapshot or make note of the entries.

1.20 Maintain CRM RFC ParameterThis entry is maintained in table CRMRFCPAR in all sender/receiver systems(R3/BW etc)Verify the entries take a screenshot.

1.21 Validate HP OMS entry in SPADUse transaction SPAD

Select Full Administration button

Go to Output Management Systems tab

Check Real Output Management Systems by clicking on Display Double click on HP-DAZEL and validate OMS Configuration info

For Eg. QA2, it should be: -N -DDAZELNS=DAZEL:hpomdev.d,qa1oms1[4008]For Eg. U11, it should be: -N -DDAZELNS=DAZEL:hpompre.d,preoms1[4007]

Take a note or screenshot of the settings and if different add its entry onprevious line for the specific SID.

Please Add SBX specific info

1.22 Display / Note Logon Group DefinitionsRun Transaction SMLGTake a screenshot of currently configured logon groups

1.23 Check operation modesRun Transaction RZ04

Take a screenshot of currently defined OP modes

1.24 Check for ITSRun transaction SM30

Give the table name TWPURLSVR

Click on Display

Double click on your Logical system host nameTake a screen shot of that so that after the refresh we can reconfigure the same.

1.25 Verify DBA Planning Calendar

Run transaction DB13.Note the scheduling period for DBA jobs or take screenshot.



12/63

1.26 XI Specific Steps

1.26.1 Export SLD InformationLogon to xiRun TransactionSLDCHECK

Select Administration

Select contents Export All (in export line)

save the file to your desktop.

1.26.2 Export the Repository server informationLogon to Windows terminal server

Logon to your Target systemRun transaction SXMB_IFRSap Exchange Infrastructure Page will be opened

Select Integration builderLog on with xisuperIntegration builder page will opened

In objects tabHere a list of software components will be present thereSelect the software componentGo to toolsClick on Export Design ObjectsSelect the icon at the end of the software component version fieldA list of software components will be displayedExpand your software componentSelect your software component version

Click on ApplyClick on continue

Now select objects list field will be displayedExpand your object setSelect all objects of software component versionClick on Finish ButtonExport all your repository objects using the above procedure.

The objects will be exported to/sapmnt//global/xi/repository_server/exportAfter the export is completed move all the objects from export directory to atemporary directory to import them later after the JAVA install. At that point,move these files to the following directory to import /sapmnt//global/xi/repository_server/import



13/63

1.26.3 Export the Directory server informationNow go to your Sap Exchange Infrastructure PageClick on Integration Directory linkLogon with xisuperIntegration builder page will openedIn the scenarios tab select your Configuration ScenarioGo to toolsSelect Export Configuration ObjectsSelect mode will be displayed

Say continueSelect object set all objects of a ScenarioSelect your business scenarioSay okClick finishExport all your directory objects using the above procedure.

The objects will be exported to/sapmnt//global/xi/directory_server/exportAfter the export is completed move all the objects from export directory to atemporary directory to import them later after the JAVA install. At that point,move these files to the following directory to import -/sapmnt//global/xi/directory_server/import

1.26.4 Configure CMS SetupVerify if the following parameters are set to true in Integration Builder section..

com.sap.aii.ibdir.core.cms.enableTransportWizardcom.sap.aii.ibdir.core.enable.TransportWizardcom.sap.aii.ibrep.core.cms.enableClTransportcom.sap.aii.ibrep.core.cms.enableTransportWizard

1.26.5 SLD DATA supplier and BridgeLog on to http://url:port/sld go to administration and select data supplierbridge.Note down the configured SLD bridges.

1.26.6 SLD Business SystemsLog on to http://url:port/sld go to Technical and then Business systemsNote all the Technical and Business Systems configured along with transportgroups source and target. This needs to be reconfigured during post refresh.



14/63

1.26.8 XI Message Archiving & DeletionCheck Existence of physical directory at the operating system level forstoring the archived XI messages at the following location.As always, make

sure that the /interfaces directory and the FILEPORTS are correctlychanged.

Path: interfaces//client/out/ready/archiving/

Verify logical path in TCODE FILE and take snapshots at the locations below:

i) Logical File = ARCHIVE_XI_DATA_FILE

double click

Specify physical/logical file path based on pre-refresh screenshotTake snapshot* Validate Definition of variable: FILENAME and SYNTAX GROUP Definition

** Validate Definition of variable FILENAME** Validate Syntax group Definition

Take snapshot in both the cases

ii) Transaction: SXMB_ADM Schedule Archiving Job

Archive Administration

Make sure the object is BC_XMB

Click on Customizing.

Go to Cross-Archiving Object Customizing

Technical Settings[Take ScreenShot]

iii) Transaction SXMB_ADM Archiving Object Specific Customizing

Technical settings.

Configure as per pre-refresh screenshot.* Make sure the Delete Jobs is set to Start

Automatically and alogical File Name.

iv) Transaction : SXMB_ADM

Define Interfaces for Archiving and Retention Periods[Take snapshot]

Click on Retention periods[Take snapshot]



15/63

1.27 BI Specific Steps

1.27.1 Conversion of Logical System NamesLogon to BIRun Transaction RSA1Select Tools -> Conversion of Logical System Names

Take a screenshot of conversion Table to reinstate after refresh beforetransports are applied

1.27.2 UDC Connection Container SettingsTelnet to BI Central instance as adm using Reflection or Hummingbird X-Term session:

cdDcd j2eecd admin

./go (make sure an x-client is used with DISPLAY variable set up)select the Central Instance Server in the left pane and open it upselect Services -> JDBC ConnectorNow select Connector Container in the left paneSelect the jdbc connector container, e.g.,SDK_JDBC_TDSDK_JDBC_TD_ISCP

Go to tab Managed Connection Factory and then Properties for all thespecified connector containers,

Note down the following for each of the Connectors Document the FixedSchema

Find the password for Password field (Obtain Password Prior to refresh) anddocument it for each landscap in this document for future refreshes.

Document for URL

Document for UserName



16/63


17/63

1.28.5 Stop/check CIF queue/n/SAPAPO/OM17

/nWE02 check the failed iDOC

1.28.6 LiveCache consistency/n/SAPAPO/OM13

1.28.7 Backup liveCacherun dbmgui > connect source system > make complete backup to the filesystem>validate the backup file from unix > rename the file to xx.orig

Check and Verify Launch MaxDB dbm GUI from your laptop/PC

Click on backup

Select complete data backup and click next.

Connect to source LC instance database server: FQDN of database server

database name: username:control

Password:control

Backup file will be created under default path

/sapdb//sapbackup/full._COM

FTP the source file (i.e. /sapdb//sapbackup/full._COM ) tothe target system to the following location

/sapdb//sapbackup/

1.29 SRM Specific

1.29.1 Copy the SRM IPC parameter file

cp /usr/sap/ipc/lib/properties/parameters.xml/usr/sap/put_refresh/srm_.parameter.xml



18/63

Please Add this specific info for all the landscapes

1.30 Display/Note Logical Ports

Run transaction LPCONFIG to confirm the settings or take screenshot of thelogical port.

Here Port for SmartMapper Lookup double click and verify the parameter URLpath.

Example --http://PHGP0159:14810/XrefLookup_WS/Xref_Lookup.serviceagent/Xref_LookupEndpoint

This settings needs to be reconfigured during post refresh.



19/63

2 Database Backup

2.1 Oracle Database Backup Source SystemBased on DB Refresh requirement, we will perform one of the following backups.

Disk_to_Disk_Copy

Offline Backup

Online Backup

2.2 SCM maxDB liveCache Backup - Source System

Rename file from

/sapdb//sapbackup/full._COM to/sapdb//sapbackup/full._COM***** make sure to follow proper case while renaming file name.*****



20/63

Toggle source database to ADMIN mode- Connect to target LC instance(QL2,UL1,DL2 etc) from OS level and log in asadm- Connect to DBM client by typing the command

dbmcli d -u control,control

-You will be connected to dbm client on that instance.db_admin

Launch dbm gui again and connect to target LC instance -Click on recovery with initialization

-restore a medium-fullfileClick Start

Log on to SCM server and go to transaction LC10.

Click on Integration and change all settings corresponding to the targetsystem, reset password for CONTROL and SAPQL2.

3. Oracle Database Restore TargetSystem

3.1 Reproduce Source System environment on Target SystemCreate soft link for Source Systemln s /oracle/ /oracle/Validate user exists on the target system.Change the ownership of all /oracle/ files to source system ora.To change the ownership we need to be the root.Now login as rootsudo su Change the ownership

chown R ora:dba /oracle/



21/63

3.2 Add Source system in /etc/hosts fileWork with the OS team to make sure you have an entry for the source system inthe target systems/etc/hosts file. This is needed to avoid affectingthe source system during the re-build activities.

3.3 Start database as Source SystemLogon the target system as orasu ora

sqlplus / as sysdbastartup;

exit

3.4 Create Control File

Logon the target system as orasu orasqlplus / as sysdbaalter database backup controlfile to trace;exit

cd /oracle//saptrace/usertraceGet the latest file you just created through sqlplus command

vi ` ls ltr |tail -1|awk {print $9} `Go to the end of the file and scroll up till you see the following textSTARTUP NOMOUNTScroll one line up and delete all the lines from the beginning of the file to thecurrent line.:1,.dOnce you have deleted the lines, your first line should beSTARTUP NOMOUNT

Now replace the Source_SID with Target_SID on all the lines by running thefollowingcommand.:%s,Source_SID,Target_SID,gNow search the string CREATE in the file and replace the following line:/CREATECREATE CONTROLFILE REUSE DATABASE ""RESETLOGS ARCHIVELOGWithCREATE CONTROLFILE SET DATABASE ""RESETLOGS

For editing the line do the following, On the following line go to end of the lineCREATE CONTROLFILE REUSE DATABASE ""



22/63

RESETLOGS ARCHIVELOG$Move your cursor upto word ARCHIVELOG by using key h on your keyboarddwand move your cursor upto word REUSE and by using h on your keyboard

dwnow switch to insert mode iNow write SETNow your modified command looks likeCREATE CONTROLFILE SET DATABASE ""RESETLOGSNow search the string RECOVER in the file and replace the following line:/RECOVERRECOVER DATABASE USING BACKUP CONTROLFILEWithRECOVER DATABASE USING BACKUP CONTROLFILE until cancelFor editing the line do the following

Go to end of the line and append as follows$auntil cancelNow your modified command looks likeRECOVER DATABASE USING BACKUP CONTROLFILE until cancelNow save the file as/tmp/rename.sql using the following command::w /oracle//rename.sql

3.6 Copy back the pre-staged files from the staging Directory -

/usr/sap/put_refreshsudo su cd /oracle/rm fr 102_64

cd /oracle/


23/63

3.7 Change the ownership of all files to target system

3.7.1 To change the ownership we need to be the rootLogin as root

sudo su Remove exe Directory from the Instance Directories. This will be recreated withthe J2EE Install.cd /usr/sap//SCSxx

rm fr exe

cd /usr/sap//DVEBMGSxxrm fr exeRemove and re-create /usr/sap//SYS/exe/run Directory

cd /usr/sap//SYS/exe/

rm fr runmkdir run

3.7.2 Change the ownershipchown R ora:dba /oracle/

chown Radm:sapsys /usr/sap/chown Radm:sapsys /sapmnt/

3.7.3 Set the permission for the new kernel filescd /sapmnt//exe

chown R adm:sapsys *chmod R 755 *

3.7.4 Copy the files from /sapmnt//exe to

/usr/sap//SYS/exe/run Directorycd /sapmnt//exe

cp rp * /usr/sap//SYS/exe/run/.

3.7.5 Now run the saproot.sh script./saproot.sh Note: saproot.sh script file updates the ownership and permissions of files underthe following path: /usr/sap//SYS/exe/run

3.7.6 Now copy the files from /usr/sap//SYS/exe/run to

/sapmnt//execd /usr/sap//SYS/exe/runcp rp * /sapmnt//exe/.



24/63

3.8 Recover Database as Target System

3.8.1 Recover the database on target system as oraCheck the Online Logs permission in /oracle//oraarch directory. It should be set

as:Owner : ora Group : dba

Sqlplus / as sysdba

@rename.sqlThis might ask for multiple Online logs to recover; so, just keeps ENTER and watch

carefully the screen.

cancelNote:- here it will ask us for CANCEL option at the end of command execution.Say CANCELalter database open resetlogs;

Open another telnet session to tail the rename.sql file and run the last sqlcommand from the rename.sql file to create the PSAPTEMP tablespace. Here isthe example of the command you need to run:

ALTER TABLESPACE PSAPTEMP ADD TEMPFILE'/oracle//sapdata3/temp_1/temp.data1' SIZE 629145600 REUSE

AUTOEXTEND OFF;

3.8.2 Restart the database to make sure that DB starts correctlyshutdown immediate

startup

3.8.3 Create the ops$adm users and grant permissioncreate user ops$adm identified externally

default tablespace psapdatusr temporary tablespace psaptemp;

Grant dba,connect,resource to ops$adm;create user ops$ora identified externally

default tablespace psapdatusr temporary tablespace psaptemp;

Grant dba,connect,resource to ops$ora;create table ops$adm.sapuser as select * from

ops$adm.sapuser;exit



25/63

3.8.4 Test the connectivity to the database as user admsu - admR3trans dThis should give the return code of (0000) for successful logon to database.If it was not able to connect /logon to database it will throw a return code 0008.

3.9 Create the Oracle Password File (OPTIONAL)Logon to UNIX level as ora

sqlplus / as sysdba

create pfile from spfile;shutdown immediate;Using vi add the following entry

"remote_login_passwordfile = exclusive"Create the Oracle password file:

$ORACLE_HOME/bin/orapwd file=$ORACLE_HOME/dbs/orapwpassword= entries=100(Use password for system)Logon to UNIX level as ora

sqlplus / as sysdba

create spfile from pfile;

startup

4 Delete Target Java Installation

4.1 **Delete the currently installed JAVA Installation**Make sure your Database is down for this step, which it should be sinceyou did not start SAP as yet.

4.2 Delete the following directories on Target DB server

Su -admcdDrm fr /usr/sap//DVEBMGS/SDM

rm fr /usr/sap//DVEBMGS/j2eerm fr /usr/sap//SCS

rm fr /sapmnt//exeU(If it exists.)Note: - The directory exeU is only present in versions below 640.

4.3 Delete the following directories on each of the application server

/usr/sap//D/j2ee



26/63

4.4 Delete the JAVA profilecdprorm -f /sapmnt//profile/_SCSxx_hostname

rm - f /sapmnt//profile/START_SCSxx_hostname

4.5 Drop your j2ee schemaLog on as user oraStart sqlplus and connect to the database.

sqlplus /nologconnect / as sysdba

startupNote:- when sqlplus /nolog is executed we get the error connected to an idleinstance. This means the database is not connected. So at that time we need tostart the database using startup command. Enter the following command to

delete the database objects of the database schema:drop user SAPDB cascade;Enter the following command to get the name of schema of the associated data

files in the systemselect file_name from dba_data_files where tablespace_name =

'PSAPDB';

4.6 Now drop the table spaces as they are emptyEnter the following command to delete the tablespace of the database schema:drop tablespace PSAPDB including contents;

Exit sqlplus:shutdown immediate

exit

4.7 Delete the data files of tablespace PSAPDB from

the systemrm rf /oracle//sapdata4/db_1

Now your java instance is completely deleted.



27/63



28/63

5 Post SAP Refresh

5.1 Install sap licenseLogon as adm

su admBrowse to the directory where the license backup file is kept

more .saplicensesaplicense install

5.2 Set Background Process as ZeroLogon as adm

su adm

cdproEdit SAP Instance Profile

vi _DVEBMGS_find parameter rdisp/wp_no_btccomment out # rdisp/wp_no_btcappendrdisp/wp_no_btc = 0To make background process = 0

5.3 Cleanup /sapmnt/SID/globalBefore starting SAP remove the JOBLOG & SLOG files in the /sapmnt/SID/global/directory on the target system.

cd /sapmnt//globalrm fr *JOBLG*

rm fr *SLOGJ*rm -fr WF_LOG*

5.4 STARTSAPstartsapLogon to your sapWe see the default client of which is configured in instanceprofile

Remove the default client number and type default client number.Provide the logon information of

5.5 Reinitialize TMS after DB copylogon to 000 as DDIC

Run transaction SE06 database copy or database migration

Reinstall CTS yes

change original to yes

cts not configured ok

delete the TMS Configuration yesdelete all versions of transports yes



29/63

delete transport routs yes

5.6 Delete Jobs** WARNING: MAKE SURE YOU ARE IN TARGET SYSTEM/CLIENT **

Execute transaction SM37Delete all released jobs from the system

5.7 Revert background processes to originalLogon as adm

su adm

cdpro

5.7.1 Edit instance profile

vi _DVEBMGS_Find parameter rdisp/wp_no_btcReset to original values

5.7.2 Stop SAP serverstopsap

5.7.3 Start SAP

startsap

5.8 Re-initialize JobsAfter the database restore has successfully completed, the import jobs used bythe tp command may not work properly. Proceed as follows:Logon to SAP in client 000 as DDIC and run transaction SE38Execute program RDDNEWPPSelect NormalA message will show up in the status bar which indicates the job has beenscheduled.

5.9 Schedule Standard JobsGo to transaction SM36 as BASIS-BATCH.Schedule all standard jobs

5.10 Configure SAP Profile Parameter FilesAfter the database restore, the active profiles listed in the SAP system will be

from the old hostname. These profiles need to be deleted and the profiles fromthe OS need to be re-imported. Proceed as follows:



30/63

Run transaction RZ10Delete source system profiles:Click the Profile drop-down box and choose a profile (this process must be donefor each profile).Select menu items: Profile -> Delete -> All versions of a profile.

Click Yes to first prompt to update the databaseClick No to delete the files from the Op. Sys. LevelClick green check on all versions deleted screenRepeat steps 1-3 for all source system profiles listed in the Profile drop-down list.Import all profiles from UNIX by selecting menu items: Utilities -> Import Profiles-> of active servers.Green back arrow.

5.11 Configure Op ModesAfter the database restore, the target system will contain Operation Modes from

the old hostname. These Op Modes need to be deleted and the correct OpModes need to be imported. Proceed as follows:Run transaction RZ04Select Instance/OpmodesSelect a server name and press SHIFT F2.Do this for each source system op mode listed.Create the target system op mode configuration(s) by selecting the menuitems Settings -> Based on Current Status -> New Instances -> GenerateClick the SAVE button.

5.12 Check System LogsCheck the system logs to see if there were any unusual error messagesgenerated while the SAP system was started back up. Proceed as follows:Execute transaction SM21

Select menu items System logs -> Choose -> All remote system logs.Set the from date/time fields to the date and time just prior to starting the

SAP system.Select the All messages radio button.Click the Reread system log button.Review the system messages. Take action on any messages that may look

suspicious.

5.13 Fix Logon Group NamesRun transaction SMLGAdd the newly added systems to existing LOGON groups.Highlight the New Hostname Entries.Click the Assign Group button and assign the Logon groups respectively.Highlight the Old Hostname Entries.Click the Delete button.Save.Note: Do not delete the groups instead of that delete only instances assigned. If

you deletethe groups both the groups and instances will be deleted.



31/63

Re-execute transaction SMLG once again and validate the logon groupconfiguration.

5.14 Fix Server Group Names

Run transaction SM61Click pencil for change mode, click cleanup list.Select Job-ServerGruppenClick Create Group

Type GENERAL, click continueExpand All Groups folderHighlight GENERAL, click on + assignmentDrop down instance name box, select only application serversDo this for each application server available, but if no app servers are configuredfor the instance, use the CI.Once all the new entries are added. Delete the Source System Entries.

5.15 Import User Master DataImporting the previously exported Users from the Pre-Client Copy StepsRun T-Code: STMSClick on the transport button (Truck)Double click on the System name

On the toolbar, goto ExtrasOtherAddAdd the transport request number.Click on the transport button (Half Truck) after selecting the added request.Provide target Client number and continue.

5.16 Post user master importLogin into your target clientRun Transaction SCC7From Menu options choose start immediately.SCC3 check your logs

5.17 Import Printer, RFC Definitions

Run Transaction SPADSelect menu items utilities for output devices delete all.Run Transaction STMS

Select menu items overview imports double click on target system

Select your request. Import request give client no okClick refresh until your truck symbol is lost and the transport is successful.Repeat this transaction for all the transportsRun transaction SPAD

Select menu items utilities for output devices assign server.Run transaction SM59Validate RFC definitions.



32/63

5.18 Fix ITS InformationRun transaction SM30Edit the tableTWPURLSVR by selecting the change option.Change the hostname reflecting the new hostname.Save

5.19 Delete Local CUA/Detach a Satellite ClientDelete the target hostname and system number under SM1 trusted connectionentry.Run transaction SE38Execute the report RSDELCUA.Select Child System -> CLNT500 and unselect Test -> execute.Use the Green back arrow to go to the previous screenRe-execute the last step to invalidate the CUA contents.

5.20 Update HP OMS entry in SPADUse transaction SPADSelect Full Administration buttonGo to Output Management Systems tabCheck Real Output Management Systems by clicking on DisplaySelect change and update HP-DAZEL with the new OMS Configuration infoFor QA2, set it to: -N -DDAZELNS=DAZEL:hpomdev.d,qa1oms1[4008]For UA1, set it to: -N -DDAZELNS=DAZEL:hpompre.d,preoms1[4007]Save

5.21 Disconnect from previously connected P21(For all systems that are source systems of BW: ECC, SRM, CRM)

Run Transaction SE37Enter RSAP_BIW_DISCONNECTHit Test/Execute (F8)Enter data into the following fields:I_BIW_LOGSYS: P21CLNT500I_OLTP_LOGSYS: I_FORCE_DELETE: XHit execute (F8)

5.22 Converting Logical SystemsRun transaction BDLSEnter Old logical system name in the Old logical system name fieldEnter New logical system name in the new Logical system Name fieldSelect Conversion of Client-Dependent and Client-Independent tables.Uncheck Test RunUncheck Existence of New Names in Tables.Execute

Press Return again, if any warnings are encountered.Rerun this transaction for all the Target Logical System entries.Note: BDLS should be executed for each existing connection to other



33/63

components in the respective clients. Example, if the logical system client says110, BDLS should be executed in client 110 for each logical system connected tothe system. This rule applies currently to ECC and SRM where there are multipleclients.Note: Check the logs in SLG1 for possible errors.

BW Systems: Execute RSBKDTP_BDLS via SE38 for each source system in RSA1.

Old Logical System Name: (ex. P11CLNT500, P31CLNT500, etc)New Logical System Name (ex. Q11CLNT500, Q31CLNT500, etc)

5.23 Logical System NamesRun Transaction BD54Verify and Redefine the logical systems as per the screenshot during pre-refresh.

5.24 IDOC Port DefinitionsRun Transaction WE21Adjust the port assignment / RFC Destinations as per the pre-refresh screenshot.Note: During port creation, use the system provided port numbers.Remove any ports that were pointing to production.

5.25 Partner ProfileCreate and adjust the Logical System/RFC Destinations as per the pre-refreshscreenshotActivate the partner profiles if set to I set it to AIf a particular message type is not associated with the IDOC type, maintain the

associationin WE82 transaction.

5.26 Create Trusted SystemRun Transaction SMT1Reconfigure the trusted systems as per the pre-refresh screenshot/description.Delete the entries reflecting Source System entries.

To create the Trusted systems you need to have access to the remote systemswith proper authorization in the case of QA2 it was SA2 and SM1. SM1 systemwill be created by Kevin Flattery.

5.27 Republish ServicesRun Transaction SE38

Enter Program name W3_PUBLISH_SERVICES.Execute and follow the screens to republish the services.

Run transaction SICFSelect the necessary services one at a time

Deactivate the ServicesActivate the Services.



34/63

Make sure that the SAP GUI service was enabled and working.

5.28 Trust Manager Portals CertificatesDelete existing certificates and import portal certificates corresponding to target

system.Run Transaction STRUSTSSO2Check the existing public-key certificate of Portal Servers in component system'scertificate list.Delete the Certificates.Reconfigure/Import the appropriate certificates in component system as duringpre-refreshPortals Certificates will be imported by Portal administrators.

5.29 Integration Engine Configuration

Run transaction SXMB_ADMDouble Click on Integration engine configurationReconfigure integration engine data as per the pre-refresh screenshot.

5.30 Port Maintenance IDOC AdaptersRun transaction IDX1Configure all the ports and corresponding RFC destinations as per pre-refreshscreenshot.

5.31 IDOC Adapter Metadata OverviewRun transaction IDX2Configure all the ports and corresponding RFC destinations as per pre-refreshscreenshot.

5.32 Verify Distribution Model ViewRun transaction BD64 and check pertinent model views.Verify the same pre-refresh distribution model views existing after requestimport.

5.33 Delete Workload Analysis Logs for Old ServerRun Transaction ST03Change your user mode to Expert Mode.

Collector and Performance DB Performance Database Monitoring Database

contentsDouble click on contents.

In the Host Column select the old host name Delete Server Confirm Delete.To make the changes effective save it after deleting the server. To view thechanges go to the first screen and come back after saving the changes.



35/63

5.34 Reset the passwords for the following usersRun transaction SU01Reset the password for the following users from the default client. These userswill be recreated during the JAVA Install.

J2EE_ADMIN

J2EE_GUESTSAPJSFXI* (Only on XI systems)LD* ( Only on XI systems)

5.35 Client DefinitionRun Transaction SCC4Change the client description to reflect as per pre-refresh description.

5.36 Maintain DBA Planning CalendarRun transaction DB13 as BASIS-BATCH.Setup DBA jobs as per the pre-refresh screenshot.

5.37 qRFC MonitorRun transaction SMQR& SMQSDelete old monitor and setup new monitor with correct system name. .(Registration Table-> Reorganise)SMQ1, SMQ2 deleted the old queues and any old error entries .

SLD Specific

5.38 Maintain SLD connection parametersRun transaction SLDAPICUSTChange the connection parameters pointing to correct SLD source.

To change switch to editing mode and choose Insert Row. Specify the connectionparameters (host name, port, user, and password) and set this SLD server asPrimary. Only the entry marked as Primary is active.Save your entries.

Configure the SLD Data Supplier Service in the Visual AdministratorLogon as j2ee_admin/administrator in Visual Admin.Change and verify the connection parameters for SLD connection and CIM clientgeneration settings in SLD Data supplier service.Verify by triggering the SLD data load.

Maintain the SLD connection in ABAP systemsRun transaction RZ70Maintain SLD bridge host and gateway.Validate SLD Connection/configurationRun transaction SLDCHECKValidate the all the checks are successful.



36/63

5.39 Schedule XML Messages Delete JobsRun Transaction SXMB_ADM as user DDICGo to SXMB_ADM Define Interfaces for Archiving and Retention Periods Retention periodsRetention Periods for Asynchronous messages in the Database:XML Messages without Errors Awaiting Deletion: 30 DaysXML Messages without Errors Awaiting Archiving: 7 DaysRetention periods for Synchronous messages in the Database:XML Messages with Errors Awaiting Deletion: 7 DaysXML Messages without Errors Awaiting Deletion: 0 DaysRetention periods for History entries in the Database:History Entries for Deleted XML Messages: 35 DaysRun Transaction SXMB_ADM as user DDICSchedule Delete JobsCheck the settings and reconfigure as per the screenshot takenVerify Parameters: Period of Days set to 1.

Click on Job Overview (SM37) and verify the below jobs scheduled as pre-refresh.SAP_BC_XMB_DELETE_SAP_BC_XMB_HIST_DELETE_.

5.40 Attach a Satellite Client to CUALogon to Satellite ClientRun T-Code: SM59Validate entry for an ABAP system - SA2_SYSTEM.Validate entry for an ABAP system - SA2CLNT100.

Run T-Code: BD54Select New EntryDefine a new Logical System for CUA, e.g., SA2CLNT100Provide a description under NameSaveCreate a new transport or use an existing transport.

Run T-Code: SMT1Select Create ButtonSA2CLNT100 in Destination field.

Login to CUA SystemRun T-Code: SM59Validate ebtry for the ABAP system Q42CLNT500

Run T-Code: BD54Validate Logical System entry for Satellite System, e.g., Q42CLNT500Create a new transport or use an existing transport

Run T-Code: SCUAEnter the Satellite Instance Name, e.g., S11CLNT005 at the bottom of the list

Select SAVEYou will have to enter DDIC user-id and password for the satellite system on the



37/63

follow-up screenCheck the log file to validate that this command is completed successfully.

Logon to Satellite ClientRun T-Code: WE20

Validate that under LS, a Partner Profile for SA2CLNT100 is now defined and alsoSU01 has lesser number of available options.

6. Install J2EE and Apply Java Patches on CIPlease use the reset passwords, during the J2EE Installation

Important:This section activity should be performed on available Pepsico WindowsTerminal Server(WTS); because if your PC/laptop lost connection thenthere will be incosistency or might have to restart the process.

6.1 NW04S Java Install

Logon to available WTS

Run ProgramsReflection and open X-term to UNIX server where you are installingJ2EE.

Check X-Windows

xclockThis will display Clock Window; then you can proceed, otherwise you need to export

DISPLAY.

Run SAPINST to install Java ADD-in as below

SAPINST_USE_HOSTNAME=cd /install//xx/sapcd/sap/install/unicode/crm50/master/master/IM_HPUX_IA64/sapinst

On Initial Screen Selection

Usage Type Parameter

ECC SAP ERP 2005

BI SAP NetWeaver 2004s

CRM SAP CRM 2005

XI SAP NetWeaver 2004s

sapcd selection :



38/63

SAPCDSoftware Units Selection (Central Instance Java Add In for ABAP)

SLD Configuration Selection (Central Instance Java Add In for ABAP)

Usage Type No SLD Destination Configure Local SLD Register in Existing SLD

ECC YES*

BI YES*

CRM YES*

XI YES

Select No SLD Destination if XI SLD is not yet configured.

6.2 NW04 Install(SRM/SCM Specific)

Run SAPINST to install Java ADD-in as belowcd /install//xx/

sapcd/sap/install/unicode/crm50/nw04sr1/hpux/ia64/master/DVD_NW_04_SR1_Installation_Master/IM07_HPUX_IA64/SAPINST/UNIX/HPIA64sapinstSAPINST_USE_HOSTNAME=

On Initial Screen Selection

Usage TypeDescription

SRM SAP Netweaver 2004 Support Release 1 Java Add In for

ABAPOracle Central System Java system Finalization


DVD/CD Name Package Selection Installation

KERNEL DVD/sapcd/sap/install/unicode/crm50/kernel/kernel/KN_HPUX_IA64 SCS

/sapcd/sap/install/unicode/crm50/kernel_2/kernel2/KU_HPUX_IA64SCS & CI

JAVA DVD

NetWeaver

/sapcd/sap/install/unicode/crm50/java_usage/java/J2EE_OSINDEP DB & CI

/sapcd/sap/install/unicode/crm50/java_export/java_export DB

Usage Type Software Units

ECC None

BI None

CRM CRM-APP

JCRM

XI PI


39/63

SCM SAP Netweaver 2004 Support Release 1 Java Add In for

ABAPOracle

Central System Java system Finalization

SAPCD SelectionDVD/CD Name Package Selection

JAVA DVD

/sapcd/sap/install/unicode/nw04sr1/hpux/ia64/java_osind/DVD_NW_04_SR1_ SAP_Web_AS_JAVA/J2EE_OSINDEP

If the above directory doesnt work then please try thebelow:/sapcd/sap/install/unicode/nw04sr1/hpux/ia64/java_scs/DVD_NW_04_SR1_SAP_Web_AS_JAVA/SCS_HPIA64/SCS

Export /sapcd/sap/install/unicode/nw04sr1/hpux/ia64/export

SLD Configuration Selection (Java Add In for ABAP)

Usage Type No SLD Destination Configure Local SLD Register in Existing SLD

SRM YES*

SCM YES*

* Select No SLD Destination if XI SLD is not yet configured.* Port should be 39XX(XX is instance number).*Use ABAP system for users only.

6.3 Java Patches on CIBefore applying JAVA Patches we need to Update SDM (Software Deployment Manager) andJSPM (JAVA Support Patch Manager) to the Patch level we going to apply.E.g.: Applying JAVA SP11 on Q12 system.

6.3.1 Update SDMUpdate SDM to SP11 from OS Level.

Login as adm

cd /sapcd/sap/patches/nw04s/SP11/JAVA

cp * /usr/sap/ecctrans/EPS/in mkdir /usr/sap//DVEBMGS/SDM/test

cd /usr/sap//DVEBMGS/SDM/test

jar xvf /usr/sap/ecctrans/EPS/in/*.JAR

cdmod +x *

cd /usr/sap//DVEBMGS/SDM/program

./StopServer.sh

./sdm.sh jstartup mode=standalone

./update.csh (update SDM from test directory. Make sure SDM is not running while

executing this command )



40/63

While updating it asks for SDM installation directory. Give the installation directory as/usr/sap//DVEBMGS/SDM/program

After the SDM update is successful again go to

cd ../program./sdm.sh jstartup mode=integrated

./StartServer.sh./RemoteGui.sh

6.3.2 Update JSPMLogin as adm

./RemoteGui.sh

Enter SDM Password

Click on Deployment tab in SDM.

Browse to /usr/sap/trans/EPS/in System_Name like ecc bw srm

Select JSPM_-xxxxxxxx.SCA file Eg. JSPM12_0-10003470.SCA

Select the JSPM package and Deploy

6.3.3 Apply Java Patch on CILogin adm

cd /usr/sap//DVEBMGS/j2ee/JSPM

./go

Enter SDM administrator password.

Now, Select the following on this screen

Select a package type to apply

Single support packages (advanced use) NWDI Control

No NWDI control Click Next

Click Next

Check Queue and Deploy Queue to apply

6.3.4 Troubleshoot Errors while applying support package using

JSPM

If there is error while applying support package using JSPM, we need to identify the packagewhich got error.



41/63

Login to SDM and go to Undeployment tab.

Select the error package and undeploy completely.

Now apply the Error package using SDM tool from Deployment tab.

Make sure all the packages are deployed completely from URL

http://qa2q12.corp.pep.pvt:51200

Select the system information and check for successfully applied Support packs.

6.3.5 For Target systems (Eg: SRM, SCM) which have J2EE 640

(Oracle 9i) install on Oracle 10.2 DatabaseReview the Oracle Upgrade document and update the location of classes12.jar file under J2EESpecific entries from Post Steps.

http://qa2q12.corp.pep.pvt:51200/http://qa2q12.corp.pep.pvt:51200/


42/63

7. Post SAP System Specific steps:

7.1 XI Specific Steps

7.1.1 Configure the SLD Bridge (XI)As per prerefresh screenshot

7.1.2 Configure CMS SetupBased on pre-refresh steps, add the following parameters and set to truein Exchange Profile.

com.sap.aii.ibdir.core.cms.enableTransportWizardcom.sap.aii.ibdir.core.enable.TransportWizardcom.sap.aii.ibrep.core.cms.enableClTransportcom.sap.aii.ibrep.core.cms.enableTransportWizard

7.1.3 Run transaction SXMB_IFRVerify link for repository, runtime workbench etc.

This should point to http://host: (icm http port)/rwb

7.1.4 Activate XI related servicesRun transactionSE38

RSXMB_ACTIVATE_ICF_SERVICES Execute

7.1.5 Refresh XI CacheRun transactionSXI_CACHE.Select GotoSelect Adapter Engine CacheSelect line item under Adapter Engine Connection Data Cache sectionDelete

7.1.6 XI Message Archiving & DeletionCheck Existence of physical directory at the operating system level forstoring the archived XI messages. Path:interfaces/sid/client/out/ready/archiving/Verify logical path in TCODE FILE

Logical File = ARCHIVE_XI_DATA_FILE double clickSpecify physical/logical file path based on pre-refresh screenshot

Validate Definition of variable FILENAME Use TCode: FILE,

Create as per the screenshot from pre-refreshValidate Syntax group Definition create syntax group for operating



43/63

systems with the same syntax for file names and paths from pre-refreshscreenshot.Check assignment of syntax group to operating system as per thescreenshot.

Go to SXMB_ADM Schedule Archiving Job Archive Administration

Make sure the object is BC_XMB

Click on Customizing. Go to Cross-Archiving Object Customizing Technical Settings Configure as perpre-refresh screenshot

Go to Archiving Object Specific Customizing Technical settings.Configure as per pre-refresh screenshot. Make sure the Delete Jobs is setto Start Automatically and a logical File Name.

/* Go to SXMB_ADM Define Interfaces for Archiving and Retention

Periods Select the interfaces for Archiving using the Multiple selectionbutton and click on Flag interface for Archiving. */Note: The following database tables are key tables in archiving and

Deletion process:SXMSPMAST & SXMSPHIST

Go to SXMB_ADM as DDIC Schedule Archiving Job assign the StartDate, Period & Spool Parameter data as per the pre-refresh screenshot.Activate Archive infostructure,

Go to SXMB_ADM Schedule archiving jobs Archive Management

Information System Customizing Choose Archive Infostructure for

object SAP_BC_XMB Activate.

7.1.7 Configure JCo RFC provider using Visual Admin

Run Transaction SM59 and verify the below RFC connections in TCP/IP ConnectionsLCRSAPRFCSAPSLDAPIAI_RUNTIMEAI_DIRECTOR

Create following Destinations in Visual Admin Server Services JCo RFC provider



44/63



45/63

7.2 BI Specific Steps

7.2.1 Restore the Logical system destinations

Go to TcodeSE16 RSLOGSYSDEST select each LOGSYS and change theDestination to the target logical system name.Ex: LOGSYS DESTINATIONOriginal Value U51CLNT500 P51CLNT500New Value U51CLNT500 U51CLNT500In the Java side add the JCO RFC connection

Go to Visual admin server services JCo RFC Provider.Add BW_J2EE.

7.2.2 Restore the Table RSBKDTP entries to Target SID

Go to Tcode SE16 RSLOGSYSDEST select the entry and change the valueof field RSBKDTP:SRC from CLNT toCLNT

Go to Tcode SE38 RSBKDTP_BDLS and Execute.



46/63

7.2.3 Restore Source System ConnectionNOTE: In case the Source Systems have also been refreshed, make sure all therefresh activities have been completed before you restore the connection.Should not perform the restore for UD Connect Systems but can do the checks.

Verify the RFC Destination/Aleremote using Tcode SM59 Open the client using TCode SCC4.

Change System settings to modifiable in SE06 Tcode.

Go to TCode RSA1Source System

Restore all systems one by one, starting with BW System (Myself)

Specify the ALEREMOTE passwords for source and receiversystems when prompted.

Restoring all source systems may take some time to completedepending on number of extract structures/Data sources to bereplicated.

Rename the logical system name in RSA1 to maintain consistency.

Right click on the source system Select Rename

Change the name to appropriate value.

7.2.4 Maintain IDOC Sender/Receiver SystemsTable RSBASIDOC should have sender and receiver source systems rightlyconfigured.

Verify in SE16 appropriate entries for all sender and receiver systems.

7.2.5 RSA1 CheckIn RSA1 perform source system check by right click the source system

checkRecommendedPerform simple master data load from source to target to confirm the extraction

to be okay.

In RSA1 InfoSources select some Master data attribute. For example(0VENDOR_ATTR or 0BUSSYS or 0COMPCODE etc) select the the infopackageand trigger the load.Verify the successful completion of the load in transaction RSMON.

This helps in rectifying any ALE specific issues if still existing.

7.2.6 BI Integration into the PortalCall transaction SPRO and choose SAP NetWeaver->Business Intelligence->Reporting- >relevant Settings->BEx Web->Integration into the Portal.Follow the instructions for the following steps:Create RFC Destination in J2EE EngineImport BI Certificate to the PortalMaintain Portal Server Settings for the PortalCreate RFC Destination for the PortalImport Portal Certificate to BI System

sap refresh (2)

Documents