Tuesday, 31 May 2011

WebGui for SAP

1)verify if the ICM is working correctly. Transaction SMICM (ICM Monitor)
displays the central entry point to the ICM configuration and monitoring. After starting this
transaction, you will see the ICM status. Make sure it is running. Check the following ICM
parameters via Menu-> Goto -> Parameters ->Display:

icm/server_port_0 PROT=HTTP,PORT=8000(PORT Number can Varies )
icm/host_name_full server.full.domain

2)With transaction SICF and locate the
services by path
3)Activate the full path to these services
4)Browse to
and login to the

Use Following transcation if you face any service error:
#SIAC_PUBLISH_ALL_INTERNAL (Transcation used to publish all the service )

For more Query Please refer sappandit

ITS WEBGUI Activation (Back End )

  1. Make sure Internet Communication Manager (ICM) is up and running. You can check it by calling transaction "SMICM". A window pops up where the ICMS status should be "Running" and show the green light.
  2. Make sure the Fully Qualified Domain Name is set up on the server. You can check it by calling transaction "RZ10" (Edit profiles). There should be an entry with "icm/host_name_full=mybackend.project.mycompany.intra"
  3. Set "INTERNAL" as the publishing site:
    Start transaction "SE80". In the top menu choose "Utilities(M)" --> "settings...". Right-click on the tab-arrow until you come to tab "Internet Transaction Server". Choose tab "Publish" inside and check mark "Integrated ITS".
  4. Start transaction "SE80". Choose "Internet Service" from the first drop down box located in the middle of the left side pane. Enter "SYSTEM" in the input field below and click the glasses-like button "display" next to it. You will see the ITS service SYSTEM and its components in a tree structure. Right click on "SYSTEM" in the tree and select "Publish" --> "Complete Service" to publish the service. Once the publishing is completed the system will issue a message "Object published successfully; site INTERNAL".
  5. Repeat the previous step with "SHUFFLER" and "WEBGUI" instead of "SYSTEM" to publish both, too.
  6. Set missing parameters:
    Execute transaction "SICF". Enter "Hierarchy Type" = "SERVICE ", then click on checkmark "execute (F8)". Now browse to "default-host" --> "sap" --> "bc" --> "gui" -->"sap" --> "its" --> "webgui". Right-click on it and choose "Display Service". Under tab "Service Data" inside chapter "Interactive Options" click on button "GUI Configuration". In the blank line, insert following parameter:
    Parameter Name: "~webgui_theme"
    Value: "sl"
  7. Clear cache:
    Execute transaction "SITSPMON". Select tab "Template and Mimes tab". Under tabs "Invalidate Template Caches" and "Invalidate MIME Cache", click on "System-wide"
  8. Test WebGUI:
    Execute transaction "SICF". Enter "Hierarchy Type" = "SERVICE", then click on checkmark "execute (F8)". Now browse to "default-host" --> "sap" --> "bc" --> "gui" -->"sap" --> "its" --> "webgui". Right-click on it and choose "Test Service".
    A browser window (Internet explorer) pops up with the URL "http://mybackend.project.mycompany.intra:8002/sap/bc/gui/sap/its/webgui?sap-client=100". It asks for username and password. Enter your credentials that you used for SAP-Logon. Then you should see a screen similar to the initial SAP-Logon screen: a screen titled "SAP Easy Access" with the SAP menu.

Error report :

"No switch to HTTPS occurred, so it is not secure to send a password" 

---> Use FQDN

DNS Not able to Report:

--> Add FQDN in local client
windows -->  window/system32/drivers/etc/hosts
Unix --> /etc/hosts

Thursday, 26 May 2011

Tape Backup Reference

Below link give basic idea about taking Tape backup in unix platform.


-->Aix you can use smitty 

BOTThe tape is positioned at the beginning of the first file.
EOTA tape operation has reached the physical End Of Tape.
EOFThe tape is positioned just after a filemark.
WR_PROTThe tape (or drive) is write-protected. For some drives this can also mean that the drive does not support writing on the current medium type.
ONLINEThe drive has a tape in place and ready for operation.
DR_OPENDoor is open. Depending on the type of drive, this usually means that the drive does not have a tape in place.
IM_REP_ENImmediate report mode. This bit is set if there are no guarantees that the data has been physically written to the tape when the write call returns. It is set to zero only when the driver does not buffer data and the drive is set not to buffer data.
SMThe tape is currently positioned at a setmark. DDS specific.
EODThe tape is positioned at the end of recorded data. DDS specific.
This "generic" status information reports the current density setting for 9-track 1/2 inch tape drives only.

Wednesday, 18 May 2011

Extending the Expiry of License date:

