Вы находитесь на странице: 1из 73

Knowing your current SAP R3

SPAM Level
Some friends ask me how to get information about support package level on their current SAP R/3
server. Actually it is very simple. Just follow this next step:
Type SPAM on your SAPGUI command screen.

You this SPAM screen. SPAM program also has its level. You can see it on the top of it. My current
SPAM version is 6.20 level 26.
To check other support package level, just press Package level button.
On the left side, you see support package component such as SAP_BASIS (SAP Basis
Component), SAP_ABA (Cross Application Component), SAP_APPL (Logistics and Accounting),
SAP_HR (Human Resources), etc.
For level package, just check level component. For example, SAP_BASIS has its level 64.
OK, thats all you need to know about your current support package level. On the next tutorial, Ill
guide you about how to increase your support package level.
====================================================================================

How to Start/Launch Software Update


Manager Tool (SUM) | INTRODUCTION
SUM
By admin August 30, 2016

Software Update Manager Tool


(SUM):
This article covers :

What is Software Update Manager Tool (SUM):


How to Launch / Start Software Update Manager Tool (SUM):
What is Software Update Manager Tool
(SUM):
Software Update Manager Tool (SUM) is Upgrade tool which is used for all kind of
Upgrade,Patching,Migration,Conversion activities.

Previously we used SPAM for ABAP Patch upgrade and JSPM for JAVA Patch
upgrade and EHPI installer for EHP upgrade.Now SAP , Replaced all tools with SINGLE
Tool SUM .
With help of SUM we can do ABAP Support Pack Upgrade, Java Support Pack Upgrade,EHP
upgrade,Version upgrade,Unicode migration,S4 Hana migration.

Without knowing about SUM and its use,Nobody can be expert BASIS ADMIN,

How to Start/Launch Software Update


Manager Tool (SUM):
Follow below steps :

Download SAR FILE from Service Market Place.


Uncar SAR file as SAPCAR -xvf <SUMTOOL.SAR> > It creates SUM directory.
Goto SUM directory which is created after Uncar.
cd /usr/sap/<SID>/SUM
<HSTNAME> ls -ltr
total 48
-rwxr-xr-x 1 ch1adm sapsys 9833 May 17 2015 STARTUP
-rw-rr 1 ch1adm sapsys 316 May 17 2015 summanifest.mf
drwxr-xr-x 3 ch1adm sapsys 256 May 17 2015 jvm
drwxr-xr-x 2 ch1adm sapsys 256 May 17 2015 sapcrypto
drwxr-xr-x 23 ch1adm sapsys 4096 Mar 4 10:53 abap
drwxr-xr-x 24 ch1adm sapsys 4096 Mar 4 12:07 sdt

<>HOSTNAME> ./STARTUP
*** Checking if C++ runtime is installed
*** Starting from /usr/sap/<SID>/SUM/sdt
** Checking username sidadm for compliance
Aug 30, 2016 5:43:05 AM [Info]: *************************
Aug 30, 2016 5:43:05 AM [Info]: Starting Server
Aug 30, 2016 5:43:05 AM [Info]: Reading server configuration.
Aug 30, 2016 5:43:07 AM [Info]: Reading service configuration UseCaseService.
Aug 30, 2016 5:43:07 AM [Info]: Configuring LogManager
Aug 30, 2016 5:43:07 AM [Info]: *************************************************
Aug 30, 2016 5:43:07 AM [Info]: Starting SL Controller listening on port 4241 ...
Aug 30, 2016 5:43:07 AM [Info]: Starting StorageService
Aug 30, 2016 5:43:07 AM [Info]: Initializing SecurityManager
Aug 30, 2016 5:43:11 AM [Info]: Server certificate fingerprint is A1 FC 90 0E 9F 2A AC 6D F6
16 ED 74 5F 2C DB E9
Aug 30, 2016 5:43:11 AM [Info]: Configuring HTTPManager
Aug 30, 2016 5:43:11 AM [Info]: Starting WebstartService
Aug 30, 2016 5:43:11 AM [Info]: Starting RoleService
Aug 30, 2016 5:43:11 AM [Info]: Starting AlertService
Aug 30, 2016 5:43:11 AM [Info]: Starting NotesService
Aug 30, 2016 5:43:11 AM [Info]: Starting ProcessService
Aug 30, 2016 5:43:11 AM [Info]: Starting MIDService
Aug 30, 2016 5:43:11 AM [Info]: Starting FileService
Aug 30, 2016 5:43:11 AM [Info]: LogService switched off.
Aug 30, 2016 5:43:11 AM [Info]: Starting MailService
Aug 30, 2016 5:43:11 AM [Info]: Starting services
Aug 30, 2016 5:43:11 AM [Info]: Starting service UseCaseService
Aug 30, 2016 5:43:12 AM [Info]: Starting MIDService
Aug 30, 2016 5:43:17 AM [Info]: Service UseCaseService started
Aug 30, 2016 5:43:17 AM [Info]: Services started.
Aug 30, 2016 5:43:17 AM [Info]: Starting HTTP server listening on port 4239 ...
Aug 30, 2016 5:43:17 AM [Info]: HTTP server started.
Aug 30, 2016 5:43:17 AM [Info]: SL Controller started.
Once SL Controller is started ,we can launch SUM tool from browser From the logs its clear
that it opens HTTP port on 4239.

Open Browser and start SUM tool as below:


Please Note This procedure is applicable till SUM SP 13 patch ,From SUM SP 14 patch we have
separate method for starting/launching SUM tool.

For latest SUM please refer my article mentioned below:

HOW To Launch /Start NEW Software Update Manager SUM for


SP_14_15_16_17_Upgrade.htm

====================================================================================

Download Software Update Manager SUM


By admin August 30, 2016

How to Download Software


Update Manager SUM Tool
Open Service market Place http://service.sap.com
Then navigate to SAP Support Portal >>Download Software ,It will ask Service Market Place
user ID and password.

After successful authentication itll redirect to below page : Navigate as below to reach Software
Update Manager SUM latest SAR file.
From (A-Z index ) select S then SL TOOlSET

Select SL TOOLSET >> SL TOOLSET 1.0 >>ENTRY BY COMPONENT


>>SOFTWARE UPDATE MANAGER (SUM) >> SOFTWARE UPDATE MANAGER 1.0

Download above SAR File and proceed as below article .

Software Update Manager Tool (SUM)

====================================================================================

HOW to Launch NEW SUM Tool SP 14,15,16 and 17 patch for


doing Upgrade/Patching
Process for launching SUM tool has been changed from SUM Tool patch 14 ,Previolsy SUM tool was
launched with http://<hostname >:4239 till SUM SPS 13.
With the new SUM, there is a new method of starting up the SAP Software Update Manager (SUM) tool.
Presteps:
Download the latest SUM and extract it using the SAPCAR.(Latest SUM SPS patch 17 patch is
available now)
Latest SAP Host Agent in your operating system should be installed.

HOW TO LAUNCH/START SUM:


In new SUM tool ,port has been changed from 4239 to 1129 (https)& 1128(http) and It has been
intregrated with SAP Host agent.
Please follow below steps for laucnching SUM in 14,15,16,17 Patch.
Step 1 : We need to register SAP Host agent with SUM
cd /usr/sap/<SID>/SUM
./STARTUP confighostagent <SID>
Step 2: Restart the SAP Host Agent using the following commands:
cd /usr/sap/<SID>/SUM
<HOSTAGENT directory>/exe/saphostexec -restart
Step 3: Open a web browser window and in the address bar, enter the following URL:
https://<hostname>:1129/lmsl/sumabap/<SID>/doc/sluigui {FOR SSL if it is configured}
OR , If the SSL has not been configured, use http instead of https at the beginning of the URL and use
port 1128:
http://<hostname>:1128/lmsl/sumabap/<SID>/doc/sluigui
Step 4 :In the dialog box that appears, enter the user name <sid>adm and the password.

Launch from Web browser


http://<hostname>:1128/lmsl/sumabap/<SID>/doc/sluigui
I hope ,you really got some useful information related to "SUM Tool " .Can you please give 30 sec of
your time now to have a look into main tutorials collection home page ,I guarantee you will get very
useful tutorials over there.

Here you'll get different set of tutorials <Beginner level ,Advance level ,SAP
Upgrade related,Oracle Basis related ,Solution manager related >

====================================================================================

SAP BASIS-1 SOLUTION


Introduction to Maintenance Planner and How to
Generate Stack File from SAP Maintenance Planner
Open Maintenance Planner from URL given in below screenshot:
Click on Explore System Tracks:
Here track should be defined with verification status OK.

Click on already defined system track:


Below screen will come where we can Plan for new upgrade/patching or we
can say to generate Stack file from Maintenance Planner:
Click on Plan to generate Stack File:
Please follow below screenshot and change accordingly to you upgrade plan.
Below example is for generate stack file for SAP NetWeaver 7.4.

