Support :-
Basis support is an activity which used to provide runtime support to the implemented system based on SLA(service level Agreement) there could be various level of support which is based on the organisation size.It also includes offshore,onsite,rightshore support.
The support can be 24*7*365 , some of the support activities are monitoring the system health, background jobs, updates, batch inputs,spool errors ,workload analysis,buffer analysis,top cpu users, programs &transactions, analyzing the error logs,sytem dumps and operating system monitor.
In easy way we can say that support means giving runtime support(help) to the SAP customers for which the SAP BASIS software using by the customers....
In support first we have remember the Transaction codes(T-Codes) it plays a major role in this module because we have to monitor the sap systems
By using T-Codes we can do the daily check list here i providing some T-Codes
Work Process:-
DEVBMGS
1)D-Dialog
2)E-Enqueue
3)B-Background
4)M-Message
5)G-Gateway
6)S-Spool Process
1)D-Dialog Process
2)E-Enqueue Process
3)B-Background
5)G-Gateway
6)S-Spool Process
Basis support is an activity which used to provide runtime support to the implemented system based on SLA(service level Agreement) there could be various level of support which is based on the organisation size.It also includes offshore,onsite,rightshore support.
The support can be 24*7*365 , some of the support activities are monitoring the system health, background jobs, updates, batch inputs,spool errors ,workload analysis,buffer analysis,top cpu users, programs &transactions, analyzing the error logs,sytem dumps and operating system monitor.
In easy way we can say that support means giving runtime support(help) to the SAP customers for which the SAP BASIS software using by the customers....
In support first we have remember the Transaction codes(T-Codes) it plays a major role in this module because we have to monitor the sap systems
By using T-Codes we can do the daily check list here i providing some T-Codes
TRANSCATION CODES
1
|
SM-50
|
Monitor the work Process Status
|
2
|
SM-51
|
Monitor the Active Application Server Status
|
3
|
SM-21
|
Monitor the System logs
|
4
|
ST-22
|
Monitor the ABAP System Dumps
|
5
|
ST-06
|
Monitor the file system space & Monitor the CPU and Memory Utilization
|
6
|
SM-13
|
Monitor the updates in the system
|
7
|
SM-12
|
Monitor the locks in the system
|
8
|
SP-01
|
Monitor the spool Requests Status
|
9
|
SMGW
|
Monitor the Gateway Connections
|
10
|
SM-04
|
Monitor the logged in users locally
|
11
|
AL-08
|
Monitor the Logged in users Globally
|
12
|
SM-66
|
Monitor the Global work process for all Instances
|
13
|
SM-37
|
Monitor the Background Jobs
|
14
|
SM-35
|
Monitor the Batch Inputs Logs
|
15
|
RZ-20
|
Monitor the CCMS—(Computing Centre Monitoring
System
|
16
|
DB-13
|
Monitor the Database Backup calendar and their
status
|
17
|
DB-12
|
Monitor the Database Backup Logs/DBA Logs &
Monitor the Archive Directory Status
|
18
|
DB-02
|
Monitor the Database Growth---
|
19
|
DB-14
|
Monitor the DBA BR(Backup, Restore & Recovery)
Tools Log
|
20
|
ST-03
|
Monitor the Workload Overview
|
21
|
ST-02
|
Monitor the Buffer Utilization
|
22
|
ST-07
|
Monitor the Application Monitor
|
23
|
ST-11
|
Monitor the Developer Traces
|
24
|
AL-11
|
Monitor the Directory Structure of File System
|
25
|
SMICM
|
Monitor the Internet Communication Manager
|
26
|
WE-05
|
Monitor the IDOC’S( Intermediate Documents)
|
27
|
SM-58
|
Monitor the Hanging Data (Errors Records)--
|
28
|
SOST
|
Monitor the Mails Transmission/Hanging Mails
|
29
|
SMQ1
|
Monitor the Outbound Queue
|
30
|
SMQ2
|
Monitor the Inbound Queue
|
31
|
SMMS
|
Monitor the Message in Server
|
32
|
ST-04
|
Monitor the Database Buffer Hit Ratio
|
33
|
ST-01
|
Monitor the Traces
|
34
|
SM-20
|
Monitor the Audit Logs
|
Process Flow in Application Server:-
1) User submits the request using
Sap (JAVA/WINDOWS/HTML)
2) GUI requires application server
Host/IP address and Instance number (port)
3) User Request uses DIAG(Dynamic
Information Action Gateway) protocol and port between 3200-3299 (Based on
Instance number) 3200+Instance Number (Instance number is a two digit number
ranges from 00-99 where 97,98 and 99 are reversed by SAP
Work Process:-
DEVBMGS
1)D-Dialog
2)E-Enqueue
3)B-Background
4)M-Message
5)G-Gateway
6)S-Spool Process
1)D-Dialog Process
Dialog process:-
- Dialog process is an interactive
- The process can handle 5-10 user requests
- The average response time is 600 milli sec
- The restricted time for dialog process is 600seconds
- Sum dialog process > non- dialog process
- Dialog process can handle other tasks like temp tables up back spool
- Sm-50 status are running, waiting, stopped ended
- The parameter uses to change rdidp/max_wprun_time=600
- Dialog process is multiplexing
- Dialog are monitor in ‘DPMON’, sapmmc,SM-50/SM-66
- Dialog process needs 75-300mb
- Dialog process should be 2-99 processes
2)E-Enqueue Process
3)B-Background
ü The programs which run long run times ,expensive programs should be
scheduled to run in the background during off peak hours in non-interactive
ü Background process are configured by using parameter rdisp/wp_no_btc=2
ü Two minimum background processes are required for entire system. It
is possible to configure as many background processes based on the available
resources.
ü Background processes are dedicated to background jobs and remains
the job until it is completed/cancelled.
ü The background jobs could not be timed out by runtime parameter and
it can be run for days/hours to complete the job.
4)M-Message
6)S-Spool Process
No comments:
Post a Comment