SAP Library - Find your answers

You can use the Dialog per Application Server monitor to display the most important attributes for the dialog service, broken down by the application servers of your system. The attributes are taken from the Entire System monitor of the SAP CCMS Monitor Templates monitor set.

Features

The monitor contains the following monitoring tree elements (MTEs):

Activities

To start the monitor, follow the procedure below:

...

1. Start the Alert Monitor using transaction RZ20 or choose CCMS ® Control/Monitoring ® Alert Monitor.

2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.

3. Start the Dialog per Application Server monitor from the list by double clicking it.

SAP Installation Procedure on WIN 2k Adv Server

With Compliments by: Bhanu Prakash Pogula
Email: bpogula@sify.com

INSTALLING HARD DISK ( IF U ARE TRYING TO
LOAD SAP ON A SEPARATE HDD)

Connect HDD with cable
Win 2000 installation.
1.      Go to bios set up by pressing continuously clicking del on start.
2.      change the first bootable device to CD.
3.      insert the CD and RESTART system.
4.      click any key to boot from CD.
5.      click ENTER
6.      click ENTER again
7.      Click on C ( to continue)
8.      click on F8 ( to agree)
9.      partitions C: 4197Mb, D 12000Mb, E 6000Mb
10.     select C drive
11.     click ENTER to install
12.     click ENTER again to continue
automatically restarts, set up continues.
13.     click on NEXT
14.     click on NEXT
15.     click on NEXT
16.     key RBDC9-VTRC8-D7972-J97JY-PRVMG
17.     click on NEXT
18.     TYPE no of concurrent connections  9
19.     click on NEXT
20.     TYPE COMPUTER NAME 46IDES
21.     click on NEXT
22.     remove IIS (deselect)
23.     click on NEXT
24.     enter date & time
25.     click on NEXT
26.     finish

WINDOWS CONFIGURATION
Creating partitions for new disk.
STARTà PROGRAMMESà ADMIN TOOLSà COMP MANAGEMENTà DISK MANAGEMENT
1.      right click on unallocated space.
2.      click on CREATE PARTITIONS,
3.      click on NEXT
4.      click on NEXT
5.      type 11320 (partition size)
6.      click on NEXT
7.      click on NEXT
8.      type file system NTFS
9.      click on quick format
10.     click on NEXT
11.     click on FINISH
12.     again right click on unallocated space
13.     repeat the exercise from  point 5 but for complete size
note
C drive contains operating system
E/D drive contain 46C software
S drive contains SAP software..

PERFORMANCE
MY COMPUTERà propertiesà advanced à performance optionsàchange,
1.      Select S drive.
2.      type initial =1600& max =1652
3.      click on SET  
4.      click on OK
5.      click on OK
6.      click on OK