Selected :Upgrade SAP NetWeaver

Selected :SAP NetWeaver 7.4

Selected: Kernel version.


Selected: Stack dependent and Independent Files:
Details of overall selected components:

Download Stack File

I hope ,you really got some useful information related to "Maintenance Planner " .Can you please give
30 sec of your time now to have a look into main tutorials collection home page ,I guarantee you will get
very useful tutorials over there.

Here you'll get different set of tutorials <Beginner level ,Advance level ,SAP
Upgrade related,Oracle Basis related ,Solution manager related >

====================================================================================

How to Uncar Support Packs .SAR Files


SAP
By admin October 19, 2016
How to Uncar Support Packs
.SAR Files SAP
Support Packs files downloaded from the marketplace are in the .car format. To be able to install
a support package, we have to uncar these files. The procedure for uncaring of files is as given
below:
Uncarring the .CAR Support Pack files :
On the Unix Level
Login as <SID>ADM
cd /usr/sap/trans<SID>
/sapmnt/<SID>/exe/SAPCAR -xvf <filename>.CAR
This will extract the support packages into the /usr/sap/trans/EPS/in directory automatically.
====================================================================================

Support Pack Upgrade in SAP Complete


Guide
By admin October 19, 2016

Support Pack Upgrade in SAP-


SPAM-Complete Guide
This Support Pack Upgrade Guide answers below queries:

How to upgrade support package in sap


sap support package upgrade steps
Different support pack upgrade phases
What to do with SPDD and SPAU
Support pack upgrade prerequisites
How to uncar Support packs.
How to update SPAM in sap

Pre-requisites for Support Package :


Download support pack from SAP Service market Place
Uncar Support Packs .SAR Files SAP
Check enough space under /usr/sap/trans directory.
Installing the support package using transaction
SPAM
Log into SAP GUI, client 000 as user upgrade
Go to transaction SPAM

Step 1 : SPAM/SAINT Update:


A SPAM/SAINT Update contains updates Support Package Manager (SPAM) program as well
Add-On Installation Tool SAINT program. SPAM/SAINT update is recommended for support
package upgrade.

Step 2 : Load Package :


Load support packages we have two options:-

1. From Application Server


2. From Front End >> If file size is less than 16 MB.
Normally we do it from Application Server:
From the menu bar select Support Packages >> Load Packages >> From Application Server this
will load all of the support packages into the queue

Step 3 : Display/Define Queue:

Click the Display/Define button

Step 4 : Calculate Queue:


Click the All Components button/Select particular components
Click the Calculate Queue button

Click the Green Check button


Step 5 : Import Queue:
Click the Truck icon at the upper left to execute the import

Click on the green checkmark only after making setting in Start option as below:

As seen in the screenshot above, the phases in a SPAM upgrade are:


Preparation: all the preparatory and test steps are performed in this module (such as the test
import and Add-on conflict verification). >> Select Dialog from Start Option
Import 1: Dictionary objects are imported and activated in this module. The changes that result
from importing and activating the dictionary are still in an inactive state in the system.>> Select
Background from Start Option
Import 2: The remaining import steps are performed in this module, including activating the
inactive dictionary nametabs. Here, since changes are being imported in various transport
objects, no productive operation can take place while this module is running. This avoids any
inconsistencies.>> Select Background from Start Option
Clean Up: All the clean up activities are performed in this module, notably a modification
adjustment of the Repository objects.>> Select Manual/dialog from Start Option
Step 6 : Adjust SPDD and SPAU:
CALL SPAU when below screen comes and capture SPAU and send it to ABAP Team,Similarly
do for SPDD.

Then press Continue button:

SPAU: This transaction is used for adjusting the objects imported during the upgrade

SPDD: This transaction is used for adjusting the data dictionary objects imported during the
upgrade
Click on the green checkmark.

Click on the green checkmark.

Step 7 : Confirm Queue:


Confirm the queue by going to Support Package Confirm
Once Support packs are imported successfully then Run SGEN as below:

Generating objects using transaction SGEN


NOTE: Before you run SGEN make sure that database archiving is off.
Go to transaction SGEN
Click on Generate all objects of selected software component
Click continue
Select All and Press Continue
Select the Server (Note: Production will have CI and Dialog but not Dev, DC or Sandbox)
Click continue
Press the Start Job Directly button (this screen is called Load Generator Job Monitor)
====================================================================================

BW 7.4 and 7.5 version upgrade BW related high level


Pre steps

1. STC01 pre steps:

There are some BW pre-steps that need to be done before downtime (upgrade)
Goto Tcode : STC01
Select Task list: SAP_BW_BEFORE_UPGRADE and execute

Youl get list of steps which need to be done.


There is document also along with each step. Please analyze those steps and perform. From the same
screen steps can be executed directly.

2. Pre steps of ASU toolbox for SAP BW:

Go to Tcode : /n/ASU/UPGRADE
Perform all the pre steps mentioned by this transaction, Most of the steps should be covered by
STC01 transaction executed previously, Please cross check once again.

3. Stop all daemon process

4. Activate all Data Store objects - valid for all SAP BW Releases 3.x and 7.0x

5. Repair Inconsistent Info Packages - transaction RSBATCH


6. Execute upgrade checks - SAP_DROP_TMPTABLES / RSUPGRCHECK

Execute report SAP_DROP_TMPTABLES >> It will remove temporary database objects.


Execute report RSUPGRCHECK >> It will check DDIC inconsistency.

I hope ,you really got some useful information related to "BW Upgrade Presteps for 7.4 and 7.5 " .Can
you please give 30 sec of your time now to have a look into main tutorials collection home page ,I
guarantee you will get very useful tutorials over there.

Here you'll get different set of tutorials <Beginner level ,Advance level ,SAP
Upgrade related,Oracle Basis related ,Solution manager related >

====================================================================================

How to Check System Usage before Upgrade SUM


Whenever we plan for any upgrade (ehp, version), before generating stack file we need to check active
system usage else during configuration phase wel get Stack mismatch error:

Error:
Validation of deployment queue completed with error: The stack does not match the system. Probably
the system was changed after the stack was generated. Synchronize the system with SAP Solution
Manager and then generate a new stack.

Fix:
Please cross check all the system usages are activated before generating stack file.

http://<HOSTNAME:PORT>/utl/UsageTypesInfo

Information about Active Usage Types

Active Usage Types

Product Code UT Code Short Name Description

NetWeaver AS AS Java Application Server Java

NetWeaver AAS AS ABAP Application Server ABAP

ERP ECC ECC Central Component

http://<HOSTNAME:PORT>/utl/UsageTypesDetailedInfo
Detailed information about Usage Types UTL version
Usage Types

Sho
UT Activat List
Product Vend rt Descriptio Acti Requir Cover Deliver Mandat Configu Nati
Co ion ord
Name or Na n ve ed UT ed UT ed ory red ve
de date er
me

SAP
Process
NetWea sap.c AAS ,
PI PI Integratio No No No No No Yes
ver om AS
n
2004s

SAP
Mobile
NetWea sap.c AAS ,
MI MI Infrastruc No No No No No Yes
ver om AS
ture
2004s

http://<HOSTNAME:PORT>/utl/ProductsDetailedInfo

Detailed information about products

Products

Product code Short name Description

NetWeaver NetWeaver SAP NetWeaver 2004s

CRM CRM 2005 SAP CRM 2005

SRM SRM 2005 SAP SRM 2005

SCM SCM 2005 SAP SCM 2005

http://<HOSTNAME:PORT>/utl/ComponentsDetailedInfo

Detailed information about components

Components

Usage Name Vendor Description Type File name PPMS key

PI SAP_XIAF sap.com XI ADAPTER FRAMEWORK 7.00 SCA SAPXIAF**_*.SCA

PI SAP_XITOOL sap.com XI TOOLS 7.00 SCA SAPXITOOL**_*.SCA

PI SAP-XIAFC sap.com XI ADAPTER FRAMEWORK CORE 7.00 SCA SAPXIAFC**_*.SCA

http://<HOSTNAME:PORT>/sap/monitoring/ComponentInfo
http://<HOSTNAME:PORT>/sap/monitoring/SystemInfo
I hope ,you really got some useful information related to "JAVA SYSTEM USAGE " .Can you please give
30 sec of your time now to have a look into main tutorials collection home page ,I guarantee you will get
very useful tutorials over there.

Here you'll get different set of tutorials <Beginner level ,Advance level ,SAP
Upgrade related,Oracle Basis related ,Solution manager related >

====================================================================================

SUM Upgrade Error:

During the upgrade we generally get below error in Check phase if we dont have correct Java Instance
ID of system:

