Sap Refresh

SAP
Document Revision History

Date
Version
1.0
1.1
Author
SAP Refresh Master Document
Change Description
Page 1 of 61
Text Heading Legend

System Color
ECC
BW
CRM
XI
SRM
SCM
1. PRE-DATABASE/SAP REFRESH....................................................................................7
1.1Post a System Message about Scheduled Downtime....................................................................................................7
1.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................................................................7
1.5 Export User Master data.............................................................................................................................................8
1.6Transport Printer Definitions.........................................................................................................................................8
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 ...........................................................................................................................................................9
1.13 Trust Manager Portals Certificates.........................................................................................................................9
1.14 Integration Engine Configuration.............................................................................................................................10
1.15 Maintain SLD Access data ........................................................................................................................................10
1.16 SLD Bridge Info ABAP/JAVA .............................................................................................................................10
1.16.1 ABAP ...................................................................................................................................................................10
1.16.2 Java .....................................................................................................................................................................10
1.17 Port Maintenance IDOC Adapters...........................................................................................................................10
Page 2 of 61
1.18 IDOC Adapter Metadata Overview..........................................................................................................................10

1.19 Distribution Model View............................................................................................................................................10
1.20 Maintain CRM RFC Parameter ...............................................................................................................................10
1.21 Validate HP OMS entry in SPAD ............................................................................................................................10
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........................................................................................................................................................11
1.26.1 Export SLD Information.......................................................................................................................................11
1.26.2 Export the Repository server information............................................................................................................12
1.26.3 Export the Directory server information..............................................................................................................12
1.26.4 Configure CMS Setup..........................................................................................................................................13
1.26.5 SLD DATA supplier and Bridge..........................................................................................................................13
1.26.6 SLD Business Systems.........................................................................................................................................13
1.26.8 XI Message Archiving & Deletion.......................................................................................................................13
1.27 BI Specific Steps.........................................................................................................................................................14
1.27.1 Conversion of Logical System Names.................................................................................................................14
1.27.2 UDC Connection Container Settings....................................................................................................................14
1.28 SCM Specific Steps....................................................................................................................................................15
1.28.1 Document connections to liveCache.....................................................................................................................15
1.28.2 Configure UDC (* same step as BI **).................................................................................................................15
1.28.3 Document Business System Groups (BSG).........................................................................................................16
1.28.4 qRFC Monitor......................................................................................................................................................16
1.28.5 Stop/check CIF queue..........................................................................................................................................16
1.28.6 LiveCache consistency.........................................................................................................................................16
1.28.7 Backup liveCache.................................................................................................................................................16
1.29 SRM Specific..............................................................................................................................................................17
1.29.1 Copy the SRM IPC parameter file .......................................................................................................................17
1.30 Display/Note Logical Ports.....................................................................................................................................18
2 DATABASE BACKUP.......................................................................................................19
2.1Oracle Database Backup Source System..................................................................................................................19
2.2SCM maxDB liveCache Backup - Source System......................................................................................................19
3.
ORACLE DATABASE RESTORE TARGET SYSTEM............................................19
3.1 Reproduce Source System environment on Target System...................................................................................20

3.2 Add Source system in /etc/hosts file.........................................................................................................................20
3.3 Start database as Source System..............................................................................................................................20
3.4 Create Control File....................................................................................................................................................20
3.6 Copy back the pre-staged files from the staging Directory - /usr/sap/put_refresh............................................21
3.7 Change the ownership of all <T-SID> files to target system.................................................................................22
3.7.1 To change the ownership we need to be the root...................................................................................................22
3.7.2 Change the ownership...........................................................................................................................................22
3.7.3 Set the permission for the new kernel files...........................................................................................................22
3.7.4 Copy the files from /sapmnt/<SID>/exe to /usr/sap/<SID>/SYS/exe/run Directory...........................................22
3.7.5 Now run the saproot.sh script................................................................................................................................22
3.7.6 Now copy the files from /usr/sap/<SID>/SYS/exe/run to /sapmnt/<SID>/exe....................................................22
3.8 Recover Database as Target System........................................................................................................................23
3.8.1 Recover the database on target system as ora<Target_sid> ..................................................................................23
3.8.2 Restart the database to make sure that DB starts correctly...................................................................................23
3.8.3 Create the ops$<Target_sid>adm users and grant permission..............................................................................23
3.8.4 Test the connectivity to the database as user <Target_sid>adm...........................................................................24
3.9 Create the Oracle Password File (OPTIONAL).....................................................................................................24
DELETE TARGET JAVA INSTALLATION................................................................24
4.1 **Delete the currently installed JAVA Installation**............................................................................................24

4.2 Delete the following directories on Target DB server..............................................................................................24
Page 3 of 61
4.3 Delete the following directories on each of the application server...........................................................................24

4.4 Delete the JAVA profile............................................................................................................................................25
4.5 Drop your j2ee schema..............................................................................................................................................25
4.6 Now drop the table spaces as they are empty.........................................................................................................25
4.7 Delete the data files of tablespace PSAP<Source_SID>DB from the system .......................................................25
5.1 Install sap license........................................................................................................................................................27
5.2 Set Background Process as Zero ..............................................................................................................................27
5.3 Cleanup /sapmnt/SID/global......................................................................................................................................27
5.4 STARTSAP ................................................................................................................................................................27
5.5 Reinitialize TMS after DB copy...............................................................................................................................27
5.6 Delete Jobs .................................................................................................................................................................28
5.7 Revert background processes to original................................................................................................................28
5.7.1Edit instance profile..................................................................................................................................................28
5.7.2 Stop SAP server ....................................................................................................................................................28
5.7.3Start SAP..................................................................................................................................................................28
5.8 Re-initialize Jobs......................................................................................................................................................28
5.9 Schedule Standard Jobs..............................................................................................................................................28
.............................................................................................................................................................................................28
5.10 Configure SAP Profile Parameter Files ................................................................................................................28
5.11 Configure Op Modes ...............................................................................................................................................29
5.12 Check System Logs..................................................................................................................................................29
5.13 Fix Logon Group Names.........................................................................................................................................29
5.14 Fix Server Group Names.........................................................................................................................................29
5.15 Import User Master Data........................................................................................................................................30
5.16 Post user master import..........................................................................................................................................30
5.17 Import Printer, RFC Definitions............................................................................................................................30
5.18 Fix ITS Information................................................................................................................................................30
5.19 Delete Local CUA/Detach a Satellite Client..........................................................................................................30
5.20 Update HP OMS entry in SPAD ...........................................................................................................................31
5.21 Disconnect from previously connected P21 ...........................................................................................................31
5.22 Converting Logical Systems....................................................................................................................................31
5.23 Logical System Names..............................................................................................................................................31
5.24 IDOC Port Definitions.............................................................................................................................................32
5.25 Partner Profile..........................................................................................................................................................32
5.26 Create Trusted System ...........................................................................................................................................32
5.27 Republish Services...................................................................................................................................................32
5.28 Trust Manager Portals Certificates....................................................................................................................32
5.29 Integration Engine Configuration..........................................................................................................................32
5.30 Port Maintenance IDOC Adapters........................................................................................................................33
5.31 IDOC Adapter Metadata Overview.......................................................................................................................33
5.32 Verify Distribution Model View.............................................................................................................................33
5.33 Delete Workload Analysis Logs for Old Server....................................................................................................33
5.34 Reset the passwords for the following users .........................................................................................................33
5.35 Client Definition ......................................................................................................................................................33
5.36 Maintain DBA Planning Calendar.........................................................................................................................33
5.37 qRFC Monitor..........................................................................................................................................................33
SLD Specific........................................................................................................................................................................34
5.38 Maintain SLD connection parameters......................................................................................................................34
5.39 Schedule XML Messages Delete Jobs......................................................................................................................34
5.40 Attach a Satellite Client to CUA.............................................................................................................................34
6. INSTALL J2EE AND APPLY JAVA PATCHES ON CI..................................................35

6.1 NW04S Java Install................................................................................................................................................36
6.2 NW04 Install(SRM/SCM Specific)...........................................................................................................................37
6.3 Java Patches on CI....................................................................................................................................................37
6.3.1 Update SDM...........................................................................................................................................................38
6.3.2 Update JSPM..........................................................................................................................................................38
6.3.3 Apply Java Patch on CI..........................................................................................................................................38
6.3.4 Troubleshoot Errors while applying support package using JSPM.......................................................................39
Page 4 of 61
6.3.5 For Target systems (Eg: SRM, SCM) which have J2EE 640 (Oracle 9i) install on Oracle 10.2 Database............39
7.POST SAP SYSTEM SPECIFIC STEPS:..........................................................................40