NETWORK SETTINGS
STARTàSETTINGSà CONTROL PANELà ADD/REMOVE HARD WARE,
1.      click on NEXT
2.      click on NEXT
3.      select ad a new device
4.      click on NEXT
5.      select (now I want to select from Hardware list)
6.      click on NEXT
7.      select network adaptors,
8.      click on NEXT
9.      select MICROSOFT
10.     click on NEXT
11.     click on NEXT
12.     click on FINISH
13.     close all windows
14.     right click on MY NETWORK PLACES,
15.     go to properties,
16.     right click on local area connections
17.     should be able to see Microsoft loopback adaptor on the screen.
18.     select properties
19.     select TCP/IP
20.     click on properties
21.     select ( use the following IP addresses)
22.     type IP addresses 198.1.1.1
23.     subnet mass 255.255.255.0
24.     click on OK
25.     select show icon on Task bar
26.     click on OK
27.     close all windows.
HOST FILE CONFIGURATION
1.      go to WINDOWS EXPLORER
2.      select C drive, WIN NT, system 32 , DRIVERS, etc
3.      double click on HOSTS
4.      open with note pad
5.      go to end of the page
6.      type IP address 198.1.1.1
7.      press TAB once
8.      type 46cides
9.      press TAB twice
10.     click on SAVE
11.     click on EXIT
12.     RESTART sytem
Software contains three folders
1.      46cides ( a. KERNEL, b. ORACLE 817, c.ORACLE  PATCHES
2.      DB EXPORT
3.      SAP GUI

ORACLE INSTALLATION
1.      46CIDESàoracle 817à NTài386àsetup run the set up by double clicking
2.      click on NEXT
3.      source path …………
destination path : S:\oracle\ora81
4.      click on NEXT
5.      click on NEXT
6.      click on NEXT
7.      type GLOBAL DATA BASE NAME : ORACLE
8.      click on NEXT
9.      click on INSTALL
10.     click on OK
11.     click on EXIT
12.     click on YES
13.     close all windows
14.     startà programsàadmin toolsà services
15.     select ORACLE SERVICES
16.     select all ORACLE releated services ONE BY ONE.

ORACLE PATCHES
46CIDESà ORACLE PATCHESàPATCHà DISK1à INSTALLà WIN 32
1.      set up (double click)
2.      click on NEXT
3.      click on NEXT
4.      click on INSTALL
5.      click on INSTALL
6.      click on EXIT

KERNEL INSTALLATION
46CIDESàKERNELàNTà I386à MMC
1.      double click on IMMC
2.      click on NEXT
3.      I agree
4.      click on NEXT
5.      click on NEXT
6.      click on NEXT
7.      click on FINISH
46CIDESàKERNELàNTà I386à NT PATCH
1.      double click on R3DLLINS
2.      click on Ok
3.      close all windows
4.      RESTART
46CIDESàKERNELàNTà COMMONà
1.      double click on R3 SET UP
2.      type SAP SYSTEM NAME IND
3.      click on NEXT
4.      click on NEXT
5.      click on NEXT    at 85%
6.      click on NEXT    automatically logs off
7.      login and control+alt+del

CENTROL INSTANCE
Startàprogramsàsap system for INDà install CENTRAL INSTANCE
1.      click on NEXT
2.      type instance no OO,
3.      click on NEXT
4.      click on NEXT
5.      click on NEXT
6.      click on NEXT
7.      click on NEXT
8.      click on NEXT
9.      click on NEXT
10.     click on NEXT
11.     click on NEXT
12.     type LOCATION OF KERNEL CD   E:cides\kernel
13.     click on NEXT
14.     password AAA    
    AAA
15.     click on NEXT
16.     password AAA
    AAA
17.     click on NEXT
18.     select NO LDAP SUPPORTS
19.     click on NEXT
20.     click on NEXT
21.     click on NEXT
22.     click on NEXT
23.     click on  EXIT when finished

DATA BASE INSTANCE
Startà programsà SAP set up system for INDà install database instance
1.      click on NEXT
2.      click on NEXT
3.      click on NEXT
4.      click on NEXT
5.      click on NEXT
6.      click on NEXT
7.      click on NEXT
8.      click on NEXT
9.      click on NEXT
10.     click on NEXT
11.     click on NEXT
12.     click on NEXT
13.     click on NEXT
14.     click on NEXT
15.     click on NEXT
16.     type location of CDS  for KERNEL  : E:\ 46cides\KERNEL
for EXPORT  : E:\DBEXPORT
17.     click on NEXT
18.     password AAA
    AAA
19.     click on NEXT
20.     click on NEXT
21.     click on NEXT
22.     click on NEXT
23.     click on EXIT  at 32%
24.     log off
25.     log in
26.     user à ind adm
27.     passwordà AAA
28.     OK
WINDOWS EXPLORERà C:\USERS\IND ADM\INSTALL\R3 SET UP FILE
1.      double clik on R# set up file
2.      select database R3S
3.      open
4.      type pass word AAA
        AAA
5.      click on NEXT
6.      at 91% password AAA
AAA
7.      at  93% start MMC
8.      click on NEXT
9.      at 100% EXIT
10.     click on STOP MMC
11.     restart system

POST INSTALLATION
E:\apgui320\gui\windows\win 32\setup(double click)
1.      click on NEXT
2.      click on INSTALL      
3.      click on FINISH
4.      click on SAP logon
5.      select NEW
6.      type DESCRIPTION : 46CIDES
7.      type application server : 46CIDES
8.      type system no : 00
9.      start MMC


10.     close MMC
11.     log in SAP
12.     client 000, user sap* password 06071992
13.     txn code SM28
14.     ENTER ( TO CHECK ERROR)
15.     RESULT : NO ERROR REPORTED ( in installation)

STMS
Description à Student
Click on SAVE
Go to overviewà transport routes
Select display change mode (second icon)
Configurationàstandard configurationà single system ( main menu)
Click on Enter
Configurationàdistributeàactivate
Click on Enter
F3 (to go back)

RZ 10
Utilitiesà import profiles of active servers
Click on Enter
Click on F3 (to go back)
Profile  click on F4
Select INDà DVEMGS00à46CIDES
Select EXTEND MAINTà change
Select create paramaeters9 icon)
Type paramter name : rdisp/max-wprun-time
Type parameter value ; 3000
Copy icon
Go back
Click Yes