Error:
The central instance ID that would be calculated by the batch config utility is <XYZ>.
The following problem has occurred during step
execution: com.sap.sdt.j2ee.services.servicesimpl.AnalyseChecksResultsException:
The detected instance ID <XYZ> and the one calculated from the box number <ABC> do not match. A
possible reason for that is that you have changed the box number in the central instance
instance.properties file.

Root Cause:
This error comes if during the system copy/refresh java part was not taken care by standard SAP tool
We fixed java manually from Configtool after system refresh.

Solution :
Please take Java export of source system and again perform Java Import in target system using System
copy tool SWPM.
I hope ,you really got some useful information related to "SUM Upgrade " .Can you please give 30 sec of
your time now to have a look into main tutorials collection home page ,I guarantee you will get very
useful tutorials over there.
Here you'll get different set of tutorials <Beginner level ,Advance level ,SAP
Upgrade related,Oracle Basis related ,Solution manager related >

====================================================================================

How to Activate Business Function sap


By admin September 24, 2016

What is Business Function in sap


When we upgrade our SAP system ( EHP upgrade or Version Upgrade) during Stack generation
file ,we select Business Usage and Technical usage and based upon our selection for Technical
Usage at the end of the upgrade some additional Business Function comes in our upgraded
system.

In order to get those business functionalities in upgraded system ,we need to activate
corresponding Business Function else There is no use of upgrade from Business point of view.

How to Activate Business


Function sap
Go to Sap T Code : SFW5
Click on Continue:
Select related Business Function and Press Activate Changes.

NOTE: Its very dangerous to activate Business Functions without knowledge / proper
understanding ,Dont Do it in Production directly as some business functions are not
reversible.
After activation business functions,we need to activate related services from SICF.

Refer SAP documentation for activation of Business Functions for more details.

====================================================================================

How to Deploy SCA file using SDM


Software Deployment Manager Command
Line
By admin September 5, 2016
Software Deployment Manager
tool SDM | How to Deploy SCA
file using SDM Command Line
Software Deployment Manager SDM tool comes with the SAP Java stack.
In SAP Netweaver 2004 ,We used to deploy java support patches using Software Deployment
Manager SDM but later JSPM (JaVa Support Pack Manager) came into picture in NW 2004s

JSPM was advance tool compare to SDM.It automatically calculate Queue and import Java
Patches ,We can say easy method to deploy java Patches.
But internally JSPM calls SDM only and patches are deployed with SDM only.

So we can say SDM is core of JSPM Java Support Pack Manager.


In this tutorial i cover, how we can apply Java patch with SDM,suppose we have single Java
patch so applying with JSPM is time consuming and SDM is good approach in this case.Here i
am explaining to deploy java patches with command line:

Please follow below commands in sequence:

Step 1: Goto SDM program directory:


cd /usr/sap/<SID>/DVEBMGS<instance no>/SDM/program
Step 1: Stop SDM server :
StopServer.sh

Step 3 :Start SDM= JStartup in standalone mode means not intregated with Java-
sdm.sh jstartup mode=standalone
Step 4: Deploy Java Patch with below command-
sdm.sh deploy file=<complete path of SCA/SDA file>

Step 5 :Start SDM-JStartup in integrated mode with JAVA-


sdm.sh jstartup mode=integrated

Step 6: Start SDM server-


StartServer.sh
====================================================================================

Java Post Steps in SAP after Oracle


Upgrade
By admin September 24, 2016
Java Post Steps in SAP after
Oracle Upgrade
If you are running with Dual Stack and You have recently upgrade Oracle to new version then
Java will not come ,Youll have to do some additional steps pointing to correct oracle client
version and correct rdbms.driverLocation.Please follow below steps after oracle upgrade for
Java:

Change the file config.properties as


follows:
1) Change to the correct directory containing the file config.properties

Goto /usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee/configtool

2) Replace the old driver location with the new


one:/oracle/client/<Oracle_client_major_version>x_64/instantclient/<java_class_archive>.jar

where <Oracle_client_major_version> is the major version of the Oracle client that you are using
after this upgrade.
Make sure correct ODBC jar file should be pointed.

Open Config tool and make changes:


1) Change to Configuration Editor mode.

2)Use the Edit mode to replace the driver location in the following property sheets that contain
the string rdbms.driverLocation= followed by the driver location: cluster_data/Propertysheet
instance.properties.IDXXXXXXX/IDXXXXXXX.JavaParameters
where XXXXXXX is the instance number

NOTE
Make sure that you change all occurrences.If you have more than one server or dispatcher you
must modify all relevant property sheets.

3) Close Editor mode and do global search and change correct rdbms.driverLocation.

4) Close the J2EE Engine ConfigTool.


Change the driver location in the
Java instance profile as follows:
1) Change to the correct directory containing the instance profile
<SAPSID>_JC<instance_number>_<host>:/usr/sap/<SAPSID>/SYS/profile

2) Replace the old driver location with the new


one:/oracle/client/<Oracle_client_major_version>x_64/instantclient/<java_class_archive>.jar in
instance profile.

Change the file sdmrepository.sdc as


follows:
1) Goto /usr/sap/<SAPSID>/DVEBMGS<instance_number>/SDM/program/config

2) Search for the following text

<Param type=String hide=false name=jarPaths encrypted=false displayName=Driver


Paths (separated by ;)>

3) If required, replace the old driver location with the new


one:/oracle/client/<Oracle_client_major_version>x_64/instantclient/<java_class_archive>.jar

Change the file bootstrap.properties


as follows:
1) Goto /usr/sap/<instance_ID>/DVEBMGS<instance_number>/j2ee/cluster/bootstrap

2) Open the file with your text editor and search for the property rdbms.driverLocation.

3) Replace the old driver location with the new


one:/oracle/client/<Oracle_client_major_version>x_64/instantclient/<java_class_archive>.jar

Change the file rdb.properties as


follows
1) Goto /usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee/deploying

2) Open the file with your text editor and search for the property rdbms.driverLocation
3) Replace the old driver location with the new
one:/oracle/client/<Oracle_client_major_version>x_64/instantclient/<java_class_archive>.jar

====================================================================================

How to enable SAPGUI SCRIPTING


1.Go to TCODE RZ11

2.Type parameter as sapgui/user_scripting

Click on display.

3.If GUI Scripting is not enabled, then Current value will be FALSE
4. To enable, click on Change Value ()
5. Change the New Value as TRUE and put a tick mark on Switch on all severs .
F. Click on Save.
====================================================================================

HOW to Check SAP HOST AGENT Version


This article covers the steps to check SAP HOST AGENT Version,Please follow
below steps to check version.{Below example is for UNIX/AIX/LINUX OS}

1. Login as root as <sidadm> doesnt have permission for executing SAP HOST AGENT commands.
2. cd /usr/sap/hostctrl/exe {navigate to directory where sap host agent is installed}
3. execute command ./saphostexec -version
Please screenshot shows SAP Host Agent version of my system is at
721_REL and patch level 15.
====================================================================================

How to install SAP Host Agent


This article covers the steps to install SAP HOST AGENT ,Please follow below
steps to install SAP HOST AGENT .{Below example is for UNIX/AIX/LINUX
OS }

1. Login as root as <sidadm> doesnt have permission for executing SAP HOST AGENT commands.
2. cd /usr/sap/tmp
3. mkdir hostagent {create new directory}
4. cd hostagent
5. Uncar SAP HOST AGENT Sar file as belowSAPCAR xvf SAPHOSTAGENT114_114-
20005727.SAR <SAPHOSTAGNET SAR FILE ,We need to download it from service market place>

6. Execute command as below ./saphostexec -install {Execute from root user}


7. Validate if it is installed correctly ,Below 3 processes should be running.

====================================================================================

SAP HOSTAGENT UPGRADE


By admin August 24, 2016
Download and Uncar latest host agent file from SAP market place ,here we uncared under
/usr/sap/TEMP.

Execute command ./saphostexec -upgrade as root.


# ./saphostexec -upgrade
Upgrade service
[Thr 01] Tue Sep 22 06:55:55 2015
[Thr 01] *** WARNING => HostExecUpgrade initialization Unable to stat
/usr/sap/hostctrl/exe/libslcryptokernel.o: No such file or directory [HostExecAuto 125]
[Thr 01] *** WARNING => HostExecUpgrade initialization Unable to stat
/usr/sap/hostctrl/exe/libslcryptokernel.o.sha256: No such file or directory [HostExecAuto 125]
IsUpgradeNecessary: /usr/sap/TEMP/saphostexec is newer than
/usr/sap/hostctrl/exe/saphostexec
Upgrade saphostexec / saphostcontrol
Check Installation Path
saphostexec is already running (pid=5439500). Stopping
ok
Copy Executable ok
Install SYS-V service -> Start /usr/sap/hostctrl/exe/saphostexec
pf=/usr/sap/hostctrl/exe/host_profile <-
start hostcontrol using profile /usr/sap/hostctrl/exe/host_profile
ok
[OK] SAPHostExec / SAPHostControl successfully upgraded