Serveral tricks to be followed to change the expire date:

First Trick :

1. When you install IDES you can move forward your Windows datetime into the future date. eg : 01.01.2020 (22 years foward)
2. After you finished installation, then start SAP MMC for the first time in the future date.
3. Doing any kind of activities using SAP GUI, still in the future date
4. Stop SAP MMC
5. Restart your machine
6. Change your date to the correct date
7. Start SAP MMC again
8. Now, you have IDES for 22 years

Second Trick :

1. Move backward your computer date to installation date before start SAP MMC
2. In some case, this trick only work if you haven't start your SAP MMC after license is expired

If the first and second trick doesn't work, then you can try an illegal trick.

Third Trick.

1. Download "ZAPGUI" (Sap R3 License Keys Generator), you can download from p2p network. eg : eMule
2. open SAP GUI
3. Enter login using sap* or other super user
4. Open t-Code "SLICENSE"
5. Click "Install" button
7. Fill some field in ZAPGUI according to Installation information in SLICENSE
>> Customer Key = fill it with Hardware Key
>> Installation Number = Ints. Number
>> SID = SAP System
>> YYYYMMDD = 99991231
8. Click "Install" button in ZAPGUI
9. Copy license key on the Result Field
10. Paste into "Key" field on SLICENSE
11. Press enter to install new Crack License
12. Stop SAP MMC
13. Restart your Machine
14. Start SAP MMC

Now, you have 2 license, after the trial license is expired then automatically then second license will be active.

Tuesday, 17 May 2011

RHEL Prerequsites for SAP Installation

Red Hat Enterprise Linux 5

1. File System     size(GB)

 /(Or all OS realted file system)  30
 /sapmnt      25
 /usr/sap     25
 /oracle      350
 /sapmedia            40

2. Swap space    40

3.Kernel Parameters
  Change the following parameters in  /etc/sysctl.conf
 Paramater Name

 kernel.msgmni 1024
 kernel.sem 1250 256000 100 1024
 vm.max_map_count 1000000
 kernel.shmmax   0
 kernel.shmall   5242880
Activate these settings with the command "sysctl -p".

5.Java needed to be  installed.
Required rpm for java to be installed  IBMJavaSDK-1.4.2-13.5
Download from ibm site ( create userid )

6.Services should be running  on RHEL 5.5

7.Root Access required
zip utility in all Linux Hosts
FTP/SFTP utility in all Linux Hosts
X Window-Manager

Please Do read the following Notes before starting SAP installation on Linux platform:

Note 1048303 - Red Hat Enterprise Linux 5.x: Installation and upgrade
Note 171356 - SAP software on Linux: Essential information (import)
Note 941735 - SAP memory management for 64-bit Linux systems

Note 1172419 - Linux: Supported Java versions on the x86_64 platform
( IBMJava2-AMD64-142-SDK-1.4.2-13.8.x86_64.rpm )

Note 386605 - SAP Memory Management for Linux (32-bit)

Note 187864 - Linux: Locale Support on Linux

To resolve libxp.so.6 error , install XFree86-libs


if you get error in creating user for sap system
1.) check the log message
2.) oraadm -- password is wrong
3.) then rechange the password to master password
4.) click retry button

Oracle Pacth installation
stop all oracle process before patching
1.) unzip
2.) shutdown
3.) ./runinstaller

4.) startup upgrade
5.) run the script catetcrd.sql
SQL> @?/rdbms/admin/catupgrd.sql

if open migrate  error comes then stop the database and run the catupgrd.sql
then start the database stage by stage
1.)  STARTUP NOMOUNT (startup mount)
2.)  MOUNT (alter database mount )
3.)  OPEN THE DATABASE (alter database open)

then click on retry...

important notes:
OSS-note no. 0112891 (Last-Minute Infos about the IDES-Installation)
OSS-note no. 0039228 (Getting Started with IDES)
OSS-note no. 0043106 (IDES General Customer Information)

Default Users
Just as there is a default client, every installed R/3 System contains default users that have specific predefined authorizations
Client    User                         Default Password
000        SAP*                         06071992
000        DDIC                        19920706
001       SAP*                          06071992
001       DDIC                         19920706
066       EARLYWATCH                   SUPPORT
If You try to delete the user SAP* and DDIC, the password is reset to the password in the R/3 kernel, PASS. The users themselves are retained. This is constitutes a gap in security.
To overcome this we user to Restrict the login on USER SAP*. Through SAP Profile Management

Wednesday, 11 May 2011

Oracle SAP Notes

980426 - Oracle 10.2 software installation on new operating system
871735 - Current Patch set for oracle 10.2.0 ( Prerequisties )
839187 - Applying patch oracle 10.2.0
169706 - Oracle