CREATE PARAMETER
Paramater name : abap\ field exit
Value ; YES
Select COPY icon, go back à YES
Create parameter
: login/system-client
: 800
select copy iconàgo back à yes
create parameter
:eu/iwb/installed/languages
:EN
select COPY icon – go back à YES
again go back
click on YES
click on SAVE
click on YES
click on ENTER
click on ENTER

(USER CREATION)
TXN : SU01
user : sapuser
select : create icon

address                 logon data
title                   go on clicking ENTER no of times
first name              initial password : abc
last name               repeat pass word : abc

DEFAULTS
Logon language          : En
Output device   ; LP01
Select : Out put immediately & decimal

PROFILES
Type 1. SAP – ALL
TYPE 2. SAP – NEW
SAVE
Log off from SAP
Login to SAP

type     user : sapuser     password : abc
new password : abap
repeat password : abap

txn : SALE
IMGàerror handlingàbasic work flow settings
Select AUTOMATIC CUSTOMIZING icon
Go back
Txn 00w4
Select DISPLAY CHANGE MODE icon
Create icon

CREATE
Prefix no       978
System ID       IND
Client          000
Click on Save
Local object
Cancel    X


CREATE
Prefix no       972
System ID       IND
Client          800
Click on Save
Local object
Cancel    X

TXN SE 38

Program name : Z FIRST
CREATE
ACCESS KEY : 36687663221261278694
TITLE : DEMO
TYPE : EXECUTOR
Click on SAVE

LOCAL OBJECT
Log off from SAP
Log into SAP
Client          : 800
User            : sap
Pass word       : 06071992

RUN txn SU01  for 000 client


Log off from SAP
Log into SAP
Client                  : 800
User                    : sap
Pass word               : abc
Click on ENTER
Enter new password : abap
Logoff
Stop MMC

We are in the process of implementing SAP for our overseas sales offices. However, the Server will be situated at our country. We want our overseas sales office to connect to our SAP Server through VPN. What should be the optimum internet bandwidth that they should use at their place to connect to our SAP server? Does SAP recommend any standard bandwidth for this process?

From our experience, there is no general rule that one can follow, as several factors will affect the connectivity

1. No of hops between your ISP and that of the remote site, the more hops the poorer the performance, even having large bandwidth may not improve the performance by much if there are numerous hops in between.

2. Is the Internet connectivity solely used for your VPN or other purposes such as web surfing, email etc, other traffic can consume large amount of traffic thus causing your SAP performance to be poorer

3. ISP's bandwidth to the public internet - If the ISP is heavily over subscribed, and has limited bandwidth connecting to the international network, you will find that you will not be able to get the international throughput you subscribed for as such, performance may be poor even you have paid for a line with a large bandwidth

4. No of users at your remote office using the VPN - In general the lines we use are 64kbps for sites with approx 3-5 users, we are also using ADSL lines with 512kbps connectivity and they enjoy close to local Lan performance for SAP.

Keyword: BASIS
Title : SAP NetWeaver Application Server High Availability

Use TCode AL11 to browse the application servers directory structure.

