Sapdatabase for all sap modules

sapdatabase provides you all sap modules information,latest updates

Sapdatabase for sap education

sapdatabase provides you all sap modules material,interview needs

Sapdatabase for all sap information

Sapdatabase makes you as a sap professional

Sapdatabase for outsourcing and online training

Sapdatabase provides you online training,outsource services for all sap modules in econamic fee

Sapdatabase for sap jobs

Sapdatabase makes job searching for you

Showing posts with label SAP NETWEAVAR 7.1. Show all posts
Showing posts with label SAP NETWEAVAR 7.1. Show all posts

Thursday, November 15, 2012

Support Stack implementation using JSPM screens

Upgrade JSPM first.
Put the Support stack into /usr/sap/trans/EPS/in

Goto /usr/sap/<VNW>/DVEBMGS00/j2ee/JSPM

In JSPM choose the option

Now apply Support stack: 17 
Select the option : Single support package

 Click on Start

Verify the current release and target release and Click on Next.

 After completion click exit.

Thursday, August 30, 2012

SAP BI System Daily Monitoring Report

Tcode Activities from SAP BI.

RSPCM Monitoring Process chains
SM58 Monitoring Transactional RFC
RSMO Monitoring Loads
RSA1 Checking source system connectvity
DB02 Check database size and consistency check logs
DB12 Backups  log
SM13 Check Update process and terminated updates
SM51 Check for the Availability of DB and all application servers
SM37 Check  cancelled Jobs and Job queues
ST02 Check SAP Buffers
SM21 Critical/Serious system log messages
ST22 Check and Analyze Program terminations (short dumps)
OSS1 Research SAPNet database for short dumps, determine relevance to THE CLIENT and forward it to super-users
SM50 Check Work process status
SM12 Check Lock Entries
SP01 Check spool request status
ST06 Check for the OS logs
SMLG Check for logon load balancing
SM66 Check for long running Background jobs
ST03 Check for Average Response time
AL08 Check user load balancing across application servers
DB13 Check for completion of Backups
ST06 Check Disk I/O response times
DB01 Check for the database deadlocks

Thursday, May 3, 2012

Sap NETWEAVER versions, Releases, Kernel & support packs levels


SAP Enhancement Package 3 for SAP NetWeaver 7.0 and
SAP Enhancement Package 1 for SAP NetWeaver 7.3
PI_BASIS          731  00
SAP_ABA           731  00
SAP_BASIS         731  00
SAP_BW            731  00
ST-PI      2008_1_710  04
Kernel version: 720_EXT_REL patch number 100
SAP NetWeaver 7.3
SAP_BASIS         730  00
SAP_ABA           730  00
SAP_BW            730  00
PI_BASIS          730  00
ST-PI      2008_1_710  01
Kernel version: 720
SAP Enhancement Package 2 for SAP NetWeaver 7.0
SAP_BASIS         702  02
SAP_ABA           702  02
SAP_BW            702  02
PI_BASIS          702  02
Kernel version: 720 patch number 35
SAP Enhancement Package 1 for SAP NetWeaver 7.0 Support Release 1
SAP_BASIS         701  03
SAP_ABA           701  03
SAP_BW            701  03
PI_BASIS          701  03
SAP Enhancement Package 1 for SAP NetWeaver Application Server for ABAP 7.1
SAP_BASIS         711  00
SAP_ABA           711  00
SAP_BW            711  00
PI_BASIS          711  00
ST-PI      2005_1_710  03
SAP Enhancement Package 1 for SAP NetWeaver 7.0
SAP_BASIS         701  00
SAP_ABA           701  00
SAP_BW            701  00
PI_BASIS          701  00
SAP NetWeaver Process Integration 7.1
SAP_BASIS         710  04
SAP_ABA           710  04
SAP_BW            710  04
PI_BASIS   2006_1_710  04
ST-PI      2005_1_710  03
This delivery contains SAP NetWeaver 7.10 SP Stack 04.
SAP NetWeaver Mobile 7.1
SAP_BASIS         710  01
SAP_ABA           710  01
SAP_BW            710  01
PI_BASIS   2006_1_710  01
ST-PI      2005_1_710  01
This delivery contains SAP NetWeaver 7.10 SP Stack 01.
SAP NetWeaver ABAP for Banking
SAP_BASIS         710  00
SAP_ABA           710  00
SAP_BW            710  00
PI_BASIS   2006_1_710  00
ST-PI      2005_1_710  00
SAP NetWeaver 7.0 Support Release 3
SAP_BASIS         700  14
SAP_ABA           700  14
SAP_BW            700  16
PI_BASIS   2005_1_700  14
This delivery contains SAP NetWeaver 7.00 SP Stack 14.
SAP NetWeaver 7.0 Support Release 2
Kernel            700  75
SAP_BASIS         700   9
SAP_ABA           700   9
SAP_BW            700   9
PI_BASIS   2005_1_700   9
This delivery contains SAP NetWeaver 7.00 SP Stack 09.
SAP NetWeaver 7.0 Support Release 1
Kernel            700  48
SAP_BASIS         700   6
SAP_ABA           700   6
SAP_BW            700   6
PI_BASIS   2005_1_700   6
This delivery contains SAP NetWeaver 7.00 SP Stack 06.
SAP NetWeaver 7.0
Kernel            700  18
SAP_BASIS         700   1
SAP_ABA           700   1
SAP_BW            700   1
PI_BASIS   2005_1_700   1
SAP NetWeaver 2004 Support Release 1
Kernel            640  43
SAP_BASIS         640   9
SAP_ABA           640   9
SAP_BW            350   9
PI_BASIS   2004_1_640   6
SAP NetWeaver 2004
Kernel            640   1 (not authorized for productive operation)
SAP_BASIS         640   0
SAP_ABA           640   0
SAP_BW            350   0
PI_BASIS   2004_1_640   0