7.1 XI Specific Steps........................................................................................................................................................40
7.1.1 Configure the SLD Bridge (XI) ...........................................................................................................................40
7.1.2 Configure CMS Setup..........................................................................................................................................40
7.1.3 Run transaction SXMB_IFR................................................................................................................................40
7.1.4 Activate XI related services .................................................................................................................................40
7.1.5 Refresh XI Cache.................................................................................................................................................40
7.1.6 XI Message Archiving & Deletion.......................................................................................................................40
7.1.7 Configure JCo RFC provider using Visual Admin...............................................................................................41
7.2 BI Specific Steps..........................................................................................................................................................43
7.2.1 Restore the Logical system destinations...............................................................................................................43
7.2.2 Restore the Table RSBKDTP entries to Target SID.............................................................................................43
7.2.3 Restore Source System Connection.....................................................................................................................44
7.2.4 Maintain IDOC Sender/Receiver Systems...........................................................................................................44
7.2.5 RSA1 Check.........................................................................................................................................................44
7.2.6 BI Integration into the Portal................................................................................................................................44
7.2.7 Configure UDC....................................................................................................................................................44
7.2.8 Modify Logical System conversion Table...........................................................................................................45
7.2.9Change BIA (BI Accelerator) RFC Destination.......................................................................................................46
7.3 SCM Specific Steps....................................................................................................................................................47
7.3.1 Delete connections to liveCache..........................................................................................................................47
7.3.2 Setup Logical Systems.........................................................................................................................................47
7.3.4 qRFC Monitor......................................................................................................................................................47
7.3.5 Start CIF queue....................................................................................................................................................47
7.3.6 liveCache Restore.................................................................................................................................................47
7.3.7 liveCache consistency..........................................................................................................................................48
7.4 ECC Specific Steps....................................................................................................................................................48
7.4.1 Update Custom tables..............................................................................................................................................48
7.4.2 ECC Adapter Ports..................................................................................................................................................48
7.5 SRM Specific Steps....................................................................................................................................................49
7.5.1 Update Custom table : ZPCARDENCRYPT..........................................................................................................49
7.5.2 Update Custom table : ZZRFCDES.......................................................................................................................49
7.5.3 Synchronize Encryption for SRM...........................................................................................................................49
7.5.4 IPC Settings.............................................................................................................................................................49
7.6 CRM Specific Steps.....................................................................................................................................................51
7.7 Control-M Specific Steps............................................................................................................................................53
7.8 FireFighter Installation................................................................................................................................................53
8.BEFORE RELEASING SYSTEM TO BUSINESS (POST CHECKOUTS).....................54

8.1 General Check for All Systems..................................................................................................................................55
8.1.1 Valid license for PRD in DR-systems..................................................................................................................55
8.1.2 SAP access PRD Cl..............................................................................................................................................55
8.1.3 Oracle Alert Log...................................................................................................................................................55
8.1.4 DB12 Backup Logs...........................................................................................................................................55
8.1.5 DB13 DBA Planning Calendar.........................................................................................................................55
8.1.6 OS07.....................................................................................................................................................................55
8.1.7 RZ70 -> Ensure successful transmission of data to SLD.....................................................................................55
8.1.8 RZ03 -> No Configuration Alerts........................................................................................................................55
8.1.9 SICK SAP Initial Consistency Check...............................................................................................................55
8.1.10 SMICM -- ICM Monitor.....................................................................................................................................55
8.1.11 SM12 Check Lock Entries................................................................................................................................55
8.1.12 SM13 Check Update Requests..........................................................................................................................55
8.1.13 SM21 System Logs...........................................................................................................................................55
8.1.14 SM37 Batch Jobs...............................................................................................................................................55
8.1.15 SM51 Check SAP Servers.................................................................................................................................55
8.1.16 SM50 Check Work Processes...........................................................................................................................55
Page 5 of 61
8.1.17 SM59 -> ABAP Connections -> Check connectivity to other SAP system in the landscape..............................55
8.1.18 SMLG Check SAP Logon Groups....................................................................................................................55
8.1.19 SPAD -> Print to any printer other than LOCL and validate successful printing using SP01.............................55
8.1.20 ST22 Check SAP Dumps..................................................................................................................................55
8.1.21 SM58 Check Transactional RFCs.....................................................................................................................55
8.1.22 SMQ1 Monitor Outbound Queue......................................................................................................................55
8.1.23 SMQ2 Monitor Inbound Queue........................................................................................................................55
8.1.24 http://hostname:5xx00 -> Check system Information -- Check System Information and Patch levels.............55
8.2 ECC Specific...............................................................................................................................................................55
8.2.2 SM59......................................................................................................................................................................55
8.2.3 KGS......................................................................................................................................................................55
8.2.4 FAX......................................................................................................................................................................56
8.2.5 ITS Check.............................................................................................................................................................56
8.3 BW Specific...............................................................................................................................................................56
8.3.1 RSA1 -> Source System -> Right Click individual system and select Check.......................................................56
8.3.2 Check for BI UDC..................................................................................................................................................56
8.4 SRM Specific ............................................................................................................................................................57
8.4.1 SM59 Tcode Check for Live Auction................................................................................................................57
8.4.2 SMOKE TEST for Live Auction ..........................................................................................................................57
8.5 XI Specific .................................................................................................................................................................59
8.5.3 TIBCO SXMB_IFR............................................................................................................................................59
8.6 SCM Specific Checkouts..........................................................................................................................................59
8.6.1 LC10 - Check for LiveCache ...............................................................................................................................60
8.6.2 JDBC Check..........................................................................................................................................................60
8.6.3 Analyse LiveCache & LCA Objects ....................................................................................................................60
8.6.4 Optimizer Installation Tests
......................................................................................................................60
8.6.5 Check for BI UDC.................................................................................................................................................60
8.6.6 APO Consistency Check.......................................................................................................................................60
APPENDIX.............................................................................................................................60
Steps to reset the SDM password......................................................................................................................................60
Steps to synchronize SDM Server ....................................................................................................................................61
To recreate PSAPTEMP table space................................................................................................................................61
Starting Java SDM server..................................................................................................................................................61
Stopping Java SDM server:...............................................................................................................................................61
Page 6 of 61
1. Pre-Database/SAP Refresh
Most of the steps under this section will be performed at least One week prior to Refresh .
1.1 Post a System Message about Scheduled Downtime

Use SM02 T-code to Post a System Message and let users know about the scheduled downtime.
Example:
IMPORTANT : <SAPSID> System will be unavailable from 10-Oct-2007 at 5pm CST to 15-Oct-2007
at 10am CST for a System Refresh. Please, plan your work accordingly.
1.2 Saplicense
Logon to as <sid>adm on Source System
Check your sap license
saplicense show
Export the saplicense information to a file under <sid>adm home directory.
cd /home/<sidadm>
saplicense show > saplicense.SID
1.3 Confirm Passwords for Source/Target system with Security team

DDIC password in Client 000
DDIC and BASIS-BATCH in default client.
1.4 Stage Instance Specific Information before Volume Group is

recreated
Validate staging File System is available. This should return a valid File System entry.
bdf /usr/sap/put_refresh
Copy the required directories to the staging Directory - /usr/sap/put_refresh
Page 7 of 61
cd /usr/sap/put_refrersh
mkdir -p oracle/T_SID
mkdir -p usr/sap/T_SID/DVEBMSxx
mkdir -p sapmnt/T_SID
cd /oracle/<T_SID>
tar -cvf /usr/sap/put_refresh/oracle/U11/102_64.tar 102_64
{Note: To check the tar file structure tar -tvf <filename>.tar}
cd /oracle/<T_SID>
tar cvf /usr/sap/put_refresh/oracle/U11/dotastrik.tar .[a-z]*
cd /sapmnt/<T_SID>
tar -cvf /usr/sap/put_refresh/sapmnt/U11/profile.tar profile
cd /usr/sap/<T_SID>/DVEBMGSxx
tar -cvf /usr/sap/put_refresh/usr/sap/DVEBMGSxx/igs.tar igs
cd /oracle
tar cvf /usr/sap/put_refresh/oracle/client.tar client
tar -cvf /usr/sap/put_refresh/oracle/oraInventory.tar oraInventory
Team - Please add any other directories or files that you want to save off before the Volume Group is
recopied with Target Volume Group.
1.5
Export User Master data

Log 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 logs
Always, logon as <sid>adm at the OS level and validate the recent creation of cofiles & data
files.
cd /usr/sap/trans/cofiles
ls ltr
The 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.
1.6 Transport Printer Definitions

Run Transaction SPAD
Output Devices Display
Go to Edit transport transport all
Note down the request number
Release the Transport
Page 8 of 61
1.7 Transport RFC Definitions

Create a workbench request in SE01
Go to change mode of your request
Include the following object Name with Program ID : R3TR Object Type : TABU
RFCATTRIB
RFCDES
RFCDESSECU
RFCDOC
Now double click on each of your RFC table entry and it will open another screen and click on Insert
Row button.
Give * as input (i.e. all the keys corresponding to that table are taken)
Now save the transport request
Note down your request number
Release your request.
1.8 Logical System Definitions

