Make sure all the below are uptodate
- Users at OS
- Shared folders
- Environment Variables
- File Systems
Install SAP GUI on client systems and create logon pad entries.
Run SAP Server using R/3 MMC or command line
Startsap name=<SID> nr=00 sapdiahost=host name
Stopsap name=<SID> nr=00 sapdiahost=host name
Logon to SAP using GUI with SAP* or DDIC into client 000
Users we have to create super user, and change the standard password.
Perform installation consistency check SICK/SM28
To find the inconsistency between os kernel ,db kernel and find inconsistency between patch levels Import.
Import the profile parameters os level to sap level in RZ10
- change the work process parameters, memory parameters,
- login parameters and buffer parameters.
- set the parameter login/no_automatic_user_sapstar=0 (in rz10)
Create SAP standard backgrpund jobs and schedule (SM36, SM37)
Create a new client and copy from 000 using local client copy (SCCL)
- development: customizing(cust), sandbox(sand)
- quality: test , pre test (ptst)
- production: production (prd).
Initialize CTS (TCODE: SE06) and Config TMS
- standard installation
- sytem copy or migration.
Select standard installation and check perform Post installation activites set cts and perform the following steps:
- Apply required support packs and install add-ons and pluggins (SPAM, SAINT)
- Create a local printer
- Check tablespace, free space stats and add required data files.
- Take initial DB Backup either online or offline
- Schedule SGEN
- Create required RFC connections using SM59
- Update DB Stats
- Install sap license
- Create users and check the user operations password never expires is set
Also do the following for sap accounts <sid>adm, sap service<sid>
- SAP router configuration: Configure sap router production System
- Check the system logs.
- To schedule/create a background job, use the menu path: Tools CCMS Jobs definition (or transaction SM36).
- When creating a background job, you must specify a job name and a job class (priority level A, B, or C with A being the highest priority- data transfer form external system. B – important periodic jobs performance statistics. C – non-critical jobs: list and queries.
- The target host is not required. Normally, you will just leave this field blank. However, if you are using an SAP system that has multiple application servers (and each of these servers has background work processes), you can specify the specific application server on which the background job should be processed.
- Next, you should enter the steps (i.e., programs) to be included in the background job
To include an ABAP/4 program in a background job, you must specify the program name and, if necessary, its variant. A variant is a set of parameter values needed for the execution of aparticular program.
External programs may only be executed by users having the same authorization as the system administrator The name of the server where the external program is executed must be specified.
External commands can be executed via background jobs defined with transaction SM36 as shown above These commands are defined by the administrator and protected with authorizations.
Use transaction SM69 to define and maintain external commands. External commands that defined by SAP can not be changed
- Logical command name
- External commands are uniquely identified by a logical name and the assignment of an operating system
- Operating system (CASE SENSITIVE FIELD)
- External commands can be restricted to execute on a particular operating system (AIX) or any operating system (ANYOS)
- Operating system command (PATH NAME)
- Name of an operating system program
- Parameters for operating system command
- Check module
- Optional function module to further check a user’s authorization to execute this command. Then maintaining external commands (SM69), you can specify the name of a check module, which is a function module that is executed immediately before the command, and can decide whether the command will be executed.
When you change the parameter, it is changed in Db only so when you re-start the instance again the change will be lost. Need to click on save button and the profile file will be saved and a backup is created at OS level.
Click on Param Name button
If the required param is not in the listed 500 inputs, simply click on the down arrow button at the top of the above screen. Type in the parameter name partially with * before and after the partial name and hit enter. Choose the required param and double click.
Enter the param value and click copy. It will copy and notify you in the status bar “Changes were made”. Now click on back arrow on the top and it will ask you to save the profile. Click OK and it will save the profile to OS.
Then it will ask you to change and activate the profile. Click ON and it will save the profile. Now open the profile in notepad and you will see the changes made to the instance profile (DEV_DVEBMGS_CHALAKI in this case)
Choose One of Administration data, Basic Maintenance or Extended Maintenance and click display button to view the data or Change button to Change the data.
Basic Maintenance: Change work processes and buffer Values Extended Maintenance You can manage all the parameters in this screen. Click on Param, Param+ and Param- buttons to change the value of a parameter.
Use RZ10 transaction code to Manage Profiles of all Instances running in a SAP R/3 system.
when you run RZ10 the following screen will apear. You will see option to Edit Profile
- Administration data
- Basic Maintenance
- Extended Maintenance
Click on Utilities/Import Profiles/Of Active Servers. This will import all profiles in all the active instances.
Click on Profile Button to see list of all imported profiles.
Select the one that u need to maintain and click ok.
Maintain the Profile
Administration data Profile
Now go to ‘Operation Mode’ view. Choose the instance name and click on menu ‘Maintain instance/Work process distribution’
Double click on the ‘* All operation mode’ and it will show you the following screen. In this click on other op mode button and then on click on operation mode entry field to choose an op mode.
You can right mouse click on a op mode and choose to delete it once its assigned to an instance.
Work process distribution for the op modes across the instances
Double click on the op mode to see the work process distribution dialog. Click on the Background or update or spool work process and use + or – button to increase or decrease the work processes.
Manually switching the operation modes.
- Choose RZ03
- system displays list of OP modes
Choose the target op mode by clicking on “Choose operation mode” button
- Choose the op mode and click ‘choose’
- To switch all servers to the op mode chose in above step use:
- Control/Switch Operation Mode/All Servers
- To switch selected servers to the op mode chose in above step use:
- Control/Switch Operation Mode/ selected Servers
Give name and short description and click save. Repeate this for all the op modes. Once all the op modes are created you will see a list of op modes. Also you will see an additional op mode called DUMMY listed along with the ones create by the admins.
Assign a time table to the op modes.
Click on time table and choose normal operation and click on change button.
Choose the time interval and click ASSIGN button. Next screen will let you choose an op mode to assign to the time interval chosen from the previous screen.
Choose the appropriate op mode and click OK to save. Now choose another interval and assign to another op mode. You need to repeat this step till all 24hr time slots are assigned to any op mode.