Ecc Post Install Steps
Ecc Post Install Steps
Ecc Post Install Steps
Version 0.1a
Document Information
Project Name:
GCS team:
Document Id:
ECC_POST_INSTALL_STEPS.doc
Version
0.1a
Distribution List
To
Action*
Due Date
Comment
Cc
Action*
Due Date
Comment
Action Types: Approve, Review, Inform, File, Action Required, Attend Meeting, Other (please specify)
Page 1/ 42
TECHNICAL PROCEDURE
Version 0.1a
Version History
Version
Date
Revised By Description
Validation
Quality Review Method:
Prepared By:
Reviewed By:
Validated level 1 by :
Date:
Validated level 2 by :
Date:
Date:
Page 2/ 42
TECHNICAL PROCEDURE
Version 0.1a
Table of contents
1. Object : ......................................................................................................................................................... 6
1.1. Scope..................................................................................................................................................... 6
1.2. Inputs and referenced documents......................................................................................................... 6
1.3. Involved SAP transaction, ..................................................................................................................... 6
2. Pre-requisites................................................................................................................................................ 7
2.1. Installing the SAP system (central and database instance)...................................................................7
2.2. Checking and monitor the database freespace......................................................................................7
2.3. Checking transport directory freespace.................................................................................................7
2.4. Turning off archive log mode................................................................................................................. 7
3. Before starting the SAP System.................................................................................................................. 7
3.1. Checking / Updating the SAP Kernel..................................................................................................... 7
3.1.1. Checking Kernel release.................................................................................................................... 7
3.1.2. Updating kernel to patch 129.............................................................................................................. 8
3.1.3. Installing the SAP License.................................................................................................................. 8
3.2. Checking instance profile parameters values........................................................................................9
3.2.1. Checking / Importing Instance profile................................................................................................. 9
3.2.2. Checking parameters rdisp/bufrefmode.............................................................................................. 9
3.3. Starting the SAP system...................................................................................................................... 10
4. When SAP System was Started................................................................................................................. 10
4.1. User Creation and Check..................................................................................................................... 10
4.1.1. Create the adminsap user in client 000............................................................................................10
4.1.2. Checking / change password for SAP* and DDIC in client 000........................................................10
4.2. TMS Configuration............................................................................................................................... 10
4.2.1. Checking Modifying the transport directory...................................................................................10
4.2.2. SE06 - Perform post Installation tasks..............................................................................................11
4.2.3. Adding the new System to the transport Domain..............................................................................11
4.3. Configure Access to Online support services (OSS)...........................................................................12
4.4. Upgrading the Support Package level.................................................................................................. 13
4.5. Checking Brtools Release.................................................................................................................... 14
4.6. Installing additional languages............................................................................................................. 14
4.6.1. SAP installed from release SR0....................................................................................................... 14
4.6.2. SAP Installed from release SR1 or other.......................................................................................... 15
4.6.3. Language Installation procedure document......................................................................................15
4.6.4. Installing language part of support packages...................................................................................15
4.6.5. Language Supplementation.............................................................................................................. 15
Page 3/ 42
TECHNICAL PROCEDURE
Version 0.1a
Page 4/ 42
TECHNICAL PROCEDURE
Version 0.1a
Page 5/ 42
TECHNICAL PROCEDURE
Version 0.1a
1. Object :
The objective of this procedure is to describe the post installation steps for an ECC / GMR installation.
Post Installation starts from the point were database was successfully installed.
1.1. Scope
The list hereafter states which systems these procedure is related to:
Input / Document
Scope
ALL
Type
Date
Origin
BRIDGE_ECC_SAP_START_STOP_V1.0a.doc
05.12.2006
Build
BRIDGE_ALL_SPAM-SAINT-SP-UPD.doc
SPs Upg
Build
BRIDGE_ALL_SAP_LANGUAGE_IMPORT_&_SUP
PLEMENTATION.doc
Language import.
Build
RZ10 / RZ11
SLICENSE
SU01
SE06
STMS
SE38
DB02
OSS1
SM36
RZ03
RZ04
BD54
SCC4
SCCL
SCC3
RZ70
SLDAPICUST
SM59
DB13
SMSY
SSAA
Page 6/ 42
TECHNICAL PROCEDURE
Version 0.1a
2. Pre-requisites.
2.1. Installing the SAP system (central and database instance)
The ECC System (Central instance and database) have to be successfully installed.
Check database freespace with DB02 and use brtools to add new files for tablespaces:
SYSTEM, PSAPECC and PSAPECC640.
Page 7/ 42
TECHNICAL PROCEDURE
Version 0.1a
Check the new sap kernel target (patch level 129 for V1 systems).
Check the new kernel location.
Logon to your AIX server with root user.
Stop completely your sap system (+saposcol).
Go into your sapmnt<SIDW directory: cd /sapmnt/<SID>
Rename the kernel directory to old.exe: mv exe exe.old
Create une new directory /sapmnt/<SID>/exe (mkdir exe).
Check directory permission (should be 755).
Logon to service.sap.com under the following link and ask a new license for your system:
Keys & Requests.
Request license key
Page 8/ 42
TECHNICAL PROCEDURE
Version 0.1a
Use command: saplicense install to install the new license with paramters extracted from
the SAPNET site.
You can use later in SAP, the transaction SLICENSE to check it.
Use SLICENSE transaction to check and update the SAP License informations.
Launch SLICENSE and check the result.
For Cluster environnement, you must install two licenses (one for each cluster node, extract hardware key on
each of the node.
The default setting sendon, exeauto means that the buffer synchronization is activated (all changes are
logged).
sendon means that changes to buffered objects are logged in the table DDLOG
exeauto means that the local buffer is brought up to the newest state by cyclical
processing of the new DDLOG records.
Page 9/ 42
TECHNICAL PROCEDURE
Version 0.1a
4.1.2. Checking / change password for SAP* and DDIC in client 000.
Use RSUR003 program to check for standard password, change them if necessary.
You must have the following result after modified all users standards passwords.
Use RZ11 with parameter name DIR_TRANS to check the actual transport directory.
Check with the Change and Control Team which transport directory has to be used.
Page 10/ 42
TECHNICAL PROCEDURE
Version 0.1a
Choose
Now, as requested, continue with the transport management system configuration (TMS).
Logon to the new system in client 000, with user DDIC in English language.
Launch STMS transaction.
Use F4 to see all available domain and save with the right one.
Logon to transport Domain controller in client 000, with user DDIC in English
language
Page 11/ 42
TECHNICAL PROCEDURE
Version 0.1a
Launch STMS.
Go to Menu Overview systems.
Accept the new system waiting for approbation in the system list.
Check and adapt the transport route of the system in the domain controller (to be done
by or with the Change and Control team).
Use the check funuction in STMS to check if the transport directory is readable and
writable from newly created system.
Page 12/ 42
TECHNICAL PROCEDURE
Version 0.1a
Page 13/ 42
NAM E
TECHNICAL PROCEDURE
Version 0.1a
RELEASE
PL
SAP_BASIS
640
16
SAP_ABA
640
16
ST-PI
2005_1_640
PI_BASIS
2005_1_640
SAP_BW
350
16
SAP_APPL
500
12
SAP_HR
500
12
2004_1_500
EA-IPPE
300
EA-RETAIL
500
EA-PS
500
EA-HR
500
11
EA-GLTRADE
500
EA-FINSERV
500
EA-DFPS
500
EA-APPL
500
110_640
222
01H_ECC500
500
640
20
PI
WFMCORE
LOT
ST-A/PI
MRSS
SAP CORE CEE
SPAM
Be sure to check the support package level with Max attention and that it is in phase with the Bridge
Landscape.
Page 14/ 42
TECHNICAL PROCEDURE
Version 0.1a
BRIDGE_ALL_SAP_LANGUAGE_IMPORT_&_SUPPLEMENTATION.doc
This step has to be performed for each new language (here: French, Spanish,
Chinese).
To do it, use the chapter 5 of the Language import document.
BRIDGE_ALL_SAP_LANGUAGE_IMPORT_&_SUPPLEMENTATION.doc
Perform the language supplementation for all new languages installed (here: French,
Spanish, Chinese).
Supplementation language for all installed language must be ENGLISH.
BRIDGE_ALL_SAP_LANGUAGE_IMPORT_&_SUPPLEMENTATION.doc
Use the following configuration when launching Supplementation in client 000.
Page 15/ 42
TECHNICAL PROCEDURE
Version 0.1a
To be able to logon to the system in the new languages its necessary to add this
parameters in the DEFAULT profile.
Continue.
Page 16/ 42
TECHNICAL PROCEDURE
Version 0.1a
Choose Create
Fill in the details.
Page 17/ 42
TECHNICAL PROCEDURE
Version 0.1a
Do the Same to create a night Operation mode with less dialogue process and more
btach process.
Page 18/ 42
TECHNICAL PROCEDURE
Version 0.1a
Choose Save.
Page 19/ 42
TECHNICAL PROCEDURE
Version 0.1a
4.7.4. Activate the operation mode and perform an operation mode switch.
Page 20/ 42
TECHNICAL PROCEDURE
Version 0.1a
Use
Fil in your entries
Mandataory entries are: Logical system, client number, client role (not prod to able
to do the client copy.
Save your entries
Logon to the new client with user SAP* and password pass.
Use button
Validate the popup and dont change the client profile SAP_ALL.
Check the settings
Page 21/ 42
TECHNICAL PROCEDURE
Version 0.1a
Choose button
Choose button
Save
Now the client copy was launched.
Use SCC3 to check if realy started and no canceled for any reason.
Page 22/ 42
TECHNICAL PROCEDURE
Version 0.1a
For all V2 systems, SAP job have to be launched by control-M scheduler, to do that all job have to be
created in SAP with the status scheduled, control-M then connect SAP system, make a copy of the created
job and launch it following the schedule attributes.
So, if control-M is active, ask the control-M team to schedule the sap standard job list.
Use button
Use Button
Page 23/ 42
TECHNICAL PROCEDURE
Version 0.1a
Choose:
Choose:
Choose:
Choose
Choose
Fill the parameter name to modify + enter.
Choose
Choose
Set the parameter value.
Choose C for continue.
Check the command return.
Page 24/ 42
TECHNICAL PROCEDURE
Version 0.1a
The parameter was correctly modified in pfile and spfile, so the value was dynamically activated and persistent
because created in oracle pfile and spfile.
Duration is about 3 hours, depending of you system architecture (one or several SAP
system on the same host) and the selected component to generate.
Page 25/ 42
TECHNICAL PROCEDURE
Version 0.1a
4.13.4. Oracle archiving (changing generated archive name for production, preproduction
and maintenance systems).
TO DO ONLY FOR PREPROD and PROD systems.
To meet the backup requirement for Pre-production and production environnements, you have
to modify the archive name generated at each log switch in the /oracle/<SID>/oraarch
directory.
The archive policy is the following: generated archives are zipped and moved to ora_zipped
directory under ../oraarch and externalized on another server.
3 days archive files are always keeped locally (and copied) to able to quickly restore.
If a restore is needed, always asks the infrastructure team to do it.
Modifying archive name for Preprod and prod systems.
1 Modify the init<SID>.ora :
Add entry :
*.log_archive_format='<sid>db_<SID>_arch_%t_%s.arc'
*.log_archive_dest='/oracle/<SID>/oraarch/<SID>arch'
Replace by :
*.log_archive_dest='/oracle/<SID>/oraarch'
2 Stop the database.
Page 26/ 42
TECHNICAL PROCEDURE
Version 0.1a
Use command:
Use command:
Choose
Enter the Directory Name : /usr/sap/<SID>/interfaces
Page 27/ 42
TECHNICAL PROCEDURE
Version 0.1a
Choose
Choose
.
(save)
Page 28/ 42
TECHNICAL PROCEDURE
Version 0.1a
Note :
Refer to the following document (or ask the design team to know wich system have to be
configurated to exchange data with the new one).:
N:\GTCC\Technical_Design_and_Build\02-SAP&DBBuild\01Design\LandscapeIndia\PDE-TA-CS-Landscape_DetailDesign-V6-22-10-06.xls
Execute transactionSM59.
Check the RFC Links with partner systems at both side.
Note :
Refer to the following document (or ask the design team to know wich system have to be
configurated to exchange data with the new one).:
N:\GTCC\Technical_Design_and_Build\02-SAP & DB Build\01India\PDE-TA-CS-Landscape_DetailDesign-V6 -22-10-06.xls
Design\Landscape
Use SICF to check the avaibility of the services (CI and AS)
Default_hostsapbcguisapitswebgui
If the webgui is in gray color, it mean that the service is deactivated :
Page 29/ 42
TECHNICAL PROCEDURE
Version 0.1a
Check in transaction SMICM Menu Goto Parameters Display if the hostname full is
correct (different name for CI ans AS).
Only BRIDGE logon group have to created for dialog and RFC (RZ12 and SMLG).
Page 30/ 42
TECHNICAL PROCEDURE
Version 0.1a
In case of application servers, Central Instance does not have to be added to those logon group BRIDGE.
Launch SM59, and check the RFC Destination IGS_RFC_DEST (TCP/IP connections)
with the following attributes:
Connection type: T.
Registered programs name: IGS.<SID>
Then, execute RSRT to do an IGS Test (This check has to be done on each instances) :
Select
to test the display.
Check the following (OK).
Page 31/ 42
TECHNICAL PROCEDURE
Version 0.1a
Page 32/ 42
TECHNICAL PROCEDURE
Version 0.1a
Go to the Client tab, select the differents client and then select Check
RFC Destinations
Page 33/ 42
TECHNICAL PROCEDURE
Version 0.1a
Use SLDCHECK tcode to check the connection to the System Landscape Directory by the
internet browser.
Check the host and the Service in accordance with the screenshot made before the refresh
(section 2.1.1) :
Page 34/ 42
TECHNICAL PROCEDURE
Version 0.1a
Page 35/ 42
TECHNICAL PROCEDURE
Version 0.1a
Page 36/ 42
TECHNICAL PROCEDURE
Version 0.1a
Clic on Set (for Internet), and check the Address area (*):
Check the following in the menu path: SCOT Menu settings Default domain.
Check the following in the menu path: SCOT Menu settings Confirmation of receipt.
Page 37/ 42
TECHNICAL PROCEDURE
Version 0.1a
Checking functionality by using SBWP to send a new message (perform this test from the Central Instance
and from Application servers).
Page 38/ 42
TECHNICAL PROCEDURE
Version 0.1a
Logon to the database server with user ora<sid> and launch sqlplus.
Execute the following command to create the Tivoli users:
Connect to the following server to get the cofiles and data for transport order : TV1K000149
Path server: pz1serv : /softs/distrib/tivoli/ITMSAP/SAPLA0006/ABAP/
Files: K000149.TV1 and R000149.TV1
Import the transport request (for Unicode systems): TV1K000149
User: TIVOLI_<SID>
Password: 06_TIVO
User type: communication.
User profile: S_A.ADMIN and SA.SYSTEM.
Page 39/ 42
TECHNICAL PROCEDURE
Version 0.1a
The transport requests to be imported are client dependant, so have to be imported into every working clients.
For ECC Systems, imports the followings:
SQ1K900123 (authorization roles).
WP1K900024 (ECCs function modules)
For BW Systems, imports the followings:
Same as ECC but you have to import request 900296 after the 900024.
7. Final Check.
7.1. Activate archive-log.
Use brtools to reactivate database archive log if not already done.
Check with SCC4 transaction if the client settings are correct too.
Page 40/ 42
TECHNICAL PROCEDURE
Version 0.1a
Make sure the host doesnt swap while SAP is running with no user activity.
Check configuration of each AS.
Make sure there is enough work processes.
The patch number HAS TO BE the same on each instances(central instance and Application
servers) of the SAP system.
Page 41/ 42
TECHNICAL PROCEDURE
Version 0.1a
Open the running your SAP System folder and perform all the step (must be succesfull)
correct all errors if necessary).
END OF DOCUMENT.
Page 42/ 42