Run Transaction BD54
Take a screenshot of Logical Systems Definition
1.9 Partner Profile

Run Transaction WE20
Take a screenshot of Partner Profile, specifically all Partner Type Logical Systems
1.10 IDOC Port Definitions

Drill Down on Transactional RFC, Take a screenshot of RFC Destination Port Assignment
1.11 Client Definitions

Run Transaction SCC4.
Take a screenshot of clients overview to note the Client Description and settings.
1.12 Trusted Systems

Run 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 Certificates

Run Transaction STRUSTSSO2.
Check the existing public-key certificate of Portal Servers in component system's certificate list. This
needs to be reconfigured during post refresh activities.
Page 9 of 61
1.14 Integration Engine Configuration

Run transaction SXMB_ADM
Double Click on Integration engine configuration
Take screenshot of configuration data
1.15 Maintain SLD Access data

Run transaction SLDAPICUST
Take a snapshot or make note of the entries.
1.16
SLD Bridge Info ABAP/JAVA
1.16.1 ABAP
Run Transaction RZ70
Take screenshot or note the SLD Bridge Host and Service Info.
1.16.2 Java
Logon to Visual Admin
Go to services Select SLD Data Supplier Note SLD Data Collection Settings
Note CIM Client Generation Settings
1.17 Port Maintenance IDOC Adapters

Run transaction IDX1
Note all the ports and corresponding RFC destinations or take a screenshot of the same.
This needs to be reconfigured during post refresh.
1.18 IDOC Adapter Metadata Overview

Note all the ports and corresponding RFC destinations or take a screenshot of the same.
This needs to be reconfigured during post refresh.
1.19 Distribution Model View

Run transaction BD64
Take a snapshot or make note of the entries.
1.20 Maintain CRM RFC Parameter

This 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 SPAD

Use transaction SPAD
Page 10 of 61
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 on previous line for the specific
SID.
Please Add SBX specific info
1.22
Display / Note Logon Group Definitions

Run Transaction SMLG
Take a screenshot of currently configured logon groups
1.23
Check operation modes

Run Transaction RZ04
Take a screenshot of currently defined OP modes
1.24 Check for ITS

Run transaction SM30
Give the table name TWPURLSVR
Click on Display
Double click on your Logical system host name
Take 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.
1.26
XI Specific Steps
1.26.1 Export SLD Information

Logon to xi
Run Transaction SLDCHECK
Page 11 of 61
Select Administration
Select contents Export All (in export line)
save the file to your desktop.
1.26.2 Export the Repository server information

Logon to Windows terminal server
Logon to your Target system
Run transaction SXMB_IFR
Sap Exchange Infrastructure Page will be opened
Select Integration builder
Log on with xisuper
Integration builder page will opened
In objects tab
Here a list of software components will be present there
Select the software component
Go to tools
Click on Export Design Objects
Select the icon at the end of the software component version field
A list of software components will be displayed
Expand your software component
Select your software component version
Click on Apply
Click on continue
Now select objects list field will be displayed
Expand your object set
Select all objects of software component version
Click on Finish Button
Export all your repository objects using the above procedure.
The objects will be exported to
/sapmnt/<SID>/global/xi/repository_server/export
After the export is completed move all the objects from export directory to a temporary directory to
import them later after the JAVA install. At that point, move these files to the following directory to
import /sapmnt/<SID>/global/xi/repository_server/import
1.26.3 Export the Directory server information

Now go to your Sap Exchange Infrastructure Page
Click on Integration Directory link
Logon with xisuper
Integration builder page will opened
In the scenarios tab select your Configuration Scenario
Go to tools
Select Export Configuration Objects
Select mode will be displayed
Say continue
Page 12 of 61
Select object set all objects of a Scenario

Select your business scenario
Say ok
Click finish
Export all your directory objects using the above procedure.
The objects will be exported to
/sapmnt/<SID>/global/xi/directory_server/export
After the export is completed move all the objects from export directory to a temporary directory to
import them later after the JAVA install. At that point, move these files to the following directory to
import - /sapmnt/<SID>/global/xi/directory_server/import
1.26.4 Configure CMS Setup

Verify if the following parameters are set to true in Integration Builder section..
com.sap.aii.ibdir.core.cms.enableTransportWizard
com.sap.aii.ibdir.core.enable.TransportWizard
com.sap.aii.ibrep.core.cms.enableClTransport
com.sap.aii.ibrep.core.cms.enableTransportWizard
1.26.5 SLD DATA supplier and Bridge

Log on to http://url:port/sld go to administration and select data supplier bridge.
Note down the configured SLD bridges.
1.26.6 SLD Business Systems

Log on to http://url:port/sld go to Technical and then Business systems
Note all the Technical and Business Systems configured along with transport groups source and
target. This needs to be reconfigured during post refresh.
1.26.8 XI Message Archiving & Deletion

Check Existence of physical directory at the operating system level for storing the archived XI
messages at the following location.As always, make sure that the /interfaces directory and the
FILEPORTS are correctly changed.
Path: interfaces/<sid>/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 screenshot
Take 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
Page 13 of 61
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 a
logical File Name.
iv) Transaction : SXMB_ADM
Define Interfaces for Archiving and Retention Periods
[Take snapshot]
Click on Retention periods
[Take snapshot]
1.27
BI Specific Steps
1.27.1 Conversion of Logical System Names

Logon to BI
Run Transaction RSA1
Select Tools -> Conversion of Logical System Names
Take a screenshot of conversion Table to reinstate after refresh before transports are applied
1.27.2 UDC Connection Container Settings

Telnet to BI Central instance as <sid>adm using Reflection or Hummingbird X-Term session:
cdD
cd j2ee
cd 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 up
select Services -> JDBC Connector
Now select Connector Container in the left pane
Page 14 of 61
Select the jdbc connector container, e.g.,

SDK_JDBC_TD
SDK_JDBC_TD_ISCP
Go to tab Managed Connection Factory and then Properties for all the specified 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) and document it for each
landscap in this document for future refreshes.
Document for URL
Document for UserName
1.28
SCM Specific Steps
1.28.1 Document connections to liveCache

Run transaction LC10
Name of database connection: Type LCA
Press Integration button
Switch to change mode <Shift+F1>
Delete connection (Connection|Delete)
Repeat 1-4 for remaining connections. Hit drop down on database connections to find all connections
1.28.2 Configure UDC (* same step as BI **)

Telnet to SCM Central instance as <sid>adm using Reflection or Hummingbird X-Term session:
cdD
cd j2ee
cd admin
select the Central Instance Server in the left pane and open it up
select Services -> JDBC Connector
Select the jdbc connector container, e.g.,
SDK_JDBC_TD
SDK_JDBC_TD_ISCP
Go to tab Managed Connection Factory and then Properties for all the specified connector
Page 15 of 61
containers,
Note down the following for each of the Connectors
Document the FixedSchema
Find the password for Password field (Obtain Password Prior to refresh) and document it for each
landscap in this document for future refreshes.
Document for URL
Document for UserName
1.28.3 Document Business System Groups (BSG)

Run transaction /SAPAPO/C1
Hit new entries
BUS<SID><First 2 characters of client>
Description Bus Sys Grp - <SID>CLNT<Client>
document BSG to Logical System
/SAPAPO/C2
1.28.4 qRFC Monitor

Run transaction SMQR
SMQ1 and SMQ2 and make sure there is no data.
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 liveCache

run dbmgui > connect source system > make complete backup to the file system
>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: <Source SID>
username:control
Password:control
Backup file will be created under default path

/sapdb/<sid>/sapbackup/full.<source sid>_COM
Page 16 of 61
FTP the source file (i.e. /sapdb/<sid>/sapbackup/full.<source sid>_COM ) to the target system to the
following location
/sapdb/<T_sid>/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_<S_SID>.parameter.xml
Page 17 of 61
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 the logical port.
Here Port for SmartMapper Lookup double click and verify the parameter URL path.
Example -http://PHGP0159:14810/XrefLookup_WS/Xref_Lookup.serviceagent/Xref_LookupEndpoint
This settings needs to be reconfigured during post refresh.
Page 18 of 61
Database Backup
2.1 Oracle Database Backup Source System

Based 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/<T_sid>/sapbackup/full.<sourcesid>_COM to
/sapdb/<T_sid>/sapbackup/full.<targetsid>_COM
***** make sure to follow proper case while renaming file name.*****
Toggle source database to ADMIN mode

- Connect to target LC instance(QL2,UL1,DL2 etc) from OS level and log in as <sid>adm
- Connect to DBM client by typing the command
dbmcli d <sid of LC instance> -u control,control
-You will be connected to dbm client on that instance.
db_admin
3.
Launch dbm gui again and connect to target LC instance