SAP Host agent upgraded successfully.
====================================================================================
HOW TO SAP HOST AGENT START
,STOP,UPGRADE,STATUS,VERSION,INSTALL & UNINSTALL
This article covers the steps to
START,STOP,RESTART,INSTALL,UNINSTALL,STATUS of SAP HOST AGENT
Version,Please follow below steps to check version.{Below example is for
UNIX/AIX/LINUX OS}

1. Login as root as <sidadm> doesnt have permission for executing SAP HOST AGENT commands.
2. cd /usr/sap/hostctrl/exe {navigate to directory where sap host agent is installed}
3. execute command ./saphostexec USE BELOW MENTIONED OPTION
USE OPTION for doing action which you want as for -start use ./saphostexec -
start
-install : Install the agent
-upgrade [-archive SAPHOSTAGENT_ARCHIVE] : Upgrade the agent [from
SAPHOSTAGENT archive]
-uninstall : Uninstall the agent
-restart : Start or Restart the agent
-stop : Stop a running agent
-status : return the status of the agent
-version : return a detailed version
information
Please Read similar Articles of SAP HOST AGENT using same option for more
details.

HOW to Check SAP HOST AGENT Version


How to install SAP Host Agent
SAPHOSTAGENT UPGRADE
====================================================================================

What is SSFS and How we can add SSFS authentication

SSFS (Secure Storage in File System) configuration


What is SSFS:

As of kernel release 7.20, SAP has therefore introduced a new method of securely storing the database
password and for connecting to the database: "Secure Storage in File System" (SSFS). The encrypted
password for the SAP database user is then no longer stored in the database, but in the file system.

Prior to SSFS, the connection between the SAP system (AS ABAP) and the SAP tools that use the ABAP
database interface (R3trans, R3load etc.) to the database via SQLNet (using the database alias name, for
like configured in TNS) worked in such a way that an OPS$ connection (with the database user
OPS$<SID>ADM) that was authorized by the operating system user sidadm was created first ( via
"connect /@TNS"). With this approach access to the table OPS$<SID>ADM.SAPUSER, and to this table
was only allowed. It contains the encrypted password for the actual database connection of the SAP
database user (default name Schema User).
Referred SAP Notes:
1. 1639578 = Documents Basis instructions/steps below.
2. 1623922 = Provides overview on how to connect to the Database using SSFS.
3. 1622837 = Documents steps/instructions to be taken care of by DBA team.

High Level Sequence:


Step 1: Basis change internal connect. This is all accomplished in Note #1 above.
Step 2: DBA change the external connect. This is all accomplished in Note #3 above.
Step 3: DBA drop OPS$ and old authentication

NOTE: No application validation required.

SW pre-requisites:

We should at a minimum, needs to be at Kernel 720, Patch 98. Referred SAP Note 1611877.

Basis Steps to be performed for to enable SSFS authentication:

1. Preparing and securing the file system


Create dir rsecssfs/data and rsecssfs/key Under /sapmnt/SID/global/security.Make sure to give
appropriate permission.

<server:sidadm> mkdir rsecssfs


<server:sidadm> chmod 775 rsecssfs
<server:sidadm> rsecssfs
<server:sidadm> mkdir data
<server:sidadm> mkdir key
<server:sidadm> chmod 777 data key

2. Maintaining the SSFS profile parameters:


Add below mentioned parameter in Default profile-
rsdb_ssfs_connect = 0
RSEC_SSFS_DATAPATH = /sapmnt/<SID>/global/security/rsecssfs/data
RSEC_SSFS_KEYPATH = /sapmnt/<SID>/global/security/rsecssfs/key

3. Maintaining the SSFS environment variable:


Update below mentioned env variables in .sapenv * profiles in home directory of sidadm ( Eg:
/home/sapsys/<SID>adm)

setenv rsdb_ssfs_connect 0
setenv RSEC_SSFS_DATAPATH /sapmnt/<SID>/global/security/rsecssfs/data
setenv RSEC_SSFS_KEYPATH /sapmnt/<SID>/global/security/rsecssfs/key

NOTE: Make sure you are updating these env variable for app server also else app server will not
come up after this activity.

4. Change the ORA SCHEMA user password to your password from BR-Tools:
Find out schema user from env : dbs_ora_schema=<schema>
Please refer any link to change ORA Schema (SAPSR3) user password.

SAP SCHEMA PASSWORD CHANGE


HOW TO CHANGE SCHEMA PASSWORD FROM BRTOOLS

5. Bounce the System

Bounce the system to reflect the parameter changes .

Note: For doing bounce come out from sidadm and do again sudo su sidadm and then
perform system bounce.

6. Setting up the SSFS data storage and checking the access rights and perform check:

After the system bounce execute below mentioned commands as sidadm.

rsecssfx put DB_CONNECT/DEFAULT_DB_USER <schema name> -plain - Use SAPSCHEMA NAME


rsecssfx put DB_CONNECT/DEFAULT_DB_PASSWORD <pwd> - password of schema User

7. Changing to the new connection method:

Change the Profile parameter : rsdb/ssfs_connect = 1 in Default profile .Initially we set it =0.

Update below mentioned env variable in .sapenv * profiles in home directory of sidadm ( Eg:
/home/sapsys/<SID>adm) of all servers.

rsdb_ssfs_connect=1 initially it was set 0.

8. Bounce the System

Bounce the system to reflect the parameter changes .

Note: For doing bounce come out from sidadm and do again sudo su sidadm and then
perform system bounce.

9. Checking the successful changeover/Validation

Check below entries in SM50 work process log --- B read_con_info_ssfs(): DBSL supports extended
connect protocol
B ==> connect info for default DB will be read from ssfs

10. DBA Teams Activity-

DBA will perform below tasks:

Steps Team Details Phase


drop sapuser table DBA drop table ops$<sid>adm.sapuser; note execution - uptime (5
1622837 minutes)
remove the parameter DBA alter system reset remote_os_authent execution - uptime (5
REMOTE_OS_AUTHENT scope=spfile; note 1622837 minutes)

download BRTOOLS DBA per note 1764043, require version 7.20 execution - uptime (10
patch 28 is required minutes)

create brtools user DBA create user brt$adm execution - uptime 5 minutes

create storage DBA Create dir rsecssfs/data and execution - uptime 5 minutes
directories rsecssfs/key Under
/oracle/<SID>/security

drop OPS$ users DBA lock OPS$ users execution - uptime 5 minutes

After getting system back from DBA team perform a clean system bounce and perform system
validation:

I hope ,you really got some useful information related to "SSFS" .Can you please give 30 sec of your time
now to have a look into main tutorials collection home page ,I guarantee you will get very useful tutorials
over there.

====================================================================================

RZ70 SLD CONFIGURATION


In the post i am covering below points:

What is SLD.
How to push ABAP system data to SLD <Step by Step procedure with screenshot>
What is RZ70 and What we don in RZ70.
SLD is System Landscape Directory ,A central repository containing complete System
Landscape information in terms of System component,Hardware Components,Software
Updates and many more.
RZ70 TCODE is used to configure SLD to that local system and used to send
ABAP system data to SLD.Please follow below steps to send System data to
Central SLD.

GO to TCODE : RZ70 > Proceed as per below screenshot.


Fill SLD host name where we have configured SLD of project.You can also
set Job frequency of SLD data transfer job.

Proceed as 1 >2>3>4
Click on activate and Execute.You will get MSG Administration Data activated
successfully
Yes.

It will execute SLD data transfer in dialog also will schedule SLD data
transfer Jon in background.

Here youll see output of data transfer

====================================================================================

How to reset/change ICMADM user password


Password Reset for ICMADM user for webdispatcher:
ICMADM user is used to login into web dispatcher page. It is called Web Administration user to login
into Web Administration Interface.

Suppose the< icmadm> password id locked or you have forgotten the password so below is the trick to
get new password for <icmadm user>.

Step1 :Goto Webdispatcher path:

cd /usr/sap/<SID>/sapwebdisp

Step 2:Delete icmauth.txt file: This file is a authorization file for <icmadm> user and contains
the password information.

rm icmauth.txt

Step 3 :Run BOOTSTRAP: Bootstrap is used to generate new webdispacter profile.But here well
not generate new profile as we have already existing profile and here our objective is to change
get password.

cd /usr/sap/<SID>/sapwebdisp

./sapwebdisp bootsrap [execute by sidadm]


In case of already existing sapwebdisp.pfl ,itll not ask for inputs and directly provide the password.

====================================================================================