Saturday, March 17, 2012

Java stack start up procedure & request flow steps

JAVA Request Flow
User submits the request
request is handled by JAVA Dispatcher
Dispatcher assigns the least loaded server process
Server process assigns application thread manager to process the request
Server process processes the requests till it is completed/ or the memory is exhausted/ timeout
ATM Handles the user request Internal process/ Intra process (For Locking)is handled by Server process.
Server process communicates with DB and the response is sent back to the user.
Central services are used for load balancing and locking purposes.(During an update)
JAVA Start up
 Use MMC
 Startsap command
 or rdisp/j2ee_start=true used to start along with ABAP Engine but consumes at least 10 Mins to 30 Mins.
Process of JAVA Start up
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
START_DVEBMGS_<Hostname> (Integrated Engine)
START_JC00_<Hostname> (Standalone JAVA Engine)
3. It also uses start_scs01_<Hostname> for starting SAP Central Services
4. It uses default profile to start the engine with minimal parameters that are required by all the Dialogue Instances.
5. It uses the instance profile to start the engine with instance specific (Memory Buffer etc)
     <SID>_SCS01_Hostname for SCS and
     <SID>_DVEBMGS00_hostname for Integrated Engine and
     <SID>_JC00_Hostname for Standalone Java Engine
6. In order to start the JAVA engine Jcontrol process is used to initialize the
7. JControl initializes the bootstrap process to read the parameters from
 8. JControl starts JLaunch process by reading
                        JLaunch         -  Dispatcher
                        JLaunch         -  server process
JAVA Engine Start up Flow

It consumes more time to start because bootstrap reads the parameters from the database to 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.

Thursday, March 15, 2012

Netweaver Installation inputs & users