-Click on recovery with initialization
-restore a medium
-fullfile
Click Start
Log on to SCM server and go to transaction LC10.
Click on Integration and change all settings corresponding to the target system, reset password for
CONTROL and SAPQL2.
Oracle Database Restore Target System
Page 19 of 61
3.1
Reproduce Source System environment on Target System

Create soft link for Source System
ln s /oracle/<T-SID> /oracle/<S-SID>
Validate user exists on the target system.
Change the ownership of all /oracle/<T-SID> files to source system ora<s-sid>.
To change the ownership we need to be the root.
Now login as root
sudo su
Change the ownership
chown R ora<target_sid>:dba /oracle/<Source_SID>
3.2
Add Source system in /etc/hosts file

Work with the OS team to make sure you have an entry for the source system in the
target
systems /etc/hosts file. This is needed to avoid affecting the source system during the re-build
activities.
3.3
Start database as Source System

Logon the target system as ora<Source_system_sid>
su ora<s-sid>
sqlplus / as sysdba
startup;
exit
3.4
Create Control File

Logon the target system as ora<source_system_sid>
su ora<s-sid>
sqlplus / as sysdba
alter database backup controlfile to trace;
exit
cd /oracle/<Source_SID>/saptrace/usertrace
Get 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 text
STARTUP NOMOUNT
Scroll one line up and delete all the lines from the beginning of the file to the current line.
:1,.d
Once you have deleted the lines, your first line should be
STARTUP NOMOUNT
Now replace the Source_SID with Target_SID on all the lines by running the following
command.
Page 20 of 61
:%s,Source_SID,Target_SID,g
Now search the string CREATE in the file and replace the following line:
/CREATE
CREATE CONTROLFILE REUSE DATABASE "<Target_System_SID>" RESETLOGS
ARCHIVELOG
With
CREATE CONTROLFILE SET DATABASE "<Target_System_SID>" RESETLOGS
For editing the line do the following, On the following line go to end of the line
CREATE CONTROLFILE REUSE DATABASE "<Target_System_SID>" RESETLOGS
ARCHIVELOG
$
Move your cursor upto word ARCHIVELOG by using key h on your keyboard
dw
and move your cursor upto word REUSE and by using h on your keyboard
dw
now switch to insert mode i
Now write SET
Now your modified command looks like
CREATE CONTROLFILE SET DATABASE "<Target_System_SID>" RESETLOGS
Now search the string RECOVER in the file and replace the following line:
/RECOVER
RECOVER DATABASE USING BACKUP CONTROLFILE
With
RECOVER DATABASE USING BACKUP CONTROLFILE until cancel
For editing the line do the following
Go to end of the line and append as follows
$
a
until cancel
Now your modified command looks like
RECOVER DATABASE USING BACKUP CONTROLFILE until cancel
Now save the file as /tmp/rename.sql using the following command:
:w /oracle/<Source_SID>/rename.sql
3.6
Copy back the pre-staged files from the staging Directory /usr/sap/put_refresh
sudo su
cd /oracle/<T_SID>
rm fr 102_64
cd /oracle/<T_SID{Note: To check the tar file structure tar- tvf <filename>.tar}
tar -xvf /usr/sap/put_refresh/oracle/<T_SID>/102_64.tar
cd /oracle/<T_SID>
tar -xvf /usr/sap/put_refresh/oracle/<T_SID>/dotastrik.tar
cd /sapmnt/<T_SID>
tar -xvf /usr/sap/put_refresh/sapmnt/<T_SID>/profile.tar
cd /usr/sap/<T_SID>/DVEBMGSxx
tar -xvf /usr/sap/put_refresh/usr/sap/DVEBMGSxx/igs.tar
cd /oracle
Page 21 of 61
tar -xvf /usr/sap/put_refresh/oracle/client.tar

tar -xvf /usr/sap/put_refresh/oracle/oraInventory.tar
3.7
Change the ownership of all <T-SID> files to target system
3.7.1 To change the ownership we need to be the root

Login as root
sudo su
Remove exe Directory from the Instance Directories. This will be recreated with the J2EE
Install.
cd /usr/sap/<SID>/SCSxx
rm fr exe
cd /usr/sap/<SID>/DVEBMGSxx
rm fr exe
Remove and re-create /usr/sap/<SID>/SYS/exe/run Directory
cd /usr/sap/<SID>/SYS/exe/
rm fr run
mkdir run
3.7.2 Change the ownership

chown R ora<target_sid>:dba /oracle/<Target_SID>
chown R <target_sid>adm:sapsys /usr/sap/<Target_SID>
chown R <target_sid>adm:sapsys /sapmnt/<Target_SID>
3.7.3 Set the permission for the new kernel files

cd /sapmnt/<SID>/exe
chown R <sid>adm:sapsys *
chmod R 755 *
3.7.4 Copy the files from /sapmnt/<SID>/exe to

/usr/sap/<SID>/SYS/exe/run Directory
cd /sapmnt/<SID>/exe
cp rp * /usr/sap/<SID>/SYS/exe/run/.
3.7.5 Now run the saproot.sh script

./saproot.sh <SID>
Note: saproot.sh script file updates the ownership and permissions of files under the following path:
/usr/sap/<SID>/SYS/exe/run
3.7.6 Now copy the files from /usr/sap/<SID>/SYS/exe/run to

/sapmnt/<SID>/exe
cd /usr/sap/<SID>/SYS/exe/run
Page 22 of 61
cp rp * /sapmnt/<SID>/exe/.
3.8
Recover Database as Target System
3.8.1 Recover the database on target system as ora<Target_sid>

Check the Online Logs permission in /oracle/<T_SID>/oraarch directory. It should be set
as:
Owner : ora<T_SID>
Group : dba
Sqlplus / as sysdba
@rename.sql
This might ask for multiple Online logs to recover; so, just keeps ENTER and watch
carefully the screen.
cancel
Note:- here it will ask us for CANCEL option at the end of command execution. Say CANCEL
alter database open resetlogs;

Open another telnet session to tail the rename.sql file and run the last sql command from the
rename.sql file to create the PSAPTEMP tablespace. Here is the example of the command you need
to run:
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE
'/oracle/<Target_SID>/sapdata3/temp_1/temp.data1' SIZE 629145600 REUSE AUTOEXTEND
OFF;
3.8.2 Restart the database to make sure that DB starts correctly

shutdown immediate
startup
3.8.3 Create the ops$<Target_sid>adm users and grant permission

create user ops$<Target_sid>adm identified externally
default tablespace psapdatusr temporary tablespace psaptemp;
Grant dba,connect,resource to ops$<Target_sid>adm;
create user ops$ora<Target_sid> identified externally
default tablespace psapdatusr temporary tablespace psaptemp;
Grant dba,connect,resource to ops$ora<Target_sid>;
create table ops$<Target_sid>adm.sapuser as select * from
ops$<Source_sid>adm.sapuser;
exit
Page 23 of 61
3.8.4 Test the connectivity to the database as user <Target_sid>adm

su - <sid>adm
R3trans d
This 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<sid>
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/orapw<SID>
password=<system password> entries=100
(Use password for system)
sqlplus / as sysdba
create spfile from pfile;
startup
4
4.1
Delete Target Java Installation

**Delete the currently installed JAVA Installation**
Make sure your Database is down for this step, which it should be since you did not start SAP as yet.
4.2 Delete the following directories on Target DB server

Su -<sid>adm
cdD
rm fr /usr/sap/<SAPSID>/DVEBMGS<xx>/SDM
rm fr /usr/sap/<SAPSID>/DVEBMGS<xx>/j2ee
rm fr /usr/sap/<SAPSID>/SCS<xx>
rm fr /sapmnt/<SAPSID>/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/<SAPSID>/D<xx>/j2ee
Page 24 of 61
4.4 Delete the JAVA profile

cdpro
rm -f /sapmnt/<SAPSID>/profile/<SID>_SCSxx_hostname
rm - f /sapmnt/<SAPSID>/profile/START_SCSxx_hostname
4.5 Drop your j2ee schema

Log on as user ora<Target_sid>
Start sqlplus and connect to the database.
sqlplus /nolog
connect / as sysdba
startup
Note:- when sqlplus /nolog is executed we get the error connected to an idle instance. This means the
database is not connected. So at that time we need to start the database using startup command. Enter
the following command to delete the database objects of the database schema:
drop user SAP<Source_System_SID>DB cascade;

Enter the following command to get the name of schema of the associated data files in the
system
select file_name from dba_data_files where tablespace_name =

'PSAP<Source_System_SID>DB';
4.6
Now drop the table spaces as they are empty

Enter the following command to delete the tablespace of the database schema:
drop tablespace PSAP<Source_System_SID>DB including contents;

Exit sqlplus:
shutdown immediate
exit
4.7
Delete the data files of tablespace PSAP<Source_SID>DB from