Performance Tuning: Check expensive Statement in SAP


Performance Tuning: How to Check Bad/Expensive SQL
Trick: Follow as below
ST04 => Detail Analysis Menu => SQL Request => (Buffer Gets >= 1000,Disk Reads >= 100)=> OK =>

=> (place cursor on 1st row of 'Buffer Gets') => Sort => SQL text is all the way to the right;

dbl click on SQL text => Explain => bdl click on lines below SELECT statement to show which

indices are used (???)

Goto ST04OLD: Click on Detail analysis Menu

Click on SQL Requests:


In the next screen given input as (Buffer Gets >= 1000,Disk Reads >= 100 and execute.

DO sort by Buffer Gets:


Topmost SQL are the Bad SQL ,double click on them and do Explain to optimize the cost.

====================================================================================

How to Execute All Stuck TRFCs at once


Sometime there is a requirement to execute TRFC manually but if no of TRFCs are very high in no then
use below trick to execute them all at once:

Goto Transaction SM58: Execute based upon your selection criteria

In the next screen click as below

In the next screen based upon your selection criteria you can process all TRFC on single click
Press Execute:

Alternative Method: Execute Report RSARFCEX,itll redirect to the same


screen as above.
====================================================================================

====================================================================================

SAP WEB DISPATCHER


INSTALLATION
Below are the steps that we performed on kernel 720 for web dispatcher installation /
rebuild
====================================================================
============
NW702/720 Web dispatcher rebuild tasks on KERNEL 720

1) shutdown webdisp that is running on older version( if still running).


===============================================
===============================================
======
:adm 33> pwd
/usr/sap//sapwebdisp
:adm 34> ls -ltr
total 12672
-rwsr-x 1 root sapsys 1720616 Aug 31 2011 icmbnd
-rwxrwxr-x 1 adm sapsys 4566584 Aug 31 2011 sapwebdisp
-rwxrwxr-x 1 adm sapsys 121699 Aug 31 2011 icmadmin.SAR
drwxr-xr-x 5 adm sapsys 1024 Aug 31 2011 admin
-rw-rw-r 1 adm sapsys 770 Aug 31 2011 sapwebdisp.pfl_OLD
-rw-rw-r 1 adm sapsys 1072 Aug 31 2011 sapwebdisp.pfl_OLD1
-rwxrr 1 adm sapsys 14178 Aug 31 2011 controlWD.sh
drwxrwxrwx 2 adm sapsys 96 Aug 31 2011 hpux-11.0-64
drwxrwxrwx 2 adm sapsys 1024 Sep 2 2011 sec
-rw-rw-r 1 adm sapsys 158 Sep 2 2011 icmauth.txt.bak
-rw-rw-r 1 adm sapsys 203 Sep 2 2011 icmauth.txt
-rwxr-xr-x 1 adm sapsys 973 Feb 3 04:11 sapwebdisp.pfl_bkup2012_0203
-rwxr-xr-x 1 adm sapsys 970 Feb 3 04:13 sapwebdisp.pfl
-rw-rr 1 adm sapsys 725 Mar 21 02:20 dev_webdisp.old
-rw-rr 1 root sapsys 1504 Mar 21 02:20 dev_icmbnd
-rw- 1 adm sapsys 1339 Mar 21 02:20 nohup.out
-rw-rr 1 adm sapsys 48971 Mar 26 12:01 dev_webdisp

:adm 35> pwd


/usr/sap//sapwebdisp
:adm 36> ./controlWD.sh STOP
###### ####### # # #######
# # # # ## # #
########
# # # # # # # #####
########
# # # # # ## #
###### ####### # # #######
===============================================
================
2) Cleanup some old files from the webdisp directory.
===============================================
==============

Imp. Note: DONT DELETE the SEC directory ( this holds the SSL certificate,
intermediate certificates and some other stuff), controlWD.sh,icmbnd &
sapwebdisp files.

Remove the following.

Command: rm Changelog.txt LEGAL.TXT LICENSE.TXT Ver555.pl16


WHICH.TXT icmauth.txt ticket icmadmin.SAR
remove the following directories.
==================================

:adm 44> rm -rf admin


:adm 45> rm -rf hpux-11.11-64
:adm 51> rm -rf hpux-11.0-64

===============================================
save webdispatcher profile
==============================================

Save a copy of the sapwebdisp.pfl profile, before cleaning up the files.

===============================================
===============================================
======
3) Copy from files form /exe directory to /usr/sap//sapwebdisp (or
/sapmnt//sapwebdisp/ where we have already installed dispacther )
===============================================
===============================================
======

cp -p icmadmin.SAR /usr/sap//sapwebdisp
cp -p wdispadmin.SAR /usr/sap//sapwebdisp

===============================================
===============================================
======
4) Extract the files in the sapwebdisp directory
===============================================
===============================================
======

SAPCAR -xvf icmadmin.SAR


SAPCAR -xvf wdispadmin.SAR

:adm 71> SAPCAR -xvf icmadmin.SAR


SAPCAR: processing archive icmadmin.SAR (version 2.01)
x admin/README
x admin/icp/confirm.icp
x admin/icp/do_action.icp
x admin/icp/filter_admin.icp
x admin/icp/monitor.icp
x admin/icp/mpi_info.icp
x admin/icp/nav.icp
x admin/icp/serv_admin.icp
x admin/icp/show_admin.icp
x admin/icp/show_auth.icp
x admin/icp/show_cache.icp
x admin/icp/show_conns.icp
x admin/icp/show_cthr.icp
x admin/icp/show_htab.icp
x admin/icp/show_log.icp
x admin/icp/show_mod.icp
x admin/icp/show_params.icp
x admin/icp/show_pconns.icp
x admin/icp/show_relinfo.icp
x admin/icp/show_serv.icp
x admin/icp/show_slog.icp
x admin/icp/show_trace.icp
x admin/icp/show_wd_params.icp
x admin/icp/statistic.icp
x admin/icp/user_admin.icp
x admin/icp/wdisp_group.icp
x admin/icp/wdisp_host.icp
x admin/icp/wdisp_perm.icp
x admin/icp/wdisp_session.icp
x admin/icp/wdisp_ssl.icp
x admin/icp/wdisp_url.icp
x admin/public/bodyframe.html
x admin/public/bodyframepub.html
x admin/public/css/controls_default.css
x admin/public/css/controls_ie4.css
x admin/public/css/controls_ie5.css
x admin/public/css/controls_ie6.css
x admin/public/css/controls_ie7.css
x admin/public/css/controls_nn4.css
x admin/public/css/controls_nn4l.css
x admin/public/css/controls_nn6.css
x admin/public/css/controls_nn7.css
x admin/public/css/sapbsp.css
x admin/public/default.html
x admin/public/header.html
x admin/public/icons/s_m_crit.gif
x admin/public/icons/s_m_erro.gif
x admin/public/icons/s_m_info.gif
x admin/public/icons/s_m_warn.gif
x admin/public/icons/s_s_locl.gif
x admin/public/icons/s_s_okay.gif
x admin/public/icons/s_s_space.gif
x admin/public/icons/s_s_tl_g.gif
x admin/public/icons/s_s_tl_r.gif
x admin/public/icons/s_s_tl_y.gif
x admin/public/images/11.gif
x admin/public/images/cmenu/Triangle.gif
x admin/public/images/hbrowser/doc_symbol.gif
x admin/public/images/hbrowser/folder_symbol.gif
x admin/public/images/hbrowser/left.gif
x admin/public/images/hbrowser/left_off.gif
x admin/public/images/hbrowser/outleft.gif
x admin/public/images/hbrowser/outleft_off.gif
x admin/public/images/hbrowser/outright.gif
x admin/public/images/hbrowser/outright_off.gif
x admin/public/images/hbrowser/pageleft.gif
x admin/public/images/hbrowser/pageleft_off.gif
x admin/public/images/hbrowser/pageright.gif
x admin/public/images/hbrowser/pageright_off.gif
x admin/public/images/hbrowser/right.gif
x admin/public/images/hbrowser/right_off.gif
x admin/public/images/poweredby.jpg
x admin/public/images/poweredby2.jpg
x admin/public/images/s_s_okay.gif
x admin/public/images/s_s_tl_g.gif
x admin/public/images/s_s_tl_r.gif
x admin/public/images/s_s_tl_y.gif
x admin/public/images/sap_logo.gif
x admin/public/images/sap_logo.jpg
x admin/public/images/saplogo.jpg
x admin/public/images/sapop.gif
x admin/public/images/slogan.gif
x admin/public/images/sort.gif
x admin/public/images/sortasc.gif
x admin/public/images/sortdesc.gif
x admin/public/images/tableview/bottom.gif
x admin/public/images/tableview/bottom_off.gif
x admin/public/images/tableview/down.gif
x admin/public/images/tableview/down_off.gif
x admin/public/images/tableview/filter.gif
x admin/public/images/tableview/pagedown.gif
x admin/public/images/tableview/pagedown_off.gif
x admin/public/images/tableview/pageup.gif
x admin/public/images/tableview/pageup_off.gif
x admin/public/images/tableview/personalize.gif
x admin/public/images/tableview/slogan.gif
x admin/public/images/tableview/top.gif
x admin/public/images/tableview/top_off.gif
x admin/public/images/tableview/up.gif
x admin/public/images/tableview/up_off.gif
x admin/public/images/tagline_gray_text.gif
x admin/public/images/treeview/expander_close.gif
x admin/public/images/treeview/expander_none.gif
x admin/public/images/treeview/expander_open.gif
x admin/public/images/treeview/treeleaf.gif
x admin/public/images/welle.jpg
x admin/public/index.html
x admin/public/js/bspMenu.js
x admin/public/js/menulist.js
x admin/public/welcome.html
x admin/public/welcomebody.html
x admin/publicicp/monitorpub.icp
x admin/publicicp/mpi_infopub.icp
x admin/publicicp/navpub.icp
x admin/publicicp/show_cthrpub.icp
x admin/publicicp/show_htabpub.icp
x admin/publicicp/show_relinfopub.icp
x admin/publicicp/show_servpub.icp
x admin/publicincl/http_subhdl.inc
x admin/publicincl/tools.inc
SAPCAR: 120 file(s) extracted