Get Hardware Information On Linux Using dmidecode Command

dmidecode command reads the system DMI table to display hardware and BIOS information of the server. Apart from getting current configuration of the system, you can also get information about maximum supported configuration of the system using dmidecode

DMI Types
DMI Type id will give information about a particular hardware component of your system. Following command with type id 4 will get the information about CPU of the system

# dmidecode -t 4# dmidecode 2.9
SMBIOS 2.3 present.

Handle 0x0400, DMI type 4, 35 bytes
Processor Information
        Socket Designation: Processor 1
        Type: Central Processor
        Family: Xeon
        Manufacturer: Intel
        ID: 29 0F 00 00 FF FB EB BF
        Signature: Type 0, Family 15, Model 2, Stepping 9
                FPU (Floating-point unit on-chip)
                VME (Virtual mode extension)
                DE (Debugging extension)
                PSE (Page size extension)
                TSC (Time stamp counter)
                MSR (Model specific registers)

Following are the different DMI types available

 Type   Information
          0   BIOS
          1   System
          2   Base Board
          3   Chassis
          4   Processor
          5   Memory Controller
          6   Memory Module
          7   Cache
          8   Port Connector
          9   System Slots
         10   On Board Devices
         11   OEM Strings
         12   System Configuration Options
         13   BIOS Language
         14   Group Associations
         15   System Event Log
         16   Physical Memory Array
         17   Memory Device
         18   32-bit Memory Error
         19   Memory Array Mapped Address
         20   Memory Device Mapped Address
         21   Built-in Pointing Device
         22   Portable Battery
         23   System Reset
         24   Hardware Security
         25   System Power Controls
         26   Voltage Probe
         27   Cooling Device
         28   Temperature Probe
         29   Electrical Current Probe
         30   Out-of-band Remote Access
         31   Boot Integrity Services
         32   System Boot
         33   64-bit Memory Error
         34   Management Device
         35   Management Device Component
         36   Management Device Threshold Data
         37   Memory Channel
         38   IPMI Device
         39   Power Supply

JRE Downloads

Saturday, 7 May 2011

Table contain all Tcode

- TSTC table will contain all the Tcodes and
- TSTCT table will contain all the Tcodes with Texts.

Various Important SAP Basis T-Code
1)   SU01  User Maintainence
2)   SCC4  Client Overview ( Create , Quick Delete , Modify )
3)   SCC5  Deletes a client completely with tables & other factors
4)   SCCL  Local Client Copy
5)   SCC9  Remote Client Copy
6)   SCC3  Client Copy log Analysis
7)   DB02   Storage Management & Database Performance
8)   DB12  SAP Backup Logs
9)   DB14  Database Monitor
10) SM12  Lock Entries
11) SM21  System Logs
12) SM36  Background Job Scheduling
13) SM37  Background Job Monitoring
14) SM31  Table Maintenance
15) SM50  Process Overview
16) ST22    ABAP Dumps
17) ST02   Buffer Analysis
18) ST03   Workflow Analysis
19) RZ04   Operation Mode
20) SE09   Transport Organizer
21) SCC1  Copy as per Transport Request
22) STMS  Transport Management System

SAP Kernel upgrade in unix

1. Login as root

2. Make new backup directory
cd /
mkdir SIDkernel_<date>

3. Create latest kernel backup
cp -pr /sapmnt/SID/exe/* /SIDkernel_<date>

4. Compare the original kernel and the backup
du -sk /sapmnt/SID/exe
du -sk /SIDkernel_<date>

5. Make new directory
cd /
mkdir newkernel_<release>

6. Copy the new downloaded kernel files into /newkernel_<release>

7. Unpack the new downloaded kernel in folder /newkernel_<release>

8. Login as sidadm

9. Stop the SAP System

10. Stop saposcol
saposcol -k

11. Login as root

12. Go to the current kernel directory
cd /sapmnt/SID/exe

13. Copy all extracted support packages into this folder
cp -pr /newkernel_<release>/* /sapmnt/SID/exe

14. Copy back the original file saproot.sh into this folder.
cp -p /SIDkernel_<date>/saproot.sh /sapmnt/SID/exe

15. Go to the current kernel directory
cd /sapmnt/SID/exe
Then run:
./saproot.sh SID

16. Login as sidadm

17. Start the saposcol service

18. Start the SAP system

Sunday, 1 May 2011

Sap Staus

To check the status of the sap system from OS ( Unix ) end.

1.) Login to server
2.) switch to su - sidadm
3.) startsap check 
4.) disp+work

startsap check gives clear picture of application running status & database status.