the system
rm rf /oracle/<Source_SID>/sapdata4/<Source_SID>db_1
Now your java instance is completely deleted.
Page 25 of 61
Page 26 of 61
Post SAP Refresh
5.1 Install sap license

Logon as <sid>adm
su <sid>adm
Browse to the directory where the license backup file is kept
more <SID>.saplicense
saplicense install
5.2 Set Background Process as Zero

Logon as <sid>adm
su <sid>adm
cdpro
Edit SAP Instance Profile
vi <sid>_DVEBMGS<no>_<host>
find parameter rdisp/wp_no_btc
comment out # rdisp/wp_no_btc
append
rdisp/wp_no_btc = 0
To make background process = 0
5.3 Cleanup /sapmnt/SID/global

Before starting SAP remove the JOBLOG & SLOG files in the /sapmnt/SID/global/ directory on the
target system.
cd /sapmnt/<Target_SID>/global
rm fr *JOBLG*
rm fr *SLOGJ*
rm -fr WF_LOG*
5.4 STARTSAP
startsap
Logon to your sap
We see the default client of <Target System> which is configured in instance profile
Remove the <target system> default client number and type <source system > default client number.
Provide the logon information of <Source System>
5.5
Reinitialize TMS after DB copy

logon to 000 as DDIC
Run transaction SE06 database copy or database migration
Reinstall CTS yes
change original <S_System <SID>>to <T_System <SID>> yes
cts not configured ok
delete the TMS Configuration yes
delete all versions of transports yes
delete transport routs yes
Page 27 of 61
5.6
Delete Jobs
** WARNING: MAKE SURE YOU ARE IN TARGET SYSTEM/CLIENT **
Execute transaction SM37
Delete all released jobs from the system
5.7
Revert background processes to original

Logon as <sid>adm
su <sid>adm
cdpro
5.7.1 Edit instance profile

vi <sid>_DVEBMGS<no>_<host>
Find parameter rdisp/wp_no_btc
Reset to original values
5.7.2 Stop SAP server

stopsap
5.7.3 Start SAP

startsap
5.8
Re-initialize Jobs
After the database restore has successfully completed, the import jobs used by the tp command may
not work properly. Proceed as follows:
Logon to SAP in client 000 as DDIC and run transaction SE38
Execute program RDDNEWPP
Select Normal
A message will show up in the status bar which indicates the job has been scheduled.
5.9 Schedule Standard Jobs

Go to transaction SM36 as BASIS-BATCH.
Schedule all standard jobs
5.10
Configure SAP Profile Parameter Files

After 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 from the OS need to be re-imported. Proceed as
follows:
Run transaction RZ10
Delete source system profiles:
Click the Profile drop-down box and choose a profile (this process must be done for each profile).
Select menu items: Profile -> Delete -> All versions of a profile.
Click Yes to first prompt to update the database
Page 28 of 61
Click No to delete the files from the Op. Sys. Level

Click green check on all versions deleted screen
Repeat 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 Modes

After the database restore, the target system will contain Operation Modes from the old hostname.
These Op Modes need to be deleted and the correct Op Modes need to be imported. Proceed as
follows:
Select Instance/Opmodes
Select 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 menu items Settings -> Based
on Current Status -> New Instances -> Generate
Click the SAVE button.
5.12
Check System Logs

Check the system logs to see if there were any unusual error messages generated 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 Names

Run transaction SMLG
Add 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 delete
the groups both the groups and instances will be deleted.
Re-execute transaction SMLG once again and validate the logon group configuration.
5.14
Fix Server Group Names

Click pencil for change mode, click cleanup list.
Select Job-ServerGruppen
Click Create Group
Type GENERAL, click continue
Page 29 of 61
Expand All Groups folder

Highlight GENERAL, click on + assignment
Drop down instance name box, select only application servers
Do this for each application server available, but if no app servers are configured for the instance, use
the CI.
Once all the new entries are added. Delete the Source System Entries.
5.15
Import User Master Data

Importing the previously exported Users from the Pre-Client Copy Steps
Run T-Code: STMS
Click 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 import

Login into your target client
Run Transaction SCC7
From Menu options choose start immediately.
SCC3 check your logs
5.17
Import Printer, RFC Definitions

Run Transaction SPAD
Select 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 ok
Click refresh until your truck symbol is lost and the transport is successful.
Repeat this transaction for all the transports
Run transaction SPAD
Select menu items utilities for output devices assign server.
Validate RFC definitions.
5.18
Fix ITS Information

Edit the table TWPURLSVR by selecting the change option.
Change the hostname reflecting the new hostname.
Save
5.19
Delete Local CUA/Detach a Satellite Client

Delete the target hostname and system number under SM1 trusted connection entry.
Run transaction SE38
Execute the report RSDELCUA.
Page 30 of 61
Select Child System -> <SID>CLNT500 and unselect Test -> execute.
Use the Green back arrow to go to the previous screen
Re-execute the last step to invalidate the CUA contents.
5.20
Update HP OMS entry in SPAD

Use transaction SPAD
Select Full Administration button
Go to Output Management Systems tab
Check Real Output Management Systems by clicking on Display
Select change and update HP-DAZEL with the new OMS Configuration info
For 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 SE37
Enter RSAP_BIW_DISCONNECT
Hit Test/Execute (F8)
Enter data into the following fields:
I_BIW_LOGSYS: P21CLNT500
I_OLTP_LOGSYS: <Logical system for your Production System>
I_FORCE_DELETE: X
Hit execute (F8)
5.22
Converting Logical Systems

Run transaction BDLS
Enter Old logical system name in the Old logical system name field
Enter New logical system name in the new Logical system Name field
Select Conversion of Client-Dependent and Client-Independent tables.
Uncheck Test Run
Uncheck 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 components in the respective
clients. Example, if the logical system client says 110, BDLS should be executed in client 110 for
each logical system connected to the system. This rule applies currently to ECC and SRM where there
are multiple clients.
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 Names

Run Transaction BD54
Page 31 of 61
Verify and Redefine the logical systems as per the screenshot during pre-refresh.
5.24
IDOC Port Definitions

Adjust 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 Profile

Create and adjust the Logical System/RFC Destinations as per the pre-refresh screenshot
Activate the partner profiles if set to I set it to A
If a particular message type is not associated with the IDOC type, maintain the association
in WE82 transaction.
5.26
Create Trusted System

Run Transaction SMT1
Reconfigure 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 systems with proper
authorization in the case of QA2 it was SA2 and SM1. SM1 system will be created by Kevin Flattery.
5.27
Republish Services
Run Transaction SE38
Enter Program name W3_PUBLISH_SERVICES.
Execute and follow the screens to republish the services.
Run transaction SICF
Select the necessary services one at a time
Deactivate the Services
Activate the Services.
Make sure that the SAP GUI service was enabled and working.
5.28
Trust Manager Portals Certificates

Delete existing certificates and import portal certificates corresponding to target system.
Run Transaction STRUSTSSO2
Check the existing public-key certificate of Portal Servers in component system's certificate list.
Delete the Certificates.
Reconfigure/Import the appropriate certificates in component system as during pre-refresh
Portals Certificates will be imported by Portal administrators.
5.29
Integration Engine Configuration

Run transaction SXMB_ADM
Double Click on Integration engine configuration
Reconfigure integration engine data as per the pre-refresh screenshot.
Page 32 of 61
5.30
Port Maintenance IDOC Adapters

Configure all the ports and corresponding RFC destinations as per pre-refresh screenshot.
5.31
IDOC Adapter Metadata Overview

Configure all the ports and corresponding RFC destinations as per pre-refresh screenshot.
5.32
Verify Distribution Model View

Run transaction BD64 and check pertinent model views.
Verify the same pre-refresh distribution model views existing after request import.
5.33
Delete Workload Analysis Logs for Old Server

Run Transaction ST03
Change your user mode to Expert Mode.
Collector and Performance DB Performance Database Monitoring Database contents
Double 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 the changes go to the first
screen and come back after saving the changes.
5.34
Reset the passwords for the following users

Run transaction SU01
Reset the password for the following users from the default client. These users will be recreated
during the JAVA Install.
J2EE_ADMIN
J2EE_GUEST
SAPJSF
XI* (Only on XI systems)
LD* ( Only on XI systems)
5.35
Client Definition
Run Transaction SCC4
Change the client description to reflect as per pre-refresh description.
5.36
Maintain DBA Planning Calendar

Run transaction DB13 as BASIS-BATCH.
Setup DBA jobs as per the pre-refresh screenshot.
5.37
qRFC Monitor
Run transaction SMQR & SMQS
Page 33 of 61
Delete 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 parameters
Run transaction SLDAPICUST
Change the connection parameters pointing to correct SLD source.
To change switch to editing mode and choose Insert Row. Specify the connection parameters (host
name, port, user, and password) and set this SLD server as Primary. Only the entry marked as Primary
is active.
Save your entries.
Configure the SLD Data Supplier Service in the Visual Administrator
Logon as j2ee_admin/administrator in Visual Admin.
Change and verify the connection parameters for SLD connection and CIM client generation settings
in SLD Data supplier service.
Verify by triggering the SLD data load.
Maintain the SLD connection in ABAP systems
Maintain SLD bridge host and gateway.
Validate SLD Connection/configuration
Run transaction SLDCHECK
Validate the all the checks are successful.
5.39 Schedule XML Messages Delete Jobs