:adm 72> SAPCAR -xvf wdispadmin.SAR


SAPCAR: processing archive wdispadmin.SAR (version 2.01)
x admin/README
x admin/icp/confirm.icp
x admin/icp/do_action.icp
x admin/icp/filter_admin.icp
x admin/icp/monitor.icp
x admin/icp/mpi_info.icp
x admin/icp/nav.icp
x admin/icp/serv_admin.icp
x admin/icp/show_admin.icp
x admin/icp/show_auth.icp
x admin/icp/show_cache.icp
x admin/icp/show_conns.icp
x admin/icp/show_cthr.icp
x admin/icp/show_htab.icp
x admin/icp/show_log.icp
x admin/icp/show_mod.icp
x admin/icp/show_params.icp
x admin/icp/show_pconns.icp
x admin/icp/show_relinfo.icp
x admin/icp/show_serv.icp
x admin/icp/show_slog.icp
x admin/icp/show_trace.icp
x admin/icp/show_wd_params.icp
x admin/icp/statistic.icp
x admin/icp/user_admin.icp
x admin/icp/wdisp_group.icp
x admin/icp/wdisp_host.icp
x admin/icp/wdisp_perm.icp
x admin/icp/wdisp_session.icp
x admin/icp/wdisp_ssl.icp
x admin/icp/wdisp_url.icp
x admin/public/bodyframe.html
x admin/public/bodyframepub.html
x admin/public/css/controls_default.css
x admin/public/css/controls_ie4.css
x admin/public/css/controls_ie5.css
x admin/public/css/controls_ie6.css
x admin/public/css/controls_ie7.css
x admin/public/css/controls_nn4.css
x admin/public/css/controls_nn4l.css
x admin/public/css/controls_nn6.css
x admin/public/css/controls_nn7.css
x admin/public/css/sapbsp.css
x admin/public/default.html
x admin/public/header.html
x admin/public/icons/s_m_crit.gif
x admin/public/icons/s_m_erro.gif
x admin/public/icons/s_m_info.gif
x admin/public/icons/s_m_warn.gif
x admin/public/icons/s_s_locl.gif
x admin/public/icons/s_s_okay.gif
x admin/public/icons/s_s_space.gif
x admin/public/icons/s_s_tl_g.gif
x admin/public/icons/s_s_tl_r.gif
x admin/public/icons/s_s_tl_y.gif
x admin/public/images/11.gif
x admin/public/images/cmenu/Triangle.gif
x admin/public/images/hbrowser/doc_symbol.gif
x admin/public/images/hbrowser/folder_symbol.gif
x admin/public/images/hbrowser/left.gif
x admin/public/images/hbrowser/left_off.gif
x admin/public/images/hbrowser/outleft.gif
x admin/public/images/hbrowser/outleft_off.gif
x admin/public/images/hbrowser/outright.gif
x admin/public/images/hbrowser/outright_off.gif
x admin/public/images/hbrowser/pageleft.gif
x admin/public/images/hbrowser/pageleft_off.gif
x admin/public/images/hbrowser/pageright.gif
x admin/public/images/hbrowser/pageright_off.gif
x admin/public/images/hbrowser/right.gif
x admin/public/images/hbrowser/right_off.gif
x admin/public/images/poweredby.jpg
x admin/public/images/poweredby2.jpg
x admin/public/images/s_s_okay.gif
x admin/public/images/s_s_tl_g.gif
x admin/public/images/s_s_tl_r.gif
x admin/public/images/s_s_tl_y.gif
x admin/public/images/sap_logo.gif
x admin/public/images/sap_logo.jpg
x admin/public/images/saplogo.jpg
x admin/public/images/sapop.gif
x admin/public/images/slogan.gif
x admin/public/images/sort.gif
x admin/public/images/sortasc.gif
x admin/public/images/sortdesc.gif
x admin/public/images/tableview/bottom.gif
x admin/public/images/tableview/bottom_off.gif
x admin/public/images/tableview/down.gif
x admin/public/images/tableview/down_off.gif
x admin/public/images/tableview/filter.gif
x admin/public/images/tableview/pagedown.gif
x admin/public/images/tableview/pagedown_off.gif
x admin/public/images/tableview/pageup.gif
x admin/public/images/tableview/pageup_off.gif
x admin/public/images/tableview/personalize.gif
x admin/public/images/tableview/slogan.gif
x admin/public/images/tableview/top.gif
x admin/public/images/tableview/top_off.gif
x admin/public/images/tableview/up.gif
x admin/public/images/tableview/up_off.gif
x admin/public/images/tagline_gray_text.gif
x admin/public/images/treeview/expander_close.gif
x admin/public/images/treeview/expander_none.gif
x admin/public/images/treeview/expander_open.gif
x admin/public/images/treeview/treeleaf.gif
x admin/public/images/welle.jpg
x admin/public/index.html
x admin/public/js/bspMenu.js
x admin/public/js/menulist.js
x admin/public/welcome.html
x admin/public/welcomebody.html
x admin/publicicp/monitorpub.icp
x admin/publicicp/mpi_infopub.icp
x admin/publicicp/navpub.icp
x admin/publicicp/show_cthrpub.icp
x admin/publicicp/show_htabpub.icp
x admin/publicicp/show_relinfopub.icp
x admin/publicicp/show_servpub.icp
x admin/publicincl/http_subhdl.inc
x admin/publicincl/tools.inc
SAPCAR: 120 file(s) extracted

===============================================
===============================================
======
5) Extract the new version of SAP cryptos to /usr/sap//sapwebdisp
directory.
===============================================
===============================================
======

SAPCAR -xvf ( New version of SAPCRYPTOs for PA_RISC on SW depot)

:adm 74> SAPCAR -xvf <SAPCRYPTO.SAR


SAPCAR: processing archive x Changelog.txt
x LEGAL.TXT
x LICENSE.TXT
x Ver555.pl32
x WHICH.TXT
x hpux-11.0-32
x hpux-11.0-32/sapgenpse
x hpux-11.0-32/libsapcrypto.sl
x hpux-11.0-32/sapcrypto.lst
x hpux-11.0-64
x hpux-11.0-64/sapgenpse
x hpux-11.0-64/libsapcrypto.sl
x hpux-11.0-64/sapcrypto.lst
x hpux-11.11-32
x hpux-11.11-32/sapgenpse
x hpux-11.11-32/libsapcrypto.sl
x hpux-11.11-32/sapcrypto.lst
x hpux-11.11-64
x hpux-11.11-64/sapgenpse
x hpux-11.11-64/libsapcrypto.sl
x hpux-11.11-64/sapcrypto.lst
x hpux-11.31-64
x hpux-11.31-64/sapgenpse
x hpux-11.31-64/libsapcrypto.sl
x hpux-11.31-64/sapcrypto.lst
x hpux.txt
x ticket
SAPCAR: 27 file(s) extracted

===============================================
===============================================
======
6) Check the sap cryptos. (hpux-11.11-64 in our case ,please check your os
hardware version from uname -a then select correct folder)
===============================================
===============================================
======

:adm 220> cd hpux-11.11-64


