Академический Документы
Профессиональный Документы
Культура Документы
15-jul-11
SAP BASIS
2
SAP BASIS
Yahoo/
Google
1. Client requests
2. The request is processed by an interface
3. The request reaches server
4. The server process the request
5. Response back to the user either {Ticket/ Email}
R/2 Client-Server
4. Servers are heavily loaded/ traffic, long queues there by reducing the performance of the servers.
6. Server needs to process the request (Understanding the user language). Interpretation takes time.
Client requests and server responds. The major disadvantage of Client Server architecture is
The need of middle layer/ tier rose to come out of the steps. The result is the Application layer/ Server
1. DB Client is installed to free up the clients (i.e. there will be only one DB Client for Application
server earlier each client needs DB Client software)
2. There is a queue mechanism to handle the request there by reducing the load on the client and
server.
3. User requests are served based on the FIFO using dispatcher.
4. Work process task handlers are used to interpret and process the request.
4
5. Intermediate buffers are available for the frequently accessed content to reduce the load on the
Database server.
6. The server side processing is only takes place for new requests there by server resources are
optimally used.
It is the Intermediate layer in between the Client and the Server. It is installed with a database
client to communicate with the database server i.e. all the clients are freed with DB Clients.
Application server/ layer handle the request and process them based on FIFO (First in and First out). It
has its own queue mechanism to process the user request. It also contains the task interpreters to
interpret the user request and route it to the server.
5
It is intelligent to store the frequently accessed data thereby reducing the load on the server.
R/3 Architecture:
SAP uses the industry specific 3-Layer Architecture and named it as R/3 Architecture.
It consists of three 3 Layers
1. Presentation Server:
It is a client for all the SAP Solutions. It is also referred as SAPGUI. There are three 3 types of SAP GUI
SAP provides various versions of GUI (4.6c, 620, 640, 700, 710 and 720)
2. Application Server:
It is used to handle the user request and process them to the database. It has dispatcher
to process and monitor the user request, work process to process and interpret the requests, Buffer
areas to store the frequently accessed data. It absorbs the load both from Client and the server.
It is the area where the complete data resides. It has its own queue, process, buffers, and
request handling mechanism. Most of the databases are on Oracle. SAP is pushing MAXDB (without
any license key), Microsoft SQL Server & IBM DB2 with discounted prizes.
SAP is focusing SMB (Small Mid-sized Business) and promoting SAP for nearly 1 million/ Rs. 10 Lakhs/
per customer.
6
Supporting Platforms:
SAP can be installed on Microsoft windows 2000, win2k3 (2008 is under evaluation). It
can be installed on 32bit or 64bit operating systems. 64 bit means a single process can serve the user
with 4GB RAM/ Memory whereas in 32 bit it is 1.9GB Memory. 264, 232 / 8 bytes.
HP UNIX 11.23
ORACLE 9.2.0.6 / 10.2.0.4
IBM Specific operating system with version 5.3 technical (TL) level 7 (TL7)
This is also IBM specific which provides more consistency, reliability, mileage than any other
operating system and database.
Note: Linux with MaxDB is supported by SAP and provides more leverage (Finance)
Microsoft windows and SQL Server This is the best combination for interactive usage
7
Installation of Presentation Server (SAPGUI)
Use presentation server DVD and go to the respective OS win32 and run setupall.exe and follow the
onscreen instructions.
BASIS
Eg:
Basis provides User Management
Business process Monitoring
Role based Security
Performance Gauge etc.
1. Presentation Server
2. Application Server
3. Database Server
1. Presentation Server
It is an SAP GUI. It is of 3 types SAPGUI for windows, HTML and JAVA. It is used to
establish connection with SAP Application Server based on the name of the application server,
Instance Number, SID etc.
8
Installation of Presentation Server (SAPGUI)
Use presentation server DVD and go to the respective OS win32 and run setupall.exe and follow the
onscreen instructions.
Click on logon
1. Single GUI to access all the SAP Applications (ERP, CRM, SCM, XI, BI and SRM)
2. We can login with our logon language i.e. specify the language during logon. Same GUI is allowed
to login with different languages
Login - From Tools Administration SU01 - From Menu Favorites > Add
4. GUI is downward compatible to support all the SAP Applications which are below the gui version.
Example: GUI 7.0 cannot support the component that are built on 7.10 but 7.0 can handle 7.00,
640, 620, 46D, 45A etc.
5. User parameters are defined for the frequently keyed in content. Eg: A user belonging to the sales
organization, division, plant, sales area should get all the values by default while creating sales order
(VA01) etc.,
Steps:
Click on sales organisation field and press F1 and click on technical settings
2. Execute SU01
Save the data. Now whenever the user executes the transaction VA01 it will be filled with the default
values with 0001 and 01 for Sales organization and Distribution channel respectively there by
reducing the user tasks.
6. User can be specified with 1. Role based menu or with 2. SAP Easy access Menu to reduce the load
on the request processing (Roll Area)
7. SAP GUI is intelligent to determine the least loaded server when more than one instance is
configured. It gets the information from the Message server.
8. It provides access across the low speed connections and displays the screens without graphics/
logo which consume more network traffic. (Low Speed/ High Speed)
9. It provides command window to navigate to the respective functionality and minimizes dialogue
steps.
12. SAP Provides various shortcuts window /n to open window from existing window and /o to open a
new window /ex to exit the screen.
14. The character set can be changed to suite various languages and printers.
2. Application Server
It is a physical server which is used to handle and process the user request. In SAP naming convention
we define them as an Instance and it is possible to install more than one instance on a single server
provided they are differentiated by the instance number.
Instance number is a 2 digit number that varies between [00 to 97] 98 and 99 are reserved for routing
purposes.
1. Database Instance
2. Central Instance
This is the Instance where Application Server/ Tier/ Layer are installed. There will be only
one instance in the entire system.
3. Dialogue Instance
These are the instances which are used to handle the load on the central instances. We
can install as many instances as possible assuming that each instance can serve up to 200 - 500 users
depending upon the type of the users.
12
Kernel
SAP
K
E DB
R
OS
Usr\sap\<SID>\sys\exe\uc\NT1386
Installation Logs
.tsk file specifies the table/ index etc that needs to be created on the DB.
Each task is commanded by .cmd file and during the process they writes into .log file
Eg: Sasapappl0.tsk.bck
Sapappl0.tsk
Sapappl0.cmd
Sapappl0.log
Sapappl0.str - Structure of the DB
Control.xml
Keydb.xml -Helps to restart installation from the point where it is failed.
13
WHAT HAPPENS DURING INSTALLATION?
2. Sapinst tool is used to install the software if required we need to download it from
service.sap.com/swdc
Note: The user who initiates the installation should have the privileges as Local administrator to install
the software, create users, create groups, assign groups, create services etc., (This problems occurs in
a Domain)
If the user does not exist it creates now.
On Windows OS <SID>ADM is also responsible for database but on UNIX ORA<SID> is the owner
to work on the database. ORA<SID> provide the runtime environment for Database.
Windows
App Server Database
<SID>ADM <SID>ADM
UNIX
5. It creates local groups and global groups and assigns them to users
SAP_LocalAdmin
SAP_SOL_GlobalAdmin from Computer Management -> Local
SAP_SOL_LocalAdmin Users and Computers we can view this
6. It creates Services
SAP<SID> is used to start the SAP System; if the service is not started SAP will not start.
SAPOSCOL is started first to check whether the resources are available (Operating system collector) It
is used to collect the OS Utilization information and pass into SAP system.
SAPCCMSR is an agent to collect JARM (Java Application response time Management) and pass it to
ABAP CCMS (Computing Center Monitoring System)
It is only used in JAVA and ABAP stack.
Users
Groups
Services
Creating directories
Executables
- OS Dependent
- DB Dependent
15
Note:
Where the systems are installed with these schema owners i.e., these users owns the respective
databases.
Query:
9. Now command files are created pointing to .str and data on the exports
10. The task files are created to create the tables and load the entries
The task files are displayed as process on the installation screen
"2 complete 3 running 4 waiting"
11. Upon running all the tasks the SAP Database is created and DBStatistics runs.
12. DB Users are set with default password and SAP Application open RFC Connection.
--- Installation Successful --
16
SAP Installation Steps
\USR directory is created with a shared folder SAP with shared SAPMNT & SAPLOC
CCMS
PRFCLOG
PUT
SID HOSTS
Trans
CCMS - Used for alert logs that is populated by the service SAPCCMSR
(Java Stack Only)
SAPMnt: Is a shared SAP Mount which is used to host the directories related to SAP.
(It may be required to create SAPMnt in earlier versions but in the current versions based on
Netweaver it is created automatically)
SAPLoc in Windows
This SAPmnt is shared because it needs to share the transports, support packages, profiles,
executables etc between systems in the landscape.
TASKS
Installing SAP Component on SOLMAN
On Windows/ SQL Server
On Windows/ Oracle
Windows/ DB2
Linux/ Oracle
HPUnix/ Oracle
AIX
Solution Manager connects all the three systems (ERP i.e., ECC6.0, Netweaver & CRM2007)
18
I. Installation Inputs
SAPInst
SID
Mater Password
JCE Policy
Users,
Groups,
Services,
Directories,
SharedMnt,
Kernel (Extraction),
CreateDB,
LoadDB,
Updated Stats,
RFC's
DEFAULT USERS
SAPSR3
SAPSR3DB
A host is either a client or a server. A host has its own address on the network, and is its own
machine.
A server has its own address and sometimes multiple addresses. It provides access to services and
information.
Interface / Screen
Exports/ System Copies
Kernel [Dependent]
Install Mstr [Dependent]
Java Comp [Independent]
JRE [Dependent]
Exports [Independent of OS, DB]
Installation Directories D:\usr\sap
\USR directory is created with a shared folder SAP with shared SAPMNT & SAPLOC
These are shared between systems and accessed locally and globally
CCMS
PRFCLOG
20
PUT
SID HOSTS
Trans
CCMS - Used for alert logs that is populated by the service SAPCCMSR
(Java Stack Only)
PRFCLOG - These are also populated from JAVA Engine
(Generic Request Message Generator GRMG)
PUT - is used during upgrade
SID Hosts - the complete SAP Application Server.
Trans - is used to host the Developments
SAPLOCAL_ADMIN
SAPGLOBAL_ADMIN
ORA_SID_DBA
ORA_DBA
ORA_SID_OPERATOR
Check the USR Directory (SAP Instance files..... App) predefined shared SAP Directory with
SharedMnt, (SAPMnt), and SAPLoc on windows
Note: SID Specifies the Application Server and is possible to have multiple <SIDS> differed by the
instance number
Queries:
Note: In the console tree of SOLMAN if all the three entries (SERVICES, USERS and GROUPS) are
available then only we can confirm there are 3 Instances in one single system.
Config..... Usagetypes.properties - used to specify the usage types that are installed on the
system.
EP EP
BI BI
JAVA JAVA
ABAP ABAP
Enterprise Portal
Contains executables and profile parameters to start and stop the system
EXE Directory - hosts all the executables from netweaver exe dir contains
UC/ NUC and 32/64, i386/ ia64
17-jul-09
Instance:
Instance Name
Instance No: 00 - 99 (98, 99 for routing purposes)
23
Structure of INSTANCE
Instance contains Dispatcher, Queue Mechanism, and Work process, Task Handler with ABAP,
SCREEN, and SQL Interpreters. It also contains buffer areas, DB Client and Roll area.
Dispatcher
It is used to handle the user requests that are coming from SAP GUI using DIAG
(Dynamic Information Action Gateway) protocol on port 3200 + Instance Number.
(3201, 3202 etc)
Dispatcher manages all the work process and maintains a queue. Once the request is
sent to dispatcher the dispatcher keeps the request in queue. Based on the availability of work
process it will assign the process to the user request based on FIFO (First In First Out)
Work Process
Work process handles the user request using Task Handler. Task Handler contains 3
Interpreters ABAP, SCREEN and SQL.
24
ABAP interpreter used to interpret the ABAP code in the user request
SCREEN interpreter use to interpret the screen
SQL interpreter interprets the SQL statements that are sent by the user.
Open SQL
This is SAP Proprietary language to ensure that the SAP Components are Database
independent. Each instance is installed with DB Client software to communicate with Database in
Native Language.
The SAP Kernel which is O/S and DB Specific helps in the interpretation.
The user request is processed and it handovers (handshake) the task to Database process.
DBWP (Database work process) process and responds back to the R/3 work process. R/3 work process
checks for frequently accessed content and keeps the copy in R/3 Buffer areas. (Frequently accessed
data). The response rolls out into the user context before it is sent to the user.
User Context
It is a user specific roll area which is used to keep user authorizations, parameters, screens and
earlier accessed content.
1. User requests
2. Dispatcher handles the request
3. Keeps in queue and assign WP based on FIFO
4. The work process gets the username, password, client, logon language and the task handler
interprets and hand over the task to the database process.
5. The DB process checks the credentials of the user and provides the necessary authorizations to the
process.
6. The entire information is copied into the user context which is referred as
ROLL OUT. (The information is copied into Roll Area which is subsequently available for all the
requests made by the user)
25
Note: The user context remains until the user is logged out. The user context is displayed in the
transaction SU56. If the user accesses other than the transactions in SU56 it is missing authorizations
and displayed from the Tcode SU53 (Missing Authorizations)
1. User executes a transaction Eg: ME22N - Purchase Order (or) VA01 - Sales order
2. The request is handled by dispatcher and hand over to the work process.
3. Work process requires information that is not available in the work process. The work process
copies the user related information into the task handler i.e. copy user context into the Task Handler.
It is also referred as ROLL IN
4. Further processing continues
Even though the processes are unique at OS level SAP differentiated between the work
processes based on the nature of work.
The process are determined by the instance name DVEBMGS<Instance_No>
For Dialogue instances the work process will be denoted as D01, D02....
D - Dialogue
V - Update
E - Enqueue
B - Back ground
M - Message
G - Gateway
S - Spool
It hosts all the process and their will be only one central instance in the entire system.
1. DIALOGUE 'D'
It is only the process which communicates interactively with the users. There
should be atleast 2 Dialogue work process per instance. Dialogue work process initiates Update,
Background and Spool.
2. UPDATE 'V'
It is used to update the transactions in the database. It is initiated by Dialogue
process. There should be atleast 1 Update in the entire system. It is also recommended to have an
update process for every 5 Dialogue.
26
3. ENQUEUE 'E'
It is used to provide locks for the records that are going to be updated. It ensures
consistency for updates. There will be only 1 Enqueue configured in the system during the
installation. It is possible to have more than one enqueue provided they are installed or configured on
the central instance.
4. BACKGROUND 'B'
The tasks which are expensive or time consuming are scheduled to run in the
background mode non-interactively. There should be atleast 2 background work process in the
system
5. MESSAGE 'M'
There should be only 1 message server in the entire R/3 system. It is used to manage
all the dispatchers. It is used to load balance the requests to identify the least loaded dispatcher.
It is also used to provide locks to the request that are coming from Dialogue instances.
6. GATEWAY 'G'
It is used to provide a means of communication with SAP and NON-SAP systems. There
will be only 1 gateway for each instance.
7. SPOOL 'S'
It is used to print the documents to a printer or output to a fax machine etc. There
should be atleast 1 Spool process in the entire system. It is also possible to configure more spool
process depending on the print/ spool volume.
18-jul-09
DVEBMGS00
Dialogue - Interactive - 2 per instance - Initiate update, spool and btc (background)
Enqueue - Provides consistency for updates - 1 per system and can be increased
Depending upon the update requests but needs to increase only on the
Central instance for optimal performance.
27
Message - Used during load balancing. It also procures lock from enqueue server
To serve the requests that is coming from dialogue instances. Only 1
Per system.
Spool - It is only the process that outputs the documents to printers, fax etc.
It is initialized by Dialogue and BTC. Atleast 1 spool per system.
INSTALLATION
6. Install JRE 1.4.2_12 (Java Run time environment) to run the sap inst screens
28
7. Set the JAVA environment variable JAVA_HOME or path
Check java -version
9. Set the host name which should not be more than 13 characters
11. Ensure that the installation ports 21212, 21213 are not blocked
(Need to inform Network Admin or Proxy Admin not to block the ports)
12. Ensure that 3200, 3300, 3600, 4700, 4800 series ports are not blocked.
(DVEBMGS utilises these ports)
13. Dump the software into the system. The folders should not contain spaces,
Special characters etc (Eg NWDump or Newfolder - all one word), underscores
are allowed
15. Get the private static IP address from the Network team (192., 172., 10. networks)
PRACTICAL SESSIONS
www.service.sap.com/instguides
www.service.sap.com/platforms
www.sercvice.sap.com/swdc
- My companies Application component
- ERP 6.0
Market place > Help and Support > Search for Notes
T1 Shopper Port scan - To check whether these ports are open or blocked.
IDES (International Demo Education System) will have more clients 11-12 Predefined clients and in
the Non-IDES system only 3 Clients (000, 001, 066)
In IDES additional clients - 800, 811, 812 clients are available.
There will be only 2 exports for Non - IDES system
And 6 Exports for IDES system.
LABEL.ASC - contains the content and the DVD number from which we can find whether it is an Export
1 Or Export 2 etc.
Note: Only exports will change for each application like CRM, SCM, SRM etc
20-jul-09
INSTALLATION
1. Central Instance
2. Database Instance
3. Dialogue Instance
JCE Policy
JAVA Cryptography which is used to provide the secured encryption & decryption over the
web - because the content transmission over the web is not secure.
- The input lists screen is displayed to review before starting the installation.
- Continue the installation
- Installation depends upon the export content (IDES version may consume 8-12 Hrs) Production
version ma take 4-6 Hrs. It also depends upon the memory.
Components lies in ECC6.0 are (SALES, FINANCE, and PURCHASE... around 35 modules)
31
To display all these over the web then EP (Enterprise portal) is required.
Note: All the SAP components will be installed on the Netweaver Platform. It is up to the customer to
choose the Netweaver components and It is mandatory to choose ABAP components. ABAP is the
platform for all the SAP Components.
ABAP is a part of the Netweaver.
ABAP provides the runtime environment for all the above components i.e. USER Management,
Administration, Management of the file system, processes securing the sensitive data, fine tuning the
performance, database administration irrespective of the SAP component and also managing printers.
SAP is a transaction based. Menu based consumes more dialogue steps than transaction based that is
why SAP BASIS consultants are more familiar with transactions.
32
Login to the system with SAP*, DDIC and Master password (specified during installation)
1. Execute transaction SM28/ SICK (Installation consistency check). It checks the compatibility
between OS, DB and the R/3 kernels. If there is any inconsistency it will recommends us to fix before
proceeding further. Based on the displayed message we may need to upgrade OS patch levels, DB
support packs and R/3 Kernels.
SM28/ SICK
2. SLICENSE - It is a transaction that is used to apply the license to get the runtime support for
the system even though it is valid for 30 days (4 Weeks i.e. 28 days). It is recommended to apply
license because they are not considered for support.
Except DEV and SANDBOX remaining all the systems like QAS, PRD, PRE-PRD are set to not-
modifiable i.e. no object can be modified in these systems.
The changes are only transported to the not modifiable systems.
21-jul-09
Checks for the Incompatibility between R/3 Patch Levels, Kernel Levels, OS levels and Database
patch levels.
2. SLICENSE
SAP Issues two licenses, one is the permanent key valid upto [31129999]
The other one is Maintenance Certificate which is valid upto 3 Months. This Maintenance certificate
is introduced from JAN/ 2009 onwards. It locks SPAM so that no upgrades are allowed without a valid
Maintenance certificate.
SE06 transaction is used to set the CTS (Change Transport System). It initializes the Transport
Management system. A message will populate to configure TMS in the client 000.
35
TMS: Transport Management System. It is used to setup the systems, their roles, Domain controller,
backup domain controller, landscape and their routes.
1. Domain Controller: There will be only one Domain Controller in the system landscape. In most of
the environments [DEV] is treated as DC because, this is the first system in the Landscape
Login to the system/ Client 000 with the user other than SAP*/ DDIC
Execute T-Code STMS
NOTE: If the Domain already exists then we can execute a TCode [DICO] to delete the existing TMS
configuration. It should be executed in STMS and also the RFC connections.
TMSADM is a communication user created during TMS configuration (Do not delete the user, lock
the user, change password, set to expiry will hault the system transports, support packages and
applicatoins etc)
A message SAP system "waiting to be included in the transport domain" is displayed in the external
system.
Login to the DC
Execute STMS
From Menu Overview > Systems
The system is waiting to be included
Select the system and click on approve from Menu SAP System.
Virtual Machines/ Systems can be replaced by real systems and the configuration now points
to the real system.
System : JOQ
Description : Quality System
TRANSPORT GROUP
It is a naming convention group_<SID> we can configure all the systems to a single transport group
i.e. all the developments which are performed in Development system will be automatically available
to other systems in the landscape. The group of systems which shares the transport directory in
common are said to be in one group but due to sensitivity of PRD it is moved into a separate group.
1.
Shared Data
2.
22-jul-09
Perform DICO to delete the STMS configured earlier if necessary and the RFC connection from the
external system.
Create an new user as SAPUSER copied from SAP*/ DDIC logging in as SAP* user from the newly
created client.
Login to the new client with our userid and password and lock the DDIC and SAP*
Execute SMW0
Click on execute
39
Create new
Obj name : ZTEST
Desc : IMAGE
Browse for the Picture
GOTO - SM30
Click on maintain
Click on new entries
START_IMAGE : ZTEST
Prompts for the Change request - proceed and test the logo
SETTING UP TEXT
Execute - SE61
40
1. SICK
2. SE06
3. SE03
5. RZ10
Used to import the profiles from OS level to DB. The profiles are available in
\usr\sap\<sid>\sys\profile. These profile requires management for fine tuning, configuring buffers etc
From 000 > Goto RZ10 > Utilities > Import profiles of Active servers >SAVE
6. SMLT
41
Perform language transports if any. The system is an unicoded system to support the
all available languages but we need to import the additional languages as per the requirements.
Download the languages in
\usr\sap\trans\eps\in Directory
Goto SMLT > and create a language > specify supplementary language i.e. if the script is not
available in main language it will display in secondary language.
English > Primary
German > Secondary
Clink on ADD from NLS settings to include additional languages that are going to be
imported using SMLT.
Steps:
42
1. Execute I18N
2. Add language that needs to be imported in I18N
3. SMLT create language
4. Click on > Import package > specify the path \usr\sap\trans\eps\in
6. SPAM
Apply the patches that are relevant for SAP application component
SAP Provides screen context help i.e. when a user struck at one screen he can use Menu Help >
Application help.
SR13 >
New Entries
1. Dynamic Help
2. Plain Html Help - Html documentation installed on Web Server
3. Plain HTML - HTML docu installed on File server
4. HTML Help File - It occupies less space, opened by html help viewer.
It is in compressed format.
For documentation > Market Place > SAP Solutions > SAP ERP >English
Note: Need to create a folder in D:\SAPHELP...... (sapdocdc.ini) paste the path.
Note: Create users in SU01 and assign SAP_ALL to the functional and technical team as the security is
not implemented.
24-jul-09
Dispatcher - DPMON
Workprocess - SM50/ SM66
User Context - SU56
Task Handler - from Work Directory
Buffers - ST02
Dispatcher receives the request and processes them according to the queue. The requests are
processed by using a dialogue process. Dialogue process is the only process that interacts with/
communicates interactively with the user. There should be atleast 2 Dialogue process per instance.
Each process requires 75MB to 150MB of memory on any average.
The memory should be calculated after reserving memory for OS and the Database.
Min and Max upto 40 Processes, but depends upon how heavy the processing goes.. If a reporting
user requires 3GB of memory then there will be a memory bottleneck.
The maximum number of work process an instance can support is W0 to W99 (100 Work processes).
There are cases where more than 100 are configured but it is not recommended. If the system
supports more than 100 processes then it is better to configure one more instance on the same server
differed by the instance number.
The dialogue response time should be around 600 to 1000 Milliseconds (1 Second)
Each dialogue process is restricted by using a parameter rdisp/max_wprun_time = 600 s
(10 Minutes) after which the process will be timed out. In order to run the activities that consume
more time then the above we need to run in the background mode or increase the parameter value
from RZ11 (Dynamic parameter) i.e. during the month end the parameter can be changed to 1800 -
10000 from RZ11 for specific period of time. Upon task completion reset the value in RZ11 (No
system restart is required)
Each user transaction may be served by one or more processes with out restricting to the user
similarly each work process serve multiple users with out restricting the user. (No dialogue process
remains ideal)
Each process can serve 5 - 10 users and Each SAP transaction consists of multiple (LUW -
Logical unit of work) Each LUW contains task which should be completed/ rollback as a group. Each
LUW is a commit or rollback (no intermediate stage ... which makes the system inconsistency)
2. BIND 1 & 2
Tickets to and fro + Accommodation)
Each of the LUW is performed by a single different work process and is restricted to 600 Seconds and
task has to complete within 600 milliseconds
46
LICENSING
10 + 1
Users Developer
4% VAT 48,000
17% Maintenance /Year 2, 04,000
-------------------------
14,04, 000
5 1 2
22% 24% 26%
Once the license key is received then goto SLICENSE Tcode -> INSTALL
And click Install new licenses button
25-jul-09
Dialogue handles the requests and process only reports with out any assistance. If the reports are
long running, time consuming, expensive then they can be scheduled to run in the BTC mode.
During an update dialogue updates temporary table and update-process updates them later.
48
For print requests Dialogue handles the request and update in Temse. The spool process
Prints from Temse (Temporary Sequential file it can be at file/ DB Table)
Dialogue communicates with enqueue while updating a transaction and obtains lock so that no user
can update there by assuring data consistency.
Dialogue communicates with the message server to obtain locks for a record that is coming from
Dialogue instance.
Dialogue communicates with the gateway while establishing connection with other SAP systems.
DPMON.exe is a dispatcher monitor which can be executed when the user could not login to the
system (Experience Hour glass). Its not a TCode.
Work process list is displayed in SM50/ SM66. Each process has the following
Waiting for
PRIV Mode: The process goes into Heap mode. It will be completed only after the task
completion/ timeout.
SLEEP MODE: The work process goes into sleep mode waiting for resources (RFC
problem)
- Restart YES/ NO : if the process is terminated and it will restart automatically (Yes), not restart(NO)
26-jul-09
It displays the processes based on status. It displays the processes belongs to all the instances.
From SM66 - Click on SELECT PROCESS
50
The major advantage of this is it displays the memory consumed by work process. Double click on
the WP to display (Extended, Roll and the Heap Memory)
On Oracle execute
SM04 : is used to display the logged in users along with the sessions. We can terminate
the session or the user completely using End session or logoff user.
From User > Logoff User > Local or End the session
It is used to run the expensive programs, reports that consumes more time in the background mode.
i.e. a job is scheduled to run at a specific time or periodically.
Example: Daily report, Weekly sales report or expensive to run in the peak hours so they are
scheduled to run in the background mode during off peak hours.
Process Flow
5. BWP looks into the table and identify the jobs which are in the Ready State.
6. BWP runs the job in the Active mode till completion/ Cancelled.
BWP are defined by using rdisp/wp_no_btc=2 (Min 2 per system)
We can increase as many as possible depending upon the resources.
Class A requires a dedicated BTC of class A which are defined in operation modes.
Class B has medium priority over class C jobs
Class C jobs runs with Normal Priority
JOB STATUS
Execution server - Name of the instance that provides BWP to run the job
Exec Target - Willsys_<SID>_00
Click on step
JOB STEPS
We need to specify the following for the JOB Execution
1. ABAP Program
2. External Command
3. External Program
1. ABAP Program - Is a predefined program that will be run in the background with user inputs as
variants.
2. External Commands: The job can be executed by external commands which are defined in SM49/
SM69. These commands are OS commands that will be executed at command level.
3. External Programs:
NAME: Name of the program
Parameter:
Target Host:
Name : Specify the name of the program and the parameters. Specify the name of the target host.
Specify the start condition
Immediate/ Periodic/ Jobstart, Event (SM62)/ Operation. Modes.
It is the process of switching DIA to BTC and vice versa during the peak hours as we need more
dialogue process and during off peak we need more BWP to run the BTC jobs.
rdisp/wp_no_btc = 2
rdisp/btctime = 10
Execute SM37
Specify username, date & time, job name, status ----- Execute F8
1. The jobs with status RELEASED indicate the jobs are released with scheduled time and waiting for
their turn/ time.
2. The jobs with status READY indicates the jobs are ready to pickup by the scheduler
Eg: Consider a CAB - might come late
No sufficient CABS
1. The existing jobs are running for a long time i.e. expensive programming or sql statements/
fetching huge amount of data.
2. The configured BTC processes are not sufficient to handle the requests in Ready status.
4. Also due to passing the jobs by extending scheduler time/ making BTC to 0 by running the
program BTCTRNS1.
Action:
1. Increase BTC work processes based on the available resources by using the parameter
rdisp/wp_no_btc = 2
1. Some jobs are bound to run for hours and based on history leave them to run.
2. Check the bottle neck on the target system (ERP-BI-EP-SRM-SCM-SRM)
3. Wait until the locks are released/ jobs are completed. Report to SAP in case of dead locks.
Select the status - Db click - and click on Job Logs
Execute SM37
5. CANCELLED
1. User and password Issues (Authentication/ Authorization) user lock, userid expiry, password
change, lack of roles etc.
2. File system problems: BTC reads from the file system to update the database. File not opened, or
corrupted, file sharing issues, file came with different characters, file not found as well.
10. Problem in the program and inputs (Indefinite loops like 1/0)
1. As a part of the post installation we need to schedule house keeping jobs in SM36
Execute SM36
Click on "Standard Background Jobs"
56
Click on Execute
1. Used to display the jobs based on job, username, date and status
5. Background job out put is a report to a spool (Printer), fax or email or even updating a database
(Eg. Client Copy)
28-jul-09
1. CONTROL-M Scheduler
2. RED WOOD Scheduler
3. TIDEL Scheduler
4. SAP Job Scheduler
5. MAESTRO Scheduler / IBM
These Third party schedulers are not specific to SAP but we can customise these to SAP
These job schedulers are intelligent to work based on the status of Predecessors.
The tool defines when to trigger, how to handle various statuses and alert users accordingly.
Sony an electronics company communicates with suppliers for the TV Cabinets/ Circuit boards, Picture
tubes, assembling & packing.
9. To run Database jobs using external commands DB13 (SM49 provides commands)
NOTE: In table TSTC, we can get a list of all existing Tcodes and which programs are called by those
transactions.
From SE11 - Provide the table name TSTC and execute providing the T-Code to find the Program
BTC logs are deleted by scheduling RSBTCDEL which deletes the log files from TBTC* based on the
time interval in the Variant SA38.
UPDATE PROCESS
It is used to update the database from Temporary tables. There are three 3 Types of updates
Technically for every 5 dialogue work process there should be one update of type V1/ V2
Update Flow:
And gets a transaction ID from Number Range Buffer (Transaction SNRO and Table NRIV Number
Range Interval Table)
SNRO
NRIV
Eg:
63
5. Update gets initialized and reads from Temp Tables and updates the permanent tables
synchronously. Update inherits the locks and releases them upon updating permanent tables. Update
updates the record based on transaction-ID using VBMOD Table (Every update is module based in
SAP)
6. When the Dialogue updates the temp tables the record is displayed in SM13 which will be
processed by update.
The record that needs to be updated by update process is displayed in SM13 with status INIT.
If the records stays for longer time in INIT status that indicates the updates are busy or there are no
sufficient update processes or update mechanism is deactivate from SM14.
1. Longer Update
2. Dead Lock (Needs to inform SAP for Program correction)
Updates which could not be updated will be thrown into ERR Status.
29-jul-09
UPDATE Statuses.
Used to repeat the ERR updates. The update are terminated or cancelled due to the following reasons
At this point of time we need to select the update (put a check mark of the update from SM13) and
click on [Repeat Update]
rdisp/vbdelete=30 to delete the update records older than 30 days irrespective of the status.
We can see either V1 or V2 in the standard SAP Program SAPMV45A by executing SE38
1. There will be only one message server through out the System.
2. It is used to manage all the dispatchers and identify the least loaded dispatcher and forward
the user request to the dispatcher provided logon load balancing is configured in transaction SMLG
66
Logon Groups SMLG
We can find the Active servers from SM51 and on db click on the Host name to view all the Processes.
CONFIGURING SMLG
3. Open GUI > Select groups and create entry by choosing group.
Mechanism
2. sapmsg.ini gets evaluated and checks the port in etc\services to communicate with the
message server.
3. Message server maintains the details of favorite server and routes the request to that
dispatcher
Message server obtains the lock for dialogue process if the request is coming from the Dialogue
instances.
Note: Server Naming convention is used because each of the process serving the user requests
(Dialogue, BTC, Update, Enqueue, Message, Gateway and Spool DVEBMGS)
It is also possible to install and configure all the above servers on different instances or hosts.
ENQUEUE:
It is used to provide data consistency while updating the system. It provides locks from a
lock table before a record gets updated and ensure that the record is available for display during an
update.
68
There will be 1 One Enqueue process installed during installation. It is also possible to increase
Enqueue processes to more than one depending upon the updates but most of the customer
environments there will be only 1 One enqueue process.
30-jul-09
DEAD LOCK
X + Y (LUW1) A + B (LUW1)
Z + M (LUW2) X + Y (LUW2) Dead Lock
Q + R (LUW3) R + Q (LUW3)
Enqueue process the locks and unlock the record during an update.
Enqueue server maintains the lock table on the shared memory of the Central Instance (or on the
instance where it is installed)
Technically the Message and the Enqueue should reside on the same instance (It is not mandatory). If
both are installed on the same machine then it will be more comfortable for message server to
communicate with Enqueue process to obtain locks for Dialogue process that are coming from other
instances.
RFC
69
DIA - MSSG - ENQ - MSSG - LOCK - DIA
Shared Mode
Exclusive Mode.
Locks are monitored in transaction SM12. In principle the lock which are older than one hour
should be reported to the escalation manager. If the lock table is filled (Enque/ Table_size) an
overflow occurs in the lock table.
1. Check whether the update server is still performing the updates. If the updating has stopped, then
the lock table can quickly become over filled with the locks held by update requests. We can resolve
the problem by restarting the updates. If updating has not been interpreted, then we must enlarge
the lock table.
Eg: Execute SU01 from Shawn user/ 800 and edit shramana user
Execute SU01 from Shawn user/800 and edit shramana user
And now execute SM12 which displays the Exclusive Mode lock
2. Update is deactivate (SM14) due to any of the issues in DB. If the update gets deactivated then the
locks are not released.
3. If the Enqueue time increases i.e. there could be RFC issue or Enque wait time is increasing then
consider increasing Enqueue work processes.
4. Dead locks (Usually never occurs, but there is a collision between PP, Manufacturing and Material
Module, so highlight this issue to SAP)
In some instances we may need to release the locks but we need to follow certain process.
Do not release the lock in SM12 (Even though there is an option)
1. Users complaint that he could not update a record and message pop up stating that the record is
locked by user XYZ.
2. Check the period of lock (if it is older than 1 hour inform to the escalation manager)
3. Get the written B&W approval from the user and terminate the session of that user using SM04.
(Only Terminate or End that session)
We may need to allow some locks for more than one hour or days (Eg. Payroll update
processing) consumes lot of time. We need to ensure that dialogue process should not held for
longer time, but however BTC is allowed.
31-jul-09
SPOOL PROCESSING
PROCESS/ FLOW:
1. User request to print a purchase order (or) user schedule to print dunning reports (LEGAL Notices,
Credits, LOANS etc)
2. These print request are processed by the respective Dialogue/ BTC and stores the content in TEMSE
- Temse is a temporary sequential objects that are stored at OS (File system) or Database level which
is defined by the parameter
rspo/store_location=G or DB
Note:
DIALOGUE - Multiplexing
BTC - Single Process
Refer:
SU22 - (s_spo_act) - To identify the tcode/ Authorization objects
SP01
SU24
The Temse can be stored in database or OS level. Temse remains in the DB/OS unless they are
deleted explicitly by SAP standard reports.
OS [G]
1. It is recommended because the print request are printed faster than database. i.e., from Global
directory requests can be converted to output request at faster rate than database.
2. This is only recommended when the requests are small in nature. (Every day 50-100 Docs) if the size
increases the search at file level consumes more time as (No indexes at file system)
72
3. File system is not backup frequently as Database. File system backup will be weekly, fortnight,
monthly whereas database is hourly (Redo Logs) and daily DB Backup. That is Temse is not secured at
file system.
DB [DB]
1. Consumes more time than Temse at OS when there are less no of records. but shows the
performance by using Indexes when the user grows (Temse can handle 90000 Requests)
Temse is a part of Normal Database (TST01 and TST03) no separate memory is required.
Default setting is DB
RZ11 : rspo_location
: rdisp/ btctime
3. The Spool process reads from TST01 and TST03 i.e. the name of the author (USER), Name of the
Printer, No of copies are procured from TST01 and Printable data from TST03
73
Spool Process formats or converts spool requests to output requests i.e. Printer specific format. If
the format is performed locally then it is said to be LAN (Local Access Method). If it is performed
remotely then it is said to be RAM (Remote access Method)
TPFYPROPTY
01-Aug-09
SAP System
Note: We should not touch the Repository data of name space 'A' to 'X'.
SE11 > table name : /* (/ is a customer name space)
74
TADIR is the repository
TSTC - Is the T-Codes with the program name.
Market place > keys & Reqs > Development Name space.
SPOOL MECHANISM
Spool process reads from TEMSE and convert spool requests to the output requests (Printer specific
requests).
The instance with atleast one spool process is referred as spool server. It is also referred as Real
spool server. (Existing)
This is not existing but pointed to a Real spool/ another logical spool server. This is used for load
balancing the spools.
75
1. Execute SPAD
2. Click on the Spool Server - Display then Change
3. Click on create
Server Name: LOGICAL SP1
Server Class : Mass Printing
1. Execute SPAD
2. Click on output device
3. Click on display
4. Click on change
5. Click on create
Model: 2200
--------------------
Note:
ACCESS METHODS
It specifies the process of formatting the spool request to printer specific output
request.
The spool work process and the host spool resides in the same machine i.e. the work process transfers
the spool request to the spool system locally.
Disadvantages: No user can print in the background because the desktop initiation is not possible in
the background during off peak hours.
Restrict the no of work process that can go into front end mode using the parameter.
rdisp/wp_no_spo_fro_max = 2
i.e. two work processes can be used for front end printing. If this parameter is not used spool
congestion occurs.
Specify I for Achieving device (Optical Devices, HSM, Jukebox (stores each copy (output doc))
Hierarchal storage machine
79
REMOTE ACCESS METHODS
Specify U for UNIX operating system where formatting is performed on the remote machine (Print
server) using Berkeley protocol.
Specify S for windows operating system. It will transfer the formatting to remote system using
SAP specific protocol SAPLPD
The spool requests are monitored in SP01. users can monitor the requests using SP02.
Note:
Put a check mark [ ] Do not query host spooler for output requests. If this option is checked, It
improves performance. If we need the exact status then uncheck the box.
Output Attributes: Depends upon the company requirements. Tray info is also similar.
-----
The Major advantage of TEMSE is the documents can be displayed even before it is printed.
1. Status '- Minus' : Indicates not yet sent to the host system (No output requests exist)
The spool process is busy/ congested, if too many requests with
this Status indicates need for increasing spool WP.
5. Printing : The host spool is printing the output request. If the SAP spool
system does not receive any status information from the host
spool, this status displayed for approximately one minute. The
system then sets the status to Complete (Competed or Error)
1. Printer issues like (Page setting issues, cartridge issues, printer not available) paper out, print server
not available) these printer specific issues will be resolved by Network Team/ Print Team.
2. User complain that they could not print documents to a specific printer.
- Check the availability of the printer, if required we can change the printer and reprint the
document.
From SP01 --- Select the request -- Use Menu "Spool Request and print directly" or select print with
changed parameters.
While changing the parameter we can set the priority between 1 - 10 (1 as High)
- The TEMSE is full i.e. TEMSE will be full when it reaches 99,000 requests and log is generated
in SM21 (System Log)
- We need to reorganize the spool requests using the SAP standard reports. (RSPO1041,
RSPO1043, RSPO0041, RSPO0043). These are used to delete the old spool requests based on
selection criteria. In general the spool requests which are older than 14 days will be deleted if
standard jobs are scheduled in SM36 they also checks the consistency of TEMSE periodically.
- We can also use SPAD for reorganization of spool (but the logic is same)
For this
Execute - SPAD > Full ADMIN > ADMIN > Delete old spool requests
Or from SA38 execute the program - RSPO0041
-----------
Refer SM01 - Transaction Codes [Lock/ Unlock]
82
----------
Note: If we need to forward a spool request select the request in SP01 and forward it to another user
where user can print from alternative printer.
Use SBWP (SAP business work place) to display the request in inbox.
PRINT QUEUES
Note: Should have enough spool work process to format the requests to printer specific requests.
Similarly we should have enough output devices to avoid the print queues.
From SU01 we can specify default printer to the user but do not check the box "delete the request
after output immediately" which improves the spool performance.
03-Aug-09
83
Dialogue
2 Min / Instance
75 - 150 MB
5 - 10 Users (Refer ST07)
Handles request Interactively
Multiplexing
Rdisp/max_wp_runtime = 600
SM50/ SM66
wp_no_dia
DPMON
It initiates update, BTC, spool, Message server and enqueue
BTC
SMGW is used to monitor the gateway process. Gateway is used to communicate between SAP and
NON-SAP systems. There will be only 1 gateway/ instance. If required we can also install a standalone
gateway on a JAVA engine.
Gateway listens on port '3300'+instance number (3300, 3301,3302 where 01, 02 are the instances).
Gateway provides an interface so that the external system can communicate with SAP system on the
specified port.
84
When RFC's are defined between the systems they use SAP gateway when (ALE, EDI, IDOC are
transferring they use gateway)
INSTANCE MANAGEMENT
1. Default
2. Startup
3. Instance Profile
As part of post installation we import the profiles of Active servers from RZ10.
The profiles resides at OS level in the directory (usr\sap\<SID>\sys\profile). They can be managed/
edited using a notepad. But the consistency is not checked (say for eg. if we modify the instance
profile WP DIA=2000 and there is no error message and versions are not maintained under OS level)
DEV_DVEBMGS00_willsysdel.
So these profiles are imported into database management for consistency check and version
management.
Startup Profile
Starting Database
Starting Message Server
Dispatcher + Work.
Do not modify these parameter under any circumstances on OS level.
Default Profile
It is used to provide global parameters for all the instances, buffer parameters, security
parameters (Password, User restrictions), Message server host, enqueue host)
Instance Profile
This is specific to instance configuration such as work process, timeout parameters etc.
Starting Sequence
85
1. Startup profile is read by the system to start the engine by starting database, message server and
dispatcher in Central Instance.
2. Startup profile is read by the system to start the engine by starting (DISP+WORK) on dialogue
instance.
3. There will be only one default profile in the entire system which provides global values.
4. Instance specific profile - This is used to set the instance specific parameters.
Eg. How many profiles are available on a system with 10 Dialogue instances.
PROFILE MANAGEMENT
RZ11 is also used to change some parameters dynamically without restarting the system but they will
be reset once the system is restarted.
RZ10
There are three types of Administration.
86
1. Administration data
No need to maintain using this option. It only specifies the path of the
parameters.
2. Basic Maintenance:
It is used to maintain the profile parameters without any technical names. GUI based
using mouse
87
3. Extended Maintenance
Profiles are changed on SAP recommendation or based on experience. Do not change any of the
profiles on trail and error method. System will hang and may not restart.
04-Aug-09
It is used to route the requests to the least loaded instance of that group.
Factors to define LLB.
Identify the components along with users. If the users are logging to different instances the buffers
are scattered therefore they are not effectively used.
So for this
Mechanism
5. Message server communicates will all the dispatchers and identifies the least loaded server and
mark it as a favorite server in SMLG. The request is routed to the favorite server.
During the implementation of the legacy system needs to be preserved or used in the current system.
Example: A customer/ company is running business for the past 30 Years. He is maintaining customer
details, vendor details, supplier details, employees and salaries, account payables, account receivables
and P&L (Profit and Loss). This information is required by the customer in SAP System. So there is
need to transfer the legacy system data to SAP system.
Example: Customer implemented SAP but the employees who are old cannot make use of SAP
system. They would like to work on the traditional systems. After go live both systems SAP and legacy
travel parallely. The data entered in the legacy system i.e. PO's, Invoices, Billing, Shipping are to be
transferred periodically(Hourly) bi-hourly(for every 4 hrs) or daily
SO --- PO
BI ---- INV
Example: Reliance, Hero Honda [B2B Company to Dealers] not B2C [Distributers to customers] they
communicate with dealers, suppliers, using SAP. But dealers and suppliers use non-SAP system so it is
required to establish communication between SAP and NON SAP systems and perform the data
transfer periodically.
RFC is used to communicate between SAP systems and SAP to Non-SAP systems using TCP/IP
protocol. RFC's are defined in [SM59]. There are 4 types of RFC's
90
1. Asynchronous RFC
2. Synchronous RFC
3. Transactional RFC
4. Queue RFC
1. Asynchronous RFC - (Like a post card). The sending system may or may not receive it. i.e. there is
no acknowledgement from the receiving . The transmission is not reliable.
2. Synchronous RFC - It is not like ARFC. It gets an acknowledgement from the target system. (like a
register post).
If the receiving system is not available the process goes into RFC/ CPIC/ Sleep
mode and waits until it is wakened by the target system. Target system/ Receiving system may be
busy i.e. all the resources are used up. This is reliable but time consuming and expensive (Client Copy)
the job should get finished.
Note: SAP uses CPIC protocol SAP specific (Common Programming Interface for Communication) to
communicate between system.
3. Transactional RFC - TRFC - It is an advanced version of ARFC and SRFC. The request goes to
receiving system if it is not handled a Transaction ID is generated by the source system. A program
RSARFCSE is scheduled in the background to run for every 60 seconds.
Transaction SM58 is used for Transactional RFC. It is used to document all the
transactional ID's and ensure that they are received by the recipient system.
This is consistence and reliable.
A user is created in the parent client and transferred to the child client when they are available?
4. Queued RFC - It is an advanced version of TRF and ensures that the transaction is committed
based on FIFO/ Queue. It ensures transaction consistency of LUW and reliability of data transmission.
SMQ1 - to monitor the outbound queues of a sending system refer SCOTT for FAX...
SMQ2 - Provides interface to monitor Inbound queues.
91
05-Aug-09
SAP systems consists of more than one client - technically 1000 client can be created in one system.
So we need to identify which client is the business client. Preciously SAP is client based (A mandatory
field while login)
Each client is defined with a logical system name that is defined in SALE. (Sap System linking and
enabling). Each system is identified by SID, client by 3 digit number. So, Logical system number
should be <SID>CLNT<CLNT_Number>
Eg. DEVCLNT900
Goto > BD64 or SALE > To define the sending systems and receiving systems
Or
Use the SAP standard moral for that application.
DEVCLNT001
DEVCLNT000
DELCLNT001 save to configure CUA
Users are distributed to the child client using TRFC(SM58) and if the client system is not
Available the record hangs in SM58 and ensure that is updated in the child client.
To delete : Execute report : RSDELCUA or SCUA select the client and delete.
IDOCS (Intermediate Documents) are used to transfer the data. It will be in the
Understandable format of both sending and receiving systems. SAP - NON SAP.
SYSTEM MONITORING
06-Aug-09
Monitor the instance specific processes in SM50 and Global Specific Process overview based on
status in SM66.
Monitor the processes with status(reasons) running, hold, stopped, sleep, RFC/ CPIC, PRIV.
Identify the user, time, client, Action.
If BTC is running for longer times check whether it is permissible as per the process document.
Dialogue process should not consume more than 1-2 seconds for normal tasks. It will be
automatically down (Killed) by system in 600 Seconds. If it is not killed the process might be occupied
by dedicated resource and uses heap memory with status PRIV. The process has to complete the job
or Heap Memory should exhaust, so that process comes out. We may need to kill the processes with
status PRIV using DPMON, Task Manager or Kill -9 Command on UNIX.
If more number goes into PRIV we may need to restart the instance.
Standard Jobs
- RSBTCDEL - Deletes the batch job logs
95
- RSSNAPDL - Delete Old ABAP Dumps
- RSPO1041 - Delete Old spool logs and files
- RSMO13002- Delete old update request logs
- RSCOLL00 - Collects performance info in Transaction ST03
- RSPO1043 - Spool Reorganization.
DPMON - When the user could not login to the system (Experience Hour glass)
Process the list @ OS Level
DPMON
K
Provide SR. Number
Provide PID.
07-Aug-09
Exports [1 of 4 ]
Kernel, Java Components
> Add to download Basket
Paste in
<SID>\sys\exe\UC |
SYSTEM MONITORING
Each customer provides a standard check list to monitor their systems from time to time.
Eg: BSI (British Standard Institute) requests the consultants to monitor the system on hourly basis.
96
P&G requests their production systems to be monitored periodically for every 8 Hrs.
1. Identify the instances which are down i.e. SM51 to list the servers and monitor the instances
which are up and running. If any instance is down, we need to report with high priority.
2. Analyse the reason for failure (Check if the system is scheduled for downtime) If we are
authorized start the instance and if it could not be started then look into work directory for logs.
----
IMPORT ABAP : c:\prog files\sapinst_instdir\erp\system\ora\central\as
Err, Ok, exe.
----
08-Aug-09
TRANSPORT GROUPS
Security
On JOD >
97
Perform SICK
SE06 > Standard Installation - Perform Post Installation
DICO
STMS
1. Login to DC (Domain Controller) Development System/ 000 client with user like DDIC
SAVE
Upon saving the request from quality system is sent to DC to include in the domain.
5. Login to the DC
6. From DC
From Menu Overview > Systems
JOD
JOQ
JOP
Select the system JOP from SAP System Menu > Click on approve.
Select the system JOQ and click on Approve from Menu SAP System > Approve
98
TRANSPORT GROUP
If each system has their own transport group i.e. they maintain transport groups
themselves i.e. 3 - Transport directories are configured.
Note: In principle there will be only one client in the production system.
SYSTEM MONITORING
SM51
SM50/ SM66
SM13
SM14
SM37
SP01
99
SM04/ AL08 : Used to identify the number of users logged on to the instance. Identify the users
who are consuming more memory and also identify the transactions and identify why it is consuming
more time. This TCODE is also used to logoff the user session if required.
AL08
SM04
SM21: System logs specific to the instance. We can also identify the logs of other instances.
System log > Remote system
It is used to display the logs for the following activities.
100
When ever a SAP Program (ABAP program) could not be executed due to an error it will be thrown
out from the GUI- Screen and a dump is recorded in ST22.
2. Memory related issues with error message PXA, SWAP, PAGE, OUT OF MEMORY.
This error requires memory corrections to the parameters.
3. Program Corrections: The problem is with SAP standard program for which SAP provides a
correction through notes (The correction can be applied through SNOTE)
4. Customer defined programs ('Y', 'Z') consumes more memory, endless loops, improper select
statements etc. The program need to be corrected by the developer.
7. Database issues like table space over flow, max-extents reached, archive stuck.
8. Illegal time: (Day light savings) - During day light savings the system date and time has to be
changed. Stop the AS and change the date if not, the above error occurs.
Note
09-Aug-09
PERFORMANCE TUNING ST02
102
This complete journey should be completed within 600 Milli seconds on an average or goes up to 600
Seconds Max.
1. Front End Time/ GUI Time : Time taken by the user to reach the dispatcher is called as Front end
time. The GUI time should not exceed more than 200 M.Sec. If it exceeds this consider the following.
Note: GUI response time is not considered as a part of the Dialogue response time because the
request is not received by the dispatcher.
2. Wait Time: The amount of time the user request sits in the queue. Generally it should not be more
than 50 M.Sec or 10% of the response time. If the time exceeds, consider the following.
1. The work process are not sufficient to handle the user requests. (1:5)
2. There are sufficient processes but the existing process are held with expensive request.
Login/disable_multi_gui_login.
3. Roll in Time: The work process copies the Roll in User context into WP task handler. The time taken
by the work process to copy the context (Roll In) is referred as Roll in time. Generally it should not be
more than 50 M.Sec. If it is more than this consider the following.
1. The user context is heavy to Roll in (User might having more authorizations, parameters)
103
2. Minimize the authorizations.
4. Roll Out Time: The time taken by the work process to copy the information from its local memory
to Roll Area/ Roll File/ User context/ Roll buffer and it should not be more than 50 M. Sec.
5. Roll Wait Time: During the processing when a dialogue process communicates with RFC's and
waiting for the response at this time the user context is copied/ rolled back to
Note: Roll wait time is not considered as a part of response time. If the roll wait time increases
consider there is a bottle next on the RFC communication.
6. Processing Time: The time taken by the work process to process the user request using
interpreters. The processing time should not be more than 200 M.Sec. If the processing time is more
we can consider either ABAP program is expensive, screen is expensive or SQL statements are
expensive.
7. CPU Time: When the request are processed using interpreters an amount of CPU is utilized to
process the request using CPU resources is referred as CPU time.
As CPU time is included in processing time it is not calculated in the response time.
CPU time should not be more than (40% of the Dialogue response time - Wait time). If CPU time is
more consider tuning ABAP Programs Refer to ABAP development team (Also Refer SE30 ABAP Run
time Analysis, ST05 Performance Analysis)
8. LG Time: Load and Generation Time: Time required to load the objects such as source code, GUI
info, screen info from the database and generate these objects.
(Refer LC10 : Live Cache). It should not be more than 200 M.Sec.
Run SGEN tcode after patch application, upgrade, new installation or when there is a mass change in
the programs.
9. Enqueue Time: The time taken by the process to communicate with enqueue for obtaining the lock
while updating a record is referred as Enqueue time. Enqueue time should be 5 M.Sec. on a Central
instance and 100 M.Sec on a Dialogue instance. If it exceeds more than this time we can consider that
the enqueues are not sufficient or Enqueue table overflow. or WP waiting for a lock.
10. RFC or CPIC Time: The time taken by the process to communicate with external interfaces is
referred as RFC time. It should be as minimal as possible. (Communication between any BW/ CRM/
SCM system). There wont be any threshold value as it depends on External system.
104
11. Database Time: The time taken by the process to reach the database and process the request.
Generally it should not be more than 40% of (Response time - Wait time). It is similar to the CPU time.
IF DB Time is more consider the following.
12. Dialogue Response time: The time taken by the Dialogue process to process the request which
includes [Wait time ........ To ......... Roll Out Time]
10-Aug-09
ST03 It is used to calculate the work load analysis. Select Expert Mode to identify the expensive
programs, transactions, reports and users.
While calculating the average consider the number of dialogue steps of the transaction user. If
the response time is more and dialogue steps of fewer 1 or 2 then the average response time could
not be worked out. The response time should be worked out only when there are atleast 10,000
dialogue steps.
MEMORY
Physical Memory: The memory that is available or the memory that is configured on the instance
using the parameter PHYS_MEMSIZE.
Virtual Memory: The physical memory and SWAP memory/ Pagging Memory on the disk
The physical memory will not be sufficient to provide the users for temporary work area/ Calculations/
so a part of the disk which is configured for SWAP is used.
105
On UNIX during installation assign atleast 20GB of SWAP. On windows assign atleast 3*RAM size/
20 GB which ever is higher.
Shared Memory: The memory that is used by all the applications (OS, DB, R/3)
Extended Memory: The memory that is used by SAP work processes is referred as Extended Memory.
Local Memory: The memory that is assigned to work process is referred as Local Memory
Roll Memory/ Roll Buffer: The memory that is used by work process to store the user context
information is referred as Roll memory.
Private/ Heap Memory: The memory that is used by work process exclusively by restricting itself.
MEMORY ALLOCATION
Abap/heaplimit=4GB
Abap/heap_area_dia
Memory : RAM is the first Memory. Out of this we don't want to allow SAP to utilize the whole
memory.
Virtual Memory: Pagefile.sys
11-Aug-09
106
CASE STUDY
We have configured 20 WP in the Instance and we know pretty well that each user request consumes
a minimum of 25MB of Memory
When the process uses Heap Memory it is used in Heap/ Private mode. The processes
which are in PRIV Mode cannot be timed out by
Rdisp/max_wprun_time
Rdisp/max_priv_time
So configure so that the process is timed out after this time (600 Seconds/ 10 Minutes) when the work
process goes into PRIV mode it will not listen to rdisp/max_wprun_time=600sec. It will be released
only after the task completion or Memory is exhausted(Abap/heap_area_dia)/ timed out by
rdisp/max_priv_time. This situation is referred as Hour Glass Mode or WP Congestion. At this situation
we can use DPMON or SM04 to terminate the user session. If not kill the process at OS level based
on PID.
Q. The user complains that he could not login to the system - Hour Glass Mode?
A. 1. WP into PRIV Mode
2. ARCHIVE STUCK (The user could not update any record and results in hour glass mode)
BUFFERS ST02
The frequently used content and less frequently modified is eligible for buffering. Company
Name, GUI, screens, calendars, table definitions, programs etc are eligible for buffering.
Data such as Exchange Rates, Transactional Data(PO, Sales Order, Invoice, Billing) are not
eligible for buffering.
Buffering is specific to instance. Each buffered element is stored in the memory of the instance
in terms of Directories and Space.
Eg. Programs can be stored up to 150000 KB, 150 MB in 37,500 directories. If the directories/ size is
full then Buffer Swaps occurs in ST02.
When SWAP occurs the content needs to be fetched again from Database which increases the
response time.
12-Aug-09
108
Next >
Search Term : SAP Router
Or Go with Message
Select the system & select the component
Dear SAP,
We have installed solution manager and 3 ERP systems in the landscape. Before we start
implementation we would like to establish connecting with SAP using SAP Router.
SID : JOS
INSTANCE NO : 00
{ Open the connectivity, How many hours it needs to be opened; Provide Userid and password/ Client
}
Note: from Market Place > My Profile > Maintain Single Sign on Certificate > Specify Password.
109
From Market place > Check the email.
SAP : 213.210.213.197
JOLSOLMAN
194.39.131.34
----------------
Earlier from the Back End system say for eg: SOLMAN system
SAP Router is a software program which is used to restrict to access the customer systems using the
table SAPROUTTAB.
SAPROUTTAB is a text file with out any extension in the router directory with prefix P, D and S (Permit,
Deny and Secure sometimes)
Note
SAPRouter is an executable in the kernel directory (usr\sap\SID\sys\exe\uc\NTi386).
Nipping is an executable to ping to the router. This two executables needs to be copied to the router
directory. However we can also download from market place.
On Windows> Check whether the SAPRouter service is running or not to make sure whether the
SAPRouter is already configured or not.
3. Login as <SID>ADM
7. From market place click on Download Area > SAP Cryptographic Software
.sar file.
It depends on OS
We can download either CAR or SAR file
111
Variable : SECUDIR
Path: E:\usr\sap\saprouter
Variable :SNC_LIB
Path: E:\sur\sap\saprouter\nt-X86_64\sapcrypto.dll
Saprouter> CD nt-X86_64
Saprouter\nt-X86_64>
sapgenpse get_pse -v -r certreq -p local.pse "Paste the distinguished name"
Prompts for PIN : any password
Twice
Sapgenpse - SAP Generic Personal Security Encryption
--------------------------------------------
To Uninstall
Ntscmgr install saprouter -b E:\.........
SAPSR3 - 14
SAPSR2 - 9
113
SAPSR1 - 6
------------------------------------------
---------------------------------------
Goto Market Place
Download service connection
Maintain Data > System Data
SOLMAN
Production System
Goto DB Server
Hostname > SOLMAN
IP Address : 124.12.124.19
OS : NT/ INtel
Version : Win2003
DB Release : 9.2.0.8.0
13-Aug-09
SAP ROUTER
Theory
SAP Router is an executable which is used to restrict the access to the customer systems over the
network. It works like a firewall/ proxy to permit and deny the access to the SAP systems.
SAP Router
1. Create message to SAP along with your SAP Router [Hostname], IP Address and Customer Number
(SAP Router need not to be installed on Solution Manager /DEV/ QAS/ PRD. It can be installed on any
desktop, but it is advised to install on SOLMAN system to ensure that it is monitored periodically.
Cust Number : When we buy SAP we will be provided with the customer number.
4. Download the Cryptography files from Market place related to OS and bit version (Download *.SAR
files)
7. Generate the certificate using distinguished "DN" name with executable SAPGENPSE.
8. Copy and Paste certificate from Begin to End the market place url
/Saprouter-SNCADD
115
SAPOSS, SAP-OSS, SAPSNOTE are created on communicating with the Market Place.
---------------------------------------------
ST02 continuation.
Buffer swaps occurs when there are no sufficient directories or space. When more swaps occur they
are displayed on ST02 in swaps column.
Analysis:
Identify the buffer areas whose swaps/ Database access are more.
Do no take any decisions based on the readings on a specific day. Analysis has to be carried out if
there are atleast 10,000 requests.
Key areas that effect the performance are program buffers, table buffers and Table and Field
definitions. Change the program buffer using ABAP/ buffer_size to a maximum of 600 MB on 32 bit
Machines.
Remaining parameters based on SAP recommendation from RZ11.
TABLE Buffering
SAP stores the content in tables (Every data except start and stop logs is stored in DATABASE, no
prog/ no data is available in the file system)
1. FULL Buffering
2. Generic Buffering
3. Single Record Buffering
4. No Buffering
1. Full Buffering: The tables which are frequently used and rarely modified are eligible for buffering.
(Also which are small in size)
Eg: T000 have all the clients and required to create a client copy. (This is fully buffered)
2. Generic Buffering: Tables which are relatively large, frequently used, rarely modified using a set of
keys (Fields)
3. Single Record Buffering: The tables which are large in size, frequently used and rarely modified
are buffered using a primary key.
4. No Buffering: The tables which are large frequently used, and frequently modified are not eligible
for buffering.. VBAK (SALES), EKKO (PURCHASE)
BUFFER SYNCHRONIZATION
When more than one application server is configured then buffers between different instances
may not be synchronized. In order to synchronize buffers set the parameter
117
Rdisp/ buffermode = Send on; exec auto.
Rdisp/ buffertime = 60 Sec.
Mechanism
1. User1 request to APP1 for update Sales order to Rs. 500 @ 10:00:01
2. User2 request to APP2 for update the same sales order to Rs.550 @ 10:00:20
3. User3 request APP1 for display @ 10:00:40
WP will ask DDLOG table to check for recent update within 60 Sec. (DDLOG is a buffer synchronization
table).
If there is any change then it will fetch from DB and swap out the buffer. IF there are no updates
fetches the same from APP1 Buffer. If the content is requested after 60 Seconds, by that time it will be
synchronized between APP1 and APP2.
DDLOG is a synchronization between instances and maintain TIMESTAMP
- SQL server performance analysis. It is used to display the database buffer hit ratio. It is
recommended that it should not be less than 94% i.e. for every hundred reads only 6 should goes to
the database.
- Database hit ratio comes down below 94% then consider the following.
118
Logical Reads is the sum of [Physical reads and Buffer Reads] (Buffer Gets/ Reads)
FROM ST04
ST06 OSMONITOR
It Fetches the data using service SAPOSCOL and it displays CPU Utilization, Memory Utilization and
disk response time.
The CPU idle time should not be less than 30% [For Portal up to 80% to 85%]
If it is below 30% we can consider the following.
1. The ABAP programs are expensive with multiple conditions and endless loops.
2. The CPU is not sufficient to handle the load because the hardware is not procured as per sizing.
Probably the hardware is procured as per sizing but the number of users grown dynamically (300-
600). In this scenario we advice to deploy additional instances.
It also displays the memory installed on the machine, Memory available(Free) along with the
SWAP space. Ensure that physical memory free is available to handle the user requests. If not
memory bottleneck.
Note: OSCOL brings the operating system information into ST06. If OSCOL is not started ST06 will be
blank.
119
We can check TOP CPU utilization for the current in the last 24 Hrs.
LAN CHECK BY PING is used to ping to all the systems in the Network/ Landscape.
If a user complaints that he could not connect to the server (Ping to the desktop)
120
ST11: It is used to display the work directory. It displays the log files related to work process.
1. RFC Trace
2. Buffer Trace Available in ST01 and ST05
3. Enqueue Trace
4. SQL Trace
1. When the RFC/ CPIC time are going beyond threshold value then switch on RFC Trace.
2. When more buffer swaps occurs in the table buffering ST02. Switch on Buffer Trace.
122
3. Enqueue Trace: When the enque or enque wait time is increasing by 5 M.Sec on CI(Central
Instance) 100 M.Sec on Dialogue instance (Consider switching enqueue trace)
4. When there are too many expensive SQL Statements which are increasing the database response
time in ST04 then switch on SQL Trace. (Identify those statements in ST04)
Eg. Select * from can be fine tuned by using select single * from with appropriate where conditions.
5. Authorization Check: Whenever user encounters missing authorizations and could not be traced in
SU53 can be traced out by switching the trace on User.
6. Kernel Trace: Used to identify the consistency of Kernel. It records all the calls that are made to
kernel when the trace is ON.
Note: Do not switch on the traces when they are not required. It will populate enormous log files and
occupies the complete disk place and system stands still. As a practice switch on the trace and inform
the user to run the transaction. Switch Off the trace.
RC=0 (Return Code)
Note: Tuning is not testing we need enormous analysis and data to justify the conclusion.
17-Aug-09
IMPLEMENTATION OF SAP
Pre-Requisites
1.1. Customer wanted to deploy an application that suites to his requirements by replacing the
existing software due to the following reasons.
1. The existing Hardware is old and the response times are high.
2. The software is out of maintenance with no updates, or with no company (Company
Bankrupt/ Merger etc.)
3. The customer could not be competitive in the market due to the legacy methods deployed
B1 - C++
No ABAP, BASIS, NW
Customer enquires in the market and calls for the Auditors to identify the software, hardware and the
Implementer.
Delloite, Bearing Point, KPBG, PWC (Price Water Coupons) are the auditors to identify the
requirements in the company. They define the pain points of every business user owner and
document them.
Example:
- The software should be installed on all the operating systems and databases.
- The GUI should be compatible, user friendly, ergonomically designed, colors, fonts, languages,
password change.
- The software should be unicoded language to support all the languages.
- The software should support (Online, Offline, incremental, partial, table level backup)
- The software/ Hardware should support mirroring, RAID, clustering, Disaster Recovery, Restore etc.
- The software should support Mobile devices, Email, Fax, SMS, Pager, PDA etc.
Issue --- Description ---- Possible/ Not Possible/ Customizable/ If customizable Amount of effort.
124
These requirements list will be floated as RFQ feasibility of software.
- These list will be submitted to Oracle Apps, NAVISION, Hyperion, Peoplesoft, Seibel (CRM)
implementing partners.
SAND
DEV/ CUST/ GOLDEN
UNIT TESTING
INTEGRATION
PAYROLL/ TDMS 8
TRAINING
PRE PROD
PROD
- Customer decides software with the help of feasibility reports and assistance from auditors.
- Support partners like IBM, TCS, WIPRO, MAHINDRA submits the proposal. They can also raise
questions in the form of RFI (Request for Information)
18-Aug-09
------------------
C:\pf\sapinst_instdir\ERP\system\ORA\central\AS
Ensure that there should not be any .bck files while reinstalling the SAP
---------------
Note:
External Security
Routing
Switching
Proxy
Firewall
Internal Security
126
Authenticating Authorized users is Internal Security.
Project Costing:
3. Project can be a fixed bid let us say 2,00,000 (i.e. @ Million Dollars for completion all inclusive
(Fares, accommodation, staff, Replacement, Holidays, vacations, sick etc).
Payment will be released in Parts ---- Project Start 10%, Blue print - 20% Realization - 20%, Final
Preparation - 20%, Go-Live - 30%.
4. Let us say the Project Manager is SAP. We need to provide manpower to SAP to implement @
customer site. Eg. SAP Project bidder is SAP for 28 Crores in Singareni Collories ... They out sourced to
Seal Infotech for training and implementation.
1. Fixed Bid
2. Time and Material (T&M)
3. Resource Based
4. Activity Based (Try to include Wait time)
The scope of work needs to be defined properly before sign-on. If SOW is not defined properly, it is
vendor responsibility.
It is an exercise carried out by Basis consultant with the help of the customer business process
owners, Project Manager and Hardware vendors (IBM, HP, SUN, DELL). It is used to determine the
CPU's, Storage (Hard disks) and Memory.
Note: Legacy database size (get the details from customer what amount of data they are planning to
migrate into SAP, Example Customer Database size is 400GB but they want to migrate 250GB into SAP
(Customer, Vendor, Supplier, Material, Address, FI Transactions)
High Availability options (Time of Availability)
These are the general details that are required for sizing.
Note:
----------------------------
IBM - DB2 [AIX O/s - DB2 Database]; I Series V5R4 - DB2]
SAP - MAXDB
Oracle
SQL Server - Microsoft
P Series, X Series (I Series V5R4) is the O/s
21-Aug-09
Sizing is performed by quick sizer which is proprietary by quick sizer which is proprietary tool of SAP.
Sizing is based on the following.
1. High Availability
2. Type of Users
3. Modules used
1. High Availability
1. RAID1 - Mirroring (1:1) on disk goes down other should take over.
2. RAID5 - (5 Disks---- Util -4; 1 Spare/ Parity)
129
8. If the complete system collapses due to hardware failure use clustering -- Two Parallel systems
(Used for failover or Load balancing)
Unless unlocked by IBM we cannot make use of the additional Hard Disks
Module Selection: Select the modules that are going to be implemented like
Logistics, Financials, Product life cycle Management (Currently HR is not going to be implemented
but, there is a plan to implement in future, If it before three years consider HR in sizing if not.
130
1. User - 480 Dialogue Steps with the system
- 40 HRS * 60 Mins
22-Aug-09
Service Desk >
Component BC-MID-RFC
Test
Low
Test -- TKT No: 008000000001
The Strategy is to migrate/ upgrade the hardware for every three years. The sizing is based on
1. High Availability
131
2. Modules and
3. No of users
The sizing is also called as T-Shirt sizing which determines your servers as (S, XS, M, L, XL, XXL) Sizing
output determines the memory, storage and CPU in terms of Saps'.
SAPS are calculated based on Sales module. SAP assumes that a sales order/ Purchase order
consumes around 8-12 Dialogue steps. For every 2000 sales documents that are generated per hour
requires 100 SAPS.
CPU cannot be arrived directly because the process speed depends upon the hardware vendor.
(The hardware vendor determines the CPU Size based on SAPS example an ISeries machine single
CPU generates 800 SAPS.
1. OS
2. Database
3. Interfaces (Like Fax, Email, SMS, Pager etc.)
4. Printers
5. Third party communication (Batch processing etc)
So we can consider adding 30-50% to the sizing results.
- Hardware vendors take 3 weeks to 4 weeks to deliver based on the availability of the hardware.
HP ships from Singapore, Philippines and Malaysia
IBM ships from US
Communicate with SAP vendor (Channel Partners) and purchase the license.
License is a single user based. i.e. If we buy one license we can access ... ERP, SRM, BI, PI, EP, Solution
Manager, MI etc.)
If we buy MYSAP business suite then all comes under one license.
* There is no lock for licensed users in the system. We can buy 100 Users and used for 10,000 Users.
* Every year we need to run USMM and send the report to SAP.
For 40,000 we should have atleast 150-200 Users for 10+1 cost 18 Lakhs.
---------------------------
Note:
Buffer
Bin - Points to the target system
SAP_BC_ADMIn
S_Transports
CTS_Admin
Disp+exe ( PING, Etc Entry, Any Kernel upgrade has been done (DEV_DISP.log)
---------------------------
27-Aug-09
133
BASIS
SAP determined to bring all the components on to a common platform and introduced SAP Web
Application Server (WAS)
XI - 3.0
EP - 6.0
134
ERP - ECC6.0
BW - BI7.0
EP - EP7.0
XI - PI7.0
SRM - 5.0
CRM - 5.0
Install ABAP(CI, DBI), JAVA add on. Install Central System Installation (Select Usage type during
Installation)
Run directory is used to host executables of kernel upto 640 where as OS version (NTI386, AMD64,
IA64) with UC/ NUC is available in version 700.
OLD: The database table spaces are 27 which ends with D(Data) and I(Index)..[SAPR3] owner.
From 620
The database contains only 6 tablespaces(Physical Location) in 640 owner is SAP<SID>
PSAP<SID>
PSAP<SID>USR
PSAP<SID>REL
SYSTEM
PSAPROLL(PSAPUNDO)
PSAPTEMP
The database contains only 8 tablespaces in 700. Owner is SAPSR3 for ABAP engine and SAPSR3DB is
for JAVA Engine.
GUI Versions
46C
46D
620
640
700
710
Database Users (DDIC and SAP* are SAP Users resides in USR02 Table)
19,xxx 65xxx
Components: BASIS BASIS+ERP
31-Aug-09
DATABASE
Database: Used to store the data in the organized format and it has to follow RDBMS rules (Relational
Database Management System)
- Data is stored in terms of tables (Tables contain rows and columns). Columns are headers and rows
are the data.
Eg: As in windows we can create as many folders and subfolders with the same name and the search
criteria depends on the search string.
C:\shawn\shawn\shawn.......
- Database has its own structure to manage the data using the database specific binaries and libraries.
Oracle/bin; mssql/bin; db2/bin;
Oracle/lib; mssql/lib; db2/lib;
- Database provides tools for backup management, reorganization, restore and recovery
- Databases follow RDBMS rules to achieve consistency, reliability and transaction LUW.
It consists of one or more transactions that are bundled together which can be committed as a group
or rollback without any data loss.
137
RFQ(Approved) - Sales Order
Purchase Req - FI Dept (Approval) - Purchase Order - Tenders (Contractors)
(Eg: Purchase Order, Sales Order, Invoice, GR(Goods Receipt), GI (Goods Issued) AP (Account
Payables), AR (Account Receivables)
NORMALIZATION
Process of splitting up the larger tables into smaller tables using primary keys and secondary keys...
ERP(ECC6), SRM.
DENORMALIZATION
Process of grouping smaller tables into larger tables for having data comprehensively available for
analysis and reporting BIW.
Scenario
User requests for weekly status report.
UPDATE COMMAND
Log buffers are a small area around 1Mb - 4 Mb. As the log buffer is small the content is moved in to
Redo logs periodically.
Redo logs are duplexed (Mirror logs and Orig Logs) and ensure that the data is updated in the
database.
12. The committed data is updated into database
13. The locks are released and rollback gets invalidated.
Note: Committed data can be updated or Redo.
14. User gets the response that the record is updated.
ORACLE
Oracle is a database that is used by 2/3rd of SAP Customers. In order to support SAP
Customers it is mandatory to know the database management.
Oracle is a proven, well spoken among customers, strong, reliable, consistent, robust
database to handle any amount of data in Terra bytes.
Microsoft SQL Server from Microsoft, DB2 from IBM and SAPDB(MAXDB) from SAP
shares the remaining 1/3rd of SAP Customers.
Versions
Oracle has versions of database
SAP License is costlier on Oracle than any other combinations.
DATABASE ARCHITECHTURE
OPS$ Mechanism
It is a mechanism which is used by operating system users to connect to the database without
any password.
All the work processes uses OPS$<SID>ADM to connect to the database without any
password.
OPS$<SID>ADM is the user who owns the table SAPUSER and contains the SCHEMA OWNER
SAPSR3 user and password.
SQL>
Select table_name from dba_tables where owner = 'OPS$WILLSYS99\NWDADM';
SYSTEM GLOBAL AREA is the sum of Shared pool, DB buffers and log buffers
SHARED POOL
DB BUFFER : Used to store the content that is accessed from the database. It is used to reduce the
hits on the database there by reducing the load on the database. Its quality is measured by database
buffer hit ratio. In general for an optimized database the ratio should be not less than 94%.
DB Buffer is used to store the data until its size is full (or) the content gets invalidated by a change or
least recently used. It is defined by a parameter db_block_buffers.
Its size is defined by multiplying by 8kb because each block size is 8 kb.
LOG BUFFER: It is used to perform the data manipulations by database work process. Every request
that needs modification/ update / delete has to be performed only in this area. It is defined by the
parameter log_buffer generally its size varies between 1MB to 4MB. It should not be too big or too
small.
SYSTEM/ SHARED GLOBAL AREA: It is a memory area which resides purely on memory and it is lost
when the system is stopped.
SGA is lost the complete cache information is lost. It takes time to build SGA when system is started
that is why the system is slow after a restart.
ORACLE PROCESSES
1. Shadow Process
143
2. Background Process/ Server Process
SHADOW PROCESS
These are used to handle the user requests. They perform the task assigned by an R/3
WP. They called as shadow processes because they perform the task non-interactively. These are also
called as User processes (In Oracle Terms)
The process are established at the rate of 1:1 during the startup of SAP system.
These are non-interactive to R/3 Processes. These are initiated by system based
on requirement.
LOG WRITER
Mechanism
a) R/3 work process submits the request for an update.
b) Shadow process handles the update by locking in the database
c) It takes a backup of PSAPROLL/ PSAPUNDO to roll back to the original state if
the update is cancelled or abrupt.
d) The record is fetched into DB Buffer for allowing selection.
e) A copy of the record is taken to log buffer for modification
f) the data/ record is modified in log buffer. This cannot be kept for long in the
log buffer as the log buffer size is small.
LOGWRITE (LGWR) is used to write the committed data into Redo log files (Origlog A, Origlog B,
Mirrorlog A, B) from log buffer.
This is the first place where a record is written to the disk to ensure that committed changes are not
lost. To ensure the disk consistency log writer writes into Origredolog and Mirrorredolog files (Both
resides on two different physical disks).
When the data is committed System Change Number is generated to ensure the faster commit
mechanism. Log writer writes the commit into Redo log files but when the size of Redo log file is full
size 50MB. It will perform Log Switch.
LOG SWITCH
02-Sep-09
(Note: If the buffer size is more no updates will happen. The DB WP waits till the buffer total memory
gets utilized and then updates the DB)
It is a memory area which resides purely on memory and it is lost when the system is stopped.
i.e. SGA is lost the complete cache information is lost. It takes time to build SGA when system is
started that is why the system is slow after a restart.
ORACLE PROCESSESS
1. Shadow Processes
2. Background/ Server Process
Shadow Processes
These are used to handle the user requests. They perform the task assigned by an R/3 WP.
They are called as Shadow Processes because they perform the task non-interactively. These are called
as User Processes (In Oracle Terms).
These are non-interactive to R/3 Processes. These are initiated by system based on the
requirement.
1. LOG WRITER
145
Mechanism
This cannot be kept for long in the log buffer as the log buffer size is small.
* Log Writer is used to write the committed data into Redolog files (OriglogA, OriglogB, MirrorlogA,
B) from log buffer.
This is the first place where a record is written to the disk to ensure that committed changes are not
lost. To ensure the disk consistency log writer writes into Origredolog and Mirrorredolog files (Both
resides on two different physical disks).
When the data is committed SYS Change number is generated to ensure the faster commit
mechanism log writer (LGWR) writes the commits in to Redolog files but when the Redolog file is full)
size 50MB. It will perform log switch.
LOG SWITCH
03-Sep-09
146
The Content of OriglogA, OriglogB, MirrorlogA, MirrorlogB ... (Redolog files) gets filled and need
to move to other location. If it is not moved.
1. Redolog files gets filled and does not have space to write the content from log buffer.
When log buffer cannot write the content then log buffer gets filled and subsequently the update
mechanism gets halted. so, the redo log files needs to write to an alternative location immediately once
they get filled.
ARCH Process
During the log switch OriglogA gets filled for writing and OriglogB is opened for writing. The contents
of OriglogA will be written to ORAARCH directory (Provided archieve_log_mode is set to true). The
contents are written by ARCH from RedologA to ORAARCH and RedologA is ready to be written by
LOGWR. Similarly RedologB.
The content that needs to be updated is fetched into DB Buffer for selection. A copy is made to LOG
Buffer for updation. Once the content is updated in Log Buffer it marks the content in Database Buffer
as Dirty buffers and not eligible for selection.
Note: Every select statement hits the database and brings the data to DB Buffers. All the updates will
be done from Logbuffers.
download.oracle.com/docs/cd/310501_01/server.920/a96524/C09procs.htm#21919
It updates the headers of all datafiles to record the details of the checkpoint.
It triggers DBWR/ LGWR
Used to monitor the process recovery when a user process (Shadow process) fails. PMON is
responsible for cleaning up the database buffer cache and freeing resources that the user process is
using and release the locks.
PMON periodically checks the status of dispatcher and server processes and restarts any that have
stopped.
1. Datafiles : These files are with extension (.dbf). These are used to store the data in the Oracle
specific RDBMS format.
2. Control Files: These are used to display the structure of the database into Six different locations. It
is the most important file (Cntrl<SID>.DBF) The location is specified by a parameter control_file. Do
not modify the control file manually, the system modifies by itself when ever there are any changes.
3. Initialization Files:
init<sid>.ora is used to provide the startup parameters for Oracle.
148
init<sid>.sap us used to provide the database backup/ restore (brbackup, brarchive, brconnect,
brrestore) control parameters.
4. Network/ Admin
Listener.ora - Provide Port and the Host Name.
Tnsnames.ora - Provide port and the host name
Sqlnet.ora - .....
04-Sep-09
Special Parameterization files (SPFILE)
All the changes that are made requires a reboot of Oracle database. In order to change certain
parameters SPFILE is maintained.
Oracle Startup
Commands
Startup open
Startup mount
Startup no mount.
1. Startup Nomount : This phase is used to create control files and database. No datafiles are
mounted.
2. Startup Mount: We can start a DB and mount a database without opening it, allowing us to
perform specific maintenance operation.
3. Startup Restrict:
149
4. Startup Open: When DB is started using startup cmd. It reads the init parameters in the following
sequence.
1) SPFILE<SID>.ORA
2) SPFILE.ORA
3) INIT<SID>.ORA
4) INIT.ORA
Oracle Shutdown
1. Shutdown Immediate
05-Sep-09
Shutdown Modes
1. Shutdown Abort
The database is forcibly shuts down and may not be consistent and requires recovery during startup.
SMON ensures that the database is consistent (REDO/ UNDO)
All the users who are working on the system gets terminated abruptly and the intermediate data is
lost. (Which is committed)
Not Consistent.
2. Shutdown Immediate
The database is shutdown immediately but all the committed transaction are updated in the database
and opened transactions are rolled back. No new connections are allowed.
Consistent.
3. Shutdown Transactional.
The database does not allow any new connections, all the committed data is updated
150
In the database and opened transactions are only allowed to complete, no new transactions are
allowed.
Consistent
4. Shutdown Normal
It allows the users to complete all the transactions and shut down the database. No new connections
are allowed but time consuming to stop the database.
STORAGE
The database uses file system but organized in the RDBMS concept. The data is stored in terms of
Database block size in terms of Datablocks. Each block size is 8KB(8192 Bytes)
Data files are physical files on the file system where data is stored in Datablocks.
EXTENTS
These are used to allocate space to a table/ segment to control the growth
1. Initial Extents
2. Minimum Extents
3. Next Extents
4. Max Extents
1. PSAP<SCHEMAID> PSAPDEV
2. PSAP<SID>RELEASE PSAPDEV640/ 700
3. PSAP<SID>USR PSAPDEVUSR
4. PSAPTEMP Temporary Table Space
5. PSAPROLL/ PSAPUNDO UNDO Table Space
6. SYSAUX
Tablespace is pointed to physical datafiles. Each Tablespace can have one or more datafiles to store
the table data/ Index data.
Eg: Users are creating purchase orders extensively into the tables EKPO, EKKO and other child tables.
These tables are assigned to a tablespace PSAP<SID>. This tablespace is pointing to two datafiles of
size 4GB each.
User encountered an error ORA-1653/ ORA-1654 tablespace over flown and the user could not
update/ create any more PO's
The user could not update the data because the datafiles are filled (or) there is no enough space to
allocate for extents.
Resolution
152
Use BRTOOLS (Backup Recovery Tool) to resize the datafile (or) add a datafile. (Alternatively we can
add using SQL Command)
SQL>
Alter tablespace (Tablespace Name/ PSAP<SID>) add datafile location and size;
EXTENT MANAGEMENT
When a table or Index is created they are assigned with Min Extent, Init, Next, Max along with the
Percentage of Increase. CAP is Max.
When ever a table is growing it increase it extents i.e. it uses next extents. The free space in the
existing extents is not used there by Fragmentation. It requires database Reorganization.
Users encounters an error ORA-1631 and ORA-1632 Max Extents Reached, but there is a tablespace.
Default table spaces from 10g which manage the extents locally instead of dictionary management.. It
collase the space that is left in all the extents before allocating an extent. It reduces the
fragmentation there by reorganization is not required. SAP recommends to migrate all the dictionary
managed tablespaces to locally managed before 10g upgrade (Oracle).
06-Sep-09
ops$willsys99\saservicesr3
ops$willsys99\saservice<SID>
ops$willsys99\<sid>adm
sys - The complete or absolute owner of oracle database server to perform the activities.
DATABASE MONITORING
As a part of the routine SAP basis checks the following database tasks can also included.
Note: Oracle writes all startup logs into alrt<SID>.log which resides in SAPTRACE directory. It is the
only log which can gives us the complete history of database activities.
1. Monitor the size of the database to have a detailed capacity planning. Login to SAP system and log
the database growth on daily basis.
1 2 3 4 5 6 7 8 9 10
200 210 220 230 230 230 250 280 300 350
Conclusion
DB02 is used to monitor the disk space, critical objects based on Table spaces.
Tables and Indexes Monitor
Identify the tablespaces which are grown more than 90% and add datafiles.
Enter choice - 1 (For which tablespace we need to increase the size of datafile)
PSAPSR3700 - Press Enter
E:\oracle\SID\sapdata3\sr3700_16
155
In this path 16 datafiles are there if we increase the tablespace size one more data file is created
called sr3700_17
- Add the datafile or resize datafile before its gets an error message "Tablespace overflow"
MISSING INDEXES
Identify the missing indexes in DB02 (which will reduce the performance without proper indexes)
- Objects which are missing are displayed in Red, select them and create in the database.
Logical Reads : The number of reads that are made to Database buffer.
Physical Reads: The number of reads that are made to Physical Database.
Physical reads are increasing conclude that the database hits are more.
If the ratio is reduced we can conclude that DB_BLOCK_BUFFERS size is not sufficient or there are
frequent updates on the system.
DB13
We need to check
SCHEDULE DB BACKUP
07-Sep-09
BRTOOLS
These tools are used to manage or monitor the oracle database which are specifically provided by
SAP.
1. BRCONNECT
Check conditions are described in transaction DB17 which in turn stores the details in DBMSGORA
brconnect -f stats
Used to run the database statistics. It identifies the tables whose statistics are outdated and updates
them. We need to run the DB optimizer once a week. So that all the tables and Indexes where there
are stored will be known to DB Optimizer. It is updated periodically (Weekly). Optimizer is used to
collect the statistics for the tables whose statistics are outdated.
brconnect -f cleanup
It is used to clean the old log files from saptrace and sapcheck directory
brconnect -f next
It is used to adopt the next extents (i.e. Next extents can be increased automatically)
These jobs can be scheduled using DBCALENDER (DB13). How ever when these jobs are scheduled
BRCONNECT runs in the background.
BR-BACKUP
BR Backup is used to take backup of the database (Datafiles). When ever a backup is triggered BR
Backup is initialized.
1. Offline Backup
2. Online Backup
3. Incremental Backup
4. Partial Backup
Whole Offline Backup: The backup taken fully and a catalog is opened to start the incremental
backup.
158
Eg: A database is of 2000 GB Which is not possible to take a daily full offline backup with a backup
speed of 150GB/ Hour.
2. Online Backup
The DB is up and running with out effecting the user transactions. It is consistent and reliable with
redo logs that are generating during backup.
Whole Online Backup: The backup is taken fully and a catalog is opened to start the online
incremental backup.
Full Online Backup: It is complete database backup with out any catalogs.
3. Incremental Backup
It is initiated from level0 backup and used when the database size is too big. It can be
online or offline.
4. Partial Backup
Backup_mode = all
Backup_type = offline
Backup_dev_type = Tape or Disk
Backup_root_dir = H:\oracle\SID\sapbackup
BR ARCHIVE (initSID.sap)
159
It is used to backup the offline redolog file to tape or disk i.e. from ORAARCH directory to tape or
disk.
Reads content from Log Buffer. Log writer writes to OrigLogA and OrigLog B, Mirror Log A, Mirror Log B.
When OrigLog A is full it is moved to OrigLog B When OraArch is full it is backed up to a tape or disk.
- While copying Oracle provides various means of log save because we don't want the corruption of
logs.
160
08-Sep-09
BRTOOLS
- Tablespace management (Create drop alter. mostly create and drop are not used)
- Reorganisation (Create, Rebuild, Indexes Export and Import tables)
- Database standard house keeping jobs (DBStatistics, cleanup logs, dbcheck, adapt next extents)
- Display profiles, change schema password etc.
2. Heterogeneous Copy
3. DB Refresh
It is the process of refreshing the data of one system by another system data.
(OS, DB, R3) remains the same but only database is refreshed.
1. To setup a new system in the landscape (Only DEV and PRD exists, now we need to deploy QAS as
a copy of PRD)
3. To move out from one OS to another or One DB to another DB which is called as OS/ DB Migration
which needs to be carried under the guidance of Certified consultant.
4. While applying patches, Kernel Upgrade to test the objects with Production data.
1. Source System
2. Use Installation Master DVD
- Use Additional Tasks
- System Copy
- Source System
- select database instance export
- specify typical
- specify Profile directory e:\usr\sap\sid\sys\profile
- specify the password if <sid>adm
- Specify the export location for Import.
Review the inputs and continue the import.
DATABASE REFRESH
162
Let us say there are three systems DEV, QAS and PRD existing in the landscape. The objects which
are developed in DEV needs to be transported to QAS and PRD the objects behave differently in DEV,
QAS and PRD.
Eg. A Small report which fetches monthly sales executes 1 Sec in DEV and in QAS where as in PRD it is
consuming 30Min. PRD DB Size 1TB 2TB. The report is good in DEV and QAS but bad in PRD that
means quality checks are failed.
So we need to copy the PRD (DATA files) system to QAS system from time to time to get proper
quality done.
Similarly we need to apply patches, Kernel , add-ons in the landscape. We don't want any issues that
crops up on the production system. So we will take a copy in QAS and apply before PRD.
Process
1. PRE STEPS
2. DB REFRESH
3. POST STEPS
Pre steps
Pre Steps on the Target system. It is required to keep the dependencies of the target system to
restore them later i.e. after refresh.
Eg. After Refresh the target system QAS behaves like production System. Se we need to delete the
source dependencies and restore the target dependencies, Users, RFC Connections, Batch Jobs,
License, Printers, Roles etc.
1. Create the transport of copies by using SE01 and specify the following objects/ tables
USR01, USR02, RFCDES and TBDLS
And then we need to release the Transport of Copies.
4. And then
We need to delete all the datafiles related to QAS system. data1, data2 etc. First we need to stop the
oracle services the structure should remain same.
5. First Activity
After taking the backup of PRD server we need to generate control file.
> Alter database backup controlfile to Trace.
It will generate the Cntrl File under usertrace directory.
Copy the cntrl file to quality system and rename it as with .sql extension.
08-Sep-09
BRTOOLS ERRORS
09-Sep-09
IMPLEMENTATION
5. Entry in etc\services
PORTS
6. Make sure that Installation Ports 21212, 21213 are not used
8. All the entries are stored in control.xml and installation progress is stored in keydb.xml If the
installation is aborted/ cancelled then the above two files will help us to start from the point where it
stopped earlier.
9. An installation directory sapinst_dir is created which host the log files of the installation
Note: SMSY > System Landscape > Other object > create
sap* : 06071992
ddic : 19920706
165
10-Sep-09
Repository consists of your ABAP objects like programs, function modules. ABAP data dictionary
consists of tables, domains etc.
Data dictionary is like a part of repository only.
From SE11
these are database objects
Database tables
views
datatype
Lock objects
Searchhelp.
Type group
Domain.
Note:
----------------------------------------------------------
OS = SIDADM
SAPSERVICE<SID>
PROFILE MANAGEMENT
Usr\sap\SID\sys\profile
1. Default
2. start_DVEBMGS00_<HOSTNAME>.pfl
3. <SID>_DVEBMGS00_<HOSTNAME>.pfl
Installation Questions
1. Installation Pre-Requisites
167
2. Installation Inputs
3. Difference between earlier and Current Versions
4. Installation Checks
5. Starting of SAP System.
Installation Pre-Requisites
Installation Inputs
Parameter Summary
Task Progress.....~~~~~~~~~~~~~~~~~~~
Installation Checks
SAPOSCOL is an operating system collector ensure that sufficient resources are available to start SAP
system.
2. Groups: Following groups are created to work on Oracle Database and R/3 Executables.
ORA_<SID>_DBA
ORA_<SID>_OPER
SAP_<SID>_GLOBALADMIN
SAP_<SID>_LOCALADMIN
SAP_LOCALADMIN
6. SAPDATA1 is created with datafiles saparch, oraarch, sapcheck, saptrace, sapreorg and
redolog files (OriglogA, OriglogB, MirrorlogA, MirrorlogB)
Database specific file system.
7. On Windows MMC(Gui based) is created to start and stop the SAP System
To start and stop the SAP System
8. On UNIX startup scripts are created on <SID>ADM in Home Directory (startsap, stopsap)
10. Oracle database uses (ORASID on UNIX other users like OPS$ Users, SAPSR3, SAPSR3DB)
a) Starting the database using command strdbs.cmd this command starts the database and writes
the log files to stderr1.log which is in the work directory
b) Starts the Message server using executable msg_server.exe and writes the log into work
directory dev_ms.log if it is not started it writes the log into stderr.log
c) Starts the Dispatcher using executable disp+work and write the log file into
work\dev_disp and stderr.log
4. When the process are started they read properties from Instance Profile
SID_DVEBMGS00_HOSTNAME.pfl
Such as number of work processes, memory, buffers etc and writes the logs into dev_w0, dev_w1,
dev_w2 ... dev_wn-1
11-Sep-09
192/ 172/ 10
202.65.136.146
171
NAT - Network Address Translation
All the servers are managed with Private IP but , they are available externally by using Public IP.
Whenever a request comes from Internet to a public IP. It is translated to Private IP or Routed to PVT
IP.
EPSIBIC - Extended Binary Code.
2. If the database is not started then start the database and look into the log files alert<SID>.log
which resides in saptrace\ background directory
Oracle\SID\saptrace\background
Identify for Oracle errors that start with "ORA"
Example 1033 .... DB_Connect Issues. i.e. The work process is unable to connect to the database.
Check the connectivity, listener status, listener.log, listener ports, listener hostnames, database startup
statuses etc.
cmd> lsnrctl
14-Sep-09
172
07-Jul-09
BASIS
Recently
SAP --
Manufact
uring
--
Retail
Applicati
on Server -
Allocates
Processes
-
Accelerates the
requests
INSTANCE
-
It's an Agent
-
Communicates
173
with Database with the
Native SQL
- Dispatcher
Accessing the BASIS repository over the web... and for this SAP Implemented a component called ITS
(Internet Transaction Server) separate tool windows specific. IIS (Microsoft internet information
service)
ABAP
BASIS into a common supply chain/ Platform
BW
The integrated ITS uses the common HTTP mechanism as in SAP Web AS, no additional Web server is
required as, in the case of the standalone ITS.
08-Jul-09
BASIS
All these applications are robust, reliable, stable, and consistent which are built on ABAP language.
LANGUAGE ***************************
SINGLE CODE PAGE: The database is installed on a code page like 1100 which can support the
like minded languages around 10 (En, German, Dutch.....) but each additional languages should be
imported. SMLT
Languages like Chinese, Thai, Korean, and Japanese cannot be accessed using the
above code page, due to this reason we need multicode page (MDMP - Multi Display Multiple
Language) on the same system.
MDMP has various disadvantages during upgrade i.e., code page conversion.
From SAPWEBAS 640 SAP provides only two versions (Non-Unicode and
Unicode). SAP Stopped supporting blended (Multi) code pages i.e., MDMP and introduced UNICODE
to support all the languages i.e., the characters are stored in more than one byte.
NON-UNICODE: It is similar to single code page and supports only the like minded
languages.
When there are no plans to expand the business globally this is the best
option. In future we can perform a UNICODE Migration. (NON UNICODE to UNICODE)
1. Ensure that the version is Unicode enabled like ECC6.0, BI7.0, and CRM2005 etc,
2. Use SAP Installation Master DVD
- Additional Life Cycle.
175
- TASKS
- System copy
- Source system
- export NUC
3. Target system System -> Import with Unicode Kernel.
Note: As the Kernel is going to be changed during migration the whole database needs to be deleted.
****************************
In order to provide the web functionality to all SAP components ITS (Internet Transaction Server) is
introduced by SAP.
ITS installed on a separate machine or Application server to handle the web requests. In the earlier
scenarios APPS Dispatcher used to handle the user request but in web scenario the HTTP requests are
handled by ITS.
Process Flow:
1. The web requests are received by Wgate which are in the form of .HTML or .CSS
(Cascading Style Sheets).
2. These requests are forwarded to Agate.
176
Diag is a protocol that is used to handle the request coming from SAPGUI on port 3200 Series 3200
+ Instance Number
3. Agate converts web request into Dynpro specific requests so that they
can be handled by Diag Protocol.
4. The Dispatcher in the Application server handles the request and process it.
Time Consuming
Not an Integrated Service
It depends on IIS (Internet Information Server) to host the pages
Non Business
User input -> Queue -> Assign a Counter -> Screen -> Withdrawal -> Insert, Update or delete.
Instead of ITS SAP included WEBAS 640 and included ICM service within the Application Server. (ICM
- Internet Communication Manager) which is called IITS (Integrated Internet Server) Tcode:
SITSPMON
178
IE -> [ICM + IITS]
WEBAS
Introduction of WEBAS
Until versions R/3 4.6c (Kernel Version 4.6D) ITS provided the web functionality (APO 3.0, BIW 3.0 are
the last basis components)
SAP Introduced ICM (Internet Communication Manager) and named the platform as SAPWEBAS 6,
this platform is going to be a common platform for all the SAP Applications even the ICM is
introduced in SAPWEBAS and its still require ITS to process the web request. SAP introduced IITS
which is integrated in WEBAS640. It is accessed by the tcode: SITSPMON
BIW 3.5
ECC 5.0
ECC 6.0
XI 3.0
SCM 4.0
SRM 4.0
CRM 4.0
Are the SAP components that are installed on a common platform SAPWEBAS 640.
09-Jul-09
Colorful, dynamic, chat, Knowledge Management, Work List, Rooms, WEBEX, offline, Logos etc.,
179
Consider an Example -
KM - Knowledge Management
CM - Content Management
TREX Engine - Text retrieval and classification engine searches the information and bring out from
Terra Bytes of data.
PI - Where the content is fetched either from BI, XI, as and when required
NETWEAVER - PIPA
P - People Integration
I - Information Integration
P - Process Integration
A - Application Platform
From Netweaver '04 S, SR1, SR2, SR3 or Netweaver '07 all the above content provided on one single
DVD.
- The software that is required is Installation Master
- Exports
- Java Components
- JCE Policy (Java Cryptography Extension)
- Kernel
- The respective database (DB2, SQL, ORACLE, MaxDB)
After installation the entire content resides in the database only.
Kernel resides at OS level. It provides runtime executables/ libraries that are required for SAP Engine
(SAPWEBAS)
The Installation master provides an option to install all the Netweaver components together with SAP
application component (ERP, CRM, SCM, and SRM)
Usage Types: Provides certain functionality to the business components. Usage types are selected
during the installation.
Usage types are ABAP, JAVA, PI, BI, JAVA, EPCORE, EP, BI, MI (Mobile Infra), Development
Infrastructure.
10-Jul-09
Netweaver alone cannot bring business it should be coupled with one of the SAP Business
component like ERP, CRM, SCM etc., However when we choose to install ERP, CRM, SCM they gets
installed on ABAP platform which is a part of Netweaver.
Netweaver Installation:
OS : <SID>adm
: SAPService<SID>
DB : ORA: Sys, System, Outln,
MSS (Microsoft SQL Server): <SID>
OS (UNIX) : ORA<SID>
R/3 Specific application users : SAP*, DDIC
R/3 DB Owners : SAP<SID> upto WAS640
: SAPSR3 for ABAP on WAS700
: SAPSR3DB fro JAVA on WAS700
MSS : <SID>
Select username from DBA_USERS;
5. Provide the path for Software dump (Kernel, Exports, JAVA Components) on UNIX we may need to
abrupt the installation and install the database but on windows the database can be installed before
in hand.
6. Ports
3600 - 3697 - ABAP Message Server
3900 - 3999 - JAVA Message Server
3200 - 3297 - Dispatcher port
184
4700 - 4797 - Dispatcher security port
3300 - 3397 - Gateway port
4800 - 4897 - Secured gateway port
50000 - JAVA instance port if instance number is 00
Eg: https://201.17.12.22:50001
50001 - SSL (Https) ref: help.sap.com
ABAP dispatcher starts the JAVA instance provided the parameter rdisp/
start_j2ee is set to true or use SMICM to start manually.
Central Services instances are provided in JAVA Engine which consists of JAVA Message Server and
Enque Server to provide load balancing to the web users and central locking for all the JAVA
instances.
Dialogue Instance: Except Message and Enque (Dia, BTC, Spool, gateway &
Update)
Dispatcher-ABAP is used to handle the requests and process them based on FIFO
Dispatcher allocates the requests to work process (Dialogue) for interactive communication.
Dispatcher-JAVA is used to handle the requests and process them to server processes.
11-Jul-09
A Business Configuration Set is a set of Customizing settings which are grouped according to
logical, business management criteria to a unit. For documentary, quality assurance and re-use
purposes which is independent of the original Customizing tables/views which is accessible across the
system landscape.
JAVA Startup
- Use MMC
- Startsap command
- SMICM
- or rdisp/j2ee_start=true used to start along with ABAP Engine but consumes at least 10 Mins
to 30 Mins.
- Database Instance
- Central Services Instance
- Central Instance
- JAVA Dialogue Instance (Optional)
Process Flow
1. User uses any of the above startup methods to start the JAVA Engine
2. The system is started by using startup profile
It consumes more time to start because bootstrap reads the parameters from the database to
instance.properties and bootstrap initializes Jlaunch for dispatcher, jlaunch for SDM and while
initializing Jlaunch for server process it synchronize the binaries(All logs) of the dispatcher and
the servers.
Install the LAN Drivers and assign the static IP Address : 172.17.10.11
255.255.0.0
Installing ECC6.0
SAP Installation.
- run sapinst.exe
- SID
- Master Password
- JAVA Components
- Exports
- Kernel
And prompts for SOLMAN Key get this from SOLMAN System.
12-Jul-09
Usagetypes.properties
1. Usage types
ABAP, JAVA, EP, EPCORE, DI (Development Infrastructure), BI
JAVA, PI and MI
2. Machine Type
193
NT INTEL, HP UNIX etc
3. Memory available on the system
4. The number of CPU's and CPU speed
5. System ID and Instance Number
6. Hostname and ports used along with backend ABAP Client. It also specifies the users
that are created during installation along with the encrypted password.
Note: SAPJSF user (Security Framework user) is created in ABAP Engine to communicate with JAVA
Engine. This user reads the ABAP user master and ensure all the users are in the JAVA engine. JAVA
engine doesn't let us to create users as the Data source will be in ABAP.
SAP*
DDIC
SAPCP These are not counted for Licensing
It is the Instance directory which specifies the types of processes, engine type, instance
number. It contains the following directories.
1. DATA: Used for storing the lock entries, statistical data etc
DVEBMGS it is a Kernel directory (Soft link to the physical one)
2. IGS: Internet Graphic Server which is used to provide graphic services over the
web.
1. Admin Directory: Used for administrating the J2EE engine using Visual Admin tool.
It also contains the directory Standalone Log Viewer to display the logs of the J2ee engine if its not
started.
Dispatcher + Server = Local instance (Cluster)
2. Cluster: It specifies the dispatcher, server and bootstrap process. It contains binaries
that are required to start the above process. It also contains instance.properties to start the instance
(We can find by what time the instance is started)
194
Cluster\dispatcher\log
Defaulttrace.0.trc is a file available in the log directory for both server and dispatcher.
3. Config Tool: It provides a tool to change parameters of the instances either globally
or locally.
4. Deploying: It is a tool that is used to deploy the small programs in to the JAVA
engine.
5. JSPM: it is a tool to apply patches (JAVA Support Pack Manager)
6. Log Directory: sol\DVEBMGS00 it specifies the MMC log/ SM21 Logs with log goto
slog - clear all the logs and that is equal to Syslog.
It is used to apply the patches for various Netweaver640 and 700 and it is discontinued in 7.1
NETWEAVER TOOLS
\usr\sap\<sid>\sys\global
Sys\profile directory: consists of profiles to start and also to control the behavior of the instance
Sys\global directory: consists of SLD (system landscape directory), XI folders, template config tool,
Adobe services etc.
\work directory: consists of developer traces, JVM Logs (Java Virtual Machine), Standard error logs
starts with std and these are used to debug the startup errors.
SAP Provides predefined templates to configure BW, EP, XI, J2EE engine etc.
It is used to provide the log access at O/S level when the instance is not started and also
used to display the logs based on search text, date and time, severity etc., (Displays the logs in user
friendly format)
\usr\sap\<sid>\DVEBMSG\j2ee\admin\logviewer.standalone
This is used to deploy and undeploy the support packages, small developments that are
coming with extension .sca (SAP component Archive) .sda (SAP Deployable archives), .zip, .jar (JAVA
Archives), .ear (Enterprise archives), .war (Web archives) etc.
SDM is started as a process using the executable jlaunch. There will be only one SDM in
the entire system.
SDM has its own directory which contains binaries, config, log and libraries.
During deployment (applying the support pack) it takes backup of the repository. The major
advantage of SDM is to undeploy the support packages(during conflicts) but its a disadvantage when
compared with system consistency because it can undeploy the dependent packs also. SAP
recommends to use JSPM from 7.0 onwards. In WEBAS 640/ NETWEAVER 640 JSPM is not available
and in NW710 SDM is not available.
Changing the SDM Password: if SDM password is unknown we can set a new password using
command line interface
196
sdm changepassword.
Note: In order to change the password SDM should be running in standalone mode.
SDM can be started in standalone or in integrated mode using command
sdm jstartup sdmhome =<.....> [mode = integrated/ standalone]
Note: it is always recommended to logoff from the SDM instead of closing the window. the window is
closed but the SDM Client is still connected to the server in this case we need to restart the SDM.
Depending upon the nature of the patch it updates any one of the above
Click on next and click on start deployment
Logviewer tab provides the deployment status along with the duration of the deployment.
SDM reads the files from the specified location not eps/in and it has its own inbox to process the
deployment.
The patch status is obtained from system - information option in the home page
http://<hostname>:50000
SDM startup modes are standalone/ Integrated. Default mode is integrated and standalone mode is
used to change the password.
13-Jul-09
4. Config Tool:
a) When JAVA programs are defined they used to save extension .JAVA (eg bank.java) it is
compiled into bank.class file. This class file will be distributed to the customers irrespective of the
operating system
Authenticate - login
Authorized - Executing tasks
These files are interpreted by using JAVA Virtual Machine. JVM contains Byte code verifier and
class loader. Initially JVM checks the class files and verify the bytes in the code and then signals to
load the class file to display the screens/ Logic executed. This is the reason why JRE is required to
execute JAVA Program.
e) Offline configuration mode to change certain parameters eg: when all the users are locked,
this option is used to enable SAP* user. when SAP* is enable no other user can work on the system.
Unlock the admin users and disable SAP* (two restarts are required)
f) It works only on the database as it needs to connect to the database using the OS
authentication (doesn't require any userid and password)
14-Jul-09
It is used to login to the system remotely when the system is congested (Hourglass mode).
In Netweaver 7.1 SAP provides Shell Console Tool in the J2ee Directory and up to Netweaver 7.0
telnet tool has to be executed manually from the command prompt.
\usr\sap\<sid>\DVEBMSG\shellconsole from 7.1 only
It provides the menu to administer cluster, memory and restart the processes if required.
Command=> 0 to Exit
Command=> 30 to refresh the instance data
(It is used to clear the shared memory in use)
It is introduced in Netweaver 7.0 to replace SDM tool. SDM is not available in NW 7.1
It is initialized by go.bat which is available in JSPM directory. JSPM has its own patch level similar to
SPAM which is updated by JSPM.
JSPM is used to deploy business packages like employee self service, manager self service, new
software components & additional usage types. It is also used to control the transport of objects
between systems in the landscape.
The main advantage of JSPM is undeployment is not possible, consistency between support packages
are checked and displays the source and target patch levels. The another major advantage is the
patches can be deployed arbitrarily like 1 to 5 (i.e missing the sequence).
It is also used to upgrade kernel where the system will be restarted as per the requirement (NW
Consultant should take the backup of the kernel)
Process:
Download the respective software into EPS\In directory (.sca, .sda, .sar etc) and place them in
EPS\In
Specify the SDM Password (SDM and JSPM should not be operated simultaneously to avoid
inconsistency of the system).
JSPM reads the EPS\In directory and displays if a valid support pack is available.
Note: In earlier cases before applying any packs need to apply SPAM but here JSPM.
200
Support Packs NW - 18
EHP1
SOL - EHP1
ERP - EHP4
Note: Among the selected packages SAP Identifies which one be prioritized first in this case JSPM
goes first.
Select the target SP level can click on next to deploy the patches.
JSPM maintains its own log files if any dependencies are missing it will abort the deployment.
It is used to administer the users, groups and roles. User admin is a part of NW Identity
Management tool.
Standalone JAVA engine has various options lie user creation and password management in the user
admin tool but whereas in the integrated engine the user management is taken over by ABAP Engine
except assigning J2EE roles.
It is available since NW7.0 and used for JAVA engine, administration, configuration and
monitoring. It is used to perform the post installation activities based on the usage types. Also used to
start/stop various services, process and applications. From NW7.10 all the visual admin tool tasks are
performed by NWA Tool. It provides reports related to users, memory, performance, components etc
similar to ST03.
http://<hostname>:50000/sid
It is a landscape information provider service to provide the information of all the systems in
the landscape along with products, software components, patch levels, clients information etc.
(000,001, 066)
201
It is effectively used in XI, PI and became a mandatory component as per ITIL/ Standards
Infrastructure Library.
15-Jul-09
\server0\apps\sap.com
Applications only sync by the server process.
1. JControl Initialization
2. Initialize bootstraps (Cluster)
3. Bootstrap reads properties from DB
4. Bootstrap updates instance.properties
5. JControl Initialises Jlaunch (DISP)
6. Dispatcher Kernel, Libraries are synchronized before they get started
7. JControl initialises JLaunch (SDM)
8. JControl initialises JLaunch (Server Process)
9. Server Kernel, Libraries, Binaries are synchronized before they get started
10.Server Starts the Application
So each manager/ service has four values and the priority of execution as follows
Global Default
Global Custom
Local default
Local Custom
Services:
These are similar to SAP Transactions to perform certain tasks on the J2EE engine. These are
also used to perform certain post-installation activities.
205
1. Log configuration Service:
This is similar to SM18/ SM19 to trace the user activities. It is used to set the log locations for
the applications. It is also used to set the traces for certain activities.
It can be edited by choosing the server/dispatcher, or using the service in config tool/ Visual
admin tool.
Set the granularity of the log level (Using Min & Max)
Severity is also setup based on requirement.
Most of the services are available both in config tool and visual admin tool. VA services are
explanatory than config tool services and also VA provides additional functionality.
Tracing option is provided in VA Tool whereas in config tool it is not provided. It is used to set (SQL,
RFC, Enque, Buffer ST05 Trace) the traces, logs.
Logs: These are by default written to the default log locations without any initiation/ Initiative. These
are logged into categories.
Traces: These are explicitly switch on by the user to trace the user activities. These are logged into
locations.
We can also switch SQL Trace similar to ST05 to identify the expensive SQL Statement.
J2ee\cluster\dispatcher\log
It is used to display the logs and it is similar to standalone log viewer service.
16-Jul-09
Note: It contains 2 licenses one is standard license (Permanent) which is valid till 31.12.9999 and the
other one is maintenance certificate which is valid up to 3 months.
Maintenance certificate locks the SPAM and JSPM after 3 Months.
It is similar to SM59 used to create RFC connections to the backend systems. Program ID
plays an important role to establish connection between the systems.
It is used to handle the request and keep them in socket queue. They will wait in the
queue until they are processed (or) timeout (This is applicable for dispatcher only).
From Visual Admin
Dispatcher
- Services HTTP Provider
Keep Alive time to 75 instead 15 Sec.
On server side we have to set Cache Size up to 999 and file buffer size & Other parameters specified
bye SAP from VA Tool.
6. Deploy Service:
It is used to start and stop the deployed applications. It is widely used in XI/ PI to check
the specified applications are running, if not manually run/ start the application.
It is also useful to deploy the small application like (*.ear) Enterprise Archive files.
It is similar to SM12 and is used to identify the users who are explicitly locking the
resources for update. We can select the user and release the lock. (Process needs to be followed)
Enqueue Table (100MB size) determines the locking table size enque/table_size
8. Monitoring Service
It is used to provide monitoring for all the kernel, services and performance of the
system. It is similar to CCMS Monitor (RZ20) alert monitor.
Eg: If the defined threads are completely used then Thread congestion occurs. If no threads are
available the system marks the respective Manager/ Service in traffic light signals (Yellow-Green) in
this case it is Red.
9. Performance Tracing
It is similar to SE30 runtime analysis of ABAP Program and ST05 system trace to trace
SQL, RFC, Buffers and enqueue. We need to switch on the trace explicitly for a specific module along
with the user name.
Used to fetch the information of users, threads, component and requests. Similar to
ST03-(Work Load Analysis)
It is similar to SU01, Pfcg which is used to create users and assign roles. It is also similar
to SM04 to display the login Users.
This service populates the JAVA Engine information into SLD for every 720 Minutes
(12Hrs) in ABAP Engine RZ70 is used to populate SLD.
Login\password digits
Login\lang etc.
Note: Form Netweaver 7.10 onwards VA tool is discontinued instead NWA is implemented.
17-Jul-09
Note: Solution Manager installed with usage type JAVA and SLD is configured on it.
Both the systems are used to maintain the landscape information.
Existing System
PRD
Scenario:
ERP
EP XI BI DI CRM
SCM With JAVA Stack
SRM
SAP Provides system copy option in the installation master DVD from Netweaver onwards.
System Copy:
While performing a system copy using SAP tools it will prompt whether database can be
exported (use database specific methods) This option should be unchecked if we are performing the
following.
Note: It is a time consuming process because the complete database content is exported into an
independent format which will suite to all operating systems and databases.
In case of a system refresh select Database specific tools so that the DB can be restored from a
valid backup which will minimizes the export and import. In this case it exports the directory structure,
SDM and application specific content. (D:\tmp)
18-Jul-09
Discussion class about System Copy.
19-Jul-09
No class
20-Jul-09
212
Memory Management
Physical Memory:
The memory that is installed on the machine and allocated to the machine by
PHYS_MEMSIZE.
The memory that is installed could not cater to the requirements of the users so a part
of disk is used temporarily which is referred as virtual memory. It should atleast 20GB or 3 times the
RAM (which ever is larger)
Shared Memory:
Local Memory:
Extended Memory:
The memory that is exclusively measured for all the SAP WP (It is a part of shared
memory)
213
Ztta/roll_extension per user context
Em/initial_size_mb = 512MB
Heap Memory:
The memory that is dedicated to a process till the completion of the task or timeout.
ABAP/heaplimit
ABAP/heap_area_dia
ABAP/heap_area_nondia
ABAP/heap_area_total
Zttaroll_first 20 KB
Zttaroll_ext 500MB
Roll_Area 20MB
ABAP/ Heap 2 GB
PVT Mode
WP goes to pvt mode then use DPMON and kill the session.
Eg:
Rdisp/max_priv_time
Rdisp/wppriv_max_no (wont waits for default 600secs)
Eg:
Note:
SM50
Note: All the memory parameters need a restart as the memory is @ OS level.
1. When a user request for a resource the Work Process rolls the user context for
handling the task.
3. If this memory is not sufficient then it uses the extended memory i.e.,
configured by ztta/roll_extension
4. If Extended memory is not sufficient then it uses the remaining part of the local
memory i.e. configured by ztta/roll_area
5. If local memory is not sufficient the it uses the heap memory that is configured
by abap/heap_area_dia which is a part of abap/heap_area_total
6. if the work process uses the heap memory it is said to be in private mode and
its runtime cannot be controlled by
If more number of WP goes into pvt mode then memory bottle neck/ hourglass/ WP
congestion occurs which can be resolved by killing the expensive work process using DPMON
because logon is not possible to kill through SM50.
Each WP required around 75MB to 150MB (DVEBMGS) of memory. This memory should
be configured by (PHYS_MEMSIZE). Each dialogue WP serves
5 - 10 Users.
JAVA memory is managed by JAVA Virtual machine. The programs are loaded using
class loader, byte codes are verified before they are interpreted.
JAVA uses heap memory to ensure that the requests are completed.
Heap memory is configured using -XMS 1024M from config tool.
It is only configured for Active instances i.e. only local configuration is allowed. Dispatcher and server
has their own values.
216
While interpreting the requests if a new content is fetched it uses NEW GENERATION MEMORY
which is configured by parameter.
- XX:NEWSIZE
- XX:MAXNEWSIZE
It will be 1/3rd the size of heap memory
Eg: for 1GB(1024) Heap 341MB
If the content is old and can be reused then it will uses OLD/ Tenured generation.
It is calculated by using new generation memory.
For server process the new generation memory will be 1/6th of the Heap size or 1/4th of the PERM
size.
If the content is not eligible to store it will be thrown into garbage (GC)
21-Jul-09
Do not modify the store unless it is recommended by SAP. The default store is UME store (User
Management Engine).
Universal Description Discovery and Integration is used to populate the users from the third party
database (Oracle, Siebel etc). It is an industry standard to populate the users from one database to
other using web services.
1. Using ABAP SU01 (Mandatory in case of an Integrated Installation i.e. ABAP + JAVA). The details are
available in UME Provider Service from VA tool.
Note: No need to create RFC's to have the users to replicate in JAVA which has been created in ABAP
(SU01) & LDAP.
We can also use VA tool to get the configuration of the back end engine.
It is also possible to have LDAP in the back end engine i.e. users can be populated in ABAP engine
using LDAP.
218
Note: In case of Integrated engine, ABAP engine take over the complete user management i.e. users
are created only through SU01 (The back end engine can get users from either LDAP or CUA)
In order to ensure the consistency of user management SAP Allows only one data store to populate
the users. UME can get the users from any one of the following Data source.
It is used to populate the users from a directory server (MSADS - Microsoft Active Directory),
(Lotus-Domino from IBM), IPlanet.
Userpath: it shows where the users are placed common name : BASIS
The above information is provided by Domain administrator.
* SAP_BC_JSF_Communication_RO (read only) we can also cerate our own user but the above role is
required to communicate with J2ee.
c) UME Engine
Roles:
Roles are used to provide access to data and functions. As discussed above users are only
populated from the backend systems we need to assign roles in the J2ee engine to access the
functionality over the web so, in order to access a report on the web the user should have permissions
220
both on the J2ee/ ABAP (back end system). If any one of them are missing user cannot access the
functionality.
22-Jul-09
ROLES
SOX: Segregating roles to different users. A business transaction should not be assigned to a single
person to avoid the fund misusage
221
Sarbanes-Oxley Act (SOX)
23-Jul-09
AUTHORIZATION
ROLES: Roles provide the activities that can be performed by user. ABAP roles does not
have any authorization in JAVA Engine.
1. UME Roles
2. J2EE Security roles.
UME Roles:
J2ee core engine is built with Java programs. Each program that needs control is defined
by permissions.
a) User Administration
b) Role and Administration
c) Support and Administration
Each Application should be defined with roles that appears as J2EE security roles. As the programs
needs security the developer should identify and define them during development. During
deployment the descriptions should specify the roles. In most of the programs web.xml contains the
roles and these are displayed in
These roles need to be assigned to the users using VA tool. Due to the discontinuation of VA Tool,
these roles will be moved to portal roles and can be assigned using User Admin tool.
Example: SLD: The role name is lcradministrator is now displayed as UME Role. However other
application roles will be displayed as portal roles.
Portal roles are application roles that are used to protect business packages. Even though full
authorization is provided in JAVA engine we may not able to access the content/ functionality in the
back end system unless ABAP roles are assigned to the user.
Note: ABAP roles are used to protect the sensitive data like HR information, Functional information,
Material information, Sale Info etc. Java roles provide screens, pages to display the above data.
User should authenticate to login JAVA and Authorized to access the screens. Also should have
authorization in the back end engine.
SAP_BC_Roles
LDAP - SM59
1. Execute SM59
2. Define a connection of Type T
3. Specify the connection (LDAP Connector)
4. Create an (System User) not SU01 user
5 Define LDAP Server by using connector
6. Connect to the LDAP server using system user
7. Define LDAPMAP for user attributes
(users that are defined in ADS needs to be mapped w.r.t. SU01)
8. The traffic light should be green
223
9. Use LDAPLog to check the user synchronization logs.
10. Schedule synchronization using RSLDAPSync_user
11. Use RSLDAPTEST in SA38 to test ADS (Active Directory Server)
JAVA Monitoring
1. Monitor the work directory so that Dev_Rfc; Dev_Rd are not populated largely (the growth indicates
the RFC issue).
2. Log files in cluster directory and archive them frequently. Log files such as default.trc
J2ee\cluster\server0
3 Monitor the space (there should not much growth on the file system, unless the log files grow
abnormally, patch application, tran/eps/in (Can be cleared)
6. Use log viewer service to monitor the logs related to the applications.
7. Ensure that traces are not switched on during normal operations(they will fill the OS and the J2EE
engine may not be started)
8. Using monitoring service to monitor the user request overview. component overview and identify
the critical requests with high response time.
9. The response time is defined as 2 to 3 seconds depending on the system resources.(It purely
depends on the backend system database time)
10. The backend system may sabotage(damage) the response time of J2ee Engine so it is also
required to fine tune the back end systems (running DB stats, identify the missing indexes etc)
224
11. User creation and role assignment
16. Worked with SLD assigned roles LCR* to configure SLD both manually and using NWA Tool.
18. Configured ABAP engine using RZ70 to populate information into SLD.
19. Configured JAVA engine using SLD DS service to populate info in to SLD
21. Imported the latest CR Content into SLD from the Market place.
22. Performed backup of the SLD so that it can be imported during SLD Inconsistencies
26. Define the landscape and include all the systems in the landscape.
SOLMAN SLD
24-Jul-09
SLD provides the landscape information of both SAP and NON-SAP systems. This is required as
a part of the ITIL standards. IT Infrastructure library standards.
DMTF- Distributed Management task force is an initiative to provide the information of the available
systems in the landscape.
SLD - DMTF
SLD is available using url http://<hostname>:50000/sld. In order to work with SLD we need
lcradministrator role. It can be assigned using Visual Admin Tool but now in User Admin Tool.
SLD can be initialized by using NWA tool. By default SLD is configured in the J2EE engine.
NWA tool is to check the SLD, Startup and also the availability of SLD to other systems.
Eg. SLD on a standalone J2EE engine is not available to other systems, because SLD needs a
gateway which is available through ABAP engine. To work with standalone gateway to be installed on
the SLD.
RZ70
NWA Tool - click - deploy and change configuration views
226
- Initial configuration or
- All configuration tasks
Post Installation activities can be done from here for PI, BI, MI, EP, etc.
Sapinst.exe
- Netweaver 2004s
- Standalone Engine
- Gateway
- Gateway installation
SLD_UC
SLD_NUC RFC's are created to establish communication with SLD.
We can register a system in SLD, but it is recommended to use RZ70 in ABAP engine
227
SAP_SLD_DATA_COLLECT
SAP_SLD_DATA_STARTUP
Systems like XI, Seibel, Remedy can be registered as a third party systems.
To define a third party system we need to define Product and the Software component version.
Under software Catalog - Click products
3. It provides the details of each managed systems like OS, DB, SAP Application, patch levels, client
information, logon groups, number of instances, message server etc.
4. It provides the available and current patch level information using CIM/ CR_Content
(Component Information Model and Content Repository) This information is updated by
downloading from SAP Market place using note 669669.
8. All the systems to configure as backend for EP, XI, BI needs to be registered as Technical systems in
SLD.
25-Jul-09
TYPES OF SLD
1. SINGLE SLD
There will be only one SLD in the landscape which provides the complete information of systems in
the landscape.
This is used in small mid sized companies where only one landscape is maintained.
2. DISTRIBUTED SLD
Companies like HP, P&G, GE, Coke has their global presence through out the world which maintains
multiple landscapes across the world.
It will be difficult to fetch the information of all the systems using single SLD. So it is
recommended to have individual SLD for each landscape and communicate each other using data
suppliers.
Downloads Tab
> SAP Distribution Center
>Downloads
>Support Patches and Contents
229
>My Company Application Component
3. ISLAND SLD
Companies may require Data security. Production systems and they doesn't want the SLD to be
shared between DEV, QAS and PRD. All the production systems in the landscape uses a different SLD
called as ISLAND SLD.
SLD can be started and stopped using the option Administration. It will not effect the
operation of J2EE Engine.
SLD Log
Profile
It is used to set various parameters that are required by the SLD (Do not change the
parameters during import, export and backup)
230
Eg: In a standalone J2ee installed reset the Data supplier parameter. Gateway host, gateway
service. Default trace should be false.
Data Supplier: We can configure other SLD's in case if we are defining distributed SLD.
Content: Import export backup. It provides the product and software component information along
with systems that are configured on the SLD.
Import: Basically this is used to import the content that is delivered by SAP. But we can also import
the content that is exported earlier from the same SLD.
Backup: It is used to take the backup of SLD content. It contains only time stamp to differentiate
between backups.
Backup (Copy of SLD Content)
Export: It is similar to backup but versions are maintained between exports along with time stamp.
Change Logs: Used to display the logs of content change based on user name, class name and the
time interval.
Name Space: Used to define the namespace for developing the objects by default SLD/Active is
provided.
231
26-Jul-09
UPGRADE MOTIVATION
SAP Supports support packages, stacks, notes, patches, upgrade, runtime support, license key,
developer keys etc. All of the above can be obtained by using suserid of the other company
The Hardware doesn't support the current load and users encounter-frequent bottle necks on
memory CPU and storage.
To get the enhanced features that are provided in the current release.
SAP upgrade may involves O/S and database upgrade which drastically improves performance on the
new hardware.
Upgrade never impacts on the DB Size. The upgrade only upgrades data dictionary and repository
objects.
The same OS, DB, R/3 patch levels for homogenous. Different OS, Different DB but same R/3 version
with patch levels- Heterogeneous.
It is not possible to refresh database of 4.7EE on ECC5.0 vice versa because the complete DD and
Repository is different.
If the DB Schema ID/ Owner is SAPR3... then the version is 4.6C and below.
232
UPGRADE PLAN
19. Unicode consumes atleast 40% more than the current system resources.
27-Jul-09
233
20. Development and Technical teams need to certify the upgrade before going live.
21. Prepare and upgrade phase list are provided with expected percentage of time. Use that list to
document the phases and to update the status to management and SAP.
22. Document all the interfaces and 3rd party tools like IFS, VERTEX, VIRSA, Background Schedulers
like TIDAL, MAESTRO, REDWOOD, CONTROL IN etc.
Running Prepare
Prepare need to be executed and ensure that all the prepare phases are run successfully.
Prepare prepares the system for upgrade by checking all the pre-requisites and documents in
checks.log
Mount the upgrade master and execute prepare.bat to create a directory and extract
executables.
On UNIX we may need to create /usr/sap/put with SIDADM as the owner with atleast 10GB of
space.
Upgrade runs on client - server mode. So upgrade server needs to be started to run the
upgrade assistant.
All the components are priced based on business suite. A user created in component can access other
components with same license key.
I. INPUT PHASE
It checks all the pre-requisites and writes into checks.log
OS, DB upgrade, Additional Hardware.
All the above phases can run individually or can run as a total.
It checks for the following OS Versions, DB versions, Disk space, File system,
Patches, languages, kernel, readability of profiles etc.
Eg: If profiles (Startup, Default, Instance) are corrupted or not readable the PREPARE fails.
\put directory is an upgrade directory.
1. SAP<SID>, Instance number, batch host (The instance that provides the background process).
Profile paths \usr\sap\<sid>\sys\profile, Host name, Mount point of CD's (Upgrade master, kernel,
upgrade languages, upgrade exports)
Specify the parameter dir_put (put = \usr\sap\put) put directory is the upgrade
directory which hosts exe, log etc.
During initialization it checks for OS, DB Versions, checks for enough space in the
put directory for import, checks RFC connection using DDIC pwd and the client.
Checks the connectivity with the DB.
235
IV. INSTALLATION
1. Instance number of shadow system, port number, kernel directory, profiles (\usr\sap\put), create
DB_user for shadow instance. Include support packages in the BIND_PATCH phase, Add-ons in
IS_SELECT phase and languages LANG_SELECT. It checks for unreleased transports, add on conflicts,
language compatibility and database issues like table space over flow (ORA-1631 & 32), (ORA-1653 &
54)
Archieve Issues
Ensure that all the prepare modules ran successfully to proceed for the upgrade.
During the prepare phase we need to download the upgrade fix FIX.SAR
28-Jul-09
PREPARE also checks the following
- Free database size and recommends the tablespaces that needs to be extended.
- Free extents in the tablespaces which needs to increase (ORA-1631; ORA-1632)
- Checks the Archive directory (ORA-272; ORA-255)
- Checks the connectivity to the database (ORA - 12500)
- Checks the space in the upgrade directory
- The should not be any terminated/ Pending updates
- There should not be any unreleased transport requests
SPAD/ SPAU
During the upgrade it only changes the SAP standard data structure like tables, programs, screens,
menus, function modules etc.
Customer might have changed the above objects by obtaining SSCR keys (SAP Software Change
Registration) or they are upgraded by Note, Patch, Support Package, Stack etc.
236
SPDD: for the data dictionary elements (like table, domain and the dataelement).
Eg: Employee ID is 25 ; EMPID 25(INT) is changed into EMPID 50(INT)
SPAU: for repository objects like (Reports, Screens, Programs RICEF) that is code which is written in
ABAP is changed.
The SPAD & SPAU changes can be recorded in development system to change requests. which can be
included in the upgrade of other systems in the landscape.
TIPS
TABLE E070
SICK
SE06
RZ10
System name : Can be find from RZ10
Stms
Slicense (HW Key)
Host : willsysdell
User name : administrator
The standard objects should be corrected within 14days after an upgrade. After 14 days we need to
obtain SCCR Keys
Upgrade Process: We need to choose the strategy either downtime minimised or resource
minimised.
Downtime minimised provides high availability to the system which is going to upgrade.
ACCTIT
Large size tables
COEP
29-Jul-09
That is why support packages, Add-ons, CRT, Notes, DB Exports are OS/ DB independent.
In order to apply them to a specific database and O/S TP, R3TRANS should be capable of
communicate with DB Libraries and update database.
238
TP, R3TRANS should be compatible with DB specific libraries to connect to DB for import.
To read parameters from tp_domain_<SID>.pfl TP initializes R3TRANS and writes all the jobs in TRBAT
and TRJOB.
RDDIMPDP, RDDNEWPP jobs should be scheduled in client 000 using user DDIC (DDIC should not be
locked)
RDD* Jobs are scheduled in the background which reads content from TRBAT and TRJOB and import
into DB
*.data *.tsk.bak
T - Table
D - Data
P - Primary Key These all will be in the Task File
I - Index
View.
STR files are provided by SAP (We can create STR Files during the exports)
1. Structure
239
2. Splitter
3. DB Export with DB specific method
4. DB Export ... DB export method
The above two options are used to handle large databases to perform parallel export and import.
However DB export will be performed by option 3 only.
Experienced OS/ DB Consultants can trigger all the above at OS level using R/3 load.
DEVELOPMENT INFRASTRUCTURE DI
Domain
Data element
Tables SE11
Screens SE51
Menus SE41
240
Transaction SE91
30-Jul-09
1. ABAP development resides in the Database. No specific format for ABAP Programs.
Refer Table TADIR, TRDIR, DD02L, TFDIR.
6. ABAP development consists of the same program with different versions from developers. Data
Inconsistency (In BI, PI there is a locking system)
7. ABAP uses TP, R3Trans to move the objects from DB to OS specific and vice versa.
10. ABAP uses transport routes/ transport layers to transport the object.
JAVA
3. JAVA requires JRE, javac and java to save, compile and execute program
5. JAVA uses CMS and four system landscape (At least 3 system landscape)
CMS - Change management system
6. JAVA uses the entire system to differentiate customizing because JAVA does not have client
customization.
10. ABAP objects are defined in the custom name space 'Y' and 'Z'. JAVA objects are defined based on
product/ SWCV version (Software Component Version) that are defined in SLD.
1. It is an usage type provided by SAP to develop programs in-house for meeting the specific
requirement.
INSTALLATION
242
Select the usage type DI during the installation
POST INSTALLATION.
NWDI_CMSADM
NWDI_DEV
NWDI_ADM
These users are created during post installation to work on DI. users require certain roles to work on
CMS.
NWDI Administrator
JDI Administrator
NWDI Developer
JDI Developer
The DTR provides central file and folder based on storage of source code. Version histories and
concurrent work on resources. It enables effective team work among developers distributed over
different locations.
Each Individual system is a DEV System but development is not done in the DEV system. If any
changes required it will be sent back to individual systems which is considered as Development.
Domain ID DEV
Domain Name DEV
Domain Desc DEB
Ext Servers
Developer uses developer studio to develop the programs upon successful completion they will check
in the objects into \usr\sap\trans of domain. (Generally domain will be development). The objects are
checked into DEV system using the credentials that are provided in runtime systems.
Note:/ Mechanism: The Transport Mechanism performed by using SDM, HOST, PORT NUMBER 50018
& PWD.
TRACK
Track is used to define the path to move the objects. Track is mandatory to move the
objects. In ABAP engine the objects are assigned to development class and development class is
245
assigned to a transport layer and layer is assigned to a transport group and subsequently assign
the route to a system to define the landscape.
In JAVA
Note: This DI Configuration is only required when there is a need to develop the products, software
components and programs specific to industry requirements. As a new consultant we need to perform
the following.
Note: Even though DI is introduced for transporting the objects EP, XI, BI has their own transport
package, transport mechanism to transport the objects.
Eg. BI - STMS
EP - Transport of Packages (Export/ Import)
PI/XI - Export Objects and Import Objects
BI-JAVA - is deployed on portal so it uses transport of the packages.
Deploy service is provided in Visual Admin Tool to import the small objects.
31-Jul-09
Each database supports various languages depending upon the code page i.e. selected.
SAP components are installed on code page 1100 which supports English, German & Other
languages. It is not possible to access the system in Chinese, Japanese and Korean etc using the same
code page.
SAP from 2007 onwards implemented Unicode i.e. all the products will be released on Unicode only.
MDMP has various issues during upgrade and migration. There are around 3000 MDMP logon/
system_lang = EN
247
Unicode supports all the languages because if it is installed on double byte code depending upon the
language.
Zcsa/ system_language
Abap/buffersize
Big Endian stores the most significant byte in the smallest address.
SPUMG: It checks for all the tables that needs to be converted to Unicode. It runs for hours
3. Export the database using Non-Unicode kernel. While exporting select Unicode(Little Endian or Big
Endian)
4. Specify the parallel process at least to increase speed depending upon the available resources.
5. Install the system with option target system using Unicode kernel.
01-Aug-09
1. Too many applications like ERP, SCM, SRM, Mailbox, File Browser, Web browser
2. Too many GUI's (Outlook Client, SAP GUI, Web server GUI, IE etc.)
5. Less Productivity.
How to resolve?
Motivation of Portal
Portal provides a role based, user based, single point of access to all the applications.
Customers having applications like Microsoft, Exchange Server, Domino Server, Web Server, File
Server, Oracle Apps, Siebel, SAP ERP, CRM, XI, SRM etc.
Customer needs the people centric, role based single point of access, in the specific language to all
the applications.
Customer (SONY) should provide the feasibility to work from home for developers, technical
consultants, functional consultants and end users.
SAP Introduced Enterprise Portal to overcome the above issues. It provides the following.
1. People centric, web based, role based, language specific, single point of access to applications.
5. Single sign on is configured to communicate with all applications. However authorizations needs to
be maintained in the back end systems. SSO provides only authentication (Single Sign on)
6. SAP provides predefined content in the name of business packages which can be deployed by
using JSPM.
7. SAP provides development environment using visual composer which is a web based tool.
10. EP provides content management which is the part of Knowledge Management to access the
documents from various repositories.
11. EP provides rooms, chatting engine, quick poll, FAQ's, user forums, news, announcements' etc.
12. EP provides Interactive environment where logos, banners, screens and desktops can be
customized.
13. It provides personalization to select our own themes, fonts and colors etc.
14. It provides user friendly navigational features, history of navigation, favorites etc.
16. It resides on the proven JAVA Engine there by using all the features of JAVA.
17. Its License cost is around 1/5th of the ABAP license cost and cost depends upon negotiation.
ABAP engine user can use EP without any license.
250
INSTALLATION
Similar to JAVA Engine we need BI functionality is required over web then Include BI-JAVA usage type.
HARDWARE SIZING
Sizing is an activity that is calculated over web using sizing tool provided by SAP. It is used to
calculate the hardware resources that are required by the selected application based on number of
users.
ABAP Users
Assuming each PO high volume consumes 12 dialogue steps. User creates 8 POs per day.
But in general PO is created with 8 DS
96/8 = 12 PO's per day.
Dialogue steps
1. Logging in - One dialogue step
2. Issuing SU01 Tcode - One dialogue step
3. Selecting field - One dialogue step
2. Medium Users
Each DS = 40 *60*60/4800 = 30 Seconds
I.e. 120 PO's per day
251
3. High Users
Each DS = 40 * 60*60/ 14400 = 10 Seconds
360 PO's per day
JAVA SIZING
02-Aug-09
SIZING Tools
CPUS specific to Hardware, Vendor (Pentium, Cytrix, Celeron and ) each processor has their own unit.
SAP S is an understandable unit of hardware. Vendors to calculate the number of CPU's required.
800 SAP's are generated by I Series CPU (IBM) similarly DELL, HP, SUN has their own measurements
for CPU calculation.
252
Example.
Note: Consider the number of interfaces on the system (Job Scheduler, Mail Server, Paging, SMS, BIW,
CRM, XI, SRM and SCM) (Memory required at CPU Level)
In Principle add 30-40% more the net calculation while calculating sizing for portal
Note: The purpose of JAVA standalone - It is a platform and we need to have an application installed
on it.
1. It does not have any specific steps in NWA like BI, PI, MI and SLD.
2. EP is an application that resides in JAVA Engine. EP consists of portal, Knowledge Management and
Collaboration.
3. EP by default cannot contain any business transactions. The business packages need to be
deployed to communicate with backend systems.
5. UME provides portal roles to access the EP content. There is no single role which provide access to
the entire content.
6. The deployed business packages contains roles, webdynpro connections which needs to be
configured.
7. The collaboration and KM features are available which needs activation/ enablement for access.
03-Aug-09
Portal logs
(Config tool, VA tool, Telnet tool, SDM, JSPM, NWA Tool for monitoring, Visual composer for
development etc.)
Portal Security
Portal roles are available to access the portal content.
Memory Usage
Memory concept is as same as JAVA stack.
Portal utilizes the J2EE engine runtime along with deployed portal applications (BI, KM, Content
Management, Collaboration, Visual Composer, RTC Real time Collaboration, EP, EPCore.)
http://<hostname>:50000/irj (integrated run time java)
SAP provides default desktop for the portal which can be customized.
The portal desktop elements are the following
1. Header Area
2. Content Area
3. Navigational Elements
1. Header Area
a) Mast Head
255
It is the first strip on the page. It contains salutation, banner, home, logoff, personalize and SAP
logo.
LOGO, salutation can be customized. We can change banner and logo. Personalization is only
available when EU_ROLE is assigned.
b) Tool Area
It is the second strip on the page. It contains collaboration, search and advanced search collaboration
need to be enabled.
Eg: Home ----- Third strip contains company, work, team documents and portal information on the
fourth strip.
The fifth strip on the page and it contains page title, history of pages navigated and flexibility to move
forward and back. It provides an option to save the screen as favorite.
2. Content Area
It is used to display the content and it will be around 2/3 of the page.
3. Navigational Elements
It is used to provide various navigational elements. They resides on the LHS to the page. Save
favorites detailed navigation.
PORTAL DESKTOP
It is default desktop that is provided by SAP. SAP provides various themes to customize the desktops.
SAP also provides theme editor to create and edit the themes.
Goto Theme Editor and select a theme , save it as a new theme and customize accordingly.
PORTAL ACTIVITIES
Enabling various functionality of portal like (Personalization, collaboration, RTC, content management
etc)
Working with user management (LDAP, ABAP engine)
Installation and Post Installation Activities/
------
Install Portal
Apply patches......... 18 patch
Deploy ESS, MSS and XMII
Customize portal.
------
TASKS
257
List down the JAVA Activities
List down the SOLMAN Activities
What is the purpose of DI?
Explain the process of upgrade (326) include prepare
Explain HW sizing
Explain the functionality of Market place with respect to customer environment.
Motivation for portal.
04-Aug-09
MDM:
SAP introduced MySAPBusiness suite 7.0 (SCM7.0, SRM7.0, ECC6.0, SR3 EHP4, CRM7.0) All these
components need to be maintained customer, vendor, supplier, material master records in various
systems and synchronization is becoming difficult. SAP provides MDM where the synchronization
starts from MDM to all the systems i.e. one Master data for all the systems
Note: Web dispatcher identifies the least loaded ICM when going for BSP
258
Note:
Refer ST07
User Groups
Roles
Tcode: SUGR
---------------------------------
05-Aug-09
259
ENTERPRISE PORTAL PERSONALIZATION
It is used to setup the portal desktop along with specified language, Fonts, themes and
manage personal data. Every user needs EU_ROLE (Standard End user role) which can be customized
according to the requirements. Add the role to the end user group and assign the group to every
user.
Due to the performance issue on the web the personalization is restricted to change the
password and contact info only.
User Profile: It is used to change the general information like email-id, contact info, address and
organizational elements. On a standalone JAVA change password is also provided.
User Mapping: (Remote Iviews) While accessing the data remote systems specify the userid
authorized in the backend systems. Eg: Users uses standard HR user to get the HR related information
from the back end.
Work Protect Mode: This option is used to set the work protect mode i.e. when a user partially
entered data in the screen while navigating away from that screen it should prompt whether to save
changes or open up a new window or discard the changes or save the data.
Http://<hostname>:50000/irj
Home
> Documents
Collaboration is used to provide various options to communicate with employees, Instant messages,
sending email, create tasks, assign the tasks, monitor the tasks etc.
06-Aug-09
DEFINING SYSTEM
System Definition
- Open the object for describing the backend details and specify
application host [Willerpdev]
gateway host [ ]
gateway services [ ] sapgw00
SAP Client
Client 800
Port 3200
System type SAP_R3 Save.
1. SAP_R3
2. SAP_BW
3. SAP_CRM
System aliases is a name that will be used while defining the portal content objects. Aliases is a
pointer to the backend system.
When the content is defined like ESS and MSS they will use alias name which intern points to the real
system. The real system will be customer system. The alias name will be unique through out the
landscape.
262
Defining the portal Content
Portal content provides the data that needs to be displayed over the portal.
Portal content contains the following iviews, pages, layouts, worksets and roles
PCD is the portal content database which are in the directory structure i.e. portal content directory.
Browse
> Select Folder
> Rt Click
>Create > New Iview.
IVIEW: It provides an internet view to the content. It is displayed in the content area. Iview can be SAP
transaction, webgui, url etc.
Iviews are pointed to an alias > Rt click the Iviews and preview.
Iviews are created as an copy or as an delta link.
Iviews are defined from a portal template when we copy from an iview it is completely copied
pointing to the template.
The properties are inherited from the Master template only, not from the copied iview.
Using delta link the properties are inherited from linked iview and master (template) iview.
----
Portal + ERP ESS, MSS configuration
----
07-Aug-09
Enterprise port contains predefined content that is available through PCD. (Portal Content Database/
Directory).
There are locate name prefix which is displayed in Quick Info. SAP also recommends to use the
predefined prefix to identify the objects uniquely.
Goto > Content Admin > Portal Content > Select the folder and create the respective content.
* Portal provides user based, role based and secure interactive content.
1. Create System
2. Provide an user mapping ID in user admin to access the content without userid and password.
Goto User Admin Tab > Identity Management > Add Identity
Search name: ABAP J2ee_Admin
Hit modify
Goto User Mapping for system access > System : Your Back End System Eg: NW6
Userid : Superuser
Passwd: Admin123
Note: When you copy the system to the FOLDER the alias will not be copied. so you need to create
alias one again.
Now Goto > System Administrator > Support > Sap Application > Select type >
Transaction > RUN
Now Goto your Folder > select RC > IVIEW > (.) Transaction Iview > Next > Select the system [ALIAS]
> FINISH > select the iview and preview.
PAGE : Select the Folder > RC > page > give the details > Next
(.) Default page > Next > light : 2 Columns > ADD > T-Layout > Next > Finish.
Select the Iview > RC > Add to page.
BP Best Practices provide predefined content, documentation, roles, users to implement in the
landscape with high productivity.
After Import > Goto Content Administration > Portal Content > Content provided by SAP > Specialist
> Here you will find all the roles and iviews.
Now Goto > User Administration > Identity Management > Select the user J2EE_ADMIN > modify >
Assign role called Finance Manager select Finance manager ADD similarly add material manager.
Now Goto > System Configuration > System Landscape > Assign the alias name as SAP_R3_BP >
SAVE.
Now Goto > Identity Management > Find out the user J2EE_Admin > Goto > User Mapping for
source system tab > Give the mapping users & password > Mapping user id sapuser -- Back end
system user and Password.
08-Aug-09
Questions PORTAL
A. Portal lies in JAVA Engine where as ERP lies on ABAP engine. To use portal we need only internet
explorer where as for ERP we need SAP GUI.
34. How do you monitor the portal? What are the various tools available?
35. How documents are stored in Portal? How do you create documents?
36. How do you work with Quick Poll, Favorites, Forums, News, Rooms?
37. What is Visual Composer? Adobe SVG Viewer?
Workset: It is used to display an activity. It can contain iviews, pages and a workset.
Role: It is a synonym of a position. It can contain iview, page, workset and role.
Roles are assigned to users and groups. All the above can be assigned as a copy or as a Delta link. It is
recommended to use delta link because inheritance from parent to child exists in Delta link.
Import and Export: The developed content can be exported to global directory to transport to other
systems.
SAP Provides transport of packages option to include the content in the package and transport.
Client : Path
Server
The extension is *.epa (Enterprise Portal Archives)
Permissions Editor : Used to assign the permissions to the content. Allows us to set authorization
permissions on portal objects, components and services to portal users, groups or roles.
09-Aug-09
267
SDM - SOFTWARE DEPLOYMENT MANAGER
It is used to deploy the patches up to version NW7.0. It is discontinued from Version 7.10
Note: NW7.0/ NW640 becomes NW7.10 when is it upgraded where as it comes 7.01, 7.02, 7.03, 7.04
(EHP1, EHP2, 3, 4) when EHP is applied.
- SDM uses port 50018 and password to deploy the packages. SDM is also used for undeployment
which is a great disadvantage/ because of dependencies may not work.
Used to deploy the patches/ support packages, support stacks and business packages.
JSPM reads from EPS\IN where as SDM needs to be feeded with the path
ESR - Enterprise services repository.
4 associated patches.
We need to import the package and define the JCO connections, user mapping or Single sign on etc.
Application Path
Connection should be created using dedicated application server.
Refer to ESS/ MSS documentation and create systems and aliases accordingly.
Define the permissions for the deployed content. Predefined roles are available only we need to set
the permissions (Role owner, End user etc)
Assign the roles to users and ensure that the respective tabs are displayed.
SINGLE SIGN ON
The portal is role based, user based, people centric, language specific, personalized, web based
interface to the users.
Single sign on provides an access to all the back end systems without any password.
SSSO cannot provide Authorizations, it provides only authentication.
6. The login ticket does not contain passwords. It contains userid, authentication
scheme, date of expiry, digital signature, information about the issuing system.
CONFIGURING SSO
EP to BW
1. STRUSTSS02
In order to setup SSO, we need to setup single sign on parameters from RZ10.
7. Execute RSPOSRT.
1. System User - To transfer the data or client copy with in the system or local clients in the system
2. Communication User: To transfer the data from one system to another system. like RFC users.
3. Reference Users - To Provide additional rights to the user. SU01 - Under Role tab. When the user is
absent the reference of the other user will take care.
4. Service User: Is also called as reporting user. PWD doesn't expires, login is possible. Production
target/ bonus.
5. Dialogue User.
10-Aug-09
Regarding Permissions> System Administration > Employee Self Permissions > Permissions
Content --------- Directly to behave as owner, end user, role assigner, read only.
Content Assignment to group ------ users ---- to behave as owner, end user, role assigner, read only.
Content -------- Roles ---- Users ----- to behave as owner, end user, role assigner, read only.
Note: Even though roles are defined on portal they are used to only to control the access to tabs.
11-Aug-09
NO CLASS
12-Aug-09
Note:
13-Aug-09
COLLABORATION
It is available by default when the portal is installed. Collaboration brings the integration
between people and provides all the features which are available with yahoo, Google etc.
Teams: It is used to collaborate between group of people. We need to configure rooms before we
work with teans.
Give the description and details > Hit Next > Add User > Finish.
Now click on Enter Room
http://<hostname>:50000/irj
Content Management - Quick Poll Administration.
SAP provides entry points to store and access the documents. It provides 6 entries.
1. Favorites: It is used to store the accessed in links/ documents and provide navigation in one step.
2. Common Folders: It is used by a team or group to store the documents between them.
3. Personal Documents: We can store our personal documents and can display from any part of the
world provided access to portal is available.
4. Recently used: It provides the list of documents that are recently accessed.
5. Taxonomies: It is used to organize the date in categories. The information is fetched and organized
by topic.
Eg: Science/ Physics, chemistry, biology. If you click on physics you need to get statics and dynamics.
Note: All collaborative activities using system administration > System Configuration > Collaboration
in RHS and click on group ware transport. Group ware transport are used to configure the Microsoft
exchange server, Lotus domino server or any other mail servers.
Click on NEW > Provide the user logon domain.
274
14-Aug-09
It can be enterprise portal archive or webdynpros. Webdynpros mainly transported using JDI. (Use
transport studio to transport objects or SDM to deploy them manually)
User management (End user requests from suppliers, vendors, employees, customers and business
process owners)
- Password rest, User creation, Role Assignment(in portal and backend system), user mapping,
defining roles based on content, assigning to a group and group assignment to users.
Eg: A company with 30,000 portal users will be maintained by using user groups. (like SD group, MM
group etc)
Understanding the user and security mechanism.
- Users are created in ADS (Active Directory Server) ---> Populate
SPAM is for ABAP and JSPM is for JAVA. JSPM is cumulative/ growing and SPAM is incremental. JSPM
we can jump from 6 to 9 Directly where as in SPAM we need to follow sequence.
Portal ---- Assign Portal Roles ---- User Mapping --- ensure backend system mapper user (Service
User) has relevant authorizations.
Customization, Content Manager role to change the NEWS, FAQS, QUICK POLLS etc.
Portal Thread Weaver is a monitoring toll. We can download from Market place and apply.
Modifying the system IP Address (Host Name) in systems if required --- Rare Job (Sys Admin -----
System Config)
Apply support packages/ business packages etc. using JSPM and update Kernel.
275
Monitoring content overviews - It is used to display the components that are accessed.
System Administration - Monitoring - Content Overview
Identify the component which consumes more gross time, CPU time and No. of Calls etc.
Each component should not consume more than 2 Seconds on all average.
Component, Request, User uses only CPU and Memory of the portal to get the content displayed. It
contains time because the database engine is a backend system.
CPU time more than 40 to 60% of the response time then consider CPU is expensive. i.e. it is running
expensive Iviews (Embedded Iviews).
Request summary is used to identify the CPU time, Average response time, total number of calls....
If the calls are more and response time is high we may consider deploying of a proxy server.
1------- 10000
2 ------ 2000
3 ------ 2000 As the calls are more Response time will come down
4 ------ 1000
5 ------ 200
6 ------ 200
Request overview provides the user and component accessed along with CPU time and duration. We
can display the content based on search criteria like duration., Userid etc. It is used to identify the
expensive users at that point of time.
15-Aug-09
Versions
3.0
3.1
3.1C are the Basis versions .... BIW
From WEBAS 640 it is by default available with the Platform i.e. When ABAP is installed (SAP-ABAP,
SAP_BASIS, SAP_BW) comes by default.
SAP Provides BI_CONT (BI Content) which contains predefined info cubes, Roles etc.(In Netweaver 7.0
It became a part of architecture with Information Integration)
Motivation
1. Analytical Reports
2. Decision Making System
3. Graphical Representation with help of BO (Business Objects), Bar Charts, Pie diagrams, Line Charts
and graphical representation , Dash Boards etc.
4. Web Broadcasting
5. Business Cockpit (In BI7) New
6. Archiving system (Date from legacy systems is achieved into BI Systems.
7. Reporting system to run the heavy background jobs. Eg. ECC/ ERP system is consuming more time
to run the background jobs. So, BI is used to run those reports with out effecting the performance.
8. Compare the date that is available in market DUN & BRAND street to define the competitive
reports.
7.03 (Deploy atleast 703 because upto 702 are out of maintenance) current is 710.
BI Communicates with various backend systems (ERP, Flat files (*.txt, *.csv, *.xls, CRM etc) and fetch
the data into FACT and Dimension Tables.
These tables are used to define various reports as per customer requirements.
The report fetches data from various data sources so more memory and more BTC work process are
required.
Front end can be BEX or an Enterprise portal, Crystal reports, XCelsius can also be used to fetch the
reports from BI system.
Installation of BI System
7. Define logical system to client (BI uses ALE Mechanism to transfer data from ERP to BI) so the
communication happens between logical systems only.
8. Establish connection between ERP and BI system
278
16-Aug-09
17-Aug-09
DOWNLOAD BI CONTENT
www.service.sap.com/ SWDC
- downloads
- sap software distribution center
- downloads
- Installation & Upgrade
- My SAP Application Components
- BI Content 7.03 around 500 MB
Select download - Add to download basket & Download BIADMIN also from the Market place. With
this we can admin BI System through Portal.
BI ADMIN is a business package provided by SAP
Select business package -> Next > SAP BI/ ADMIN (next) - Deploy will be finished.
Once deployed goto > /irj > User Administration > Identity Management > Find the user > Modify >
Assign roles > Search for "BI Administrator" role > Add > SAVE.
Now Under system administration > Monitoring > you will find Business Intelligence
. RZ20
. ST03
279
RSC_COl is a background job runs to pump the date to ST03
MONI is the table from here the data will be read by the above Job.
Download the BP[BI ADMINA] from Market place copy it to \usr\sap\trans\eps\in directory
Use JSPM to deploy the Business Package [BI ADMIN]
BI ADMIN COCKPIT
Navigation
Note: Don't change logical systems name once they are assigned to client. Instead use BDLS to
change the logical system.
Note: Logical system names are required to change only during system copy.
The above figure shows it is a system copy in the landscape. After performing system copy in the
landscape we need to change the logical system name. To perform this we need to go with BDLS and
change LSN
RSPOR_SETUP (SA38) is a report specify the steps that needs to be followed to integrate BI with JAVA
Engine. You cal do it by using NWA , /nwa
RSPOR_SETUP (SA38)
SPRO in BI System
Or manually in BI System.
18-Aug-09
BI SECURITY
BI Security is similar to R/3 Security which consists of SU20, SU21, SU22, SU25 with authorization field,
activities, authorization objects, authorization classes, authorization profiles, composite profiles,
menus, favorites, user assignments, user comparison, roles, composite roles etc.
The area that differs is to protect the info objects at field level. SAP Provides around 20 authorization
objects which are required for reporting administration.
Solution Manager is a CRM System, BI System & Solution Manager System. If you install Solman we
will get all the above components.
From BW3.5 i.e. Netweaver onwards the above transaction is obsolete. Now it is RSECADMIN.
- In BW3.0 the RSSM, RSSMTRACE, RSSMQ has been moved to RSECADMIN in Netweaver 7.0
Eg: To Create custom authorization object we use SU21 in R/3 where as in BW(BI) we use
RSECADMIN.
282
In order to protect the reports at object and field level we need to make them authorization
relevant in RSA1 where as SU20 in R/3. PFCG will defaultly we need to use.
In RSA1 - Transport Connection - Select the grouping , objects - Select the object click on Truck BEX
we can transport in this way. We have another button Object Changeability with this we can give the
object as a edit compatibility.
Goto RSA1 - Info Object - Select Info Objects - RC - Change - Goto Business explorer tab -
Authorization Check relevant.
Note: Every user will have the default tcodes (SU53, SU56, SP01, SU3). We need to provide this to
every user.
Now Goto > PFCG -- Define Role -- Include Authorization object manually or
- We can also include authorization object in a Transaction SU24.
- Save and generate the profile in PFCG and assign the role to the user.
- Perform user comparison
Goto PFCG - Create Zrole - Goto Authorization Table - Click on change authorization tab -> X - In the
next screen - Add manually - give the object which is authorization relevant - Assign the user - do the
user comparison.
TRANSPORTATION OF OBJECTS
In RSA1 define the objects -- - Collect them in package and transport -- Use Object Changeability tab
in RSA1 to ensure that the object can be modified in PRD system.
19-Aug-09
SYSTEM COPY (FOR BI SYSTEM)
4. Restore the database from backup /or physical copy of the datafiles (SAPDATA1, SAPDATA2..............)
6. Remove the entries before "startup nomount" and after "Characteristics WE8DEC'
Run Control file on the target system
Mechanism:
1. User i.e. work process connects to the database as user "OPS$<Hostname>\SIDADM to get
SAPSR3's password.
2. SAPSR3 is the schema user whose password stores in table SAPUSER which is owned by
OPS$<hostname>\SIDADM
Note: OPS$ mechanism provides a means to connect to the database without any password i.e. user
with prefix OPS$. The OS user is created in the database with prefix OPS$(OS Username).
Remote_OS_Authenticate = True
SAP recommends to change the schema user password using BRTOOLS/ SAPDBA.
If it is manual we need to change in two tables.
SQL> Insert into table 'OPS$<hostname>/SIDADM'.SAPUSER values
SQL> Alter user SAPSR3 identified by "New password"
When you insert password it is alphanumeric(It will be in the encrypted format after restart)
Question:
We have 300 user and every month their password needs to be changed.
Or
You have different users with different roles and profiles. How can you achieve this? This will be
achieved from SECATT Tcode.
Click on Execute F3
In the main screen >> In the toll bar.
Now go to change mode > click on Pattern
www.erpgenic.com/ecatt
-------------------
SM35
Create new recording - Give tcode SU01 - give the record name. SAVE
Goto that particular SU01. Change - Change password - Save.
Now goto SM35 you will find all the activities on SU01. Export that data as excel sheet. Change the
password & username and ...
-------------------
POST ACTIVITIES
2. Alternatively you can set rdisp/ wp_no_btc=0 before you start the system or set the time to
rdisp/btctime = 0 (Don't worry as SICK results in error)
Backup need to take USR02, RFCDES, SLICENSE, DBLS (Used to change logical system names) Client
information, STMS configuration, system specific programs, reports transactions.
Pre-Activities
20-Aug-09
BI MONITORING
BI uses batch processes to execute the reports, queries, etc. which consumes more time and
resources.
Technically batch process uses heap memory, extended and roll memory sequentially where as
dialogue uses roll memory, extended and heap memory. If the memory is not sufficient in both the
cases the process gets terminated or hangs up.
Response time depends upon the data to be fetched, query being used, or the duration of the report.
(From Date - To Date)
Released: When the execution time is specified for a defined job then its status is released to execute
at a point of time.
Ready: When the specified time elapses then the status will be ready.
Process Flow
TCodes
RSPC Variant
RSPC Process Log
Note: Each BI System has its own process before you start working ensure that you are well aware of
the process of DTP, Source System, Process Owner, Critical Jobs and their priority and escalation
levels.
Capacity Planning:
DB02--------- Space Analysis------- Identify top 50 table and record them every week to identify the
growth of the table. (It is also used to identify the accidental data growth)
22-Aug-09
RFC: Remote function call (SM59) it is used to call the other system using the gateway to fetch or
send the information.
1. ARFC
2. SRFC
3. TRFC
4. QRFC
ARFC : Asynchronous RFC: It is used to communicate between two systems but the source system
process may not get the acknowledge from the Target. Some times the data may be lost in transition.
The source system process does not bother whether the information is received by the target system.
It is similar to a post card. It is not reliable and consistent.
SRFC: Synchronous RFC: It is used to communicate with receiving system and wait for
acknowledgement. If the acknowledgement is delayed it will go into RFC/ Sleep/ CPIC Mode.
It is reliable but the resource gets blocked at the target system. If the target system is not
available (Example BTC Process waiting too long in the active state)
TRFC: Transactional RFC : It is an advanced version of ARFC. It is used to communicate with receiving
system and if the system is not available it will generate a Transaction ID in SM58. and a background
job RSARFCSE runs for every 60 Seconds. It is reliable, gets the acknowledgement and data
transmission is consistent.
Parent client creates users and send it to child clients. If child client is not available it creates a
transaction ID in SM58 and ensures delivery when the child client is available.
QRFC: Queued RFC: It is an advanced version of TRFC to ensure the jobs are processed in a queue. To
execute QRFC we have a job called QUIN Scheduler
- We have SMQ1 (Outbound), SMQ2 , SMQR - Quin Schedulers
QRFC generates the process of LUW's in the sequence. When the sequence is mandatory in the data
transmission QRFC is recommended. SAP Implemented all the above services to ensure the quality in
the data transmission. SAP named it as QoS (Quality of Service). SAP consider SRFC, TRFC and QRFC.
1. SRFC --- BE (Best of Efforts) - With best of efforts it will deliver to Target system. When you find BE
it is SRFC. Majorly we are going to use in BI and XI Systems.
ALE: (Application Link Enabling): It is used to transfer two loosely coupled systems (SAP to SAP
systems) Eg. BW to CRM; ERP to ERP etc. SALE/ BD64/ BD54 it is used to define the logical systems
and sending/ receiving systems. Each system that participates in the data transmission is identified by
it's logical system name i.e. SIDCLNTCLIENTNO.
And is recommended to define the RFC's using logical system name to uniquely identify in the
landscape.
1. Define the distribution model (In Sale TCode) in BD64 (Change) - Create Model View - Give the tech
name - Continue.
289
2. API's Application Programming Interface: It is an interface in BD64 select the model click on
ADD API defined based on your application either to send or receive data based on the business it is
called as BAPI. (Business API's). The BAPI will be assigned between the sending and receiving system
EDI: Electronic Data Interchange: It is used to transfer the data between SAP to Non-SAP systems and
vice versa.
In order to monitor the EDI used TCODE WE05
IDOC: Intermediate Document: It is in the understandable format of both sender and the receiver.
Non SAP systems could communicate directly with SAP systems. They required adapters (File Adapter,
J2EE Adapter, IDOC Adapter, HTTP Adapter etc)
When the supply chain market is growing the necessity of 'E-Commerce' Electronic business EB's) is
gaining importance and the vendors, suppliers wants the documents flow electronically with out any
paper In order to monitor multiple senders and recipients it will be difficult to use SAP Standard
transactions, SAP standard systems and mechanisms.
It is used to communicate between SAP to NON-SAP and vice versa. It communicates with both
sending systems and receiving systems via Intelligent Broker.
XI Communicates with out Adapter for the versions based on WEBAS 640 and above i.e. 4.6c is
involved then it requires an adapter.
SLD : http://<hostname>:50000/SLD
290
- SLD is to define technical system (Hostname) & Business system (Client) that are going to participate
in Integration .
- It is used to define the roles of business systems in the XI domain.
- It is used to define the XI Domain
- Architectural components need to be defined.
23-Aug-09
- XI/PI is an Intelligent broker to communicate with systems using adapter with RFC Mechanism......
(BE, EO and EOIO)
- XI/PI has not penetrated into market because ALE, EDI, IDOC, file transfer, Batch inputs, BDC (Batch
data transfer communication) are in place. To replace them we need a new server i.e. landscape (DEV,
QAS, PRD) environment which is expensive and technology required.. Where as companies are
habituated to use TIBCO, ROSETTANET etc.
XI Architecture:
- Integration Builder is used to build the objects that are required for Integration (Source and
receiving system). It contains two areas IR and ID.
- IR is often referred as Design Time (Integration Repository) which is used to create and design the
integration objects.
NOTE: XI/PI license is based on date transfer like size -- 2GB, 5GB, 10 GB.
XI Uses global format (XML Format) Extensible Markup language with the help of SOAP (Simple object
access protocol). XML is an industry standard which is in the understandable format (Using meta data
(Data about data)) It uses its own tags <address>, <price>, <customer>, <shannu><willsys>
- ID (Integration Directory) is referred as config time (Integration directory) which is used to configure
the run time objects (Sender, Receiver, Interface, Agreements).
- To avoid complex developments SAP Provides predefined XI-Content which can be deployed using
Integration Repository. The content provided will be in ZIP format which contains ".TPZ" Extension.
292
Note:
1. How did you deploy XI-Content? Through IR.
2. Architecture of XI?
3. How did you apply patches? Through JSPM
4. How did you transport the objects.
Extensions:
Tools
Usr\sap\sid\dvebmgs00\j2ee\admin\go.bat
On UNIX ./go
(JAVA parameter need to set like environment variable)
Config Tool.
Usr\sap\sid\dvebmgs00\j2ee\configtool\configtool.bat
SDM
Usr\sap\sid\dvebmgs00\SMD\remotegui.bat
JSPM
Usr\sap\sid\dvebmgs00\j2ee\jspm\go.bat
NWA
http://<hostname>:50000/NWA
SLD
http://<hostname>:50000/SLD
Questions IMP
EP Url's
IR http://<hostname>:50000/irj
Useradmin: http://<hostname>:50000/user admin
J2EE engine: http://<hostname>:50000
XI Url's
In order to ensure SOD (Separation of Duty) XI creates users during installation only.
(In the above user names take out PI and use the AF, DIR, REP etc for user name analysis)
294
Note: All the system that need to participate in the integration must be registered in SLD along
with software component version and products.
If the participating system is ABAP a technical system pointed to business system is mandatory.
24-Aug-09
PCK: Partner connectivity kit. This can be installed at partner landscape. This is used to communicate
with XI/PI to transfer data to SAP systems.
XI Installation
640 - XI3.0
Install ABAP Instance (Central and Database Instance)
Create a client and perform ABAP - Post Installation Activities
Install JAVA as an add-on on that client
Install XI_Content
Install Adapter Engine
PI 7.0
In PI7.0 all the above can be selected during the selection of usage type.
- Select ABAP, JAVA and process integration..
XI requires both ABAP and JAVA components.
XI Landscape
Production Landscape
295
2. You can use NWA Tool to perform the post-installation activities automatically.
Note: In PI 7.1 it is recommended to use NWA tool only (like creation of Users (SUSERS), generation of
roles and profiles and assignment of roles to users.
Earlier these activities are performed during installation, now moved as a part of post installation
activities.
25-Aug-09
1. MANUAL PROCESS.
1. Check all the services are running from Visual admin tool.
296
Com.sap.aii
Com.sap.lcr
Com.sap.rprof.remoteprofile
Com.sap.xi
8. Assign application role to user group in SLD data Supplier service click on user group icon.
9. Configure ABAP system to SLD using transaction. RZ70 with the help of RFC "SLD_UC"
10. Use SLD data supplier service to populate information of JAVA engine to SLD
Note: 9 & 10 are mandatory for all systems that are going to participate in the integration.
11. Define a technical system in SLD & assign the product and software component.
12. Define a business system i.e. a technical system with specific client.
13. Define the role of a system in SLD.. Application system integration server.
Note: There will be only one integration server in the XI Domain that is used to process the messages,
Senders & Receivers are configured as Application System.
- Define RFC type "H" INTEGRATOIN_DIRECTORY_HMI to refresh the service in J2EE Engine.
AI_DIRECTORY_JCOSERVER: Points form integration server to the integration builder. The Program ID
corresponds to the entry under for the J2EE Engine (Used to refresh the runtime cache)
14. Create RFC connection of type "H" for PMIStore (Process Monitoring Infrastructure)
- Use the URL: http://<hostname>:8000/sap/bc/spi_gate
With user PIRWBUSER & password
- It is used to populate the monitoring into ABAP Engine.
- We can use ABAP/WEB to display the end to end monitoring of a message.
297
15. Configuring Integration Server on ABAP Engine
- In principle XI Domain is defined in SLD & associated.
- Integration server & application systems are defined in SLD itself
- Each system is registered in the SLD, but ABAP engine process the messages flow between them
using Integration Server.
- So each system that needs to participate in the integration define itself with a system role.
- Execute transaction SXMB_ADM (Integration Engine Administration)
Each ABAP engine is a Integration Engine. If the integration engine is configured as an
Integration Server then it is called as XI Engine & other are called as Application system (Senders or
Receivers)
17. Triggering the self registration of Adapter Engine Deploy comsap.aii.af.cp .cpp to trigger SAL self
registration.
Development.
Maintenance certificate is mandatory for all the patches in NW04S SR3 form January 2009 onwards..
Maintenance certificate locks SPAM & is valid for 3 Months.
XI/ PI should be updated (kernel, Patches), SLD, CIM should be updated before any other system in
the landscape.
26-Aug-09
INTEGRATION REPOSITORY
1. Import XI Content
2. Export XI Content
3. Import the system landscape (Products & Software components) into Integration Repository.
4. Define the uniform resource name
5. Clear the cache if required for SLD
Note: IR requires JAVA webstart which is around 30MB on each XI Consultant desktop.
INTEGRATION DIRECTORY
Business System
299
The system that is defined in SLD (assigned with client no. to a technical system). Party in a
company customer.
When the data is not updated in the messages during runtime. Then we will go to ID to clear SLD.
Category : Parameters
Monitor : PM2_Monitoring
Tuning : EO_
It is used to trace based on users, client & condition also set for tracing.
Create specify condition
Username : DDIC
Action: Trace level.
Argument: 3
Display pipeline definition. It is used to process the message from Sender to the receiver. There are 6
Pipeline (Central, Central_back, Sender, Sender_back, receiver, receiver_back)
The message is sent by a sender using by calling a outbound interface (Sending System). It uses
pipeline call integration server.
The message is received in IE or Server by using Inbound with logical routing & the message is
processed through the outbound processing using LTM.
The message is received by the inbound proxy of the receiving engine & it acknowledges back to the
integration server.
27-Aug-09
http://<hostname>:8000/sap/xi/engine
RUNTIME WORKBENCH
301
It is used to monitor the XML messages from one end to another end. It provides the following
monitoring elements.
1. Message Monitoring
2. Component Monitoring
3. End to End Monitoring
Integration repository.
Integration directory
Runtime Wrokbench
SLD
Integration Server
XSMB_ADM
Message Monitoring:
It is used to monitor the XML message use transaction SXMB_MON1/
SXI_MONITOR to monitor the message or the web option (rwb0 to monitor the message.
Messages can be filtered based on status, data and time, sender, receiver. The status determines
whether the message can be processed or not. It specifies where the message is stuck in the error
category. On day-day basis we need to identify the messages that are not processed and escalated to
the respective trans.
Message Flow:
1. Sender sends the message to integration server, this should be displayed in the message
monitoring.
2. The message is received in the inbox of the integration server. which will be displayed in the
message monitoring
3. The message is processed with receiver determination to identify the receiver who is configured in
the integration directory. (Register in the SLD)
302
4. Interface determination
Interface has to be determined so that the message will be pick by that API.
5. Mapping: The sending message data structure should map with the receiving message data
structure. There are mapping failures (in IR).
6. Technical Routing: This is where the exact business system of a sender and receiver is identified.
7. Call Adapter: If required central, adapter engine is called (CAE). It consists of various adapters (File
Adapter, J2EE, J2SE, HTTP, SOAP, RINF, ROSSATANET), If third party adapter like Tipco is used, PI
supports it.
TOO_MANY_RECEIVE_CASE_BE
There should be only one receiver in a synchronous message. i.e. too many receivers are not allowed
in BE SYNC (Synchronous) i.e. It is possible to define more than one receiver E010/ E0
Technical routing fails with message outbound binding not found. If receiver agreement not found
than this error occurs. Check and refresh the cache using SXI_CACHE or check the configuration in the
Integration Directory.
Mapping Errors
RFC ERRORS
Check the RFC connectivity, Userid and Password, Gateway.
QUEUE MONITORING
SMQ1, SMQ2, monitor the status of queues, if the error is like SYS_FAIL - Full disk or database errors.
ICM - Connection Exceeded (Increase the ICM Threads/ Soft shut down RZ10)
ICM/ Min - Thread
Adapter Problems
303
Check the adaptors and connection between IS, Receiver and sender.
IDOCS: If the messages are still processed using IDOCs use SM58, WE05, WE21/ To check IDOCS.
IDEX5 is used to identify the XML Messages (IDOCS) in the adapter. We also need to refresh adapter
cache in SXI_CACHE into adapter engine cache.
Technical Components
An SAP system consists of several application server instances, as well as one or more databases.
In addition to multiple dialog instances that execute user requests, there is a special instance that
contains the message server and the enqueue server - the SCS (System Central Services) for the AS
Java, the ASCS (ABAP System Central Services). It cannot process any dialog requests.
A dialog instance with AS ABAP and AS Java consists of the following components:
The Internet Communication Manager (ICM) sets up the connection to the Internet. It can process
both server and client Web requests. It supports HTTP, HTTPS und SMTP protocols for the AS ABAP. In
AS Java the ICM supports the HTTP(S), P4, IIOP and Telnet protocols. The SAP NW AS can act as a
Web server or a Web client.
Central services (message server and enqueue server) are used for lock administration, message
exchange, and load balancing in the SAP system.
AS ABAP components (in the graphic on the left):
The dispatcher distributes the requests to the work processes. If all the processes are occupied the
requests are stored in the dispatcher queue.
The work processes execute ABAP or Java programs.
The SAP Gateway provides the RFC interface between the SAP instances (within an SAP system and
beyond system boundaries).
AS Java components (in the graphic on the right):
The Server Processes execute Java requests.
The instance controller controls and monitors the life cycle of the AS Java instance.
More information:
Internet Communication Manager (ICM)
Work Process (BC-CST)
SAP Gateway
Java Cluster Architecture.
The graphic below shows the components of the SAP NetWeaver Application Server (in grey). To
retain clarity a few communication channels are not included in the graphic.
304
Upgrading
Integration
Develop * Customization
Basis Platform
305
Advantages of SAP
6. Netweaver
7. OS Independent
8. DB Independent
11. Continuous improvement by releasing Support Packs, Upgrades and Enhanced Patches
BASIS NETWEAVER
Basis Consultant
Netweaver
Security Consultant
Enterprise Portal Tech
Solution Manager
Basis: A foundation layer for all SAP systems and with out Basis there is no SAP System
B A S I S
SAPWEBAS SAPWEBAS
ABAP JAVA
Provides Business Functionality Interactive/ Dynamic, Multilanguage
WEBAS ITS
Basis Layer
NETWEAVER is a PIPA
Application Platform
People Integration
Information Integration
Process Integration
BASIS Netweaver
BI Security, XI Security
24/Jun/09
SAP R3 4.0B, 4.5B, 4.6B, 4.6D and so on ....
/usr/sap/<SID>/SYS/exe/runthe directory that holds a local copy of all SAP instance
executables, libraries and tools
Goto transaction sm51, and click (not double click) on the Database
server and then click on release notes. There you will see the SAP R/3
kernel and patch level etc.
310
Kernel or Shell :
The core that provides basic services for all other parts of the operating system.
or
KERNEL: The kernel is the part of the Operating System(OS) that interacts directly with the hardware
of computer through device drivers that are built into the kernel. It provides set of services that can
be used by programs insulating these programs from the underlying hardware.
4. To handle interrupts
5. To handle errors
6. To perform input and output services (which allows computers to interact with terminals storage
devices and printers) and
7. To allocate the resources of the computer (such as CPU and input/output devices) among users.
--
SAPMnt: Is a shared SAP Mount which is used to host the directories related to SAP.
(It may be required to create SAPMnt in earlier versions but in the current versions based on
Netweaver it is created automatically)
SAPLoc in Windows
This SAPmnt is shared because it needs to share the transports, support packages, profiles,
executables etc between systems in the landscape.
[Dev] ---------->[Qlty]---------->[Prod]
SAPmnt
311
Default Users
SAPSR3
SAPSR3DB
Earlier case Individual passwords need to be set but now day's only one Master password for all the
userids.
A host is either a client or a server. A host has its own address on the network, and is its own
machine.
A server has its own address and sometimes multiple addresses. It provides access to services and
information.
Interface / Screen
Exports/ System Copies
Kernel [ Dependent]
312
Install Mstr [ Dependent]
Java Comp [ Independent]
JRE [ Dependent]
Exports [ Independent of OS, DB]
R/3 Architecture
GUI
Mobile
IE
Debit Card ATM
* Commit occurs then only amount (Synchronous update) will be debited from the ATM.
Caching/ Buffers
Note: If one App server is down no need to worry we can access another application server. It process
data rather than carrying data.
App server doesn't contain any data on its own.
313
Sql Server - Transact SQL
Oracle - Pl/ SQL
Presentation Server:
Submits the user request
Application Server:
Process the user request by interpreting the request and it has a queuing
mechanism based on FIFO.
Frequently accessed/ rarely changed (Master Data)
Eg: Address, Company name.
Users always communicates in OPEN SQL which is SAP Specific format and not
dependable on any database.
Kernel
SAP
K
R
314
DB
OS
Usr\sap\sol\sys\exe\uc\NT1386
25/Jun/09
Installation Logs
C:\program files\sapinst_instdir\solman\system\ora\central\as
.tsk file specifies the table/ index etc that needs to be created on the DB.
Each task is commanded by .cmd file and during the process they writes into .log file
Eg: Sasapappl0.tsk.bck
Sapappl0.tsk
Sapappl0.cmd
Sapappl0.log
Sapappl0.str - Structure of the DB
Control.xml
Keydb.xml -Helps to restart installation from the point where it is failed.
2. Sapinst tool is used to install the software if required we need to download it from
service.sap.com/swdc
315
Note: The user who initiates the installation should have the privileges as Local administrator to install
the software, create users, create groups, assign groups, create services etc., (This problems occurs in
a Domain)
If the user does not exists it creates now.
On Windows OS <SID>ADM is also responsible for database but on UNIX ORA<SID> is the owner
to work on the database. ORA<SID> provides the runtime environment for Database.
Windows
App Server Database
<SID>ADM <SID>ADM
UNIX
5. It creates local groups and global groups and assigns them to users
316
SAP_LocalAdmin
SAP_SOL_GlobalAdmin From Computer Management -> Local
SAP_SOL_LocalAdmin Users and Computers we can view this
6. It creates Services
SAP<SID> is used to start the SAP System; if the service is not started SAP will not start.
SAPOSCOL is started first to check whether the resources are available (Operating system collector) It
is used to collect the OS Utilization information and pass into SAP system.
SAPCCMSR is an agent to collect JARM (Java Application response time Management) and pass it to
ABAP CCMS (Computing Center Monitoring System)
It is only used in JAVA and ABAP stack.
Users
Groups
Services
Creating directories
Executables
- OS Dependent
- DB Dependent
Note:
Query:
9. Now command files are created pointing to .str and data on the exports
10. The task files are created to create the tables and load the entries
The task files are displayed as process on the installation screen
"2 complete 3 running 4 waiting"
11. Upon running all the tasks the SAP Database is created and DBStatistics runs.
12. DB Users are set with default password and SAP Application open RFC Connection.
\USR directory is created with a shared folder SAP with shared SAPMNT & SAPLOC
These are shared between systems and accessed locally and globally
CCMS
318
PRFCLOG
PUT
SID HOSTS
Trans
CCMS - Used for alert logs that is populated by the service SAPCCMSR
(Java Stack Only)
26/Jun/09
TASKS
Solution Manager Connects all the three systems (ERP i.e, ECC6.0, Netweaver & CRM2007)
I. Installation Inputs
SAPInst
SID
319
Instance Number (Default 00, 01)
Mater Password
JCE Policy
Users,
groups,
Services,
Directories,
SharedMnt,
Kernel (Extraction),
CreateDB,
LoadDB,
Updated Stats,
RFC's
POST INSTALLATION
SAPLOCAL_ADMIN
SAPGLOBAL_ADMIN
ORA_SID_DBA
ORA-DBA
ORA_SID_OPERATOR
8. Check the USR Directory (SAP Instance files..... App) predefined shared SAP Directory with
SharedMnt, (SAPMnt), and SAPLoc on windows
Note: SID Specifies the Application Server and is possible to have multiple <SIDS> differed by the
instance number
Queries:
Note: In the console tree of SOLMAN if all the three entries (SERVICES, USERS and GROUPS) are
available then only we can confirm there are 3 Instances in one single system.
Config..... Usagetypes.properties - used to specify the usage types that are installed on the
system.
EP EP
BI BI
JAVA JAVA
ABAP ABAP
Enterprise Portal
322
Contains executables and profile parameters to start and stop the system
EXE Directory - hosts all the executables from netweaver exe dir contains
UC/ NUC and 32/64, i386/ ia64
--------------------
\USR\SOL\SYS\EXE\UC\NTI386\ strbs.cmd
START_DVEBMGS00_WILLSYS28
<Instance> <Host Name>
3. It starts the database and writes the logs into the work directory
Note:
Stderr1.log (Standard Error Log) ; sapstart.log
\USR\SAP\SOL\DVEBMGS00\WORK
Eg :
323
5. Starts the instance i.e., dialogue by using disp+work and writes into
Dev_disp, dev_w0, dev_w1.....
6. Starts internet communication manager by using icman.exe and writes Log file into dev_icm.
STARTUP Sequence
SHUTDOWN Sequence
1. ICM
2. Dialogue
3. Central
4. Database.
27/Jun/09
Note: Solution Manager Connects all 3 Sys - ERP (ECC6.0, Netweaver & CRM 2007)
1. Pre-requisites
2. Installation Inputs
3. Installation Steps
4. Installation Logs and then Significance
324
5. Installation Check/ Test
6. Starting and Stoping System
7. Startup Errors and Resolution
8. Installation post steps
1. Pre-Requisites
1. Hardware
2. CRM/ SOLMAN/ XI... Installation Guide
Www. Servicemarketplace/instguide
3. Sizing H/w (If user increases)
4. Swap memory 20GB RAM * 3 Times
5. IP Address/ Hostname - Ports should not be used
6. JAVA, JRE and set the path 1.4/2_12
7. CD with Lable.asc
8. CPIC_MAX_CONV = 500
CPIC Protocal (Common Programming Interface for Comm)
In Linux
Startup
Startup Uses MMC ->Select SID -> RT Click - Start
It reaches from the Startup Profile
Start Database --- Strdbs.cmd - v9start.sql
Listner control -> Lsnrctl
Lsnrctl start
Look for services Oracleservice <SID> and Oracle Listner.
Causes:
Oracle/ HP DB2
Unix
Linux
5. Analyze Alert <SID>.log for Oracle errors like 0ra-1578, ora-600 etc.,
It uses disp+work to start the instance and writes the logs into stderr/ dev_disp/
dev_w0........
326
DVEBMGS00\Work [ Available.log ]
Each work process goes to the db and db will listen the workprocess
OracleSOL01TNSListner - need to started on Linux Manually
System Profiles
Resides in
\usr\sap\<SID>\sys\profile
Default profile is used to provide default parameters to start the system. It provides value globally to
all the instance when more than one instance is configured.
327
Dialogue instance is something like extending reservation counters when users increase.
Dialogue Instance
Database
Central Instance
Dialogue Instance
Dialogue Instance
Startup profile will be available for all the instances and it contains database, msg server, dispatcher,
work process, ICM startup.
Instance profile depends upon the resources and it contains only dispatcher, work process, ICM
Startup.
Schedule Downtime
28-Jun-09
Architecture of R/3
R/3 Multilayer
PS AS DS
Eg: SAPGUI
It has various versions: 4.6c, 4.6d, 620, 640, 700, 710
From Netweaver onwards to provide Web functionality <<internet communication framework>> ICF
is provided so that the system can be accessed through web browsers.
Installation of SAPGUI
Use the presentation server DVD to install SAPGUI, there are three types
SAPGUI for windows, JAVA, HTML - JAVA (Non Windows, Unix)
329
1. SAPLogon.ini - Mandatory
2. SAPMSG.ini - Used for load balancing
3. SAPROUTE.ini - to access servers over router
4. SAPDOCCD.ini - to access sap library
5. SAPRFC.ini - for RFC these files govern SAPGUI and
requires on each end user desktop based on
the need.
Solman\gui\press\gui\...
SAPLOGON.ini copy on the desktop, open it and try to add some items.
Login to the system with the user DDIC with the Master password and create a super user similar to
DDIC
Note: Download SAPNote to activate SICF services. The system name should be FQHN (Fully qualified
with atleast two dots eg: www.sillsys.net)
Under object name folder "System" rt click -> publish complete service.
Application Server: It is a physical entity used to handle the user requests. In sap terms it is an
instance.
Instance has its own instance number and it is possible to install multiple
instances on single application server based on available resources.
Central Instance: There will be only one central instance in the sap system. It provides Message
server and Enque server along with other services.
Database Layer/ Database Server/ Database Instance: There will be only one database instance in
the SAP System. It is used to store the Data.
CI - Client
Oracle DB
DI - Client
331
Post-Installation Activities
19. Apply license through transaction SLicense (Access Market Place to apply License)
22. Hotpacks Patches that are applied online without restarting the
System
In UNIX
29/Jun/09
23. Notes These are small corrections to the programs which are
applied through transaction SNOTE
334
24. Support Package Group of notes, program corrections, bug fixes,
Enhancements and additional functionality.
25. Support Stacks It is a group of support packages that includes ABAP, Basis
PI Basis, Kernel, SAPM et.c.,
Licensing
service.sap.com
From the tab called - Key and Requests
TCODE - SLICENSE
System - status - Solmon click on mirror icon
335
Note:
SAND
TEST
CUST (DEV)
QTST
TRNG
PPRD
PRD
MIGR/ PRL
LICENSING
336
Standard License - till 9999(YYYY)
Maintenance License - 3 Months
10 + 1
Users Developer
4% VAT 48,000
17% Maintenance /Year 2, 04,000
-------------------------
14,04, 000
5 1 2
22% 24% 26%
Once the license key is received then goto SLICENSE Tcode -> INSTALL
And click Install new licenses button
337
Note: Patches should be applied on Test/ Cust first after 3 - 4 weeks will be applied on PRD.
30-Jun-09
--- Notes --
Note: First Message Server comes up, next enqueue and then the dispatcher
(Or)
Network works for Message server and Message server searches for the least loaded dispatcher
for load balancing
SU53 Contains what all the notes, screens, programs owned by the user.
2. Dialogue writes the entry of the background job in the following tables
TBTCP and TBTCS
Each dialogue - 5 Users
Each work processes (15 - 150MB)
4. Post Installation activities should be done on 003 or other and not on 001
DEV PRD
QTY
2 system landscape
GOTO I18N
System configuration
341
ADD
And provide AR ARABIC
Click on simulate
01-July-09
SM63
Solution Manager
1. System Monitoring
2. System Administration
3. Service Level Reporting (SLR)
4. Maintenance Optimizer (MUPZ)
5. Early Watch Reports (EWA)
7. Configured the service Desk to raise the issues as tickets and forward them to SAP if required.
S_SMC_47000017/ CRM_DNO_Monitor Tcodes
System should be registered with Solman to get the support
1. Satellite systems are the backend systems which are defined in the SAP Landscape.
These are required to Monitor, Administer the systems from a central location called Solution
Manager.
Note: Except exe's everything will be stored in DB. These exe are required to be at OS level to startup
the engine.
1. License Keys - It is mandatory to provide the installation key for all the Netweaver system without
which the installation cannot be continued.
Goto SMSY - Goto - Other Objects a pop up box is prompted to provide the inputs
Provide SID, MsgServer Hostname, Instance Number and Click on generate Installation or upgrade
key. This key is called as Solution manager key and it is system specific (SID, Hostname, Instance
Number). It is required only for Central Instance as it is tied up with the Message Server.
Subsequently we can define systems, servers, databases manually but, all of those are created
automatically when a satellite system is defined.
02-Jul-09
Goto SMSY
Continue -->
345
Continue -->
Establishes
Generate RFC Destinations put a check mark the connections
Assign Logical components put a check mark b/w R/3 and Solman
Clients - 800
Continue -->
Note: SOLMAN will connect to the back end system either trusted/ Logon screen
Outgoing RFC's
User : SOLMANSOL001
Continue -->>
RFC Connection for Change Management
User : SOLTMWSOL001
Continue -->>
RFC Connection for Trusted Connection
User : SOLMANSEWD
346
Additional RFC Connection Data
Continue -->>
Continue -->>
Complete -->>
It brings up the password screen 3 times - need to provide the password for the back end system.
To create users and RFC connections in the Satellite system (it 3 times knocks the door of the back
end system) and the 4th time need to provide the username and password for the solution manager.
The user should have the authorization objects S_RFC; S_RFCACL in the role to create and
communicate with the back end systems.
SMSY Continuation --
Logical components are more important to communicate with specific client, specific role in the back
end system.
348
Main Instance Logical Component Role Client
Note: Ensure that RFC Connections are created earlier, users are not existing
Delete the user by ensuring that they are not pointed to any RFC and similarly RFC Connections as
well.
Logical components specify the client number and the client role.
Solution Landscape which is used to include logical components (<SID>Client) so that all the above
activities are carried out based on Solution.
03/Jul/09
Note: Group users can only be modified by that owner of the group i.e., group_admin and SID Admin
Note: System - Status (From here we need to apply patches) in Solution Manager
Note: Maintenance Optimizer is used to find the next level of patches available.
Note: process will be slow down because of some expensive reports (select * from ...) might be
running even the processor is good enough to handle.
Note: We can also integrate ticketing tools like Remedy, Synergy with the Solution Manager. Solman
has its own Service Desk (Ticketing Tool)
T-Code: DSWP
* Note: Through SMSY we can find whether the logical systems are assigned or not.
Setting up Operations
System Monitoring
Save it.
Once we save the solution under
> Solution Structure | The SAP System with all the details are displayed
It displays all the systems that are subjected for monitoring through this system.
Click on create
Target SID ..
RFC Destinations
SM_WISCLNT001_READ
SM_WISCLNT001_ONLINE
353
This requires the satellite systems required patch up (ABAP, BASIS, ST-PI, PI-BASIS etc.,). This is to
ensure the compatibility between Solution Manager and the Satellite systems
|
P A T C H E S
|
04/Jul/09
SAP Router
It is an executable file downloaded from service market place. It will be in the run directory (Older
versions). For latest version we need to download from the Market place.
Prerequisites (Till 6th point is from SAP Website not from Willsys Notes)
You have the latest version of SAProuter (available from the SAP Service Marketplace
(http://service.sap.com/patches)
Procedure
...
If there is no SAProuter there, you can get a version (may be obsolete) from your directory
<drive>:\usr\sap\<SID>\SYS\exe\run.
3. If SAProuter has already been entered as a service with srvany.exe, remove the definition of the
service from the Registry and restart the host.
5. Define standard service properties in Control Panel Services, set the startup type to
automatic and enter a user. SAProuter should not run under the SystemAccount.
6. To avoid the error message The description for Event ID (0) in Windows NT event log, you have
to enter the following in the registry: Under
HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Event Log Application enter
the key saprouter and define the following values for it:
EventMessageFile (REG_SZ): ....\saprouter\saprouter.exe
TypesSupported (REG_DWORD): 0x7
Or
In usr\sap directory create a sub folder called SAPRouter. We have to maintain maintenance
optimizer in Solution Manager and should get an approval to download SAP Router with our host
name and IP Address (This info need to send to SAP)
We have to download Cryptographic file so that it will connect to SAP System by converting the
password related information.
SAP Router are meant to login to our SAP System (remote) by the SAP to resolve any issue that may
occur.
Copy SAP OSS RFC to SAP-OSS, SAPSNOTE and provide the logon security details that is language
EN, Client 001, user is SUSERID, if this RFC doesn't work we can't establish connectivity with SAP.
Note: Any changes in the route tab require the router to be restarted.
Service Desk
It is a tool used to create messages from the satellite systems and monitor from the solution manager.
This tool is similar to Remedy, Clarity, Synergy ticketing tools.
Or
CRM_DNO_MONITOR
Note: SPRO1 is used to perform post installation activities for the Solution Manager.
SPRO stands for - SAP Project Reference Object
OSS - Online SAP Service
5-Jul-09
TASKS
1. Satellite Systems
2. Solutions
- Activating EWA (Early Watch Alerts)
3. EWA (Early Watch Alerts)
4. System Monitoring
5. Administration
6. SLR - Service Level reporting
When ever we need Read permissions for CCMS monitoring we have to define topology.
SOLMAN_DIRECTORY
Goto solution manager and use above tcode to find the solution.
/SCPR20 is a transaction which is used to activate the business sets that are provided in the system.
We need to activate business sets for service desk, maintenance optimizer, change request
management etc.,
In the current version of netweaver most of the components are activated. But when we install the
system with lower package levels {Solution Manager 4.0} with base level 6 then we need to activate
upon upgrading the patch levels.
Installation Base
We can use this to identify the installation base of the satellite system.
AIS user is used to maintain service market place userid to communicate with SAP and the RFC
Connection will be SAP-OSS
06-Jul-09
It is a tool provided by SAP to ensure that all the support packages that are released after April 2007
related to Netweaver will be approved and downloaded through MOPZ we can add support packages
to the download basket in the Market place.
https://websmp203-sap-ag.de/swdc
Support packages and patches entry by application group
Maintain the table AISuser
In order to maintain this table SAP_MAINT_OPT_ADMIN role should present.
Ensure that your solution manager is having support package ST[Solution Tools] minimum 10 level.
SAP-OSS (RFC connection should also use the same userid to communicate with the market place)
SOLMAN40_MOPZ_TTYP_SLMO_000
SOLMAN40_CHARM_PROXYFACT_001
Note: BCSET should be activated only once because it over writes the existing data
Tcode: /$tab
/$sync deletes the buffer on the application server.
(Need to use carefully in the production system)
Project Management
SAP Solution manager provides project implementation tools through ASAP methodology
(Accelerated SAP)
ASAP Methodologies
: It contains 5 steps
1. Project Preparation
2. Business Blue Print phase
359
3. Realization Phase
4. Final Preparation
5. Golive / Support
1. Project Preparation: During this phase the business requirements are gathered and documented.
The core team is defined from SAP, implementing partner, customer, business owners, etc also
referred as Steering Committee (With some management skills)
These committees assemble from time to time & review the progress of the project.
SOLAR_PROJECT_ADMIN
Click on create
1. Provide project name
2. Type of project Implementation, support, upgrade etc..
Companies such as IBM may create a template project so that all the projects follows the same.
3. Select the solution: EWD solution for eg
Hit okie
4. Select Led by (Customer or SAP)
Provide plan days say 2000 PD
5. Define the scope of the work under SCOPE tab
Note: Include the logical component that is going to be involved in the project
2. Business Blueprint
In this phase the project is documented and the blue print gets signed off from the customer.
This is a phase where the required scenarios are selected. Scenario is nothing but a group of
transactions that are related to a specific module like SD, MM, FI, HR, BI etc
The scenarios are provided through SAP BPR (Business Process Repository)
360
07-Jul-09
3. Realization
Note: Solution Manager is also called as frontend platform to configure all the back end systems.
The configuration takes place and change requests are generated in the target system subsequently a
support message is raised to release or import the transport request before testing.
4. Testing
Testing takes place either in the testing client, integration client and test cases are built during the
configuration only.
1. Unit testing: Used to test the customizing in its test client within the same system. Tcode:
SCC1 is used to copy the requests between clients before change requests are released.
Non _ Modifiable
Note:
5. Final Preparation:
It is used to prepare the quality and as well as production system. The integration testing signoff from
the users, MTP (Mote to Production) and readiness of production system communicating with SAP to
conduct GO-Live sessions, End user training, End user acceptance, SAP Early watch report, internal and
external security.
Internal security is obtained by defining roles and assigning those to the users. External security
obtained by deploying routers, proxy, firewalls, filters and SAP Router etc.,
6. GO-LIVE
During this phase the system is subjected for parallel run i.e., both Legacy and SAP runs together for
certain period of time.
Data Transfer to SAP system is performed periodically fro legacy systems and the legacy systems are
discontinued in due course of time upon final acceptance from the business process owners.
It provides the complete implementation steps which are discussed above along with accelerators.
Accelerators are nothing but predefined templates, url's, PowerPoint's, pdfs, word docs, MOM's
(Minutes of Meeting) Etc.,
GOTO - RMMAIN
- Select the ASAP Methodology
- Goto Project Prep and Db click
- From Menu GOTO - Select Accelerator
Note: Need to focus on these points considering Solution Manager
1. Installation 2. Post Installation Activities 3. Administration 4. BCSET 5. Service Market Place.