Evaluate ITS Server Speed issues

You have 10 users accessing sap via an ITS server (6.20) and it is soooo slow !!! access via sapgui is fast - any ideas what to look for ??

We tested several options for deploying the SAPGUI :-

Tivoli packages
ITS
Citrix MF XP

Tivoli was already built and in house so all we had to do was create a SAPGUI package and deploy it to the field (3000+ users) - pain in the butt because we had to find out all the users workstation id's for the users in 900+ locations. So far we have deployed 35% and our Go-live is 10/01!

ITS - We had an ITS consultant come in and review our setup. We were able to enhance the performance to some extent (20%). But, that was still unacceptable in comparison to the WINGUI that the users are now accustomed to. In short, we scraped the ITS project because of the problems with latency/performance. Our connection between our test locations and the Data Center was 100MB. The other locations were 10MB.

ITS Tuning in relating to performance of the ITS Server

1. HKEY_LOCAL_MACHINE\Software\SAP\ITS.0\\Programs\SAPjulep\StaticTemplats
To simulate the test, the parameter for Static Templates was changed from 0 to 1

Recommendation : Development system = 0 ; Production System = 1

2. ITS Parameters / Recommended / Ours

a) Worktreads and Sessions
MaxSessions 400 400
MaxWorkThreads 64 40 (can be reduced)
MinWorkThreads 64 40 (can be reduced)

b) Caching
Caching 1 1
CacheSize 16384 16384
FileSize 1048576 1048576
TimeToLive 31 31
StaticTemplates 1 0
CacheInvalidateHour
CacheInvalidateMinute
Staticflows 1
ProductionMode 1 0
StaticBor 1 0

c) Timeout Parameters
TimeoutPercentage 75 75

d) Debugging Parameters
~rfcDebuggingOn 0 0
~rfcTraceOn 0 0
AdminEnabled 0 0
localTraceLevel 0 0
SAPDebuggerDelay

e) Miscellaneous
MinRespSize 32768 32768
MaxRespSize 2097152 2097152
MaxServiceContextSize 20480 20480
~http_compress_level 7 7
~http_use_compression 1 1

2. Load Balancing and Multiple Agates
IncAGates 1 (Do not modify this value.)
MinAGates (Do not modify this value.)
MaxAgates (Do not modify this value.)
IncWorkThreads 1

3. Windows Environment Settings

4. SAP R/3 Parameters
rdisp/gui_auto_logout >= ~userTimeout

3. Check the following internet option settings.
Under "Advanced", make sure both HTTP 1.1 settings are on
Under "Security", "Custom Level" under the point "micellaneous" make sure these are ENABLE:

a) access the data sources across domains
b) Launch programs and files in IFRAME
c) Migrate sub-frames across different domains

4 Verify Compression. These values were changed in the global.srvc file
~http_use_compression 1
To increase the transmission speed and reduce the overall network load we reduce the size of the data sent from the server to the web browser by using compression. The values are 0 to disable compression and 1 to enable compression.

~http_compress_level 7
The compress level can be set between 1- 9 where 1 is the lowest compression level and 9 is the highest. The higher the value set for ~http_compress_level, the better the compression achieved.

The Level 1 achieves the lowest compression level/ fastest procession speed and Level 9 achieves the highest compression level/slowest procession speed

5 ~navigationenabled : Enables / Disables Drag & Relate functionality in the SAP GUI for HTML.
Using Drag & Relate in the SAP GUI for HTML requires a callback from the R/3 System for nearly every request / response cycle. This is an unnecessary overhead for many applications. Hence we disable Drag&Relate by setting this parameter to 0 in the webgui.srvc file on the Agate.

Citrix proved to be just too expensive an option for right now. The SAP 4.6d protocol proved to be quite thin, with the bandwidth requirements tracking only slightly greater than ICA. However, on a number of occasions over the test period, it was observed that SAP could demand a considerable amount of bandwidth for short bursts. This traffic was primarily outbound, targeted at port 4803. However, even with the thin nature of SAP, ICA still provided a bandwidth advantage.