sht014g1:adm 221> ll
total 7116
-rwxr-xr-x 1 hraadm sapsys 3564672 Apr 1 19:10 libsapcrypto.sl
-rw-rr 1 hraadm sapsys 40 May 3 14:46 sapcrypto.lst
-rwxr-xr-x 1 hraadm sapsys 76120 Apr 1 19:10 sapgenpse
:adm 222> cdexe
:adm 223> ls -ltr libsapcrypto.sl
-rwxr-xr-x 1 hraadm sapsys 3564672 Jul 22 14:24 libsapcrypto.sl
:adm 224> ls -ltr sapgenpse
-rwxr-xr-x 1 hraadm sapsys 76120 Jul 22 14:25 sapgenpse

check the binaries libsapcrypto.sl and sapgenpse are both the same version
under /exe directory and under /usr/sap//sapwebdisp/hpux-11.11-64
directory.

===============================================
===============================================
======
7) Now upgrade the sapwendisp as ROOT ID.
===============================================
===============================================
======

://usr/sap//sapwebdisp> ls -ltr
total 13234
-rr 1 adm sapsys 878 Nov 13 2001 LEGAL.TXT
-rr 1 adm sapsys 374 Nov 13 2001 ticket
-rr 1 adm sapsys 822 Feb 19 2003 LICENSE.TXT
-rr 1 adm sapsys 2766 Apr 17 2009 WHICH.TXT
-rr 1 adm sapsys 0 Mar 8 2011 Ver555.pl32
-rw-r 1 adm sapsys 1426 Mar 24 2011 hpux.txt
drwxr-xr-x 2 adm sapsys 96 Apr 4 2011 hpux-11.11-32
drwxr-xr-x 2 adm sapsys 96 Apr 4 2011 hpux-11.31-64
drwxr-xr-x 2 adm sapsys 96 Apr 4 2011 hpux-11.0-32
drwxr-xr-x 2 adm sapsys 96 Apr 4 2011 hpux-11.0-64
drwxr-xr-x 2 adm sapsys 96 Apr 4 2011 hpux-11.11-64
-rw-r 1 adm sapsys 33345 May 2 2011 Changelog.txt
-rwxr-xr-x 1 adm sapsys 186251 May 20 2011 icmadmin.SAR
-rwxr-xr-x 1 adm sapsys 186251 May 20 2011 wdispadmin.SAR
-rwsr-x 1 root sapsys 1720616 Aug 31 2011 icmbnd
-rwxrwxr-x 1 adm sapsys 4566584 Aug 31 2011 sapwebdisp
-rwxrr 1 adm sapsys 14178 Aug 31 2011 controlWD.sh
drwxrwxrwx 2 adm sapsys 1024 Sep 2 2011 sec
-rwxr-xr-x 1 adm sapsys 973 Feb 3 04:11 sapwebdisp.pfl_bkup2012_0203
-rwxr-xr-x 1 adm sapsys 970 Feb 3 04:13 sapwebdisp.pfl_03302012
-rwxr-xr-x 1 adm sapsys 970 Feb 3 04:13 sapwebdisp.pfl
-rw-rr 1 adm sapsys 725 Mar 21 02:20 dev_webdisp.old
-rw-rr 1 root sapsys 1504 Mar 21 02:20 dev_icmbnd
-rw- 1 adm sapsys 1339 Mar 21 02:20 nohup.out
-rw-rr 1 adm sapsys 48971 Mar 26 12:01 dev_webdisp
drwxr-xr-x 6 adm sapsys 96 Mar 30 04:17 admin
://usr/sap//sapwebdisp> pwd
/usr/sap//sapwebdisp
://usr/sap//sapwebdisp> id
uid=0(root) gid=3(sys)
groups=0(root),1(other),2(bin),4(adm),5(daemon),6(mail),7(lp),20(users)
://usr/sap//sapwebdisp> ./controlWD.sh UPGRADE
cp -p /usr/sap//sapwebdisp/sapwebdisp
/usr/sap//sapwebdisp/sapwebdisp.old
cp -p /sapmnt//exe/sapwebdisp /usr/sap//sapwebdisp/sapwebdisp
cp -p /usr/sap//sapwebdisp/icmbnd /usr/sap//sapwebdisp/icmbnd.old
cp -p /sapmnt//exe/icmbnd /usr/sap//sapwebdisp/icmbnd
===============================================
==============
UPGRADE DONE; PLEASE check the sticky bit on icmbnd
If needed use Command ==> chmod 4750 icmbnd
===============================================
================

===============================================
===============================================
======

8) Update the path for cyrptos on the sapwebdisp.pfl file.


===============================================
===============================================
======

ssl/ssl_lib=/usr/sap//sapwebdisp/hpux-11.0-64/libsapcrypto.sl

after change

ssl/ssl_lib=/usr/sap//sapwebdisp/hpux-11.11-64/libsapcrypto.sl

===============================================
===============================================
======
9) Now run the bootstrap process to regenerate sapwebdisp.pfl profile and
icmauth.txt file

===============================================
===============================================
======

it will regenerate the new sapwebdisp profile and icmauth.txt file with a new
password.

:adm 57> ./sapwebdisp -bootstrap


SAP Web Dispatcher Bootstrap
============================

This bootstrap will perform the following steps:


1. create profile file sapwebdisp.pfl for SAP Web Dispatcher (if not already
existing)
2. create user for web based administration in file icmauth.txt (if not
already exisiting)
3. start SAP Web Dispatcher with the created profile
After the bootstrap you can use the web based administration

Generating Profile sapwebdisp.pfl


Hostname of Message Server (rdisp/mshost):
HTTP Port of Message Server (ms/http_port): 8106
Checking connection to message serverOK
Unique Instance Number for SAP Web Dispatcher (SAPSYSTEM): 27
HTTP port number for SAP Web Dispatcher: 81
Create configuration for s(mall), m(edium), l(arge) system (default:
medium): m
Profile sapwebdisp.pfl generated
Authentication file icmauth.txt generated
Web Administration user is icmadm with password VlDJrsPu
Restart sapwebdisp with profile: sapwebdisp.pfl
sapwebdisp started with new pid 19492
Web administration accessible with http://:81/sap/wdisp/admin

SAP Web Dispatcher bootstrap ended (rc=0)


:adm 58> ./log/SLOG27: No such file or directory
rslgwr1(11): rstrbopen cannot open SysLog file.
SysLog:lIM120120330043926001949200000IC
:0
:SAP Web Dispatcher&.sddc.sbc.com&19492& icxxrout1914
*** WARNING: Could not start service (rc=-1)
PORT=81,PROT=HTTP,TIMEOUT=60,PROCTIMEOUT=60
*** SAP Web Dispatcher up and operational (pid: 19492) ***

:adm 66> ./controlWD.sh STOP


###### ####### # # #######
# # # # ## # #
########
# # # # # # # #####
########
# # # # # ## #
###### ####### # # #######

:adm 67> cleanipc 27 remove


Show/Cleanup SAP-IPC-Objects V2.3, 94/01/20
===========================================

Running SAP-Systems (Nr):


-
- Clear IPC-Objects of Sap-System 27
-
OsKey: 12716 0x000031ac Shared Memory Key: 16 removed
OsKey: 12762 0x000031da Shared Memory Key: 62 removed
OsKey: 12763 0x000031db Shared Memory Key: 63 removed
OsKey: 12773 0x000031e5 Shared Memory Key: 73 removed
OsKey: 12782 0x000031ee Shared Memory Key: 82 removed
OsKey: 22738 0x000058d2 Semaphore Key: 38 removed
OsKey: 22752 0x000058e0 Semaphore Key: 52 removed
OsKey: 58900127 0x0382be9f SCSA Shared Memory Key: 58900000
removed

Number of IPC-Objects..: 8
Number of removed IPC-Objects: 8

Number of SAP_ES files found:.: 0


Number of SAP_ES files removed:..: 0

:adm 68> ./controlWD.sh START

sid dev_webdisp has WebDispatcher with PID=19492 ; checking if active

*************************************************************
**
NO WebDispatcher running in sid with PID=19492 ; Re-starting WD
*************************************************************
**

Cleaning shared memory first; then issuing nohup command.


sapscsa(5):20872: I am , but should be sapsys .
sapscsa: system(/usr/sap//sapwebdisp/sapmscsa
pf=/usr/sap//sapwebdisp/sapwebdisp.pfl );
sh: /usr/sap//sapwebdisp/sapmscsa: not found.
rslgwr1(16): I cannot get addr of SCSA.
SysLog:lIM120120330044633002087200000IC
:0
:SAP Web Dispatcher&&20872& icxxrout1914
shared memory cleanup done
Issuing the nohup command to start SAP webdisptacher
Sending output to nohup.out

===============================================
====================
Web Dispatcher STARTED with PID=20880 on 03/30/12-04:46:31
===============================================
====================

10) Test the Webdisp URL


===============================================
====================

http://:81/sap/wdisp/admin/public/default.html

