Extended Post Installation Steps for SAP Systems

8/12/2019 Extended Post Installation Steps for SAP Systems

http://slidepdf.com/reader/full/extended-post-installation-steps-for-sap-systems 1/3

Extended post installation steps for SAP systems.

1. Stop your SAP system, including any SAP services that were installed. Backup your kernel. Download themost recent kernel and apply.

2. Make changes to your instance profile. Here is what I typically add to the existing profile:

# ——— -Parameters Changed ———–

rdisp/wp_no_dia = 10

rdisp/wp_no_btc = 3

rdisp/wp_no_enq = 1

rdisp/wp_no_vb = 3

rdisp/wp_no_vb2 = 3

rdisp/wp_no_spo = 1

login/system_client = 200 ***200 for standard system, 800 for IDES system

# ——— -Parameters Created ———–

rdisp/keepalive_timeout = 600

rdisp/keepalive = 6H

ms/keepalive = 9999999

ms/conn_timeout = 100000ms/http_timeout = 600

em/initial_size_MB = 1024

DIR_EPS_ROOT = \\<hos>\sapmnt\trans\EPS

DIR_TRANS = \\<host>1955\sapmnt\trans

login/create_sso2_ticket = 2

login/accept_sso2_ticket = 1

icm/host_name_full = <host>.acmeinc.net

login/no_automatic_user_sapstar = 0

sapgui/user_scripting_set_readonly = FALSE

sapgui/user_scripting_disable_recording = FALSE

sapgui/user_scripting = TRUE

zcsa/system_language = E

icm/keep_alive_timeout = 6000

icm/conn_timeout = 9999999

rdisp/max_wprun_time = 14400

rdisp/gui_auto_logout = 0

em/blocksize_KB = 4096

em/max_size_MB = 20000

em/address_space_MB = 512

rdisp/ROLL_MAXFS = 10000

rdisp/ROLL_SHM = 10000

rdisp/PG_MAXFS = 32768

rdisp/PG_SHM = 5000

rsdb/ntab/entrycount = 80000

rsdb/esm/max_objects = 10000

dbs/ora/array_buf_size = 1000000

rsdb/ntab/size = 60000

http://scn.sap.com/acmesap1955/sapmnt/trans/EPS



http://scn.sap.com/acmesap1955/sapmnt/trans







rsdb/ntab/irbdsize = 8000

sap/bufdir_entries = 10000

rsdb/obj/buffersize = 40000

rsdb/obj/max_objects = 20000

rdisp/max_arq = 2000

gw/max_conn = 2000

rdisp/tm_max_no = 2000

rdisp/max_comm_entries = 2000

gw/max_overflow_size = 25000000

enque/table_size = 10000

rsdb/ntab/ftabsize = 60000

abap/buffersize = 300000

abap/heap_area_dia = 2000000000

abap/heap_area_nondia = 2000000000

abap/heap_area_total = 2000000000

abap/heaplimit = 40894464

abap/swap_reserve = 20971520

vmcj/property/vmc.cachesiz = 50

vmcj/option/percentageCopyOnlySC = 20

vmcj/option/percentageSharedClasses = 10

zcsa/presentation_buffer_area = 4400128

zcsa/table_buffer_area = 30000128

ztta/roll_area = 2000000

ztta/roll_extension = 2000000000

ztta/roll_first = 1

vmcj/enable = on

vmcj/max_vm_heap_MB = 128

vmcj/option/gc/sharedWaterMark = 70

vmcj/option/ps = 1024M

vmcj/option/maxJavaHeap = 128M

3. Restart your SAP system.

4. Log on to client 000 as DDIC – the password should either be the default which is 19920706 or whatever you entered during the installation.

5. Use transaction SU20 and create a company. Add the company and then change it to make it the standard company for that client.

6. Use transaction SU01 to create a new user with God-like powers. I start with copying the DDIC user. Modify the default information, supply a

password, make the user a Service user so you never have to change your password, and add all the RFC profiles you can find. Save the user. Log off

and log back on using this new user. Do all work from this point with the new user and not DDIC or SAP*.7. Copy your new user name to a new user called RFC_USER. Change the type to system and Save. This new user will be used for

future SM59 destinations.

8. Use SE06 to initialize the TMS

system. Then setup up a new or connect to an existing TMS configuration using transaction STMS. If you are adding this system to an existing TMS

domain, make sure to add the proper SAPTRANSHOST to the \…\etc\host file and be sure to add the <sid>adm and SAPService<SID> users as

administrators to the server home to TMS. Connect these users to the SAP_LocalAdmin and Administrators groups.

9. Use transaction SE80 to create a new package called ZUSER for future customer system modifications.

10. Use transaction SPRO to activate any extension sets you will need in this system.

11. Download all outstanding add-ons and support patches and patch your system using the SPAM and SAINTtransactions.

12. Connect SAP Online Help using SR13.



13. Use transaction SALE to add any logical systems names that you will need to a new local client and anySM59 connections you will create.

14. Create a new client using SCC4.

15. Use RZ12 to create parallel processing groups.

16. Use RZ10 to import all active profiles.

17. Use STZAC to change the client to the correct time zone.

18. Schedule a client copy from client 000 to your new client.

19. After the client copy has been completed, you can do most of your work from that client.

20. Add your company logo via SMW0 – you will need to add a PICs MIME before you can add any type of picture. Use SM30 to tell your system

about your new startup picture.

21. Add an initial screen system message called ZLOGIN_SCREEN_INFO using SE61.

22. Recompile all your ABAP loads by scheduling a job using SGEN.

23. Create a non-Basis profile for your users.

24. If using CUA, add this system to the CUA Distribution Model. Make you will add all the groups that the parent will expect you to have.

25. Apply to SAP for your permanent license key at service.sap.com/licensekey .

26. Use transaction SICF to turn ―on‖ all services you plan to use on the internet.

27. If you want to use SolMan to monitor this system, add the ST PI add-on and run the program RTCCTOOL.

28. Create variants for programs RTBTCDEL, RSPO0041, and RHAUTUPD_NEW and schedule periodic jobs for each one.

29. Confirm or change the passwords for DDIC and SAP*.

30. Add any printers via SPAD.

31. If you need other languages, use transaction SMLT to import them and transaction se38 to run programRSCPINST to help you make the

necessary system adjustments so the languages can be used.

32. Run program RSLANG20 for all languages to delete corrupt language buffers.

33. Verify that your standard system jobs are running in SM36.

34. Use the Database Maintenance Planner for MS SQL Server to schedule weekly refreshes of the <SID> database statistics. Use DB13 to schedule

statistics for Oracle.

35. Configure your SAProuter software using transaction OSS1 and make it a NT service.

36. Install a SMTP server on your server and use SCOT to connect for SAP email.

37. Turn off database logging for your database if this is a sandbox, DEV or QAS system.

38. Back up your system.

Documents

Extended Post Installation Steps for SAP Systems