Run Transaction SXMB_ADM as user DDIC
Go to SXMB_ADM Define Interfaces for Archiving and Retention Periods Retention periods
Retention Periods for Asynchronous messages in the Database:
XML Messages without Errors Awaiting Deletion:
30 Days
XML Messages without Errors Awaiting Archiving:
7 Days
Retention periods for Synchronous messages in the Database:
XML Messages with Errors Awaiting Deletion:
7 Days
XML Messages without Errors Awaiting Deletion:
0 Days
Retention periods for History entries in the Database:
History Entries for Deleted XML Messages:
35 Days
Run Transaction SXMB_ADM as user DDIC
Schedule Delete Jobs
Check the settings and reconfigure as per the screenshot taken
Verify 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_<client>
SAP_BC_XMB_HIST_DELETE_<client>.
5.40
Attach a Satellite Client to CUA

Logon to Satellite Client
Run T-Code: SM59
Page 34 of 61
Validate entry for an ABAP system - SA2_SYSTEM.

Validate entry for an ABAP system - SA2CLNT100.
Run T-Code: BD54
Select New Entry
Define a new Logical System for CUA, e.g., SA2CLNT100
Provide a description under Name
Save
Create a new transport or use an existing transport.
Run T-Code: SMT1
Select Create Button
SA2CLNT100 in Destination field.
Login to CUA System

Run T-Code: SM59
Validate ebtry for the ABAP system Q42CLNT500
Run T-Code: BD54
Validate Logical System entry for Satellite System, e.g., Q42CLNT500
Create a new transport or use an existing transport
Run T-Code: SCUA
Enter the Satellite Instance Name, e.g., S11CLNT005 at the bottom of the list
Select SAVE
You will have to enter DDIC user-id and password for the satellite system on the follow-up screen
Check the log file to validate that this command is completed successfully.
Logon to Satellite Client
Run T-Code: WE20
Validate that under LS, a Partner Profile for SA2CLNT100 is now defined and also SU01 has lesser
number of available options.
6. Install J2EE and Apply Java Patches on CI

Please use the reset passwords, during the J2EE Installation
Important:
This section activity should be performed on available Pepsico Windows Terminal
Server(WTS); because if your PC/laptop lost connection then there will be incosistency or might
have to restart the process.
Page 35 of 61
6.1
NW04S Java Install
Logon to available WTS

Run ProgramsReflection and open X-term to UNIX server where you are installing
J2EE.
Check X-Windows
xclock
This 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=<hostname>
cd /install/<SID>/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 :
DVD/CD Name Package Selection
Installation
/sapcd/sap/install/unicode/crm50/kernel/kernel/KN_HPUX_IA64
SCS
KERNEL DVD
/sapcd/sap/install/unicode/crm50/kernel_2/kernel2/KU_HPUX_IA64SCS & CI
JAVA DVD
/sapcd/sap/install/unicode/crm50/java_usage/java/J2EE_OSINDEP DB & CI
NetWeaver
/sapcd/sap/install/unicode/crm50/java_export/java_export
DB
SAPCD
Software Units Selection (Central Instance Java Add In for ABAP)
Usage Type
ECC
BI
CRM
XI
Software Units
None
None
CRM-APP
JCRM
PI
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*
Page 36 of 61
CRM
XI
YES*
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 below
cd /install/<SID>/xx
/
sapcd/sap/install/unicode/crm50/nw04sr1/hpux/ia64/master/DVD_NW_04_SR1_Installation_
Master/IM07_HPUX_IA64/SAPINST/UNIX/HPIA64sapinst
SAPINST_USE_HOSTNAME=<hostname>
On Initial Screen Selection
Usage TypeDescription
SRM
SAP Netweaver 2004 Support Release 1 Java Add In for ABAPOracle
Central System Java system Finalization
SCM
SAP Netweaver 2004 Support Release 1 Java Add In for ABAPOracle
Central System Java system Finalization
SAPCD Selection
DVD/CD Name Package Selection
/sapcd/sap/install/unicode/nw04sr1/hpux
/ia64/java_osind/DVD_NW_04_SR1_ SAP_Web_AS_JAVA/J2EE_OSINDEP
JAVA DVD
If the above directory doesnt work then please try the below:
/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 CI
Before applying JAVA Patches we need to Update SDM (Software Deployment Manager) and
JSPM (JAVA Support Patch Manager) to the Patch level we going to apply.
E.g.: Applying JAVA SP11 on Q12 system.
Page 37 of 61
6.3.1 Update SDM