12) Shutdown webdispatcher and then copy the old profile values from the
saved sapwebdisp.pfl( saved OLD version) to the new sapwebdisp.pfl and
then restart the webdisp.

Please have a look on my post on introduction of SAP Web dispatcher:

Sap Web dispacther Intro -Stop/Start/Autorestart


====================================================================================

SAP Web dispatcher


Sap Web dispatcher is used to load balancing users requests to SAP application servers.The SAP Web
dispatcher exists between the Internet and our SAP System. It takes HTTP(s) requests from users into
our system.

User Requests -- > Sap Web dispatcher --> Web dispatcher distributes to the application server

Starting the SAP Web Dispatcher:

Goto webdispatcher installation path:

cd /usr/sap/<SID>/sapwebdisp

Execute Command: ./controlWD.sh START <SID>

Stopping the SAP Web Dispatcher:

Goto webdispatcher installation path:

cd /usr/sap/<SID>/sapwebdisp

Execute Command: ./controlWD.sh STOP<SID>

Start the web dispatcher with AUTO Restart: If in case of any crash, web dispatcher will start
automatically.
cd /usr/sap/<SID>/sapwebdisp
Execute Command: ./sapwebdisp pf=sapwebdisp.pfl auto_restart

-auto_restart With this option you can enable high availability for the SAP Web dispatcher at process
level.

-version displays the version of the SAP Web dispatcher

====================================================================================

GRC 10 installation Complete guide high


level
By admin August 19, 2016
GRC 10.1 installation Guide high level steps:
SAP Access Control 10.1, Process Control 10.1, and Risk Management 10.1 are part of the SAP
solutions for governance, risk, and compliance (GRC). SAP Access Control 10.1 runs on SAP
NetWeaver 7.40 SP02 (on non-HANA or HANA databases).

From Basis side high level steps for installation are mentioned below:
Steps for GRC 10.1 system:

1. Install NW 7.40 SP 04 AS ABAP by SWPM.


2. For Access Control, Process Control & Risk Management ,install Software Component:
GRCFND_A. as ADDON from SAINT. or SUM on installed system
3. We need to install Software Component: SLL-LEG ,if we want to use Global Trade system on
installed system
4. We need to install Software component :GRFD_STRUCTURE,if we want to use content life
cycle management on installed system.
5. Activating the Applications in Clients
6. Checking SAP ICF Services >> Activate services
7. Configuring the SAP Net Weaver Gateway
8. Maintaining Plug-in Settings >> Once plug-ins are installed in Backend systems.
9. Activating BC Sets >> Based upon client requirement, we need to activate BC sets ,it may be
related to AC,PC and RM.
10. Creating the Initial User in the ABAP System for process control.

Steps for Backend systems:


Installation of Plug-In for AC/PC 10.1 on ERP
GRCPIERP Used for HR function
GRCPINW Used for Non HR functions.
SLL_PI Used for GTS plugin.
Portal and BW are optional: Portal and BW are optional based on requirement. To enable the
printing of PDFs from Process Control reports and Risk Management reports We need to install
GRC plugin Portal Content & BI content on portal and BW respectively. BI Java Usage Type
must be installed on the same system as the Adobe Document Services. As we dont have any
portal system in our landscape so dont see any requirement to install separate portal.
We can also use NWBC as web client to access GRC ,if we dont use portal.
====================================================================================

SPUMG in Unicode Conversion


By admin September 10, 2016

What is SPUMG
SPUMG is very important tool used in Non unicode to Unicode conversion.It is standrad Tcode
provided by SAP based upon our SAP release.
SPUMG is used in Preconversion Phase:
Preconversion phase means,before doing actual unicode conversion,We need to complete many
presteps or we can say we need to prepare our system for Unicode Conversion so mostly
preconversion presteps are covered bt SPUMG Tcode.

How to Use SPUMG:


SPUMG is used to prepare the database tables of a non-Unicode system for conversion phase
(R3load). Its results are stored in the Export Control Table and the Language List.

Goto Tocde: SPUMG


First thing we need to do with SPUMG is >
Restart SPUMG:
After a restart, you will be displayed the entrance screen of SPUMG. All data which might have
been already entered in SPUMG are now deleted.
Go to Scanner Restart SPUMG
After Restart of SPUMG we can perform highligted Steped with the help of SPUMG.

Please read : How to perform addional steps with SPUMG for Unicode Conversion
http://www.sapbasis1solution.com/unicode-conversion-preparation-spumg/
====================================================================================

Unicode Conversion Preparation with


SPUMG
By admin September 10, 2016

Unicode Conversion Preparation


with SPUMG
SPUMG plays major role in performing unicode conversion preparation steps.In this article ill
cover how we can perform major presteps with SPUMG.

First Please read to Undersatnd What is SPUMG and How to start it.

Start SPUMG:
Go to Tcode: SPUMG and click on addional steps button as per below screen.

with this step report UMG_ADD_PREP_STEP will be initiated which consists of several reports
which were created for deleting corrupt or obsolete table data prior to Unicode conversion. On
the next screen the included reports are displayed. Choose Background. All reports will be
executed automatically.
Once Job finish then check status of all steps mentioned above.

====================================================================================

TDMS- TEST DATA MIGRATION


SERVER PRESTEPS
By admin August 16, 2016
SAP Test Data Migration Server (SAP TDMS) is a high-speed data tool that transfers business
data from your SAP production system to your development, test, quality training system.
By enabling the transfer of just the relevant set of application data from the SAP production
system, SAP TDMS allows you to create a lean and consistent non-production system.
Recommended system settings for TDMS
Refer to OSS Note 890797 for the recommended settings for Control / Central / Sender /
Receiver systems.

Some of the required system settings are given below:

Central system:
Dialog work processes 15 (minimum 6)

Background work processes 10 (minimum 8)

Profile parameters: rec/client=off, rdisp/max_wprun_time=900 (s)

DB settings logging switched off (NOARCHIVELOGMODE)

System change options (SCC4) Allowed changes to repository and Cross-client customizing

Sender system:
Dialog work processes 15 (minimum 10)

Background work processes 10 (minimum 8)

Profile parameters: rdisp/max_wprun_time=1800 (s)

Receiver system:
Dialog work processes 15 (minimum 10)

Background work processes 10 (minimum 8)

Profile parameters: rdisp/max_wprun_time=1800 (s)

DB settings logging switched off (NOARCHIVELOGMODE)

UNDO tablespace ~2% of estimated data transfer, UNDO RETENTION TIME set
appropriately (lowered)

Make sure to set the Database in NOARCHLOG mode for Central & Receiver Systems before
starting the copy.

The Database will be unmounted and remounted during the archivelog mode change.

Also, please make sure you have adequate freespace available in DB of the Receiver system.

Also, keep an eye on filesystem /usr/sap/ of Central system as the size of stats file will increase
rapidly during copy which may lead to the filesystem getting full.
====================================================================================

Checking Package and Patch Versions Installed on the SAP


Application Server
To use the QuickTest Professional Add-in for SAP Solutions, you must confirm that you
have the correct support package and kernel patch levels for your software component
release. The following table shows the minimum required versions and levels. You must
have these versions and levels or higher:

Software Component Release Support Package Kernel Patch Level

SAP_APPL 31I SAPKH31I96 Kernel 3.1I level 650

SAP_APPL 40B SAPKH40B71 Kernel 4.0B level 903

SAP_APPL 45B SAPKH45B49 Kernel 4.5B level 753

SAP_BASIS 46B SAPKB46B37 Kernel 4.6D level 948

SAP_BASIS 46C SAPKB46C29 Kernel 4.6D level 948

SAP_BASIS 46D SAPKB46D17 Kernel 4.6D level 948

SAP_BASIS 610 SAPKB61012 Kernel 6.10 level 360

To check the support package:

1. Log on to your SAP server.


2. Run the SPAM transaction.

3. In the Directory section, select All Support Packages and click the Display button.
4. The All packages window opens. Verify that the correct package is installed for the SAP
release you are using (see Checking Package and Patch Versions Installed on the SAP
Application Server).
If the correct package is installed, a green light icon is displayed in the Status column.
If you do not have the required package installed, download and install it.
For more information on downloading and installing the required package, see SAP OSS
note # 480149.

To check the kernel patch level:

1. Log on to your SAP server.


2. Select System > Status. The System: Status dialog box opens.

3. Click the Other kernel information button . The System: Kernel information dialog
box opens.
4. In the Kernel information section, check the value of the Sup. Pkg. lvl.

If the level is lower than the required level for the SAP release you are using
(see Checking Package and Patch Versions Installed on the SAP Application Server), you
must download the latest kernel version and upgrade your existing one.
For more information on downloading and installing the required kernel patch level, see
SAP OSS note #480149.

====================================================================================