1. Use Installation Master
2. Select the respective Sapinst. (sapinst.exe for windows and ./sapinst on UNIX)
3. Select the installation Database (Oracle, SQL, MaxDB..)
4. Provide the following inputs
1. SID
2. Instance Number (00 to 97)
3. JCE Policy (Java Cryprography - which is used to provide secure communication over the web.
4. Master password for the users
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
4700 - 4797     - Dispatcher security port
3300 - 3397     - Gateway port
4800 - 4897     - Secured gateway port
50000              - JAVA instance port if instance number is 00

Say for eg if the instance number is 25 then
50000 (100 + 25)        = 52500
04 is for Administration port : 52504
Say for eg 99   - 59904 - 59916
50008              - Telnet Port
50026              - SDM Ports    (00 - Instance Number)
50001              - SSL (Https) 

Friday, February 17, 2012

configure sap System into OSS

  • (SAP AG should make this entry, when the license is requested. So check, whether all customer system are entered)
  • Login into OSS using a customer-S-User
  • Click on the Service button
  • Click on Service connection button
  • Then all systems which are owned by the customer are displayed
In exceptional cases (if we do not have any s-User, but the Support expert has to look onto the system nevertheless), one can mount the concerned server under the customer system with the SID <SID>:

  • Login into OSS using SAP Hosting-S-User
  • Service -> Service connection
  • Then the SAPHosting-Systems will be displayed
  • Double click the <SID>
  • Server -> System data -> Tab Application Server -> edit
  • Create server -> create Server ->
  • Hostname, IP, Operating system, Instance number
  • Save
Now the SAP-Support export can login into the system using CSN -> /nstfk -> sid -> R/3-Support -> hwdf... (Of course a user for the Support expert has to be created inside the R/3-System first !)

If the customer does not know, how he can enter his system into OSS:
  • Customer might login into OSS using his OSS-User
  • Press buttons: General Functions-> System data maintenance
  • Then he will see his installation number. He might click on the node, under which the new system should be implemented (click on SID "NEW")
  • Right mouse click -> System data -> display/change
  • Enter installation name, e.g. Infraserv CRM Test system
  • Purpose: e.g. T for Test system
  • Create System Button ->
  • A Popup „request license key “appears
  • SID:                                        enter new SID
  • System type:                        e.g. Test
  • Software product:                               CRM     
  • SW-Product-Re:                   2.0
  • Basis-Release:                      46
  • Database
  • Operating System
  • Click on „New“ inside the field license key
  • Enter hardware key (provided on the OS-Level or from R/3 /slicense
  • Click request Button.....
  • Then SAP AG will automatically replicate the system under installation number. This can last for while.
  • Customer has to wait until the license key is available. At that time the system will be visible.

Thursday, February 9, 2012

When administrator or j2ee_admin user is locked in SAP & EP (enterprises portal)

 When Java administrator or j2ee_admin user locked in SAP... 
 forgot or lock "Administrator or J2EE_ADMIN" password just we need to follow this steps

 Enable "SAP*"
a.Go toConfigtool C:\usr\sap\\\j2ee\configtool\configtool.bat

b.Goto cluster-data --> Global server configuration --> services -->

c.Double-click on the property "ume.superadmin.activated = TRUE"

d.Double-click on the property "ume.superadmin.password="


f. Restart the engine.

 Login with "SAP*" into portal

a. http://:/useradmin/index.jsp

b. Enter userid / password as" SAP* / "

c. Search for "Administrator" user

d. Reset or change password for "Administrtor"

once process was done need to disable super admin
 Disable "SAP*"

a.Start the Config Tool C:\usr\sap\\\j2ee\configtool\configtool.bat

b.Goto cluster-data --> Global server configuration --> services -->

c.Double-click on the property "ume.superadmin.activated = FALSE"


e. Restart the engine.

Login with "Administrator"

a. http://:/useradmin/index.jsp

b. Enter userid / Password as "Administrator /

c. it will ask change password just change it.

Thursday, February 2, 2012


  • System copy is a process of setting up a new system using a copy/backup of existing system.
  • It is required in the following scenarios.
                                I.            H/w migration.
                              II.            Os/db migration.
                            III.            Testing the backup of sap system.
                            IV.            Patch application and kernel upgrade.
                              V.            Sap upgrade.
                            VI.            To test the developed objects before moving to production.
                          VII.            To setup a sandbox, testing of training system in the landscape.
  • There are various ways to perform a system copy.
§  Homogeneous system copy- if there is no change in the database of operating system. Homogeneous system copy can be performed by following methods.
1.       File system copy.
2.       Database backup and restore (db specific method).
3.       Sapinst tool export and import.
Note: option 3 is the only method for heterogeneous copies/Unicode conversions, net weavers system based on java. For heterogeneous system based on oracle and db2. Sap also supports db specific methods using br tools.
§  Heterogeneous system copy- if there is a change either in the os or db of the target system. It has to be performed by a os/db migration certified consultant.
  • If the system is setup as new system then it is referred as system copy/installation os,  db, erp, restore/import is required for which no [re steps are required i.e the system is completely built from os, db and r/3 without changing os or db.
The system exists with os, db, erp (sap component). Which is refreshed (replaced) by the database of any other system mostly PRD in the landscape. In such cases the source dependencies need to be documented or transported to revert them back after the refresh.
1.       Take full offline backup of database using  BR Tolls/DB 13.
Directly using the single line command of brtools
Brbackup –u –p init<sid>.sap –d disk –t offline –m all
or go through the br tools menu
Select 4th option –backup and database copy
Select 1st option –database backup
Select 2nd to change backup device type to disk
Select 6th to change backup type to offline_force type c for continue
Select 3rd option of menu for compression mode and set to yes. And the backup starts and in b/w asks for prompt continue, then type c to continue.
2.       Generate of control file.
è By generating trace file at os level (this method is used for /DB refresh )
Sql> alter database backup controlfile to trace
We can find the trace file in oracle/sid/saptrace/usertrace. Copy it on the desktop and do the modifications.
Remove all the lines above “STARTUP NOMOUNT” below CHARACTER SER UTF8;  save the file.
Replace S_sid with T_sid.
Replace REUSE with SET.e
Copy the init<sid>.ora and init<sid>.sap from source system(oracle/sid/102/database) and change the source S_sid with T_sid.
è  By using ORABRCOPY tool (java tool to generate control file)
ORABRCOPY is available as .SAR file in instmaster/im_windows_i386/common/dbtools/install /ora
Create a new directory copy the .sar file full permission, login to <Sid>adm and uncar using the command SAPCAR –XVF ORABRCOPY.SAP
It will generate 3 files
1. ------- used for linux os.
2.       Ora_br_copy.bat -------used for windows os.
3.       Orabrcopy .jar.
Now generate the control file using (orasid)
Ora_br_copy.bat -generateFiles –forceLogSwitch –targetSid < **> -password <******>  -listnerPort 1521
It will generate control.sql(target system) and control.trc(source system) and init<sid>.ora (target system).
Compare control.sql with control.trc and change according to control.trc file in control.sql file.
Copy the init<sid>.sap from /oracle/sid/102/database of the source system and change S_sid with T_sid.
3.       Target system preparation
Ø  Install os and oracle with same patch level as source.
Ø  Go to installation master and run Sapinst and select as below
n  Sap net wear 2004’s support release.
n  Sap system.
n  Additional life cycle tasks.
n  System copy.
n  Oracle.
n  Target system.
n  Central instance as abap.
Ø  Click ok.
Select the custom option. It will ask for log off click ok.
Select the java component.
Select the jdk directory.
Select the jce policy archive.
Provide sap sid .<T01>
Installation drive<e:>.
Enable Unicode system.
Ø  Provide the password.
Ø  Select local installation.
Ø  Provide os user password.
Ø  Select homogeneous system copy.
Ø  Provide db sid. it will show a reference error
Ø  Go to installation directory (pf/sap_instdir/nw045/lm/copy/ora/system/central/as/edit control.xml.
Search for update ORACHECK_PAR                 and delete line row. Create Db= false and restart the installation.
Ø  Provide the DB system parameters.
Ø  Select the DB system driver for installation
Ø  Provide standard database users
Ø  Click next for 4 times
Ø  Select kernel and oracle client path
Ø  Now it will ask to restore the db data. Click ok
Ø  Copy the init<dbsid>.sap from source system. Replace S_sid with T_sid and place it in target system /oracle/sid/102/database directory.
Ø  Copy the init<dbsid>.ora from source system and replace S_sid with T_sid and place database directory.
Ø  Copy control.sql file and place it in the target system installation directory.
Ø  Change S_sid with T_sid in b*****.afd log file which is generated during the offline backup.
Ø  Create the folders mirrlogA, mirrlogB, oraarch, saparch, origlogA/cntrl, origlogB/cntrl, sapbackup. Sapcheck, sapdata1/cntrl, sapdata2, sapdata3, sapdata4, sapreorg, saptrace/background and usertrace.
Ø  Copy the backup of source system and keep in the target system sapbackup directory.
Ø  Switch the user  <sid>adm and restore the db using
brrestore –u –b b*****.afd –d disk –k yes –m all
-k denotes compress  mode
-d means device type
-b backup log file
Ø  Click ok to continue and the target system installation will complete itself.
Ø  To ensure that the system copy is done successfully or not. We have to calculate the count of the tables before and after the system copy
RSTABLESEZE, TADIR, DD02L, TFDIR, TSTC, patch level, tables related to material master (MARA), vendor master (LFA1), plants and storage locations (T001l),RFCDES for RFC connections.
Ø   RSTABLESIZE is the report used to find the size of client patch level (ABAP,BASIS,APPL & HR) –screen shots.

 See Related posts