To better understand this and develop conservative figures, a trend analysis of the data was performed. This analysis allowed for a weighted smoothing of the statistics, lessening the impact of the burst type activities. Based on the trend figures, the following observations where made:
SAP showed an overall Kbps trend average of 2.5 Kbps
ICA showed an overall Kbps trend average of 1.7 Kbps

Overall, ICA showed a 30% improvement in bandwidth utilization when compared to SAP, based on the trend analysis of the data. This margin jumps to almost 70% when averages are analyzed.
The maximum SAP burst activity exceeded the maximum ICA burst activity by 70%.
Both SAP and ICA displayed extremely limited network utilization. Over extended periods, ICA displayed consistently low inbound traffic, trending towards .8

If all you have is 10 users, what's wrong with deploying the SAPGUI?

The ITS environment was initially created with very minimal customized configurations (2 servers Dell 2650's). Most ITS performance parameters were accepted as default. We tested over dual T1's (1.5MB) as well as Ethernet 10/100MB max.

For each request by the webserver, a separate request is made to the backend - so what you get is a constant request/send, even though each one is milliseconds adding hundreds of requests through the WGate to AGate to R/3 you can see there just isn't much you can do to improve the speed.

To help diagnose the network or measure network metrics, we used a program from SAP called “NIPING”. Niping is a test program for the network interfaces (NI) layer. It provides connection and performance test with the same mechanisms that the SAPGUI uses. To test the network, the niping tool runs a continuous test. It generate and evaluate a network trace simultaneously from the ITS server and the front end. We ran several niping tests and the following results were produced.

Since the communication between the client and the Web servers is over the HTTP protocol, SAP-ITS also makes the SAP transactions accessible to distant locations via the Internet, enterprise networks, and virtual private networks. These networks are typically very complex and have many users. As the distance between the nodes and the complexity of the network increase, application performance becomes an important issue. The performance of a network depends mainly on two
different factors - the bandwidth (throughput) and the latency (delay).

Bandwidth is the most commonly known factor affecting performance of a network. Network bandwidth defines the amount of data that can be transferred at a given time. Networks with higher bandwidth provide better performance.

The second factor relating to performance of a network is latency. Latency can be defined as the delay in processing data within the network. A network with lower latency performs better than a network with high latency.

In addition to the individual effects on bandwidth and latency within the network, their combination can also affect the quality of communication, hence determining the overall network performance (network speed).

Understanding SAP ITS - Internet Transaction Server

The SAP Internet Transaction Server (ITS) is the essential link between the SAP R/3 system and the Internet. It enables Internet (and Intranet) users to communicate directly between R/3 system to run R/e transactions, remote enabled function modules and reports as Internet applications components. The ITS is one of the cornerstones of SAP's mySAP.com offerings and strategy and integrated into the SAP 6.10 Web Application Server release. The ITS is the key technology behind the following products: Workplace, Employee Self-Service (ESS), Enterprise Buyer Professional (EBP), BW 2.0 Interface, Online Store and Retail Store, and the APO Interface. There are many other SAP products and applications that are based on ITS technology to interface from the Web to SAP R/3.

SAP ITS can handle complementary Web technologies to access data from SAP R/3:

- SAP GUI for Html: SAP transaction screens are dynamically converted to HTML pages

- Web transactions: SAP transactions that can be called from an HTML page (template based mode)

- Web remote function call (RFC): SAP R/3 function module that can be called from an HTML page

- Web reporting: Mechanism for linking to SAP reports and regenerated lists from an HTML page. Web reporting is implemented as a special-case RFC.

- ITS Flow Logic: Events, statuses, and modes used to model the dialog logic of a Web application in "flow files" on the SAP ITS.

SAP's Internet applications are known as Internet Application Components (IAC) or Easy Web Transactions (EWT). Both are complete business solutions that allow Internet and Intranet users to access business information in the SAP R/3 system by starting transactions, function modules, and reports from a Web browser. All IACs or EWTs are based on a common infrastructure consisting of two essential components.

SAP Internet Transaction Server (ITS) - The ITS is the interface between the Internet and R/3 and is the runtime engine that links Web server to the R/3 Application server.

ABAP workbench tool - Web Application Builder and/or SAP@Web Studio - WAB is an R/3 ABAP workbench tool and SAP@Web Studio is a PC tool for creating, modifying and managing all ITS objects on which IACs or EWTs are based. These objects include service files, HTML Templates and HTRC language resource files.

The ITS solution to developing Internet applications is based on the premise that there is already a suitable business application solution, which has a stock of transactions, function modules and reports, as well as its own integrated development environment. All that is needed to enable Internet users to access and run these applications is an interface to the Internet. Apart from the general advantages derived from making SAP R/3 business information available over the internet, the ITS solution has many benefits.

These include:

• Ease of development - Programmers can develop IACsEWTs using a business application system (R/3), development environment (ABAP Workbench) and a programming language (ABAP), with which they are already familiar. There is also integrated data dictionary support from the ABAP Dictionary and appropriate transaction handling.
• Ease of deployment - The ITS solution supports internationalization of applications.
• Ease of use - ITS based IACs and EWTs have the same look and feel as any other Web site.

We are in the process of implementing SAP for our overseas sales offices. However, the Server will be situated at our country. We want our overseas sales office to connect to our SAP Server through VPN. What should be the optimum internet bandwidth that they should use at their place to connect to our SAP server? Does SAP recommend any standard bandwidth for this process?

From our experience, there is no general rule that one can follow, as several factors will affect the connectivity

1. No of hops between your ISP and that of the remote site, the more hops the poorer the performance, even having large bandwidth may not improve the performance by much if there are numerous hops in between.

2. Is the Internet connectivity solely used for your VPN or other purposes such as web surfing, email etc, other traffic can consume large amount of traffic thus causing your SAP performance to be poorer

3. ISP's bandwidth to the public internet - If the ISP is heavily over subscribed, and has limited bandwidth connecting to the international network, you will find that you will not be able to get the international throughput you subscribed for as such, performance may be poor even you have paid for a line with a large bandwidth

4. No of users at your remote office using the VPN - In general the lines we use are 64kbps for sites with approx 3-5 users, we are also using ADSL lines with 512kbps connectivity and they enjoy close to local Lan performance for SAP.

This can be diagnoised using NIPING.EXE command, which is available in Exe -> Run directory. To test the connectivity between SAP and front end computer, do the following:

First start the NIPING server on computer:

Nipping –s –I 0

Then start the same on the client. Use the following command:

Nipping –c –h

Applying SP4 to Windows 2000 Server

You need to download a newer SAP kernel. You will need an OSS ID and password to access http://service.sap.com/patches. And you will need to know what R/3 version, database, and OS you currently use.

Once you are at the patches website, you will need to click in the navigation tree:
R/3 -> R/3 + ?Release number? -> Binary patches ->
SAP Kernel + ?Release number? + 32-Bit -> NT/I386.

Download everything from the database section and everything from the database independent section.

One of the files you downloaded should start with SAPCAR and end with a *.exe.
Rename this file to SAPCAR.EXE and place it in the c:\winnt\system32 directory.
Go to \usr\sap\\SYS\exe\run and backup the entire directory to some other directory -
I usually create a \usr\sap\\SYS\exe\backup_run directory. Make sure SAP is down, the database is down, the TNS listener is down, and the SAPOSCOL is down before you do this.

Uncompress all the files you downloaded by opening a DOS box and typing:

SAPCAR -xvf .CAR

All files ending with .SAR or .CAR must be uncompressed. All the extracted files need to be moved to the \usr\sap\\SYS\exe\run AFTER that directory has been completely backed up.

Once everything has been downloaded, uncompressed, and moved into the exe\run directory, you can start the SAPOSCOL, the listener and the database services again. And then you should be able to start SAP. If there are any application servers for this database instance, the SAP software will update those kernels on startup.

If the SAP instance STILL does not come back up, you can take down everything again and restore the exe\run directory with your backup copy. Nothing will have been damaged.

You need to download a newer SAP kernel. You will need an OSS ID and password to access http://service.sap.com/patches. And you will need to know what R/3 version, database, and OS you currently use.

Once you are at the patches website, you will need to click in the navigation tree:
R/3 -> R/3 + ?Release number? -> Binary patches ->
SAP Kernel + ?Release number? + 32-Bit -> NT/I386.

Download everything from the database section and everything from the database independent section.

One of the files you downloaded should start with SAPCAR and end with a *.exe.
Rename this file to SAPCAR.EXE and place it in the c:\winnt\system32 directory.
Go to \usr\sap\\SYS\exe\run and backup the entire directory to some other directory -
I usually create a \usr\sap\\SYS\exe\backup_run directory. Make sure SAP is down, the database is down, the TNS listener is down, and the SAPOSCOL is down before you do this.

Uncompress all the files you downloaded by opening a DOS box and typing:

SAPCAR -xvf .CAR

All files ending with .SAR or .CAR must be uncompressed. All the extracted files need to be moved to the \usr\sap\\SYS\exe\run AFTER that directory has been completely backed up.

Once everything has been downloaded, uncompressed, and moved into the exe\run directory, you can start the SAPOSCOL, the listener and the database services again. And then you should be able to start SAP. If there are any application servers for this database instance, the SAP software will update those kernels on startup.

If the SAP instance STILL does not come back up, you can take down everything again and restore the exe\run directory with your backup copy. Nothing will have been damaged.

Keyword: BASIS
Title : SAP NetWeaver Application Server High Availability

Keyword: BASIS
Title : SAP NetWeaver Application Server High Availability

Keyword: BASIS
Title : SAP NetWeaver Application Server High Availability

Keyword: BASIS
Title : Monitoring RFC Resources on the Application Server

Keyword: BASIS
Title : Java Instance – Server Process

1. Individual Testing ( Individually which we've created)
2. Regressive Testing ( Entire Process)
3. Integration Testing ( Along with other integrated modules)

The 3 types of testing is as follows:-

1. Unit testing (where an individual process relevant to FI or MM etc is tested)

2. Integration testing (where a process is tested that cuts across all areas of SAP).

3. Stress testing (where lots of transactions are run to see if the system can handle the load)

SAP IDES Installation Procedure for SAP Install on W2k server

Procedure for installation on W2k server with sp3.

Installation Of SAP 4.6b

System Requirements.

P-III System
1024 MB or 512 MB RAM
Minimum 60GB HDD
40 GB Hdd (2GB for WinNT & 38 GB for oracle & SAP)
10 GB Hdd for CD dumps.
CDROM drive.
Network Card

C:\ - 10GB - Windows 2000 Server - NTFS
D:\ - 40GB - Oracle & SAP - NTFS
E:\ - 10GB - CD Dumps - NTFS
F:\ - CDROM Drive

Install Windows 2000 server in first 10GB partition
Computer Name - SAPSRV
IP Address - 192.168.1.2
Subnet Mask - 255.255.255.0
Work Group - TEKSOFT
Complete the installation & Restart.

Install Service Pack 3
Install All the Drivers
Install IE6 SP1

Create two Users as mentioned bellow

Start -> Programs -> Administrative Tools -> Computer Management -> Local Users
and Groups -> Users -> New User

a. First user name TEKADM
Give password, disable the already enabled option & enable
"Password Never Expires & user cannot change the password option "

b. Second user name SAPServiceTEK
Give password, disable the already enabled option & enable
"Password Never Expires & user cannot change the password option "

Add the two Users to Administrators Group

Change hostfile

Open C:\Winnt\System32\driver\ect\host file in Notepad & add IP Address and Computer Name in
The bottom of file. Save & Exit.

Change the Virtual Memory

C: Min - 512MB
Max - 1024MB

D: Min - 2048MB
Max - 2560MB

Change the File and Printer sharing properties to “ Maximize through

Logon as TEKADM
Insert SAP-Oracle CD &
Select F:\NT\i386\setup & click enter
Location of oracle D:\orant & click enter
Accept path change & click enter
Oracle 8 enterprise edition & click enter
(Oracle 8.1.7 will not be supported by SAP Kernel 4.6B)
(Oracle 8.1.7 will be supported by SAP Kernel 4.6C only)

After completion of oracle Stop the service "Oracle TNSlistner 80"
Select F:\NT\i386\Patchs.0.5.2.2\setup & click enter
Accept the defaults & complete the installation.
Restart the system.

Dump all the export CDs (6 CDs) into
E:\dump\db1 - export CD 1
E:\dump\db2 - export CD 2
E:\dump\db3 - export CD 3 (To dump type as E:\dump\db1>Xcopy /e f: & enter)
E:\dump\db4 - export CD 4
E:\dump\db5 - export CD 5
E:\dump\db6 - export CD 6

Insert Kernel CD

Select F:bker\NT\i386\NTPATCH\R3dllins & click enter
This will install patch for NT.

Restart the system.

Logon as TEKADM
From kernel CD
F:\NT\common\r3setup & enter
Enter the following

System Name - TEK (must be 3 Letters Capital)
Location - C:\users\Tekadm\install (it comes by default)
Accept to restart the machine.

Logon on as TEKADM
Copy the file "db_ides.r3s" from DB1\IDES\NT\ORA\DB_IDES.R3S
(18KB files size) to C:\users\tekadm\install

Start r3setup from
C:\users\tekadm\install\r3setup & enter
Select "central.r3s" file & enter
& Follow as mentioned bellow

System Name - TEK
Instance no. - 00
Accept Defaults
Directory of SAP system -change to D:
RAM of the sys. - Accept the default
Location of the KERNEL CD - F:
Port no. - 3600
Enter the password of TEKADM two times
Enter the password of SAPServiceTEK two times
Start the installation.
This will come upto

Select C:\users\tekadm\install\r3setup & enter
Select "db_ides.r3s" & enter
System Name - TEK
Instance no. - 00
Accept Defaults
Select WE8DEC (default for r/3 4.x system) & enter
Oracle dir. - D:

Location of SAP Database specific files

SAP Database Drive

SAPARCH D
SAPBACKUP D
SAPCHECK D
SAPREORG D
SAPTRACE D & enter

Location of Oracle Data files

Oracle Data directory drive

SAPDATA1 D
SAPDATA2 D
SAPDATA3 D
SAPDATA4 D
SAPDATA5 D
SAPDATA6 D & enter

Location Database LOG files

Dir. for LOG files Drive

ORIGLOGA D
ORIGLOGB D & enter

Location Mirrored Database LOG files
(Change from D to C)

Dir. for LOG files Drive

MIRRLOGA C
MIRRLOGB C & enter

Accept the default RAM & enter

Location of export CDs dump

CD name Location Copy destination

KERNEL F:bker
EXPORT1 E:\dump\db1
EXPORT2 E:\dump\db2
EXPORT3 E:\dump\db3
EXPORT4 E:\dump\db4 (Clear this field)
EXPORT5 E:\dump\db5
EXPORT6 E:\dump\db6 & enter

Enter the Password of TEKADM
No. of parallel process - 1
Start installation.

Wait for 14 to 15 Hrs & installation will come Upto 91% & will ask for SAPr3 password.
Enter the password of TEKADM & enter

This will come upto 95%
Open SAP Management Console from desktop & Right click "TEK" & start the service.
Wait for the service to start & will change from yellow to green.
Come to the r3setup screen & click next.
This will bring upto 100% & the installation is over.
Exit the r3setup & stop the "TEK"service & Restart the system.

POST INSTALLATION TASKS

After SAP installation, install SAPGUI in the server. (CD 9)
Restart the system

Open SAP Management Console & start the sap service.

Start the Sap Frontend from the start\programs\sap frontend\sapsrv.

Logon as
Client 000
User name DDIC

Password 19920706
Language en

CD Title------CD Location-----------CD copy to this location
kernel--------Dump location1-------clear , don't re copy
cd1-----------Dump2--------- -------clear, this field
cd2-----------........3-----------------clear
cd3-----------.........4----------------clear