Update SDM to SP11 from OS Level.
Login as <SID>adm
cd /sapcd/sap/patches/nw04s/SP11/JAVA
cp * /usr/sap/ecctrans/EPS/in
mkdir /usr/sap/<SID>/DVEBMGS<xx>/SDM/test
cd /usr/sap/<SID>/DVEBMGS<xx>/SDM/test
jar xvf /usr/sap/ecctrans/EPS/in/*.JAR
cdmod +x *
cd /usr/sap/<SID>/DVEBMGS<xx>/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 )
While updating it asks for SDM installation directory. Give the installation directory as
/usr/sap/<SID>/DVEBMGS<xx>/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 JSPM

Login as <SID>adm
./RemoteGui.sh
Enter SDM Password
Click on Deployment tab in SDM.
Browse to /usr/sap/<System_Name>trans/EPS/in
Select JSPM<xx>_<x>-xxxxxxxx.SCA file
Select the JSPM package and Deploy
System_Name like ecc bw srm

Eg. JSPM12_0-10003470.SCA
6.3.3 Apply Java Patch on CI

Login <SID>adm
cd /usr/sap/<SID>/DVEBMGS<xx>/j2ee/JSPM
./go
Enter SDM administrator password.
Now, Select the following on this screen
Page 38 of 61
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 package
which got error.
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 Database
Review the Oracle Upgrade document and update the location of classes12.jar file under J2EE
Specific entries from Post Steps.
Page 39 of 61
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 Setup

Based on pre-refresh steps, add the following parameters and set to true in Exchange Profile.
com.sap.aii.ibdir.core.cms.enableTransportWizard
com.sap.aii.ibdir.core.enable.TransportWizard
com.sap.aii.ibrep.core.cms.enableClTransport
com.sap.aii.ibrep.core.cms.enableTransportWizard
7.1.3
Run transaction SXMB_IFR

Verify link for repository, runtime workbench etc.
This should point to http://host: (icm http port)/rwb
7.1.4 Activate XI related services

Run transaction SE38
RSXMB_ACTIVATE_ICF_SERVICES Execute
7.1.5
Refresh XI Cache
Run transaction SXI_CACHE.
Select Goto
Select Adapter Engine Cache
Select line item under Adapter Engine Connection Data Cache section
Delete
7.1.6
XI Message Archiving & Deletion

Check Existence of physical directory at the operating system level for storing the archived
XI messages. Path: interfaces/sid/client/out/ready/archiving/
Verify logical path in TCODE FILE
Logical File = ARCHIVE_XI_DATA_FILE double click
Specify physical/logical file path based on pre-refresh screenshot
Validate Definition of variable FILENAME Use TCode: FILE,
Create as per the screenshot from pre-refresh
Validate Syntax group Definition create syntax group for operating systems with the same
syntax for file names and paths from pre-refresh screenshot.
Check assignment of syntax group to operating system as per the screenshot.
Go to SXMB_ADM Schedule Archiving Job Archive Administration Make sure the
Page 40 of 61
object is BC_XMB Click on Customizing. Go to Cross-Archiving Object Customizing

Technical Settings Configure as per pre-refresh screenshot
Go to Archiving Object Specific Customizing Technical settings. Configure as per prerefresh screenshot. Make sure the Delete Jobs is set to 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 selection button 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 Start Date, 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 Connections
LCRSAPRFC
SAPSLDAPI
AI_RUNTIME
AI_DIRECTOR
Create following Destinations in Visual Admin Server Services JCo RFC provider
Page 41 of 61
Page 42 of 61
7.2 BI Specific Steps

7.2.1 Restore the Logical system destinations
Go to Tcode SE16 RSLOGSYSDEST select each LOGSYS and change the Destination to the
target logical system name.
Ex:
LOGSYS
DESTINATION
Original Value
U51CLNT500 P51CLNT500
New Value
U51CLNT500 U51CLNT500
In 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 value of field
RSBKDTP:SRC from <S_SID>CLNT<CLIENTNo:> to <T_SID>CLNT<CLIENTNo:>
Go to Tcode SE38 RSBKDTP_BDLS and Execute.
Page 43 of 61
7.2.3
Restore Source System Connection

NOTE: In case the Source Systems have also been refreshed, make sure all the refresh activities
have been completed before you restore the connection. Should not perform the restore for UD
Connect Systems but can do the checks.
7.2.4
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 RSA1 Source System
Restore all systems one by one, starting with BW System (Myself)
Specify the ALEREMOTE passwords for source and receiver systems when
prompted.
Restoring all source systems may take some time to complete depending on number
of extract structures/Data sources to be replicated.
Rename the logical system name in RSA1 to maintain consistency.
Right click on the source system Select Rename
Change the name to appropriate value.
Maintain IDOC Sender/Receiver Systems

Table RSBASIDOC should have sender and receiver source systems rightly configured.
Verify in SE16 appropriate entries for all sender and receiver systems.
7.2.5
RSA1 Check
In RSA1 perform source system check by right click the source system check
Recommended
Perform 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 infopackage and 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 Portal

Call 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 Engine
Import BI Certificate to the Portal
Maintain Portal Server Settings for the Portal
Create RFC Destination for the Portal
Import Portal Certificate to BI System
7.2.7
Configure UDC
Logon to available WTS
Run ProgramsReflection and open X-term to UNIX server where you are installing
J2EE.
Page 44 of 61
Check X-Windows
xclock
This will display Clock Window; then you can proceed, otherwise you need to export
DISPLAY.
Telnet to BI Central instance as <sid>adm.
cdD
cd j2ee
cd admin
select the central instance server in the left pane and open it up.
select services -> JDBC Connector
In the middle pane select Driver and click on Create New Driver or DataSource
For Driver Name enter teradata
When asked to pick a Jar file for the driver go to /home/<sid>adm/TeraJDBC_304 and select the
following 3 files: tdgssconfig.jar, tdgssjava.jar, terajdbc4.jar
Open the jdbc connector container
Select SDK_JDBC and hit the Clone button
Enter the name SDK_JDBC_TD
Hit Save
Select SDK_JDBC_TD and go to the Resource Adapter tab
Click the add button and enter: library:teradata
Save
Go to tab Managed Connection Factory and then Properties
Enter the following configuration properties:
com.ncr.teradata.TeraDriver for DriverName
QTG_S for FixedSchema
???? for Password (Obtain Password Prior to refresh)
jdbc:teradata://td4.corp.pep.pvt for URL
RQ2250TD4 for UserName
Hit Save
Select SDK_JDBC_TD and hit the Clone button
Enter the name SDK_JDBC_TD_ISCP
Hit Save
Select SDK_JDBC_TD_ISCP
Go to tab Managed Connection Factory and then Properties
Enter or verify the following configuration properties:
com.ncr.teradata.TeraDriver for DriverName
QTG_S_ISCP for FixedSchema
???? for Password (Obtain Password Prior to refresh)
jdbc:teradata://td4.corp.pep.pvt for URL
RQ2250TD4 for UserName
Hit Save
Exit Visual Administrator
7.2.8
Modify Logical System conversion Table

Logon to BI
Run Transaction RSA1
Select Tools -> Conversion of Logical System Names
Modify entries based on the screenshot taken before the refresh.
Page 45 of 61
7.2.9 Change BIA (BI Accelerator) RFC Destination

Run Transaction RSCUSTA
Switch to change mode.
Use chart below to determine the entry for RFC BI Accelerator
Target BI System
RFC BI Accelerator Entry
Q21
BIA_QE1
U21
BIA_UE1
P21
BIA_PE1
All Others
Should be blank, delete entry if there is one.
Page 46 of 61
7.3
7.3.1
SCM Specific Steps

Delete connections to liveCache
Run transaction LC10.
Name of database connection: Type LCA
Press Integration button
Switch to change mode <Shift+F1>
Delete connection (Connection|Delete)
Repeat 1-4 for remaining connections. Hit drop down on database connections to find all
connections
7.3.2
Setup Logical Systems

Run transaction SALE
Basic Settings|Logical Systems|Define Logical System
Make sure all required logical systems exist after BDLS. Add any additional ones
Basic Settings|Logical Systems|Assign Logical System to Client
Make sure correct logical system is assigned to correct client.
7.3.4
qRFC Monitor
Run transaction SMQR
SMQ1 and SMQ2 and make sure there is no data.
7.3.5
Start CIF queue

/n/SAPAPO/OM17
7.3.6
liveCache Restore
run dbmgui > connect target system > make complete backup to the file system > validate the
backup file from unix
ftp the file to the source system > rename the file to the source system backup file
dbmgui > select recovery > recovery with initialization > check and make one more backup as
above
dbmgui > menu instance > configuration > database user > validate the sap user name sapSID
from /nLC10 > button integratin > change the user name and password of "standard liveCache user"
as sapSID
/nWE02 > check the failed iDOC
Page 47 of 61
7.3.7
liveCache consistency
/n/SAPAPO/OM13
7.4
ECC Specific Steps
7.4.1 Update Custom tables

Transaction SM30 to table ZRFCECCSRM and add corresponding Sid and Logical system entries
for ECC and SRM
7.4.2 ECC Adapter Ports

Check the attached Adapter ports confiuration file.
D:\Documents and
Settings\09031393\Desktop\PEP\P1UP - TIBCO IDOC and CDM Usage Tracker.xls
Page 48 of 61
7.5
SRM Specific Steps
7.5.1 Update Custom table : ZPCARDENCRYPT

Transaction SM30 to table ZPCARDENCRYPT and change corresponding SID and directory specs
to destination system settings.
7.5.2 Update Custom table : ZZRFCDES

Transaction SM30 to table ZZRFCDES and adjust entries to match destination SIDs in both Client
500 and 530.
7.5.3 Synchronize Encryption for SRM
Step 1: Logon to each of the application servers at the Unix level and ftp files SAP*.pse files from
the CI to the application server directory. The directory is /usr/sap/<SID>/D<##>/sec.
Step 2: Then login to STRUSTSSO2, right click on System PSE and select distribute, and all lights
should go to green. Step should not be performed until step 1 has been completed.
7.5.4 IPC Settings
Change the correct settings for IPC
Logon <sid>adm
sudo su
su ipcadm
Edit the parameters file under /usr/sap/ipc/lib/properties
vi /usr/sap/ipc/lib/properties/parameters.xml
Now serch for 500
Old Values:
Page 49 of 61
<Database Alias="P51" IsBasisSystem="true" IsR3System="false" IsServerConnection="true"

ApplicationServer="prdp51.corp.pep.pvt" SystemNo="55" DatabaseActive="true">
<Client ClientNo="500" User="IPCUSER"
Password="BEkERBEdRVkFUFVVARATMQ==
" ClientActive="true"
ClientEnabled="true">
Change the values in RED to your settings.
Smoke Test
Page 50 of 61
7.6 CRM Specific Steps

Maintain CRM RFC Parameter
This entry is maintained in table CRMRFCPAR in all sender/receiver systems (R3/BW etc)
SM30 CRMRFCPAR Maintain Delete the existing entry for CRM
Create a new one with the previous values.
Update CRMC ICM RFC Parameter
Update table CRMC_ICM_RFCDEST to reflect the new environment. The ECC and BW RFC destinations
should reflect the ECC & BW systems in the refreshed environment.
SM30 for table CRMC_ICM_RFCDEST.
Select customizing.
Continue w/out specifying Project
Under Incentive and Commission Management --> BW-ICM Transfer of BW Data to ICM
Execute the Set up RFC Destinations for ICM Engine and BW System
Page 51 of 61
The ECC and BW RFC destinations should reflect the ECC & BW systems in the refreshed environment.
Page 52 of 61
7.7 Control-M Specific Steps

Check the below document for all Control-M specific steps. Please, check all SAP systems i.e.
ECC, BI, CRM, SCM, SRM.
7.8 FireFighter Installation

Check the attached document for FireFighter Installation and configuration.
Page 53 of 61
D:\Documents and
Settings\09031393\Desktop\PEP\FireFighter Installation.doc
8. Before Releasing System to Business (Post Checkouts)
Page 54 of 61
8.1 General Check for All Systems

8.1.1 Valid license for PRD in DR-systems
8.1.2 SAP access PRD Cl
8.1.3 Oracle Alert Log
8.1.4 DB12 Backup Logs
8.1.5 DB13 DBA Planning Calendar
8.1.6 OS07
8.1.7 RZ70 -> Ensure successful transmission of data to SLD
8.1.8 RZ03 -> No Configuration Alerts
8.1.9 SICK SAP Initial Consistency Check
8.1.10 SMICM -- ICM Monitor
8.1.11 SM12 Check Lock Entries
8.1.12 SM13 Check Update Requests
8.1.13 SM21 System Logs
8.1.14 SM37 Batch Jobs
8.1.15 SM51 Check SAP Servers
8.1.16 SM50 Check Work Processes
8.1.17 SM59 -> ABAP Connections -> Check connectivity to other SAP system in the landscape
8.1.18 SMLG Check SAP Logon Groups
8.1.19 SPAD -> Print to any printer other than LOCL and validate successful printing using SP01.
8.1.20 ST22 Check SAP Dumps
8.1.21 SM58 Check Transactional RFCs
8.1.22 SMQ1 Monitor Outbound Queue
8.1.23 SMQ2 Monitor Inbound Queue
8.1.24 http://hostname:5xx00 -> Check system Information -- Check System Information and Patch levels
8.1.25 Tcode SICF -> execute -> default host -> sap -> bc -> gui -> sap -> its
-> webgui -> Test Service -> WebGui Logon Page
8.1.26 TCode SLDCHECK
8.2
ECC Specific
8.2.2 SM59
TCP/IP Connections ->
IGS_RFC_DEST
HPOM_RFC_DESTINATION
SLD_UC
TIBCO_P11
TIB_QTG1_P11
VERTEX
8.2.3
KGS
OAAD -> Technical Search ->
Business Object:
BUS0815
Page 55 of 61
Client:
500
Archive:
-> Press Enter for the next pop-up window -> Select any of the two documents
-> Display PDF file
8.2.4
FAX
SBWP -> New Message ->
Title:
Test
Recipient:
US3128217756
Recip. Type: FAX
-> Send
SCOT -> At least 1 entry should be there under Waiting for FAXP11 queue
-> Start Send Process(CNTRL + F7)
-> The count for (In transit) followed by (Completed) should inccrease by 1.
8.2.5
ITS Check
Tcode : SITSPMON
8.3
BW Specific
8.3.1 RSA1 -> Source System -> Right Click individual system and select Check
8.3.2 Check for BI UDC
http://<SID_hostname>.corp.pep.pvt:5<SID Instance#>00/BI_UDC/servlet/GrmgServlet
Page 56 of 61
8.4
SRM Specific
8.4.1 SM59 Tcode Check for Live Auction

8.4.2 SMOKE TEST for Live Auction
http://prdp51.corp.pep.pvt:55500/srm/la/smoketest.jsp
8.4.3
Check certificates
8.4.4
Check encryption
STRUSTSSO2 -> Select (System PSE)/(SNC)/(SSL Server)/(SSl Client)

-> Ensure that all the line items for each system is GREEN.
TCode SE38 -> SSF01 -> use variant Z_PCARD_TEST
Page 57 of 61
Page 58 of 61
8.5
XI Specific
8.5.1
SXMB_IFR -> On the web page select all the components to ensure proper connectivity
8.5.2
SXMB_MONI - Check for any Red Flag Messages
8.5.3
TIBCO SXMB_IFR
-> On the web page select (Runtime Workbench) -> Login as XISUPER ->
-> Select (Component Monitoring) -> Click on Display -> Adapter Engine prdp41
-> Adapter Monitoring -> login as XISUPER ->
-> Select the arrow on http://sap.com/xi/XI/System -> Select JMS
-> Ensure the status is Green for all the four line items under JMS section.
8.6
SCM Specific Checkouts
Page 59 of 61
8.6.1 LC10 - Check for LiveCache

8.6.2 JDBC Check
http://prdp61.corp.pep.pvt:56500/TestJDBC_Web/TestJDBCPage.jsp
http://prdp61.corp.pep.pvt:56500/TestJDBC_Web/TestJDBCPage2.jsp?sys_jdbc=SDK_JDBC_ISCP
8.6.3 Analyse LiveCache & LCA Objects

TCode : /sapapo/om13
8.6.4 Optimizer Installation Tests

TCode : /sapapo/opt_inst
8.6.5 Check for BI UDC

http://prdp61.corp.pep.pvt:56500/BI_UDC/servlet/GrmgServlet
8.6.6 APO Consistency Check

se38 -> /SAPAPO/TS_LCM_CONS_CHECK_ALL
APPENDIX
Steps to reset the SDM password.
Logon to the system as <sid>adm.
cd /usr/sap/<SID>/DVEBMGSxx/SDM/program
./sdm.sh jstartup sdmhome=/usr/sap/<SID>/DVEBMGSxx/SDM/program
mode=standalone
./sdm.sh changepassword sdmhome=/usr/sap/<SID>/DVEBMGSxx/SDM/program
newpassword=xxxxx
Page 60 of 61
./sdm.sh jstartup sdmhome=/usr/sap/<SID>/DVEBMGSxx/SDM/program

mode=integrated
Steps to synchronize SDM Server
if required if your java patches doesnt reflect in the system info after applying them with JSPM.
Go to /usr/sap/DC2/DVEBMGS37/SDM/program
./StopServer.sh
./sdm.sh SystemComponentState mode=Sync
./StartServer.sh
Once Dev1 Instance is up and TMS is set in the Dev1 instance then run the following:
Reset TMS
Logon to SAP in client 000 as DDIC on the DEV Instance (TMS Domain Controller for system, i.e.
D11 or D21, D41, D51).
Run transaction STMS
Overview -> systems
CTRL F10 Distribute and Activate TMS configuration
Select Distribute configuration to all systems.
You might be prompted to LOGON to Target system, just logon to client 000 with DDIC
user/password.
To recreate PSAPTEMP table space

mkdir p /oracle/Q41/sapdata3/temp2
sqlplus / as sysdba
create temporary tablespace psaptemp2 tempfile '/oracle/Q41/sapdata3/temp2/temp.data1'
size 100m;
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE "PSAPTEMP2";
drop tablespace PSAPTEMP including contents;
create temporary tablespace psaptemp tempfile '/oracle/Q41/sapdata3/temp_1/temp.data1'
size 1048584192 reuse autoextend off;
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE "PSAPTEMP";
drop tablespace PSAPTEMP2 including contents;
exit;
Starting Java SDM server
Login <SID>adm
./StartServer.sh
Stopping Java SDM server:
Login <SID>adm
./StopServer.sh
Page 61 of 61

Sap Refresh

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Sap Refresh

Diunggah oleh

Hak Cipta:

Format Tersedia

SAP

Document Revision History

SAP Refresh Master Document

Text Heading Legend

SAP Refresh Master Document

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

ORACLE DATABASE RESTORE TARGET SYSTEM............................................19

3.1 Reproduce Source System environment on Target System...................................................................................20

DELETE TARGET JAVA INSTALLATION................................................................24

4.1 **Delete the currently installed JAVA Installation**............................................................................................24

SAP Refresh Master Document

4.3 Delete the following directories on each of the application server...........................................................................24

6. INSTALL J2EE AND APPLY JAVA PATCHES ON CI..................................................35

SAP Refresh Master Document

7.POST SAP SYSTEM SPECIFIC STEPS:..........................................................................40

8.BEFORE RELEASING SYSTEM TO BUSINESS (POST CHECKOUTS).....................54

SAP Refresh Master Document

SAP Refresh Master Document

1.1 Post a System Message about Scheduled Downtime

1.3 Confirm Passwords for Source/Target system with Security team

1.4 Stage Instance Specific Information before Volume Group is

SAP Refresh Master Document

Export User Master data

1.6 Transport Printer Definitions

SAP Refresh Master Document

1.7 Transport RFC Definitions

1.8 Logical System Definitions

1.9 Partner Profile

1.10 IDOC Port Definitions

1.11 Client Definitions

1.12 Trusted Systems

1.13 Trust Manager Portals Certificates

SAP Refresh Master Document

1.14 Integration Engine Configuration

1.15 Maintain SLD Access data

SLD Bridge Info ABAP/JAVA

1.17 Port Maintenance IDOC Adapters

1.18 IDOC Adapter Metadata Overview

1.19 Distribution Model View

1.20 Maintain CRM RFC Parameter

1.21 Validate HP OMS entry in SPAD

SAP Refresh Master Document

Select Full Administration button

Display / Note Logon Group Definitions

Check operation modes

1.24 Check for ITS

1.25 Verify DBA Planning Calendar

1.26.1 Export SLD Information

SAP Refresh Master Document

1.26.2 Export the Repository server information

1.26.3 Export the Directory server information

SAP Refresh Master Document

Select object set all objects of a Scenario

1.26.4 Configure CMS Setup

1.26.5 SLD DATA supplier and Bridge

1.26.6 SLD Business Systems

1.26.8 XI Message Archiving & Deletion

SAP Refresh Master Document

ii) Transaction: SXMB_ADM Schedule Archiving Job

1.27.1 Conversion of Logical System Names

1.27.2 UDC Connection Container Settings

SAP Refresh Master Document

Select the jdbc connector container, e.g.,

SCM Specific Steps

4.1 Delete the currently installed JAVA Installation............................................................................................24